Re: [onap-discuss] [ptls][cli] Review ONAP functionalites tosupport from CLI

[Kanagaraj Manickam]

Dear Martial & Gunangrong,

Thanks for reviewing.
I will update the wiki to refer DCAE instead of Holmes.

Regards
Kanagaraj M

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

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

From: fu.guangr...@zte.com.cn 
[mailto:fu.guangr...@zte.com.cn]
Sent: Wednesday, July 19, 2017 5:55 PM
To: gn4...@intl.att.com
Cc: Kanagaraj Manickam; 
kp...@linuxfoundation.org; 
onap-discuss@lists.onap.org; 
gg2...@att.com; sw3...@att.com; 
rk5...@att.com; es4...@att.com
Subject: Re: [onap-discuss] [ptls][cli] Review ONAP functionalites tosupport 
from CLI


Yes, Martial. You're right.



When integrated with DCAE, Holmes is actually a consumer of the DMaaP data. It 
does not collect alarms directly from VNFs.



Regards,

Guangrong








Original Mail
Sender:  >;
To:  >; 
>; 
>;
CC:  >; 
>; 
>; 
>;
Date: 2017/07/19 20:10
Subject: Re: [onap-discuss] [ptls][cli] Review ONAP functionalites tosupport 
from CLI


Hello

I think the project on which depends Alarm management on your wiki page:  
https://wiki.onap.org/display/DW/CLI+Functionalities
Is wrong you listed “Holmes” but I believe it should be DCAE as Holmes doesn’t 
collect alarm as such it is more the core DCAE.

Br,
Martial

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kanagaraj Manickam
Sent: Wednesday, July 12, 2017 3:02 PM
To: onap-discuss@lists.onap.org
Cc: KOYA, RAMPRASAD >; GLOVER, GREG L 
>; SUNDELOF, ERIK 
>; WRIGHT, STEVEN A 
>; 
onap-...@lists.onap.org
Subject: [onap-discuss] [ptls][cli] Review ONAP functionalites to support from 
CLI

Dear PTLs,

From ONAP wiki, I have gone thru the Use-cases defined for release A and based 
on my understanding,
captured the minimum-required-top level functionalities in the wiki  
https://wiki.onap.org/display/DW/CLI+Functionalities

For each of the functionality, I tried to match them with respective project.
Could you please review them, provide your approvals/feedbacks. Thank you.

Regards
Kanagaraj M


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

***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than 

[onap-discuss] [cli] MoM July 19th 2017

[Kanagaraj Manickam]

Dear team,
Pls find the yesterday’s CLI meeting minutes here  
https://wiki.onap.org/display/DW/CLI+meetings#CLImeetings-19-July-2017

Regards
Kanagaraj M


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

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

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

[onap-discuss] [vfc]please cancel the vfc meeting next week

[杨艳]

Hi Kenny,

 

Can you please cancel the weekly meeting for
VF-C(https://zoom.us/j/621738721
 ) next week. Because it conflicts
with virtual developer event.

Thanks for your kindly help.

 

 

 

Best Regards,

Yan

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

Re: [onap-discuss] [ccsdk] Meeting Minutes/Synchronous Communication Method?

[HANSEN, TONY L]

I’ve never seen an invite to [onap-discuss] for any [ccsdk] weekly meetings. 
The wiki says EDT Tue 9pm / CNT Wed 9am. Is that correct?

Tony Hansen

From:  on behalf of "Williams, Marcus" 

Date: Wednesday, July 19, 2017 at 5:32 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] [ccsdk] Meeting Minutes/Synchronous Communication 
Method?

CCSDK Project,

1.Are meeting minutes available for the weekly and one off CCSDK 
meetings? In other open source communities it is standard practice to produce 
meeting minutes so that discussions/decisions are public record and to 
demonstrate openness. Not to mention that they are also useful for those out on 
PTO, as I was recently. Often these minutes are taken using IRC bots and this 
is a collaborative effort with many members of the project helping keep the 
minutes. I believe we have collabot available in the #onap-meeting IRC channel. 
For meetings I’m able to attend, I volunteer to start keeping minutes using 
collabot if there are no objections or other suggestions. When meetings are 
finished all that's required is an email to the list with link to minutes 
created through collabot (see for example 
http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-07-11-14.07.html)

2.Is there a preferred synchronous communication method for CCSDK 
Project? This is helpful when conferring about patches, discussing issues in 
real-time and creating a community around a project. In other open source 
communities IRC is used. I’ve created an #onap-ccsdk IRC channel for this 
purpose, but have heard in the past that some cannot use IRC due to proxy 
issues.

Thanks,
Marcus Williams
IRC @ mgkwill
Network Software Engineer
Intel Corp. - DataCenter Network Solutions Group

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

[onap-discuss] 答复: Re: About workflow engine

[zhang.maopeng1]

Hi Zahi




Yes, definite.  Workflow engines have different workflow templates. If 
the workflow is designed by user via SDC,  it will effect SDC.

In my mind, some workflow is used by user, maybe some workflow is used 
only by the code developer as well, such as Camunda offline tools, DG offline 
tools,

However  if the workflow design for user can be integrated with SDC via 
portal SDK, It will be greater.




Best Regards

Maopeng



原始邮件



发件人： 
收件人：张茂鹏10030173  
抄送人： 
日 期 ：2017年07月20日 02:27
主 题 ：Re: [onap-discuss] About workflow engine 





Can we also have a discussion about the workflow designer (which should be part 
of SDC), its capabilities, proposed architecture etc.?

Zahi Kapeluto
Lead Architect, Network Communications LOB
AT Network Applications Development · SD
Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
·
Mobile: +972 (54) 6636831
Office: +972 (3) 9280064

From:  on behalf of 
"zhang.maope...@zte.com.cn" 
Date: Wednesday, 19 July 2017 at 12:46
To: "seshu.kuma...@huawei.com" , 
"onap-discuss@lists.onap.org" 
Subject: [onap-discuss] About workflow engine


Hi seshu and guys



   About the workflow engine(WFE) usage, I have an idea and want to share in 
the community, If I am wrong, please correct me.

   In the SO or controllers projects of ONAP,  there are many opensource party 
workflow engines, such as Camunda, MSO, DG, aria tosca workflow engine, ...etc.

   Most of those workflow engines now bind to the project.

   Workflow engines self are independant fucntion and can be decoupled with the 
specific project logic functions.

   Could the projects make them as micro service? If some projects use the 
same one,  the WFE instance could be shared among them.

   If possible, we can create an group or wiki page to discuss the issue.

   Thanks all.



Best Regards

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

Re: [onap-discuss] Versioning for Amsterdam

[C.T. Paterson]

Agreed with Option 2.  It seems a standard practice to collect the various
versioned components into a manifest.

In A we have a decomposed microservices architecture, and actually tried
our own version of Option 1 for a while.  Unsurprisingly, it created more
overhead and confusion among development, and are trying to move to #2
internally.

Cheers.


On 19 July 2017 at 11:06, SPATSCHECK, OLIVER (OLIVER) <
spat...@research.att.com> wrote:

>
> On the OOM call the question of versioning came up and as this is a larger
> issue across projects David and I decided to bring it up with the larger
> community. I know we have discussed this before but I am not sure we made a
> final decision for Amsterdam (sorry if there was a decision I missed but
> nobody on the call was aware of any decision…).
>
> The question is how to handle the fact that the seed code is tagged with
> different version numbers > 1 already.
>
> There are really two options to fix that.
>
> 1. We try to keep the version numbers all in sync and in sync with the
> release number which will require “down versioning” some of the code with
> all the problems that will cause with dependencies and artifact caching. It
> will also be difficult to maintain as we are applying patches after the
> Amsterdam release is out (a patch to one component would trigger a version
> update to all other components).
>
> 2. We allow each repo to manage there own version number and then the
> Amsterdam release is just really a collection of artifacts with different
> version numbers properly tagged/referenced.
>
> I think most people I talked to prefer 2.
>
> Do we have consensus on this?
>
> Does the TSC have to officially bless this?
>
> Thx
>
> Oliver
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] #PTL

[GILBERT, MAZIN E (MAZIN E)]

PTL Team, 

Some projects have made an outstanding job on reducing and cleaning-up the 
committers' list.
Please review committers in your project and approach them to ensure their 
commitment
and appropriate role in your project. Let’s stick to up-to 2 committers per 
company.

Phil and I will review where we are in the TSC meeting Thursday.

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

Re: [onap-discuss] Versioning for Amsterdam

[Yunxia Chen]

Option 3 is an alternative as option 1. I +1 for option 1 or option 3 from 
Integration point of view and end user point of view.

I understand that the “freedom” on each project with its own versioning. As 
stated in Gildas’s email, currently we have 20+ projects which will participate 
the Arsterdam simultaneous release, it will be very hard for us to test all 
those combinations and maintain that mapping.

Regards,

Helen Chen

From:  on behalf of Gildas Lanilis 

Date: Wednesday, July 19, 2017 at 1:58 PM
To: "HANSEN, TONY L" , "onap-discuss@lists.onap.org" 

Subject: Re: [onap-discuss] Versioning for Amsterdam

To my knowledge, no decision was made on versioning.

If we go with option #2:

Questions:

1)  Who is maintaining the version dependency? Or ideally how to generate 
automatically that dependency graph?

2)  When we will deliver Amsterdam later in November, we are going to say: 
We are delivering Amsterdam Release 1.0.0 that embeds the following components: 
AAI version 2.0.3, AAF version 1.0.8, Clamp version 0.9.0. and so on. Are we 
comfortable with that approach?



3)  Independently of option #1 or #2, do we agree to adopt Semantic 
Versionning?


[cid:image001.jpg@01D300AB.EC99B3E0]

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of HANSEN, TONY L
Sent: Wednesday, July 19, 2017 1:24 PM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Versioning for Amsterdam

Here’s my +1 as well for option 2. I also like Randa’s addition, but make sure 
you also add in “Prototype” or “PreRelease” or something along those lines for 
issues filed against the current pre-Amsterdam code base.

Tony

From: 
>
 on behalf of "MAHER, RANDA" >
Date: Wednesday, July 19, 2017 at 3:43 PM
To: "TALASILA, MANOOP" 
>, 
"onap-discuss@lists.onap.org" 
>, "SPATSCHECK, 
OLIVER" >
Subject: Re: [onap-discuss] Versioning for Amsterdam

I would further propose an enhancement for Option 2:

All Jira project be updated to include a new field called Release Name and 
entries for that field be from a pull down menu that would include Amsterdam, 
Beijing, and any future release added when the name is determined. Further, 
that Affects Version and Fix Version be used to identify the version number in 
which an issue is found in and/or submitted in.

Having a separate Release Name Attribute in Jira will allow to easily build  
query to collect all the items being submitted for Amsterdam and we don’t have 
to worry about different version numbers being used across different projects 
for the same major release.

Randa

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of TALASILA, MANOOP
Sent: Wednesday, July 19, 2017 2:51 PM
To: onap-discuss@lists.onap.org; 
SPATSCHECK, OLIVER >
Subject: Re: [onap-discuss] Versioning for Amsterdam

+1 for option 2 (from Portal team)
Manoop

On Wed, Jul 19, 2017 at 11:06 AM -0400, "SPATSCHECK, OLIVER (OLIVER)" 
> wrote:

*** Security Advisory: This Message Originated Outside of AT ***.

Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.







On the OOM call the question of versioning came up and as this is a larger 
issue across projects David and I decided to bring it up with the larger 
community. I know we have discussed this before but I am not sure we made a 
final decision for Amsterdam (sorry if there was a decision I missed but nobody 
on the call was aware of any decision…).







The question is how to handle the fact that the seed code is tagged with 
different version numbers > 1 already.







There are really two options to fix that.







1. We try to keep the version numbers all in sync and in sync with the release 
number which will require “down versioning” some of the code with all the 
problems that will cause with dependencies and artifact caching. It will also 
be difficult to maintain as we are applying patches after the Amsterdam release 
is out (a patch to one component would trigger a version update to all other 
components).







2. We allow each repo to manage there own version number and then the Amsterdam 
release is just really a collection of artifacts with different version numbers 
properly 

Re: [onap-discuss] [appc] Synchronous Communication Method?

[MAHER, RANDA]

Hi Marcus,
Yes indeed, for many of us getting to IRC is a challenge.
Up to this point, we have been depending on emails, weekly meeting ,and ad-hoc 
meetings as needed.
As we get closer to pairwise/integration testing, this may not necessarily work 
best, so we need to overcome the firewall issue. I'm still looking into this.
Thanks,
Randa


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Williams, Marcus
Sent: Wednesday, July 19, 2017 5:24 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [appc] Synchronous Communication Method?

APPC Project,

Is there a preferred synchronous communication method for APPC Project. This is 
helpful when conferring about patches, discussing issues in real-time and 
creating a community around a project. In other open source communities IRC is 
used. I've created an #onap-appc IRC channel for this purpose, but have heard 
in the past that some cannot use IRC due to proxy issues.

Thanks,
Marcus Williams
IRC @ mgkwill
Network Software Engineer
Intel Corp. - DataCenter Network Solutions Group

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

[onap-discuss] [integration][so] vCPE questions related to SO

[Kang Xi]

Hi Seshu and SO team,

We have the following questions related to SO. The first one is partially 
answered based on the previous meetings. Please review for accuracy and answer 
the rest of the question. Appreciate if you could provide comments/answers by 
the end of this week. You can either use email or update the wiki page 
directly: 
https://wiki.onap.org/display/DW/Use+Case+Related+Important+Questions+and+Answers

4. Question:
What specific workflow recipes are needed for vCPE? What are the tools to 
create such recipes? How are the workflow recipes associated with the service, 
packaged, and distributed?

Answer:
There will be two sets of workflows.
 - The first is to instantiate the general infrastructure, including vBNG, 
vG_Mux, vDHCP, and vAAA. They are explained on the use case wiki page?.
 - The second is to instantiate per-customer service, including 
service-level operations and resource-level operations (tunnel cross connect, 
vG, and vBRG). They are explained in these slides.
https://wiki.onap.org/download/attachments/3246168/vCPE%20Use%20Case%20-%20Customer%20Service%20Instantiation.pptx?version=1=1500335608000=v2

10. Question:
Message bus topics need to be defined and used on DMaaP to enable communication 
among different modules. When are such topics defined and how are they 
configured? E.g., Policy will send event on a TOPIC_VM_RESTART to invoke VM 
restart, APPC will subscribe to TOPIC_VM_RESTART and execute the restart DG. 
When and where to define this topic? Who configures Policy and APPC to 
publish/subscribe to the topic, and when?

Regards,
Kang


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

[onap-discuss] [sdnc] Meeting Minutes/Synchronous Communication Method?

[Williams, Marcus]

SDNC Project,

1.Are meeting minutes available for the weekly and one off SDNC 
meetings? In other open source communities it is standard practice to produce 
meeting minutes so that discussions/decisions are public record and to 
demonstrate openness. Not to mention that they are also useful for those out on 
PTO, as I was recently. Often these minutes are taken using IRC bots and this 
is a collaborative effort with many members of the project helping keep the 
minutes. I believe we have collabot available in the #onap-meeting IRC channel. 
For meetings I'm able to attend, I volunteer to start keeping minutes using 
collabot if there are no objections or other suggestions. When meetings are 
finished all that's required is an email to the list with link to minutes 
created through collabot (see 
http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-07-11-14.07.html)

2.Is there a preferred synchronous communication method for SDNC 
Project? This is helpful when conferring about patches, discussing issues in 
real-time and creating a community around a project. In other open source 
communities IRC is used. I've created an #onap-sdnc IRC channel for this 
purpose, but have heard in the past that some cannot use IRC due to proxy 
issues.

Thanks,
Marcus Williams
IRC @ mgkwill
Network Software Engineer
Intel Corp. - DataCenter Network Solutions Group

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

[onap-discuss] [ccsdk] Meeting Minutes/Synchronous Communication Method?

[Williams, Marcus]

CCSDK Project,

1.Are meeting minutes available for the weekly and one off CCSDK 
meetings? In other open source communities it is standard practice to produce 
meeting minutes so that discussions/decisions are public record and to 
demonstrate openness. Not to mention that they are also useful for those out on 
PTO, as I was recently. Often these minutes are taken using IRC bots and this 
is a collaborative effort with many members of the project helping keep the 
minutes. I believe we have collabot available in the #onap-meeting IRC channel. 
For meetings I'm able to attend, I volunteer to start keeping minutes using 
collabot if there are no objections or other suggestions. When meetings are 
finished all that's required is an email to the list with link to minutes 
created through collabot (see for example 
http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-07-11-14.07.html)

2.Is there a preferred synchronous communication method for CCSDK 
Project? This is helpful when conferring about patches, discussing issues in 
real-time and creating a community around a project. In other open source 
communities IRC is used. I've created an #onap-ccsdk IRC channel for this 
purpose, but have heard in the past that some cannot use IRC due to proxy 
issues.

Thanks,
Marcus Williams
IRC @ mgkwill
Network Software Engineer
Intel Corp. - DataCenter Network Solutions Group

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

Re: [onap-discuss] Getting Release Engineering support

[Andrew Grimberg]

helpd...@onap.org gets redirected to
onap-helpd...@rt.linuxfoundation.org on the backend. They're one and the
same location. The first is just easier for most folks to remember ;)

-Andy-

On 07/19/2017 01:34 PM, MAHER, RANDA wrote:
> Hi Andrew,
> 
> The email I had for requesting support was 
> onap-helpd...@rt.linuxfoundation.org 
> Should this be retired in favor of helpd...@onap.org  or do both work?
> 
> Thanks, Randa 
> 
> -Original Message-
> From: onap-discuss-boun...@lists.onap.org 
> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Andrew Grimberg
> Sent: Wednesday, July 19, 2017 10:57 AM
> To: onap-discuss@lists.onap.org
> Subject: [onap-discuss] Getting Release Engineering support
> 
> Greetings folks,
> 
> I've been seeing a large uptick in unicast support requests directly to 
> myself or myself and other LF Release Engineers.
> 
> As an reminder, the LF Release Engineering team does not work on support 
> requests that are directed to our personal / corporate email. Support 
> requests _must_ be directed at our helpdesk ticketing system by sending them 
> to helpd...@onap.org
> 
> If we feel that the request / issue doesn't warrant being in a ticket we'll 
> pull the discussion offline from the ticketing system, but that is where you 
> should be starting for most things.
> 
> -Andy-
> 
> --
> Andrew J Grimberg
> Lead, IT Release Engineering
> The Linux Foundation
> 

-- 
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation



signature.asc
Description: OpenPGP digital signature
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [appc] Synchronous Communication Method?

[Williams, Marcus]

APPC Project,

Is there a preferred synchronous communication method for APPC Project. This is 
helpful when conferring about patches, discussing issues in real-time and 
creating a community around a project. In other open source communities IRC is 
used. I've created an #onap-appc IRC channel for this purpose, but have heard 
in the past that some cannot use IRC due to proxy issues.

