Top 10 for Intel IT Private Cloud – am I asking for too little or too much?

Hello Again,

Today I am going to share my Top 10 areas of focus for 2012, some of these are stretch goals, but would like to share ideas and see what others are doing in these regards.  Again, we are primarily focused on an internal enterprise private cloud, due to TCO, security, and performance reasons.  However we do intend to use external capacity for specific use cases, we can discuss that later….

First of all, as discussed in my last blog, we are going after three big business goals:

Business Goals 

1.) Achieve 80% Effective Utilization (CapEx Reduction)

2.) Velocity Increases at a Cadence for Service Provisioning and Maintenance activities (Agility and lower OpEx through more automation)

3.) Zero Business Impact (Resiliency)

Top 10 for IaaS and PaaS - we can discuss SaaS in a future discussion...

1.)  Cloud Bursting automatically, first from one Intel Data Center, then to second Intel Data Center, then to public cloud all through controllable policy.

2.)  Automated Sourcing at Provision and Runtime- as a consumer enters our portal or calls our APIs, based on business requirements entered, security classification, capacity available, and workload characteristics…. the automation and business logic will decide what type of services and the location (public, private, or hybrid cloud).  Workloads are dynamically migrated to higher performance infrastructure (and back) as demands change through the app’s life cycle.  End result is a dynamic infrastructure based on a Hybrid Cloud that adapts to consumer needs automatically.

3.)  Automated End-to-End Service Monitoring - as the Automated Sourcing occurs, all components are dynamically added immediately (as fast as provisioning time) to an end-to-end service model representing health, utilization, and usage of the deployed service.  Dynamic changes to environment are handled through automation (add/remove nodes, etc).  Key service level objectives QoS are exposed to the consumer (i.e.. availability, performance, configuration compliance, associated service requests) providing the consumer a view of how the service is performing to SLA for their precise instance.

4.)  Automated component based recovery - as specific components in the end-to-end service fail, automated remediation is completed resulting in 95% of situations being rectified through destroy/create concepts and or other immediate remediation solutions - net effect is Zero business impact.

5.)  Automated deployment of resilient services - nodes and components are deployed and managed through automation in such a way that allows for 100% uptime (zero business impact), through methods such as affinity, striping across multiple points of failure, active/active deployment across multiple data centers and disaster zones.  All done based on choice in portal on resiliency requirements for application, and with minimal complexity.  Applications built through PaaS are always built with Active/Active resiliency and with Design for Failure elements enabled.

6.)  All aspects of solution are available through Open APIs and rich but simplistic UI, or API layer that allows for usage of different service providers or different platform solutions allowing for write once methods with backwards compatibility for application layer.  Features are exposed via control panel to cloud consumer that permit manipulation of backup schedules, patch parameters, alerting thresholds, and other key elements for supporting a production service. Integrated dashboard views are available for different participants: operations, end-user, and management.

7.)  Security –Security assurance provided allowing for trusted computing for compute and data components of Cloud hosting environments.  Levels of trust available through programmatic queries and UI, with configurable settings to establish level of trust where security standards are not yet in existence, this configuration could include logical segmentation, physical segmentation, and authorized users roles, as well as such elements as encryption of data at rest, in motion, or in memory.   

8.)  Exposure of scale out data services (Relational, structured, unstructured, file shares) - through APIs, with replication between all necessary locations based on placement of nodes supporting application.

9.)  PaaS layer for both Java, and .NET applications - with associated IDE, Manageability, Data, and Compute Services, exposed at PaaS layer instead of IaaS, PaaS layer should automatically enable key design elements such as automated elasticity, automated deployment of resilient services, secure code on a trusted platform, and with client awareness.

10.)Select and Choose web services for consumption with appropriate interfaces exposed based on choices in portal on business solution being developed - encourage of reuse of existing web service stores in both public cloud space, as well as private cloud.  Providing community of mash-ups for specific business processes, and associated IaaS and PaaS underlying technology exposed as needed for use case described in portal.  Net effect is the ability to enable our Innovative Idea to Production Service < 1 day.

Are you doing similar things in your Cloud environment, are you doing these today already in your private Cloud?  As usual love to hear your thoughts on where you are going, as many of us are on this same journey to transform how IT is used to help things happen faster, better, and cheaper.

Intel IT Cloud Lead