Skip to main content

VMworld US 2017 - Shaping the Future

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 for a Flexible Container Experience On-Premises and in the Cloud
  •       VMware Joins Pivotal and Google Cloud's Kubo Collaboration by Committing Significant R&D Resources

 Pivotal and VMware are applying their deep enterprise expertise to launch PKS™, a commercial release of the open source Kubo technology, to help Global 2000 companies operationalize Kubernetes. Software teams that have decided on containers as their unit of deployment need a reliable, scalable container orchestration platform like Kubernetes. PKS will help operations teams deliver a hardened, maintainable container platform, while giving developers on-demand access to a production-ready environment featuring high availability, security, and multi-tenancy across private and public clouds.

The new offering is expected to become available in calendar Q4 2017. Once I have some hands-on with this offering, and we know how the whole thing will be packaged, I’ll share more details with you.

There are other major announcements and you can read more http://ir.vmware.com/overview/press-releases/default.aspx

Here below are the information in case you missed 

We continue with VMworld Europe in Barcelona beginning Monday, September 11 and the vFORUMS through the end of the year.


Labels:

Popular posts from this blog

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N...
Read more

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...
Read more

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this...
Read more