Re: [onap-discuss] [coe] Team meeting Agenda

[HU, BIN]

Victor,

The endpoint is the one (URL) in “Auth Url” when using ESR portal, or the 
“service-url” property in “esr-system-info” when using curl.

The endpoint is the base URL of K8S API (as a microservice), which we should 
define.

Thanks
Bin

From: Morales, Victor [mailto:victor.mora...@intel.com]
Sent: Tuesday, June 12, 2018 4:02 PM
To: HU, BIN ; Addepalli, Srinivasa R 
; onap-discuss@lists.onap.org
Subject: Re: [coe] Team meeting Agenda

Hey there,

@Bin, I have a question about using the ESR VIM registration portal. According 
to the wiki using this method will trigger a discovery process. I’m wondering 
if we have to create an endpoint for this, maybe it’s something that we can 
include into the API definition and implement it later.

@Srini regarding your questions, for this PoC we have only considered the 
scenario for consuming the ./kube/config[1] file. In the other hand, I noticed 
that’s possible to configure Kubernetes to use Basic Authentication method [2] 
which can do something similar than OpenStack.  Lastly, regarding the 
concatenation I have the impression that what Kubernetes is doing internally is 
quite enough to guarantee its uniqueness, but we can include it as a functional 
test to cover that scenario.

Regards,
Victor Morales

[1] 
https://github.com/electrocucaracha/krd/blob/master/installer#L97
[2] 
https://github.com/electrocucaracha/krd/blob/master/inventory/group_vars/k8s-cluster.yml#L69


From: "HU, BIN" mailto:bh5...@att.com>>
Date: Tuesday, June 12, 2018 at 1:04 PM
To: "Addepalli, Srinivasa R" 
mailto:srinivasa.r.addepa...@intel.com>>, 
Victor Morales mailto:victor.mora...@intel.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Subject: RE: [coe] Team meeting Agenda

Refer to the wiki page: 
https://wiki.onap.org/pages/viewpage.action?pageId=25431491
 (How-To: Register a VIM/Cloud Instance to 
ONAP).

In this guide, when registering a new VIM, we need to:

-  Create Complex object in A

-  Register VIM/Cloud instance in A

-  And some other steps

When registering VIM/Cloud instance in A, one can use curl command to create 
a cloud region object in A This Cloud Region Object contains a 
“esr-system-info-list” which includes “username” and “password” for keystone 
authentication.

Because this schema is OpenStack-centric, we may have 2 options:

-  Reuse “password” property, and store kubeconfig information within 
this “password” property

-  Or expand the “esr-system-info-list” with a new property for 
kubeconfig information.

Hope it helps
Thanks
Bin

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Addepalli, Srinivasa R
Sent: Tuesday, June 12, 2018 12:29 PM
To: Morales, Victor 
mailto:victor.mora...@intel.com>>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [coe] Team meeting Agenda

Hi Victor and Shashank,

There were few questions from Multi-Cloud meeting yesterday (Shankar and 
others).  It would be good if we could cover following also today


-  K8S plugin needs to have access to information that connect to K8S 
masters in the remote edge-clouds/sites.  Normal practice for K8S client is to 
read kubeconfig file  that has connectivity information for each cluster and 
certificate/private key to be used to communicate with remote site K8S master.  
In ONAP, we have ESR. Are we going to use ESR or K8S plugin provides its own 
way to upload kubeconfig information.  If so, how does get stored in A Is 
there any schema change required?

-  K8S plugin at the run time will use same deployment template files 
multiple times.  But, each deployment instance needs to be uniquely identified. 
Normally, ObjectMeta.Name is used to uniquely identify each deployment.  I 
guess it means that K8S 

[onap-discuss] Building blocks for multicloud k8s plugin, RE: [coe] Team meeting Agenda

[Yang, Bin]

Hi Victor, Srini and all,

In addition to the agenda you listed, could you also add one more to touch the 
topic of building blocks (e.g. “language binding” with golang instead of 
python) for multicloud k8s plugin?

I do understand that from the architecture perspective it is irrelevant w.r.t. 
how to implement the plugin service, hence up to developers/contributors’ 
choice. However, it is worth to think again for following reasons:

1, Leverage and Scale
   Aligning to existing practice of multicloud plugin 
implementation enables developers focus on the core value of the plugin, e.g. 
mediate ONAP orchestration to k8s cluster in case of multicloud k8s plugin. As 
part of ONAP projects it is required that the multicloud k8s plugin be 
integrated with CI/CD process and other shared services (e.g. AAF, centralized 
logging, etc.)  Right now CI/CD support projects with python binding very well, 
and the logging AOP facility for Python is well supported, I don’t know if 
there is off-the-shelf utility for golang available yet. If multicloud k8s 
plugin align to the existing practice of openstack plugin and vio plugin, then 
you don’t have to invest further time/cost on those effort.


2, Facilitate more participation from current multicloud committers/contributors
   multicloud committers/contributors has been working on python 
already for a long time , and it is not surprising that many of them are 
willing to participate/contribute to this multicloud k8s plugin development. 
Assuming that Golang is not as widely adopted as Python so most of them is not 
that familiar with Golang compared to Python, it would lower the barrier for 
them to contribute if multicloud k8s plugin could adopt the same language and 
framework.

3, Decrease the maintenance cost from either community and the Service 
Providers who will productize ONAP
   By align to the same practice and share the same building blocks 
across multicloud plugins, one committer/contributor support/maintain one 
plugin could also be possible to support another one with low cost to 
learn/understand it. This will decrease the TCO which is always a pain of open 
source product compared to those commercialized close source product.

4, facilitate pairwise/integration testing for fast release cadence
   It might not concern those architect, but it is really a pain 
for developers who support the pairwise/integration testing. Fortunately, 
python make our life better since it is possible to fix the bug on runtime and 
test it immediately, which reduce the cycle of debugging. I can share you some 
feedback from several PTLs whom I had supported during Pairwise/integration 
test if you are interested to know.

So it is my 2 cents, please let me know if you have other concerns/opinions and 
I am willing to learn them, 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 Yang, Bin
Sent: Wednesday, June 13, 2018 9:21 AM
To: ADDEPALLI, SRINIVASA; MORALES RUVALCABA, VICTOR; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [coe] Team meeting Agenda

Hi Srini, and all,

   With regarding to the “each deployment instance needs to be 
uniquely identified”,  what is the intention for this “uniquely identified”? I 
mean, who will care about/consume this unique ID?

IMHO, from multicloud NBI consumers’ perspective, I don’t get the point to 
identify uniquely each deployment instance of multicloud plugin for following 
reasons:
1, every multicloud plugin could be deployed as a cluster/replicated set of 
“deployment instances” within a single ONAP instance, but they all should 
expose the NBI via the same endpoint. I assume every multicloud plugin are 
stateless service so that the consumer’s requests can be distributed via MSB or 
some other load balance mechanism . In that case multicloud consumers are not 
aware the “multiple deployment instances” of any multicloud plugin.

2, every multicloud plugin can also be deployed in the distributed way (e.g. 
deployed along with each edge ONAP instance).  In this case the each multicloud 
deployment instance exposes unique NBI endpoint since the IP address of hosts 
(which are used to deploy the multicloud plugins) are different, so the 
consumers should be aware of which edge ONAP they are talking to.

With either case the multicloud consumers are not necessarily identify uniquely 
the deployment instance.

You may also wonder to know that how the consumers (SO, APPC,VFC) know what the 
multicloud plugin deployment instance’s NBI endpoint is in either cases above, 
here is my understanding :
1, The MultiCloud deployment instance’s NBI endpoint can be found from the 
cloud region in AAI (e.g. "identity-url": "http://: 

Re: [onap-discuss] [E] TOSCA on Kubernetes: Puccini

[Tal Liron]

Thank you, Kumar, for taking a look and for the good questions. I'll
respond with big wall-of-text answers. :)

>
>- As you had rightly mentioned in your AriaTosca message in
>mailinglist, ONAP has already got handful of parsers, including very own
>aria and it is not fully integrated with SO yet ( please correct me if I'm
>wrong ). What unique advantages would puccini bring, apart from being yet
>another, fresh, tosca 1.1 compliant, standalone, golang-js-based parser ?
>I'm not debating the arguments that you made on the aria-mailing list, am
>just trying to understand your argument on how it could benefit ONAP in
>particular?
>
> I would frame this question even more broadly: Why does ONAP need TOSCA at
all?

