Jon,
That seems like a bug in your openstack. The point of 'latest' is that it is supposed to just be a copy of the "latest" (which would be 2015-10-15 for you). It should have the network-data.json file.
From the openstack that I can get at, I see network_data.json available in 2015-10-15 (liberty) and later which aligns with what the code says should be there.
Jon,
That seems like a bug in your openstack. The point of 'latest' is that it is supposed to just be a copy of the "latest" (which would be 2015-10-15 for you). It should have the network-data.json file.
the code that generates that is in /github. com/openstack/ nova/blob/ master/ nova/api/ metadata/ base.py
https:/
From the openstack that I can get at, I see network_data.json available in 2015-10-15 (liberty) and later which aligns with what the code says should be there.
$ mount /dev/sr0 /mnt 04-04/meta- data.json meta-data. json 2012-08- 10/meta_ data.json 2013-04- 04/meta_ data.json 2013-10- 17/meta_ data.json 2013-10- 17/vendor_ data.json 2015-10- 15/meta_ data.json 2015-10- 15/network_ data.json 2015-10- 15/vendor_ data.json 2016-06- 30/meta_ data.json 2016-06- 30/network_ data.json 2016-06- 30/vendor_ data.json 2016-10- 06/meta_ data.json 2016-10- 06/network_ data.json 2016-10- 06/vendor_ data.json 2016-10- 06/vendor_ data2.json 2017-02- 22/meta_ data.json 2017-02- 22/network_ data.json 2017-02- 22/vendor_ data.json 2017-02- 22/vendor_ data2.json latest/ meta_data. json latest/ network_ data.json latest/ vendor_ data.json latest/ vendor_ data2.json
$ ( cd /mnt && find * -type f )
ec2/2009-
ec2/latest/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/
openstack/