On 3/26/2019 2:03 PM, Dean Troyer wrote:
The upstreaming effort is still in progress with 31 items across 5 projects complete (or expected to still make Stein) and 20 items remaining to be completed, all in Nova. In preparing for the May release of StarlingX we have identified from this list of 20 items 3 features and 8 bug fixes as critical for the release.
Funny coincidence because I was just triaging this nova bug this morning: https://bugs.launchpad.net/nova/+bug/1821755 And referenced the starlingx fix for it in there, but now I've also duplicated it against the old bug linked in the spreadsheet. I did leave some comments in the bug that are likely limitations in the starlingx solution which work for starlingx when you have 1-2 nodes in an edge site with 1-2 nova-conductor services, but likely wouldn't be sufficient in a large public cloud with nova-conductor services spread across multiple hosts (unless some distributed lock manager is being used, which I don't think oslo.concurrency supports under the covers does it?). Skimming the other items in the spreadsheet they mostly look like already in-progress items upstream, are planned for discussion at the PTG, or are related to server groups (which is a known haven for race issues since we don't model affinity in placement yet).
If you have any questions or concerns please reply here, contact me or anyone on the StarlingX TSC, or find us in IRC at #starlingx.
Thanks for the update and transparency here.
dt
[0] The work items are listed in the 'Stein Backport Items' tab of the following spreadsheet: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1... * The last item marked for Glance and Cinder is out of scope here, it is work in a StarlingX project repo
-- Thanks, Matt