Branch: refs/heads/master
Home: https://github.com/gc3-uzh-ch/elasticluster
Commit: d82ec65876a25160099c5b87cb5cb6f489bb813d
https://github.com/gc3-uzh-ch/elasticluster/commit/d82ec65876a25160099c5b87cb5cb6f489bb813d
Author: Riccardo Murri <riccardo.mu...@gmail.com>
Date: 2018-04-23 (Mon, 23 Apr 2018)
Changed paths:
M elasticluster/cluster.py
M elasticluster/exceptions.py
M elasticluster/providers/ansible_provider.py
Log Message:
-----------
Raise an error if not enough nodes of each kind are available at setup.
This reverses the previous behavior which was to consider an empty
inventory file as "fine" (!?!?), and, consequently, print out the
message "Your cluster is ready" which was totally misleading.
In addition, remove code that tried to juggle nodes around if not
enough nodes of each kind were started. The reason for this is
threefold:
(1) cloud providers have gotten so much better since 2012 that VM boot
errors are rare,
(2) this "juggling" behavior was anyway incorrect since different node
kinds can in principle have different flavors, and
(3) trying to be too smart makes it difficult to reason about what a
supposedly simple function like `Cluster.start()` does.
--
You received this message because you are subscribed to the Google Groups
"elasticluster-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticluster-dev+unsubscr...@googlegroups.com.
To post to this group, send email to elasticluster-dev@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticluster-dev/5ade4dec894bc_69ee2adf34ad1c0c12297%40hookshot-fe-31feec6.cp1-iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.
