BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T020000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Yunxia Chen:MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Sauvageau,
David ([email protected])":MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="PLATANIA,
MARCO (MARCO)":MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Gildas Lan
ilis:MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Roger Mait
land:MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Seshu m:MA
ILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=ah0398@int
l.att.com:MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=dtimoney@a
tt.com:MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=rk541m@att
.com:MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=talasila@r
esearch.att.com:MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyanyj@
chinamobile.com:MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Xinhui Li:
MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=pdragosh@r
esearch.att.com:MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=jf2512@att
.com:MAILTO:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
ss:MAILTO:[email protected]
ATTACH:CID:[email protected]
DESCRIPTION;LANGUAGE=en-US:When: Friday\, September 01\, 2017 7:00 AM-8:00
AM. (UTC-08:00) Pacific Time (US & Canada)\nWhere: https://zoom.us/j/44666
68888\n\n*~*~*~*~*~*~*~*~*~*\n\nHi\, David\, Marco and PTLs on this list\,
\n\nLet’s use this time to decide which way we should go. If necessary\,
we report to TSC for approval.\n\nFor people who are not aware of the con
text\, please refer to Marco’s initial emails (attached).\n\nFor PTLs on
this list\, from my information (may not up to date)\, OOM has not integr
ated with your project:\nAAI\nVID\nSO\nSDNC\nDCAE\nPortal\nVFC\nMulti-VIM\
nMSBhjn\nPolicy\nCCF\n\nIf you or your proxy cannot make this meeting\, pl
ease go to the following wiki page to add comments related to your project
and cc us as well before 9/1/2017 7:00am PDT :\nhttps://wiki.onap.org/dis
play/DW/ONAP+Installation+Strategy+for+Release+A\n\nIf you’d like to use
OOM\, please work with David to give us a solid date for when it could be
done. Since Integration team is doing daily testing\, we need to identify
one tool to deploy ONAP for R1 before the end of this week.\n\nThank you\
,\nHelen Chen\n\n\nONAP Deployment Strategy for R1: OOM vs Heat Template\n
\n(Non LF Zoom Licence)\nJoin from PC\, Mac\, Linux\, iOS or Android: http
s://zoom.us/j/4466668888<https://www.google.com/url?q=https%3A%2F%2Fzoom.u
s%2Fj%2F4466668888&sa=D&usd=2&usg=AFQjCNGOukyk-yviNF7xE6h-W_r5G1RgPA>\nOr
iPhone one-tap (US Toll): +16465588656\,4466668888# or +14086380968\,44666
68888#\nOr Telephone:\nDial: +1 646 558 8656 (US Toll) or +1 408 638 0968
(US Toll)\nMeeting ID: 44 6666 88888\nInternational numbers available: htt
ps://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86<https://www
.google.com/url?q=https%3A%2F%2Fzoom.us%2Fzoomconference%3Fm%3DCqsAwHx4CSy
RanCfPHKBvf6Vslgcsn86&sa=D&usd=2&usg=AFQjCNHmeO65V_ncgXTJyNNL6g4uKzSNyg>\n
\n
SUMMARY;LANGUAGE=en-US:ONAP Deployment Strategy for R1: OOM vs Heat Templat
e
DTSTART;TZID=Pacific Standard Time:20170901T070000
DTEND;TZID=Pacific Standard Time:20170901T080000
UID:C3293BC8-4F40-456A-AE9E-3F3A00A74522
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170831T165753Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/4466668888
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115567164
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:TRUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
--- Begin Message ---
Dear PTLs,
The Integration and OOM teams are working together to figure out what strategy
we should use to install ONAP R1 for integration testing. Due to the limited
timeframe and the amount of work to do, we should come with a plan by the end
of this week. We have two alternatives:
1. Using OOM (K8-based strategy), which was approved in the past
face-to-face meeting and will be the standard/preferred way in the long run;
2. Using Heat template, which is what we did for OpenECOMP.
With the second approach (ONAP installation via Heat template), we will install
docker containers in OpenStack VMs. The installation process is based on
cloud-init plus custom installation scripts (bash scripts, docker-compose
files, etc). This requires each team to collaborate with us, providing:
· VM resource requirements (CPUs, RAM, Volumes, etc…);
· All the necessary scripts that cloud-init will run automatically to
install the specific ONAP component. OpenECOMP components typically use a bash
script that eventually calls docker-compose (or docker run) to spin up
containers.
Please let us know how you install your components today, what you already have
(scripts, docker-compose, …) and what is the effort and risk to pursue option 1
or option 2 as described above. Please also consider that both approach will
require some work, so it’s crucial to have a quick turn-around here so as to
select one strategy and focus the effort on that.
At this time, the following components (from OpenECOMP) are already set to work
with strategy 2:
· AAI
· APPC
· Policy
· Portal
· SDC
· MSO
· SDNC
· VID
The following components should be integrated, if strategy 2 will be the
preferred one in the short run:
· AAF
· CLAMP
· DCAE GEN 2
· DMAAP (not sure whether this is the same DMAAP as in the original
OpenECOMP seed code; if so, it’s already set)
· Holmes
· MSB
· Multi-VIM
· OOM
· VFC
Finally, I’m not sure whether these are ONAP components or not (as opposed to
libraries, docs, etc.). If so, they should also be integrated:
· CLI
· CCSDK
· External API Framework
· Logging
· Modeling
· VNF-SDK
Helen, Gildas, David, Oliver,
Please feel free to integrate.
Thanks for the cooperation,
Marco
--- End Message ---
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
