deployment

GitOps is an idea that entire systems are declaratively specified in code, versioned in Git, and that repositories are a team’s source of truth. There’s some plumbing required that takes the specified code and reconciles the system to that specification. In my experience, GitOps can be taken way too far and end up becoming a hassle. This post discusses some drawbacks of GitOps that I’ve encountered. First: GitOps isn’t awful Before I get into GitOps drawbacks, let me be clear: GitOps-y approaches aren’t always bad....

Our chargeback policy for virtual machines was not clearly defined. To encourage adoption, the provisioning fee for a virtual machine was $500 regardless of system requirements. In lieu of a host being added and other considerable investments being made hardware, the chargeback policy needed to be revised. Virtual Machines within our matured Virtual Infrastructure cost more to provide but add a considerable amount of value. After a bit of reading at vmMBA and watching BM15 Managing Chargeback with VMware Infrastructure 3 from VMworld 2007 we decided to go with a tiered chargeback method....

One of the things I have to do as a Virtual Infrastructure Administrator is evangelize value added with virtual machines. What are my stakeholders going to get out of this? Where’s the value added? Why should we use a virtual machines instead of physical machines? Here’s my explanation of some advantages and value added using VMware Virtual Infrastructure 3 from a system deployment standpoint. This post will show a “before and after” view of system deployment....