<div dir="ltr"><div>Hi Lakshmi,</div><div><br></div><div>Yes, only the v2 keystone api is supported at the moment.</div><div><br></div><div>The "Physical network" and "Interface mappings" are related.</div><div>"Physical network" defines the physical (external) network,</div><div>while "Interface mappings" maps this network to a specific interface</div><div>on the host.</div><div><br></div><div>"Physical network" is mapped to the "provider:physical_network"</div><div>parameter in a neutron network.</div><div>"Interface mappings" is mapped to the "physical_interface_mappings"</div><div>parameter in the neutron agent on the host. </div><div>Please look at the following link for a better explanation of how to connect</div><div>neutron to an interface:</div><div><a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_openstack_platform/7/html/networking_guide/sec-connect-instance">https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_openstack_platform/7/html/networking_guide/sec-connect-instance</a><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 27, 2017 at 3:02 PM, Lakshmi Narasimhan Sundararajan <span dir="ltr"><<a href="mailto:lakshmi.n@msystechnologies.com" target="_blank">lakshmi.n@msystechnologies.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Team,<br>
I am looking at integrating openstack neutron with oVirt.<br>
Reading the docs so far, and through my setup experiments, I can see that<br>
oVirt and neutron do seem to understand each other.<br>
<br>
But I need some helpful pointers to help me understand a few items<br>
during configuration.<br>
<br>
1) During External Provider registration,<br>
<br>
a) although openstack keystone is currently supporting v3 api<br>
endpoints, only configuring v2 works. I see an exception otherwise.I<br>
have a feeling only v2 auth is supported with oVirt.<br>
<br>
b) Interface mappings.<br>
This I believe is a way for logical networks to switch/route traffic<br>
back to physical networks. This is of the form label:interface. Where<br>
label is placed on each Hosts network setting to point to the right<br>
physical interface.<br>
<br>
I did map label "red" when I setup Host networks to a physical Nic.<br>
And used "red:br-red, green:br-green" here, wherein my intention is to<br>
create a bridge br-red on each Host for this logical network and<br>
switch/route packets over the "red" label mapped physical nic on each<br>
host. And every vm attached to "red" logical network shall have a vnic<br>
placed on "br-red" Is my understanding correct?<br>
<br>
2) Now I finally create a logical network using external provider<br>
"openstack neutron". Herein "Physical Network" parameter that I<br>
totally do not understand.<br>
If the registration were to have many interface mappings, is this a<br>
way of pinning to the right interface?<br>
<br>
I cannot choose, red, red:br-red... I can only leave it empty,<br>
<br>
So what is the IP address of the physical address argument part of<br>
logical network creation?<br>
<br>
"Optionally select the Create on external provider check box. Select<br>
the External Provider from the drop-down list and provide the IP<br>
address of the Physical Network". What this field means?<br>
<br>
I would appreciate some clarity and helpful pointers here.<br>
<br>
Best regards<br>
<br>
--<br>
<br>
<br>
DISCLAIMER<br>
<br>
The information in this e-mail is confidential and may be subject to legal<br>
privilege. It is intended solely for the addressee. Access to this e-mail<br>
by anyone else is unauthorized. If you have received this communication in<br>
error, please address with the subject heading "Received in error," send to<br>
<a href="mailto:it@msystechnologies.com">it@msystechnologies.com</a>, then delete the e-mail and destroy any copies of<br>
it. If you are not the intended recipient, any disclosure, copying,<br>
distribution or any action taken or omitted to be taken in reliance on it,<br>
is prohibited and may be unlawful. The views, opinions, conclusions and<br>
other information expressed in this electronic mail and any attachments are<br>
not given or endorsed by the company unless otherwise indicated by an<br>
authorized representative independent of this message.<br>
MSys cannot guarantee that e-mail communications are secure or error-free,<br>
as information could be intercepted, corrupted, amended, lost, destroyed,<br>
arrive late or incomplete, or contain viruses, though all reasonable<br>
precautions have been taken to ensure no viruses are present in this e-mail.<br>
As our company cannot accept responsibility for any loss or damage arising<br>
from the use of this e-mail or attachments we recommend that you subject<br>
these to your virus checking procedures prior to use<br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
</blockquote></div><br></div>