Hi, Couple questions regarding Contrail and BMS support...
We are currently in the POC stages of a build-out that would be primarily bare metal based using Contrail to configure interfaces on QFX switches acting as hardware VETPs and building the proper EVPN routing instances on MX routers. The use case is to provision on demand L2 networks between bare metal dedicated servers throughout our datacenter (tied together via L3 leaf/spine underlay) for customers. Currently we have Contrail 2.1 deployed and it is properly configuring switch ports via OVSDB and seems to be distributing known macs properly between TOR switches and MX gateways. However, we are seeing a ton of issues with ARP/unknown unicast. It some cases it seems to work but not in any reliable manner. Reading through commits on github it looks like there has been a lot of work done recently on this front which leads me to a few questions: 1. Is our setup supported at all in 2.1 or will we need 2.2? 2. If 2.2 is required, does anyone have any pointers on successfully installing from master branch along with Juno? I've been able to successfully install this combo but am seeing the following errors in nova-compute logs when spinning up a VM instance: "NovaException: Unexpected vif_type=vrouter". I imagine this is due to the changing in architecture with Neutron plugins when moving to Juno. I also tried doing a devstack install with Icehouse but ran into other issues causing openstack to not even install as shown here: http://pastebin.com/5MQU6zJF 3. Ultimately I'm curious if we're on the right track and if anyone has any pointers on getting a more recent build running. Or, should we just wait for 2.2 official release assuming it's still planned for this month? Thanks! Dan H.
_______________________________________________ Dev mailing list Dev@lists.opencontrail.org http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
