Hi,
First, thank you all for your contributions on that topic (I don't know
what it has been split in two thread but let reply on this one)
Igor : the problem I try to solve is the following, I would like to be able
to :
1/decide on which compute node I want to deploy a plugin. for the example
of
Hi Samuel,
Here's my 2 cents on this topic. First of all, I'd like to ask you -
what problem do you try to solve? Please, answer on that first because
it'll help me to come back with solution.
Currently it looks like an error-prone approach to apply nova-nfs
tasks only on roles with some label. W
Samuel,
We could likely extend NodeGroups to do some of theses things. It was
initially intended to create separated underlay network schemes for
multiple-cluster-networks [1] but you would not be prevented from using the
same network addresses if you didn't need the partation from that. I'm not
s
Hi guys,
And also for 7.0 there is a spec in review [1] about custom labels that
may be interesting to differentiate nodes with the same role if labels are
exposed via the astute.yaml.
Regards,
[1] https://review.openstack.org/#/c/184076/
On Thu, Jun 25, 2015 at 12:47 PM, Andrey Danin wrote:
Hi, Samuel,
We use magic words in node names for Fuel Contrail plugin. It uses
the "bare" role to deploy Contrail controllers.
Unfortunately, we don't have node tags in 6.1, but we are going to
implement custom roles from a plugin in 7.0. Please see a spec
https://blueprints.launchpad.net/fuel/+s
Samuel,
As I know one node can have many roles.
For 1/ You can specify custom nova-nfs role and assign it on compute nodes.
Regards,
Andriy
On Wed, Jun 24, 2015 at 10:21 PM, Samuel Bartel wrote:
> Andriy,
>
> May be 'role' was not the correct word here.
> For me role are compute, controller,
Andriy,
May be 'role' was not the correct word here.
For me role are compute, controller, base-os, cinder, mongo. I know that we
can specify that a task A should be executed on some role (controller and
compute for example) and a task B on some other roles (Cinder for example).
To come back to m
Samuel,
AFAIK labels will not be related to tasks, it's just marks for filtering
nodes.
What "roles" means for you?
we have tasks (A, B, C, D) and on some nodes tasks A B D should be
executed, on some B C etc. So plugin can provide specials marks or tags or
sets (we call it "roles") and link
task
Julia,
It is exactly what i was thinking. With such a mechanism we would be able
to define custom labels to apply different type of task on compute nodes
according to their labels. I add a comment on the review. As for now I
don't see how we would be able to create custom label from plugin. In suc
Samuel, I would like you to consider this proposal:
https://review.openstack.org/#/c/184076/6/specs/7.0/node-custom-attributes.rst
This is about support of custom node labels. I think plugins should be able
to assign its own labels to nodes via Nailgun API. Is it possible? Will it
suit your case?
Irina,
Thanks for the link. Unfortunatly it does not cover my use cases. What we
would like to do is not define a new role.
We would like to be able to apply plugin to some compute node for example
and not in the others compute nodes or to be able to execute plugin with a
given config on some comp
Samuel,
Currently, there is a spec on introducing a new role through a plugin [1] -
the feature is targeted at 7.0.
Feel free to comment on it and ask questions right in the commit.
[1] https://review.openstack.org/#/c/185267/
--
Best regards,
Irina
Partner Management Business Analyst
skype:
Hi folks
I am wondering if it is possible to differenciate nodes within a same role.
Is it possible for example to apply aplugin to a compute node A but not a
compute node B?
It will be more clear with examples :
1) for the nfs plugin I want to use nfs storage backend for compute node A
but LVM fo
13 matches
Mail list logo
