Building infrastructure for the 3rd platform apps – top down or bottom up approach ?

butd-2

World enterprises are struggling these days with a big question: how to move forward to the next generation 3rd platform applications.
In some of the organization the transition starts from a business need, and in others, the development teams are pushing for the change.

While most of the development departments within today’s organizations are already starting to adopt the new 3rd platform development tools, the IT departments find themselves in a strange situation.

The developers are starting to take infrastructure decision and are sketching a new IT horizon.

The apps determine how the infrastructure will look like and actually taking the “We don’t care” approach asking for big “White Boxes” to carry their application loads while saying: “We will take care of everything.”

This Facebook, Google and Amazon approach is right when it comes to large organizations that develop mass scale applications but mostly does not fit the typical enterprise that has limited development and IT teams.

One of the most common approaches for today’s 3rd platform apps is using software containers to build a microservice application.
While software containers are an excellent way to package and ship applications without the need of a complex infrastructure to rely on, most of the container’s management systems are focusing on placement, shared API, and process management and still depend on a general purpose O/S to run the containers loads.

This general purpose O/S usually known as the “Container Host” is the place where all containers run as separated processes.

Some companies had created a stripped down O/S  that has only the basic functionality of running containers, among this solutions are VMware’s Photon O/S, Tectonic Core OS, Project Atomic (sponsored by Redhat), Ubuntu core and Microsoft’s Nano Server.

So when going back to the traditional enterprise dilemma, there are the two ways of deploying containers in an organization.

“Top Down” approach: The most common used today and developer-centric, basically it gives a container API to the developers and sprawl container hosts on physical or virtual servers leaving the developers to maintain the Container Host O/S.

hard

 

“Bottom Up” approach: A new approach that distributes the responsibility and sponsorship between the developers and the IT departments empowering the developers with architecting the app and the IT with building a dedicated Container infrastructure platform aligned with company policy and share it’s API back to the developers.

hard

 

There is no right or wrong here!

The top-down approach fits mostly large corporates that need to build a mass scale app to serve billions of users (Facebook, google, amazon) and usually create their own container host flavor and tools to deploy and maintain it.

The bottom-up approach fits organization that needs to adopt containers as a part of a wider team strategy and still needs to maintain company IT policy.
This company usually rely on a standard solution that have a known architecture and full support from the supplier-vendor.

Taking into consideration the virtualization revolution that created a new “Data Center Operating System” to minimize the dependency in the general purpose O/S, we can use the same architecture to help enterprise organization in the transition from the 2nd to the 3rd platform.

grren_brown.png

The first step will be to run containers side by side along with the 2nd generation applications.
Most organization will develop their mobile and internet apps using containers while continue to run the primary and backend applications on 2nd platform solutions.
Doing so it’s crucial for this organization to have a platform that can host 2nd platform apps (monolithic) side by side with 3rd platform apps (microservices)

micro services

VMware’s vSphere Integrated Containers will fill the gap in allowing these two technologies work together on the current most adopted Data Center Operating System known as vSphere:

RUNDOCKER

 

While containers technology and microservices architecture adoption increase in the organization the need to develop a native but trusted platform to run containers arise.

With this to take into consideration, the new bottom app approach architecture will be the most suitable for the enterprise to adopt.

VMware’s Photon Platform is the first enterprise-ready solution based on an industry proof micro-visor and controller utilizing all the experience and knowledge VMware gathered for the last 15 years running enterprise production loads at scale.

photon platform.png

Short for micro-hypervisor.

micro-visor works with the VT (Virtualization Technology) features built into Intel, AMD and other CPUs to create hardware-isolated micro virtual machines (micro-vas) for each task performed by a user that utilizes data originating from an unknown source.
The micro-VMs created by the micro-visor provide a secure environment, isolating user tasks from other tasks, applications, and other systems on the network. Tasks, in this case, entail the computation that takes place within an application as well as within the system kernel, so the micro-visor ensures security at both the application and operating system kernel levels.

