Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED
OK for stx-fault and stx-metal. Regards, Tao -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa@gmail.com] Sent: November 2, 2018 1:37 PM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Hi Technical Leads, I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task. I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an 'OK' in case the core team for your project is listed correctly. Please let me know if you have any questions. Thanks and Best Regards, Ildikó stx-clients - client libraries Jerry Sun (Jerry.Sun@windriver.com<mailto:Jerry.Sun@windriver.com>) Greg Waines (Greg.Waines@windriver.com<mailto:Greg.Waines@windriver.com>) stx-config - Configuration Management Bart Wensley (Barton.Wensley@windriver.com<mailto:Barton.Wensley@windriver.com>) John Kung (John.Kung@windriver.com<mailto:John.Kung@windriver.com>) Don Penney (Don.Penney@windriver.com<mailto:Don.Penney@windriver.com>) Bob Church (Robert.Church@windriver.com<mailto:Robert.Church@windriver.com>) Chris Friesen (Chris.Friesen@windriver.com<mailto:Chris.Friesen@windriver.com>) stx-fault - Fault Management Tao Liu (Tao.Liu@windriver.com<mailto:Tao.Liu@windriver.com>) Al Bailey (Al.Bailey@windriver.com<mailto:Al.Bailey@windriver.com>) stx-integ - Integration and packaging Scott Little (scott.little@windriver.com<mailto:scott.little@windriver.com>) Bob Church (Robert.Church@windriver.com<mailto:Robert.Church@windriver.com>) Don Penney (Don.Penney@windriver.com<mailto:Don.Penney@windriver.com> ) stx-gui - Horizon plugins for new services Tyler Smith (Tyler.Smith@windriver.com<mailto:Tyler.Smith@windriver.com>) Angie Wang (Angie.Wang@windriver.com<mailto:Angie.Wang@windriver.com>) Kristine Bujold (Kristine.Bujold@windriver.com<mailto:Kristine.Bujold@windriver.com>) stx-ha - High Availability/Service Management Bin Qian (Bin.Qian@windriver.com<mailto:Bin.Qian@windriver.com>) Eric Macdonald (Eric.MacDonald@windriver.com<mailto:Eric.MacDonald@windriver.com>) John Kung (John.Kung@windriver.com<mailto:John.Kung@windriver.com>) stx-metal - Bare Metal Management Eric Macdonald (Eric.MacDonald@windriver.com<mailto:Eric.MacDonald@windriver.com>) John Kung (John.Kung@windriver.com<mailto:John.Kung@windriver.com>) Tao Liu (Tao.Liu@windriver.com<mailto:Tao.Liu@windriver.com>) stx-nfv - NFVI Orchestration Bart Wensley (Barton.Wensley@windriver.com<mailto:Barton.Wensley@windriver.com>) Al Bailey (Al.Bailey@windriver.com<mailto:Al.Bailey@windriver.com>) Jack Ding (Jack.Ding@windriver.com<mailto:Jack.Ding@windriver.com>) stx-update - Installation/Update/Patching Bart Wensley (Barton.Wensley@windriver.com<mailto:Barton.Wensley@windriver.com>) Don Penney (Don.Penney@windriver.com<mailto:Don.Penney@windriver.com>) David Sullivan (David.Sullivan@windriver.com<mailto:David.Sullivan@windriver.com>) stx-upstream - Upstream packages Bob Church (Robert.Church@windriver.com<mailto:Robert.Church@windriver.com>) Al Bailey (Al.Bailey@windriver.com<mailto:Al.Bailey@windriver.com>) Chris Friesen (Chris.Friesen@windriver.com<mailto:Chris.Friesen@windriver.com>) stx-distcloud - Distributed Cloud Bart Wensley (Barton.Wensley@windriver.com<mailto:Barton.Wensley@windriver.com>) Brent Rowsell brent.rowsell@windriver.com<mailto:brent.rowsell@windriver.com> Chris Friesen (Chris.Friesen@windriver.com<mailto:Chris.Friesen@windriver.com>) Dean Troyer dtroyer@gmail.com<mailto:dtroyer@gmail.com> John Kung john.kung@windriver.com<mailto:john.kung@windriver.com> Saul Wold sgw@linux.intel.com<mailto:sgw@linux.intel.com> stx-distcloud-client - Distributed Cloud Bart Wensley (Barton.Wensley@windriver.com<mailto:Barton.Wensley@windriver.com>) Chris Friesen (Chris.Friesen@windriver.com<mailto:Chris.Friesen@windriver.com>) John Kung (John.Kung@windriver.com<mailto:John.Kung@windriver.com> ) stx-manifest - source manifest to manage the repositories Scott Little (scott.little@windriver.com<mailto:scott.little@windriver.com>) Jason McKenna (Jason.McKenna@windriver.com<mailto:Jason.McKenna@windriver.com>) stx-root - build source tree root Scott Little (scott.little@windriver.com<mailto:scott.little@windriver.com>) Jason McKenna (Jason.McKenna@windriver.com<mailto:Jason.McKenna@windriver.com>) stx-tis-repo - build support Scott Little (scott.little@windriver.com<mailto:scott.little@windriver.com>) Jason McKenna (Jason.McKenna@windriver.com<mailto:Jason.McKenna@windriver.com>) stx-tools - build tools Scott Little (scott.little@windriver.com<mailto:scott.little@windriver.com>) Jason McKenna (Jason.McKenna@windriver.com<mailto:Jason.McKenna@windriver.com>) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181105/a7527a43/attachment-0001.html> ------------------------------ Message: 2 Date: Mon, 5 Nov 2018 12:07:26 -0800 From: Saul Wold <sgw@linux.intel.com> To: "Xie, Cindy" <cindy.xie@intel.com>, Ildiko Vancsa <ildiko.vancsa@gmail.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED Message-ID: <edf7019c-9230-ee0a-8263-aafd19632f84@linux.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed I agree with this, I also think I should be added to stx-root, stx-tools, stx-manifest and stx-tis-repo as part of the build. Thanks Sau! On 11/4/18 10:24 PM, Xie, Cindy wrote:
For stx-integ, this repo was used for non-openstack distro sub-project a lot. I am hoping that both Saul and Brent can be the core reviewers for it.
stx-integ - Integration and packaging Scott Little (scott.little@windriver.com) Bob Church (Robert.Church@windriver.com) Don Penney (Don.Penney@windriver.com ) Wold, Saul <saul.wold@intel.com> Rowsell, Brent <Brent.Rowsell@windriver.com>
Thx. - cindy
-----Original Message----- From: Smith, Tyler [mailto:tyler.smith@windriver.com] Sent: Friday, November 2, 2018 11:20 AM To: Ildiko Vancsa <ildiko.vancsa@gmail.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED
OK for stx-gui
Thanks, Tyler
-----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa@gmail.com] Sent: Friday, November 2, 2018 1:37 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] TLs to sign off on initial core reviewer groups - ACTION NEEDED
Hi Technical Leads,
I started to work on creating the core reviewer groups in Gerrit for each of the sub-projects in StarlingX and I need your input to complete this task.
I have an initial list below containing the sub-project repos and the names of the core reviewers belonging to the groups. Please check your sub-project and respond with corrections or with an ‘OK’ in case the core team for your project is listed correctly.
Please let me know if you have any questions.
Thanks and Best Regards, Ildikó
stx-clients - client libraries Jerry Sun (Jerry.Sun@windriver.com) Greg Waines (Greg.Waines@windriver.com)
stx-config - Configuration Management Bart Wensley (Barton.Wensley@windriver.com) John Kung (John.Kung@windriver.com) Don Penney (Don.Penney@windriver.com) Bob Church (Robert.Church@windriver.com) Chris Friesen (Chris.Friesen@windriver.com)
stx-fault - Fault Management Tao Liu (Tao.Liu@windriver.com) Al Bailey (Al.Bailey@windriver.com)
stx-integ - Integration and packaging Scott Little (scott.little@windriver.com) Bob Church (Robert.Church@windriver.com) Don Penney (Don.Penney@windriver.com )
stx-gui - Horizon plugins for new services Tyler Smith (Tyler.Smith@windriver.com) Angie Wang (Angie.Wang@windriver.com) Kristine Bujold (Kristine.Bujold@windriver.com)
stx-ha - High Availability/Service Management Bin Qian (Bin.Qian@windriver.com) Eric Macdonald (Eric.MacDonald@windriver.com) John Kung (John.Kung@windriver.com)
stx-metal - Bare Metal Management Eric Macdonald (Eric.MacDonald@windriver.com) John Kung (John.Kung@windriver.com) Tao Liu (Tao.Liu@windriver.com)
stx-nfv - NFVI Orchestration Bart Wensley (Barton.Wensley@windriver.com) Al Bailey (Al.Bailey@windriver.com) Jack Ding (Jack.Ding@windriver.com)
stx-update - Installation/Update/Patching Bart Wensley (Barton.Wensley@windriver.com) Don Penney (Don.Penney@windriver.com) David Sullivan (David.Sullivan@windriver.com)
stx-upstream - Upstream packages Bob Church (Robert.Church@windriver.com) Al Bailey (Al.Bailey@windriver.com) Chris Friesen (Chris.Friesen@windriver.com)
stx-distcloud – Distributed Cloud Bart Wensley (Barton.Wensley@windriver.com) Brent Rowsell brent.rowsell@windriver.com Chris Friesen (Chris.Friesen@windriver.com) Dean Troyer dtroyer@gmail.com John Kung john.kung@windriver.com Saul Wold sgw@linux.intel.com
stx-distcloud-client – Distributed Cloud Bart Wensley (Barton.Wensley@windriver.com) Chris Friesen (Chris.Friesen@windriver.com) John Kung (John.Kung@windriver.com )
stx-manifest - source manifest to manage the repositories Scott Little (scott.little@windriver.com) Jason McKenna (Jason.McKenna@windriver.com)
stx-root - build source tree root Scott Little (scott.little@windriver.com) Jason McKenna (Jason.McKenna@windriver.com)
stx-tis-repo - build support Scott Little (scott.little@windriver.com) Jason McKenna (Jason.McKenna@windriver.com)
stx-tools - build tools Scott Little (scott.little@windriver.com) Jason McKenna (Jason.McKenna@windriver.com)
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
------------------------------ Message: 3 Date: Mon, 5 Nov 2018 21:21:06 +0100 From: Tung Doan <doantungbk.203@gmail.com> To: dtroyer@gmail.com Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Propose OpenStack/Apmec to StarlingX like an upstream component Message-ID: <CAMSUe3SbLS3JLd3CBK8edSduMWoEKbh3SaM+1apK4xuvrq98rg@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi Dean, Thank you for your attention to this integration. I just gave you the feedbacks. Please see inline. Vào Th 5, 1 thg 11, 2018 vào lúc 18:16 Dean Troyer <dtroyer@gmail.com> đã viết:
I am Tung Doan - An OpenStack contributor and the PTL of OpenStack/Apmec
On Thu, Nov 1, 2018 at 7:44 AM Tung Doan <doantungbk.203@gmail.com> wrote: project. Since we acknowledged the potential integration between Apmec and StarlingX, I am writing this email to propose adding OpenStack/Apmec to StarlingX like an upstream project.
Project description: OpenStack Apmec [1] stands for the Automated
Provisioning Framework for Multi-access Edge Computing which is the first orchestration and management framework dedicated to the MEC services in OpenStack. Below are some of the outstanding features of Apmec project:
I believe Apmec is not an official OpenStack project (as listed in [0]), do you have plans to apply to become an official OpenStack project under TC governance? (Until then you do need to be careful about referring to Apmec as 'an OpenStack project', it is hosted by OpenStack, but is not (yet?) an OpenStack project.)
Apmec is not official OpenStack but we planned to aplly to make it become the official project as stated in [1].
- no need to take care of the NFV functionalities. Since existing NFV MANO frameworks (Tacker, ONAP, OSM, OpenBaton,...) are diverse, integrating them can make StarlingX complicated. Apmec was designed to take over responsibility for integrating them since the delivery of MEC services is our critical mission.
Is this replacing existing StarlingX functionality?
Our desire is to make Apmec become a "bridge" that helps StarlingX to cooperate with different NFV MANO frameworks. Instead of managing various APIs from the diffirent NFV MANO frameworks, StarlingX can offload them to Apmec.
- no need to take care of the life-cycle management of the MEC applications. Apmec offers API to help StarlingX perform this function. As mentioned earlier, Apmec is OpenStack project, therefore, to provide low-latency for MEC applications, Apmec is also planned to support acceleration technologies (e.g, integrated with OpenStack Cyborg) such as DPDK and FPGA.
Can you get more specific about what the integration with StarlingX looks like?
Since Apmec is OpenStack repo, it has good chances to leverage different OpenStack projects. When integrated with Starling, Apmec provides APIs that help Starling manage the MEC applications which could be supported many acceleration technologies. StarlingX does not need to take care of low-layer design for such features. StarlingX only needs to describe the requirements for the applications (Apmec provides tool to describe them [2]), the rest will be taken care by Apmec.
dt
[0] https://governance.openstack.org/tc/reference/projects/index.html
--
Dean Troyer dtroyer@gmail.com
[1] https://review.openstack.org/#/c/612962/ [2] https://review.openstack.org/#/c/570797/ -- Name: Doan Van Tung Email: van_tung.doan@mailbox.tu-dresden.de A member of 5G Lab Germany *Deutsche Telekom Chair of Communication Networks (ComNets)* *Würzburger Str. 35, 01187 Dresden* *TU Dresden, Germany* -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181105/d1f0f69e/attachment.html> ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 6, Issue 15 ************************************************
participants (1)
-
Liu, Tao