The current uses of TOSCA in ONAP don't make much sense to me. We're just
using it as a place to dump ETSI descriptor properties. Packaging in CSAR
is not interesting: it's just a ZIP file. We could have just as easily
packaged VNFs in a ZIP file with a few YAML descriptor files of the agreed
upon attributes and without any of the TOSCA parsing overhead. (I imagine
that's what many ONAP engineers would have preferred.)

But TOSCA, if used as fully intended, has the potential to allow
cloud-native VNFs to more fully cooperate with ONAP. "Cloud native" means
that they can manage their own lifecycle, but by exposing their internals
to the high-level orchestrator (ONAP) they can delegate some control to the
orchestrator and provide better visibility.

VNFs know themselves best. They know what they need to do in order to scale
and heal. They know what metrics make sense for their workloads. All these
details are very implementation-specific, but TOSCA provides a general
grammar for describing these things, including custom configurable policies
for adaptive behavior. The idea is that neither orchestrator nor VNF is a
"black box", but still we let each component do what it does best.

For TOSCA to live up to its potential it has to be used by and useful for
VNFs. To be useful, it must interact with the cloud-native domain. And
that's always implementation-specific. As I have argued for a long time:
the TOSCA grammar is good, the TOSCA normative types—not so good. The key
to making TOSCA useful is to model the infrastructure directly and
precisely. Instead of a generic "Compute" type, Puccini provides node,
capability, data, and policy types that model the Kubernetes platform, so a
VNF can use TOSCA to deploy itself with full specificity. TOSCA should not
be overhead, but a solution: a desirable solution for both the VNF and for
the orchestrator.

By the way, cloud-native Kubernetes is not just about YAML specs. In my
other talk in Beijing (I'm planning two) I will introduce the growing
necessity for writing custom "operators
" for Kubernetes,
to manage the specialized, non-generic lifecycle needs. Specifically, I
will show how Clearwater can scale its SIP routers/edge-proxies on its own
terms by embedding operators into Kubernetes. This is not something that
Kubernetes can do out-of-the-box, because it's highly application-specific.
All of this can be modeled in a higher level with TOSCA, so it can be
comprehensible by both the VNF and the orchestrator.

>
>- Since today, SO is predominantly BPMN driven, how much effort does
>it take to come up with BPMN backend ? Is it feasible ?
>
> It is entirely feasible. Puccini's innovation here is in providing an
intermediary format (Clout). TOSCA compiles to Clout, and then Clout can be
processed by a workflow engine. Again, as I keep emphasizing, the key to
making such solutions work well is domain-specific modeling. Once you free
yourself from being locked into generic types you can really make TOSCA do
a lot for you. The TOSCA service templates should include types
(interfaces, policies) that would make sense specifically for a your custom
BPMN workflow environment. Moreover, the Clout can contain simple
JavaScript to automagically spit out the format that you need.

TOSCA is very good at this because it allows you to inherit/compose
existing types. So, a VNF vendor can provide a detailed model of its
components (and their internal requirements-and-capabilities). To interact
with BPMN properly it would be possible to "import" both sets of types and
model and configure them together. There's always on-boarding work to be
done, but this could allow you to work with the VNF instead of against it.

Clout also attempts to solve the "day 2" problem. TOSCA is only your day 1
model: after you deploy a VNF, it is expected that it will change
(scale/heal), making the original TOSCA no longer relevant. But, that Clout
has all the attributes and functions compiled into it. So all you need to
do is read from the live deployment and update your existing Clout with the
updated topology and attributes. And your tool chain will continue to work
as usual. This has always been part of 

Re: [onap-discuss] [coe] Meeting's survey

[Yang, Bin]

Hi Victor,

   Is this survey closed?  The current schedule is not friendly for 
developers in China, could you help re-open the survey so that we can find out 
the time slot accommodating everyone participant?

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 Morales, Victor
Sent: Friday, May 25, 2018 5:55 AM
To: HU, BIN; ADDEPALLI, SRINIVASA; Munish Agarwal; onap-discuss@lists.onap.org; 
SHANKAR, SHASHANK KUMAR; YELESWARAPU, RAMAMANI
Subject: [onap-discuss] [coe] Meeting's survey

Hey there,

Maybe I was the only confused about the time for this meeting but it could be a 
good time to propose a different time. So please vote for the best time that 
works for you.

https://www.surveymonkey.com/r/FRSKR85

Regards,
Victor Morales
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [coe] Team meeting Agenda

[Yang, Bin]

Hi Srini, and all,

   With regarding to the “each deployment instance needs to be 
uniquely identified”,  what is the intention for this “uniquely identified”? I 
mean, who will care about/consume this unique ID?

IMHO, from multicloud NBI consumers’ perspective, I don’t get the point to 
identify uniquely each deployment instance of multicloud plugin for following 
reasons:
1, every multicloud plugin could be deployed as a cluster/replicated set of 
“deployment instances” within a single ONAP instance, but they all should 
expose the NBI via the same endpoint. I assume every multicloud plugin are 
stateless service so that the consumer’s requests can be distributed via MSB or 
some other load balance mechanism . In that case multicloud consumers are not 
aware the “multiple deployment instances” of any multicloud plugin.

2, every multicloud plugin can also be deployed in the distributed way (e.g. 
deployed along with each edge ONAP instance).  In this case the each multicloud 
deployment instance exposes unique NBI endpoint since the IP address of hosts 
(which are used to deploy the multicloud plugins) are different, so the 
consumers should be aware of which edge ONAP they are talking to.

With either case the multicloud consumers are not necessarily identify uniquely 
the deployment instance.

You may also wonder to know that how the consumers (SO, APPC,VFC) know what the 
multicloud plugin deployment instance’s NBI endpoint is in either cases above, 
here is my understanding :
1, The MultiCloud deployment instance’s NBI endpoint can be found from the 
cloud region in AAI (e.g. "identity-url": "http://: /api/multicloud-titanium_cloud/v0/CloudOwner2_RegionOne/identity/v2.0")
   2, This identify-url are populated by multicloud plugin during 
the VIM/Cloud instance on boarding procedure. So it is possible that different 
cloud region are populated with different multicloud NBI endpoint.
   3, Idealy, the VIM/Cloud instance on boarding procedure are 
triggered from and excuted in the context of  respectively ONAP instance, so 
for those edge cloud orchestrated by edge ONAP will be on boarded via the edge 
ONAP ESR portal/API. In this case the multicloud plugin instance within the 
same ONAP instance will provision the cloud region with the  consistent 
endpoints , I mean , with the same service ip :port . But the muticloud plugin 
instance from different ONAP instance will provision cloud region with 
different endpoint (I mean, different service ip: port)

Does that make sense? Please let me know what you think of that.
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 Addepalli, Srinivasa R
Sent: Wednesday, June 13, 2018 3:29 AM
To: MORALES RUVALCABA, VICTOR; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [coe] Team meeting Agenda

Hi Victor and Shashank,

There were few questions from Multi-Cloud meeting yesterday (Shankar and 
others).  It would be good if we could cover following also today


-K8S plugin needs to have access to information that connect to K8S 
masters in the remote edge-clouds/sites.  Normal practice for K8S client is to 
read kubeconfig file  that has connectivity information for each cluster and 
certificate/private key to be used to communicate with remote site K8S master.  
In ONAP, we have ESR. Are we going to use ESR or K8S plugin provides its own 
way to upload kubeconfig information.  If so, how does get stored in A Is 
there any schema change required?

-K8S plugin at the run time will use same deployment template files 
multiple times.  But, each deployment instance needs to be uniquely identified. 
Normally, ObjectMeta.Name is used to uniquely identify each deployment.  I 
guess it means that K8S plugin needs to generate this name dynamically to make 
it unique.  One way to do this is to create UUID, concatenate with Name field 
of deployment template (artifact) and store the UUID in the A on per VNF 
basis.  Does this require any A schema changes?  When Delete/Update/Query 
VNF is called at later time, it is expected that concatenated name is passed by 
SO (test SO in this case). Let us discuss this too today.

Thanks
Srini


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Morales, Victor
Sent: Tuesday, June 12, 2018 8:47 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [coe] Team meeting Agenda

Hey there,

These are the topics that I’d like to talk about today


•Project status

•API Definition Discussion

•Opens

But I want to check first if someone has an additional topic that needs to 
discussed.

Regards,
Victor Morales
___
onap-discuss mailing list

Re: [onap-discuss] Container Based VNF's and Orchestration

[Naresh Babu]

Hi Srini,

I am located in Chennai city ,India and as per Indian Time the Meeting
happening on Wednesday Early morning 1.30 AM IST.I will join in next week
call and will try and ensure to join in the weekly calls.I am looking
forward to work on this project and to ONAP community.

Thanks
Naresh Babu.S

On 12 Jun 2018 23:02, "Addepalli, Srinivasa R" <
srinivasa.r.addepa...@intel.com> wrote:

We have regular 1:00PM PST meetings on every Tuesday.  I am not sure where
you are located. If you could join, that would be great.



Thanks

Srini





*From:* Naresh Babu [mailto:mailbox.nareshb...@gmail.com]
*Sent:* Tuesday, June 12, 2018 10:22 AM
*To:* Addepalli, Srinivasa R 
*Cc:* onap-discuss@lists.onap.org
*Subject:* RE: [onap-discuss] Container Based VNF's and Orchestration



Hi Srinivasa,

I am interested to be a contributor for this project. Thank you.

Thanks
Naresh Babu.S



On 12 Jun 2018 22:37, "Addepalli, Srinivasa R"  wrote:

We started a new initiative to support K8S based edge-clouds and CaaS
providers (R3+ in case of CaaS).



This is the page where you can find more information.



https://wiki.onap.org/display/DW/Support+for+K8S+%
28Kubernetes%29+based+Cloud+regions



We will be happy to have more contributors for this project.  Let us know
if you want to be a contributor.



Thanks

Srini





*From:* onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-bounces@
lists.onap.org] *On Behalf Of *Naresh Babu
*Sent:* Tuesday, June 12, 2018 9:57 AM
*To:* onap-discuss@lists.onap.org
*Subject:* [onap-discuss] Container Based VNF's and Orchestration



Hi Team,



I really appreciate the team efforts for bringing ONAP as one of the best
orchestration tool for SDN and NFV.I just need to provide my thoughts and
inputs further on NFV.Like Most of the VNF's applications are deployed
under Virtual machines normally it take up a lot of system resources. Each
VM runs not just a full copy of an operating system, but a virtual copy of
all the hardware that the operating system needs to run. This quickly adds
up to a lot of RAM and CPU's.To improve the NFV application performance
,microservices and VNF's can be deployed in containers which we can
achieve  the continuous delivery of VNF critical applications.

This allows for each service upgradation and versioning separately as
opposed to upgrading the entire VNF in a virtual machine. While upgrading a
whole application or VNF, the container determines which individual
services have changed and deploys only those specific services.We can use
Kubernets for managing Containered VNF's and integrate SDN controller
Opencontrail (Now it is called as tungsten Fabric opensource controller)
for better networking ,slicing,Isolation and improved security and we can
use tosca yaml templates for Docker as well.Containers going to play huge
role in futute NFV and 5G and  we need to start look in to it for Container
based VNF's developing and deployment with orchestration and closed loop
automation as well.I am Just sharing my thoughts and inputs on this.Thank
you !



Thanks
Naresh Babu S
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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

[Yunxia Chen]

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.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [coe] Team meeting Agenda

[Morales, Victor]

Hey there,

@Bin, I have a question about using the ESR VIM registration portal. According 
to the wiki using this method will trigger a discovery process. I’m wondering 
if we have to create an endpoint for this, maybe it’s something that we can 
include into the API definition and implement it later.

@Srini regarding your questions, for this PoC we have only considered the 
scenario for consuming the ./kube/config[1] file. In the other hand, I noticed 
that’s possible to configure Kubernetes to use Basic Authentication method [2] 
which can do something similar than OpenStack.  Lastly, regarding the 
concatenation I have the impression that what Kubernetes is doing internally is 
quite enough to guarantee its uniqueness, but we can include it as a functional 
test to cover that scenario.

Regards,
Victor Morales

[1] https://github.com/electrocucaracha/krd/blob/master/installer#L97
[2] 
https://github.com/electrocucaracha/krd/blob/master/inventory/group_vars/k8s-cluster.yml#L69


From: "HU, BIN" 
Date: Tuesday, June 12, 2018 at 1:04 PM
To: "Addepalli, Srinivasa R" , Victor Morales 
, "onap-discuss@lists.onap.org" 

Subject: RE: [coe] Team meeting Agenda

Refer to the wiki page: 
https://wiki.onap.org/pages/viewpage.action?pageId=25431491 (How-To: Register a 
VIM/Cloud Instance to 
ONAP).

In this guide, when registering a new VIM, we need to:

-  Create Complex object in A

-  Register VIM/Cloud instance in A

-  And some other steps

When registering VIM/Cloud instance in A, one can use curl command to create 
a cloud region object in A This Cloud Region Object contains a 
“esr-system-info-list” which includes “username” and “password” for keystone 
authentication.

