Thanks Evgeniy. On Fri, Feb 5, 2016 at 11:07 AM, Evgeniy L <e...@mirantis.com> 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 <spasqu...@mirantis.com> > 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: >> openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev