My IT Blog

I hope you and your loved ones are safe and healthy   During this pandemic time, I have got a chance to onboard the VMware ON AWS to another location of our business. In this blog series I will share my experience and few tips about VMware ON AWS (VMC). This is purely my view and the intention are to spread the views to the community. If you have any issues, comments, feedback kindly share via email. Let’s get straight to the topic.  Why VMC:  Before we go choose to proceed with VMC, we need to understand and convince ourselves on below items,  Where do we fit this VMC in our existing infrastructure?  How could VMC bring in a value to our business  What workloads or solutions do we plan to run in this VMC?  Do we have a DR requirement? If yes, do we have an existing setup to migrate to VMC or its going to be a new DR setup?  Like this you might have to ask few questions which you might need to address it. When we have a problem statement and the solution, we are ready to proceed.  What

Virtual Container Host Deployment using the "vic-machine" Utility - VMware Integrated Containers In our previous posts , we saw the steps to deploy VIC appliance and deploying the VCH from vSphere client. In this post, we will see the steps to deploy the VCH using the "vic-machine" CLI Utility  Refernce: https://github.com/rdjagadeesh/vic_homelab/ Once we deploy the vSphere Integrated Containers (VIC) appliance, access the VIC appliance IP from the browser and we land on the below page. From this page, we can download the vSphere Integrated Containers Engine bundle from the appliance and unpack it on the workstation/laptop/ jump host where we connect to our vSphere environment. Unpack the downloaded bundle  The bundle included the following contents and utilities   The VIC bundle includes the vic-machine CLI utility. We use "vic-machine" to deploy and manage virtual container hosts (VCHs) at the command line. Procedure: 

VMware introduced a new API service in vSphere 6.5 version which is known as vSphere Automation API. This service allows us to introduce several new SDKs for JAVA, Perl, Ruby, REST etc.   Today we will see how to setup the basic wizard to start using the API service in day to day life. For more information about what was introduced with the vSphere Automation APIs visit Here Documentation : The documentation for this SDK version is pretty straight forward. We can browse to each level of API and see the sections of what the operations it performs. We can get the URL, JSON , XML representation for each and every operations in the document. SDK Documentation   SDK tool kit: You can download the SDK kit from VMware { code } Tools required: We will use Postman today so that we will be able to start working with the API quickly and build your knowledge of how it works before using API in your own application. Postman is a great application to design, bu

Just off from the VMworld 2017 US event. As always VMware featured a number of great announcements at VMworld 2017 including VMware Cloud on AWS. VMware customers can now run new or existing virtualized workloads in the AWS cloud while maintaining their current VMware tools and skill sets This announcement provides an important shift in the hybrid cloud market for businesses looking to adopt the agile flexibility and services of cloud while preserving infrastructure and investments in the datacenter Another BIG announcement was VMware and Pivotal Launch Pivotal Container Service (PKS) and Collaborate with Google Cloud to Bring Kubernetes to Enterprise Customers.     New Pivotal Container Service™ (PKS) Delivers a Simple Way to Deploy and Operate Production-Ready Kubernetes on VMware vSphere® and Google Cloud Platform (GCP)        PKS Features Kubernetes Distribution Built on Kubo, an Open Source Technology Created by Pivotal and Google Cloud, Addressing the Need fo