-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
heat-jeos image should print out the location of the generated image #3
Comments
It is really confusion to split the image creation into I didn't realize that I needed to do the first one until my image didn't work and found that the cfn-tools were all of size 0 How about the following:
|
I'm in favour of all of these suggestions except for this: I think we should still support a command that does the registration. Right now when you want to set up heat, you have to do a lot of steps and one of them is:
and it does everything. Now you'd need to have two commands:
It would complicate the getting started guide (the What if we added a Is there a reason we should tear out glance registration completely? |
At the moment I believe we need glance registration as a feature. If Richard Jones does something with registration of images (see http://fedoraproject.org/wiki/Features/OpenStack_using_Oz_for_image_building) it may make more sense to integrate with that upstream longer term. The suggested flag --register-with-glance makes good sense Regards |
OK, sounds good to me. Main point is to make it more obvious to use. |
My latest suggestion on mailing list based upon Angus's original thoughts: heat-jeos list id distro name distro version archF16-x86_64 Fedora 16 x86_64 distro name/version/arc would be parsed from the tdl files heat-jeos create U10.04.4-amd64 --register-with-glance |
Fixes issues #2 and #3 We'll use only two commands: `list` and `create`. `list` displays the bundled Oz templates and `create` builds the JEOS and optionally registers it with Glance. The OS metadata (distro, arch, version) are no longer passed as the cli arguments. ISO location is read from the template. The user can pass their own custom template. Signed-off-by: Tomas Sedovic <tomas@sedovic.cz>
unless you know the location of the images you don't know the location of it.
Also what is the point of register? Isn't using glance just as easy?
How about:
The text was updated successfully, but these errors were encountered: