In addition to omitting instances or instance groups from the inventory file, you must also deprovision instances or instance groups before starting the upgrade. Omitting the instance or the instance group from the inventory file will not be enough to remove them from the cluster. The database server should be on the same network or in the same data center as the Tower server for performance reasons.įor upgrading an existing cluster: When upgrading a cluster, you may decide that you want to also reconfigure your cluster to omit existing instances or instance groups. Tower will not configure replication or failover for the database that it uses, although Tower should work with any replication that you have. Edit this file and add your external database information before running the setup script.įor Ansible Automation Platform or Automation Hub: Be sure to add an automation hub host in the group (Tower and Automation Hub cannot be installed on the same node). setup.sh installer playbook.įor installations and upgrades: If you need to make use of external databases, you must ensure the database sections of your inventory file are properly setup. The contents of the inventory file should be defined in. Setting up the Inventory File ¶Īs you edit your inventory file, there are a few things you must keep in mind: If this is the case, you can set automationhub_backup_collections = false and the backup/restore process will not have to backup/restore /var/lib/pulp.įor OpenShift-based deployments, refer to OpenShift Deployment and Configuration. If a partition (e.g., LVM, NFS, CephFS, etc.) was mounted there, an enterprise organization would ensure it is always backed up. By default, this is set to true so Tower automatically backs up the artifacts by default. It will end up in /etc/galaxy-importer/galaxy-importer.cfgĪutomationhub_require_content_approval: Whether or not Automation Hub enforces the approval mechanism before collections are made availableĪutomationhub_disable_https: Whether or not Automation Hub should be deployed with TLS enabledĪutomationhub_disable_hsts: Whether or not Automation Hub should be deployed with the HTTP Strict Transport Security (HSTS) web-security policy mechanism enabledĪutomationhub_ssl_validate_certs: Whether or not Automation Hub should validate certificate when requesting itself (default = False) because by default, Platform deploys with self-signed certificatesĪutomationhub_ssl_cert: Same as web_server_ssl_cert but for Automation Hub UI and APIĪutomationhub_ssl_key: Same as web_server_ssl_key but for Automation Hub UI and APIĪutomationhub_backup_collections: Automation Hub provides artifacts in /var/lib/pulp. Settings available for an Automation Platform install:Īutomationhub_importer_settings: Dictionary of settings/configuration to pass to galaxy-importer. It means that any deployment of the Platform becomes at least a 2-node deployment topology. Tower and Automation Hub can not run on the same node, this is a scenario that is not supported. The database server should be on the same network or in the same datacenter as the Tower server for performance reasons.
0 Comments
Leave a Reply. |