Summary William Lam and I are doing a Hackathon Training class on Integrating VMware API’s and Amazon Echo - Session ID is VMTN6721U. It runs Monday Night 6:30pm-8pm. A preview of the content is below; along with the FIRST screenshot of the content. The class will be interactive, fun, with minimal slideware focusing on Hands on work instead Primarily taught in Python, we will leverage Flask, Flask-Ask, and VMware’s REST API’s to build some cool voice integrations with the platform We will also touch on leveraging ClarityUI and containers Afterwards, I’m leading a hackathon team named The Humble Brackets where we will target expanding the integration in some really crazy ways.
The Short Version My blog has been migrated off of Wordpress and onto AWS S3 I’m using AWS CodePipeline and CodeBuild to automate the deployment process as I commit posts to a private Github repository AWS CloudFront is running as a CDN which is providing a crazy fast cache as well as redundancy across the US The cost is estimated at less than $1 a month for the entire solution.
Hey All, Quick update video! We’re starting to clean up the file content for release. Very soon the github repo will be opened up and made available for all to consume. In the meantime, take a look at this video where I talk about changes to the authentication mechanisms, folder and file cleanup, and my favorite demo yet! Have a great fathers day to all the fathers out there; remember, nothing is as cool as being a good Dad!
Hey all! Quick update today around the project we’ve been working on around leveraging the Amazon Echo, Python, and VMware API’s to bring voice command capability to VMware management. 2 major changes to the platform to note Gideon now runs as a container instead of the python development interface, or running Apache with WSGI. The container drastically improves resource utilization, agility, and development speed. Management interface implemented using ClarityUI to match VMware products and services moving forward Early vSAN and VAMI API’s implemented New intents for provisioned memory, CPU, and appliance up time implemented Take a look at the video below to see a demonstration.
Start With the ending, a demo! If a picture is worth a thousand words; a video is worth volumes! This is an incredibly long blog post; for those of you that wanted to just see it in action - Here’s a demo video! For those of you that want to get into the details and figure out “how” we get here; read on after the video! If you’re interested in the code for this post, check out my GitHub repository that has this project in it.
Behold! The folks at Cloud Management Business Unit (CMBU) within VMware have provided a gift! vRealize Automation 7.3 is now Generally Available (GA)! It’s no secret that my love of vRealize Automation is one of the things that made working at VMware a bit more exciting. I truly believe in the product; and as a customer I watched as feature requests came from the drawing board to be a reality (some faster than others).
Update 4/26: I’ve revised the blog post to no longer connect to the appliance via SSH to deploy the VIC host; instead providing instructions for installing the Docker Toolkit on Windows 10 and leveraging it locally. This is the “right” way to do it. Using the appliance works; but is not recommended. In the original blog post; we SSH’d into the VIC appliance to perform the following tasks (deploy VIC Host, call Docker API, etc…).
It’s funny how life changes. I’m 2 months into my Senior Systems Engineer role at VMware, representing SLED West out of California. At my core, I believe in growth. That’s why I ended up here. I want to grow as a technologist, outside of my comfort zone. I wanted to be a part of a company who’s products I believed in, but more importantly, who’s culture was a place I felt like I fit in at.
I’ve had a few goals for learning this year. One of them has been to crack open the scripting world of Python. Knowing that the current version’s of vSphere have an incredible Python based API; but not being skilled enough to use it has been…challenging. Ultimately; I’ve wanted to utilize the API to create a number of detailed infrastructure level reports. I’ve created workarounds to complete these goals using vRealize Orchestrator - creating inserts into a SQL database that dump machine facts via custom properties.
I’ve completed rethought the configuration of my environment. It’s far from best practice at this point - but it’s getting the job done. Ultimately my issue came down to the fact that best practice is obliterating my power bill. Running 4+ ESXi hosts on server grade hardware is just too expensive to keep cool and operate in Sacramento, California. I’ve moved to leveraging a larger “Core” host inside the house where I can keep it cool, and a distributed configuration remotely (in the garage) running on my former server hardware.