posted

Authored by Kit Colbert, CTO, Cloud Platform BU

dockercon2017-01

Another great DockerCon was just wrapped up.  The conference continues to grow, with 5,500 attendees this year.  The conference itself also feels more mature.  Customers are doing more interesting things with containers, the expo is filled with a broader variety of vendors, and there’s just a ton of content.  Yet DockerCon is able to maintain its nerdy-fun hacker ethos.  And, of course, the quality of the food continues to beat out all other conferences!

DockerCon had a simple message this year: containers are going mainstream.  They focused on two areas to back that up: first is the staggering growth and increasing maturity of the Docker open source projects and second is that containers are ready for the enterprise.  But are containers really mainstream?  Let us see…

Starting with the open source Docker project, the hero numbers are striking:

  • 14M Docker hosts
  • 900K Docker apps
  • 12B image pulls 
  • 3,300 project contributors

Open source Docker is used across every industry and has a thriving ecosystem.  Docker Engine is getting important usability improvements, such as multi-stage builds.  Docker Swarm continues to mature, getting more features around security and orchestration.  Certainly many of these data points indicate containers are very much going mainstream!

But in order for containers to be mainstream, they need to be adopted by enterprises.  A key element of enterprise adoption is the requirement that containers support all applications, not just “cloud-native apps”, or modern, distributed, and usually greenfield applications.  While companies are building new cloud-native apps, the reality is that businesses have tons of existing traditional, monolithically architected applications.  By containerizing those applications, businesses can reap some of the benefits of containers, such as better CI/CD tooling and automation and greater runtime efficiency, without the need for the expensive and resource-intensive task of rewriting, rearchitecting, or in general, changing any code in the application.  Certainly this is mainstream activity!

Indeed many customers presented both on the keynote stage as well as in breakouts about how they were containerizing traditional applications, including Visa, Metlife, Cornell, Northern Trust, Microsoft IT, Societe General, and PayPal.  There were discussions about which applications make good candidates for containerization, intros to Image2Docker, and best practices for making the transition.

While “day 1” containerization and provisioning activities were covered, I didn’t see much about “day 2” activities, specifically how folks actually operated those containerized applications in production.  For instance, how does one deal with availability issues for a monolithic app?  E.g. what if the host has to go down for maintenance?  Can the app be restarted on another host?  How long does the app take to restart?  What if the app takes dozens of minutes or hours to get back up to full speed?  What about performance monitoring?  Or logging?  Or compliance assessments?  What about backup?  DR?  These are the questions that didn’t seem to be addressed.

Quite the opposite, in one session, Metlife even explicitly ruled out discussing these items:

dockercon2017-02

To some degree, this is a maturity question.  You’ve got to get the basics of packaging and provisioning solved before you can move on to the meatier topics of day 2 operations.  And the reality is that many of those day 2 operations capabilities aren’t well-solved yet in container environments.  When talking to one customer, he mentioned that he is running a couple of containerized traditional apps in production but quickly admitted that they’re “not the important ones.”  Indeed he did not have solutions for monitoring, back up, or any of the other items I mentioned above.  Even Northern Trust, who gave a fairly impassioned talk in support of containerizing traditional apps, mentioned at the end of the session that they had only containerized one Tomcat app and a single Weblogic cluster.

This is exactly where we at VMware want to help!  With vSphere Integrated Containers (VIC), we can leverage the high availability features of vSphere as well as its robust ecosystem to solve some of the shortcomings in the container space today.  VIC allows you to run a containerized traditional app in production, because it’s leveraging all the production capabilities of vSphere.  This means that businesses don’t need to reinvent the wheel for monitoring, compliance, DR, etc – they can leverage the solutions they already have for vSphere!  In addition, we’re working closely with Docker, Inc on many different projects, from containerd to LinuxKit to Docker Enterprise Edition.  So if you haven’t checked out what we’re doing with VIC, you definitely should!

In the end, have containers gone mainstream?  I think we’re oh-so-close, on the precipice.  To date, the industry has lacked mature solutions in the container space for all the operational requirements businesses have for any application they want to run in production.  But those solutions are coming fast, from the improvements in the open source Docker projects to the growing container ecosystem to what we’re doing with VIC.  So if containers aren’t mainstream now, they will be very soon!  What do you think – are we there yet?

You can follow Kit on Twitter: @kitcolbert

posted

Authored by Debra Robertson, Product Marketing Manager, Cloud Native Applications

DockerCon 2017 is a three-day, Docker-­centric conference organized by Docker, Inc that takes place from April 17-20, 2017 in Austin, Texas. As a gold sponsor of the event, VMware will be there to support the Docker community and participate in sessions, share demos, and promote the event.  

If you’re heading to DockerCon 2017 next week in Austin, connect with us to learn how VMware’s Cloud Native Apps portfolio and open source technologies enable developers and IT from dev-test to production. VMware subject matter experts will be onsite to walk you through demos and use cases for securely developing, deploying and managing container-based applications.

Attend the Self-Service Provisioning of Docker Datacenter on VMware vSphere Session

Join VMware in a session discussing how new self-service provisioning capabilities in vSphere will allow developers and cloud admins to deploy and operate Docker Datacenter in a ticketless manner. Software Engineers Ivan Porto Carrero and Benjamin Corrie will give a sneak preview of current development work aimed at giving developers access to container frameworks on demand – while at the same time leveraging the advanced performance, availability, and security capabilities of vSphere.

WHEN: Tuesday, Apr 18, 4:15 PM – 4:35 PM
WHAT: Self-Service Provisioning of Docker Datacenter on VMware vSphere
TRACK: Ballroom C

This session will highlight how features like DRS, SDRS, HA, and NSX micro-segmentation can be used to make your container deployments more highly available, secure, performant and maintainable.

Join the Conversation at Booth G9

While at DockerCon, you can connect with VMware’s cloud-native team, and experience our solutions through our many booth demos:

  • vSphere Integrated Containers: Deploy enterprise-grade container infrastructure designed specifically for running traditional apps in containers, alongside VM-based workloads on vSphere.
  • Docker Datacenter on vSphere: Rapid, self-service provisioning of Docker Datacenter on vSphere. Empower developers and cloud admins to deploy secure, highly available and performant container frameworks on demand.
  • NSX for Docker Networking: Deploys micro-segmentation to secure and network Docker containers by leveraging advanced NSX CNM/libnetwork capabilities.
  • vSphere Docker Volume Services: Enables high availability for stateful apps with Docker-certified vSphere Docker Volume Storage.
  • Project Admiral – Container Management Platform: Operationalizes Docker with enterprise container management services including full life cycle management.
  • Project Harbor – Enterprise Service Registry: Project Harbor provides an open source, secure, private container registry for enterprises. Features LDAP/AD integration, policy-based replication, and advanced audit and logging functionality.
  • Photon Platform and Docker Swarm: Provisions containers on Photon Platform through Docker Swarm with easy integration and compatibility

Pick Up Your Access Pass for the Cloud-Native Fiesta

Join the VMware Cloud-Native team for an exclusive rooftop party with tacos and margaritas during DockerCon in Austin on Wednesday, April 19th at 5:30 PM. At this event, you will have the opportunity to kick up your heels and network with other container community members. Stop by the VMware booth #G9 to pick your access pass; space is limited.

invite-cloud-native-fiesta-austin-april-dockercon

Navigate DockerCon Like Pro

Last year the lines were extremely long at the time the floor opened, so if you can check in early!

  • Registration: Bring your ID – You’ll need this to check in and for the DockerCon Party. Registration opens on Monday, April 17 from 10:00am – 7:30pm

Additionally, here are some tools provided by DockerCon to help you navigate the show and network with the community:

  • Mobile App: Download the official DockerCon Mobile App to stay informed with the most up to date news and information.
  • DockerCon Slack: Download DockerCon Slack – This is the conference preferred
  • Moby Mingle: Log into your account and set up Offers, Request and/or Group Chats!

Stay Connected

Stay connected with VMware Cloud Native by following us on Twitter at @cloudnativeapps.
We hope to see you there!

posted

Authored by Massimo Re Ferre, Technical Product Manager for Cloud Native Applications

Kubecon 2017 contained plenty of presentations that moved the needle further up the steep learning curve of Kubernetes. Listening to the advanced experiences and the enthusiasm of presenters gives you the sense that Kubernetes is here to stick around–and that it will be a key driving force in the future of cloud computing.

The technology is evolving quickly. Its implementation is bringing success to startups and small organizations as well as in pockets of enterprises. And in the cases where it has been deployed in pockets of enterprises, the teams that own the deployment are starting to seek help from IT to run Kubernetes for them. Multitenancy and security are beginning to become concerns.

Meanwhile, at the expo, the dominant areas of the Kubernetes ecosystem on display were setup, maintenance, networking, and monitoring. There were, in particular, many interesting offerings and solutions in the area of monitoring.

During the keynote, areas of improvement and the newer features of Kubernetes were at the heart of the presentation by Aparna Sinha of Google’s Kubernetes product team. Improvements include support for 5000 hosts, RBAC and dynamic storage provisioning. One of the seemingly new features in the scheduler allows for “taint” and “toleration,” which may be useful to segment specific worker nodes for different namespaces.

Etcd version 3 gets a mention as having a quite big role in the scalability enhancements to Kubernetes, but the new version seemed to trigger concern among some participants on how to safely migrate from etcd version 2 to the etcd version 3.

Aparna also talked about disks. She suggests leveraging claims to decouple the K8s admin role (infrastructure aware) from the K8s user role (infrastructure agnostic).

Dynamic storage provisioning is available out of the box, and it supports a set of back-end infrastructure (GCE, AWS, Azure, vSphere, Cinder).

For the next version of Kubernetes, Aparna alluded to some network policies being cooked up.

Next, Clayton Coleman of Red Hat talked about K8s security. When he asks how many people set up and consume their own Kubernetes cluster, the vast majority of users raise their hands–very few, it seems, are running centralized Kubernetes instances that users access in multitenant mode, an understandable state of affairs given that RBAC has just made it into the platform.

Clayton went on to mention that security in these “personal” environments isn’t as important as it will be when K8s starts to be deployed and managed by a central organization expressly for users to consume it. At that stage, a clear definition of roles and proper access control will be paramount. As a side note, with 1.6, cluster-up doesn’t enable RBAC by default but Kubeadm does.

On Thursday, Kelsey Hightower talked about cluster federation–that is, federating different K8s clusters. The federation API control plane is a special K8s client that coordinates dealing with multiple clusters.

Many of the breakout sessions were completely full. The containerd session presented by Docker highlighted that containerd was born in 2015 to control and manage runC. It K8s integration will look like this:

Kubelet –> CRI shim –> containerd –> containers

Keep in mind, though, that there is no opinionated networking support, no volumes support, no build support, no logging management support, etc.

Containerd uses gRPC and exposes gRPC APIs. There is the expectation that you interact with containerd through the gRPC APIs, typically via a platform. There is, however, a containerd API that is not expected to be a viable way for a standard user to deal with containerd. In other words,  containerd will not have a fully featured, supported CLI. It is, instead, code that is to be used with or integrated into higher-level code, such as Kubernetes or Docker.

gRPC and container metrics are exposed via a Prometheus end-point. Full Windows support is in the plan but not yet in the repo.

One speaker, Justin Cormack, mentions that VMware has an implementation that can replace containerd with a different runtime, the vSphere Integrated Containers engine. For more on containerd, see one of my previous blog posts, Docker Containerd Explained in Plain Words (http://www.it20.info/2017/03/docker-containerd-explained-in-plain-words/).

Another interesting breakout session was on cluster operations. Presented by Brandon Philips, the CoreOS CTO, the session covered some best practices to manage Kubernetes clusters. What stood out was the mechanism that Tectonic uses to manage the deployment. Fundamentally, CoreOS deploys Kubernetes components as containers and lets Kubernetes manage those containers (basically letting Kubernetes manage itself). This way Tectonic can take advantage of Kubernetes’s own features, such as keeping the control plane up and running and doing rolling upgrades of the API and scheduler.

Another session covered Helm, a package manager for Kubernetes. Helm Charts are logical units of K8s resources plus variables. The aim of the session was to present new use cases for Helm that aspire to go beyond the mere packaging and interactive setup of a multi-container app.

All in all, KubeCon exposed a lot of people’s experiences with Kubernetes to help developers and operators learn about the system and its related projects, adapt the system to their needs, and deploy it successfully.

posted

 

Authored by Nathan Ness, Senior Technical Marketing Engineer, Cloud Native Applications

Last week in Berlin, VMware joined the Kubernetes community to support the Cloud Native Computing Foundation community and participate in sessions, share demos, and promote the event.  Did you miss our booth demos or are you looking for a refresher? Here’s what we showcased:

Photon Platform + Kubernetes

Kubernetes is a container orchestration platform that provides developers agility, high availability, and scheduling for deploying container workloads. This is accomplished by submitting API calls to a Kubernetes Master with in a cluster. The Kubernetes Master schedules Deployments, Pods, etc., on to available workers nodes within the cluster. Photon Platform can provide Kubernetes clusters on demand with a single API call. This can done by either the “Provider” of infrastructure and the Kubernetes API endpoint can be handed off to the “Consumer” developer team(s). Or the developers can deploy and manage the Kubernetes cluster through Photon Platform in a self-service manner.

k8-blog-nate-001

Need to increase the size of the Kubernetes cluster? You shouldn’t have to rely on manual processes to manage the deployment/lifecycle of a Kubernetes cluster.  You can resize the cluster from the UI of Photon Platform or the again from the API.  If you have the available capacity to increase the size the cluster you can easily increase the number Kubernetes nodes and Photon will automatically provision and add them into the Kubernetes cluster.

k8-blog-nate-002

Photon Platform manages your available cloud resources for you with quotas. These quotas can be divided up into different tenants assigned to projects for consumption. This ensures that development teams have boundaries for the amount of infrastructure consumed.

k8-blog-nate-003

Lastly, Photon Platform is monitoring the health of the cluster. If a worker dies for any reason, Photon Platform will automatically spin up a new worker and keep the worker node count at the deployed number.

VMware NSX + Kubernetes

Last week the NSX-T with K8s demonstration showed how NSX uses the Container Networking Interface (CNI) Integration to provide enterprise networking to containers.  Benefits of using the NSX-T network virtualization and security platform for container networking include automating the creation of network topology as well as enhancing security with per Pod (group of containers) logical ports and micro-segmentation between Pods.  

Interested in learning more NSX and container networking? Check out this technical blog!

Stay Connected

Stay connected with Cloud Native by following us on Twitter at @cloudnativeapps.

posted

Authored by Debra Robertson, Product Marketing Manager, Cloud Native Applications

CloudNativeCon + KubeCon will showcase Cloud Native Computing Foundation (CNCF) projects under one roof in Berlin from March 29th to March 30th, 2017. As a gold sponsor of the event, VMware will be there to support the CNCF community and participate in sessions, share demos, and promote the event.  

If you’re heading to KubeCon 2017 next week in Berlin, connect with us to learn how VMware’s cloud native portfolio and open source technologies enable developers and IT from dev-test to production. VMware subject matter experts will be onsite to walk you through demos and use cases for securely developing, deploying and managing container-based applications.

Attend the Network-Aware Kubernetes Scheduler Session

Join two of VMware’s Kubernates contributors discussing Kubernetes exposes an interface to build a custom scheduler. Software Engineers Akash Gangil and Salvatore Orlando are presenting on how better scheduling decisions can be made with information about the network topology.

WHEN: Thursday March 30, 2017 16:25 – 17:00
WHAT: A Network-Aware Kubernetes Scheduler
WHERE: Rooms B 05 – B 06

The scheduler would make pod scheduling decisions as a function of network health, in addition to other resources like cpu and memory predicates used by the default scheduler. Demo setup would consist of kubernetes with OVN as a networking backend using the ovn-kubernetes plugin. 

Learn about VMware’s Kubernetes as a Service Platform for Enterprises

Photon Platform is built on open source Photon OS and Photon Controller which are custom-designed for high churn, massively scalable container environments. Photon Platform is part of VMware’s Cloud Native Apps solutions and leverages production-grade networking and storage for a thin IaaS to support Kubernetes as a Service.  

Join the Conversation at Booth G1

VMware is a sponsor of CNCF and OCI to drive open source collaboration and standards for container deployments. We have open source projects to ease integrations with other technologies and are working with customer across the world to build and contribute our development to the industry. In addition to learning more about our open source projects, you can also connect with VMware’s cloud native experts, and experience our solutions:

  • See a Kubernetes-as-a-Service demo showcasing Photon Platform, a container-optimized cloud platform which delivers on-demand developer tools and services. We will show:
    • Self-service Kubernetes clusters for platform and app development teams
    • Self-healing Kubernetes clusters which automatically recover from failure
    • Commercially supported Kubernetes and Linux distros from VMware
  • Watch a networking demo featuring NSX-T which integrates with Kubernetes via a CNI plugin. The demo will show how NSX can be used to provide per pod (group of containers) logical ports and micro-segmentation between pods. The demo will demonstrate all the benefits gained by using NSX-T for container networking.

Stay Connected

Stay connected with Cloud Native by following us on Twitter at @cloudnativeapps.

We hope to see you there!

posted

VMware Hands-On Lab (HOL) by Dave Rollins

Today we are releasing the reaming network and Cloud Native Apps labs in 2017 Hands-on Labs catalog.  While we have already released the HOL-1703 and HOL-1725 series of NSX based content, today’s labs focus on VMware Integrated OpenStack and Partner solutions from Check Point and Trend Micro.

vmw_7334

These also contain our first vertical solutions for Healthcare and the Teclo industry.  HOL-1741-USE-1 shows a use case on how Horizon, NSX and Trend Micro can help secure and protect the healthcare environment, but in practice, these solutions can be applied to any industry.

The VMware Network Functions Virtualization lab (HOL-1786-HBD-1) covers how communication service providers can virtualize network service functions to reduce CapEx and OpEx, while improving service agility.

jan_9525

As an added bonus, we are releasing the much anticipated Cloud Native Apps labs today.  These where slated to be released later this week, but with the announcement at VMworld Europe of updates to the Photon Platform, we have received a number of requests for their release!  Along with the Photon Platform lab, we are also releasing the vSphere Integrated Containers lab.

Here are the links to the labs we have for you today.  You can click on the Lab SKU link to be taken directly to the lab entry and start taking the lab.  Also, you can download any of the lab manuals from the Hands-on Labs Document site.

LAB SKU DESCRIPTION ARCHIVED 2016 LAB
HOL-1720-SDC-1 VMware Integrated OpenStack (VIO) with vSphere and NSX HOL-SDC-1620
HOL-1724-SDC-1 Advanced SDDC Security with Check Point vSEC and NSX N/A
HOL-1730-USE-1 vSphere Integrated Containers HOL-SDC-1630
HOL-1730-USE-2 Cloud Native Apps With Photon Platform HOL-SDC-1630
HOL-1741-USE-1 Horizon and NSX/Trend Micro: Use Cases to Secure and Protect Healthcare HOL-MBL-1661
HOL-1786-USE-1 vCloud Network Functions Virtualization N/A

If you attended VMworld, you may have noticed some Hands-on Labs staff wearing the Yellow (banana) shirts.  They were focused on assisting attendees with NSX and networking questions and are also affectionately known as “Tina’s Minions”!  Hi Keith!

jim_3147

posted

Authored by Jared Rosoff, Chief Technologist Cloud-Native Applications

Over the past few years our customers have been asking us how they can get the developer productivity and agility of the public cloud, but with the cost, security, and control of their private data center. Photon Platform, which we are announcing today at VMworld Barcelona, delivers on this promise. In this article we’ll dig into the background of why we built Photon Platform and how it delivers on this new need for cloud native workloads.

The need for developer services

As much as the public cloud heralded in a new cost model, shifting from capex to opex, the bigger change is actually in the way we construct software. Public cloud is as much a programming model as it is a cost model.

Developers today demand on-demand, API-drive access to the tools and services they need to write software. Teams are embracing devops toolchains, leveraging things like Chef, Puppet and Terraform to describe and automate deployments. These environments are highly dynamic, often getting provisioned, used, and then torn down over the course of an hour.

Developers are taking new levels of responsibility for the operation of their software. No longer do they push builds over a wall to an operations team. Instead they are responsible both for writing the software and for maintaining the running instances of the software. This means they need direct access to monitoring, management, and diagnostic tools that previously only the IT operations teams used.

The need for private cloud

Public cloud has defined and delivered this new developer experience. But for many organizations, there is a need to achieve this same operating model in their own data center.

For large applications, the cost of renting vs. buying makes the public cloud a poor option. Shifting from capex to opex is great when you have rapidly changing costs or lack predictability in your workloads. But when applications reach maturity and have predictable growth, continuing to pay the tax to rent your hardware gets expensive.

Many organizations have strict security and regulatory requirements that make public cloud prohibited. There are often strict controls on the location of data in order to comply with data sovereignty laws. Sometimes you need to build applications that interoperate with existing systems already in your data center. For these workloads, the latency of crossing from public cloud to your own data center makes this architecture infeasible.

Problems faced with private cloud

As we talked to more and more customers that were making this journey to deliver a public cloud experience in their private data center, several things became very apparent:

  1. vSphere is a different thing. It’s operational model is focused on enabling IT to directly manage workloads and infrastructure, rather than provide a set of service to developers.
  2. Other options are immature, complex, or incomplete. Whether looking at the open-source OpenStack ecosystem, or newer bare-metal container based solutions, IT professionals struggle to get these systems up and running and to keep them running. When they do, they often lack the features, flexibility and security needed to power mission critical enterprise workloads.

We need a new way.

Photon platform

Photon Platform is an Enterprise Cloud Infrastructure Platform which enables IT to deliver on-demand tools and services developers need to build and run modern applications while retaining security, control and performance of the datacenter. Purpose-built for cloud native applications with natively-integrated enterprise container infrastructure support, Photon Platform brings the scale, performance and features previously accessible only to hyper-scale web companies into the customer’s own datacenter. It leverages the industry leading hypervisor, networking, and storage technologies to bring the best-in-class performance, reliability and ease-of-use to cloud native workloads.

photon-platform-marketecture-image

Features

Kubernetes as a Service

Photon Platform enables you to deliver Kubernetes as a Service to multiple tenants from a single shared pool of hardware. Each tenant gets access to API, CLI and GUI tools which allow them to provision dedicated Kubernetes clusters on the fly. Users get a dedicated kubernetes cluster with strong isolation from other tenants. Photon Platform automates the provisioning and high availability of these clusters, automatically replacing failed nodes with no human intervention.

Infrastructure as a Service

Photon Platform delivers core IaaS capabilities including VMs, Networks, and Persistent Disks on-demand to developers. Resources are provisioned quickly and reliably, supporting the needs of devops tools that programmatically allocate resources at scale.

Modern Developer Experience

Photon Platform exposes services to developers through REST API, CLI or HTML5 based GUI. This makes it easy to integrate Photon Platform’s capabilities into developer tools and workflows including CI/CD, deployment automation, or configuration management tools.

Scale-out architecture

Photon Platform uses a unique scale-out, multi-master control plane. Photon controller implements a quorum based consensus model that ensures that as long as >50% of controller nodes are available, the control plane still operates with full capabilities. A standard deployment is 3x Photon Controller nodes, but you may deploy more nodes to increase the capacity of the control plane or to enable more sophisticated high availability models. Control plane data and and processing is spread across photon controller nodes. Photon controller has no external dependencies; you don’t need to run any databases, message queues, or other systems to keep the control plane running.

Conclusion

We’re very excited to introduce Photon Platform to the VMware family of products. We believe this new architecture enables modern IT organizations to deliver a best-in-class developer experience to their development teams with the cost, security and control advantages of the private cloud.

To learn more about Photon Platform, check the product page at http://www.vmware.com/products/photon-platform.html

posted

Authored by Emad Benjamin, Principal Architect, Global Services Advanced Architecture

The room for this session was packed in Las Vegas, and boy did people come armed with their questions. It was great to see attendees for multiple companies who are paying attention to the Cloud Native Apps (CNA) space.  Now, we promised that what was discussed in Vegas would stay in Vegas, but if we can offer a glimpse for our European attendees, then we are sure you would appreciate this minor break away from tradition.

Speaking of breaking away from tradition, well “Hello, CNA!” – What a way to begin the session as to just what is CNA, how does one distinguish a cloud native app from a monolithic one. But wait a minute!? What is monolithic, draw it for me please!?  And this is how the conversation began; we defined what we see as being a monolithic app as opposed to highly scaled out micro-services like architecture often found in CNA.  It is all great flexibility offered on Day-1 and we talked about the benefits, but what happens on Day-2 (security, manageability, scalability) – well we discussed the answers to that too, and won’t spoil the surprise, but suffice to say that if you come to the session we will do our best to answer any and all questions about this, IMHO a rapidly forming new and highly opinionated space.  Come join us and listen to a few of our technical services experts as to how their customers are tackling CNA.

state-of-the-u

But wait…you didn’t think that was it…here read more…

In this group discussion we will have an interactive session on what is cloud native, what scale it addresses, who are some of the adopters, and which direction this trend is forcing the market over the next few years.  It is an opportunity for you to ask the simplest of questions to the most complex ones, sometimes a simple question as “what is cloud native” can quickly turn into a complicated answer, and hence is the opportunity to discuss the wide variety of opinion that surrounds this.

In this talk we will highlight the elements of this rapidly moving phenomenon through our industry, a phenomenon of building platforms, not just business logic software but infrastructure as software. We humbly believe that the drive towards these platform solutions is due to the following fact: approximately half of new applications fail to meet their performance objectives, and almost all of these have 2.x more cloud capacity provisioned than what is actually needed. As developers/DevOps engineers we live with this fact every day, always chasing performance and feasible scalability, but never actually cementing it into a scientific equation where it is predictable, but rather it has always been trial based, and heavily prone to error. As a result we find ourselves delving with some interesting platforming patterns of this decade, and unfortunately we are lead to believe that such patterns as microservices, 3rd platforms, cloud native, and 12factor are mainly a change in coding patterns.  However, contrary to this popular belief, these patterns represent a major change in “deployment” approach, a change in how we deploy and structure code artifacts within applications runtimes, and how those application runtimes can leverage the underlying cloud capacity. These patterns are not code design patterns, but rather platform engineering patterns, with a drive to using APIs/Software to define application platform policies to manage scalability, availability and performance in a predictable manner.

 

posted

Authored by Mark Peek, Principal Engineer, Cloud-Native Applications

Technologies such as PaaS and containers are making developers increasingly more efficient at delivering their code into production. The tooling around continuous integration and continuous deployment is reducing the time it takes to safely push code through the delivery pipeline. Earlier this year we announced the Pivotal-VMware Cloud Native Stack which delivered the power of the Pivotal Cloud Foundry on top of Photon Platform. And at VMworld US 2016 we hinted about more to come on top of Photon Platform.

container_blog

Next week at VMworld Europe 2016 in Barcelona, Jared Rosoff (CTO, Cloud Native Applications) will be delivering a spotlight session on Delivering Containers as a Service with Photon Platform [CNA12273]. In this session he will talk about how containers are becoming increasingly popular as a way to deliver software from development out into production. Kuberenetes integration with Photon Platform can address the challenges to running an enterprise container infrastructure. Jared will discuss the capabilities such as self-service Kubernetes clusters on demand, multi-tenant operation, and much more. Come join us in Barcelona to hear about our Photon Platform offerings.

posted

Authored by Alka Gupta, Senior Global Technical Alliance Manager


screen-shot-2016-10-06-at-1-33-06-pm

You have heard about Pivotal CloudFoundry. You have also heard about VMware’s brand new product, Photon Platform. You want to learn more about each one of them and  how the two work together to deliver an optimized cloud native experience to both operators and developers? Where does each sit in the stack and what use cases does a PCF+Photon Platform solution address. When should I run PCF on vSphere and when on Photon Platform?

These are exactly the questions we will address in this session: Architecting Cloud-Native Systems with Photon and Pivotal Cloud Foundry [CNA7813-QT]

We will share a real world case study on deploying PCF on Photon Platform, lessons learned and some best practices. You will be able to walk away with an understanding of Photon Platform architecture, why it is best suited to run Pivotal Cloud Foundry, architecture components of each and how they integrate together.