Bruce, Since there won't be another TSC meeting til Jul 11th, can you provide some more detail on the 3 not discussed items. Thanks, Brent From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, June 27, 2019 12:16 PM To: Rowsell, Brent <Brent.Rowsell@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX 3.0 features Thank you, Brent for your review and questions. 1) FPGA accelerator support is for OpenStack (e.g. Cyborg integration) 2) Agree that the Containerized Ceph spec can/should be split 3) "Lead" is the person responsible internally for getting the work done and is the contact for any questions about the feature. It may or may not be the person who writes the spec. brucej From: Rowsell, Brent [mailto:Brent.Rowsell@windriver.com] Sent: Thursday, June 27, 2019 8:58 AM To: Jones, Bruce E <bruce.e.jones@intel.com<mailto:bruce.e.jones@intel.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] StarlingX 3.0 features Bruce, Thanks. A couple of comments/questions. 1) What's the difference between FPGA accelerator support and k8s fpga device plugin. As discussed at the TSC two wks ago, I have a dev that will be doing a spec for the later. 2) Containerized CEPH. It would be good to break this into two specs I think, one for prep content (R3) and one to complete the integration 3) What do we mean by Lead ? Spec owner ? Brent From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, June 27, 2019 11:44 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] StarlingX 3.0 features Here is a list of StarlingX 3.0 features that our team plans to work on. I would like to ask the TSC to please review the "Not yet discussed" features before closing on the 3.0 feature list. Thank you! brucej Work item TSC status Lead Status IA platform features Not yet discussed Abraham, Saul, Ada Most work is validation, new features are integrated as we adopt newer kernels over time. Real time features for industrial use cases are going into 5.x kernels and may (or may not) be back-portable. Containerize OVS DPDK AR Yong Forrest Not yet approved, Yong to get with Forrest and confirm intent Performance testing Not yet discussed Victor, Ada Proposal in progress FPGA accelerator support Push to 4.0 Abraham, Ada Too big for 3.0 but will likely need to start soon. FPGA hardware has been ordered OpenStack Train integration Approved Bruce (Dean) Continuous integration from OpenStack master Containerized Ceph Push to 4.0 Vivian Too big for 3.0 but will likely need to start soon Time Sensitive Networking Approved Forrest Spec in progress Kubernetes plugins for IA Partial Cindy Some reviews in progress, QAT approved, FPGA likely 4.0 Redfish Approved Cindy Spec in progress IOT device management Not yet discussed Abraham Demo'd @ Denver. POC / pathfinding work for a customer in progress, item likely too big for 3.0 SUSE build support & enablement Approved Abraham, Saul In progress, previously approved for 2.0 and continuing on Containerized OpenStack Clients Approved Dean? Nearly completed for 2.0, pushed to 3.0

I've created a Storyboard for Kata support: https://storyboard.openstack.org/#!/story/2006145 we will do technical feasibility study and bring in/out proposal to release team. thx. - cindy From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Friday, June 28, 2019 11:31 PM To: Rowsell, Brent <Brent.Rowsell@windriver.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX 3.0 features "IA Platform features" are things like RDT (Resource Director Technology), SGX (Software Guard Extensions) and EPID (Extended Platform Identification). These features tend to get added automatically when we upgrade to newer components but should be tested within StarlingX. "Performance Testing" is creating an open framework to measure key performance indicators for StarlingX - things like network latency, fault detection times and so forth. "IOT Device Management" is building on the demo you showed at Denver and taking that to the next level, enabling IOT gateways and similar devices. brucej From: Rowsell, Brent [mailto:Brent.Rowsell@windriver.com] Sent: Thursday, June 27, 2019 6:46 PM To: Jones, Bruce E <bruce.e.jones@intel.com<mailto:bruce.e.jones@intel.com>> Cc: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] StarlingX 3.0 features Bruce, Since there won't be another TSC meeting til Jul 11th, can you provide some more detail on the 3 not discussed items. Thanks, Brent From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, June 27, 2019 12:16 PM To: Rowsell, Brent <Brent.Rowsell@windriver.com<mailto:Brent.Rowsell@windriver.com>> Cc: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] StarlingX 3.0 features Thank you, Brent for your review and questions. 1) FPGA accelerator support is for OpenStack (e.g. Cyborg integration) 2) Agree that the Containerized Ceph spec can/should be split 3) "Lead" is the person responsible internally for getting the work done and is the contact for any questions about the feature. It may or may not be the person who writes the spec. brucej From: Rowsell, Brent [mailto:Brent.Rowsell@windriver.com] Sent: Thursday, June 27, 2019 8:58 AM To: Jones, Bruce E <bruce.e.jones@intel.com<mailto:bruce.e.jones@intel.com>>; starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] StarlingX 3.0 features Bruce, Thanks. A couple of comments/questions. 1) What's the difference between FPGA accelerator support and k8s fpga device plugin. As discussed at the TSC two wks ago, I have a dev that will be doing a spec for the later. 2) Containerized CEPH. It would be good to break this into two specs I think, one for prep content (R3) and one to complete the integration 3) What do we mean by Lead ? Spec owner ? Brent From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, June 27, 2019 11:44 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] StarlingX 3.0 features Here is a list of StarlingX 3.0 features that our team plans to work on. I would like to ask the TSC to please review the "Not yet discussed" features before closing on the 3.0 feature list. Thank you! brucej Work item TSC status Lead Status IA platform features Not yet discussed Abraham, Saul, Ada Most work is validation, new features are integrated as we adopt newer kernels over time. Real time features for industrial use cases are going into 5.x kernels and may (or may not) be back-portable. Containerize OVS DPDK AR Yong Forrest Not yet approved, Yong to get with Forrest and confirm intent Performance testing Not yet discussed Victor, Ada Proposal in progress FPGA accelerator support Push to 4.0 Abraham, Ada Too big for 3.0 but will likely need to start soon. FPGA hardware has been ordered OpenStack Train integration Approved Bruce (Dean) Continuous integration from OpenStack master Containerized Ceph Push to 4.0 Vivian Too big for 3.0 but will likely need to start soon Time Sensitive Networking Approved Forrest Spec in progress Kubernetes plugins for IA Partial Cindy Some reviews in progress, QAT approved, FPGA likely 4.0 Redfish Approved Cindy Spec in progress IOT device management Not yet discussed Abraham Demo'd @ Denver. POC / pathfinding work for a customer in progress, item likely too big for 3.0 SUSE build support & enablement Approved Abraham, Saul In progress, previously approved for 2.0 and continuing on Containerized OpenStack Clients Approved Dean? Nearly completed for 2.0, pushed to 3.0

Bruce: For the Containerized OpenStack Clients feature, this one was mostly done for stx2.0 and does not need much more effort to complete in stx3.0. As this was tracked in the containerization subproject it makes the most sense for me to continue to track this one. Dean as you were the original author of the openstack client commands, it would be great to have your input for this one once Stefan has completed his testing and the current gerrit review updated. I expect this to occur shortly after the stx3.0 branch is available. Frank From: Eslimi, Dariush [mailto:Dariush.Eslimi@windriver.com] Sent: Thursday, June 27, 2019 4:36 PM To: Jones, Bruce E <bruce.e.jones@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX 3.0 features Bruce, RedFish changes are almost all in maintenance area, I do not think we would need Lead per feature in this case, Eric and Zhipeng are already collaborating very close on this. I will be leading this feature to completion. Thanks. Dariush From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: June-27-19 11:44 AM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] StarlingX 3.0 features Here is a list of StarlingX 3.0 features that our team plans to work on. I would like to ask the TSC to please review the "Not yet discussed" features before closing on the 3.0 feature list. Thank you! brucej Work item TSC status Lead Status IA platform features Not yet discussed Abraham, Saul, Ada Most work is validation, new features are integrated as we adopt newer kernels over time. Real time features for industrial use cases are going into 5.x kernels and may (or may not) be back-portable. Containerize OVS DPDK AR Yong Forrest Not yet approved, Yong to get with Forrest and confirm intent Performance testing Not yet discussed Victor, Ada Proposal in progress FPGA accelerator support Push to 4.0 Abraham, Ada Too big for 3.0 but will likely need to start soon. FPGA hardware has been ordered OpenStack Train integration Approved Bruce (Dean) Continuous integration from OpenStack master Containerized Ceph Push to 4.0 Vivian Too big for 3.0 but will likely need to start soon Time Sensitive Networking Approved Forrest Spec in progress Kubernetes plugins for IA Partial Cindy Some reviews in progress, QAT approved, FPGA likely 4.0 Redfish Approved Cindy Spec in progress IOT device management Not yet discussed Abraham Demo'd @ Denver. POC / pathfinding work for a customer in progress, item likely too big for 3.0 SUSE build support & enablement Approved Abraham, Saul In progress, previously approved for 2.0 and continuing on Containerized OpenStack Clients Approved Dean? Nearly completed for 2.0, pushed to 3.0

