[openstack-dev] [nova] request spec freeze exception for Add spec for VIF Driver for SR-IOV InfiniBand

/145779/ Thanks, Moshe Levi. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman

Re: [openstack-dev] [nova][sriov] SRIOV related specs pending for approval

Also this one: Nova: Add spec for VIF Driver for SR-IOV InfiniBandhttps://review.openstack.org/131729 https://review.openstack.org/#/c/131729/ From: Robert Li (baoli) [mailto:ba...@cisco.com] Sent: Wednesday, January 07, 2015 5:03 PM To: OpenStack Development Mailing List (not for usage

[openstack-dev] [nova][pci-passthrough] Error: An object of type PciDevicePoolList is required here

Hi, In the latest master nova code I am keep getting this error An object of type PciDevicePoolList is required here My nova.conf contains pci_passthrough_whitelist. When I tried to launch vm after devstack installation the vm was successfully booted. When I restart the compute node and

Re: [openstack-dev] [nova][pci-passthrough] Error: An object of type PciDevicePoolList is required here

] [nova][pci-passthrough] Error: An object of type PciDevicePoolList is required here On Sun, Mar 22, 2015 at 04:58:00PM +, Moshe Levi wrote: Hi, In the latest master nova code I am keep getting this error An object of type PciDevicePoolList is required here My nova.conf contains

Re: [openstack-dev] [neutron]Anyone looking at support for VLAN-aware VMs in Liberty?

Hi Erik, Mellanox is also interested in it but for ML2 plugin with and sriov-nic-switch mechanism driver. I planning to do agent support for the sriov-nic-switch (when the driver will support it), but if you need help in other places I can also pitch in. -Original Message- From: Jay

[openstack-dev] [nova][neutron][SR-IOV]

will arrange BoF session. Time and day are TBD. [1] https://etherpad.openstack.org/p/liberty-sriov Regards, Moshe Levi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev

[openstack-dev] [nova][neutron] bring NIC attributes to OPSK

[1]. [1] https://review.openstack.org/#/c/91275/19/specs/juno/physical-network-topology.rst Please share your thoughts and feel free to comment. Best Regard, Moshe Levi __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [nova] Mellanox CI Issues

. nova/nova/virt/ironic 3. nova/nova/virt/vmwareapi 4. nova/nova/virt/xenapi Is there any Nova CI guidelines for file filtering? Again I would like to apologize for the inconvenient. [1] https://review.openstack.org/#/c/188383/ Thank, Moshe Levi. -Original Message- From: Lenny

Re: [openstack-dev] [nova] Progressing/tracking work on libvirt / vif drivers

Hi Neil, First of all thank for organizing this. Both Infiniband SR-IOV VIF type and Removal of mlnx_direct VIF type are ready for core review. -Original Message- From: Neil Jerram [mailto:neil.jer...@metaswitch.com] Sent: Monday, June 01, 2015 8:38 PM To:

Re: [openstack-dev] PCI pass-through SRIOV

Hi Kamsali, According to the logs you got binding failed error, which mean neutron failed to bind the port. Can you send the neutron server log and the your neutron ml2 conf file? Thank, Moshe Levi From: Kamsali, RaghavendraChari (Artesyn)mailto:raghavendrachari.kams...@artesyn.com

Re: [openstack-dev] PCI pass-through SRIOV

not be initialized You are using intel card therefore I think you should contact them and ask if this card is supported. From: Kamsali, RaghavendraChari (Artesyn) [mailto:raghavendrachari.kams...@artesyn.com] Sent: Tuesday, May 26, 2015 4:49 PM To: Kamsali, RaghavendraChari (Artesyn); Moshe Levi

Re: [openstack-dev] 回复： [Neutron][SR-IOV]How to assign VF to a VM?

-- 原始邮件 -- 发件人: Moshe Levi;mosh...@mellanox.commailto:mosh...@mellanox.com; 发送时间: 2015年8月21日(星期五) 下午5:15 收件人: OpenStack Development Mailing List (not for usage questions)openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org; openstack-operatorsopenstack

Re: [openstack-dev] [Neutron][SR-IOV]How to assign VF to a VM?

The problem is the sriov mechanism drive failed to bind the port. For the log I see that you are working with agent_required=True, but the device mapping is empty {u'devices': 0, u'device_mappings': {} Please check the agent configuration file see that you have the following [securitygroup]

Re: [openstack-dev] sr-iov kilo getting libvirtd error while spawning a vm

Hi, The driver name should be kvm and not qemu. interface type=hostdev managed=yes mac address=fa:16:3e:eb:38:da/ driver name=qemu/ source address type=pci domain=0x bus=0x81 slot=0x02 function=0x7/ /source vlan tag id=1009/ /vlan

[openstack-dev] [nova][FFE] Feature Freeze Exception Request for 'Adding support for InfiniBand SR-IOV vif type'

/187054/ and not merging this will break the mlnx mechanism driver in the neutron core. The code is self-contained and very minimal. Thanks, Moshe Levi. __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [neutron][sriov] SRIOV-VM could not work well with normal VM

> -Original Message- > From: yujie [mailto:judy_yu...@126.com] > Sent: Tuesday, October 20, 2015 5:34 AM > To: Moshe Levi <mosh...@mellanox.com> > Cc: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org>

Re: [openstack-dev] [Nova] SR-IOV subteam

Maybe we can you use the pci- passthrough meeting slot http://eavesdrop.openstack.org/#PCI_Passthrough_Meeting It been a long time since we had a meeting. > -Original Message- > From: Nikola Đipanov [mailto:ndipa...@redhat.com] > Sent: Tuesday, November 03, 2015 6:53 AM > To:

[openstack-dev] [neutron][SR-IOV] deprecate agent_required option for SR-IOV mechanism driver

://eavesdrop.openstack.org/meetings/pci_passthrough/2015/pci_passthrough.2015-06-23-13.09.log.txt [2] - sriov: update port state even if ip link fails - https://review.openstack.org/#/c/195060/ [3] - SR-IOV: deprecate agent_required option - https://review.openstack.org/#/c/214324/ Thanks, Moshe Levi

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

> -Original Message- > From: Sean M. Collins [mailto:s...@coreitpro.com] > Sent: Thursday, October 01, 2015 6:42 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [neutron] New cycle started. What

Re: [openstack-dev] [neutron][sriov] SRIOV-VM could not work well with normal VM

Hi Yujie, There is a patch https://review.openstack.org/#/c/198736/ which I wrote to add the mac of the normal instance to the SR-IOV embedded switch so that the packet will go to the PF instead of going to the wire. This is done by using bridge tool with the command "bridge fdb add dev "

Re: [openstack-dev] [neutron] [QoS] meeting rebooted

Just to add more details about the when and where :) We will have a weekly meeting on Wednesday at 1400 UTC in #openstack-meeting-3 http://eavesdrop.openstack.org/#Neutron_QoS_Meeting Thanks, Moshe Levi. > -Original Message- > From: Ihar Hrachyshka [mailto:ihrac...@redh

Re: [openstack-dev] [nova][neutron][os-vif] os-vif core review team membership

rest in os-vif, we came up with a > > cross-section of contributors across the Nova, Neutron and NFV spaces > > to be the initial core team: > > > > Jay Pipes > > Daniel Berrange > > Sean Mooney > > Moshe Levi > > Russell Bryant > > Sahi

[openstack-dev] [nova][SR-IOV/PCI] SR-IOV/PCI CI for mutli node

Hi, As part of the Performance VMs CI and technical debt session we had in Ausin summit, we decide to focus on fixing pci resize and migration bugs. Currently the pci resize patch [1] and migration patch [2] are up for review. The resize patch is tested with Intel PCI CI

Re: [openstack-dev] [ironic][neutron] bonding?

Hi Jim, Neutron is supporting resource tagging [1] which is support currently network resource_type With a simple change is neutron you can also allow resource tagging for port resource_type [2] This will allow you to tags ports and indicate that they are in the same group maybe that can work

[openstack-dev] [tempest][SR-IOV] tempest breaks Mellanox CI

Hi all, A recent change [1] in tempest broke all Mellanox CIs. This is the second time it happened. After the first time it happened we decided that Mellanox CI will comment on tempest. On this time I saw that Mellanox CI was commenting on that patch with a failure but was still got

Re: [openstack-dev] [Fuel][Fuel-Library] Nominating Matthew Mosesohn for Fuel Library Core

+1 ☺ From: Ivan Berezovskiy [mailto:iberezovs...@mirantis.com] Sent: Wednesday, February 24, 2016 4:47 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Fuel][Fuel-Library] Nominating Matthew Mosesohn for Fuel

Re: [openstack-dev] [neutron] [nova] scheduling bandwidth resources / NIC_BW_KB resource class

From: Miguel Angel Ajo Pelayo [mailto:majop...@redhat.com] Sent: Friday, April 08, 2016 4:17 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] [nova] scheduling bandwidth resources / NIC_BW_KB resource

Re: [openstack-dev] [nova] The same SRIOV / NFV CI failures missed a regression, why?

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Friday, March 25, 2016 10:20 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova] The same SRIOV / NFV CI failures missed a > regression, why? > > On 03/24/2016 09:35 AM, Matt

Re: [openstack-dev] [nova] The same SRIOV / NFV CI failures missed a regression, why?

> -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Thursday, March 24, 2016 3:35 PM > To: OpenStack Development Mailing List (not for usage questions) d...@lists.openstack.org> > Subject: [openstack-dev] [nova] The same SRIOV / NFV CI failures missed

[openstack-dev] [nova][neutron] restarting SR-IOV/PCI Passthrough meeting

vendors CI representative will join the meeting, so that we can make progress in that area. Please review the etherpad and add stuff that you want to talk about (remember the current focus is on CI and bug fixes) I updated the sriov meeting chair see [2] Thanks, Moshe Levi. [1] - https

[openstack-dev] [nova] race condition with resize

Hi all, While I was working on fixing the resize for pci passthrough [1] I have notice the following issue in resize. If you are using small image and you resize-confirm it very fast the old resources are not getting freed. After debug this issue I found out the root cause of it. A

Re: [openstack-dev] [nova][neutron] restarting SR-IOV/PCI Passthrough meeting

Small correction, the biweekly meetings will start from May 3rd. -Original Message- From: Moshe Levi [mailto:mosh...@mellanox.com] Sent: Friday, April 29, 2016 8:13 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [nova][neutron] restarting SR-IOV/PCI Passthrough

[openstack-dev] [neutron][nova][SR-IOV] SR-IOV meeting May 3 2016 - update

Patches that needs owner - feel free to add your irc name to the patches you think you can continue [1] - https://review.openstack.org/#/c/312107/ [2] - https://etherpad.openstack.org/p/sriov_meeting_agenda Thanks, Moshe Levi

Re: [openstack-dev] [neutron] how to create initial db migration script to sub-project

are now out of date, so I have created a patch [2] for you and we can use this as the new "template patch for initial alembic migrations." Some more comments inline ... Moshe Levi <mosh...@mellanox.com> wrote: > Hi, > > I am trying to create initial db for the networking-m

[openstack-dev] [neutron] how to create initial db migration script to sub-project

Hi, I am trying to create initial db for the networking-mlnx project. I am following this neutron alembic documentation [1]. I added a entrypoint to networking-mlnx setup.cfg neutron.db.alembic_migrations = networking-mlnx = networking_mlnx.db.migration:alembic_migrations I added model.py

[openstack-dev] [neutron] weird behavior of neutron create port with extra dhcp option

Hi, I encounter a weird behavior with neutron create port command. I am using neutron master. When I run this neutron create-port command stack@r-dcs88:/opt/devstack$ neutron port-create --device-id=984b4a6d-a66d-4db7-8acc-1113cd1097ef --device-owner=baremetal:none --mac-address

Re: [openstack-dev] [neutron] Neutron Port MAC Address Uniqueness

: Miguel Angel Ajo Pelayo [mailto:majop...@redhat.com] Sent: Wednesday, August 10, 2016 12:04 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Cc: Armando M. <arma...@gmail.com>; Moshe Levi <mosh...@mellanox.com> Subject:

Re: [openstack-dev] [neutron] Neutron Port MAC Address Uniqueness