Because this schema is OpenStack-centric, we may have 2 options:

-  Reuse “password” property, and store kubeconfig information within 
this “password” property

-  Or expand the “esr-system-info-list” with a new property for 
kubeconfig information.

Hope it helps
Thanks
Bin

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Addepalli, Srinivasa R
Sent: Tuesday, June 12, 2018 12:29 PM
To: Morales, Victor ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [coe] Team meeting Agenda

Hi Victor and Shashank,

There were few questions from Multi-Cloud meeting yesterday (Shankar and 
others).  It would be good if we could cover following also today


-  K8S plugin needs to have access to information that connect to K8S 
masters in the remote edge-clouds/sites.  Normal practice for K8S client is to 
read kubeconfig file  that has connectivity information for each cluster and 
certificate/private key to be used to communicate with remote site K8S master.  
In ONAP, we have ESR. Are we going to use ESR or K8S plugin provides its own 
way to upload kubeconfig information.  If so, how does get stored in A Is 
there any schema change required?

-  K8S plugin at the run time will use same deployment template files 
multiple times.  But, each deployment instance needs to be uniquely identified. 
Normally, ObjectMeta.Name is used to uniquely identify each deployment.  I 
guess it means that K8S plugin needs to generate this name dynamically to make 
it unique.  One way to do this is to create UUID, concatenate with Name field 
of deployment template (artifact) and store the UUID in the A on per VNF 
basis.  Does this require any A schema changes?  When Delete/Update/Query 
VNF is called at later time, it is expected that concatenated name is passed by 
SO (test SO in this case). Let us discuss this too today.

Thanks
Srini


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Morales, Victor
Sent: Tuesday, June 12, 2018 8:47 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [coe] Team meeting Agenda

Hey there,

These are the topics that I’d like to talk about today


· Project status

· API Definition Discussion

· Opens

But I want to check first if someone has an additional topic that needs to 
discussed.

Regards,
Victor Morales
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] 答复：Re: 答复：[dcae] dcae-cli Installation Failure

[VENKATESH KUMAR, VIJAY]

HI Suraj, It was not part of Amsterdam, DCAE-DS was included in Beijing 
release. I’ve copied Michael from SDC team who can give more info.

However DCAE-DS was not used for model/blueprint generation in R2 (component 
blueprints were created manually). For R3, current plans are to onboard the 
DCAE MS through SDC/DS.

Thanks,
Vijay

From: Bisht, Suraj (Nokia - US/Irving) 
Sent: Tuesday, June 12, 2018 12:42 PM
To: VENKATESH KUMAR, VIJAY ; HWANG, MICHAEL 
; fu.guangr...@zte.com.cn; JI, LUSHENG 

Cc: peng.congc...@zte.com.cn; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] 答复：Re: 答复：[dcae] dcae-cli Installation Failure

Hi Vijay, Mike

Is DCAE-DS tool available in Amsterdam release? I can’t find any link in SDC 
GUI to access DCAE-DS tool kindly clarify how to access DCAE-DS, is there any 
specific ONAP component IP/link need to be used?
Some background for our use case
We are trying to create a micro service/application in DCAE to 
Publish/Subscribe particular events through new application.

Thanks,
Suraj

From: VENKATESH KUMAR, VIJAY [mailto:vv7...@att.com]
Sent: Friday, June 08, 2018 1:34 PM
To: HWANG, MICHAEL mailto:mhw...@research.att.com>>; 
Bisht, Suraj (Nokia - US/Irving) 
mailto:suraj.bi...@nokia.com>>; 
fu.guangr...@zte.com.cn; JI, LUSHENG 
mailto:l...@research.att.com>>
Cc: peng.congc...@zte.com.cn; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] 答复：Re: 答复：[dcae] dcae-cli Installation Failure

The component spec example of VES collector is available on the same 
wiki

The ToscaLab tool used for model generations are supported by DCAE-DS under SDC 
project (updated the onboarding sequence flow which had an older version).

Thanks,
Vijay

From: HWANG, MICHAEL
Sent: Friday, June 08, 2018 10:05 AM
To: Bisht, Suraj (Nokia - US/Irving) 
mailto:suraj.bi...@nokia.com>>; 
fu.guangr...@zte.com.cn; JI, LUSHENG 
mailto:l...@research.att.com>>
Cc: peng.congc...@zte.com.cn; 
onap-discuss@lists.onap.org; VENKATESH 
KUMAR, VIJAY mailto:vv7...@att.com>>
Subject: Re: [onap-discuss] 答复：Re: 答复：[dcae] dcae-cli Installation Failure

+Vijay

The dcae_cli tool does not generate csar packages.  It is intended that the 
dcae_cli tool should generate tosca models which are to be used by the dcae 
design studio which is in sdc.  Currently this tosca model generation is a 
separate step.

Regarding self service of tosca model generation, @Lusheng who can help him 
with the tooling?

Regarding samples, one of the features of the dcae onboarding experience is to 
provide a shared catalog of components so that developers can share and browse. 
 However, this sort of environment is not being hosted right now.  @Vijay could 
you provide the ves's component spec as a sample?
On 06/04/2018 05:36 PM, Bisht, Suraj (Nokia - US/Irving) wrote:
Hi Mike,

Thanks for your response,
I was going through following link
https://wiki.onap.org/display/DW/MicroServices+Onboarding

and I got impression that dcae_cli tool will be used to generate csar package 
which can be used in SDC during DCAE component design, is this not the case?

Can you guide me how to create SDC compliant template to create DCAE component 
if I have data-formats and component-spec json files?
If possible kindly share one sample to verify DCAE micro service component 
deployment.

Thanks,
Suraj

From: Michael Hwang [mailto:mhw...@research.att.com]
Sent: Monday, June 04, 2018 4:24 PM
To: Bisht, Suraj (Nokia - US/Irving) 
; 
fu.guangr...@zte.com.cn; 
l...@research.att.com
Cc: peng.congc...@zte.com.cn; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] 答复：Re: 答复：[dcae] dcae-cli Installation Failure

Hi Suraj

> a)   Is dcae_cli postgress database for catalog a separate database, can 
> we use existing database from other ONAP components (i.e. SDC)?

Yes the dcae_cli postgres is a separate database.  You could share a common 
postgres instance but would have to have been initialized with the dcae_cli 
tables.

> b)Is dcae CLI an offline tool, can it be install and used independently 
> from DCAE/ONAP 

Re: [onap-discuss] [E] TOSCA on Kubernetes: Puccini

[Kumar Skand Priya, Viswanath V via onap-discuss]

Hi Tal,

I had a glance of puccini and am yet to explore more by getting my hands
dirty. But then I have following questions, based on my glance.

   - As you had rightly mentioned in your AriaTosca message in mailinglist,
   ONAP has already got handful of parsers, including very own aria and it is
   not fully integrated with SO yet ( please correct me if I'm wrong ). What
   unique advantages would puccini bring, apart from being yet another, fresh,
   tosca 1.1 compliant, standalone, golang-js-based parser ? I'm not debating
   the arguments that you made on the aria-mailing list, am just trying to
   understand your argument on how it could benefit ONAP in particular?
   - Since today, SO is predominantly BPMN driven, how much effort does it
   take to come up with BPMN backend ? Is it feasible ?
   - IMHO Kubern8s space is already (kinda) standardized and deployment of
   ONAP components may not need another language. Personally I am interested
   to know if puccini would ease the job of parsing SOL 001 compliant NSDs &
   VNFDs and seamlessly translate to ONAP specific workflows ( BPMN, DAGs etc
   ) with minimum efforts.

Looking forward to your talk at Beijing summit.

BR,
Viswa




Viswanath Kumar Skand Priya
Architect
Technology, Architecture & Planning


On Tue, Jun 12, 2018 at 10:42 PM, Tal Liron  wrote:

> Hi folks,
>
> I'm happy to finally reveal a project I've been working on for a few
> months:
>
> https://github.com/tliron/puccini
> 
>
> The gist of Puccini:
>
> 1) Very fast and full-featured stateless TOSCA compiler
> 2) Targets Kubernetes directly (more targets to come)
> 3) Finally introduces an "intermediary format" for TOSCA, called "Clout"
>
> For ONAP, I humbly suggest that it could provide 1) a way to deploy
> containerized VNFs while staying entirely in TOSCA and CSAR, and 2) a
> possible alternative to Helm in order to minimize the number of modeling
> languages in the project. Or neither! This is not an official proposal,
> just the beginning of a discussion that with hopefully expand our
> imagination on ways to solve some thorny architectural problems.
>
> I'll be presenting it in Beijing next week, but will be happy to answer
> questions here, too.
>
> Also, to be clear: this is *not* an official or endorsed Red Hat project.
>
> For a comparison with AriaTosca, see this message
> 
> .
>
> ___
> 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=
> MJRff2sguAcB41OPSRvEKIOauXFg2qB1GXlB6-k40Yg=gsMHRQj-
> oDHwMcitvir9lRjevH7VUwkUECsh5qCiSeQ=
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] MSB - DCAE/VESCollector

[VENKATESH KUMAR, VIJAY]

Hi William,  The VEScollector is also exposed via Nodeport (30235 by default). 
You can configure the PNF to send events into  :30235/eventListener/v5.

Regards,
Vijay
From: onap-discuss-boun...@lists.onap.org  
On Behalf Of William Kurkian
Sent: Tuesday, June 12, 2018 2:51 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] MSB - DCAE/VESCollector

Hello,

Does anyone know how devices external to ONAP, such as a PNF, should access the 
VES Collector in a Kubernetes installation?

One thing I looked at was querying the MSB, but it did not have the VES 
collector listed, at least in my current installation. I am a few weeks behind, 
so I don't know if it has been added since.

Thanks,
William Kurkian
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [modeling] Papyrus Training Session

[jessie jewitt]

Sorry for the continued confusion about the bridge.
We will be using Kevin's bridge:

https://zoom.us/j/746737796
Thank you,
Jessie

On Mon, Jun 4, 2018 at 6:13 PM, jessie jewitt <
jessie.jew...@oamtechnologies.com> wrote:

> The VNFSDK Modeling team is hosting a Papyrus training session on
> Wednesday, June 13th at 6am Pacific / 9am Eastern / 9pm China time
> This session will cover:
>
> 1. How to install Papyrus
> 2. The value of using a modeling tool such as Papyrus within ONAP
> 3. How to use Papyrus alongside the wiki.
>
>
> We will be using Kevin's bridge:
> https://connect2.uc.att.com/attinc/meet/?ExEventID=81618271=M
>
> Please plan on attending.
> -Jessie
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [APP-C][CDT] - What is the expected payload for ANSIBLE?

[CHO, TAKAMUNE]

Hi Alexis,

Correct. Here are the right contents:

[cid:image001.jpg@01D40267.5CE8E180]

Taka

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, June 12, 2018 2:28 PM
To: CHO, TAKAMUNE 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [APP-C][CDT] - What is the expected payload for 
ANSIBLE?

Sorry if this is going in many direction. I just confirm that the change I’ve 
made to the GENERATE_CONFIG_DG column is not required, this can remain NULL 
instead of Generic_AnsibleDG.


On Jun 12, 2018, at 2:15 PM, Alexis de Talhouët 
mailto:adetalhoue...@gmail.com>> wrote:

Actually, I also tweaked to DB tables, to have GENERATE_CONFIG_DG be 
Generic_AnsibleDG and DOWNLOAD_CONFIG_DG be ansible-adapter-1.0

In sdnctl.CONFIGURE_ACTION_DG

| CONFIGURE_ACTION_DG_ID | VNF_TYPE   | ACTION| GENERATE_CONFIG_DG | 
DOWNLOAD_CONFIG_DG  |
|   19 | vlns/vmx 0| 
ConfigModify | Generic_AnsibleDG  | ansible-adapter-1.0   |


And in sdnctl.DOWNLOAD_DG_REFERENCE

| DOWNLOAD_DG_REFERENCE_ID | PROTOCOL| DOWNLOAD_CONFIG_DG  |
| 2 | ANSIBLE | 
ansible-adapter-1.0 |

Is this necessary?


On Jun 12, 2018, at 1:39 PM, Alexis de Talhouët 
mailto:adetalhoue...@gmail.com>> wrote:

Taka,

Thanks for the answer. I was able to call my ansible playbook after doing the 
following:

1. Add the XYZ.ANSIBLE.ConfigModify.url = 
http://172.19.22.13:1234/Dispatch
 in /opt/appc/data/properties/appc_southbound.properties
2. Define a template with the following payload: {"PlaybookName": "$playbook}”}
3. Send the LCM RPC request using this payload:

"payload": 
"{\"configuration-parameters\":{\"operations_timeout\":\"3600\",\"playbook\":\"playbook1\"}}"


Question, is there a way to pass the agent url as argument of the LCM RPC input 
in some ways? Like we do for NETCONF configure action with vnf-host-ip-address?


Thanks,
Alexis

On Jun 12, 2018, at 12:04 PM, CHO, TAKAMUNE 
mailto:tc0...@att.com>> wrote:

Hi Alexis,

The payload for ConfigModify that you used is not correct.  AgentUrl has to be 
present in Device Authentication Table rather than in the Payload. Below is one 
sample:

"payload": 
"{\"request-parameters\":{\"vnf-name\":\"xxx\",\"vnf-host-ip-address\":\"https://xx.xxx.xx.xx:5000/Dispatch\"},\"configuration-parameters\":{\"vnf_name\":\”XYZ\",\"operations_timeout\":\"3600\"}}"

To Answer your next question for CDT’s PD. Here is the sample for PD:

kind: "Property Definition"
version: V1
vnf-parameter-list:
- name: vnf_name
  type: null
  description: null
  required: null
  default: null
  source: Manual
  rule-type: null
  request-keys: null
response-keys: null

and one payload for Anisble:

{
  "PlaybookName": "comx/latest/ansible/modify/site.yml",
  "EnvParameters": {"vnf_instance": "${vnf_name}"},
  "Timeout": 3600
}

-Taka

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Monday, June 11, 2018 4:56 PM
To: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] [APP-C][CDT] - What is the expected payload for ANSIBLE?

Greetings team,

I’m trying to use the ConfigModify action using the ANSIBLE “device protocol” 
within CDT.
I’m trying to execute my REST API from Postman to APP-C. I’m using the bellow 
payload.
I cannot get around this error:
org.onap.ccsdk.sli.core.sli.SvcLogicException: Error constructing request for 
execution of playbook due to missing mandatory parameters. Reason = Ansible: 
Mandatory AnsibleAdapter key AgentUrl not found in parameters provided by 
calling agent !

I do see AnsibleMessageParser#reqMessage is enforcing few parameters, final 
String[] mandatoryTestParams = {AGENT_URL_KEY,PLAYBOOK_NAME_KEY, USER_KEY, 
PASS_KEY};
but I don’t know how to input them...

Can you help me understand what’s the expected payload for this REST API?

On another note, what is the expected template and parameter definition when 
using Ansible within CDT?

Thanks,
Alexis

{
"input": {
"common-header": {
"timestamp": "2018-06-11T17:42:14.227Z",
"api-ver": "2.00",
"originator-id": "ALEX",
"request-id": "TEST-6",
"sub-request-id": 

[onap-discuss] Seeking LFN Booth Demo Ideas for ONS Europe: ONAP

[Brandon Wick]

Hello ONAP Community:

Those in attendance at OSN North America in Los Angeles last March will
recall that we hosted an *LF Networking Booth* that showcased 8
compelling, community-driven
demos from the LFN technical projects. See this blog post

 for a description of the ONS North America booth demos, their focus areas,
and how they fit together.

We wanted to reach out now to each of the LFN project communities to let
you know that there will be space for ~8 networking demos inside the LFN
booth again at ONS Europe

 (Sept 25-27, Amsterdam) and we are seeking demo ideas again using the same
process as last time. Our goal again is to show compelling uses of LFN
networking project technology to solve real world industry challenges.
Demos that show cross-project elements (e.g. between LFN projects and
others), that map to a specific industry use case, and that are endorsed by
a service provider are preferred. That said, we have some room for demos
that highlight the good work and value-add from projects that don't
necessarily meet these criteria. At least one demo slot will be made
available for each LFN project that submits a quality idea.

Another LFN Booth demo option we're exploring is to feature the PNDA project
  analyzing data from other open source projects (e.g.
ONAP). If we went this direction, it would require participation and
coordination with the PNDA team for demo development and execution. If you
have been working on PNDA integration and are interested in pursuing this
idea, please contact Nick Hall: nich...@cisco.com.

Demos stations will again have storage space, a counter, backdrop, monitor,
power, and Wi-Fi internet provided. A demo station mock up is now under
development and will be shared back with interested parties. There is no
cost to host a demo in the LFN booth although additional power, internet,
spaces, etc. may incur a cost.

Here are the key dates to keep in mind:

   - June 12: Demo idea solicitation email sent to community lists
   - July 9: Demo ideas submissions due
   - July 20: Demos ideas reviewed, chosen, and notifications sent

To submit your demo idea for consideration, please collect and provide the
following information:

   - Demo title (10 words max)
   - Brief demo description (200 words max)
   - List of demo manager(s) with contact information
   - List of open source projects involved
   - List of companies involved
   - Any extra requirements or special considerations

Demo manager responsibilities include:

   - Creating the demo concept and actual demo to be shown
   - Responding promptly to requests for information
   - Meeting all demo prep deadlines
   - Setting up and testing the demo pre-show and taking down post-show
   - Staffing the demo during ONS expo hours (along with other designated
   team members to help share the load)
   - Being willing to participate in media activities, e.g. photos, videos

ONS sponsor companies are of course welcome to host demos in their booths
on the show floor as well. Please heck with your ONS Europe sponsorship
managers to explore these opportunities.

*Submit your demo ideas by July 9 by sending an email
to bw...@linuxfoundation.org *. LFN staff
leadership (Heather, Phil, Arpit) will then review the submissions, get
back to submitters with questions, suggestions, and recommend a final demo
roster by July 20th. Send any questions you may have to
bw...@linuxfoundation.org.

We look forward to seeing your demo ideas.

Best,

Brandon Wick
Senior Integrated Marketing Manager
The Linux Foundation
bw...@linuxfoundation.org
+1.917.282.0960
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] ELK stack deployment for onap Amsterdam

[Michael O'Brien]

Urwashi,
   Hi, the Amsterdam repo is essentially deprecated and has an elk stack under 
the log pod – all deployment code is in the oom repo as usual.
https://git.onap.org/oom/tree/kubernetes/log?h=amsterdam
use the following script to bring up the system old or new.
https://git.onap.org/logging-analytics/tree/deploy/cd.sh

   I would advise using Beijing or master as a lot of changes/fixes have went 
in since Amsterdam – including the full containerization of DCAE from the 
hybrid deployment of amsterdam.
An example of a recent project that implemented the current filebeat (the 
filebeat/logstash architecture will likely be modified in Casablanca) config is 
CLAMP

https://git.onap.org/oom/tree/kubernetes/clamp
https://jira.onap.org/browse/CLAMP-170
https://gerrit.onap.org/r/#/c/48961/
https://wiki.onap.org/display/DW/Logging+User+Guide

/michael



From: Urwashi Saraswat
Sent: Tuesday, June 12, 2018 2:12 PM
To: Michael O'Brien 
Cc: onap-discuss@lists.onap.org
Subject: ELK stack deployment for onap Amsterdam

HI Michael,
Do you have deployment for ELK stack in onap Amsterdam  which has new filebeat 
configuration. ? This is regarding the  onap logging project

Thanks
Urwashi
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

[onap-discuss] [integration] Integration Weekly Meeting Time Poll

[Yunxia Chen]

Dear ONAP Integration Members,

As we have discussed in this morning’s weekly meeting, we’d like to move our 
weekly meeting to a new time slot to avoid the conflicts with other two 
meetings Integration team wants to attend, architect and use cases. Below is a 
suggested new timeslot:


· Wed UTC 14:00 / China 22:00 / Eastern 10:00 / Pacific 07:00

· Mon UTC 15:00 / China 23:00 / Eastern 11:00 / Pacific 08:00

· Wed UTC 15:00 / China 23:00 / Eastern 11:00 / Pacific 08:00

Please select the options working for you from the following poll:
https://doodle.com/poll/fuspdctxbd22rgfb
Poll will end at this Friday, 6/15/2018, 6:00PDT.

Thank you!
Helen Chen
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] MSB - DCAE/VESCollector

[William Kurkian]

Hello,

Does anyone know how devices external to ONAP, such as a PNF, should access
the VES Collector in a Kubernetes installation?

One thing I looked at was querying the MSB, but it did not have the VES
collector listed, at least in my current installation. I am a few weeks
behind, so I don't know if it has been added since.

Thanks,
William Kurkian
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [APP-C][CDT] - What is the expected payload for ANSIBLE?

[Alexis de Talhouët]

Sorry if this is going in many direction. I just confirm that the change I’ve 
made to the GENERATE_CONFIG_DG column is not required, this can remain NULL 
instead of Generic_AnsibleDG.

> On Jun 12, 2018, at 2:15 PM, Alexis de Talhouët  
> wrote:
> 
> Actually, I also tweaked to DB tables, to have GENERATE_CONFIG_DG be 
> Generic_AnsibleDG and DOWNLOAD_CONFIG_DG be ansible-adapter-1.0
> 
> In sdnctl.CONFIGURE_ACTION_DG
> 
> | CONFIGURE_ACTION_DG_ID | VNF_TYPE   | ACTION| GENERATE_CONFIG_DG | 
> DOWNLOAD_CONFIG_DG  |
> |   19 | vlns/vmx 0| 
> ConfigModify | Generic_AnsibleDG  | ansible-adapter-1.0   |
> 
> 
> And in sdnctl.DOWNLOAD_DG_REFERENCE
> 
> | DOWNLOAD_DG_REFERENCE_ID | PROTOCOL| DOWNLOAD_CONFIG_DG  |
> | 2 | ANSIBLE 
> | ansible-adapter-1.0 |
> 
> Is this necessary?
> 
>> On Jun 12, 2018, at 1:39 PM, Alexis de Talhouët > > wrote:
>> 
>> Taka,
>> 
>> Thanks for the answer. I was able to call my ansible playbook after doing 
>> the following:
>> 
>> 1. Add the XYZ.ANSIBLE.ConfigModify.url = http://172.19.22.13:1234/Dispatch 
>>  in 
>> /opt/appc/data/properties/appc_southbound.properties
>> 2. Define a template with the following payload: {"PlaybookName": 
>> "$playbook}”}
>> 3. Send the LCM RPC request using this payload:
>> 
>> "payload": 
>> "{\"configuration-parameters\":{\"operations_timeout\":\"3600\",\"playbook\":\"playbook1\"}}"
>> 
>> 
>> Question, is there a way to pass the agent url as argument of the LCM RPC 
>> input in some ways? Like we do for NETCONF configure action with 
>> vnf-host-ip-address?
>> 
>> 
>> Thanks,
>> Alexis
>> 
>>> On Jun 12, 2018, at 12:04 PM, CHO, TAKAMUNE >> > wrote:
>>> 
>>> Hi Alexis,
>>>  
>>> The payload for ConfigModify that you used is not correct.  AgentUrl has to 
>>> be present in Device Authentication Table rather than in the Payload. Below 
>>> is one sample:
>>>  
>>> "payload": 
>>> "{\"request-parameters\":{\"vnf-name\":\"xxx\",\"vnf-host-ip-address\":\"https://xx.xxx.xx.xx:5000/Dispatch\"},\"configuration-parameters\":{\"vnf_name\":\”XYZ\",\"operations_timeout\":\"3600\
>>>  
>>> "}}"
>>>  
>>> To Answer your next question for CDT’s PD. Here is the sample for PD:
>>>  
>>> kind: "Property Definition"
>>> version: V1
>>> vnf-parameter-list:
>>> - name: vnf_name
>>>   type: null
>>>   description: null
>>>   required: null
>>>   default: null
>>>   source: Manual
>>>   rule-type: null
>>>   request-keys: null
>>> response-keys: null
>>>  
>>> and one payload for Anisble:
>>>  
>>> {
>>>   "PlaybookName": "comx/latest/ansible/modify/site.yml",
>>>   "EnvParameters": {"vnf_instance": "${vnf_name}"},
>>>   "Timeout": 3600
>>> }
>>>  
>>> -Taka
>>>  
>>> From: onap-discuss-boun...@lists.onap.org 
>>>  
>>> [mailto:onap-discuss-boun...@lists.onap.org 
>>> ] On Behalf Of Alexis de 
>>> Talhouët
>>> Sent: Monday, June 11, 2018 4:56 PM
>>> To: onap-discuss >> >
>>> Subject: [onap-discuss] [APP-C][CDT] - What is the expected payload for 
>>> ANSIBLE?
>>>  
>>> Greetings team,
>>>  
>>> I’m trying to use the ConfigModify action using the ANSIBLE “device 
>>> protocol” within CDT.
>>> I’m trying to execute my REST API from Postman to APP-C. I’m using the 
>>> bellow payload.
>>> I cannot get around this error: 
>>> org.onap.ccsdk.sli.core.sli.SvcLogicException: Error constructing request 
>>> for execution of playbook due to missing mandatory parameters. Reason = 
>>> Ansible: Mandatory AnsibleAdapter key AgentUrl not found in parameters 
>>> provided by calling agent !
>>>  
>>> I do see AnsibleMessageParser#reqMessage is enforcing few parameters, final 
>>> String[] mandatoryTestParams = {AGENT_URL_KEY,PLAYBOOK_NAME_KEY, USER_KEY, 
>>> PASS_KEY};
>>> but I don’t know how to input them...
>>>  
>>> Can you help me understand what’s the expected payload for this REST API? 
>>>  
>>> On another note, what is the expected template and parameter definition 
>>> when using Ansible within CDT?
>>>  
>>> Thanks,
>>> Alexis
>>>  
>>> {
>>> "input": {
>>> "common-header": {
>>> "timestamp": "2018-06-11T17:42:14.227Z",
>>> "api-ver": "2.00",
>>> "originator-id": "ALEX",
>>> "request-id": "TEST-6",
>>> "sub-request-id": "TEST-2",
>>> "flags": {
>>> "force": "TRUE",
>>> "ttl": 12000
>>> }
>>> },
>>> "action": "ConfigModify",
>>> "action-identifiers": {
>>> "vnf-id": 

Re: [onap-discuss] [APP-C][CDT] - What is the expected payload for ANSIBLE?

[Alexis de Talhouët]

I’d like to avoid having to hardcode the agent url in the appc config file. I 
see you pass it as param here, is it because I changed the GENERATE_CONFIG_DG 
to Generic_AnsibleDG that I have to provide it in the config?

"payload": 
"{\"request-parameters\":{\"vnf-name\":\"xxx\",\"vnf-host-ip-address\":\"https://xx.xxx.xx.xx:5000/Dispatch\"},\"configuration-parameters\":{\"vnf_name\":\”XYZ\",\"operations_timeout\":\"3600\
 
"}}"


I’m going to try.
Thanks,
Alexis

> On Jun 12, 2018, at 2:07 PM, CHO, TAKAMUNE  wrote:
> 
> HI Alexis,
>  
> Just like to clarify you question:
>  
> You want to pass the agenturl as an argument in an ansible payload?
>  
> Taka
>  
> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 
> Sent: Tuesday, June 12, 2018 1:40 PM
> To: CHO, TAKAMUNE 
> Cc: onap-discuss 
> Subject: Re: [onap-discuss] [APP-C][CDT] - What is the expected payload for 
> ANSIBLE?
>  
> Taka,
>  
> Thanks for the answer. I was able to call my ansible playbook after doing the 
> following:
>  
> 1. Add the XYZ.ANSIBLE.ConfigModify.url = http://172.19.22.13:1234/Dispatch 
> 
>  in /opt/appc/data/properties/appc_southbound.properties
> 2. Define a template with the following payload: {"PlaybookName": 
> "$playbook}”}
> 3. Send the LCM RPC request using this payload:
>  
> "payload": 
> "{\"configuration-parameters\":{\"operations_timeout\":\"3600\",\"playbook\":\"playbook1\"}}"
>  
>  
> Question, is there a way to pass the agent url as argument of the LCM RPC 
> input in some ways? Like we do for NETCONF configure action with 
> vnf-host-ip-address?
>  
>  
> Thanks,
> Alexis
>  
> On Jun 12, 2018, at 12:04 PM, CHO, TAKAMUNE  > wrote:
>  
> Hi Alexis,
>  
> The payload for ConfigModify that you used is not correct.  AgentUrl has to 
> be present in Device Authentication Table rather than in the Payload. Below 
> is one sample:
>  
> "payload": 
> "{\"request-parameters\":{\"vnf-name\":\"xxx\",\"vnf-host-ip-address\":\"https://xx.xxx.xx.xx:5000/Dispatch\"},\"configuration-parameters\":{\"vnf_name\":\”XYZ\",\"operations_timeout\":\"3600\
>  
> "}}"
>  
> To Answer your next question for CDT’s PD. Here is the sample for PD:
>  
> kind: "Property Definition"
> version: V1
> vnf-parameter-list:
> - name: vnf_name
>   type: null
>   description: null
>   required: null
>   default: null
>   source: Manual
>   rule-type: null
>   request-keys: null
> response-keys: null
>  
> and one payload for Anisble:
>  
> {
>   "PlaybookName": "comx/latest/ansible/modify/site.yml",
>   "EnvParameters": {"vnf_instance": "${vnf_name}"},
>   "Timeout": 3600
> }
>  
> -Taka
>  
> From: onap-discuss-boun...@lists.onap.org 
>  
> [mailto:onap-discuss-boun...@lists.onap.org 
> ] On Behalf Of Alexis de Talhouët
> Sent: Monday, June 11, 2018 4:56 PM
> To: onap-discuss  >
> Subject: [onap-discuss] [APP-C][CDT] - What is the expected payload for 
> ANSIBLE?
>  
> Greetings team,
>  
> I’m trying to use the ConfigModify action using the ANSIBLE “device protocol” 
> within CDT.
> I’m trying to execute my REST API from Postman to APP-C. I’m using the bellow 
> payload.
> I cannot get around this error: 
> org.onap.ccsdk.sli.core.sli.SvcLogicException: Error constructing request for 
> execution of playbook due to missing mandatory parameters. Reason = Ansible: 
> Mandatory AnsibleAdapter key AgentUrl not found in parameters provided by 
> calling agent !
>  
> I do see AnsibleMessageParser#reqMessage is enforcing few parameters, final 
> String[] mandatoryTestParams = {AGENT_URL_KEY,PLAYBOOK_NAME_KEY, USER_KEY, 
> PASS_KEY};
> but I don’t know how to input them...
>  
> Can you help me understand what’s the expected payload for this REST API? 
>  
> On another note, what is the expected template and parameter definition when 
> using Ansible within CDT?
>  
> Thanks,
> 

Re: [onap-discuss] [APP-C][CDT] - What is the expected payload for ANSIBLE?

[Alexis de Talhouët]

Actually, I also tweaked to DB tables, to have GENERATE_CONFIG_DG be 
Generic_AnsibleDG and DOWNLOAD_CONFIG_DG be ansible-adapter-1.0

In sdnctl.CONFIGURE_ACTION_DG

| CONFIGURE_ACTION_DG_ID | VNF_TYPE   | ACTION| GENERATE_CONFIG_DG | 
DOWNLOAD_CONFIG_DG  |
|   19 | vlns/vmx 0| 
ConfigModify | Generic_AnsibleDG  | ansible-adapter-1.0   |


And in sdnctl.DOWNLOAD_DG_REFERENCE

| DOWNLOAD_DG_REFERENCE_ID | PROTOCOL| DOWNLOAD_CONFIG_DG  |
| 2 | ANSIBLE | 
ansible-adapter-1.0 |

Is this necessary?

> On Jun 12, 2018, at 1:39 PM, Alexis de Talhouët  
> wrote:
> 
> Taka,
> 
> Thanks for the answer. I was able to call my ansible playbook after doing the 
> following:
> 
> 1. Add the XYZ.ANSIBLE.ConfigModify.url = http://172.19.22.13:1234/Dispatch 
>  in 
> /opt/appc/data/properties/appc_southbound.properties
> 2. Define a template with the following payload: {"PlaybookName": 
> "$playbook}”}
> 3. Send the LCM RPC request using this payload:
> 
> "payload": 
> "{\"configuration-parameters\":{\"operations_timeout\":\"3600\",\"playbook\":\"playbook1\"}}"
> 
> 
> Question, is there a way to pass the agent url as argument of the LCM RPC 
> input in some ways? Like we do for NETCONF configure action with 
> vnf-host-ip-address?
> 
> 
> Thanks,
> Alexis
> 
>> On Jun 12, 2018, at 12:04 PM, CHO, TAKAMUNE > > wrote:
>> 
>> Hi Alexis,
>>  
>> The payload for ConfigModify that you used is not correct.  AgentUrl has to 
>> be present in Device Authentication Table rather than in the Payload. Below 
>> is one sample:
>>  
>> "payload": 
>> "{\"request-parameters\":{\"vnf-name\":\"xxx\",\"vnf-host-ip-address\":\"https://xx.xxx.xx.xx:5000/Dispatch\"},\"configuration-parameters\":{\"vnf_name\":\”XYZ\",\"operations_timeout\":\"3600\
>>  
>> "}}"
>>  
>> To Answer your next question for CDT’s PD. Here is the sample for PD:
>>  
>> kind: "Property Definition"
>> version: V1
>> vnf-parameter-list:
>> - name: vnf_name
>>   type: null
>>   description: null
>>   required: null
>>   default: null
>>   source: Manual
>>   rule-type: null
>>   request-keys: null
>> response-keys: null
>>  
>> and one payload for Anisble:
>>  
>> {
>>   "PlaybookName": "comx/latest/ansible/modify/site.yml",
>>   "EnvParameters": {"vnf_instance": "${vnf_name}"},
>>   "Timeout": 3600
>> }
>>  
>> -Taka
>>  
>> From: onap-discuss-boun...@lists.onap.org 
>>  
>> [mailto:onap-discuss-boun...@lists.onap.org 
>> ] On Behalf Of Alexis de Talhouët
>> Sent: Monday, June 11, 2018 4:56 PM
>> To: onap-discuss > >
>> Subject: [onap-discuss] [APP-C][CDT] - What is the expected payload for 
>> ANSIBLE?
>>  
>> Greetings team,
>>  
>> I’m trying to use the ConfigModify action using the ANSIBLE “device 
>> protocol” within CDT.
>> I’m trying to execute my REST API from Postman to APP-C. I’m using the 
>> bellow payload.
>> I cannot get around this error: 
>> org.onap.ccsdk.sli.core.sli.SvcLogicException: Error constructing request 
>> for execution of playbook due to missing mandatory parameters. Reason = 
>> Ansible: Mandatory AnsibleAdapter key AgentUrl not found in parameters 
>> provided by calling agent !
>>  
>> I do see AnsibleMessageParser#reqMessage is enforcing few parameters, final 
>> String[] mandatoryTestParams = {AGENT_URL_KEY,PLAYBOOK_NAME_KEY, USER_KEY, 
>> PASS_KEY};
>> but I don’t know how to input them...
>>  
>> Can you help me understand what’s the expected payload for this REST API? 
>>  
>> On another note, what is the expected template and parameter definition when 
>> using Ansible within CDT?
>>  
>> Thanks,
>> Alexis
>>  
>> {
>> "input": {
>> "common-header": {
>> "timestamp": "2018-06-11T17:42:14.227Z",
>> "api-ver": "2.00",
>> "originator-id": "ALEX",
>> "request-id": "TEST-6",
>> "sub-request-id": "TEST-2",
>> "flags": {
>> "force": "TRUE",
>> "ttl": 12000
>> }
>> },
>> "action": "ConfigModify",
>> "action-identifiers": {
>> "vnf-id": "8ef725b6-f94a-4596-89b1-d6810ca9d6f0"
>> },
>> "payload": 
>> "{\"AgentUrl\":\"10m\",\"request-parameters\":{\"AgentUrl\":\"10m\",\"vf-module-id\":
>>  
>> \"fc8c4122-42a7-4657-9561-5adb2aa34f57\",\"vnf-host-ip-address\":\"10.195.198.22\",\"controller-template-id\":
>>  \"vlns\"},\"configuration-parameters\":{\"AgentUrl\":\"10m\"}}"
>> }
>> }
> 

___
onap-discuss mailing list

[onap-discuss] ELK stack deployment for onap Amsterdam

[Urwashi Saraswat]

HI Michael,
Do you have deployment for ELK stack in onap Amsterdam  which has new filebeat 
configuration. ? This is regarding the  onap logging project

Thanks
Urwashi
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] [APP-C][CDT] - What is the expected payload for ANSIBLE?

[CHO, TAKAMUNE]

HI Alexis,

Just like to clarify you question:

You want to pass the agenturl as an argument in an ansible payload?

Taka

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, June 12, 2018 1:40 PM
To: CHO, TAKAMUNE 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [APP-C][CDT] - What is the expected payload for 
ANSIBLE?

Taka,

Thanks for the answer. I was able to call my ansible playbook after doing the 
following:

1. Add the XYZ.ANSIBLE.ConfigModify.url = 
http://172.19.22.13:1234/Dispatch
 in /opt/appc/data/properties/appc_southbound.properties
2. Define a template with the following payload: {"PlaybookName": "$playbook}”}
3. Send the LCM RPC request using this payload:

"payload": 
"{\"configuration-parameters\":{\"operations_timeout\":\"3600\",\"playbook\":\"playbook1\"}}"


Question, is there a way to pass the agent url as argument of the LCM RPC input 
in some ways? Like we do for NETCONF configure action with vnf-host-ip-address?


Thanks,
Alexis

On Jun 12, 2018, at 12:04 PM, CHO, TAKAMUNE 
mailto:tc0...@att.com>> wrote:

Hi Alexis,

The payload for ConfigModify that you used is not correct.  AgentUrl has to be 
present in Device Authentication Table rather than in the Payload. Below is one 
sample:

"payload": 
"{\"request-parameters\":{\"vnf-name\":\"xxx\",\"vnf-host-ip-address\":\"https://xx.xxx.xx.xx:5000/Dispatch\"},\"configuration-parameters\":{\"vnf_name\":\”XYZ\",\"operations_timeout\":\"3600\"}}"

To Answer your next question for CDT’s PD. Here is the sample for PD:

kind: "Property Definition"
version: V1
vnf-parameter-list:
- name: vnf_name
  type: null
  description: null
  required: null
  default: null
  source: Manual
  rule-type: null
  request-keys: null
response-keys: null

and one payload for Anisble:

{
  "PlaybookName": "comx/latest/ansible/modify/site.yml",
  "EnvParameters": {"vnf_instance": "${vnf_name}"},
  "Timeout": 3600
}

-Taka

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Monday, June 11, 2018 4:56 PM
To: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] [APP-C][CDT] - What is the expected payload for ANSIBLE?

Greetings team,

I’m trying to use the ConfigModify action using the ANSIBLE “device protocol” 
within CDT.
I’m trying to execute my REST API from Postman to APP-C. I’m using the bellow 
payload.
I cannot get around this error:
org.onap.ccsdk.sli.core.sli.SvcLogicException: Error constructing request for 
execution of playbook due to missing mandatory parameters. Reason = Ansible: 
Mandatory AnsibleAdapter key AgentUrl not found in parameters provided by 
calling agent !

I do see AnsibleMessageParser#reqMessage is enforcing few parameters, final 
String[] mandatoryTestParams = {AGENT_URL_KEY,PLAYBOOK_NAME_KEY, USER_KEY, 
PASS_KEY};
but I don’t know how to input them...

Can you help me understand what’s the expected payload for this REST API?

On another note, what is the expected template and parameter definition when 
using Ansible within CDT?

Thanks,
Alexis

{
"input": {
"common-header": {
"timestamp": "2018-06-11T17:42:14.227Z",
"api-ver": "2.00",
"originator-id": "ALEX",
"request-id": "TEST-6",
"sub-request-id": "TEST-2",
"flags": {
"force": "TRUE",
"ttl": 12000
}
},
"action": "ConfigModify",
"action-identifiers": {
"vnf-id": "8ef725b6-f94a-4596-89b1-d6810ca9d6f0"
},
"payload": 
"{\"AgentUrl\":\"10m\",\"request-parameters\":{\"AgentUrl\":\"10m\",\"vf-module-id\":
 
\"fc8c4122-42a7-4657-9561-5adb2aa34f57\",\"vnf-host-ip-address\":\"10.195.198.22\",\"controller-template-id\":
 \"vlns\"},\"configuration-parameters\":{\"AgentUrl\":\"10m\"}}"
}
}

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

Re: [onap-discuss] [APP-C][CDT] - What is the expected payload for ANSIBLE?

[Alexis de Talhouët]

Taka,

Thanks for the answer. I was able to call my ansible playbook after doing the 
following:

1. Add the XYZ.ANSIBLE.ConfigModify.url = http://172.19.22.13:1234/Dispatch 
 in 
/opt/appc/data/properties/appc_southbound.properties
2. Define a template with the following payload: {"PlaybookName": "$playbook}”}
3. Send the LCM RPC request using this payload:

"payload": 
"{\"configuration-parameters\":{\"operations_timeout\":\"3600\",\"playbook\":\"playbook1\"}}"


Question, is there a way to pass the agent url as argument of the LCM RPC input 
in some ways? Like we do for NETCONF configure action with vnf-host-ip-address?


Thanks,
Alexis

> On Jun 12, 2018, at 12:04 PM, CHO, TAKAMUNE  wrote:
> 
> Hi Alexis,
>  
> The payload for ConfigModify that you used is not correct.  AgentUrl has to 
> be present in Device Authentication Table rather than in the Payload. Below 
> is one sample:
>  
> "payload": 
> "{\"request-parameters\":{\"vnf-name\":\"xxx\",\"vnf-host-ip-address\":\"https://xx.xxx.xx.xx:5000/Dispatch\"},\"configuration-parameters\":{\"vnf_name\":\”XYZ\",\"operations_timeout\":\"3600\
>  
> "}}"
>  
> To Answer your next question for CDT’s PD. Here is the sample for PD:
>  
> kind: "Property Definition"
> version: V1
> vnf-parameter-list:
> - name: vnf_name
>   type: null
>   description: null
>   required: null
>   default: null
>   source: Manual
>   rule-type: null
>   request-keys: null
> response-keys: null
>  
> and one payload for Anisble:
>  
> {
>   "PlaybookName": "comx/latest/ansible/modify/site.yml",
>   "EnvParameters": {"vnf_instance": "${vnf_name}"},
>   "Timeout": 3600
> }
>  
> -Taka
>  
> From: onap-discuss-boun...@lists.onap.org 
>  
> [mailto:onap-discuss-boun...@lists.onap.org 
> ] On Behalf Of Alexis de Talhouët
> Sent: Monday, June 11, 2018 4:56 PM
> To: onap-discuss  >
> Subject: [onap-discuss] [APP-C][CDT] - What is the expected payload for 
> ANSIBLE?
>  
> Greetings team,
>  
> I’m trying to use the ConfigModify action using the ANSIBLE “device protocol” 
> within CDT.
> I’m trying to execute my REST API from Postman to APP-C. I’m using the bellow 
> payload.
> I cannot get around this error: 
> org.onap.ccsdk.sli.core.sli.SvcLogicException: Error constructing request for 
> execution of playbook due to missing mandatory parameters. Reason = Ansible: 
> Mandatory AnsibleAdapter key AgentUrl not found in parameters provided by 
> calling agent !
>  
> I do see AnsibleMessageParser#reqMessage is enforcing few parameters, final 
> String[] mandatoryTestParams = {AGENT_URL_KEY,PLAYBOOK_NAME_KEY, USER_KEY, 
> PASS_KEY};
> but I don’t know how to input them...
>  
> Can you help me understand what’s the expected payload for this REST API? 
>  
> On another note, what is the expected template and parameter definition when 
> using Ansible within CDT?
>  
> Thanks,
> Alexis
>  
> {
> "input": {
> "common-header": {
> "timestamp": "2018-06-11T17:42:14.227Z",
> "api-ver": "2.00",
> "originator-id": "ALEX",
> "request-id": "TEST-6",
> "sub-request-id": "TEST-2",
> "flags": {
> "force": "TRUE",
> "ttl": 12000
> }
> },
> "action": "ConfigModify",
> "action-identifiers": {
> "vnf-id": "8ef725b6-f94a-4596-89b1-d6810ca9d6f0"
> },
> "payload": 
> "{\"AgentUrl\":\"10m\",\"request-parameters\":{\"AgentUrl\":\"10m\",\"vf-module-id\":
>  
> \"fc8c4122-42a7-4657-9561-5adb2aa34f57\",\"vnf-host-ip-address\":\"10.195.198.22\",\"controller-template-id\":
>  \"vlns\"},\"configuration-parameters\":{\"AgentUrl\":\"10m\"}}"
> }
> }

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

Re: [onap-discuss] Container Based VNF's and Orchestration

[Addepalli, Srinivasa R]

We have regular 1:00PM PST meetings on every Tuesday.  I am not sure where you 
are located. If you could join, that would be great.

Thanks
Srini


From: Naresh Babu [mailto:mailbox.nareshb...@gmail.com]
Sent: Tuesday, June 12, 2018 10:22 AM
To: Addepalli, Srinivasa R 
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Container Based VNF's and Orchestration


Hi Srinivasa,

I am interested to be a contributor for this project. Thank you.

Thanks
Naresh Babu.S

On 12 Jun 2018 22:37, "Addepalli, Srinivasa R" 
mailto:srinivasa.r.addepa...@intel.com>> wrote:
We started a new initiative to support K8S based edge-clouds and CaaS providers 
(R3+ in case of CaaS).

This is the page where you can find more information.

https://wiki.onap.org/display/DW/Support+for+K8S+%28Kubernetes%29+based+Cloud+regions

We will be happy to have more contributors for this project.  Let us know if 
you want to be a contributor.

Thanks
Srini


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org]
 On Behalf Of Naresh Babu
Sent: Tuesday, June 12, 2018 9:57 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Container Based VNF's and Orchestration

Hi Team,

I really appreciate the team efforts for bringing ONAP as one of the best 
orchestration tool for SDN and NFV.I just need to provide my thoughts and 
inputs further on NFV.Like Most of the VNF's applications are deployed under 
Virtual machines normally it take up a lot of system resources. Each VM runs 
not just a full copy of an operating system, but a virtual copy of all the 
hardware that the operating system needs to run. This quickly adds up to a lot 
of RAM and CPU's.To improve the NFV application performance ,microservices and 
VNF's can be deployed in containers which we can achieve  the continuous 
delivery of VNF critical applications.
This allows for each service upgradation and versioning separately as opposed 
to upgrading the entire VNF in a virtual machine. While upgrading a whole 
application or VNF, the container determines which individual services have 
changed and deploys only those specific services.We can use Kubernets for 
managing Containered VNF's and integrate SDN controller Opencontrail (Now it is 
called as tungsten Fabric opensource controller) for better networking 
,slicing,Isolation and improved security and we can use tosca yaml templates 
for Docker as well.Containers going to play huge role in futute NFV and 5G and  
we need to start look in to it for Container based VNF's developing and 
deployment with orchestration and closed loop automation as well.I am Just 
sharing my thoughts and inputs on this.Thank you !

Thanks
Naresh Babu S
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Container Based VNF's and Orchestration

[Naresh Babu]

Hi Srinivasa,

I am interested to be a contributor for this project. Thank you.

Thanks
Naresh Babu.S

On 12 Jun 2018 22:37, "Addepalli, Srinivasa R" <
srinivasa.r.addepa...@intel.com> wrote:

> We started a new initiative to support K8S based edge-clouds and CaaS
> providers (R3+ in case of CaaS).
>
>
>
> This is the page where you can find more information.
>
>
>
> https://wiki.onap.org/display/DW/Support+for+K8S+%
> 28Kubernetes%29+based+Cloud+regions
>
>
>
> We will be happy to have more contributors for this project.  Let us know
> if you want to be a contributor.
>
>
>
> Thanks
>
> Srini
>
>
>
>
>
> *From:* onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-bounces@
> lists.onap.org] *On Behalf Of *Naresh Babu
> *Sent:* Tuesday, June 12, 2018 9:57 AM
> *To:* onap-discuss@lists.onap.org
> *Subject:* [onap-discuss] Container Based VNF's and Orchestration
>
>
>
> Hi Team,
>
>
>
> I really appreciate the team efforts for bringing ONAP as one of the best
> orchestration tool for SDN and NFV.I just need to provide my thoughts and
> inputs further on NFV.Like Most of the VNF's applications are deployed
> under Virtual machines normally it take up a lot of system resources. Each
> VM runs not just a full copy of an operating system, but a virtual copy of
> all the hardware that the operating system needs to run. This quickly adds
> up to a lot of RAM and CPU's.To improve the NFV application performance
> ,microservices and VNF's can be deployed in containers which we can
> achieve  the continuous delivery of VNF critical applications.
>
> This allows for each service upgradation and versioning separately as
> opposed to upgrading the entire VNF in a virtual machine. While upgrading a
> whole application or VNF, the container determines which individual
> services have changed and deploys only those specific services.We can use
> Kubernets for managing Containered VNF's and integrate SDN controller
> Opencontrail (Now it is called as tungsten Fabric opensource controller)
> for better networking ,slicing,Isolation and improved security and we can
> use tosca yaml templates for Docker as well.Containers going to play huge
> role in futute NFV and 5G and  we need to start look in to it for Container
> based VNF's developing and deployment with orchestration and closed loop
> automation as well.I am Just sharing my thoughts and inputs on this.Thank
> you !
>
>
>
> Thanks
> Naresh Babu S
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] TOSCA on Kubernetes: Puccini

[Tal Liron]

Hi folks,

I'm happy to finally reveal a project I've been working on for a few months:

https://github.com/tliron/puccini

The gist of Puccini:

1) Very fast and full-featured stateless TOSCA compiler
2) Targets Kubernetes directly (more targets to come)
3) Finally introduces an "intermediary format" for TOSCA, called "Clout"

For ONAP, I humbly suggest that it could provide 1) a way to deploy
containerized VNFs while staying entirely in TOSCA and CSAR, and 2) a
possible alternative to Helm in order to minimize the number of modeling
languages in the project. Or neither! This is not an official proposal,
just the beginning of a discussion that with hopefully expand our
imagination on ways to solve some thorny architectural problems.

