Re: [Openstack] [User-committee] Stepping aside announcement

[Yih Leong, Sun.]

Sad to hear but thanks for your contributions and I enjoyed the time
working with you!


On Monday, January 29, 2018, Edgar Magana  wrote:

> Dear Community,
>
>
>
> This is an overdue announcement but I was waiting for the right moment and
> today it is with the opening of the UC election. It has been almost seven
> years of full commitment to OpenStack and the entire ecosystem around it.
> During the last couple of years, I had the opportunity to serve as Chair of
> the User Committee. I have participated in this role with nothing more
> important but passion and dedication for the users and operators. OpenStack
> has been very important for me and it will be always the most enjoyable
> work I have ever done.
>
>
>
> It is time to move on. Our team is extending its focus to other cloud
> domains and I will be leading one of the those. Therefore, I would like to
> announce that I am stepping aside from my role as UC Chair. Per our UC
> election, there will be no just 2 seats available but three:
> https://governance.openstack.org/uc/reference/uc-election-feb2018.html
>
>
>
> I want to encourage the whole AUC community to participate, be part of the
> User Committee is a very important and grateful activity. Please, go for it!
>
>
>
> Thank you all,
>
>
>
> Edgar Magana
>
> Sr. Principal Architect
>
> Workday, Inc.
>
>
>
>
>
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [User-committee] Stepping aside announcement

[Melvin Hillsman]

Thanks for your service to the community Edgar! Hope to see you at an event
soon and we can toast to your departure and continued success!

On Mon, Jan 29, 2018 at 11:59 AM, Amy Marrich  wrote:

> Edgar,
>
> Thank you for all your hard work and contributions!
>
> Amy (spotz)
>
> On Mon, Jan 29, 2018 at 11:12 AM, Edgar Magana 
> wrote:
>
>> Dear Community,
>>
>>
>>
>> This is an overdue announcement but I was waiting for the right moment
>> and today it is with the opening of the UC election. It has been almost
>> seven years of full commitment to OpenStack and the entire ecosystem around
>> it. During the last couple of years, I had the opportunity to serve as
>> Chair of the User Committee. I have participated in this role with nothing
>> more important but passion and dedication for the users and operators.
>> OpenStack has been very important for me and it will be always the most
>> enjoyable work I have ever done.
>>
>>
>>
>> It is time to move on. Our team is extending its focus to other cloud
>> domains and I will be leading one of the those. Therefore, I would like to
>> announce that I am stepping aside from my role as UC Chair. Per our UC
>> election, there will be no just 2 seats available but three:
>> https://governance.openstack.org/uc/reference/uc-election-feb2018.html
>>
>>
>>
>> I want to encourage the whole AUC community to participate, be part of
>> the User Committee is a very important and grateful activity. Please, go
>> for it!
>>
>>
>>
>> Thank you all,
>>
>>
>>
>> Edgar Magana
>>
>> Sr. Principal Architect
>>
>> Workday, Inc.
>>
>>
>>
>>
>>
>>
>>
>> ___
>> User-committee mailing list
>> user-commit...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>>
>>
>
> ___
> User-committee mailing list
> user-commit...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>
>


-- 
Kind regards,

Melvin Hillsman
mrhills...@gmail.com
mobile: (832) 264-2646
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [User-committee] Stepping aside announcement

[Amy Marrich]

Edgar,

Thank you for all your hard work and contributions!

Amy (spotz)

On Mon, Jan 29, 2018 at 11:12 AM, Edgar Magana 
wrote:

> Dear Community,
>
>
>
> This is an overdue announcement but I was waiting for the right moment and
> today it is with the opening of the UC election. It has been almost seven
> years of full commitment to OpenStack and the entire ecosystem around it.
> During the last couple of years, I had the opportunity to serve as Chair of
> the User Committee. I have participated in this role with nothing more
> important but passion and dedication for the users and operators. OpenStack
> has been very important for me and it will be always the most enjoyable
> work I have ever done.
>
>
>
> It is time to move on. Our team is extending its focus to other cloud
> domains and I will be leading one of the those. Therefore, I would like to
> announce that I am stepping aside from my role as UC Chair. Per our UC
> election, there will be no just 2 seats available but three:
> https://governance.openstack.org/uc/reference/uc-election-feb2018.html
>
>
>
> I want to encourage the whole AUC community to participate, be part of the
> User Committee is a very important and grateful activity. Please, go for it!
>
>
>
> Thank you all,
>
>
>
> Edgar Magana
>
> Sr. Principal Architect
>
> Workday, Inc.
>
>
>
>
>
>
>
> ___
> User-committee mailing list
> user-commit...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [User-committee] Stepping aside announcement

