5 Keys to Delivering Storage-as-a-Service Without Losing Control

Ron Smith, VP Sales & Marketing
iWave Software

NetApp Insight session #MG-2-711

Copyright© 2012 iWave Software. All Rights Reserved 1

Why Change Storage Admin Status Quo?
 Growth in storage demands

 Maturing Storage Admin population

 Change in user expectations:
magnifying need to reduce
provisioning times

 Deployment of private cloud initiatives

 Increase in CIO “IT-as-a-Service” initiatives


What is Storage-as-a Service (STaaS)?
 Users request storage services via self-
service portal

 Storage services are fully automated

 Can be “Private” or “Public”

 Private “Storage Clouds”
– Leverage your existing storage assets
– Hosted from your secure data center


Storage-as-a Service: a “Win” for Users

 Mirrors consumer behavior from public
storage cloud services

 Reduces provisioning times from:

 Empowers users to request own storage


Storage-as-a-Service: “Win” for Storage Admins
 Offloads and automates routine storage
administration tasks

 Automates the tracking of storage
consumption to storage users

 Scales existing storage admin staff to meet
growth rate in storage

 Enables storage support staff to evolve into
new “IT-as-a-Service” initiative


So What’s Holding StaaS Back?
 Fear of loss of control
 Complex, heterogeneous storage infrastructure
 Organizational boundaries and politics
 Complex processes: scripts, CLIs and tribal knowledge
 Integration of ITSM tools and processes
 Lack of vendor & product standards
 Fear of change


5 Keys: Delivering Storage-as-a-Service
Determine the scope for your Storage-as-a-Service
project

Choose the right storage automation platform

Define & implement storage policies to maintain
control

Establish a continuous “Storage-as-a-Service” process

Integrate StaaS into your existing ITIL processes


#1: Scope Your StaaS Offering
Process Candidates for
Identify storage tasks that can be STaaS Offering
automated based on:
 Frequency • Storage Provisioning
 Complexity • Storage Replication
 Routine/Mundane • Data Protection
 Cost • Data Migration
 Impact (if done wrong)


Typical Storage Provisioning Process

Find Best
•Performance Available •Change Approval Provision •User Notification
•Capacity Storage •Scheduling Storage •Chargeback
•Compatibility •Maint. Windows •Asset Mgmt
•Usage Profile •Resource
•Data Protection •Tier/ Service Reservation •Storage Provisioning
Level
•Fabric Configuration
•Storage Array Complete
Analyze •Host Configuration
•Device Group Request
Storage •Application
•Device Type Approve & Configuration
Request •Data Path Schedule

Typical storage provisioning processes takes 3 – 25 business days in large organizations


Admin Time Spent on Provisioning

Find Best
Available Provision
Storage Storage

Complete
Analyze
Request
Storage
Approve &
Request
Schedule

Typical storage provisioning processes takes 3 – 25 business days in large organizations


#2: Choose Right Storage Automation Platform

• Self-service • Rules engine • Execute automated • RESTful API
storage services
• Web-based • Matches storage w/ • Drives every service
storage requests • Change control in the catalog
• Multi-tenant
• Works with different • Maintenance windows • Ability to integrate
• Role-based
arrays, fabric, hosts with 3rd party portals,
access control • Preview & roll-back
IT automation tools,
etc.


#3 – Define & Implement Intelligent Policies
Application/Host Requirements Storage Attributes
• Storage admins set
selection policies

• Finds right storage to
• Infrastructure
fulfill automated storage
request • Disk speed, type etc.
• Performance
• Automatically chooses • Data Protection
the best “device group” (RAID, Snapshots,
• ASPs refine the set of
Replication)
candidate device groups • Acceptability

• Algorithm uses service
levels as input to select
the best device group


#3 – Execute Services to Help You Maintain Control
• Executes automated storage services
• Performs pre-condition checks
• Supports rollback to “last known good
state” in event of failure
• Uses standardized execution plans
– XML Documents
– Defines pre-condition checks, execution &
rollback
– Enables storage admin modification
• Change control set on per service basis &
integrates with service desk tools
• Operates within maintenance windows


#4 – Components for Policy Selection


#4: Establish Continuous StaaS Process
Select storage
automation
solution

Incorporate Identify storage
feedback for profiles &
improvement processes

Develop
Get Feedback automation
services w/SDK

Deploy Storage
Automation


#4: Establish Continuous StaaS Process
Identify storage
profiles &
processes
Incorporate Develop
feedback for automation
improvement services w/SDK

Storage-as-a-Service Process

Deploy Storage
Get Feedback
Automation


#4 - Storage Automation Workflow

New services and adapters using Storage Administrators control via
SDK. New objects are created, execution plans & policies in an Self-service portal
managed by execution plans. admin console


#5:Integrate Staas with ITIL Processes

CMDB

IT & Business Management Change
Approvals & Monitoring Management


Deliver Storage-as-a-Service
Scope your Storage-as-a-Service project +

Choose the right storage automation platform +

Define & implement storage policies to maintain control +

Establish continuous StaaS process +

Integrate StaaS into existing ITIL processes

Happy
Happy
Storage
Users
Admins


iWave Software Resources
Ron Smith
+1 469.287.5889, rsmith@iwavesoftware.com

Julius Clayton
+44 20 7492 1980, jclayton@iwavesoftware.com

www.iwavesoftware.com


5 Keys to Delivering Storage-as-a-Service Without Losing Control

More Related Content

What's hot (17)

Similar to 5 Keys to Delivering Storage-as-a-Service Without Losing Control (20)

5 Keys to Delivering Storage-as-a-Service Without Losing Control