Sunday OTW and @ VMworld 2019

The Trip

Sitting here in a quiet terminal is slightly surreal. I’m not used to silence or the singular sound of roller bags one at a time going through. Its peaceful… too peaceful. I got here too early.

I’m a stickler for rules. I don’t know why, but if I’m told to be at the airport two hours early I don’t ask questions I just do. However, since waking up at 3AM and being unable to get back to sleep, getting to this point has been paramount. I should explain that the last time I flew out of DFW Airport I was late for my flight. I’m more a Love field guy. Suffice it to say I had a lot of anxiety about today.

One thing people don’t tell you about much is time management with VMworld. Oh sure the #1 thing people say to prepare you is “COMFY SHOES” its almost something on a t-shirt or a bumper sticker, but time management is paramount. Which is also something I’m not great with.

Lets see, I fly out and arrive a little after 11, and have 2 hours before my first session it get to the hotel, check-in, register at VMworld, and hopefully get something to eat along the way. Lots of places for things to go wrong. But one place to go right. to inform you, dear reader, that flying out on Saturday, isn’t a bad way to do it. Sure, its one extra night, and meals, but the free thought and peace of knowing you’re not crunched is definitely worth it.

Lets see If I get to Run Kubernetes on VMware. Which is paramount to my going to VMworld, since I’m being a deciding factor on where we should run out Kube cluster(AWS, Azure, on-prem, IBM, etc.)

TIM DAVIS WHAT UP! I normally catch up on twitter when I can, and the airport definitely affords that. While scrolling and responding back and forth in twitter I found out my friend Tim Davis was at the same airport on the same flight, but was chilling in the admirals lounge! He got me in so we could catch up and prep some more for the oncoming VMworld enjoyment. Thanks TIM!

Not much to state about the flight, it wa pretty non-eventful. I don’t normally fly American, so it was nice to see all the great stuff that they had. What I get Movies?! cool…

Run Kubernetes on VMware

@Boskey, and @morellatosimone

Well as a first session goes, this is impressive. A full house made right at the kickoff. Really excited. As this is a Workshop there isn’t much to discuss or talk about. This will supposedly be an intro into kubernetes and a great warm up for VMworld. Here.We.Go…

  • Definition of Devops in this session is “Improving the pipeline to deploy code.”
  • its time to abstract the Operating system. (Heck yes it is. This is the main response to containers in our environment)
  • Kubernetes is a container orchestration layer that maintains desired state, distribute containerized workloads, decouple app from infrastructure.
  • Focusing on the removal of the App from the Infrastructure, normally when building an application you need the binary, configs, resources, storage, replication, load balancer(if needed), security(ACL) and Upgrades(CI/CD)
  • The same app in Kubernetes speak turns int pods, Secrets, deployment, PV(Persistant Volume) Claims, Replica Sets, services, Network Policies, Labels, and Services.JKBk72RNS2a3YFXCDX8MSw
  • The infrastructure layer would be either vSphere, AWS, GCP, or Azure.
  • Kubernetes Workloads: Pods, Jobs, Cron Jobs, Daemon Sets, Deployments, Replica Sets, Stateful Sets, CRDs8uvwa8ErStW0k2kkSgMRQw
  • p0nWwEMKSHGOwE2cOM3%TA
  • XEYikXi7QV6GDLpSZhtdOQ
  • Normally Kubernetes is stateless applications, but here we define StatefulSet in action:
  • v4mS2YoUSd2S1sKtyj7Tow
  • LabelsdI50KvjtSv2ePVHILw2fdg.jpg
  • Deployments, Replica Sets and ServiceIfL43QceSiyf8it7KpbLLw
  • Map of Kubernetes and Load balancingxY7LcSO4SlaM+glqFXuFcA
  • Map of PODS(How it looks)NkHwQ9GkTkKBHM9gmvRTTQ
  • Now the good stuff. Persistent Volumes. This is definitely a confusing discussion and caused a lot of questions. Here are the slides to hopefully show what it looks like.PoXPDMVtTcmHXg3ttmaj3AKXUzbgnPQpCjcUzfH%dgbQ
  • Slide on Config Maps/Secrets. This is something that I don’t really know enough about and need to review but hey, thats what Google is for right?APqiEQZiF5arlBuFBPA
  • Good summary of the SessionfOisSMr7TieT3Hb5%fVNow
  • Here is the link to alot of the PODS. Unfortunately, this requires PKS deployed and a pod available. Perhaps you can spin up a PKS HOL and have time to go through this as the YAMLs and information is all in a public Github.
  • Labs here:

The main difficulty for me was getting the VKE and Kubernetes cli in the /usr/bin. Its worth noting that if you have El Capitan installed on your Macbook /usr/bin is now a system folder and you can’t move or copy files there. I got around this by putting it in /usr/local/bin and then setting the PATH variable there.

