date:20171206

Re: [onap-discuss] POD start up issue | SDC component

2017-12-06 Thread Michael O'Brien

Atul,
  Hi, sorry to hear that.  I have not run master for about a week –but the 
release-1.1.0 branch of OOM is highly optimized and stable – we are mostly 
cherry picking fixes still out of it into master.

   Your issue is likely that you are not running the message-router dependency 
– see below – partial deployments are tricky – you need the entire dependency 
branch of whatever you are bringing up- try everything if you have 55G

  If you switch to release-1.1.0 for now (the Amsterdam release) – then all 
pods will come up ~84 except for 1 aaf container – you don’t need right now.
  Check the health status on the CD server for Amsterdam for a reference – also 
I just verified OOM-328 which required a clean VM install and everything was OK.

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

  In your case if you see failed container startups there are 9+ causes

1)  The ONAP code has issues (not in release-1.1.0) – can’t verify this 
until I pull master again – or we run 2 CD jobs

2)  The config is out of date – maybe in master until all cherry-picks in

3)  Your config pod was not run or was not “Completed” when the pods 
started to come up – fix is delete/create the failed pods – not you

4)  Your config pod is in error – usually because of unset variables in 
onap-parameters.yaml – not you

5)  Your docker images are not pulling – verify you sourced setenv.sh

6)  You are still pulling images – try one of the prepull scripts first

7)  Use the included cd.sh script

8)  Your HD is full – you need 75G +

9)  Your RAM is full – you need 55G to run the whole system – or ~40G to 
run the vFWCL

10)   You don’t have dependent pods started – check the dependency section in 
the yaml (for example vnc-portal needs sdc and vid to be up)
This one looks like yours – a partial system has dependencies – in your case 
sdc-be.yaml needs message-router-dmaap.yaml
do a ./createAll.bash –n onap –a message-router
then a

./deleteAll.bash –n onap –a sdc – then create sdc again
although the dependency tree may continue

11)   I can’t remember the other ones right now – feeding my rabbits and then 
going to bed

Thank you
/michael

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Atul Angrish
Sent: Wednesday, December 6, 2017 13:15
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] POD start up issue | SDC component

HI Guys,

Greetings

I am currently working on ONAP deployment using Kubernetes. I am new to these 
things.
I am referring below mentioned wiki page for ONAP deployment using K8s.

https://wiki.onap.org/display/DW/ONAP+on+Kubernetes

We are facing an issue while deploying pods mainly SDC using Kubernetes.

root@k8s-2:/# kubectl get pods --all-namespaces -a
NAMESPACE NAMEREADY STATUS  
  RESTARTS   AGE
kube-system   heapster-4285517626-km9jg   1/1   Running 
  8  2h
kube-system   kube-dns-638003847-z8gnh3/3   Running 
  23 2h
kube-system   kubernetes-dashboard-716739405-xn4hx1/1   Running 
  7  2h
kube-system   monitoring-grafana-2360823841-fsznx 1/1   Running 
  7  2h
kube-system   monitoring-influxdb-2323019309-qks0t1/1   Running 
  7  2h
kube-system   tiller-deploy-737598192-wlhmk   1/1   Running 
  7  2h
onap  config  0/1   
Completed 0  1h
onap-aai  aai-resources-898583818-6ptc4   2/2   Running 
  0  1h
onap-aai  aai-service-749944520-0jhxf 1/1   Running 
  0  1h
onap-mso  mariadb-829081257-vx3n1 1/1   Running 
  0  1h
onap-mso  mso-821928192-qp6tn 2/2   Running 
  0  1h
onap-sdc  sdc-be-754421819-phch8  0/2   
PodInitializing   0  1h
onap-sdc  sdc-cs-2937804434-qn1q6 1/1   Running 
  0  1h
onap-sdc  sdc-es-2514443912-c7fmd 1/1   Running 
  0  1h
onap-sdc  sdc-fe-902103934-rlbhv  0/2   
Init:0/1  8  1h
onap-sdc  sdc-kb-281446026-tvg8r  1/1   Running 
  0  1h

As can see that all others pods are going to be upped except onap-sdc.
It seems to be a problem in sdc-be container.

When we see the logs of this container we can say that there are issues in some 
chef scripts.

Please find below the steps to check the logs:-


1)  Run kubectl command to check the pods status.

 kubectl get pods --all-namespaces –a

onap-mso

Re: [onap-discuss] [integration] DCAE DNS zones accidentally deleted in lab

2017-12-06 Thread Yang, Bin

Hi Gary,
   I believe what you deleted is the zones belong to your 
tenant/surrogate tenant (Integration-Jenkins in your case). Hope this mitigate 
your worry :)

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

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gary Wu
Sent: Thursday, December 07, 2017 8:06 AM
To: onap-discuss
Subject: [onap-discuss] [integration] DCAE DNS zones accidentally deleted in lab

Hi all,

In an effort to deal with over-quota issues with DCAE DNS zone recordsets in 
the Wind River lab, I inadvertently deleted all the existing DNS zones created 
under the "demo" user.  This may have broken your existing DCAE stacks in the 
lab.  Sorry for this mishap.

Thanks,
Gary


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

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

2017-12-06 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:20171208T05
DTEND;TZID=America/Los_Angeles:20171208T06
RRULE:FREQ=WEEKLY;BYDAY=FR
DTSTAMP:20171207T011633Z
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;RSVP=
 TRUE;CN=lxin...@vmware.com;X-NUM-GUESTS=0:mailto:lxin...@vmware.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
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\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~::~:~::-\nPlease do not edit this section of the description.
 \n\nView your event at https://www.google.com/calendar/event?action=VIEW
 d=MWhub29qNHY3dW45MHJqaGw1aW43c2lvMnAgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn&
 tok=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm9
 1cC5jYWxlbmRhci5nb29nbGUuY29tMzAxMmMyM2FkMzc0NjQ0OTQ0YjFjNjdjZTNiZGVlZDM4YW
 ExZTRlMA=America/Los_Angeles=en.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20171207T011632Z
LOCATION:https://zoom.us/j/587662385
SEQUENCE:0
STATUS:CONFIRMED
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] Canceled event: [multicloud] Weekly Meeting @ Weekly from 6am to 7am on Friday (PDT) (onap-discuss@lists.onap.org)

2017-12-06 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:20170811T06
DTEND;TZID=America/Los_Angeles:20170811T07
RRULE:FREQ=WEEKLY;BYDAY=FR
DTSTAMP:20171207T011340Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:2gc2f7onof9jhpbe27j6eb415c_r20170811t130...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=bh
 5...@att.com;X-NUM-GUESTS=0:mailto:bh5...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=ap
 hi...@microsoft.com;X-NUM-GUESTS=0:mailto:aphi...@microsoft.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=gi
 l.hellm...@windriver.com;X-NUM-GUESTS=0:mailto:gil.hellm...@windriver.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=li
 n...@vmware.com;X-NUM-GUESTS=0:mailto:l...@vmware.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=zh
 anganb...@chinamobile.com;X-NUM-GUESTS=0:mailto:zhanganb...@chinamobile.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=bi
 n.y...@windriver.com;X-NUM-GUESTS=0:mailto:bin.y...@windriver.com
CREATED:20170617T004808Z
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/587662385\n\nOr iPhone one-tap (US Toll):  +16465588656\,587662385# or 
 +14086380968\,587662385#\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: 587 662 385\nInternation
 al numbers available: https://zoom.us/zoomconference?m=6Sb3YBZOK2xsIM1KYlXb
 kQxXkgtFGkgS\n\n
LAST-MODIFIED:20171207T011340Z
LOCATION:https://zoom.us/j/587662385
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[multicloud] Weekly Meeting
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] Invitation: [dcaegen2] Weekly (Updated Dec. 6, 2017) @ Weekly from 7:30am to 8:30am on Thursday (PST) (onap-discuss@lists.onap.org)

2017-12-06 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:20171207T073000
DTEND;TZID=America/Los_Angeles:20171207T083000
RRULE:FREQ=WEEKLY;BYDAY=TH
DTSTAMP:20171207T010758Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:1po3nuoin3rt6mu6s7tn6ep...@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=NEEDS-ACTION;RSVP=
 TRUE;CN=l...@research.att.com;X-NUM-GUESTS=0:mailto:l...@research.att.com
CREATED:20171207T010757Z
DESCRIPTION:Updated Dec. 6\, 2017\n\nONAP Meeting 4 is inviting you to a sc
 heduled Zoom meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: http
 s://zoom.us/j/824147956\n\nOr iPhone one-tap :\nUS: +16465588656\,\,824
 147956#  or +16699006833\,\,824147956# \nOr Telephone:\nDial(for higher
  quality\, dial a number based on your current location)：\nUS: +1 6
 46 558 8656  or +1 669 900 6833  or +1 855 880 1246 (Toll Free) or +1 877 3
 69 0926 (Toll Free)\nMeeting ID: 824 147 956\nInternational numbers
  available: https://zoom.us/zoomconference?m=HN2MIJkxqxYgu8EjDmekdG0WHlAnv3
 Zp\n\n\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~::~:~::-\nPlease do not edit this section of the description.
 \n\nView your event at https://www.google.com/calendar/event?action=VIEW
 d=MXBvM251b2luM3J0Nm11NnM3dG42ZXBhYWYgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn&
 tok=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm9
 1cC5jYWxlbmRhci5nb29nbGUuY29tZjhmNGIzY2IzYzRiZTNmZGU4NWUxNWNkYzI4NmFmMWJmYj
 AyZDJkMQ=America/Los_Angeles=en.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20171207T010757Z
LOCATION:https://zoom.us/j/824147956
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:[dcaegen2] 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] Canceled event: [dcaegen2] Weekly Meeting @ Weekly from 6am to 7am on Thursday (PDT) (onap-discuss@lists.onap.org)

2017-12-06 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:20170810T06
DTEND;TZID=America/Los_Angeles:20170810T07
RRULE:FREQ=WEEKLY;BYDAY=TH
DTSTAMP:20171207T010402Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:nor7q8ipbsespapn486pkrtta4_r20170810t130...@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=lj
 i...@research.att.com;X-NUM-GUESTS=0:mailto:l...@research.att.com
CLASS:PUBLIC
CREATED:20170616T164806Z
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/824147956\n\nOr iPhone one-tap (US Toll):  +14086380968\,824147956# or 
 +16465588656\,824147956#\n\nOr Telephone:\nDial: +1 408 638 0968 (US To
 ll) 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: 824 147 956\nInternation
 al numbers available: https://zoom.us/zoomconference?m=HN2MIJkxqxYgu8EjDmek
 dG0WHlAnv3Zp\n\n
LAST-MODIFIED:20171207T010401Z
LOCATION:https://zoom.us/j/824147956
SEQUENCE:2
STATUS:CANCELLED
SUMMARY:[dcaegen2] 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

[onap-discuss] Canceled event: DCAE Weekly Meeting @ Weekly from 6am to 7am on Thursday (PDT) (onap-discuss@lists.onap.org)

2017-12-06 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:20170622T06
DTEND;TZID=America/Los_Angeles:20170622T07
RRULE:FREQ=WEEKLY;UNTIL=20170810T065959Z;BYDAY=TH
DTSTAMP:20171207T010402Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:nor7q8ipbsespapn486pkrt...@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=lj
 i...@research.att.com;X-NUM-GUESTS=0:mailto:l...@research.att.com
CLASS:PUBLIC
CREATED:20170616T164806Z
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/824147956\n\nOr iPhone one-tap (US Toll):  +14086380968\,824147956# or 
 +16465588656\,824147956#\n\nOr Telephone:\nDial: +1 408 638 0968 (US To
 ll) 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: 824 147 956\nInternation
 al numbers available: https://zoom.us/zoomconference?m=HN2MIJkxqxYgu8EjDmek
 dG0WHlAnv3Zp\n\n
LAST-MODIFIED:20171207T010401Z
LOCATION:https://zoom.us/j/824147956
SEQUENCE:2
STATUS:CANCELLED
SUMMARY:DCAE 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

[onap-discuss] Invitation: [aai] Weekly (Updated Dec. 6, 2017) @ Weekly from 6am to 7am on Friday (PST) (onap-discuss@lists.onap.org)

2017-12-06 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:20171208T06
DTEND;TZID=America/Los_Angeles:20171208T07
RRULE:FREQ=WEEKLY;BYDAY=FR
DTSTAMP:20171207T010040Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:405oug1gqh4o5frc2n18jk7...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jf2...@att.com;X-NUM-GUESTS=0:mailto:jf2...@att.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
CREATED:20171207T010039Z
DESCRIPTION:updated Dec. 6 2017\n\nONAP Meeting 2 is inviting you to a sche
 duled Zoom meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https:
 //zoom.us/j/403219274\n\nOr iPhone one-tap :\nUS: +16465588656\,\,40321
 9274#  or +16699006833\,\,403219274# \nOr Telephone:\nDial(for higher q
 uality\, dial a number based on your current location)：\nUS: +1 646
  558 8656  or +1 669 900 6833  or +1 855 880 1246 (Toll Free) or +1 877 369
  0926 (Toll Free)\nMeeting ID: 403 219 274\nInternational numbers a
 vailable: https://zoom.us/zoomconference?m=0tliieyuLYiDQ83E-kQHw86QJZABgcPF
 \n\n\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~::~:~::-\nPlease do not edit this section of the description.\n
 \nView your event at https://www.google.com/calendar/event?action=VIEW=
 NDA1b3VnMWdxaDRvNWZyYzJuMThqazdtcDAgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn
 k=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91c
 C5jYWxlbmRhci5nb29nbGUuY29tZDU3YmZkNjRjYjZlNDQxOWRjNDA0NGViYmYwZjVkZTUxMWJk
 NzJhMQ=America/Los_Angeles=en.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20171207T010039Z
LOCATION:https://zoom.us/j/403219274
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:[aai] 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] Canceled event: A Weekly @ Weekly from 6am to 7am on Thursday (PDT) (onap-discuss@lists.onap.org)

2017-12-06 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:20170629T06
DTEND;TZID=America/Los_Angeles:20170629T07
RRULE:FREQ=WEEKLY;UNTIL=20170810T065959Z;BYDAY=TH
DTSTAMP:20171207T005550Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:n2l5brkbr8kmetnn8a5k0s7...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=jf
 2...@att.com;X-NUM-GUESTS=0:mailto:jf2...@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
CREATED:20170628T235038Z
DESCRIPTION:Hi there\, \n\nUTC: 1:00AM\, Bejing: 09:00 PM\, Eastern: 09:00 
 AM\, Pacific: 06:00 AM\n\nONAP Meeting 2 is inviting you to a scheduled Zoo
 m meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us
 /j/403219274\n\nOr iPhone one-tap (US Toll):  +14086380968\,\,403219274# or
  +16465588656\,\,403219274#\n\nOr Telephone:\nDial: +1 408 638 0968 (US
  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: 403 219 274\nInternat
 ional numbers available: https://zoom.us/zoomconference?m=0tliieyuLYiDQ83E-
 kQHw86QJZABgcPF\n\n
LAST-MODIFIED:20171207T005549Z
LOCATION:https://zoom.us/j/403219274
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:A 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

[onap-discuss] Canceled event: [aai] Weekly @ Weekly from 6am to 7am on Thursday (PDT) (onap-discuss@lists.onap.org)

2017-12-06 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:20170810T06
DTEND;TZID=America/Los_Angeles:20170810T07
RRULE:FREQ=WEEKLY;BYDAY=TH
DTSTAMP:20171207T005550Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:n2l5brkbr8kmetnn8a5k0s77ek_r20170810t130...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=jf
 2...@att.com;X-NUM-GUESTS=0:mailto:jf2...@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
CREATED:20170628T235038Z
DESCRIPTION:Hi there\, \n\nUTC: 1:00AM\, Bejing: 09:00 PM\, Eastern: 09:00 
 AM\, Pacific: 06:00 AM\n\nONAP Meeting 2 is inviting you to a scheduled Zoo
 m meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us
 /j/403219274\n\nOr iPhone one-tap (US Toll):  +14086380968\,\,403219274# or
  +16465588656\,\,403219274#\n\nOr Telephone:\nDial: +1 408 638 0968 (US
  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: 403 219 274\nInternat
 ional numbers available: https://zoom.us/zoomconference?m=0tliieyuLYiDQ83E-
 kQHw86QJZABgcPF\n\n
LAST-MODIFIED:20171207T005549Z
LOCATION:https://zoom.us/j/403219274
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[aai] 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

[onap-discuss] Invitation: [holmes] Weekly Mtg (Updated Dec. 6, 2017) @ Weekly from 4am to 5am on Thursday (PST) (onap-discuss@lists.onap.org)

2017-12-06 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:20171207T04
DTEND;TZID=America/Los_Angeles:20171207T05
RRULE:FREQ=WEEKLY;BYDAY=TH
DTSTAMP:20171207T005227Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:7e3h9semg8reves1t2v9hn8...@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=NEEDS-ACTION;RSVP=
 TRUE;CN=kp...@linuxfoundation.org;X-NUM-GUESTS=0:mailto:kpaul@linuxfoundati
 on.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=fu.guangr...@zte.com.cn;X-NUM-GUESTS=0:mailto:fu.guangr...@zte.com.
 cn
CREATED:20171207T005227Z
DESCRIPTION:updated Dec. 6\, 2017\nhttps://zoom.us/j/66\n\n-::~:~::
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:
 ~::-\nPlease do not edit this section of the description.\n\nView your even
 t at https://www.google.com/calendar/event?action=VIEW=N2UzaDlzZW1nOHJl
 dmVzMXQydjlobjhwZjQgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=NzIjbGludXhmb3
 VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb
 29nbGUuY29tMzViYTY2ZjUwMzZhZWY4NjNmOGE5MTU4NjY1OWQxNTA2YTA5ZGM0MA=Ameri
 ca/Los_Angeles=en.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20171207T005227Z
LOCATION:https://zoom.us/j/66
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:[holmes] Weekly Mtg (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] Canceled event: [holmes] Weekly Meeting @ Weekly from 5am to 6am on Thursday (PDT) (onap-discuss@lists.onap.org)

2017-12-06 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:20170720T05
DTEND;TZID=America/Los_Angeles:20170720T06
RRULE:FREQ=WEEKLY;BYDAY=TH
DTSTAMP:20171207T004831Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:d3cfnlnnlthei1vg4qk3fab...@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=fu
 .guangr...@zte.com.cn;X-NUM-GUESTS=0:mailto:fu.guangr...@zte.com.cn
CREATED:20170715T010112Z
DESCRIPTION:\nhttps://zoom.us/j/66\n\n
LAST-MODIFIED:20171207T004830Z
LOCATION:https://zoom.us/j/66
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[holmes] Weekly Meeting
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] ONAP Community Awards - VOTING OPEN

2017-12-06 Thread Kenny Paul


Voting for the community awards is now open. I received 87 different 
nominations across the 6 categories, resulting in 53 unique names or projects.

To see a list of nominees and find the link to vote, please visit 
https://wiki.onap.org/display/DW/ONAP+Community+Awards+-+Amsterdam+Release 
 

Voting ends at 2pm pacific time on Monday, Dec. 11.
 

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] POD start up issue | SDC component

2017-12-06 Thread Atul Angrish

HI Guys,

Greetings

I am currently working on ONAP deployment using Kubernetes. I am new to these 
things.
I am referring below mentioned wiki page for ONAP deployment using K8s.

https://wiki.onap.org/display/DW/ONAP+on+Kubernetes

We are facing an issue while deploying pods mainly SDC using Kubernetes.

root@k8s-2:/# kubectl get pods --all-namespaces -a
NAMESPACE NAMEREADY STATUS  
  RESTARTS   AGE
kube-system   heapster-4285517626-km9jg   1/1   Running 
  8  2h
kube-system   kube-dns-638003847-z8gnh3/3   Running 
  23 2h
kube-system   kubernetes-dashboard-716739405-xn4hx1/1   Running 
  7  2h
kube-system   monitoring-grafana-2360823841-fsznx 1/1   Running 
  7  2h
kube-system   monitoring-influxdb-2323019309-qks0t1/1   Running 
  7  2h
kube-system   tiller-deploy-737598192-wlhmk   1/1   Running 
  7  2h
onap  config  0/1   
Completed 0  1h
onap-aai  aai-resources-898583818-6ptc4   2/2   Running 
  0  1h
onap-aai  aai-service-749944520-0jhxf 1/1   Running 
  0  1h
onap-mso  mariadb-829081257-vx3n1 1/1   Running 
  0  1h
onap-mso  mso-821928192-qp6tn 2/2   Running 
  0  1h
onap-sdc  sdc-be-754421819-phch8  0/2   
PodInitializing   0  1h
onap-sdc  sdc-cs-2937804434-qn1q6 1/1   Running 
  0  1h
onap-sdc  sdc-es-2514443912-c7fmd 1/1   Running 
  0  1h
onap-sdc  sdc-fe-902103934-rlbhv  0/2   
Init:0/1  8  1h
onap-sdc  sdc-kb-281446026-tvg8r  1/1   Running 
  0  1h

As can see that all others pods are going to be upped except onap-sdc.
It seems to be a problem in sdc-be container.

When we see the logs of this container we can say that there are issues in some 
chef scripts.

Please find below the steps to check the logs:-


1)  Run kubectl command to check the pods status.

 kubectl get pods --all-namespaces -a

onap-mso  mso-821928192-qp6tn 2/2   Running 
  0  1h
onap-sdc  sdc-be-754421819-phch8  0/2   
PodInitializing   0  1h
onap-sdc  sdc-cs-2937804434-qn1q6 1/1   Running 
  0  1h
onap-sdc  sdc-es-2514443912-c7fmd 1/1   Running 
  0  1h


2)  Using docker ps -a command to list the containers.

root@k8s-2:/# docker ps -a | grep sdc-be
347b4da64d9c
nexus3.onap.org:10001/openecomp/sdc-backend@sha256:d4007e41988fd0bd451b8400144b27c60b4ba0a2e54fca1a02356d8b5ec3ac0d
"/root/startup.sh"53 minutes ago  Up 53 minutes 
  
k8s_sdc-be_sdc-be-754421819-phch8_onap-sdc_d7e74e36-da76-11e7-a79e-02ffdf18df1f_0
2b4cf42b163a
oomk8s/readiness-check@sha256:ab8a4a13e39535d67f110a618312bb2971b9a291c99392ef91415743b6a25ecb
 "/root/ready.py --con"57 minutes ago  
Exited (0) 53 minutes ago   
k8s_sdc-dmaap-readiness_sdc-be-754421819-phch8_onap-sdc_d7e74e36-da76-11e7-a79e-02ffdf18df1f_3
a066ef35890b
oomk8s/readiness-check@sha256:ab8a4a13e39535d67f110a618312bb2971b9a291c99392ef91415743b6a25ecb
 "/root/ready.py --con"About an hour ago   
Exited (0) About an hour ago
k8s_sdc-be-readiness_sdc-be-754421819-phch8_onap-sdc_d7e74e36-da76-11e7-a79e-02ffdf18df1f_0
1fdc79e399fdgcr.io/google_containers/pause-amd64:3.0
   "/pause" 
 About an hour ago   Up About an hour   
 
k8s_POD_sdc-be-754421819-phch8_onap-sdc_d7e74e36-da76-11e7-a79e-02ffdf18df


3)  Use this command to see the docker logs

Docker logs 347b4da64d9c| grep error



4)  Observe the error logs and exceptions.

Currently we are getting below mentioned exceptions:

Recipe Compile Error in 
/root/chef-solo/cache/cookbooks/sdc-catalog-be/recipes/BE_2_setup_configuration
2017-12-06T11:53:48+00:00] ERROR: bash[upgrade-normatives] 
(sdc-normatives::upgrade_Normatives line 7) had an error: 
Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but 
received '1'

[onap-discuss] [integration] DCAE DNS zones accidentally deleted in lab

2017-12-06 Thread Gary Wu

Hi all,

In an effort to deal with over-quota issues with DCAE DNS zone recordsets in 
the Wind River lab, I inadvertently deleted all the existing DNS zones created 
under the "demo" user.  This may have broken your existing DCAE stacks in the 
lab.  Sorry for this mishap.

Thanks,
Gary


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

Re: [onap-discuss] [integration] Could I take Integration?

2017-12-06 Thread Kang Xi

This is to confirm that vCPE does not need the Integration workspace anymore. 
Everything we do is in SB01. Thanks.

Regards,
Kang

From: FREEMAN, BRIAN D [mailto:bf1...@att.com]
Sent: Wednesday, December 06, 2017 17:22
To: Yunxia Chen ; onap-discuss 
; OBRIEN, FRANK MICHAEL ; 
Kang Xi ; PLATANIA, MARCO 
Subject: RE: [integration] Could I take Integration?

I think the last use of Integration was when we were doing the migration to 
SB01  (but its been a few weeks now).

Kang would have my vote on whether we need it for vCPE testing.

I think Marco was using SB00.

Brian

From: Yunxia Chen [mailto:helen.c...@huawei.com]
Sent: Wednesday, December 06, 2017 4:40 PM
To: onap-discuss 
>; OBRIEN, 
FRANK MICHAEL >; Kang 
Xi >; FREEMAN, BRIAN D 
>; PLATANIA, MARCO 
>
Subject: [integration] Could I take Integration?

Hi,
Anyone is using Integration space? I would like to clean this space and take it 
for some testing.

Regards,
Helen Chen

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

Re: [onap-discuss] [integration] Could I take Integration?

2017-12-06 Thread FREEMAN, BRIAN D

I think the last use of Integration was when we were doing the migration to 
SB01  (but its been a few weeks now).

Kang would have my vote on whether we need it for vCPE testing.

I think Marco was using SB00.

Brian


From: Yunxia Chen [mailto:helen.c...@huawei.com]
Sent: Wednesday, December 06, 2017 4:40 PM
To: onap-discuss ; OBRIEN, FRANK MICHAEL 
; Kang Xi ; FREEMAN, BRIAN D 
; PLATANIA, MARCO 
Subject: [integration] Could I take Integration?

Hi,
Anyone is using Integration space? I would like to clean this space and take it 
for some testing.

Regards,
Helen Chen

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

[onap-discuss] [integration] Could I take Integration?

2017-12-06 Thread Yunxia Chen

Hi,
Anyone is using Integration space? I would like to clean this space and take it 
for some testing.

Regards,
Helen Chen

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

Re: [onap-discuss] [integration] Integration Weekly Meeting

2017-12-06 Thread Yunxia Chen

Totally agree that is much easier to read. We tried IRC with collbolt, which 
will automatically generate this, but people have issue to use IRC because of 
company policy.

Regards,

Helen Chen

From: "morgan.richo...@orange.com" 
Date: Wednesday, December 6, 2017 at 8:23 AM
To: Helen Chen 00725961 , onap-discuss 

Cc: Eric Debeau 
Subject: Re: [onap-discuss] [integration] Integration Weekly Meeting

MoM: 
http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2017/onap-int.2017-12-06-14.33.html
please fell free to froward to onap mailing list if you want
As you can see there is no action point, but usually there are, and we start 
the meeting by the follow-up of such action points
there is no way to force people to work, but when they have precise action 
point in public minutes meeting, it can be motivating...

according to me, such minutes are much easier to read than watching a video
it allows to follow offline (when timetable is not reasonable for attendees)
it gives an history of the progress
most of the Open Source communities are using it

/Morgan

Le mercredi 06 décembre 2017 à 06:46 +, Yunxia Chen a écrit :
[integration] Integration Weekly Meeting
Lieu : https://zoom.us/j/44
Heure de début : Aujourd’hui 15:30
Heure de fin : Aujourd’hui 16:30

When: Wednesday, December 06, 2017 6:30 AM-7:30 AM. (UTC-08:00) Pacific Time 
(US & Canada)
Where: https://zoom.us/j/44

*~*~*~*~*~*~*~*~*~*

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

_

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

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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

Re: [onap-discuss] [integration] Integration Weekly Meeting

2017-12-06 Thread morgan.richomme

MoM: 
http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2017/onap-int.2017-12-06-14.33.html
please fell free to froward to onap mailing list if you want
As you can see there is no action point, but usually there are, and we start 
the meeting by the follow-up of such action points
there is no way to force people to work, but when they have precise action 
point in public minutes meeting, it can be motivating...

according to me, such minutes are much easier to read than watching a video
it allows to follow offline (when timetable is not reasonable for attendees)
it gives an history of the progress
most of the Open Source communities are using it

/Morgan

Le mercredi 06 décembre 2017 à 06:46 +, Yunxia Chen a écrit :
[integration] Integration Weekly Meeting
Lieu : https://zoom.us/j/44
Heure de début : Aujourd’hui 15:30
Heure de fin : Aujourd’hui 16:30

When: Wednesday, December 06, 2017 6:30 AM-7:30 AM. (UTC-08:00) Pacific Time 
(US & Canada)
Where: https://zoom.us/j/44

*~*~*~*~*~*~*~*~*~*


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

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

Re: [onap-discuss] Issues with Kubectl setup and newly pulled dockers not showing in kubectl list ---namespace

2017-12-06 Thread Alexis de Talhouët

I see, so for point 1 I cannot help much. It worked well for me.

For the second point, do kubernetes manifests exist for esr and esr gui? You 
need the deployment and the service kubernetes manifests as explained in my 
previous mail.

Thanks,
Alexis

> On Dec 6, 2017, at 10:57 AM, Gaurav Gupta (c)  wrote:
> 
> thanks Alexis  
> 
> response in line .
> 
> with best regards
> gaurav 
> From: Alexis de Talhouët  >
> Sent: 06 December 2017 19:57
> To: Gaurav Gupta (c)
> Cc: onap-discuss@lists.onap.org ; Michael 
> O'Brien; Ramesh Tammana; Ramki Krishnan; Arun Arora (c)
> Subject: Re: Issues with Kubectl setup and newly pulled dockers not showing 
> in kubectl list ---namespace
>  
> Hi,
> 
> Some answers inline.
> 
> Thanks,
> Alexis
> 
>> On Dec 6, 2017, at 8:34 AM, Gaurav Gupta (c) > > wrote:
>> 
>> Hi All , Michal , Alexis 
>> 
>> We are into 2 very distinct issues while trying vDNS Demo on OOM .
>> 
>> issue 1 - kubectl 
>>  post following below information .
>>  1. curl -LO 
>> https://storage.googleapis.com/kubernetes-release/release/v1.7.0/bin/linux/amd64/kubectl
>>  
>> 
>>   2. chmod +x ./kubectl
>>   3. mv kubectl /usr/local/bin 
>>4 setting up config in ~/.kube/config 
>> 
>> 5. while running kubectl cluster-info an dump 
>> 
>> oot@k8s-node-0-30a414d1-5a13-41a5-a15a-5970f7fb74ed:~/.kube# kubectl 
>> cluster-info dump
>> Unable to connect to the server: dial tcp 10.110.208.207:443: i/o timeout
>> 
>> root@k8s-node-0-30a414d1-5a13-41a5-a15a-5970f7fb74ed:~/.kube# kubectl 
>> cluster-info
>> Kubernetes master is running at https://10.110.208.207:443/ 
>> 
> AdT: I’m not sure to understand the issue been raised here. Can you clarify?
> 
> [Gaurav ] -  I think I have some issues with  kubectl setup  so if some one 
> has attempted the kubectl installation and faced similar issues and resolved 
> them , It will help me as well .  
> This is needed so that OOM based deployment can be done and health check 
> scripts refers to kubectl commands . 
>> 
>> 
>> issue 2 - We pulled 2 esr dockers manually  inside our OOM deployment . 
>> However the new dockers are not getting listed in kubectl commands .  So, 
>> essentially these containers dont have any specific IP address attached to 
>> them along with the port.
>> 
>>   questions 
>>  -  Are we missing something - I mean is this even valid 
>> operation in OOM ?  .
> 
> AdT: Pulling docker images and starting them will not make them appear in 
> Kubernetes UI. For that, you need to create Kubernetes manifests defining the 
> deployment, e.g. how the docker container should looks like (port, 
> entrypoint, volume, pre-conditions, …) and the service, exposing the ports 
> defined in the deployment to the external world (when using NodePort).
> 
> [Gaurav ] - The use case is - we had OOM Deployement done with few dockers , 
> But we wanted to pull 2 more dockers i.e esr and esr gui . We did pull the 
> dockers from nexsus repo  but we donot see them getting listed in the kubectl 
> list --namespaces .Due to this we are also assuming that No Port /IP Address 
> is getting assigned to those . 
> Can this use work or we have to do a complete OOM Deployment fresh ?  .
>   
> 
>>  -is there anything else that  we should be doing in 
>> this situation ? .
>> 
>> thanks in advance 
>> 
>> with best regards
>> gaurav 
> 
> 

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

Re: [onap-discuss] Issues with Kubectl setup and newly pulled dockers not showing in kubectl list ---namespace

2017-12-06 Thread Gaurav Gupta (c)

thanks Alexis


response in line .

with best regards
gaurav

From: Alexis de Talhouët 
Sent: 06 December 2017 19:57
To: Gaurav Gupta (c)
Cc: onap-discuss@lists.onap.org; Michael O'Brien; Ramesh Tammana; Ramki 
Krishnan; Arun Arora (c)
Subject: Re: Issues with Kubectl setup and newly pulled dockers not showing in 
kubectl list ---namespace

Hi,

Some answers inline.

Thanks,
Alexis

On Dec 6, 2017, at 8:34 AM, Gaurav Gupta (c) 
> wrote:

Hi All , Michal , Alexis

We are into 2 very distinct issues while trying vDNS Demo on OOM .

issue 1 - kubectl
 post following below information .
 1. curl -LO 
https://storage.googleapis.com/kubernetes-release/release/v1.7.0/bin/linux/amd64/kubectl
  2. chmod +x ./kubectl
  3. mv kubectl /usr/local/bin
   4 setting up config in ~/.kube/config

5. while running kubectl cluster-info an dump

oot@k8s-node-0-30a414d1-5a13-41a5-a15a-5970f7fb74ed:~/.kube# kubectl 
cluster-info dump
Unable to connect to the server: dial tcp 10.110.208.207:443: i/o timeout

root@k8s-node-0-30a414d1-5a13-41a5-a15a-5970f7fb74ed:~/.kube# kubectl 
cluster-info
Kubernetes master is running at 
https://10.110.208.207:443/

AdT: I’m not sure to understand the issue been raised here. Can you clarify?

[Gaurav ] -  I think I have some issues with  kubectl setup  so if some one has 
attempted the kubectl installation and faced similar issues and resolved them , 
It will help me as well .
This is needed so that OOM based deployment can be done and health check 
scripts refers to kubectl commands .

issue 2 - We pulled 2 esr dockers manually  inside our OOM deployment . However 
the new dockers are not getting listed in kubectl commands .  So, essentially 
these containers dont have any specific IP address attached to them along with 
the port.

  questions
 -  Are we missing something - I mean is this even valid 
