date:20180202

Re: [onap-discuss] [vfc]VF-C VoLTE Configuration

2018-02-02 Thread Chengli Wang

Hi Manoj,

For 1st question,
After distributing the services which designed by SDC. You should use 
UUI-Services-VNF/NS Packages to onboard these packages to VF-C.
The issue you mentioned I guess the reason is that VF-C catalog component can 
not talk with SDC. You can check the config 
file(/service/vfc/nfvo/catalog/catalog/pub/config/config.py), located in 
*vfc_catalog* container. Pay attention to two parameters, they are 'MSB ip’ and 
'sdc url’. They should complied  with your EVN.

For the second question,
The VL used to connect VNFs together will be consumed by VFC components, VFC 
will create the virtual network/subnet via MultiCloud according to the VL 
models. No additional CSAR packages for VL needed.

Regards,
Chengli

> 在 2018年2月2日，下午9:37，Manoj K Nair  写道：
> 
> Hi, 
>  
> I am referring to VoLTE demo here 
> 
>  and have two questions 
> 1)  I tried to onboard a couple of VNF packages using the UUI on SDC 
> (this is not shown in demo video) . I navigated to UUI -> Services-> VNF/NS 
> Packages and then clicked on OnBoard. I got an error “Failed to query 
> artifacts from SDC” . Not sure if this is the right procedure to onboard CSAR 
> packages to VF-C 
> 2)  In the demo video at 14:04 Service Network (VL) is being selected. 
> How this Service network can be created? I noticed that Service network is a 
> VL (zte ext VL) with Service network capability. How this VL can be created ? 
> Any additional CSARs to be loaded ? Appreciate if some one from VoLTE use 
> case clarify this? 
>  
> Regards
>  
> Manoj 
>  
> 
> 
> The information transmitted herein is intended only for the person or entity 
> to which it is addressed and may contain confidential, proprietary and/or 
> privileged material. Any review, retransmission, dissemination or other use 
> of, or taking of any action in reliance upon, this information by persons or 
> entities other than the intended recipient is prohibited. If you received 
> this in error, please contact the sender and delete the material from any 
> computer.

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

[onap-discuss] VF2F Info

2018-02-02 Thread Kenny Paul

For ease of facilitation it would be best if the version of zoom you are using 
is 4.1.8826.0925 or higher on Mac or Windows.
(before you ask, the new features haven’t been ported to the linux version of 
zoom yet ;-)
To update the Mac click the update button when you view “About zoom”
To update Windows, go to https://zoom.us/download#client_4meeting 
 and down load and install the “Zoom 
Client for Meetings”


Agenda: ONAP VF2F 


Bridge 1 Sessions:  https://zoom.us/j/702887735 

 
China 22:00 – Midnight
India 19:30 – 21:30
Israel 16:00 – 18:00
UTC 14:00 - 16:00
US East 09:00 – 11:00
US Pacific  06:00– 08:00

join by phone: 
Dial(for higher quality, dial a number based on your current location): 
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) 
or +1 855 880 1246 (Toll Free) 
Webinar ID: 702 887 735 
International numbers available: 
https://zoom.us/zoomconference?m=4U63LP9_uhXJxBg2Ma9uBH3t7jnICnUn 

 



Best Regards, 
-kenny

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

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

[onap-discuss] [AAI][OOM] Zoom session to assist AA with Kubernetes PV changes for Cassandra 3 node cluster (20180202 and 20180126 meets)

2018-02-02 Thread Michael O'Brien

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Michael O'Brien:MAILTO:frank.obr...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:Team\,\n   In the last 2 calls there were assist
 ance requests on OOM from the AAI team on bringing up a 3 node Cassandra c
 luster – specifically PV issues related to config.  There are several di
 scussions going on.  We decided in the call that a zoom session would be g
 ood to run the yaml changes life and bring in everyone involved and intere
 sted – this Monday right after the vF2F.\n\nhttps://zoom.us/j/7939937123
 \n\nsee\nhttps://wiki.onap.org/display/DW/2018-02-02+AAI+Weekly+Meeting+no
 tes\nhttps://jira.onap.org/browse/AAI-539\nhttps://jira.onap.org/browse/OO
 M-591\n\nJames\, just verifying in prep of the meet – this is Amsterdam 
 as 591 is set to – not master/Beijing right – the meeting note mention
 s Beijing.\n\nDiscussions\nhttps://lists.onap.org/pipermail/onap-discuss/2
 018-January/007392.html\nhttps://lists.onap.org/pipermail/onap-discuss/201
 8-January/007487.html\n\n\n\n
SUMMARY;LANGUAGE=en-US:[AAI][OOM] Zoom session to assist AA with Kubernet
 es PV changes for Cassandra 3 node cluster (20180202 and 20180126 meets)
DTSTART;TZID=Eastern Standard Time:20180205T11
DTEND;TZID=Eastern Standard Time:20180205T12
UID:04008200E00074C5B7101A82E008A0F297AA5E9CD301000
 01000A2F65C96A02FF0478840E23E46C91290
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180203T004732Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/7939937123
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1013065698
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [modeling]Modeling call next week

2018-02-02 Thread denghui (L)

Hi Kenny

From latest program: https://wiki.onap.org/display/DW/VF2F+Feb.+5-8%2C+2017
We are starting from 9:30am eastern time , which is 10:30pm Beijing time

Thanks  a lot for your reminder

Best regards,

DENG Hui

From: Kenny Paul [mailto:kp...@linuxfoundation.org]
Sent: Saturday, February 3, 2018 3:29 AM
To: denghui (L) 
Cc: onap-discuss@lists.onap.org; onap-...@lists.onap.org P 
; Rittwik Jana ; 邓灵莉 

Subject: Re: [modeling]Modeling call next week

Hi Deng,
I'll cxl next week's call even though these requests should always be routed 
throgh the wiki page
Meeting Requests, Changes, Hosting & 
Recording

I don’t understand the sentence that follows however. Not sure if this is a 
request for a change, or what the intent is.
>> we will have our modeling subcommittee session on Wednesday 9am eastern 
>> time, 10pm Beijing time.

Thanks!

Best Regards,
-kenny

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


On Feb 2, 2018, at 4:46 AM, denghui (L) 
> wrote:

Hello all

Our modeling subcommittee call will be cancelled next week due to vf2f,

Hi Kenny,

could you kindly help to cancel next week call, thanks a lot

and we will have our modeling subcommittee session on Wednesday 9am eastern 
time, 10pm Beijing time.

1)  Resource IM Xu Yang

2)  Service IM Maopeng Zhang

3)  Data modeling Anatoly

4)  Centralized Parser Atul

5)  Modeling tools Nigel

6) Projects follow up modeling spec discussion (Modeling contact from each 
Project)

Let me know if you have any other suggestions.



Thanks a lot



DENG Hui



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

[onap-discuss] Community Scribes Needed For VF2F

