Oracle® Enterprise Manager Ops Center Feature Reference Guide 12c Release 1 (12.1.1.0.0) Part Number E27511-04 |
|
|
PDF · Mobi · ePub |
The following information is included:
Oracle Enterprise Manager Ops Center uses libraries to store and manage cached data, images, packages, and metadata. A library that stores images for provisioning operations is called a Software Library, or in the case of Oracle Solaris 11, the Oracle Solaris 11 Software Update Library. At least one software library always exists on the Enterprise Controller.
A Software Library accepts the following types of images:
OS images that install an operating system
Branded images that install a specialized version of an operating system
Firmware images and the supporting metadata to update existing firmware on service processors, RAID controllers, and disks
Another type of library is a storage library. See Chapter 6, "Storage Libraries" for information about this type of library.
The following table lists the tasks and the role required to complete the task. Contact your administrator if you do not have the necessary role or privilege to complete a task. See the Oracle Enterprise Manager Ops Center Administration Guide for information about the different roles and the permissions they grant.
Table 5-1 Software Libraries Roles and Permissions
Task | Role |
---|---|
Set Enterprise Controller Storage Library |
Oracle Enterprise Manager Ops Center Admin |
Create Library |
Storage Admin |
Delete Library |
Storage Admin |
Associate Library |
Storage Admin |
Import image |
Storage Admin |
Upload image |
Storage Admin |
View details of an image |
Storage Admin |
Moving an image |
Storage Admin |
Edit Attributes |
Storage Admin |
Associate Library to Server Pool |
Cloud Admin |
You can perform the following actions, depending on the requirements:
Designate a default software library
View details of an image
Create Library
Delete Library
Associate Library
Import Image
Upload Image
Moving an image
Edit Attributes
Create Update Library
By default, Oracle Enterprise Manager Ops Center is configured in Connected mode. In this mode, the Enterprise Controller uses the Internet to download images and metadata from the Oracle Knowledge Base, and the Oracle Solaris 11 Package Repository. The Oracle Knowledge Base (KB) contains metadata for Oracle Solaris 10, 9, and 8 as well as Oracle Linux OS components. The Oracle Solaris 11 Package Repository includes packages of images. In both cases, the metadata is information about patch dependencies, standard patch compatibilities, withdrawn updates, downloads, and deployment rules. In addition, the KB includes URLs for each supported operating system and downloads the components from the appropriate vendor download site.
If it is necessary to use the Oracle Enterprise Manager Ops Center software in Disconnected mode, that is, without Internet access, your site can create a local version of the Knowledge Base or Repository on your site's network. In this case, the Enterprise Controller connects to the local network location to get the latest information.
The Enterprise Controller must have at least one Software Library to store the new versions of images that are downloaded from the Oracle Knowledge Base automatically. This default EC Library is updated at the following maximum intervals between updates:
New Oracle Solaris updates – 1 day (including security updates, Oracle Solaris Cluster updates, and standard updates)
Oracle Solaris updates — 3 weeks
Oracle Solaris EIS Baseline — 7 days
Oracle Solaris Freeware Package — 3 days
Linux Software Update (RPM) — 1 day
Linux Service Pack — 3 weeks
Linux Distribution New Version — 30 days
In addition to the routine download operations, you can create jobs to update assets. When you submit an update job for specific target assets, the Agent Controllers on the targets send a request to the KB through the Enterprise Controller to download the latest information.
The Initial EC Library is created when the product software is installed. At any time, you can specify a different software library to accept the automatic download operations from the Knowledge Base. The current active library is identified by its badge, a white down arrow on a green background, as shown in Figure 5-1.
Figure 5-1 Badge Identifying the Current Default Library
To Change EC Software Libraries
To specify a different software library as the default software library:
Expand Administration in the Navigation pane.
Click Set Enterprise Controller Storage Library in the Action pane. The window lists all libraries with the current library highlighted.
Click the library you want to store the images from the automatic download operations.
Click Apply.
When the job is completed, the Library section of the Navigation pane shows the software library you selected as the default library.
Beginning with Oracle Solaris 11, updates are delivered in packages. With Oracle Enterprise Manager Ops Center, you do not need to create an Image Packaging System (IPS) repository.
The Oracle Solaris 11 Package Repository resides at the Oracle site: http://pkg.oracle.com/solaris/release/
. This repository has the role of Publisher and Parent. The Oracle Solaris 11 Package repository is similar to the Knowledge Base but is only for Oracle Solaris 11 images and updates. As with the Knowledge Base, you can create a local repository.
A component of an Oracle Solaris 11 update package is the IPS Package Manifest. The manifest is the metadata for the package (such as name, description, version, and category), what files and directories are included, and the package dependencies. Packages might specify what services to restart in order to refresh some configuration on the system, specify what aliases to update for a given hardware driver, or what users and groups to create as part of the package installation process.
In addition to the default EC Library, you can create more Software Libraries and organize their content, according to your site's purposes. You can use a file system on the Enterprise Controller's system or a shared file system on an NFS server that the Enterprise Controller mounts. The file system on the Enterprise Controller is called a local software library. The file system on the NFS server is called a NAS software library. See Types of Storage for Libraries.
When Oracle Enterprise Manager Ops Center provisions target systems with an operating system or firmware, it copies the images files from the designated Software Library to each Proxy Controller. The Proxy Controllers handle the provisioning operations. When Oracle Enterprise Manager Ops Center provisions target systems with an update to an operating system, it uses the software library named Linux and Oracle Solaris 8-10 Software Update Library or the Oracle Solaris 11 Software Update Library.
You can display the contents of the software library, its associations, and details about the disks in the software library. You can also see how the library is being monitored and any problems.
To View the Contents of a NAS Software Library
Expand Libraries in the Navigation pane.
Click NAS Storage in Software Libraries.
Click a software library.
The details of the selected NAS library are displayed in the center pane in a set of tabs. The Summary tab displays information about the entire software library:
URL — NFS
Size — Total storage capacity of the library
Used Space — Space assigned to guests and zones
State — State of the library
Access — Read-Write
The Library Contents table lists all the images in the library, organized by type, and includes the size and date the image was modified.
The Disks tab lists all disks in the library by name and description and shows the current use of each one by allocation and size.
To see the results of monitoring the software library, click the Incidents tab.
To see the attributes and values that are being monitored, click the Monitoring tab.
You can create a software library that uses space on a file system on the Enterprise Controller's system. This is called an Local Library. You can also create a software library that uses space on a shared file system on an NFS server. This is called a NAS Library.
Note:
When you use both local and NAS software libraries, do not use the same name for the library.To Create a Local Software Library
Expand Libraries in the Navigation pane. The current active library is identified by its badge.
Click New EC Local Library in the Action pane.
Enter a unique name and description.
In the URL field, enter the location of the file system.
Click Create.
To Create a NAS Software Library
Expand Libraries in the Navigation pane. The current active library is identified by its badge.
Click New EC NAS Library in the Action pane.
Enter a unique name and a description.
Choose the type of service:
To use a unified storage appliance, select an appliance and specify the exported share to use.
To use an NFS server, enter the hostname and path for the NAS appliance.
Click Create.
In Connected mode, the Linux and Oracle Solaris 8-10 Software Update Library is updated on the schedule described in EC Library.
The Oracle Solaris 11 Image Packaging System (IPS) contains the packages that you need to install, provision, and update your Oracle Solaris 11 operating system. Each IPS package has an associated manifest that describes how the package is put together. The package manifest provides basic metadata about the package (such as name, description, version, and category), what files and directories are included, and the package dependencies. Packages might specify what services to restart in order to refresh some configuration on the system, specify what aliases to update for a given hardware driver, or what users and groups to create as part of the package installation process. All software packages are hosted by a package repository and systems must connect to the repository to install software updates.
Oracle Enterprise Manager Ops Center incorporates and simplifies the IPS. The software provides a local IPS repository on the Enterprise Controller, called the Oracle Solaris 11 Software Update Library, and provides package lifecycle management. The Oracle Solaris 11 Software Update Library enables you to interact with the IPS. You can assign storage to the Oracle Solaris 11 Software Update Library, and then populate it with a local copy of the IPS.
Note:
The host system for the Enterprise Controller must have the Oracle Solaris 11 operating system. It is not possible to initialize an Oracle Solaris 11 Software Update Library on a different Oracle Solaris operating system.You can configure the Oracle Solaris 11 Software Update Library when you install and configure Oracle Enterprise Manager Ops Center, or you can configure the Oracle Solaris 11 Software Update Library after installation using the Create Update Library action.
The Oracle Solaris 11 Software Update Library has the following states:
Unconfigured – Oracle Solaris 11 Software Update Library was not configured when you installed and configured Oracle Enterprise Manager Ops Center.
Configuring – The Oracle Solaris 11 Software Update Library is in the process of being configured.
Syncing – The Oracle Solaris 11 Software Update Library is in the process of updating and synchronizing with the IPS or is in the process of being reconfigured. The Oracle Solaris 11 Software Update Library is locked and unavailable for use when in this state.
Ready – The Oracle Solaris 11 Software Update Library is ready to use.
If the Oracle Solaris 11 Software Update Library is in an unconfigured state, use the Initialize Oracle Solaris 11 Software Update Library action to define the port that the repository uses, assign at least 10 gigabytes (GB) of storage, and create a Local EC Library to populate the library with a local copy of the IPS. When complete, the new library appears in the Libraries section and contains three sections: Summary, Boot Image, and Packages.
Note:
The process of initializing the library takes several hours.To obtain updated packages for the Oracle Solaris 11 Software Update Library, synchronize with the remote parent IPS repository. The Oracle Solaris 11 Software Update Library is locked during the process and you cannot perform OS provisioning or OS update tasks.
Parent repositories are the URLs of Oracle Solaris 11 content that you use to update, or sync, your local Oracle Solaris 11 Software Update Library. Other parent repositories, such as Oracle Solaris Cluster, are available. You can configure more than one parent repository and provide their credentials. For a list of all available Oracle repositories, go to pkg-register.oracle.com
A child repository is a subset, such as the release and branch for an Oracle Solaris 11 update release.
The Oracle Solaris 11 Software Update Library Summary is available after the library is configured. The summary provides an overview of the health, status, and last update. The URL listed on the Summary is the location of the Oracle Solaris 11 Software Update Library. The size is the amount of space allocated to the file system, and the used space shows how much space is used by the packages that are located in the library.
The Publisher table shows the Parents and the associated credentials. Parents are the URLs for Oracle Solaris 11 packages and content located in the Image Packaging System (IPS). These URLs are used to synchronize the information in your Oracle Solaris 11 Software Update Library with the Image Packaging System. The Parent list is created when you use the Create Parent Repositories wizard. If your site has its own local repository for Oracle Solaris 11 packages, you can update Oracle Enterprise Manager Ops Center's library from that location.
Figure 5-3 Oracle Solaris 11 Software Update Library Summary
The Content tab displays a list of the packages in the Oracle Solaris 11 Software Update Library with a brief description of each package. You can search for a specific package, or you can refine the search by category and version.
Figure 5-4 Oracle Solaris 11 Software Update Library Content
You can manage publishers for the parent repository and synchronize the Oracle Solaris 11 Software Update Library with the parent. You can manually synchronize the repositories at any time, or you can create a recurring synchronization schedule to automatically synchronize the Oracle Solaris 11 Software Update Library during non-peak hours. In the Configure Parent Repositories wizard, you create a list of parent repositories and associated credentials that you use to update the Oracle Solaris 11 Software Update Library. You can update the Oracle Solaris 11 Software Update Library manually, or schedule updates during off peak hours.
You can define a parent repository and add content to the Oracle Solaris 11 Software Update Library manually by using the Add Content action. The parent repository URL and credentials are not saved when you use this action. To save a list of repositories, use the Configure Parent Repository action.
Update Profiles and any profiles you create that provision an OS or firmware image rely on the contents of a software library. For Oracle Solaris 10, 9, and 8 and for Oracle Linux, a dedicated software library called Linux, Solaris 8-10 Software Update Library contains the packages, updates, and site-specific scripts and configuration files for these operating systems. For each OS, this software library organizes its contents in the following categories:
Clusters (groups of Oracle Solaris packages)
Configuration files
Hardware
Local
Local Packages
Local RPMs
Notifications
Packages
Patches
Post-actions
Pre-actions
Probes
Recommended Software Configurations
Oracle Solaris Baselines
You can change the display of the contents of the library according to the OS distribution, the category, the type of view, and the version.
See Images for information about managing the content in the library.
See Local Content for information about managing the content of the local categories.
In most cases, all the images you need are downloaded from the Oracle Knowledge Base. However, you can also create images within Oracle Enterprise Manager Ops Center or obtain them from a location external to Oracle Enterprise Manager Ops Center and then import or upload them into Oracle Enterprise Manager Ops Center.
Oracle Enterprise Manager Ops Center manages the following categories of images:
Firmware image - In Oracle Enterprise Manager Ops Center, a firmware image consists of the hardware's firmware, the instructions to use the firmware, its platform, and its software dependencies. These images are stored in the Software Libraries. The following firmware types are supported:
Service Processor firmware
Chassis firmware
Power distribution unit firmware
Storage Component firmware updates firmware on RAID Controllers, Expanders and Disks. The maximum size of a firmware image is 20 MB.
OS image – An OS image contains an entire operating system. A subset of OS images are branded images, which install an operating system that is optimized for a specific purpose and can also install applications. For example, a branded image for Oracle Solaris 9 can be installed in a nonglobal zone of a system running Oracle Solaris 10. The maximum size of an OS image is 2 GB. These images are stored in the Software Libraries.
ISO image – The image, also called a disk image, contains uncompressed directories and files of any type. This is the image that resides on removable media. It can be an application or data or both. While the firmware and OS images are stored in one of the dedicated update libraries, these images can be stored in other software libraries. When you create a profile for these images, you specify the software library where it is located. The maximum size of an ISO image that you can transfer using browser operations is 2 GB. If the image is larger than 2 GB, move the file manually to the Enterprise Controller's system and then import it.
Note:
Another type of image is guest metadata. These images are stored in the Storage Libraries and have a different purpose. This image contains the configuration information for a virtualization host's guest, its operating system, and the applications used by a virtualization host's guest, either a logical domain or a nonglobal zones, depending on the type of virtualization host.OS images provision both hardware servers and virtualization hosts with an operating system. In addition to being grouped as packages, updates, Oracle Solaris OS images are also grouped into baselines. You import OS images from existing ISO files. OS images for virtualization hosts are provided as ISO files that you import in the same manner as Oracle Solaris or Linux OS images.
An OS image must be in an image file that has the ISO format. If the image is not in an ISO file, create the file. For example, on an Oracle Solaris system, the following command collects all OS component files on the auto-mounted file system into an ISO file.
# mkisofs -o <name_of_OS.iso> -J -R /cdrom/<name_of_OS>
The Oracle Enterprise Manager Ops Center software loads one ISO file per operation. If an ISO file spans more than one CD, combine the content on one DVD.
An ISO file cannot be made from Oracle Solaris installation CDs.
Table 5-3 Types of Images for Each Operating System
Operating System | Location of Images |
---|---|
Oracle Solaris 11 |
Oracle Solaris 11 Software Update Library |
Oracle Solaris 10, 9, 8 |
Linux and Oracle Solaris 8-10 Software Update Library |
Oracle Linux |
Linux and Oracle Solaris 8-10 Software Update Library |
JumpStart Enterprise Toolkit |
JumpStart Enterprise Toolkit (JET) is available for Oracle Solaris 8, 9, and 10. |
Firmware images provision hardware assets and are grouped as packages or updates. They are created by their manufacturers and must be downloaded from vendor web sites or uploaded from their media. A firmware image is a copy of the vendor's firmware file and metadata for the firmware, such as the platform it is used on and any software dependencies.
When you import a firmware image, you might be required to provide metadata to complete the image file. You can usually find the information in the image's README file. You must provide the firmware type, the systems that the firmware supports, the version of the firmware, and any other firmware images that this firmware image depends on.
Example 5-1 Example of Firmware Metadata
The following is an example of a README file for ALOM-CMT firmware, where a single binary is deployed to the Service Processor.
To determine the type and version of the firmware update:
Latest Sun System Firmware(6.1.2): ---------------------------------- System Firmware 6.1.2 Sun Fire[TM] T2000 2006/01/20 18:19 ALOM-CMT v1.1.2 Jan 20 2006 18:06:10 VBSC 1.1.1 Jan 20 2006 17:56:19 Reset V1.0.0 Hypervisor 1.1.0 2005/12/15 11:10 OBP 4.20.0 2005/12/15 16:48 Sun Fire[TM] T2000 POST 4.20.0 2005/12/15 17:19
To determine the models supported:
This README is intended for users who wish to upgrade the firmware in their Sun Fire T2000.
To determine if the system needs to be powered off before updating the firmware:
a)To update the Sun System Firmware, the system must be powered off (i.e. in standby mode).
From this README file, you can identify the following metadata:
Available platforms - Sun Fire T2000
Type - VBSC
Version - 1.1.1
Require power off - Yes
For this example, the VBSC firmware subcomponent/type with version 1.1.1 was used. You can use any of the other types such as ALOM-CMT:1.1.2 or OBP:4.20.0. However, you must ensure that the version specified is always the firmware subcomponent/type.
To provision firmware or an OS, you use a deployment plan to direct Oracle Enterprise Manager Ops Center to retrieve the images from the appropriate software library and install them on the targeted assets. Each time you import an image, a profile is also created with the same name. This default profile can be used in deployment plans but, as a good practice, rename a copy of this profile for use in deployment plans and leave the original profile with its original name in the library.
To use an image in a deployment plan, the image must be in one of the Oracle Enterprise Manager Ops Center's software libraries. You upload an image or import an image, depending on where the image resides. In both cases, you are moving the image from a location external to Oracle Enterprise Manager Ops Center's management into one of its libraries.
If the image resides on the Enterprise Controller's system, import the image.
If the image does not reside on the Enterprise Controller's system, upload the image.
See the procedures in Keeping Your Firmware Up-to-Date in the How To library
The firmware for a PDU consists of two files, one for the firmware and one for the management software of the PDU. Each firmware image must be imported or uploaded and then a profile created that includes both images. The firmware images must have metadata, which is not always included in the image. In that case, you specify the metadata during the import or upload operation.
Uploading Firmware With Metadata
Use the procedures in Keeping Your Firmware Up-to-Date in the How To library
to upload firmware. At the step for Select Firmware Components, select both firmware components:
MKAPP_Vfirmware_version
.DL
HTML_Vfirmware_version
.DL
Uploading Firmware Without Metadata
Use the procedures in Keeping Your Firmware Up-to-Date in the How To library
to upload firmware. At the step for Select Firmware Components, select one firmware component, MKAPP_Vfirmware_version
.DL and click Upload. To define the metadata for the firmware:
For the target type click PDU.
For the platform, click Sun Rack II PDU.
Type the version of the firmware.
Choose Depends On None and accept the remaining default options.
After the job is completed, repeat the procedure with the other firmware image, HTML_Vfirmware_version
.DL with one difference: At Step4
, specify that this firmware image depends on the MKAPP_Vfirmware_version
.DL image.
Creating a Firmware Profile for PDU Firmware Updates
Click Create Firmware Profile in the Actions pane.
Type a name and description for the profile.
For subtype, click Power Distribution Units.
For target type, click Power Distribution Units. Click Next.
For Firmware Configuration, accept the default options and values. Click Next.
Select both images: MKAPP_Vfirmware_version
.DL an dHTML_Vfirmware_version
.DL. Click Next.
Review the summary of the new profile and click Finish to submit the job.
The Linux and Oracle Solaris 8-10 Software Update Library software library also stores and gives access to site-specific configuration files, and scripts used in deployment plans. Other local content your site requires can be data files, executable files, or binary files. For example, you might develop a script to test servers before running a provisioning job.
The Local categories of the Updates Library have no connection to the Knowledge Base. You upload files to the software update library, directed into one of the categories, and then maintain them throughout their life cycle. You can create subcategories of any category to organize the files.
You can view details about a component such as distribution, version, release, group, size URL, when the file was added or edited, any summary and description information, host, RPM, and vendor.
An action is a script, binary file, or executable file that makes changes to the managed host. After you upload the script or file to the appropriate category, you create a profile for the type of script or files and then include the profile in the deployment plan that installs or upgrades the OS or firmware. The following actions are available:
Pre-Actions – Script that runs on a managed host before the provisioning step starts. When you create the deployment plan, you select the Execute Pre-Install step and then select the profile that includes the script.
Post-Actions – Script that runs on a managed host after a job is completed. When you create the deployment plan, you select the Execute Post-Install step and then select the profile that includes the script.
Probes – Script that runs on a managed host to verify that a job can be performed.
Macros – Script that modifies a generic configuration file to make it appropriate for a managed host. The script outputs a single line that replaces a macro sign in a configuration file. Use macros to apply a single configuration file across multiple hosts by customizing the configuration file for each host's environment.
Expand Libraries in the Navigation pane.
Click Linux and Oracle Solaris 8-10 Software Update Library.
Click Upload Local Action in the Actions pane.
The Upload Local Action window is displayed.
Enter a name for the action.
Enter text to describe the purpose of the script or executable file.
Select the type of action such as Pre-Action, Post-action, Macros, or Probes.
Click the name of the distribution that is appropriate for the script or executable file.
The Parent Category field shows the category you specified as the type of Action. If your site uses subcategories, click the Browse button to navigate to the specific subcategory.
Click Browse to locate and select the script or executable file.
Click Upload. The file is uploaded to the Linux, Solaris 8-10 Software Update Library in the category you specified.
You can now create a profile for the script and then use the profile in a deployment plan.
You can upload software in the following formats:
pkg
rpm
tar
zip
gzip
compress
If the file is in compressed format, the file is uncompressed after it is uploaded.
To Upload a Local Software Package
Expand Libraries in the Navigation pane.
Click the operating system's Software Update Library.
Click Upload Local Software Packages in the Actions pane.
Select Yes if the package is a security fix for a previous version of the software. Otherwise, select No.
Click the name of the distribution to which you want to add this package.
In the Parent Category section, click Local PKGs or click Browse to locate a subcategory.
In the Files section, click Add to see the list of files. Select at least one software package.
Click Upload. The file is uploaded to the Linux, Solaris 8-10 Software Update Library in the category you specified.
You can now include the package or RPM in an provisioning profile.
A configuration file is a text file, binary file, or non-RPM application that contains the settings and values for an asset type. A profile or deployment plan then uses the configuration file on all of the assets defined for it.
To Upload a Local Configuration File
Expand Libraries in the Navigation pane.
Click Linux and Oracle Solaris 8-10 Software Update Library.
Click Upload Local Configuration File in the Actions pane.
The Upload Local Configuration File window is displayed.
Figure 5-6 Upload Local Configuration File
In Target path on server, type the full path to the configuration file.
In Version, type a character string to identify this version of the file. The string is appended to the file name when it is displayed in a Components list.
Type a brief description of the file.
Select the Distribution to which this file is applied. You can choose multiple distributions.
In Parent Category, accept the Configuration Files category or click Browse to locate a subcategory.
Click Browse to locate and select the configuration file.
Click Upload. The file is uploaded to the Linux, Solaris 8-10 Software Update Library in the category you specified.
Your site's local content is organized into the following default categories: local RPMs or PKGs, configuration files, macros, pre-actions, post-actions, and probes. You can create subcategories to further organize your local content. The type of local content allowed in a subcategory depends on its parent category.
Expand Libraries in the Navigation pane.
Click Linux and Oracle Solaris 8-10 Software Update Library.
Click Add Local Category in the Actions pane.
Enter a name for the new subcategory.
Enter a brief description for the new subcategory such as its purpose.
Click Distribution to assign to the subcategory.
Click Parent Category to select one of the system-defined categories for the subcategory.
Click Apply. The new subcategory is created under the selected default category. You can now upload software packages and files into the new subcategory.
You can edit the contents of a local component file. For example, if you uploaded a system file that contained IP addresses and determined that there was an incorrect IP address in the file, you can edit the file to correct the IP address. You can also use this procedure to replace the file with a corrected file.
Expand Libraries in the Navigation pane.
Click Linux and Oracle Solaris 8-10 Software Update Library.
Click Edit Local Component File in the Actions pane.
To specify the file, type its name or click the Browse button to navigate to the file. If the file is not found, click Distribution to select the correct distribution. Only files in the selected distribution are displayed.
Select either Edit existing file or Replace existing file.
If you choose to edit the file, make changes to the file and click Save.
If you choose to replace the file, browse for the replacement file and click Upload.
You can remove your site's local content but you cannot remove the default categories.
Note:
Deleting content does not require confirmation and cannot be undone. Verify you are deleting the correct local component.To Delete a Local Component File
Expand Libraries in the Navigation pane.
Click Linux and Oracle Solaris 8-10 Software Update Library.
Click Delete Local Component in the Actions pane.
Expand the category to display the component you want to delete. To change the distribution that is displayed, click Distribution.
Select the component or a subcategory to delete.
Click Delete.
To remove a subcategory and its components, do not attempt to remove each component and then remove the subcategory. When there are no components in a subcategory, the subcategory creates a placeholder component, which you cannot delete. Repeat the procedure and select the subcategory itself to delete. The placeholder component is also removed.
You can upload multiple files or an entire directory in one operation. For example, you can upload the contents of a DVD or you can specify a directory. All components in the directory and subdirectories are uploaded.
The files must be in the following formats:
pkg
rpm
(for Linux RPMs)
tar
zip
gzip
compress
If files are compressed, the software extracts the files after it uploads them.
Verify that the files have the supported file types.
Verify that the file size does not exceed 2 GB. If the file is larger than 2 GB, copy the file manually to a file system on the Enterprise Controller's system.
If you are uploading from removable media, insert the media.
To Upload Local Software in Bulk
Expand Libraries in the Navigation pane.
Click Linux and Oracle Solaris 8-10 Software Update Library
Click Bulk Upload Packages and Patches in the Actions pane.
The Upload Packages, Patches, and RPMS window is displayed
Click Distribution to select the distribution that applies to these files.
Select either Upload from OS Image or Upload from Directory.
Specify the path to the OS image or directory or click Browse to locate and select it. If you specify a directory, all files in the directory and its subdirectories are uploaded. If you specify an OS image, you must mount the OS image and select the files.
Click one of the OS images and click Mount.
Click Browse to locate and select the files.
Click Submit. The upload job is created.
To view the status of the upload job, select Bulk Upload Results.
To view the certified packages in the software update library, click the Content tab in the center pane and select Patches in the Category list. To view non-certified packages, click Local PKGs or Local RPMs in the Category list.
You can view a detailed history of all the local components that were uploaded in bulk.
Expand Libraries in the Navigation pane.
Click Linux and Oracle Solaris 8-10 Software Update Library.
Click Bulk Upload Results in the Actions pane. The uploaded components list displays the name, description, status, and date for each component.
Select a component and click View Results. The details of the uploaded components are displayed.
The ecadm backup
command does not back up the software libraries. It is a good practice to create the software library for OS images on networked storage (NAS) and include the network storage device in your site's backup plan. As an alternative, back up the Enterprise Controller's directory manually.
To Back Up Images and Local Content
Move the archive to another server, file-share facility, or a location outside of the /var/opt/sun
directory, according to your site's disaster recovery plan.
If it is necessary to rebuild the Enterprise Controller, restore the Enterprise Controller and then restore the /var/opt/sun/xvm/images/os
hierarchy.
For instructions in performing actions or to learn more about the role of this feature, see the following resources in the How To library: http://www.oracle.com/pls/topic/lookup?ctx=oc121&id=howto
.
Configuring and Managing Software Libraries on the Enterprise Controller
Keeping Your Firmware Up-to-Date