[openstack-dev] [Fuel][Plugins] Role for Fuel Master Node

Javeria Khan javeriak at plumgrid.com
Fri Nov 6 09:35:13 UTC 2015


Sounds great.


--
Javeria

On Fri, Nov 6, 2015 at 2:31 PM, Evgeniy L <eli at mirantis.com> wrote:

> Great, let us know, if you have any problems.
>
> Also for the future we have some ideas/plans to provide a way for
> a plugin to retrieve any information from API.
>
> Thanks,
>
> On Fri, Nov 6, 2015 at 12:16 PM, Javeria Khan <javeriak at plumgrid.com>
> wrote:
>
>> Thank Evgeniy.  I came to the same conclusion.
>>
>>
>> --
>> Javeria
>>
>> On Fri, Nov 6, 2015 at 1:41 PM, Evgeniy L <eli at mirantis.com> wrote:
>>
>>> Javeria,
>>>
>>> In your case, I think it's easier to generate config on the target node,
>>> using puppet for example, since the information which you may need
>>> is placed in /etc/astute.yaml file. Also it may be a problem to retrieve
>>> all required information about the cluster, since API is protected with
>>> keystone authentication.
>>>
>>> Thanks,
>>>
>>> On Thu, Nov 5, 2015 at 5:35 PM, Javeria Khan <javeriak at plumgrid.com>
>>> wrote:
>>>
>>>> Hi Evgeniy,
>>>>
>>>>>
>>>>> 1. what version of Fuel do you use?
>>>>>
>>>> Using 7.0
>>>>
>>>>
>>>>> 2. could you please clarify what did you mean by "moving to
>>>>> deployment_tasks.yaml"?
>>>>>
>>>> I tried changing my tasks.yaml to a deployment_tasks.yaml as the wiki
>>>> suggests for 7.0. However I kept hitting issues.
>>>>
>>>>
>>>>> 3. could you please describe your use-case a bit more? Why do you want
>>>>> to run
>>>>>     tasks on the host itself?
>>>>>
>>>>
>>>> I have a monitoring tool that accompanies my new plugin, which
>>>> basically uses a config file that contains details about the cluster (IPs,
>>>> VIPs, networks etc). This config file is typically created on the installer
>>>> nodes through the deployment, Fuel Master in this case.
>>>>
>>>>
>>>> __________________________________________________________________________
>>>> 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
>>>
>>>
>>
>> __________________________________________________________________________
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151106/7d14e3d0/attachment.html>


More information about the OpenStack-dev mailing list