If the images have been built on a dedicated Image Building Server, use the
scp
com-
mand or the remote copy option of your file browser:
1
Use the following command to copy the system images to the
/srv/SLEPOS/
image
directory (type the command all on one line):
scp
/var/lib/SLEPOS/system/images/
image_name
/
image_name
.
architecture-version
adminserver_address
:/srv/SLEPOS/image/
image_name
.
architecture-version
2
Use the following command to copy the corresponding MD5 checksum files to
the
/srv/SLEPOS/image
directory (type the command all on one line):
scp
/var/lib/SLEPOS/system/images/
image_name
/
image_name
.
architecture-version
.md5
adminserver_address
:/srv/SLEPOS/image/
image_name
.
architecture-version
.md5
4.6.1 Deploying New Versions of System
Images
If you build new system images, you can preserve old file names and overwrite existing
images. In such a case, there is no need to update objects in LDAP database.
Alternatively, you can copy the new image to a file with new version number. You
must add the new version (
scPosImageVersion
) to the related
scPosImage
object (see Section 7.4.7, “Activating Images” (page 86)).
You can also use a new name and version number. In such a case, you must create a
new
scPosImage
(see Section 7.4.6, “Adding an
scPosImage
Object” (page 84)).
If the new image uses a different kernel version, the new
scPosImage
must be added
to the corresponding
scDistributionContainer
.
44
SUSE Linux Enterprise Point of Service Guide
