On Wed, 30 Jan 2019 02:37:00 -0000 "Brian Wilson" <[email protected]> wrote:
> > > Would external OVN networks fit for your scenario? > > We steered away from them when we couldn't figure out how to add a > VLAN Id on them without having to turn around and attach them to an > "outside network" anyway we would essentially end up with double the > networks with them in order to allow VMs to interface with Physical > Hardware on the Same Vlan IDs > If you would be interested in using Open vSwitch, which is still in technology preview in oVirt and limited https://ovirt.org/develop/release-management/features/network/openvswitch/native-openvswitch.html#limitations , there would be a way to connect OVN networks to physical VLANs: 1. Create a new cluster with switchtype OVS and ovirt-provider-ovn as default network provider. 2. At least one host is added, in best case a new installed one, to the new cluster. 3. Create a new network in oVirt, e.g. called 'trunk_net', and attach this to the network interface on the hosts, which should transport the data. 4. Create the OVN networks with port-security disabled, provider:network_type vlan, provider:physical_network trunk_net and the desired VLAN tag as provider:segmentation_id. For me worked the following script utilizing the python module 'openstack': #!/bin/env python from __future__ import print_function import openstack cloud = openstack.connect(cloud='ovirt') provider = { 'network_type': 'vlan', 'segmentation_id': 2, 'physical_network': 'trunk_net' } print(cloud.create_network('ovn_vlan_2', port_security_enabled=False, provider=provider)) The configuration of the python module 'openstack' is documented in https://docs.openstack.org/python-openstackclient/pike/configuration/index.html e.g. a file clouds.yaml in the working directory with content similar to: clouds: ovirt: auth: auth_url: https://localhost:35357/v2.0 password: '123456' username: admin@internal verify: false should do the trick. Alternatively the configuration could be provided by the environment variables: OS_USERNAME, OS_PASSWORD, OS_AUTH_URL and OS_CACERT. In default configuration, the networks will be imported automatically into oVirt and ready to be attached to VMs. > > > > If possible, would you be able to share the relevant part of > > engine.log? > I can try to kick off the playbook again and gather the logs > > > > From my point of view, it is a good idea to label the host interface > > after creating the networks, if many networks are created rapidly. > > That could be a workable solution to an extent if we were to propop > them and then do the label assignment at the end, this specific use > case was adding to an existing label where there may be VMs using > networks on the label already > > > > Is this cluster of switchtype OVS or linux bridge? > Linux Bridge > > > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ List > Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/VPGE7SZH46TYAEKY2CP5II2LRCYYSIVZ/ _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/64I5FSBGBZSKDVUQICJ7SWP5VHEE3E2X/