2018-02-02 Thread Kenny Paul

As I will be facilitating the VF2F note takers from the Community will be 
required to capture key decisions and action items.
Please let me know (including your IRC handle if not obvious from your name), 
so that I can add you as a chairperson.
Thank you.

Best Regards, 
-kenny

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

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

[onap-discuss] Canceled event: [multicloud] Weekly (Updated Dec. 6, 2017) @ Weekly from 5am to 6am on Friday (PST) (onap-discuss@lists.onap.org)

2018-02-02 Thread 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:20171208T05
DTEND;TZID=America/Los_Angeles:20171208T06
RRULE:FREQ=WEEKLY;BYDAY=FR
DTSTAMP:20180202T222621Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:1hnooj4v7un90rjhl5in7si...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=lx
 in...@vmware.com;X-NUM-GUESTS=0:mailto:lxin...@vmware.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
CREATED:20171207T011632Z
DESCRIPTION:Updated Dec. 6\, 2017\n\nONAP Meeting 3 is inviting you to a sc
 heduled Zoom meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: http
 s://zoom.us/j/587662385\n\nOr iPhone one-tap :\nUS: +16699006833\,\,587
 662385#  or +16465588656\,\,587662385# \nOr Telephone:\nDial(for higher
  quality\, dial a number based on your current location)：\nUS: +1 6
 69 900 6833  or +1 646 558 8656  or +1 877 369 0926 (Toll Free) or +1 855 8
 80 1246 (Toll Free)\nMeeting ID: 587 662 385\nInternational numbers
  available: https://zoom.us/zoomconference?m=6Sb3YBZOK2xsIM1KYlXbkQxXkgtFGk
 gS\n\n
LAST-MODIFIED:20180202T222620Z
LOCATION:https://zoom.us/j/587662385
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[multicloud] Weekly (Updated Dec. 6\, 2017)
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

[onap-discuss] Requesting ONAP Program Committee membership for ONS Developer Forum

2018-02-02 Thread Kenny Paul

As you know the next physical F2F opportunity will occur at ONS March.  

The Developer Forum on Monday the 26th & Tuesday the 27th will be comprised of 
time for both LFN Cross-Project plenary sessions and time dedicated for ONAP 
community breakout sessions.

I am looking for 3-4 community members to form an ad-hoc Program committee to 
make the selections of content and scheduling of ONAP breakout topics and for 
any presentations that would be appropriate for ONAP to share during the 
plenary sessions.

Please contact me directly.
Thank you!

Best Regards, 
-kenny

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

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

[onap-discuss] Updated invitation: ONAP VF2F Bridge 1 Sessions @ Daily from 6am to 8am from Mon Feb 5 to Thu Feb 8 (PST) (onap-discuss@lists.onap.org)

2018-02-02 Thread kpaul

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
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:20180205T06
DTEND;TZID=America/Los_Angeles:20180205T08
RRULE:FREQ=DAILY;UNTIL=20180209T075959Z
DTSTAMP:20180202T213055Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:7tglfeaq312052vlgqkh1nk...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=onap-discuss@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@list
 s.onap.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=kp...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:kpaul@linuxfoundation.o
 rg
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=onap-...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-...@lists.onap.org
CREATED:20180108T151953Z
DESCRIPTION:Beijing Release Planning Virtual Face-2-Face for all project te
 amsJoin from a PC\, Mac\, iPad\, iPhone or Android device:<
 b>Please click this URL to join. https://www.google.com/url?q=http
 s%3A%2F%2Fzoom.us%2Fj%2F702887735\;sa=D\;ust=1517614004837000\;
 usg=AFQjCNEMjDMsKH9SC2VkO3a9Q2IPLKZ0ug" target="_blank">https://zoom.us/j/7
 02887735Or join by phone:Dial(for higher quality\, dial
  a number based on your current location):US: +1 669 900 6833  or +
 1 646 558 8656  or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Fre
 e)Webinar ID: 702 887 735International numbers available: https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fzoomconference%3Fm%3D4
 U63LP9_uhXJxBg2Ma9uBH3t7jnICnUn\;sa=D\;ust=1517614004837000\;us
 g=AFQjCNEUEE-AyTkjmUDYWtxNN0hdGM-fCg" target="_blank">https://zoom.us/zoomc
 onference?m=4U63LP9_uhXJxBg2Ma9uBH3t7jnICnUn\n\n-::~:~::~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nPlease do
  not edit this section of the description.\n\nView your event at https://ww
 w.google.com/calendar/event?action=VIEW=N3RnbGZlYXEzMTIwNTJ2bGdxa2gxbms
 xa2wgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=NzIjbGludXhmb3VuZGF0aW9uLm9yZ
 18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tNTk3
 M2VjYjIzOGVlMjNlZGUzZmQ2MjM1ODdiYTE5YTU3OGIyMjgyNg=America/Los_Angeles&
 hl=en.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180202T213055Z
LOCATION: https://zoom.us/j/702887735 
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:ONAP VF2F Bridge 1 Sessions
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] [dcae][dcaegen2][holmes] A Question on Auto Scailing of DCAE Microservices

2018-02-02 Thread JI, LUSHENG (LUSHENG)

Roger,

Thanks for the pointers.

Guangrong,

The details of the Kubernetes plan for DCAE is still work-in-progress.  Here 
are some of highlights for service components.

  1.  Will support Kubernetes based scaling and resilience mechanism for 
dockerized service components.
 *   This implies that the container/containers of a service component will 
be packaged as pod.  The resilience is expected to be provided by Kubernetes 
cluster.
 *   The Kubernetes based scaling support may need additional support from 
service component developer. For example, if a service component is stateless, 
for which each instance behaves exactly the same as the next, are 
“scaling-ready”.  Load can be distributed to any instance and the result would 
be the same.  However, if the service component keeps states, multiple replicas 
of this service component may have different local states if not handled 
carefully.  The actual mechanism to ensure state synchronization is application 
dependent.  But one typical approach is to push “states” to an external service 
such as a DB, or persistent volume, or a distributed kv store, etc, and states 
are loaded into individual replica when needed (e.g. startup) so different 
replicas get the state view from the same copy.
 *   In terms of multiple replicas subscribing to the same message router 
topic, there is a way to distribute the load.  That is, each replica uses the 
same “groupid” but different “userid”.  Message router will consider a message 
received by a group when it is received by any user of the group.  This way we 
can avoid the same message being delivered to multiple replicas.
  2.  Our goal is to maintain the interfaces that how a service component 
interacts with the rest of DCAE the same, e.g. how your component gets deployed 
and how your component receives configuration updates, etc.
  3.  How the scaling trigger arrives and the actual scaling (i.e. more 
replicas) is handled by external mechanisms.  Service components themselves do 
not need to worry about that.

We hope to have more details to share the next week, and set up focus meeting 
discussing more.

Thanks,
Lusheng


