Re: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what does it test?

Hi, mriedem Shaohe is on vacation. And Intel SRIOV CI comment to Neutron. running the macvtap vnic SRIOV testing and plus required neutron smoking test. [4] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-SRIOV-CI Regards Yongli He 在 2016年03月30日 23:21, Matt Riedemann 写道

Re: [openstack-dev] [nova][pci] What is the point of the ALLOCATED vs. CLAIMED device status?

patch) Regards Yongli He 在 2016年03月08日 02:23, Jay Pipes 写道: Subject says it all. I've been trying to fix this bug: https://bugs.launchpad.net/nova/+bug/1549984 and just shake my head every time I look at the PCI handling code in nova/pci/manager.py and nova/pci/stats.py. Why do we have

Re: [openstack-dev] pci_alias

Hi, Beliveau, Ludovic currently the alias define as a multiple string option item. this make the code look this configure option is a array, but user define it multiple times instead of a array. pci_alias_opt = cfg.MultiStrOpt Yongli He 在 2015年10月27日 23:44, Beliveau, Ludovic 写道: Hi, I&#

Re: [openstack-dev] [nova] Intel PCI CI appears lost in the weeds

Hi, mriedem and all Sorry for the CI problem. we now back from holiday now, and find the problem and got solution. CI will be back soon. summary: the LOG server connection lost, so the test result failed to uploading. Yongli He 在 2015年10月08日 07:03, Matt Riedemann 写道: Was seeing

[openstack-dev] [Nova][infra][third-party] Intel actively seeking solution to CI issue and getting close to a solution

Hello OpenStackers! The Intel PCI/SRIOV/NGFW/PTAS CI located in China, due to reasons beyond our control, lost connectivity to the Jenkins servers. Although the CI system is working fine we haven’t been able to report results back for about a month now. We are actively looking for a solution

Re: [openstack-dev] Fwd: PCI passthrough of 40G ethernet interface

在 2015年03月11日 22:15, jacob jacob 写道: Hi, jacob we now find przemyslaw.czesnowicz have same NIC, hope will help a little bit. Yongli He -- Forwarded message -- From: *jacob jacob* mailto:opstk...@gmail.com>> Date: Tue, Mar 10, 2015 at 6:00 PM Subject: PCI passthro

Re: [openstack-dev] Fwd: PCI passthrough of 40G ethernet interface

在 2015年03月11日 22:15, jacob jacob 写道: Hi, jacob I'm trying to find someone to check it, if there any feed back, i update you. Yongli He -- Forwarded message -- From: *jacob jacob* mailto:opstk...@gmail.com>> Date: Tue, Mar 10, 2015 at 6:00 PM Subject: PCI passthr

Re: [openstack-dev] [nova][ThirdPartyCI][PCI] Intel Third party Hardware based CI for PCI

I for this purposes. networking CI(commenting to Neutron) - https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-Networking-CI Yongli He Chris On 01/07/2015 08:31 PM, yongli he wrote: Hi, Intel set up a Hardware based Third Part CI. it's already running sets of PCI test ca

Re: [openstack-dev] [nova][ThirdPartyCI][PCI] Intel Third party Hardware based CI for PCI

tions are here: http://git.openstack.org/cgit/openstack-infra/system-config/tree/doc/source/third_party.rst thanks very much, we does considering change to a dns name. Yongli He Kurt Taylor (krtaylor) On Sun, Jan 11, 2015 at 11:18 PM, yongli he <mailto:yongli...@intel.com>> wrote:

[openstack-dev] [nova][qa][pci] Intel PCI CI , testing method/env and test cases

Hi, all Intel PCI CI use hardware machine to testing PCI, there are some change to devstack, tempest use Jerkins dispatch task. basic information: * the topology: log server <---> Jenkins server <> node pool * use devstack deploy testing env. PCI CI 's main problem is how to know

Re: [openstack-dev] [nova][ThirdPartyCI][PCI] Intel Third party Hardware based CI for PCI

在 2015年01月08日 10:31, yongli he 写道: to make a more stable service we upgrade the networking device, then the log server address change to a new IP address: 198.175.100.33 so the sample log change to(replace the 192.55.68.190 to new address): http://198.175.100.33/143614/6/ http

[openstack-dev] [nova][ThirdPartyCI][PCI] Intel Third party Hardware based CI for PCI

90/139900/4 http://192.55.68.190/143372/3/ http://192.55.68.190/141995/6/ http://192.55.68.190/137715/13/ http://192.55.68.190/133269/14/ 3. Test cases on github: https://github.com/intel-hw-ci/Intel-Openstack-Hardware-CI/tree/master/pci_testcases Thank

[openstack-dev] [nova][ThirdPartyCI][PCI CI] comments to Nova

c PCI pass through testing. * after it begin to working, more test cases will be added , include basic SRIOV Thanks Yongli He More logs: http://192.55.68.190/138795/6 http://192.55.68.190/74423/6 http://192.55.68.190/141115/6 http://192.55.68.190/142565/2 http://192.55.68.190/142835/3

[openstack-dev] [nova][pci] A couple of questions

-sriov,n,z Yongli He ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][pci] A couple of questions

this name is libvirt returned device name, use to oprate the device via libvirt later. device_id might a good name for this. Yongli He For the second one, thanks for point the issue out. Yes, I'm working on fixing it. --jyh *From:*Robert Li (baoli) [mailto:ba...@cisco.com] *Sent:*

Re: [openstack-dev] about pci device filter

于 2014年05月05日 16:28, Bohai (ricky) 写道: Hi, stackers: Now there is an default while list filter for PCI device. But maybe it's not enough in some scenario. Maybe it's better if we provide a mechanism to specify a customize filter. For example: So user can make a special filter , then specify wh

Re: [openstack-dev] [nova][pci]PCI SR-IOV use cases initial doc

have different picture in my head , i.e how do you think this: tenant user want to pick up a PCI acceleration card with MD5 and RC6 encryption/hash support. 1. is this the use case you are look for? 2. what other information should be add to this use-case? and any other suggestion? Yongli he &

Re: [openstack-dev] [nova][pci]PCI SR-IOV use cases initial doc

case flow without bothering a reference design . > > John > > > On 10 April 2014 09:14, yongli he wrote: >> 于 2014年04月10日 15:59, Irena Berezovsky 写道: >> >> Hi Robert, >> >> Thanks a lot the inputs you posted in the doc. >> >> I have rai

Re: [openstack-dev] [nova][pci]PCI SR-IOV use cases initial doc

Intel/Cisco/Mellanox card, does not mean we should disable it, or don't give a chance. 3. i raise couple of question and questioning the aggregate solution. see inline comments. https://docs.google.com/document/d/1zgMaXqrCnad01-jQH7Mkmf6amlghw9RMScGLBrKslmw/edit Yongli He Thanks, Ir

Re: [openstack-dev] [nova][PCI] one use case make the flavor/extra-info based solution to be right choice

ES,3DES, AES, RSA, SHA-x, IDEA, RC4,5,6 the way to select such a device is use it's feature set instead of one or 2 of group, so the extra information about a pci card is need, in a flexible way. Yongli He Best, -jay ___ OpenStack-

Re: [openstack-dev] [nova][PCI] problem about PCI SRIOV

le there already has the m1.tiny flavor, will the "pci_flavor" be separated from the normal flavor in the next step? yes. but not mean the pci_flavor is separated from normal flavor, the flavor is the original alias with api support. we rename to pci_flavor because it's just for

Re: [openstack-dev] [nova][PCI] flavor/extra-info based solution： why need vendor/product id

easy to manage. Therefore, I believe it requires further work. I think that practical use cases would really help us find the right solution, and provide the optimal interface to the admin/user. So let's keep the discussion going. thanks, Robert On 3/20/14 4:22 AM, "yongli he" wrote

Re: [openstack-dev] [nova][PCI] one use case make the flavor/extra-info based solution to be right choice

ally lacks the level of abstraction that clearly defines the usage and semantics. It's up to a well educated admin to use it properly, and it's not easy to manage. Therefore, I believe it requires further work. I think that practical use cases would really help us find the right solution, an

[openstack-dev] [nova][PCI] one use case make the flavor/extra-info based solution to be right choice

he pci device, then user can not request a simple thing like the "intel-NIC" or "1G_NIC. Regards Yongli He ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [nova][pci][sriov] rewriting the the common SRIOV support blue-prints :https://blueprints.launchpad.net/nova/+spec/pci-extra-info

this blue prints, i really want you guy check this bp to make sure it's the right things we had agreed( i think so) before and after new bp is done. i will update you when i finished it. meeting link: https://wiki.openstack.org/wiki/Meetings/Passthrough Regards Yong

Re: [openstack-dev] PCI SRIOV meeting suspend?

On 2014年03月04日 20:45, Robert Li (baoli) wrote: > Hi Yongli, > > I have been looking at your patch set. Let me look at it again if you have > new update. look forward to that. thanks. > > The meeting changed back to UTC 1300 Tuesday. > > thanks, > Robert > > On 3/

Re: [openstack-dev] PCI SRIOV meeting suspend?

On 2014年03月04日 13:33, Irena Berezovsky wrote: Hi Yongli He, The PCI SRIOV meeting switched back to weekly occurrences,. Next meeting will be today at usual time slot: https://wiki.openstack.org/wiki/Meetings#PCI_Passthrough_Meeting In coming meetings we would like to work on content to be

[openstack-dev] PCI SRIOV meeting suspend?

HI, Robert does it stop for while? and if you are convenient please review this patch set , check if the interface is ok. https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/pci-extra-info,n,z Yongli He

Re: [openstack-dev] [nova] A problem about pci-passthrough

"consume_from_instance" will raise a exception. Hi Jeremy, You didn't mention the PciPassthroughFilter, have you enabled this in definitely need this filter. Yongli He your scheduler? https://wiki.openstack.org/wiki/Pci_passthrough Alexis ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] pci device hotplug

. The reason of no support yet is bandwidth. The folks working on PCI spend a lot of time on SR-IOV NIC discussion. --jyh sorry for later notice this, sure i also think it should have hotplug . --Yongli He ___ OpenStack-dev mailing list OpenStack-dev

[openstack-dev] does exception need localize or not?

essages is not actively encouraged. Exception text should/not/be marked for translation, becuase if an exception occurs there is no guarantee that the translation machinery will be functional. Regards Yongli He ___ OpenStack-dev mailing list Ope

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

On 2014?01?16? 08:28, Ian Wells wrote: To clarify a couple of Robert's points, since we had a conversation earlier: On 15 January 2014 23:47, Robert Li (baoli) > wrote: --- do we agree that BDF address (or device id, whatever you call it), and node id shouldn't

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

On 2014?01?10? 00:49, Robert Li (baoli) wrote: Hi Folks, HI, all basiclly i flavor the pic-flavor style and against massing the white-list. please see my inline comments. With John joining the IRC, so far, we had a couple of productive meetings in an effort to come to consensus and m

Re: [openstack-dev] [nova] [neutron] Todays' meeting log: PCI pass-through network support

On 2013?12?24? 07:35, Ian Wells wrote: On autodiscovery and configuration, we agree that each compute node finds out what it has based on some sort of list of match expressions; we just disagree on where they should live. i think what we talk is group/class auto discovery here. I know we've t

Re: [openstack-dev] [Nova] [Infra] Support for PCI Passthrough

On 2013年11月27日 23:43, Jeremy Stanley wrote: On 2013-11-27 11:18:46 +0800 (+0800), yongli he wrote: [...] if you post -1, you should post testing log somewhere for people to debug it, so does third party testing can post testing log to the infra log server? Not at the moment--the "infr

Re: [openstack-dev] [Nova] [Infra] Support for PCI Passthrough

On 2013年11月23日 03:43, Jeremy Stanley wrote: Hi, Jeremy for currently, we need setup it up asap, so the third party seems the right way. but i have some concern, if you post -1, you should post testing log somewhere for people to debug it, so does third party testing can post testing log to t

[openstack-dev] [Nova] PCI next step blue print

/PCI_passthrough_SRIOV_support <https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support> user case discuss: https://docs.google.com/document/d/1EMwDg9J8zOxzvTnQJ9HwZdiotaVstFWKIuKrPse6JOs/edit#heading=h.30de7p6sgoxp Yongli He (Pauli He) @int

Re: [openstack-dev] [Nova] [Infra] Support for PCI Passthrough

lution for such testing. Yongli He(Pauli He) TripleO cloud is aiming at) and infra running the tests; for checking without infra running it the third-party system is a good mechanism (and that can be run from a single TripleO region too, in p

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

vice extra info?) 4) scheduler enhancement to meet NIC requements Yongli He@intel We want to integrate our solution with PCI pass-through Nova support. I will be glad to share more details if you are interested. The PCI pass-through networking support is planned to be discussed during the su

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

On 2013?10?29? 03:22, Robert Li (baoli) wrote: Hi Irena, Thank you very much for your comments. See inline. --Robert On 10/27/13 3:48 AM, "Irena Berezovsky" > wrote: Hi Robert, Thank you very much for sharing the information regarding your efforts. Ca

Re: [openstack-dev] [nova] [Pci passthrough] bug? -- 'NoneType' object has no attribute 'support_requests'

于 2013年09月17日 05:07, David Kang 写道: Hi, David this should be fixed. Hi, I'm testing PCI passthrough features on Havana (single node installation). I've installed OpenStack on CentOS 6.4 using EPEL. The pci_passthrough_filter doesn't seem to be able to get the object 'host_state.pci_stats'.

Re: [openstack-dev] [nova] [pci passthrough] Is "extra_info" broken?

于 2013年09月21日 05:05, David Kang 写道: - Original Message - From: "Russell Bryant" To: openstack-dev@lists.openstack.org Sent: Friday, September 20, 2013 1:28:13 PM Subject: Re: [openstack-dev] [nova] [pci passthrough] Is "extra_info" broken? https://bugs.launchpad.net/nova/+bug/1223559 T

Re: [openstack-dev] [nova] [pci device passthrough] fails with "NameError: global name '_' is not defined"

于 2013年09月11日 21:27, Henry Gessau 写道: For the "TypeError: expected string or buffer" I have filed Bug #1223874. On Wed, Sep 11, at 7:41 am, yongli he wrote: 于 2013年09月11日 05:38, David Kang 写道: - Original Message - From: "Russell Bryant" To: "Da

Re: [openstack-dev] [nova] [pci device passthrough] fails with "NameError: global name '_' is not defined"

于 2013年09月11日 21:27, Henry Gessau 写道: For the "TypeError: expected string or buffer" I have filed Bug #1223874. got， thanks。 On Wed, Sep 11, at 7:41 am, yongli he wrote: 于 2013年09月11日 05:38, David Kang 写道: - Original Message - From: "Russell Bryant"

Re: [openstack-dev] [nova] [pci device passthrough] fails with "NameError: global name '_' is not defined"

13:56:35.366 16736 TRACE nova.openstack.common.threadgroup 2013-09-10 13:56:35.366 16736 TRACE nova.openstack.common.threadgroup File "/usr/lib64/python2.6/json/decoder.py", line 319, in decode 2013-09-10 13:56:35.366 16736 TRACE nova.openstack.common.threadgroup obj, end = self.raw_de

Re: [openstack-dev] [nova] [pci device passthrough] fails with "NameError: global name '_' is not defined"

于 2013年09月11日 05:17, Russell Bryant 写道: On 09/10/2013 05:03 PM, David Kang wrote: - Original Message - From: "Russell Bryant" To: "OpenStack Development Mailing List" Cc: "David Kang" Sent: Tuesday, September 10, 2013 4:42:41 PM Subject: Re: [openstack-dev] [nova] [pci device passthr