2012.03.30 - IBM SmartCloud Provisioning
Upcoming SlideShare
Loading in...5

2012.03.30 - IBM SmartCloud Provisioning







Total Views
Views on SlideShare
Embed Views



9 Embeds 176

http://ibmcloudcatalog.blogspot.fr 79
http://ibmcloudcatalog.blogspot.com 72
http://www.scoop.it 12
http://ibmcloudcatalog.blogspot.ca 6
http://ibmcloudcatalog.blogspot.it 3
http://ibmcloudcatalog.blogspot.ch 1
http://ibmcloudcatalog.blogspot.co.uk 1
http://ibmcloudcatalog.blogspot.com.br 1
http://ibmcloudcatalog.blogspot.be 1



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • VMware vCloud Director is not as simple to setup as IBM SmartCloud Provisioning “ Given the [vCloud Director] technical requirements, the nontrivial installation process, and the risks associated with a v1 product, we will be focusing on larger enterprises with a deep relationship with VMware... ” Source: VMware vCD 1.0 document for partners (non-public) Real world installations of vCloud Directory typically take a day to setup largely due to its prerequisite Oracle/Microsoft database, with upgrades taking an hour Beyond simple installation, vCloud Director requires configuration to access existing servers, as well as ongoing maintenance of the managed environment. IBM SmartCloud Provisioning is designed to be simple to setup and simple to use with extensive automation to reduce time to value (TTV) and no separate middleware prereqs TTV tests have initial setup in less than 4 hours, with upgrades in 30 minutes POCs which have been completed at the customer in under a day start to finish
  • We recently tested a 50 node IBM SmartCloud Provisioning installation and we were able to load more than 10,000 VMs in an hour. We also added 14 brand new blades and had them available to provision VMs (from bare metal) in less than 6 minutes.
  • We recently tested a 50 node IBM SmartCloud Provisioning installation and we were able to load more than 10,000 VMs in an hour. We also added 14 brand new blades and had them available to provision VMs (from bare metal) in less than 6 minutes. Typical Virtualization vendors mistakenly put the configurations inside the VM, making it either difficult or impossible to automate with scriptsc
  • We recently tested a 50 node IBM SmartCloud Provisioning installation and we were able to load more than 10,000 VMs in an hour. We also added 14 brand new blades and had them available to provision VMs (from bare metal) in less than 6 minutes. Typical Virtualization vendors mistakenly put the configurations inside the VM, making it either difficult or impossible to automate with scriptsc
  • We recently tested a 50 node IBM SmartCloud Provisioning installation and we were able to load more than 10,000 VMs in an hour. We also added 14 brand new blades and had them available to provision VMs (from bare metal) in less than 6 minutes. Typical Virtualization vendors mistakenly put the configurations inside the VM, making it either difficult or impossible to automate with scriptsc
  • Deploy highly available cloud infrastructure that automatically tolerates HW and SW failures and scales with no manual configurations
  • Deploy highly available cloud infrastructure that automatically tolerates HW and SW failures and scales with no manual configurations

