Commit d4605cdb authored by jeremy's avatar jeremy

update upgrade procedure for 3.0

parent ccbeac04
......@@ -6,7 +6,7 @@ This page explains how to upgrade your version of BCD.
Each of the versions follow the MAJOR.MINOR.PATCH format.
We have split this documentation in order to describe the differences for a major upgrade (1.0.x to 2.1.y) or a minor (2.0.x to 2.1.y).
We have split this documentation in order to describe the differences between upgrades.
We will focus on :
- scenarios : indeed you may want to keep your existing scenarios. It will allow you to recreate the same kind of stack or manipulate an existing one (deploy, undeploy, destroy).
......@@ -18,55 +18,37 @@ So if you want to be able to manage an existing stack (i.e. a stack already depl
## How it works
### From a 1.0.x towards a 2.1.y
### From a 1.0.x towards a ${varVersion}.y
#### Scenarios
You will first need to copy the files
```
cp bonita-continuous-delivery_1.0.5/scenarios/*.yml bonita-continuous-delivery_2.1.0/scenarios/
```
Then you will have to check `Breaking changes` section into the [release notes](release_notes.md). Indeed you may want to override `bonita_http_api` default value that has changed. Or for deployments that do not use `aws` for `bcd_provider` you will need to replace `on-premises` by `static_inventory`.
#### Terraform
You will need first to create a directory named like your stack inside Terraform directory and then copy into it the corresponding tfstate file.
```
mkdir bonita-continuous-delivery_2.1.0/terraform/your_stack_name
cp bonita-continuous-delivery_1.0.5/terraform/your_stack_name.tfstate bonita-continuous-delivery_2.1.0/terraform/your_stack_name/your_stack_name.tfstate
```
#### BCD controller
As is described into the "Installation guide" from the [Getting started](getting_started.md) you will need to load the last version of `bcd-controller_<version>.tar.zip Docker image.
#### Vagrant
The operating system of Vagrant VMs has been changed from Ubuntu Trusty to Xenial.
Please follow the previous documentation describing the [upgrade from 1.0 toward 2.1](https://documentation.bonitasoft.com/bcd/2.1/upgrade_bcd). Then follow the instructions in the next section.
As the controller access to them over the network it's not necessary to move them on the filesystem.
### From a 2.0.x towards a 2.1.y
### From a 2.1.x towards a ${varVersion}.y
#### Scenarios
You just need to copy the files.
You will first need to copy the files
```
cp bonita-continuous-delivery_2.0.0/scenarios/*.yml bonita-continuous-delivery_2.1.0/scenarios/
cp bonita-continuous-delivery_2.1.0/scenarios/*.yml bonita-continuous-delivery_${varVersion}.0/scenarios/
```
Then you will have to check `Breaking changes` section into the [release notes](release_notes.md). Indeed you will have to had the new parameters `bcd_registry_user` and `bcd_registry_password` in order to retrieves the BCD dependencies from a private docker registry.
#### Terraform
Copy the directory corresponding to your stack.
```
cp -r bonita-continuous-delivery_2.0.0/terraform/your_stack_name bonita-continuous-delivery_2.1.0/terraform/
cp -r bonita-continuous-delivery_2.1.0/terraform/your_stack_name bonita-continuous-delivery_${varVersion}.0/terraform/
```
#### BCD controller
As is described into the "Installation guide" from the [Getting started](getting_started.md) you will need to load the last version of `bcd-controller_<version>.tar.zip Docker image.
You can also directly use the private Docker registry to retrive the latest image.
```
docker login quay.io
Username: myusername
Password: mypassword
docker pull quay.io/bonitasoft/bcd-controller
```
#### Vagrant
......@@ -74,8 +56,8 @@ As the controller access to them over the network it's not necessary to move the
But if you plan to cleanup the old directory you can moved the vagrant data located inside `1-machine` or `2-machines` directories by copying the `.vagrant` subdirectories.
```
cp -r bonita-continuous-delivery_2.0.0/vagrant/1-machine/.vagrant bonita-continuous-delivery_2.1.0/vagrant/1-machine/
cp -r bonita-continuous-delivery_2.0.0/vagrant/2-machines/.vagrant bonita-continuous-delivery_2.1.0/vagrant/2-machines/
cp -r bonita-continuous-delivery_2.1.0/vagrant/1-machine/.vagrant bonita-continuous-delivery_${varVersion}.0/vagrant/1-machine/
cp -r bonita-continuous-delivery_2.1.0/vagrant/2-machines/.vagrant bonita-continuous-delivery_${varVersion}.0/vagrant/2-machines/
```
#### Living Application repositories
......@@ -84,5 +66,5 @@ Move the directories where you have cloned your repositories.
For example :
```
cp -r bonita-continuous-delivery_2.0.0/bonita-vacation-management-example bonita-continuous-delivery_2.1.0/bonita-vacation-management-example
cp -r bonita-continuous-delivery_2.1.0/bonita-vacation-management-example bonita-continuous-delivery_${varVersion}.0/bonita-vacation-management-example
```
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