[openstack-dev] [tripleo] Building images separation and moving images into right place at right time
Arkady_Kanevsky at DELL.com
Arkady_Kanevsky at DELL.com
Fri Apr 17 17:59:43 UTC 2015
Dell - Internal Use - Confidential
If images under consideration are for overcloud nodes then they will changing all the time also. It all depends on which layer you are working on.
Just consider images for overcloud nodes as a cloud application, and then follow rules you would apply to any cloud application development.
I feel that we are in agreement on the goal and only specific work to be done is under discussion.
Do you have a blueprint or spec? That will simplify discussion.
Thanks,
Arkady
-----Original Message-----
From: Jaromir Coufal [mailto:jcoufal at redhat.com]
Sent: Friday, April 17, 2015 10:54 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [tripleo] Building images separation and moving images into right place at right time
Hey Arkady,
yes, this should stay as fundamental requirement. This is tandard Glance functionality, I just want to separate discover and deploy images since these will not be very likely subject of change and they belong into undercloud installation stage.
That's why I want to separate overcloud building images (which is actually already there) so that user can easily replace this image with different one.
-- Jarda
On 17/04/15 16:18, Arkady_Kanevsky at DELL.com wrote:
> We need an ability for an Admin to add/remove new images at will to deploy new overcloud images at any time.
> Expect that it is standard glance functionality.
>
>
> -----Original Message-----
> From: Jaromir Coufal [mailto:jcoufal at redhat.com]
> Sent: Friday, April 17, 2015 8:51 AM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [tripleo] Building images separation and
> moving images into right place at right time
>
> Hi All,
>
> at the moment we are building discovery, deploy and overcloud images all at once. Then we face user to deal with uploading all images at one step.
>
> User should not be exposed to discovery/deploy images. This should happen automatically for the user during undercloud installation as post-config step, so that undercloud is usable.
>
> Once user installs undercloud (and have discovery & deploy images at their place) he should be able to build / download / create overcloud images (by overcloud images I mean overcloud-full.*). This is what user should deal with.
>
> For this we will need to separate building process for discovery+deploy images and for overcloud images. Is that possible?
>
> -- Jarda
>
> ______________________________________________________________________
> ____ OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> ______________________________________________________________________
> ____ OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
More information about the OpenStack-dev
mailing list