| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Update the tests to match 3.3 being the only version.
Add support for non-latest if it's specified in the config file.
|
|
|
|
|
|
| |
With the latest changes to behavior around uninstalled hosts during a scaleup,
nosetests were broken. This updates the tests to verify that we exit when we are
expecting.
|
|
|
|
|
| |
Update the nosetests to reflect the new location of ansible_ssh_user
in the config file.
|
|
|
|
|
|
| |
Remove the option to select unsupported versions in the quick installer.
Fixes BZ#1358101
|
|
|
|
|
|
|
|
|
|
| |
A more dynamic and flexible method of writing out host groups to the ansible
inventory file. To accompany this, in the quick-installer interactive mode
the etcd role is automatically applied to any masters. Anyone hand writing
the quick installer config will now have to explicitly specify which hosts
will be etcd.
Fixes #2200
|
|
|
|
| |
Initial build of new, more flexible installer config file format.
|
|
|
|
|
| |
Some UI improvements to help make it more clear to the user what information we
are looking for.
|
|
|
|
| |
Update the input to account for the new questions around proxies.
|
|
|
|
|
|
|
| |
Always prompt the user for a storage host. The prompt defaults to the first master and warns the
user not to use a container-based installation for this.
WIP
|
|\
| |
| | |
Add --gen-inventory command to atomic-openshift-installer.
|
| |
| |
| |
| |
| |
| | |
With the addition of a --gen-inventory flag and always displaying the location
of the inventory written to disk, we should write the hosts file to a more
prominent location rather than a hidden directory.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This will just generate the Ansible inventory once all information is gathered,
inform the user where to find it, and exit.
Includes some test utility updates to make what broke as a result of this
change less fragile.
|
|/ |
|
|
|
|
| |
Fix the nosetests after the rebase
|
|
|
|
| |
Add a question to ask the user for a default subdomain.
|
| |
|
|
|
|
| |
Add test for not displaying HA hints for 3.0 installs
|
|
|
|
| |
working with preconfigured load balancer
|
| |
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
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
|
|\ |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|