[Shamail Tahir]

> On Jan 29, 2018, at 12:12 PM, Edgar Magana  wrote:
> 
> Dear Community,
>  
> This is an overdue announcement but I was waiting for the right moment and 
> today it is with the opening of the UC election. It has been almost seven 
> years of full commitment to OpenStack and the entire ecosystem around it. 
> During the last couple of years, I had the opportunity to serve as Chair of 
> the User Committee. I have participated in this role with nothing more 
> important but passion and dedication for the users and operators. OpenStack 
> has been very important for me and it will be always the most enjoyable work 
> I have ever done.
>  
> It is time to move on. Our team is extending its focus to other cloud domains 
> and I will be leading one of the those. Therefore, I would like to announce 
> that I am stepping aside from my role as UC Chair. Per our UC election, there 
> will be no just 2 seats available but three: 
> https://governance.openstack.org/uc/reference/uc-election-feb2018.html

Thank you for everything you’ve done for the community thus far Edgar! Your 
leadership has been instrumental in helping us evolve over the last 2-3 cycles. 
I hope you are still able to participate in the community even after you leave 
the User Committee.
>  
> I want to encourage the whole AUC community to participate, be part of the 
> User Committee is a very important and grateful activity. Please, go for it!
>  
> Thank you all,
>  
> Edgar Magana
> Sr. Principal Architect
> Workday, Inc.
>  
>  
>  
> ___
> User-committee mailing list
> user-commit...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Stepping aside announcement

[Edgar Magana]

Dear Community,

This is an overdue announcement but I was waiting for the right moment and 
today it is with the opening of the UC election. It has been almost seven years 
of full commitment to OpenStack and the entire ecosystem around it. During the 
last couple of years, I had the opportunity to serve as Chair of the User 
Committee. I have participated in this role with nothing more important but 
passion and dedication for the users and operators. OpenStack has been very 
important for me and it will be always the most enjoyable work I have ever done.

It is time to move on. Our team is extending its focus to other cloud domains 
and I will be leading one of the those. Therefore, I would like to announce 
that I am stepping aside from my role as UC Chair. Per our UC election, there 
will be no just 2 seats available but three: 
https://governance.openstack.org/uc/reference/uc-election-feb2018.html

I want to encourage the whole AUC community to participate, be part of the User 
Committee is a very important and grateful activity. Please, go for it!

Thank you all,

Edgar Magana
Sr. Principal Architect
Workday, Inc.



___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Regarding Openings on Red Hat's Public Sector Team for OpenStack Engineers

[Jeremy Stanley]

On 2018-01-29 07:36:51 -0500 (-0500), Suzie Grieco wrote:
> May I request the following to be forwarded to members of your OpenStack
> mailing list?
[...]

In the future, please post OpenStack-related job openings at
https://www.openstack.org/community/jobs/ instead of on our
discussion lists. Thanks!
-- 
Jeremy Stanley


signature.asc
Description: PGP signature
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance

[Navdeep Uniyal]

Hi Moshe,

Thank you.

Dear All,

Has anyone worked with intel NICs to enable SRIOV in Openstack. If yes, please 
if you could help me in configuring the NIC to be made suitable for Openstack 
to pick up. Currently, I am facing issues with Libvirt failing to list the 
node. With driver i40evf running, it lists the interfaces. However, if I 
disable the i40evf driver it does not list the interfaces in nodedev-list. 
Please if someone could verify this as right behaviour or not.


Kind Regards,
Navdeep

From: Moshe Levi [mailto:mosh...@mellanox.com]
Sent: 29 January 2018 12:00
To: Navdeep Uniyal ; openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Hi Nadepp,

