ansible tower upgrade and migration · 2017. 7. 20. · ansible tower upgrade and migration,...

Ansible Tower Upgrade and MigrationRelease Ansible Tower 3.1.0

Red Hat, Inc.

Jul 12, 2017

CONTENTS

1 Release Notes for Ansible Tower Version 3.1.0 21.1 Ansible Tower Version 3.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Upgrading Ansible Tower 42.1 Upgrade Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2 Obtaining Ansible Tower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.3 Setting up the Inventory File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.4 The Setup Playbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 System Tracking Migration 9

4 Role-Based Access Controls 104.1 Enhanced and Simplified RBAC System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.2 Specific Changes to Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5 Job Template Changes 115.1 Prompt on Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.2 Permissions/RBAC Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135.3 Surveys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

6 Job Output View Changes 156.1 Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176.2 Standard Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186.3 Job Details View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.4 Event Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

7 Using virtualenv with Ansible Tower 257.1 Modifying the virtualenv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

8 Index 26

9 Copyright © 2016 Red Hat, Inc. 27

Index 28

i

Ansible Tower Upgrade and Migration, Release Ansible Tower 3.1.0

Thank you for your interest in Ansible Tower by Red Hat. Ansible Tower is a commercial offering that helps teamsmanage complex multi-tier deployments by adding control, knowledge, and delegation to Ansible-powered environ-ments.

Note: You must upgrade your Ansible Tower 2.4.4 (or later) system to Ansible Tower 3.0 before you can upgrade toAnsible Tower 3.1.0.

The Ansible Tower Upgrade and Migration Guide discusses how to upgrade your Ansible Tower 2.4.4 (or later) systemto the 3.0 version. The Ansible Tower 3.0 release introduced many updates and changes to Tower, including changesto the way upgrades run and a completely rewritten RBAC system. This guide covers these and other related changesthat you should keep in mind as you plan to migrate your data and prepare for this upgrade.

Ansible Tower Version 3.1.0; Feb 28, 2017; https://access.redhat.com/

CONTENTS 1

https://access.redhat.com/

CHAPTER

ONE

RELEASE NOTES FOR ANSIBLE TOWER VERSION 3.1.0

1.1 Ansible Tower Version 3.1.0

• Added support for configuring most aspects of Ansible Tower directly from the Tower user interface (and TowerAPI), rather than editing Tower configuration files

• Added support for “Scale-Out” Clusters, which replaces the HA/Redundancy method from prior Tower releases

• Added support for Workflows, a chain of job templates executed in order

• Added support for sending event and log messages to various logging services (Elastic, Splunk, Sumologic,Loggly, generic REST endpoint)

• Added support for a new Tower Search feature which supports GitHub-style “key:value” searching

• Added support for Ubuntu 16.04

• Added support for a New Project Sync Architecture, where projects are now checked out at job runtime

• Added support for setting timeouts on job runs

• Added support for internationalization and localization (French and Japanese)

• Added support for multi-playbook Workflows

• Added /api/v1/settings for Tower managed settings. This corresponds to the in-Tower configuration UI

• Added support for windows scan jobs

• Added support so that the SCM Revision used is now stored on Job

• Added support for API endpoints to now show __search filter fields for broader searching of objects

• Added support so that system jobs are now shown in /api/v1/unified_jobs

• Added support for the new Ansible vmware_inventory script

• Added support for Job stdout downloads, which may generate and cache on the fly

• Added support for /api/v1/inventory_updates and /api/v1/project_updates to view thosespecific job types

• Added support for user_capabilities API elements in various places to allow API consumers to know if theiruser can perform the referenced actions on the object

• Added support for set_stats for Workflow jobs to persist data between Workflow job runs, support added inansible core also

• Added support for Tower callbacks so that they can now resolve ansible_host as well asansible_ssh_host

• Added support for Tower callbacks so that they now filter out ansible_ variables on POST

2


• Added support for notifications so that they are emitted on jobs marked as failed by the dead job detector

• Added eu-west-2 and ca-central-1 to the list of supported EC2 regions

• Added support for format=ansi_download when downloading stdout

• Deprecated support for Rackspace inventories

• Fixed an issue where manual projects could be launched/updated