From: Roger Maitland 
Date: Friday, February 2, 2018 at 1:48 PM
To: "fu.guangr...@zte.com.cn" , "JI, LUSHENG 
(LUSHENG)" 
Cc: "onap-discuss@lists.onap.org" , 
"tang.pe...@zte.com.cn" 
Subject: RE: [onap-discuss] [dcae][dcaegen2][holmes] A Question on Auto 
Scailing of DCAE Microservices

Guangrong,

I don’t have an answer in the context of the DCAE controller but OOM/Kubernetes 
has facilities to help build a Holmes cluster in the containerized version of 
DCAE (which is being worked on).  The cluster can be static (which is believe 
is what most projects intend for Beijing) or dynamic (the OOM team would love 
to work with you on this). Here are some links I hope you find useful:

  *   OOM Scaling: 
https://wiki.onap.org/display/DW/Beijing+Scope#BeijingScope-Scale-clusterONAPservicestoenableseamlessscaling
  *   K8s auto-scaling: 
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/

Here is a sample of how an auto-scaler is configured:
apiVersion: autoscaling/v2beta1
kind: HorizontalPodAutoscaler
metadata:
  name: php-apache
  namespace: default
spec:
  scaleTargetRef:
apiVersion: apps/v1beta1
kind: Deployment
name: php-apache
  minReplicas: 1
  maxReplicas: 10
  metrics:
  - type: Resource
resource:
  name: cpu
  targetAverageUtilization: 50
status:
  observedGeneration: 1
  lastScaleTime: 
  currentReplicas: 1
  desiredReplicas: 1
  currentMetrics:
  - type: Resource
resource:
  name: cpu
  currentAverageUtilization: 0
  currentAverageValue: 0

The OOM team would be happy to work with you on implementing this.

Cheers,
Roger
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
fu.guangr...@zte.com.cn
Sent: Friday, February 2, 2018 2:58 AM
To: l...@research.att.com
Cc: onap-discuss@lists.onap.org; tang.pe...@zte.com.cn
Subject: [onap-discuss] [dcae][dcaegen2][holmes] A Question on Auto Scailing of 
DCAE Microservices


Lusheng,



The Holmes team is currently working on the auto scaling plans for Holmes. We 
need to confirm something

[onap-discuss] SO issues with keystone

2018-02-02 Thread PLATANIA, MARCO (MARCO)

All,

I’m instantiating VNFs in a remote OpenStack lab called RegionTwo. I modified 
mso-docker.config appropriately. See below:

"mso-po-adapter-config":
{
  "identity_services":
  [
{
  "dcp_clli": "DEFAULT_KEYSTONE",
  "identity_url": "http://135.197.225.10:35357/v2.0;,
  "mso_id": "admin",
  "mso_pass": "a83e2b8446193c5ac450d84f0f1dc711",
  "admin_tenant": "service",
  "member_role": "admin",
  "tenant_metadata": "true",
  "identity_server_type": "KEYSTONE",
  "identity_authentication_type": "USERNAME_PASSWORD"
},
{
  "dcp_clli": "DEFAULT_KEYSTONE2",
  "identity_url": "http:// 135.197.220.71:5000/v3",
  "mso_id": "marco",
  "mso_pass": "f461eb3230f0b4b7b1ce8ed018da155f",
  "admin_tenant": "service",
  "member_role": "admin",
  "tenant_metadata": "true",
  "identity_server_type": "KEYSTONE",
  "identity_authentication_type": "USERNAME_PASSWORD"
}
  ],

  "cloud_sites":
  [
{
  "id": "RegionOne",
  "aic_version": "2.5",
  "lcp_clli": "RegionOne",
  "region_id": "RegionOne",
  "identity_service_id": "DEFAULT_KEYSTONE"
},
{
  "id": "RegionTwo",
  "aic_version": "2.5",
  "lcp_clli": "RegionTwo",
  "region_id": "RegionTwo",
  "identity_service_id": "DEFAULT_KEYSTONE2"
}
  ],

When I try to install a VNF, I receive the following error from SO:

2018-02-02T18:21:48.847Z|0d1b96a0-9fbe-4d1a-a197-4eebd4041c5f|Thread-282|CreateVfModule|BPELClient|Openstack||ERROR|DataError|Openstack
 Keystone Error on TokenAuth|MSO-RA-9202E Exception communicating with 
Openstack Keystone Error on TokenAuth: Error [code=404, title=Not Found, 
message=The resource could not be found.]: {1}

2018-02-02T18:21:48.848Z|0d1b96a0-9fbe-4d1a-a197-4eebd4041c5f|Thread-282|CreateVfModule|BPELClient|Openstack||ERROR|AvailabilityError|Connection
 Exception|MSO-RA-9202E Exception communicating with OpenStack: Openstack 
Exception on Token request: 404 Not Found: The resource could not be found.

2018-02-02T18:21:48.849Z|0d1b96a0-9fbe-4d1a-a197-4eebd4041c5f|Thread-282|CreateVfModule|BPELClient|OpenStack|queryStack|ERROR|DataError|Exception
 - queryStack|MSO-RA-9227E Exception while query VNF:Vfmodule_vLB-0201 in 
RegionTwo/c236140a3dff4911bb4c7c86940616cc

2018-02-02T18:21:48.850Z|0d1b96a0-9fbe-4d1a-a197-4eebd4041c5f|Thread-282|CreateVfModule|BPELClient|OpenStack|queryStack|ERROR|DataError|Exception
 - queryStack|MSO-RA-9200E Exception: 404 Not Found: The resource could not be 
found. - at 
org.openecomp.mso.openstack.utils.MsoCommonUtils.keystoneErrorToMsoException(MsoCommonUtils.java:173)
 - at 
org.openecomp.mso.openstack.utils.MsoHeatUtils.getHeatClient(MsoHeatUtils.java:996)
 - at 
org.openecomp.mso.openstack.utils.MsoHeatUtils.queryStack(MsoHeatUtils.java:646)
 - at 
org.openecomp.mso.adapters.vnf.MsoVnfAdapterImpl.createVfModule(MsoVnfAdapterImpl.java:788)
 - at 
org.openecomp.mso.adapters.vnf.VnfAdapterRest$CreateVfModuleTask.run(VnfAdapterRest.java:388)
 - at java.lang.Thread.run(Thread.java:748) -

Does someone know when this error happens in SO? It seems resource not found 
when talking to keystone, but the OpenStack lab has all the endpoints 
configured correctly and also RegionTwo/c236140a3dff4911bb4c7c86940616cc 
exists. CLI operations against OpenStack work as expected. Note that this 
OpenStack lab uses Keystone v3. Is that supported in SO?

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

Re: [onap-discuss] [onap-tsc] [modeling]Modeling call next week

2018-02-02 Thread Kenny Paul

Everything Monday through Thursday next week between 6am and 8am pacific time 
clashes with the VF2F. 
:-)

Best Regards, 
-kenny

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

> On Feb 2, 2018, at 11:06 AM, Parviz Yegani  wrote:
> 
> Hi Deng Hui,
>  
> Wed 6:00AM PST clashes with the SDNC weekly call. We should avoid this 
> overlap for next week’s vF2F if possible.
>  
> Thank you
> Parviz
>  
> ---
> PARVIZ YEGANI, PhD 
> Chief SDN/NFV Architect
> CTO Office, Cloud Network Solutions
>  
> FutureWei Technologies, Inc.
> 2330 Central Express Way
> Santa Clara, CA 95050, USA
> Phone: +1 (408) 330-4668
> Mobile : +1 (408) 759-1973
> parviz.yeg...@huawei.com 
>  
>  
>  
> From: onap-tsc-boun...@lists.onap.org 
>  
> [mailto:onap-tsc-boun...@lists.onap.org 
> ] On Behalf Of denghui (L)
> Sent: Friday, February 02, 2018 4:46 AM
> To: onap-discuss@lists.onap.org ; 
> onap-...@lists.onap.org  P 
> >
> Cc: Rittwik Jana >
> Subject: [onap-tsc] [modeling]Modeling call next week
>  
> Hello all
>  
> Our modeling subcommittee call will be cancelled next week due to vf2f,
>  
> Hi Kenny, 
>  
> could you kindly help to cancel next week call, thanks a lot
>  
> and we will have our modeling subcommittee session on Wednesday 9am eastern 
> time, 10pm Beijing time.
> 1)  Resource IM Xu Yang
> 
> 2)  Service IM Maopeng Zhang
> 
> 3)  Data modeling Anatoly
> 
> 4)  Centralized Parser Atul
> 
> 5)  Modeling tools Nigel
> 
> 6) Projects follow up modeling spec discussion (Modeling contact from each 
> Project)
> 
> Let me know if you have any other suggestions.
>  
> Thanks a lot
>  
> DENG Hui
>  
> ___
> ONAP-TSC mailing list
> onap-...@lists.onap.org 
> https://lists.onap.org/mailman/listinfo/onap-tsc 
> 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Canceled event: [modeling] Project Bi-Weekly @ Tue Feb 6, 2018 6am - 7am (PST) (onap-discuss@lists.onap.org)

2018-02-02 Thread 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:20180206T06
DTEND;TZID=America/Los_Angeles:20180206T07
DTSTAMP:20180202T193519Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:458082f5m1knfkhui30a916...@google.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
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=de
 nghu...@huawei.com;X-NUM-GUESTS=0:mailto:denghu...@huawei.com
RECURRENCE-ID;TZID=America/Los_Angeles:20180206T06
CREATED:20170718T121010Z
DESCRIPTION:ONAP Meeting 5 is inviting you to a scheduled Zoom meeting. \n\
 nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/137904496\n
 \nOr iPhone one-tap (US Toll):  +14086380968\,137904496# or +16465588656\,1
 37904496#\n\nOr Telephone:\nDial: +1 408 638 0968 (US Toll) or +1 646 5
 58 8656 (US Toll)\nMeeting ID: 137 904 496\nInternational numbers a
 vailable: https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a
 \n\n
LAST-MODIFIED:20180202T193518Z
LOCATION:https://zoom.us/j/137904496
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[modeling] Project Bi-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] [modeling]Modeling call next week

2018-02-02 Thread Kenny Paul

Hi Deng,
I'll cxl next week's call even though these requests should always be routed 
throgh the wiki page
Meeting Requests, Changes, Hosting & Recording 


I don’t understand the sentence that follows however. Not sure if this is a 
request for a change, or what the intent is.
>> we will have our modeling subcommittee session on Wednesday 9am eastern 
>> time, 10pm Beijing time.

Thanks!
Best Regards, 
-kenny

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

> On Feb 2, 2018, at 4:46 AM, denghui (L)  wrote:
> 
> Hello all
> 
> Our modeling subcommittee call will be cancelled next week due to vf2f,
> 
> Hi Kenny,
> 
> could you kindly help to cancel next week call, thanks a lot
> 
> and we will have our modeling subcommittee session on Wednesday 9am eastern 
> time, 10pm Beijing time.
> 
> 1)  Resource IM Xu Yang
> 
> 2)  Service IM Maopeng Zhang
> 
> 3)  Data modeling Anatoly
> 
> 4)  Centralized Parser Atul
> 
> 5)  Modeling tools Nigel
> 
> 6) Projects follow up modeling spec discussion (Modeling contact from each 
> Project)
> 
> Let me know if you have any other suggestions.
> 
>  
> 
> Thanks a lot
> 
>  
> 
> DENG Hui
> 
>  
> 

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

Re: [onap-discuss] [Onap-release] M2 Requirement for JUnit code coverage

2018-02-02 Thread Gildas Lanilis

Hi,

Thanks all for sharing your feedback.

I think we all recognize that providing test coverage is something that cannot 
be achieve overnight hence the reason why we have built the checklists and the 
periodic milestones. I guess none of us want to be in the same situation we 
were in M4 for Amsterdam in Paris, negotiating extra time to reach the target.

The basic idea is to start early, unit testing should not be an after thoughts 
but rather baked in. Some repos have already achieve their 50% goals. I can 
even some repos are over 80% code coverage. Excellent work.

Listening to your feedback, I would like to propose the community (the TSC will 
need to decide here) to set 50% code coverage as a stretch goal for M2 and M3 
and a mandatory goal for M4. In the M2 and M3 checklist simply provide a 
screenshot of your progress.

Regarding repos that require Python, LF told me the work is in progress. I am 
hoping to learn a firm date from LF next week during the V F2F. In the 
meantime, as we did in Amsterdam, provide a screenshot of your local code 
coverage.

Here is the link to 
Sonar
 to visualize the status (you can sort  it out by “Overall Coverage”, by “Name” 
or by “Last Analysis” date).

Let me know if you have any questions, I will be glad to help.

Thanks,

Gildas

ONAP Release Manager

1 415 238 6287

-Original Message-
From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Thursday, February 01, 2018 6:45 AM
To: Seshu m ; Gildas Lanilis 

Cc: onap-rele...@lists.onap.org
Subject: Re: [Onap-release] M2 Requirement for JUnit code coverage

Gildas,

Same here.

Please consider moving 50% as gating requirement for M4.

Thanks,

Lusheng Ji

On 2/1/18, 6:13 AM, "onap-release-boun...@lists.onap.org on behalf of Seshu 
m" 
>
 wrote:

Hi Gildas,

I share the same thoughts, we have the functional aspects being worked upon 
till M2 and still a lot of discussions/clarifications are required there.

So, it would be better to consider 50% code coverage for M4 and 30% for M2.

Best regards

Seshu Kumar M

Huawei Technologies India Pvt, Ltd.

本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁

止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中

的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！

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!

-Original Message-

From: 
onap-release-boun...@lists.onap.org 
[mailto:onap-release-boun...@lists.onap.org] On Behalf Of Lefevre, Catherine

Sent: Thursday, February 01, 2018 5:40 AM

To: Shankaranarayanan P N

Cc: onap-rele...@lists.onap.org

Subject: Re: [Onap-release] M2 Requirement for JUnit code coverage

Gildas,

I agree with the feedback provided by the PTLs

The 50% test coverage is a new Beijing requirement as part of S3P/Security 
therefore it should be treated as any other Beijing code deliverable i.e being 
gated at M4 code freeze milestone.

I am not aware that SP3 requirements are expected to be completed earlier.

30% test coverage should be gated at M2/M3 milestone.

Please also note that non-java test coverage can not yet been measured.

We really need to progress on this issue as well.

Best regards

Catherine

Le 31 janv. 2018 à 15:14, Shankaranarayanan P N 
>>
 a écrit :

Hi Gildas,

I have the same concerns that Jimmy and Randa raised here. In particular, 
the seed code for OOF is being upstreamed for the first time in Beijing 
Release. While we do have unit test coverage as one of our priorities in R2, we 
had planned progressive test coverage increase to happen as we move along 
towards M4. Given this, it would be very challenging

Re: [onap-discuss] [modeling]Modeling call next week

2018-02-02 Thread Parviz Yegani

Hi Deng Hui,

Wed 6:00AM PST clashes with the SDNC weekly call. We should avoid this overlap 
for next week's vF2F if possible.

Thank you
Parviz

---
PARVIZ YEGANI, PhD
Chief SDN/NFV Architect
CTO Office, Cloud Network Solutions

FutureWei Technologies, Inc.
2330 Central Express Way
Santa Clara, CA 95050, USA
Phone: +1 (408) 330-4668
Mobile : +1 (408) 759-1973
parviz.yeg...@huawei.com



From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of denghui (L)
Sent: Friday, February 02, 2018 4:46 AM
To: onap-discuss@lists.onap.org; onap-...@lists.onap.org P 

Cc: Rittwik Jana 
Subject: [onap-tsc] [modeling]Modeling call next week

Hello all

Our modeling subcommittee call will be cancelled next week due to vf2f,

Hi Kenny,

could you kindly help to cancel next week call, thanks a lot

and we will have our modeling subcommittee session on Wednesday 9am eastern 
time, 10pm Beijing time.

1)  Resource IM Xu Yang

2)  Service IM Maopeng Zhang

3)  Data modeling Anatoly

4)  Centralized Parser Atul

5)  Modeling tools Nigel

6) Projects follow up modeling spec discussion (Modeling contact from each 
Project)
Let me know if you have any other suggestions.

Thanks a lot

DENG Hui

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

Re: [onap-discuss] [oom] Question on DCAE deployment using OOM

2018-02-02 Thread Roger Maitland

Viswa, as Alexis mentioned the DCAE and OOM teams are working towards a fully 
containerized version of DCAE.  The only component remaining to be 
containerized is the DCAE controller but the Cloudify team has recently told us 
that they are working on completing this.  Hopefully with all of us working 
together we’ll be able to get this done quickly.

Cheers,
Roger

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Wednesday, January 31, 2018 8:16 AM
To: Kumar Skand Priya, Viswanath V 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [oom] Question on DCAE deployment using OOM

Hi,

Let’s clarify one thing, OOM is the medium to deploy ONAP. DCAE doesn’t provide 
a way to be deployed in Kubernetes for now, hence OOM is not able to do this.

What OOM does is create the HEAT stack in OpenStack, HEAT stack that will 
create a VM running the dcae-boostrap container, which will then deploy the 
whole DCAE. OOM has created a wrapper on top of this so one can seamlessly 
deploy ONAP using OOM, as it’s done with HEAT. Please see the attachment here: 
https://jira.onap.org/browse/OOM-508 explaining the implementation.

DCAE team and OOM team are working together to see how we can migrate DCAE 
components into Kubernetes deployment/services.  That work is still in 
progress, and I don’t have a clear view of the timeline for completion. Until 
this is done, ONAP will still requires a VIM to deploy DCAE.

Thanks,
Alexis



On Jan 31, 2018, at 2:17 AM, Kumar Skand Priya, Viswanath V via onap-discuss 
> wrote:

Dear OOM Team,

We found that, even-though OOM deploys DCAE bootstrap container inside a POD, 
the bootstrap container in-turn deploys other DCAE components as VMs in 
underlying VIM ( openstack ).

Would like to know, why doesn't entire DCAE run under kubern8s mode? and also 
what's the story of DCAE's LCM with OOM, since some parts of DCAE are still in 
VM mode ?

BR,
Viswa

[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]

Viswanath Kumar Skand Priya
Architect
Verizon India ( VDSI )

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

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

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

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

Re: [onap-discuss] [dcae][dcaegen2][holmes] A Question on Auto Scailing of DCAE Microservices

2018-02-02 Thread Roger Maitland

Guangrong,

I don’t have an answer in the context of the DCAE controller but OOM/Kubernetes 
has facilities to help build a Holmes cluster in the containerized version of 
DCAE (which is being worked on).  The cluster can be static (which is believe 
is what most projects intend for Beijing) or dynamic (the OOM team would love 
to work with you on this). Here are some links I hope you find useful:

  *   OOM Scaling: 
https://wiki.onap.org/display/DW/Beijing+Scope#BeijingScope-Scale-clusterONAPservicestoenableseamlessscaling
  *   K8s auto-scaling: 
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/

Here is a sample of how an auto-scaler is configured:
apiVersion: autoscaling/v2beta1
kind: HorizontalPodAutoscaler
metadata:
  name: php-apache
  namespace: default
spec:
  scaleTargetRef:
apiVersion: apps/v1beta1
kind: Deployment
name: php-apache
  minReplicas: 1
  maxReplicas: 10
  metrics:
  - type: Resource
resource:
  name: cpu
  targetAverageUtilization: 50
status:
  observedGeneration: 1
  lastScaleTime: 
  currentReplicas: 1
  desiredReplicas: 1
  currentMetrics:
  - type: Resource
resource:
  name: cpu
  currentAverageUtilization: 0
  currentAverageValue: 0

The OOM team would be happy to work with you on implementing this.

Cheers,
Roger
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
fu.guangr...@zte.com.cn
Sent: Friday, February 2, 2018 2:58 AM
To: l...@research.att.com
Cc: onap-discuss@lists.onap.org; tang.pe...@zte.com.cn
Subject: [onap-discuss] [dcae][dcaegen2][holmes] A Question on Auto Scailing of 
DCAE Microservices


Lusheng,



The Holmes team is currently working on the auto scaling plans for Holmes. We 
need to confirm something with you.



To my understanding, the microservice should only focus on how to maintain and 
balance its data flow rather than how the docker containers/vms are scaled by 
their controller. As a DCAE application, I think it's DCAE controller's 
responsiblity to determine when and how to scale in or scale out Holmes 
instances. Is that correct?