I am not familiar  with Intel NIC  (I work at Mellanox)
Maybe the intel folks in the mailing list can help you.


From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk]
Sent: Monday, January 29, 2018 1:58 PM
To: Moshe Levi mailto:mosh...@mellanox.com>>; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Hi Moshe,

Thank you for your response.

I am creating VFs on intel X710 NIC. As per the documentation I need to disable 
'i40evf driver' on the host machine to get the VMs running with the VFs 
however, on doing so I am not getting the VF list while doing 'virsh 
nodedev-list'. Could you please advise if this driver is required to be running 
or not.


Best Regards,
Navdeep

From: Moshe Levi [mailto:mosh...@mellanox.com]
Sent: 29 January 2018 09:30
To: Navdeep Uniyal 
mailto:navdeep.uni...@bristol.ac.uk>>; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Can you try to restart libvirtd and query again "virsh nodedev-list"

From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk]
Sent: Monday, January 29, 2018 10:32 AM
To: Moshe Levi mailto:mosh...@mellanox.com>>; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Hi Moshe,

Thank you very much for your response. I could see the list of nodes using 
virsh:

net_enp129s0f0_3c_fd_fe_a9_37_c0
net_enp129s0f1_3c_fd_fe_a9_37_c1
net_enp129s2_36_a5_18_f7_41_c6
net_enp129s2f1_96_b0_b3_37_cf_c5
net_enp129s2f2_0e_0c_63_76_07_0f
net_enp129s2f3_36_ca_41_10_7f_62
net_enp129s2f4_f2_79_ee_75_38_a9
net_enp129s2f5_2a_a1_c6_02_55_11
net_enp129s2f6_16_e3_c4_01_8c_6d
net_enp129s2f7_66_56_63_d8_a8_ad

these does not have the node 'net_enp129s2_b2_87_6e_13_a1_5e' listed. Could you 
please help me finding out what could be the reason behind this mismatch.


Kind Regards,
Navdeep Uniyal

From: Moshe Levi [mailto:mosh...@mellanox.com]
Sent: 29 January 2018 06:50
To: Navdeep Uniyal 
mailto:navdeep.uni...@bristol.ac.uk>>; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Hi Navdeep,

The errors you are pointing out shouldn't cause  error while creating instance 
with SR-IOV/PCI passthrough.
They are part of the SR-IOV nic capabilities feature which is not completed yet.

Libvirt "virsh nodedev-list" command will show you the list of nic and this 
method [1] will look it in the hypervisor.
For some reason you have a mismatch here. You need to compare them.  Anyway if 
there is a mismatch it just won't report the capabilities of the nic.
As I mentioned above I think this is not the issue for the error while creating 
instance

[1] 
https://github.com/openstack/nova/blob/91f7a88b3f857d738d39984117e6c514cbec/nova/pci/utils.py#L196-L217


From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk]
Sent: Sunday, January 28, 2018 10:58 PM
To: openstack@lists.openstack.org
Subject: [Openstack] Openstack SRIOV and PCI passthrough error while creating 
instance

Dear All,

I am getting an error while creating SRIOV enabled instances following the 
guide from Openstack pike 
https://docs.openstack.org/neutron/pike/admin/config-sriov.html



I want to start an instance on open

[Openstack] Regarding Openings on Red Hat's Public Sector Team for OpenStack Engineers

[Suzie Grieco]

Hello,

May I request the following to be forwarded to members of your OpenStack
mailing list?

Red Hat's public sector team is looking for OpenStack engineers with
experience implementing in a production environment.  Having a Top Secret
or higher clearance would be a plus!  Below is the position description
along with a link
.
If interested in learning more, please schedule time to talk to Suzie
Grieco at SG2 Recruiting using scheduler in signature line


SG2 Recruiting is a Red Hat Public Sector Team recruiting partner and we
are seeking OpenStack systems engineers and architects to join their
growing team creating innovative open source solutions for government
clients. Responsible for post sales project delivery and support, you will
apply consulting experience, systems engineering and design as well as
strong knowledge of relevant IT trends to solve complex problems.
Certifications aren't required-- just the technical curiosity and
willingness to learn! Your key responsibilities will include:


   - Serving as the lead consultant on a large consulting projects
 utilizing several different technologies to create and architect the
 solution
 - Coordinating architecture and dependencies with other teams in a
 broad technical context, and demonstrating an understanding of the
 consequences of technological choices.
 - Applying proven industry standards and practices as they relate
 to projects and solutions led by the architect
 - Remaining current on IT trends pertaining to their area of
 practice (e.g., Agile, DevOps, containerization, microservices)
 - Identifying client opportunities spanning multiple technical
 disciplines.
 - Serving as a technical mentor for consultants, providing
 valuable, timely, and accurate technical leadership by
sharing knowledge
 and best practices associated with Red Hat product stack,
including OSes,
 virtualization, middleware, storage, messaging, and cloud.

Requirements:


   - 8+ years experience as a consultant, system architect or
 implementation lead, operating in a senior capacity in the open source
 community
 - BS degree in computer science, MIS or related field
 - You are able to obtain US Government security clearances
 - Strong OpenStack deployment and troubleshooting skills with
 Director, preferably to a code level using Python
 - Hands on experience with Puppet, Heat Templates, and Ansible
 - Red Hat Satellite 6
 - Basic knowledge of Internet Protocol Address (IPA) components
 - Ability to support clients throughout DC Metro Area

Desired Qualifications (one or more of the following):


   - You have an active TS/SCI clearance with ability to obtain and
 maintain higher level clearances
 - Interest in open source technology and community
 - Red Hat Certified Engineer (RHCE) Certification
 - Red Hat Certified Architect (RHCA) Certification

Similar Job Titles:


   - OpenStack Engineer
 - OpenStack Cloud Systems Engineer
 - Senior OpenStack Deployment Engineer
 - Cloud Infrastructure Engineer


Suzie Grieco | President
SG2 Recruiting 
703.675.6286 | sgri...@sg2recruiting.com

Visit me on LinkedIn 
Schedule a meeting

with
me.


Thank you in advance for sharing with the OpenStack listserve!

Suzie

--

Suzie Grieco | President
SG2 Recruiting 
703.675.6286 | sgri...@sg2recruiting.com

Visit me on LinkedIn .
Check out our current openings. 
Schedule a meeting

with
me.
---
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [ironic] how to prevent ironic user to controle ipmi through OS?

[Tomáš Vondra]

How about HPE iLO, does anyone know a way to disable access from the OS?

 

From: Tyler Bishop [mailto:tyler.bis...@beyondhosting.net] 
Sent: Sunday, January 28, 2018 2:01 AM
To: Guo James
Cc: openstack
Subject: Re: [Openstack] [ironic] how to prevent ironic user to controle ipmi 
through OS?

 

On dell DRAC you can disable IPMI/RAC control at the the device for OS 
configuration.

 

With Supermicro IPMI you just need to create a random user and random password 
that is not "admin".

 

 

_

Tyler Bishop

Founder EST 2007

 

Obrázek byl odebrán odesílatelem.

 

O: 513-299-7108 x10

M: 513-646-5809

http://BeyondHosting.net

 

 

This email is intended only for the recipient(s) above and/or otherwise 
authorized personnel. The information contained herein and attached is 
confidential and the property of Beyond Hosting. Any unauthorized copying, 
forwarding, printing, and/or disclosing any information related to this email 
is prohibited. If you received this message in error, please contact the sender 
and destroy all copies of this email and any attachment(s).

 

  _  

From: "Guo James" 
To: xief...@sina.com, "openstack" 
Sent: Wednesday, January 10, 2018 10:16:34 PM
Subject: Re: [Openstack] [ironic] how to prevent ironic user to controle ipmi 
through OS?

 

Ironic user can change ipmi address so that OpenStack ironic lose control of 
bare mental.

I think that is unacceptable.

It seems that we should make ironic image without root privilege

 

From: xief...@sina.com [mailto:xief...@sina.com] 
Sent: Thursday, January 11, 2018 9:12 AM
To: Guo James; openstack
Subject: 回复：[Openstack] [ironic] how to prevent ironic user to controle ipmi 
through OS?

 

If you can not get the usename and password of the OS, you can not modify ipmi 
configuration through you got the ironic user info.

 

 

- 原始邮件 -
发件人：Guo James 
收件人："openstack@lists.openstack.org" 
主题：[Openstack] [ironic] how to prevent ironic user to controle ipmi through OS?
日期：2018年01月10日 17点21分


I notice that after an ironic user get a bare mental successfully, he can 
access ipmi through ipmi device although he can't access ipmi through LAN
How to prevent the situation?
If he modify ipmi configuration, that will be mess.
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance

[Moshe Levi]

Hi Nadepp,

I am not familiar  with Intel NIC  (I work at Mellanox)
Maybe the intel folks in the mailing list can help you.


From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk]
Sent: Monday, January 29, 2018 1:58 PM
To: Moshe Levi ; openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Hi Moshe,

Thank you for your response.

I am creating VFs on intel X710 NIC. As per the documentation I need to disable 
'i40evf driver' on the host machine to get the VMs running with the VFs 
however, on doing so I am not getting the VF list while doing 'virsh 
nodedev-list'. Could you please advise if this driver is required to be running 
or not.


Best Regards,
Navdeep

From: Moshe Levi [mailto:mosh...@mellanox.com]
Sent: 29 January 2018 09:30
To: Navdeep Uniyal 
mailto:navdeep.uni...@bristol.ac.uk>>; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Can you try to restart libvirtd and query again "virsh nodedev-list"

From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk]
Sent: Monday, January 29, 2018 10:32 AM
To: Moshe Levi mailto:mosh...@mellanox.com>>; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Hi Moshe,

Thank you very much for your response. I could see the list of nodes using 
virsh:

net_enp129s0f0_3c_fd_fe_a9_37_c0
net_enp129s0f1_3c_fd_fe_a9_37_c1
net_enp129s2_36_a5_18_f7_41_c6
net_enp129s2f1_96_b0_b3_37_cf_c5
net_enp129s2f2_0e_0c_63_76_07_0f
net_enp129s2f3_36_ca_41_10_7f_62
net_enp129s2f4_f2_79_ee_75_38_a9
net_enp129s2f5_2a_a1_c6_02_55_11
net_enp129s2f6_16_e3_c4_01_8c_6d
net_enp129s2f7_66_56_63_d8_a8_ad

these does not have the node 'net_enp129s2_b2_87_6e_13_a1_5e' listed. Could you 
please help me finding out what could be the reason behind this mismatch.


Kind Regards,
Navdeep Uniyal

From: Moshe Levi [mailto:mosh...@mellanox.com]
Sent: 29 January 2018 06:50
To: Navdeep Uniyal 
mailto:navdeep.uni...@bristol.ac.uk>>; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Hi Navdeep,

The errors you are pointing out shouldn't cause  error while creating instance 
with SR-IOV/PCI passthrough.
They are part of the SR-IOV nic capabilities feature which is not completed yet.

Libvirt "virsh nodedev-list" command will show you the list of nic and this 
method [1] will look it in the hypervisor.
For some reason you have a mismatch here. You need to compare them.  Anyway if 
there is a mismatch it just won't report the capabilities of the nic.
As I mentioned above I think this is not the issue for the error while creating 
instance

[1] 
https://github.com/openstack/nova/blob/91f7a88b3f857d738d39984117e6c514cbec/nova/pci/utils.py#L196-L217


From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk]
Sent: Sunday, January 28, 2018 10:58 PM
To: openstack@lists.openstack.org
Subject: [Openstack] Openstack SRIOV and PCI passthrough error while creating 
instance

Dear All,

I am getting an error while creating SRIOV enabled instances following the 
guide from Openstack pike 
https://docs.openstack.org/neutron/pike/admin/config-sriov.html



I want to start an instance on openstack pike with SRIOV enabled NICs. However, 
I am getting a Libvirt error regarding the node name. The error looks weird as 
the node name is not matching the interface name on the host machine or in the 
configuration files.

2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager 
[req-caa92f1d-5ac1-402d-a8bc-b08ab350a21f - - - - -] Error updating resources 
for node jupiter.: libvirtError: Node device not found: no node device with 
matching name 'net_enp129s2_b2_87_6e_13_a1_5e' 2018-01-28 20:40:11.416 2953 
ERROR nova.compute.manager Traceback (most recent call last): 2018-01-28 
20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 6696, in 
update_available_resource_for_node 2018-01-28 20:40:11.416 2953 ERROR 
nova.

Re: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance

[Navdeep Uniyal]

Hi Moshe,

Thank you for your response.

I am creating VFs on intel X710 NIC. As per the documentation I need to disable 
'i40evf driver' on the host machine to get the VMs running with the VFs 
however, on doing so I am not getting the VF list while doing 'virsh 
nodedev-list'. Could you please advise if this driver is required to be running 
or not.


Best Regards,
Navdeep

From: Moshe Levi [mailto:mosh...@mellanox.com]
Sent: 29 January 2018 09:30
To: Navdeep Uniyal ; openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Can you try to restart libvirtd and query again "virsh nodedev-list"

From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk]
Sent: Monday, January 29, 2018 10:32 AM
To: Moshe Levi mailto:mosh...@mellanox.com>>; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Hi Moshe,

Thank you very much for your response. I could see the list of nodes using 
virsh:

net_enp129s0f0_3c_fd_fe_a9_37_c0
net_enp129s0f1_3c_fd_fe_a9_37_c1
net_enp129s2_36_a5_18_f7_41_c6
net_enp129s2f1_96_b0_b3_37_cf_c5
net_enp129s2f2_0e_0c_63_76_07_0f
net_enp129s2f3_36_ca_41_10_7f_62
net_enp129s2f4_f2_79_ee_75_38_a9
net_enp129s2f5_2a_a1_c6_02_55_11
net_enp129s2f6_16_e3_c4_01_8c_6d
net_enp129s2f7_66_56_63_d8_a8_ad

these does not have the node 'net_enp129s2_b2_87_6e_13_a1_5e' listed. Could you 
please help me finding out what could be the reason behind this mismatch.


Kind Regards,
Navdeep Uniyal

From: Moshe Levi [mailto:mosh...@mellanox.com]
Sent: 29 January 2018 06:50
To: Navdeep Uniyal 
mailto:navdeep.uni...@bristol.ac.uk>>; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Hi Navdeep,

The errors you are pointing out shouldn't cause  error while creating instance 
with SR-IOV/PCI passthrough.
They are part of the SR-IOV nic capabilities feature which is not completed yet.

Libvirt "virsh nodedev-list" command will show you the list of nic and this 
method [1] will look it in the hypervisor.
For some reason you have a mismatch here. You need to compare them.  Anyway if 
there is a mismatch it just won't report the capabilities of the nic.
As I mentioned above I think this is not the issue for the error while creating 
instance

[1] 
https://github.com/openstack/nova/blob/91f7a88b3f857d738d39984117e6c514cbec/nova/pci/utils.py#L196-L217


From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk]
Sent: Sunday, January 28, 2018 10:58 PM
To: openstack@lists.openstack.org
Subject: [Openstack] Openstack SRIOV and PCI passthrough error while creating 
instance

Dear All,

I am getting an error while creating SRIOV enabled instances following the 
guide from Openstack pike 
https://docs.openstack.org/neutron/pike/admin/config-sriov.html



I want to start an instance on openstack pike with SRIOV enabled NICs. However, 
I am getting a Libvirt error regarding the node name. The error looks weird as 
the node name is not matching the interface name on the host machine or in the 
configuration files.

2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager 
[req-caa92f1d-5ac1-402d-a8bc-b08ab350a21f - - - - -] Error updating resources 
for node jupiter.: libvirtError: Node device not found: no node device with 
matching name 'net_enp129s2_b2_87_6e_13_a1_5e' 2018-01-28 20:40:11.416 2953 
ERROR nova.compute.manager Traceback (most recent call last): 2018-01-28 
20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 6696, in 
update_available_resource_for_node 2018-01-28 20:40:11.416 2953 ERROR 
nova.compute.manager rt.update_available_resource(context, nodename) 2018-01-28 
20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 641, 
in update_available_resource 2018-01-28 20:40:11.416 2953 ERROR 
nova.compute.manager resources = self.driver.get_available_resource(nodename) 
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-pac