operation in OOM ?  .

AdT: Pulling docker images and starting them will not make them appear in 
Kubernetes UI. For that, you need to create Kubernetes manifests defining the 
deployment, e.g. how the docker container should looks like (port, entrypoint, 
volume, pre-conditions, …) and the service, exposing the ports defined in the 
deployment to the external world (when using NodePort).

[Gaurav ] - The use case is - we had OOM Deployement done with few dockers , 
But we wanted to pull 2 more dockers i.e esr and esr gui . We did pull the 
dockers from nexsus repo  but we donot see them getting listed in the kubectl 
list --namespaces .Due to this we are also assuming that No Port /IP Address is 
getting assigned to those .
Can this use work or we have to do a complete OOM Deployment fresh ?  .


 -is there anything else that  we should be doing in this 
situation ? .

thanks in advance

with best regards
gaurav

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

[onap-discuss] Nominations.

2017-12-06 Thread Kenny Paul

Just an YFY I received 40 new nominations after I signed off for the day last 
night.
It will take me a while to process these.

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] successful vFW instantiation with k8s ONAP

2017-12-06 Thread Michael O'Brien

From: Michael O'Brien
Sent: Wednesday, December 6, 2017 09:36
To: 'de Talhouet, Alexis' ; PLATANIA, MARCO (MARCO) 

Cc: Mandeep Khinda ; Ran Pollak 
; J.Ram Balasubramanian 
; Roger Maitland ; 
Mike Elliott ; Ramki Krishnan ; 
onap-discuss@lists.onap.org; Arun Arora (c) ; Geora 
Barsky ; Stela Stoykova ; Ramesh 
Tammana ; ISUKAPALLI, SASTRY S (SASTRY) 
(sas...@research.att.com) ; James MacNider 
; Rahul Sharma (153216) ; 
Joey Sullivan ; Beili Zhou 
Subject: RE: successful vFW instantiation with k8s ONAP

Marco,
   Very nice, this is excellent work – thanks for also going all the way on OOM
   There are several developers also reproducing the work from last week on 
their OOM deployments – most are a lot further – hopefully we can all get to 
the appc step before Friday.  Working on getting DCAE up in the openlab for 
closed loop
The clustered OOM should not be an issue – but yes a lot of us run on a 
single host – you bring up a good point – will raise a couple jiras on this – 
just so we have a verified answer – but K8S should handle pods split across 
hosts (we can adjust the affinity rule as well) out of the box.
 Just to verify – your /dockerdata-nfs is a shared mount  - also need to 
