Administering Moves
The entities that need to be administered for moves are listed below.
- Repositories
- Environments
- Stacks
- Container Types
- Containers
- Applications
In general you should set entitities up in the order that they appear above. The entities are described in detail below.
Environments
Environments are really just a lookup that identifies the function of containers within a stack. The standard environments are 'Production', 'QA', and 'Development'. These are already set up when Moves is deployed, so they will not need to be changed. However, we allow creation of new future environments (for example 'Continuous Integration' or 'Staging').
Stacks
A Stack is simply a grouping of Containers by Environment. Stacks allow Moves to answer the question 'What is the container for Application 'X' in Environment 'Y'. Once you create a Stack, you can add containers to it for each environment. When we subsequently configure an application, we will tell it what Stack is associated with that application. (So, for example, the application 'OGS Application' might reference 'OGS Stack'. 'OGS Stack' references containers for 'Production', 'QA', and 'Development'). By looking at these relationships, Moves knows which container to deploy to when asked to deploy to a particular environment.
Currently, the approach is to set up a stack for each application. Moves will allow
(This is a business rule, Moves will allow you to associate multiple