Open Stack

On 05/22/15 at 10:16am, Deepak Shetty wrote:
>On Fri, May 22, 2015 at 5:19 AM, Mathieu Gagné <mgagne at iweb.com> wrote:
>
>> On 2015-05-21 4:18 PM, Chris Friesen wrote:
>> >>>
>> >>
>> >> I guess it's for the reason I mentioned above:
>> >>
>> >> To not break all OpenStack installations on Earth running with default
>> >> config values.
>> >>
>> >
>> > So that's not breaking *upgrades* of all OpenStack installations with
>> > default config values, which is a slightly different thing.
>> >
>>
>> Yes it will. Try to change instance_template_name and manage existing
>> instances. You won't be able.
>>
>> The above scenario is the same as upgrading OpenStack Nova and having
>> instance_template_name changes its default value. Unless someone patches
>> Nova to use the instance UUID instead of its name to find it in libvirt.
>>
>
>Novice question:
>   For each instance I believe we store the name (instance-0000xx) and uuid
>in
>the DB ? If yes, then can't nova lookup using uuid given the name or vice
>versa
>since the mapping to name - uuid is possible from DB ?

The name is not stored in the database, or at all.  It is generated by a 
config option template on each database access.  So if the config option 
is changed all instance names will change.

>
>
>>
>> --
>> Mathieu
>>
>> __________________________________________________________________________
>> 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