Re: [openstack-dev] [zun] zun-api error
Hi Hongbin Lu,
After I run the etcd service up and tried to create container I see the
below error and my container is in error state
Could you please share me if I need to change any configuration in neutron
for docker kuryer
ckercfg'] find_config_file
/usr/local/lib/python2.7/dist-packages/docker/utils/config.py:21
2018-04-09 16:47:44.058 41736 DEBUG docker.utils.config
[req-0afc6b91-e50e-4a5a-a673-c2cecd6f2986 - - - - -] No config file found
find_config_file
/usr/local/lib/python2.7/dist-packages/docker/utils/config.py:28
2018-04-09 16:47:44.345 41736 ERROR zun.compute.manager
[req-0afc6b91-e50e-4a5a-a673-c2cecd6f2986 - - - - -] Error occurred while
calling Docker start API: Docker internal error: 500 Server Error: Internal
Server Error ("IpamDriver.RequestAddress: Requested ip address
{'subnet_id': u'fb768eca-8ad9-4afc-99f7-e13b9c36096e', 'ip_address':
u'3.3.3.12'} already belongs to a bound Neutron port:
401a5599-2309-482e-b100-e2317c4118cf").: DockerError: Docker internal
error: 500 Server Error: Internal Server Error ("IpamDriver.RequestAddress:
Requested ip address {'subnet_id': u'fb768eca-8ad9-4afc-99f7-e13b9c36096e',
'ip_address': u'3.3.3.12'} already belongs to a bound Neutron port:
401a5599-2309-482e-b100-e2317c4118cf").
2018-04-09 16:47:44.372 41736 DEBUG oslo_concurrency.lockutils
[req-0afc6b91-e50e-4a5a-a673-c2cecd6f2986 - - - - -] Lock
"b861d7cc-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', 60664) server /usr/lib/python2.7/dis
Thanks
-Murali
On Fri, Apr 6, 2018 at 11:00 AM, Murali B <mbi...@gmail.com> wrote:
> Hi Hongbin Lu,
>
> Thank you. After changing the endpoint it worked. Actually I was using
> magnum service also. I used the service as "container" for magnum that is
> why its is going to 9511 instead of 9517
> After I corrected it worked.
>
> Thanks
> -Murali
>
> On Fri, Apr 6, 2018 at 8:45 AM, Hongbin Lu <hongbin...@gmail.com> wrote:
>
>> Hi Murali,
>>
>> It looks your zunclient was sending API requests to
>> http://10.11.142.2:9511/v1/services , which doesn't seem to be the right
>> API endpoint. According to the Keystone endpoint you configured, the API
>> endpoint of Zun should be http://10.11.142.2:9517/v1/services
>> <http://10.11.142.2:9511/v1/services> (it is on port 9517 instead of
>> 9511).
>>
>> What confused the zunclient is the endpoint's type you configured in
>> Keystone. Zun expects an endpoint of type "container" but it was configured
>> to be "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 PM, Murali B <mbi...@gmail.com> wrote:
>>
>>> 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-b641-44b9-9739-0c2d050f18b3)
>>> root@cluster3-2:~/python-zunclient# zun --debug service-list
>>> DEBUG (extension:180) found extension EntryPoint.parse('vitrage-keycloak
>>> = vitrageclient.auth:VitrageKeycloakLoader')
>>> DEBUG (extension:180) found extension EntryPoint.parse('vitrage-noauth
>>> = vitrageclient.auth:VitrageNoAuthLoader')
>>> DEBUG (extension:180) found extension EntryPoint.parse('noauth =
>>> cinderclient.contrib.noauth:CinderNoAuthLoader')
>>> DEBUG (extension:180) found extension EntryPoint.parse('v2token =
>>> keystoneauth1.loading._plugins.identity.v2:Token')
>>> DEBUG (extension:180) found extension EntryPoint.parse('none =
>>> keystoneauth1.loading._plugins.noauth:NoAuth')
>>> DEBUG (extension:180) found extension EntryPoint.parse('v3oauth1 =
>>> keystoneauth1.extras.oauth1._loading:V3OAuth1')
>>> DEBUG (extension:180) found extension EntryPoint.parse('admin_token =
>>> keystoneauth1.loading._plugins.admin_token:AdminToken')
>>> DEBUG (extension:180) found extension EntryPoint.parse('v3oidcauthcode
>>> = keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAuth
>>> orizationCode')
>>> DEBUG (extension:180) found extensi
Re: [openstack-dev] [zun] zun-api error
Hi Hongbin Lu,
Thank you. After changing the endpoint it worked. Actually I was using
magnum service also. I used the service as "container" for magnum that is
why its is going to 9511 instead of 9517
After I corrected it worked.
Thanks
-Murali
On Fri, Apr 6, 2018 at 8:45 AM, Hongbin Lu <hongbin...@gmail.com> wrote:
> Hi Murali,
>
> It looks your zunclient was sending API requests to
> http://10.11.142.2:9511/v1/services , which doesn't seem to be the right
> API endpoint. According to the Keystone endpoint you configured, the API
> endpoint of Zun should be http://10.11.142.2:9517/v1/services
> <http://10.11.142.2:9511/v1/services> (it is on port 9517 instead of
> 9511).
>
> What confused the zunclient is the endpoint's type you configured in
> Keystone. Zun expects an endpoint of type "container" but it was configured
> to be "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 PM, Murali B <mbi...@gmail.com> wrote:
>
>> 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-b641-44b9-9739-0c2d050f18b3)
>> root@cluster3-2:~/python-zunclient# zun --debug service-list
>> DEBUG (extension:180) found extension EntryPoint.parse('vitrage-keycloak
>> = vitrageclient.auth:VitrageKeycloakLoader')
>> DEBUG (extension:180) found extension EntryPoint.parse('vitrage-noauth =
>> vitrageclient.auth:VitrageNoAuthLoader')
>> DEBUG (extension:180) found extension EntryPoint.parse('noauth =
>> cinderclient.contrib.noauth:CinderNoAuthLoader')
>> DEBUG (extension:180) found extension EntryPoint.parse('v2token =
>> keystoneauth1.loading._plugins.identity.v2:Token')
>> DEBUG (extension:180) found extension EntryPoint.parse('none =
>> keystoneauth1.loading._plugins.noauth:NoAuth')
>> DEBUG (extension:180) found extension EntryPoint.parse('v3oauth1 =
>> keystoneauth1.extras.oauth1._loading:V3OAuth1')
>> DEBUG (extension:180) found extension EntryPoint.parse('admin_token =
>> keystoneauth1.loading._plugins.admin_token:AdminToken')
>> DEBUG (extension:180) found extension EntryPoint.parse('v3oidcauthcode =
>> keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAuth
>> orizationCode')
>> DEBUG (extension:180) found extension EntryPoint.parse('v2password =
>> keystoneauth1.loading._plugins.identity.v2:Password')
>> DEBUG (extension:180) found extension EntryPoint.parse('v3samlpassword =
>> keystoneauth1.extras._saml2._loading:Saml2Password')
>> DEBUG (extension:180) found extension EntryPoint.parse('v3password =
>> keystoneauth1.loading._plugins.identity.v3:Password')
>> DEBUG (extension:180) found extension EntryPoint.parse('v3adfspassword =
>> keystoneauth1.extras._saml2._loading:ADFSPassword')
>> DEBUG (extension:180) found extension EntryPoint.parse('v3oidcaccesstoken
>> = keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAccessToken')
>> DEBUG (extension:180) found extension EntryPoint.parse('v3oidcpassword =
>> keystoneauth1.loading._plugins.identity.v3:OpenIDConnectPassword')
>> DEBUG (extension:180) found extension EntryPoint.parse('v3kerberos =
>> keystoneauth1.extras.kerberos._loading:Kerberos')
>> DEBUG (extension:180) found extension EntryPoint.parse('token =
>> keystoneauth1.loading._plugins.identity.generic:Token')
>> DEBUG (extension:180) found extension
>> EntryPoint.parse('v3oidcclientcredentials
>> = keystoneauth1.loading._plugins.identity.v3:OpenIDConnectClie
>> ntCredentials')
>> DEBUG (extension:180) found extension EntryPoint.parse('v3tokenlessauth
>> = keystoneauth1.loading._plugins.identity.v3:TokenlessAuth')
>> DEBUG (extension:180) found extension EntryPoint.parse('v3token =
>> keystoneauth1.loading._plugins.identity.v3:Token')
>> DEBUG (extension:180) found extension EntryPoint.parse('v3totp =
>> keystoneauth1.loading._plugins.identity.v3:TOTP')
>> DEBUG (extension:180) found extension
>> EntryPoint.parse('v3applicationcredential
>> = keystoneauth1.loading._plugins.identity.v3:ApplicationCredential')
>> DEBUG (extension:180) found extension EntryPoint.parse('password =
>> keystoneauth1.loading._plugins.identity.generic:Password')
>> DEBUG (extension:1
[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-b641-44b9-9739-0c2d050f18b3)
root@cluster3-2:~/python-zunclient# zun --debug service-list
DEBUG (extension:180) found extension EntryPoint.parse('vitrage-keycloak =
vitrageclient.auth:VitrageKeycloakLoader')
DEBUG (extension:180) found extension EntryPoint.parse('vitrage-noauth =
vitrageclient.auth:VitrageNoAuthLoader')
DEBUG (extension:180) found extension EntryPoint.parse('noauth =
cinderclient.contrib.noauth:CinderNoAuthLoader')
DEBUG (extension:180) found extension EntryPoint.parse('v2token =
keystoneauth1.loading._plugins.identity.v2:Token')
DEBUG (extension:180) found extension EntryPoint.parse('none =
keystoneauth1.loading._plugins.noauth:NoAuth')
DEBUG (extension:180) found extension EntryPoint.parse('v3oauth1 =
keystoneauth1.extras.oauth1._loading:V3OAuth1')
DEBUG (extension:180) found extension EntryPoint.parse('admin_token =
keystoneauth1.loading._plugins.admin_token:AdminToken')
DEBUG (extension:180) found extension EntryPoint.parse('v3oidcauthcode =
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAuthorizationCode')
DEBUG (extension:180) found extension EntryPoint.parse('v2password =
keystoneauth1.loading._plugins.identity.v2:Password')
DEBUG (extension:180) found extension EntryPoint.parse('v3samlpassword =
keystoneauth1.extras._saml2._loading:Saml2Password')
DEBUG (extension:180) found extension EntryPoint.parse('v3password =
keystoneauth1.loading._plugins.identity.v3:Password')
DEBUG (extension:180) found extension EntryPoint.parse('v3adfspassword =
keystoneauth1.extras._saml2._loading:ADFSPassword')
DEBUG (extension:180) found extension EntryPoint.parse('v3oidcaccesstoken =
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAccessToken')
DEBUG (extension:180) found extension EntryPoint.parse('v3oidcpassword =
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectPassword')
DEBUG (extension:180) found extension EntryPoint.parse('v3kerberos =
keystoneauth1.extras.kerberos._loading:Kerberos')
DEBUG (extension:180) found extension EntryPoint.parse('token =
keystoneauth1.loading._plugins.identity.generic:Token')
DEBUG (extension:180) found extension
EntryPoint.parse('v3oidcclientcredentials =
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectClientCredentials')
DEBUG (extension:180) found extension EntryPoint.parse('v3tokenlessauth =
keystoneauth1.loading._plugins.identity.v3:TokenlessAuth')
DEBUG (extension:180) found extension EntryPoint.parse('v3token =
keystoneauth1.loading._plugins.identity.v3:Token')
DEBUG (extension:180) found extension EntryPoint.parse('v3totp =
keystoneauth1.loading._plugins.identity.v3:TOTP')
DEBUG (extension:180) found extension
EntryPoint.parse('v3applicationcredential =
keystoneauth1.loading._plugins.identity.v3:ApplicationCredential')
DEBUG (extension:180) found extension EntryPoint.parse('password =
keystoneauth1.loading._plugins.identity.generic:Password')
DEBUG (extension:180) found extension EntryPoint.parse('v3fedkerb =
keystoneauth1.extras.kerberos._loading:MappedKerberos')
DEBUG (extension:180) found extension EntryPoint.parse('v1password =
swiftclient.authv1:PasswordLoader')
DEBUG (extension:180) found extension EntryPoint.parse('token_endpoint =
openstackclient.api.auth_plugin:TokenEndpoint')
DEBUG (extension:180) found extension EntryPoint.parse('gnocchi-basic =
gnocchiclient.auth:GnocchiBasicLoader')
DEBUG (extension:180) found extension EntryPoint.parse('gnocchi-noauth =
gnocchiclient.auth:GnocchiNoAuthLoader')
DEBUG (extension:180) found extension EntryPoint.parse('aodh-noauth =
aodhclient.noauth:AodhNoAuthLoader')
DEBUG (session:372) REQ: curl -g -i -X GET http://ubuntu16:35357/v3 -H
"Accept: application/json" -H "User-Agent: zun keystoneauth1/3.4.0
python-requests/2.18.1 CPython/2.7.12"
DEBUG (connectionpool:207) Starting new HTTP connection (1): ubuntu16
DEBUG (connectionpool:395) http://ubuntu16:35357 "GET /v3 HTTP/1.1" 200 248
DEBUG (session:419) RESP: [200] Date: Thu, 05 Apr 2018 23:11:07 GMT Server:
Apache/2.4.18 (Ubuntu) Vary: X-Auth-Token X-Distribution: Ubuntu
x-openstack-request-id: req-3b1a12cc-fb3f-4d05-87fc-d2a1ff43395c
Content-Length: 248 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive
Content-Type: application/json
RESP BODY: {"version": {"status": "stable", "updated":
"2017-02-22T00:00:00Z", "media-types": [{"base": "application/json",
"type": "application/vnd.openstack.identity-v3+json"}], "id": "v3.8",
"links": [{"href": "http://ubuntu16:35357/v3/;, "rel": "self"}]}}
DEBUG (session:722) GET call to None for http://ubuntu16:35357/v3 used
request id req-3b1a12cc-fb3f-4d05-87fc-d2a1ff43395c
DEBUG (base:175) Making authentication request to
http://ubuntu16:35357/v3/auth/tokens
DEBUG (connectionpool:395)
Re: [openstack-dev] SRIOV-port refused to bind
Hi Lenny, Thank you for your response. I am able to resolve the issue. My sriov-agent is not able to read the vf's There is some config misssmatch in agent config. Thanks -Murali On Tue, Oct 4, 2016 at 10:42 PM, Lenny Verkhovsky <len...@mellanox.com> wrote: > Hi Murali, > > > > Try adding filters to nova.conf > > scheduler_available_filters=nova.scheduler.filters.all_filters > > scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, > RamFilter, ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, > PciPassthroughFilter > > > > is it 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 > > > > *From:* Murali B [mailto:mbi...@gmail.com] > *Sent:* Thursday, September 29, 2016 10:46 PM > *To:* Lenny Verkhovsky <len...@mellanox.com>; OpenStack Development > Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> > *Subject:* 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_IMAGE=/vmlinuz-4.2.0-42-generic > root=UUID=ff1b5507-414f-4c96-9fbe-cc3c02c682fc > ro intel_iommu=on igbe.max_vfs=2 pci=assign-busses quiet splash vt.handoff=7 > > > > root@A1-22932-compute1:~# lspci | grep Ether > > 03:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network > Connection (rev 01) > > 03:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network > Connection (rev 01) > > 04:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev > 01) > > 04:10.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev > 01) > > 04:10.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev > 01) > > 04:10.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev > 01) > > 08:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network > Connection > > 09:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network > Connection > > > > root@A1-22932-compute1:~# ls /sys/bus/pci/devices/\:04\:10.0/net/ > > eth1 > > > > > > Please find the config here http://pastebin.com/Tfaez4Je > > > > here are the logs on controller http://pastebin.com/e3s1LaMw > > > > here is the nova-compute log http://pastebin.com/qRzG6Tif > > > > Thanks > > -Murali > > > > > > > > > > > __ 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] 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_IMAGE=/vmlinuz-4.2.0-42-generic root=UUID=ff1b5507-414f-4c96-9fbe-cc3c02c682fc ro intel_iommu=on igbe.max_vfs=2 pci=assign-busses quiet splash vt.handoff=7 root@A1-22932-compute1:~# lspci | grep Ether 03:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 03:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 04:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 04:10.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 04:10.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 04:10.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01) 08:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 09:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection root@A1-22932-compute1:~# ls /sys/bus/pci/devices/\:04\:10.0/net/ eth1 Please find the config here http://pastebin.com/Tfaez4Je here are the logs on controller http://pastebin.com/e3s1LaMw here is the nova-compute log http://pastebin.com/qRzG6Tif Thanks -Murali __ 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
[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/drivers/mech_agent.py:65
2016-09-28 18:55:18.384 16531 ERROR neutron.plugins.ml2.managers
[req-443e9b6a-45c6-4b30-aa50-52a9b0a4926c 7d0ef58dd1214f54983c9d843fec0bde
238c9900a2ae4b57b01fa72abdeddf81 - - -] Failed to bind port
e96eadf3-5501-442a-8bcc-0b4d64617b26 on host A1-22932-compute1 for
vnic_type direct using segments [{'segmentation_id': 123,
'physical_network': u'physnet1', 'id':
u'30b77081-d02c-4e29-a41a-f8997c1f9f66', 'network_type': u'vlan'}]
On compute node I see the below error.
2016-09-28 18:55:18.688 7651 ERROR nova.compute.manager [instance:
4c737a89-51b8-4504-a208-05f2da178482] flavor, virt_type, self._host)
2016-09-28 18:55:18.688 7651 ERROR nova.compute.manager [instance:
4c737a89-51b8-4504-a208-05f2da178482] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 447, in
get_config
2016-09-28 18:55:18.688 7651 ERROR nova.compute.manager [instance:
4c737a89-51b8-4504-a208-05f2da178482] _("Unexpected vif_type=%s") %
vif_type)
2016-09-28 18:55:18.688 7651 ERROR nova.compute.manager [instance:
4c737a89-51b8-4504-a208-05f2da178482] NovaException: Unexpected
vif_type=binding_failed
Could somebody help me to come-out this issue.
Thanks
-Murali
__
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
[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 launched successfully using the docker command docker run --name selfCP1 -t -i name /usr/local/bin/bash So I really doubt something wrong with nova-docker driver I raised bug for the same https://bugs.launchpad.net/nova-docker/+bug/1454982. Please share the info if anybody facing the same issue. Thanks -Murali __ 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
[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_routing:RoutingDriver') _load_plugins
/usr/local/lib/python2.7/dist-packages/stevedore/extension.py:156
2015-05-07 13:06:36.077 10670 DEBUG stevedore.extension [-] found extension
EntryPoint.parse('test = oslo.messaging.notify._impl_test:TestDriver')
_load_plugins
/usr/local/lib/python2.7/dist-packages/stevedore/extension.py:156
2015-05-07 13:06:36.077 10670 DEBUG stevedore.extension [-] found extension
EntryPoint.parse('messaging =
oslo.messaging.notify._impl_messaging:MessagingDriver') _load_plugins
/usr/local/lib/python2.7/dist-packages/stevedore/extension.py:156
2015-05-07 13:06:36.077 10670 DEBUG stevedore.extension [-] found extension
EntryPoint.parse('AWSTemplateFormatVersion.2010-09-09 =
heat.engine.cfn.template:CfnTemplate') _load_plugins
/usr/local/lib/python2.7/dist-packages/stevedore/extension.py:156
2015-05-07 13:06:36.084 10670 CRITICAL heat.engine [-] Could not load
AWSTemplateFormatVersion.2010-09-09: (sqlalchemy-migrate 0.9.6
(/usr/local/lib/python2.7/dist-packages),
Requirement.parse('sqlalchemy-migrate==0.9.1'))
your help is appreciated
Thanks
-Murali
__
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] 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 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
[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 image-id --nic net-id=net-id dock command I am seeing the below ^[[01;31m2015-04-27 18:17:12.213 TRACE nova.compute.manager ^[[01;35m[instance: a4752d27-041c-4b5f-b025-cd803343f013] ^[[00mTraceback (most recent call last): ^[[01;31m2015-04-27 18:17:12.213 TRACE nova.compute.manager ^[[01;35m[instance: a4752d27-041c-4b5f-b025-cd803343f013] ^[[00m File /opt/stack/nova/nova/compute/manager.py, line 2303, in _build_resources ^[[01;31m2015-04-27 18:17:12.213 TRACE nova.compute.manager ^[[01;35m[instance: a4752d27-041c-4b5f-b025-cd803343f013] ^[[00myield resources ^[[01;31m2015-04-27 18:17:12.213 TRACE nova.compute.manager ^[[01;35m[instance: a4752d27-041c-4b5f-b025-cd803343f013] ^[[00m File /opt/stack/nova/nova/compute/manager.py, line 2173, in _build_and_run_instance ^[[01;31m2015-04-27 18:17:12.213 TRACE nova.compute.manager ^[[01;35m[instance: a4752d27-041c-4b5f-b025-cd803343f013] ^[[00m flavor=flavor) ^[[01;31m2015-04-27 18:17:12.213 TRACE nova.compute.manager ^[[01;35m[instance: a4752d27-041c-4b5f-b025-cd803343f013] ^[[00m File /usr/local/lib/python2.7/dist-packages/novadocker/virt/docker/driver.py, line 423, in spawn ^[[01;31m2015-04-27 18:17:12.213 TRACE nova.compute.manager ^[[01;35m[instance: a4752d27-041c-4b5f-b025-cd803343f013] ^[[00m 'mem_limit': self._get_memory_limit_bytes(instance), ^[[01;31m2015-04-27 18:17:12.213 TRACE nova.compute.manager ^[[01;35m[instance: a4752d27-041c-4b5f-b025-cd803343f013] ^[[00m File /usr/local/lib/python2.7/dist-packages/novadocker/virt/docker/driver.py, line 336, in _get_memory_limit_bytes ^[[01;31m2015-04-27 18:17:12.213 TRACE nova.compute.manager ^[[01;35m[instance: a4752d27-041c-4b5f-b025-cd803343f013] ^[[00mreturn instance.flavor.memory_mb * units.Mi ^[[01;31m2015-04-27 18:17:12.213 TRACE nova.compute.manager ^[[01;35m[instance: a4752d27-041c-4b5f-b025-cd803343f013] ^[[00mAttributeError: 'Instance' object has no attribute 'flavor' ^[[01;31m2015-04-27 18:17:12.213 TRACE nova.compute.manager ^[[01;35m[instance: a4752d27-041c-4b5f-b025-cd803343f013] ^[[00m 2015-04-27 18:17:12.214 ^[[01;36mAUDIT nova.compute.manager [^[[01;36mreq-d5179c71-527b-45c7-b7ec-3c67a171627c ^[[00;36madmin demo^[[01;36m] ^[[01;35m[instance: a4752d27-041c-4b5f-b025-cd803343f013] ^[[01;36mTerminating instance^[[00m your help is appreciated to overcome this error Thanks -Murali __ 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] Our idea for SFC using OpenFlow. RE: [NFV][Telco] Service VM v/s its basic framework
Thank you Vikram, Could you or somebody please provide the access the full specification document Thanks -Murali On Mon, Dec 22, 2014 at 11:48 AM, Vikram Choudhary vikram.choudh...@huawei.com wrote: Hi Murali, We have proposed service function chaining idea using open flow. https://blueprints.launchpad.net/neutron/+spec/service-function-chaining-using-openflow Will submit the same for review soon. Thanks Vikram *From:* yuriy.babe...@telekom.de [mailto:yuriy.babe...@telekom.de] *Sent:* 18 December 2014 19:35 *To:* openstack-dev@lists.openstack.org; stephen.kf.w...@gmail.com *Subject:* Re: [openstack-dev] [NFV][Telco] Service VM v/s its basic framework Hi, in the IRC meeting yesterday we agreed to work on the use-case for service function chaining as it seems to be important for a lot of participants [1]. We will prepare the first draft and share it in the TelcoWG Wiki for discussion. There is one blueprint in openstack on that in [2] [1] http://eavesdrop.openstack.org/meetings/telcowg/2014/telcowg.2014-12-17-14.01.txt [2] https://blueprints.launchpad.net/group-based-policy/+spec/group-based-policy-service-chaining Kind regards/Mit freundlichen Grüßen Yuriy Babenko *Von:* A, Keshava [mailto:keshav...@hp.com keshav...@hp.com] *Gesendet:* Mittwoch, 10. Dezember 2014 19:06 *An:* stephen.kf.w...@gmail.com; OpenStack Development Mailing List (not for usage questions) *Betreff:* Re: [openstack-dev] [NFV][Telco] Service VM v/s its basic framework Hi Murali, There are many unknows w.r.t ‘Service-VM’ and how it should from NFV perspective. In my opinion it was not decided how the Service-VM framework should be. Depending on this we at OpenStack also will have impact for ‘Service Chaining’. *Please find the mail attached w.r.t that discussion with NFV for ‘Service-VM + Openstack OVS related discussion”.* Regards, keshava *From:* Stephen Wong [mailto:stephen.kf.w...@gmail.com stephen.kf.w...@gmail.com] *Sent:* Wednesday, December 10, 2014 10:03 PM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [NFV][Telco] Service VM v/s its basic framework Hi Murali, There is already a ServiceVM project (Tacker), currently under 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 meeting and start to contribute to the project's direction and design. Thanks, - Stephen On Wed, Dec 10, 2014 at 7:01 AM, Murali B mbi...@gmail.com wrote: 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 service VM(traffic is redirected at L2). All the tenant VM's in cloud could use this service VM services by adding the ovs-rules in OVS Thanks -Murali ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[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/openstack-dev
Re: [openstack-dev] SRIOV-error
Hi David,
From the neutron agent-list I can see that you are not running the
sriov-agent.
Please run the sriov-agent after adding the below configuration.
Add the below configuration at controller in
/etc/neutron/plugins/ml2/ml2_conf_sriov.ini
[ml2_sriov]
# (ListOpt) Comma-separated list of
# supported Vendor PCI Devices, in format vendor_id:product_id
#
#* supported_pci_vendor_devs = 15b3:1004, 8086:10c9*
*supported_pci_vendor_devs = 8086:10c9*
# Example: supported_pci_vendor_devs = 15b3:1004
#
# (BoolOpt) Requires running SRIOV neutron agent for port binding
agent_required = True
Thanks
-Murali
On Tue, Dec 16, 2014 at 9:06 AM, david jhon djhon9...@gmail.com wrote:
Hi Murali,
Thanks for your response, I did the same, it has resolved errors
apparently but 1) neutron agent-list shows no agent for sriov, 2) neutron
port is created successfully but creating vm is erred in scheduling as
follows:
result from neutron agent-list:
+--++-+---++---+
| id | agent_type | host|
alive | admin_state_up | binary|
+--++-+---++---+
| 2acc7044-e552-4601-b00b-00ba591b453f | Open vSwitch agent | blade08 |
xxx | True | neutron-openvswitch-agent |
| 595d07c6-120e-42ea-a950-6c77a6455f10 | Metadata agent | blade08 |
:-) | True | neutron-metadata-agent|
| a1f253a8-e02e-4498-8609-4e265285534b | DHCP agent | blade08 |
:-) | True | neutron-dhcp-agent|
| d46b29d8-4b5f-4838-bf25-b7925cb3e3a7 | L3 agent | blade08 |
:-) | True | neutron-l3-agent |
+--++-+---++---+
2014-12-15 19:30:44.546 40249 ERROR oslo.messaging.rpc.dispatcher
[req-c7741cff-a7d8-422f-b605-6a1d976aeb09 ] Exception during message
handling: PCI $
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher
Traceback (most recent call last):
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
13$
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher
incoming.message))
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
17$
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher
return self._do_dispatch(endpoint, method, ctxt, args)
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line
12$
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher
result = getattr(endpoint, method)(ctxt, **new_args)
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/server.py, line 139,
i$
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher
return func(*args, **kwargs)
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/nova/scheduler/manager.py, line 175, in
s$
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher
filter_properties)
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py, line
$
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher
filter_properties)
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py, line
$
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher
chosen_host.obj.consume_from_instance(instance_properties)
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/nova/scheduler/host_manager.py, line
246,$
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher
self.pci_stats.apply_requests(pci_requests.requests)
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/nova/pci/pci_stats.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 ({'requests':
[InstancePCIRequest(alias_$
2014-12-15 19:30:44.546 40249 TRACE oslo.messaging.rpc.dispatcher.
Moreover, no /var/log/sriov-agent.log file exists. Please help me to fix
this issue. Thanks everyone!
On Mon, Dec 15, 2014 at 5:18 PM, Murali B mbi...@gmail.com wrote:
Hi David,
Please add as per
[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 service VM(traffic is redirected at L2). All the tenant VM's in cloud could use this service VM services by adding the ovs-rules in OVS Thanks -Murali ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] SRIOV failures error-
Hi Irena,
Thanks for response. we made the change to have same network across all the
compute nodes.
After the change we are getting the new error saying the binding failed for
the vif port when we create the VM.
FYI: Please find the complete logs below
Neutron/server.log
2014-12-04 18:35:02.498 6997 WARNING neutron.plugins.ml2.managers
[req-9fbe04eb-b31b-43a1-aba1-2c1009cf0dc4 None] Failed to bind port
f2536225-12bf-4381-adc7-e05660ea9bac on host compute4
2014-12-04 18:35:02.529 6997 WARNING neutron.plugins.ml2.plugin
[req-9fbe04eb-b31b-43a1-aba1-2c1009cf0dc4 None] In
_notify_port_updated(), no bound segment for port
f2536225-12bf-4381-adc7-e05660ea9bac on network
2cb7d304-9d31-4e28-b6ea-24f9abda99c1
2014-12-04 13:27:02.669 6997 ERROR neutron.notifiers.nova [-] Failed
to notify nova on events: [{'name': 'network-changed', 'server_uuid':
u'3eff58fe-0cc1-4b15-ae0b-70af47cc8f73'}]
Attached the document with complete bug report. please go through for more
information
Thanks
-Murali
On Wed, Dec 3, 2014 at 12:10 PM, Irena Berezovsky ire...@mellanox.com
wrote:
Hi Murali,
Seems there is a mismatch between pci_whitelist configuration and
requested network.
In the table below:
physical_network: *physnet2*
In the error you sent, there is:
[InstancePCIRequest(alias_name=None,count=1,is_new=False,request_id=58584ee1-8a41-4979-9905-4d18a3df3425,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
*To:* openstack-dev@lists.openstack.org; itz...@redhat.com
*Subject:* [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;
+-+---+
| hypervisor_hostname |
pci_stats
|
+-+---+
| compute2|
[]
|
| xilinx-r720 | [{count: 1, vendor_id: 8086,
physical_network: physnet2, product_id: 10ed}] |
| compute1|
[]
|
| compute4|
[]
|
+-+---+
we have enabled SRIOV agent on compute node 4 as well as xilinx-r720
Thanks
-Murali
BUG_Juno_SRIOV.docx
Description: MS-Word 2007 document
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
