<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/openstack/nova.git/doc/api_schemas/network_data.json, branch master</title>
<subtitle>opendev.org: openstack/nova.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/'/>
<entry>
<title>Add a proper schema version to network_data.json</title>
<updated>2022-07-14T15:59:21+00:00</updated>
<author>
<name>Dmitry Tantsur</name>
<email>dtantsur@protonmail.com</email>
</author>
<published>2022-07-14T15:59:21+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=4fdc0807b44e5a9819287fa60f5b6feffa025653'/>
<id>4fdc0807b44e5a9819287fa60f5b6feffa025653</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix bond_mode enum 802.1ad -&gt; 802.3ad</title>
<updated>2021-04-29T15:42:59+00:00</updated>
<author>
<name>Balazs Gibizer</name>
<email>balazs.gibizer@est.tech</email>
</author>
<published>2021-04-29T15:42:59+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=0b05b838a47f4c05ecf8443ec48a6d6b2670f579'/>
<id>0b05b838a47f4c05ecf8443ec48a6d6b2670f579</id>
<content type='text'>
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
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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
</pre>
</div>
</content>
</entry>
<entry>
<title>Add JSON schema and test for network_data.json</title>
<updated>2020-02-17T14:35:24+00:00</updated>
<author>
<name>Ilya Etingof</name>
<email>etingof@gmail.com</email>
</author>
<published>2020-01-14T17:19:40+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/openstack/nova.git/commit/?id=69ee625a663b7877e67c938ed0d6dbca9c8fa5e7'/>
<id>69ee625a663b7877e67c938ed0d6dbca9c8fa5e7</id>
<content type='text'>
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 &lt;balazs.gibizer@est.tech&gt;
Change-Id: Ie5a5a1fc81c7c2d3f61b72d19de464cfc9dab5ec
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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 &lt;balazs.gibizer@est.tech&gt;
Change-Id: Ie5a5a1fc81c7c2d3f61b72d19de464cfc9dab5ec
</pre>
</div>
</content>
</entry>
</feed>
