Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VIO image upload best practices (78960)

Last Updated: 6/17/2022Categories: Best PracticesTotal Views: 5756Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Details

When uploading image to glance through horizon/CLI, it may timeout before completion due to the size of the image or transfer speed.

If the image import is done through the Horizon UI,

The image will first upload to horizon temp folder,

The image will be transferred to glance-api working folder,

Conversion of the image would be done if needed

Upload to the glance datastore (by default NFC is used)

Note:  The horizon session timeout is 1 hour.  If the operation can not complete within 1 hour, the session will be terminated, halting the image upload process.

If the image import is done through the CLI,

The image will upload to the glance-api working folder,

Conversion of the image would be done if needed,

Upload to the glance datastore (by default NFC is used)

Note:  The

image_transfer_timeout default value is 7200s.  If the operation can not complete within 2 hours, the session will be terminated, halting the image upload process.

Solution

To help speed up the process:

Pre-convert the image to VMDK to save time on import.   (qemu-img for example)

Use CLI commands to remove the extra step of upload to horizon tmp folder.

Pass property value vmware_vcenter_upload=true while uploading image to disable NFC upload.

For example

# openstack --insecure image create ‘ubuntu’ --disk-format vmdk --file /root/ess/xenial-server-cloudimg-amd64-disk1.vmdk --property vmware_vcenter_upload=true --container-format bare --public

For large images, check the size of the root disk on the controllers.  You would need at least 2x the image size in space available.  To increase the size of the controllers disk, follow Extending root disk of VIO controllers

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
将 Cloud Director 9.5 迁移到 10.0 的过程中，出现“无法读取或写入配置文件: 密钥库已被篡改，或密码不正确”错误 (78924)

KB
•
VMware Intelligent Hub 20.04 for iOS リリースのお知らせ (78889)

KB
•
VMware Update Manager の診断情報の収集 (1003693)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Integrated OpenStack

Related Versions:

VMware Integrated Openstack 7.x

Take Our Survey

Support Assistant