@@ -42,8 +42,8 @@
<li>
One or more (usually many) <dfn>hypervisors</dfn>. Hypervisors must run
Open vSwitch and implement the interface described in
- <code>IntegrationGuide.rst</code> in the OVS source tree. Any hypervisor
- platform supported by Open vSwitch is acceptable.
+ <code>Documentation/topics/integration.rst</code> in the OVN source tree.
+ Any hypervisor platform supported by Open vSwitch is acceptable.
</li>
<li>
@@ -294,10 +294,10 @@
<li>
On a hypervisor, any VIFs that are to be attached to logical networks.
The hypervisor itself, or the integration between Open vSwitch and the
- hypervisor (described in <code>IntegrationGuide.rst</code>) takes care of
- this. (This is not part of OVN or new to OVN; this is pre-existing
- integration work that has already been done on hypervisors that support
- OVS.)
+ hypervisor (described in
+ <code>Documentation/topics/integration.rst</code>) takes care of this.
+ (This is not part of OVN or new to OVN; this is pre-existing integration
+ work that has already been done on hypervisors that support OVS.)
</li>
<li>
@@ -489,8 +489,9 @@
<li>
Eventually, a user powers on the VM that owns the VIF. On the hypervisor
where the VM is powered on, the integration between the hypervisor and
- Open vSwitch (described in <code>IntegrationGuide.rst</code>) adds the VIF
- to the OVN integration bridge and stores <var>vif-id</var> in
+ Open vSwitch (described in
+ <code>Documentation/topics/integration.rst</code>) adds the VIF to the OVN
+ integration bridge and stores <var>vif-id</var> in
<code>external_ids</code>:<code>iface-id</code> to indicate that the
interface is an instantiation of the new VIF. (None of this code is new
in OVN; this is pre-existing integration work that has already been done
The name is changed, and also the document is hosted in OVN tree that is separate from OVS tree. Signed-off-by: Ihar Hrachyshka <ihrachys@redhat.com> --- ovn-architecture.7.xml | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-)