There are many options for maintaining a website these days. There are free options on blogger and WordPress, all the way up to premium services. I hosted this site on Squarespace for many years. The service is good but their templates selection was lacking for a tech blog. I was also underwhelmed with their editor’s performance and it is fairly expensive. I set a goal to migrate my website onto another service to both reduce the cost to maintain and to make it a little easier to update if I am offline.
Maintaining valid licensing in vRealize Operations Manager is crucial to getting the most out of the tool. There are two methods of licensing vROps: per processor with unlimited VMs or per virtual machine or physical server monitored. The latter method is also referred to as an Operating System Instance, or OSI. An OSI is any device, physical or virtual, that has an IP address and is capable of being monitored.
Sizing a vRealize Operations Manager Environment VMware vRealize Operations Manager is the flagship monitoring suite for the entire VMware Software Defined Datacenter stack. The software is incredibly powerful, but it can be a bit daunting to a newcomer. Each update has improved out of the box functionality, however there is a lot to learn to master the software and truly make the most out of its features. Every successful environment starts with a strong design.
Designing for a Home Lab A practical way to gain experience with vRealize Operations Manager is to deploy and implement it into a home lab. A design for a home lab almost seems too simple, but planning it out and diagraming a simple example can help when the time comes to design a production environment. The environment will need to support the following: Monitor 100 Objects Monitor 10 End Point Operations Management agents The environment is also resource constrained, and the node can be no larger than a Small node size.
I am proud to announce that I have been named a member of the inaugural group of vExpert Cloud. The vExpert program is an award given to community members that contribute via blogs, VMUG, vBrownbag, and other means. Since VMware is such a large product the vExpert team has broken the disciplines up into three additional specialties: NSX, vSAN, and Cloud. This cloud designation is extremely valuable to me as my focus over the past three months has been VMware Cloud Foundation.
Public speaking is hard. Standing in front of a crowd and being the center of attention can be a scary thought. Luckily, there are many members of the technology community out there willing to ease you through it. At VMworld 2017 I was fortunate enough to participate in a vBrownBag panel discussion with some giants in the VMware community: Edward Haletky, Simon Long, and Ariel Sanchez Mora. The four of us were talking after the session and decided we would like to formally arrange a mentoring program to help give back to the community that has helped us so much.
VMworld 2017 is upon us and looks to be busy as ever. I’ll be returning to Las Vegas and the place this ride started last year. There has been a LOT happening in my life during the past 50 weeks. I’m proud to say I joined Rackspace in the Specialist Cloud Architecture business, representing VMware products and services. As many of you also know, I joined the vBrownBag crew and will be hanging out at the TechTalk booth as much as possible.
ob interviews are really hard. Between having to take time off work with little notice, having to prep, and then opening yourself up to be judged by a stranger. The experience causes me a lot of anxiety. Being good at an interview is a skill. The key to mastering any skill is practice, so I asked my fellow vBrownBag crewmates to help me with a mock interview. Rebecca Fitzhugh agreed to help out and we recorded it for the vBrownBag podcast
In my article about creating an Azure virtual machine, I walked us through the very basic wizard to create a VM. There is an entire segment of the virtual machine build process dedicated to optional features. These features allow new virtual machines to integrate a VM into an existing Azure environment. When we created our first machine we accepted the default settings, which created new network and storage accounts. That works perfectly for a first look but it wouldn’t be appropriate for use in a real life Azure Infrastructure.
One of the most basic tasks a VMware administrator will perform is deploying a virtual machine. Whether it is creating a VM from scratch or using a template, we’ve all worked through the wizard. As I dig deeper into Azure I can’t help but bring my experience with vSphere along with me. The Azure Resource Manger is a very different experience from the vSphere Web Client but there also quite a few similarities.