Page History
...
Environments
The minimum should be:
| Gliffy Diagramdrawio | ||||
|---|---|---|---|---|
|
Even better:
| Gliffy Diagramdrawio | ||||
|---|---|---|---|---|
|
Creating the recipe and doing deployment
Seeing beside the number og levels of environments on our platform, we do have the oppertunity to improve our recipe through the environments from Development to Production, and with todays techonologies for virtualizing like VMware or snapshotting filesystems (like ZFS) within a short timeframe - we can repeat and improve the recipe several times, even within each environment:
| Gliffy Diagramdrawio | ||||
|---|---|---|---|---|
|
From recipe to SOP
A recipe in typically going forward from A to B, it does not (always) imply the thoughts of getting back to the base, besides rolling back to a snapshot.
...
So final step is to make the SOP:
| Gliffy Diagramdrawio | ||||
|---|---|---|---|---|
|
Divide and conquer
The Divide and conquer principle is crucial for good Changes and SOPs - as opposite to havin a big Change with many steps and types of implementation (Application, Firewall, Database, OS), You should divide the Change into smaller Changes that are independant and/or sequentiel to be done separately. This also means that a rollback of a Change is not highly critical for the complete scope of the Changes.