<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>If thats true, then it could probably be changed and a note placed in the release/migration notes.<br>
<br>
Thanks,<br>
Kevin <strong>
<div><font face="Tahoma" color="#000000" size="2"> </font></div>
</strong>
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> Chris Friesen<br>
<b>Sent:</b> Thursday, May 21, 2015 4:18:20 PM<br>
<b>To:</b> openstack-dev@lists.openstack.org<br>
<b>Subject:</b> Re: [openstack-dev] [Nova][libvirt] Understand why we lookup libvirt domains by instance name<br>
</font><br>
<div></div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On 05/21/2015 03:42 PM, Mathieu Gagné wrote:<br>
> On 2015-05-21 3:38 PM, Chris Friesen wrote:<br>
>> On 05/21/2015 03:20 PM, Mathieu Gagné wrote:<br>
>>> On 2015-05-21 3:13 AM, Daniel P. Berrange wrote:<br>
>>>> You do know you can configure the instance name used...<br>
>>>><br>
>>>> eg in nova.conf<br>
>>>><br>
>>>> instance_name_template='inst-%(uuid)s'<br>
>>>><br>
>>><br>
>>> Please note that you CANNOT change instance_name_template ones instances<br>
>>> are created otherwise they become unmanageable by Nova. This is because<br>
>>> Nova tries to find the libvirt instance by its name instead of its UUID.<br>
>>> So since instances were spawned with the old value, it won't find<br>
>>> existing instances using the new value.<br>
>>><br>
>>> And no, I haven't found a way to rename an instance without<br>
>>> redefining/restarting it in libvirt.<br>
>><br>
>> Is there any reason why we couldn't default to using something like<br>
>> 'inst-%(uuid)s' for the instance name?<br>
>><br>
><br>
> I guess it's for the reason I mentioned above:<br>
><br>
> To not break all OpenStack installations on Earth running with default<br>
> config values.<br>
><br>
<br>
So that's not breaking *upgrades* of all OpenStack installations with default <br>
config values, which is a slightly different thing.<br>
<br>
Chris<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</span></font>
</body>
</html>