Hybrid and On-premise AWS workloads using HP Helion Eucalyptus

© Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
HybridandOn-premiseAWS
workloadsusingHPHelion
Eucalyptus
HP Helion Eucalyptus
Vedanta Barooah (HP Technology Services) / 3 June 2015
#HPDISCOVER
@vedanta

Agenda
•Introduction and Value Proposition
•Technical Overview
•Eucalyptus Operations
•Uses Cases and Workload Migration
•Q&A and Conclusion

Introduction
• IaaS cloud software platform to build private and hybrid clouds
– Open source and runs on Linux on commodity hardware
– Multiple components working together with nodes (virtual hosts) to create a cloud
environment
– Abstracts physical infrastructure into a service-oriented platform
– Implements AWS compatibility
• Version 1.0 released in 2008, incorporated in 2009, acquired by HP in 2014
• Open Source
– Freely available (github.com/eucalyptus)
– www.eucalyptus.com/try

Provides cloud computing benefits
•On Demand
•Scalability
•Measurable
•Self-Service
•Ease of use
InfrastructureCost$
Time
Forecasted Demand
Actual Utilization
Elastic Capacity

HP Helion Eucalyptus
On Premise Private and Hybrid Services for AWS Users
Costs
Reduce public cloud
spend and rebalance
capex/opex spend
Data
Put data governance
and control back into
the hands of IT
Performance
Cloud solutions that
match your
performance
requirements
Mobility
Freedom to choose
where workloads reside

Cloud Ecosystems
• With HP Helion Eucalyptus customers have the
choice to run application either as self-service IaaS
or migrate applications to have cloud native
functionality
• Customers can pilot applications built to use AWS
services on premise and test functionality and
feasibility, before committing and migrating to the
public cloud.
HP
Helion
OpenStack AWS
Cloud Foundry
Eucalyptus
Managed
Services Cloud
Eucalyptus
Private Cloud

HP Helion Eucalyptus – AWS Compatibility
Why AWS compatibility is key?
• Benefits of clouds can be truly achieved when applications
are “Cloud Native” or “Cloud Enabled” – “App is King”
• Same design across both private, hybrid and public cloud
providers – leverage of skills and ease of management.
• Tools can be leveraged across providers
• Developers can use same API on both platforms
• API enables automation and usage of common toolsets
• Migration across platforms is easier
• Applications written on cloud services can be designed with
more robustness and high availability compared to
traditional approaches.
App AppApp
PaaS
EC2 S3 VPCAS ELBIAM
APIAPI

How is AWS compatibility achieved in HP Helion Eucalyptus?
• Diligently implements AWS services and functionality on commodity hardware
• Mimics AWS Services and API functionality as closely as possible
• Eucalyptus services are tested against AWS SDKs
• AWS and 3rd Party AWS toolkits are used to test Eucalyptus
• Eucalyptus toolkits are tested against AWS to maintain compatibility
• Eucalyptus commands can be used to either manage Eucalyptus or AWS services

HP Helion Eucalyptus - Service Implementations
EC2 EBS S3 VPC
CloudFormation Auto Scaling CloudWatch ELB
IAM STS

Compatibility Matrix
Platform / Vendor Requirements
OS/Hypervisor KVM In-distro RHEL or CentOS 6.x
Storage
Dell Equalogic PS4000/PS6000
EMC VNX Flare v5.32+
NetApp
FAS 2000/4000/6000 ONTAP
8.1
HP 3PAR COMING SOON
RiakCS (object) 1.4.5
Ceph Tech Preview
Hardware Commodity x86_64
Cloud Service: 8 Cores, 2.4GHz,
8GB RAM, 500GB Disk space
Node Controller: 4 Cores,
2.4GHz, 8GB RAM, 160GB Disk
space
Network
TCP/IP Networking No special requirements
Midokura (VPC) Tech Preview

Deployment
• One machine installation to try out using FastStart
– bash <(curl -Ls https://www.eucalyptus.com/install)
• Can be automated using configuration management and provisioning tools
– Chef, Puppet, Ansible, etc
• Designed to easily integrate with other tools

Eucalyptus Key Concepts
Images (EMI)
• Templates for instances (virtual machines)
• Stored in object store
• Can be created with various lifecycle operations
Instances
• An instance (virtual machine) of an image
• Have various properties which note capacity, size/performance and
placement in the cloud
• Have a public and private IP address
EBS Storage
• Persistent block storage for instances
• Can be cloned via snapshotting
Object Storage
• General purpose storage with S3-compatible web interface
• Best suited to data with low volatility
Availability Zone
• An aggregation of compute resource
• Provides physical, logical and SLA-based partitioning in the cloud
• Behaves like an Amazon Availability Zone
• Also referred to as a cluster

Cloud Component Map
Management
Console
AWS-
compatible
APIs
Object Storage
Provider (OSP)
Cloud
Controller (CLC)
Storage
Controller (SC)
Cluster
Controller (CC)
Node
Controller (NC)
Node
Controller (NC)
VM VM VM VM
UI & API
CLOUD
CLUSTER
(Availability Zone)
NODES

Cloud Architecture
Cloud
Controller
(CLC)
Object Storage
Gateway(s)
(OSG)
Cluster
Controller
(CC)
Storage
Controller
(SC)
Node
Controller
(NC)
VM VM
VMware
Broker
(Optional)
User Facing
Services (API
Endpoints)
Mgmt
Console
Object Storage
Provider (OSP)
Backend Services
User ServicesService-Managed
Instances
VM VM
Availability Zone

Deployment Topology
PoC / Pilot Small Single Cluster
CLC, Walrus, UFS, CC, SC
Node Controller
VM VM VM
CLC, Walrus, UFS, CC, SC
Node Controller
VM VM VM
Node Controller
VM VM VM
Node Controller
VM VM VM
Single Cluster
Node Controller
VM VM VM
Node Controller
VM VM VM
Node Controller
VM VM VM
WalrusCLC, UFS
SC
SAN /
Ceph
CC

Large-scale Logical Architecture
Cluster 1
Cloud ControllerUsers
Cluster N………….
Node
Network (Euca
Mgmt, VM
Private)
Storage/Cluster Controller
Node
Controllers
Network Network
Node
Controllers
Network (Euca
Mgmt, VM
Private)
Network (Euca Mgmt, VM
Private)
Storage/Cluster Controller
SAN or Ceph
Cluster
Console/UFS/OSG
Console/UFS/OSG
Riak Cluster
SAN or Ceph
Cluster
VM VM VM VM
Block
Volume
Block
Volume
Object Data
Network (Service
Endpoint, VM Public)
SDN Agent SDN Agent
Node
SDN GatewayPublic IP /
Firewalls

Eucalyptus Tools
• Euca2ools
– CLI tools to interact with AWS Services and other services compatible with AWS like Eucalyptus
– Provides REST-based and Query-based API for –
• Auto Scaling (commands start with "euscale")
• CloudFormation (commands start with "euform")
• CloudWatch (commands start with "euwatch")
• EC2 (commands start with "euca")
• Elastic Load Balancing (commands start with "eulb")
• IAM (commands start with "euare")
– https://github.com/eucalyptus/euca2ools
• Management Console
– Web based front-end for Eucalyptus and AWS (somewhat similar to AWS Console)
– Can be used to manage AWS services with AWS Access ID and Key
• Third-party Tools
– AWS client tools can be used with Eucalyptus with little or no modifications
– Some examples are – Eucalobo, Hybridfox, etc.

HP Helion Eucalyptus – EMI and Instances
• Instances provide resizable compute capacity
• Instances are instantiated from Eucalyptus Machine Image (EMI) images
• EMIs are images of Operating Systems (with software and customizations)
• An instance is essentially a virtual machine
• EMIs have a unique instance number - emi-<nnnnnnnn>
• EMI are similar to AWS’s AMI (AMIs can be downloaded and deployed on Eucalyptus)
• Instances are VMs deployed from EMI
• euca2ools provides “euca” commands to work with EMI and Instances
EMI InstanceOS

EMI and Instances (Demo)
• Objective :
– Create a key pair
– Create an instance
– Login into the instance
– Destroy an instance
euca-run-instances -k hp-euca-key3 -g console -t c1.medium emi-d1de3cc0

HP Helion Eucalyptus – Elastic Block Storage
• Persistent block level storage for compute Instances
• Allows for Instance scale out
• EBS can be used to store images and can also be attached to running instances to
store data persistently
• EBS support different file systems and can be backed up by creating snapshots
• Eucalyptus EBS is analogous to AWS EBS

HP Helion Eucalyptus – Elastic Block Storage (Demo)
• Objective
– Create a EBS volume
– Attach an EBS volume to an Instance
– Create a snapshot of EBS volume

HP Helion Eucalyptus – Networking and Security
• Instances by default will have a private IP address
• Public Elastic IP addresses (EIP) can be reserved and associated with Instances
• Security groups allow to configure security for instances – inbound and outbound
• Each instance has a virtual firewall
• Secure by default, configure as needed
• All inbound traffic is blocked by default
• Open port as needed
• Only unicast traffic
• Security groups can be configured to allow only certain IP addresses
SSH/22
RDP/3389
Instance Security

HP Helion Eucalyptus – Autoscaling and Cloudwatch
Autoscaling
– Automatically mange Instance capacity
– Scale on demand based on application capacity requirements
– Maintain HA / healthy number of instances for an application
– Scale up / down based on application requirements and trends
– Can be used for cost-control measures
CloudWatch
– Collects, aggregates and dispenses data from cloud resources
– CloudWatch matrices can be used to build AutoScale policies
– Following services and resources are monitored using CloudWatch
• Instances
• Elastic Block Store (EBS) volumes
• Auto Scaling instances
• Eucalyptus Load Balancers (ELB)

How AutoScaling works?
Application Server
(1)
Load Monitor
Application Server
(2)
Add Resource
Remove
Resource
CloudWatch & Autoscaling
Autoscaling Policy
Report Server
Load
Launch
Server
Terminate
Server
ELB
(Elastic Load Balancing)

HP Helion Eucalyptus – CloudFormation
• Implementation of AWS CloudFormation
• Allows for application repeatability and redundancy
• Used for automation, config management, machine and environment repeatability
• Uses JSON
• Compatible with AWS CloudFormation Templates
{
"Resources" : {
"MyInstance": {
"Type": "AWS::EC2::Instance",
"Properties": {
"ImageId" : "emi-db0b2276"
}
}
}
}
{
"Parameters": {
"MyImageId": {
"Description":"Image id",
"Type":"String"
}
},
"Resources" : {
"MyInstance": {
"Type": "AWS::EC2::Instance",
"Properties": {
"ImageId" : { "Ref" : "MyImageId" }
}
}
}
}

HP Helion Eucalyptus – Other Topics
•Image Management
•Walrus Object Storage
•Virtual Private Networks (VPC)
•Access Management

Use Cases
• “Cloud Enabled” and “Cloud Native” applications make better use of cloud design patterns –
emphasizing on scale out, no-single point of failure deployment, and efficient pay per use models
• Customers trying to move legacy application to cloud native AWS architectures can design and deploy
onto a on premise Eucalyptus cloud securely to gain confidence and learning
• Hybrid application topologies can be built to safe guard data on premise and host tertiary services on
AWS as needed to maintain compliance
• Applications can be run on premise using Eucalyptus during low-traffic seasons and can be scaled out
to AWS during peak-traffic seasons
• Testing of data security and integrity on premise using Eucalyptus before public AWS deployment
• Leverage processes, tools and skills across public and private cloud providers
• Cost savings (including use of commodity hardware already invested on)

Eucalyptus – Application Scenario
To understand “Cloud Enabled” application architectures we will look at a
simple enterprise application, how it typically resides on traditional data
centers, how it can be deployed on AWS and how it can be deployed on
Eucalyptus.
Hybrid Cloud
(AWS +
Eucalyptus)
Public
Cloud
(AWS)
Traditional
DC

TimeCapture – Application Architecture
Time
Capture
Directory
Database
Projects
Application
Data Warehouse
Analytics
BI
Reporting
1
2
3
4
5
6
#1 Employees log time on the TimeCapture portal hosted
on a Web Server (Example – Apache + PHP)
#2 Application uses enterprise directory to authenticate
employees (Example – AD/ LDAP)
TimeCapture uses API feeds from Projects Application
for Project WBS ID for employees' to log time. (Example –
REST API)
#4 Database stores time logs from employees (Example
– Oracle)
DWH pulls data from various applications –
Projects, TimeCapture which feeds into Analytics, BI and
Reporting
Requirements
- Users are globally located – application response
times are critical
- Directory is globally spread out and needs syncing
- Database needs to be fault tolerant
- Applications get patched and updated regularly
- DWH requirement to store petabyte scale datasets
- Analytics needs to tie into reporting and BI
1
2
3
4
5 6
LDAP / AD Directory

Virtualize and Shared
Environments
TimeCapture – Traditional Deployment
LDAP / AD
App
Web DB DWH Hadoop
Servers for each tier
Add hardware
load balancers
Localize for user bases
Scale out databases
by adding servers
Servers / Instances per application
DWH Server Pool
Hadoop Node Pool
Monitoring
Shared Storage
Logging
Create tier replicas
Create HA Clusters

EC2
Directory Service
RDS
Region > VPC > AZ
TimeCapture – AWS / Cloud Enabled
LDAP / AD
App
DB DWH HadoopWeb
Route 53 (DNS)
Autoscale
ELB
Cloud Front
Replica
RedShift EMR
Autoscale
EC2 CS
S3
SQS
CloudWatch

TimeCapture – Eucalyptus + AWS / Cloud Enabled / Public + Private = Hybrid
LDAP / AD
App
Web DB DWH Hadoop
Eucalyptus (Private)
AWS (Public)
Traditional On-Premise
Compute
Storage
Network
Monitoring
Identity
Autoscaling
Cloud FormationSustain parts of application with
sensitive data / IP on premise?
Utilize on premise capex – like Storage,
Networking, etc.
Use Monitoring to monitor both private
and public cloud
Not everything has to move to the cloud
AWS is not just service, its also the robust
infrastructure hard to achieve on premise – use it
when it make sense.

Cloud Application and Workload Portability
Suitability
Analysis
Mapping to
Cloud
Workload
Migration
Cloud
Enablement
Discovery
• Which workloads can we move?
• What can I expect the costs and
the benefits to be?
• Which workloads should I
move to Cloud ?
• And to which Cloud?
• How do I move these workloads
to the Cloud?
• How do we mitigate risk in the
process?
• Are we ready for the cloud?
• What is my application
(workload) landscape?
• Integrate migrated workloads into
one environment
• Adapt/Modernize
• Optimize

Suitability Analysis Process Tree
Application
Cloud Candidate
Traditional Migration
Simple
Medium
Complex
Standard DC Migration
Cloud Migration
One-Step Migration
New Applications
Phased Migration
Approach
RefactorReplace Rebuild Host / RehostRevise

Migration Approaches to the Cloud
X2C Migration Container Migrations Database Migrations Application Migrations Hybrid Migrations Total Migrations
Compute Migrations Application Migrations Cloud Enabled Applications
Migrate servers and applications to the cloud for
IaaS and PaaS
Migrate applications to the cloud for SaaS and
DbaaS
Refactor applications to the cloud to use
services provided by the cloud platform
Migration of Server
infrastructure to the
Cloud
Contain and migrate
applications to the
cloud
Migrate databases to the
cloud to use databases
as a service
Migrate applications to
cloud to use software as
a service
Use cloud services to
provide all application
functionality
Map application to
partially use cloud
services and retain
custom compute to
provide functionality
Image based migration
• Scripting
• RiverMeadow
• Doubletake
• VM Import/Export
Container migration
Docker
AppZero
Rocket
Replication
Import / Export
Tool Based
Install
Customize
Host
Map
Refactor
Migrate
Host
Map
Refactor
Host
New applications
Complexity & Effort Required

Migration of Applications and Workloads to Eucalyptus
• Instance migration can be done using OS native toolkits and commands
• OS Images are compatible across traditional and cloud platforms – conversion is easy
• Eucalyptus provides AMI image compatibility – images can be converted to EMI and used
• AWS CloudWatch metric data and CloudTrail can be used to identify AWS workloads that are feasible
for migration to eucalyptus
• AWS Billing data can be used to understand resource overage and wastage – and identify possible
workloads that needs to be migrated on premise
• Eucalyptus EBS and snapshot features can be used to store instances on premise and used as
necessary either on AWS or Eucalyptus.

Hybrid and On-premise AWS workloads using HP Helion Eucalyptus

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Hybrid and On-premise AWS workloads using HP Helion Eucalyptus

Similaire à Hybrid and On-premise AWS workloads using HP Helion Eucalyptus (20)

Dernier

Dernier (20)

Hybrid and On-premise AWS workloads using HP Helion Eucalyptus