summaryrefslogtreecommitdiffstats
path: root/utils/src
Commit message (Collapse)AuthorAgeFilesLines
* atomic-openshift-installer: Remove HA hint for 3.0 installSamuel Munilla2015-12-161-10/+10
| | | | | Small update to remove the hint for multiple masters if we are doing a 3.0 installation.
* atomic-openshift-installer: Error handling on yaml loadingSamuel Munilla2015-12-081-3/+9
| | | | | | This addresses the stack trace that has been plaguing recent demos. In the case of an error with callback_facts.yaml the program output is much clearer and a course of action is suggested.
* Improving output when gathering factsBrenton Leanhardt2015-12-081-1/+1
|
* Bug 1287977 - Incorrect check output from atomic-openshift-installer when ↵Brenton Leanhardt2015-12-081-2/+8
| | | | working with preconfigured load balancer
* Centralize etcd/schedulability logic for each host.Devan Goodwin2015-12-013-19/+37
|
* Improved installation summary.Devan Goodwin2015-12-011-12/+45
| | | | | | Displays each host and the roles it will play based on the current configuration. As the configuration grows the summary will adapt to indicate embedded vs separte etcd, scheduled vs unscheduled nodes, etc.
* Add warning for HA deployments with < 3 dedicated nodes.Devan Goodwin2015-12-011-8/+12
|
* Cleanup more schedulable typos.Devan Goodwin2015-12-011-1/+1
|
* Merge branch 'master' into loadbalanced-2Devan Goodwin2015-12-012-9/+9
|\
| * Fixing 'unscheduleable' typoBrenton Leanhardt2015-11-302-9/+9
| |
* | Fix bug when warning on no dedicated nodes.Devan Goodwin2015-11-301-3/+2
| |
* | Suggest dedicated nodes for an HA deployment.Devan Goodwin2015-11-301-0/+9
| |
* | Error out if no load balancer specified.Devan Goodwin2015-11-301-14/+10
| |
* | Adjust requirement for 3 masters for HA deployments.Devan Goodwin2015-11-301-8/+33
| | | | | | | | | | | | | | | | | | 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.
* | Improved output when re-running after editing config.Devan Goodwin2015-11-271-4/+5
| |
* | Print a system summary after adding each.Devan Goodwin2015-11-271-8/+20
| |
* | Text improvements for host specification.Devan Goodwin2015-11-271-7/+19
| |
* | Test unattended HA quick install.Devan Goodwin2015-11-262-9/+16
| | | | | | | | | | Checking behavior when there is no LB specified, and when the user attempts to re-use a master or node as their LB.
* | Don't prompt to continue during unattended installs.Devan Goodwin2015-11-261-4/+6
| |
* | Block re-use of master/node as load balancer in attended install.Devan Goodwin2015-11-262-12/+27
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | Explicitly set schedulable when masters == nodes.Devan Goodwin2015-11-251-5/+13
|/ | | | | | 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.
* Merge pull request #968 from detiber/fixScaleup2Brenton Leanhardt2015-11-241-2/+2
|\ | | | | Improve scaleup playbook
| * fixes for installer wrapper scaleupJason DeTiberus2015-11-241-2/+2
| |
* | Merge pull request #978 from brenton/quick_haBrenton Leanhardt2015-11-243-35/+176
|\ \ | |/ |/| HA support for atomic-openshift-installer
| * Properly setting scheduleability for HA Master scenariosBrenton Leanhardt2015-11-242-10/+16
| | | | | | | | If the only Nodes we have are also on Masters we set the scheduleable.
| * Avoid printing the master and node totals in the add-a-node scenarioBrenton Leanhardt2015-11-241-7/+8
| |
| * Fixing tests for quick_haBrenton Leanhardt2015-11-241-2/+3
| | | | | | | | | | | | Also: * minor rewording of the text that informs the admin about scheduleable masters.
| * Removing a debug lineBrenton Leanhardt2015-11-241-1/+0
| |
| * atomic-openshift-installer: Fix lint issueSamuel Munilla2015-11-231-1/+1
| |
| * Handling preconfigured load balancersBrenton Leanhardt2015-11-233-15/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * atomic-openshift-installer: Rename ha_proxySamuel Munilla2015-11-233-14/+14
| | | | | | | | | | Rename ha_proxy variables and methods to 'master_lb' to better future-proof things.
| * atomic-openshift-installer: Reverse version and host collectionSamuel Munilla2015-11-231-8/+10
| | | | | | | | | | | | 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.
| * Breakup inventory writingSamuel Munilla2015-11-231-16/+24
| |
| * Enforce 1 or 3 mastersSamuel Munilla2015-11-231-2/+8
| |
| * atomic-openshift-installer: HA for quick installerSamuel Munilla2015-11-233-17/+110
| | | | | | | | This adds the ability to quickly set up a multi-master environment.
* | Bug 1284991 - "atomic-openshift-installer uninstall" error when ↵Brenton Leanhardt2015-11-241-1/+1
|/ | | | configuration file is missing.
* Merge pull request #890 from smunilla/friendly_unattended_errorsBrenton Leanhardt2015-11-201-1/+6
|\ | | | | atomic-openshift-installer: connect_to error handling
| * atomic-openshift-installer: connect_to error handlingSamuel Munilla2015-11-201-1/+6
| | | | | | | | Catch the exception that happens when connect_to isn't specified in installer.cfg.yaml
* | atomic-openshift-installer: pylint fixesSamuel Munilla2015-11-201-5/+7
|/ | | | A few fixes to keep pylint happy.
* Merge pull request #902 from dgoodwin/rpm-test-fixBrenton Leanhardt2015-11-202-5/+8
|\ | | | | Default to OSE 3.1 in interactive installer instead of 3.0.
| * Pylint fix for long line in cli docstring.Devan Goodwin2015-11-161-1/+2
| |
| * Default to installing OSE 3.1 instead of 3.0.Devan Goodwin2015-11-162-3/+4
| |
| * Fix tests on systems with openshift-ansible rpms installed.Devan Goodwin2015-11-161-1/+2
| |
* | atomic-openshift-installer: Correct single master caseSamuel Munilla2015-11-171-1/+1
| | | | | | | | Correct the case where the first host entered is not a master.
* | atomic-openshift-installer: Temporarily restrict to single masterSamuel Munilla2015-11-161-4/+6
|/ | | | | For now, we should restrict the quick installer to a single master. This should change in the near future.
* Fix invalid sudo command testTakayoshi Kimura2015-11-161-1/+1
|
* Merge pull request #884 from smunilla/english_updatesBrenton Leanhardt2015-11-121-4/+8
|\ | | | | atomic-openshift-installer: Update prompts and help messages
| * atomic-openshift-installer: Update prompts and help messagesSamuel Munilla2015-11-121-4/+8
| |
* | atomic-openshift-installer: Update nopwd sudo testSamuel Munilla2015-11-121-1/+1
|/ | | | | This is an update to the no password sudo test meant to address some weirdness around group vs. user permissions.
* Refactor upgrade playbook(s)Jason DeTiberus2015-11-103-6/+11
| | | | | | | | | | | | | - 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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-06 03:44:08 +0000