Bug 1212467
| Summary: | [RFE] [RDO-Manager] [CLI] Add an ability to create an overcloud image associated with kernel/ramdisk images in one CLI step | ||
|---|---|---|---|
| Product: | [Community] RDO | Reporter: | Jaromir Coufal <jcoufal> |
| Component: | rdo-manager-cli | Assignee: | Ana Krivokapic <akrivoka> |
| Status: | CLOSED EOL | QA Contact: | Shai Revivo <srevivo> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | trunk | CC: | calfonso, jcoufal, mburns |
| Target Milestone: | --- | Keywords: | RFE, Triaged |
| Target Release: | Kilo | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-19 15:54:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Right now we can do:
openstack overcloud image build --all
To create the images, and
openstack overcloud image upload
To load them into glance.
Is that what you meant, or just for one specific image?
The image upload counts with hardcoded image names and gives no flexibility. From my perspective I wanted to have ability to upload only overcloud-full image with associated kernel/ramdisk. This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen. |
at the moment I have to run: # Save parameters so that we don't have to repeat them in following commands image_name="overcloud-full" image_location="./" # Create kernel/ramdisk images (use above defined variables) openstack image create ${image_name}-kernel --public --disk-format=aki --container-format=aki --file="${image_location}${image_name}.vmlinuz" openstack image create ${image_name}-ramdisk --public --disk-format=ari --container-format=ari --file="${image_location}${image_name}.initrd" # Save kernel and ramdisk IDs kernel_id=$(openstack image show ${image_name}-kernel | grep ' id ' | awk '{print $4}') ramdisk_id=$(openstack image show ${image_name}-ramdisk | grep ' id ' | awk '{print $4}') # Create overcloud-full image with associations to kernel and ramdisk images openstack image create overcloud-full \ --public \ --disk-format=qcow2 \ --container-format=bare \ --property kernel_id=$kernel_id \ --property ramdisk_id=$ramdisk_id \ --file="${image_location}${image_name}.qcow2" In order to create an overcloud image. Would be nice if we can automate that with something like: openstack overcloud image create --name=overcloud-full It will search for images with given name, create kernel & ramdisk images and create overcloud-full with those associations in the end.