| commit | cb561c8ce365a51b1b8c42744dd7d60e5891ed69 | [log] [tgz] |
|---|---|---|
| author | Carlos Frias <friasc@google.com> | Wed May 02 17:12:41 2018 -0400 |
| committer | Carlos Frias <friasc@google.com> | Wed May 02 17:12:41 2018 -0400 |
| tree | b9f1fde9e533b602f1156051dda0c0cbe26998ee | |
| parent | 6b6b5978f0a6f6c682e795aee2329115e1c88ad5 [diff] |
Updated existing changes
This repository contains Ansible playbooks that use roles to install, configure and maintain Apigee Edge, Developer Portal and the Monitoring Dashboard. These playbooks orchestrate the usage of the roles to achieve the installation, upgrade and maintenance of the Edge platform. The roles perform functionally discrete activities. This is important because many installation, configuration and maintenance activities are multiple invocations of the same scripts or commands except for changes in either the parameters used, the sequence of the invocations or both. Please see the links below for descriptions and instructions specific to your activity.
Ansible playbooks are invoked at the command line. The assumption is that you know Ansible or are capable of learning Ansible quickly.
Usage involves the following steps:
ansible-galaxy to download rolesansible-playbook to execute the tasks.An Apigee OPDK Ansible Configuration Accelerator is available to get you going quickly. Please refer to the accelerator to understand how to configure the following:
custom-properties.ymlcredentials.ymllicense.txtPlease refer to Ansible Documentation for details on installing, configuring and running Ansible.
We are using Ansible Galaxy to distribute playbook role dependencies. The basic usage pattern we follow is:
ansible-galaxy install -r { galaxy-formatted-requirements-file.yml } -f
A table has been provided that maps Ansible Galaxy dependency files to Ansible Playbooks.
Ansible playbooks are invoked at the command line as:
ansible-playbook { playbook-file.yml }
These playbooks use Ansible tags extensively to execute functionally significant portions of the installation. These tags have been used consistently across all the playbooks. In some cases, the tags perform slightly different tasks but achieve the semantic functionality ascribed by the name.
| Tag Name | Description |
|---|---|
| cache | Updates the local Ansible cache with OPDK variables that are used for the generation of configuration files. |
| os | Prepares the operating system for the installation of OPDK as covered in the Edge Installation Overview and Install the Edge Apigee Setup Utility. This covers operating system packages, updates to system configuration files and adapts to operating systems. |
| bootstrap | Install the Apigee bootstrap. This adapts to either online or offline |
| common | Install common Apigee components used on all nodes. This does not include operating system packages |
| config | Generate the Edge Configuration File |
| ds | Install the ds profile |
| ms | Install the ms profile |
| rmp | Install the rmp profile |
| r | Install the r profile |
| mp | Install the mp profile |
| qpid | Install the qs profile |
| pg | Install the ps profile |
| org | Onboard an organization |
| validate | Validate the installation |
| logs | Download the configuration files and logs on a node that contains an Apigee component |
This is not an officially supported Google product.
We'd love to accept your patches and contributions to this project. Please review our guidelines.