| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
If only 2 masters are specified, consider this a configuration error if running
an unattended install, and prevent it completely if running an attended
install. (continues to prompt for hosts until you have at least 3)
Because this condition cannot be entered in the interactive install, we can't
really write a test for this negative case.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
We're asserting the same things in loading facts over and over, which is not
what these tests are really intended to catch. This behavior is tested
elsewhere.
|
|
|
|
|
| |
Checking behavior when there is no LB specified, and when the user attempts
to re-use a master or node as their LB.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code was present to catch this in unattended installs but was looking for a
host record with both master/node and master_lb set to true, but in the
attended installs we were adding a separate host record with the same
connect_to.
Attended tests can now optionally specify multiple "attempted" strings for the
master_lb specification, we'll try to input each if multiple are specified.
Cleanup some empty defaults and error messages as well.
|
|
|
|
|
|
| |
When the masters are the only nodes in play, we need to explicitly set
schedulable to True due to logic in openshift_facts.py which assumes that if
the node is also a master, schedulable should be false.
|
|\
| |
| | |
Improve scaleup playbook
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
- modify evaluate host to set oo_nodes_to_config to a new variable
g_new_nodes_group if defined rather than g_nodes_group and also skip adding
the master when g_new_nodes_group is set.
- Remove byo specific naming from playbooks/common/openshift-cluster/scaleup.yml
and created a new playbooks/byo/openshift-cluster/scaleup.yml playbook.
|
| | |
|
|\ \
| | |
| | | |
HA support for atomic-openshift-installer
|
| | |
| | |
| | |
| | | |
harness
|
| | |
| | |
| | |
| | | |
If the only Nodes we have are also on Masters we set the scheduleable.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Also:
* minor rewording of the text that informs the admin about scheduleable
masters.
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The preconfigured load balancers, previously denoted by having 'run_on' set to
false, cannot have their facts gathered which results in a stack trace. Later
when we write out the inventory we have to fake out the hostname and just use
'connect_to'.
We're likely going to have the concept of other types of "plug-in" hosts where
we don't run ansible. We should make sure we abstract this properly so it's
easy to add additional types of hosts.
Also in the commit:
- Renamed 'run_on' to 'preconfigured' and inverted the logic as needed
- Output tally of Masters and Nodes as well as remaining Masters required for
HA
- Minor rewording in a few places
- Currently only prompting for the load balancer after all other hosts have
been entered
- Removed spurious echo
|
| | |\ \
| | | | |
| | | | |
| | | | | |
into quick_ha
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Rename ha_proxy variables and methods to 'master_lb' to better
future-proof things.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Reverse the order we ask two questions: What variant the user wants
to install and which hosts to install on. This lets us avoid asking
for multiple masters for 3.0 installs.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
This adds the ability to quickly set up a multi-master environment.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The preconfigured load balancers, previously denoted by having 'run_on' set to
false, cannot have their facts gathered which results in a stack trace. Later
when we write out the inventory we have to fake out the hostname and just use
'connect_to'.
We're likely going to have the concept of other types of "plug-in" hosts where
we don't run ansible. We should make sure we abstract this properly so it's
easy to add additional types of hosts.
Also in the commit:
- Renamed 'run_on' to 'preconfigured' and inverted the logic as needed
- Output tally of Masters and Nodes as well as remaining Masters required for
HA
- Minor rewording in a few places
- Currently only prompting for the load balancer after all other hosts have
been entered
- Removed spurious echo
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Rename ha_proxy variables and methods to 'master_lb' to better
future-proof things.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Reverse the order we ask two questions: What variant the user wants
to install and which hosts to install on. This lets us avoid asking
for multiple masters for 3.0 installs.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
This adds the ability to quickly set up a multi-master environment.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Rework setting of hostname
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- set the hostname for all installs < 3.1 or 1.1
- provide a new variable openshift_set_hostname to override default behavior
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
added graphs for openshift master and network in zabbix
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fixed a bug. opsconditions now updates propertly.
|