Re: [onap-discuss] [aai][integration] Bad image tags

[eric.debeau]

Hello Helen

I simply follow the official documentation ;-) and deploy on our lab with no 
pre-installed Docker images.

And Jimmy agreed there is a problem in the deploy_vm1.sh script
Cf https://lists.onap.org/pipermail/onap-discuss/2018-June/010250.html


With the associated JIRA ticket https://jira.onap.org/browse/AAI-1222

I suspect that it ok on WindRiver platform because you have the right Docker 
images downloaded from previous installation.

In addition, you are also using the following Docker  repo: 10.12.5.2:5000 
according to
https://git.onap.org/integration/tree/test/ete/labs/windriver/onap-openstack-template.env

Best Regards

Eric

De : Yunxia Chen [mailto:helen.c...@huawei.com]
Envoyé : mercredi 13 juin 2018 01:08
À : DEBEAU Eric IMT/OLN; onap-discuss@lists.onap.org; Gary Wu
Objet : Re: [onap-discuss] [aai][integration] Bad image tags

Hi, Eric,
Could you please show us what’s the command you use to get this? Gary did some 
sanity testing with this env, it seems fine:

http://12.234.32.117/jenkins/job/windriver-beijing-heat-deploy/

Regards,

Helen Chen

From:  on behalf of Eric Debeau 

Date: Tuesday, June 12, 2018 at 5:17 AM
To: onap-discuss 
Subject: [onap-discuss] [aai][integration] Bad image tags

Hello

We tested the fresh new installation using Heat and the 2.0.0-ONAP branch


For AAI, we have some pbs due to the bad image tags. The init script fetches 
docker image with tag 1.2.2

Pulling repository nexus3.onap.org:10001/onap/model-loader
Tag 1.2.2 not found in repository nexus3.onap.org:10001/onap/model-loader
Error response from daemon: No such image: 
nexus3.onap.org:10001/onap/model-loader:1.2.2
Pulling repository nexus3.onap.org:10001/onap/sparky-be
Tag 1.2.2 not found in repository nexus3.onap.org:10001/onap/sparky-be
Error response from daemon: No such image: 
nexus3.onap.org:10001/onap/sparky-be:1.2.2
Pulling repository nexus3.onap.org:10001/onap/champ
Error: image onap/champ:1.2.2 not found
Error response from daemon: No such image: 
nexus3.onap.org:10001/onap/champ:1.2.2
Pulling repository nexus3.onap.org:10001/onap/gizmo
Error: image onap/gizmo:1.2.2 not found
Error response from daemon: No such image: 
nexus3.onap.org:10001/onap/gizmo:1.2.2
Pulling repository nexus3.onap.org:10001/onap/babel
Error: image onap/babel:1.2.2 not found
Error response from daemon: No such image: 
nexus3.onap.org:10001/onap/babel:1.2.2

These tags are not aligned with the manifest
https://onap.readthedocs.io/en/beijing/release/release-manifest.html#doc-release-manifest

As a result, it is not possible to download the docker images. We must do it 
manually with the right tag.

I believe that we must update the script deploy_vm1.sh to get the right tag 
values

Best regards

Eric

_



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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] [aai][integration] Bad image tags

[eric.debeau]

Hello

We tested the fresh new installation using Heat and the 2.0.0-ONAP branch


For AAI, we have some pbs due to the bad image tags. The init script fetches 
docker image with tag 1.2.2

