Glossary of COR related Terms. More...

Glossary of COR related Terms.

Bundle

A bundle is a group of jobs. A bundle enables efficient communication between the COR client, COR server, and OI by limiting the number of RMD calls between them. A bundle can either be operated as a transactional or a non transactional bundle. COR service ensures that all jobs in a transactional bundle are either successful or unsuccessful (failures). A non transactional bundle does not contain such restrictions and can contain unsuccessfully executed jobs due to error conditions.

Class Tree

The classes and the containment relationship between these resources classes form a Class Tree. The above diagram is, therefore, a Class Tree representation.

Data Manager (DM)

Associated with an MO and MSO is a DM object. An MO and MSO each have an associated DM object that contains the attributes. The DM object is referred via a ClasssId and InstanceId pair. The classId acts as a key to obtain respective DM class. The instance ID, serves as an index to access the instance of the object.

Job

A job is an entity that specifies a CREATE, DELETE, SET, or GET operation on a MO. A job that specifies MO creation is called Create-Job. A job that specifies MO deletion is called Delete-Job. A job that represents a SET operation on the MO is called Set-Job and a job that represents a GET operation is called a Get-Job. A Get-Job has an MO and a list of attributes that need to be read.

Managed Object

An instantiation of these resource classes is called a Managed Object (MO) and it represents the actual Resource Instance present in the system and the attributes associated with it.

Managed Object Tree

Relationship between these resource instances is termed as MO tree (Managed Object tree). A Managed Object is always associated with a resource instance.

Managed Service Object (MSO)

The objects corresponding to Provisioning and Alarm attributes are termed as MSOs. The MSOs corresponding to an MO are identified by an MOID (MO) and a Service ID, where serviceID identifies the type of attribute. (Alarm or provisioning)

MOID

Each Resource Instance is identified with a unique path called MOID. MOID depicts the containment relationship of a resource. For example, the MOID Chassis:0/GigeBlade:1/GigeNode:2 represents the resource GigeNode:2 that is contained in the zeroth instance of Chassis and the first instance of GigeBlade.

Object Implementer

An ASP service or component that implements an object.

Provisioning and Alarm MSO

Associated with each Managed object are 'Provision-able Attributes', 'Alarm Attributes' and 'Private Attributes'. Each of these attributes is represented via an object of the corresponding kind. The object associated with Provision attributes is called PROVISION MSO, and the object associated with Alarm attributes is called ALARM MSO.

Runtime Attribute

Runtime attributes are also called transient attributes and are read-only. They are owned by the Object Implementors. To read a runtime attribute the OI needs to be contacted. The run-time objects and attributes form the descriptive part of the Information Model.}

Station List

COR provides a mechanism through which components can participate in creation/deletion/attribute change associated with a MO/MSO. For each MO/MSO, COR maintains a list of components that it needs to visit when an operation is performed. These components are termed as stations and the list of componets is termed as station List.

Transaction

COR implements Atomicity of operation via a two-phase transaction. As a part of a single transaction session, clients can supply multiple MO/MSO operations. These operations will be executed atomically and efficiently (as multiple jobs are performed via one API call to COR server).