I'll be presenting it in Beijing next week, but will be happy to answer
questions here, too.

Also, to be clear: this is *not* an official or endorsed Red Hat project.

For a comparison with AriaTosca, see this message

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

Re: [onap-discuss] Container Based VNF's and Orchestration

[Addepalli, Srinivasa R]

We started a new initiative to support K8S based edge-clouds and CaaS providers 
(R3+ in case of CaaS).

This is the page where you can find more information.

https://wiki.onap.org/display/DW/Support+for+K8S+%28Kubernetes%29+based+Cloud+regions

We will be happy to have more contributors for this project.  Let us know if 
you want to be a contributor.

Thanks
Srini


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Naresh Babu
Sent: Tuesday, June 12, 2018 9:57 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Container Based VNF's and Orchestration

Hi Team,

I really appreciate the team efforts for bringing ONAP as one of the best 
orchestration tool for SDN and NFV.I just need to provide my thoughts and 
inputs further on NFV.Like Most of the VNF's applications are deployed under 
Virtual machines normally it take up a lot of system resources. Each VM runs 
not just a full copy of an operating system, but a virtual copy of all the 
hardware that the operating system needs to run. This quickly adds up to a lot 
of RAM and CPU's.To improve the NFV application performance ,microservices and 
VNF's can be deployed in containers which we can achieve  the continuous 
delivery of VNF critical applications.
This allows for each service upgradation and versioning separately as opposed 
to upgrading the entire VNF in a virtual machine. While upgrading a whole 
application or VNF, the container determines which individual services have 
changed and deploys only those specific services.We can use Kubernets for 
managing Containered VNF's and integrate SDN controller Opencontrail (Now it is 
called as tungsten Fabric opensource controller) for better networking 
,slicing,Isolation and improved security and we can use tosca yaml templates 
for Docker as well.Containers going to play huge role in futute NFV and 5G and  
we need to start look in to it for Container based VNF's developing and 
deployment with orchestration and closed loop automation as well.I am Just 
sharing my thoughts and inputs on this.Thank you !