2012.03.30 - IBM SmartCloud Provisioning 2012.03.30 - IBM SmartCloud Provisioning Presentation Transcript

  • March 2012Build a low-touch, highly scalable cloud withIBM SmartCloud Provisioning © 2012 IBM Corporation
  • Companies need an affordable entry point for cloudOrganizations need a low-cost, low-risk entry point to cloud computing technologywith compelling features that achieves their business goals. Customer goals: • Provide agile service delivery that caters to changing business needs. • We know virtualization helps reduce capital expense but how do I control my operational cost? • Need to increase the performance, utilization, reliability and scalability of IT resources while reducing IT complexity • Ability to expand capabilities VISIBILITY CONTROL AUTOMATION See services in real time & Better manage assets, Achieve greater efficiency better predict business service & compliance. and service quality outcomes2 © 2012 IBM Corporation
  • IBM SmartCloud Provisioning is a true Infrastructure-as-a-Service cloud, reducingcost and providing a highly scalable, rapid-deployment environment with near-zero downtime and automated recovery across heterogeneous platforms.Key Benefits: Key Differentiators: Distributed architecture for solution resilience.  Hypervisor agnostic supporting KVM, ESX, Xen Rapid scalable deployment designed to deliver  Reduced hypervisor licensing by accessing the near-instant deployment of 100s of virtual hypervisor directly without going through the machines in seconds instead of mins or hours. licensed (and costly) management components. Continuous operations during upgrades and  Hardware agnostic enabling choice of maintenance resulting in no outages or supporting your current hardware. downtime.  Advanced Image lifecycle management & image Reliable, non-stop cloud capable of composition tooling. automatically tolerating and recovering from  Intelligent load balancing during provisioning. software and hardware failures. Save IT labor resources at scale by enabling self-  Open source based providing and easy service request and highly automated operations extensible platform utilizing existing. Reduce complexity through ease of use and  Small footprint of code with core components improve time to value. for the Cloud management less than 200Mb.3 © 2012 IBM Corporation
  • Quickly get started with IBM SmartCloud Provisioning• Quickly stand up a cloud • Start small and scale based on need • No additional pre-reqs such as databases, app Provisioning servers, messaging middleware • Freedom of choice for hypervisors • Avoid expensive vendor lock in • VMWare ESX, KVM, Xen Compute node Compute node• Highly cost effective solution • Requires no additional hypervisor management tools • Requires no HA hardware or software First Box• Rich set of interfaces into the cloud • Web Interface, scripting and web services Storage node • All function can be driven by a user or by scripts Storage node for complete automation • Out-of-the-box and running in less than 4 hours • Get started with only 4 servers4 © 2012 IBM Corporation
  • Provides Unparalleled Scalability, Speed and Fault Tolerance• It’s Fast • Can start 100 VMs in under 3 mins • Can start a single VM and load OS in under 10 seconds • Can go from bare metal to ready for work in under 5 minutes• It Scales up to and beyond 50,000 VMs in an hour (50 nodes) • Add capacity by simply plugging in a blade or server • Writes only the data you change • Peer-peer architecture to avoid traditional bottlenecks• Its Fault-Tolerant Provisioning • “Live Update” capability to patch or upgrade the Cloud • No single point of failure • Automatic failure recovery Bo Bo t VM Bo Mgt VM t Hypervisor Hypervisor t VM Bo Hypervisor Hardware t VM Bo Hardware VM Bo t Hardware t Hypervisor Hypervisor Bo Hypervisor Hardware VM Bo Hardware t Bo t HardwareRequested VMs will be up Hypervisor Hypervisor Hypervisor tand running under a minute Hardware Hardware Hardwareusing standard HW5 © 2012 IBM Corporation
  • IBM SmartCloud Provisioning key concepts..• IBM SmartCloud Provisioning coordinates three indipendent ingredients: • Virtual servers • Network addresses • Storage volumes When a request is made, a given virtual server is attached to one or more network addresses and one or more storage volumes• This has several advantages: • Quickly recover from failures – cheaper to replace than to fix: - Swap out old VM and replace with fresh new VM on different hardware Dramatically simplifies patch, image and change management: - New versions can be easily swapped in, and old versions can be easily put back if problems arise - Servers can be restarted and then reattached to their previous storage volumes and addresses to quickly restore their state6 © 2012 IBM Corporation
  • IBM SmartCloud Provisioning vs traditional hierarchical architecture VV M VV MVMMM VV M VV M V MMM VV M VV M V MMM VV M VV MV MMM V End Users V M VV M V End Users MMM VV M VV M V MMM VV VV V V V V V V V V MVV MV M VV MV MV M VV M VV M VV M MV MV MV MV Server machines Storage devices M M M M M M M M M M M M M M M M (iSCSI) No single points of failure, no bottlenecks in data Failures that will impact your users, slowdowns that yourserving/processing, no intervention to repair broken parts! users will notice, and extra work for the admin team! Multiple, load balanced instances of all services  Single instance of critical services Parallel processing against storage  Serialized processing Self-adapting peer-to-peer communication & coordination  No automatic restart and rerouting of requests Recovery oriented computing  Patches and upgrades go everywhere Network deployed software & image updating  Requires very high cost hardware Distributed request processing, data storage and messaging  The bigger the cloud the worse the damage Designed to run on lower cost hardware and storage devices  Request for images bound to a single location All services monitor and restart each other, and dynamically  Serialized, slow access and susceptible to peak overloadselect the leader  Patches/upgrades require taking down the Cloud to apply and Base software is loaded via network boot (PXE) they need to be carefully applied Services are images, so update themselves by restarting with  When a service breaks, that part of the system is outnew image version  Admins have to troubleshoot and fix7 © 2012 IBM Corporation
  • Failure mode and automatic recovery 1. Leader fails • triggers reelection and another takes over 2. Agent fails • watchdog restarts Standard IaaS Interface 3. Storage node fails • Multi-path continues uninterrupted • Agent connects to another replica V V V V M M M M 0 0 0 0 • Leader tries to restart V V V V M M M M VM3 VM2 VM1 Dom0 ∆‘s ∆‘s ∆‘s 0 0 0 0 ∆‘s ∆‘s ∆‘s iSCSI iSCSI Hypervisor Hypervisor 4. Compute node failure Compute Nodes Dynamic P2P • Partial faults cause agent to stop accepting requests Management Agent network overlay V M 0 V M 0 V M 0 V M 0 to evacuate iSCSI ∆‘s iSCSI ∆‘s ∆‘s Hypervisor • Once empty will restart (PXE fresh image) ∆‘s ∆‘s ∆‘s V M 0 V M 0 V M 0 V M 0 • Full failure detected by leader which stops sending V V V V M M M M V V V V 0 0 0 0 M M M M requests iSCSI ∆‘s ∆‘s ∆‘s Hypervisor iSCSI ∆‘s ∆‘s ∆‘s 0 0 0 0 Hypervisor Hypervisor iSCSI ∆‘s ∆‘s ∆‘s • Leader cycle’s server power (PXE fresh image) Image streaming Hypervisor V V V V M M M M 0 0 0 0 5. Service VM fails ∆‘s iSCSI ∆‘s ∆‘s Hypervisor • All services are clustered to tolerate individual faults • Leader VM detects and replaces failed VM Storage Nodes 6. Network fault8 • Redundant interfaces automatically take over © 2012 IBM Corporation
  • Nice to knowLeverage Open Source software: • HBase™: a scalable, distributed database that supports structured data storage for large tables • ZooKeeper™: A high-performance coordination service for distributed applications • OpenLDAP™ Software: an open source implementation of the Lightweight Directory Access Protocol • Dojo Toolkit: an open source modular JavaScript library • HTMLSmall footprint … less than 200MB of which 80MB for Java™ libraryOffer a variety of interfaces: UI, command line, REST APIsIBM Infrastructure as a Service APIs submitted to DMTF (Desktop Management Task Force), also used by IBM SmartCloud Enterprise9 © 2012 IBM Corporation
  • What’s the problem with Virtualization and Standardization? 1 In the beginning, there was the perfect image… 2 Then users starting making changes and “snapshots”… …and what they put in the images is unknown… 3 Then they get copied to multiple locations… …and some change again… 4 Then you need to apply a critical security patch…how? … where?10 © 2012 IBM Corporation
  • IBM SmartCloud Provisioning Puts You Back in Control Control over Image Versions, Content and Locations – Image library allows check in, check out, and tracking of versions in the environment •Changes can finally be tracked – Powerful image analytics finds the content you need and can show the specific changes from one image to another •Encourages reuse and gives needed visibility to analyzing whole systems at a glance – Images are tracked across multiple Clouds and/or multiple sites •Critical for disaster recovery arrangements and decentralized use Control over Image Construction – Build images using Company-certified OS, middleware, and application packages •Avoids images being taken out of production due to non-compliance11 © 2012 IBM Corporation
  • Two optionally installable components: •Image Construction and Composition Tool •Import images from etherogeneous providers •Extend images Avoid images being taken out of production due to non-compliance •Image library •Import & export images across an etherogeneous set of repositories •Assign version to images •Search for images •Compare images12 Get full control on image lifecycle © 2012 IBM Corporation
  • Solution Architecture Compute Nodes run the virtual servers instances, Storage Nodes run the management components, load balanced across all the nodes in a distributed Users Reseller store the image templates, and handles all of the Cloud architecture. This is where the “Cloud Services” are storage I/O for VMs via iSCSI (either locally attached Admin delivered to the Cloud consumers. Typically there to the storage node, or network attached thru the are 4x to 5x compute nodes to storage nodes. storage node) Linux VM Window VM IaaS VM WebConsole Web Services Zoo Keeper HBase Management Components run as a series of VMs Non-Persistent VMs are used for stateless VMs (web providing Web Console for UI, Web Services layer for servers, app servers). No changes to the VM API access, Zoo Keeper running the management captured, so that if re-instantiation is needed, just xSeries Hardware “bots”, Hadoop database storing configuration, state xSeries Hardware re-launch from the image template. Separating the and usage data, and Open LDAP for access. data from the image (through remotely connected data) allow faster stateless VMs to be deployed. Image Templates are stored on the storage nodes, iSCSI and read into memory (in the hypervisor) on the Persistent VMs are used for stateful VMs (DBs, compute nodes during the provisioning process. By general IaaS). A copy is made of the image template exploiting “copy-on-write” provisioning events can from the storage node, so that ant changes to the happen in seconds. VM can be written to the disk, to maintain its state. Compute Nodes Storage Nodes Persistent storage volumes are created on the iSCSI storage nodes and mapped to the virtual machines on the compute nodes. Data access is via iSCSI. PXE Server is used for deployingNAS boot image to SAN / the Storage new nodes added to the Cloud. When a new bare metal node is powered on, the PXE server will PXE Server automatically download to the boot image, and configure the physical Persistent Storage node as either a compute or storage node. Typically takes 2-3 mins to configure.13 © 2012 IBM Corporation
  • Use cases: from the setup to the use Manage End user tasksCompare Index Check-in Image Administrative tasks Images Images Images Versioning Image management Federate Start/Stop Search Import Check-out Allocate Create Image Deployed Images Images Images vLANs Volumes Repositories VMs Register Build Register Deploy Attach Install IPs Images Images VMs VolumesRegister Create Users/ Modify Capture Allocate Terminate Monitor vLANs Groups Images Images IPs VMs User workload Assign Monitor Associate Delete Usage Quotas cloud IPs images14 © 2012 IBM Corporation
  • Use Case: Rapid deployment & low touch resource additionUse Case: User driven rapid deployment offew or 100’s of vm’s across heterogeneousplatforms and hypervisorsIT Admin needs to provision few to hundreds ofVMs in minutes across multiple hypervisors andplatforms in a fault-tolerant environment . ITAdmin requests deployment of an image acrossseveral VM instances. Deploy fails due to lack ofresources. New blade is powered on and allowedPXE boot to our infrastructure. In less than 6minutes with no manual configuration, resource isavailable in cloud to be consumed. IT Adminresubmits provisioning job, Image is selected fromthe image library and provisioned across rackswith each node provisioning VMs. A hardwarefailure occurs and a blade is removed. The work isautomatically balanced across remaining blades Customer Valuewith no disruptions in running the workloads. Power up and forget: Scale up cloud infrastructure with no manual configuration and rapid crossChallenge(s) this Scenario Addresses: domain provisioningScaling up cloud resources  Choice through extensive hypervisor and platform support15 © 2012 IBM Corporation 15
  • Use Case : Build and manage a fault tolerant cloudUse Case: Deploy highly available cloudinfrastructure that automatically tolerates HW andSW failures and scales with no manualconfigurationsCloud Admin sets up a infrastructure-as-a-servicecloud which allows cloud users to deploy applicationsin the cloud. He is responsible to mange andmaintain availability for this infrastructure so thecloud has high reliable and available. To achieve thishe will use the OOTB fault tolerance infrastructureprovided by IBM SmartCloud Provisioning. He makessure depending on number of Compute nodes andstorage nodes in his environment he is able tomaintain a 7x24 up and running cloud. IT Adminrequests deployment of an image across several VMinstances. Image is selected from the image libraryand provisioned across racks with each node Customer Valueprovisioning VMs. A hardware failure occurs and a  Zero downtime, tolerates hardware failures drivingblade is removed. The work is automatically higher customer satisfactionbalanced across remaining blades with no  Power up and forget: Scale up cloud infrastructure withdisruptions in running the workloads. no manual configuration and rapid cross domain provisioningChallenge(s) this Scenario Addresses:  Choice through extensive hypervisor and platformNon availability of cloud infrastructure in event of supporthardware failure which impacts SLA’s 16 © 2012 IBM Corporation 16
  • Use Case: image Lifecycle ManagementUse case: Control image sprawl and reducebusiness risk with rich analytics, imageversioning and federated image library tostandardize imagesOrganization has virtualized IT, but needs toimplement preventative measures to control imagesprawl. IT Architect designs and models the fullstack image according to company policies,synchronizes the image , and captures instancesas cloud ready image to publish to master imagerepository. The IT Admin controls image versionsand federates across all images by convertingimage formats and editing and analyzing image tooptimize impact on storage, and then selects animage from the library to deploy to repositories inthe cloud. Customer ValueChallenge(s) this Scenario Addresses: • Reduced data storage through smarter analytics and single instance storage can reduce image storage costsImage Sprawl and drift by up to 80%  Reduced risk of using non-compliant images that could have security exposure  Over 70% reduction in image provisioning time and labor costs through automated image lifecycle management17 © 2012 IBM Corporation 17
  • Customer Deployment ScenariosRapid service delivery of IaaS & PaaS Disaster Recovery of IaaS & PaaSProblem: Customers want to respond quickly to Problem: Customer wants DR capability for IaaSbusiness events, and need to provision new for the provision of 200 machines within an SLAserver resources in a few minutes. of 60 mins. Typically this is done by having dedicated hardware on warm/cold standby.Benefit: SCP Allows us to provide a new level ofresponsiveness and agility that customers are Benefit: SCP means that we do not needfinding extremely beneficial to them, and driving dedicated hardware, but just ensuring we havemore revenue for us. (It’s a differentiator) sufficient total capacity available. This increases our utilisation rates / improves costs.Partner Reseller Model Development of Sharepoint ServicesProblem: Business partners don’t want to own Problem: One of customers uses high end laptopsidle capacity, but do want to scale up quickly to for the development of Sharepoint sites for itsrespond to their customer needs. customers – due to their hardware & storage constrained IT environment.Benefit: SCP supports a reseller model wherepresentation UI can be branded, quotas set for Benefit: SCP allow us to offer Sharepoint PaaSsoft limits and dedicated resources can be images that can not only be provided quickly, butassigned to support delivery for different with regular versioning on images for snapshots.partners. This offers a huge cost saving to the customer and18 improved agility. © 2012 IBM Corporation
  • Business Challenge Solution Hardware constraints Leverage SmartCloud Provisioning to rapidly  Significant number of machines required to support stand up development and test development life-cycle environments  Low HW utilization rates Currently using SmartCloud in 28 development  Forced to use outdated HW and test projects in Tivoli Time constraints  Required time to setup a complex topologies Reduced setup time from 2 hours to 5 minutes  Significant time spent on setup rather than testing Returned 356 old physical machines to surplus Skills requirements Enables more time to be spent validating  Training engineers to setup complex software stack software instead of setting up environments Befor Avg: 2 hours Test Environment (physical machine) e Request HW for TestingTester Now Avg: 5 mins Test Environment (SmartCloud instance) IBM SmartCloudTester Provisioning Launch instance 19 © 2012 IBM Corporation
  • Upcoming FeaturesReferences in content to IBM products, software, programs, services or associated technologies do not imply that they willbe available in all countries in which IBM operates. Content, including any plans contained in content, may change at anytime at IBMs sole discretion, based on market opportunities or other factors, and is not intended to be a commitment tofuture content, including product or feature availability, in any way. Statements regarding IBMs future direction or intentare subject to change or withdrawal without notice and represent goals and objectives only. Please refer to thedeveloperWorks terms of use for more information. Installation enhancements: • Standalone installer for Virtual Image Library Functional enhancements: • Virtual Machines take over • Group Level Administration • Command line for Image Construction and Composition Tool • Extending Windows images with Image Construction and Composition Tool • New look and feel for the webconsole • Pattern deployment Additional hypervisors: • Hyper-V • PowerVM ...more coming, stay tuned!!! • z/VM20 © 2012 IBM Corporation