Difference between revisions of "Provisioning Terminology"

Revision as of 15:36, 10 April 2007

One goal of the Ganymede Provisioning Workshop is a consistent and useful lexicon of provisioning terminology. We provide this page as a working space for this effort. Thought the workshop we will allow multiple and even contradictory definitions with the hope that prefered usage for most words can be identified before the event is over.

(We have created many sections to simplify ordering and reduce editing conflicts. See example definition.)

A

Agent

The provisioning infrastructure on client machines is generally referred to as the agent. Agents can manage themselves as well as other profiles. An agent may run separate from any other Eclipse system being managed or may be embedded inside of another Eclipse system. Agents can manage many profiles (see below) and indeed, a given system may have many agents running on it.

B

Bill of Materials

A concrete list of artifacts to be installed. Analagous to an OSGi configuration.

C

D

Definition

To make clear one or more meanings of a word. This entry is itself a definition and has been provided as an example of reasonable wiki formatting.

E

Engine

The engine is responsible for determining how to achieve the desired provisioning operations as determined by a director. Whereas the subject of the director's work is metadata, the subject of the engine's work is the artifacts and configuration information contained in the IUs selected by the director. Engines cooperate with repositories and transport mechanisms to ensure that the required artifacts are available in the desired locations.

F

G

H

I

J

K

L

M

N

O

Order

Abstract list of things to be installed (aka wish list)

P

Q

R

S

T

U

V

W

X

Y

Z