homelab/docs/ADR/001-Development-environment.md

# 001  Development environment

## Status

Accepted

## Context

we need to create a virtual cluster to do test without impact on production.

### Virtualisation or Container

Virtualisation provide better isolation but must ressource are needed.  
Container able to create more item without consum as resource than virtual machine.

### Creation Wrapper

Vagrant is good top manage virtual machine but not a lot of LXC box availlable, Vagant van be use with other configuration manager than ansible.
Molecule can manage molecule with plugins molecule-LXD. molecule is ansible exclusive solution

## Decision

we will use container instead VM for the resource consumption avantage.

Molecule wrapper will be use  because all our configuration is already provide by ansible and we can have a better choise of container with molecule than vagrant.

25/08/2023

some issue are meet with lxc (share kernel, privilege, plugin not maintain)
I have increase RAM on my computer so I can switch to virtual machine for the dev env
instead to build vagrant VM in a molecule playbooke we only use a vagrant file to avoid toi many overlay  to maintain.

## Consequences

migrate molecule provissioning on dedicated vagrant file
modify docs 2022-11-01 09:49:56 +00:00			`# 001 Development environment`
add dev-environement ADR 2022-11-01 09:45:21 +00:00
			`## Status`

			`Accepted`

			`## Context`

style: lint markdown 2022-11-29 21:08:34 +00:00			`we need to create a virtual cluster to do test without impact on production.`
add dev-environement ADR 2022-11-01 09:45:21 +00:00
			`### Virtualisation or Container`

			`Virtualisation provide better isolation but must ressource are needed.`
			`Container able to create more item without consum as resource than virtual machine.`

			`### Creation Wrapper`

			`Vagrant is good top manage virtual machine but not a lot of LXC box availlable, Vagant van be use with other configuration manager than ansible.`
			`Molecule can manage molecule with plugins molecule-LXD. molecule is ansible exclusive solution`

			`## Decision`

			`we will use container instead VM for the resource consumption avantage.`

			`Molecule wrapper will be use because all our configuration is already provide by ansible and we can have a better choise of container with molecule than vagrant.`

docs: add vagrant docs 2023-08-25 12:12:22 +00:00			`25/08/2023`

			`some issue are meet with lxc (share kernel, privilege, plugin not maintain)`
			`I have increase RAM on my computer so I can switch to virtual machine for the dev env`
			`instead to build vagrant VM in a molecule playbooke we only use a vagrant file to avoid toi many overlay to maintain.`

add dev-environement ADR 2022-11-01 09:45:21 +00:00			`## Consequences`

docs: add vagrant docs 2023-08-25 12:12:22 +00:00			`migrate molecule provissioning on dedicated vagrant file`