sonic-3: creating large scale installations & deployments andrew s. neumann principal engineer...

SONIC-3: Creating Large Scale Installations & Deployments

Andrew S. NeumannPrincipal Engineer

Progress Sonic

© 2007 Progress Software Corporation2 SONIC-3: Creating Large Scale Installations & Deployments

Agenda

Use Cases Challenges of Configuration & Deployment Overview of SDM Using SDM for Configuration & Deployment Summary Time for Questions


Depends upon context Could be a centralized server farm

• 10, 100, 1000+ servers in racks

Could be location of server(s) for Management Domain host(s)• For multiple remote sites

• For replicated Management Domain

Could be a room at each remote site

Definition: “Server Room”


Centralized “Server Farm” Replicated Management Domain Multiple Remote Locations

Use Cases


Typically performed from remote console 10+, 100+, 1000+ machines Similar, but not quite identical, configuration

on each host

Centralized Server Farm

Aspects of Installation & Configuration


Might be done in conjunction w/centralized or remote server room deployment

Similar Domain Manager configurations on 2 hosts• Primary

• Backup

Replicated Domain Manager



Similar to centralized server room deployment, might range from 10-1000+ sites

Effectively have many remote “server rooms”, each of which must be configured and updated

Spread over wide geographical area, physically remote from central location

Remote Server Room Sites



Lifecycle for Server Room Deployments

Acceptance Platform

Integration Server

Integration Server

Integration Server

Development Platform

DevelopmentMachine

DevelopmentMachine

DevelopmentMachine

DevelopmentMachine

DevelopmentMachine

Staging Platform

Source CodeControl

Test Platform

Test Platform

Production Platform

Production Server

Production Server

Production Server

Promote Promote Promote

Common approach for server rooms: develop, test, deploy…


Go to the Server Insert CD Run character mode or GUI install

• Sonic™ Product Installer• Install individual products (e.g. SonicMQ®, Sonic ESB®,

etc.) Configure and start Domain Manager on central host Create additional containers, management objects

and components Set properties to desired values Install Sonic products on one of the many servers in

the domain, create container boot files, etc. Rinse, lather, repeat...

Installation

Conventional Installation Approach


Configuration of full Sonic domain is complex May be thousands of properties overall; often

inconsistently set Inconsistent naming conventions Failure to create component, container, etc. Manual recreation of configuration on each remote

machine, leading to mistakes Extensive upgrade process TIME!

The Problem: Server Room Configuration Complexity

Issues With Configuration & Deployment


Wouldn’t it be nice if there was something to:• Avoid repetitive manual tasks

• Validate configurations

• Enforce naming conventions

• Recreate a configuration consistently

• Ease the upgrade process

Addressing the Common Issues


A tool that allows the creation and deployment of Sonic configurations in a reusable and repeatable fashion

A tool used for several years by the Sonic Professional Services Organization in support of large scale customer deployments• Now becoming an officially released and

supported product

The Solution: Server Room Configuration with SDM

Sonic Deployment Manager


Model-based• XML model • Supports validation• Higher level abstraction

One model used for one or more domains Support for naming conventions Support for deployment-specific parameter values Creation of Domain Manager

• Including initial creation/configuration of Directory Service

Best practices “built in”

SDM Basics


<Model>

<GeneralConfig> <ModelName>DSBackupWithSharedDir</ModelName> <Version>1.0</Version> <Description>Sample Model for DS backup, using a shared directory</Description> </GeneralConfig>

<DSReference> <DomainName>dmDSBackup</DomainName> <BasePort>2600</BasePort> <DSHostName>MyHost</DSHostName> <User>Administrator</User> <Password>Administrator</Password> <CAAConnectionURL>tcp://MyHost:2602</CAAConnectionURL> </DSReference>

<DSHost> <License>xh1qypqa3gcX</License> <BrokerName>managementBr</BrokerName> </DSHost>

<DSBackup> <License>xh1qypqa3gcX</License> <BrokerName>managementBakBr</BrokerName> <SharedDir>/tmp/sdmShared</SharedDir> </DSBackup>

</Model>

Sample Model: Backup DS Using Shared Directory


Run the script to process the model file:

cleanInstallation ./Models/DSBackupWithSharedDir

Sample Model: Processing


Sample Model: Resulting Configuration

View of Created Components