Pulling repository nexus3.onap.org:10001/onap/model-loader
Tag 1.2.2 not found in repository nexus3.onap.org:10001/onap/model-loader
Error response from daemon: No such image: 
nexus3.onap.org:10001/onap/model-loader:1.2.2
Pulling repository nexus3.onap.org:10001/onap/sparky-be
Tag 1.2.2 not found in repository nexus3.onap.org:10001/onap/sparky-be
Error response from daemon: No such image: 
nexus3.onap.org:10001/onap/sparky-be:1.2.2
Pulling repository nexus3.onap.org:10001/onap/champ
Error: image onap/champ:1.2.2 not found
Error response from daemon: No such image: 
nexus3.onap.org:10001/onap/champ:1.2.2
Pulling repository nexus3.onap.org:10001/onap/gizmo
Error: image onap/gizmo:1.2.2 not found
Error response from daemon: No such image: 
nexus3.onap.org:10001/onap/gizmo:1.2.2
Pulling repository nexus3.onap.org:10001/onap/babel
Error: image onap/babel:1.2.2 not found
Error response from daemon: No such image: 
nexus3.onap.org:10001/onap/babel:1.2.2

These tags are not aligned with the manifest
https://onap.readthedocs.io/en/beijing/release/release-manifest.html#doc-release-manifest

As a result, it is not possible to download the docker images. We must do it 
manually with the right tag.

I believe that we must update the script deploy_vm1.sh to get the right tag 
values

Best regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] License for docker-compose.yml

[eric.debeau]

Hello

Following feedbacks from Linux Foundation, the last license scan detected that 
docker-compose.yml does not contain license. Do we need to put a license in 
docker-compose.yml file ?

In general, where are defined the rules to exclude some files with license 
issues ?

Best Regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] [university] EdX course Introduction to ONAP: Complete Network Automation

[eric.debeau]

Hello
A very good EdX course on ONAP introduction "Introduction to ONAP: Complete 
Network Automation"
https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS163x+1T2018/course/

After reminding some basic NFV concepts, the course explains ONAP, the 
architecture, the main components and the use-case overview.
A very good introduction for beginners with a large number of cool quizzes.

Best Regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] [documentation] Amsterdam installation correction

[eric.debeau]

Hello

I corrected the documentation for SettingUp ONAP for Amsterdam 
https://onap.readthedocs.io/en/amsterdam/guides/onap-developer/settingup/fullonap.html
 with the links towards the Amsterdam Branch for the Heat and environment files.

Best Regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] [doc] ONAP for the newbies

[eric.debeau]

Hello

Please find the presentation on ONAP for newbies on the wiki
https://wiki.onap.org/download/attachments/25429038/ONAP-Newbies%202-08-2018.pdf?version=1=1518105955000=v2


Best Regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

[eric.debeau]

Hello

We first need to define what we want to test on the labs.

We need various platforms to test at least a minimal installation on various 
environments to validate that the installation works fine in different 
environments (ie 3 different platforms) in a daily basis.
I believe that we need around 100~150 GB RAM memory for that (we are working to 
optimize a minimal installation).
We can offer our lab for that.

Each project should test their various modules in standalone and cluster mode 
and that should not require such many resources on a project basis.

Now, do we need to test a full HA mode for all the components ?
If yes, It may require a huge amount of resources according to first answers 
(eg SDNC) running on different platforms.
We need to estimate that.

Best Regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] Resources Required

[eric.debeau]

Hello Ayush

We documented the full ONAP installation requirements in readthedocs: 
http://onap.readthedocs.io/en/latest/guides/onap-developer/settingup/fullonap.html#requirements

We are working to define a minimal configuration with smaller flavors to run 
with a minimal number of users and VNFs.

Best Regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

Re: [onap-discuss] DockerHub: missing latest tag

[eric.debeau]

+1 for the docs for every onap docker image

Best Regards

Eric

De : Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Envoyé : lundi 27 novembre 2017 09:01
À : DEBEAU Eric IMT/OLN; onap-discuss@lists.onap.org
Objet : RE: [onap-discuss] DockerHub: missing latest tag

Dear Eric,

Yes, we should tag it with latest. Also It would be  great if we could put 
description and url to docs page for every onap docker image.

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 
eric.deb...@orange.com
Sent: Monday, November 27, 2017 1:12 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] DockerHub: missing latest tag

Hello

The ONAP Docker images are hosted in DockerHub (https://hub.docker.com/r/onap). 
However, the latest tag is missing for many images. As a consequence the
Docker pull onap/ fails. We need to specific the tag to pull the 
image.

Best regards

Eric

_



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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] DockerHub: missing latest tag

[eric.debeau]

Hello

The ONAP Docker images are hosted in DockerHub (https://hub.docker.com/r/onap). 
However, the latest tag is missing for many images. As a consequence the
Docker pull onap/ fails. We need to specific the tag to pull the 
image.

Best regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

Re: [onap-discuss] [doc] Setting UP ONAP

[eric.debeau]

Hello

Thank you for the feedback.

There is some minor issues in the RST file and some missing links.

I will correct it.

Best Regards

Eric

De : Yang, Bin [mailto:bin.y...@windriver.com]
Envoyé : vendredi 17 novembre 2017 02:11
À : DEBEAU Eric IMT/OLN; onap-discuss@lists.onap.org
Cc : li.z...@zte.com.cn; shen...@chinamobile.com; Xinhui Li (lxin...@vmware.com)
Objet : RE: [onap-discuss] [doc] Setting UP ONAP

Hi Eric,

A minor issue: The section "ONAP 
components"
 seems not list all of ONAP projects in that table, at least the ONAP 
MulitCloud project is not listed which is running over VM named 
"onap-multi-service" .
Perhaps the same issue applies to ESR and UUI. So I copy the PTLs (Lizi and 
Shentao) for confirmation.
Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
eric.deb...@orange.com
Sent: Thursday, November 16, 2017 6:15 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [doc] Setting UP ONAP

Hello

Please, can you review the setting Up ONAP under the readthedocs.
http://onap.readthedocs.io/en/latest/guides/onap-developer/settingup/fullonap.html

Thanks you for your feedbacks

Eric

_



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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] [doc] Setting UP ONAP

[eric.debeau]

Hello

Please, can you review the setting Up ONAP under the readthedocs.
http://onap.readthedocs.io/en/latest/guides/onap-developer/settingup/fullonap.html

Thanks you for your feedbacks

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

Re: [onap-discuss] Modeling Project doc missing

[eric.debeau]

Hello

I will help DeWayne

Eric
De : denghui (L) [mailto:denghu...@huawei.com]
Envoyé : jeudi 16 novembre 2017 03:16
À : DeWayne Filppi; onap-discuss@lists.onap.org
Cc : DEBEAU Eric IMT/OLN
Objet : RE: [onap-discuss] Modeling Project doc missing

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

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

Re: [onap-discuss] Modeling Project doc missing

[eric.debeau]

Thanks Arthur

But how this parser/component is used within ONAP ?

Best Regards

Eric

De : Arthur Berezin [mailto:art...@cloudify.co]
Envoyé : mardi 7 novembre 2017 18:16
À : denghui (L)
Cc : DEBEAU Eric IMT/OLN; JORA, SERBAN; Rittwik Jana; art...@gigaspaces.com; 
shang.xiaod...@zte.com.cn; meng.zhaoxi...@zte.com.cn; BENNETT, RICH; 
denglin...@chinamobile.com; onap-discuss
Objet : Re: Modeling Project doc missing


On Tue, Nov 7, 2017 at 1:39 PM denghui (L) 
> wrote:
Hi Eric, Trimed and inline please,  == >

Hi Serban, there is one question from Eric for you below
Hi Arthur, there is one question from Eric for you inside


I think we should provide more example how to use it bot using CLI and API.

We should also provide some documentation to explain the TOSCA models that can 
be managed by the tool (like for the NFV parser: 
http://onap.readthedocs.io/en/latest/submodules/modeling/toscaparsers.git/docs/nfvparser/userguide/feature.userguide.html)

I can check if there is some example in the code.
== >As you may know, release 1 is not very stable release, there will be many 
changes in release 2, especially for modeling part, TSC chair only ask for 
minimal documentation requirement for each project,
I can’t ask more requirement to developers at this moment, some of them are not 
just busy with this project.


For API,
It is based on wiki documentation, but it is confusing.
We have 3 Parsers describes while only 2 are defined in the Documentation with 
different names

Wiki:

•Openstack Tosca Parser API: (Python)

•Apache ARIA-TOSCA(Python + CLI + REST API)

•Java based Tosca Parser API: (Java)

DOC :
javatoscachecker
NFV 
Parser

I assume that Java based Tosca Parser API = 
javatoscachecker
And NFV 
Parser
 =  Openstack Tosca Parser API: (Python)

Which name do we keep: Java based Tosca Parser and NFV Parser ?
== > Serban, do you have any suggestion?
Where is documented Apache ARIA-TOSCA(Python + CLI + REST API) ?
== > I heard that Aria would like their code in SO project, so I don’t know 
where is their document, Arthur, do you have answer here?

The complete project reference documentation can be found on the proejct's home 
page here:
http://ariatosca.incubator.apache.org/docs/html/index.html

I suggest starting with the getting started guild here:
http://ariatosca.incubator.apache.org/getting-started/

Additionally, you can find more some concrete examples of TOSCA Modeling 
(Incluidng basic HelloWorld, and more complex ClearWater example) here:
https://github.com/apache/incubator-ariatosca/tree/master/examples

Best,
Arthur

We introduced a API ref page within the documentation. I would like to update 
it with a link to the API rst page from modeling.

I propose the following changes.


•Merge wiki documentation with RST files if my assumptions are ok

•Add an API page for the modeling that will give the links towards the 
various Parsers API

•I update the global API ref for the documentation with the new API 
page for modeling
== > we are asked to publish API in the architecture team, not in modeling, but 
I am fine with this contribution, we could create another folder on it.
Thanks

DENG Hui

I can do it today if your are ok.

Best Regards

Eric

De : denghui (L) [mailto:denghu...@huawei.com]
Envoyé : mardi 7 novembre 2017 04:11
À : DEBEAU Eric IMT/OLN
Cc : BENNETT, RICH
Objet : RE: Modeling Project doc missing

Hello Eric

Thanks a lot for your kind offer.
Here is the updated link : 
http://onap.readthedocs.io/en/latest/submodules/modeling/toscaparsers.git/docs/javatoscachecker/index.html
Feel free to let us know if we need to make any further any update.

For API, it has been documented on the wiki page
https://wiki.onap.org/display/DW/Modeling+API

thanks a lot

DENG Hui


From: eric.deb...@orange.com 
[mailto:eric.deb...@orange.com]
Sent: Tuesday, November 7, 2017 1:21 AM
To: denghui (L) >
Cc: BENNETT, RICH >
Subject: RE: Modeling Project doc missing

Hello Hui

The documentation for javatoscachecker is still missing

We also need to identify if the parsers offer some API. It still unclear for me 
if the parsers are only some libraries or independent components offering API.

If you have some issues to translate the initial PDF file provided for 
javatoscachecker, we may find a solution.

Best Regards

Eric

De : denghui (L) [mailto:denghu...@huawei.com]
Envoyé : 

[onap-discuss] AAI UI

[eric.debeau]

We can find some information on the VIEW_INSPECT.MD and VNFS.MD files under the 
aai/sparky-be.git repo

Regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] Layer123 presentation

[eric.debeau]

Hello

Please find the slides presented during the Layer123 event
https://wiki.onap.org/download/attachments/16001688/SNDWC-ONAP-MiniSummit-VNF-Onboarding.pdf?api=v2

Regards,

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] [documentation] Paris-Saclay Monday slides for the session Documentation: how to describe detailed call flows

[eric.debeau]

Hello, I uploaded the slides presented on Monday afternoon for the 
"Documentation: how to describe detailed call flows" session
https://wiki.onap.org/download/attachments/15997434/ONAP-Documentation-Detailed-Call-Flows.pdf?api=v2

