Skip to main content

Buzz words around VMware


In VMworld’19, Pat has mentioned that Kubernetes is becoming the front and center of the company’s product strategy.
Sanjay poonan has declared that using containers in digital transformation is a  “birthright” of VMware.

wait wait.! what are these Buzz words? Why are they overused? Because they sound cool? or exciting? 


Lets break this down and understand this in detail.

Containers :  It’s a method to bundle packages of application and can be isolated with its Network, file system and its processes.  One of the famous container technology is “Docker”
Kubernetes : When I have huge number of containers I need someone to manage and orchestrate it, that is achieved thru a technology called “Kubernetes” -> Google’s product which was made opensource.

Related to VMware:

Project pacific : VMware is Embedding Kubernetes right into the core of vSphere. This will enable developers and IT operators to build and manage apps comprised of containers and/or virtual machines.
VMware Tanzu : It is a centralized control plane to manage Kubernetes clusters running within on-prem data centers and public cloud platforms.  Heard about PKS - Pivotal Kubernetes Service ? Yes Tanzu can be called as a rebranded version of it.

Why do you have to know about this?
VMware has always responded to market dynamics in a way to leverage its products for the customers. But this is the first time VMware is going to change and adjust its basic building blocks with the vSphere products to upper hand in Hybrid cloud. So it’s good to know about these buzz words as we are going to hear them quite often in the future ESXi releases.  So Stay tuned!

Reference links :
https://www.vmware.com/products/vsphere/projectpacific.html
https://cloud.vmware.com/tanzu

Comments

Post a Comment

Popular posts from this blog

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)   ...
Post a Comment
Read more

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive ...
Post a Comment
Read more

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...
Post a Comment
Read more