Hello Maike,
> How is this exactly supposed to be applied?
It isn't. Ansible's `--limit` option will limit also the information
gathering to the listed hosts, thus breaking ElastiCluster's playbooks
which rely on a "global view" of the cluster (i.e., much of the info
is taken dynamically from discovered `hostvars` instead of filled in
statically in the inventory).
You can use `--no-setup` if you want to run a batch of operations in
ElastiCluster and only reconfigure the cluster at the end::
elasticluster remove-node mycluster compute003 --no-setup
elasticluster remove-node mycluster compute004 --no-setup
elasticluster resize --add 2:bigcompute --no-setup mycluster
# now configure the cluster with the new "shape"
elasticluster setup mycluster
Does this help?
Ciao,
R
--
You received this message because you are subscribed to the Google Groups
"elasticluster" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