Best Regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] [sdc] vendorName size limitation

[eric.debeau]

Hello

When testing the SDC API, I get the following answer for the request
http://{sdc-ip}:8080/onboarding-api/v1.0/vendor-license-models


{"status":"EXPECTATION_FAILED","errorCode":"FIELD_VALIDATION_ERROR_ERR_ID","message":"Field
 does not conform to predefined criteria : vendorName : size must be between 0 
and 25"}

I could not find documentation on this limitation. We should document it in the 
SDC project.

Regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] Bitergia Dashboard Is Now Live

[eric.debeau]

Thanks Paul

I think there is still a lot of unknown (eg Alla ...)

Regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] 1.1 deployment: AAI vm1 traversal and model-loader container failure on startup on JAXB dup field "invStatus" during v11 initialization

[eric.debeau]

Hello

I share the same problem on a Vanilla OpenStack platform (Newton), but I 
believe there is also a Chef problem. I launched the stack yesterday 3:30 PM 
UTC.

Btw it would be very nice if we could start tagging builds - especially the 
ones that passed E2E integration tests - so we would not have to pick up master.

I agree with Michael. When deploying a full ONAP stack, we should rely on 
images that passed the E2E integration tests.


My docker logs for testconfig_aai-resources.api.simpledemo.openecomp.org_1

Cloning into 'aai-config'...
Cloning into 'aai-data'...
[2017-08-07T15:32:08+00:00] INFO: Started chef-zero at 
chefzero://localhost:8889 with repository at /var/chef/aai-config
  One version per cookbook
  environments at /var/chef/aai-data/environments