If what my understanding is correct, does DCAE have any specific requirements 
regarding collecting the status and metrics of its microservices?



Regards,

Guangrong








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] Zoom update

2018-02-02 Thread Kenny Paul

There is a recent update to zoom that is required to continue screen sharing.
If you see a note about new version available, please install it.


Best Regards, 
-kenny

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

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

Re: [onap-discuss] [modeling] Whether How and when we should move to Github for modeling spec update process

2018-02-02 Thread Michela Bevilacqua

+1,  favorable to a Git for ONAP IM in Papyrus.

ONAP modeling subcommittee can be responsible for this with committers based on 
commit operation in papyrus.
Use GenDoc to document the model.
Approach it in Beijing release, learn from the experience and  be more 
effective in Casablanca release.

BR
Michela

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Brian Hedstrom
Sent: den 2 februari 2018 16:12
To: denghui (L) 
Cc: jessie jewitt ; 
onap-discuss@lists.onap.org; onap-...@lists.onap.org P 
Subject: Re: [onap-discuss] [modeling] Whether How and when we should move to 
Github for modeling spec update process

Hi Deng,
I'm in favor of using Git for model development.
Do we want to add a Poll page to the wiki to track participant voting on this 
topic?

Thanks
Brian

On Wed, Jan 31, 2018 at 7:31 PM, denghui (L) 
> wrote:
Hello modeling subcommittee,

Many Thanks to Jessie’s kind presentation on GitHub for Papyrus model.
https://wiki.onap.org/display/DW/Modeling+sub-committee+Contributions
https://wiki.onap.org/download/attachments/16003450/GitHub%20for%20Papyrus%20Model.pptx?api=v2

Due to time limitation, we would like to discussion in the list together with 
the communities whether, how and when we should move to Github to manage the 
modeling spec update process.

Thanks a lot for your advice
Best regards,

DENG Hui



--
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oam.technology
brian.hedst...@oamtechnologies.com
720-470-7091
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

2018-02-02 Thread Elie Dit Cosaque, David (Nokia - US/Irving)

Thanks, for the link,
David

-Original Message-
From: Determe, Sebastien [mailto:sd3...@intl.att.com] 
Sent: Friday, February 2, 2018 2:32 AM
To: Elie Dit Cosaque, David (Nokia - US/Irving) 
; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

Hi David,
Have a look to this:
https://wiki.onap.org/download/attachments/25430497/PresentationCLAMP_ONAP.mp4?version=1=1517476892000=v2

Seb

-Original Message-
From: Elie Dit Cosaque, David (Nokia - US/Irving) 
[mailto:david.elie_dit_cosa...@nokia.com] 
Sent: Thursday, February 01, 2018 6:56 PM
To: Determe, Sebastien ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

Hi Seb, Yury,

We finally have found a working openssl command:

openssl aes-128-ecb -K aa3871669d893c7fb8abbcda31b88b4f   -e -in in.txt -out 
out_ecb.txt

in.txt: contains the data to encrypt, in our case 
Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U

The encrypted output (out_ecb.txt) is in binary format so I used the bless hex 
editor to copy the value. 

After changing the encrypted password, we see no authentication error and can 
get the list of services from SDC. 

I was expecting CLAMP GUI to somehow retrieve the clamp policies from the 
policy VM and present them in the CLAMP designer with an option to start/stop. 
Do we need to create a template and model ? Do you know about a procedure on 
how to do this for the vFWCL demo.

Thanks,

David.

-Original Message-

From: Elie Dit Cosaque, David (Nokia - US/Irving) 

Sent: Wednesday, January 31, 2018 3:27 PM

To: 'Determe, Sebastien' ; onap-discuss@lists.onap.org

Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

Thanks Seb and Yuri

Could you please share the complete openssl command line to generate the 
encrypted password. Our SDC password is Basic 
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=

So base64 decoded:

vid:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U

How can we get the encrypted hex from 
Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U? I always end up with padding error 
when I try (I have done many tries ☹).

Thanks,

David.

-Original Message-

From: Determe, Sebastien [mailto:sd3...@intl.att.com]

Sent: Wednesday, January 31, 2018 2:17 PM

To: Elie Dit Cosaque, David (Nokia - US/Irving) 
; onap-discuss@lists.onap.org

Subject: Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

Yes that is the key, for the encryption mecanism check the cryptoutils class 
header. You can encrypt using openssl command.

Seb

Sent from my Samsung Galaxy smartphone.

 Original message 

From: "Elie Dit Cosaque, David (Nokia - US/Irving)" 

Date: 1/31/18 18:50 (GMT+01:00)

To: "Determe, Sebastien" , onap-discuss@lists.onap.org

Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

I have not encrypted the password so this must be the issue. Is there tool that 
I can use to do that? Can I retrieve the SDC password from the Authorization 
header such as:  Basic 
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=

Is the CLAMP key aa3871669d893c7fb8abbcda31b88b4f ?

Thanks,

David.

From: Determe, Sebastien [mailto:sd3...@intl.att.com]

Sent: Wednesday, January 31, 2018 11:00 AM

To: Elie Dit Cosaque, David (Nokia - US/Irving) 
; onap-discuss@lists.onap.org

Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

OK so it indicates that the password you have set for SDC has not been 
decrypted properly.

Did you encrypt it with AES-CBC-128 ?

Seb

From: Elie Dit Cosaque, David (Nokia - US/Irving) 
[mailto:david.elie_dit_cosa...@nokia.com]

Sent: Wednesday, January 31, 2018 5:57 PM

To: Determe, Sebastien >; 
onap-discuss@lists.onap.org

Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

Hi Sebastien,

For the first error, I was able to find a java stack trace but for the second, 
I see only the error below at he following URL:

http://{{CLAMP_IP}}:8080/restservices/clds/v1/clds/sdc/services

[

{

"code": 500,

"message": "Given final block not properly padded"

}

]

Thanks,

David.

These are all the logs captured during the designer page

[onap-discuss] Canceled event: [integration] weekly (updated Jan. 8) @ Tue Feb 6, 2018 6:30am - 7:30am (PST) (onap-discuss@lists.onap.org)

2018-02-02 Thread 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:20180206T063000
DTEND;TZID=America/Los_Angeles:20180206T073000
DTSTAMP:20180202T14Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:3b6845hqldvdhb2npj5tsdm...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=jp
 he...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:jphe...@linuxfoundation.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=jw
 agant...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:jwagantall@linuxfoundati
 on.org
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
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=he
 len.c...@huawei.com;X-NUM-GUESTS=0:mailto:helen.c...@huawei.com
RECURRENCE-ID;TZID=America/Los_Angeles:20180206T063000
CREATED:20180108T180207Z
DESCRIPTION:Join from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/
 44\n\nOr iPhone one-tap (US Toll): +16465588656\,44# or +14
 086380968\,44#\n\nOr Telephone:\nDial: +1 646 558 8656 (US Toll) or
  +1 408 638 0968 (US Toll)\nMeeting ID: 44  8\nInternational number
 s available: https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcs
 n86
