Re: [onap-discuss] Issue in vFW instantiation E2E - OOM with OpenStack

2017-12-18 Thread Sonsino, Ofir
...@infosys.com] Sent: Monday, December 18, 2017 4:21 PM To: Sonsino, Ofir ; PLATANIA, MARCO ; onap-discuss@lists.onap.org Cc: Sambasiva Rao Kokkirala ; Kiruthiga R Subject: RE: [onap-discuss] Issue in vFW instantiation E2E - OOM with OpenStack Hi We downloaded the vid docker (1.1.1) as suggested in

Re: [onap-discuss] Issue in vFW instantiation E2E - OOM with OpenStack

2017-12-18 Thread Pavithra R13
: PLATANIA, MARCO ; Pavithra R13 ; onap-discuss@lists.onap.org Subject: RE: [onap-discuss] Issue in vFW instantiation E2E - OOM with OpenStack Hi Pavithra, Regarding deleting a VF module, we had that issue fixed: https://jira.onap.org/browse/VID-95<https://imsva91-ctp.trendmicro.com:443/

Re: [onap-discuss] Issue in vFW instantiation E2E - OOM with OpenStack

2017-12-17 Thread Sonsino, Ofir
, December 14, 2017 3:20 PM To: Pavithra R13 ; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] Issue in vFW instantiation E2E - OOM with OpenStack ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. H

Re: [onap-discuss] Issue in vFW instantiation E2E - OOM with OpenStack

2017-12-14 Thread PLATANIA, MARCO (MARCO)
Hello Pavithra, Make sure you are populating oom/kubernetes/config/onap-parameters.yaml correctly. Those parameters should reflect your OpenStack environment and are used by SO during VNF instantiation. “Maximun number of poll attempts exceeded” indicates a timeout expiration. SO is trying to