6.5 Managing Image Objects

Images are managed in LDAP with scPosImage objects. The scPosImage object stores information about an image stored on the Administration Server. For more information on images, see Section 8.0, Building Images with the scr ImageBuilder Tool.

The following sections outline how to use posAdmin to manage images in LDAP:

NOTE:Each LDAP object has two types of attributes: must and may attributes. The must attributes are the minimum requirements for an object. The may attributes are optional.

6.5.1 Adding an scPosImage Object

Every client image that you want to distribute to Point of Service terminals must have a corresponding scPosImage object in the LDAP directory. These objects are typically organized within Distribution Container objects under the Global container in the LDAP tree.

NOTE:Boot images do no have scPosImage objects; they are referenced in the scInitrdName attribute in the scDistributionContainer object.

After the installation and configuration of the Novell Linux Point of Service, an scPosImage object is automatically added to the Default Distribution Container for the Minimal image. However, this LDAP entry is only intended to serve as an example. You must manually add an scPosImage object for each client image you want to distribute to Point of Service terminals.

IMPORTANT:The images that ship with Novell Linux Point of Service 9 are built on Novell Linux Desktop (NLD) which runs the Linux 2.6 kernel. Therefore, the reference objects for Novell Linux Point of Service 9 images must be created in the Default Distribution Container.

If you migrate from SLRS 8 to Novell Linux Point of Service 9, the migration script creates the SLRS 8 distribution container. This container references the SLRS 8 kernel and therefore, must store all the scPosImage objects for SLRS 8 images. For more information, see Migrating from SLRS 8 to Novell Linux Point of Service 9 in the Novell Linux Point of Service 9 Installation Guide.

Table 6-13 summarizes the posAdmin command options for scPosImage object attributes.

Table 6-13 Command options for scPosImage objects

Option

Type

Description

--base

must

The base distinguished name of the scPosImage object; for example, cn=global,o=mycorp,c=us.

--cn

must

The common name of the client image; for example, myjava.

--scImageName

must

The name of the client image; for example, myjava.

--scPosImageVersion

must

The version number of the client image, followed by the flag passive or active; for example, 2.0.21; active. The version number and the flag are semicolon-separated (’;’). There are several combinations possible of this attribute, which are described in Table 6-14.

--scDhcpOptionsRemote

must

The boot option of the Point of Service terminal.The mandatory value is /boot/pxelinux.0.

--scDhcpOptionsLocal

reserved

This attribute is reserved for future extension of the Novell Linux Point of Service and is not used at this time.

--scImageFile

must

The filename of the image, which the terminal will download from the Branch Server; for example, myjava.

--scBsize

must

Specifies the block size for the TFTP download of the client image. For example, 8192. possible values are: 4096 (4 KB) for image sizes less than 128 MB, 8192 (8 KB) for image sizes less than 256MB, 16384 (16 KB) for image sizes less than 512 MB and 32768 (32 KB) for image sizes less than 1GB. You must select a TFTP block size of 32 KB for the full-featured Desktop image, because there is a limitation of the block counter for TFTP.

--scConfigFile

may

Specifies the path where the configuration file is installed on the Point of Service terminal; for example, /etc/ntp.conf or /etc/X11/XF86Config.

The following example adds a scPosImage object below the Global container (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us  --password secret 
--base cn=global,o=mycorp,c=us --add --scPosImage --cn myJava 
--scImageName myJava --scPosImageVersion "2.0.21;active" 
--scDhcpOptionsRemote /boot/pxelinux.0 --scDhcpOptionsLocal LOCALBOOT --scImageFile myJava --scConfigFile /etc/X11/XF86Config

6.5.2 Activating Images

Each image can be available in several versions, as shown in Table 6-14. The scPosImageVersion attribute in each scPosImage object must be set to either active or passive. Active versions are downloaded by the Branch Server. If there are multiple active versions of a single image, the Branch Server selects the highest active version. Passive image versions are never downloaded to the Branch Server unless they are explicitly configured in the scWorkstation entry for the individual Point of Service terminal.

Table 6-14 Possible values for the scPosImageVersion attribute

Value

Description

1.1.2

The version number is set to 1.1.2, but this client image is disabled in LDAP and cannot be used for a new Point of Service terminal, even when the scCashRegister object that corresponds to the Point of Service terminal matches the scPosImageDn attribute entry.

1.1.2;passive

Same behavior as above.

1.1.2;active

This client image with version 1.1.2 is enabled and downloaded to the Point of Service terminals.

1.1.2;active 1.1.3;active 1.1.5;active

All image versions are enabled, but only the latest image version is downloaded to the Point of Service terminals.

1.1.2;passive 1.1.3;active 1.1.5;passive

Only image version 1.1.3 is enabled and downloaded to the Point of Service terminals.

To activate a registered image, set its scPosImageVersion attribute to active. This is done with posAdmin using the --modify keyword and the --multival (multivalue) option as follows (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret 
--modify --scPosImage --multival 
--scPosImageVersion '2.3.10;passive=>2.3.10;active'  
--DN cn=browser,cn=default,cn=global,o=mycorp,c=us

To activate the new image version on a Branch Server, use possyncimages.pl and posldap2crconfig.pl with the --dumpall option.

possyncimages
posldap2crconfig --dumpall

6.5.3 Assigning an Image to a Point of Service Terminal

You can assign a specific image to a Point of Service terminal through its scWorkstation object.

The following command assigns Browser image 2.3.10 to the CR001 scWorkstation object in the boston1 container (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret
--modify --scWorkstation 
--scPosImageDn cn=browser,cn=default,cn=global,o=mycorp,c=us 
--scPosImageVersion 2.3.10 
--DN cn=CR001,cn=boston1,ou=boston,o=mycorp,c=us

When you explicitly assign an image in the scWorkstation entry, the active or passive flag set for the scPosImage object in the global container is ignored.

NOTE:The scWorkstation object is automatically created in the LDAP directory the first time you boot a Point of Service terminal. The posleases2ldap daemon automatically triggers posldap2crconfig.pl which then creates an scWorkstation object and hardware configuration files for each Point of Service terminal that registers on the Branch Server. For more information on this process, see Section 3.0, Point of Service Terminals.

6.5.4 Removing Images

To remove the image assigned to a workstation, run the following command (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret 
--remove --scWorkstation --scPosImageDn  --scPosImageVersion  
--DN  cn=CR001,ou=boston1,ou=boston,o=mycorp,c=us