Hi Simon. For running selected tasks on already deployed nodes you can use the following command of CLI (fuel command-line utility):
fuel node --node node_id1[,node_idN] --tasks task1[,taskN] where node_id - is the unique identifier of node, where specified tasks shall be run. >>>> Any plan to have a nicer experience in future Fuel releases? Yes, we are working on this. Regards, Bulat Gaifullin Mirantis Inc. > On 05 Feb 2016, at 15:54, Igor Kalnitsky <[email protected]> wrote: > > Simon, > >> Nope, it doesn't work for me since it should run for *all* the nodes, >> irrespective of their roles. AFAIK update_required doesn't support '*'. > > If your plugin provides a new node role as well as additional tasks > for other node roles, you may try to workaround that by using > > reexecute_on: [deploy_changes] > > task marker. In that case, the task will be executed each time you hit > "Deploy Changes" button, so make sure it's idempotent task. > > - igor > > > On Fri, Feb 5, 2016 at 1:04 PM, Evgeniy L <[email protected]> wrote: >> Simon, >> >>>> Any plan to have a nicer experience in future Fuel releases? >> >> I haven't heard about any plans on improvements for that, but management >> team should know better whether it's on roadmap or not. >> >> Thanks, >> >> On Fri, Feb 5, 2016 at 1:52 PM, Simon Pasquier <[email protected]> >> wrote: >>> >>> Thanks Evgeniy. >>> >>> On Fri, Feb 5, 2016 at 11:07 AM, Evgeniy L <[email protected]> wrote: >>>> >>>> Hi Simon, >>>> >>>> As far as I know it's expected behaviour (at least for the current >>>> release), and it's expected that user reruns deployment on required nodes >>>> using fuel cli, in order to install plugin on a live environment. >>> >>> >>> Ok. For the record, this means running this command for every node that is >>> already deployed: >>> $ fuel node --node-id <id> --deploy >>> >>> Any plan to have a nicer experience in future Fuel releases? >>> >>>> >>>> It depends on specific role, but "update_required" field may help you, it >>>> can be added to role description, Fuel reruns deployment on nodes with >>>> roles, which are specified in the list, if new node with the role is added >>>> to the environment. >>> >>> >>> Nope, it doesn't work for me since it should run for *all* the nodes, >>> irrespective of their roles. AFAIK update_required doesn't support '*'. >>> >>>> >>>> >>>> Thanks, >>>> >>>> [1] >>>> https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/fixtures/openstack.yaml#L16-L18 >>>> >>>> On Fri, Feb 5, 2016 at 12:53 PM, Simon Pasquier <[email protected]> >>>> wrote: >>>>> >>>>> Hi, >>>>> I'm testing the ability to install Fuel plugins in a an environment that >>>>> is already deployed. >>>>> My starting environment is quite simple: 1 controller + 1 compute. After >>>>> the initial deployment, I've installed the 4 LMA plugins: >>>>> - LMA collector >>>>> - Elasticsearch-Kibana [*] >>>>> - InfluxDB-Grafana [*] >>>>> - Infrastructure Alerting [*] >>>>> [*] adds a new role >>>>> Of course, all plugins have "is_hotpluggable: true" in their metadata >>>>> definition. >>>>> My expectation is that I can add a new node with the new roles and that >>>>> the LMA collector tasks are executed for all 3 nodes. So I've added the >>>>> new >>>>> node and click the "Deploy changes" button. My re-deployment runs fine >>>>> but I >>>>> notice that the plugins aren't installed on the existing nodes (eg >>>>> /etc/fuel/plugins/...) so there is no way that the plugins tasks can be >>>>> executed on already deployed nodes... Is this a known limitation? Am I >>>>> missing something? >>>>> Best regards, >>>>> Simon >>>>> >>>>> >>>>> >>>>> __________________________________________________________________________ >>>>> 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 >>> >> >> >> __________________________________________________________________________ >> 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
