summaryrefslogtreecommitdiff
path: root/doc/api_schemas
Commit message (Collapse)AuthorAgeFilesLines
* Add a proper schema version to network_data.jsonDmitry Tantsur2022-07-141-1/+1
| | | | | | | What we have there is not a schema URI. Having a proper URI allows auto-detection of the schema version (draft-07 in this case). Change-Id: I208a05c7ba64a21ed8cde7bc1ebae2b5878109e0
* Fix bond_mode enum 802.1ad -> 802.3adBalazs Gibizer2021-04-291-2/+2
| | | | | | | | | | | | | | This seems to me a clerical error made a long time ago in the spec [1]. The 802.1ad values does not seems to be a valid bonding mode but 802.3ad does. This patch fixes the schema in the nova doc. No test are changed as nova does not generate this part of the network metadata. [1] https://specs.openstack.org/openstack/nova-specs/specs/kilo/approved/metadata-service-network-info.html#rest-api-impact Change-Id: I0055d13b055e34372a8186008ba75be68aa2edf9 Closes-Bug: #1925388
* Add JSON schema and test for network_data.jsonIlya Etingof2020-02-172-0/+610
Added JSON schema defining `network_data.json` contents and beefed up the MetadataTest functional test cases to use a real instance instead of a database shell. This way the tests see real data in the metadata service like a real network_data.json. Besides internal Nova consumption, this schema might be helpful to other tools (such as ironic or Glean) to validate human-generated `network_data.json` prior to using it. Co-Authored-By: Balazs Gibizer <balazs.gibizer@est.tech> Change-Id: Ie5a5a1fc81c7c2d3f61b72d19de464cfc9dab5ec