Hybrid Cloud Models Platf Cloud Native

Introduction to Dell EMC Converged Systems and Hybrid Cloud Platforms for Digital and IT Transformation
Hybrid Cloud Models

Hybrid cloud models, platforms, and cloud native application development
In this section, let’s talk about hybrid cloud models and the value they can create for a business.
Hybrid Cloud Models, Platforms, and Cloud Native Application Development 1

Copyright © 2017 Dell Inc.
Hybrid cloud models
Why does any business need a hybrid cloud, what is it good for, and why is it important? Think for a moment about technology and computers.
The technology, such as compute, network, and storage, produce no direct business value.
Even together as a whole, they provide little significance without the applications they support.
Applications, together with the technologies and environments that support them, are the central point of importance and value.
Now, because converged infrastructure, hyper-converged infrastructure, and cloud computing technologies can provide huge efficiencies in
creating and maintaining technology, IT can devote more time, energy and budget focused on optimizing the application development and the
operational environments.
We’ll start this section with a conversation about the changing business technology investment cycle as well as the value of the hybrid cloud and
the significance of its variants.

Learning objectives
Upon completion of this training you will be able to explain how and why hybrid cloud models are valuable. Describe what is a hybrid cloud
offering and its technologies. You will be able to describe how a hybrid cloud empowers businesses with its features. Describe Cloud Native
Application development platforms, what they offer, and their technologies. And you will be able to describe how Pivotal Cloud Foundry supports
application development on Cloud Native Application development platforms.

Hybrid cloud models
Before we are done with this section, these are the topics we will discuss. First, we’ll address the changing business technology investment cycle.
This lesson will provide insight on Hybrid Could Models and the importance these models can provide to a business.

New business investment cycle
For digital transformation to succeed, one approach is to provide a larger budget to the IT department.
Another way is to find ways to meet its IT needs by increasing efficiency on day-to-day operations. This approach can provide greater time, effort,
and budget for strategic issues that add significant value. This value is derived through optimized application development and the operational
environments.
By improving the operation and maintenance of their traditional applications, IT teams can shift resources towards a new set of investments, and
create a better balance of managing old applications and investing in new ones. This also includes the development of new smarter cloud-native
applications built to deliver new mobile experiences, better data analytics, and deeper digital innovation for the products and services they provide.
But in doing this, IT executives face a complex set of initiatives. One is creating efficiencies in traditional applications and the other focused on
driving innovation and new application models.
The dilemma that exists between modernizing as rapidly as possible, without starving core business applications, is a challenge for most
companies.

Hybrid cloud and digital business prowess
According to an IDG global survey of 905 IT executives, the connection between hybrid cloud and digital business proficiency is considerable. The
study revealed that companies globally, that aggressively adopted a hybrid cloud model, are three times more likely than non-adopters to
achieving their digital business and infrastructure readiness goals. Some of the key findings are:
88% view hybrid cloud as important or critical to enabling digital business transformation
78% of the survey participants agreed that hybrid cloud models speed IT delivery
76% agreed that hybrid cloud positions the organization to be more agile and innovative
24% is the average IT cost savings realized from hybrid cloud
The IDG Research Services surveys suggest the single most significant finding is that the businesses that are furthest along in hybrid cloud
adoption are collecting dramatically richer benefits.
This proves that the further companies go with hybrid cloud investments, the more they get from them.
Respondents with a significant number of workloads via hybrid cloud are experiencing nearly fifty percent more IT cost reduction than those with
just some hybrid cloud workloads. They’re also reinvesting over 10 percent more of their savings in innovation and are over five times more likely
to say their hybrid cloud environment is exceeding expectations.
The most aggressive hybrid cloud adopters are also the most advanced at digital transformation. Organizations with a significant number of hybrid
cloud workloads are three times more likely than non-adopters to be approaching their digital business and infrastructure readiness goals.

Challenge to digital transformation…
The challenge is that 71% of IT budgets go to managing existing applications. Traditional applications are expensive to maintain, leaving little
funding for innovation. How can we get this under control? How can we become more efficient with the demand for IT resources needed to
support traditional applications?
2017 US Tech Budgets: The Outlook for Tech Spending Overall and By Industry
Steady US Economic Growth and The BT Agenda Will Drive 5% Tech Market Growth In 2017
October 17, 2016 | Updated November 4, 2016

Value of a hybrid cloud model
For many, one of the key benefits a hybrid cloud provides is the security and control of an on-premises deployment with the rapid elasticity of an
off-premises cloud. In addition, capabilities include on-demand, self-service provisioning of resources, resource pooling, and the ability to measure
services for capacity planning.
All contribute to helping organizations become more agile while ensuring that their investments are providing a positive ROI.
.

Hybrid cloud methods
A hybrid cloud can support many different services, features and capabilities. The right type of cloud to deploy depends on the application
workloads that will run in that cloud. We will look at two high-level categories of hybrid clouds.
The first is an Infrastructure as a Service (IaaS) hybrid cloud. In an Infrastructure as a Service model, the components of the hardware
infrastructure are managed by the IT department or a service provider. This includes the compute, network, storage and virtualization technologies.
In many cases now, even standardized operating system templates are provided. Consumers, or those that are deploying services in the cloud,
can then manage the virtual server in accordance with company guidelines.
In contrast to IaaS clouds, Platform as a Service (PaaS) clouds focus above the infrastructure layer. Typically used for cloud native applications,
PaaS hybrid clouds provide an environment to accelerate application development and deployment. These environments take advantage of
standardized infrastructure and tools, automation capabilities, and all of the other aspects of the IaaS layer, allowing developers to focus on the
applications.
In the next couple of sections, we’ll take a closer look at each.