Re: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance

[Moshe Levi]

Can you try to restart libvirtd and query again "virsh nodedev-list"

From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk]
Sent: Monday, January 29, 2018 10:32 AM
To: Moshe Levi ; openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Hi Moshe,

Thank you very much for your response. I could see the list of nodes using 
virsh:

net_enp129s0f0_3c_fd_fe_a9_37_c0
net_enp129s0f1_3c_fd_fe_a9_37_c1
net_enp129s2_36_a5_18_f7_41_c6
net_enp129s2f1_96_b0_b3_37_cf_c5
net_enp129s2f2_0e_0c_63_76_07_0f
net_enp129s2f3_36_ca_41_10_7f_62
net_enp129s2f4_f2_79_ee_75_38_a9
net_enp129s2f5_2a_a1_c6_02_55_11
net_enp129s2f6_16_e3_c4_01_8c_6d
net_enp129s2f7_66_56_63_d8_a8_ad

these does not have the node 'net_enp129s2_b2_87_6e_13_a1_5e' listed. Could you 
please help me finding out what could be the reason behind this mismatch.


Kind Regards,
Navdeep Uniyal

From: Moshe Levi [mailto:mosh...@mellanox.com]
Sent: 29 January 2018 06:50
To: Navdeep Uniyal 
mailto:navdeep.uni...@bristol.ac.uk>>; 
openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Hi Navdeep,

The errors you are pointing out shouldn't cause  error while creating instance 
with SR-IOV/PCI passthrough.
They are part of the SR-IOV nic capabilities feature which is not completed yet.

Libvirt "virsh nodedev-list" command will show you the list of nic and this 
method [1] will look it in the hypervisor.
For some reason you have a mismatch here. You need to compare them.  Anyway if 
there is a mismatch it just won't report the capabilities of the nic.
As I mentioned above I think this is not the issue for the error while creating 
instance

[1] 
https://github.com/openstack/nova/blob/91f7a88b3f857d738d39984117e6c514cbec/nova/pci/utils.py#L196-L217


From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk]
Sent: Sunday, January 28, 2018 10:58 PM
To: openstack@lists.openstack.org
Subject: [Openstack] Openstack SRIOV and PCI passthrough error while creating 
instance

Dear All,

I am getting an error while creating SRIOV enabled instances following the 
guide from Openstack pike 
https://docs.openstack.org/neutron/pike/admin/config-sriov.html



I want to start an instance on openstack pike with SRIOV enabled NICs. However, 
I am getting a Libvirt error regarding the node name. The error looks weird as 
the node name is not matching the interface name on the host machine or in the 
configuration files.

2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager 
[req-caa92f1d-5ac1-402d-a8bc-b08ab350a21f - - - - -] Error updating resources 
for node jupiter.: libvirtError: Node device not found: no node device with 
matching name 'net_enp129s2_b2_87_6e_13_a1_5e' 2018-01-28 20:40:11.416 2953 
ERROR nova.compute.manager Traceback (most recent call last): 2018-01-28 
20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 6696, in 
update_available_resource_for_node 2018-01-28 20:40:11.416 2953 ERROR 
nova.compute.manager rt.update_available_resource(context, nodename) 2018-01-28 
20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 641, 
in update_available_resource 2018-01-28 20:40:11.416 2953 ERROR 
nova.compute.manager resources = self.driver.get_available_resource(nodename) 
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5857, in 
get_available_resource 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager 
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5621, in 
_get_pci_passthrough_devices 2018-01-28 20:40:11.416 2953 ERROR 
nova.compute.manager for name in dev_names: 2018-01-28 20:40:11.416 2953 ERROR 
nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5582, in 
_get_pcidev_info 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager 
device['label'] = 'label_%(vendor_id)s_%(product_id)s' % device 2018-

Re: [Openstack] Openstack SRIOV and PCI passthrough error while creating instance

[Navdeep Uniyal]

Hi Moshe,

Thank you very much for your response. I could see the list of nodes using 
virsh:

net_enp129s0f0_3c_fd_fe_a9_37_c0
net_enp129s0f1_3c_fd_fe_a9_37_c1
net_enp129s2_36_a5_18_f7_41_c6
net_enp129s2f1_96_b0_b3_37_cf_c5
net_enp129s2f2_0e_0c_63_76_07_0f
net_enp129s2f3_36_ca_41_10_7f_62
net_enp129s2f4_f2_79_ee_75_38_a9
net_enp129s2f5_2a_a1_c6_02_55_11
net_enp129s2f6_16_e3_c4_01_8c_6d
net_enp129s2f7_66_56_63_d8_a8_ad

these does not have the node 'net_enp129s2_b2_87_6e_13_a1_5e' listed. Could you 
please help me finding out what could be the reason behind this mismatch.


Kind Regards,
Navdeep Uniyal

From: Moshe Levi [mailto:mosh...@mellanox.com]
Sent: 29 January 2018 06:50
To: Navdeep Uniyal ; openstack@lists.openstack.org
Subject: RE: [Openstack] Openstack SRIOV and PCI passthrough error while 
creating instance

Hi Navdeep,

The errors you are pointing out shouldn't cause  error while creating instance 
with SR-IOV/PCI passthrough.
They are part of the SR-IOV nic capabilities feature which is not completed yet.

Libvirt "virsh nodedev-list" command will show you the list of nic and this 
method [1] will look it in the hypervisor.
For some reason you have a mismatch here. You need to compare them.  Anyway if 
there is a mismatch it just won't report the capabilities of the nic.
As I mentioned above I think this is not the issue for the error while creating 
instance

[1] 
https://github.com/openstack/nova/blob/91f7a88b3f857d738d39984117e6c514cbec/nova/pci/utils.py#L196-L217


From: Navdeep Uniyal [mailto:navdeep.uni...@bristol.ac.uk]
Sent: Sunday, January 28, 2018 10:58 PM
To: openstack@lists.openstack.org
Subject: [Openstack] Openstack SRIOV and PCI passthrough error while creating 
instance

Dear All,

I am getting an error while creating SRIOV enabled instances following the 
guide from Openstack pike 
https://docs.openstack.org/neutron/pike/admin/config-sriov.html



I want to start an instance on openstack pike with SRIOV enabled NICs. However, 
I am getting a Libvirt error regarding the node name. The error looks weird as 
the node name is not matching the interface name on the host machine or in the 
configuration files.

2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager 
[req-caa92f1d-5ac1-402d-a8bc-b08ab350a21f - - - - -] Error updating resources 
for node jupiter.: libvirtError: Node device not found: no node device with 
matching name 'net_enp129s2_b2_87_6e_13_a1_5e' 2018-01-28 20:40:11.416 2953 
ERROR nova.compute.manager Traceback (most recent call last): 2018-01-28 
20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 6696, in 
update_available_resource_for_node 2018-01-28 20:40:11.416 2953 ERROR 
nova.compute.manager rt.update_available_resource(context, nodename) 2018-01-28 
20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/compute/resource_tracker.py", line 641, 
in update_available_resource 2018-01-28 20:40:11.416 2953 ERROR 
nova.compute.manager resources = self.driver.get_available_resource(nodename) 
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5857, in 
get_available_resource 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager 
2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5621, in 
_get_pci_passthrough_devices 2018-01-28 20:40:11.416 2953 ERROR 
nova.compute.manager for name in dev_names: 2018-01-28 20:40:11.416 2953 ERROR 
nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5582, in 
_get_pcidev_info 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager 
device['label'] = 'label_%(vendor_id)s_%(product_id)s' % device 2018-01-28 
20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5553, in 
_get_device_capabilities 2018-01-28 20:40:11.416 2953 ERROR 
nova.compute.manager pcinet_info = self._get_pcinet_info(address) 2018-01-28 
20:40:11.416 2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 5496, in 
_get_pcinet_info 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager 
virtdev = self._host.device_lookup_by_name(devname) 2018-01-28 20:40:11.416 
2953 ERROR nova.compute.manager File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/host.py", line 845, in 
device_lookup_by_name 2018-01-28 20:40:11.416 2953 ERROR nova.compute.manager 
return self.get_connect