You are viewing documentation for a previous version of Platform9 products. For the latest Private Cloud Director documentation, click here.
Managed OpenStack
v5.10
×
Introduction
Getting Started
Infrastructure
Networks
Volumes and Snapshots
Images
Instances
Flavors
Tenant Administration
User Administration
Authentication & Authorization
Accessing VMs
Application Management
CLI Access
Monitoring & Alarms
Troubleshooting
Tutorials
Support
Regions
Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
Use vSphere Datastore as backing for Image Catalog
Summarize Page
Copy Markdown
Open in ChatGPT
Open in Claude
This Tutorial describes steps required for setting up a vSphere Datastore as a backing for your OpenStack Glance Image Catalog in Platform9 Managed OpenStack.
Set Up OpenStack Glance:
- Enabling Glance datastore feature requires authorization of VMware gateway by specifying the datastore and appliance IP that should to be paired with Platform9 Glance.

- Exactly one datastore can be paired with Platform9 Glance.
- Any glance commands must be executed from a machine that can access the gateway.
How it Works:
Once the initial setup is complete, all Glance operations will use the VMware datastore as the backend.
- Templates, however will be discovered based on the datastores paired with Nova.
- Image upload to the datastore is an HTTP PUT on the datastore directly and does not invoke any vCenter operation.
- Datastores paired with Nova Compute and Glance need not be the same.
- All glance images can be found at
/pf9/openstack_glancepath on the Glance datastore.
Using OpenStack Glance Command Line:
Glance command line client can be used to perform image operations to datastores. Below are few examples.
- Creating an image:
Two Platform9 specific properties need to be specified for the uploading the image, ie., pf9_virtual_size and pf9_description. pf9_virtual_size is the virtual size of the image and pf9_description is optional. Additionally, the property
vmware_ostypeshould be specified correctly, especially for Windows OSes. You can refer to the list of supported VMware OS types here. If you have more than one (1) region in your Platform9 deployment, you will also need to specify the region via the--os-region-nameparameter.
OpenStack
glance image-create \[--os-region-name <region name>] \--name cirros \--file /path/to/image/filename.vmdk \--container-format=bare \--disk-format=vmdk \--property vmware_disktype="preallocated" \--property vmware_adaptertype="ide" \--property pf9_virtual_size="40894464" \--property vmware_ostype="otherGuest64" \--property pf9_description="glance cmdline image upload"List Images:
OpenStack
glance image-delete <image-id>Display properties of an image:
OpenStack
glance image-delete <image-id>Delete image:
OpenStack
glance image-delete <image-id>Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Last updated on
Was this page helpful?
Next to read:
InstancesDiscard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message