March 2014 CMUG Minutes

Configuration Management – User Group (formerly: Marimba Users Group)

www.CM-UG.com

© Copyright July 10, 2014 [email protected]

Conference Call Information

All CM-UG calls unless otherwise noted will use

the following dial in information:

US Conferencing Number: 1-855-747-8824

CODE: 236 606 4030

March 19th 2014

Details:

1. Marimba / Symphony transition details

2. Marimba 8.3.02 – Bare Metal OS Provisioning

3. Webex for April 2014

http://www.cm-ug.com/newsletters.htm

http://www.symphonyteleca.com/company/newsroom/press-releases/symphony-teleca-announces-major-release-of-symphony-marimba-client-automation-solution/


www.CM-UG.com


Upcoming CM-UG Events

2014 CM-UG meeting dates:

Wednesday, April 16th, 2014 @ noon Central time

Wednesday, May 21st, 2014 @ noon Central time

Wednesday, June 18th, 2014 @ noon Central time

Wednesday, July 23rd, 2014 @ noon Central time - 4th week

Wednesday, August 20th, 2014 @ noon Central time

Wednesday, September 17th, 2014 @ noon Central time

Wednesday, October 15th, 2014 @ noon Central time

Wednesday, November 19th, 2014 @ noon Central time

Wednesday, December 17th, 2014 @ noon Central time

Upcoming Events

Reminder:

The CM-UG call is normally the 3rd Wednesday of each month at 12 noon central time.

The CM-UG calendar is also located here > http://calendar.cm-ug.com

http://calendar.cm-ug.com/




http://www.linkedin.com/groups?gid=1774296


www.CM-UG.com

April 2014 Webex Information

https://bmc.webex.com/bmc/j.php?MTID=m32de58a3a0f1986794583d556ad56c93

Topic: Marimba User Group

Date: Wednesday, April 16, 2014

Time: 12:00 pm, Central Daylight Time (Chicago, GMT-05:00)

Meeting Number: 751 235 352

Meeting Password: 123

US Conferencing Number: 1-855-747-8824

CODE: 236 606 4030

https://bmc.webex.com/bmc/j.php?MTID=m32de58a3a0f1986794583d556ad56c93

Symphony Teleca - Marimba Bare Metal Provisioning

March 29, 2014

Nitish Shrivastava

Copyright © 2013 Symphony Teleca Corp. All rights reserved. CONFIDENTIAL AND PROPRIETARY 5

• Architecture

• Preparation

• Workflow

• In progress items

• Demo

Agenda

Architecture


Architecture

Transmitter

Laptop

Desktop

Workstation

Legacy PC Proxy DHCP / PXE

TFTP Service

DHCP

OS Image

Boot Image

Profile


Flow

• New Transmitter Services

• Inbuilt proxy DHCP Service

• PXE server that offers boot image to endpoint

• Inbuilt TFTP service

• Offers boot image over tftp service

• Endpoint starts

• Client sends DHCP-request (IP and PXE-details)

• ”Regular” DHCP-server responds with IP

• Transmitter responds with PXE-details (boot-menu)

• Client presents boot-menu

• Client discovers boot-servers

• Transmitter responds, providing a client-specific boot-file etc

• Client downloads boot-file over TFTP

• Transmitter TFTP-server serves the boot-file and following files

• Client launches pre-boot OS (WinPE)

• WinPE comes with custom script that download appropriate channels (info) and go ahead with disk partition and OS installation

Preparation


Preparation

• Channels needed

– OS image (s) for OS/Arch – http://products.marimba.com/Win7Image

• Content rep channel for OS Image (Wim)

– Migration profile - http://products.marimba.com/SalesProfile

• Content rep channel that contains detail about OS Image, credentials etc (created through UI)

– Profile Info channel - http://products.marimba.com/Info

• Content rep channel that contains file ‘mapping.txt’

• Should contain mapping of mac ids and profile to be used. E.g.

– 00:0c:29:41:e8:a6=http://products.marimba.com/SalesProfile

http://products.marimba.com/Win7Image

http://products.marimba.com/SalesProfile

http://products.marimba.com/Info

http://products.marimba.com/SalesProfile


Preparation

• Channels needed

– Boot image specific to OS/Arch/Custom definition

• Prepare boot image using WAIK (UI available in marimba)

• Special properties

– type=BootImage [this type channels are loaded in tx as potential boot image for requests]

– bootfile=pxelinux.0 [points to the boot loader file (set implicit by UI)]

– boot.arch=0 [Sets the architecture; this will be mapped to architecture mapping for specific/all endpoints. In a general note, you can use 0 for x86, 1 for x64, 2 for x86_embedded and so on]. There must be 1 boot file per architecture. You cant have multiple boot channels with same arch property.

• WinPE image to have config.txt (inside windows/system32) and should have two properties

– Channel.url (channel url for info channel)

– Install.type=baremetal (to notify that it is in baremetal cycle and so it should ignore migration steps)

DHCP & PXE/TFTP on different boxes

Recommended Configuration


Architecture

Transmitter

Laptop

Desktop

Workstation

Legacy PC Proxy DHCP / PXE

TFTP Service

DHCP

OS Image

Boot Image

Profile


Preparation

• Transmitter settings

– Set transmitter property ‘osd.services.enabled=true’ to activate pxe and tftp services in transmitter

– Set transmitter property ‘osd.pxe.disable=false’ to enable pxe service, with this both tftp & PXE will start

