[openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

Jaromir Coufal jcoufal at redhat.com
Wed Jan 15 10:47:54 UTC 2014

On 2014/13/01 16:45, Jiří Stránský wrote:
>> The other approach is just to scale the number of nodes in a role and
>> let system decide the best match (which node profile is chosen will be
>> decided on the best fit, probably).
> Hmm i'm not sure i understand - what do you think by "best fit" here?
> E.g. i have 32 GB RAM profile and 256 GB RAM profile in the compute role
> (and i have unused machines available for both profiles), and i increase
> compute node count by 2. What do i best-fit against?
> (Alternatively, if we want to support scaling a role using just one
> spinner, even though the role has more profiles, maybe we could pick the
> "largest" profile with unused nodes available?)
Hehe, that is a good question - what is the magic 'best fit'. It will 
depend on nova-scheduler, how it is implemented.

Complete product of my mind follows...
Theoretically, it might be the way that scheduler will look at all 
requirements and find the best distribution across the deployment so it 
satisfies all needs (for example two roles are fighting for one node). 
If there is situation that it doesn't matter, it would take the 
higher/lower one (there can be some preference, priority to set it up).

To summarize, I think this is all about scheduler configuration.

-- Jarda

More information about the OpenStack-dev mailing list