Mode dictates steps SDM performs during clean installation or update of existing configuration

3 different modes:• Configuration

• Resources

• Default (= Resources + Configuration)

SDM Operational Modes


Runs centrally for all machines in the domain Model file used to create configuration within

the Directory Service for hosts in the domain No manual intervention required

SDM Configuration Mode Basics


Same model file used on each machine Necessary runtime software laid down No manual intervention required during

installation process Virtual host name support provides means to

apply specific parts of model to specific host

SDM Resources Mode Basics


SDM Default Mode (Example of Clean Installation)

Sonic

Installation CD

SDM Model

SDM

Environment

Tailoring

Parameters

Server Host

for

Sonic

Domain Manager

Install Resources

Configure

Run SDM on server that will host Sonic Domain Manager:• Uses model to determine required

installs• Installs SonicMQ®, SonicESB®, etc.• Creates Directory Service and Agent

Manager– FT and cluster support for Management

Brokers an option

SDM then creates configuration:• Starts the Management Broker, Directory

Service and Agent Manager• Configures the running Directory Service

with information from the model


SDM Resources Mode (Example of Update)

Sonic

Installation CD

SDM Model

SDM

Environment

Tailoring

Parameters

Domain Manager Server

Configure

Connect

Run SDM again on a clean remote machine:• Uses model to find required

installs• Installs SonicMQ®, Sonic ESB®,

etc. (if configured)• Creates scripts for container(s)

Remote Host

Install

Run SDM on Domain Manager server to update existing Domain:• Configures the running

Directory Service with information from the model for the remote host


Completely Automated Server Installation Software Life Cycle support

• Development -> Test -> QA -> Production

Versioned Domain Configurations Repeatable Installation of Sonic Deployment Re-Installation of a Sonic Deployment Updates of an existing Sonic Deployment

Simplification of Installation & Configuration


Run SDM script with Model and Sonic Products CD(s)

End result = desired Sonic Installation Same model used for multiple hosts No manual intervention required Enforces naming conventions

Automated Server Installation


One model may be used for each phase:• Development -> Test -> QA -> Production

Hosts, and number of hosts, can change No changes required to model Ensures production deployment is as

successful as test environment

SDM for Software Lifecycle Support


Development Platform

Development

Machine

Lifecycle for Server Room Deployments Using SDM

Production Platform

Production Server

Production Server

Production Server

Promote Promote Promote

SDM-based approach for server rooms: develop, test, deploy…Staging Platform

Source CodeControl

Test Platform

Acceptance Platform

Integration Server

Integration Server

SDM Model

Development

Tailoring

Parameters

Production

Tailoring

Parameters

Integration

Tailoring

Parameters

Test

Tailoring

Parameters


Can add model files to source control As deployment is updated, can track changes Simple to revert to earlier deployment

topology if necessary Simple to track down issues that arise as

deployment is modified

Versioned Server Setup


Model is used to create each new installation on a given server

No variance from Server A to Server B• Consistency across all servers

• Valid configuration on all servers

Repeatable Installation


Recreate deployment on replacement remote host• Model file ensures EXACT replica

No concerns if host machine needs to be replaced• Consistency

• Validity

Handling Hardware Failure


Reverse Engineering -> model of existing deployment Model may be “forward engineered” to recreate

deployment Simplifies upgrade process

• Deployment of older version may remain in place

• Deployment of newer version done w/o shutting down old deployment

• Reliability!

Version Migration for Existing Deployments


In Summary

Manual creation of large-scale server room deployments• Complex configurations• Many opportunities for errors• Repetitive• Time consuming

SDM:• Automates, simplifies the process• Reusable, repeatable • Eases upgrade process• Reduces errors -> time savings


For More Information…

Please contact your authorized sales representative for additional details


Questions?


D I S C L A I M E R

Don’t Quote Me On This…

This Question & Answer session may include information about potential future products and/or product enhancements.

What I am going to say reflects our current thinking, but the information contained herein is preliminary and subject to change. Any future products we ultimately deliver may be materially different from what is described here.

D I S C L A I M E R


Thank you foryour time

sonic-3: creating large scale installations & deployments andrew s. neumann principal engineer...

Documents

sonic domain

server room deployments

progress software corporation

configuration deployment

sonic products

sonic esb

remote server rooms

sonic product installer