Nagendra, could you help Matt. Looks like we need to disable bond interface renaming.
Ashish > On Aug 17, 2015, at 7:19 PM, [email protected] wrote: > > Hi List, > > I'm having some issues getting 802.1ad bonded interfaces working in my > compute nodes, and was wondering if anyone has had similar issues and can > assist. > > I have a working 2.2 installation using Openstack Juno. I'm trying to add > bonded interfaces for the vrouter compute nodes. I start off with a normal > bond0 interface that is functional, then I run "fab setup_vrouter". It > cleanly exits, and I manually reboot. The network does not come, almost as > though the bond section of my testbed.py is being ignored. It renames the > ifcfg-bond0 file, and creates the ifcfg-vhost0 file. > > testbed.py portions > > bond = { > kpdevosch11: { 'name': 'bond0', 'member': ['enp16s0f0','eno1'], 'mode': > '802.3ad', 'xmit_hash_policy': 'layer3+4' }, > } > > env.ostypes = { > kpdevosch11: 'centos', > } > > env.roledefs = { > 'compute': [kpdevosch11], > } > > env.interface_rename = False > interface_rename = False > > > I'm curious, am I supposed to start off with a functional bonded interface, > or allow the setup to create the bond from a single standalone NIC? > > I've attached the log file (without passwords). > > Any assistance will be greatly appreciated. > > Cheers, > Matt > > > ---- Message sent via Adam Internet WebMail - http://www.adam.com.au/ > <log.txt>_______________________________________________ > Users mailing list > [email protected] > http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org _______________________________________________ Users mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org
