Thank Evgeniy. I came to the same conclusion.
-- Javeria On Fri, Nov 6, 2015 at 1:41 PM, Evgeniy L <[email protected]> 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 <[email protected]> > 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: >> [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