iginal Message- From: Moshe Levi Sent: Wednesday, August 10, 2016 5:59 PM To: 'Miguel Angel Ajo Pelayo' <majop...@redhat.com>; OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Cc: Armando M. <arma...@gmail.com> Subject: RE: [openstac

[openstack-dev] [nova][tempest][SR-IOV] SR-IOV CI for Mutli-Node with migration test

Hi all, We are in advance stage of resolving migration with SR-IOV and to improve the coverage in that part. We have proposed the following patches to fix SR-IOV migration and its race conditions: [1] - Allocate PCI devices on migration: https://review.openstack.org/#/c/328983 [2] - Update

Re: [openstack-dev] [neutron][nova][SR-IOV] deprecation of supported_pci_vendor_devs

This is the deprecation patch [2] [2] - https://review.openstack.org/#/c/352812/ -Original Message- From: Moshe Levi [mailto:mosh...@mellanox.com] Sent: Monday, August 08, 2016 3:43 PM To: OpenStack Development Mailing List (not for usage questions) (openstack-dev@lists.openstack.org

[openstack-dev] [neutron][nova][SR-IOV] deprecation of supported_pci_vendor_devs

Hi all, To reduce complexity in configuring SR-IOV I want to deprecate the supported_pci_vendor_devs option [1] in the neutron-server ml2 config. This option is doing extra validation that pci vendor id and product id provided by nova in the neutron port binding profile is matching to the

[openstack-dev] [nova][SR-IOV] PCI/SR-IOV meeting today is canceled 06/28/16

Sorry for the late mail, but I won't be able to chair the meeting today __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [nova][SR-IOV] PCI/SR-IOV meeting today is canceled 08/16/16

Sorry for the late mail, but I won't be able to chair the meeting today __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [ironic-pyhon-agent][DIB] IPA failed to start on Ubuntu because of modprobe path

then ExecStartPre=/sbin/modprobe vfat What is the best way to fix this? Thanks, Moshe Levi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [neutron][l2gatewaty] how to create l2-gateway-create when 2 switches has the same name

--+ (neutron) l2-gateway-connection-create SW1 private L2 Gateway Device ovsdb1 could not be found. Neutron server returns request_ids: ['req-f26351fb-fcf5-4d77-b2fe-8b58ac9057dc'] Thanks, Moshe Levi

[openstack-dev] [neutron][nova][SR-IOV] SR-IOV meetings are canceled between 10/9-10/21

Hi, The 2 SR-IOV meeting between 10/9-10/21 are canceled. We have holidays, so I won't be able to chair the meeting. Thanks, Moshe Levi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe

[openstack-dev] [nova][neutron[SR-IOV] SR-IOV meeting is cancel today

Hi all, Sorry for the late mail, but I have to cancel the meeting today. Thanks, Moshe Levi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

Re: [openstack-dev] [acceleration]Team Biweekly Meeting 2016.11.10 minutes

stack-dev@lists.openstack.org>; rodolfo.alonso.hernan...@intel.com; Michele Paolino <m.paol...@virtualopensystems.com>; Scott Kelso <ske...@lenovo.com>; Roman Dobosz <roman.dob...@intel.com>; Jim Golden <jim.gol...@nist.gov>; Miroslav Halas <mha...@lenovo.com>; Moshe Le

[openstack-dev] [nova][SR-IOV] update the SR-IOV meeting to bi-weekly

Hi all, I would like to update the frequency of the SR-IOV meeting to be bi-weekly [1]. Does anyone see value in keeping it as weekly meeting? [1] - https://review.openstack.org/#/c/405415/ Thanks, Moshe Levi

Re: [openstack-dev] [neutron][networking-l2gw] Unable to create release tag

Hi, I had similar problem with networking-mlnx (I think) and I resolve by creating Annotated Tags Did you create the tag like this “git tag -am "Adding 10.0.0 Ocata tag" -s 10.0.0 gerrit/stable/ocata”? From: Gary Kotton [mailto:gkot...@vmware.com] Sent: Tuesday, March 14, 2017 7:40 AM To:

Re: [openstack-dev] [nova] hardware offload support for openvswitch feature exception

, 2017 4:56 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova] hardware offload support for openvswitch feature exception On 7/26/2017 10:42 PM, Moshe Levi wrote: > Hi all, > > In the last few week I was working on hardware offload support for > openvswitch. &

[openstack-dev] [nova] hardware offload support for openvswitch feature exception

Hi all, In the last few week I was working on hardware offload support for openvswitch. The idea is to leverage SR-IOV technology with OVS control plane management. Just last month the ovs community merged all the required patches to enable this feature [1] should be in OVS-2.8.0. I was working

Re: [openstack-dev] [os-vif] [vif_plug_ovs] Queries on VIF_Type VIFHostDevice

F_Type VIFHostDevice > -Original Message- > From: Moshe Levi [mailto:mosh...@mellanox.com] > Sent: Wednesday, August 9, 2017 3:25 PM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [opensta

Re: [openstack-dev] [os-vif] [vif_plug_ovs] Queries on VIF_Type VIFHostDevice

Hi, 1) you should use neutron port with vnic_type direct 2) yes, just use neutron port with vnic_type direct and confighure the nova compute with pci passthogth whitelist 3) you can configure firewall_driver = openvswitch to work with Conntrack. So in your case if have SR-IOV nic which

Re: [openstack-dev] [nova][vlan trunking] Guest networking configuration for vlan trunk

Hi Robert, The closes thing that I know about is tagging of SR-IOV physical function’s VLAN tag to guests see [1] Maybe you can leverage the same mechanism to config vlan trunking in guest. [1] -

Re: [openstack-dev] [networking-ovn] Support for direct vnic_type

Hi, From Mellanox perspective supporting direct port in OVN is in the plan. One of the reason that we did not contribute this change to OVN was because of that OVN support geneve tunnel and not vxlan. (Mellanox card don't support hw-offloading of geneve). If you want to contribute please go

Re: [openstack-dev] [os-vif] [passthrough] [VifHostDevice]

The ODL part is still not ready. We need to do code changes in odl to make it work see [1] [2] [1] https://git.opendaylight.org/gerrit/#/c/62481/ [2] https://git.opendaylight.org/gerrit/#/c/60259/ We try to make the design as generic as possible so if you have a SR-IOV NIC that support

Re: [openstack-dev] [networking-ovn] Support for direct vnic_type

> -Original Message- > From: pranab boruah [mailto:pranabjyotibor...@gmail.com] > Sent: Friday, September 22, 2017 5:06 PM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Cc: Moshe Levi <mosh

Re: [openstack-dev] [TripleO][DIB] how create triplo overcloud image with latest kernel?

org> Cc: Moshe Levi <mosh...@mellanox.com>; Hasan Qunoo <has...@mellanox.com>; Waleed Musa <wale...@mellanox.com> Subject: Re: [openstack-dev] [TripleO][DIB] how create triplo overcloud image with latest kernel? If you need a guideline about how to build TripleO images with DI

[openstack-dev] [TripleO] Configure SR-IOV VFs in tripleo

Hi all, While working on tripleo-ovs-hw-offload work, I encounter the following issue with SR-IVO. I added -e ~/heat-templates/environments/neutron-sriov.yaml -e ~/heat-templates/environments/host-config-and-reboot.yaml to the overcloud-deploy.sh. The

[openstack-dev] [TripleO] OVS Hardware Offload

/398265/ [4] - https://review.openstack.org/#/c/504911/ [5] - https://review.openstack.org/#/c/502313/ [6] - https://review.openstack.org/#/c/502440/ [7] - https://review.openstack.org/#/c/507100/ [8] - https://review.openstack.org/#/c/507401/ Thanks, Moshe Levi

[openstack-dev] [TripleO][DIB] how create triplo overcloud image with latest kernel?

Hi all, As part of the OVS Hardware Offload [1] [2], we need to create new Centos/Redhat 7 image with latest kernel/ovs/iproute. We tried to use virsh-customize to install the packages and we were able to update iproute and ovs, but for the kernel there is no space. We also tried with

Re: [openstack-dev] [TripleO] Configure SR-IOV VFs in tripleo

eO] Configure SR-IOV VFs in tripleo > > On Tue, Sep 26, 2017 at 3:37 PM, Moshe Levi <mosh...@mellanox.com> > wrote: > > Hi all, > > > > > > > > While working on tripleo-ovs-hw-offload work, I encounter the > > following issue with SR-IVO. > > >