LAST-MODIFIED:20180202T13Z
LOCATION:https://zoom.us/j/44
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[integration] weekly (updated Jan. 8)
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] [modeling] Whether How and when we should move to Github for modeling spec update process

2018-02-02 Thread Brian Hedstrom

Hi Deng,
I'm in favor of using Git for model development.
Do we want to add a Poll page to the wiki to track participant voting on
this topic?

Thanks
Brian

On Wed, Jan 31, 2018 at 7:31 PM, denghui (L)  wrote:

> Hello modeling subcommittee,
>
>
>
> Many Thanks to Jessie’s kind presentation on GitHub for Papyrus model.
>
> https://wiki.onap.org/display/DW/Modeling+sub-committee+Contributions
>
> https://wiki.onap.org/download/attachments/16003450/
> GitHub%20for%20Papyrus%20Model.pptx?api=v2
>
>
>
> Due to time limitation, we would like to discussion in the list together
> with the communities whether, how and when we should move to Github to
> manage the modeling spec update process.
>
>
>
> Thanks a lot for your advice
>
> Best regards,
>
>
>
> DENG Hui
>



-- 
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oam.technology
brian.hedst...@oamtechnologies.com
720-470-7091
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] help

2018-02-02 Thread Smith, Brian


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

[onap-discuss] [vfc]VF-C VoLTE Configuration

2018-02-02 Thread Manoj K Nair

Hi,

I am referring to VoLTE demo 
here
 and have two questions

1)  I tried to onboard a couple of VNF packages using the UUI on SDC (this 
is not shown in demo video) . I navigated to UUI -> Services-> VNF/NS Packages 
and then clicked on OnBoard. I got an error "Failed to query artifacts from 
SDC" . Not sure if this is the right procedure to onboard CSAR packages to VF-C

2)  In the demo video at 14:04 Service Network (VL) is being selected. How 
this Service network can be created? I noticed that Service network is a VL 
(zte ext VL) with Service network capability. How this VL can be created ? Any 
additional CSARs to be loaded ? Appreciate if some one from VoLTE use case 
clarify this?

Regards

Manoj




The information transmitted herein is intended only for the person or entity to 
which it is addressed and may contain confidential, proprietary and/or 
privileged material. Any review, retransmission, dissemination or other use of, 
or taking of any action in reliance upon, this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and delete the material from any computer.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [AAI] [optfra] [multicloud] Persistence of HPA related information in A

2018-02-02 Thread FORSYTH, JAMES

Hi, Dileep,

I added this item to the agenda for today.  Thanks.

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

Christina and Yugandhar, this will definitely be of interest to you.

Thanks,
jimmy

From: "Ranganathan, Dileep" 
Date: Friday, February 2, 2018 at 2:26 AM
To: "FORSYTH, JAMES" , "onap-discuss@lists.onap.org" 
, "Vul, Alex" 
Subject: [onap-discuss] [AAI] [optfra] [multicloud] Persistence of HPA related 
information in A

I would like to discuss about the Persistence of HPA related information in 
A in the weekly meeting call.
I would like to discuss my proposal to capture the HPA capabilities in a 
generic way in A as
represented here --> 
https://wiki.onap.org/display/DW/Persistence+of+HPA+related+information+in+AAI
I would appreciate if we could include this in tomorrow’s meeting.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [modeling]Modeling call next week

2018-02-02 Thread denghui (L)

Hello all

Our modeling subcommittee call will be cancelled next week due to vf2f,

Hi Kenny,

could you kindly help to cancel next week call, thanks a lot

and we will have our modeling subcommittee session on Wednesday 9am eastern 
time, 10pm Beijing time.

1)  Resource IM Xu Yang

2)  Service IM Maopeng Zhang

3)  Data modeling Anatoly

4)  Centralized Parser Atul

5)  Modeling tools Nigel

6) Projects follow up modeling spec discussion (Modeling contact from each 
Project)
Let me know if you have any other suggestions.

Thanks a lot

DENG Hui

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

[onap-discuss] 答复: Re: VIM registration failure

2018-02-02 Thread Vitaliy Emporopulo


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] [SDC][SO] Service Distribution failing with Amsterdam Release HEAT template installation

2018-02-02 Thread ESWAR RAO

HI All,

I am using ONAP Amsterdam release with HEAT templates.

Installation is successful and Robot health checks are fine.


While distributing a service, I am facing below problems:

Can someone please help me in debugging issues:


*sdc_docker: v1.1.0*
*so_docker: v1.1.2*
*so_branch: amsterdam*
*sdc_branch: amsterdam*

root@onap-sdc:/opt# curl http://10.0.3.1:8181/sdc1/rest/healthCheck
ALL are OK

*# SDC-BE*
2018-02-02T09:00:31.674Z|||7597bee7-57ed-45ed-8f90-538116420d07|bcd84c21-84b1-471c-952f-438507b9f279|qtp2006034581-665898|
||SDC-BE|op0001|||INFO||172.17.0.5||10.0.3.1|172.17.0.1|o.o.s.b.a.i.AuditingLogFormatUtil|
|ActivityType=, Desc=
2018-02-02T09:00:37.572Z|||7597bee7-57ed-45ed-8f90-538116420d07|bcd84c21-84b1-471c-952f-438507b9f279|
distribution-notification-thread-4|||SDC-BE|op0001|||INFO||172.17.0.5||10.0.3.1|172.17.0.1|
o.o.s.b.a.i.AuditingLogFormatUtil||ActivityType=,
Desc=*



*# SO*
root@mso:/var/log/ecomp/MSO/ASDCController# tail -f debugmso.log
2018-02-02T09:51:24.729Z|trace-#|UEB GET
/events/SDC-DISTR-NOTIF-TOPIC-AUTO/sdc-OpenSource-Env1-mso-dockero/sdc-COpenSource-Env11-mso-dockero
2018-02-02T09:51:24.731Z|trace-#|GET
http://10.0.11.1:3904/events/SDC-DISTR-NOTIF-TOPIC-AUTO/sdc-OpenSource-Env1-mso-dockero/sdc-COpenSource-Env11-mso-dockero
will send credentials over a clear channel.
2018-02-02T09:51:24.731Z|trace-#|GET
http://10.0.11.1:3904/events/SDC-DISTR-NOTIF-TOPIC-AUTO/sdc-OpenSource-Env1-mso-dockero/sdc-COpenSource-Env11-mso-dockero
(as mYCJXPn1wpcVRiJm) ...
2018-02-02T09:51:30.003Z|trace-#|DistributionClient - init
2018-02-02T09:51:30.003Z|trace-#|DistributionClientResultImpl
[responseStatus=*CONF_INVALID_ASDC_FQDN, responseMessage=configuration is
invalid: CONF_INVALID_ASDC_FQDN]*
2018-02-02T09:51:34.853Z|trace-#|   --> HTTP/1.1 200 OK


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

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