• Fixed various unicode issues

• Fixed various issues dealing with self signed certificatesvalue.

• Fixed Jobs so that they now show $encrypted for these variables, where they previously did not

• Improved performance for viewing job and job template lists

• Improved Tower virtualenv so that it is purged on upgrade

• Improved setup playbook so that it is more tolerant of various iptables/firewalld configurations

• Improved the optimization of PostgreSQL installation to improve overall performance

• Improved database migrations through consolidation to make upgrades/installs faster

• Improved hardening for web server configuration (SSL, HSTS)

• Removed zeromq as a communications channel between dependent services in favor of rabbitmq

• Removed /api/v1/jobs/n/job_plays and /api/v1/jobs/n/job_tasks

• Removed proot in favor of bubblewrap for process isolation

• Removed the ability to make POST requests on the /api/v1/jobs/ endpoint

• Removed has_schedules from various endpoints, as it was never populated

• Removed support for Red Hat Enterprise Linux 6/CentOS 6 and Ubuntu 12.04

• Updated surveys so that a blank value for a survey question default value now passes an empty string as a value

• Updated surveys so that previously existing surveys with blank default question values now pass empty stringsas an extra variable

• Updated Websockets, moving them from socket.io to django channels and are now served under port 443/80along with the regular web service. Port 8080 is no longer needed.

• Updated Job results so that they are now driven by job events and thus provides clickable context

• Updated Tower so that it now uses the system time zone by default

• Updated Tower requirements for Ansible–Tower now requires Ansible 2.1 or later

• Updated Ansible inventory plugins to the latest versions

• Updated Web server to NGINX from Apache

• Updated survey passwords so that they are now encrypted when stored in the database

• Updated request_tower_configuration.sh

1.1. Ansible Tower Version 3.1.0 3

CHAPTER

TWO

UPGRADING ANSIBLE TOWER

Topics:

• Upgrade Planning

• Obtaining Ansible Tower

• Setting up the Inventory File

• The Setup Playbook

Note: You must upgrade your Ansible Tower 2.4.4 (or later) system to Ansible Tower 3.0 before you can upgrade toAnsible Tower 3.1.0.

2.1 Upgrade Planning

This section covers changes that you should keep in mind as you attempt to upgrade your Ansible Tower Instance

• If you are not yet using a 2.4.x version of Ansible Tower, do not attempt to upgrade directly to Ansible Tower3.0.x or 3.1.0. You must start with a system which has a verison of Tower 2.4.x installed or the upgrade will fail.

• If you are not using using a 3.0.x version of Ansible Tower; you must upgrade to 3.0.x before you can upgradeto 3.1.0.

• Ansible Tower 3.0 simplified installation and removed the need to run ./configure/ as part of the initialsetup.

• The file tower_setup_conf.yml is no long used. Instead, you should now edit the inventory file in the/ansible-tower-setup-<tower_version>/ directory.

• Earlier version of Tower used MongoDB when setting up an initial database; please note that Ansible Tower 3.0has replaced the use of MongoDB with PostgreSQL.

2.2 Obtaining Ansible Tower

Download and then extract the Ansible Tower installation/upgrade tool: http://releases.ansible.com/ansible-tower/setup/

4

http://releases.ansible.com/ansible-tower/setup/

http://releases.ansible.com/ansible-tower/setup/


root@localhost:~$ tar xvzf ansible-tower-setup-latest.tar.gzroot@localhost:~$ cd ansible-tower-setup-<tower_version>

To install or upgrade, start by editing the inventory file in the ansible-tower-setup-<tower_version>directory, replacing <tower_version> with the version number, such as 2.4.5 or 3.0.0. directory.

2.3 Setting up the Inventory File

As you edit your inventory file, there are a few things you must keep in mind:

• The contents of the inventory file should be defined in ./inventory, next to the ./setup.sh installerplaybook.

• For installations and upgrades: If you need to make use of external databases, you must ensure the databasesections of your inventory file are properly setup. Edit this file and add your external database informationbefore running the setup script.

• For redundant installations: If you are creating a redundant setup, you must replace localhost with thehostname or IP address of all instances. All nodes/instances must be able to reach any others using this hostnameor address.

