date:20171115

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

2017-11-15 Thread PLATANIA, MARCO (MARCO)

Arun, Sylvain, Michael,

I ran docker pull for SDNC WindRiver and it worked. I noticed the same issue 
with MSB though, because the docker version in Heat is wrong. It is v1.0.0, 
while it should be 1.0.0 (without v). I’m going to submit a change soon, please 
update your local Heat env.


Arun,

If you are using an old heat template, please switch to the latest one: 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=f948399f5fcbe2300f0d7b8417792aea4682425d;hb=refs/heads/master

/opt/config/nexus_docker_repo.txt in the SDNC VM is used by the vm_init script 
to point to the Nexus repository. Make sure you have port 10001 instead of 
10003 in that file.

Marco

From:  on behalf of Arun Arora 

Date: Wednesday, November 15, 2017 at 12:23 PM
To: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails


Following JIRA Ticket: 
https://jira.onap.org/browse/SDNC-102



was created for this issue and marked as Resolved and Closed. However, the 
issue still seems to be present.



In comments it was mentioned to change the port from 10003 to 10001 in 
docker-compose.yml.

But I didn't find any such port in 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml.



Can someone provide me a working hack..



Thanks,

Arun Arora




[SDNC-102] SDNC Failed Robot Health Check - 
ONAP
jira.onap.org
No reviews matched the request. Check your Options in the drop-down menu of 
this sections header.



From: onap-discuss-boun...@lists.onap.org  
on behalf of Arun Arora 
Sent: Wednesday, November 15, 2017 10:37:33 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [SDNC] sdnc_vm_init.sh fails




