[Starlingx-discuss] PTG upstreaming discussion
Hi all; Just a short note to share what Brent, Saul, Dean and I reviewed on Thursday at the PTG last week. We went through the upstreaming backlog and the notes below summarize the outcomes. This does not reflect the outcomes of the direct engagement with the Neutron and Nova teams, that summary will follow. We added a new tag – maintain, items which we know we will need to maintain. Horizon: Eddie and Tyler to get together to review what is left out of STX-GUI and what additional refactoring may be required or patches left to upstream Keystone: Nothing left after March release due to containerization of Openstack Python-Clients: items need to map to main project server-side disposition. Additionally, we agreed we should move the clients as close to master as possible, this can be done independently as this provides users backward compatibility. Heat: most are related to underlying changes and should be mapped to those items as close as possible. There are a few bug fixes that can be tackled easily. Step 1 is to mapping out the dependencies so that the bugs can be focused on. Glance: raw caching can it be replaced by cinder feature. Removes several Glance patches. Lisa and Brent to analyze – emails in flight. Cinder: in good shape, but, there is work left to do. We need to identify who can focus on these items up so we can retire the repo. Ceilometer: Many can be retired, we did a scrub in real time. Nova: 200 – 300 items to be worked on. We discussed an approach to break down and focus our efforts in Nova. We identified the following priority areas: (additional discussions were held on Friday, so this may change) 1. Anything to do with Live migration 2. Logging – improvements 3. vTPM – contribute to work in flight 4. Clean-up of PCI/SRIOV items 5. CAT – wait for T release Operating system: Reviewed a big chunk of items and discussed and updated in real time. We made lots of updates to the google-spreadsheet in real time. [0] We agreed to meet again next week and again in 4 weeks. Regards; Ian [0] https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAugOWXMj...
Forwarding to the ML. Brent -----Original Message----- From: Jolliffe, Ian Sent: Monday, September 17, 2018 9:43 AM To: Rowsell, Brent <Brent.Rowsell@windriver.com>; Saul Wold <sgw@linux.intel.com>; Troyer, Dean <dean.troyer@intel.com> Cc: starlingx-discuss@lists.starlingx.io Subject: PTG upstreaming discussion Hi all; Just a short note to share what Brent, Saul, Dean and I reviewed on Thursday at the PTG last week. We went through the upstreaming backlog and the notes below summarize the outcomes. This does not reflect the outcomes of the direct engagement with the Neutron and Nova teams, that summary will follow. We added a new tag – maintain, items which we know we will need to maintain. Horizon: Eddie and Tyler to get together to review what is left out of STX-GUI and what additional refactoring may be required or patches left to upstream Keystone: Nothing left after March release due to containerization of Openstack Python-Clients: items need to map to main project server-side disposition. Additionally, we agreed we should move the clients as close to master as possible, this can be done independently as this provides users backward compatibility. Heat: most are related to underlying changes and should be mapped to those items as close as possible. There are a few bug fixes that can be tackled easily. Step 1 is to mapping out the dependencies so that the bugs can be focused on. Glance: raw caching can it be replaced by cinder feature. Removes several Glance patches. Lisa and Brent to analyze – emails in flight. Cinder: in good shape, but, there is work left to do. We need to identify who can focus on these items up so we can retire the repo. Ceilometer: Many can be retired, we did a scrub in real time. Nova: 200 – 300 items to be worked on. We discussed an approach to break down and focus our efforts in Nova. We identified the following priority areas: (additional discussions were held on Friday, so this may change) 1. Anything to do with Live migration 2. Logging – improvements 3. vTPM – contribute to work in flight 4. Clean-up of PCI/SRIOV items 5. CAT – wait for T release Operating system: Reviewed a big chunk of items and discussed and updated in real time. We made lots of updates to the google-spreadsheet in real time. [0] We agreed to meet again next week and again in 4 weeks. Regards; Ian [0] https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAugOWXMj...
On Mon, 17 Sep 2018, Jolliffe, Ian wrote:
and the notes below summarize the outcomes. This does not reflect the outcomes of the direct engagement with the Neutron and Nova teams, that summary will follow.
Here are my notes from Friday afternoon's Nova session, line numbers are in the Nova etherpad as of writing this * Y: vcpu models (begins line 872): (patch 0012, more?) cfriesen to write a spec for listing CPU models in nova.conf * Y: read-only API additions (line 893): (part of patch 0024, others?) one spec and one microversion will cover the additional bits reported in server show returns (GET /servers) * N: non-default quotas (line 907): this is changed in the transition to unified limits in Keystone, can be handled in client libs * Y: I/O semaphore (line 910): (first part of patch 0015) new config option to limit concurrent high-IOPS operations * Y: Flavor extra spec and image validation (line 919): (patch 0022) validate the bits that are not virt driver-specific * Y: periodic orphan resource cleanup (line 927): (patch 0018) add a name check for configured prefixes marked as deleted in database, kill if still running * N: libvirt reboot timeout (line 936): (patch 0020) maybe document hard reboot alternative * N: compute node latency/power mgmt (line 941): new enough libvirt can do this? sean-k-mooney checking, preference to push this into hypervisor * Y: HPET (line 945): (patch 0068) no spec required, bp only; also implemented in cyborg * Y: NUMA-aware live migration (line 953): Artom will continue (spec https://review.openstack.org/#/c/599587/)
Python-Clients: items need to map to main project server-side disposition. Additionally, we agreed we should move the clients as close to master as possible, this can be done independently as this provides users backward compatibility.
More details: client libs, OpenStack SDK and OpenStackClient are all released independently from the main release cycle, although there are cycle stable branches maintained for co-installability/dependency issues. The major client changes are in areas that can be maintained separately from the upstream (OSC plugins, SDK-like addon libs), I would like to consider keeping the user-facing bits as close to current release (maybe not quite on master) as possible.
We made lots of updates to the google-spreadsheet in real time. [0]
I am going back through my notes to update Jira tickets to reflect the spreadsheet changes I made... dt -- Dean Troyer dtroyer@gmail.com
participants (3)
-
Dean Troyer
-
Jolliffe, Ian
-
Rowsell, Brent