Thanks,
Marcus Williams
IRC @ mgkwill
Network Software Engineer
Intel Corp. - DataCenter Network Solutions Group

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

[onap-discuss] [Integration][SDC] Use case questions related to SDC

[Kang Xi]

Hi Michael and SDC team,

Would you please take a look at the slides at the following link and see if the 
requirements to SDC look good? The use case subcommittee would like to finish 
the use case analysis by the end of this week. If you have any comments please 
let us know by then. If everything looks good please ensure that the 
requirements are included in your R1 planning.

https://wiki.onap.org/download/attachments/3246168/vCPE%20Use%20Case%20-%20Customer%20Service%20Instantiation.pptx?version=1=1500335608000=v2

Also we have the following questions related to SDC. Appreciate if you could 
provide comments/answers by the end of this week. You can either use email or 
update the wiki page directly: 
https://wiki.onap.org/display/DW/Use+Case+Related+Important+Questions+and+Answers

Q1. The output of SDC will include a variety of files (csar, xml, yang, etc) 
being distributed to multiple modules, SO, AAI, Policy, etc. Can we create a 
document to specify the details, including package structure, format, usage, 
etc. There are NSD and VNFD specs on the VF-C page (refer 
https://wiki.onap.org/display/DW/VF-C+R1+Deliverables). Does ONAP use them as 
generic spec?

Q2. For VoLTE, the input is TOSCA. SDC please confirm whether TOSCA input will 
be supported or not.

Regards,
Kang

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

[onap-discuss] Canceled Event: External API Framework Weekly @ Wed Jul 26, 2017 7am - 8am (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20170726T07
DTEND;TZID=America/Los_Angeles:20170726T08
DTSTAMP:20170719T211753Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:pb8m9g0c4nluod9pj8sji2k...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=am
 8...@att.com;X-NUM-GUESTS=0:mailto:am8...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
RECURRENCE-ID;TZID=America/Los_Angeles:20170726T07
CREATED:20170627T004051Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 1 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/399880266\n\nOr iPhone one-tap (US Toll):  +14086380968\,\,399880266# o
 r +16465588656\,\,399880266#\n\nOr Telephone:\nDial: +1 408 638 0968 (U
 S Toll) or +1 646 558 8656 (US Toll)\n+1 855 880 1246 (US Toll Free)\n 
+1 877 369 0926 (US Toll Free)\nMeeting ID: 399 880 266\nInterna
 tional numbers available: https://zoom.us/zoomconference?m=LF2HGv5CtX4TFta0
 8oFdd9riWHL_hEVN\n\n
LAST-MODIFIED:20170719T211752Z
LOCATION:https://zoom.us/j/399880266
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:External API Framework Weekly
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Updated: [sdnc] Weekly SDNC project team meeting

[Williams, Marcus]

Brian,
Thanks! This looks really useful. I'd be happy to give feedback after I've 
walked through the tutorials.

Thanks,
Marcus Williams
IRC @ mgkwill
Network Software Engineer
Intel Corp. - DataCenter Network Solutions Group

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of FREEMAN, BRIAN D
Sent: Wednesday, July 19, 2017 11:10 AM
To: TIMONEY, DAN ; ARIA, LALENA ; BOROKHOVICH, 
MICHAEL ; CHINTHAKAYALA, SHESHASHAILAVAS 
; GUPTA, ALOK ; LANDO, MICHAEL 
; LANTHIER, STEPHEN ; NGUYEN, 
TOAN T ; OBRIEN, FRANK MICHAEL ; 
onap-discuss@lists.onap.org; REECE, CHRIS ; ROTUNDO, 
AL ; SILVERTHORN, DANIEL ; 
SPATSCHECK, OLIVER ; STILWELL, DAVE ; 
TABEDZKI, RICHARD ; TALASILA, MANOOP 
; THORPE, HENRY E ; TOFIGH, TOM 

Subject: Re: [onap-discuss] Updated: [sdnc] Weekly SDNC project team meeting

I created a Tutorial page on how to prototype in SDNC using the SLI-API Execute 
Graph function.

https://wiki.onap.org/display/DW/How+to+use+SLI-API+for+SDNC+Model%2C+Directed+Graph+and+Adapter+prototyping

Feedback greatly appreciated.

For VoLTE,  I think using the REST API call node to test against a 3rd party 
controller would be useful to understand the data you need in the yang model to 
support the API calls. The tutorial on netconf setup between SDNC and APPC is 
an example of that if you want to review that tutorial.

https://wiki.onap.org/display/DW/Automatically+Creating+a+Netconf+Mount+in+APPC+from+SDNC

In particular:


 
 
 
 
 
 
 


Brian


-Original Appointment-
From: TIMONEY, DAN
Sent: Wednesday, July 05, 2017 9:13 AM
To: TIMONEY, DAN; ARIA, LALENA; BOROKHOVICH, MICHAEL; CHINTHAKAYALA, 
SHESHASHAILAVAS; GUPTA, ALOK; LANDO, MICHAEL; LANTHIER, STEPHEN; NGUYEN, TOAN 
T; OBRIEN, FRANK MICHAEL; 
onap-discuss@lists.onap.org; REECE, CHRIS; 
ROTUNDO, AL; SILVERTHORN, DANIEL; SPATSCHECK, OLIVER; STILWELL, DAVE; TABEDZKI, 
RICHARD; TALASILA, MANOOP; THORPE, HENRY E; TOFIGH, TOM
Subject: [onap-discuss] Updated: [sdnc] Weekly SDNC project team meeting
When: Wednesday, July 19, 2017 9:00 AM-9:30 AM America/New_York.
Where: Zoom meeting - see notes for logistics


***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
When: July 12, 2017 at 9:00:00 AM EDT (recurring)
Where: Zoom meeting - see notes for logistics
--
ONAP Meeting 6 is inviting you to a scheduled Zoom meeting.

Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/330824945

Or iPhone one-tap (US Toll): +16465588656,,330824945# or 
+14086380968,,330824945#

Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 330 824 945
International numbers available: 
https://zoom.us/zoomconference?m=rRItS256rDo_7UtkIznpz4jzZNmjTfbO

<< File: ATT1.txt >>

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

Re: [onap-discuss] Versioning for Amsterdam

[Gildas Lanilis]

To my knowledge, no decision was made on versioning.

If we go with option #2:

Questions:

1)   Who is maintaining the version dependency? Or ideally how to generate 
automatically that dependency graph?

2)   When we will deliver Amsterdam later in November, we are going to say: 
We are delivering Amsterdam Release 1.0.0 that embeds the following components: 
AAI version 2.0.3, AAF version 1.0.8, Clamp version 0.9.0. and so on. Are we 
comfortable with that approach?



3)   Independently of option #1 or #2, do we agree to adopt Semantic 
Versionning?


[cid:image003.jpg@01D30097.08B57DD0]

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of HANSEN, TONY L
Sent: Wednesday, July 19, 2017 1:24 PM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Versioning for Amsterdam

Here’s my +1 as well for option 2. I also like Randa’s addition, but make sure 
you also add in “Prototype” or “PreRelease” or something along those lines for 
issues filed against the current pre-Amsterdam code base.

Tony

From: 
>
 on behalf of "MAHER, RANDA" >
Date: Wednesday, July 19, 2017 at 3:43 PM
To: "TALASILA, MANOOP" 
>, 
"onap-discuss@lists.onap.org" 
>, "SPATSCHECK, 
OLIVER" >
Subject: Re: [onap-discuss] Versioning for Amsterdam

I would further propose an enhancement for Option 2:

All Jira project be updated to include a new field called Release Name and 
entries for that field be from a pull down menu that would include Amsterdam, 
Beijing, and any future release added when the name is determined. Further, 
that Affects Version and Fix Version be used to identify the version number in 
which an issue is found in and/or submitted in.

Having a separate Release Name Attribute in Jira will allow to easily build  
query to collect all the items being submitted for Amsterdam and we don’t have 
to worry about different version numbers being used across different projects 
for the same major release.

Randa

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of TALASILA, MANOOP
Sent: Wednesday, July 19, 2017 2:51 PM
To: onap-discuss@lists.onap.org; 
SPATSCHECK, OLIVER >
Subject: Re: [onap-discuss] Versioning for Amsterdam

+1 for option 2 (from Portal team)
Manoop

On Wed, Jul 19, 2017 at 11:06 AM -0400, "SPATSCHECK, OLIVER (OLIVER)" 
> wrote:

*** Security Advisory: This Message Originated Outside of AT ***.

Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.







On the OOM call the question of versioning came up and as this is a larger 
issue across projects David and I decided to bring it up with the larger 
community. I know we have discussed this before but I am not sure we made a 
final decision for Amsterdam (sorry if there was a decision I missed but nobody 
on the call was aware of any decision…).







The question is how to handle the fact that the seed code is tagged with 
different version numbers > 1 already.







There are really two options to fix that.







1. We try to keep the version numbers all in sync and in sync with the release 
number which will require “down versioning” some of the code with all the 
problems that will cause with dependencies and artifact caching. It will also 
be difficult to maintain as we are applying patches after the Amsterdam release 
is out (a patch to one component would trigger a version update to all other 
components).







2. We allow each repo to manage there own version number and then the Amsterdam 
release is just really a collection of artifacts with different version numbers 
properly tagged/referenced.







I think most people I talked to prefer 2.







Do we have consensus on this?







Does the TSC have to officially bless this?







Thx







Oliver


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

Re: [onap-discuss] Getting Release Engineering support

[Gildas Lanilis]

Hi Andy,

You have a very legitimate request.
I think it would help the community, if we could have a web interface to submit 
ticket. That will help the community to see what has already been submitted 
(and avoid duplicates) and track progress on resolution. 

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Andrew Grimberg
Sent: Wednesday, July 19, 2017 7:57 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Getting Release Engineering support

Greetings folks,

I've been seeing a large uptick in unicast support requests directly to myself 
or myself and other LF Release Engineers.

As an reminder, the LF Release Engineering team does not work on support 
requests that are directed to our personal / corporate email. Support requests 
_must_ be directed at our helpdesk ticketing system by sending them to 
helpd...@onap.org

If we feel that the request / issue doesn't warrant being in a ticket we'll 
pull the discussion offline from the ticketing system, but that is where you 
should be starting for most things.

-Andy-

--
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation

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

Re: [onap-discuss] Versioning for Amsterdam

[HERNANDEZ-HERRERO, JORGE]

For scope clarification on #2 proposal, does #2 implies versioning freedom 
*within* a given repo?   For example policy/drools-applications repo could have 
some artifacts delivered to be in version X, and others version Y.

Jorge

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of HANSEN, TONY L
Sent: Wednesday, July 19, 2017 3:24 PM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Versioning for Amsterdam

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Here’s my +1 as well for option 2. I also like Randa’s addition, but make sure 
you also add in “Prototype” or “PreRelease” or something along those lines for 
issues filed against the current pre-Amsterdam code base.

Tony

From: 
>
 on behalf of "MAHER, RANDA" >
Date: Wednesday, July 19, 2017 at 3:43 PM
To: "TALASILA, MANOOP" 
>, 
"onap-discuss@lists.onap.org" 
>, "SPATSCHECK, 
OLIVER" >
Subject: Re: [onap-discuss] Versioning for Amsterdam

I would further propose an enhancement for Option 2:

All Jira project be updated to include a new field called Release Name and 
entries for that field be from a pull down menu that would include Amsterdam, 
Beijing, and any future release added when the name is determined. Further, 
that Affects Version and Fix Version be used to identify the version number in 
which an issue is found in and/or submitted in.

Having a separate Release Name Attribute in Jira will allow to easily build  
query to collect all the items being submitted for Amsterdam and we don’t have 
to worry about different version numbers being used across different projects 
for the same major release.

Randa

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of TALASILA, MANOOP
Sent: Wednesday, July 19, 2017 2:51 PM
To: onap-discuss@lists.onap.org; 
SPATSCHECK, OLIVER >
Subject: Re: [onap-discuss] Versioning for Amsterdam

+1 for option 2 (from Portal team)
Manoop

On Wed, Jul 19, 2017 at 11:06 AM -0400, "SPATSCHECK, OLIVER (OLIVER)" 
> wrote:

*** Security Advisory: This Message Originated Outside of AT ***.

Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.







On the OOM call the question of versioning came up and as this is a larger 
issue across projects David and I decided to bring it up with the larger 
community. I know we have discussed this before but I am not sure we made a 
final decision for Amsterdam (sorry if there was a decision I missed but nobody 
on the call was aware of any decision…).







The question is how to handle the fact that the seed code is tagged with 
different version numbers > 1 already.







There are really two options to fix that.







1. We try to keep the version numbers all in sync and in sync with the release 
number which will require “down versioning” some of the code with all the 
problems that will cause with dependencies and artifact caching. It will also 
be difficult to maintain as we are applying patches after the Amsterdam release 
is out (a patch to one component would trigger a version update to all other 
components).







2. We allow each repo to manage there own version number and then the Amsterdam 
release is just really a collection of artifacts with different version numbers 
properly tagged/referenced.







I think most people I talked to prefer 2.







Do we have consensus on this?







Does the TSC have to officially bless this?







Thx







Oliver


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

Re: [onap-discuss] Getting Release Engineering support

[MAHER, RANDA]

Hi Andrew,

The email I had for requesting support was onap-helpd...@rt.linuxfoundation.org 
Should this be retired in favor of helpd...@onap.org  or do both work?

Thanks, Randa 

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Andrew Grimberg
Sent: Wednesday, July 19, 2017 10:57 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Getting Release Engineering support

Greetings folks,

I've been seeing a large uptick in unicast support requests directly to myself 
or myself and other LF Release Engineers.

As an reminder, the LF Release Engineering team does not work on support 
requests that are directed to our personal / corporate email. Support requests 
_must_ be directed at our helpdesk ticketing system by sending them to 
helpd...@onap.org

If we feel that the request / issue doesn't warrant being in a ticket we'll 
pull the discussion offline from the ticketing system, but that is where you 
should be starting for most things.

-Andy-

--
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation

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

[onap-discuss] Canceled Event: CLAMP Weekly Meeting @ Wed Jul 26, 2017 6am - 7am (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20170726T06
DTEND;TZID=America/Los_Angeles:20170726T07
DTSTAMP:20170719T195408Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:0upe2fpbg1j2smc20bh4cnaje0_r20170628t130...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=rs
 hac...@research.att.com;X-NUM-GUESTS=0:mailto:rshac...@research.att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
RECURRENCE-ID;TZID=America/Los_Angeles:20170726T06
CLASS:PUBLIC
CREATED:20170616T165703Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 4 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/985787133\n\nOr iPhone one-tap (US Toll):  +16465588656\,985787133# or 
 +14086380968\,985787133#\n\nOr Telephone:\nDial: +1 646 558 8656 (US To
 ll) or +1 408 638 0968 (US Toll)\n+1 855 880 1246 (US Toll Free)\n+
 1 877 369 0926 (US Toll Free)\nMeeting ID: 985 787 133\nInternation
 al numbers available: https://zoom.us/zoomconference?m=-Nj9qjeFFTIOFpGsEEV5
 yqOJU7UFyFPN\n\n
LAST-MODIFIED:20170719T195408Z
LOCATION:https://zoom.us/j/985787133
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:CLAMP Weekly Meeting
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Versioning for Amsterdam

[MAHER, RANDA]

I would further propose an enhancement for Option 2:

All Jira project be updated to include a new field called Release Name and 
entries for that field be from a pull down menu that would include Amsterdam, 
Beijing, and any future release added when the name is determined. Further, 
that Affects Version and Fix Version be used to identify the version number in 
which an issue is found in and/or submitted in.

Having a separate Release Name Attribute in Jira will allow to easily build  
query to collect all the items being submitted for Amsterdam and we don't have 
to worry about different version numbers being used across different projects 
for the same major release.

Randa

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of TALASILA, MANOOP
Sent: Wednesday, July 19, 2017 2:51 PM
To: onap-discuss@lists.onap.org; SPATSCHECK, OLIVER 
Subject: Re: [onap-discuss] Versioning for Amsterdam

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
+1 for option 2 (from Portal team)
Manoop



On Wed, Jul 19, 2017 at 11:06 AM -0400, "SPATSCHECK, OLIVER (OLIVER)" 
> wrote:

*** Security Advisory: This Message Originated Outside of AT ***.

Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.







On the OOM call the question of versioning came up and as this is a larger 
issue across projects David and I decided to bring it up with the larger 
community. I know we have discussed this before but I am not sure we made a 
final decision for Amsterdam (sorry if there was a decision I missed but nobody 
on the call was aware of any decision...).







The question is how to handle the fact that the seed code is tagged with 
different version numbers > 1 already.







There are really two options to fix that.







1. We try to keep the version numbers all in sync and in sync with the release 
number which will require "down versioning" some of the code with all the 
problems that will cause with dependencies and artifact caching. It will also 
be difficult to maintain as we are applying patches after the Amsterdam release 
is out (a patch to one component would trigger a version update to all other 
components).







2. We allow each repo to manage there own version number and then the Amsterdam 
release is just really a collection of artifacts with different version numbers 
properly tagged/referenced.







I think most people I talked to prefer 2.







Do we have consensus on this?







Does the TSC have to officially bless this?







Thx







Oliver

___

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=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=LAI-Umc4zSkltMhqFIe2AtXWQ2i16n3NXqLDr3PzAeA=evSWTr1B0z6sN35ujTQQgNXd3mwx6Ck4s-FOmrAcgHg=
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] DCAE controller-startup.sh fails and throws error

[Arun Arora]

Thanks Marco.
Will get back here soon with results.

Regards,
Arun


From: PLATANIA, MARCO  (MARCO)
Sent: Thursday, July 20, 12:09 AM
Subject: Re: [onap-discuss] DCAE controller-startup.sh fails and throws error
To: Arun Arora (c), LUND, CARSTEN  (CARSTEN)
Cc: onap-discuss@lists.onap.org


Arun,

You can modify the yaml file manually. Then you have to run “make down” to 
shutdown the entire environment and then “bash init.sh” and “make up” to 
startup again. Those files are in /opt/dcae-startup-vm-controller.

No need to rebuild ONAP.

Thanks,
Marco


From:  on behalf of "Arun Arora (c)" 

Date: Wednesday, July 19, 2017 at 2:00 PM
To: "LUND, CARSTEN (CARSTEN)" 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] DCAE controller-startup.sh fails and throws error

Okay, thanks for pointing that out. I think redeploying ONAP stack is not 
necessary? Will it be fine if I just change the Zone in config.yaml in DCAE and 
rerun 
dcae_install.sh
 manually?
Also, do you think this is causing the problem of missing files and directories?
Thanks,
Arun
On Jul 19, 2017, at 11:06 PM, "LUND, CARSTEN (CARSTEN)" 
> wrote:
I noticed this from the log

+ export 'ZONE=NorthIndia '
+ ZONE='NorthIndia '

Note the space after NorthIndia.

Please remove from config.yaml and redeploy.

Carsten

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Wednesday, July 19, 2017 9:29 AM
To: MAJHI, TAPAN ; Josef Reisinger 
; FREEMAN, BRIAN D ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] DCAE controller-startup.sh fails and throws error

Hi All,

Regarding the issue I am facing for DCAE VMs deployment, the immediate blocker 
for me is required files and directories are not found (like cdap-instances, 
docker-instances, docker-instances). I am suspecting these directories are 
created in run-time as I searched them in the DCAA VM, Container and DCAE Demo 
Gittree but couldn’t find them.
Attaching the execution logs for your reference. All errors for missing files, 
directories are mentioned as exceptions in the attached execution log.

1)  I tried with rel-1.0 and rel-1.1 but both gave same errors
2)  Also tried with both 2-NIC and 1-NIC-FLOATING-IPS. No luck in this as 
well
3)  Currently using 1-NIC-FLOATING-IPS
4)  Verified config.yaml parameters with all configurations and 
modifications in 
https://jira.onap.org/browse/DCAEGEN2-69
 and 
https://jira.onap.org/browse/DCAEGEN2-7
5)  Found some more config issues in the config.yaml and fixed
6)  Finally, made sure the execution is going as per the sequence mentioned 
in 

Re: [onap-discuss] Versioning for Amsterdam

[TALASILA, MANOOP (MANOOP)]

+1 for option 2 (from Portal team)

Manoop




On Wed, Jul 19, 2017 at 11:06 AM -0400, "SPATSCHECK, OLIVER (OLIVER)" 
> wrote:


*** Security Advisory: This Message Originated Outside of AT ***.
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.



On the OOM call the question of versioning came up and as this is a larger 
issue across projects David and I decided to bring it up with the larger 
community. I know we have discussed this before but I am not sure we made a 
final decision for Amsterdam (sorry if there was a decision I missed but nobody 
on the call was aware of any decision…).



The question is how to handle the fact that the seed code is tagged with 
different version numbers > 1 already.



There are really two options to fix that.



1. We try to keep the version numbers all in sync and in sync with the release 
number which will require “down versioning” some of the code with all the 
problems that will cause with dependencies and artifact caching. It will also 
be difficult to maintain as we are applying patches after the Amsterdam release 
is out (a patch to one component would trigger a version update to all other 
components).



2. We allow each repo to manage there own version number and then the Amsterdam 
release is just really a collection of artifacts with different version numbers 
properly tagged/referenced.



I think most people I talked to prefer 2.



Do we have consensus on this?



Does the TSC have to officially bless this?



Thx



Oliver
___
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=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w=LAI-Umc4zSkltMhqFIe2AtXWQ2i16n3NXqLDr3PzAeA=evSWTr1B0z6sN35ujTQQgNXd3mwx6Ck4s-FOmrAcgHg=

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

Re: [onap-discuss] Updated: [sdnc] Weekly SDNC project team meeting

[FREEMAN, BRIAN D]

I created a Tutorial page on how to prototype in SDNC using the SLI-API Execute 
Graph function.

https://wiki.onap.org/display/DW/How+to+use+SLI-API+for+SDNC+Model%2C+Directed+Graph+and+Adapter+prototyping

Feedback greatly appreciated.

For VoLTE,  I think using the REST API call node to test against a 3rd party 
controller would be useful to understand the data you need in the yang model to 
support the API calls. The tutorial on netconf setup between SDNC and APPC is 
an example of that if you want to review that tutorial.

https://wiki.onap.org/display/DW/Automatically+Creating+a+Netconf+Mount+in+APPC+from+SDNC

In particular:



 
 
 
 
 
 
 


Brian


-Original Appointment-
From: TIMONEY, DAN
Sent: Wednesday, July 05, 2017 9:13 AM
To: TIMONEY, DAN; ARIA, LALENA; BOROKHOVICH, MICHAEL; CHINTHAKAYALA, 
SHESHASHAILAVAS; GUPTA, ALOK; LANDO, MICHAEL; LANTHIER, STEPHEN; NGUYEN, TOAN 
T; OBRIEN, FRANK MICHAEL; onap-discuss@lists.onap.org; REECE, CHRIS; ROTUNDO, 
AL; SILVERTHORN, DANIEL; SPATSCHECK, OLIVER; STILWELL, DAVE; TABEDZKI, RICHARD; 
TALASILA, MANOOP; THORPE, HENRY E; TOFIGH, TOM
Subject: [onap-discuss] Updated: [sdnc] Weekly SDNC project team meeting
When: Wednesday, July 19, 2017 9:00 AM-9:30 AM America/New_York.
Where: Zoom meeting - see notes for logistics


***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.


When: July 12, 2017 at 9:00:00 AM EDT (recurring)
Where: Zoom meeting - see notes for logistics
--
ONAP Meeting 6 is inviting you to a scheduled Zoom meeting.

Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/330824945

Or iPhone one-tap (US Toll): +16465588656,,330824945# or 
+14086380968,,330824945#

Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 330 824 945
International numbers available: 
https://zoom.us/zoomconference?m=rRItS256rDo_7UtkIznpz4jzZNmjTfbO

 << File: ATT1.txt >>

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

Re: [onap-discuss] DCAE controller-startup.sh fails and throws error

[PLATANIA, MARCO (MARCO)]

Arun,

You can modify the yaml file manually. Then you have to run “make down” to 
shutdown the entire environment and then “bash init.sh” and “make up” to 
startup again. Those files are in /opt/dcae-startup-vm-controller.

No need to rebuild ONAP.

Thanks,
Marco


From:  on behalf of "Arun Arora (c)" 

Date: Wednesday, July 19, 2017 at 2:00 PM
To: "LUND, CARSTEN (CARSTEN)" 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] DCAE controller-startup.sh fails and throws error

Okay, thanks for pointing that out. I think redeploying ONAP stack is not 
necessary? Will it be fine if I just change the Zone in config.yaml in DCAE and 
rerun 
dcae_install.sh
 manually?
Also, do you think this is causing the problem of missing files and directories?
Thanks,
Arun
On Jul 19, 2017, at 11:06 PM, "LUND, CARSTEN (CARSTEN)" 
> wrote:
I noticed this from the log


+ export 'ZONE=NorthIndia '
+ ZONE='NorthIndia '


Note the space after NorthIndia.


Please remove from config.yaml and redeploy.


Carsten


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Wednesday, July 19, 2017 9:29 AM
To: MAJHI, TAPAN ; Josef Reisinger 
; FREEMAN, BRIAN D ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] DCAE controller-startup.sh fails and throws error



Hi All,



Regarding the issue I am facing for DCAE VMs deployment, the immediate blocker 
for me is required files and directories are not found (like cdap-instances, 
docker-instances, docker-instances). I am suspecting these directories are 
created in run-time as I searched them in the DCAA VM, Container and DCAE Demo 
Gittree but couldn’t find them.

Attaching the execution logs for your reference. All errors for missing files, 
directories are mentioned as exceptions in the attached execution log.



1)  I tried with rel-1.0 and rel-1.1 but both gave same errors

2)  Also tried with both 2-NIC and 1-NIC-FLOATING-IPS. No luck in this as 
well

3)  Currently using 1-NIC-FLOATING-IPS

4)  Verified config.yaml parameters with all configurations and 
modifications in 
https://jira.onap.org/browse/DCAEGEN2-69
 and 
https://jira.onap.org/browse/DCAEGEN2-7

5)  Found some more config issues in the config.yaml and fixed

6)  Finally, made sure the execution is going as per the sequence mentioned 
in 
https://wiki.onap.org/display/DW/DCAE+Controller+Development+Guide



The problem happens with the following command execution done as part of ‘make 
gen-config sync restart’

java -cp 'lib/*' 
org.openecomp.dcae.controller.operation.utils.GenControllerConfiguration $ZONE 
. GITLINK OPENECOMP-DEMO



I am not able to find the directories/ files listed in the errors.



Any pointers from anyone who have fixed these issues?

@Tapan, @Joseph, @Brian, special mention to you for any pointers to resolve 
this issue, as you have finished the deployment (Congrats BTW ☺ )





Thanks & Regards,

Arun Arora



PS: Wanted to mention again, I am deploying on VIO (VMware Integrated OpenStack)









From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Tuesday, July 18, 2017 8:29 PM
To: Arun Arora (c) >; 
onap-discuss@lists.onap.org
Subject: RE: DCAE controller-startup.sh fails and throws error



We also faced this issue and created an JIRA ID: DCAEGEN2-69



And  we tried to provided required conf and logs. Please let us know if 
additional details required.



Thanks.



Regards

Kanagaraj M



***

Re: [onap-discuss] About workflow engine

[Kapeluto, Zahi]

Can we also have a discussion about the workflow designer (which should be part 
of SDC), its capabilities, proposed architecture etc.?

Zahi Kapeluto
Lead Architect, Network Communications LOB
AT Network Applications Development · SD
Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
·
Mobile: +972 (54) 6636831
Office: +972 (3) 9280064

From:  on behalf of 
"zhang.maope...@zte.com.cn" 
Date: Wednesday, 19 July 2017 at 12:46
To: "seshu.kuma...@huawei.com" , 
"onap-discuss@lists.onap.org" 
Subject: [onap-discuss] About workflow engine


Hi seshu and guys



   About the workflow engine(WFE) usage, I have an idea and want to share in 
the community, If I am wrong, please correct me.

   In the SO or controllers projects of ONAP,  there are many opensource party 
workflow engines, such as Camunda, MSO, DG, aria tosca workflow engine, ...etc.

   Most of those workflow engines now bind to the project.

   Workflow engines self are independant fucntion and can be decoupled with the 
