Hi Team, I am looking at integrating openstack neutron with oVirt. Reading the docs so far, and through my setup experiments, I can see that oVirt and neutron do seem to understand each other. But I need some helpful pointers to help me understand a few items during configuration. 1) During External Provider registration, a) although openstack keystone is currently supporting v3 api endpoints, only configuring v2 works. I see an exception otherwise.I have a feeling only v2 auth is supported with oVirt. b) Interface mappings. This I believe is a way for logical networks to switch/route traffic back to physical networks. This is of the form label:interface. Where label is placed on each Hosts network setting to point to the right physical interface. I did map label "red" when I setup Host networks to a physical Nic. And used "red:br-red, green:br-green" here, wherein my intention is to create a bridge br-red on each Host for this logical network and switch/route packets over the "red" label mapped physical nic on each host. And every vm attached to "red" logical network shall have a vnic placed on "br-red" Is my understanding correct? 2) Now I finally create a logical network using external provider "openstack neutron". Herein "Physical Network" parameter that I totally do not understand. If the registration were to have many interface mappings, is this a way of pinning to the right interface? I cannot choose, red, red:br-red... I can only leave it empty, So what is the IP address of the physical address argument part of logical network creation? "Optionally select the Create on external provider check box. Select the External Provider from the drop-down list and provide the IP address of the Physical Network". What this field means? I would appreciate some clarity and helpful pointers here. Best regards -- DISCLAIMER The information in this e-mail is confidential and may be subject to legal privilege. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you have received this communication in error, please address with the subject heading "Received in error," send to it(a)msystechnologies.com, then delete the e-mail and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. The views, opinions, conclusions and other information expressed in this electronic mail and any attachments are not given or endorsed by the company unless otherwise indicated by an authorized representative independent of this message. MSys cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses, though all reasonable precautions have been taken to ensure no viruses are present in this e-mail. As our company cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments we recommend that you subject these to your virus checking procedures prior to use _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users