Re: [onap-discuss] [OOM] static routes from SDNC to vGMUX

2018-02-16 Thread FREEMAN, BRIAN D
ct: Re: [onap-discuss] [OOM] static routes from SDNC to vGMUX Sorry I misread your mail. To do this, either you need to enter your docker container with privileged access: - docker exec -it -u 0 bash Either you configure the host running the SDNC container with the proper route. because K8

Re: [onap-discuss] [OOM] static routes from SDNC to vGMUX

2018-02-15 Thread Alexis de Talhouët
For us, when we need ODL to reach other machine, we add the route in the host having the container, not in the container itself. > On Feb 15, 2018, at 10:42 AM, Alexis de Talhouët > wrote: > > Sorry I misread your mail. To do this, either you need to enter your docker

Re: [onap-discuss] [OOM] static routes from SDNC to vGMUX

2018-02-15 Thread Alexis de Talhouët
Sorry I misread your mail. To do this, either you need to enter your docker container with privileged access: - docker exec -it -u 0 bash Either you configure the host running the SDNC container with the proper route. because K8S rely on the host routing table. Alexis > On Feb 9, 2018, at

Re: [onap-discuss] [OOM] static routes from SDNC to vGMUX

2018-02-15 Thread Alexis de Talhouët
Brian SDNC controller is using a script to boostrap, as shown here: https://github.com/onap/oom/blob/amsterdam/kubernetes/sdnc/templates/sdnc-deployment.yaml#L45 What I suggest is to customize this

Re: [onap-discuss] [OOM] static routes from SDNC to vGMUX

2018-02-09 Thread SULLIVAN, BRYAN L (BRYAN L)
scuss-boun...@lists.onap.org] On Behalf Of FREEMAN, BRIAN D Sent: Friday, February 09, 2018 2:36 PM To: onap-discuss@lists.onap.org Subject: [onap-discuss] [OOM] static routes from SDNC to vGMUX ***Security Advisory: This Message Originated Outside of AT *** Reference http://cso.att.com/EmailSecurity/IDSP.htm

[onap-discuss] [OOM] static routes from SDNC to vGMUX

2018-02-09 Thread FREEMAN, BRIAN D
For the vCPE Use Case we add a static route from the SDNC controller to the vBNG so that we can to the vBRG to create the tunnels to the vGMUX. The command we use on regular docker seems to fail on the K8 based image. ip route add 10.3.0.0/24 via 10.0.101.10 dev eth0 RTNETLINK answers: