To register to view this Playback:
Thank you to everyone who attended the Global Tivoli User Community - Simplify Cloud Management with IBM SmartCloud Monitoring. If you did not have an opportunity to take advantage of this free training live - you can still take advantage by viewing the replay. Slides, demonstrations and audio are captured in the recording.
Registered attendees may view the Playback with this link:https://de202.centra.com:443/GP/main/0000002d488f160134dc28bb9c007b01
To register to view this Playback:
IBM SmartCloud Provisioning is an infr
How do I find out if my warehouse has all the tables/views needed to run a report or create a custom report?
A new set of reports have been added under the folder "Prerequisites Checking" in ITMfVE 7.1 for the VMware VI agent which provide you with a prerequisite scanner that checks if the list of all tables/views needed to run the predefined reports and the ones needed to support custom reporting are available in the Tivoli Data Warehouse. It also checks the VMware VI agent version and lets you know if the available version is up-to-date or not. The reports also point you to appropriate documentation which can be helpful in enabling historical collection and summarization and pruning, creating IBM_TRAM schema, Time Dimension and other shared dimensions like WEEKDAY_LOOKUP, MONTH_LOOKUP and ComputerSystem and populating Time dimension. In addition to this, the report also provides the list of attribute groups for the VMware VI agent to guide the users while enabling historical collection.Please note that in spite of having all the prerequisite tables/views in the Tivoli Data Warehouse, you may not be able to run the reports [Continue Reading]
email@example.com 1200006580 标签：  portal tip itmfve resize integrated tivoli resolution screen page 5,664 次访问
ITM for Virtual Environments provides out-of-the-box pages in TIP (Tivoli Integrated Portal) that display well on a standard screen size of 1280 by 1024 pixels. If you use a higher screen resolution, you can customize the TIP pages to better suit your screen. Additionally, you can rearrange the components on a TIP page if you prefer that certain widgets are shown on a certain portion of the page. Let's examine both of these customizations.
Let's go through an example where we use a screen resolution of 1600 by 900 pixels, to see how we can change an ITM for Virtual Environments page to use the full screen real estate. Initially, when you pull up the ITMfVE VMware Cluster Dashboard, it looks like the following:
For our particular screen resolution (1600 x 900), this is not optimal. However, we can easily modify the screen above to look like:
To see the details on how we make this change, click [here to continue reading].
Jacques.Fontignie 270000UHFU 标签：  provenance versioning cloud virtualization image-library image library 5,368 次访问
Cloud systems have made a huge
improvement in terms of tracking and performance. In “Rapid deployments with
IBM Smart Cloud Provisioning” blog, we have shown that virtual machines or
appliances can be started and configured in a matter of seconds. It has never
been so easy to create a virtual machine (VM), install software, and configure
middleware. However, with great power comes great responsibility… it is now
possible to create a VM, but what is its lifecycle? Will it be destroyed after
being used, is the starting image deprecated, or is there a better starting
image given the needed configuration and software install requirements?
IBM SmartCloud Provisioning provides a component called IBM Virtual Image Library (also known as IVIL) to solve common issues that arise in large scale virtualized environments:
VIL can be integrated simply into
your virtualization infrastructure; the only requirement to start using IVIL is
the credentials required to contact the virtualization infrastructure. No changes to your current virtualization
environment are required. After credentials
are provided, IVIL can automatically determine the provenance, state, and the
content of each virtual image or virtual machine in the virtualization
environment. After the environment is
registered you will have a clear picture
of your various images, their content, history, and similarity with one
another. More important, as soon as IVIL
is used in the infrastructure, it can be used to move the images from one
hypervisor vendor to another and keep track of these migrations. To summarize, IVIL
not only keeps track of the changes of an image on one hypervisor but continues
when images are in a heterogeneous environment.
A common solution to track the contents and versioning of images is by use of a naming convention, for example, a name such as RHEL_6.1_WebSphere7.1_v2.1 implies the image is Red Hat Linux 6.1 with WebSphere 7.1 installed, and that this is version 2.1 of this image. It is feasible to use this approach with a small number of images but becomes cumbersome and confusing with anything but small examples. Basic information that is typically attempted to be conveyed includes:
Using an image naming convention can work in some cases and provide some of the needed information but it does not scale beyond a small number of simple images. To solve this, IVIL provides versioning and provenance control to understand where an image comes from:
What is provenance? Simply put provenance tracks the history of the image as it has evolved over time in the virtual environment. It tracks how the bits that make up the image came to be – through IVIL checkout operations, image clone operations, image copy operations, and so on. It is used to understand the lineage of an image from the perspective of the virtual system which might or might not match with how the user of IVIL views the image.
For example, let’s assume that you
have an image called “A”. If you decide to start this image on multiple
instances of IBM SmartCloud Provisioning or if you decide to clone this image
possibly multiple times, then IVIL will keep track of the relation between all
the created images and instances. At any time, if a security flaw is found on
A, then you can infer that the associated images and instances are likely affected
also. IVIL provides this functionality not only for a single virtual
environment, but across heterogeneous virtual environments also.
What is versioning? Versioning is the logical user-defined lineage of an image or virtual appliance; it is the way a user would think of versioning his or her image functionality, for example this is version 2 of my AccountsPayableService virtual image. When an image is available with a particular application version, the OS and libraries behind are often not important, only the application is. Is it important to know its template? Not necessarily, only the information about the OS is relevant. However, it is good to know the application version and if there is a newer version available for this image or if a new image has been released with the latest security patches. This is the versioning system in IVIL; it helps to understand if there are other versions of the application in the infrastructure, if some applications contain a patch or not.
To summarize, provenance is
oriented to infrastructure administration whereas versioning is more oriented
towards applications and workloads.
For example, let’s assume that we want to provide version 1.0 of software S as image. By default, users can decide to use software S and trigger any instance of image A. At a certain point, the version 1.0 is deprecated and we must upgrade software S to version 1.1. Unfortunately, the OS distribution must be upgraded. A solution is to reinstall the OS from scratch and install S version 1.1 on it; this new image will be called B. These images do not have any common lineage from a provenance perspective, however the content has a logical lineage to the user. Image A is the parent of image B from a versioning perspective.
It is important to understand that
an image can have only one provenance parent but can have multiple version
parents. The second claim makes sense because an image may have multiple
applications installed and thus each one may be associated to a logical
This concludes the introduction of Virtual Image Library component in IBM SmartCloud Provisioning. Next time, I will introduce the concept of similarity between images and the power that it provides in terms of debugging, infrastructure consolidation, licensing cost, and more.
Are your queries taking an unusually long time to run for the amount of data that you've in your Tivoli Data Warehouse? Do your Cognos based reports take forever to render the screen with some results? There are several tweaks that can be made to the data model and the reports to get optimum performance while running your reports. Some of the best practices to be followed while developing your custom reports and data models are discussed here.
Editing the data model using Framework Manager to optimize performance of queries: [Continue Reading]
jhkeenan 270001K41A 标签：  cloud_cost_management usage accounting metering chargeback showback 5,800 次访问
You can get some expert exposure to Tivoli Usage and Accounting Manager and our Cloud Cost Management solutions via our demo's and workshops at Pulse 2012. Please come along to see us if you are at Pulse this year.
The workshops are in the MGM Studio Ballrooms.
In this lab exercise, you learn how to use IBM Tivoli Usage and Accounting Manager (TUAM) for metering and also accounting for projects and servers in a IBM Service Delivery Manager or IBM Tivoli Service Automation Manager based Self Service Virtual Server Management Environment. You analyze accounting showback reports in a demonstration setup. Optionally, you can create your own cloud financial model with the Financial Modeler. You can enter budgets, select rate codes, distribute costs, calculate rates, and run comparison reports.
In this lab exercise, you learn how to use IBM® Tivoli® Usage and Accounting Manager (TUAM) to collect resource usage data, and to create an invoice and usage showback reports. Optionally, you can create your own financial model with TUAM Financial Modeler. You can enter budgets, select rate codes, distribute costs, calculate rates, and run comparison reports.
The labs will be hosted by our TUAM technical enablement specialist Joachim Schmalzried.
Please look out for us as well at the ISDM/TSAM Ped.
To learn more about the Cloud track at Pulse, see this site: http://www-01.ibm.com/software/tivoli/pulse/cloud/
I really liked the post Rapid deployments with IBM Smart Cloud Provisioning that explains how simple and fast is to deploy instances using SmartCloud Provisioning.
But once the instances are deployed the next questions are:
The solution is to integrate SmartCloud Provisioning with Tivoli Endpoint Manager (TEM) so that all the running instances will be connected to the TEM Server and managed according the configured security and corporate standards
It can be achieved exploiting the current integration between SmartCloud Provisioning and Image Construction and Composition Tool (ICCT) available in SmartCloud Provisioning version 1.2 performing the following steps:
After doing that when the extended image is launched the TEM agent will automatically start and connect to the TEM Server without requiring any user action.
Then from the TEM console you will be able to see and manage it performing actions and/or downloading fixlets.
This is just the basic integration and more advanced scenarios can be implemented, like for example exploiting the OVF parameters (as described in the topic Customizing virtual images with IBM SmartCloud Provisioning) for configuring and grouping the TEM Agents but they will be described in my next blogs !
For further information on IBM SmartCloud Provisioning and Image Construction and Composition Tool see IBM SmartCloud Provisioning Infocenter
If you would like to try out IBM SmartCloud Provisioning 1.2 core functionalities but you are worried you do not have time to spend installing it or you do not have enough hardware, you can download a special demo package from Integrated Service Management Library
It gets installed in a single physical box.
The system must use x86_64 processors that support virtualization.
In addition to that you need at least 3 GB memory and 30 GB disk space
The required operating system for this installation is Linux CentOS 6.0 64 bits.
In addition to that the following packages are required:
Then the installer configures the physical box as compute node, storage node, pxe server and dhcp server, then it creates a virtual image (the hypervisor is KVM) that acts as second storage node, webconsole, web-adminconsole, webservice, rest server, hbase and zookeeper.
Further installation details are available in the readme downloadable with the package.
As customers consolidate and virtualize application workloads along their journey toward Cloud, the cost savings that they had envisioned often prove elusive. True efficiency comes from the ability to right-size both the environment and the virtual workloads - in response to actual performance data, rather than theoretical estimates – in order to create an optimized Cloud infrastructure that runs densely enough to provide true consolidation while maintaining application service levels and room for expansion. The migration to a Cloud infrastructure, where the physical resources that we're accustomed to monitoring have been "abstracted" into pools of virtual resources, presents us with a visibility problem. It's more difficult to tweak the knobs and turn the dials to make an individual server respond to our management needs. More importantly, any changes we make at the Cloud infrastructure level have the potential to dramatically affect other workloads and services.
Join us on February 16, 2012 for Simplify Cloud Management with IBM SmartCloud Monitoring, where Ben Stern will demonstrate how our latest infrastructure management offering can help a Cloud or virtualization administrator overcome those visibility hurdles, leveraging infrastructure monitoring, health dashboards performance and capacity analytics, and policy-driven optimization of workloads and their placement in the Cloud. Most customers want a Cloud monitoring product that can be plugged into their existing data center monitoring toolset, as part of an enterprise-proven, heterogeneous solution, providing continuity of historical data and preservation of skills. You'll hear how SmartCloud Monitoring has descended from the same IBM Tivoli Monitoring DNA running in the data centers of the world's largest corporations, and quickly discover that you already know more about SmartCloud Monitoring than you realized.
Ben Stern has spent over 20 years working in the IT industry in a variety of management and technical roles within the software development organization. Prior to his current role, he was the lead for the Tivoli Service Availability and Performance Management Best Practices team. In that role, he helped define best practices for the Tivoli portfolio while working with hundreds of customers around the world. In his current role, he is focusing on Tivoli's virtualization and cloud solutions.
Link to Register
Select the session that fits your schedule.
February 16th 2011 11:00 AM to Noon EST US and Canada (GMT -05:00)
February 16th 2011 6:00 PM to 7:00 PM EST US and Canada (GMT -05:00)
I've been impressed by the speed of provisioning a set of virtual machines in just a few tens of seconds using IBM Smart Cloud Provisioning. In most cases you can get a running virtual machine in less than one minute.
The Smart Cloud Provisioning technology has been devised and particularly optimized for managing the following cloud infrastructure scenarios:
Many other workloads can be deployed and easily automated on top of Smart Cloud Provisioning. For example, traditional stateful applications can be easily deployed for simple HA solutions. Anyway you get the maximum performances from Smart Cloud Provisioning when operating in the context of the above scenarios.
To achieve such high performances Smart Cloud Provisioning has been designed focusing the attention to an optimized virtualization infrastructure based on OS streaming: no need to copy large image files over the network when provisioning.
Image copying is the single biggest bottleneck in VM provisioning today both in terms of CPU, memory, I/O and bandwidth usage. In traditional Cloud provisioning approaches all of this overhead is system resource that is just pure overhead (nobody builds a Cloud to provision systems - provisioning is an overhead that is required to have systems on which business workload is deployed, and any overhead is in conflict with the business workload).
The key element of such infrastructure are the so called ephemeral instances, that are virtual machines having no persistent state. Once they get terminated all the data associated with them is deleted as well. They are clones of a master image and these clones will have a primary virtual disk which is ephemeral: when the instance goes, so does its ephemeral storage (mechanisms exist in Smart Cloud Provisioning to provide persistence, if needed by some scenarios).
When creating a new instance, since master images are read-only resources and are replicated across the storage cluster, Smart Cloud Provisioning uses the Copy-on-Write (CoW) technology and the iSCSI protocol to stream them avoiding expensive copying. Each iSCSI session results in a valid block device to be created in the host OS. Of course each guest OS (corresponding to a given instance) requires a writable block device representing the main disk of the system. All supported hypervisors have a storage virtualization layer which includes the Copy-on-Write technology. For example, KVM's qcow2 files can be configured to implement CoW by referencing a backing storage device. VMWare has something called redo files which effectively do the same thing as well. In each case, the hypervisor can natively use the CoW file referencing the iSCSI block device to expose a virtual block device to the virtual machine. Depending on the hypervisor and guest OS this device will show up as something like /dev/sda or c:\. The CoW files are stored locally on the hypervisor's file system. When the instance is terminated, the Smart Cloud Provisioning agent will simply discard the CoW file and check if any other instances are using the same iSCSI device. If the device is no longer in use, the agent will also tear down the iSCSI device.
Thanks to the above infrastructure the action of provisioning a new virtual machine results in a very fast and reliable process that allows to create individual systems in tens of seconds and of peak requests of 1000s of systems per hour.
If you're interested in trying the Smart Cloud Provisioning product, you can download a trial version from the following link:
IBM® Tivoli® Service Automation Manager (TSAM) 7.2.2 introduces the concept of extension, a set of TSAM software components that can implement a new IT service automation solution (known as a service definition) or add capabilities to existing service definitions.
This article (Deploy a J2EE app with TSAM extensions) defines a scenario in which the desired result is to securely deploy a three-tiered enterprise application (a J2EE app) to the cloud. It demonstrates how to set up and provision extensions in TSAM as the first step to accomplishing this task. Then it describes how to standardize the three-tiered business application and provision it using standard TSAM offerings.
The second part of the article (Manage a J2EE app with TSAM extensions) focuses on the management aspects of the J2EE app. The authors explain how to add and remove application servers as the workload of the business application changes; and how to modify the security settings and why you might need to do that.
Framework Manager, a Windows only desktop client is a tool used to customize/extend/create data models. If the user wants to add new or 3rd party data to Tivoli data, he can use the data modeling tool to enhance/create data models that can be used for reporting. However, if the user wants to if the user wants to create reports with the attribute groups supported by the installed agent only, he will not need to use this tool.
Installing Framework Manager: Framework Manager (FM) ships with Tivoli Common Reporting (TCR) and the setup files for installation can be found under the CognosModeling/win32 folder. Make sure to run the setup files under CognosModelingFix/win32 folder once the Framework Manager is installed. This will help you fix the SSL encryption errors that you might encounter after the FM installation. [Continue Reading]
marvin_goodman 11000085U5 标签：  cloud virtualization virtual-infrastructure cloud-monitoring 8,999 次访问
With December's release of IBM SmartCloud Monitoring, Tivoli's venerable IBM Tivoli Monitoring product family, proven in data centers at the world's largest corporations, begins to adopt a "Cloud" posture. Sure, "Cloud" is a term bereft of a clear operational definition that we can apply at any given moment, and customers, analysts and vendors tend to bandy it about pretty freely these days. However, if we don't get too hung up what Cloud is or isn't, we can probably agree that it represents a migration from our traditional server-delivered infrastructure to one comprised of pooled computing resources shared by virtual workloads. Whether or not our customers are calling their virtualized environments "private clouds" today, and whether or not they've got a "cloud budget" that they're using for such initiatives, the fact that they're moving along the cloud maturity continuum at some pace seems inescapable, given IDC's assertion that we crossed the magical "50%" boundary last year, when half of all corporate workloads were running on virtual machines instead of physical ones.
If we're beginning to think in terms of clouds of pooled computing resources, it makes sense that we begin to deliver management solutions in the same way, right? If the server administrators, storage administrators and network administrators now report to a cloud administrator, we should begin to package solutions for those cloud administrators, combining multiple pieces of management technology into a single part number that customers can purchase and deploy. That's exactly what we've done with SmartCloud Monitoring. The discrete monitoring agents that are at the heart of IBM Tivoli Monitoring; OS monitors, application monitors, storage, etc., are as important as they ever were. Even though we're pooling those resources across virtual machines, we still have to monitor things like processes, CPU activity, IO throughput, and so on. We just need to add a layer on top of all that granular detail, so the cloud administrator can see, at a glance, what's healthy or unhealthy about his cloud environment, before drilling down into the nuts and bolts.
SmartCloud monitoring combines the VMware virtualization management features in ITM for Virtual Environments with virtual machine instance monitoring from ITM's operating system agents, to monitor a cloud infrastructure and the workloads running on it.
Our roadmap looks like an analyst's cloud maturity ladder, adding features such as automated provisioning, usage and accounting integration, and more detailed network monitoring, so our solution will "mature" along with the market, and customers' needs. See if the challenges along this ladder look like things that you or your customer have faced on their cloud journey, or are grappling with now. It's important to note that Tivoli has solutions that can be applied to each step, and for each problem. What SmartCloud promises is a way to bring those solutions together into more consumable bundles, tightly integrated together, to make cloud management simple to purchase and simple to deploy.
SmartCloud Monitoring delivers key capabilities for optimizing and maintaining a private cloud, including:
I'm a big fan of standardization. I'm a big fan of using non-persistent images as well. They just make my life so much easier.
The only issue I see with them is the need anyway to provide to the end user some configuration and customization possibilities.
It could be something trivial like having your own screen saver, or a special keyboard and language configuration or it could be
something like connecting the softwares inside the image to some specific devices, disks or additional, external software.
I even do not want to think about having a master image for each of the possible situation. This would simply make my image catalog
so uselessly big that it would shortly become unmaneageable. I would even not mention all the possible issues I could have when I
need to upgrade a master image, I just need to do it for all the customized masater images derived from that one.
I will loose all the advantages of dealing with a cloud of non-persistent images. I'm only sliding the issue from the virtual machine
instances to the master images themselves.
A possible solution would be to have the user reconfigure his VM everytime he starts it: unbereable! ...especially if you think about
complex software stacks.
I found interesting the solution included into IBM SmartCloud Provisioning. What you can do with that is to allow the end user to specify
a set of configuration parameters at image deployment time so that the image will be automatically configured accordingly at boot time.
The idea under the cover is pretty easy: the image builder inserts in the master image a script that is run at system boot.
The script is supposed to be able to parse the information passed by the end user at VM deployment time and takes the needed action like
reconfiguring the operating system or a specific software.
All information inserted by the end user in the web user interface are saved on the compute node and then injected back into the deployed instance
If you are worried about the fact the end users might be reluctant to type in information in a specific format (a possibility is to let him
deal with free text, but then you'll get mad in parsing it) and that the process could be error prone, consider that if you use Image
Construction and Composition Tool (an optionally installable component inside IBM SmartCloud
Provisioning), the web UI gets automatically modified to show the end user the parameters you may want him to put in.
Of course if you are a lazy end user and you do not want to type in information or remember them (especially if you do it frequently),
you can type your input parameters in a file and use the command line to deploy the image passing the file as one of the deployment parameters.
For further information on IBM SmartCloud Provisioning and Image Construction and Composition Tool see IBM SmartCloud Provisioning infocenter