All in All an amazing session. Give @Boskey, and @morellatosimone a follow!

Opening the Solutions Exchange

HASHICORP IS HERE! Getting face to face with people for the application is probably as good if not better than any session at VMworld. I only did about 4 to 5 booths, but was able to hit up Hashicorp, Git, Puppet, and cloudbolt. So many more vendors to talk to, with the bigger companies like Cohesity, Rubrik, Dell, AWS, GCP, Pure, etc.

Obviously these are great conversations here but I’m extending an already extended blog, so lets just call it a great time had by all 🙂


With Jet Lag and everything I didn’t make any parties to talk about. I tried to get to the VMUG and the VMunderground, but didn’t make either. So sad… Now to bed… I’m really tired…

Automation: Getting Started with vRealize Automation (Part 3)

So at this point you should have the following:

  1. Endpoint connection with your VCenter
  2. Fabric Group allowing the resources to be granted
  3. Business Groups allowing specific group of users access to..
  4. Reservations setup to grant resources to business groups
  5. Reservation policies to allow specific Reservations to be called
  6. Network Policy to allow specific IP pools to be pulled/pushed from
  7. Active directory policy to place computer objects in specific OUs

You should have All this from the following blogs:

It sounds insane to say it but now that you have all these building blocks completed. Now you can setup your blueprints and start your deployments.

The Design

Before you start your blueprint plot out on paper or your mind or whatever how you want the end goal of the deployment. Do you want a SAAS solution tacked on? Are you using Enterprise vRA or Advanced? All of these questions lead up to how you deploy your instances. For this purpose we’ll assume the following

  1. You read my blog, and you did the stuff
  2. You use Customization specifications for vSphere deployments
  3. You utilize Templates for your deployment

With the following assumed I’m just going to walk through a basic setup for a basic deployment. The goal here isn’t to get fancy. Its really just to get your feet wet so that the next steps will be to custom build the server from there on.

The Canvas

Once your logged back into vRA you will go to design, and then click the green + for a new blueprint. Here is the screen you will see:Screen Shot 2019-07-19 at 10.53.29 PM

So this is pretty basic,

  • Name is the name of the blueprint your creating
  • Id is the name of the blueprint as well, but no spaces
  • Description is pretty much what it is
  • Deployment limit, This limits the number of the deployments per request. This will allow users to build multiples of the same machine, However, you will need to have your naming statically set.
  • Lease Days – For this you can set the minimum of a lease, at the end of that lease if the user does not extend within the last two days it’ll shut down the machine and then the user can extend. If he doesn’t extend it will just stay shutdown. Once it gets to Archive day(s) it will shutdown the machine and delete it(So be careful). The deployment limit lease and archive are optional and do not need to be set.

Now lets look at the design canvas:Screen Shot 2019-07-19 at 11.14.51 PM

On the left you see your different categories and the assets you can deploy, From machines, Software components(ONLY IN ENTERPRISE LICENSE. Advanced will still see the option but not have the ability to change add one). Blueprints for nested deployment, Networks, XAAS, Containers, Config Management, and Other Components. These are all fun and great things to work with, but for this we’re going to keep it simple.

  • Machine Type – For now drag a VMware machine type onto the canvas and have that stick. This consists of the majority of properties, and is the central hub for the additional assets. Once you add the machine type into the canvas it’ll open up alot of other properties that we’ll get into.
  • Software Components – This is setup in Enterprise Licensed vRA and then can be attached to machine types in the canvas.
  • Blueprints – If you want to place an already setup blueprint in the canvas and attach multiple pre-built machines to a deployment.
  • Network & Security – Here is where a lot of you NSX automatons come in. For now we are just going to use the external network and connect it to our network profile.
  • Xaas – This attaches an automation for basically anything to a machine deployment
  • Containers – Deploys a container app into a cluster. However, there are pre-reqs there that are needed to be deployed properly.
  • Configuration Management – This deploys built in Ansible and Puppet workflows(I believe this started in 7.5 but perhaps 7.6)
  • Other Components – This is any other resource component or solution published for the deployment workflows


Instead of giving a written write-up on how to do this, I figured its WAY easier to just see some of the pros do this in a video. @virtualJad has some amazing stuff thats older but still useful to get your feet wet, and if you’ve followed this blog the pre-reqs should still be there:


Along with Videos, There are hands on labs that VMware uses to teach you how to create a deployment. Here are the labs:


I think these videos and HOL’s are a great way to pick up where this leaves off and get you going.

I hope this series has been a help to get you started using vRealize Automation.



The Positive Side of Failure

Disclaimer: This isn’t another Mental Health post. I’ll share that part of my story sometime later. This is going to be raw, so if you can’t read this, don’t. I am not looking for empathy or sympathy. These experiences brought me to where I am and I don’t resent them. I want this to be something that helps others know they can be better, and push themselves to find it. Even though the road is rough.

The first road

One thing people find strange about me is that I never intended to work with computers. The idea of IT work was something that sounded so tedious and horrible, that when I was 7 I knew it wasn’t something I wanted to do. No, 8 year old Nathan knew he was going to be a pastor, or a missionary but definitely something to do with the Gospel message of Good news. I taught Sunday school, lead children’s church as a teenager. Led worship once even, and while I was in college I was a youth minister for a small church. However, whatever religion, belief you are, you know that things don’t always turn out how you plan.

While I was in seminary our church went through a very rough time. So rough in fact that the pastor had lost the trust of the session. To those that know what that means its a pretty messed up place for all involved; the church, the session, and most importantly the pastor. The church voted to remove the pastor, a man who had been mentoring me in becoming a better version of myself behind the pulpit, and a strong help in my life.

This was rough, but then I was also flunking one of my classes. I talked to my teacher who told me,

“Just memorize this passage and I’ll pass you.”

Instead of taking the win, my reaction was, “Then why is this class mandatory?” The straw that broke the camels back was we were in seminary housing, and we were told we could have a cat. But when they found out we had one, they wanted us out. This lead to a perfect storm that taught me one thing. I was in the wrong place.

One thing that came out of it was my wife (who’s still married to me, don’t ask me how). Came home after another day of bringing home the $$ for the family, and found me in the middle of the living room, with all the pieces of my computer spread out. “What happened??”, I replied, “I found the noise in my computer, I KNEW it wasn’t the fan.” This led my patient wife to ask me later on, “So why don’t you work with computers??”

The second road

“So why don’t I?? Its always been a hobby. I’ve been ok with it from time to time, and for some reason my wife and others think I’m good at it… Nah, I’ll never be good at it.” 

This was my thinking after we moved out of seminary and into a house. I took a job as a barista at Starbucks over a job with Bomgar (which is now Beyond Trust). At the time we were living in Mississippi, and Bomgar headquarters was only 20 mins from my house. That nagging feeling stayed there. Especially when I couldn’t say what “DNS” stood for.

I worked as a Barista for about a year, and man I was good at it. I loved working with the people, and I REALLY loved my boss, Summer. She was a hard taskmaster but a good listener. She really helped me out once or twice at work. Some of the assistant managers didn’t take too kindly to me when I started, but I worked my way up, and moved to the only barista on the 6AM drive through (Which meant I took orders and made the drinks). Man I was good at that. It helped that I was good talking to people, after about 6 years in retail from selling toys, to books, and music.

As I was working at Starbucks my dad told me of one of his friends who needed a tech hand. I asked what was needed and he said, “Oh you just need to be able to image and re-image machines.” Thats childs play I though. I told my dad I’d be happy to look into that job all the while that voice was in the back of my head. “You can’t do IT… Its not your thing…” was the voice in my head. Arguably it was a jump. At this point I’ve only worked on my own computers and sold them at Circuit City(dating myself here). So I picked up the job.

Third Road

The interview process for this job was strange. I came to this mans house and gasped at how nice it was. I went to the front and rang the doorbell. After meeting his wife and son, I met the friend of my dad’s. He was a military man and I could tell from talking to him he was a strict man. After our discussion(which was over an hour), He told me I had the job and told me to start Monday. This wasn’t a problem as my manager at Starbucks was stellar and a friend from seminary. She let me off and I took the position.

Its worth mentioning this was my first time to touch a server. It didn’t help that it was a desktop server and not rails. In fact, I never touched a rail server through this job. I pushed updates, Ran CCcleaner and did random tasks. I basically did whatever his client asked me to do. I started to learn from them and him, but I was distracted. That voice never left. I never could break the idea that I could do well in this environment.

One thing I immediately realized was I had an issue with checklists, I had an astigmatism in my right eye that made me skip lines when I was reading, so I would miss steps.

I only worked for the man 3 months. Within the first 1.5 months we were at odds. I’d ask for help from him on the phone and he would talk me through things now and again, but one time I stayed on the phone after I said goodbye just out of tiredness and I heard the words,

“What an Idiot!”

To say my confidence was shattered at that job from then on is pretty easy to understand. I kept trying though. I became unable to think for myself, and leaned on him more which led him to get more angry at me. You see, he wanted me to ONLY do things his way, but my personality was more curious than that. If I had a document to follow, I’d still have questions about it.

In a troubleshooting session I called him and after working through some issues he said he would reach out to support. When I was back on the phone with him I was greeted by a friendly, “Good to meet you Nathan, let’s take a look.” So I began to talk through what was going on and what the issue was, after about 30 seconds, my boss interjected, “I’ve already told him the issue you don’t have to go into it.” I shook that off this time, because this time I thought I found the issue. I let him talk for a second then asked, “Well I think the problem is over in…” and was interrupted again,

“Nathan this is the guy who helped code the application. Your opinion is not needed or wanted, you can go home.”

So I did. I never heard what the issue was, and I asked. My boss never told me. It was a week later my boss said he believe my heart to not be in the job. A week after that I told him that I was going to quit. I’ll never forget his response.

Thats good Nathan, I think your a great artist. You should do guitar or choir or something in music but stay out of IT. You will never be successful in that field. You don’t have what it takes. I just don’t think you can comprehend it”

The artist statement was because I was a music minor in college. I played classical guitar and sang in the choir mostly. I also took a couple of classes here and there. The problem with going into music was I was in my mid 20s at the time and I knew I didn’t have the skills.

The pit stop

Calling the next couple years a pit stop is a generous statement. I literally had no idea what I was doing or where I was going. I took on odd jobs, played lots of video games.

That awesome Starbucks manager took me back, and even though she already had the staff to run the shop, she found a place for me. So I went back to Starbucks for another 6 months. That time was pretty critical for me because I started re-gaining some very needed confidence.

I began realizing that no matter what people said, I am good at things. I just don’t know what I should be doing.

My amazing wife continued to be my cheerleader, friend and hope each day. She took on some rough jobs to keep the bills paid, but she was just stellar through this whole process. She would come home and talk about the people at work and I would tell her how I played video games each day, and did some studying.

That studying was because I had an amazing cousin who spun up a Hyper-v cluster for me to utilize to learn Microsoft Active Directory and other computer issues. To be fair, I didn’t utilize it enough or appreciate the gift that he had created for me. My mind was in such a state that I just didn’t know what to do, and I needed a good kick to get me out of this funk.

The kick

During this time we had moved from Mississippi to Fort Worth, Texas. We were living in a house that my in-laws had and wanted to keep clean/kept up, instead of just being dormant. Well it was summer and we were told the house needed to be sold and we needed to find a new place. Also during this time, we were trying to sell the house in Mississippi that we bought. That house stayed on the market for over a year, and after swapping realtors we found out that we were asking well over what that house was worth. However, we got an offer and took it having to pull a 12k loan to get out of that house. Debt piling up and the fear of no roof over my head, the only thing I could do was go back into the job market. I went to a legitimate temp agency just to get something. Surprisingly, they said my skills are mostly fit for IT, and they place me at RadioShack as a graveyard shift tech for setting up new stores.

Its kinda funny how that 12$ an hour job was a godsend to us. My income had doubled and I thought, “This is ok for now till I find a better solution.”

The Road I’m On…

Working at RadioShack ended up being a great experience. The people I worked with were fun and hilarious, the bosses were nice (mostly), and some were even tough taskmasters. But one thing they all had that I didn’t know existed in IT, was resilience. Failure wasn’t the worst thing, nor was following documents. The worst thing you could do was to be lazy and complacent.

While I was there I learned a lot, but still thought I’d never be great at higher level IT. I didn’t even think this was IT. I just slung hardware at problems and never really dug into much. Then after the project was over they were going to cut the contractors. However, I had worked through the night and into the day shift and had grown a good relationship with that team and manager. They had even put me in the day phone queue for a while to help with calls. After all this my bosses boss came up to me and said,

“Stop working overtime! I’m not going to pay it if you can’t watch your hours!” That shook me for a second, then the dayshift manager (who wasn’t my manager) piped up and said,“He’s worth it”. Then his boss responded, “Well, HIRE him.”

The guy that said that probably had no idea, and still doesn’t know how big those three words were to me. For the first time, I had worth in the IT field. I was GOOD at it, at a professional level. Even though phone help is seen at a lower scale, to me it was still a “big boy job”.

RadioShack definitely had its hardships, but I built great relationships with people, learned a lot, and went from a phone tech, to a level 2 server admin, to a network operator. My next job was a graveyard tech at an Oil company. I worked graveyard for about a year, and then moved to the day shift doing data analysis with BMC Remedy, and then the VMware guy who was dealing with vRealize Automation asked me to code the automation for creating, adjusting, modifying tickets and the CMDB.

My issues with checklists, went away with automation, and I finally found my home. I’ve been working automation ever since pushing either DevOps code based solutions, or Gui based automation that will push one thing to the next without having to manually click buttons off a procedural checklist.

The Positive Side of Failure…

This may read very negatively, but I’m very glad for each step I took along the way. I love my wife and remember each day that she did for me, what I do for her now. I love that she can be what she wants and has that freedom. I push myself each day to learn and grow, but more importantly, I push myself to ‘fail’.

Out of my career I’ve learned that failure isn’t an option, it’s a part of life. It’s going to happen no matter what you do. It is how you respond to it that defines your success. It took me a long time to learn that lesson. I still know people who deal with failure incorrectly. They think if they fail, they will never be successful. I find that I’m successful, because I fail, and I’m not alone. Here are some quotes by some interesting people:

“Nothing in this world can take the place of persistence. Talent will not: nothing is more common than unsuccessful men with talent. Genius will not; unrewarded genius is almost a proverb. Education will not: the world is full of educated derelicts. Persistence and determination alone are omnipotent. ” – Calvin Coolidge

I have not failed. I’ve just found 10,000 ways that won’t work.  – Thomas A. Edison

As a kid, falling was embarrassing. As I got older, I got used to falling and picking myself back up. There’s not a sense of failure. It’s of disappointment. You train so hard to not make mistakes. When you do, you’re learning from that. How do I improve? How do I get better for the next time? Through every failure, there’s something to be learned. – Michelle Kwan

“Failures, repeated failures, are finger posts on the road to achievement. One fails forward toward success.” – C. S. Lewis

“Around here, however, we don’t look backwards for very long. We keep moving forward, opening up new doors and doing new things, because we’re curious … and curiosity keeps leading us down new paths.” – Walt Disney

Let these be the voices in your head, and each time you fall, remember that fall, accept what happens, take the noise from the fall out of your head, and move on. Each fall is teaching you something, learn from it. Michael J. Fox uses the word vacuum very well:

“There’s always failure. And there’s always disappointment. And there’s always loss. But the secret is learning from the loss, and realizing that none of those holes are vacuums.”  – Michael J. Fox

This hits home for me. That voice in my head so many years, was a vacuum, and these take multiple forms. You can let it be a boss, a job that you lost, a friends issues, etc. The challenge of life is to learn from these and move on. Because if you don’t they may suck you in and down a hole that takes entirely too long to get out.

If you made it this far, thanks for staying with me. This is a bit of my story telling how I made it to where I am. I’m not the most amazing person out there, and I don’t have the technical knowhow to know everything, but that’s the path I’m on. Wether I learn from failing or reading, or doing, everything is learning. I may fail in how I teach my kids, or how I fix up the shower, or anything. This is my perspective now in life.

“I will fail. I will fall. But I will learn the best that I can from it.”

Automation: Getting started with vRealize Automation (Part 1)

Acronyms used:

  1. vRA = VMware vRealize Automation
  2. vRO = VMware vRealize Orchestrator
  3. vROPS = VMware vRealize Operations

I was hit with a shocking realization this past week. During a conversation with a VMware representative about automation and the success that we have found within it, he stated, “You know we could sell the cloud suite license to ten customers and probably two of them would use automation, and maybe one would be successful.”

I bypassed this statement and just moved on for the next couple days, but then a friend asked me how to create a blueprint on how to get started with vRA. I spent a huge amount of my time scrounging the internet for blogs to tell me how to do one thing or another, which is one of the ways I have helped our company be successful. Because of blogs, I found the answers I was looking for. I lost sight of what this blog was suppose to accomplish, which is to help others start. So… Let’s start.

You’ve installed vRA… Now What?

So with a fresh install of vRA, you now have a shell. Nothing is being managed, no domain users are able to login, and no machines are able to be built. It’s kinda a pointless stubb when its first deployed and needs someone to start the setup. During the installation you will stipulate the administrator password. This is your first login. Once you’re in, the screen you’re met with is kinda bleak.

Once your logged in, go to the “Administration” tab and select “Tenants”. You should be met with your default tenant for vRA, so, select it. From here, select “Local Users” and add a new user (Most will just name this account “Admin”).

Screen Shot 2019-06-22 at 7.58.55 AM
Pay no heed to the 2nd “Administration” Tab to the right, you shouldn’t see this.

After the account is created, go to “Administrators” and add your new account as “Tenant Administrators”, and “IaaS Administrators”. Screen Shot 2019-06-22 at 7.46.59 AMThis will grant the needed access to start utilizing vRA. *BONUS POINTS*: you can configure your incoming and outgoing email servers here. Probably a good idea to do that too.

Fabric Groups are basically what allows resources to be consumed by vRA. It really doesn’t do anything until the Fabric Group is created. So lets do that… first thing to do is create your Fabric Group Endpoint(Basically what resources are to be consumed). Log Out of your “Administrator” account and log into the account you created above. Go to “Infrastructures -> Endpoints -> New ->vsphere”

Screen Shot 2019-06-22 at 7.16.23 AM

Now you will see the needed information to create your endpoint. Please note the examples that VMware gives you before you start typing. Many gung-ho automation enthusiasts have lost hair because they didn’t look first. TAKE NOTE** The name you input here, SHOULD MATCH the name you install as your vcenter agent during installation of vRA. If you have forgot that, you can go on the agent box and look at the service. Most will dupe the name of the agent with the service. If it’s not you will get a message “The Vsphere agent does not exist or may not be running“. The correct inputs and test connection should show:

Screen Shot 2019-06-22 at 7.23.28 AM

So click “OK”. Now that you have your endpoint we need to create a Fabric Group. On “Infrastructure -> Fabric Groups -> New” you should see your new vCenter ready to be managed:Screen Shot 2019-06-22 at 7.27.32 AM

Configure the name of the group, its administrators and select the resource to manage it. Now we have resources, we have tenant admins. We need users. “Administration ->Directory Management -> Directories -> New” This will allow you to create a new Domain to sync to vRA so user management at the base level is controlled in AD. Custom groups can still be utilized, but in a different way after is pulled in from AD. You can use this over LDAP, IWA, Or Local. You should see the following:Screen Shot 2019-06-22 at 7.38.57 AM

Input the Directory name, and the Sync Connector will default to Master node. Select your search attribute, and your Bind User information(Again Note the defaults VMware puts in the fields before you input your data, as it helps you). Test your connection and now you have a directory. To sync users, Go to the Directory and click “Sync Settings”. From here you will see config tabs for management of the users. Here is an example of syncing the domain users:Screen Shot 2019-06-22 at 7.41.59 AM

Now you have users, and resources. You probably want to give yourself God Rights in this environment(Doesn’t everyone?). From here, logout of your admin account and back in as the default “Administrator” account. Go back to “Tenants -> Default Tenant -> Administrators” Now that you synced yourself in the directory, and you should now be able to add your domain account as “IAAS”, and “Tenant Admins”. Here is an example of how it should look:

Screen Shot 2019-06-22 at 7.46.59 AM
vcoadmins is a default built in “Custom Group” for vRO administration.

After you add your domain accounts here, log in now with your God-Mode Domain Credentials(The new Directory, or Domain, will be available on the login screen).  After your in go to “Administration -> Users and Groups -> Search your username”Screen Shot 2019-06-22 at 7.51.05 AM

Select your username and go to the “Add roles to this user” window to the right. Go hog, you earned it.Screen Shot 2019-06-22 at 7.55.39 AM

Now you have god rights, you have all the roles your heart could wish for; you have an endpoint and resources. The next steps are Reservations, Network Profiles, and then Blueprints.

I’m going to try to get things out more often. Sickness has plagued my house, but I’d love to help at least one person learn how automation helps life.

Terraform: A Noob continues…

Ok, so you have Terraform installed, well… neat. Remember this is from the perspective of a guy learning Terraform, so come along with me and let’s learn together.

Let’s get into the nitty-gritty and start learning what this whole ‘infrastructure as code’ is really all about. The first thing we are going to do is open a Terminal/cmd prompt and go to the Terraform folder.
Note: On mac I had to run all terraform commands with “sudo”. I went through some changes so I could “sudo -su” the terminal to raise the permissions.


or for cmd prompt
type nul > ""

Now that you have the example folder, it’s time to fill it in with the needed information for a basic apply…

Note: It’s best to go ahead and create a free account with AWS. Here is a great link to start your free account.

Now open the “” file to edit using either “vim”, (Probably need sudo) or opening notepad.

Paste the following:

provider "aws" {
access_key = "ACCESS_KEY_HERE"
secret_key = "SECRET_KEY_HERE"
region = "us-east-1"
resource "aws_instance" "example" {
ami = "ami-0338bce19a7cb103e
instance_type = "t2.micro"

Update the access_key and secret_key with the needed information. To find this in AWS you would go to the IAM to create a user. Once the user is created, go back into the user in IAM and under “Security Credentials” and click “Create Key”.

I updated the ami to a newer template. When I tried to run the apply, the base template would not work from the site. On vim run your “:wq” or “ctrl + s” in notepad to save the work. Now run the following command

terraform init

You should see something similar to the following:

Screen Shot 2019-05-09 at 7.14.52 PM

Ok, now the fun begins. You now have the AWS provider, and you have a file you can utilize for deployments. Next run:

terraform plan

You should see the following:Screen Shot 2019-05-09 at 7.18.42 PM

And finally:

terraform apply

Which will deploy the instance to your EC2 account.
Screen Shot 2019-05-09 at 7.26.14 PM

Cool! But whats cooler than building stuff?? DESTROYING IT WHA HA HA… ok..

Terraform makes that easy to:

terraform destroy

This will run in realtime and loop until the instance is destroyed. I really liked that as a feature because once the destroy command is done, the machine is really gone. Pretty awesome. I plan to move through this into more variables, and into file structures per provider. Also, I really want to dig into how this will work with vRA and Azure. Stay tuned.

Terraform: The Noob Starts

Terraform. We’ve all heard the following phrase, or, if you haven’t, here ya go;

“Terraform has become the de-facto platform for infrastructure as code in the public cloud.”

Well, guess that means some old dogs need to learn new tricks.

What is Terraform?

The definition pulled straight from the source:

“HashiCorp Terraform enables you to safely and predictably create, change, and improve infrastructure. It is an open source tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.”

What this means, is you have a document that specifies the blueprint for the deployment, and you can copy-paste the needed preferences, (as well as adjust afterwards which is a total gas.) So upon reading this, it made me immediately want to get into it. Let’s be real, no one likes using the cloud client to migrate your blueprints…it’s just not enjoyable (If you enjoy it, why/how?). This is really something I wanted to look into. And well Then this happened.

WHAT IaC and with vRA…..



Idk what more needs to be said. Sounds cool, looks cool. Lets get to it…

Terraform Install

There are a lot of docs out there for installing Terraform. has some great links itself. Obviously their link for doing the install of linux and windows works well out of the box. But what about Mac? Well, my recent purchase of a Mac to prove to others that I wasn’t a normal windows snob, has driven me to extremes lately. Its just not the same, and WHY DON’T THE DANG WINDOWS CLOSE!

Anywho, I tried to follow the linux installation for Mac. Then I google’d how to get to the elusive /usr/ folder, then I realized I was an idiot, and installed Terraform. Then the path setting was the next thing. I’d set it and try… nope… try to reset it again and try… nope…. I only had about 10 minutes left then God opened the cloudy skies above…


For those that don’t use Homebrew, Here’s Cody De Arkland(anyone with De in the name = De Man).

For a guy that uses the term “dope” a lot. I dig it. So, I typed in “brew install terraform” after installing Homebrew (See link) and life was good again. Did a quick Terraform -version..

Image 5-8-19 at 7.17 PM

VOILA. Good times man… now to start with this whole Terraform configuration thing…

The Challenge of DevOps

Disclaimer: I am not an expert in this area, this is just a blog over difficulties and conflicts created in the search for DevOps. I will go through some fallacies that will make each group look bad, so stick with it if you can. I really would like to get conversations started where they weren’t.

The Phoenix Project. One of the greatest books of this IT age gives a good concept when it comes to how Infrastructure and Development work with each other. However, there are a plethora of definitions for “DevOps”. How do you take a company that has existed just fine with two (if not more) warring parties and get them not only to work with each other, but to help each other.

Fallacy 1: DevOps is Infrastructure working for Developers

This was my first collision with the term. The idea here, again, is basic. Infrastructure and its core individuals exist to give a foundation and support to the developers, and nothing more. A good example of this is a simple ticket request for a new server with specifics of the hardware. Any infrastructure worker worth his salt would look at those requirements and ask “why”, but this adoption of DevOps is “Why not?”. Obviously I’m taking things to an extreme here, but I have seen too many server requests for extreme hardware requirements (really…a virtual machine with 64 gb of ram?) and the inevitable fight that ensues in response to that three letter question “why?” There are so many other examples I’ve seen, from resource adjustments of the ridiculous, to the blatant opening of security holes. Obviously this is in varying environments, but the idea is the same.

This expands past infrastructure into Operations. For example, when there is a “priority one” ticket, and everyone jumps on the call, the first phrase is, “If operations did their job and fixed this we wouldn’t have to deal with this. I don’t even know why we are here.” Which is something I’ve heard this stated multiple times for multiple reasons.

Like all Fallacies there is truth here. Developers are the reason companies make money. Unless you work in the past, Devs work daily to create and stabilize performance that generate monetization for the rest of IT. The greatest example of this is Uber. Of course the top Taxi company in the nation is an app. So without it there is no real company at all.

For IT workers that, will lead them to a mindset of denial. No they’re not in denial, but  the next fallacy.

Fallacy 2: Developers should come to heel for Infrastructure

So ok, here we go. This is so prevalent in my career that I can’t even think of that many specific instances, because it’s almost daily that I hear something along this term.

Developer asked to be able to monitor or help maintain resources with their machine,  “No”. Developer asked to be able to create snaps for code roll, “No”. Developer asks to be local admin on a box, “No”. Developer asks to have a new dev environment that mirrors production, “No.”, and so on.

Its amazing and a marvel to me that people can just shutdown Developers for minimal reasons and yet, this is the normal situation I find myself involved in. I see a ticket and instead of doing investigation or adjustment the immediate response that I hear is either, “No”, or, “We cant do that”, or “Thats not our problem”.

This is just a few examples, and I’m sure everyone could think of their own examples. One thing that has really stirred this up and made my brain hurt is Containers. Developers ask for a container solution from infrastructure, and they get a big fat, “Why? It’s in the OS, so you figure it out.” This is a very frustrating stalemate.

This pushes to an extreme called “Shadow IT”. Shadow IT is basically if infrastructure wont grant the needed support or help getting things off the ground, Dev will use their individual budget and spin up an entire instance in AWS, GCP, Azure, or a basic private cloud. Just a license  for VMware Workstation can create Shadow IT, it’s that easy (don’t get any ideas). I heard a developer talking about the public cloud saying, “It makes me happy knowing no infrastructure people are touching my boxes.”

This fallacy again comes from a smidge of truth. Development doesn’t know everything about infrastructure. Infrastructure spends all their time doing resource management, monitoring, and adjustments trying to keep the infrastructure running in the best way possible, so they should be the main contributors to the how/what/why of infrastructure.

Fallacy 3: Security CONTROLS ALL

With Ransomware and Wannacry still being buzzwords in our time period, this is definitely a big deal. Security is extremely needed this day and age, from blocking things like DNS floods, to removing patch vulnerabilities. There are countless reasons to keep security up to date. Where does this come in for Infrastructure or Development? Well, Security is the Uber-Deny group. Almost every security individual I’ve met has stated something along the terms of, “My job is to make sure we don’t do something stupid.” I feel like the answer to this is both “Yes”, and “No”. I’m sure people do stupid stuff all the time that has nothing to do with security. The proper statement would be something like, “My position is to rectify security vulnerabilities throughout the stack” Or something like that.

Security will try to block where networks are, how they are setup, where infrastructure is placed, and the list goes on. Are there legitimate reasons? Of course! Security is the necessary part of IT that helps keep things in line, away from prying eyes, and malicious intent.

The Common Factor

All of these fallacies are connected to an amount of truth. They all start when the truth is twisted and exploited by individuals to make their position greater than it is.

It’s like the problem with DevOps is even more internal than IT. The problem with DevOps is us.



I love this quite so much, because at its core it grasps the internal hierarchy of DevOps. It all starts with People.

Obviously each group mentioned is run by People. These people are all built around their own past experiences and troubles. Like iron, these experiences and troubles have made us stronger and sharper, but like the fingers of a string musician we become callous, and those callouses help generate better solutions in both good and bad ways.

There is also the problem with Ego. My favorite statement with immediate meetings are, “Everyone check your ego at the door. It has no place here.” If we only were able to do that and bring only the strengths of the department and not the callous overreaching, “where would we go?”

Finally for us, the problem of listening and understanding.


I know this picture hits a chord for all us. How many of us have listened to what seems like the dumbest ideas and kept our mouths shut to it? DevOps starts with listening, and by listening, I mean the whole management stack. Is this easy to do? Absolutely not, in fact, it’s extremely hard to listen for nuggets of truth in a whirlwind of ideas. However, thats what we need to do. To start this, the greatest thing we can do is just listen, and if you don’t understand, ask the dumb questions that everyone is too proud to ask, so that you do. You are probably not the only one who has that same question.

Finally: People… Again

End Users…the concept is lost by all groups now and again, but everyone in IT works for end users. The hardest concept to grasp, and the easiest road to DevOps, is how to create a better solution for them. Developing a new patch, a more secure Dev infrastructure, or new storage solution. This all has DIRECT impact on an end user, and each group works individually to create a solution for them. Now how to mix them all together? A good start is a CI/CD pipeline and securing an automated solution for Developers to run continual delivery. It exists on infrastructure, it has to run in the best HA stability, and it has to be secured. This is a great solution that involves all groups together. There is so, so much more, but that’s the journey we are all on.

Call me “Optimistic”, or “Crazy,” Or “Nuts”, Or “Dangerous”, but I believe this is the future of our industry. With the kubernetes, containers, CI/CD buzzphrases, and the dominance of public cloud, the old standards needs to be replaced with the promise of DevOps. Now, how will you do it?

Things I learned this week!

  1. Error 500 in VCenter when deploying OVF.. Verify your VCenter certificate is trusted… Also How to do this on MAC and then trust it by selecting “get-info” and setting it to “always trust” Needed this for LifeCycle Manager and NSX deployment
  2. INSTALL PowerCLI on da MAC (Includes Homebrew, Powershell Core).
  3. Initial setup of vLCM