ERROR: {"message":"repository onap/sdnc-image not found: does not exist or no 
pull access"}



Hi All,



I am seeing this error since yesterday. I tried to re-pull SDNC dockers afresh. 
For that I deleted all dockers along with all the files/ directories downloaded 
in /opt when sdnc_install.sh runs.



I tried this many times but the I receive the same error above in each trial.



What may be the reason of this error? I doubt it is some local setup issue as I 
re-pulled other VMs as well along with SDNC but didn't see any such error.



Is this seen by someone else? Any possible solutions?



Thanks,

Arun Arora




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

Re: [onap-discuss] [HEAT Deployment] Many failures on components

2017-11-15 Thread sylvain.desbureaux

Hi Michael and thanksgiving for the very interesting email.
Where I fail is really related to ONAP deployment through Heat (bad default 
version for docker images, pull on git from a old branch for a docker 
compose...) and then that’s why you don’t see them on OOM.
By the way, I love to see CD of ONAP! Good job!

Le 15 nov. 2017 à 18:40, Michael O'Brien 
> a écrit :

Sylvain,
   Good question and thank you for syncing your deployment state with the rest 
of us.
   Some of the openecomp to onap namespace refactor is still going on – one 
went it 2 days ago to another component – it was fully OK.
   There is a small chance that runtime classloading – during spring container 
instantiation in a .forName() – the xml references to the class name were not 
updated – but these are very rare (Note: these are not caught by Jenkins jobs 
unless they deploy component or all of onap = CD)

   I’ll take a look through the commits on master.
   I expect that a lot of these are version changes – like you found - that 
have not been done in the templates yet.
   We will also start a review of the docker version numbers to see if they 
match changes in prep of branching/releasing.

   When we get an official CD deployment job going on Jenkins – these should be 
caught and become historically traceable
.  I’ll see if we have these same issues on the Kubernetes deployment of ONAP – 
in its hourly CD Jenkins job.

   As of 1 hour ago
   We fail DCAE because the Jenkins CD job still needs proper config setup – so 
unrelated – my bad!
   We fail sdc, appc and policy – where only appc failure lines up with yourself
   We pass on sdngc, portal and SO – where you fail
   I will also do a pass to verify that the deployment yamls are up to date 
with the latest versions

http://jenkins.onap.info/job/oom-cd/

16:32:09 Basic DCAE Health Check   
[ WARN ] Retrying (Retry(total=2, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 
'NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known',)': /healthcheck
16:32:10 Basic SDNGC Health Check  
| PASS |
16:32:10 
--
16:32:10 Basic A Health Check   
| PASS |
16:32:10 
--
16:32:12 Basic Policy Health Check 
| FAIL |
16:32:12 'False' should be true.
16:32:12 
--
16:32:25 Basic MSO Health Check
| PASS |
16:32:25 
--
16:32:25 Basic ASDC Health Check   
| FAIL |
16:32:25 500 != 200
16:32:25 
--
16:32:25 Basic APPC Health Check   
| FAIL |
16:32:25 404 != 200
16:32:25 
--
16:32:25 Basic Portal Health Check 
| PASS |
16:32:25 
--
16:32:25 Basic Message Router Health Check 
| PASS |
16:32:25 
--
16:32:26 Basic VID Health Check
| PASS |

   Looking at SDNGC for example – over the past 3 days, the hourly build logged 
a healthcheck failure on SDNC

-Failing until 0700 EDT yesterday, and once at 2200 last night (but 
that one looks like a performance spike – as the build took 30 min to deploy 
instead of the usual 15 min – because we are temporarily using a host with half 
the cores)

-So SDNGC has been passing since 7am EDT yesterday for us – using master

http://kibana.onap.info:5601/app/kibana#/discover?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now-7d,mode:quick,to:now))&_a=(columns:!(_source),index:AV-vxHzpUcDKD8zJ1zbn,interval:auto,query:(query_string:(query:'message:%20%20(%22SDNGC%22%20AND%20%22FAIL%22)')),sort:!('@timestamp',desc))

SO has always passed for the last 3 days
http://kibana.onap.info:5601/app/kibana#/discover?_g=(refreshInterval:('$$hashKey':'object:1605',display:'5%20seconds',pause:!f,section:1,value:5000),time:(from:now-7d,mode:quick,to:now))&_a=(columns:!(_source),index:AV-vxHzpUcDKD8zJ1zbn,interval:auto,query:(query_string:(query:'message:%20%20(%22MSO%22%20AND%20%22PASS%22)')),sort:!('@timestamp',desc))

thank you
/michael

From:

Re: [onap-discuss] [HEAT Deployment] Many failures on components

2017-11-15 Thread Michael O'Brien

Sylvain,
   Good question and thank you for syncing your deployment state with the rest 
of us.
   Some of the openecomp to onap namespace refactor is still going on – one 
went it 2 days ago to another component – it was fully OK.
   There is a small chance that runtime classloading – during spring container 
instantiation in a .forName() – the xml references to the class name were not 
updated – but these are very rare (Note: these are not caught by Jenkins jobs 
unless they deploy component or all of onap = CD)

   I’ll take a look through the commits on master.
   I expect that a lot of these are version changes – like you found - that 
have not been done in the templates yet.
   We will also start a review of the docker version numbers to see if they 
match changes in prep of branching/releasing.

   When we get an official CD deployment job going on Jenkins – these should be 
caught and become historically traceable
.  I’ll see if we have these same issues on the Kubernetes deployment of ONAP – 
in its hourly CD Jenkins job.

   As of 1 hour ago
   We fail DCAE because the Jenkins CD job still needs proper config setup – so 
unrelated – my bad!
   We fail sdc, appc and policy – where only appc failure lines up with yourself
   We pass on sdngc, portal and SO – where you fail
   I will also do a pass to verify that the deployment yamls are up to date 
with the latest versions

http://jenkins.onap.info/job/oom-cd/

16:32:09 Basic DCAE Health Check   
[ WARN ] Retrying (Retry(total=2, connect=None, read=None, redirect=None, 
status=None)) after connection broken by 
'NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or 
service not known',)': /healthcheck
16:32:10 Basic SDNGC Health Check  
| PASS |
16:32:10 
--
16:32:10 Basic A Health Check   
| PASS |
16:32:10 
--
16:32:12 Basic Policy Health Check 
| FAIL |
16:32:12 'False' should be true.
16:32:12 
--
16:32:25 Basic MSO Health Check
| PASS |
16:32:25 
--
16:32:25 Basic ASDC Health Check   
| FAIL |
16:32:25 500 != 200
16:32:25 
--
16:32:25 Basic APPC Health Check   
| FAIL |
16:32:25 404 != 200
16:32:25 
--
16:32:25 Basic Portal Health Check 
| PASS |
16:32:25 
--
16:32:25 Basic Message Router Health Check 
| PASS |
16:32:25 
--
16:32:26 Basic VID Health Check
| PASS |

   Looking at SDNGC for example – over the past 3 days, the hourly build logged 
a healthcheck failure on SDNC

-Failing until 0700 EDT yesterday, and once at 2200 last night (but 
that one looks like a performance spike – as the build took 30 min to deploy 
instead of the usual 15 min – because we are temporarily using a host with half 
the cores)

-So SDNGC has been passing since 7am EDT yesterday for us – using master

http://kibana.onap.info:5601/app/kibana#/discover?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now-7d,mode:quick,to:now))&_a=(columns:!(_source),index:AV-vxHzpUcDKD8zJ1zbn,interval:auto,query:(query_string:(query:'message:%20%20(%22SDNGC%22%20AND%20%22FAIL%22)')),sort:!('@timestamp',desc))

SO has always passed for the last 3 days
http://kibana.onap.info:5601/app/kibana#/discover?_g=(refreshInterval:('$$hashKey':'object:1605',display:'5%20seconds',pause:!f,section:1,value:5000),time:(from:now-7d,mode:quick,to:now))&_a=(columns:!(_source),index:AV-vxHzpUcDKD8zJ1zbn,interval:auto,query:(query_string:(query:'message:%20%20(%22MSO%22%20AND%20%22PASS%22)')),sort:!('@timestamp',desc))

thank you
/michael

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
sylvain.desbure...@orange.com
Sent: Wednesday, November 15, 2017 11:26
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [HEAT Deployment] Many failures on components

Hello guys,
I’ve started a Heat deployment 4h ago with fresh pull just before.


At the end of the deployment,  I’ve got 6 over 30 tests only which are green :

  *   DCAE fails (but this is because of multi

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

2017-11-15 Thread PLATANIA, MARCO (MARCO)

Geora,

Please change /opt/config/gerrit_branch.txt from release-1.1.0 to master and 
retry.

Thanks,
Marco

From: Geora Barsky 
Date: Wednesday, November 15, 2017 at 4:16 PM
To: "PLATANIA, MARCO (MARCO)" , Arun Arora 
, "onap-discuss@lists.onap.org" 
, "sylvain.desbure...@orange.com" 
, Michael O'Brien 
Subject: RE: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Hi Marco,

In addition to below , I also noticed that there is an issue with 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml .

It points to openecomp/images instead of onap

sdnc:
image: openecomp/sdnc-image:latest

During the installation it seems like this code is  pulled from release-1.1.0 
branch :

As a result we fail :

Status: Image is up to date for 
nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image:1.2-STAGING-latest
Pulling sdnc (openecomp/sdnc-image:latest)...
ERROR: {"message":"repository openecomp/sdnc-image not found: does not exist or 
no pull access"}

Thanks

Geora Barsky
Amdocs Technology
647-688-1039

[mdocs-a]

Follow us on 
Facebook,

Twitter,

LinkedIn,

YouTube,

Google+
 and the Amdocs blog 
network.

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO 
(MARCO)
Sent: Wednesday, November 15, 2017 1:27 PM
To: Arun Arora ; onap-discuss@lists.onap.org; 
sylvain.desbure...@orange.com; Michael O'Brien 
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Arun, Sylvain, Michael,

I ran docker pull for SDNC WindRiver and it worked. I noticed the same issue 
with MSB though, because the docker version in Heat is wrong. It is v1.0.0, 
while it should be 1.0.0 (without v). I’m going to submit a change soon, please 
update your local Heat env.

Arun,

If you are using an old heat template, please switch to the latest one: 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=f948399f5fcbe2300f0d7b8417792aea4682425d;hb=refs/heads/master

/opt/config/nexus_docker_repo.txt in the SDNC VM is used by the vm_init script 
to point to the Nexus repository. Make sure you have port 10001 instead of 
10003 in that file.

Marco

From: 
>
 on behalf of Arun Arora >
Date: Wednesday, November 15, 2017 at 12:23 PM
To: "onap-discuss@lists.onap.org" 
>
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Following JIRA Ticket: 
https://jira.onap.org/browse/SDNC-102

was created for this issue and marked as Resolved and Closed. However, the 
issue still seems to be present.

In comments it

Re: [onap-discuss] Clarifying the TSC selected branching model for Amsterdam

2017-11-15 Thread Kenny Paul

Hi Michael,

just a quick note to let you know I saw your tweet.  The community is 
heads-down for tomorrow’s go/no-go decision right now. I’d hazard a guess that 
you are not the only person looking for clarification on these points, and 
expect that your email weill be the jumping off pointy for that discussion once 
everyone comes up for air.
 
Best Regards, 
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

> On Nov 14, 2017, at 9:24 PM, Michael Still  wrote:
> 
> Hi,
> 
> so I've been watching the video of the 9 November TSC meeting, and find the 
> discussion of the branching model for Amsterdam quite interesting. Is this 
> documented anywhere on the wiki? I ask because I have a couple of questions:
> 
>  - my understanding of the stated plan is that Amsterdam will be a stable 
> branch off master at release time
>  - that branch will receive back ported bug fixes and security fixes from 
> master
>  - _all_ bug fixes will be back ported, not just high priority changes
>  - features added in master will _not_ be back ported to the Amsterdam stable 
> branch
> 
> I'm a bit confused about the discussion of a one month maintenance release 
> for Amsterdam. Does that imply back ports stop after that maintenance 
> release? Or is that just the timeline for the _first_ maintenance release?
> 
> What about when Beijing is released? Is it another stable branch off master? 
> When Beijing is released, will that cause maintenance back ports to the 
> Amsterdam stable branch to cease?
> 
> For reference, I am quite familiar with the OpenStack stable branch model, 
> which is quite similar in some respects. The OpenStack community has a 
> sliding window for what gets back ported, as documented at 
> https://docs.openstack.org/project-team-guide/stable-branches.html 
>  . 
> OpenStack supports two previous releases as stable branches, but the 
> consistent feedback from the operator community is that they'd like to see 
> that period extended. The reason this hasn't happened is mainly developer 
> resources (but also some technical limitations around gating).
> 
> Another interesting difference is that OpenStack has a policy of only back 
> porting to stable branches, they never write new code directly against a 
> stable branch. Does the TSC have a read on what they want to do there?
> 
> As ONAP becomes more widely adopted there will be pressure from operators to 
> provide supported releases for longer periods, so being clear on all this 
> from the outset seems wise.
> 
> Thanks,
> Michael
> ___
> 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] [SDNC] sdnc_vm_init.sh fails

2017-11-15 Thread TIMONEY, DAN

Geora,

The release-1.1.0 branch is pre-Amsterdam seed code.   You want to be using the 
master branch, which should be working fine.

The sdnc_install.sh script sets GERRIT_BRANCH (which is where it does the pull) 
to the contents of /opt/config/gerrit_branch.txt.  I’m not sure how that’s set 
(Marco would know that better than me), but it sounds like that’s set to 
release-1.1.0 instead of master.

Marco – can they just update that file and re-run sdnc-install.sh?

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From:  on behalf of "BARSKY, GEORA" 

Date: Wednesday, November 15, 2017 at 4:16 PM
To: "PLATANIA, MARCO" , Arun Arora 
, "onap-discuss@lists.onap.org" 
, "sylvain.desbure...@orange.com" 
, "OBRIEN, FRANK MICHAEL" 

Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Hi Marco,

In addition to below , I also noticed that there is an issue with 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml .

It points to openecomp/images instead of onap

sdnc:
image: openecomp/sdnc-image:latest


During the installation it seems like this code is  pulled from release-1.1.0 
branch :

As a result we fail :

Status: Image is up to date for 
nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image:1.2-STAGING-latest
Pulling sdnc (openecomp/sdnc-image:latest)...
ERROR: {"message":"repository openecomp/sdnc-image not found: does not exist or 
no pull access"}


Thanks

Geora Barsky
Amdocs Technology
647-688-1039

[mdocs-a]

Follow us on 
Facebook,
 
Twitter,
 
LinkedIn,
 
YouTube,
 
Google+
 and the Amdocs blog 
network.


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO 
(MARCO)
Sent: Wednesday, November 15, 2017 1:27 PM
To: Arun Arora ; onap-discuss@lists.onap.org; 
sylvain.desbure...@orange.com; Michael O'Brien 
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Arun, Sylvain, Michael,

I ran docker pull for SDNC WindRiver and it worked. I noticed the same issue 
with MSB though, because the docker version in Heat is wrong. It is v1.0.0, 
while it should be 1.0.0 (without v). I’m going to submit a change soon, please 
update your local Heat env.


Arun,

If you are using an old heat template, please switch to the latest one: 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=f948399f5fcbe2300f0d7b8417792aea4682425d;hb=refs/heads/master

/opt/config/nexus_docker_repo.txt in the SDNC VM is used by the vm_init script 
to point to the Nexus repository. Make sure you have port 10001 instead of 
10003 in that file.

Marco

From: 
>
 on behalf of Arun Arora >
Date: Wednesday, November 15, 2017 at 12:23 PM
To: "onap-discuss@lists.onap.org"

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

2017-11-15 Thread PLATANIA, MARCO (MARCO)

Yes, this is what I suggested in a separate email.

Marco

From: "TIMONEY, DAN" 
Date: Wednesday, November 15, 2017 at 4:32 PM
To: "BARSKY, GEORA" , "PLATANIA, MARCO (MARCO)" 
, Arun Arora , 
"onap-discuss@lists.onap.org" , 
"sylvain.desbure...@orange.com" , "OBRIEN, FRANK 
MICHAEL" 
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Geora,

The release-1.1.0 branch is pre-Amsterdam seed code.   You want to be using the 
master branch, which should be working fine.

The sdnc_install.sh script sets GERRIT_BRANCH (which is where it does the pull) 
to the contents of /opt/config/gerrit_branch.txt.  I’m not sure how that’s set 
(Marco would know that better than me), but it sounds like that’s set to 
release-1.1.0 instead of master.

Marco – can they just update that file and re-run sdnc-install.sh?

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.

From:  on behalf of "BARSKY, GEORA" 

Date: Wednesday, November 15, 2017 at 4:16 PM
To: "PLATANIA, MARCO" , Arun Arora 
, "onap-discuss@lists.onap.org" 
, "sylvain.desbure...@orange.com" 
, "OBRIEN, FRANK MICHAEL" 

Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Hi Marco,

In addition to below , I also noticed that there is an issue with 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml .

It points to openecomp/images instead of onap

sdnc:
image: openecomp/sdnc-image:latest

During the installation it seems like this code is  pulled from release-1.1.0 
branch :

As a result we fail :

Status: Image is up to date for 
nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image:1.2-STAGING-latest
Pulling sdnc (openecomp/sdnc-image:latest)...
ERROR: {"message":"repository openecomp/sdnc-image not found: does not exist or 
no pull access"}

Thanks

Geora Barsky
Amdocs Technology
647-688-1039

[docs-a]

Follow us on 
Facebook,

Twitter,

LinkedIn,

YouTube,

Google+
 and the Amdocs blog 
network.

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO 
(MARCO)
Sent: Wednesday, November 15, 2017 1:27 PM
To: Arun Arora ; onap-discuss@lists.onap.org; 
sylvain.desbure...@orange.com; Michael O'Brien 
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Arun, Sylvain, Michael,

I ran docker pull for SDNC WindRiver and it worked. I noticed the same issue 
with MSB though, because the docker version in Heat is wrong. It is v1.0.0, 
while it should be 1.0.0 (without v). I’m going to submit a change soon, please 
update your local Heat env.

Arun,

If you are using an old heat template, please switch to the latest one:

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

2017-11-15 Thread Geora Barsky

Yes, it worked fine after modifying   /opt/config/gerrit_branch.txt   to master

release-1.1.0  is getting into /opt/config/gerrit_branch.txt  from 
onap_openstack.env :

  aai_branch: master
  appc_branch: master
  so_branch: master
  mr_branch: master
  policy_branch: master
  portal_branch: release-1.3.0
  robot_branch: master
  sdc_branch: release-1.1.0
  sdnc_branch: release-1.1.0
  vid_branch: master
  clamp_branch: master
  vnfsdk_branch: master

Geora Barsky
Amdocs Technology
647-688-1039

[amdocs-a]

Follow us on Facebook, 
Twitter, 
LinkedIn, 
YouTube, 
Google+ and the Amdocs blog 
network.


From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Wednesday, November 15, 2017 4:39 PM
To: TIMONEY, DAN ; Geora Barsky ; Arun Arora 
; onap-discuss@lists.onap.org; 
sylvain.desbure...@orange.com; Michael O'Brien 
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Yes, this is what I suggested in a separate email.

Marco

From: "TIMONEY, DAN" >
Date: Wednesday, November 15, 2017 at 4:32 PM
To: "BARSKY, GEORA" >, "PLATANIA, 
MARCO (MARCO)" >, 
Arun Arora >, 
"onap-discuss@lists.onap.org" 
>, 
"sylvain.desbure...@orange.com" 
>, "OBRIEN, 
FRANK MICHAEL" >
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Geora,

The release-1.1.0 branch is pre-Amsterdam seed code.   You want to be using the 
master branch, which should be working fine.

The sdnc_install.sh script sets GERRIT_BRANCH (which is where it does the pull) 
to the contents of /opt/config/gerrit_branch.txt.  I’m not sure how that’s set 
(Marco would know that better than me), but it sounds like that’s set to 
release-1.1.0 instead of master.

Marco – can they just update that file and re-run sdnc-install.sh?

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From: 
>
 on behalf of "BARSKY, GEORA" >
Date: Wednesday, November 15, 2017 at 4:16 PM
To: "PLATANIA, MARCO" 
>, Arun Arora 
>, 
"onap-discuss@lists.onap.org" 
>, 
"sylvain.desbure...@orange.com" 
>, "OBRIEN, 
FRANK MICHAEL" >
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Hi Marco,

In addition to below , I also noticed that there is an issue with 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml .

It points to openecomp/images instead of onap

sdnc:
image: openecomp/sdnc-image:latest


During the installation it seems like this code is  pulled from release-1.1.0 
branch :

As a result we fail :

Status: Image is up to date for 
nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image:1.2-STAGING-latest
Pulling sdnc (openecomp/sdnc-image:latest)...
ERROR: {"message":"repository openecomp/sdnc-image not found: does not exist or 
no pull access"}


Thanks

Geora Barsky
Amdocs Technology
647-688-1039

[docs-a]

Follow us on 
Facebook,
 
Twitter,
 
LinkedIn,

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

2017-11-15 Thread sylvain.desbureaux

Dan, the tag release-1.1.0 is the default value in current HEAT template (as 
said in https://jira.onap.org/browse/SDNC-196). That means that as soon as the 
release is released it should point to the stable branch of SDN-C. If it’s 
1.1.0, fine (even if I would louve to have the branch merged soon with code in 
order to be able to test the full heat deployment _before_ the release).

Remember that all the people who want to try ONAP will be pointed to the Heat 
template (and helm template later on), so if it doesn’t work it will be 
shameless at the very least...

Le 15 nov. 2017 à 22:33, TIMONEY, DAN > a 
écrit :

Geora,

The release-1.1.0 branch is pre-Amsterdam seed code.   You want to be using the 
master branch, which should be working fine.

The sdnc_install.sh script sets GERRIT_BRANCH (which is where it does the pull) 
to the contents of /opt/config/gerrit_branch.txt.  I’m not sure how that’s set 
(Marco would know that better than me), but it sounds like that’s set to 
release-1.1.0 instead of master.

Marco – can they just update that file and re-run sdnc-install.sh?

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From: 
>
 on behalf of "BARSKY, GEORA" >
Date: Wednesday, November 15, 2017 at 4:16 PM
To: "PLATANIA, MARCO" 
>, Arun Arora 
>, 
"onap-discuss@lists.onap.org" 
>, 
"sylvain.desbure...@orange.com" 
>, "OBRIEN, 
FRANK MICHAEL" >
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Hi Marco,

In addition to below , I also noticed that there is an issue with 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml .

It points to openecomp/images instead of onap

sdnc:
image: openecomp/sdnc-image:latest


During the installation it seems like this code is  pulled from release-1.1.0 
branch :

As a result we fail :

Status: Image is up to date for 
nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image:1.2-STAGING-latest
Pulling sdnc (openecomp/sdnc-image:latest)...
ERROR: {"message":"repository openecomp/sdnc-image not found: does not exist or 
no pull access"}


Thanks

Geora Barsky
Amdocs Technology
647-688-1039



Follow us on 
Facebook,
 
Twitter,
 
LinkedIn,
 
YouTube,
 
Google+
 and the Amdocs blog 
network.


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO 
(MARCO)
Sent: Wednesday, November 15, 2017 1:27 PM
To: Arun Arora >; 
onap-discuss@lists.onap.org; 
sylvain.desbure...@orange.com; Michael 
O'Brien >
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Arun, Sylvain, Michael,

I ran docker pull for SDNC WindRiver and it

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

2017-11-15 Thread Geora Barsky

Hi Marco,

In addition to below , I also noticed that there is an issue with 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml .

It points to openecomp/images instead of onap

sdnc:
image: openecomp/sdnc-image:latest


During the installation it seems like this code is  pulled from release-1.1.0 
branch :

As a result we fail :

Status: Image is up to date for 
nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image:1.2-STAGING-latest
Pulling sdnc (openecomp/sdnc-image:latest)...
ERROR: {"message":"repository openecomp/sdnc-image not found: does not exist or 
no pull access"}


Thanks

Geora Barsky
Amdocs Technology
647-688-1039

[amdocs-a]

Follow us on Facebook, 
Twitter, 
LinkedIn, 
YouTube, 
Google+ and the Amdocs blog 
network.


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO 
(MARCO)
Sent: Wednesday, November 15, 2017 1:27 PM
To: Arun Arora ; onap-discuss@lists.onap.org; 
sylvain.desbure...@orange.com; Michael O'Brien 
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Arun, Sylvain, Michael,

I ran docker pull for SDNC WindRiver and it worked. I noticed the same issue 
with MSB though, because the docker version in Heat is wrong. It is v1.0.0, 
while it should be 1.0.0 (without v). I’m going to submit a change soon, please 
update your local Heat env.


Arun,

If you are using an old heat template, please switch to the latest one: 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=f948399f5fcbe2300f0d7b8417792aea4682425d;hb=refs/heads/master

/opt/config/nexus_docker_repo.txt in the SDNC VM is used by the vm_init script 
to point to the Nexus repository. Make sure you have port 10001 instead of 
10003 in that file.

Marco

From: 
>
 on behalf of Arun Arora >
Date: Wednesday, November 15, 2017 at 12:23 PM
To: "onap-discuss@lists.onap.org" 
>
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails


Following JIRA Ticket: 
https://jira.onap.org/browse/SDNC-102



was created for this issue and marked as Resolved and Closed. However, the 
issue still seems to be present.



In comments it was mentioned to change the port from 10003 to 10001 in 
docker-compose.yml.

But I didn't find any such port in 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml.



Can someone provide me a working hack..



Thanks,

Arun Arora




[SDNC-102] SDNC Failed Robot Health Check - 
ONAP
jira.onap.org
No reviews matched the request. Check your Options in the drop-down menu of 
this sections header.



From: 
onap-discuss-boun...@lists.onap.org 
>
 on behalf of Arun Arora >
Sent: Wednesday, November 15, 2017 10:37:33 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [SDNC] sdnc_vm_init.sh fails




ERROR: {"message":"repository onap/sdnc-image not found: does not exist or no 
pull access"}



Hi All,



I am seeing this error since yesterday. I tried to re-pull SDNC dockers afresh. 
For that I deleted all dockers along with all the files/ directories downloaded 
in /opt when sdnc_install.sh runs.



I tried this many times but the I receive the same error above in each trial.



What may be the reason of this error? I doubt it is some local setup issue as I 
re-pulled other VMs as well along with SDNC but didn't see any such error.



Is this seen by someone else? Any possible solutions?



Thanks,

Arun Arora




This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at

[onap-discuss] newbee question

2017-11-15 Thread Andrey Selivanov via onap-discuss

Hi!

How  ONAP official release (e.g. Amsterdam) corresponds to ECOMP software code 
base currently in production at AT (about 2 years I've heard)?
Is it 2 completely different software projects from AT point of view? Do they 
collide in future?
Sorry for stupidity).

wbr,
AS





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

Re: [onap-discuss] [vvp] - documentation

2017-11-15 Thread Binshtok, Edan

Hello Moshe,
VVP is built from multiple containers which rely on each other except from 
validation scripts.
You need to set up the all system in order to use it as platform not just a 
single docker.
VVP is based on kubernetes and use rockets.
For example, the rocket you sent a picture of is just a FE.

The best way to handle booting up a system is of corse starting from the devkit 
repo which is in charge of all the process mentioned above
Here is the repo https://gerrit.onap.org/r/gitweb?p=vvp%2Fdevkit.git;a=summary

Thank you,
Edan Binshtok.

From:  on behalf of Moshe Hoadley 

Date: Thursday, 2 November 2017 at 10:33
To: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] [vvp] - documentation

Hi
I’m trying to learn more about the vvp project but couldn’t find any meaningful 
information.
Where can I find documentation for this project?

I also tried building the code – I was able to create and run the vvp-portal 
docker but couldn’t get it to actually work.

Thanks
Moshe Hoadley
• 972-9-77-62712
[id:image001.png@01D2F989.346CD870]
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] 答复: RE: question about sdc_vm_init

2017-11-15 Thread Lando,Michael

It is a part but it is not needed for any of the use cases and currently has no 
integration with SDC.
What Marco is pointing is that it is not needed in Amsterdam as a functional 
component.





BR,

Michael Lando
Opensource TL , SDC
AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com

From: lv.bo...@zte.com.cn [mailto:lv.bo...@zte.com.cn]
Sent: Wednesday, November 15, 2017 4:04 AM
To: PLATANIA, MARCO 
Cc: FREEMAN, BRIAN D ; Lando,Michael ; 
onap-discuss@lists.onap.org
Subject: 答复: Re: [onap-discuss] 答复: RE: question about sdc_vm_init


sdc-workflow-designer url is 
http://gerrit.onap.org/r/sdc/sdc-workflow-designer



workflow designer is a component of sdc. It will be released with sdc R1.

Right now, I don't know how should I pull the repo. So, I will just put the 
sdc_workflow_designer_docker_run.sh under demo/boot temporarily. It will be 
invoked by sdc_vm_init.sh. Is that ok?



Lv Bo.


原始邮件
发件人： >;
收件人： >;吕波10185543; 
>;
抄送人： >;
日 期 ：2017年11月14日 21:53
主 题 ：Re: [onap-discuss] 答复: RE: question about sdc_vm_init
If this is not strictly required for Amsterdam, please wait till we cut the 
release on Thursday.

Marco

From: "FREEMAN, BRIAN D" >
Date: Monday, November 13, 2017 at 9:37 PM
To: "lv.bo...@zte.com.cn" 
>, "LANDO, MICHAEL" 
>, "PLATANIA, MARCO (MARCO)" 
>
Cc: "onap-discuss@lists.onap.org" 
>
Subject: RE: [onap-discuss] 答复: RE: question about sdc_vm_init

Sometimes the repo to clone is the start script that is the last line in the 
vm_init.sh script.

But for sdc it looks like it is supposed to be in the vm_install.sh but I dont 
have  fresh environment.
On an old environment the remote url for orign is shown below.

root@vm1-sdc:/opt/sdc# git remote get-url --all  origin
http://gerrit.onap.org/r/sdc.git

I;ve never seen the work flow designer so not sure of the repo to use.

Did you simply check 
gerrit.onap.org
 under project list filter for sdc

Brian



From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
lv.bo...@zte.com.cn
Sent: Monday, November 13, 2017 8:31 PM
To: LANDO, MICHAEL >; PLATANIA, 
MARCO >
Cc: onap-discuss@lists.onap.org
Subject: [onap-discuss] 答复: RE: question about sdc_vm_init


Marco and Michael,



I checked the sdc_vm_init.sh file and did not found where to set the parameters 
of what repo to clone.

Then, I thought the sdc_workflow_designer repo already existed. I just need to 
pull the new version.

But Marco said there is no sdc_workflow_designer repo under opt/ in sdc vm.

So again, how should I get the repo on sdc vm ?






原始邮件
发件人： >;
收件人：吕波10185543; >;
抄送人：赵化冰10201488; 
>;
日 期 ：2017年11月05日 20:42
主 题 ：RE: question about sdc_vm_init
As far as I think.
You should have clone of your repo as part of the init.
The init hase paremeters to define from what repo to clone.
Once cloned the run script should be part of it.





BR,

Michael Lando
Opensource TL , SDC
AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

2017-11-15 Thread TIMONEY, DAN

Sylvia,

I believe Marco submitted a fix to the Heat template for this – I see that the 
current version is using the master branch.

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From: "sylvain.desbure...@orange.com" 
Date: Wednesday, November 15, 2017 at 5:41 PM
To: "TIMONEY, DAN" 
Cc: "BARSKY, GEORA" , "PLATANIA, MARCO" 
, Arun Arora , 
"onap-discuss@lists.onap.org" , "OBRIEN, FRANK 
MICHAEL" 
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Dan, the tag release-1.1.0 is the default value in current HEAT template (as 
said in 
https://jira.onap.org/browse/SDNC-196).
 That means that as soon as the release is released it should point to the 
stable branch of SDN-C. If it’s 1.1.0, fine (even if I would louve to have the 
branch merged soon with code in order to be able to test the full heat 
deployment _before_ the release).

Remember that all the people who want to try ONAP will be pointed to the Heat 
template (and helm template later on), so if it doesn’t work it will be 
shameless at the very least...

Le 15 nov. 2017 à 22:33, TIMONEY, DAN > a 
écrit :
Geora,

The release-1.1.0 branch is pre-Amsterdam seed code.   You want to be using the 
master branch, which should be working fine.

The sdnc_install.sh script sets GERRIT_BRANCH (which is where it does the pull) 
to the contents of /opt/config/gerrit_branch.txt.  I’m not sure how that’s set 
(Marco would know that better than me), but it sounds like that’s set to 
release-1.1.0 instead of master.

Marco – can they just update that file and re-run 
sdnc-install.sh?

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From: 
>
 on behalf of "BARSKY, GEORA" >
Date: Wednesday, November 15, 2017 at 4:16 PM
To: "PLATANIA, MARCO" 
>, Arun Arora 
>, 
"onap-discuss@lists.onap.org" 
>, 
"sylvain.desbure...@orange.com" 
>, "OBRIEN, 
FRANK MICHAEL" >
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Hi Marco,

In addition to below , I also noticed that there is an issue with 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml .

It points to openecomp/images instead of onap

sdnc:
image: openecomp/sdnc-image:latest


During the installation it seems like this code is  pulled from release-1.1.0 
branch :

As a result we fail :

Status: Image is up to date for 
nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image:1.2-STAGING-latest
Pulling sdnc (openecomp/sdnc-image:latest)...
ERROR: {"message":"repository openecomp/sdnc-image not found: does not exist or 
no pull access"}


Thanks

Geora Barsky
Amdocs Technology
647-688-1039



Follow us on 
Facebook,
 
Twitter,

[onap-discuss] 答复: [onap-tsc] Official ONAP Architecture Slide

2017-11-15 Thread 杨艳

Hi,

 

Agree that Jamil's suggestion in adding a general description for standard 
alignment to the text description.

To avoid confusion mentioned by Susana, it is recommended to keep  
‘ETSI-aligned' description in VF-C in the diagram.

 

 

Best Regards,

Yan

发件人: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
代表 jamil.cha...@orange.com
发送时间: 2017年11月15日 23:47
收件人: zhang.maope...@zte.com.cn; christopher.don...@huawei.com
抄送: onap-discuss@lists.onap.org; lcayw...@linuxfoundation.org; 
onap-...@lists.onap.org
主题: Re: [onap-tsc] [onap-discuss] Official ONAP Architecture Slide

 

Hi Maopeng

I understand that it is not easy to map ETSI to ONAP architecture. But I don’t 
think by putting VFC aligned with ETSI NFV make any sense.

As we are in one project my preference is to mention that ONAP is a way to 
implement ETSI NFV functionalities. 

Regards

jamil

 

 

De : zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
Envoyé : mercredi 15 novembre 2017 08:54
À : CHAWKI Jamil IMT/OLN; christopher.don...@huawei.com
Cc : kp...@linuxfoundation.org; onap-discuss@lists.onap.org
Objet : 答复: RE: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

 

Hi Jamil

 

As the reader, It will confus me about the mapping method.  It does not 
make sense.

About the interfaces, I have explained in the another email. 

VFC mainly focus on the NSLCM and VNFLCM, which mainly is align to the ETSI 
NFV LCM related interfaces. 

VFC also provides the driver to adaptor more vendor VNFM to do the 
integration. 

 

BR

Maopeng

原始邮件

发件人： ;

收件人：张茂鹏10030173;

抄送人： ; ;

日 期 ：2017年11月14日 19:54

主 题 ：RE: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

 

Hi Maopeng

In slide 9 you have a  first mapping of ONAP architecture to ETSI NFV one.  

For APPC stream NFVO is distributed between SO and DCAE. The VNFM is also 
distributed in SO, APPC and DCAE.

Regards

Jamil

 

De : zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
Envoyé : mardi 14 novembre 2017 11:44
À : CHAWKI Jamil IMT/OLN
Cc : kp...@linuxfoundation.org; onap-discuss@lists.onap.org
Objet : 答复: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

 

Hi jamil

  

   One quick question:

   How is the ONAP architecture Functionally aligned with ETSI NFV?  Which 
components are NFVO and VNFM in the ONAP aligned  with ETSI NFV?

   Thanks

 

BR

Maopeng

原始邮件

发件人： <  jamil.cha...@orange.com>;

收件人： <  kp...@linuxfoundation.org>; < 
 onap-discuss@lists.onap.org>;  < 
 onap-...@lists.onap.org>; < 
 ajoship...@linuxfoundation.org>; < 
 lcayw...@linuxfoundation.org>;

日 期 ：2017年11月14日  17:43

主 题 ：Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

 

Hello Kenny

I have a question on the ETSI aligned of VFC module, to my knowledge the VFC 
interfaces  are not aligned with ETSI NFV.

I think we need to remove this term from VFC and to add that ONAP architecture 
is Functionally  aligned with ETSI NFV.

Regards

Jamil

 

De :   onap-tsc-boun...@lists.onap.org 
[  
mailto:onap-tsc-boun...@lists.onap.org] De la part de Kenny Paul
Envoyé : mardi 14 novembre 2017 01:04
À : onap-discuss; onap-tsc
Cc : Lisa Caywood
Objet : [onap-tsc] Official ONAP Architecture Slide

 

As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least. 

The officially approved image for the Amsterdam Architecture and be found here:

 

 
https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2

 

 

 

In preparation for the release announcement here is what we are asking in order 
of priority:

 

-If an archecture image is referecned in your official readthedocs 
documentation, please use this image 

 

-If an archecture image is referenced in your wiki pages,  please add the URL 
above to reference the the image.

 

-If an archecture image is referecned in a presentation slide deck, please 
ensure you use this image.

 

I am intentionally NOT distributing it because that is how we ended up with so 
many versions in the first place. :-)

 

Thanks!

 

 

 

Best Regards, 
-kenny

Kenny Paul,  Technical Program Manager
  kp...@linuxfoundation.org
510.766.5945

 

_
  Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc pas etre

Re: [onap-discuss] newbee question

2017-11-15 Thread GILBERT, MAZIN E (MAZIN E)

AS
Please identify which company or institute you are part of so we track 
contributors and inquirers.
AT ECOMP and LF ONAP are aligned.

Mazin





On Nov 15, 2017, at 3:22 PM, Andrey Selivanov via onap-discuss 
> wrote:

Hi!

How  ONAP official release (e.g. Amsterdam) corresponds to ECOMP software code 
base currently in production at AT (about 2 years I've heard)?
Is it 2 completely different software projects from AT point of view? Do they 
collide in future?
Sorry for stupidity).

wbr,
AS





.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=DbhlkUFNHq6CyB96LwdRKz3dc9YvFxqskS7bCwPKRT8=oa81UchgBgBIyTKMjX6gGAGke5fwJFAge3AFEhWLNc0=

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

Re: [onap-discuss] Modeling Project doc missing

2017-11-15 Thread denghui (L)

Hi Eric

Since you contributed this part document, do you want to help Aria by including 
them?

Thanks

DENG Hui

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of DeWayne Filppi
Sent: Thursday, November 16, 2017 12:52 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Modeling Project doc missing

The ARIA REST API is contributed code to the ONAP project; ARIA includes a 
Python library and CLI.  Runtime ARIA in ONAP lives in a container ( 
https://gerrit.onap.org/r/gitweb?p=so.git;a=blob;f=packages/docker/src/main/docker/docker-files/Dockerfile.aria).
  Also contributed to ONAP is a Java binding for this REST API (  
https://gerrit.onap.org/r/gitweb?p=so.git;a=tree;f=aria/aria-rest-java-client). 
 The Java binding doesn't model TOSCA itself, it just provides a Java binding 
for the REST API.  Note that the REST API provides for fetching the parsed 
model representation as JSON, but that call isn't in the Java binding (yet).   
There has been talk about moving the ARIA work out of SO and into the Common 
Controller SDK, which I think makes some sense.
Currently the container isn't pushing properly to the Docker repo, but if you 
want to look, a recent version lives on Dockerhub as cloudifyco/aria:0.1.1.

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

[onap-discuss] 答复: RE: RE: Re: [onap-tsc] Official ONAP ArchitectureSlide

2017-11-15 Thread zhang.maopeng1

Hi Jamil


   


From the VFC project coming into ONAP, VFC focus on ETSI NFV implimention, 
which is well-known in the community.


In R1 arch, VFC marked with ETSI NFV is no problem, which can make the 
reader more clear about the main-contribution project.


Because VFC as one project in ONAP, so say ONAP implement ETSI NFV, it is 
OK as well.  But the mapping pre-shared really confuses the reader.


As I know ONAP scope is more the ETSI NFV, also SDN domain and service 
domain.





BR


Maopeng



原始邮件




发件人： ;
收件人：张茂鹏10030173; ;
抄送人： ; ; 
; ; 
;
日 期 ：2017年11月15日 23:47
主 题 ：RE: RE: Re: [onap-discuss] [onap-tsc] Official ONAP ArchitectureSlide







Hi Maopeng


I understand that it is not easy to map ETSI to ONAP architecture. But I don’t 
think by putting VFC aligned with ETSI NFV make any sense.


As we are in one project my preference is to mention that ONAP is a way to 
implement ETSI NFV functionalities.


Regards


jamil


 


 


De : zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Envoyé : mercredi 15 novembre 2017 08:54
 À : CHAWKI Jamil IMT/OLN; christopher.don...@huawei.com
 Cc : kp...@linuxfoundation.org; onap-discuss@lists.onap.org
 Objet : 答复: RE: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide


 

Hi Jamil

 

As the reader, It will confus me about the mapping method.  It does not 
make sense.

About the interfaces, I have explained in the another email. 

VFC mainly focus on the NSLCM and VNFLCM, which mainly is align to the ETSI 
NFV LCM related interfaces. 

VFC also provides the driver to adaptor more vendor VNFM to do the 
integration. 

 

BR

Maopeng


原始邮件



发件人： ;



收件人：张茂鹏10030173;



抄送人： ; ;



日 期 ：2017年11月14日  19:54



主 题 ：RE: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide




 


Hi Maopeng

In slide 9 you have a  first mapping of ONAP architecture to ETSI NFV one.  

For APPC stream NFVO is distributed between SO and DCAE. The VNFM is also 
distributed in SO, APPC and DCAE.

Regards

Jamil


 


De : zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn] 
 Envoyé : mardi 14 novembre 2017 11:44
 À : CHAWKI Jamil IMT/OLN
 Cc : kp...@linuxfoundation.org; onap-discuss@lists.onap.org
 Objet : 答复: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide


 

Hi jamil

  

   One quick question:

   How is the ONAP architecture Functionally aligned with ETSI NFV?  Which 
components are NFVO and VNFM in the ONAP aligned   with ETSI NFV?

   Thanks

 

BR

Maopeng


原始邮件



发件人： ;



收件人： ; ;   
; ;  
;



日 期 ：2017年11月14日  17:43



主 题 ：Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide




 



Hello Kenny


I have a question on the ETSI aligned of VFC module, to my knowledge the VFC 
interfaces   are not aligned with ETSI NFV.


I think we need to remove this term from VFC and to add that ONAP architecture 
is Functionally   aligned with ETSI NFV.


Regards


Jamil


 



De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
De la part de Kenny Paul
 Envoyé : mardi 14 novembre 2017 01:04
 À : onap-discuss; onap-tsc
 Cc : Lisa Caywood
 Objet : [onap-tsc] Official ONAP Architecture Slide




 


As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least. 


The officially approved image for the Amsterdam Architecture and be found here:



https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2



 


 


 


In preparation for the release announcement here is what we are asking in order 
of priority:



 



-If an archecture image is referecned in your official readthedocs 
documentation, please use this image 




 


-If an archecture image is referenced in your wiki pages,  please add the URL 
above to reference the the image.




 


-If an archecture image is referecned in a presentation slide deck, please 
ensure you use this image.




 


I am intentionally NOT distributing it because that is how we ended up with so 
many versions in the first place. :-)


 


Thanks!



 


 


 


Best Regards, 
 -kenny
 
 Kenny Paul,  Technical Program Manager
 kp...@linuxfoundation.org
 510.766.5945






 




_
  Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites 
ou copies sans autorisation. Si vous

[onap-discuss] [vnfrqts] The requirement of open source database needs discussion and I suggest we remove it in R1.

2017-11-15 Thread feng.yuanxing

Hi Steven,




I saw this item, but it has not been discussed. I suggest we remove it from R1 
requirements and discuss it later. I opened a jira ticket.

R-88199 The VNF MUST utilize virtualized, scalable open source database 
software that can meet the performance/latency requirements of the  service for 
all datastores.




Thanks,

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

[onap-discuss] 答复: [vnfrqts] vnf requirement keeps align with vnf guideline

2017-11-15 Thread Wenyao Guan

Hi Neal, Steven

 

I think this issue must be corrected immediately. Please refer to the VNF
Guidelines document.

What is the bug number?

 

Regards,

Wenyao

 

发件人: Zhuning [mailto:zhun...@huawei.com] 
发送时间: 2017年11月16日 13:28
收件人: sw3...@att.com
抄送: liying...@chinamobile.com; 'Lingli Deng' ;
Wenyao Guan ; feng.yuanx...@zte.com.cn; Lishitao
; onap-discuss@lists.onap.org
主题: [onap-discuss] [vnfrqts] vnf requirement keeps align with vnf
guideline 

 

sorry for the title of the previous email was wrongly written

 

 

Hi Steven,

   I just create a bug on VNF requirement in JIRA for I just notice that
there are 2 requirement items are not in line with VNF guideline document.
Sorry for so late.

2 weeks ago, in weekly meeting, VNF guideline document was modified.
VNF is not mandatory requested to only use the NCSP’s standard set of OS
images now. R-46960 and R-23475 of VNF requirement should keep changes
synchronized

 

R-46960 The VNF MUST utilize  only the Guest OS versions that are supported
by the NCSP’s Network Cloud.
 [1]

R-23475 The VNF SHOULD utilize  only NCSP provided Guest OS images.
 [1]

 

I suggest that maybe we can copy the relevant text from guideline document
directly.

 

 

Best Regards,

Neal

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

[onap-discuss] compile:aai

2017-11-15 Thread aijianwen

Hi,team:
I want to produce the dockers of aai/data-router.
I download the code of aai/data-router project,then using the shell script:

#!/bin/bash -x

#build ajsc-aai

echo "building docker for aai-data-router"

source /etc/profile

mvn  package -Dmaven.test.skip=true docker:build -e


[INFO] Building image /onap/data-router
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 55.202 s
[INFO] Finished at: 2017-11-16T09:05:42+08:00
[INFO] Final Memory: 88M/2927M
[INFO] 
[ERROR] Failed to execute goal com.spotify:docker-maven-plugin:0.4.11:build 
(default-cli) on project data-router: Exception caught: Request error: POST 
unix://localhost:80/build?t=/onap/data-router: 500: HTTP 500 Internal Server 
Error -> [Help 1]

How to solve it?

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

[onap-discuss] [integration][uui]VoLTE use case UUI peroformance and alarm function test

2017-11-15 Thread Yang Xu (Yang, Fixed Network)

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Yang Xu (Yang, Fixed Network)":MAILTO:yang@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=shentao@ch
 inamobile.com:MAILTO:shen...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Pengyu (Pe
 rry):MAILTO:perry.p...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Wangzhenhu
 a (F):MAILTO:wangzhenh...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 ss:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:When: Wednesday\, November 15\, 2017 8:00 PM-10:
 00 PM (UTC+08:00) Beijing\, Chongqing\, Hong Kong\, Urumqi.\nWhere: https:
 //zoom.us/j/4238608129\n\nNote: The GMT offset above does not reflect dayl
 ight saving time adjustments.\n\n*~*~*~*~*~*~*~*~*~*\n\nTopic: UUI perform
 ance and alarm function test\n\n
SUMMARY;LANGUAGE=en-US:[integration][uui]VoLTE use case UUI peroformance an
 d alarm function test
DTSTART;TZID=China Standard Time:20171115T20
DTEND;TZID=China Standard Time:20171115T22
UID:04008200E00074C5B7101A82E008E07EFB4D3D5ED301000
 0100030717AEE80605E4789A0C1D9EBC447D2
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20171115T101234Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/4238608129
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-1534085151
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

2017-11-15 Thread Sabater, Susana, Vodafone Spain

Thanks Maopeng!
I was guessing that was the case when referencing IFA and not SOL specs. In any 
case, it will be good to update the links and make clear that VF-C does comply 
with NFV APIs and functionality, to avoid confusion as in this long thread.

Cheers!
/Susana

From: zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn]
Sent: Wednesday, November 15, 2017 8:32 AM
To: Sabater, Susana, Vodafone Spain 
Cc: jamil.cha...@orange.com; kp...@linuxfoundation.org; 
onap-discuss@lists.onap.org; onap-...@lists.onap.org; 
ajoship...@linuxfoundation.org; lcayw...@linuxfoundation.org
Subject: 答复: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide


Hi  Susana,



  VFC project in R1 includes NFVO and VNFM components, mainly 
focused on the NS LCM and VNFLCM.

 NSLCM  NBI and GVNFM NBI  please refer to 
https://wiki.onap.org/display/DW/VF-C+R1+Deliverables
  NSLCM API Specification 
v0.1.
  and GVNFM API Specification 
v0.1.

 As the project started, NSLCM and GVNFM mainly refer to IFA 
document and refer to the SOL Draft, because the SOL does not provide engough 
APIs and is not published at that time.

 Now SOL003 is published and SOL005 is still in the draft(almost 
stable), I compare the API of the SOL, the main flow is same and most of LCM 
interfaces be aligned.

 In the following release, VFC team will plan to align the SOL as 
needed and also consider the usecase requirements.

 In the R1, VFC has more work on the integration with other ONAP 
componenst. The document is not well formatted, we will try to do it in the 
next release.

 If interested about VFC projects, welcome to join, thanks.



BR

Maopeng
原始邮件
发件人： >;
收件人： >; 
>; 
>; 
>; 
>; 
>;
日 期 ：2017年11月14日 22:25
主 题 ：Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide


Hi,

Is it so that VF-C interfaces are not aligned with ETSI NFV ones? In the 
documentation of VF-C it appeared like aligned, but I observed  the reference 
is made to IFA007 and IFA008 and not to the published APIs, as opposed to 
referencing SOL005 for NS LCM.
In any case, it is difficult to find now the documentation of the VF-C; 
wouldn’t it be good to add relevant links to the modules, their  documentation, 
user guides, etc in the Amsterdam arch page?

Regards
/Susana

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of 
jamil.cha...@orange.com
Sent: Tuesday, November 14, 2017 10:41 AM
To: Kenny Paul >; 
onap-discuss >; 
onap-tsc >; Arpit 
Joshipura 
(ajoship...@linuxfoundation.org) 
>; Lisa 
Caywood >
Subject: Re: [onap-tsc] Official ONAP Architecture Slide

Hello Kenny
I have a question on the ETSI aligned of VFC module, to my knowledge the VFC 
interfaces are not aligned with ETSI NFV.
I think we need to remove this term from VFC and to add that ONAP architecture 
is Functionally aligned with ETSI NFV..
Regards
Jamil

De : onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] De la part de Kenny Paul
Envoyé : mardi 14 novembre 2017 01:04
À : onap-discuss; onap-tsc
Cc : Lisa Caywood
Objet : [onap-tsc] Official ONAP Architecture Slide

As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least.
The officially approved image for the Amsterdam Architecture and be found here:
https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2



In preparation for the release announcement here is what we are asking in order 
of priority:

-If an archecture image is referecned in your official readthedocs 
documentation, please use this image

-If an archecture image is referenced in your wiki pages,

[onap-discuss] 答复: [onap-tsc] Official ONAP Architecture Slide

2017-11-15 Thread Zengjianguo (OSS Design)

Hi
I’d afraid that I can’t agree on it. The goal of VFC in ONAP is to 
provide ETSI NFV align capability, so make ONAP integrated with ETSI NFV 
complaint commercial solution in a more smooth way. I think the original 
version is most suitable way to describe the difference between VFC and  APPC.

Best regards

发件人: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
代表 jamil.cha...@orange.com
发送时间: 2017年11月14日 23:30
收件人: Sabater, Susana, Vodafone Spain; Lisa Caywood
抄送: onap-discuss; onap-tsc
主题: Re: [onap-tsc] Official ONAP Architecture Slide

Hi Susana
Ok in this case we have to remove this from VFC.
Regards
jamil

De : Sabater, Susana, Vodafone Spain [mailto:susana.saba...@vodafone.com]
Envoyé : mardi 14 novembre 2017 16:26
À : Lisa Caywood; CHAWKI Jamil IMT/OLN
Cc : onap-discuss; onap-tsc
Objet : RE: [onap-tsc] Official ONAP Architecture Slide

And maybe it is wise to avoid making any statement that “ONAP is functionally 
aligned with ETSI NFV architecture”, since it will deeply confuse the audience 
trying to see the alignment.

Cheers
/Susana

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lisa Caywood
Sent: Tuesday, November 14, 2017 4:19 PM
To: CHAWKI Jamil IMT/OLN 
>
Cc: onap-discuss 
>; onap-tsc 
>
Subject: Re: [onap-tsc] Official ONAP Architecture Slide

Jamil, we can not spell out the names of all of the components on the slide; 
there isn't room. It must be legible, including from a distance (eg in a public 
presentation).

Chris can answer #2.

Thanks, Lisa

On Tue, Nov 14, 2017 at 7:14 AM, 
> wrote:
Hello Kenny
Additional comments and proposals on this figure:

1- Remove ETSI NFV alignment from VFC and to replace it by a general note  
that ‘ONAP is functionally aligned with ETSI NFV architecture’

2- We need to remove AWS, Rackspace and Azure. Why Rackspace is listed and 
not WindRiver ?

3- MultiCloud Infrastructure Adaptation Layer => it is not an adaptation 
layer today. Replace it by Multi VIM/Cloud (official project name).

4- Replace SDN-C by SDN Controller, similar to Application Controller

5- VVP, VNF Requirements, Modelling, Testing & integration are not 
mentioned in the architecture

a. Proposals:

  i.To add Requirements and 
Validation with VNF SDK.

 ii.To add Modelling with CLAMP

iii.To add Test and Integration 
with OOM

6- We need to avoid the abbreviations like AAF, OOF …

a. Proposal to replace:

  i.SDC by Service Design Creation

 ii.Clamp by Closed Loop Design

iii.DMaaP by Data Movement

iv.A by Active & Available 
Inventory

 v.Holmes by Fault Correction

vi.DCAE by Data Collection 
Analytics and Events

   vii.AAF by Application Authorization 
Framework

  viii.CC SDK Common Controller SDK

ix.OOF by Optimization Framework

Regards
jamil

De : onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org]
 De la part de Kenny Paul
Envoyé : mardi 14 novembre 2017 01:04
À : onap-discuss; onap-tsc
Cc : Lisa Caywood
Objet : [onap-tsc] Official ONAP Architecture Slide

As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least.
The officially approved image for the Amsterdam Architecture and be found here:
https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2

In preparation for the release announcement here is what we are asking in order 
of priority:

-If an archecture image is referecned in your official readthedocs 
documentation, please use this image

-If an archecture image is referenced in your wiki pages,  please add the URL 
above to reference the the image.

-If an archecture image is referecned in a presentation slide deck, please 
ensure you use this image.

I am intentionally NOT distributing it because that is how we ended up with so 
many versions in the first place. :-)

Thanks!

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

Re: [onap-discuss] [onap-tsc] 答复: Official ONAP Architecture Slide

2017-11-15 Thread yuan.yue

+1







I don't believe 9 commercial vNFs from three different vendors could 
successfully deployed by VFC in voLTE service without compliance with ETSI 
specification.  






Yuan Yue















袁越 yuanyue


资深战略规划师   Senior Strategy Planner



技术规划部/技术规划部/系统产品 Technology Planning Dept./Technology Planning Dept./System 
Product









南京市雨花区软件大道50号中兴通讯3号楼1/F,Building 3, ZTE Nanjing R Center II, No.50, Software 
Avenue,YuHua District,Nanjing,P.R.China 210012
T: +025 88013478 

M: +86 13851446442 
E: yuan@zte.com.cn 
www.zte.com.cn
















原始邮件



发件人： ;
收件人： ; ; 
;
抄送人： ; ;
日 期 ：2017年11月15日 18:02
主 题 ：[onap-tsc] 答复:  Official ONAP Architecture Slide








Hi


I’d afraid that I can’t agree on it. The goal of VFC in ONAP is to 
provide ETSI NFV align capability, so make ONAP integrated with ETSI  NFV 
complaint commercial solution in a more smooth way. I think the original 
version is most suitable way to describe the difference between VFC and  APPC.





Best regards


 



发件人: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
代表 jamil.cha...@orange.com
 发送时间: 2017年11月14日  23:30
 收件人: Sabater, Susana, Vodafone Spain; Lisa Caywood
 抄送: onap-discuss; onap-tsc
 主题: Re: [onap-tsc] Official ONAP Architecture Slide




 


Hi Susana


Ok in this case we have to remove this from VFC.


Regards


jamil


 



De : Sabater, Susana, Vodafone Spain [mailto:susana.saba...@vodafone.com] 
 Envoyé : mardi 14 novembre 2017 16:26
 À : Lisa Caywood; CHAWKI Jamil IMT/OLN
 Cc : onap-discuss; onap-tsc
 Objet : RE: [onap-tsc] Official ONAP Architecture Slide




 


And maybe it is wise to avoid making any statement that “ONAP is functionally 
aligned with ETSI NFV architecture”, since it will deeply confuse  the audience 
trying to see the alignment.


 


Cheers


/Susana


 


From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Lisa Caywood
 Sent: Tuesday, November 14, 2017 4:19 PM
 To: CHAWKI Jamil IMT/OLN 
 Cc: onap-discuss ; onap-tsc 

 Subject: Re: [onap-tsc] Official ONAP Architecture Slide


 


Jamil, we can not spell out the names of all of the components on the slide; 
there isn't room. It must be legible, including from a distance (eg in a public 
presentation).


 



Chris can answer #2. 



 



Thanks, Lisa




 


On Tue, Nov 14, 2017 at 7:14 AM,  wrote:


Hello Kenny


Additional comments and proposals on this figure:


1- Remove ETSI NFV alignment from VFC and to replace it by a general note  
that ‘ONAP is functionally aligned with ETSI NFV architecture’


2- We need to remove AWS, Rackspace and Azure. Why Rackspace is listed and 
not WindRiver ?


3- MultiCloud Infrastructure Adaptation Layer => it is not an adaptation 
layer today. Replace it by Multi VIM/Cloud (official project name).


4- Replace SDN-C by SDN Controller, similar to Application Controller


5- VVP, VNF Requirements, Modelling, Testing & integration are not 
mentioned in the architecture


a. Proposals: 


  i.To add Requirements and 
Validation with VNF SDK.


 ii.To add Modelling with CLAMP


iii.To add Test and Integration 
with OOM


 


6- We need to avoid the abbreviations like AAF, OOF …


a. Proposal to replace:


  i.SDC by Service Design Creation 


 ii.Clamp by Closed Loop Design


iii.DMaaP by Data Movement


iv.A by Active & Available 
Inventory


 v.Holmes by Fault Correction


vi.DCAE by Data Collection 
Analytics and Events 


   vii.AAF by Application Authorization 
Framework 


  viii.CC SDK Common Controller SDK 


ix.OOF by Optimization Framework  


 


Regards


jamil


 


 



De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
De la part de Kenny Paul
 Envoyé : mardi 14 novembre 2017 01:04
 À : onap-discuss; onap-tsc
 Cc : Lisa Caywood
 Objet : [onap-tsc] Official ONAP Architecture Slide




 


As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least. 


The officially approved image for the Amsterdam Architecture and be found here:

[onap-discuss] Service distribution WorkFlow across various sdc/mso/aai/sdnc/v Containers via SDC Gui by Ops user

2017-11-15 Thread Gaurav Gupta (c)

 All , Michael


While chasing the issue of Service distribution via SDC Gui and using VID to 
Deploy Service failing .

There are certain dots that are missing while trying to establish due to which 
ONAP Container that issues is coming .


For example in Distribution Flow


Following are the Docker container that plays a role in Service Onboarding 
workFlow . Can this be confirmed ? .


sdc-fe container -> msotestlab_1

sdc-fe container ->  aai_resource

sdc-fe container  ->  sdnc-ueblistener


Please note that is based on the information on the below links .

https://wiki.onap.org/pages/viewpage.action?pageId=3246170

https://wiki.onap.org/display/DW/Tutorial%3A+Verifying+and+Observing+a+deployed+Service+Instance#Tutorial:VerifyingandObservingadeployedServiceInstance-vFirewallFlow

Tutorial: Verifying and Observing a deployed Service 
...
wiki.onap.org
How many of the 10 TG streams is running is TBD? TBD: the exact nature of what 
enabling 5 of the 10 TGs is? TBD: what exactly is the correlation between the 
SEC ...


thanks in advance for helping on this  .


thanks and regards

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

Re: [onap-discuss] [E] Centralized Image Management proposal discussion

2017-11-15 Thread Kumar Skand Priya, Viswanath V via onap-discuss

Dear All,

I have a question as to whether this proposal ( Centralized Image
management ) conflicts with SDC Image management proposal, that was
proposed earlier ?

BR,
Viswa




Viswanath Kumar Skand Priya
Architect
Verizon Network Ops & Eng


On Wed, Nov 15, 2017 at 2:10 PM,  wrote:

>
> Hi Chris and all,
>
>
> As discussed in last Architecture meeting, I have update the Image manage
> powerpoint. Please see the attachment. If you have any question or
> suggestion, please don't hesitate to tell me.
>
>
> To Chris: If do the image validation check with VNF-SDK. What the sequnce
> would be like? What the output data would be after the VNF-SDK checked the
> images?
>
>
>
>
>
>
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=
> udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=9F3pNUkzjE-
> 2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ=
> 5TpzLl1CEJmxeMuHEcfkD8FyhB3E4HTFKvWpDIe7wjs=
> 642o4rh5qd0sNTjtC8lxlRurnblMRn1TRrFzXl26Ln4=
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [vvp] - documentation

2017-11-15 Thread Moshe Hoadley

Thanks for your reply.
As you suggested, I started working according to the 'devkit' summary:
- I setup a linux development environment with vagrant and ansible.
- from ../vvp/devkit I ran:
. setenv
vagrant up
watch -n5 "kubectl get po -n kube-system"
However, kubectl fails with: " The connection to the server localhost:8080 was 
refused".

Am I missing a configuration step for kubectl?
Also, should I run a maven build before 'vagrant up'?

Thanks
Moshe Hoadley
M 972-9-77-62712    


-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Binshtok, Edan
Sent: Wednesday, November 15, 2017 10:48 AM
To: Moshe Hoadley ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [vvp] - documentation

Hello Moshe,
VVP is built from multiple containers which rely on each other except from 
validation scripts.
You need to set up the all system in order to use it as platform not just a 
single docker.
VVP is based on kubernetes and use rockets.
For example, the rocket you sent a picture of is just a FE.

The best way to handle booting up a system is of corse starting from the devkit 
repo which is in charge of all the process mentioned above Here is the repo 
https://gerrit.onap.org/r/gitweb?p=vvp%2Fdevkit.git;a=summary

Thank you,
Edan Binshtok.

From:  on behalf of Moshe Hoadley 

Date: Thursday, 2 November 2017 at 10:33
To: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] [vvp] - documentation

Hi
I’m trying to learn more about the vvp project but couldn’t find any meaningful 
information.
Where can I find documentation for this project?

I also tried building the code – I was able to create and run the vvp-portal 
docker but couldn’t get it to actually work.

Thanks
Moshe Hoadley
• 972-9-77-62712
[id:image001.png@01D2F989.346CD870]
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement, you may review at 
https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

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

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

2017-11-15 Thread jamil.chawki

+1 in addition Portal should not be  part of the Design Time.
OOM need to be positioned on the right to avoid to be considered as  on the top 
of External API
Regards
Jamil

De : TALASILA, MANOOP (MANOOP) [mailto:talas...@research.att.com]
Envoyé : mercredi 15 novembre 2017 03:43
À : Kenny Paul; Lisa Caywood
Cc : onap-discuss; onap-tsc; CHAWKI Jamil IMT/OLN; Sabater, Susana, Vodafone 
Spain
Objet : Re: [onap-tsc] Official ONAP Architecture Slide

Hi Kenny,

In the Architecture slide, can we please rename “Portal Framework - UI” -> 
“ONAP Portal Platform”? as it is not just UI (I hear this misconception most of 
the time), it provides many backend application integration services along with 
a runtime dashboard. Thanks.

Manoop

From: > 
on behalf of "jamil.cha...@orange.com" 
>
Date: Tuesday, November 14, 2017 at 10:29 AM
To: "Sabater, Susana, Vodafone Spain" 
>, Lisa Caywood 
>
Cc: onap-discuss 
>, onap-tsc 
>
Subject: Re: [onap-tsc] Official ONAP Architecture Slide

Hi Susana
Ok in this case we have to remove this from VFC.
Regards
jamil

De : Sabater, Susana, Vodafone Spain [mailto:susana.saba...@vodafone.com]
Envoyé : mardi 14 novembre 2017 16:26
À : Lisa Caywood; CHAWKI Jamil IMT/OLN
Cc : onap-discuss; onap-tsc
Objet : RE: [onap-tsc] Official ONAP Architecture Slide

And maybe it is wise to avoid making any statement that “ONAP is functionally 
aligned with ETSI NFV architecture”, since it will deeply confuse the audience 
trying to see the alignment.

Cheers
/Susana

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lisa Caywood
Sent: Tuesday, November 14, 2017 4:19 PM
To: CHAWKI Jamil IMT/OLN 
>
Cc: onap-discuss 
>; onap-tsc 
>
Subject: Re: [onap-tsc] Official ONAP Architecture Slide

Jamil, we can not spell out the names of all of the components on the slide; 
there isn't room. It must be legible, including from a distance (eg in a public 
presentation).

Chris can answer #2.

Thanks, Lisa

On Tue, Nov 14, 2017 at 7:14 AM, 
> wrote:
Hello Kenny
Additional comments and proposals on this figure:

1- Remove ETSI NFV alignment from VFC and to replace it by a general note  
that ‘ONAP is functionally aligned with ETSI NFV architecture’

2- We need to remove AWS, Rackspace and Azure. Why Rackspace is listed and 
not WindRiver ?

3- MultiCloud Infrastructure Adaptation Layer => it is not an adaptation 
layer today. Replace it by Multi VIM/Cloud (official project name).

4- Replace SDN-C by SDN Controller, similar to Application Controller

5- VVP, VNF Requirements, Modelling, Testing & integration are not 
mentioned in the architecture

a. Proposals:

  i.To add Requirements and 
Validation with VNF SDK.

 ii.To add Modelling with CLAMP

iii.To add Test and Integration 
with OOM

6- We need to avoid the abbreviations like AAF, OOF …

a. Proposal to replace:

  i.SDC by Service Design Creation

 ii.Clamp by Closed Loop Design

iii.DMaaP by Data Movement

iv.A by Active & Available 
Inventory

 v.Holmes by Fault Correction

vi.DCAE by Data Collection 
Analytics and Events

   vii.AAF by Application Authorization 
Framework

  viii.CC SDK Common Controller SDK

ix.OOF by Optimization Framework

Regards
jamil

De : onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org]
 De la part de Kenny Paul
