Download presentation
Presentation is loading. Please wait.
1
Consumer Cloud Monitoring Beta Kick-Off
October 24, 2012 Mac Holloway – Release Manager 08/24/2012 Consumer Cloud Monitoring Beta Kick-Off IBM Confidential
2
–We are recording this web conference so that:
Reminders – Please keep your phone on mute when not speaking (*6 toggles mute on phone conference facility if your phone does not have Mute button) –We are recording this web conference so that: • People not able to attend can review • You can share with colleagues who have an interest (keep in mind Confidential, though, please don’t share outside your company) • IBM Dev team can review if needed to make sure we capture feedback correctly. IBM Confidential
3
IBM Confidential Information & Disclaimer
Cloud Consumer Monitoring has not yet been announced, so this web conference and other early information is considered IBM Confidential. Please use care in sharing this information with others, and treat it as you would your own Confidential information. THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF: CREATING ANY WARRANTY OR REPRESENTATION FROM IBM (OR ITS AFFILIATES OR ITS OR THEIR SUPPLIERS AND/OR LICENSORS); OR ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF IBM SOFTWARE. IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. IBM Confidential
4
Agenda General Interactions Marketing (short) Technical Overview
UI Flows Schedule details Demo Wrap Up IBM Confidential
5
General information What we want to accomplish: We want to work with you to develop an offering both you and IBM will derive success from. This needs to be Win-Win collaboration. We will provide code drops every 3 weeks. This will be per a published schedule. The schedule will change per input from you. We want recommendations. On capabilities On look-and-feel On organization On Time To Value issues On collateral and support On September 14 we will shift to an Open Beta model and we will be expanding the participation to accommodate more of the customers that have shown interest. IBM Confidential
6
Interactions Forum – this is a general discussion forum for all items of general interest. Please try it out. Wiki – a place for making documentation and other deliverables generally available. If you have thoughts or needs for material or information or other collateral this is where we would make it available. Presentations and recordings will be available here. Advocate - for each of the business partners on this call we will assign you an advocate from the Tivoli team to insure that we are aware of your needs and progress. Weekly calls - These meetings will be for: Issues – technical, procedural, informational Requirements discussions Previews of upcoming capabilities if there is interest Special projects - We will also have separate support for other work like creating an agent, running a beta with a customer/end user, etc. IBM Confidential
7
Why Cloud Consumer Monitoring ?
IBM Confidential
8
Cloud Consumer Scope & Landscape
Cloud Provider Users Cloud Services Provider Personnel (Cloud Broker) Manages and fulfill cloud requests QoS Cloud Cloud Service Request & Delivery Platform Cloud Consumer Users Request cloud services (execute, control, etc) Manages the Cloud Services Delivery Platform VM Workload Provision resources Deploy workload Create images Cloud Monitoring Tools (Cloud Provider) Cloud Consumer workload Cloud Administrator Cloud Operator SMEs Hypervisor VM OS Appl Monitor workloads Manages the Cloud Infrastructure Operations Dev Ops Line of business Private Public Hybrid Cloud Infrastructure IBM Confidential
9
Requirements Low Time To Value
Infrastructure install by cloud provider must be on the order of minutes or 10s of minutes CVM instantiation/monitoring/debug by cloud consumermust be on the order of a couple of minutes Light weight Adaptive to highly dynamic environment – VMs come and go all the time Extensibility - easy to add more monitoring coverage Integration Events can be fed to any enterprise event management system Historical data can be sent to a data warehouse Any data can be pulled into other tooling Broad platform coverage EC2, VMware, SCP, … IBM Confidential
10
Insightful Lightweight Secure
October 24, 2012 Cloud service providers, and their tenants, need a multi-tenant, lightweight, elastically scalable solution for monitoring virtual machines and the applications running on them, without having to wrestle with a complex monitoring infrastructure. Insightful Application-level metrics. The monitoring infrastructure collects data from within the application, bringing into focus application-level data that the hypervisor can’t see. Intuitive interface. Attractive web-based UI presents application-level data in an intuitive way that supports actionable insights at the application level. Integration with cloud service provider platforms. The monitoring infrastructure integrates with cloud provisioning systems to create a highly dynamic and automated ecosystem that aligns with customer business processes. Lightweight Quick time-to-value. Newly provisioned virtual machines are automatically discovered, and are displaying performance metrics in the UI in under a minute. Self-configuring. Monitoring is established and maintained automatically, as the VM image is deployed. Self-optimizing. The monitoring infrastructure dynamically scales itself to the workload, monitoring only what is needed using an appropriate amount of resource. Secure Multi-tenant. Multiple tenants may share the monitoring infrastructure within a safe and secure environment in which each can only access his/her own data. Clarify what cloud consumers means in first sentence… line-of-business, application owners. This slide needs to stand as a one-slide story summary. Who are the cloud consumers? Public? Private LOB? (both, so figure out how to say it). IBM Confidential IBM Confidential 10
11
Technical overview and sample panel flow
IBM Confidential
12
Small, Extensible, Integrated and EASY
Cloud Platform support Mgmt Fabric Node Enterprise Integration Extendible UI Providers Data Multiple Agent Arch. Distributed Highly Events Scalability Smart Cloud Provisioning Amazon EC2 ITM Data Warehouse Omnibus ITM User Provided Custom Default Appl. Support Local Short Term Store Forwarding ITM Agents Agent Less Local / Remote OSLC exposed No Centralized Data IBM Confidential
13
High Level Architecture
Customer VM Agent SQL Adapter Base Fabric Node Data Warehouse UI AMZ … SCP Cloud Platform ITM Ominbus IBM Confidential
14
CCM Panels – Overall Flow
October 24, 2012 CCM Panels – Overall Flow Cloud Dashboard (initial page) Group Details (one tab on the page for each agent type in group. BP/Customer may contribute tabs.) drill down drill down Event Details (drill into {Group, EventSeverity} choice.) Event Console Situation Config VM Groups: 1. Out of the box, grouping is constructed as follows: 1A. If we are able to determine groups via OSLC relationships (e.g. multiple WAS VMs are related, and they are also related to a DB2 VM), then those VMs are grouped together. 1B. VMs that don’t match any group in 1A are put into their own group (single VM) 1C. Customer can change groups manually. Note that a VM may be part of multiple groups. For instance a DB2 server may be used by several applications, and therefore may be in several groups. Group Setup Health Check / Troubleshoot. User Management CCM Component Config Eclipse Help (Context Sensitive) IBM Confidential IBM Confidential 14
15
Cloud Dashboard IBM Confidential October 24, 2012
VM Group VM Count Offline Credit Services 2 1 4 6 WebSphere 4 2 8 DB2 2 1 4 6 vm27.ibm.com 1 4 test1.ibm.com 1 test2.ibm.com 1 VM Groups: 1. Out of the box, grouping is constructed as follows: 1A. If we are able to determine groups via OSLC relationships (e.g. multiple WAS VMs are related, and they are also related to a DB2 VM), then those VMs are grouped together. 1B. VMs that don’t match any group in 1A are put into their own group (single VM) 1C. Customer can change groups manually. Note that a VM may be part of multiple groups. For instance a DB2 server may be used by several applications, and therefore may be in several groups. test3ibm.com 1 IBM Confidential IBM Confidential 15
16
Group Details – Sample Agent Tab (Linux VMs)
October 24, 2012 Group Details – Sample Agent Tab (Linux VMs) VM Groups: 1. Out of the box, grouping is constructed as follows: 1A. If we are able to determine groups via OSLC relationships (e.g. multiple WAS VMs are related, and they are also related to a DB2 VM), then those VMs are grouped together. 1B. VMs that don’t match any group in 1A are put into their own group (single VM) 1C. Customer can change groups manually. Note that a VM may be part of multiple groups. For instance a DB2 server may be used by several applications, and therefore may be in several groups. IBM Confidential IBM Confidential 16
17
Disk Utilization % (Top 5)
October 24, 2012 Home Credit Services Linux VMs credit8.raleigh.ibm.com:LNX credit8.raleigh.ibm.com:LNX Overview Overview Properties CPU Disk Memory Network Process 1 Search Severity Status Events Event Description Group Impacted Time Display Item Critical Open Linux_Process_High_CPU The percentage.. Credit ServicesProtection 8/14/2012 3:27PM LocMapper 1-6 of 6 items | | | | | All < << > >> VM Groups: 1. Out of the box, grouping is constructed as follows: 1A. If we are able to determine groups via OSLC relationships (e.g. multiple WAS VMs are related, and they are also related to a DB2 VM), then those VMs are grouped together. 1B. VMs that don’t match any group in 1A are put into their own group (single VM) 1C. Customer can change groups manually. Note that a VM may be part of multiple groups. For instance a DB2 server may be used by several applications, and therefore may be in several groups. CPU Utilization (Top 5) Disk Utilization % (Top 5) LocMapper HADR1 bash HADR2 notifier TEST chrome SAMPLE ksh IBM Confidential SAMPLE2 IBM Confidential 17
18
Schedule IBM Confidential
19
Beta Drop schedule For each drop we will have defined content.
Date Drop 1 Drop 2 Drop 3 Drop 4 Drop 5 Drop 6 Sprint 8/24 9/14 10/05 10/26 11/16 12/14 Beta drop 9/19 10/10 10/31 11/21 12/19 For each drop we will have defined content. For each drop there will be a set of capabilities that we want customers to exercise. For each drop there will be value that we are trying to deliver. For each drop we want customer input on the value and how to improve it. Additionally we want to continually review the schedule and (to the extent it is possible) adjust it per the general customer input on priorities. There is a schedule but this is a beta. We need to keep working on the product until it is ready to ship. We will look to the customers to work with us on determining when this has been achieved. Two caveats – this is software development so content for any givne drop may change for various reasons. Change in content based on customer input may have other effects on content. IBM Confidential
20
Drop 1 Basic capabilities running in Amazon/EC2 or SCP. We will provide installables for the fabric node and Customer VM(s) (Linux instance(s)). The customer will be able to: Install the fabric node code. Install the ITM agents (Linux OS, X, and ITM Agent Builder MySQL SAMPLE) Instantiate a fabric node. Instantiate VMs with Linux OS agent already installed Group panel showing VMs in a group (all VMs in the cluster at this point) Customer experience: The customer gets to experience the ease or difficulty of the fabric node creation. The customer gets to experience/validate the deployment TTV seeing monitoring within seconds or minutes of instantiating a VM in their environment. The customer gets an initial insight into what groups/workloads could be. The customer sees both performance data for a VM running Linux OS. The customer gets to see that ANY ITM agent can be used albeit in a default table view. The customer gets to see the events and associated status for all of the ITM agents. The customer gets to see a SAMPLE ITM agent builder agent in operation. IBM is looking for: Impressions on the install. Is this easy enough ? What would make it easier ? What other cloud platforms are important ? Impressions on the UI look and feel. Is this “sexy” enough ? Is the flow logical ? Is the arrangement intuitive ? What should change ? Is this the right data to monitor/show ? What should change ? How should status be aggregated ? Is the sample useful ? Validation of the order of value delivery – the plan. IBM Confidential
21
Drop 2 Add grouping, event panel, event forwarding, VMware/Vcenter support, and full Gaian on the customer VM (with non-ITM data source and no event or status support) In basic terms this is what is new: Ability to group data sources and list and render groups Windows OS panel showing Windows performance metrics and event based status Event based status Event list panel Discovery plug-in for VMware/Vcenter – allows Vcenter based private clouds i.e. VCELL. The user uses the configuration manager UI to have events forwarded to OMNIbus (or other event consumer) Ability to add non-ITM data sources (no event support, table display only, no contribution to group status) More configuration Customer experience: The customer can now create groups. This is the key workload concept. The customer can now run on VMware. The customer can leverage event driven status for single VMs. The customer can play with more of the configuration through the UI. The customer can create a non-ITM agent data source using the distributed db interface What IBM wants: Does the grouping capability make sense ? How would they change it ? Does the status aggregation for groups makes sense ? Is the aggregation algorithm sufficient for a first release ? If we were going to make modifications, what would they recommend ? What types of data sources are they interested ? What kind of samples do they need ? What kind of custom display options are they interested in ? IBM Confidential
22
Drop 3 Add status aggregation, self-healing, WAS monitoring, and historical data In basic terms this is what is new: Status for aggregates - groups First pass of components restarting on failure WAS monitoring Historical data Customer experience: The customer can play with killing components and watching the recovery. The customer can now monitor WAS and include it in groups. The customer can use historical data to debug a problem. The customer can see aggregated status for groups – user defined, data source type, all VMs IBM is looking for: Testing help on the self-healing. Help in whether the WAS metrics are what they need. Is the WAS page(s) layout effective ? Help in whether the default set of event sis appropriate. Validation of group status aggregation. IBM Confidential
23
Drop 4 Add fabric delivery, DB2 monitoring, remote monitoring (will need to work with public cloud providers and private cloud users on this) In basic terms this is what is new: DB2 monitoring Advanced extensibility Remote monitoring (aka agent-less monitoring) for OSes Customer experience: The customer can now use an appliance based fabric node rather than having to build one. The customer can now create a custom page(s) for an ITM agent builder agent and insert it into the product. This is the other half of the extensibility capability. She/he can now use the samples as a basis to create a custom agent with customer display of the data. The customer can now monitor DB2 and include these data sources in groups. The customer can now do OS monitoring without having an OS agent on each VM. IBM is looking for: Validation of the usefulness of an appliance approach. Is the sample sufficient? what other doc do they need ? Are the DB2 metrics the ones they need ? Is the DB2 page(s) layout effective ? Are the DB2 defaults events appropriate ? Is the remote monitoring sufficient ? enough data ? enough agents ? IBM Confidential
24
Drop 5 Drop 5 Add custom pages for other agents, more config, more self healing In basic terms what is new: The user wants to consider data sources other than ITM agent builder agent The user selects an image with on it and adds both the application(s) and a non-ITM data collectors feeding the distributed db interface The user provides page definitions to a panel in the CCM UI which dowloads them and inserts them into the nav structure. The user starts an instance of the VM The user navigates to the grouping page The user adds the data source to a group The user can now navigate to the provided custom pages from the group that the data source is part of Customer experience: The user can create non-ITM data sources (and associated displays). IBM is looking for: Is the situation editor “good enough” ? sufficient function ? sufficient usability ? Are the samples for the non-ITM data source sufficient ? is the doc sufficient ? Is the integration with ITM easy enough ? What is missing ? IBM Confidential
25
Drop 6 Drop 6 Add basic situation editing, ITM 6.3 dependencies – WPA and DP (including OSLC registration) In basic terms what is new: The user can send data to her ITM infrastructure. The user uses the configuration manager UI to have historical data sent to an ITM Data Warehouse. The user points an application at the OSLC api and pulls data from the fabric node. The user can change the basic values for a given situation She opens the situation editor Specifics in early design Customer experience: The user can edit situations for the ITM agents. The customer can integrate this with an ITM installation – events, historical data. IBM is looking for: Is the situation editor “good enough” ? sufficient function ? sufficient usability ? Is the integration with ITM easy enough ? What is missing ? IBM Confidential
26
Demo Fabric node creation - SCP Customer node creation – SCP Simple debug example - SCP MySQL EC2
IBM Confidential
27
Wrap up IBM Confidential
28
Requirements Low Time To Value
Infrastructure install by cloud provider must be on the order of minutes or 10s of minutes CVM instantiation/monitoring/debug by cloud consumermust be on the order of a couple of minutes Light weight Adaptive to highly dynamic environment – VMs come and go all the time Extensibility - easy to add more monitoring coverage Integration Events can be fed to any enterprise event management system Historical data can be sent to a data warehouse Any data can be pulled into other tooling Broad platform coverage EC2, VMware, SCP, … IBM Confidential
29
Materials Link to Forum:
Link to Wiki: Link to downloads (still cleaning up install automation – targetting 8/29 availability): Link to install instructions: IBM Confidential
30
Nest steps Advocate assignment Todos from customer input
Input from customers on scheduling cadence calls Misc. IBM Confidential
31
IBM Confidential
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.