[openstack-dev] [nova] Gap between host cpu features and guest cpu's
Hi everyone, Currently nova exposes all the host CPU instruction set extensions available on the compute node in the host state, and there is a scheduler filter `ComputeCapabilitiesFilter` which looks at these. But the limits on this is: CPU instruction set in ComputeCapabilitiesFilter should be guest's view instead of host's. Admin may use specific set of CPU instruction to deploy instance to make it migratable in a heterogeneous cloud. This is actually by design in nova as nova is using baselineCPU andallowed to pass/config guest CPU instruction feature for instance. Shall we add a string "guest_features" in ``ComputeNode`` object as ``ComputeNode:cpu_info:guest_features`` And let ComputeCapabilitiesFilter use guest_features instead of host features here? Is this a real gap ? and the above easy fix is the right way ? Thanks -yuntongjin __ 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] [devstack] pip wheel' requires the 'wheel' package
Hello, I got an error when try to ./stack.sh as: /2015-03-02 05:58:20.692 | net.ipv4.ip_local_reserved_ports = 35357,35358 2015-03-02 05:58:20.959 | New python executable in tmp-venv-NoMO/bin/python 2015-03-02 05:58:22.056 | Installing setuptools, pip...done. 2015-03-02 05:58:22.581 | ERROR: 'pip wheel' requires the 'wheel' package. To fix this, run: pip install wheel/ After pip install wheel, got same error. In [2]: wheel.__path__ Out[2]: ['/usr/local/lib/python2.7/dist-packages/wheel'] In [5]: pip.__path__ Out[5]: ['/usr/local/lib/python2.7/dist-packages/pip'] $ which python /usr/bin/python As above, the wheel can be imported successfully, any hints ? Thanks. __ 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] [blazar] currectly status
Thanks for the info, I surely will let you know when I have doubts to dive deep into the code. Thanks -yuntong From: Nikolay Starodubtsev [mailto:nstarodubt...@mirantis.com] Sent: Wednesday, February 11, 2015 5:05 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [blazar] currectly status Hi, I'm agree with Sylvain. Also, if you want to contribute to Blazar ping me in IRC, I can tell you where you can start with it. Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2015-02-11 11:18 GMT+03:00 Sylvain Bauza sba...@redhat.commailto:sba...@redhat.com: Le 11/02/2015 04:24, Jin, Yuntong a écrit : Hello, May I ask the currently status of blazar project, it’s been very quiet there for past half year, part of reason could be related to Gantt project? The way I see this project is very usefully for NFV use case, and I really like to know the status of it, maybe also Gantt project. Thanks Hi, Thanks for your interest on Blazar. The existing core team has been reallocated on various other projects so we ended doing regular updates to the repository since around 6 months. That said, as it is an open-source project, anybody can contribute and I would be glad to review some changes, provided they are not time-consuming. Last discussion with TC members in Atlanta (for the Juno summit) showed that there are benefits to have a reservation system in OpenStack, but the thought was that it would probably be something related to the Compute program, ie. something that Nova could leverage. As the current Nova scheduler is about to be spined off in a separate project called Gantt, I'm IMHO thinking (and that's my sole opinion) that Blazar could maybe merge with Gantt so that the existing backend would allow new APIs for Gantt by asking to select a destination later in time than now. That said, Gantt is far from being a separate repository now, as we're struggling to reduce the technical debt on Nova for splitting out the scheduler so I wouldn't expect any immediate benefit for Gantt nor Blazar now. As many people are looking around Blazar and Gantt, I think it would be interesting to setup a BoF session during the Vancouver Summit about reservations and SLA in OpenStack so that we could see how we could move on. -Sylvain __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ 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] [blazar] currectly status
Hello, May I ask the currently status of blazar project, it's been very quiet there for past half year, part of reason could be related to Gantt project? The way I see this project is very usefully for NFV use case, and I really like to know the status of it, maybe also Gantt project. Thanks __ 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] [ceilometer] nova api.fault notification isn't collected by ceilometer
On 2015年02月10日 11:34, yuntong wrote: On 2015年02月10日 05:12, gordon chung wrote: In nova api, a nova api.fault notification will be send out when the when there is en error. http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/__init__.py#n119 but i couldn't find where they are processed in ceilometer, an error notification can be very desired to be collected, do we have plan to add this, shall i need a bp to do that ? there's a patch for review to store error info: https://review.openstack.org/#/c/153362/ This looks good, but how do we do with other priority message like WARN ? -yuntong cheers, /gord/ Yep, that's what i'm looking for, thanks, another notification from nova that is missed in ceilometer is info from nova api: https://github.com/openstack/nova/blob/master/nova/notifications.py#L64 this notify_decorator will decorate every nova/ec2 rest api and send out a notification for each api actions: https://github.com/openstack/nova/blob/master/nova/utils.py#L526 from which will send out notification like: %s.%s.%s % (module, key, method) , and no notification plugin in ceilometer to deal with them. Let me know if i should file a bug for this. Thanks, -yuntong __ 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] [ceilometer] nova api.fault notification isn't collected by ceilometer
Hi all, In nova api, a nova api.fault notification will be send out when the when there is en error. http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/__init__.py#n119 but i couldn't find where they are processed in ceilometer, an error notification can be very desired to be collected, do we have plan to add this, shall i need a bp to do that ? -Yuntong __ 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] [ceilometer] nova api.fault notification isn't collected by ceilometer
On 2015年02月10日 05:12, gordon chung wrote: In nova api, a nova api.fault notification will be send out when the when there is en error. http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/__init__.py#n119 but i couldn't find where they are processed in ceilometer, an error notification can be very desired to be collected, do we have plan to add this, shall i need a bp to do that ? there's a patch for review to store error info: https://review.openstack.org/#/c/153362/ cheers, /gord/ Yep, that's what i'm looking for, thanks, another notification from nova that is missed in ceilometer is info from nova api: https://github.com/openstack/nova/blob/master/nova/notifications.py#L64 this notify_decorator will decorate every nova/ec2 rest api and send out a notification for each api actions: https://github.com/openstack/nova/blob/master/nova/utils.py#L526 from which will send out notification like: %s.%s.%s % (module, key, method) , and no notification plugin in ceilometer to deal with them. Let me know if i should file a bug for this. Thanks, -yuntong __ 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
