[openstack-dev] SRIOV failures error-

Hi we are trying to bring-up the SRIOV on set-up. facing the below error when we tried create the vm. *Still during creating instance ERROR appears .PciDeviceRequestFailed: PCI device request ({'requests': [InstancePCIRequest(alias_name=None,count=1,is_new=False,request_id=58584ee1-8a41-4979-99

[openstack-dev] SRIOV failures error-

Hi Itzik, Thank you for your reply Please find the below output for "#echo 'use nova;select hypervisor_hostname,pci_stats from compute_nodes;' | mysql -u root" MariaDB [nova]> select hypervisor_hostname,pci_stats from compute_nodes; +-+

Re: [openstack-dev] SRIOV failures error-

,spec=[{physical_network=' > *physnet1*'}])], > > > > Please check the neutron and nova configuration for physical_network. > > > > Cheers, > > Irena > > > > *From:* Murali B [mailto:mbi...@gmail.com] > *Sent:* Wednesday, December 03, 2014 5:19 AM

[openstack-dev] [NFV][Telco] Service VM v/s its basic framework

Hi keshava, We would like contribute towards service chain and NFV Could you please share the document if you have any related to service VM The service chain can be achieved if we able to redirect the traffic to service VM using ovs-flows in this case we no need to have routing enable on the s

[openstack-dev] SRIOV-error

Hi David, Please add as per the Irena suggestion FYI: refer the below configuration http://pastebin.com/DGmW7ZEg Thanks -Murali ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/opens

Re: [openstack-dev] SRIOV-error

ats.py", line 209, in > apply$ > 2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher > raise exception.PciDeviceRequestFailed(requests=requests) > 2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher > PciDeviceRequestFailed: PCI device request ({'

Re: [openstack-dev] Our idea for SFC using OpenFlow. RE: [NFV][Telco] Service VM v/s its basic framework

development on stackforge: > > > > https://wiki.openstack.org/wiki/ServiceVM > > > > If you are interested in this topic, please take a look at the wiki > page above and see if the project's goals align with yours. If so, you are > certainly welcome to join the IRC mee

[openstack-dev] docker with Juno devstack

Hi I would like to spawn docker image using the devstack. Able to bring-up the devstack with compute_driver = novadocker.virt.docker.DockerDriver. created the .docker image in glance. when I try to create docker image using ""nova boot --flavor 1 --image --nic net-id= dock"" command I am seein

Re: [openstack-dev] docker with Juno devstack

Hi Srinivas, Thank you for your response. I found there is bug on this nova-docker https://bugs.launchpad.net/nova-docker/+bug/1449273 after fixing the code from https://review.openstack.org/#/c/165196/ Able to create the docker image successfully using nova Thanks -Murali

[openstack-dev] Heat-engine fails to start

Hi I installed heat on juno version. When I start heat-engine it fails and I am seeing the below error cal/lib/python2.7/dist-packages/stevedore/extension.py:156 2015-05-07 13:06:36.076 10670 DEBUG stevedore.extension [-] found extension EntryPoint.parse('routing = oslo.messaging.notify._impl_ro

[openstack-dev] docker Instance failed to spawn with larger images

Hi is there any size limit docker images to spawn successfully?. I was able to successfully spawn the image with 2MB size. When I try to spawn instance with 40MB image using nova-docker it says "Instance failed to spawn" later failed to attach vif's etc But the same 40 MB image can launche

[openstack-dev] zun-api error

Hi Hongbin, Thank you for your help As per the our discussion here is the output for my current api on pike. I am not sure which version of zun client client I should use for pike root@cluster3-2:~/python-zunclient# zun service-list ERROR: Not Acceptable (HTTP 406) (Request-ID: req-be69266e-b6

Re: [openstack-dev] [zun] zun-api error

"zun-container" in your setup. I believe the error will be resolved > if you can update the Zun endpoint from type "zun-container" to type > "container". Please give it a try and let us know. > > Best regards, > Hongbin > > On Thu, Apr 5, 2018 at 7:27

Re: [openstack-dev] [zun] zun-api error

c-3e18-4037-8eaf-c6d0076b02a5" released by "zun.compute.manager.do_container_create" :: held 5.163s inner /usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:285 2018-04-09 16:47:48.493 41610 DEBUG eventlet.wsgi.server [-] (41610) accepted ('10.11.142.2',

[openstack-dev] SRIOV-port refused to bind

Hi I am using the SRIOV on mitaka. When I try to launch the VM with SRIOV port its failed. When I see the neutrn-server.log I see that below message on controller. ddf81 - - -] Refusing to bind due to unsupported vnic_type: direct bind_port /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/dr

Re: [openstack-dev] SRIOV-port refused to bind

Hi Lenny Verkhovsky, Thank you for your response. I am using the Mitaka version of openstack. I followed the https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking and set the "intel_iommu=on". Here is the output for the VF's config root@A1-22932-compute1:~# cat /proc/cmdline BOOT_IM

Re: [openstack-dev] SRIOV-port refused to bind

t possible to upload all neutron and nova logs and neutron and nova > config files? > > > > Here[1] you can see local.conf from Mellanox CI as an example > > > > [1] http://13.69.151.247/26/382126/1/check-nova/Nova-ML2- > Sriov/b835c17/local.conf.gz > > > >