specific project logic functions.

   Could the projects make them as micro service? If some projects use the 
same one,  the WFE instance could be shared among them.

   If possible, we can create an group or wiki page to discuss the issue.

   Thanks all.



Best Regards

Maopeng










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

Re: [onap-discuss] DCAE controller-startup.sh fails and throws error

[Arun Arora (c)]

Okay, thanks for pointing that out. I think redeploying ONAP stack is not 
necessary? Will it be fine if I just change the Zone in config.yaml in DCAE and 
rerun dcae_install.sh manually?

Also, do you think this is causing the problem of missing files and directories?

Thanks,
Arun
On Jul 19, 2017, at 11:06 PM, "LUND, CARSTEN (CARSTEN)" 
> wrote:
I noticed this from the log


+ export 'ZONE=NorthIndia '
+ ZONE='NorthIndia '


Note the space after NorthIndia.


Please remove from config.yaml and redeploy.


Carsten


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Wednesday, July 19, 2017 9:29 AM
To: MAJHI, TAPAN ; Josef Reisinger 
; FREEMAN, BRIAN D ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] DCAE controller-startup.sh fails and throws error



Hi All,



Regarding the issue I am facing for DCAE VMs deployment, the immediate blocker 
for me is required files and directories are not found (like cdap-instances, 
docker-instances, docker-instances). I am suspecting these directories are 
created in run-time as I searched them in the DCAA VM, Container and DCAE Demo 
Gittree but couldn’t find them.

Attaching the execution logs for your reference. All errors for missing files, 
directories are mentioned as exceptions in the attached execution log.



1)  I tried with rel-1.0 and rel-1.1 but both gave same errors

2)  Also tried with both 2-NIC and 1-NIC-FLOATING-IPS. No luck in this as 
well

3)  Currently using 1-NIC-FLOATING-IPS

4)  Verified config.yaml parameters with all configurations and 
modifications in 
https://jira.onap.org/browse/DCAEGEN2-69
 and 
https://jira.onap.org/browse/DCAEGEN2-7

5)  Found some more config issues in the config.yaml and fixed

6)  Finally, made sure the execution is going as per the sequence mentioned 
in 
https://wiki.onap.org/display/DW/DCAE+Controller+Development+Guide



The problem happens with the following command execution done as part of ‘make 
gen-config sync restart’

java -cp 'lib/*' 
org.openecomp.dcae.controller.operation.utils.GenControllerConfiguration $ZONE 
. GITLINK OPENECOMP-DEMO



I am not able to find the directories/ files listed in the errors.



Any pointers from anyone who have fixed these issues?

@Tapan, @Joseph, @Brian, special mention to you for any pointers to resolve 
this issue, as you have finished the deployment (Congrats BTW ☺ )





Thanks & Regards,

Arun Arora



PS: Wanted to mention again, I am deploying on VIO (VMware Integrated OpenStack)









From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Tuesday, July 18, 2017 8:29 PM
To: Arun Arora (c) >; 
onap-discuss@lists.onap.org
Subject: RE: DCAE controller-startup.sh fails and throws error



We also faced this issue and created an JIRA ID: DCAEGEN2-69



And  we tried to provided required conf and logs. Please let us know if 
additional details required.



Thanks.



Regards

Kanagaraj M



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

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



From: 

[onap-discuss] [CLAMP] cancel weekly meeting of 26th july

[Ngueko, Gervais-Martial]

Hi Kenny,

Can you cancel the weekly meeting for CLAMP (https://zoom.us/j/985787133). For 
next week (26th of july).
Given the virtual developer event this meeting must be cancelled.

Br,

Gervais-Martial Ngueko
Principal, Application Design
CP - Common Platform & Technology Services
AT Global Network Services Belgium/Luxembourg

"TEXTING and DRIVING... It Can Wait."

AT
Rethink Possible
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
M: +32 478 960 529
gn4...@att.com

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

[onap-discuss] [appc] OOO notification and backup contact

[MAHER, RANDA]

Hello Gildas,

I wanted to let you know that I will be out of office next week on vacation 
(7/24 - 7/28) returning 7/31/17.
My back up during this time for APPC will be Catherine Lefevre, also copied 
here.

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

[onap-discuss] [appc] Cancel 7/26/17 APPC Project call

[MAHER, RANDA]

Hello Casey,

Can you please cancel the APPC 7/26/17 APPC Project Call at 11AM EST since it 
conflicts with the Virtual Developers Event?
As always, many thanks for your excellent support.

Regards,
Randa Maher

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

[onap-discuss] Canceled Event: ONAP Policy Framework Weekly @ Wed Jul 26, 2017 5am - 6am (PDT) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20170726T05
DTEND;TZID=America/Los_Angeles:20170726T06
DTSTAMP:20170719T170355Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:3peha7dllj5vnqu92u70qjo...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=pd
 rag...@research.att.com;X-NUM-GUESTS=0:mailto:pdrag...@research.att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
RECURRENCE-ID;TZID=America/Los_Angeles:20170726T05
CLASS:PUBLIC
CREATED:20170601T195143Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 3 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/463561265\n\nOr iPhone one-tap (US Toll):  +16465588656\,463561265# or 
 +14086380968\,463561265#\n\nOr Telephone:\nDial: +1 646 558 8656 (US To
 ll) or +1 408 638 0968 (US Toll)\nMeeting ID: 463 561 265\nInternat
 ional numbers available: https://zoom.us/zoomconference?m=g-6zp_3xtuteVvzJy
 DLRVKWXKdzg-VTA\n\n
LAST-MODIFIED:20170719T170355Z
LOCATION:https://zoom.us/j/463561265
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:ONAP Policy Framework Weekly
TRANSP:TRANSPARENT
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [modeling] Use of Papyrus for UML modeling tools...

[Vul, Alex]

Dear all,

We are looking to use Papyrus as part of our modeling work in VNF SDK and 
External API projects. Does the Modeling Project need to do anything with 
respect to ownership and endorsement of this tool? If not, how do we go about 
getting an "official" version of Papyrus deployed for use across ONAP projects?

Thanks in advance,

Alex Vul
Intel Corporation


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

[onap-discuss] Gerrit survey

[Andrew Grimberg]

Greetings folks,

A survey was sent to the Gerrit mailing list yesterday soliciting
feedback from admins and users of Gerrit. If you want to possibly
influence changes to Gerrit here's your chance :)

It will take about 15 minutes to do.

https://google.qualtrics.com/jfe/form/SV_0JKI9MBgY4eY4x7

-Andy-

-- 
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation



signature.asc
Description: OpenPGP digital signature
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] DCAE controller-startup.sh fails and throws error

[Arun Arora (c)]

VIO version is 3.1 and it maps to OpenStack Mitaka.


Thanks


Arun


On Jul 19, 2017, at 6:59 PM, "Arun Arora (c)" 
> wrote:

Hi All,



Regarding the issue I am facing for DCAE VMs deployment, the immediate blocker 
for me is required files and directories are not found (like cdap-instances, 
docker-instances, docker-instances). I am suspecting these directories are 
created in run-time as I searched them in the DCAA VM, Container and DCAE Demo 
Gittree but couldn’t find them.

Attaching the execution logs for your reference. All errors for missing files, 
directories are mentioned as exceptions in the attached execution log.



1)  I tried with rel-1.0 and rel-1.1 but both gave same errors

2)  Also tried with both 2-NIC and 1-NIC-FLOATING-IPS. No luck in this as 
well

3)  Currently using 1-NIC-FLOATING-IPS

4)  Verified config.yaml parameters with all configurations and 
modifications in 
https://jira.onap.org/browse/DCAEGEN2-69
 and 
https://jira.onap.org/browse/DCAEGEN2-7

5)  Found some more config issues in the config.yaml and fixed

6)  Finally, made sure the execution is going as per the sequence mentioned 
in 
https://wiki.onap.org/display/DW/DCAE+Controller+Development+Guide



The problem happens with the following command execution done as part of ‘make 
gen-config sync restart’

java -cp 'lib/*' 
org.openecomp.dcae.controller.operation.utils.GenControllerConfiguration $ZONE 
. GITLINK OPENECOMP-DEMO



I am not able to find the directories/ files listed in the errors.



Any pointers from anyone who have fixed these issues?

@Tapan, @Joseph, @Brian, special mention to you for any pointers to resolve 
this issue, as you have finished the deployment (Congrats BTW J )





Thanks & Regards,

Arun Arora



PS: Wanted to mention again, I am deploying on VIO (VMware Integrated OpenStack)








From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Tuesday, July 18, 2017 8:29 PM
To: Arun Arora (c) ; onap-discuss@lists.onap.org
Subject: RE: DCAE controller-startup.sh fails and throws error



We also faced this issue and created an JIRA ID: DCAEGEN2-69



And  we tried to provided required conf and logs. Please let us know if 
additional details required.



Thanks.



Regards

Kanagaraj M



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

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



From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Tuesday, July 18, 2017 7:47 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] DCAE controller-startup.sh fails and throws error



Hi All,



We are trying to deploy ONAP on VIO. Using the following YAML and env files:

[onap-discuss] Versioning for Amsterdam

[SPATSCHECK, OLIVER (OLIVER)]

On the OOM call the question of versioning came up and as this is a larger 
issue across projects David and I decided to bring it up with the larger 
community. I know we have discussed this before but I am not sure we made a 
final decision for Amsterdam (sorry if there was a decision I missed but nobody 
on the call was aware of any decision…).

The question is how to handle the fact that the seed code is tagged with 
different version numbers > 1 already.

There are really two options to fix that.