Envoyé : mardi 14 novembre 2017 01:04
À : onap-discuss; onap-tsc
Cc : Lisa Caywood
Objet : [onap-tsc] Official ONAP Architecture Slide

As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least.
The officially approved image for the Amsterdam Architecture and be found here:

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

2017-11-15 Thread jamil.chawki

+1

De : Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Envoyé : mercredi 15 novembre 2017 06:00
À : TALASILA, MANOOP (MANOOP); Kenny Paul; Lisa Caywood
Cc : Sabater, Susana, Vodafone Spain; CHAWKI Jamil IMT/OLN; onap-discuss; 
onap-tsc
Objet : RE: [onap-tsc] Official ONAP Architecture Slide

Dear Kenny,

I would like share my point of view :

As Manoop mentioned below, It would be better,  if we could bring Portal, ONAP 
CLI span across Design Time and Run-Time services similar to OOM reported now.
May be something as follows:

[cid:image001.png@01D35E30.51F0C0D0]





ONAP service (design time & Run time)
















Regards
Kanagaraj M
***
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**

***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of TALASILA, MANOOP 
(MANOOP)
Sent: Wednesday, November 15, 2017 8:27 AM
To: Kenny Paul; Lisa Caywood
Cc: Sabater, Susana, Vodafone Spain; 
jamil.cha...@orange.com; onap-discuss; onap-tsc
Subject: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

Also, the Portal platform should be represented across the architecture on the 
top of the diagram similar to OOM, as the operators/users access both 
“design-time” and “run-time” applications through Portal platform (for example 
VID, AAI, SDC and Policy apps).

Manoop

From: "TALASILA, MANOOP (MANOOP)" 
>
Date: Tuesday, November 14, 2017 at 9:42 PM
To: Kenny Paul >, 
Lisa Caywood >
Cc: onap-discuss 
>, onap-tsc 
>, 
"jamil.cha...@orange.com" 
>, "Sabater, Susana, 
Vodafone Spain" 
>
Subject: Re: [onap-tsc] Official ONAP Architecture Slide

Hi Kenny,

In the Architecture slide, can we please rename “Portal Framework - UI” -> 
“ONAP Portal Platform”? as it is not just UI (I hear this misconception most of 
the time), it provides many backend application integration services along with 
a runtime dashboard. Thanks.

Manoop

From: > 
on behalf of "jamil.cha...@orange.com" 
>
Date: Tuesday, November 14, 2017 at 10:29 AM
To: "Sabater, Susana, Vodafone Spain" 
>, Lisa Caywood 
>
Cc: onap-discuss 
>, onap-tsc 
>
Subject: Re: [onap-tsc] Official ONAP Architecture Slide

Hi Susana
Ok in this case we have to remove this from VFC.
Regards
jamil

De : Sabater, Susana, Vodafone Spain [mailto:susana.saba...@vodafone.com]
Envoyé : mardi 14 novembre 2017 16:26
À : Lisa Caywood; CHAWKI Jamil IMT/OLN
Cc : onap-discuss; onap-tsc
Objet : RE: [onap-tsc] Official ONAP Architecture Slide

And maybe it is wise to avoid making any statement that “ONAP is functionally 
aligned with ETSI NFV architecture”, since it will deeply confuse the audience 
trying to see the alignment.

Cheers
/Susana

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lisa Caywood
Sent: Tuesday, November 14, 2017 4:19 PM
To: CHAWKI Jamil IMT/OLN 
>
Cc: onap-discuss 
>; onap-tsc 
>
Subject: Re: [onap-tsc] Official ONAP

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

2017-11-15 Thread jamil.chawki

Hi Maopeng
I understand that it is not easy to map ETSI to ONAP architecture. But I don’t 
think by putting VFC aligned with ETSI NFV make any sense.
As we are in one project my preference is to mention that ONAP is a way to 
implement ETSI NFV functionalities.
Regards
jamil


De : zhang.maope...@zte.com.cn [mailto:zhang.maope...@zte.com.cn]
Envoyé : mercredi 15 novembre 2017 08:54
À : CHAWKI Jamil IMT/OLN; christopher.don...@huawei.com
Cc : kp...@linuxfoundation.org; onap-discuss@lists.onap.org
Objet : 答复: RE: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide


Hi Jamil



As the reader, It will confus me about the mapping method.  It does not 
make sense.

About the interfaces, I have explained in the another email.

VFC mainly focus on the NSLCM and VNFLCM, which mainly is align to the ETSI 
NFV LCM related interfaces.

VFC also provides the driver to adaptor more vendor VNFM to do the 
integration.



BR

Maopeng
原始邮件
发件人： >;
收件人：张茂鹏10030173;
抄送人： >; 
>;
日 期 ：2017年11月14日 19:54
主 题 ：RE: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide



Hi Maopeng

In slide 9 you have a  first mapping of ONAP architecture to ETSI NFV one.

For APPC stream NFVO is distributed between SO and DCAE. The VNFM is also 
distributed in SO, APPC and DCAE.

Regards

Jamil

De : zhang.maope...@zte.com.cn 
[mailto:zhang.maope...@zte.com.cn]
Envoyé : mardi 14 novembre 2017 11:44
À : CHAWKI Jamil IMT/OLN
Cc : kp...@linuxfoundation.org; 
onap-discuss@lists.onap.org
Objet : 答复: Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide


Hi jamil



   One quick question:

   How is the ONAP architecture Functionally aligned with ETSI NFV?  Which 
components are NFVO and VNFM in the ONAP aligned  with ETSI NFV?

   Thanks



