ibm software group software distribution of clearcase artifacts with tivoli software eitan shomrai,...

IBM Software Group

®

Software Distribution of ClearCase Artifacts with Tivoli Software

Eitan Shomrai, IBM Software Group – Rational

Yuval Kimel, IBM Software Group - Tivoli

IBM Software Group | Rational software

Agenda

Goal, use case and the problem Solution

Tivoli Concepts and FrameWork ClearCase UCM & Tivoli Integration

Summary and solution workflow Q&A


Gain end-to-end control over the software development lifecycle

Deployment ? How ?


The problem

The lack of control, audit-ability and trace-ability from the development to the deployment phase.


Deployment management problems

Large and heterogeneous deployment base (i.e. multiple servers, platforms)

Operations staff may not be aware of SCM practices Separation of release management and

deployment Lack of Inventory management (what is installed

where ?) Maintenance of home grown tools results in

spending $$$ that may not yield a significant return


Rational ClearCase Builds what Tivoli manages

Optimizing software development Optimizing use and management of IT

Tivoli Configuration Manager provides enterprise class distribution Capabilities

ClearCase provides Enterprise Class Change Management Capabilities


The Solution by combining ClearCase and Tivoli

1. ClearCase baselines define what is to be distributed.

2. A ClearCase UCM stream provides the source for the Tivoli Software Package.

3. Tivoli provides Software deployment.


IBM Rational ClearCase fundamental concepts:

src/src/

VOB

foo.hfoo.h bar.cbar.cfoo.cfoo.c srcsrc

foo.cfoo.c foo.hfoo.h

ViewView

DeveloperJoin aProject

MakeChanges

DeliverChanges

RebaseStream/View

UCM developer flow:


Tivoli Concepts – Tivoli Framework

Tivoli Server Hosts TMR information

Tivoli Managed Region(TMR)

End pointsTivoli Managed Node &

Source host

`

Gateway


IBM Tivoli Configuration Manager • Inventory :

- Mobile client support- Management across firewalls- More than doubles software recognition

capability for UNIX and PC- Decreased hardware scan time by 50%,

software scan time by greater than 50%- More granular scanning of asset configuration

• Software Distribution• Desired configuration management through

reference models- Mobile client support- Management across firewalls - Activity planner which significantly reduces

effort required to distribute multiple packages to large number of endpoints

- Byte level differencing which dramatically lowers network traffic

- Dependency checking to proactively prevents distribution failures

New!!Single Product

Lower Price


NetWare

EnterpriseWide

Inventory

BACKUP(DIR)

D:\PRODUCTDIR

.........

IBM

IBM

UNIXPC NT

OtherRepositories

Tivoli Inventory

HW and SW scanning New HW, BIOS and DMI scans

Open database support Integrated query/reporting WAN-Smart architecture


Package EditorMSI, InstallShieldAIX installp, Solaris pkgadd, Linux RPM Supported in Software Package Editor


Types of Software Package

SourceFiles

Software Package Block

SourceFiles

.spb.sp or.spd

SourceFiles

Source Host

Software Package Definition


Package distribution


Tivoli Change Configuration Management


MDIST CONSOLE


The Solution architecture

Tivoli package

Tivoli package

Clearcase VOBClearCase View

Tivoli Server

Tivoli Infrastructure

Tivoli Endpoints

.SPD

.SPB

Gizmo_BL Gizmo_VOB


The UCM stream structure in the “gizmo” project

Development Streams

Integration Stream

Read-Only Deployment Streams

TEST PROD


Building Tivoli Package from ClearCase baseline

/vobs/gizmo_VOB exe auto_gizmo … recover_gizmo …..

Create baseline: gizmo_050104_BL

gizmo_int

TEST_gizmo

RebaseName Tivoli packages after ClearCase baselines !

Create

Package

Use view extended path names e.g.:

/view/gizmo_deploy_view/vobs/gizmo_VOB (UNIX)

M:\gizmo_deploy_view\gizmo_VOB (Windows)


Setup Deployment Targets

subs_gizmo_uat

serverA serverB serverC

Apps_gizmo

subs_gizmo_prod subs_gizmo_uat

gizmo_050104_BL

Profile manager


Solution WorkflowProject Manager•Uses ClearQuest•Assigns defects to developers

Developer•Rebase Workspace •Work on the defect assigned to her/him•Deliver to Integration

Integrator•Integrate changes•Build•Report defects if build fails•Create baseline

Operations•Rebase deployment workspace•Create Software Package•Deploy Software package to the end-points(Test/Production Servers)

Tester•Application deployed on a Test Machine•if Test failed:• Roll back Baselines and Report Defects•Else: Deploy solution on (i.e. Test Servers)

Production•Application Deployed in Production•Roll back Baselines if failure•Report Defects if found•Deploy solution to Production Servers

Deliver

Rebase

Rebase

Re-Deploy

Deploy

IBM Software Group

®

Tivoli Standards


Software Package Details:Packages Definition

Establish standards for packages, such asSingle Package or package / platformUse of Add Directory action

Specify different destination directoriesUse of Containers

Leverage conditionsUse of Variables

Destination directory based on OS_TYPE:$(target_dir)_$(os_name)


Software Package Details:Sample OS Conditions for Containers

Operating System os_family os_name os_version os_release

AIX 4.3.3 UNIX AIX 4 3

AIX 5.1 UNIX AIX 5 1

Solaris 2.7 UNIX SunOS Generic 5.7

Solaris 2.8 UNIX SunOS Generic 5.8

Windows 98 PC Windows_98 2222+_A_ 4.1

Windows 2000 PC Windows_NT 2195 5.0

Windows NT 4.0 SP6 PC Windows_NT 1381+Service_Pack_6 4.0

Windows XP PC Windows_NT 2600 5.1

Linux Intel UNIX Linux #1 2.4.10-4GB


Software Package Details:Package Container Example

Container: AIXCondition: os_name==AIXAction: ADD DIRECTORY:

Source: /view/<viewname>/vobs/vobname/app1/deploy/91.00.00.0001/AIX/*Target: $(target_dir_$(os_name))/app

Container: Windows_NTCondition: os_name==Windows_NTAction: ADD DIRECTORY:

Source: /view/<viewname>/vobs/vobname/app1/deploy/91.00.00.0001/Windows_NT/*Target: $(target_dir_$(os_name))/app

Container: genericAction: ADD DIRECTORY:

Source: /view/<viewname>/vobs/vobname/app1/deploy/91.00.00.0001/generic/*Target: $(target_dir_$(os_name))/app1

• Variables:Variables:‾ target_dir_Windows_NT=/applicationstarget_dir_Windows_NT=/applications‾ target_dir_AIX = /usr/local/applicationstarget_dir_AIX = /usr/local/applications‾ target_dir_SunOS = /usr/local/applicationstarget_dir_SunOS = /usr/local/applications‾ target_dir_HP-UX=/usr/local/applicationstarget_dir_HP-UX=/usr/local/applications

IBM Software Group

®

Rational Promotion


Artifact Movement

Code Repository

ClearCase Repository Server and

Tivoli Managed Node

Tivoli Managed RegionDestination (End point)e.g. UAT,IST and PROD

Step 1: Manage/Build codeStep 2: Create Tivoli packageStep 4: Make changes to code

Step 3: Deploy PackageStep 5: Re-deploy


Rational Promotion - StandardsChanges

Baseline names View names Profile Manager names Package names and versioning Directory structures


Rational Approach - StandardsSample Project, Baseline, & View Names

Project Name: <app>_<major>.<minor>Baseline Name (project level promotions): <project>.<date>Baseline Name (component level promotions): <project>_<comp>_<major>.<minor>.<date>View Name = Baseline Name

Where:• <app> = Application/Project name • <major> = Major Version• <minor> = Minor Version• <project> = Project Name• <comp> = Component Identifier (if component level promotion)

− Corresponds app directory• <date> = generated by Rational


Rational Approach – StandardsPackage Names

Package Name to contain: Project name Component Identifier (if component level promotion)

• Corresponds app directory Lifecycle

Package Version to contain: Baseline major release number Baseline minor release number Software Package patch number


Rational Promotion - StandardsSample View Structure

Top level directory: /view/<view name>/vobs/<vobname>/<app>/deploy

Underneath deploy:Develop standard directory structure to ease packaging

ibm software group software distribution of clearcase artifacts with tivoli software eitan shomrai,...

Documents