vBrownBag – VCAP6-DCV Objective 1.3

vBrownBag EMEA is in the midst of recording sessions that cover the VCAP6-DCV (3V0-622) exam. If you are interested in presenting one of the exam objective, see the Call for Presenters post here.

Objective 1.3 – Determine Risks, Requirements, Constraints, Assumptions

Skills and Abilities

  • Differentiate between the concepts of risks, requirements, constraints, and assumptions.
  • Given a statement, determine whether it is a risk, requirement, constraint, or an assumption.
  • Analyze impact of VMware best practices to identified risks, constraints, and assumptions.

Additional Resources

 

Without further ado, the podcast recording can be found here:

Selected as WT2 Speaker!

I am pleased to announce that I was selected as a speaker at the WT2 (Women Transforming Technology) conference on 28 February 2017 in Palo Alto, CA.

vuuu4k37toqjg

I will be presenting a session regarding “Leadership Lessons Learned from the Marine Corps.” I will discuss different lessons (good and bad) that I learned from my 5 years in the military and how these lessons are applicable to the tech industry. This is a breakout session for emerging leaders.

If you’ve never heard of WT2, Women Transforming Technology is a conference hosted on the VMware campus that aims to inspire, support, and connect women in all areas and levels of tech within Silicon Valley and beyond.

This year has two special keynote speakers, Kara Swisher and Gloria Steinem.

I’m very much looking forward to this opportunity to impart what I’ve learned so far in my career to women who are just starting out in the tech industry. Additionally I hope to learn quite a bit and to meet great new men and women in tech!

See you there!

Goals for 2017

Considering we’re over halfway through January, it would now would be an appropriate time for me to write down what I want to accomplish in 2017.

10ejyb5dnf4kem

My goals for this year:

  • Blog more – Blogging as been something that I’ve never been able to maintain a steady rhythm or schedule. Historically I’ve blogged when I’ve run into something interesting or when I was paid to do (ha! but really…). I planned on doing this in 2016 but it took a backseat to my VCDX pursuit. This year, I plan to blog more frequently!
  • Be more community involved – This is another item that I’ve been wanting to do for awhile but was prioritized last while in pursuit of other things. I plan to be more proactive and involved in the virtualization community. I hope to speak at my local (Los Angeles) VMUG. I was selected as a delegate for Tech Field Day in February so I’m looking forward to that! Additionally, I’ll be co-hosting and being a more active participant in vBrownbag. Who knows? Maybe I’ll even start my own podcast.
  • Second VCDX – I achieved VCDX-DCV last year, an accomplishment for sure. However, a majority of my work for the last 18 months has been around Horizon View. Because of this, I’m looking to pursue my VCDX-DTM in 2017.
  • Learn more about the NPX program – The design that I am in the midst of writing for VCDX-DTM is Nutanix based. I would like to find out more information regarding the NPX process, perhaps even attend an NPX bootcamp.
  • Be more proficient with AHV – This goes with the point above. I’m working more and more with Nutanix therefore I would like to skill up and become more proficient with Nutanix and AHV.
  • Learn AWS – I purchased AWS training spur of the moment because of a Black Friday deal I found online. I’d like to keep studying AWS and pursue the Solutions Architect certifications.
  • Speak at a conference – I’ve applied numerous times to speak at VMworld and have been rejected. This year I’d like to branch out and apply to a few different conferences and hopefully earn a speaker spot.
  • Find better work/life balance – This is my dark horse goal. I tend to bury myself in work and am constantly on the road. Additionally I’m going back to university so that’s made having a personal life even more difficult.

There you have it, ladies and gentlemen, my goals for 2017. I’ll do a recap at the end of the year to see how much I managed to accomplish.

macOS VCSA Installer “ovftool” Error

I recently ran into an issue with the vCenter Server Appliance (VCSA) 6.5 installer. When I proceeded to Step 5, “Set up appliance VM” I received the error:

“A problem occurred while reading the OVF file…Error: ovftool is not available.”

Screen Shot 2016-12-19 at 5.00.22 PM.png

After some research, it turns out that macOS Sierra (10.12.x) is not supported and, of course, that is the operating system of my laptop. I found a blog post from Emad Younis that outlines two possible options for working around this error.

I tried both options. Option 1 did not work for me, but Option 2 did. I’d like to take a minute and demonstrate step-by-step what I did to proceed with the VCSA deployment.

On the deployment wizard error, I selected Installer log.

Screen Shot 2016-12-19 at 5.00.22 PM copy.png

Quickly read through the log and find the error regarding the ovftoolCmd, it will state the directory that the installer is searching for the tool set. Copy that directory, sans /vcsa/ovftool/mac/ovftool.

Screen Shot 2016-12-19 at 5.01.03 PM.png

Launch the Terminal utility and type the open command for Finder to open that directory.

asdfasdf.png

For example:

open /private/var/folders/j8/ttwss5yx6cqf0flb5lrj_hww0000gn/T/AppTranslocation/

As mentioned before, leave off everything from /vcsa/ and on.

When that directory opens in Finder, you’ll notice that is it empty…therein lies the problem!

empty.png

Copy the vcsa folder into this directory.

vcsa.png

Once the vcsa folder has successfully copied, you should be able to go back to the macOS installer, press Back, and then hit Next to go back to Step 5.

Screen Shot 2016-12-19 at 5.04.47 PM.png

You should now be able to select the deployment size options and successfully proceed with the VCSA deployment.

App Volumes 2.12 – Provisioning Machine Must be Domain Joined?

App Volumes uses a provisioning machine to capture applications in order to create AppStacks. According to the App Volumes User Guide, “the provisioning of AppStacks must be performed on a clean base image…”

Screen Shot 2016-12-20 at 7.02.00 PM.png

In my opinion, a “clean base image” implies that this machine is not domain joined and therefore not inheriting any group policies.

In earlier versions of App Volumes, there was an option when initially configuring or later reconfiguring App Volumes’ Active Directory integration to “Allow non-domain entities.” This is an option that I always selected in order to have a non-domain joined provisioning machine.

Screen Shot 2016-12-20 at 4.20.18 PM.png

However, now in App Volumes 2.12, that option is no longer available.

Screen Shot 2016-12-20 at 3.09.57 PM.png

I’ve yet to figure out an option to bypass having the provisioning machine on the domain. And there’s no mention of this in the release notes.

😦