On 20/03/15 14:33, Rob Pothier (rpothier) wrote:
Hi All,
It was brought to my attention that the recent changes with the vnic_type
possibly should not include the colon in the property value.
In the earlier versions of the review the colon was not in the property,
and was appended later.
https://review.openstack.org/#/c/129353/4..5/heat/engine/resources/neutron/port.py
let me know if this should go back to version 4, and I will open a bug
and fix it.
I did some testing and confirmed that the YAML parser handles it without
issue, though it does look a bit weird. I guess we need a policy on
extension APIs in general, but after consideration using a colon is
probably not a terrible way to denote it.
cheers,
Zane.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
