cynthyap 110000GC4C 标签：  cloud-computing provisioning cloudops cloud cloud-monitoring devops cloud_computing smartcloud smartcloudprovisioning 7,764 次访问
DevOps has become something of a buzzword lately but the idea behind it can be truly powerful. Using a combination of technology and best practices to increase collaboration between development and operations teams can accelerate the application development lifecycle while improving software quality and reducing costs.
For many, the development process has become more complex and segregated from operations. Factors such as inefficient communications, manual processes and poor visibility into the deployment process result in production bottlenecks as well as subpar quality throughout the development and delivery cycle.
To address these challenges, organizations have often turned to adhoc and siloed efforts. And so gaps still exist due to lack of integration across people, processes and tools. The reality is that an effective DevOps solution requires an integrated approach of continuous delivery that optimizes and accelerates the application lifecycle in every phase: development, testing, staging and production.
What this means is that changes made in development are continuously built, integrated and tested for function, performance, systems verifications, user acceptance, and then staged, ready for production. And it can all be brought together through an integration framework that can automate the individual tasks across the various stages of the pipeline and continuously deliver changes, providing end-to-end lifecycle management. Continuous automation is necessary in the following key areas:
• Continuous integration provides faster validation and delivery of code changes via automated, repeatable execution of build processes with continuous feedback
• Continuous deployment provides on-demand environment configuration and the ability to continuously deploy code and configuration middleware.
• Continuous testing automates testing in production-like environments.
• Continuous monitoring increases visibility into application performance and provides data to trace and isolate product defects.
With an automated process for moving application changes through progressively richer test environments that mirror the production environment, chances for error and roll back are greatly reduced.
The result is increased visibility into the delivery pipeline, standardized communication between Dev and Ops and more efficient and accurate delivery of software projects. And the delivery process can scale dynamically as business needs grow.
Here’s how IBM is addressing DevOps, with the launch of SmartCloud Continuous Delivery--an agile, scalable and flexible solution for end-to-end lifecycle management that allows organizations to reduce software delivery cycle times and improve quality. SmartCloud Continuous Delivery is also available on Jazz.net.
LizCrider 270005ET06 标签：  vmware jacques computing community tuc shawn ibm user cloud webcast smartcloud tivoli 6,394 次访问
Join us on the upcoming Tivoli User Community webcast and opportunity for questions, Tuesday, September 18th at 11:00 AM, ET, USA
The benefits of virtualization, have spurred many organizations to move toward a virtual infrastructure. While these organizations enjoy accelerated service delivery and resource optimization to reduced costs for IT resources, they have also frequently experienced a new set of management complexities. The nature of the virtual environment, which calls for a vast network of shared resources is best handled with cloud-computing capabilities on the virtualized infrastructure. In this webcast, the IBM team will address the complexities head on by learning to increase your ROI from your current virtualized infrastructure by building the workload optimized cloud.
About The Speaker: Shawn Jaques, Program Manager IBM SmartCloud Foundation
Shawn Jaques is a program manager in IBM marketing focused on technical marketing of the IBM SmartCloud Foundation portfolio. Prior to this role, Shawn led the Tivoli Cloud product management and strategy team, responsible for identifying market opportunities and setting cloud product and portfolio direction. Shawn's prior experience includes numerous product management, market management and strategy roles within IBM as well as consulting and financial auditing for other firms. Shawn has a Master of Business Administration from The University of Texas at Austin and a Bachelor of Science from the University of Montana. He lives in Boulder, Colorado and is a fitness and outdoor enthusiast.
The Official Tivoli User Community is the largest online and offline organization of Tivoli professionals in the world – home to over 160 local User Communities and dozens of virtual/global groups from 29 countries – with more than 26,000 members. The TUC community offers Users blogs and forums for discussion and collaboration, access to the latest whitepapers, webinars, presentations and research for Users, by Users and the latest information on Tivoli products. The Tivoli User Community offers the opportunity to learn and collaborate on the latest topics and issues that matter most. Membership is complimentary. Join NOW!
Do you know that a special limited time offer went live on August 14th 2012?
The offer ends on November 14th 2012
The promotion cuts 50% list price for IBM SmartCloud Provisioning.
For example, for USA, the price gets down from 250 USD per RVU to 125 USD per RVU.
Moreover you can download from here a 60 day no charge trial.
IBM SmartCloud Provisioning seamlessly integrates with key IBM offerings for advanced levels of monitoring, security,
storage and cloud optimization. Join the cloud management integrations community and learn more about these solutions.
For more information on IBM SmartCloud Provisioning: http://www-01.ibm.com/software/tivoli/products/smartcloud-provisioning/
Version 2.1 of Service Health for IBM® SmartCloud Provisioning, featuring SmartCloud Monitoring, has been released
marvin_goodman 11000085U5 标签：  scp smartcloudmonitoring smartcloud scm monitoring smartcloudprovisioning 4,293 次访问
Version 2.1 of the Service Health for IBM® SmartCloud Provisioning has been released, and is availble for download from the IBM Integrated Service Management Library (ISML, see link below). This offering provides prebuilt integrations between IBM SmartCloud Provisioning and IBM SmartCloud Monitoring, allowing you to increase the performance and resilience of your IBM SmartCloud Provisioning infrastructure through identification of performance issues.
This solution is installed using the IBM Installation Manager. The installation uses the IBM SmartCloud Provisioning PXE server to automatically configure and deploy the necessary monitoring agents to the entire SmartCloud Provisioning infrastructure. Any future machines added to the infrastructure will automatically include the appropriate monitoring agents.
Once installed, this solution will add to the Tivoli® Enterprise Portal, provided by IBM SmartCloud Monitoring, a new custom navigator which provides a logical view of your SmartCloud Monitoring infrastructure. For each grouping in this navigator view there is a pre-built, customizable Workspace to provide information relevant to the selected SmartCloud Provisioning component.
This solution also provides sixteen new monitoring situations, or threshold configurations, to provide alerts for common issues that could affect the availability of your IBM SmartCloud Provisioning environment. In addition, Version 2.1 also includes support for IBM Virtual Image Library and IBM Workload Deployer.
This solution can be downloaded from the IBM Integrated Service Management Library( ISML ) following this link ->
Starting from August 10th 2012, SmartCloud Provisioning 2.1 is generally available.
Here is a synthesis of the new features added:
If you would like to read more about that, see IBM SmartCloud Provisioning announcement letter and IBM SmartCloud Provisioning information center
Antonio_Di_Cocco 060001977Q 标签：  onboarding cloud cloudinit image smartcloud imagelibrary 5,838 次访问
Being VMware one of most used hypervisor, it is a common scenario to have an already exiting cloud environment based on a vCenter hypervisor manager and a new cloud environment based on IBM SmartCloud Provisioning. In this scenario end user would usually starts to sue new environment but working with already existing images, containing known software as well as all required settings fulfilling company rules.
Manually running this task could not be so easy especially if new IBM SmartCloud Provisioning environment is only based on KVM hypervisor> image format conversion is required. Moreover IBM SmartCloud Provisioning requires some specific OS setting that could not be present on the already existing images.
IBM Virtual Image Library would help to overcome all these time consuming inconvenient. New 2.1 version has new feature helping end user to understand which already existing images are ready to be ported to new cloud environment, which are not ready but could be automatically modified and which are not compatible at all (i.e. because based on multiple disks).
The underlying idea is based on the concept exposed in one of my previous blog entry: “Image portability across hypervisors”. During cloud environment registration to IBM Virtual Image Library, an image analysis retrieves all needed information, so that after initial introspection end user will have a clear idea of which images can be used or not to work with IBM SmartCloud Provisioning.
Opening image properties a new tab will appear showing list of executed checks and their results with a brief explanation on what is required to be fully compatible with IBM SmartCloud Provisioning.
At this point end user knows which images can be directly used, which require some modification and which can not automatically changed to run into IBM SmartCloud Provisioning. Next step is to check in desired images into the IBM Virtual Image Library reference repository, so that images can be either just moved to new cloud environment, or modified o be High scale low touch ready or moved to IBM SmartCloud provisioning environment and automatically modified to be ready for deployment. IBM Virtual Image Library also checks if CloudInit is present on the image. If not it is automatically installed and activated making the image compatible with High scale low touch. In this way the new imported image is ready to be deployed using package script and add-ons using workload deployer delivered with IBM SmartCloud Provisioning. I consider this new feature very useful to start working with new IBM SmartCloud Provisioning allowing end user to easily and quickly populate new cloud environment. Key items saving user time are: · Having a clear list of already compatible images · Automatically configure image to be deployed through high scale low touch hypervisor manager · Reuse already existent images with few clicks without migrating any data · Automatically install CloudInit allowing to use images in more complex scenario using Workload Deployer Additional information about previous topics can be found at IBM info center pages:
At this point end user knows which images can be directly used, which require some modification and which can not automatically changed to run into IBM SmartCloud Provisioning.
Next step is to check in desired images into the IBM Virtual Image Library reference repository, so that images can be either just moved to new cloud environment, or modified o be High scale low touch ready or moved to IBM SmartCloud provisioning environment and automatically modified to be ready for deployment.
IBM Virtual Image Library also checks if CloudInit is present on the image. If not it is automatically installed and activated making the image compatible with High scale low touch. In this way the new imported image is ready to be deployed using package script and add-ons using workload deployer delivered with IBM SmartCloud Provisioning.
I consider this new feature very useful to start working with new IBM SmartCloud Provisioning allowing end user to easily and quickly populate new cloud environment. Key items saving user time are:
· Having a clear list of already compatible images
· Automatically configure image to be deployed through high scale low touch hypervisor manager
· Reuse already existent images with few clicks without migrating any data
· Automatically install CloudInit allowing to use images in more complex scenario using Workload Deployer
Additional information about previous topics can be found at IBM info center pages:
In this new post I would like to introduce a new function added in Image Construction and Composition Tool (ICCT) 1.2, it is the capability to extend a Windows base image available in IBM Smart Cloud Provisioning 2.1.
In fact in ICCT 1.2 it's possible to:
- import a Windows base image available in IBM Smart Cloud Provisioning 2.1
- extent it adding Windows bundles created using ICCT 1.2
- capture it in order to have in IBM Smart Cloud Provisioning 2.1 a new extended Windows image
It is provided using the same User Interface and the same steps already available for Linux and AIX support.
The new extended image is now ready to be deployed showing the bundle configuration parameters from the IBM Smart Cloud Provisioning 2.1 User interface.
In ICCT 1.2 a new specific Windows Enablement bundle has been provided to support the Windows images and it is described in the screenshot below:
It contains the Activation Framework needed by ICCT 1.2 to install and configure bundles based on the Windows IBM VSAE.
For the Windows bundles created using ICCT 1.2 it is also possible to provide in the tabs Installation/Configuration/Reset the scripts for the installation, configuration and reset steps invoked by ICCT when an image is extended.
The Windows support is provided for the following Operation Systems:
SandraWeiss 060000BCJJ 标签：  security provisioning image virtualization cloud smartcloud_security image_management smartcloud solutions maintenance endpoint 4,941 次访问
The solution Endpoint security for SmartCloud Provisioning v2.1 has been published on IBM Integrated Service Management Library (ISML).
The purpose of Endpoint security for SmartCloud Provisioning v2.1 is to demonstrate how IBM Tivoli Endpoint Manager can be integrated with the IBM SmartCloud Provisioning Infrastructure.
Endpoint security for SmartCloud Provisioning will generate the components required by IBM SmartCloud Provisioning 2.1 to automatically install IBM Tivoli Endpoint Manager agents when deploying virtual systems. This will allow cloud administrators to easily maintain compliance over their virtualized network.
IBM SmartCloud Provisioning v2.1 as well as IBM Tivoli Endpoint Manager v8.2 need to be available. If you are participating in the IBM SmartCloud Provisioning v2.1 beta and have IBM Tivoli Endpoint Manager, consider using Endpoint security as well.
Demo videos about Endpoint security for SmartCloud Provisioning v2.1 can be found here: https://www.ibm.com/developerworks/servicemanagement/cvm/cmi/security.html
This solution is available via the IBM Integrated Service Management Library (ISML). You can find it here -> Endpoint security for SmartCloud Provisioning v2.1 Beta Trial.
We welcome any and all feedback.
marvin_goodman 11000085U5 标签：  itmfve tcr tip cognos monitor teps itmcmd agent dashboard smartcloud tdw tacmd tep tems itm smartcloudmonitoring oslc 6,309 次访问
The next release of SmartCloud Monitoring, which includes new releases of IBM Tivoli Monitoring (ITM) and IBM Tivoli Monitoring for Virtual Environments (ITM for VE), is currently in development, and we would like to invite customers old and new to participate in our Early Adopter Program, our fancy name for a beta program (because we HAVE to have an acronym here at IBM, and how do you make an acronym out of "beta?")
This open program will allow you to download our Beta code and provide feedback and guidance on the new functionality, product improvements, and code quality of IBM Tivoli Monitoring "vNext." As the SmartCloud brand continues to expand, this beta will help long-time customers see that the ITM foundation is strong, and being continually enhanced to help us all adapt to the disruptive influence of "Cloud" on our IT management responsibilities. Both ITM and ITM for VE are still separately available (and are the products where the code enhancements you'll see reside), while the SmartCloud Monitoring bundle makes it convenient for customers to purchase the two products together.
This ITM Community site will enable you to download Beta drivers, see important announcements, interact directly with product developers and planners, and provide the ITM development team your valuable opinions about our planned product enhancements. As we develop this release, however, we're already doing long-range planning for the "N+1" release that will follow this one, so long-range enhancement requests are a good topic of discussion as well.
Please contact Nathan Bullock (mailto:email@example.com) if you have questions about the ITM vNext Open Beta Program.
PQC6_jim_Markham 120000PQC6 标签：  smartcloud provisioning storage kvm management tsm backup smartcloud_resilience cloud esx solutions integration vmware 5,039 次访问
There is a new white paper available on the IBM Integrated Service Management Library ( ISML ) that explains how to use Tivoli Storage Manager to back up a VMware virtual machine that was deployed by the Workload Deployer in IBM SmartCloud Provisioning version 2.1.
The white paper explains how to locate, and back up the virtual machine in VMware using IBM Tivoli Storage Manager, and how to restore the virtual machine to the Workload Deployer environment.
The white paper can be downloaded from the IBM Integrated Service Management Library ( ISML ) following this link -> Backing up and Restoring Workload Deployer Virtual Machines Deployed in VMware
marcese 11000065AG 标签：  smartcloud isaac icon script python build icct image provisioning 5,736 次访问
In this new post I would like to describe how you can script the building of virtual images using the Image Construction and Composition Tool provided by IBM Smart Cloud Provisioning.
The upcoming release of IBM Smart Cloud Provisioning 2.1 embeds, among other things, a new version of the Image Construction and Composition Tool. Image Construction and Composition Tool allows to build virtual images that are self-descriptive, customizable and manageable; at the end it produces Open Virtualization Appliance (OVA) images that can be deployed into a cloud environment.
One of the new features of this tool is the capability of performing image management operations directly through a command-line interface. This capability enables a set of new use cases through a scripting environment.
The command-line interface of Image Construction and Composition Tool provides a scripting environment based on Jython (i.e. the Java-based implementation of Python) and in addition to issuing commands specific to the Image Construction and Composition Tool, you can also issue Python commands at the command prompt.
Using such interface, you can manage the Image Construction and Composition Tool remotely since you can download it to any machine and then point to the system where the tool is running: it communicates with the server using the HTTPS protocol so that all the communications are encrypted. The command-line interface can be installed on both Linux and Windows operating systems and can run in both interactive and batch modes.
Anything that can be managed in the Image Construction and Composition Tool is modelled by a resource object on the command-line interface that exposes a set of methods for performing the related management actions. The following objects are available: software bundles references (for defining software configurations to be deployed on a virtual machine), cloud providers references (for defining the hypervisors used by Image Construction and Composition Tool to build and capture images), images references (for handling virtual machine images to be used for import, extend, capture and export operations) and users references (for administering the user of Image Construction and Composition Tool ).
Once you have downloaded and configured the command-line to start a new session in interactive mode you can issue the following command from a shell prompt:
<icct_cli-install-dir>/bin/icct -h <icct server> -u username -p password
One you get the interactive shell you can start issuing commands.
Here are a few examples.
To get a list of all the images for a cloud provider, you can use a command like the following:
To import a software bundle and wait for the import to complete, you can use a set of commands like the following:
>>> importingBundle = icct.bundles.import('http://localhost/myBundle.ras')
>>> if importingBundle.currentState == 'import_failed':
... print 'Bundle import failed!'
To get a list of all the images, you can use a command like the following:
>>> allImages = icct.images
And so on.
You can also use the Image Construction and Composition Tool command-line interface in batch mode, by creating your own script and then launching it. For example, to run a script called myScript.py you can issue the following command:
icct -h <icct server> -u username -p password -f myScript.py arg1 arg2 arg3
A few samples come directly with Image Construction and Composition Tool. They are located under the following directory:
They cover some of the Image Construction and Composition Tool basic flows, such as creating a new cloud provider configuration, importing an image, extending an image, etc..
You can use them as a starting point for creating your own workflows.
That's all for now.
We have just provided a quick introduction of all the capabilities of the Image Construction and Composition Tool command-line interface. If you are interested in discovering more about Image Construction and Composition Tool, its command-line interface and SCP 2.1, you can have a look at what is included in IBM Smart Cloud Provisioning beta code:
If you ever observed babies playing, you'll notice that at a certain point in their development, the idea of property comes into the game: "this is my toy, I'll not let you play with that". Usually parents needs to invest some time to make the baby understanding the value of sharing things: "the toy remains yours, but you can enjoy sharing it with other babies... If you are kind and polite the other babies may share in their turn their toys with you". Usually this trick work. The next step will be that they will start adding "special conditions": "you can use my blocks but only the blue ones" or " you can play with this doll but I'll not borrow you the pink dress". A different stories comes when sharing can make you save a lot of money: you do not need to buy the same toy your baby saw another baby is using if they can share it...
Did you ever try to apply this model to cloud computing?
I know it may sound strange at a first glance, but there are some similarities...
Let's start from the last example, kids sharing the same toys: doesn't it look like familiar to the idea of sharing the same master image? In a lot of cases I do not need my own master image, I can use the same one another user is using.
But the "conditions" apply: "you can use my same master image, but I do not want you to stay on my own network!" or "you can use my same master image, but you cannot use my package scripts!" ... Not a lot of differences from"you can play with my doll but I'll not give you the pink dress" or " you can play with my blocks but you can use only the blue ones"
There will be situations is which you even do not want to share the master image at all: "this is mine, it's my treasure, I have my own information there and I do not want you to see that"...I'm pretty sure you've seen babies doing that with their favorite teddy bear ;-)
I hope these few examples made you look at objects authorizations in a cloud with different eyes...
Anyway, the problem is there, a cloud is typically a shared environment and we do not want to have everybody to have access to everything. Privacy is important.
Let's see one of the ways to resolve this issue. We could give to every individual/user the right to determine who can access his own objects. "who" of course can be a single user or a group of users. Depending on the role of the user he can have access to different objects.
The cloud administrator for example can decide who can access a specific network, who can see a specific cloud group; the cloud catalog editor can decide who can access to which master image, or to which package scripts (package scripts are the building blocks for patterns); the image deployer can decide if somebody else can see the details of his images. In some cases he may also be interested in letting other users accessing his own volumes.
With the same ease a user can decide either to give full access, read-only access or no access at all to each of its own resources/objects.
Using such fine grained access policy makes the cloud software really flexible to fit various adoption models like a classical private cloud or a more complex environment like the ones a cloud service provider may have.
In case of enterprises and cloud service providers, authorization and network segregation are critical prerequisites for building and managing a secure cloud environment.
For this SmartCloud Provisioning is the right choice.
You can also rely on a robust auditing mechanism that allows you to track what is happening in the cloud: who logged in/out, user creation/deletion/update, data access attempts either if they are successful/unsuccessful, virtual machine instance creation/deletion update and far more...
If you are interested in walking through this model, you can have a look at what is included in IBM SmartCloud Provisioning beta code:
Kimic 270002JHJ8 标签：  smartcloud continuous devops delivery provisioning patterns 2 条评论 7,579 次访问
This goes out to all the Operations guys and gals. Have you been tasked with getting your IT organization to be more efficient, more effective..."more with less?" At the same time, your development teams are expected to delivery new applications at warp speed while you have specific service level agreements to meet governing the stability of your production environments. Speed.... stability.... seems diametrically opposed? If you haven’t heard of DevOps yet--the methodology of bringing development and operation teams together to collaborate, integrate and deliver more robust applications to the marketplace more efficiently and more effectively—its a cool new way of thinking and doing for all teams involved.
IBM has jumped into the deep-end of DevOps with the recent announcement of the SmartCloud Continuous Delivery beta. This solution will allow the integration of new and existing tools to automate and enhance the delivery pipeline of applications end-to-end. This post will hopefully give you some ideas on how you might be able to utilize DevOps to bring tangible changes to your IT organization..
First off, is your organization using cloud computing effectively today? Ops teams may already be utilizing some form of virtualization to increase efficiency and effectiveness. Aligning DevOps methodology, cloud can automate and reduce routine daily tasks and free up resources to focus on different innovation. Have a closer look how SmartCloud Continuous Delivery, in conjunction with IBM SmartCloud Provisioning, can help mobilize teams to move to DevOps.
Fact or Fiction?
I won't have to provision environments for development teams any more!
Fact - Ops can define the system patterns for developers to self-provision so they are no longer dependent on the Ops team. There will likely be times when Ops teams do want to provision environments that are needed but it doesn't have to be as often.
I will never be able to monitor all the virtual systems to validate they meet the security requirements of my company
Fiction - Patterns can be built based on the compliant virtual images that Ops maintains and tracks. Development can then self-provision these pre-defined patterns. Ops an update existing patterns and upgrade deployed VMs as required.
I can define network isolation and resource constraints to ensure the integrity of my cloud for my customers
Fact -The automated deployment scripts define the access level of authorized users and groups--these stored artifacts preserve the authorization specific users and groups are given allowing controlled multi-tenancy in a cloud.
The ability of developers to be able to standup their own environments is helpful but the consequence will be tons of stagnant VMs hanging around
Fiction - Build artifacts can be stored in the asset manager which tracks each state and age of the provisioned VMs. Policies are used to ensure VMs are maintained only as long as appropriate for a particular deployment (for example, personal deployment vs long test run deployment)
I hope this taste of Fact or Fiction gives you a sense of how DevOps can transform collaboration and effectiveness for both Development and Operations teams. The Enterprise DevOps Blog here will keep you up to date and provide additional information around DevOps. You can also test drive highly-scalable, low-touch cloud with a SmartCloud Provisioning no-charge trial.
A new beta drop for IBM SmartCloud Provisioning is available.
Backing up IBM SmartCloud Provisioning's Persistent Volumes and Infrastructure with Tivoli Storage Manager Client
PQC6_jim_Markham 120000PQC6 标签：  cloud solutions smartcloud_resilience vmware backup esx smartcloud kvm tsm integration provisioning 9,577 次访问
Two new white papers are available on the IBM Integrated Service Management Library ( ISML ) that explain how to use Tivoli Storage Manager to back up different areas within IBM SmartCloud Provisioning.
The first white paper provides information on how to use Tivoli Storage Manager Backup-Archive client to back up and restore the boot volume of an IBM SmartCloud Provisioning persistent virtual machine and how to make periodic back ups of a normal volume, and select and restore a particular backup.
This white paper can be downloaded from the IBM Integrated Service Management Library( ISML ) following this link -> Backing up IBM SmartCloud Provisioning's Persistent Volumes with Tivoli Storage Manager Client
The second white paper provides information on how to use Tivoli Storage Manager Backup-Archive client to back up and restore the following components of the IBM SmartCloud Provisioning infrastructure: the Preboot Execution Environment ( PXE ) server, the web console configuration, and the HBase data store.
This white paper can be downloaded from the IBM Integrated Service Management Library( ISML ) following this link -> Backing up IBM SmartCloud Provisioning's Infrastructure with Tivoli Storage Manager Client