Actions
Feature #12479
open
Configure API revision for vSphere Compute Resource
Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - VMware
Target version:
-
Description
Fog defaults to using 4.0 API revision to connect to vSphere. For features like storage pools or setting the boot order one needs to use at least 5.0. As a user I should be able to configure the api revision Foreman passes to fog.
Updated by The Foreman Bot about 9 years ago
- Status changed from New to Ready For Testing
- Assignee set to Timo Goebel
- Pull request https://github.com/theforeman/foreman/pull/2913 added
Updated by Timo Goebel about 9 years ago
- Blocks Feature #12436: As a user I want to deploy vSphere vms on a storage pods added
Updated by Timo Goebel about 9 years ago
- Blocks Bug #5510: Set network as first boot device for VMs in VMware compute resources added
Updated by Brandon Weeks about 9 years ago
- Blocked by Refactor #11729: Update fog to 2.0.0 added
Updated by Timo Goebel about 9 years ago
Fog now chooses the most recent API version by default, see https://github.com/fog/fog-vsphere/pull/3
We might want to show this in the GUI, though.
Updated by Timo Goebel about 9 years ago
- Blocks deleted (Feature #12436: As a user I want to deploy vSphere vms on a storage pods)
Updated by Timo Goebel about 9 years ago
- Blocks deleted (Bug #5510: Set network as first boot device for VMs in VMware compute resources)
Updated by Dominic Cleal almost 9 years ago
- Blocked by deleted (Refactor #11729: Update fog to 2.0.0)
Updated by Dominic Cleal almost 9 years ago
- Blocked by Refactor #12612: Update fog to 1.37.0 added
Updated by Dominic Cleal almost 9 years ago
- Status changed from Ready For Testing to New
- Assignee deleted (
Timo Goebel) - Pull request deleted (
https://github.com/theforeman/foreman/pull/2913)
PR was closed, but the fog-vsphere code for choosing the latest API revision should be active now.
Actions