Reviving this request. Do we need more discussion about this? Is this requests still applicable?
Thanks! Jess On Fri May 18 14:17:52 2018, [email protected] wrote: > Hi, > > I would like to propose, we postpone the discussion and potential > changes after Beijing Release is out of the door. > Focusing on getting the ONAP working is the urgency for now. > > Thanks for your understanding, > Gildas > ONAP Release Manager > 1 415 238 6287 > > > -----Original Message----- > From: [email protected] [mailto:onap-discuss- > [email protected]] On Behalf Of Jessica Wagantall via RT > Sent: Tuesday, May 15, 2018 1:12 PM > To: [email protected] > Cc: [email protected]; [email protected] > Subject: [onap-discuss] [ONAP Helpdesk #55868] RE: [onap-tsc] [LF] > Request new JIRA project - CD - for all continuous delivery/deployment > work > > Please let me know if I can help. > > Any new projects in Jira will also need Gildas' approval. > > thanks! > Jess > > On Tue May 15 13:29:02 2018, [email protected] wrote: > > Team, > > Moved all the CD/infrastructure jiras/work around 710 into the > > logging-analytics project for now > > Will request a scope change from the Architecture subcommittee > > between the 29th and 5th > > /michael > > > > From: [email protected] [mailto:onap-tsc- > > [email protected]] On Behalf Of Michael O'Brien > > Sent: Thursday, May 10, 2018 9:15 PM > > To: [email protected]; onap-tsc <[email protected]> > > Cc: '[email protected]' <[email protected]> > > Subject: Re: [onap-tsc] [LF] Request new JIRA project - CD - for all > > continuous delivery/deployment work > > > > Including the Linux Foundation > > > > From: [email protected]<mailto:onap-tsc- > > [email protected]> [mailto:[email protected]] On > > Behalf Of Michael O'Brien > > Sent: Thursday, May 10, 2018 12:05 PM > > To: [email protected]<mailto:[email protected]>; > > onap-tsc <[email protected]<mailto:[email protected]>> > > Subject: [onap-tsc] [LF] Request new JIRA project - CD - for all > > continuous delivery/deployment work > > > > Gildas, > > I would like to request a new JIRA project for CD (Continuous > > Delivery) related work. > > > > CD > > > > https://jira.onap.org/secure/BrowseProjects.jspa?selectedCategory=all&; > > selectedProjectType=software > > > > We don't need other artifacts at this time like a git repo, Jenkins > > infrastructure etc.... this is not a full project. > > I can send out a weekly meeting schedule. > > > > Had a talk with Roger who raised the project idea and maybe a > > separate > > weekly meeting - and when he suggested this - It really makes sense > > for the following reasons. > > We are currently talking with several teams - OPNFV, CNCF, Gitlab and > > ONAP member CD deployments - and it would be ideal if we had a place > > to plan all the CD work independent of any particular project > > (currently INT and OOM and CIMAN) Currently there is a lot of CD work > > going on across the teams - some of which are listed below. > > Gary and I work with our two teams in OOM and Integration meetings > > very well on CD work - but a separate JIRA project would help to > > bring > > in members from OPNFV for example and make the CD work (which is > > currently essential in measuring the daily health of ONAP) its own > > entity. > > Note: the scope of CD is to work with the existing CI system (CIMAN) > > in only deploying and running integration testing (all automatic). > > It > > would also consolidate templates/scripts for all cloud-native > > deployment options (openstack/aws/azure) we currently run. > > > > As you can see I also burden the OOM project with all the CD > > epics/stories tracking CD related work - especially the OOM-710 > > tasks. > > https://jira.onap.org/browse/OOM-150 > > https://jira.onap.org/browse/OOM-393 > > https://jira.onap.org/browse/OOM-500 > > https://jira.onap.org/browse/OOM-710 > > https://jira.onap.org/browse/INT-361 > > https://jira.onap.org/browse/INT-300 > > https://jira.onap.org/browse/INT-369 > > https://jira.onap.org/browse/AAI-189 > > https://jira.onap.org/browse/CIMAN-156 > > 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 > > 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 > > 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 > > <https://www.amdocs.com/about/email-disclaimer> > > > > _______________________________________________ > onap-discuss mailing list > [email protected] > https://lists.onap.org/mailman/listinfo/onap-discuss _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
