[Openstack] [nova] PCI alias attribute numa_policy ignored when flavor has hw:cpu_policy=dedicated set

Hi folks, It appears that the numa_policy attribute of a PCI alias is ignored for flavors referencing that alias if the flavor also has hw:cpu_policy=dedicated set. The alias config is: alias = { "name": "mlx", "device_type": "type-VF", "vendor_id": "15b3", "product_id": "1004", "numa_policy":

[openstack-dev] [kolla][iconic] baremetal network

Dear Kolla-ansible team, I am trying to deploy ironic through kolla-ansible. According to ironic documentation https://docs.openstack.org/ironic/rocky/install/configure-networking.html we need bare metal network with tenant_network_types = flat. However kolla-ansible configures:

Re: [openstack-dev] [tripleo] using molecule to test ansible playbooks and roles

On Sun, Nov 11, 2018 at 11:29:43AM +, Sorin Sbarnea wrote: > I recently came across molecule a > project originated at Cisco which recently become an officially Ansible > project, at the same time as ansible-lint. Both projects were transferred > from

Re: [openstack-dev] [neutron][neutron-release] feature/graphql branch rebase

On 10/11/18 12:03 am, Jeremy Stanley wrote: On 2018-11-09 16:35:22 +1100 (+1100), Gilles Dubreuil wrote: Could you please provide permission [1] to upload commit merges? I'm getting the following error after merging HEAD: $ git review -R feature/graphql remote: remote: Processing changes:

[openstack-dev] [tripleo] using molecule to test ansible playbooks and roles

I recently came across molecule a project originated at Cisco which recently become an officially Ansible project, at the same time as ansible-lint. Both projects were transferred from their former locations to Ansible github organization -- I guess as a