[2017-08-07T15:32:08+00:00] INFO: Forking chef instance to converge...
[2017-08-07T15:32:08+00:00] INFO: *** Chef 12.13.37 ***
[2017-08-07T15:32:08+00:00] INFO: Platform: x86_64-linux
[2017-08-07T15:32:08+00:00] INFO: Chef-client pid: 37
[2017-08-07T15:32:09+00:00] INFO: HTTP Request Returned 404 Not Found: Object 
not found: chefzero://localhost:8889/nodes/chef-node
[2017-08-07T15:32:09+00:00] INFO: Setting the run_list to 
["recipe[aai-resources-config::createConfigDirectories]", 
"recipe[aai-resources-auth::aai-resources-aai-keystore]", 
"recipe[aai-resources-config::aaiEventDMaaPPublisher]", 
"recipe[aai-resources-config::aai-resources-config]", 
"recipe[aai-resources-config::titan-cached]", 
"recipe[aai-resources-config::titan-realtime]", 
"recipe[aai-resources-config::aai-preferredRoute]"] from CLI options
[2017-08-07T15:32:09+00:00] INFO: Run List is 
[recipe[aai-resources-config::createConfigDirectories], 
recipe[aai-resources-auth::aai-resources-aai-keystore], 
recipe[aai-resources-config::aaiEventDMaaPPublisher], 
recipe[aai-resources-config::aai-resources-config], 
recipe[aai-resources-config::titan-cached], 
recipe[aai-resources-config::titan-realtime], 
recipe[aai-resources-config::aai-preferredRoute]]
[2017-08-07T15:32:09+00:00] INFO: Run List expands to 
[aai-resources-config::createConfigDirectories, 
aai-resources-auth::aai-resources-aai-keystore, 
aai-resources-config::aaiEventDMaaPPublisher, 
aai-resources-config::aai-resources-config, aai-resources-config::titan-cached, 
aai-resources-config::titan-realtime, aai-resources-config::aai-preferredRoute]
[2017-08-07T15:32:09+00:00] INFO: Starting Chef Run for chef-node
[2017-08-07T15:32:09+00:00] INFO: Running start handlers
[2017-08-07T15:32:09+00:00] INFO: Start handlers complete.
[2017-08-07T15:32:09+00:00] INFO: HTTP Request Returned 404 Not Found: Object 
not found:
[2017-08-07T15:32:09+00:00] INFO: Loading cookbooks 
[aai-resources-config@1.0.0, aai-resources-auth@1.0.0]
[2017-08-07T15:32:09+00:00] INFO: Storing updated 
cookbooks/aai-resources-config/recipes/createConfigDirectories.rb in the cache.
..
Exception in thread "main" java.lang.ExceptionInInitializerError
at 
org.openecomp.aai.introspection.ModelInjestor.getInstance(ModelInjestor.java:69)
at 
org.openecomp.aai.introspection.MoxyLoader.process(MoxyLoader.java:118)
at org.openecomp.aai.introspection.MoxyLoader.(MoxyLoader.java:69)
at 
org.openecomp.aai.introspection.LoaderFactory.createLoaderForVersion(LoaderFactory.java:36)
at 
org.openecomp.aai.dbgen.SchemaGenerator.loadSchemaIntoTitan(SchemaGenerator.java:118)
at 
org.openecomp.aai.dbgen.SchemaGenerator.loadSchemaIntoTitan(SchemaGenerator.java:68)
at org.openecomp.aai.dbgen.GenTester.main(GenTester.java:120)
Caused by: Exception [EclipseLink-50072] (Eclipse Persistence Services - 
2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.JAXBException
Exception Description: Duplicate Property named [invStatus] found on class 
[inventory.aai.onap.org.v11.PInterface]
at 
org.eclipse.persistence.exceptions.JAXBException.duplicatePropertyName(JAXBException.java:971)
at 
org.eclipse.persistence.jaxb.compiler.TypeInfo.addProperty(TypeInfo.java:314)
at 
org.eclipse.persistence.jaxb.compiler.TypeInfo.setProperties(TypeInfo.java:340)
at 
org.eclipse.persistence.jaxb.compiler.AnnotationsProcessor.buildTypeInfo(AnnotationsProcessor.java:864)
at 
org.eclipse.persistence.jaxb.compiler.AnnotationsProcessor.postBuildTypeInfo(AnnotationsProcessor.java:773)
at 
org.eclipse.persistence.jaxb.compiler.XMLProcessor.processXML(XMLProcessor.java:389)
at 
org.eclipse.persistence.jaxb.compiler.Generator.(Generator.java:106)
at 
org.eclipse.persistence.jaxb.dynamic.DynamicJAXBContext$MetadataContextInput.createContextState(DynamicJAXBContext.java:236)
at org.eclipse.persistence.jaxb.JAXBContext.(JAXBContext.java:192)
at 
org.eclipse.persistence.jaxb.dynamic.DynamicJAXBContext.(DynamicJAXBContext.java:71)
at 
org.eclipse.persistence.jaxb.dynamic.DynamicJAXBContextFactory.createContextFromOXM(DynamicJAXBContextFactory.java:347)
at 

[onap-discuss] [integration] [sdc] SDC Installation problem

[eric.debeau]

Hello

I want to deploy a new ONAP installation using the Heat template 
(onap_openstack.yaml) over an Ocata OpenStack using the environment  variables 
as proposed in the env files:
artifacts_version: 1.1.0-SNAPSHOT
docker_version: 1.1-STAGING-latest
gerrit_branch: master


I have some pbs with SDC installation. I relaunched the scripts within the VM, 
but the pbs are still there.
I read some similar pbs in the mailing lists 
(https://lists.onap.org/pipermail/onap-discuss/2017-July/002092.html), but my 
configuration seems a bit different and I have some HealthCheck pbs


The healthCheck for FE using $curl http://localhost:8080/sdc2/rest/healthCheck



Error 503 


HTTP ERROR: 503
Problem accessing /sdc2/rest/healthCheck. Reason:
Service Unavailable
http://eclipse.org/jetty;>Powered by Jetty:// 
9.3.15.v20161220




The healthCheck for BE using  curl http://localhost:8181/sdc1/rest/healthCheck
{
  "sdcVersion": "UNKNOWN",
  "siteMode": "UNKNOWN",
  "componentsInfo": [
{
  "healthCheckComponent": "FE",
  "healthCheckStatus": "UP",
  "version": "1.1.0-SNAPSHOT",
  "description": "OK"
},
{
  "healthCheckComponent": "BE",
  "healthCheckStatus": "DOWN"
},
{
  "healthCheckComponent": "TITAN",
  "healthCheckStatus": "UNKNOWN"
},
{
  "healthCheckComponent": "CASSANDRA",
  "healthCheckStatus": "UNKNOWN"
},
{
  "healthCheckComponent": "DE",
  "healthCheckStatus": "UNKNOWN"
},
{
  "healthCheckComponent": "ON_BOARDING",
  "healthCheckStatus": "UNKNOWN"
}
  ]
}

The docker logs for sdc-BE
Ran "bash"  "/tmp/jetty/chef-script20170801-603-1ht21zd" returned 1
[2017-08-01T07:08:03+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef 
run process exited unsuccessfully (exit code 1)


The docker logs for sdc-CS


Error executing action `run` on resource 'bash[excuting-schema-creation]'



Mixlib::ShellOut::ShellCommandFailed

Expected process to exit with [0], but received '2'
 Begin output of "bash"  "/tmp/chef-script20170801-409-nn82si" 
STDOUT: java 
-Dlogback.configurationFile=/tmp/sdctool/scripts/../config/logback.xml -cp 
::/tmp/sdctool/scripts/../asdctool-1.1.0-SNAPSHOT-jar-with-dependencies.jar: 
org.openecomp.sdc.asdctool.main.DataSchemaMenu create-cassandra-structures 
/tmp/sdctool/config
07:02:06,873 |-INFO in ch.qos.logback.classic.LoggerContext[default] - 
Found resource [/tmp/sdctool/scripts/../config/logback.xml] at 
[file:/tmp/sdctool/scripts/../config/logback.xml]
07:02:07,060 |-INFO in 
ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not 
set
07:02:07,090 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - 
About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
07:02:07,095 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - 
Naming appender as [STDOUT]
07:02:07,200 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@11:13 - 
no applicable action for [encoder], current ElementPath  is 
[[configuration][appender][layout][encoder]]
07:02:07,293 |-WARN in ch.qos.logback.core.ConsoleAppender[STDOUT] - This 
appender no longer admits a layout as a sub-component, set an encoder instead.
07:02:07,293 |-WARN in ch.qos.logback.core.ConsoleAppender[STDOUT] - To 
ensure compatibility, wrapping your layout in LayoutWrappingEncoder.
07:02:07,293 |-WARN in ch.qos.logback.core.ConsoleAppender[STDOUT] - See 
also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details
07:02:07,294 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - 
About to instantiate appender of type 
[ch.qos.logback.core.rolling.RollingFileAppender]
07:02:07,300 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - 
Naming appender as [DEBUG_ROLLING]
07:02:07,334 |-INFO in 
ch.qos.logback.core.rolling.FixedWindowRollingPolicy@4c75cab9 - No compression 
will be used
07:02:07,348 |-INFO in 
ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default 
type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] 
property
07:02:07,367 |-INFO in 
ch.qos.logback.core.rolling.RollingFileAppender[DEBUG_ROLLING] - Active log 
file name: /root/asdctool/logs/SDC/SDC-TOOL/debug.log
07:02:07,367 |-INFO in 
ch.qos.logback.core.rolling.RollingFileAppender[DEBUG_ROLLING] - File property 
is set to [/root/asdctool/logs/SDC/SDC-TOOL/debug.log]
07:02:07,370 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - 
About to instantiate appender of type 
[ch.qos.logback.core.rolling.RollingFileAppender]
07:02:07,370 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - 
Naming appender as [MALFORMED_DATA]
07:02:07,373 |-INFO in 

[onap-discuss] ONAP Architecture R1 (Project View)

[eric.debeau]

Hello

Thanks for sharing the slides.

Some comments:

ONAP Architecture R1
I do not understand why we introduce EMS and S-VNFM in the ONAP platform. Do 
that mean such components will be open-sourced for the community ?

Can you clarify what is the Multi-VIM component from Open-O.

It is confusing to have VF-C as a controller because VF-C embeds more functions 
than a controller

For pink modules (convergence from both sides), it is not clear why they are 
qualified as convergent : eg why Holmes is qualified as convergent ? For SO, it 
should be great to explain the various source components: eg MSO from OpenECOMP 
& GSO ? from Open-O

I also believe that we should also 2 figures:

-   The existing figure to explain the source components, the new ones...

-   Another one without explaining the source components, but with more 
explanation on the components (ie explicit DCAE, VF-C, APP-C, A, ESR)

ONAP Projects R1
Alarm Correlation App (Holmes) is no more convergent => to be aligned with 
previous slide.
Modeling should be under the common services box.
ESR is under common service box while in previous figure it is associated with 
A

Regards,

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] [multicloud] Multi-VIM API

[eric.debeau]

We need to clarify the API definition. The Multi-VIM will be used by SO, APPC, 
VFC for Infra Resource and VNF LCM.

SO, APPC, VFC will not use OpenStack direct API to request resource creation 
(using Heat or Nova API). SO, APPC & VFC will request the Multi-VIM API (to be 
defined).

SO, APPC, VFC require some specific parameters (coming from AAI) to route 
towards the right VIM

It is key to define the multi-VIM northbound API for the various components 
that will consume it.

Regards,

Eric


_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] [SDC Documentation]

