If you create a loadbalancer pool and associate a vip to it then Contrail config node launches a service instance to manage the scheduling of network namespaces. It creates to VMs (active-standby) and schedules it on two compute nodes. Once the configuration reaches the respective compute node network namespaces are created for the VM objects. There is no direct mechanism to create the network namespaces.
Netns is automatically created and launched on compute nodes when pool is associated to the VIP. Haproxy is launched in the netns. There is no direct way to create/manager the netns. The script should not be used directly - it is used by the agent only after it receives the relevant loadbalancer config (service instance, pool, vip). Rudra ________________________________ From: Wojciech Reszelewski <[email protected]> Sent: Thursday, August 13, 2015 3:17 PM To: Rudra Rugge Cc: [email protected] Subject: Re: [opencontrail-dev] ServiceInstance reference in VirtualMachine (netns, LBaaS, vrouter scheduler) I'm running LBaaS using neutron commands, but apart from that another netns is created and registered in contrail using: https://github.com/pedro-r-marques/opencontrail-netns. Is something like this allowed (running separate netns on compute node)? Wojciech 2015-08-13 18:51 GMT+02:00 Rudra Rugge <[email protected]<mailto:[email protected]>>: Are you creating LBAAS using neutron commands? This in turn creates the service instance and manages the associated VMs (active and standby VMs). Rudra ________________________________ From: Dev <[email protected]<mailto:[email protected]>> on behalf of Wojciech Reszelewski <[email protected]<mailto:[email protected]>> Sent: Thursday, August 13, 2015 1:08 AM To: [email protected]<mailto:[email protected]> Subject: [opencontrail-dev] ServiceInstance reference in VirtualMachine (netns, LBaaS, vrouter scheduler) Hi! I have some problems with LBaaS and vrouter scheduler. On compute node I run some netnses using those scripts: https://github.com/pedro-r-marques/opencontrail-netns (with fixes from pull request). VirtualMachine created with those scripts have a project and a vrouter assigned but doesn't have ServiceInstance references. With those netenses up I tried to run LoadBalancer instance and scheduler failed to choose vrouters due to luck of ServiceInstance references. The code which causes problem is here: https://github.com/Juniper/contrail-controller/blob/d87a00b3930140d5765c5ea665cd8eb9a0325af3/src/config/svc-monitor/svc_monitor/scheduler/vrouter_scheduler.py#L99-L100 What is the idea behind ServiceInstance? Should it be assigned to every VirtualMachine? What should be fixed - scheduler or script? Or maybe running separate netnses on compute node is not allowed? Thanks, Wojciech Reszelewski
_______________________________________________ Dev mailing list [email protected] http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
