| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Fix for BZ1308313
|
|
|
|
| |
Set the new_nodes group when scaling up additional nodes
|
|
|
|
| |
working with preconfigured load balancer
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
This adds the ability to quickly set up a multi-master environment.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Split playbooks into two, one for 3.0 minor upgrades and one for 3.0 to 3.1
upgrades
- Move upgrade playbooks to common/openshift/cluster/upgrades from adhoc
- Added a byo wrapper playbooks to set the groups based on the byo
conventions, other providers will need similar playbooks added eventually
- installer wrapper updates for refactored upgrade playbooks
- call new 3.0 to 3.1 upgrade playbook
- various fixes for edge cases I hit with a really old config laying
around.
- fix output of host facts to show connect_to value.
|
|
|
|
|
| |
There the tests didn't know anything about connect_to and we had a case where
we weren't handling the migration from the 3.0 installer config format to 3.1
|
|
|
|
|
| |
Changes to installer.cfg.yaml to allow for better defaults in unattended mode.
Update example in the docs.
|
| |
|
| |
|
| |
|
|
add atomic-openshift-utils to openshift-ansible.spec file
no need for redundent spec file
remove dependencies that are not needed
|