hi
just following up form yesterday.
i just finished testing the pci numa policy feature
and i can confirm that the prefer policy which allow use of non
local pci devices does not work.
the test case was relitively simple
1 host with 2 numa nodes
1 pci device attach to numa node 0
and vcpu pin
Hi Miguel,
There is another RFE “Add l2pop support for floating IP resources” proposed to
Launchpad. This RFE also comes from StarlingX and the link is below:
https://bugs.launchpad.net/neutron/+bug/1803494
Could you please help review this RFE? I think this RFE can be added to the gap
analysis.
On Wed, 21 Nov 2018 21:23:51 +0100, Melanie Witt wrote:
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
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
Thanks for doing this in the open and working with the upstream teams to
reduce divergence!
On Wed, Nov 21, 2018 at 1:17 PM Miguel Lavalle wrote:
> Hi Stackers,
>
> One of the key goals of StarlingX during the current cycle is to converge
> with the OpenStack projects master branches. In order