Thanks
Naresh Babu S
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Container Based VNF's and Orchestration

[Naresh Babu]

Hi Team,

I really appreciate the team efforts for bringing ONAP as one of the best
orchestration tool for SDN and NFV.I just need to provide my thoughts and
inputs further on NFV.Like Most of the VNF's applications are deployed
under Virtual machines normally it take up a lot of system resources. Each
VM runs not just a full copy of an operating system, but a virtual copy of
all the hardware that the operating system needs to run. This quickly adds
up to a lot of RAM and CPU's.To improve the NFV application performance
,microservices and VNF's can be deployed in containers which we can
achieve  the continuous delivery of VNF critical applications.
This allows for each service upgradation and versioning separately as
opposed to upgrading the entire VNF in a virtual machine. While upgrading a
whole application or VNF, the container determines which individual
services have changed and deploys only those specific services.We can use
Kubernets for managing Containered VNF's and integrate SDN controller
Opencontrail (Now it is called as tungsten Fabric opensource controller)
for better networking ,slicing,Isolation and improved security and we can
use tosca yaml templates for Docker as well.Containers going to play huge
role in futute NFV and 5G and  we need to start look in to it for Container
based VNF's developing and deployment with orchestration and closed loop
automation as well.I am Just sharing my thoughts and inputs on this.Thank
you !

Thanks
Naresh Babu S
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] 答复：Re: 答复：[dcae] dcae-cli Installation Failure

[Bisht, Suraj (Nokia - US/Irving)]

Hi Vijay, Mike

Is DCAE-DS tool available in Amsterdam release? I can’t find any link in SDC 
GUI to access DCAE-DS tool kindly clarify how to access DCAE-DS, is there any 
specific ONAP component IP/link need to be used?
Some background for our use case
We are trying to create a micro service/application in DCAE to 
Publish/Subscribe particular events through new application.

Thanks,
Suraj

From: VENKATESH KUMAR, VIJAY [mailto:vv7...@att.com]
Sent: Friday, June 08, 2018 1:34 PM
To: HWANG, MICHAEL ; Bisht, Suraj (Nokia - US/Irving) 
; fu.guangr...@zte.com.cn; JI, LUSHENG 

Cc: peng.congc...@zte.com.cn; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] 答复：Re: 答复：[dcae] dcae-cli Installation Failure

The component spec example of VES collector is available on the same 
wiki

The ToscaLab tool used for model generations are supported by DCAE-DS under SDC 
project (updated the onboarding sequence flow which had an older version).

Thanks,
Vijay

From: HWANG, MICHAEL
Sent: Friday, June 08, 2018 10:05 AM
To: Bisht, Suraj (Nokia - US/Irving) 
mailto:suraj.bi...@nokia.com>>; 
fu.guangr...@zte.com.cn; JI, LUSHENG 
mailto:l...@research.att.com>>
Cc: peng.congc...@zte.com.cn; 
onap-discuss@lists.onap.org; VENKATESH 
KUMAR, VIJAY mailto:vv7...@att.com>>
Subject: Re: [onap-discuss] 答复：Re: 答复：[dcae] dcae-cli Installation Failure

+Vijay

The dcae_cli tool does not generate csar packages.  It is intended that the 
dcae_cli tool should generate tosca models which are to be used by the dcae 
design studio which is in sdc.  Currently this tosca model generation is a 
separate step.

Regarding self service of tosca model generation, @Lusheng who can help him 
with the tooling?

Regarding samples, one of the features of the dcae onboarding experience is to 
provide a shared catalog of components so that developers can share and browse. 
 However, this sort of environment is not being hosted right now.  @Vijay could 
you provide the ves's component spec as a sample?
On 06/04/2018 05:36 PM, Bisht, Suraj (Nokia - US/Irving) wrote:
Hi Mike,

Thanks for your response,
I was going through following link
https://wiki.onap.org/display/DW/MicroServices+Onboarding

and I got impression that dcae_cli tool will be used to generate csar package 
which can be used in SDC during DCAE component design, is this not the case?

Can you guide me how to create SDC compliant template to create DCAE component 
if I have data-formats and component-spec json files?
If possible kindly share one sample to verify DCAE micro service component 
deployment.

Thanks,
Suraj

From: Michael Hwang [mailto:mhw...@research.att.com]
Sent: Monday, June 04, 2018 4:24 PM
To: Bisht, Suraj (Nokia - US/Irving) 
; 
fu.guangr...@zte.com.cn; 
l...@research.att.com
Cc: peng.congc...@zte.com.cn; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] 答复：Re: 答复：[dcae] dcae-cli Installation Failure

Hi Suraj

> a)   Is dcae_cli postgress database for catalog a separate database, can 
> we use existing database from other ONAP components (i.e. SDC)?

Yes the dcae_cli postgres is a separate database.  You could share a common 
postgres instance but would have to have been initialized with the dcae_cli 
tables.

> b)Is dcae CLI an offline tool, can it be install and used independently 
> from DCAE/ONAP setup?

The dcae_cli has a range of features including to help with testing your 
component on a DCAE environment as part of onboarding.  If you are not 
intending to test then you would not need a DCAE environment.

> b)  Can dcae_cli tool generate csar without setting-up catalog database?

dcae_cli does not generate csars

> c)   Is there any sample csar available to verify deployment of dcae 
> micro-service component?

See the previous answer.

Thanks

Mike
On 06/04/2018 05:07 PM, Bisht, Suraj (Nokia - US/Irving) wrote:
Hi,

Kindly clarify following queries on dcae_cli tool, will appreciate any pointers
a)   Is dcae_cli postgress database for catalog a separate database, can we 
use existing database from other ONAP components (i.e. SDC)?
b)Is dcae CLI an offline tool, can it be install and used independently 
from DCAE/ONAP setup?
b)  Can dcae_cli tool generate csar without setting-up catalog database?
c)   Is there any sample csar available to verify deployment of dcae 
micro-service component?

Thanks,

Re: [onap-discuss] [APP-C][CDT] - What is the expected payload for ANSIBLE?

[CHO, TAKAMUNE]

Hi Alexis,

The payload for ConfigModify that you used is not correct.  AgentUrl has to be 
present in Device Authentication Table rather than in the Payload. Below is one 
sample:

"payload": 
"{\"request-parameters\":{\"vnf-name\":\"xxx\",\"vnf-host-ip-address\":\"https://xx.xxx.xx.xx:5000/Dispatch\"},\"configuration-parameters\":{\"vnf_name\":\”XYZ\",\"operations_timeout\":\"3600\"}}"

To Answer your next question for CDT’s PD. Here is the sample for PD:

kind: "Property Definition"
version: V1
vnf-parameter-list:
- name: vnf_name
  type: null
  description: null
  required: null
  default: null
  source: Manual
  rule-type: null
  request-keys: null
response-keys: null

and one payload for Anisble:

{
  "PlaybookName": "comx/latest/ansible/modify/site.yml",
  "EnvParameters": {"vnf_instance": "${vnf_name}"},
  "Timeout": 3600
}

-Taka

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Monday, June 11, 2018 4:56 PM
To: onap-discuss 
Subject: [onap-discuss] [APP-C][CDT] - What is the expected payload for ANSIBLE?

Greetings team,

I’m trying to use the ConfigModify action using the ANSIBLE “device protocol” 
within CDT.
I’m trying to execute my REST API from Postman to APP-C. I’m using the bellow 
payload.
I cannot get around this error:
org.onap.ccsdk.sli.core.sli.SvcLogicException: Error constructing request for 
execution of playbook due to missing mandatory parameters. Reason = Ansible: 
Mandatory AnsibleAdapter key AgentUrl not found in parameters provided by 
calling agent !

I do see AnsibleMessageParser#reqMessage is enforcing few parameters, final 
String[] mandatoryTestParams = {AGENT_URL_KEY, PLAYBOOK_NAME_KEY, USER_KEY, 
PASS_KEY};
but I don’t know how to input them...

Can you help me understand what’s the expected payload for this REST API?

On another note, what is the expected template and parameter definition when 
using Ansible within CDT?

Thanks,
Alexis

{
"input": {
"common-header": {
"timestamp": "2018-06-11T17:42:14.227Z",
"api-ver": "2.00",
"originator-id": "ALEX",
"request-id": "TEST-6",
"sub-request-id": "TEST-2",
"flags": {
"force": "TRUE",
"ttl": 12000
}
},
"action": "ConfigModify",
"action-identifiers": {
"vnf-id": "8ef725b6-f94a-4596-89b1-d6810ca9d6f0"
},
"payload": 
"{\"AgentUrl\":\"10m\",\"request-parameters\":{\"AgentUrl\":\"10m\",\"vf-module-id\":
 
\"fc8c4122-42a7-4657-9561-5adb2aa34f57\",\"vnf-host-ip-address\":\"10.195.198.22\",\"controller-template-id\":
 \"vlns\"},\"configuration-parameters\":{\"AgentUrl\":\"10m\"}}"
}
}
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] From Casablanca Forum Program Committee

[Alla Goldner]

Hi all,

On behalf of Casablanca Forum Program Committee:

We almost finished to schedule, some adjustments still have to be made, we will 
complete asap.

In the mean time, please do the following:


  1.  Go to the page 
https://wiki.onap.org/display/DW/China+Telecom+Meeting+Rooms  and check to make 
sure your requested session is included
  2.  In case you have late sessions requests - please put them here 
https://wiki.onap.org/display/DW/Late+sessions%27+requests by Wednesday 
midnight PST the latest (also those already approached some of us by emails)

Also, we would also like to announce that meetings will be finished on Friday 
by 11 am, to make it easier for those leaving on that day.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D4027F.66909300]

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

[onap-discuss] [coe] Team meeting Agenda

[Morales, Victor]

Hey there,

These are the topics that I’d like to talk about today


· Project status

· API Definition Discussion

· Opens

But I want to check first if someone has an additional topic that needs to 
discussed.

Regards,
Victor Morales
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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

[FORSYTH, JAMES]

Hi, Eric,

Thanks for finding this – that deploy script in the Beijing branch is slightly 
out of date, and I made an update.

Tracking it here:
https://jira.onap.org/browse/AAI-1222

thanks,
jimmy

From:  on behalf of 
"eric.deb...@orange.com" 
Date: Tuesday, June 12, 2018 at 8:18 AM
To: "onap-discuss@lists.onap.org" 
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.
___
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] VNF configuration via VFC

[Singh Kalra, Mandeep]

Hi,


 I have a doubt about the VNF configuration through VFC. 
After the VNFs are instantiated is there any interface/APIs using which the 
VNFs can be configured ?
As a stretch goal in VOLTE use case was the VNF 
configuration using ansible.
  Can you please share your views on this ?

  Also, is the gvnfm used in any use case in R2 ?

Regards
Mandeep




This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise confidential information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the e-mail by you is prohibited. Where allowed by local law, electronic 
communications with Accenture and its affiliates, including e-mail and instant 
messaging (including content), may be scanned by our systems for the purposes 
of information security and assessment of internal compliance with Accenture 
policy. Your privacy is important to us. Accenture uses your personal data only 
in compliance with data protection laws. For further information on how 
Accenture processes your personal data, please see our privacy statement at 
https://www.accenture.com/us-en/privacy-policy.
__

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