cor...@inaugust.com (James E. Blair) writes: > Once we switch nodepool to use shade, we should consume that > automatically. In the mean time, I think the best solution for > current-nodepool is to revert the change to net-name and more-or-less > mirror the shade behavior change by adding a new config attribute to > nodepool providers, 'external-net-name', which will indicate to nodepool > which network is external. Or alternatively, add an 'external: True' > attribute to the net-name list. I will work on that today.
I wrote this patch to implement (approximately) this approach: https://review.openstack.org/252000 It deprecates the current net-id and net-name options in favor of a more flexible format that lets us set attributes like 'public', but maintains backwards compatibility. -Jim _______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