Bruce, We had discussion in non-OpenStack-dist meeting about features could be part of the sub-project, and below items are not on your list and I’d like to bring them up here as well: 1. Redfish support (https://storyboard.openstack.org/#!/story/2005861) 2. Python2to3 transition (https://wiki.openstack.org/wiki/StarlingX/Python2, story to be created) 3. non-Openstack patch cleanup (TBD) 4. Ceph containerization (https://storyboard.openstack.org/#!/story/2005527, spec under review: https://review.opendev.org/#/c/656371/) 5. Support Kata container (story to be created), 6. QAT support in Cinder & Glance (story to be created). 7. Systemd standardization. Needs to standarization to use systemd and move away from hybrid mode. Only 1 and 4 were included in your list. I was assuming that 2 and 3 were approved and we will continue the effort. As for 5, Kata container support, Shuicheng is taking the lead the evaluate what needs to be done, and I will propose it as stretch goal for 3.0. As for 6, QAT support in Cinder & Glance, I’ve confirmed with Vivian that this is OpenStack upstream work and target to Train release. Thus if we pick up Train, StarlingX will have the feature. Saul is pushing 7 and I think it will be great if we can standardize it. I can create the SB for those not yet, and put them onto https://etherpad.openstack.org/p/stx-r3-feature-candidates Thx. - cindy From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Friday, June 28, 2019 5:25 AM To: Miller, Frank <Frank.Miller@windriver.com> Cc: Eslimi, Dariush <Dariush.Eslimi@windriver.com>; Jones, Bruce E <bruce.e.jones@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX 3.0 features On Thu, Jun 27, 2019 at 4:12 PM Miller, Frank <Frank.Miller@windriver.com<mailto:Frank.Miller@windriver.com>> wrote: For the Containerized OpenStack Clients feature, this one was mostly done for stx2.0 and does not need much more effort to complete in stx3.0. As this was tracked in the containerization subproject it makes the most sense for me to continue to track this one. Dean as you were the original author of the openstack client commands, it would be great to have your input for this one once Stefan has completed his testing and the current gerrit review updated. I expect this to occur shortly after the stx3.0 branch is available. Sure, I'd be glad to. Note that I released the last OSC 3.x (3.19.0) and companion osc-lib a couple of weeks ago, it should be a clean upgrade and includes some much-improved live migration handling that we finally resolved in Denver last month. Next up: OSC4 finally! dt -- Dean Troyer dtroyer@gmail.com<mailto:dtroyer@gmail.com>

Hi Forrest, Did you mean Network team has plan to commit this feature for Stx.3.0? If so, are we going forward with this spec/patch: https://review.opendev.org/655830, in which the last comment was made on May 5th? Regards, Yong On 02/07/2019, 1:42 AM, "Zhao, Forrest" <forrest.zhao@intel.com<mailto:forrest.zhao@intel.com>> wrote: Hi Bruce and TSC reviewers, Here are intents of “containerize OVS DPDK”, 1. As StarlingX moves to containerization, most OpenStack components have been containerized. That includes OVS containerization, but OVS-DPDK is still running on host. It’s better to containerize OVS/DPDK as well, to leverage benefits brought by containerization. 2. Currently, StarlingX supports OVS and OVS-DPDK. OVS is managed by openstack-helm, and running in container. But OVS-DPDK is managed by puppet and run directly on the host. Maintaining two implements and keeping them consistent cost more resources than maintaining just one implement. For example. If we want to make some changes(upgrade OVS version, enable some features), we need the changes at two places. It introduces much more upgrade/maintenance costs. “Containerize OVS DPDK” can eliminate such duplication and inconsistency. Thanks, Forrest From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] Sent: Thursday, June 27, 2019 11:44 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] StarlingX 3.0 features Here is a list of StarlingX 3.0 features that our team plans to work on. I would like to ask the TSC to please review the “Not yet discussed” features before closing on the 3.0 feature list. Thank you! brucej Work item TSC status Lead Status IA platform features Not yet discussed Abraham, Saul, Ada Most work is validation, new features are integrated as we adopt newer kernels over time. Real time features for industrial use cases are going into 5.x kernels and may (or may not) be back-portable. Containerize OVS DPDK AR Yong Forrest Not yet approved, Yong to get with Forrest and confirm intent Performance testing Not yet discussed Victor, Ada Proposal in progress FPGA accelerator support Push to 4.0 Abraham, Ada Too big for 3.0 but will likely need to start soon. FPGA hardware has been ordered OpenStack Train integration Approved Bruce (Dean) Continuous integration from OpenStack master Containerized Ceph Push to 4.0 Vivian Too big for 3.0 but will likely need to start soon Time Sensitive Networking Approved Forrest Spec in progress Kubernetes plugins for IA Partial Cindy Some reviews in progress, QAT approved, FPGA likely 4.0 Redfish Approved Cindy Spec in progress IOT device management Not yet discussed Abraham Demo’d @ Denver. POC / pathfinding work for a customer in progress, item likely too big for 3.0 SUSE build support & enablement Approved Abraham, Saul In progress, previously approved for 2.0 and continuing on Containerized OpenStack Clients Approved Dean? Nearly completed for 2.0, pushed to 3.0