Commit fd5300a6 authored by jeremy's avatar jeremy

clarify quay access [BCD-333]

parent 32cb91c0
......@@ -14,7 +14,7 @@ Username: myusername
Password: mypassword
$ docker pull quay.io/bonitasoft/bcd-controller:<version>
```
The username corresponds to `bcd_registry_user` and the password corresponds to `bcd_registry_password` described into the [Scenario file reference](scenarios.md). Both has been provided by your sales representative.
## Usage
......@@ -23,10 +23,10 @@ To enter the BCD controller environment, a Docker container has to be started on
Besides the following files have to be bind mounted from the control host to make them available to the BCD controller container:
- **`/host/path/to/bonita-continuous-delivery_<version>`** (mounted as `/home/bonita/bonita-continuous-delivery`) - This directory provides BCD Ansible playbooks and is known as the `BCD_HOME` directory.
- <div class="list-group-item list-group-item-warning">This file is required for <strong>Provisioning</strong>. It is not required for Living App management.</div>
**`ssh_private_key`** (mounted as `/home/bonita/.ssh/ssh_private_key`) - The `ssh_private_key` file is the SSH private key used to connect to your target machines. For AWS, this is the private part of your [EC2 key pair](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html). This file should only be accessible from your user (`chmod 600 ~/.ssh/ssh_private_key`).
- <div class="list-group-item list-group-item-warning">AWS credentials are required for <strong>Provisioning on AWS</strong>. It is not required for Living App management.</div>
**`.boto`** (mounted as `/home/bonita/.boto`) - The [`.boto`](https://boto.readthedocs.io/en/latest/boto_config_tut.html) file contains AWS credentials used to make programmatic calls to AWS. Indeed dynamic Amazon EC2 inventory management for Ansible runs on top of [Boto](https://aws.amazon.com/sdk-for-python/). The content of a `.boto` file is as follows:
```ini
[Credentials]
......
......@@ -23,9 +23,13 @@ Follow these installation steps on your control host.
$ unzip bonita-continuous-delivery_<version>.zip
This step creates a `bonita-continuous-delivery_<version>` directory which contains Bonita Continuous Delivery Ansible playbooks and roles.
3. Pull the `quay.io/bonitasoft/bcd-controller:<version>` Docker image from secured registry:
3. Pull the `quay.io/bonitasoft/bcd-controller:<version>` Docker image from secured registry.
The username corresponds to `bcd_registry_user` and the password corresponds to `bcd_registry_password` described into the [Scenario file reference](scenarios.md). Both has been provided by your sales representative.
$ docker login quay.io
Username: bonitasoft+john_doe_at_acme_com
Password: ***
Login Succeeded
$ docker pull quay.io/bonitasoft/bcd-controller:<version>
[...]
Status: Downloaded newer image for quay.io/bonitasoft/bcd-controller:<version>
......@@ -37,6 +41,9 @@ Follow these installation steps on your control host.
Basically, the `/dependencies` volume provided by the `quay.io/bonitasoft/bcd-dependencies` Docker image must be mounted or copied into the `dependencies` directory. For instance, here is how to create a Docker named volume with BCD dependencies from the data image:
$ docker login quay.io
Username: bonitasoft+john_doe_at_acme_com
Password: ***
Login Succeeded
$ docker run --rm -v bcd-dependencies-<bonita_version>:/dependencies quay.io/bonitasoft/bcd-dependencies:<bonita_version>
$ docker logout quay.io
......@@ -109,6 +116,9 @@ Assuming you have a `bonita-continuous-delivery_3.0.0.zip` archive in your `$HOM
[...]
$ docker login quay.io
Username: bonitasoft+john_doe_at_acme_com
Password: ***
Login Succeeded
$ docker pull quay.io/bonitasoft/bcd-controller:3.0.0
[...]
Status: Downloaded newer image for quay.io/bonitasoft/bcd-controller:3.0.0
......
......@@ -53,6 +53,8 @@ Password: mypassword
$ docker pull quay.io/bonitasoft/bcd-controller
```
The username corresponds to `bcd_registry_user` and the password corresponds to `bcd_registry_password` described into the [Scenario file reference](scenarios.md). Both has been provided by your sales representative.
#### Vagrant
As the controller access to them over the network it's not necessary to move them on the filesystem.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment