Project

General

Profile

Actions

Feature #12436

closed

As a user I want to deploy vSphere vms on a storage pods

Added by Timo Goebel about 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

vSphere knows the concept of Storage Pools. It would be nice if a user could deploy a vm to a storage pool instead of a datastore.


Related issues 2 (0 open2 closed)

Related to Foreman - Bug #14051: image-based provisioning via vmware fails on `wrong number of arguments (2 for 1)`Resolved03/04/2016Actions
Blocked by Foreman - Refactor #12612: Update fog to 1.37.0ClosedTimo Goebel11/26/2015Actions
Actions #1

Updated by Dominic Cleal about 9 years ago

  • Category set to Compute resources - VMware
Actions #2

Updated by Timo Goebel about 9 years ago

  • Blocked by Feature #12479: Configure API revision for vSphere Compute Resource added
Actions #3

Updated by Timo Goebel about 9 years ago

  • Subject changed from As a user I want to deploy vSphere vms on a storage pool to As a user I want to deploy vSphere vms on a storage pods
Actions #4

Updated by Timo Goebel about 9 years ago

vSphere actually calls this storage pods in the api or simply Datastore Clusters

Actions #5

Updated by The Foreman Bot about 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2915 added
Actions #6

Updated by Timo Goebel about 9 years ago

  • Blocked by deleted (Feature #12479: Configure API revision for vSphere Compute Resource)
Actions #7

Updated by Timo Goebel about 9 years ago

Actions #8

Updated by Anonymous almost 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #9

Updated by Dominic Cleal almost 9 years ago

  • Translation missing: en.field_release set to 71
Actions #10

Updated by Dominic Cleal almost 9 years ago

  • Related to Bug #14051: image-based provisioning via vmware fails on `wrong number of arguments (2 for 1)` added
Actions

Also available in: Atom PDF