On 05/04/2017 04:59 AM, Giuseppe Di Lena wrote:
Hi Chris,
I'm pretty sure a regular user can create a server group and specify the
anti-affinity filter.
yes, but we want that the user specifies just the Robustness; the way in which
we assign the instances to the compute nodes should be a black box for the
regular user(and also for the admin).
Server groups *are* a black box though. You create a server group and
set the policy of the group to "anti-affinity" and that's it. There's no
need for the user or admin to know anything else...
Why do you need to track which compute nodes the instances are on?
Because putting the instances in the correct compute nodes is just the first
step of the algorithm that we are implementing, for the next steps we need to
know where is each instance.
In a cloud, it shouldn't matter which specific compute node an instance
is on -- in fact, in clouds, an instance (workload) may not even know
it's on a hypervisor vs. a baremetal machine vs. a privileged container.
What is important for the user in a cloud to specify is the amount of
resources the workload will consume (this is the flavor in Nova) and a
set of characteristics (traits) that the eventual host system should have.
I think it would help if you describe in a little more detail what is
the eventual outcome you are trying to achieve and what use case that
outcome serves. Then we can assist you in showing you how to get to that
outcome.
Best,
-jay
Thank you for the question.
Best regards Giuseppe
Il giorno 03 mag 2017, alle ore 21:01, Chris Friesen
<[email protected]> ha scritto:
On 05/03/2017 03:08 AM, Giuseppe Di Lena wrote:
Thank you a lot for the help!
I think that the problem can be solved using the anti-affinity filter, but we want
a regular user can choose an instance and set the property(image, flavour,
network, etc.) and a parameter Robustness >= 1(that is the number of copies of
this particular instance).
I'm pretty sure a regular user can create a server group and specify the
anti-affinity filter. And a regular user can certainly specify --min-count and
--max-count to specify the number of copies.
After that, we put every copy of this instance in a different compute, but we
need to track where we put every copy of the instance (we need to know it for
the algorithm that we would implement);
Normally only admin-level users are allowed to know which compute nodes a given
instance is placed on. Why do you need to track which compute nodes the
instances are on?
Chris
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
