I wake up everyday committed to not doing things the same old way. That is why my title has that funny word ‘Automation’ in it. I am tasked with finding a way to make what is fragile, expensive, risky, and complex; easier to manage. While most of what I am working on at VMware is not ready for the light of day. There are some things that have come out of our work that would have a greater benefit being in the public space. If you are even an infrequent reader of this blog (which given my posts lately, is everyone) you know that I am a huge fan of PuppetLabs. More than that I am a huge fan of automation using DevOps-style toolsets enabled by community development. Right now I belong to an amazing team of crazy talented engineers. I rarely go a week without seeing something that makes me wish I was capable of doing a backflip. I am proud to announce that today some of that magic is now being put in a place for everyone. Today VMware and PuppetLabs are releasing the first set of modules for managing VMware environments. This brings a bunch of new features for the first time: Management for the vCenter Appliance /w Complete initialization – Just point as a VM that was deployed from the OVF and it will standup vCenter. Datacenter and Cluster configuration – HA, DRS, and more. The one caveat being EVC (but coming soon) ESXi Host – [...]
I mentioned in a slightly important recent post that Razor, the new cloud provisioning tool for bare & virtual metal, has a full RESTful API. Now I back that up with some documentation. Freshly added to the Razor Wiki on github is a overview of the Razor API. This includes examples on the JSON format and code samples for Adding, Removing, Updating, and Getting Razor configuration. And I took the time to provide code samples for each section in Ruby, Perl, Python, Java, C# and PowerShell (for my PS buddies, you know who you are). Go read it here : Razor API Overview This is the tip of the spear and there will be more documents on API elements for each Razor Slice. The Razor project is in beta and so the API may change as things move forward. Also, since this is a community project. If you have ideas or code that will improve anything please fork and submit a pull request. Feedback & comments appreciated. .nick
I am very prone to drifting off into thoughts about patterns in real life and how they correlate to things I deal with in my work life. I am fascinated by the thought of the constantly blurring line between ourselves and technology. It is really amazing to think about how social and mobile technologies have changed they way we work, communicate, and relax. I am just as guilty as the next guy of constantly tweeting during my vacation, contacting someone through Facebook only, or the fact that I have not written an actual letter in over ten years. It is out of this day-dreaming that I often start thinking about current cloud designs and how I would change them. In my mind both public and private cloud have several core demands that have been around for a while and are an essential part of expectations in any computing utility. A simple list of these would be things like being cost effective, performant, reliable, secure, and scalable. I could spend a large amount of time defining the rules about what makes a good “cloud”. But instead I will move forward with the assumption that a cloud service provides the same or better relative utility while being cost effective to the consumer. You can find a great many blogs and personalities out there that do a much better job of defining a robust cloud service offering. My thoughts our more focus on how that actually happens.