• For installations: When performing an installation, you must supply any necessary passwords in the inventoryfile.

Note: Changes made to the installation process now require that you fill out the all of the password fields in theinventory file. If you need to know where to find the values for these they should be:

admin_password='' <— Tower local admin password

pg_password='' <—- Found in /etc/tower/conf.d/postgres.py

rabbitmq_password='' <—- create a new password here

If you have already run setup but did not previously provide passwords, you must run the following command as root orsudo, #rabbitmqctl change_password tower "rabbitPass" (whatever you populated inrabbitmq_password).

Then rerun the following command: sudo ./setup.sh

Example Inventory file

• For provisioning new nodes: When provisioning new nodes add the nodes to the inventory file with all currentnodes, make sure all passwords are included in the inventory file.

• For upgrades: When upgrading, be sure to compare your inventory file to the current release version. It isrecommended that you keep the passwords in here even when performing an updgrade.

Example Single Node Inventory File

[tower]localhost ansible_connection=local

[database]

[all:vars]admin_password='password'

pg_host=''

2.3. Setting up the Inventory File 5


pg_port=''

pg_database='awx'pg_username='awx'pg_password='password'

rabbitmq_port=5672rabbitmq_vhost=towerrabbitmq_username=towerrabbitmq_password='password'rabbitmq_cookie=rabbitmqcookie

# Needs to be true for fqdns and ip addressesrabbitmq_use_long_name=false

Example Multi Node Cluster Inventory File

[tower]clusternode1.example.comclusternode2.example.comclusternode3.example.com

[database]dbnode.example.com

[all:vars]ansible_become=true

admin_password='password'

pg_host='dbnode.example.com'pg_port='5432'

pg_database='tower'pg_username='tower'pg_password='password'

rabbitmq_port=5672rabbitmq_vhost=towerrabbitmq_username=towerrabbitmq_password=towerrabbitmq_cookie=rabbitmqcookie

# Needs to be true for fqdns and ip addressesrabbitmq_use_long_name=true

Example Inventory file for an external existing database

[tower]node.example.com ansible_connection=local

[database]

[all:vars]admin_password='password'pg_password='password'rabbitmq_password='password'

2.3. Setting up the Inventory File 6


pg_host=‘database.example.com’pg_port=’5432’


Example Inventory file for external database which needs installation

[tower]node.example.com ansible_connection=local

[database]database.example.com

[all:vars]admin_password='password'pg_password='password'rabbitmq_password='password'

pg_host=‘database.example.com’pg_port=’5432’


Once any necessary changes have been made, you are ready to run ./setup.sh.

Note: Root access to the remote machines is required. With Ansible, this can be achieved in different ways:

• ansible_ssh_user=root ansible_ssh_password=”your_password_here” inventory host or group variables

• ansible_ssh_user=root ansible_ssh_private_key_file=”path_to_your_keyfile.pem” inventory host or group vari-ables

• ANSIBLE_BECOME_METHOD=’sudo’ ANSIBLE_BECOME=True ./setup.sh

• ANSIBLE_SUDO=True ./setup.sh

2.4 The Setup Playbook

Note: Ansible Tower 3.0 simplifies installation and removes the need to run ./configure/ as part of the instal-lation setup. Users of older versions should follow the instructions available in the v.2.4.5 (or earlier) releases of theTower Documentation available at: http://docs.ansible.com/

The Tower setup playbook script uses the inventory file and is invoked as ./setup.sh from the path where youunpacked the Tower installer tarball.

root@localhost:~$ ./setup.sh

The setup script takes the following arguments:

2.4. The Setup Playbook 7

http://docs.ansible.com/


• -h – Show this help message and exit

• -i INVENTORY_FILE – Path to Ansible inventory file (default: inventory)

• -e EXTRA_VARS – Set additional Ansible variables as key=value or YAML/JSON (i.e. -ebundle_install=false forces an online installation)

• -b – Perform a database backup in lieu of installing

• -r – Perform a database restore in lieu of installing (a default restore path is used unless EXTRA_VARS areprovided with a non-default path, as shown in the code example below)

./setup.sh -e 'restore_backup_file=/path/to/nondefault/location' -r

Note: Please note that a issue was discovered in Tower 3.0.0 and 3.0.1 that prevented proper system backups andretorations.

If you need to back up or restore your Tower v3.0.0 or v3.0.1 installation, use the v3.0.2 installer to do so.

2.4. The Setup Playbook 8

CHAPTER

THREE

SYSTEM TRACKING MIGRATION

Once your system has been upgraded to Ansible Tower 3.x, you will find that your system tracking data has beenmigrated from MongoDB to PostgreSQL. If you want to delete the old data in MongoDB, you can do so manually.First, connect to your mongo database using the mongo command line client, then run the following commands:

$ use system_tracking$ db.runCommand( { dropDatabase: 1 } )

At this point, you can also remove the MongoDB packages.

9

CHAPTER

FOUR

ROLE-BASED ACCESS CONTROLS

Ansible Tower 3.0 has changed significantly around the way that the Role-Based Access Control (RBAC) systemworks. For the latest RBAC documentation, refer to the Role-Based Access Controls section in the Tower User Guide.

4.1 Enhanced and Simplified RBAC System

Bason on user feedback, Ansible Tower both expands and simplifies its role-based access control. No longer is jobtemplate visibility configured via a combination of permissions on inventory, projects, and credentials. If you want togive any user or team permissions to use a job template, just assign permissions directly on the job template. Similarly,credentials are now full objects in Tower’s RBAC system, and can be assigned to multiple users and/or teams for use.

A new ‘Auditor’ type has been introduced in Tower as well, who can see all aspects of the systems automation, but hasno permission to run or change automation, for those that need a system-level auditor. (This may also be useful for aservice account that scrapes automation information from Tower’s API.)

4.2 Specific Changes to Note

There are a few changes you should keep in mind as you work with the RBAC system as redesigned for Ansible Tower:

• You no longer set the “team” or “user” for a credential. Instead, you use Tower’s RBAC system to grantownership, auditor, or usage roles.

• Deletion of job run data is now restricted to system and organization administrators.

• Projects no longer have multiple organizations. You must provide an organization when creating a new projectthrough the API:

- projects/:id/organizations --> removed

• New Auditor type in Tower has been added which can see all aspects of the systems automation but does nothave permission to run or change things.

10

http://docs.ansible.com/ansible-tower/3.1.0/html/userguide/security.html#rbac-ug

CHAPTER

FIVE

JOB TEMPLATE CHANGES

Job templates have been updated in Tower to allow you more flexibility when creating and working with them.

5.1 Prompt on Launch

In prior versions of Ansible Tower, you could set “Prompt on Launch” against Extra Varaibles that you want topotentially pass through the job template. Starting with version 3.0, Ansible Tower allows you to prompt for aninventory selection, job type, and more.

Selecting “Prompt on Launch” means that even if a value is supplied at the time of the job template creation, theuser launching the job will be prompted to supply new information or confirm what was entered in the job templateoriginally.

The following job template settings allow for prompting at the time of launch:

• Job Type (run or check type jobs only, as scan jobs cannot be changed at the time of launch)

• Inventory

• Machine credential

• Limit

• Job Tags

• Extra variables

11


As you work with migrating your Tower 2.4.5 job templates to 3.x, please keep in mind the following:

• All “Prompt on Launch” fields are set to False by default after migrating to 3.x (new job templates created alsohave all “Prompt on Launch” fields set to False by default).

– With one exception for those upgrading from 2.4.5 to 3.x: if a credential used in Tower 2.4.5 was null, thecredential will be prompted for in 3.x.

• If you have Job Templates with a null credential, in the migration from 2.4.5 to 3.x, “ask_credential_on_launch”is set to True.

– Note that there was no way to set a default credential in 2.4.5. However, in 3.x, you can set a defaultcredential and select to prompt the user at launch time to confirm the default credential or change it tosomething new.

• All other “ask_xx_on_launch” prompts are set to False.

• Starting with Tower 3.x, if “ask_variables_on_launch” is set to False, extra variables passed at launch time (viaUI or API) that are not part of an enabled survey are ignored.

• While there are no changes to how “ask_variables_on_launch” behaves, keep in mind that these variables com-bine with survey answers.

5.1. Prompt on Launch 12


5.2 Permissions/RBAC Notes

Job template visibility is no longer configured via a combination of permissions on inventory, projects, and credentials.Admins who want to give any user or team permissions to use a job template can quickly assign permissions directlyon the job template. Similarly, credentials are now full objects in Tower’s RBAC system, and can be assigned tomultiple users and/or teams for use.

If a job template a user has been granted execution capabilities on does not specify an inventory or credential, the userwill be prompted at run-time to select among the inventory and credentials in the organization they own or have beengranted usage capabilities.

Users that are job template administrators can make changes to job templates; however, to make changes to theinventory, project, playbook, or credentials used in the job template, the user must also have the “Use” role for theproject, inventory, and all credentials currently being used or being set.

5.3 Surveys

In prior versions of Ansible Tower, you had to select a checkbox to “Enable Survey” on the Job Template before abutton appeared allowing you to “Create Survey”.

Enabling and creating surveys is much simplier in Ansible Tower.

At the bottom of each job template is a button ( ) which opens a new dialog where you can enteryour survey questions and reposnses.

Use the ON/OFF toggle button to quickly activate or deactivate this survey prompt.

Once you have entered the question information, click Add to add the survey prompt.

5.2. Permissions/RBAC Notes 13


A stylized preview of the survey is presented, along with a New Question button. Click this button to add additionalquestions.

For any question, you can click on the Edit button to edit the question, the Delete button to delete the question, andclick on the Up and Down arrow buttons to rearrange the order of the questions. Click Save to save the survey.

5.3. Surveys 14

CHAPTER

SIX

JOB OUTPUT VIEW CHANGES

With the update of the overall Tower user interface, it is worth noting the changes to how job results are displayed.

Job results for inventory syncs and SCM updates only show the Results and Standard Out of the job recently Run. Jobresults for playbook runs consist of Results, Standard Out, Details, and the Event Summary.

15


For more details regarding Job Results, refer to Jobs in the Ansible Tower User Guide.

16

http://docs.ansible.com/ansible-tower/3.1.0/html/userguide/jobs.html#ug-jobs


6.1 Results

The Results area shows the basic status of the job (Running, Pending, Successful, or Failed), its start and end times,which template was used, how long the job run took, who launched it, and more. The buttons in the top right of theResults view allow you to relaunch or delete the job.

By clicking on these Results entries, where appropriate, you can view the corresponding job templates, projects, andother Tower objects.

6.1. Results 17


6.2 Standard Out

The Standard Out display shows the full results of running the SCM Update or Inventory Sync playbook. This showsthe same information you would see if you ran the Ansible playbook using Ansible from the command line, and canbe useful for debugging.

Prior to Ansible Tower 3.0, the Standard Out was a separate display and was not included in the overall job resultsview.

The buttons in the top right corner of the Standard Out display allow you to toggle the output as a main view or todownload the output.

6.2. Standard Out 18


6.3 Job Details View

The Job Details view in Ansible Tower offers step-by-step views into Plays, Tasks, and Hosts, walking you througheach section of the job results until you drill down into your host informaiton.

6.3. Job Details View 19


6.3.1 Plays

The Plays area shows the plays that were run as part of this playbook. The displayed plays can be filtered by PlayName, and can be limited to show only failed plays (using the ALL/FAIL view toggle).

For each play, Tower shows the Play Name, start time for the play, the elapsed time of the play, the play Name, andwhether the play succeeded or failed (indicated by the status dot to the left of the pPlay Name). Clicking on a specificplay filters the Tasks and Host Events area to only display tasks and hosts relative to that selected play.

6.3.2 Tasks

The Tasks area shows the tasks run as part of plays in the playbook. The displayed tasks can be filtered by TaskName, and can be limited to only failed tasks.

For each task, Tower shows the task Name, the start time for the task, the elapsed time of the task, whether the tasksucceeded or failed. Clicking on a specific task filters the Host Events area to only display hosts relative to that task.

6.3.3 Host Events

The Host Events area shows hosts affected by the selected play and task. For each host, Tower shows the host’s status,its name, and any Item or Message set by that task.



Clicking on the linked hostname brings up the Host Event dialog for that host and task.

The Host Event dialog shows the events for this host and the selected play and task.

There is also a JSON tab which displays the result in JSON format.

There is also a JSON tab which displays the result in JSON format.



6.4 Event Summary

The Event Summary area shows a summary of events for all hosts affected by this playbook as well as the HostStatus Summary.

By default, the Event Summary is collapsed and must be expanded before it can be viewed. Versions of Tower priorto 3.0 always displayed the Event Summary.

Hosts can be filtered by their hostname, and can be limited to showing only changed, failed, OK, and unreachablehosts.

6.4. Event Summary 22


For each host, the Event Summary area shows the hostname and the number of completed tasks for that host, sortedby status.



Clicking on the hostname brings up a Host Events dialog, displaying all tasks that affected that host.

This dialog can be filtered by the status of the tasks, as well as by the hostname.

For each event, Tower displays the status, the play name, and the task name.

The Host Summary area shows a graph summarizing the status of all hosts affected by this playbook run.


CHAPTER

SEVEN

USING VIRTUALENV WITH ANSIBLE TOWER

Ansible Tower 3.0 uses virtualenv. Virtualenv creates isolated Python environments to avoid problems caused byconflicting dependencies and differing versions. Virtualenv works by simply creating a folder which contains all ofthe necessary executables and dependencies for a specific version of Python. Ansible Tower creates two virtualenvsduring installation–one is used to run Tower, while the other is used to run Ansible. This allows Tower to run in astable environment, while allowing you to add or update modules to your Ansible Python environment as necessary torun your playbooks.

Note: For more information on virtualenv, see Virtual Environments

7.1 Modifying the virtualenv

Modifying the virtualenv used by Tower is unsupported and not recommended. Instead, you can add modules tothe virtualenv that Tower uses to run Ansible.

To do so, activate the Ansible virtualenv:

. /var/lib/awx/venv/ansible/bin/activate

...and then install whatever you need using pip:

pip install mypackagename

25

http://docs.python-guide.org/en/latest/dev/virtualenvs/

CHAPTER

EIGHT

INDEX

• genindex

26

CHAPTER

NINE

COPYRIGHT © 2016 RED HAT, INC.

Ansible, Ansible Tower, Red Hat, and Red Hat Enterprise Linux are trademarks of Red Hat, Inc., registered in theUnited States and other countries.

If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and providea link to the original version.

Third Party Rights

Ubuntu and Canonical are registered trademarks of Canonical Ltd.

The CentOS Project is copyright protected. The CentOS Marks are trademarks of Red Hat, Inc. (“Red Hat”).

Microsoft, Windows, Windows Azure, and Internet Explore are trademarks of Microsoft, Inc.

VMware is a registered trademark or trademark of VMware, Inc.

Rackspace trademarks, service marks, logos and domain names are either common-law trademarks/service marks orregistered trademarks/service marks of Rackspace US, Inc., or its subsidiaries, and are protected by trademark andother laws in the United States and other countries.

Amazon Web Services”, “AWS”, “Amazon EC2”, and “EC2”, are trademarks of Amazon Web Services, Inc. or itsaffiliates.

OpenStack™ and OpenStack logo are trademarks of OpenStack, LLC.

Chrome™ and Google Compute Engine™ service registered trademarks of Google Inc.

Safari® is a registered trademark of Apple, Inc.

Firefox® is a registered trademark of the Mozilla Foundation.

All other trademarks are the property of their respective owners.

27

INDEX

AAnsible, executing in a virtual enviroment, 25

Iinstallation script

inventory file setup, 5playbook setup, 7

inventory file setup, 5

Jjob output, sdout, 15jobs

event summary, 22host events, 20host summary, 22job details, 19plays, 20tasks, 20

Mmigration, 9migration considerations, 9MongoDB data removal, 9

Ppermissions, 10, 11playbook setup, 7

setup.sh, 7PostgreSQL data migration, 9

RRBAC, 10, 11release notes, v3.0, 2roles, 10

Ssingleton roles, 10system tracking data, 9system-wide roles, 10

Uupgrade, 4

upgrade considerations, 4

Vvirtual enviroment, 25

28

ansible tower upgrade and migration · 2017. 7. 20. · ansible tower upgrade and migration,...

Documents