[eric.debeau]

Hello

On the SDC wiki (https://wiki.onap.org/pages/viewpage.action?pageId=1015837), 2 
documents are referenced for the SDC documentation, but are not available on 
the wiki.

<>, under the section "Design", describes how to use 
the SDC.

See the <> for a specific example of how to onboard a 
Virtual Network Function, using SDC.
Is it possible to upload them ?

Thanks.

Regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

Re: [onap-discuss] [onap-discssus] Tooling for call flow

[eric.debeau]

Hello

I am talking about call flow for use-case description (eg call flow for VoLTE: 
https://wiki.onap.org/download/attachments/3246140/image2017-5-17_18-34-39.png?version=1=149501728=v2
) or for any documentation.

Eric

De : ROSE, DANIEL V [mailto:dr6...@att.com]
Envoyé : mercredi 24 mai 2017 19:58
À : DEBEAU Eric IMT/OLN; onap-discuss@lists.onap.org
Objet : RE: [onap-discssus] Tooling for call flow

Hi Eric,

Are you talking about call flows in the model 
(https://wiki.onap.org/display/DW/Service+Design#ServiceDesign-CNCF )?

Or are you talking about DGs in sdnc?

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
eric.deb...@orange.com
Sent: Wednesday, May 24, 2017 3:17 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [onap-discssus] Tooling for call flow

Hello

To be able to work on call flow in a collaborative way, I believe that we 
should use a tool based on a description language rather using images.

Is there any guideline within the Linux Foundation for such tooling ?

Within Orange, we developed a cool tool:
https://github.com/Orange-OpenSource/EtherPlant

Eric

_



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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] [onap-discssus] Tooling for call flow

[eric.debeau]

Hello

To be able to work on call flow in a collaborative way, I believe that we 
should use a tool based on a description language rather using images.

Is there any guideline within the Linux Foundation for such tooling ?

Within Orange, we developed a cool tool:
https://github.com/Orange-OpenSource/EtherPlant

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[onap-discuss] Technical Deep Dive on Tuesday May 2nd

[eric.debeau]

Hello

I would like to know where we can find the cool slide sets presented last week 
during the ONAP Project Developer Event and especially for the Tuesday deep 
dive session (APP-C, SDC, AAI).

Regards

Eric

_

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 altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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