Thanks! Just want to clarify one thing... Even thought neither my TOR agents or TSN vrouter agents are running on the Control nodes, I still configure QFX to connect to the VIP on Control nodes?
-Dan On Tue, Aug 25, 2015 at 12:05 AM, Vedamurthy Ananth Joshi < [email protected]> wrote: > Dan, > Yes, redundant tor-agents can be provisioned as part of fab setup_all > itself. > If you have enabled HA during provisioning, keepalived would already be > running on the controller nodes. This would be the VIP that the ToRs needs > to connect to. > > tor_tsn_ip is the real TSN IP , not the VIP > tor_agent_id is local to the node > > Also, env.ca_cert_file should be populated in testbed.py > > The Contrail UI window you are referring to, only lets you bind/unbind the > ToR from the TA/TSNs. Initial configuration cannot be done here. > > Vedu > > From: Dan Houtz <[email protected]> > Date: Tuesday, August 25, 2015 at 2:21 AM > To: OpenContrail Users List - 2 <[email protected]> > Subject: [Users] Redundant TOR Agent Config > > Hi All, > > Now that we have an HA cluster setup we would like to get a redundant TOR > agent configuration going. We have two compute nodes dedicated to host TSN > role and TOR agents. I've done plenty of TOR agent deployments to a single > node using fab scripts but this is my first time doing a redundant setup > and the documentation is pretty light. > > Can redundant TOR agents be provisioned using fab scripts or is there > manual config that must be done to build VRRP/Keepalive config on nodes? If > manual, does anyone have quick sample config for that? > > Aside from that it looks like I'd just do something like this: > > 'tsn': [host4, host5], # Optional, Only to enable TSN. Only compute can > support TSN > 'toragent': [host4, host5], #Optional, Only to enable Tor Agent. Only > compute can > > env.tor_agent = { > > host4:[{ > 'tor_ip':'192.168.11.65', > 'tor_agent_id':'1', > 'tor_agent_name':'tor_agent-tor1-et176-zone1-ord6', > 'tor_type':'ovs', > 'tor_ovs_port':'10001', > 'tor_ovs_protocol':'pssl', > 'tor_tsn_ip':'10.10.10.7', > 'tor_tsn_name':'contrail-tsn1.zone1.ord6', > 'tor_name':'tor1.et176.zone1.ord6', > 'tor_tunnel_ip':'192.168.11.65', > 'tor_vendor_name':'Juniper', > 'tor_product_name':'QFX5100', > 'tor_agent_http_server_port': '9011', > }, > { > 'tor_ip':'192.168.11.66', > 'tor_agent_id':'2', > 'tor_agent_name':'tor_agent-tor2-et176-zone1-ord6', > 'tor_type':'ovs', > 'tor_ovs_port':'10002', > 'tor_ovs_protocol':'pssl', > 'tor_tsn_ip':'10.10.10.7', > 'tor_tsn_name':'contrail-tsn1.zone1.ord6', > 'tor_name':'tor2.et176.zone1.ord6', > 'tor_tunnel_ip':'192.168.11.66', > 'tor_vendor_name':'Juniper', > 'tor_product_name':'QFX5100', > 'tor_agent_http_server_port': '9012', > }], > > host5:[{ > 'tor_ip':'192.168.11.65', > 'tor_agent_id':'1', > 'tor_agent_name':'tor_agent-tor1-et176-zone1-ord6', > 'tor_type':'ovs', > 'tor_ovs_port':'10001', > 'tor_ovs_protocol':'pssl', > 'tor_tsn_ip':'10.10.10.7', > 'tor_tsn_name':'contrail-tsn2.zone1.ord6', > 'tor_name':'tor1.et176.zone1.ord6', > 'tor_tunnel_ip':'192.168.11.65', > 'tor_vendor_name':'Juniper', > 'tor_product_name':'QFX5100', > 'tor_agent_http_server_port': '9011', > }, > { > 'tor_ip':'192.168.11.66', > 'tor_agent_id':'2', > 'tor_agent_name':'tor_agent-tor2-et176-zone1-ord6', > 'tor_type':'ovs', > 'tor_ovs_port':'10002', > 'tor_ovs_protocol':'pssl', > 'tor_tsn_ip':'10.10.10.7', > 'tor_tsn_name':'contrail-tsn2.zone1.ord6', > 'tor_name':'tor2.et176.zone1.ord6', > 'tor_tunnel_ip':'192.168.11.66', > 'tor_vendor_name':'Juniper', > 'tor_product_name':'QFX5100', > 'tor_agent_http_server_port': '9012', > }] > > } > > > A couple question in the config above: > 1. tor_tsn_ip would be VRRP VIP address correct? > 2. Is tor_agent_id unique globally or per host? > > I also see that the Contraul UI let's you configure two TOR Agents and two > TSN nodes for a physical device. Would this eliminate the need to front > TOR/TSN with VRRP? > > Am I missing or misunderstanding anything? > > Thanks! > Dan >
_______________________________________________ Users mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/users_lists.opencontrail.org