document various distributed HA configs – SDNC has a good POC page on this type 
of setup (Rahul, Beli, Joey – thanks - 
https://wiki.onap.org/display/DW/SDN-C+Clustering+on+Kubernetes

For the policy script $DEMO_HOME/vnfs/vfw/scripts/update-vfw-op-policy.sh – 
good point – I’ll raise another on this one – likely it can go into 
oom/kubernetes/config
Meant to also talk with you about OOM boostrap scripts – wil

Also we have the OOM meet and will bring this up

/michael

From: de Talhouet, Alexis [mailto:alexis.de_talho...@bell.ca]
Sent: Tuesday, December 5, 2017 11:46
To: PLATANIA, MARCO (MARCO) 
>
Cc: Michael O'Brien >; 
Mandeep Khinda >; 
Ran Pollak >; J.Ram 
Balasubramanian 
>; 
Roger Maitland >; 
Mike Elliott >; Ramki 
Krishnan >; 
onap-discuss@lists.onap.org; Arun Arora (c) 
>; Geora Barsky 
>; Stela Stoykova 
>; Ramesh Tammana 
>
Subject: Re: successful vFW instantiation with k8s ONAP

Hey Marco,

I haven’t yet get close loop working. I’m working toward this goal. I know 
about the scripts, I have updated them already (locally). I’m following your 
video for close loop and is fixing bugs when they arise. I already identified 
the scripts, also policy isn’t ok. Thanks for pointing APPC has issue as well. 
I’ll look into them.
Today I’m busy with some other stuff, but I’ll resume this tomorrow.

Thanks,
Alexis

On Dec 5, 2017, at 11:14 AM, PLATANIA, MARCO (MARCO) 
> wrote:

OOM Team, All,

I was able to successfully instantiate the vFW VNF using an ONAP instance 
installed via OOM K8s in my private lab. Please see the attached screenshot.

Thanks to OOM Team for making such a great progress so fast!

There are still a few issues that I want to highlight, so once they will get 
fixed we can test the entire closed loop:
• The demo.sh and ete.sh scripts in $OOM_HOME/kubernetes/robot aren’t 
the latest. In particular, demo.sh doesn’t have instructions to run heatbridge, 
which is necessary to complete closed loop.
• Although I mounted the vPacketGen interface in APPC, I can’t see the 
mount point in the APPC GUI. Not sure why this happens. Can it be a 
miscommunication between APPC containers? I’m using a 2-VM cluster, with APPC 
containers spread across the two VMs.
• We built a script that updates the operational policy for the vFW 
closed look. It’s in the demo repository: 
$DEMO_HOME/vnfs/vfw/scripts/update-vfw-op-policy.sh. We should find a way to 
onboard it into some OOM directory, pretty much as with robot scripts (although 
other components like CLAMP could be used for updating policies).

Thanks,
Marco

Re: [onap-discuss] Issues with Kubectl setup and newly pulled dockers not showing in kubectl list ---namespace

2017-12-06 Thread Alexis de Talhouët

Hi,

Some answers inline.

Thanks,
Alexis

> On Dec 6, 2017, at 8:34 AM, Gaurav Gupta (c)  wrote:
> 
> Hi All , Michal , Alexis 
> 
> We are into 2 very distinct issues while trying vDNS Demo on OOM .
> 
> issue 1 - kubectl 
>  post following below information .
>  1. curl -LO 
> https://storage.googleapis.com/kubernetes-release/release/v1.7.0/bin/linux/amd64/kubectl
>  
> 
>   2. chmod +x ./kubectl
>   3. mv kubectl /usr/local/bin 
>4 setting up config in ~/.kube/config 
> 
> 5. while running kubectl cluster-info an dump 
> 
> oot@k8s-node-0-30a414d1-5a13-41a5-a15a-5970f7fb74ed:~/.kube# kubectl 
> cluster-info dump
> Unable to connect to the server: dial tcp 10.110.208.207:443: i/o timeout
> 
> root@k8s-node-0-30a414d1-5a13-41a5-a15a-5970f7fb74ed:~/.kube# kubectl 
> cluster-info
> Kubernetes master is running at https://10.110.208.207:443/ 
> 
AdT: I’m not sure to understand the issue been raised here. Can you clarify?
> 
> 
> issue 2 - We pulled 2 esr dockers manually  inside our OOM deployment . 
> However the new dockers are not getting listed in kubectl commands .  So, 
> essentially these containers dont have any specific IP address attached to 
> them along with the port.
> 
>   questions 
>  -  Are we missing something - I mean is this even valid 
> operation in OOM ?  .

AdT: Pulling docker images and starting them will not make them appear in 
Kubernetes UI. For that, you need to create Kubernetes manifests defining the 
deployment, e.g. how the docker container should looks like (port, entrypoint, 
volume, pre-conditions, …) and the service, exposing the ports defined in the 
deployment to the external world (when using NodePort).

>  -is there anything else that  we should be doing in this 
> situation ? .
> 
> thanks in advance 
> 
> with best regards
> gaurav 

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

[onap-discuss] Issues with Kubectl setup and newly pulled dockers not showing in kubectl list ---namespace

2017-12-06 Thread Gaurav Gupta (c)

Hi All , Michal , Alexis


We are into 2 very distinct issues while trying vDNS Demo on OOM .


issue 1 - kubectl

 post following below information .

 1. curl -LO 
https://storage.googleapis.com/kubernetes-release/release/v1.7.0/bin/linux/amd64/kubectl

  2. chmod +x ./kubectl

  3. mv kubectl /usr/local/bin

   4 setting up config in ~/.kube/config


5. while running kubectl cluster-info an dump


oot@k8s-node-0-30a414d1-5a13-41a5-a15a-5970f7fb74ed:~/.kube# kubectl 
cluster-info dump
Unable to connect to the server: dial tcp 10.110.208.207:443: i/o timeout

root@k8s-node-0-30a414d1-5a13-41a5-a15a-5970f7fb74ed:~/.kube# kubectl 
cluster-info
Kubernetes master is running at https://10.110.208.207:443/



issue 2 - We pulled 2 esr dockers manually  inside our OOM deployment . However 
the new dockers are not getting listed in kubectl commands .  So, essentially 
these containers dont have any specific IP address attached to them along with 
the port.


  questions

 -  Are we missing something - I mean is this even valid 
operation in OOM ?  .

 -is there anything else that  we should be doing in this 
situation ? .


thanks in advance


with best regards

gaurav

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

Re: [onap-discuss] POD start up issue | SDC component

Re: [onap-discuss] [integration] DCAE DNS zones accidentally deleted in lab

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

[onap-discuss] Canceled event: [multicloud] Weekly Meeting @ Weekly from 6am to 7am on Friday (PDT) (onap-discuss@lists.onap.org)

[onap-discuss] Invitation: [dcaegen2] Weekly (Updated Dec. 6, 2017) @ Weekly from 7:30am to 8:30am on Thursday (PST) (onap-discuss@lists.onap.org)

[onap-discuss] Canceled event: [dcaegen2] Weekly Meeting @ Weekly from 6am to 7am on Thursday (PDT) (onap-discuss@lists.onap.org)

[onap-discuss] Canceled event: DCAE Weekly Meeting @ Weekly from 6am to 7am on Thursday (PDT) (onap-discuss@lists.onap.org)

[onap-discuss] Invitation: [aai] Weekly (Updated Dec. 6, 2017) @ Weekly from 6am to 7am on Friday (PST) (onap-discuss@lists.onap.org)

[onap-discuss] Canceled event: A Weekly @ Weekly from 6am to 7am on Thursday (PDT) (onap-discuss@lists.onap.org)

[onap-discuss] Canceled event: [aai] Weekly @ Weekly from 6am to 7am on Thursday (PDT) (onap-discuss@lists.onap.org)

[onap-discuss] Invitation: [holmes] Weekly Mtg (Updated Dec. 6, 2017) @ Weekly from 4am to 5am on Thursday (PST) (onap-discuss@lists.onap.org)

[onap-discuss] Canceled event: [holmes] Weekly Meeting @ Weekly from 5am to 6am on Thursday (PDT) (onap-discuss@lists.onap.org)

[onap-discuss] ONAP Community Awards - VOTING OPEN

[onap-discuss] POD start up issue | SDC component

[onap-discuss] [integration] DCAE DNS zones accidentally deleted in lab

Re: [onap-discuss] [integration] Could I take Integration?

Re: [onap-discuss] [integration] Could I take Integration?

[onap-discuss] [integration] Could I take Integration?

Re: [onap-discuss] [integration] Integration Weekly Meeting

Re: [onap-discuss] [integration] Integration Weekly Meeting

Re: [onap-discuss] Issues with Kubectl setup and newly pulled dockers not showing in kubectl list ---namespace

Re: [onap-discuss] Issues with Kubectl setup and newly pulled dockers not showing in kubectl list ---namespace

[onap-discuss] Nominations.

Re: [onap-discuss] successful vFW instantiation with k8s ONAP

Re: [onap-discuss] Issues with Kubectl setup and newly pulled dockers not showing in kubectl list ---namespace

[onap-discuss] Issues with Kubectl setup and newly pulled dockers not showing in kubectl list ---namespace

26 matches

Site Navigation

Mail list logo

Footer information