On 12/3/13 12:08 PM, "Daniel P. Berrange" <berra...@redhat.com> wrote:
>On Tue, Dec 03, 2013 at 01:47:31AM -0800, Gary Kotton wrote: >> Hi, >> I think that this information should be used as part of the scheduling >> decision, that is hosts that are to be selected should be excluded if >>they >> do not have the necessary resources available. It will be interesting to >> know how this is going to fit into the new scheduler that is being >> discussed. > >The CPU topology support shouldn't have any interactions with, nor >cause any failures post-scheduling. ie If the host has declared that >it has sufficient resources to run a VM with the given vCPU count, >then that is sufficient. Yes, you are correct. I was thinking about another issue altogether - CPU reservations. > >This is one of the reasons why the design is such that glance image >properties just declare an upper bound on topology, not an absolute >requirement. This allows the host chosen to run the VM to decide the >guest topology to suit its specific topology / resource availability. > >Regards, >Daniel >-- >|: >https://urldefense.proofpoint.com/v1/url?u=http://berrange.com/&k=oIvRg1%2 >BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8% >3D%0A&m=%2BVH6Fb2ZdY4rBiTv4xjHlWTzi2bx3yL%2FPYmBmexK%2BCA%3D%0A&s=7ef7ed03 >951dddf6141327a904baa12ca10765e6a17210de8d44818dc9d8d008 -o- >https://urldefense.proofpoint.com/v1/url?u=http://www.flickr.com/photos/db >errange/&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfD >tysg45MkPhCZFxPEq8%3D%0A&m=%2BVH6Fb2ZdY4rBiTv4xjHlWTzi2bx3yL%2FPYmBmexK%2B >CA%3D%0A&s=9f86fd7275b4bf94724c3f1e6863f42709742d902a3b312116509377c142cc6 >7 :| >|: >https://urldefense.proofpoint.com/v1/url?u=http://libvirt.org/&k=oIvRg1%2B >dGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3 >D%0A&m=%2BVH6Fb2ZdY4rBiTv4xjHlWTzi2bx3yL%2FPYmBmexK%2BCA%3D%0A&s=a16ed6479 >e9165cbe64f8de01f8ef7d3c132afd9c7db688dcc3f8e7973c9ee21 -o- > >https://urldefense.proofpoint.com/v1/url?u=http://virt-manager.org/&k=oIvR >g1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxP >Eq8%3D%0A&m=%2BVH6Fb2ZdY4rBiTv4xjHlWTzi2bx3yL%2FPYmBmexK%2BCA%3D%0A&s=8dd3 >b1fc6613623eb226ed8373d0c141246749495c52dc4e406cad0ee36e8434 :| >|: >https://urldefense.proofpoint.com/v1/url?u=http://autobuild.org/&k=oIvRg1% >2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8 >%3D%0A&m=%2BVH6Fb2ZdY4rBiTv4xjHlWTzi2bx3yL%2FPYmBmexK%2BCA%3D%0A&s=8f19277 >d6494fac28d405a51715a945707d45bddc9ed653a1d4372db09e36198 -o- > >https://urldefense.proofpoint.com/v1/url?u=http://search.cpan.org/~danberr >/&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45M >kPhCZFxPEq8%3D%0A&m=%2BVH6Fb2ZdY4rBiTv4xjHlWTzi2bx3yL%2FPYmBmexK%2BCA%3D%0 >A&s=b6a59f4029b86825f8cb79c2ff060d70e0b2cec3d7965d5d3e5fe89d0f7991aa :| >|: >https://urldefense.proofpoint.com/v1/url?u=http://entangle-photo.org/&k=oI >vRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZF >xPEq8%3D%0A&m=%2BVH6Fb2ZdY4rBiTv4xjHlWTzi2bx3yL%2FPYmBmexK%2BCA%3D%0A&s=8f >47662a2eb99894688bb8b56f68787514b036a657f703a31cb55d4b719a132e -o- > >https://urldefense.proofpoint.com/v1/url?u=http://live.gnome.org/gtk-vnc&k >=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPh >CZFxPEq8%3D%0A&m=%2BVH6Fb2ZdY4rBiTv4xjHlWTzi2bx3yL%2FPYmBmexK%2BCA%3D%0A&s >=ea746f14f96aed6ae931abe9ab71140272560a7624e25c747e20dfcd1fa041eb :| > >_______________________________________________ >OpenStack-dev mailing list >OpenStack-dev@lists.openstack.org >https://urldefense.proofpoint.com/v1/url?u=http://lists.openstack.org/cgi- >bin/mailman/listinfo/openstack-dev&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=e >H0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=%2BVH6Fb2ZdY4rBiTv4xj >HlWTzi2bx3yL%2FPYmBmexK%2BCA%3D%0A&s=6f7cbd4e68065ed00ff18ed1065c726507ff7 >90b0671de9bd0454de01a8f2def _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev