IBM PULSE 2012 File Name Here.ppt I think it means that the boundaries of IT have changed. We’re entering a new paradigm where the infrastructure is being abstracted, making services available anytime, anywhere, and from any device. So really, the location of the infrastructure becomes irrelevant. And this is happening because there is an ‘industrialization’ or standardization of services taking place that enables scale and the application of best practices in a repeatable way. You might hear this called “Cloud computing”. Now, in order to keep up, we need to evolve IT service delivery as well. Organizations will have to source business and IT services from outside of their enterprise -- bringing a new meaning to the concept of a “business without limits”. This means that organizations will need to understand the special considerations of service delivery in this new environment and make the right choices, based on tradeoffs of risk, reward, control, and so on. [Switch Image] 11/13/12 17:27 11/13/12
Key points: There is a stepwise approach You can start with a private cloud IBM provides the tools and services to help you at every stage Speaker Notes In most data centers today there is a plethora of systems with varying degrees of standardization and best practices. In order to simplify the management and create a repeatable, predictable infrastructure, you need to create standard building blocks. The Rolling Thunder offering will guide you through the process to ensure success. IBM will be providing ready-made ensembles, but you can also start this process by applying best practice patterns to the systems that you already have. These patterns define the best practice virtualization configurations depending on the systems and the way you want to use them. The next step is to capture and catalog the images (operating systems, middleware, and software) used in the datacenter and standardize on those building blocks as well thru virtual appliance definition. This will result in simplified deployments and image management. The third step involves pooling your standardized virtual configurations into ensembles where you can manage many systems as if they were one. This logically flows into workload management according to the service level agreements defined by the data center. Service Management offerings, such as Tivoli Service Automation Management (TSAM) will help you define and manage those services in tight integration with Systems Director and Ensembles.
INTRO E PRIMA SLIDE COMUNE PER TUTTI I WEBCAST Buongiorno a tutti sono (nome, cognome, ruolo) e benvenuti al CloudCast (Titolo) primo incontro di un percorso che vuole illustrare al mercato italiano la value proposition cloud di IBM. Questo percorso prevede una serie di appuntamenti fissi on line che tratteranno i differenti aspetti dell’adozione del cloud computing; ad ogni incontro nei primi 10 minuti parleremo del valore delle specifiche soluzioni cloud per il business, portando anche esempi concreti mentre nei successivi 20 minuti ci sarà un approfondimento più tecnico. Oggi vi parleremo di ( Private Cloud ) ma prima di affontare questo tema mi preme illustrarvi come IBM ha organizzato il proprio portafoglio di offerta IBM SmartCloud affinchè risponda alle richieste del mercato. IBM Smart Cloud è organizzato in 3 aree fondamentali: SmartCloud Foundation, un insieme integrato di tecnologie e servizi per trasformare il proprio data center realizzando cloud private o ibride. SmartCloud Services, la piattaforma IBM per l’erogazione di servizi cloud per le imprese, resi disponibili in modalità ‘as a service’ SmartCloud Solutions, ovvero le nostre soluzioni di business e d’industria in Cloud, offerte in modalita’ SaaS e tra queste troviamo le soluzioni di Smarter Commerce, Smarter Cities, Social Business, Business Analytics. Tutto questo in linea con un’unica architettura di riferimento che aiuta a governare la trasformazione verso il cloud e che garantisce impegno verso standard aperti e interoperabilità Al termine dei primi 10 min (prima parte) comunicare di non abbandonare la sessione Come vi abbiamo comunicato nell’introduzione ora entreremo nei dettagli tecnici, non scollegatevi il webcast proseguirà tra pochi secondi! Al termine della presentazione annunciare il successivo webcast Bene, siamo quasi al termine. Colgo quindi l’occasione per ricordarvi che nel prossimo appuntamento del (data) si parlerà di (Public Cloud – creare slide?) ma (sono) anche disponibile successivamente anche tramite i social media, trovate i (miei) riferimenti in questa slide (slide da creare!!). Ora apriamo la chat per rispondere immediatamente alle vostre domande o dubbi Chiudere la chat ringraziando nuovamente per la partecipazione
Inserito SO nella picture We know that most clients are going to need more than just infrastructure support. We also know that for certain workloads and applications, not everything will move to a cloud environment. Cloud is all about the trade-offs. If you’re willing to trade in customization for a more standard environment, then you’ll get the benefits of lower-costs and faster time to value. And that is really what happens as you move up the stack from traditional IT to infrastructure to platform to software as a service. You are willing to accept more standardized, automated solutions, but in return you also lower your Capex and Opex. The critical thing is to understand how you target different workloads and applications to delivery models. For example email in a SaaS model is a good option if you don’t mind a standardized environment. But you may feel differently about your complex, customer legacy applications where you can benefit from the advantages of some automation of the middleware layer.
Based on your service level agreement (SLA) expectations and cost drivers, IBM plans to offer two delivery platforms—IBM SmartCloud Enterprise, which is currently available, and SmartCloud Enterprise Plus, which is planned to be available sometime during the second quarter of 2012. 1 (See note on slide.) For both SmartCloud Enterprise and Enterprise-plus, clients provide application licenses.
Inserito SO nella picture We know that most clients are going to need more than just infrastructure support. We also know that for certain workloads and applications, not everything will move to a cloud environment. Cloud is all about the trade-offs. If you’re willing to trade in customization for a more standard environment, then you’ll get the benefits of lower-costs and faster time to value. And that is really what happens as you move up the stack from traditional IT to infrastructure to platform to software as a service. You are willing to accept more standardized, automated solutions, but in return you also lower your Capex and Opex. The critical thing is to understand how you target different workloads and applications to delivery models. For example email in a SaaS model is a good option if you don’t mind a standardized environment. But you may feel differently about your complex, customer legacy applications where you can benefit from the advantages of some automation of the middleware layer.
**Central processing unit (CPUs) **Redundant array of independent disks (RAID) **Gigabyte (GB) **Terabyte (TB) **ext3 is ‘third extended file system’, a file system that is commonly used by the Linux kernel. The table illustrates the virtual machine instance types, storage and other options available with IBM SmartCloud Enterprise. Notes: The storage provided with an instance is divided up into a root segment (with 60 gigabytes) plus additional segments with the amount shown. Users may choose to provision an instance with just the root segment to shorten provisioning time. Virtual machine (VM) instance storage is erased when an instance is de-provisioned (deleted). Blocks of persistent storage and object storage should be used for storing data for longer periods. Persistent and object storage are both RAID protected, but instance storage is not. Although images can be built on one virtual machine configuration and migrated to a configuration of a different size, images have a limited set of virtual machines types and sizes they support. While small Linux virtual machines (Copper and Bronze) generally provision in approximately eight minutes or less, larger instances take longer, depending on storage size and operating system chosen.
Inserito SO nella picture We know that most clients are going to need more than just infrastructure support. We also know that for certain workloads and applications, not everything will move to a cloud environment. Cloud is all about the trade-offs. If you’re willing to trade in customization for a more standard environment, then you’ll get the benefits of lower-costs and faster time to value. And that is really what happens as you move up the stack from traditional IT to infrastructure to platform to software as a service. You are willing to accept more standardized, automated solutions, but in return you also lower your Capex and Opex. The critical thing is to understand how you target different workloads and applications to delivery models. For example email in a SaaS model is a good option if you don’t mind a standardized environment. But you may feel differently about your complex, customer legacy applications where you can benefit from the advantages of some automation of the middleware layer.
Now that we have a high level understanding regarding the options in which virtual instances can be configured within the SmartCloud Enterprise+ service, let’s take a deeper dive into the details of those options to be associated with the virtual instances. Please note that the information provided over the next four charts are based on the offering design as it stands today. Any information and technical details presented within the next few charts are subject to change at anytime as we are still in the concept phase of the offering. This information is provided to you as a best effort estimation as what the options and configurations for the SmartCloud Enterprise+ offering might look like. First, we will take a look at the virtual machine capacity options. The virtual machine configuration options are a set of standard, pre-defined configurations for CPU, memory and storage for individual instances. From a hardware platform configuration perspective, we are targeting to offer two platforms: x86 and p-Series. Within each of the hardware classes, there will be two architecture classes – either 32 bit or 64 bit. Within the 32 bit architecture platform, there will be three pre-defined packages available through the service catalog: Small, Medium & Large. The 64 bit platform for x86 will offer four packages: Small, Medium, Large and Extra Large. For p-Series, we are planning on offering the same configuration packages as x86 with the addition of a Jumbo option as well. Being able to offer such a variety of standard configuration options will provide clients the flexibility to choose the appropriate configuration that meets both the capacity and performance requirements of their application workloads across many different types of use cases. It is important to understand that these packages will be bound within the constraints of the options available through the standard configurations. The ability to offer standard configurations for virtual machines is key to being able to deliver the service in a cost effective manner through reduction of complexity of the available instances. This in turn is used to drive down lower costs per virtual machine unit.
Next, lets move along to the various service level package options that are planned to be available in the SmartCloud Enterprise+ offering. Being able to offer a variety of service levels of virtual machines within the Cloud is something which will differentiate IBM from our competitors. The ability to provide this option is not only made possible through the technology platform, but also through IBM’s years of year of experience and expertise in providing Enterprise level globally managed service operations. For the initial release of SmartCloud Enterprise+, there will be four options for service level packages available: Bronze, Silver, Gold and Platinum. It is important to note that the service level package will be made of two components: the VM availability and the infrastructure services. The VM availability SLA will be measured as the uptime availability of the individual virtual machine to perform the desired workload. This is a different model that most other Cloud providers are willing to sign up for when speaking to SLAs in a compute infrastructure as a service cloud. The main difference is that most cloud providers will offer an SLA of the “infrastructure”, meaning that they will place the SLA in the ability of an end user to provision a virtual instance. They will not move the SLA above the hypervisor level and sign up for the availability of the individual instances. With our SmartCloud Enterprise+ offering, IBM is going to place the SLA against the VM instance as well as the infrastructure. We are able to offer this not only because we are providing Enterprise class hardware for resiliency and redundancy, but also because each of the standard images within the service catalog will come integrated with the full suite of SO monitoring and management tools and agents. This will allow the SO delivery teams the capability to provide an end-to-end, ITIL based managed service using best practices and lessons learned from literally thousands of SO engagements around the world. No other Cloud service provider today will be offering the breadth and depth of service level options within their solution. In addition to the VM availability SLA within the Service Level package, SmartCloud Enterprise+ will also have an “Infrastructure Service” component with the SLA. This will set the standard SLA for such options as provisioning fulfillment requests, location of deployment, virtual machine mobility through technologies such as VMotion, and data protection or replication options. As you move up the stack in package options, say from Silver to Gold, it is important to know that the next level of availability package will include all of the available options of the previous package. For example, a Gold package will contain all of the features and functions of the Silver package. The Silver package will contain all of the characteristics of the Bronze package. As one takes a good look at this table above, it is perfectly acceptable to make the observation, “Why is it that when a package goes from Gold to Platinum, the provisioning time of and the instance jumps from 48 hours to 72 hours?”. The answer is, this is true. But it is important to keep in mind in what the offering is looking to accomplish when moving from Gold to Platinum. First off, the SLA of the VM will jump from 99.7% to 99.9%. With that move in availability there are extra pieces of physical hardware, software and OS configurations that need to be taken into consideration to achieve this SLA. This will elongate the provisioning time. For example, storage replication will need to be setup across two locations, multiple VMs will need to created to allow for site redundancy, extra agents will need to be installed for monitoring and various entries will need to be made to the asset and CMDB systems to ensure proper administration and tracking. These are just a few items that need to be looked at and analyzed before a virtual instance is considered SO ready to meet the required SLA of the end customer.
After the end user has selected the desired capacity and the required service category, the next phase is to determine the software image to be installed on the virtual instance. Currently for the x86 platform, we are looking to offer Red Hat Enterprise Linux 5.2 – 5.5, SUSE Linux Enterprise Server 11, SUSE Linux Enterprise Server 10 and Windows Server 2008 R2. On the p-Series platform, we are targeting to offering AIX 6.1. But keep in mind, that there are much more that just operating systems which will be available through the SmartCloud Enterprise+ service catalog. There will be a variety of both IBM and non-IBM software included in the images as well. I am not going to run down the entire list, but will highlight some packages such as the Websphere middleware suite, Rational development tools, enterprise databases such as DB2, Informix and Oracle as well as a host of Lotus and Microsoft applications. The point here is that we are going to be offering a very rich image catalog for SmartCloud Enterprise+ in which end users will be able to deploy and run Enterprise class workloads on a cloud infrastructure. One important item to note is regarding licensing given the current state of the offering. As of this presentation, detailed license models have not been defined completely. This will get more solidified as we move through the development process. The goal will be for IBM to allow customers to bring existing license entitlements and a limited set of pay as you go licenses.
Inserito SO nella picture We know that most clients are going to need more than just infrastructure support. We also know that for certain workloads and applications, not everything will move to a cloud environment. Cloud is all about the trade-offs. If you’re willing to trade in customization for a more standard environment, then you’ll get the benefits of lower-costs and faster time to value. And that is really what happens as you move up the stack from traditional IT to infrastructure to platform to software as a service. You are willing to accept more standardized, automated solutions, but in return you also lower your Capex and Opex. The critical thing is to understand how you target different workloads and applications to delivery models. For example email in a SaaS model is a good option if you don’t mind a standardized environment. But you may feel differently about your complex, customer legacy applications where you can benefit from the advantages of some automation of the middleware layer.
IBM Confidential In order to address the customer needs represented across the IBM Security Framework, IBM Security Services offers three different methods by which we deliver our services. Professional Security Services are more traditional consulting type services – they can be either custom or fixed price and address a variety of needs from assessment to planning to implementation Managed Security Services are those that we offer on a 24x7 basis to manage and monitor our customers’ security continuously from our global security operations centers Cloud-based security services are those that leverage shared models and private cloud architecture to deliver Security as a Service for our customers.
First of all, realize that this offering is part of the GTS Security Services portfolio and specifically sits within our cloud-portfolio. On the chart you can see several of our cloud offerings. In this case, we’re talking about security services delivered from the cloud . Just like cloud-based services from IBM, Amazon, Microsoft, SalesForce.com, Google, and dozens of others, the business world is realizing the incredible efficiencies that can be had from robust, always on, accessible anywhere, professionally managed services. The offering we’re talking about today is called hosted Mobile Device Security management.
Application programming interfaces (APIs) Cloud network attached storage (Cloud NAS) IBM SmartCloud Enterprise has integrated cloud storage technology from Nirvanix to provide a cloud storage solution designed to support millions of users, billions of objects and exabytes of data. Clients can upload a file of any size from anywhere in the world and access it anywhere—as opposed to forcing customers to upload the same file multiple times in multiple geographic regions and imposing strict file size limitations. This is designed to provide customers with continuous access to data at multiple, redundant locations for optimal performance and business continuity. This storage capability is ideally suited for unstructured data such as documents, spreadsheets, PowerPoint presentations, health records, images, audio and video files, and email and text messages, as well as for storing objects in which data, metadata and index are all encapsulated as one blob. To help provide prompt access to unstructured data and objects, each node within the storage service knows what is stored in its neighboring nodes, essentially performing as a massive, cross-connected grid. The graphic on the right consists of a cloud overlaid with a file folder structure and illustrations of different types of content that could be stored in the folders. Below the graphic is an illustration of the commands necessary to store and access the files over the Internet. “HTTP POST to upload and HTTP GET to download” are the two commands needed to store and retrieve files, respectively. “http://downloads.MyCompany.com/Application/Useraccount/Folder/Filename” is an illustration of the type of URL users can use to up- or download files using a simple link on a website.
Inserito SO nella picture We know that most clients are going to need more than just infrastructure support. We also know that for certain workloads and applications, not everything will move to a cloud environment. Cloud is all about the trade-offs. If you’re willing to trade in customization for a more standard environment, then you’ll get the benefits of lower-costs and faster time to value. And that is really what happens as you move up the stack from traditional IT to infrastructure to platform to software as a service. You are willing to accept more standardized, automated solutions, but in return you also lower your Capex and Opex. The critical thing is to understand how you target different workloads and applications to delivery models. For example email in a SaaS model is a good option if you don’t mind a standardized environment. But you may feel differently about your complex, customer legacy applications where you can benefit from the advantages of some automation of the middleware layer.