| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
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
|
| | | |
|
| |\ \
| |/
|/| |
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
|
| | |
| |
| |
| |
| | |
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.
|
| |/
|
|
| |
configuration file is missing.
|
| |\
| |
| | |
atomic-openshift-installer: connect_to error handling
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Catch the exception that happens when connect_to isn't specified in installer.cfg.yaml
|
| |/
|
|
| |
A few fixes to keep pylint happy.
|
| |\
| |
| | |
Default to OSE 3.1 in interactive installer instead of 3.0.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Correct the case where the first host entered is not a master.
|
| |/
|
|
|
| |
For now, we should restrict the quick installer to a single master.
This should change in the near future.
|
| | |
|
| |\
| |
| | |
atomic-openshift-installer: Update prompts and help messages
|
| | | |
|
| | |
| |
| |
| |
| | |
This is an update to the no password sudo test meant to address some
weirdness around group vs. user permissions.
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- 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.
|
| |\
| |
| | |
atomic-openshift-installer: Remove question for container install
|
| | | |
|
| | |
| |
| |
| |
| | |
Removing the option for a container-based install from the quick
installer with it is in tech preview.
|
| |/
|
|
|
|
|
| |
If this file exists on disk, the installer will use it if the user didn't
specify an ansible config file on the CLI.
Rename share directory to match the rpm name. (utils vs util)
|
| |\
| |
| | |
Test fixes related to connect_to
|
| | |
| |
| |
| |
| | |
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
|
