16
© 2016 Kumulus Technologie Choosing a Cloud Provider

Choosing a Cloud Provider: Public-Private-Hybrid

Embed Size (px)

Citation preview

Page 1: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Choosing a Cloud Provider

Page 2: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Who Am I?Robert Starmer: @rstarmer- CTO for Kumulus Technologies- OpenStack operations contributor since 2012 - Supporting Cloud enablement and integration for Enterprise- OpenStack, Kubernetes, BareMetal to App CD

Kumulus Technologies: @kumulustech- Systems consultants supporting cloud migration- Cloud technologies education services http://kumul.us/educate

Kumulus Tech Newsletter: https://kumul.us/newsletter/

Five Minutes of Cloud: youtube.com/fiveminutesofcloud

@rstarmer

http://kumul.us

Page 3: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Cloud Defined - the NIST Cloud Model

ServiceModels

DeploymentModels

Essential Characteristics

Community PrivatePublic Hybrid

Software as a Service (SaaS)

Platform as a Service (SaaS)

Infrastructure as a Service (SaaS)

On Demand,Self Service

MeasuredService

Broad Network Access

ResourcePooling

RapidElasticity

@rstarmer

Page 4: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Step 1 - Determine User Needs

What are your users looking for?

Provisioning Speed

● Manual Interfaces (UI) vs. Automated Integration

● Container vs. VM vs. Bare Metal

Service Models

● IaaS vs. PaaS vs. SaaS

● CI integration

1

@rstarmer

Page 5: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Step 2 - Determine Utilization Patterns

Automation vs. Manual provisioning

● Is there something driving the utilization

● Scale and performance of the app

● Development use cases

2

@rstarmer

Page 6: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Step 3 - Cost management

Monitoring integration

●Third party (Splunk, Treasure Data, etc.)

●In-house (ELK, Sensu, etc.)

Resource reporting

●Chargeback

●Billing

3

@rstarmer

Page 7: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Step 4 - Network Interactions

Bandwidth costs

●Ingress vs. egress costs

●Site-to-site vs. “local”

Network service resource costs

●VPN

●Firewall

●Load balancing

VM

4

@rstarmer

Page 8: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Step 5 - StorageData at rest

● Quantity defines costs

● Likely a constant drain on the overall cost structure

Instance storage

● Pricing included (public)

● Costs incurred if instances are “off”

How did the data get there?

● See bandwidth costs

5

@rstarmer

Page 9: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Step 6 - Lock-in?

Application deployments leverage APIs

●Standards based?

Data migration

●Possible

●Costs ?

Other “services”

●Message bus, DNS, IP addresses

6

@rstarmer

Page 10: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Step 7 - Hybrid ValueCosts of Migration

● Active migration

● Passive scale

● Storage

● Network

● Network Service (VPN, etc.)

Flexibility

● Scale, Dev resource, DSS/scale out workers

● Lambda/Serverless

7

@rstarmer

Page 11: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Your End Users

Most people treat cloud as an endless resource pool

●Lack of awareness of ongoing service costs

●Just “use more” mentality

Old habits come with using new tools

●Educate the users on best practices for cloud service use

●Most effective way of managing costs regardless of service target

@rstarmer

Page 12: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Possible Progression Public -> Private

Start app dev/prod with a public provider

●Standard APIs

●Eyes open - data transition costs

●Network flexibility (DNS service discovery)

Migrate to private at scale/baseline utilization

●Public becomes a burst and remote resource

@rstarmer

Page 13: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Possible Progression - Private -> Public

Application built on a private service

●Remote country reach

●Network tunnel back to core data

Continue to split front and back services

@rstarmer

Page 14: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Possible Value - Hybrid (?)

Hybrid for “VM” based apps?

●Scale/burst with pre-positioned app elements

●Data in “public” or “private” environment

@rstarmer

Page 15: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Service costs model

Private Cloud costs

● Infrastructure

● Datacenter space (power/cooling)

● Ops staff

● Software support

Public Cloud Costs

● Cost per “ECU” or equivalent for containers (threads)

● Storage costs

● Network bandwidth costs

● Network services

@rstarmer

Page 16: Choosing a Cloud Provider: Public-Private-Hybrid

© 2016 Kumulus Technologies

Summary

Many factors go into a decision

Pricing may be a principal factor

● Network, storage, compute

● User Education is the most effective cost management strategy

Managing utilization applies to both service domains

Hybrid may provide value, likely more in a container focused deployment (or PaaS service user)

@rstarmer