<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Andrew,</div><div><br></div><div>This change was needed to heat engine. In case when heat engine and neutron env are used Heat stacks fails with ‘Bad network UUID error’.</div><div>This happen because neutron client can’t work with networks by names. So checking network IDs at the validation stage prevents from stack fails and cluster errors. Also savanna expects IDs for all resources used during cluster creation (flavors, images etc). Now there are networks.</div><br><div>
<div>Regards,</div><div>Alexander Ignatov</div><div><br></div><br class="Apple-interchange-newline">
</div>
<br><div><div>On 28 Feb 2014, at 04:09, Andrew Lazarev <<a href="mailto:alazarev@mirantis.com">alazarev@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi Team,<div><br></div><div>I was always using <"floating_ip_pool": "net04_ext"> construction and it worked fine. Now it responds with validation error "Floating IP pool net04_ext for node group 'manager' not found" because <a href="https://bugs.launchpad.net/savanna/+bug/1282027">https://bugs.launchpad.net/savanna/+bug/1282027</a> was merged and savanna expects only ID here. Is it intentional restriction? What is the reasoning? Referencing by name is comfortable.</div>
<div><br></div><div>Thanks,</div><div>Andrew.</div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></body></html>