john/runtimeterror
1
0
Fork 0
mirror of https://github.com/jbowdre/runtimeterror.git synced 2024-11-21 22:42:19 +00:00
Code Issues Projects Releases Packages Wiki Activity

shorten iaac tag

Browse source
This commit is contained in:
John Bowdre 2023-08-22 19:39:27 -05:00
parent 89436478f6
commit 605de3463f
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/posts/create-vms-chromebook-hashicorp-vagrant/index.md
View file

@ -19,7 +19,7 @@ tags:
- linux - linux
- chromeos - chromeos
- homelab - homelab
- infrastructure-as-code - iaac
comment: true # Disable comment if false. comment: true # Disable comment if false.
--- ---
I've lately been trying to do more with [Salt](https://saltproject.io/) at work, but I'm still very much a novice with that tool. I thought it would be great to have a nice little portable lab environment where I could deploy a few lightweight VMs and practice managing them with Salt - without impacting any systems that are actually being used for anything. Along the way, I figured I'd leverage [HashiCorp Vagrant](https://www.vagrantup.com/) to create and manage the VMs, which would provide a declarative way to define what the VMs should look like. The VM (or even groups of VMs) would be specified in a single file, and I'd bypass all the tedious steps of creating the virtual hardware, attaching the installation media, installing the OS, and performing the initial configuration. Vagrant will help me build up, destroy, and redeploy a development environment in a simple and repeatable way. I've lately been trying to do more with [Salt](https://saltproject.io/) at work, but I'm still very much a novice with that tool. I thought it would be great to have a nice little portable lab environment where I could deploy a few lightweight VMs and practice managing them with Salt - without impacting any systems that are actually being used for anything. Along the way, I figured I'd leverage [HashiCorp Vagrant](https://www.vagrantup.com/) to create and manage the VMs, which would provide a declarative way to define what the VMs should look like. The VM (or even groups of VMs) would be specified in a single file, and I'd bypass all the tedious steps of creating the virtual hardware, attaching the installation media, installing the OS, and performing the initial configuration. Vagrant will help me build up, destroy, and redeploy a development environment in a simple and repeatable way.

2
content/posts/k8s-on-vsphere-node-template-with-packer/index.md
View file

@ -22,7 +22,7 @@ tags:
- automation - automation
- kubernetes - kubernetes
- containers - containers
- infrastructure-as-code - iaac
- packer - packer
comment: true # Disable comment if false. comment: true # Disable comment if false.
--- ---