Scenarios - 2
www.novell.com
Novell®
ZENworks® 7.2 Linux Management
March 30, 2007
N O V E L L Z E N W O R K S 7 . 2 L I N U X M A N A G E M E N T
Novell® ZENworks® Linux Management makes it easy to embrace and extend
Linux* within your existing environment. It is the only solution that uses policy-driven
automation to deploy, manage, and maintain Linux resources. These automated and
intelligent policies allow you to provide centralized control across the lifecycle of
Linux systems for desktop lockdown, imaging, remote management, inventory
management, and software management. The result is a comprehensive Linux
management solution that eliminates IT effort by dramatically reducing the required
overhead needed to manage Linux systems.
P U R P O S E O F T H E S C E N A R I O S
The purpose of these scenarios is to familiarize you with the some of new features
included in ZENworks 7.2 Linux Management (Breakout).
With the release of ZENworks 7.2 Linux Management, Novell engineering
has compiled scenarios that represent a number of the new features and functions
of the product. These scenarios are used by our test team and are now being shared
outside of the internal teams to better facilitate testing by users. This
information also helps to provide an overview of many of the features and also can
educate users on the new capabilities of the product.
.
A S S U MP T I O NS
We assume that you have followed:
• The instructions in Installing the ZENworks Primary Server
in the ZENworks
7.2 Linux Management Installation Guide.
• The instructions for Setting Up Managed Devices in the ZENworks 7.2 Linux
Management Installation Guide.
p. 2
Z E N W OR K S 7 . 2 LI N U X M A N A G E M E N T
S C E N AR I O S
Click any of the following headings to begin reviewing any of the included scenarios:
Installation and Upgrade Scenarios
1. Upgrading the ZENworks Server from a Previous ZENworks Linux Management
Release
2. Upgrading a Managed Device (Other Than SLES 10 OR SLED 10) from a
Previous ZENworks Linux Management Release
3. Upgrading a SLES 10 OR SLED 10 Managed Device
Package and Content Management Scenarios
4. Configuring the ZENworks Server to Choose the Best Package for a Managed
Device
5. Software Package Rollback
p. 3
1 : U P G R A D I N G T H E Z E N W O R K S S E R V E R F R O M A
P R E V IO U S ZE N W O R K S L I N U X M A N A G E M E N T R E L E A S E
Objective:
Verify the functionality of ZENworks Linux Management after upgrading the
ZENworks Server from a previous release.
Steps:
1. Install one of the previous releases with its latest patch:
• ZENworks 7 Linux Management with IR1
• ZENworks 7 Linux Management – Dell Edition
2. Create several of the different kinds of objects (bundles, policies, reports, and
so forth). For more information, see the ZENworks Linux Management
Administration Guide.
3. Create several versions of various types of bundles. For more information,
see Deploying a Different Version of a Bundle in the ZENworks 7.2 Linux
Management Administration Guide.
4. Make assignments between them and one or more devices. Be sure to use
several different kinds of schedules. For more information, see the ZENworks
Linux Management Administration Guide.
5. Perform an upgrade. For more information, see Upgrade in the ZENworks 7.2
Linux Management Installation Guide.
Expected Results
Objects still exist and their details can be viewed, the assignments still exist between
them, and the schedules are still configured.
New assignments can only be given schedules supported by ZENworks 7.2 Linux
Management, but existing associations with outdated schedules can still be viewed.
For more information, see Scheduling Changes for Bundles in ZENworks 7.2 Linux
Management in the ZENworks 7.2 Linux Management Installation Guide.
When creating a new RPM bundle, the list of Target Platforms in the RPM File
Upload dialog box is complete (the list is the same as from a new ZENworks 7.2
Linux Management installation).
All versions of all the bundles are deployable.
p. 4
2 : U P G RA D IN G A M A N A G E D D E V I C E ( O T H E R T H A N S L E S 1 0
O R S L E D 1 0) FR O M A P R E V I O U S Z E N W O R K S L I N U X
M A N A G E M E N T R E L E A S E
Objective:
Verify the functionality of ZENworks Linux Management on a managed device (other
than SLES 10 or SLED 10) after upgrading from a previous release.
Pre-Requisite:
To test this scenario, you must have one of the following setup:
• A server and a managed device (other than SLES 10 or SLED 10) with
ZENworks 7 Linux Management with IR1 installed.
• A server and a managed device (other than SLES 10 or SLED 10) with
ZENworks 7 Linux Management – Dell Edition installed.
Steps:
1. Upgrade the server to ZENworks 7.2 Linux Management. You can use the
same setup as the Scenario 1.
2. On the managed device, perform the following steps:
a. Lock any bundle by executing the rug bla bundle_name
command.
b. Lock any package by executing the rug la package_name
command.
3. Upgrade the managed device. For more information, see Upgrade in the
ZENworks 7.2 Linux Management Installation Guide.
.
Expected Results
The managed device is upgraded to ZENworks 7.2 Linux Management. All the
service associations are retained. All the bundle locks and package locks are
migrated to the new version and retained.
After the managed device is successfully upgraded, create a new bundle or a policy
on the server and associate it to this managed device. Verify that it will work.
p. 5
3 : U P G RA D IN G A S L E S 1 0 O R S L E D 1 0 M A N A G ED DE V I CE
Objective:
Verify the functionality of ZENworks Linux Management on a SLES 10 or SLED 10
managed device after upgrading it.
Pre-Requisite:
To test this scenario, you must have the following setup:
• A server with ZENworks 7 Linux Management with IR1 installed
• A SLES 10 or SLED 10 managed device
Steps:
1. Upgrade the server to ZENworks 7.2 Linux Management. You can use the
same setup as Scenario 1.
2. On the managed device, lock any bundle by executing the rug bla
bundle_name command.
3. Upgrade the managed device. For more information, see Upgrade in the
ZENworks 7.2 Linux Management Installation Guide.
.
Expected Results
The managed device is upgraded to ZENworks 7.2 Linux Management. All the
service associations are retained. All the bundle locks are migrated to the new
version and retained.
After the managed device is successfully upgraded, create a new bundle or a policy
on the server and associate it to this managed device. Verify that it will work.
p. 6
4 : C O N F I G U R I N G T H E Z E N W O R K S SE R V ER T O C H O O S E T H E
B E S T PA C KA G E F O R A M A N A G E D D E V I C E
Objective:
Assist SUSE® Linux Enterprise 10 users to determine the package best suited for
their device so that there is minimal risk in the incompatibilities with latest version of
the kernel, ATI and XGL enablement, etc., and several key packages.
Steps:
1. Install the ZENworks Agent and register it in the Management Zone. For
detailed information, see Setting Up Managed Devices
Management Installation Guide.
in the ZENworks 7.2 Linux
2. Register the managed device to a Red Carpet Enterprise (RCE) or a YUM
server by executing the rug sa URL_of_the_RCE_or_YUM_server
command.
3. On the managed device, install a package that you need by executing the
rug in package_name command.
Expected Results:
The ZENworks Management Daemon (zmd) installs the package best suited for the
managed device and not the package with the latest version. If you want install an
exact version of the package and don’t want the ZENworks server to choose the
best package, execute the rug in package_name- package_version
command.
p. 7
5 : S O FT W AR E P A C K A G E R O L L B A C K
Objective:
Revert to a previously installed software configuration state.
Steps:
1. Ensure that you have installed the ZENworks 7.2 Linux Management server
components and the ZENworks Agent. For detailed information, see
Installation
in the ZENworks 7.2 Linux Management Installation Guide.
2. In the ZENworks Control Center, create a catalog with few packages and
assign it to a managed device. For more information, see Using Catalogs in
the ZENworks 7.2 Linux Management Administration Guide.
3. On the managed device, perform the following steps:
a. Enable the Rollback preference by executing the following command:
rug set rollback true.
The Rollback preference is set to False by default.
b. Subscribe to the catalog created in Step 2 by executing the following
command: rug sub catalog_name.
c. List all packages contained in the catalog created in Step 2 by
executing the following command: rug pa catalog_name.
d. Make a note of the date and time when you enable the Rollback
preference by executing the date command.
e. Install a package by executing the following command: rug in
package_name.
f. Ensure that the package is installed by executing the following
command: rug pa catalog_name.
The status of the package should be “i”.
g. Roll back to the previously installed configuration state by executing
the following command: rug ro date_time.
For example: rug ro "02/20/2007 15:55:56"
The date and time you specify must be from the time you enable the
Rollback preference to the current time. If you do not specify the date,
then the current date is considered by default.
Specify the date in the mm/dd/yyyy format. For example, 02/28/2007.
For more information on the date format, see the rug man page.
p. 8
Expected Results
The package installed in Step 3e is uninstalled. To ensure that the package is
uninstalled, execute the rug pa catalog_name command and verify that the
status of the package is blank.
p. 9
L E G A L N O T I C E
Copyright © 2007 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent of the publisher. For Novell trademarks, see t he Novell
Trademark and Service Mark list (http:// www.novell.com/company/legal/trademarks/tmlist.html). All third-party trademarks are
the property of their respective owners. A trademark symbol (® , TM, etc.) denotes a Novell trademark; an asterisk (*) denotes
a third-party trademark.
THIS DOCUMENT AND MODIFIED VERSIONS OF THIS DOCUMENT ARE PROVIDED UNDER THE TERMS OF THE GNU
FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT:
THE DOCUMENT IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE DOCUMENT OR MODIFIED VERSION OF THE
DOCUMENT IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE, OR NON-INFRINGING. THE
ENTIRE RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR MODIFIED VERSION
OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR MODIFIED VERSION PROVE DEFECTIVE IN ANY
RESPECT, YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY
NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN
ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS
AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND
UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE),
CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY CONTRIBUTOR, OR ANY DISTRIBUTOR OF
THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE
LIABLE TO ANY PERSON FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF
ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE,
COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR LOSSES ARISING OUT OF OR
RELATING TO USE OF THE DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY
SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.
p. 10
Loading...