Hybrid clouds
First let’s explore the benefits a Hybrid Cloud can offer.

Hybrid Clouds can provide Infrastructure as a Service (IaaS) with automated self-service provisioning that combines the control, reliability and
confidence of private cloud with the simplicity, flexibility and cost efficiency of a public cloud.
Remember what Infrastructure as a Service is? In the Infrastructure as a Service model, the components of the hardware infrastructure are
provided and managed by the service provider. This includes compute, network and storage technology, as well as virtualization technology. The
customer supplies and manages the rest of the stack, including middleware and applications.

Accelerating IT transformation
Hybrid Clouds help accelerate an organization’s path toward IT Transformation by addressing three key objectives:
• Increasing agility allowing faster response to opportunities
• Changing the way IT operates and adds value to the business, and by
• Reducing the cost of day-to-day IT operations for traditional applications
This is accomplished by:
• Empowering users through on-demand, self-service access to IT resources
• Automating delivery of virtual infrastructure and traditional enterprise applications through orchestration and/or automation tools
• Providing monitoring and reporting capabilities that enable visibility into foundational components and cloud workloads
• Offering built-in security and data protection options so customers can run their infrastructure and applications with confidence.

Cloud native application development platform
The value of a Cloud Native Application development platform solution is the ability to rapidly and continuously deliver new, innovative and unique
experiences and capabilities to customers via applications, which for many, has become a requirement for business success.
To meet customer expectations, startups and enterprises alike, they are embracing development models that allow them to rapidly deliver
applications through iterative development cycles of short duration. This constant development-feedback cycle enables companies to react to
shifting demands and focus on meeting and exceeding consumer demands.

Makes the leap to cloud native easy
A Cloud Native Hybrid solution delivers all the advantages of an IaaS hybrid cloud, but instead of providing IaaS services, it focuses on Platform
as a Service (Paas) capabilities. Recall that with Platform as a Service, the service provider supplies both the hardware infrastructure as well as
the components of the programming environment, while the customer brings their application and data. For example, Pivotal Cloud Foundry can
provide a programming environment as well as a means of pushing applications into production using a Cloud Native Application development
platform infrastructure.
Cloud-native applications are designed to run and scale reliably and predictably in cloud environments, purposefully de-coupled from the
infrastructure and free to move as required. Cloud-native application architectures balance the need to move rapidly without sacrificing stability,
availability and durability.
Cloud native applications leverage key technologies and processes such as microservices, continuous delivery, containers, and DevOps. You will
learn more about these and their benefits later in this module.

Allows DevOps set you free
Companies making the transition to this cloud-native framework are seeing the results. Based on a survey that Puppet did with over 4,600 IT
professionals they observed that DevOps is helping their companies tremendously. DevOps is a software development and operations culture that
breaks down traditional silos with a focus on communication, collaboration, integration, automation and measurement of cooperation between all
functions required to deploy and run applications. Based on a study conducted by Puppet Labs and DevOps Research, it is observed that high
performing companies that have implemented a DevOps methodology have seen the following benefits.
They can recover 24 times faster from failures than their peers who do not have DevOps. This is a result of efficiencies and standardizations that
the companies have developed. It is also a function of the DevOps culture in which people, process and technology work towards the same goal.
DevOps based companies can deploy 200 times more deployments than the companies who do not. With the cloud-native approach to DevOps,
companies can deliver higher quality work at a faster time to market. Without it, companies can struggle with a silo culture which affects
efficiencies, collaboration and integration.
With adoption of DevOps companies can focus on developing new applications more than their peers.
According to IDC “DevOps helps organizations achieve greater IT speed and, thus faster achievement of business goals.”
Source: IDC Pivotal white paper: A Roadmap to Agility <https://content.pivotal.io/white-papers/a-roadmap-to-agility>

Hybrid cloud models
In this section of the training, we will focus on details of hybrid cloud solutions.

Hybrid cloud models
IT organizations world-wide are faced with the reality that they must transform their organization and technology to take advantage of cloud
platforms. Businesses are focusing on digital transformation, attempting to create or stave off disruptive services and technologies and gain an
edge in the market. Lines of businesses are looking to get their ideas to market faster and require IT to be agile, flexible, and cost effective.
Cloud solutions help organizations realize their goals faster than before. Public cloud solutions offer speed and utilitarian cost models, while
private clouds afford control, known security, and customization. A hybrid cloud offers the best of both worlds, supporting new business ventures
while allowing the business to maintain and accelerate day-to-day business operations.
A hybrid cloud provides an integrated solution designed to deliver scale, data protection, security, and control, with services to support line of
businesses. A focus on its features and technologies will provide an overview of the benefits that a hybrid cloud provides. It empowers businesses
to act and move quickly in a rapidly changing environment. Customers have been adopting the cloud and are seeing an average of 67% savings
over 3 years of use, a 42% savings in upgrades and maintenance, along with an increased ability to reinvest savings back into IT to spearhead
innovative efforts.

Hybrid cloud
As the name suggests, a hybrid cloud provides a mechanism to utilize the benefits of both a private and public cloud for a wide variety of
workloads and applications, ranging from mission-critical to general purpose apps. The hybrid cloud is meant to be agile, simple, and secure.
A hybrid cloud combines the cost efficiency, flexibility, and simplicity of a public cloud with the control, reliability, and security of a private cloud. It
delivers these features over public and private cloud assets, allowing businesses to take advantage of the hybrid cloud, while reducing the risks
often seen with implementing solutions on a public cloud infrastructure.

Hybrid clouds
A hybrid cloud is designed to quickly deliver value to the business with a small deployment window and allow the business to adapt to changing
needs by offering great speed and agility to support the varying workloads and the growing business. The solution brings IT resources to the
forefront, allowing lines of businesses to quickly access streamlined and automated resources to support their business needs.
It is often a pre-configured, integrated, and tested solution incorporating components to provide a scalable and virtualized architecture to support
demanding needs. It offers security at various levels of the environment, starting with underlying infrastructure support protocols, to VM encryption,
and provides tools and management for control and visibility of services and consumption, allowing administrators to isolate environments to
protect consumers.
Using an underlying converged or hyper-converged infrastructure, it integrates platform services that deliver IT-as-a-Service with lifecycle
management, VM protection, automated services, and a self-service catalog to provide cloud services within the organization.

Infrastructure layer
Let’s look at some of the specifics of a typical hybrid cloud.

Hybrid clouds are often an engineered solution that consists of an underlying infrastructure and cloud management service. It integrates platform
services that deliver IT-as-a-Service with lifecycle management, VM protection, automated services, and a self-service portal to support cloud
services within the organization. It can deliver infrastructure-as-a-service across one or more datacenters containing multiple infrastructure
systems. Expanding the capabilities of the system to include software defined services and business continuity services allow IT to deliver ITaaS
capabilities to end users.
The infrastructure layer can consist of converged and hyper-converged solutions. For example, Dell EMC’s VxBlock, VxRack systems, and VxRail
appliances are infrastructure platforms that enable a scalable and robust cloud infrastructure. Storage options can include storage arrays such as
VMAX and XtremIO, or software defined storage such as ScaleIO and VSAN. Disaster recovery and continuous availability can also be
implemented using various technologies.
A converged infrastructure allows a hybrid cloud to be deployed faster, while allowing customers to customize their solution using a variety of
tested components. Maintenance spend and vendor management can also be reduced as the solution is supported by appropriate vendors to
maintain the solution. This leads to a reduced total cost of ownership, allowing the business to focus on higher value goals.

Virtualization and control layer
The virtualization and control layer can incorporate the components that support the infrastructure as a layer. For example, a solution can have the
following components:
• VMware vCenter and VMware ESXi that can provide virtualization and VM management services.
• VMware NSX offers network virtualization and security to the solution, supporting software defined data services, a feature which further enables
delivery of automated services to the upper layers.
Virtualization and the realization of software defined services lets organizations make more efficient use of resources, pooling together workloads
based on requirements, and scaling infrastructure resources accordingly.

Cloud management and orchestration
At the top layer of a typical hybrid cloud solution, the VMware vRealize Suite can provide the cloud management services. It includes software to
support automation of services, operations management, log management and analysis, and cost management, metering, and pricing. The result
of automation is increased agility with an accelerated time-to-value. IT also provides a reduction in operational expenditures because fewer
resources are required to directly manage deployments. Governance rules can also be applied consistently across the board as business rules are
applied to workflows that support these processes.

Additional add-ons
In addition, a hybrid cloud solution can include a series of products and solutions that offer security, availability, and management. They include:
• VM security through CloudLink SecureVM
• Backup and recovery services with Avamar and Data Domain
• Storage reporting and analytics with ViPR SRM and Dell EMC Storage Advisor
• Availability and disaster recovery services through VPLEX, RecoverPoint, and Site Recovery Manager

Hybrid cloud benefits
Now let’s discuss how a hybrid cloud solution can provide agility. A hybrid cloud improves efficiencies, starting with the time to deploy, upgrade,
and maintain services. It allows IT to maintain flexibility, agility, and transparency so that the business can quickly see the value it gets, while IT
can continuously adjust to changing needs.
Access to deploy applications and networking is provided through the self-service catalog. Underlying services are automated to support the on-
demand services provided through the catalog. Users can select various offerings to meet their needs as well as the service level based on their
requirements. VMs, users, and data are protected with a combination of VM encryption, backup services, disaster recovery, and attributes to limit
the scope of what users can see and access.
IT maintains visibility and control of the solution with a dashboard that provides consumption rates down to the application level while offering
show back information to the customer, allowing them to easily determine the value for services consumed. To control costs and manage growth
and changes in the business requirements, IT can scale resources up or down.

Self-service access to traditional enterprise applications
Users can utilize application templates to provision application instances of SAP, Oracle Database services, and Microsoft applications.
These may be mission-critical applications that normally reside on-premises and can be difficult to manage or maintain. Using a hybrid cloud
enables the applications to be run securely on-premises or off-premises, with underlying and integrated automated services to support the
application.
As part of the cloud services provisioning process, various service levels provide end-users access to applications with active-active provisioning
and data protection options, such as backup, recovery, and continuous availability.
Users can maintain control of their deployed applications as they are able to scale out their VMs, by managing memory, processor, and storage
requirements.

IT services via a self-service catalog
Automated services can be managed through the self-service catalog, providing administrators access to IT resources within the infrastructure
layer. Some examples of services that can be enabled through the catalog are:
• Data protection through backup as a service to protect deployed virtual machines
• Disaster recovery services to reduce downtime associated with lost data
• Virtual machine encryption services to protect applications and virtual machines
• Application templates and lifecycle automation and management
• IP address management and service management frameworks
Administrators can manage application and service templates, allowing the application and resources to be easily replicated to different
environments. The environment can be scaled up or scaled down, based on workload requirements, providing administrators a level of control
often difficult to attain outside of cloud-managed environments.
Centralized logging tools are essential to maintaining the overall health of the Hybrid cloud. Products such as VMware vRealize Log Insight
facilitate the aggregation of logs from all layers of the cloud infrastructure, as well as applications, providing a single repository of information.

Data protection services
Now let’s discuss security as it applies to creating a robust hybrid cloud. Protection services can include backup and restore, continuous
availability, and disaster recovery. Some options for protection are listed here.
• Continuous availability offers compute and storage resiliency within a site or across sites
• Disaster recovery products replicate applications, at the infrastructure level, to another cloud in the same or different location, enabling the rapid
recovery of workloads
• Backups can be replicated locally or at a different location to provide operational recovery or facilitate disaster recovery

VM security services
One can use CloudLink SecureVM to provide security to VM’s. Consumers can apply portable encryption through various security service levels to
applications and virtual machines.
Virtual machine data can be encrypted when applications and workloads are provisioned from the self-service catalog. The encryption method
utilized is agnostic to the underlying platform, allowing the VM to maintain its encryption while being migrated securely across public and private
clouds.
The encryption key used to secure the VM is stored within CloudLink Center, a virtual appliance that provides key management interoperability
integration for compatible clients and manages both the encryption keys and the security policies that safeguard the VM.
Both consumers and administrators can apply encryption services to VMs. Consumers apply encryption services to their VM workloads, while
administrators can define security policies that apply encryption to VM workloads based on where they are deployed.

Increased visibility to infrastructure consumption and cost transparency
Chargeback/Showback tools provide insight into consumption of infrastructure resources. This in turn delivers financial transparency by allowing
consumers to directly view the cost for the services they are provisioning.
vRealize Business for Cloud provides financial reporting and management operations to administrators. It provides detailed accounting of cloud
resource consumption costs that can be used for consumption and chargeback reports.
The tool provides an infrastructure overview section which displays the number of VMs across all managed sites. A datacenter view lets you see
how compute, storage, and memory resources are being utilized in various datacenters managed by the solution.

Implementation examples
These features offer compelling reasons for deploying a hybrid cloud addressing challenges around a lack of a cloud-business focused strategy,
the need to transform an existing IT organization’s data centers, or managing the impact of high growth of an organization.
In the first example, a company experienced challenges with their IT organization’s inability to support business initiatives effectively. IT was
increasingly facing pressure to show its value to the business, both in what they could deliver to the business and the costs of those services. An
ineffective IT organization needs to contend with lost business as lines of business have more opportunities to directly access cloud vendors who
meet their requirements.
IT realized it’s needed to offer IT as a Service in order to better align with the business, taking advantage of the benefits, including cost
transparency and reporting, providing services through a self-service catalog, and supporting these services with automation to reduce the
operational load on IT.
A hybrid cloud was chosen and deployed. The solution gave the business’ customers the ability to quickly provision virtual machines in support of
their business efforts. They used the cost model and reporting features within the Hybrid Cloud to ensure the pricing model was consistent with the
business’ overall finances and to provide consumption reports to participating business units. Combined with the idea that the solution is fully
supported throughout, the savings on operational costs and time, allowed the business to reinvest in higher value tasks with strategic values.

The ability to enter the increasingly crowded applications marketplace means businesses need to have a strategy for quickly developing, testing,
and deploying applications. The move to the third platform lets businesses create mobile applications that can reach and support millions of
consumers and allow IT to effectively manage the lifecycle of that application with no interruptions.
In this example, a business needed to enter the marketplace to take advantage of new market opportunities and revenue streams. The business
was looking to create and deliver services to the marketplace much faster than they had before to keep up with the pace of technological changes.
The advent of the digital era has forced companies to reevaluate their approach to their application strategy.
IT was not in a position to deliver support quickly, so they chose to implement a hybrid cloud to address the business’ challenges.
Deploying a Hybrid Cloud allowed the business to bring services to the marketplace ahead of their competitors because they were able to build,
test, and deploy within the platform. Automatic provisioning provided readily available services, removing the manual engagement process, and
allowing consumers to directly access necessary services. Reducing the time spent in maintenance and manual tasks allowed IT to free up its
resources to focus on innovative solutions.
Overall, the customer experienced a 90% reduction in overall downtimes, increased performance along with the ability to scale to maintain
performance or growth, and a 50% reduction in data center costs.

IT’s inability to handle a rapidly growing organization strains data center, people, and monetary resources. It can be more difficult where you have
organic growth within the organization, where the lines of businesses are all operating under their own set of rules.
The business, in this example, constantly faced scaling issues while undergoing tremendous organic growth. Their system availability was at 96%,
while backup success was 82%. The lifecycle management was difficult to support in this environment, while the rapid growth strained storage
requirements and made compliance difficult to attain within a shorter period of time. The business was struggling from issues around timeliness
and scalability.
Implementing hybrid cloud dramatically improved operational and consumer tasks, with server deployments going from 12 days to 8 minutes.
Backups now went from 5 days to 4 hours, taking advantage of the infrastructure and the Hybrid Cloud architecture best practices for improving
backup and recovery times.
The business saw huge cost savings, allowing them to forecast a reduction in the amount of time needed to pay back on their investment.

Hybrid cloud models
Now let’s learn about Cloud Native Application development platforms.

Hybrid Cloud Models
Software is having a profound impact, forcing businesses to reevaluate their strategy to address digital transformation. Intelligent applications are
now the face of business, where applications deliver real-time, relevant, and personalized information directly to the consumer. Expectations for
new applications today is that they available anywhere, anytime, and on any device.
A challenge for businesses today is industry uncertainty. Including indecision about directions of their industry, doubt about where their industry
will be in several years, or even uncertainty regarding who will be competitors in their industry in the future.
All this uncertainty is forcing companies to find ways of enabling their business units to address and deal with uncertainty by developing, delivering
and managing strategic applications.
Cloud Native Application development platforms provides a venue that delivers cloud-native applications quickly and efficiently, helping to speed
the development to release timeframes. The features delivered by Cloud Native Application development platforms empower IT to work with
business units to quickly innovate and accelerate to business value.
Pivotal Cloud Foundry is an example that provides a development and operational platform to deploy, run, and scale applications. It delivers
platform-as-a-service and provides a foundation for cloud native applications, allowing developers to focus on building the application, and not on
operational activities meant for creating a system and environment for application development activities.
Companies have made great progress in quickly deploying an environment and capitalizing on the speed to market. We will discuss these
technologies and talk about how they enable companies to quickly build, modify, and deploy applications through a self-service environment.

Cloud native application development platforms
Cloud Native Application development platforms are developer and operations focused that combines an engineered infrastructure layer, a
platform-as-a-service layer, and a growing number of applications and developer tools in a single, turnkey solution. It is quite often purpose built to
allow businesses to:
• Innovate faster than before by allowing businesses to accelerate their application development to deployment lifecycle
• Empower developers with a platform and suite of tools that allows them to quickly build, test, deploy, and manage their applications with little to
no concern of the underlying infrastructure and middleware components
• Accelerate deployment of an infrastructure and time to market by allowing IT to quickly deliver a solution that supports digital transformation.
A Cloud Native Application development platform provides an on-premises solution with the ability to connect to a variety of external vendors to
provide and integrate with other off-premises solutions. The platform should allow businesses to re-evaluate their build versus buy model as their
capabilities to build cloud-native applications to address their target markets increase with this solution offering.

Addressing the Software Development Supply Chain Problem
Cloud native application development platforms are designed to address the challenges of two main customers or personas: developers and IT
operations.
Developers and their associated lines of businesses are looking to deploy and access resources as quickly as possible, minimize their setup and
configuration routine, and move quickly to build, deploy, and manage or maintain applications.
IT Operations are looking to support their customers, the lines of businesses, but must continue to maintain control of the infrastructure and the
platform. They are responsible for deploying and configuring the platform to support a growing roadmap of tools for the end users. They must also
maintain visibility and control of the infrastructure and platform, while allowing end users to access capabilities that let them obtain infrastructure
resources. The initial deployment of a native cloud solution can be daunting with a great deal of challenges, including lack of knowledge,
budgeting, and resource allocation.
Cloud native application development platform solution vendors can provide a Professional Services engagement in which the solution is deployed
and configured. Day 2 operations, which include designing the overall system operations to meet business requirements and derive benefits,
includes activities such as enabling billing, setting up backup and recovery operations, and engage with system and solution monitoring and
reports.
Let us now take a look at examples of possible solution components.

Native Hybrid Cloud Architecture – Infrastructure Layer
Cloud native application development platforms should be engineered and integrated offering an easier and more cost-effective way of
establishing a hybrid cloud platform. The integrated solution means IT does not have to assemble its own set of components and perform
individual testing to ensure the platform supports the business need.
For example, a solution can support VMware vSphere delivered on VxRail, taking advantage of the hyper-converged infrastructure as it provides
software-defined storage integrated with VMware vSAN. The solution is scalable, allowing IT to start small and scale up as needed. VMware vSAN
pools storage from multiple VxRail systems into an accessible and manageable resource.
In addition to the hyper-converged infrastructure, cloud native application development platforms can also support elastic cloud storage, an object
store that acts as an app data storage platform for cloud native application development platforms. It acts as the binary large object store, or blob
store, for the platform, in that it is capable of storing images, audio, multimedia objects, and binary executable code. It delivers features such as
high availability and fault tolerance to protect the data generated by applications within the solution.

Native Hybrid Cloud Architecture – Platform Layer
For example, the platform layer can be serviced by Pivotal Cloud Foundry, providing a cloud-native development platform that incorporates a
number of tools for developing and managing applications. Pivotal Cloud Foundry integrates into the solution, accessing the infrastructure through
VMware. Pivotal Components themselves run as VM images within the solution.
Pivotal Ops Manager is central to the Pivotal Cloud Foundry deployment and management. It provides a web interface used for managing the
platform, allowing administrators to add and remove products available to end users, manage resources, manage the elastic runtime environment,
make configuration changes to the environment, access Pivotal Cloud Foundry logs and monitor the environment, and manage accounts within
Pivotal Cloud Foundry.
Pivotal Ops Manager Director is an orchestration and configuration component for Pivotal Cloud Foundry. It allows you to configure integration
points to VMware vCenter, Microsoft Azure, Amazon Web Services, Google Cloud Platform, and OpenStack, as well as to other services, such as
DNS and NTP. This is the manner in which Pivotal Cloud Foundry integrates with VMware in various Cloud Native Application development
platforms.
Elastic Runtime provides the runtime environment for Pivotal Cloud Foundry. It hosts running applications, manages system health, and provides
the application programming interface endpoint and cloud controller for virtual machines provisioned by Pivotal Operations Manager.
Pivotal Ops Metrics, now known as JMX Bridge, is a Java Management Extensions tool for Elastic Runtime. It collects and exposes platform
metric data using an onboard JMX endpoint. A JMX endpoint is used to collect data from the component on which it is installed. Pivotal Ops
Metrics helps administrators monitor the health and performance of Pivotal Cloud Foundry and its applications.

Cloud native application development platforms - driving towards innovation
Cloud native application development platforms seek to address an organization’s challenges around embracing and capitalizing on cloud-native
applications. The software development through deployment cycle needs to be faster, support development frameworks, give users control,
engage various delivery end points, and do this all on a secure and robust platform.
Cloud native application development platforms can deliver a turnkey, developer-ready solution that can for example, incorporate technologies
from Pivotal, VMware, and Dell, which quickly delivers value for IT supporting their customers. A Cloud Native Application development platform
delivers IaaS features for on and off-premises deployment, while incorporating Pivotal Cloud Foundry to deliver Platform as a Service features.
Developers maintain control of their workspaces and development lifecycle with numerous self-service functionalities. The platform delivers
access to underlying infrastructure, so that developers and LOBs are not constrained by unnecessary manual intervention between themselves
and IT. They can quickly move forward with self-supporting features to quickly develop and release projects.
Multi-cloud support often requires maintaining multiple infrastructures. Cloud native application development platforms with Pivotal eliminates that,
by not only providing services that support public and private cloud deployments under a single management structure, but also give developers
the ability to deploy to multiple cloud environments.
Integrated tools and services for backup and recovery, high availability, and security lets IT deliver a truly robust, highly available, and secure
environment to maximize uptime, reduce maintenance and update timeframe, and integrate security features that persist at the application layer.

Cloud native development
Cloud native application development platforms can provide a cloud-native development environment, supporting development efforts to help
customers bring cloud native applications to market more quickly. A cloud native development environment provides support to four main
concepts to enable rapid application development and deployment. These include a DevOps framework, continuous delivery, microservices, and
containers.
Click on each of these to learn more.

DevOps:
DevOps stands for development and operations, and in this case, it refers to the application development and operations functions within an
organization. The DevOps framework removes the barriers among roles of developers, quality assurance, and operations. This enables a
smoother transition among functions with the goal of delivering a higher quality product that meets the customers’ needs.
By removing the barriers among the teams, building, testing, and operationalizing applications becomes a faster and smoother process. This
enables another aspect seen in cloud-native application development: Agile development. Agile development encourages delivery of smaller
applications in a shorter timeframe. This ties in well with continuous delivery.

Continuous delivery:
Continuous delivery is a software engineering process that uses short development cycles to produce new releases and get them into the hands
of users, safely and quickly in a sustainable way.
Think about it this way, traditionally, new releases of applications are large releases with many fixes and improvements to the application. It was
not uncommon for popular applications to receive major releases once or twice a year or less. But, if new releases of applications provide changes
and improvements that make using it more valuable to customers and users than previous releases, isn't it a good thing to get those
improvements into users hands more quickly? Won't it be more valuable if users can reap the benefits sooner rather than later?
With continuous delivery, software releases that are in development are always in a deployable state. Meaning that at any time during
development, a version of the application can be released to users with improvements that produce value for customers, even if they are just small
improvements. Anytime improved software gets in the hands of users it adds value.
The goal of continuous delivery is to build, test, and release software faster and more frequently. This approach helps reduce the cost, time, and
risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment
process is important for continuous delivery.

Microservices:
A microservice is a discrete modular software object, used as part of an application. An application can consist of several of many microservices.
Think of a microservice as fully deployable and independent software object used by the application it resides in to execute a specific function, like
directions to retrieve some data, or to execute some operation or set of operations the application requires. It is an integral part of developing
cloud-native apps, in that it moves developers from the concept of developing large monolithic applications with a large number of dependencies,
to discrete functions.
A single large application is more difficult to develop, debug, and maintain. A Microservices architecture allow you to parallelize development
efforts, choose appropriate development tools for each microservice, quickly debug services because they are smaller and more focused on a
specific function, and maintain or upgrade the microservice as needed.
Microservices architectures also encourages an application programming interface (API) first design, in which an organization looks at designing
the API before designing and developing applications. An API-first approach defines structures, protocols, and tools that developer’s use when
building application software to define methods of communications between various software components. The use of microservices and API-first
approach encourages a loosely coupled design that addresses multiple devices or interfaces.

Containers:
Containers are used to provide a standardized executable package for an application. It includes components that the application needs to
execute, including code, runtime tools, system libraries, and settings, and it is delivered on a Linux or Windows operating system.
Multiple containers can share the same operating system. Using containers ensures that the application it contains will run the same in all
deployments, no matter what the underlying environment. Because the container holds everything the application needs in order to execute
correctly. It does not rely on the environment to have the run time tools, system libraries, settings and other components needed to execute the
application. This removes issues that occur when creating an application in one environment and then having to deploy it to another.

Cloud native application development platform
These types of platforms delivers on the characteristics that support cloud native application development with the following:
• An emphasis on DevOps meant to address the cultural shift to facilitate a faster and continuous development through delivery cycle.
• Continuous delivery used to automate and speed the software development lifecycle with the end result of a high quality application that meets
the consumer’s needs.
Microservices architecture to provide a suite of discrete, deployable chunks instead of as a monolithic application.
• Containers to deploy applications to the cloud, which can then be managed both by Pivotal Cloud Foundry and affected by configurations defined
by the end user. Containers ensure the application will execute in the same manner every time and everywhere.
• In keeping with the theme of DevOps culture and continuous delivery, a cloud native development platform should be able to support build, test,
and deployment of applications to speed time to delivery.
It also delivers services above and beyond platform services, including added resiliency, log aggregation, user management services, and security
to protect data and applications. And lastly, the platform requires an infrastructure to support the platform. The infrastructure should itself be
reliable and scalable, allowing administrators to more easily provision resources, and developers and end users to access these resources.

Pivotal Cloud Foundry integration
Pivotal Cloud Foundry can be integrated into cloud native application development platforms, providing platform-as-a-service features atop
infrastructure-as-a-service. Developers gain access to a production ready application container runtime, Pivotal Cloud Foundry, and fully
automated service deployments. Operations can scale and manage applications easily through Pivotal Cloud Foundry, increasing resources as
demand on the application increases, or reducing resources during lower periods of use.
Pivotal Cloud Foundry lets developers develop for multiple application cloud platforms, including Amazon Web Services, Google Compute Engine,
Microsoft Azure, VMware vSphere, and OpenStack. Developers build using the cloud-native development methodology, 12-factor app, to ensure
applications are discrete, portable, and configurable..

Twelve-Factor App
Building cloud-native applications includes a focus on an application development manifesto known as 12-Factor app. 12-Factor App encourages
good coding behavior by providing guidelines that can be followed for building cloud-native applications. The manifesto consists of 12 factors used
to guide software development. The manifesto is often used to allow for scalability, minimal maintenance, and ease of updates.
The 12 factors within this methodology include:
• Codebase, where a single codebase is tracked in revision control with many deploys.
• Dependencies, where dependencies are explicitly declared and isolated
• Configuration, where configuration is stored in the environment
• Backing services, where backing services are treated as if they were attached resources
• Build, release, run, which strictly separates build and run stages
• Processes, where an app is executed as one or more stateless processes
• Port binding, where services are exposed through port binding

• Concurrency, where you can scale out using the process model
• Disposability, where fast startup and graceful shutdown are used to maximize robustness for the app
• Dev/prod parity, in which development, staging, and production are kept as similar as possible
• Logs, where logs are treated as event streams
• Admin processes, where administrative and management tasks are executed as one-off processes

Pivotal Cloud Foundry architecture
The application framework provides the base set of tools and runtime dependencies to address developers’ needs. The integration of tools and
services to support microservice development, operations, and security, along with configuration and registry services, and circuit breaker
dashboard to provide robust fallback service for failing services provides enterprise-level services for the environment.
Platform services available through the runtime and accessible by developers and IT, support underlying development activities and administrative
tasks. This also allows access to services, such as data services, object store, and user-developed services.
The platform lets you scale and run applications in-flight, ensuring a more positive experience for end users with little delay in addressing changing
needs. Logging, monitoring, and configuration are now in the developer’s hands, allowing them to take more control of their application to build,
maintain, update, and retire, as needed, when needed. When deploying an application, PCF creates the container image used to support your
application and required packages through build backs you specify. These build packs contain the underlying libraries you need to execute your
application. The applications execute within the container, which are dynamically load-balanced within PCF.
Overall, the combination of the platform runtime and application framework provides developers with what they need to quickly build and deploy
their apps.

Self-service features
A variety of self-service features enables developers and lines of business to quickly act and deliver on their projects.
A self-service marketplace provides access to Pivotal services and tools that can be deployed within the developer’s space. A PCF space is a
shared location in which one or more developers can create, deploy, and maintain their applications. Each application deployed to the space is a
unique instance of that application that is accessible to users within that space. Services include MySQL, Redis, RabbitMQ, and other applications
and services installed and available in the marketplace.
Self-service application deploy lets developers push their applications to the cloud so that it is immediately accessible to end users. The system
uses dynamic routing to ensure the application name is accessible through the defined host specified in the configuration file. PCF creates a
container with the resources specified to execute the application in the cloud. Self-service maintenance of the application includes scaling,
monitoring, and enforcing security on the application. Developers can un-deploy, or remove an application from the cloud using PCF. This
removes and destroys the container, reclaims resources, and removes routing to the application and host name in the cloud.

Multi-cloud application support
Developers can take advantage of the multi-cloud capabilities of the solution. This is done by developing their cloud-native applications on the
platform and deploying it to a public cloud supported with the platform. This level of portability allows developers to take advantage of the external
platforms and IT can provide a growing number of endpoints to the business. Application developers can push the same application to multiple
locations, both within the same cloud and across different clouds. By taking advantage of containerization, the application is deployed with
everything it requires and will behave the same in the different cloud platforms.

Platform availability
Developers have options provided through Pivotal Cloud Foundry to ensure that their applications are highly available. Deploying two or more
instances of an application ensures that should one instance fail, the application itself is still accessible. Developers will need to ensure they have
defined enough resources to support the number of instances they are deploying.
Built-in availability features ensure that applications are restarted should a failure occur. If the app fails, PCF will restart the app in a new container
using the same routing information provided when the app was initially deployed.
The solution itself offers robustness and availability with built-in PCF availability features described, as well as infrastructure reliability features.
Beyond those, administrators can enhance the solution with multiple availability zones. An availability zone is an independent portion of the
network segmented by network, which increases availability and fault tolerance for the system. Multiple instances can be deployed across
availability zones for load balancing and fault tolerance. Should a cluster become unavailable, the application will be accessible from the other
availability zone. Availability zones can be defined within a single cluster, in a single site with multiple clusters, or across multiple sites.

Platform security
Security is often managed through four main functions within cloud native application development platforms: identity access management, threat
management, vulnerability management, and security event management.
With identity access management, or IAM, users are authenticated with Pivotal Cloud Foundry’s User Account and Authentication server.
This involves issuing tokens that then act on behalf of runtime users, authenticating users throughout the solution with their runtime credentials,
and supporting single-sign on services using those same credentials. This allows users to authenticate into the environment and allow the system
to use that singular authentication scheme throughout the entire solution. The solution also supports role-based authorization, whereby users are
granted specific rights within the solution.
Threat management is managed in several ways:
• Reducing the surface area of attacks limits the number of contact points that the solution has with the public Internet, thereby minimizing the
number of attack vectors on the platform
• Application security groups use firewall rules to prevent access from external networks and between internal components
• Maintaining container security and isolation is handled by PCF through the use of unprivileged containers for applications, which essentially
hardens the container with limited functionality and access rights, and allowing administrators to use application security groups to block outbound

connections from the containers.

Vulnerabilities are managed both through customer provided tools as well as through updates provided through Pivotal. Releases and stemcells
address code issues and patches with security fixes respectively. A release is a collection of the various code, config files, and startup scripts used
within VMs. A stemcell is a PCF construct that contain a versioned operating system image. This image comes with preinstalled utilities. These
stemcells are VM templates that are cloned during the deployment of a service that requires a VM.
Security event management is handled through event logging and monitoring. An audit trail is provided on PCF, PCF components, and deployed
applications.

Cloud native application development platform - implementation example
One of the biggest attractions to cloud native application development platforms is the ability to quickly stand up a cloud deployment solution for
using both on-premises and off-premises resources. In this example, a major financial organization had attempted to deploy a cloud platform to
support their rapidly growing business and to build out and capitalize on the software portfolio.
Cloud native application development platforms are often chosen as the final solution as it offers a deployment solution that could easily be set up
within a week.
For example, for a particular customer, the deployment and configuration challenges one would normally face with a build-your-own solution was
addressed by Dell support services that ranged from Professional, Consulting, and Global Support. The organization quickly realized benefits of
this implemented solution which allowed lines of businesses to quickly pursue development projects. There was also a lowered total cost of
ownership as the maintenance and operational costs decreased with an engineered solution that offered easier upgrade and maintenance
features.

Summary
Congratulations, you have completed this module and in a minute, you will be able to take the assessment. In this section, we covered a lot of
content, including:
• Why hybrid cloud models are valuable
• What is a hybrid cloud and what are its technologies
• How the features of a hybrid cloud empower businesses
• Hybrid cloud native application development and its benefits
• And how Pivotal Cloud Foundry supports application development on cloud native application development platforms

Five year digital transformation plan
Let's now consider the impact that hybrid cloud and cloud native application development will have on the Beane digital transformation. We have
dealt with these topics conceptually, but detailed product information needed to help us make specific decisions about applying these technologies
at Beane was out of scope in this training. However, it is clear that Beane must commit to both of these technologies to meet the digital
transformation goals it has set. So Beane commits to purchasing and deploying these technologies as part of the five year plan.
Beane has made some good decisions, and as a result has a new infrastructure that is stable and efficient. With a VxBlock 350, a VxRack SDDC,
as well as a VxRail system, Beane has infrastructure for all of its second and third platform applications. So where does a hybrid cloud fit?

Beane’s hybrid cloud
Imagine a situation with Beane's new and improved infrastructure where everything is running smoothly with all lines of the business content with
their IT capacity and its reliability. At this point, you receive an urgent request from marketing who needs an environment for a big data initiative
and they are not real sure how much capacity they will need to start and if it will grow quickly after it is deployed. Marketing isn't even ready to
decide if this is a temporary or long term need and is definitely not ready to commit budget for new hardware for infrastructure.
You could create the environment on one of the new systems in your infrastructure, but there is a risks. What if the new application is more
demanding than expected or grows to quickly? It could impact the performance of the system it is on or affect other apps running on the system.
With a hybrid cloud, Beane can instantly deploy the new application in the public cloud. Here it will have no impact on the new systems running in
the private cloud section of the hybrid cloud. If the app experiences extreme growth more public cloud capacity can be added automatically. If
marketing decides to drop the initiative, the environment and its cost can be eliminated. And if Beane decides to keep the app it can add capacity
to its infrastructure and move the app to the private side of the hybrid cloud.
A hybrid cloud, as well as a cloud native application development environment can be important components of Beane's IT.


Hybrid Cloud Models Platf Cloud Native

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hybrid Cloud Models Platf Cloud Native

Uploaded by

Copyright:

Available Formats

Introduction to Dell EMC Converged Systems and Hybrid Cloud Platforms for Digital and IT Transformation

Hybrid Cloud Models

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 1

Hybrid cloud models

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 2

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 3

Hybrid cloud models

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 4

New business investment cycle

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 5

Hybrid cloud and digital business prowess

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 6

Challenge to digital transformation…

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 7

Value of a hybrid cloud model

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 8

Hybrid cloud methods

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 9

First let’s explore the benefits a Hybrid Cloud can offer.

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 10

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 11

Cloud native application development platform

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 12

Makes the leap to cloud native easy

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 13

Allows DevOps set you free

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 14

Hybrid cloud models

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 15

Hybrid cloud models

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 16

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 17

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 18

Let’s look at some of the specifics of a typical hybrid cloud.

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 19

Virtualization and control layer

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 20

Cloud management and orchestration

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 21

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 22

Hybrid cloud benefits

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 23

Self-service access to traditional enterprise applications

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 24

IT services via a self-service catalog

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 25

Data protection services

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 26

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 27

Increased visibility to infrastructure consumption and cost transparency

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 28

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 29

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 30

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 31

Hybrid cloud models

Now let’s learn about Cloud Native Application development platforms.

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 32

Hybrid Cloud Models

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 33

Cloud native application development platforms

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 34

Addressing the Software Development Supply Chain Problem

Hybrid Cloud Models, Platforms, and Cloud Native Application Development 35

Native Hybrid Cloud Architecture – Infrastructure Layer