My IT Blog

 VMware ON AWS Deployment - Requirements.  As mentioned in the previous post , when we are set with the project objective, we need to prepare the items mentioned in the VMC deployment checklist. Some of the basic requirements are,  The AWS account details - When we deploy our SDDC on VMware Cloud on AWS, it is created within an AWS account and a VPC dedicated to your organisation and managed by VMware. We must also connect the SDDC to an AWS account belonging to us, called the customer AWS account . This connection allows our SDDC to access AWS services belonging to our org  account. SDDC Management subnets - This is the most critical part of the deployment. Choosing the right network for SDDC and connect back to ON-Premise network (check with network team to make sure you provide unique range of CIDR, ASN etc to avoid conflicts)  Connectivity to On-Premise DC and VMC - There are different ways to connect to the On-Prem DC, using IPsec VPN, AWS Direct Connect...

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 ...

In our previous posts , we saw the option to deploy the VCH using CLI utility, vSphere client etc. In this post, we see an option to automate the VCH deployment using vRealize Automation ( vRA) Background:  The current automated world requires the seamless and fastest deployment of its infrastructure. VMware vSphere Integrated Containers gives developers an essential tool for streamlining the process of building and running containerized applications in production.  The deployment of VCH is done through various methods as we see in our previous posts. But in this post, we are going to see how to automate the VCH deployment and the first VCH in few mouse clicks. By using the service catalog in vRealize Automation to provision Virtual Container Hosts on-demand as a ticketless offer, you can make your developers self-sufficient. The vRealize Automation 7.4 and later versions support provisioning and management of Virtual Container Hosts(VCH) for running vSphere Integrated...

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:  ...

In this post we see the options to deploy the Virtual Container Hosts ( VCH) Ref:  https://github.com/rdjagadeesh/vic_homelab/ The previous post talks about vSphere Integrated Containers and their benefits. The VIC offers a robust solution that enables the vSphere environment to quickly get containers up and running in their current vSphere infrastructure. This environment can be useful for migrating current apps to containers or for in-house development. Architecture In a traditional container environment, containers run as threads within the container host. vSphere Integrated Containers leverage the native constructs of vSphere for provisioning container-based applications into its own container running its own very minimal Linux kernel with just enough code to run a Docker image, thus preventing any issue with containers being accessed from other containers by pushing isolation of the container down to the hypervisor layer that is much better at handling this type ...

What is VIC: VIC - vSphere Integrated Containers enable IT, teams, to seamlessly run traditional workloads and container workloads side-by-side on existing vSphere infrastructure. The solution is delivered in the form of an appliance just like any other VMware mgmt solution. The appliance comprises of,  vSphere Integrated Containers Engine , a container runtime for vSphere that allows you to provision containers as virtual machines, offering the same security and functionality of virtual machines in VMware ESXi™ hosts or vCenter Server® instances. vSphere Integrated Containers Plug-In for vSphere Client , that provides information about your vSphere Integrated Containers set up and allows you to deploy virtual container hosts directly from the vSphere Client. vSphere Integrated Containers Registry (Harbor) , an enterprise-class container registry server that stores and distributes container images. vSphere Integrated Containers Registry extends the Dock...