Re: [openstack-dev] [Neutron] Infiniband & Melanox OFED 4.2 eIPoIB support

This more question to mellanox then to neutron community. I suggest that you will send me private mail regarding this issue and we can take it with the relevant people in Mellanox. My email is mosh...@mellanox.com. > -Original Message- > From: Massimo Benini [mailto:ben...@cscs.ch] >

[openstack-dev] [tripleO] building overcloud image with opendaylight

Hi all, We are now working on to support the OVS hardware offload with opendaylight deployment. First setup we want to deploy triple with just opendaylight mechanism driver. I have some question regarding the deployment: 1 . As I understand from the documentation the we need to build overcloud

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

Hi Alex, I don't see the tripleo ovs hardware offload feature. The spec was merge into queens [1], but for some reason the blueprint is not in approve state [2]. I has only 3 patches left: 1. https://review.openstack.org/#/c/507401/ has 2 +2 2. https://review.openstack.org/#/c/507100/ has 1

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

rints moved out to Rocky > > On Fri, Dec 8, 2017 at 6:11 PM, Moshe Levi <mosh...@mellanox.com> wrote: > > Hi Alex, > > > > I don't see the tripleo ovs hardware offload feature. The spec was merge > into queens [1], but for some reason the blueprint is not

[openstack-dev] [tripleo] overcloud keystone error "Could not determine a suitable URL for the plugin"

Hi all, We deploy tripleo master using quickstart. We this delorean repo: name=delorean baseurl=https://trunk.rdoproject.org/centos7-master/ac/82/ac82ea9271a4ae3860528eaf8a813da7209e62a6_28eeb6c7/ The undercloud and overcloud deployment were successfully, but we I try to run command on the

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

I believe so, Just regarding the use of sample-env-generator tool is not supporting parameters for roles: Such as : # Kernel arguments for ComputeSriov node ComputeSriovParameters: KernelArgs: "intel_iommu=on iommu=pt" OvsHwOffload: True So can we merged the patches as is and fix

Re: [openstack-dev] [tripleo] overcloud keystone error "Could not determine a suitable URL for the plugin"

ndercloud access to that network. So, if it's a virtual environment and you're running that command from the undercloud (which from the log you sent it seems that's the case) you need to run that. Note that you need to run that every time you update your undercloud. BR On 6 Dec 2017 09:06, &qu

Re: [openstack-dev] [tripleo] overcloud keystone error "Could not determine a suitable URL for the plugin"

ripleo] overcloud keystone error "Could not determine a suitable URL for the plugin" On 6 Dec 2017 16:58, "Moshe Levi" <mosh...@mellanox.com<mailto:mosh...@mellanox.com>> wrote: I have the access to 10.0.0.0 network I remove the -e /home/stack/enable-tls.yaml

Re: [openstack-dev] [os-vif] [nova] Changes to os-vif cores

> -Original Message- > From: Sahid Orentino Ferdjaoui [mailto:sferd...@redhat.com] > Sent: Wednesday, October 25, 2017 11:22 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [os-vif] [nova] Changes

Re: [openstack-dev] [tripleo] odl deployment failed due to opendaylight websocket config in haproxy

ling List (not for usage questions) <openstack-dev@lists.openstack.org>; Moshe Levi <mosh...@mellanox.com> Subject: Re: [openstack-dev] [tripleo] odl deployment failed due to opendaylight websocket config in haproxy Hi Moshe There is a corresponding ODL patch [1]. To verify if the r

[openstack-dev] [tripleO] quickstart with containers deployment failed

Hi, We are trying to add container support ovs hw offload. We were able to do the deployment a few weeks ago, but now we getting an errors . Jan 14 07:14:32 localhost os-collect-config: "2018-01-14 07:14:28,568 WARNING: 18476 -- retrying pulling image:

[openstack-dev] [tripleo][opendaylight puppet] failed to deploy odl master with latest opendaylight puppet

Hi all, We are trying to test solution of the odl hw offload in tripleo. We have already merged the odl support for ovs hardware offload [1]. We are trying to test that everting is working with tripleo, but we get failure with jetty.xml.orig. For some reason it get configure like [2] and causing

Re: [openstack-dev] [tripleo] opendaylight OpenDaylightConnectionProtocol deprecation issue

> -Original Message- > From: Ben Nemec [mailto:openst...@nemebean.com] > Sent: Wednesday, January 31, 2018 5:10 PM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org>; Moshe Levi > <mosh...@mellanox.com>

[openstack-dev] [tripleo] opendaylight OpenDaylightConnectionProtocol deprecation issue

Hi all, It seem that this commit [1] deprecated the OpenDaylightConnectionProtocol, but it also remove it. This is causing the following issue when we deploy opendaylight non containerized. See [2] One solution is to add back the OpenDaylightConnectionProtocol [3] the other solution is to

[openstack-dev] [ironic][triploe] support for firmware update

Hi all, I saw that ironic-python-agent support custom hardware manager. I would like to support firmware updates (In my case Mellanox nic) and I was wandering how custom hardware manager can be used in such case? How it is integrated with ironic-python agent and also is there an integration to

[openstack-dev] [ironic][neutron] bare metal on vxlan network

Hi all, Ironic supports mutli tenancy for quite few releases and according to the spec [1] it can work with vlan/vxlan networks. I see lot of mechanism driver that support vlan network such as [2] and [3] , but I didn't find any mechanism driver that work on vxlan network. Is there a mechanism

[openstack-dev] [tripleo] odl deployment failed due to opendaylight websocket config in haproxy

Hi all, When I try to deploy tripleo with opendaylight oxygen release (we did a private build for master) it failed with haproxy failing that it can't bind the opendaylight_ws: cannot bind socket see [1]. This is failing all the deployment as the haproxy is down. The opendaylight_ws was

[openstack-dev] [tripleo] tripleo-heat-templates CI is not unit test

Hi all, While working on improving the environment_generator.py we found out that the unit test are broken see fix in [1] This is happened because no CI job in tripleo-heat-templates runes tox -epy27. Can you please add this job to tripleo-heat-templates? [1] -

[openstack-dev] [tripleo][nova] nova rx_queue_size tx_queue_size config options breaks booting vm with SR-IOV

Hi all, Recent change in tripleo [1] configure nova rx_queue_size tx_queue_size config by default. It seem that this config option breaks booting vm with SR-IOV. See [2] The issues is because of this code [3] which configure virtio queue size if the in the interface xml the driver is vhost or

[openstack-dev] testing 123

__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Removing networking-mlnx from Debian?

> -Original Message- > From: Jeremy Stanley [mailto:fu...@yuggoth.org] > Sent: Friday, April 13, 2018 3:08 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] Removing networking-mlnx from Debian? > >

Re: [openstack-dev] Removing networking-mlnx from Debian?

Hi Thomas, Networking-mlnx is still maintained. We will fix all the issues next week and I will create a tag for it. > -Original Message- > From: Thomas Goirand [mailto:z...@debian.org] > Sent: Friday, April 13, 2018 2:50 PM > To: OpenStack Development Mailing List

Re: [openstack-dev] Removing networking-mlnx from Debian?

working-mlnx from Debian? > > On 2018-04-13 14:17:29 + (+), Moshe Levi wrote: > [...] > > Yes, How can we add python3 job in zuul for testing it? > > I've proposed > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frev > iew.open

Re: [openstack-dev] Removing networking-mlnx from Debian?

__ summary ___ py34: commands succeeded congratulations :) > -Original Message- > From: Moshe Levi > Sent: Friday, April 13, 201

Re: [openstack-dev] [ironic][neutron] SmartNics with Ironic

][neutron] SmartNics with Ironic Greetings, Comments in-line. Thanks, -Julia On Sat, Sep 29, 2018 at 11:27 PM Moshe Levi mailto:mosh...@mellanox.com>> wrote: Hi Julia, I don't mind to update the ironic spec [1]. Unfortunately, I wasn't in the PTG but I had a sync meeting with Isuku. As

Re: [openstack-dev] [ironic][neutron] SmartNics with Ironic

Hi Julia, I don't mind to update the ironic spec [1]. Unfortunately, I wasn't in the PTG but I had a sync meeting with Isuku. As I see it there is 2 use-cases: 1. Running the neutron ovs agent in the smartnic 2. Running the neutron super ovs agent which manage the ovs running on the