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.
Hi All! I’ve been back from VMworld for a little over a week now, and I’m way past due on doing a “final thoughts” post around the cool technology and sessions we encountered. For now though, I’ll stick to being selfish and just posting back my sessions. William Lam at VirtuallyGhetto managed to pull together all the view URLs as direct links. You can view the full list here but I’ve included mine below.
Hi All! My session is done! I wanted to go ahead and drop this content out into the “space” so you guys could pull it down for testing. Attached I have the following items. vRealize Orchestrator Actions for Costing XaaS Deployment Workflow PowerNSX Powershell script for staging my NSX Distributed Firewall Rules (Creating Sections, Creating Rules, Basic Micro Segmentation) The workflows were added to a package and deployed so you can import the package directly.
Hey All! Now that I’ve lost all my money playing craps, which I finally know how to do, I have some time to pop on here and drop a heads up about a session I’m really excited for tomorrow (today, ugh, mornings going to come early…) Stop by NET7956 and check out VMware’s Ray Budavari and Francesco Vigo from the Network and Security Business Unit talk about ”vRealize Automation and NSX Design Best Practices”.
I wrote a blog post a few weeks back outlining my personal #VMWorld2016 session “How PG&E is Automating Secure Environments Using NSX, vRealize Automation, and vRealize Orchestrator”. What I didn’t mention is that I’m actually on 2 other Sessions during my VMWorld Stay. These sessions are “Panel” sessions with some great people. I’m incredibly honored and excited to have the opportunity to talk more about what I’ve learned over the past few years working in the Private Cloud and NSX space, as well as what PG&E is doing!
Partnering NSX with vRealize Automation creates some really intriguing possibilities when you look at taking tasks that a 3rd tier engineer would typically do, and being able to create a workflow that places a tight enough box around the task that a 1st or 2nd tier worker can complete the same task, in less time. This free’s up your 3rd tier engineers to focus on the real complex tasks.
Introduction I’ve fully bought into the value of leveraging XaaS (Anything as a Service) for a high number of catalog items in your vRealize Automation environment. So much so in fact, that I’m doing a a session on it at VMWorld 2016! This presentation is primarily about using XaaS to deploy systems, instead of the native IAAS “modules” already boxed in vRealize Automation. One thing I tend to do a lot of is build large lists in vRA for various reasons.