 | 1 | initial version |
With some hacking around, I was able to answer my own question.
Presently the networkconfig piece requires the following: - a "networkconfig" element in the JSON document - a "contentpath" key as a child of the "networkconfig" element that has a string to a file containing the debian formatted network configuration file - the aforementioned configuration file located at /openstack/content/<configuration file="" name="">
My example JSON: { "uuid": "fake-UUID", "hostname": "hostname", "networkconfig":{ "contentpath": "/content/0000/network_config" } }
Contents of the network_config file: iface eth0 inet static address 10.0.0.2 netmask 255.255.255.0 broadcast 10.0.0.255 gateway 10.0.0.1 dns-nameservers 8.8.8.8
Things of note: - the "0000" in the contentpath is ignored due to the split function in the code. I have submitted a pull request in github with a change that will correct this issue. - for the time being, I recommend placing the "networkconfig" file in the full path /openstack/content/0000/networkconfig and /openstack/content/networkconfig of your filesystem's data structure.
Mark
© 2014-2023 Cloudbase Solutions Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
