Browse Prior Art Database

Pristine Scenario support using adaptive management Disclosure Number: IPCOM000030209D
Original Publication Date: 2004-Aug-02
Included in the Prior Art Database: 2004-Aug-02
Document File: 3 page(s) / 70K

Publishing Venue



One of the most important scenarios that the adaptive management infrastructure (a.k.a On-Demand Management Infrastructure) is required to support is the "Big Bang" one. The question that needs to be answered is: how the adaptive subject will be initially put on a system so that it can be managed by the adaptive methodology? Skipping the trivial scenario of installing the subject manually on the system, this memo will try to shed some light on how the other two facets of the "Big Bang" scenario can be implemented.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 42% of the total text.

Page 1 of 3

Pristine Scenario support using adaptive management

In the Pristine support case, the scenario starts with a system that has not been installed at all or has to be reinstalled before it is booted (scratching). In either case, the system will have to boot from the network to (re)initiate the installation of a new image of the OS. To do so, it is envisioned that a PXE (Preboot eXecution Environment) - WfM (Wired for Management) standard scenario will be used to initiate the boot of a network downloaded program that will (re)install an OS Image on the system. In Adaptive Management Architecture terms, the set of PXE and non-PXE Servers cooperating to install a new OS image are called a PXE Helper. The reason is that a booting system is not a fully functional machine and requires an Adaptive Helper to be managed during this phase. On the booting system will run a simple program in charge of (re)installing (potentially also reconfiguring only) the system. Such a program should be considered as a simplified Subject that requires a Helper to function. This explains the fact that many different Subjects may be active on a system at different times. In particular, during a boot, a special simplified Subject runs to take care to cover the management duties of this timeframe.

PXE is used to load an initial OS Image Loader program into the booting system to let it become enough functional to carry on the rest of the steps to install a new OS Image (or reconfigure the system or one of its images). This OS Image Loader program is foreseen to contact the OS Images Server to receive the right OS Image for that system. The OS Images Server leverages the Shared Repository to understand which configurations and tailoring is required to the OS Image to be sent to the booting system. A specific set of rules are going to be written to handle these configuration steps and the OS Images Server will use them to prepare the OS Image to be provided to the booting system. The following picture shows the interactions between a booting Pristine system, the PXE Helper and the Shared Repository.


The OS Image Loader - PXE Subject, running on the Pristine system is in charge of providing basic information to recognize the booting system (e.g. MAC address of

  Shared Repository


(Boot Image Negotiation Layer)




BINL request\reply (File name)

TFTP file r equest

     TFTP data packets (OS Image Loader - PXE Subject)

System charact. (MAC , etc.) files / data request

data packets - cm ds (OS Image w/


DHCP request\reply

l (IP) DHCP request\reply

(Boot Server IP)




OS Images Server

Pristine System


[This page contains 1 picture or other non-text object]

Page 2 of 3

the booting network card, machine type, etc.) and to carry on the steps to install the OS Image provided by the OS Images Server or to reconfigure the machine if so instructed. It is a typical "old style" agent that responds to server commands.

The OS Imag...