BR

Maopeng
原始邮件
发件人： >;
收件人： >; 
>;  
>; 
>; 
>;
日 期 ：2017年11月14日  17:43
主 题 ：Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide


Hello Kenny
I have a question on the ETSI aligned of VFC module, to my knowledge the VFC 
interfaces  are not aligned with ETSI NFV.
I think we need to remove this term from VFC and to add that ONAP architecture 
is Functionally  aligned with ETSI NFV.
Regards
Jamil

De : onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] De la part de Kenny Paul
Envoyé : mardi 14 novembre 2017 01:04
À : onap-discuss; onap-tsc
Cc : Lisa Caywood
Objet : [onap-tsc] Official ONAP Architecture Slide

As was pointed out in Paris there are too many variations of the Amsterdam 
architecture which is bad to say the least.
The officially approved image for the Amsterdam Architecture and be found here:
https://wiki.onap.org/download/attachments/1015842/ONAP%20Amsterdam%20arch.png?api=v2



In preparation for the release announcement here is what we are asking in order 
of priority:

-If an archecture image is referecned in your official readthedocs 
documentation, please use this image

-If an archecture image is referenced in your wiki pages,  please add the URL 
above to reference the the image.

-If an archecture image is referecned in a presentation slide deck, please 
ensure you use this image.

I am intentionally NOT distributing it because that is how we ended up with so 
many versions in the first place. :-)

Thanks!



Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945


_
  Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites 
ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez 
le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les 
messages electroniques etant susceptibles d'alteration, Orange decline toute 
responsabilite si ce message a ete altere, deforme ou falsifie. Merci.  This 
message and its attachments may contain confidential or privileged information 
that may be protected by law; they should not be distributed, used or copied 
without authorisation. If you have received this email in error, please notify 
the sender and delete this message and its attachments. As emails may be

Re: [onap-discuss] Updated Invitation: [appc] Weekly Meeting @ Weekly from 8am to 9am on Wednesday (PDT) (onap-discuss@lists.onap.org)

