ovs-vsctl is a command-line interface to a database. You can automate it at the level of an individual operation using a script, or by connecting to the database from a language that has an OVSDB binding, such as C or Python. You can automate deployments at a higher level by using a controller that supports OpenFlow and OVSDB.
On Wed, May 20, 2020 at 05:02:12PM +0000, Heim, Dennis wrote: > So say, I want to create an internal interface with this command... > # ovs-vsctl add-port data vlan1 tag=1 -- set interface vlan1 type=internal > > What are some ways you would go about doing that in a programmatic > perspective? My goal is to abstract some of the OvS configuration away from > my users. > > -----Original Message----- > From: Ben Pfaff <b...@ovn.org> > Sent: Wednesday, May 20, 2020 12:33 PM > To: Heim, Dennis <dennis.h...@wwt.com> > Cc: ovs-discuss <ovs-discuss@openvswitch.org> > Subject: Re: [ovs-discuss] Automation > > On Wed, May 20, 2020 at 01:25:17AM +0000, Heim, Dennis wrote: > > I am running OvS ontop of Centos. What automation/provisioning > > mechanisms are available with OvS? I need to configure VXLAN, VLANs, > > etc. > > OVS was invented for automation. You can use OVSDB and OpenFlow to configure > it. _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
