Re: [Openstack] [HEAT] order in attributes list

2018-04-04 Thread Pavlo Shchelokovskyy
Hi, AFAIU the get_attr function does not use the values you've passed to Heat in the resource definition, instead it fetches their actual values from Neutron (basically making a 'port show' API call), and Heat does nothing wrt to ordering afterwards. Btw AFAIR this is exactly why heat requires a

[Openstack] [HEAT] order in attributes list

2018-04-03 Thread Volodymyr Litovka
Hi colleagues, I have the following HOT configuration of a port:   n1-wan:     type: OS::Neutron::Port     properties:   fixed_ips:     - { subnet: e-subnet1, ip_address: 51.x.x.x }     - { subnet: e-subnet2, ip_address: 25.x.x.x } when I try to extract these values in template