Unverified Commit cfc59458 authored by JeremJR's avatar JeremJR Committed by GitHub

Merge pull request #65 from bonitasoft/BCD-262_replace-on-premises-concept

replace 'on-premises' with 'existing infrastructure' concept (BCD-262)
parents ec864f00 edee18fc
......@@ -8,13 +8,12 @@ Welcome to **Bonita Continuous Delivery** documentation website!
The Bonita Continuous Delivery (BCD) add-on provides a solution to use _Continuous Delivery_ practice for your Bonita Living Application development and deployment.
It is composed of two parts:
The BCD add-on is powered by [Docker containerization solution](https://www.docker.com/) and [Ansible automation framework](https://www.ansible.com/). It is composed of two parts:
* First, a solution for **provisioning** of a Bonita stack on cloud or on-premises hosts
* Second, a framework for **continuous delivery** of Living Applications
The BCD add-on is compatible with [Amazon AWS cloud platform](https://aws.amazon.com/), on premises servers and local virtual machines via [Vagrant](https://www.vagrantup.com/).
It is powered by [Docker containerization solution](https://www.docker.com/) and [Ansible automation framework](https://www.ansible.com/).
* First, a solution for **Provisioning** of a Bonita stack on cloud or on-premises hosts.
BCD lets you deploy Bonita on existing servers using [Docker](https://www.docker.com/what-container) containers. Furthermore, when used with [Amazon Web Services (AWS) cloud platform](https://aws.amazon.com/), BCD enables you to create and delete [AWS EC2 instances](https://aws.amazon.com/ec2/) automatically.
* Second, a framework for **Continuous Delivery** of Living Applications.
BCD lets you build a Living Application repository and deploy the generated artifacts from the command line.
::: warning
It is highly recommended to have a clear understanding of [Docker essential concepts](https://docs.docker.com/engine/docker-overview/) prior to reading this documentation.
......@@ -82,8 +81,8 @@ Here is an overview of how BCD drives the provisioning of a Bonita stack.
![BCD Architecture Overview](images/bonita_platform_stack.png "BCD Architecture Overview")
* A **Host** can be a AWS EC2 instance or an on-premises server.
* A **Host** can be a AWS EC2 instance or an existing server running on-premises or on another cloud provider.
* The control workstation bind mounts some essential files with the controller container including:
* `~/bonita-continuous-delivery` - used as a working directory for BCD CLI known as the `BCD_HOME` directory
* `~/.ssh/private_key` - used to allow SSH access to target hosts
* `~/.boto` - credential to your AWS account (if any)
* `~/.boto` - credential to your AWS account (when applicable)
......@@ -14,9 +14,9 @@ These are general variables used while provisioning your platform.
| Name | Mandatory | Default | Description | Sample |
|--------------------------|-----------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|
| bcd_provider | Y | - | Infrastructure provider. Choose between `aws` and `on-premises`. With `aws` provider, BCD may create and destroy EC2 instances of the Bonita stack. | aws |
| bcd_provider | Y | - | Infrastructure provider. Choose between `aws` and `static_inventory`. With `aws` provider, BCD may create and destroy EC2 instances of the Bonita stack. | aws |
| bcd_stack_id | Y | - | Bonita stack identifier used to group machines by stack membership. For AWS deployments the characters allowed are limited to letters, numbers and underscore. | uswest2_test |
| bcd_inventory | N | - | Ansible inventory path required when `bcd_provider` is `on-premises`. Example on-premises inventories are provided in the `ansible/inventory/vagrant` directory. | ansible/inventory/vagrant/1-machine/inventory |
| bcd_inventory | N | - | Ansible inventory path required when `bcd_provider` is `static_inventory`. Example static inventories are provided in the `ansible/inventory/vagrant` directory. | ansible/inventory/vagrant/1-machine/inventory |
| bonita_on_single_host | N | false | Set to `True` when all containers of the Bonita stack is deployed on a single host. | true |
| configuration | Y | - | Configuration filename used to group variables for common deployment types. The corresponding YAML file must exist in the `ansible/vars` directory. | aws_vars |
| ansible_ssh_user | N | ubuntu | SSH user used to connect to target hosts. | ubuntu |
......
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