🌐 A structure for maintaining common Vagrant boxes in the HashiCorp Atlas.
This project is designed to take common systems, define them, and then track a workflow of performing system updates and publishing iterative versions to a centralized location. This alleviates the repetitive, and slow, process of bringing a bare machine image to an updated state.
New Vagrant boxes maintained by atlas-vagrant start with a bare image from a reputable source. Systems such as Windows Server, require a specific manual order of updates followed by running Windows Update with a series of reboots in-between to successfully update to a current update state. As you can imagine, this is a large time drain, with no benefit of automating with every new machine provision - atlas-vagrant is meant to eliminate this.
devopsgroup.io infrastructure experts do the research, work, and publishing of the atlas-vagrant boxes. Leaving you with a bare, yet updated, Vagrant box that is ready for your implementation.
| Platform | System | Vagrant Box | Latest Update Series | Origin |
|---|---|---|---|---|
| Windows | Windows Server 2012 R2 Standard 64-bit | devopsgroup-io/windows_server-2012r2-standard-amd64-nocm |
2016 October | OpenTable |
vagrant up <machine>- Provider guest addition updates performed
- System updates performed
- System cleanup performed
vagrant package <machine>- Release the Vagrant Box per Creating a New Vagrant Box