From 8e30abd4286fe90689a6dc63fd6e7d1d57105d2b Mon Sep 17 00:00:00 2001 From: vincent Date: Fri, 25 Aug 2023 14:12:22 +0200 Subject: [PATCH] docs: add vagrant docs --- README.md | 14 +++++++++++++- docs/ADR/001-Development-environment.md | 8 +++++++- 2 files changed, 20 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index b8899aa..53b2ced 100644 --- a/README.md +++ b/README.md @@ -2,12 +2,24 @@ This repository contain my homelab Infrastructure As Code -this Homelab is build over Hashicorp software: +this Homelab is build over Hashicorp software stack: - Nomad - Consul - Vault +## Dev + +dev stack is build over vagrant box with libvirt provider + +curently need to have vault and ldap production up to be correctly provision + +to launch dev stack provissionning : + +```sh +make create-dev +``` + ## Rebuild to rebuild from scratch ansible need a vault server up and unseal diff --git a/docs/ADR/001-Development-environment.md b/docs/ADR/001-Development-environment.md index 834687d..4ce7342 100644 --- a/docs/ADR/001-Development-environment.md +++ b/docs/ADR/001-Development-environment.md @@ -24,6 +24,12 @@ 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 -Need to create dev env other an LXD server. +migrate molecule provissioning on dedicated vagrant file