1. We try to keep the version numbers all in sync and in sync with the release 
number which will require “down versioning” some of the code with all the 
problems that will cause with dependencies and artifact caching. It will also 
be difficult to maintain as we are applying patches after the Amsterdam release 
is out (a patch to one component would trigger a version update to all other 
components).

2. We allow each repo to manage there own version number and then the Amsterdam 
release is just really a collection of artifacts with different version numbers 
properly tagged/referenced.

I think most people I talked to prefer 2. 

Do we have consensus on this?

Does the TSC have to officially bless this?

Thx

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

[onap-discuss] Getting Release Engineering support

[Andrew Grimberg]

Greetings folks,

I've been seeing a large uptick in unicast support requests directly to
myself or myself and other LF Release Engineers.

As an reminder, the LF Release Engineering team does not work on support
requests that are directed to our personal / corporate email. Support
requests _must_ be directed at our helpdesk ticketing system by sending
them to helpd...@onap.org

If we feel that the request / issue doesn't warrant being in a ticket
we'll pull the discussion offline from the ticketing system, but that is
where you should be starting for most things.

-Andy-

-- 
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation



signature.asc
Description: OpenPGP digital signature
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [holmes]A Call for Holmes Weekly Meeting Topics

[fu.guangrong]

Hi guys,




The weekly meeting of Holmes is going to be held tomorrow. As we disscussed in 
the Policy and CLAMP weekly meeting today, pls send out the questions which you 
want to be answered discussed. I'll try to sort them out and arrange the 
timeslot for all of them.




Thanks and regards,




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

[onap-discuss] please cancel the 7/26/2017 policy weekly meeting

[DRAGOSH, PAMELA L (PAM)]

In lieu of the developer conference next week.

Thanks!

Pam Dragosh
ONAP Policy PTL

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

Re: [onap-discuss] DCAE controller-startup.sh fails and throws error

[Arun Arora (c)]

Hi All,



Regarding the issue I am facing for DCAE VMs deployment, the immediate blocker 
for me is required files and directories are not found (like cdap-instances, 
docker-instances, docker-instances). I am suspecting these directories are 
created in run-time as I searched them in the DCAA VM, Container and DCAE Demo 
Gittree but couldn’t find them.

Attaching the execution logs for your reference. All errors for missing files, 
directories are mentioned as exceptions in the attached execution log.



1)  I tried with rel-1.0 and rel-1.1 but both gave same errors

2)  Also tried with both 2-NIC and 1-NIC-FLOATING-IPS. No luck in this as 
well

3)  Currently using 1-NIC-FLOATING-IPS

4)  Verified config.yaml parameters with all configurations and 
modifications in https://jira.onap.org/browse/DCAEGEN2-69 and 
https://jira.onap.org/browse/DCAEGEN2-7

5)  Found some more config issues in the config.yaml and fixed

6)  Finally, made sure the execution is going as per the sequence mentioned 
in https://wiki.onap.org/display/DW/DCAE+Controller+Development+Guide



The problem happens with the following command execution done as part of ‘make 
gen-config sync restart’

java -cp 'lib/*' 
org.openecomp.dcae.controller.operation.utils.GenControllerConfiguration $ZONE 
. GITLINK OPENECOMP-DEMO



I am not able to find the directories/ files listed in the errors.



Any pointers from anyone who have fixed these issues?

@Tapan, @Joseph, @Brian, special mention to you for any pointers to resolve 
this issue, as you have finished the deployment (Congrats BTW J )





Thanks & Regards,

Arun Arora



PS: Wanted to mention again, I am deploying on VIO (VMware Integrated OpenStack)








From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Tuesday, July 18, 2017 8:29 PM
To: Arun Arora (c) ; onap-discuss@lists.onap.org
Subject: RE: DCAE controller-startup.sh fails and throws error



We also faced this issue and created an JIRA ID: DCAEGEN2-69



And  we tried to provided required conf and logs. Please let us know if 
additional details required.



Thanks.



Regards

Kanagaraj M



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

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



From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Tuesday, July 18, 2017 7:47 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] DCAE controller-startup.sh fails and throws error



Hi All,



We are trying to deploy ONAP on VIO. Using the following YAML and env files:

https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master

https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master





In the DCAE VM, the dcae-controller docker is running however, 
controller-startup.sh inside it fails with error. Seen the following and fixed

1)  /etc/hosts has static IP addresses for each DCAE VM which does not 
match with the Private subnet IP addresses mentioned in ENV file. So changed 
the IP addresses in /etc/hosts

2)   

[onap-discuss] [vnfrqts]: Requirements Document Structure

[PATTEN, HERBERT L]

In our meeting this morning there was discussion about proposal for the 
outline
 of the VNF Requirements Document. I have edited that page with another 
approach. Please provide your comments and edits.


Herb Patten
Lead Principal - Technical Architect
Technology Operations, Technology Planning & Engineering

AT
221 W. Winton, C113, Hayward, CA 94544
m  415.272.1265 | hp1...@att.com

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

[onap-discuss] Error Code POL5000 during creating New VF

[Ajay.Priyadarshi]

Hi,

During creating Error Code POL5000 during creating New VF.

[cid:image001.png@01D300BD.D3E5AD60]

Regards,
Ajay

"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s). 
are confidential and may be privileged. If you are not the intended recipient. 
you are hereby notified that any 
review. re-transmission. conversion to hard copy. copying. circulation or other 
use of this message and any attachments is 
strictly prohibited. If you are not the intended recipient. please notify the 
sender immediately by return email. 
and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. 
The company cannot accept responsibility for any loss or damage arising from 
the use of this email or attachment."
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Robot log file is asking for password to open

[Michael O'Brien]

Tapan,
   Good question.  Andrew Fenner posted info on configuring authentication (it 
is not pre-configured on robot) on the container around test:test
   See his comment on
https://wiki.onap.org/display/DW/Tutorial%3A+Creating+a+Service+Instance+from+a+Design+Model

/michael

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Tapan Majhi
Sent: Wednesday, July 19, 2017 02:02
To: onap-discuss 
Subject: [onap-discuss] Robot log file is asking for password to open

I have installed the onap environment from 1.1-STAGING-latest image.
Trying to run robot testcase and see the logs from 
http://{robot-ip}:88/log.html
Its asking for username and password. Anyone aware of it ?


Regards,
Tapan M
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
Amdocs Development Centre India Private Limited having CIN: 
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A 
limited liability partner­ship with LLP Identification Number: AAI-6901 
effective 28th Feb 2017)
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] docker pull getting failed

[Ajay.Priyadarshi]

Hi,

For SDC & APPC docker pull is getting exception.

root@vm1-sdc:/opt#
Unable to find image 'mariadb:latest' locally
latest: Pulling from library/mariadb
9f0706ba7422: Pulling fs layer
2290e155d2d0: Pulling fs layer
547981b8269f: Pulling fs layer
2c9d42ed2f48: Waiting
25ec4aceb5b0: Waiting
9d17c8f49a76: Waiting
9581cae2cfc9: Waiting
e33e97da1c23: Waiting
1794b7ea240d: Waiting
3295fa23590d: Waiting
861b4f082c90: Waiting
6f67a3e22037: Waiting
error pulling image configuration: Get 
https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/b1/b101c8399ee344ff0b329133fa9cc5cb2915f61048f99ec38b2bfe72718b7daf/data?Expires=1500445827=JBTP1O9~exn~FMkdBDK5qJN-dfdP~wnW11bPt~-PNIn-VvGbQdcLP9mB~z9z0DWbcQofgjXn0vWrpcjZSOhemdcqA8nE11mhlVpnMD5uJIN8UqDUZmDcO5iwXBLNiy-Qxu9yJ~ok114LGYHNfpk4x6UBFd3e3uUZw523XvkamS4_=APKAJECH5M7VWIS5YZ6Q:
 net/http: TLS handshake timeout


root@vm1-appc:/opt# ./appc_vm_init.sh
Already up-to-date.
Login Succeeded
1.1-STAGING-latest: Pulling from openecomp/appc-image
Digest: sha256:e667910620bf907b09b19c0a9c1f8dd4514ac420024d4e0429317b9b80e73f4c
Status: Image is up to date for 
nexus3.onap.org:10001/openecomp/appc-image:1.1-STAGING-latest
1.1-STAGING-latest: Pulling from openecomp/dgbuilder-sdnc-image
Digest: sha256:3325af99ed2d811562157dbbf27744fe431a703d7e00cf73a5da65589bab8fc7
Status: Image is up to date for 
nexus3.onap.org:10001/openecomp/dgbuilder-sdnc-image:1.1-STAGING-latest
Pulling db (mysql/mysql-server:5.6)...
5.6: Pulling from mysql/mysql-server
7bd9e1692b54: Pulling fs layer
24b8460627ce: Pulling fs layer
61706d188c1d: Pulling fs layer
f816bc25fe64: Waiting
ERROR: error pulling image configuration: Get 
https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/79/797883af4b336a2eb675613734d7d2c9def93ac4f0023ac77aeb34d9e85c94a1/data?Expires=1500456106=ClO0CuAAFLasRLPZW5RJt8E70eIl8xp1WieKysX81~BLCUUApOPOv~P0Rtdat57aeNP9vuP8pB7XsQvs03LvQlV6pHu2creM4~D0GkPpiSGkOp4KEiWgQWUvOLUXHqmEfrQMrTAkJWyUiQqSvqxHjltq0AmQUHn576hYS9qx19w_=APKAJECH5M7VWIS5YZ6Q:
 net/http: TLS handshake timeout


Regards,
Ajay
"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s). 
are confidential and may be privileged. If you are not the intended recipient. 
you are hereby notified that any 
review. re-transmission. conversion to hard copy. copying. circulation or other 
use of this message and any attachments is 
strictly prohibited. If you are not the intended recipient. please notify the 
sender immediately by return email. 
and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. 
The company cannot accept responsibility for any loss or damage arising from 
the use of this email or attachment."
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ptls][cli] Review ONAP functionalites tosupport from CLI

[fu.guangrong]

Yes, Martial. You're right.




When integrated with DCAE, Holmes is actually a consumer of the DMaaP data. It 
does not collect alarms directly from VNFs.




Regards,

Guangrong



















Original Mail



Sender:  
To:    

CC:     
Date: 2017/07/19 20:10
Subject: Re: [onap-discuss] [ptls][cli] Review ONAP functionalites tosupport 
from CLI







Hello


 


I think the project on which depends Alarm management on your wiki page:  
https://wiki.onap.org/display/DW/CLI+Functionalities


Is wrong you listed “Holmes” but I believe it should be DCAE as Holmes doesn’t 
collect alarm as such it is more the core DCAE.


 


Br,


Martial


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kanagaraj Manickam
 Sent: Wednesday, July 12, 2017 3:02 PM
 To: onap-discuss@lists.onap.org
 Cc: KOYA, RAMPRASAD  GLOVER, GREG L  SUNDELOF, 
ERIK  WRIGHT, STEVEN A  onap-...@lists.onap.org
 Subject: [onap-discuss] [ptls][cli] Review ONAP functionalites to support from 
CLI


 


Dear PTLs,


 


From ONAP wiki, I have gone thru the Use-cases defined for release A and based 
on my understanding,


captured the minimum-required-top level functionalities in the wiki  
https://wiki.onap.org/display/DW/CLI+Functionalities


 


For each of the functionality, I tried to match them with respective project.


Could you please review them, provide your approvals/feedbacks. Thank you.


 


Regards


Kanagaraj M


 


 


***
 
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
 
 
***
 This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
 
***___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ptls][cli] Review ONAP functionalites to support from CLI

[Ngueko, Gervais-Martial]

Hello

I think the project on which depends Alarm management on your wiki page:  
https://wiki.onap.org/display/DW/CLI+Functionalities
Is wrong you listed “Holmes” but I believe it should be DCAE as Holmes doesn’t 
collect alarm as such it is more the core DCAE.

Br,
Martial

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kanagaraj Manickam
Sent: Wednesday, July 12, 2017 3:02 PM
To: onap-discuss@lists.onap.org
Cc: KOYA, RAMPRASAD >; GLOVER, GREG L 
>; SUNDELOF, ERIK 
>; WRIGHT, STEVEN A 
>; 
onap-...@lists.onap.org
Subject: [onap-discuss] [ptls][cli] Review ONAP functionalites to support from 
CLI

Dear PTLs,

From ONAP wiki, I have gone thru the Use-cases defined for release A and based 
on my understanding,
captured the minimum-required-top level functionalities in the wiki  
https://wiki.onap.org/display/DW/CLI+Functionalities

For each of the functionality, I tried to match them with respective project.
Could you please review them, provide your approvals/feedbacks. Thank you.

Regards
Kanagaraj M


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

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


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

Re: [onap-discuss] VID tab is not showing portal for VID

[Subhash Kumar Singh]

Hello Elhay,

Please check the JIRA issue [1].

[1] https://jira.onap.org/browse/PORTAL-38
--
Regards,
Subhash Kumar Singh

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

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

From: Elhay Efrat [mailto:elhay.efr...@amdocs.com]
Sent: Tuesday, July 18, 2017 9:37 PM
To: Subhash Kumar Singh ; 
onap-discuss@lists.onap.org
Subject: RE: VID tab is not showing portal for VID

Please send both docker logs vid and vid-mariadb

-- Sent from my Android Device



From: 
onap-discuss-boun...@lists.onap.org 
on behalf of Subhash Kumar Singh
Sent: Tuesday, July 18, 2017 3:49:28 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] VID tab is not showing portal for VID
Hello Everyone,

After stacking ONAP (v 1.1.0-STAGING) we observed that VID tab is not  
functional in portal tabs. In v1.0-STAGING, VID tab was functional.
Please let us know for this issue [1].

[1] https://jira.onap.org/browse/PORTAL-38

--
Regards,
Subhash Kumar Singh
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] About workflow engine

[zhang.maopeng1]

Hi seshu and guys




   About the workflow engine(WFE) usage, I have an idea and want to share in 
the community, If I am wrong, please correct me.

   In the SO or controllers projects of ONAP,  there are many opensource party 
workflow engines, such as Camunda, MSO, DG, aria tosca workflow engine, ...etc. 
 

   Most of those workflow engines now bind to the project. 

   Workflow engines self are independant fucntion and can be decoupled with the 
specific project logic functions. 

   Could the projects make them as micro service? If some projects use the 
same one,  the WFE instance could be shared among them.

   If possible, we can create an group or wiki page to discuss the issue.

   Thanks all.




Best Regards

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

Re: [onap-discuss] CSAR from SDC

[zhao.huabing]

Hi Zahi,

Thanks for your answer.




1.  Can't find the corresponding node template for the defined capabilities and 
requirements in the substitution_mappingsThe substation mapping in the below 
example contains capabilities/requirements. Those are the caps/reqs defined by 
this node template so why are you looking for any other node template?




Regarding this question, as I understand it, it's the mappings between the 
external Node Types named capabilities and requirements to existing 
implementations of those capabilities and requirements on Node templates 
declared within the topology template.  

Let me use the below TOSCA service template as an example,

the substitution_mappings capability message_receiver expose the 
message_receiver capability of  app node template, 

the substitution_mappings requirement database_endpoint  expose the database 
capability of  app node template, 

tosca_definitions_version: tosca_simple_yaml_1_0




topology_template:

  description: Template of a database including its hosting stack.

# omitted for brevity

  substitution_mappings:

node_type: example.TransactionSubsystem

capabilities:

  message_receiver: [ app, message_receiver ]

requirements:

  database_endpoint: [ app, database ]

  node_templates:

app:

  type: example.SomeApp

  properties:

# properties omitted for brevity

  capabilities:

message_receiver:

  properties:

service_ip: { get_input: mq_service_ip }

# other properties omitted for brevity

  requirements:

- database:

# details omitted for brevity

- host: websrv




In this service template  service-57431726F7e64a30Ae52-template.yml, I don't 
see this mapping.




Did I miss anything?




Thanks,

Huabing



Original Mail



Sender:  
To:  zhaohuabing10201488
CC:  YuanHu10090474 
Date: 2017/07/18 22:00
Subject: Re: [onap-discuss] CSAR from SDC





Hi Huabing,

Additional answers :

  1.  Can't find the corresponding node template for the defined capabilities 
and requirements in the substitution_mappings
The substation mapping in the below example contains capabilities/requirements. 
Those are the caps/reqs defined by this node template so why are you looking 
for any other node template?

  1.  Does SDC support the definition of TOSCA Group?
Yes

  1.  Does SDC support the definition of TOSCA Policy?
Yes

  1.  Does SDC support the mapping of Input and Node Template property?
Yes

  1.  Does SDC support the mapping of Output and Node Template attribute?
No
Zahi Kapeluto
Lead Architect, Network Communications LOB
AT Network Applications Development · SD
Tel Aviv | Tampa | Atlanta | New Jersey | Chicago
·
Mobile: +972 (54) 6636831
Office: +972 (3) 9280064

From: "SACKS, ZOHAR" 
Date: Tuesday, 18 July 2017 at 16:38
To: "zhao.huab...@zte.com.cn" 
Cc: ZAHI KAPELUTO , "onap-discuss@lists.onap.org" 
, "yuan@zte.com.cn" , 
"Rozin, Eden" 
Subject: RE: [onap-discuss] CSAR from SDC

At current time each import will create new VSP version and deletes (with 
alert) the previous data

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
Sent: Tuesday, July 18, 2017 10:34 AM
To: zhao.huab...@zte.com.cn
Cc: zk0...@intl.att.com onap-discuss@lists.onap.org yuan@zte.com.cn 
er4...@intl.att.com
Subject: Re: [onap-discuss] CSAR from SDC


One more question about SDC:

 If I import the same heat package into SDC for multiple times, how does SDC 
handle it? Will SDC create different version of the same VF, or update the 
existing VF, or just take them as different VNs?
Original Mail
Sender: zhaohuabing10201488
To:  >
CC:  > 
> 
>yuanhu10090474
Date: 2017/07/18 11:12
Subject: Re: [onap-discuss] CSAR from SDC



Hi Michael,



Could we discuss these questions at today's meeting?



Thanks,

Huabing






Sender:  >
To: zhaohuabing10201488 > 
>
CC: MengZhaoXing10024238YuanHu10090474
Date: 2017/07/17 18:08
Subject: Re:CSAR from SDC


+Eden,Zahi
Please assit

 Original Message 
From: zhao.huab...@zte.com.cn
Date: Mon, Jul 17, 2017, 12:24
To: "Lando,Michael" >
CC: meng.zhaoxi...@zte.com.cn, 

[onap-discuss] Robot log file is asking for password to open

[Tapan Majhi]

I have installed the onap environment from 1.1-STAGING-latest image.
Trying to run robot testcase and see the logs from 
http://{robot-ip}:88/log.html
Its asking for username and password. Anyone aware of it ?


Regards,
Tapan M
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 


Amdocs Development Centre India Private Limited having CIN: 
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A 
limited liability partner­ship with LLP Identification Number: AAI-6901 
effective 28th Feb 2017)
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss