Open Stack

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
sure that the group's data is sent to the nodes deployment yaml
(astute.yaml) but it probably should be as it could enable the AZ story.

[1]
https://docs.mirantis.com/openstack/fuel/fuel-6.0/reference-architecture.html#implementing-multiple-cluster-networks

On Thu, Jun 25, 2015 at 4:09 AM Guillaume Thouvenin <thouveng at gmail.com>
wrote:

> 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 <adanin at mirantis.com>
> 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/+spec/role-as-a-plugin
>>
>>
>> On Wednesday, June 24, 2015, Samuel Bartel <samuel.bartel.pro at gmail.com>
>> wrote:
>>
>>> 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 for compute node B
>>> 2) I was thinking of a plugin to define Availability zone and setup
>>> compute node A and B in AZ1 and compute node C in AZ2
>>>
>>
I'm assuming you mean you want to set the ephemeral instance storage one
way or another and not cinder as multiple providers are already supported


> I think it would possible to check according to specific value in the name
>>> of the node. But it doesn't seems to me to be very clean. And if we hav
>>> many plugins built in that way, name of the node would become very
>>> complicated soon and it is not very flexible. I was more looking a way to
>>> put a tag in the node (without needed to manually edit deployement yaml
>>> files)
>>>
>>
There is someone working on a tagging spec for future development (after
7.0) Already, I don't remember who.


> Anyone has already done something like this or has a tips on that topic?
>>>
>>> regards
>>>
>>> Samuel
>>>
>>>
>>>
>>
>> --
>> Andrey Danin
>> adanin at mirantis.com
>> skype: gcon.monolake
>>
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 

--

Andrew Woodward

Mirantis

Fuel Community Ambassador

Ceph Community
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150625/f4801ad9/attachment.html>