Re: [openstack-dev] [nova] [scheduler] blueprint for host/hypervisor location information
Host not hypervisor I think; consider nova baremetal, where hypervisor == machine that runs tftpd and makes IPMI calls, and host == place where the user workload will execute. -Rob On 29 September 2013 17:52, Mike Spreitzer wrote: > I have begun drafting a blueprint about more detailed host/hypervisor > location information, to support the sort of policy-informed placement > decision-making that Debo, Yathi, and I have been talking about. The > blueprint is at > https://blueprints.launchpad.net/nova/+spec/hypervisor-location-attribute > and the details are at > https://wiki.openstack.org/wiki/Nova/HypervisorExtendedAttributes > > You see I am a little schizophrenic here about scope. The blueprint is > named quite narrowly, and the details page is named more broadly; this is > because I am not sure what else you folks will chime in with. > > I am not sure whether this information should really be attached to a > hypervisor or to a host. I proposed hypervisor because currently the > details for a hypervisor are a map (easily extended) whereas the details for > a host are currently a list of uniformly-typed contents (not so easily > extended). But host might actually be more appropriate. I am looking for > feedback on whether/how to go that way. BTW, where would I find > documentation on host details? The current page on nova extensions > (http://docs.openstack.org/api/openstack-compute/2/content/ext-compute.html) > is lacking most of them. > > You will see that I have proposed what the API looks like, but not the > source of this additional information. I will ask my colleagues who have > something like this locally, how they got it done and what they would > recommend to OpenStack. Perhaps you good folks have some suggestions. Is > there obviously one way to do it? Is it obvious that there can be no one > way and so a plug point is required? > > Thanks, > Mike > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Robert Collins Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] [scheduler] blueprint for host/hypervisor location information
I have begun drafting a blueprint about more detailed host/hypervisor location information, to support the sort of policy-informed placement decision-making that Debo, Yathi, and I have been talking about. The blueprint is at https://blueprints.launchpad.net/nova/+spec/hypervisor-location-attribute and the details are at https://wiki.openstack.org/wiki/Nova/HypervisorExtendedAttributes You see I am a little schizophrenic here about scope. The blueprint is named quite narrowly, and the details page is named more broadly; this is because I am not sure what else you folks will chime in with. I am not sure whether this information should really be attached to a hypervisor or to a host. I proposed hypervisor because currently the details for a hypervisor are a map (easily extended) whereas the details for a host are currently a list of uniformly-typed contents (not so easily extended). But host might actually be more appropriate. I am looking for feedback on whether/how to go that way. BTW, where would I find documentation on host details? The current page on nova extensions ( http://docs.openstack.org/api/openstack-compute/2/content/ext-compute.html ) is lacking most of them. You will see that I have proposed what the API looks like, but not the source of this additional information. I will ask my colleagues who have something like this locally, how they got it done and what they would recommend to OpenStack. Perhaps you good folks have some suggestions. Is there obviously one way to do it? Is it obvious that there can be no one way and so a plug point is required? Thanks, Mike___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [oslo] Please add oslo.version to your project watches
Hey all, oslo.version is in gerrit now, which is a split out of the version code from pbr. I'd love if if you'd add oslo.version to your project watches so that patches get love. oslo.sphinx could probably use the same treatment. Monty ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Gate issues - what you can do to help
> 1) Please *do not* Approve or Reverify stable/* patches. The pyparsing > requirements conflict with neutron client from earlier in the week is still > not resolved on stable/*. Also there's an issue with quantumclient and Nova stable/grizzly: https://jenkins01.openstack.org/job/periodic-nova-python27-stable-grizzly/34/console ...nova/network/security_group/quantum_driver.py", line 101, in get id = quantumv20.find_resourceid_by_name_or_id( AttributeError: 'module' object has no attribute 'find_resourceid_by_name_or_id' Relevant difference in pip freeze from last good is: -python-quantumclient==2.2.3 +python-neutronclient==2.3.1 +python-quantumclient==2.2.4.2 Looks like new quantumclient compatbility layer is missing few methods. Cheers, Alan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
