{"push_id":1231491043,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"311df0c3828fe7571079fad9763bca9e2414b51a","before":"f17add2e8e3c40f79cf211b0cb82a359104ad675","commits":[{"sha":"311df0c3828fe7571079fad9763bca9e2414b51a","author":{"name":"Dan Sneddon","email":"f57625224dacba4cffee66080adfbead074f52fe@redhat.com"},"message":"Add adapter teaming support using teamd for ifcfg-systems\n\nThis change adds support for Linux adapter teams using teamd to\nmanage the bonds instead of the kernel bonding module. Adapter\nteams using teamd can act like bonds, but also support additional\nfeatures and possibly more robust fault tolerance.\n\nThis implementation is fairly straightforward, in order to maintain\nbackward compatibility with templates made for Linux bonds. The only\ndifference in the syntax between the two is type: team instead of\ntype: linux_bond, and the bonding_options format is different.\n\nThe configuration files for teams should contain the team options\nas a JSON string. The options that can be used are documented in\nthe teamd.conf(5) man page.\n\nIf an interface is marked as primary, the priority will be changed\nfrom default 0 to 100, making this interface the preferred one. In\naddition, the MAC address of the Team and all member interfaces will\nbe set to that of the primary interface. At this time, there is no\nway to set the priority of link members individually, only the\ninterface marked primary will have a non-default priority.\n\nThis change has been tested on bare metal and worked for a team\nwith two bonded interfaces using LACP. The team was part of an\nOVS bridge, and there was a VLAN interface on the team. Everything\nworked as expected. Unit tests are included and passing.\n\nChange-Id: If1d516ce8f9ada76375c3a52c5557d3f7348981a\nImplements: blueprint os-net-config-teaming","distinct":true,"url":"https://api.github.com/repos/openstack/os-net-config/commits/311df0c3828fe7571079fad9763bca9e2414b51a"}]}
{"actor":{"display_login":"openstack-gerrit"}}