We can add support for network names on the client / dashboard level
as an UX enhancement. Client name resolving code sounds mostly useful.
On Fri, Feb 28, 2014 at 11:43 AM, Alexander Ignatov
aigna...@mirantis.com wrote:
Andrew,
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'.
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.
Regards,
Alexander Ignatov
On 28 Feb 2014, at 04:09, Andrew Lazarev alaza...@mirantis.com wrote:
Hi Team,
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
https://bugs.launchpad.net/savanna/+bug/1282027 was merged and savanna
expects only ID here. Is it intentional restriction? What is the reasoning?
Referencing by name is comfortable.
Thanks,
Andrew.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Sincerely yours,
Sergey Lukjanov
Savanna Technical Lead
Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
