BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T020000
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
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
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jessica Wa
 gantall:MAILTO:jwagant...@linuxfoundation.org
ATTACH:CID:37CAC50216F4B046B628986FE8432E97@amdocs.com
ATTACH:CID:75223DBADFC13F4EBCFFFFEE400C8EC2@amdocs.com
DESCRIPTION;LANGUAGE=en-US:Team\,\n    Hi\, the Integration(Ran\, Marco\, G
 ary\, Helen\, Brian)\, OOM(Alexis\, Mike O\, Mike E\, Yuri)\, the Linux Fo
 undation(Jessica) and members of the TSC (Gildas) have been discussing bui
 ld tagging and continuous deployment as a way of validating the runtime in
 tegrity of each component merge – a fully jenkins triggered automated CI
 /CD system that does more than healthcheck.\n    At the last Integration m
 eet and a couple before that we discussed moving away from blind tagging a
 nd more towards continuous build validation – this meeting is in respons
 e.\n    One of the major goals of this meeting is getting a clean set of t
 asks we will present to the Linux Foundation and the PTLs on any addition/
 modification of the current Jenkins/nexus3 build structure.\n\n    We will
  be holding weekly meetings so everyone can contribute and be aware of wor
 k items and changes to the way we build\, deploy\, test and mark each comm
 it in onap.  Currently the JobBuilder does CI compilation/test marking a -
 1/+1.  We will be coming up with a set of proposals to drive CD with the g
 oal of creating/consuming a manifest per commit and marking a merge as +1/
 -1 using an additional “CDBuilder”.\n     Please come to the meeting t
 o help us align/fix anything out of order and sort out the work items.\n\n
 https://zoom.us/j/7939937123\nTentatively 1130 EST (GMT-5) on Thu – 30 m
 in after the TSC meeting – we can move it\n\n     There is a JIRA being 
 worked out that describes the tasks needed to transition a live POC using 
 what is running now.  There is also work being done in OOM-460 that will a
 lign any CD system to helm based config packaging.  This meeting is to wor
 k out tasks mostly around what will impact the LF and PTLs as we bring in 
 continuous deployment and align CI/CD with what is master right now.\n\n  
     Agenda items\nReview https://jira.onap.org/browse/OOM-500\nDiscuss ali
 gning the nexus3 docker tag timestamp format<https://nexus3.onap.org/> –
  LF task and PTL oversight\nDiscuss building tagged docker images per comm
 it – more granular than daily<https://jenkins.onap.org/view/Merge-Jobs/j
 ob/aai-sparky-be-master-merge-java/> – LF task\nDiscuss how to validate 
 a tagset containing the specific commit under test – the CD deployment<h
 ttp://jenkins.onap.info/job/oom-cd> server/job – this is where we pull/p
 ush the docker tagset manifest under test.\n\nDiscussion start (from OOM-5
 00)\n\n  existing flow (actual)\n•       gerrit review commits - partial
 -CI runs - JobBuilder marks -1 (compile failure\, sonar failure)\n•     
   gerrit review commits - partial-CI runs - JobBuilder marks +1\, committe
 r +2 merges to master\, (later daily docker merge build tagged docker blin
 dly)\n•       no way to know whether that commit degraded ONAP\n\n  prop
 osed flow (expected) - two phase JobBuilder +1 process\n•       gerrit r
 eview commits - partial-CI runs - JobBuilder marks -1 (compile failure\, s
 onar failure)\n•       gerrit review commits - partial-CI runs - JobBuil
 der marks +1\, (what we add below)\nkick in docker merge immediately\, we 
 tag the docker image\, we adjust the manifest for this review\nrun extra C
 DBuilder that runs CD deploy of OOM using above tagset manifest\, healthch
 eck\, vFW\nreport failure - marks gerrit review as -1 - no tag set publish
 ed for this failed commit\nor report pass - marks gerrit review as +1\njen
 kins now retags "latest" to the the docker built above for the review (do 
 not blindly tag "latest" to the last docker build whether it passes/fails 
 CD)\nTagset for that build becomes the latest stable master build of ONAP 
 (as in an OOM deploy will run not from master tip but from a tagged set th
 at omits the last breaking change)\n•       committer +2 merges to maste
 r\, (docker merge and tagging should not be required as long as master has
  not moved during the 1 hour CD build)\n\n\n     Thank you\n     /michael\
 n\n\n\n\n\n
SUMMARY;LANGUAGE=en-US:ONAP continuous tagging and deployment discussion - 
 full CI/CD
DTSTART;TZID=Eastern Standard Time:20180125T113000
DTEND;TZID=Eastern Standard Time:20180125T123000
UID:040000008200E00074C5B7101A82E00800000000307D072C4C94D301000000000000000
 010000000FAF336B4C838F840AAEB7256FD65EF7D
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180123T192944Z
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:213325794
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

Reply via email to