openstack/bifrost
Code Issues Proposed changes

Config drive spec uses network_data.json

Browse Source 
The filename was incorrectly implemented as network_info.json instead
of network_data.json. Support for reading the correct file already
exists in glean. As such, we need to write both files for user
compatability in the short term, and remove the second file at a
later point in time.

A release note has been added detailing this as well.

Co-Authored-By: Julia Kreger <juliaashleykreger@gmail.com>
Change-Id: I4150f86fbc141dcd6fd12094acab1ca43d76910c
This commit is contained in:
Clint Byrum
2016-05-12 20:47:55 -07:00
committed by Julia Kreger
parent b4b0ff51ba
commit 33d79b09a9
7 changed files with 39 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.rst
View File

@@ -448,7 +448,7 @@ Deployment and configuration of operating systems
By default, Bifrost deploys a configuration drive which includes the user SSH
public key, hostname, and the network configuration in the form of
network_info.json that can be read/parsed by the
network_data.json that can be read/parsed by the
`glean <https://github.com/openstack-infra/glean>`_ utility. This allows for
the deployment of Ubuntu, CentOS, or Fedora "tenants" on baremetal. This file
format is not yet supported by Cloud-Init, however it is on track for