On Wed, 21 Nov 2018 12:11:50 -0600, Miguel Lavalle wrote:
One of the key goals of StarlingX during the current cycle is to
converge with the OpenStack projects master branches. In order to
accomplish this goal, the Technical Steering Committee put together a
gap analysis that shows the specs and patches that need to merge in the
different OpenStack projects by the end of Stein. The attached PDF
document shows this analysis. Although other projects are involved, most
of the work has to be done in Nova, Neutron and Horizon. Hopefully all
the involved projects will help StarlingX achieve this important goal.
It has to be noted that work is still on-going to refine this gap
analysis, so there might be some updates to it in the near future.
Thanks for sending this out. I'm going to reply about what I know of the
status of nova-related planned upstream features.
On NUMA-aware live migration, it was identified as the top priority
issue in the NFV/HPC pain points forum session . The spec has been
approved before in the past for the Rocky cycle, so it's a matter of
re-proposing it for re-approval in Stein. We need to confirm with artom
and/or stephenfin whether one of them can pick it up this cycle.
I don't know as much about the shared/dedicated vCPUs on a single host
or the shared vCPU extension, but the cited spec  has one +2 already.
If we can find a second approver, we can work on this too in Stein.
The vTPM support spec was merged about two weeks ago and we are awaiting
implementation patches from cfriesen.
The HPET support spec was merged about two weeks ago and the
implementation patch is under active review in a runway with one +2 now.
For vCPU model, I'm not aware of any new proposed spec for Stein from
the STX community as of today. Let us know if/when the spec is proposed.
For disk performance fixes, the specless blueprint patch is currently
under active review in a runway.
The extra spec validation spec  is under active review now.
For the bits that will be addressed using upstream features that are
already available, I assume the STX community will take care of this.
Please reach out to us in #openstack-nova or on the ML if there are
For the bugs, again feel free to reach out to us for reviews/help.
OpenStack Development Mailing List (not for usage questions)