2017-11-15 Thread MAHER, RANDA

Team,

Please be aware that APPC Project call is canceled for today.

Notification has been sent to Gildas that APPC has completed all the necessary 
steps for the release.

Congratulations to the team, excellent job by all!

Randa


-Original Appointment-
From: ONAP Meetings and Events 
[mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com]
Sent: Sunday, August 06, 2017 5:20 PM
To: ONAP Meetings and Events; LEFEVRE, CATHERINE; onap-discuss@lists.onap.org
Subject: [onap-discuss] Updated Invitation: [appc] Weekly Meeting @ Weekly from 
8am to 9am on Wednesday (PDT) (onap-discuss@lists.onap.org)
When: Wednesday, November 15, 2017 11:00 AM-12:00 PM (UTC-05:00) Eastern Time 
(US & Canada).
Where: https://zoom.us/j/708562828


This event has been changed.
more details 
»

Changed: [appc] Weekly Meeting
Hi there,

ONAP Meeting 4 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/708562828
Or iPhone one-tap (US Toll): +14086380968,,708562828# or 
+16465588656,,708562828#
Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 708 562 828
International numbers available: 
https://zoom.us/zoomconference?m=nOkqgtoJBOGo7SuFC0OvOat13V5cLneM






When
Changed: Weekly from 8am to 9am on Wednesday Pacific Time

Where

https://zoom.us/j/708562828
 
(map)

Calendar
onap-discuss@lists.onap.org

Who
•
Casey Cain - creator

•
cl6...@intl.att.com

•
onap-discuss@lists.onap.org



Going?   All events in this series:   
Yes
 - 
Maybe
 -

[onap-discuss] Modeling Project doc missing

2017-11-15 Thread DeWayne Filppi

The ARIA REST API is contributed code to the ONAP project; ARIA includes a
Python library and CLI.  Runtime ARIA in ONAP lives in a container (
https://gerrit.onap.org/r/gitweb?p=so.git;a=blob;f=packages/docker/src/main/docker/docker-files/Dockerfile.aria).
Also contributed to ONAP is a Java binding for this REST API (
https://gerrit.onap.org/r/gitweb?p=so.git;a=tree;f=aria/aria-rest-java-client).
The Java binding doesn't model TOSCA itself, it just provides a Java
binding for the REST API.  Note that the REST API provides for fetching the
parsed model representation as JSON, but that call isn't in the Java
binding (yet).   There has been talk about moving the ARIA work out of SO
and into the Common Controller SDK, which I think makes some sense.
Currently the container isn't pushing properly to the Docker repo, but if
you want to look, a recent version lives on Dockerhub as
cloudifyco/aria:0.1.1.

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

Re: [onap-discuss] [HEAT Deployment] Many failures on components

2017-11-15 Thread sylvain.desbureaux

Hi  Christopher,
I agree with you. 5 minutes should be sufficient (I was actually the guy who 
proposed to move from 180s to 300s, I guess it’s not sufficient for me ;-) ).
It may be because all the VMs start at the same time and write to disks, which 
may put the servers under pressure (it’s a rather small openstack).
To be honest, this one and the one for SO are the least important imo ont the 
list :-)

Le 15 nov. 2017 à 17:54, LOTT, CHRISTOPHER M (CHRISTOPHER) 
> a écrit :

Re Portal db timeouts in version 1.3.0/R1 - the portal app server waits 300 
seconds (as configured in its docker-compose.yml file, see relevant part below) 
for the database to start.  If your system takes more than 5 minutes for the 
database docker container to become available, I wonder if something is starved 
for resources, because that seems like an unreasonably long time for a MariaDB 
server to load a few kilobytes of data.  Anyhow, to workaround you may can 
update the docker-compose file -- and submit a gerrit review so we increase the 
timeout for everyone.

--

 portal-apps:
   image: ${EP_IMG_NAME}:${PORTAL_TAG}
   ports:
 - 8989:8080
 - 8010:8009
 - 8006:8005
   links:
 - portal-db
 - portal-wms
   depends_on:
 - portal-db
 - portal-wms
   volumes:
 - 
${PROPS_DIR}/ONAPPORTAL/system.properties:${WEBAPPS_DIR}/ONAPPORTAL/WEB-INF/conf/system.properties
 - 
${PROPS_DIR}/ONAPPORTAL/fusion.properties:${WEBAPPS_DIR}/ONAPPORTAL/WEB-INF/fusion/conf/fusion.properties
 - 
${PROPS_DIR}/ONAPPORTAL/portal.properties:${WEBAPPS_DIR}/ONAPPORTAL/WEB-INF/classes/portal.properties
 - 
${PROPS_DIR}/ONAPPORTAL/openid-connect.properties:${WEBAPPS_DIR}/ONAPPORTAL/WEB-INF/classes/openid-connect.properties
 - 
${PROPS_DIR}/ONAPPORTAL/logback.xml:${WEBAPPS_DIR}/ONAPPORTAL/WEB-INF/classes/logback.xml
 - 
${PROPS_DIR}/ONAPPORTALSDK-1.3.0/fusion.properties:${WEBAPPS_DIR}/ONAPPORTALSDK/WEB-INF/fusion/conf/fusion.properties
 - 
${PROPS_DIR}/ONAPPORTALSDK-1.3.0/system.properties:${WEBAPPS_DIR}/ONAPPORTALSDK/WEB-INF/conf/system.properties
 - 
${PROPS_DIR}/ONAPPORTALSDK-1.3.0/portal.properties:${WEBAPPS_DIR}/ONAPPORTALSDK/WEB-INF/classes/portal.properties
 - 
${PROPS_DIR}/ONAPPORTALSDK-1.3.0/logback.xml:${WEBAPPS_DIR}/ONAPPORTALSDK/WEB-INF/classes/logback.xml
 - ${LOGS_DIR}:/opt/apache-tomcat-8.0.37/logs
   command:
 - /wait-for.sh
 - -t
 - "300" <- TIMEOUT VALUE IS HERE
 - portal-db:3306
 - --
 - /start-apps-cmd.sh
 # see comments in .env file
 - $EXTRA_HOST_IP
 - $EXTRA_HOST_NAME
   logging:
 driver: json-file



On Nov 15, 2017, at 11:25 AM, 
sylvain.desbure...@orange.com wrote:

Hello guys,
I’ve started a Heat deployment 4h ago with fresh pull just before.


At the end of the deployment,  I’ve got 6 over 30 tests only which are green :
   • DCAE fails (but this is because of multi cloud)
   • SDNGC fails
   • APPC fails
   • Portal fails
   • SO fails


for SDNC, it appears that the init script pull 1.1.0-release branch which is 
quite outdated compared to master. When launching with docker-compose from 
master, it starts and healthcheck is OK

for APPC, I see some errors in the logs:
Error: Could not find or load main class 
org.openecomp.sdnc.dg.loader.DGXMLGenerator
Error: Could not find or load main class org.openecomp.sdnc.dg.loader.DGXMLLoad
Error: Could not find or load main class 
org.openecomp.sdnc.dg.loader.DGXMLActivate
After changing to 1.2 instead of 1.1 for the docker version, healthcheck pass.

For portal, I’ve got a timeout from db access, after after a relaunch of the 
portal it works

For SO, a restart of the script did the trick (forgot to see the error first 
sorry)

For multicloud, I have pulling error from nexus :
Pulling repository 
nexus3.onap.org:10001/onap/msb/msb_discovery
Error: image onap/msb/msb_discovery:v1.0.0 not found
Pulling repository 
nexus3.onap.org:10001/onap/msb/msb_apigateway
nexus3.onap.org
Error: image onap/msb/msb_apigateway:v1.0.0 not found


Am I the only one having all these errors?
How can I debug multicloud?

Thanks!


--


Sylvain Desbureaux
Ingénieur concepteur développeur
ORANGE/IMT/OLN/CNC/NCA/SINA

Fixe : +33 2 96 07 13 80
Mobile : +33 6 71 17 25 57
sylvain.desbure...@orange.com

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

2017-11-15 Thread Arun Arora

Following JIRA Ticket: https://jira.onap.org/browse/SDNC-102


was created for this issue and marked as Resolved and Closed. However, the 
issue still seems to be present.


In comments it was mentioned to change the port from 10003 to 10001 in 
docker-compose.yml.

But I didn't find any such port in 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml.


Can someone provide me a working hack..


Thanks,

Arun Arora



[SDNC-102] SDNC Failed Robot Health Check - 
ONAP
jira.onap.org
No reviews matched the request. Check your Options in the drop-down menu of 
this sections header.



From: onap-discuss-boun...@lists.onap.org  
on behalf of Arun Arora 
Sent: Wednesday, November 15, 2017 10:37:33 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [SDNC] sdnc_vm_init.sh fails



ERROR: {"message":"repository onap/sdnc-image not found: does not exist or no 
pull access"}


Hi All,


I am seeing this error since yesterday. I tried to re-pull SDNC dockers afresh. 
For that I deleted all dockers along with all the files/ directories downloaded 
in /opt when sdnc_install.sh runs.


I tried this many times but the I receive the same error above in each trial.


What may be the reason of this error? I doubt it is some local setup issue as I 
re-pulled other VMs as well along with SDNC but didn't see any such error.


Is this seen by someone else? Any possible solutions?


Thanks,

Arun Arora


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

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Re: [onap-discuss] [HEAT Deployment] Many failures on components

Re: [onap-discuss] [HEAT Deployment] Many failures on components

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Re: [onap-discuss] Clarifying the TSC selected branching model for Amsterdam

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

[onap-discuss] newbee question

Re: [onap-discuss] [vvp] - documentation

Re: [onap-discuss] 答复: RE: question about sdc_vm_init

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

[onap-discuss] 答复: [onap-tsc] Official ONAP Architecture Slide

Re: [onap-discuss] newbee question

Re: [onap-discuss] Modeling Project doc missing

[onap-discuss] 答复: RE: RE: Re: [onap-tsc] Official ONAP ArchitectureSlide

[onap-discuss] [vnfrqts] The requirement of open source database needs discussion and I suggest we remove it in R1.

[onap-discuss] 答复: [vnfrqts] vnf requirement keeps align with vnf guideline

[onap-discuss] compile:aai

[onap-discuss] [integration][uui]VoLTE use case UUI peroformance and alarm function test

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

[onap-discuss] 答复: [onap-tsc] Official ONAP Architecture Slide

Re: [onap-discuss] [onap-tsc] 答复: Official ONAP Architecture Slide

[onap-discuss] Service distribution WorkFlow across various sdc/mso/aai/sdnc/v Containers via SDC Gui by Ops user

Re: [onap-discuss] [E] Centralized Image Management proposal discussion

Re: [onap-discuss] [vvp] - documentation

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

Re: [onap-discuss] Updated Invitation: [appc] Weekly Meeting @ Weekly from 8am to 9am on Wednesday (PDT) (onap-discuss@lists.onap.org)

[onap-discuss] Modeling Project doc missing

Re: [onap-discuss] [HEAT Deployment] Many failures on components

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

35 matches

Site Navigation

Mail list logo

Footer information