2018-02-02 Thread Determe, Sebastien

Hi David,
Have a look to this:
https://wiki.onap.org/download/attachments/25430497/PresentationCLAMP_ONAP.mp4?version=1=1517476892000=v2

Seb

-Original Message-
From: Elie Dit Cosaque, David (Nokia - US/Irving) 
[mailto:david.elie_dit_cosa...@nokia.com] 
Sent: Thursday, February 01, 2018 6:56 PM
To: Determe, Sebastien ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

Hi Seb, Yury,



We finally have found a working openssl command:



openssl aes-128-ecb -K aa3871669d893c7fb8abbcda31b88b4f   -e -in in.txt -out 
out_ecb.txt



in.txt: contains the data to encrypt, in our case 
Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U



The encrypted output (out_ecb.txt) is in binary format so I used the bless hex 
editor to copy the value. 



After changing the encrypted password, we see no authentication error and can 
get the list of services from SDC. 



I was expecting CLAMP GUI to somehow retrieve the clamp policies from the 
policy VM and present them in the CLAMP designer with an option to start/stop. 
Do we need to create a template and model ? Do you know about a procedure on 
how to do this for the vFWCL demo.



Thanks,

David.

 



-Original Message-

From: Elie Dit Cosaque, David (Nokia - US/Irving) 

Sent: Wednesday, January 31, 2018 3:27 PM

To: 'Determe, Sebastien' ; onap-discuss@lists.onap.org

Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC



Thanks Seb and Yuri



Could you please share the complete openssl command line to generate the 
encrypted password. Our SDC password is Basic 
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=

So base64 decoded:

vid:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U



How can we get the encrypted hex from 
Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U? I always end up with padding error 
when I try (I have done many tries ☹).



Thanks,

David.



-Original Message-

From: Determe, Sebastien [mailto:sd3...@intl.att.com]

Sent: Wednesday, January 31, 2018 2:17 PM

To: Elie Dit Cosaque, David (Nokia - US/Irving) 
; onap-discuss@lists.onap.org

Subject: Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC



Yes that is the key, for the encryption mecanism check the cryptoutils class 
header. You can encrypt using openssl command.

Seb







Sent from my Samsung Galaxy smartphone.





 Original message 

From: "Elie Dit Cosaque, David (Nokia - US/Irving)" 


Date: 1/31/18 18:50 (GMT+01:00)

To: "Determe, Sebastien" , onap-discuss@lists.onap.org

Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC



I have not encrypted the password so this must be the issue. Is there tool that 
I can use to do that? Can I retrieve the SDC password from the Authorization 
header such as:  Basic 
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=



Is the CLAMP key aa3871669d893c7fb8abbcda31b88b4f ?

Thanks,

David.

From: Determe, Sebastien [mailto:sd3...@intl.att.com]

Sent: Wednesday, January 31, 2018 11:00 AM

To: Elie Dit Cosaque, David (Nokia - US/Irving) 
; onap-discuss@lists.onap.org

Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC



OK so it indicates that the password you have set for SDC has not been 
decrypted properly.

Did you encrypt it with AES-CBC-128 ?



Seb



From: Elie Dit Cosaque, David (Nokia - US/Irving) 
[mailto:david.elie_dit_cosa...@nokia.com]

Sent: Wednesday, January 31, 2018 5:57 PM

To: Determe, Sebastien >; 
onap-discuss@lists.onap.org

Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC



Hi Sebastien,



For the first error, I was able to find a java stack trace but for the second, 
I see only the error below at he following URL:



http://{{CLAMP_IP}}:8080/restservices/clds/v1/clds/sdc/services



[

{

"code": 500,

"message": "Given final block not properly padded"

}

]



Thanks,

David.



These are all the logs captured during the designer page refresh:

==



==> /opt/clamp/log/CLAMP/debug.log <==

2018-01-31T15:42:28,557Z||7a-8810-6ae7247a9c74|DEBUG|c.a.a.c.logging.PerformanceTracking|In...:logTracker

2018-01-31T15:42:28,557Z||7a-8810-6ae7247a9c74|INFO|c.a.a.c.logging.PerformanceTracking|Performance
 Log:

Re: [onap-discuss] [vfc]VF-C VoLTE Configuration

[onap-discuss] VF2F Info

[onap-discuss] [AAI][OOM] Zoom session to assist AA with Kubernetes PV changes for Cassandra 3 node cluster (20180202 and 20180126 meets)

Re: [onap-discuss] [modeling]Modeling call next week

[onap-discuss] Community Scribes Needed For VF2F

[onap-discuss] Canceled event: [multicloud] Weekly (Updated Dec. 6, 2017) @ Weekly from 5am to 6am on Friday (PST) (onap-discuss@lists.onap.org)

[onap-discuss] Requesting ONAP Program Committee membership for ONS Developer Forum

[onap-discuss] Updated invitation: ONAP VF2F Bridge 1 Sessions @ Daily from 6am to 8am from Mon Feb 5 to Thu Feb 8 (PST) (onap-discuss@lists.onap.org)

Re: [onap-discuss] [dcae][dcaegen2][holmes] A Question on Auto Scailing of DCAE Microservices

[onap-discuss] SO issues with keystone

Re: [onap-discuss] [onap-tsc] [modeling]Modeling call next week

[onap-discuss] Canceled event: [modeling] Project Bi-Weekly @ Tue Feb 6, 2018 6am - 7am (PST) (onap-discuss@lists.onap.org)

Re: [onap-discuss] [modeling]Modeling call next week

Re: [onap-discuss] [Onap-release] M2 Requirement for JUnit code coverage

Re: [onap-discuss] [modeling]Modeling call next week

Re: [onap-discuss] [oom] Question on DCAE deployment using OOM

Re: [onap-discuss] [dcae][dcaegen2][holmes] A Question on Auto Scailing of DCAE Microservices

[onap-discuss] Zoom update

Re: [onap-discuss] [modeling] Whether How and when we should move to Github for modeling spec update process

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

[onap-discuss] Canceled event: [integration] weekly (updated Jan. 8) @ Tue Feb 6, 2018 6:30am - 7:30am (PST) (onap-discuss@lists.onap.org)

Re: [onap-discuss] [modeling] Whether How and when we should move to Github for modeling spec update process

[onap-discuss] help

[onap-discuss] [vfc]VF-C VoLTE Configuration

Re: [onap-discuss] [AAI] [optfra] [multicloud] Persistence of HPA related information in A

[onap-discuss] [modeling]Modeling call next week

[onap-discuss] 答复: Re: VIM registration failure

[onap-discuss] [SDC][SO] Service Distribution failing with Amsterdam Release HEAT template installation

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

29 matches

Site Navigation

Mail list logo

Footer information