– Set transmitter property ‘osd.mtftp.group’. This should be the multicast group that the server would use to monitor UDP requests during DHCP/PXE phase

– Set transmitter property ‘osd.macdefinition.path’ and point to the path of file that contains mac mapping (whether mac is activated for OS migration and what boot file it should pick). E.g.

<?xml version="1.0" encoding="UTF-8" ?>

<hosts>

<host mac="abcd" activation="true" bootindex="0"><host/>

<host mac="efgh" activation="true" bootindex="1"><host/>

<host mac="general" activation="true" bootindex="0"><host/>

</hosts>

– Set transmitter property ‘osd.macdefinition.sync.interval’ to set sync interval of activation file

– Set transmitter property ‘osd.all.activated’ if you want to activate all machines by default

– Set transmitter property ‘osd.boot.timeout’ if you want to set timeout; default is 5 seconds

– Set transmitter property ‘osd.boot.prompt’ if you want to set boot prompt; default is “Booting from Marimbma Transmitter. Press <F8> for menu.”


Preparation

• Transmitter and endpoints must have bridged network (can talk to each other over transmitter http bind address). To force transmitter to bind itself to specific adapter set property ‘transmitter.http.bindAddress’

DHCP & TFTP on same box

NO-PXE environment


Architecture

Transmitter

Laptop

Desktop

Workstation

Legacy PC

TFTP Service

DHCP

OS Image

Boot Image

Profile


Preparation

• Transmitter settings

– Set transmitter property ‘osd.services.enabled=true’ to activate pxe and tftp services in transmitter

– Set transmitter property ‘osd.pxe.disable=true’ to disable pxe service, Only tftp will start on tx

– Set transmitter property ‘osd.mtftp.group’. This should be the multicast group that the server would use to monitor UDP requests during DHCP/PXE phase

– Set transmitter property ‘osd.macdefinition.path’ and point to the path of file that contains mac mapping (whether mac is activated for OS migration and what boot file it should pick). E.g.

<?xml version="1.0" encoding="UTF-8" ?>

<hosts>

<host mac="abcd" activation="true" bootindex="0"><host/>

<host mac="efgh" activation="true" bootindex="1"><host/>

<host mac="general" activation="true" bootindex="0"><host/>

</hosts>

– Set transmitter property ‘osd.macdefinition.sync.interval’ to set sync interval of activation file

– Set transmitter property ‘osd.all.activated’ if you want to activate all machines by default

– Set transmitter property ‘osd.boot.timeout’ if you want to set timeout; default is 5 seconds

– Set transmitter property ‘osd.boot.prompt’ if you want to set boot prompt; default is “Booting from Marimbma Transmitter. Press <F8> for menu.”


Preparation

• Transmitter and endpoints must have bridged network (can talk to each other over transmitter http bind address). To force transmitter to bind itself to specific adapter set property ‘transmitter.http.bindAddress’

• DHCP Configuration required

– Set option 66 to point to same machine server name / IP address (localhost/hostname/ipaddress)

– Set option 67 to point to boot file (pxelinux.0)

• Make sure you disable pxe by setting transmitter property ‘osd.pxe.disable’

Workflow


• No change required in DHCP server

• Transmitter running pxe/tftp (port should be opened and there shouldn’t be other pxe in multicast group)

• Transmitter must have all channels and settings (explained earlier)

• Endpoint must be configured to boot from network (PXE boot)

• Endpoint completes DHCP request-offer cycle with regulalr DHCP

• Endpoint connects to transmitter for PXE cycle and gets boot image (loader) info

• Endpoint boots into winPE (winPE), loads config.txt to locate info channel url

• Endpoint downloads info channel to get details about profile (for mac)

• Endpoint downloads the profile channel to get all details like OS image url, Credentials etc

• Endpoint prepares the machine (partitioning etc), downloads the image, apply that, change boot sequence and gets into OS installation

Workflow

In progress items


• Boot image management – UI workflow needs some work

• Automating preparatory channels (like info)

• Automating activation/deactivation of machines*

In progress items

Open defects


Open issues

1. Multiple Stop/start OSD service by setting property ‘osd.services.enabled’ to true/false triggers exception…

java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@10843c08 rejected from java.util.concurrent.ThreadPoolExecutor@6079b99f[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 1]

at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.reject(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor.execute(Unknown Source)

at java.util.concurrent.AbstractExecutorService.submit(Unknown Source)

at com.bmc.net.common.DatagramServer.start(DatagramServer.java:58)

at com.marimba.apps.transmitter.osd.PXEServer.start(Unknown Source)

at com.marimba.apps.transmitter.osd.OSDModule.startService(Unknown Source)

at com.marimba.apps.transmitter.Server.notify(Unknown Source)

at com.marimba.tools.util.NotificationProducer.sendNotifyNow(NotificationProducer.java:213)

at com.marimba.tools.util.NotificationProducer.sendNotify(NotificationProducer.java:168)

at com.marimba.tools.util.NotificationProducer.sendNotify(NotificationProducer.java:156)


Open issues

2. Debug messages without debug flags…

3. VBScript change to handle boot sequence – bug there but there is a workaround so this will be low defect

Demo


Demo

Q&A

Thank You…


www.CM-UG.com

CM-UG - User Interaction

Join the LinkedIn Group = http://www.linkedin.com/groups?gid=1774296





www.CM-UG.com

Marimba Consulting

Find the best consultants for your next Marimba project.


http://www.tk-cs.com/



Technology

March 2014 CMUG Minutes