Utilizing VMware’s CMP (Cloud Management Platform) NSX and vSAN technologies will assure a production ready containers infrastructure platform that can be managed by the IT systems with proven and known tools while giving the developers the best API access to industry standard containers development systems.

To better understand how this solution help Organization IT to evolve, watch my Cloud Native Apps Demystified Presentation.

aviv-business-tp

 

Aviv Waiss is a Principal Systems Engineer at VMware.
Cloud Management Platform and Cloud Native Apps Specialist.
Member of the CTO Ambassador Program

 

Meet The Developer – EPOPS Agent

vrcs_logo

Picture1

vrops-256

 

As a Part of the collaboration between VMware R&D organization and our customers, we held a unique event where our top Israeli customers met the EPops Agent development team, heard about the technology behind the solution and shared with us their perception and ideas.

 

We got great interaction with the customers, lots of valuable feedback and understanding they’re requirement and challenges, excellent off session conversation about running and future projects.

Here are the event agenda and presenters

Slide2

Some pictures from the session…

Aviv Present the Agenda and logistics

IMG_0650

IMG_0635 2

Hilik Present the Israeli R&D Center.

IMG_0636 2

Ehud present vRops value and mission.

IMG_0645

Noam Present vRops architecture

IMG_0648

Yoav Demo Agent install & O/S monitoring

IMG_0653

IMG_0654

Having fun in the new training center.

IMG_0652

Ehud Demo vCenter and SQL new applications

FullSizeRender

Dan explains how to develop your own solution using EPops agent.

IMG_0661

Plugin development in action !!! Dan simplified new solution development.

IMG_0662

And finally Ronit present product roadmap and future directions

FullSizeRender 2

Thanks to everyone who contributed, submitted and participated in the event!!!

Links to the event presentations:

Session1 – Hilik

Intro to EP ops value – Ehud

EP Ops Arch Overview – Noam

Build your own plugin – Dan

Ronit’s roadmap presentation can be presented one on one to NDA customers.

 

DevOps in the traditional enterprise – a leap ahead​ in release pipeline management.

Software release management is a challenging process for big enterprises.
While most enterprise applications are critical to running the business, most often we see that the process of releasing and updating the application version is painful and inconsistent.
Let’s identify some of the causes of this situation:

Low focus on automation: In most organizations automation efforts are invested in the delivery of virtual machines or shelf applications while the legacy monolithic apps are being pushed and updated in old manual ways.

Large, applications, a big chunk of code: a lot of the organizational apps are built as a big pile of code where every change needs to be heavily evaluated and can have a global effect on the whole app.

Manual QA and test processes: in one of my customer visits, after I raised the question “how are you testing your software? ” I got an answer I didn’t expect: “we are using code blindly and wait for the result from the users,” no efficient and automated way to do QA got them to skip the process to meet the company goals.

Orphaned scripts and workflows: while some departments try to write their own solutions to build and test the code, without proper integration and a base pipeline management system this work is quarantined to the specific department and have a minimal effect on the whole release process.

To achieve better efficiency and control of the release process a change in approach need to be taken.

First, we need to have a central pipeline management system that can host all of our different scripts and workflows that take effect in the release process.
This system needs to be able to connect directly or via API to all the source control, artifact management software, platforms, and infrastructure that is involved in releasing software.

Then we need to build the different pipelines that will be made out of stages (test, QA, staging…) tasks (run scripts, run workflows, get the binaries..) and some gating rules to manage the process (test acceptance result, human approvals…)

And last we need to expose these pipelines as managed services to the development organization.
This is the most essential part as the ability to run any pipeline in a click of a button and be able to see it running is the game changer for developers that can now build code more often while maintaining the reliability of the company software.
Visualizing and versioning the pipeline runtimes is also a massive leap as we can now expose every part of the software lifecycle to any stakeholder in the organization that doesn’t understand complex scripts or workflows.

To conclude; DevOps thinking and strategy in a traditional enterprise can have a significant effect on the business software reliability, thus helping the organization to evolve faster and step up the pace in the fast-changing world.

Pipeline as a service is a feature of VMware Cloud Automation services.
For more info click https://cloud.vmware.com/cloud-automation-services

 

 

Latest announsments from VMworld US 2014

Here is a summary of what was announced in San Francisco 2014…

EVO-RAIL:
Previously called Marvin in the press, this Hyper-converged infrastructure appliance is designed by VMware and built/sold by hardware vendors providing EVO: RAIL compatible hardware with VMware software on top. Purpose: SMB customers, ready in 15 min, scalable and complete in 1 SKU Competition: Nutanix, Simplivity, Scale Computing, Maxta,…EVO: RAIL Software included: vSphere Enterprise Plus & ESXi, vCenter Server, VMware VSAN, EVO: RAIL management GUI & vCenter Log InsightHardware specifications:

  • 2U 4-nodes hardware platform optimized for EVO:RAIL and provided by selected OEM partners.
  • Dual CPU sockets.
  • Memory: Up to 192 Gb
  • 16 Tb of storage on VSAN (HDDs & Flash)
  • Automated Scale-Out up to 4 nodes (HCIAs), that can support up to 400 server VMs or 1 000 VDI VMs

1st OEMs announcing EVO:RAIL HCIA: EMC, Fujitsu, Dell & SuperMicro

vCloud Suite v5.8:

  • Improved business continuity & disaster recovery.
  • improved SRM integration with vCAC, SRM can be now offered as a Service in vCAC’s self-service portal

vCloud Automation Center 6.1 is announced

  • Enhanced next-gen apps, such as Big Data Extensions for Hadoop 2.
  • Improved interoperability with NSX.
  • New proactive support: free Support Assistant vCenter plug-in.

vSphere 6.0: (beta)

  • Fault Tolerance will support 4 CPUs
  • Cross vCenter vMotion support
  • Long distance vMotion is enhanced
  • Using NSX, network properties now be kept on long distance vMotion
  • Openstack VIO (VMware Integrated Openstack, Beta) A standard Openstack in virtual appliance (OVA) that makes it easy for IT to run an enterprise-grade OpenStack on top of their existing VMware infrastructure.

VMware vRealizeTM:
vCenter Management family products are renamed under vRealizeTM brand
vRealizeTM Suite is a Cloud Management Platform Suite

  • vRealize Operations Insight: add-on for vSphere with Operations Management (vSOM)
  • vRealize Air: SaaS offering for vCloud Automation Center
  • vRealize Suite: Complete set of VMware management products

Rebranding examples: vCloud Automation Center (vCAC) = vRealize Automation & vCenter Orchestrator (vCO) = vRealize Orchestrator…
vRealize Suite is the next step in the evolution of VMware’s cloud management family, shifting from a product to a platform strategy

End-User Computing:

  • VMware, NVIDIA & Google agreement for Graphics-Rich Applications.
  • VMware and SAP Collaborate around Mobile Security & Mobile Apps.
  • Workspace Suite: Mobile, Desktop and Content Management unified.
  • New Horizon DaaS Services and Expansion to Europe

vCloud Air (formerly vCHS):
In addition to existing IaaS, DaaS and DRaaS offering (see vCloud AirTM OnePager), VMware announced new services:

  • DevOps as a service
  • DBaaS: MS SQL and MySQL first. Other DB platforms will follow.
  • Object based storage (based on ViPR): extremely scalable, cost
  • effective, and durable storage for unstructured data.
  • Mobility Services:
    • with AirWatch: mobility management, mobile app develop…
    • with Pivotal CF Mobile Services.
  • PaaS : based on Pivotal CF
  • Cloud Management as a Service: vRealize Cloud Air Resources: