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

2018-02-16 Thread FREEMAN, BRIAN D 
Hmmm - its probably not preferred that all the ONAP applications can access the 
OAM interface on the vBNG

Brian


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Thursday, February 15, 2018 10:43 AM
To: FREEMAN, BRIAN D 
Cc: onap-discuss@lists.onap.org
Subject: 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 K8S rely on the host routing table.

Alexis



On Feb 9, 2018, at 5:35 PM, FREEMAN, BRIAN D 
mailto:bf1...@att.com>> wrote:


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: Operation not permitted

Other ip config data below.

Do we need to add this static route from the K8 side ?

Brian

root@sdnc-1507781456-qpp77:/# ifconfig
eth0  Link encap:Ethernet  HWaddr 02:f2:9c:4e:8e:03
  inet addr:10.42.105.196  Bcast:0.0.0.0  Mask:255.255.0.0
  inet6 addr: fe80::c461:2eff:fe28:5ab8/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1402  Metric:1
  RX packets:452850 errors:0 dropped:0 overruns:0 frame:0
  TX packets:374275 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:72235413 (72.2 MB)  TX bytes:53479210 (53.4 MB)

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:10453 errors:0 dropped:0 overruns:0 frame:0
  TX packets:10453 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:1155768 (1.1 MB)  TX bytes:1155768 (1.1 MB)




root@sdnc-1507781456-qpp77:/# ip route
default via 10.42.0.1 dev eth0
10.42.0.0/16 dev eth0  proto kernel  scope link  src 10.42.105.196
169.254.169.250 via 10.42.0.1 dev eth0
___
onap-discuss mailing list
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-discuss<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=Xys_8f1hijHDfQNgyhWuHFOuvkg1Obh3bANqv7M6Qrc&s=2RUQjjvoy2U756Qnv79lRRTNG6boV6Iw7PKK7_Ryokw&e=>

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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 
> 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 5:35 PM, FREEMAN, BRIAN D > > wrote:
>> 
>>  
>> 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: Operation not permitted
>>  
>> Other ip config data below.
>>  
>> Do we need to add this static route from the K8 side ?
>>  
>> Brian
>>  
>> root@sdnc-1507781456-qpp77:/# ifconfig
>> eth0  Link encap:Ethernet  HWaddr 02:f2:9c:4e:8e:03
>>   inet addr:10.42.105.196  Bcast:0.0.0.0  Mask:255.255.0.0
>>   inet6 addr: fe80::c461:2eff:fe28:5ab8/64 Scope:Link
>>   UP BROADCAST RUNNING MULTICAST  MTU:1402  Metric:1
>>   RX packets:452850 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:374275 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:0
>>   RX bytes:72235413 (72.2 MB)  TX bytes:53479210 (53.4 MB)
>>  
>> loLink encap:Local Loopback
>>   inet addr:127.0.0.1  Mask:255.0.0.0
>>   inet6 addr: ::1/128 Scope:Host
>>   UP LOOPBACK RUNNING  MTU:65536  Metric:1
>>   RX packets:10453 errors:0 dropped:0 overruns:0 frame:0
>>   TX packets:10453 errors:0 dropped:0 overruns:0 carrier:0
>>   collisions:0 txqueuelen:1000
>>   RX bytes:1155768 (1.1 MB)  TX bytes:1155768 (1.1 MB)
>>  
>>  
>>  
>>  
>> root@sdnc-1507781456-qpp77:/# ip route
>> default via 10.42.0.1 dev eth0
>> 10.42.0.0/16 dev eth0  proto kernel  scope link  src 10.42.105.196
>> 169.254.169.250 via 10.42.0.1 dev eth0
>> ___
>> onap-discuss mailing list
>> onap-discuss@lists.onap.org 
>> https://lists.onap.org/mailman/listinfo/onap-discuss 
>> 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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 5:35 PM, FREEMAN, BRIAN D  wrote:
> 
>  
> 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: Operation not permitted
>  
> Other ip config data below.
>  
> Do we need to add this static route from the K8 side ?
>  
> Brian
>  
> root@sdnc-1507781456-qpp77:/# ifconfig
> eth0  Link encap:Ethernet  HWaddr 02:f2:9c:4e:8e:03
>   inet addr:10.42.105.196  Bcast:0.0.0.0  Mask:255.255.0.0
>   inet6 addr: fe80::c461:2eff:fe28:5ab8/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1402  Metric:1
>   RX packets:452850 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:374275 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:72235413 (72.2 MB)  TX bytes:53479210 (53.4 MB)
>  
> loLink encap:Local Loopback
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING  MTU:65536  Metric:1
>   RX packets:10453 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:10453 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:1155768 (1.1 MB)  TX bytes:1155768 (1.1 MB)
>  
>  
>  
>  
> root@sdnc-1507781456-qpp77:/# ip route
> default via 10.42.0.1 dev eth0
> 10.42.0.0/16 dev eth0  proto kernel  scope link  src 10.42.105.196
> 169.254.169.250 via 10.42.0.1 dev eth0
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org 
> https://lists.onap.org/mailman/listinfo/onap-discuss 
> 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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 script to deploy the route if an 
environment parameter is set.
Could be something like: 

- name:vCPE_use_case_enable
value: true

If you don’t want to modify this script, then I suggest you create a new 
script, that will call the /opt/onap/sdnc/bin/startODL.sh script and add your 
route. If you do this, you will have to load your script in a config-map 
(similarly as done here: https://gerrit.onap.org/r/#/c/30603/ 
)  in the SDNC namespace, you will have 
to add this config-map as volume in the SDNC deployment, and you will have to 
change the start command to run your added script.

Alexis


> On Feb 9, 2018, at 5:35 PM, FREEMAN, BRIAN D  wrote:
> 
>  
> 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: Operation not permitted
>  
> Other ip config data below.
>  
> Do we need to add this static route from the K8 side ?
>  
> Brian
>  
> root@sdnc-1507781456-qpp77:/# ifconfig
> eth0  Link encap:Ethernet  HWaddr 02:f2:9c:4e:8e:03
>   inet addr:10.42.105.196  Bcast:0.0.0.0  Mask:255.255.0.0
>   inet6 addr: fe80::c461:2eff:fe28:5ab8/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1402  Metric:1
>   RX packets:452850 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:374275 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:72235413 (72.2 MB)  TX bytes:53479210 (53.4 MB)
>  
> loLink encap:Local Loopback
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING  MTU:65536  Metric:1
>   RX packets:10453 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:10453 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:1155768 (1.1 MB)  TX bytes:1155768 (1.1 MB)
>  
>  
>  
>  
> root@sdnc-1507781456-qpp77:/# ip route
> default via 10.42.0.1 dev eth0
> 10.42.0.0/16 dev eth0  proto kernel  scope link  src 10.42.105.196
> 169.254.169.250 via 10.42.0.1 dev eth0
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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

2018-02-09 Thread SULLIVAN, BRYAN L (BRYAN L) 
Brian,

Is the SDNC pod created using the privileged option? That might be required. 
See https://kubernetes.io/docs/concepts/workloads/pods/pod/ "Privileged mode 
for pod containers"

Thanks,
Bryan Sullivan | AT&T

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-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&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

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: Operation not permitted

Other ip config data below.

Do we need to add this static route from the K8 side ?

Brian

root@sdnc-1507781456-qpp77:/# ifconfig
eth0  Link encap:Ethernet  HWaddr 02:f2:9c:4e:8e:03
  inet addr:10.42.105.196  Bcast:0.0.0.0  Mask:255.255.0.0
  inet6 addr: fe80::c461:2eff:fe28:5ab8/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1402  Metric:1
  RX packets:452850 errors:0 dropped:0 overruns:0 frame:0
  TX packets:374275 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:72235413 (72.2 MB)  TX bytes:53479210 (53.4 MB)

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:10453 errors:0 dropped:0 overruns:0 frame:0
  TX packets:10453 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:1155768 (1.1 MB)  TX bytes:1155768 (1.1 MB)




root@sdnc-1507781456-qpp77:/# ip route
default via 10.42.0.1 dev eth0
10.42.0.0/16 dev eth0  proto kernel  scope link  src 10.42.105.196
169.254.169.250 via 10.42.0.1 dev eth0
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss