SuperCluster- Best Practices for Local Image Packaging System (IPS) Software Package Repository
(Doc ID 2037729.1)
Last updated on AUGUST 26, 2020
Applies to:Oracle SuperCluster Specific Software - Version 1.x to 2.x [Release 1.0 to 2.0]
Oracle SuperCluster M6-32 Hardware - Version All Versions and later
SPARC SuperCluster T4-4 Half Rack - Version All Versions and later
Oracle SuperCluster T5-8 Hardware - Version All Versions and later
SPARC SuperCluster T4-4 - Version All Versions and later
Oracle Solaris on SPARC (64-bit)
Background: Oracle SuperCluster install processes have had several different directory paths and naming conventions over the years . The install processes have now settled on a standardized method. This note will assist you in setting up a repository that matches this standard. This is mandatory if you do not have a local repository or if your existing one does not appear to function properly. Once completed you can delete any old shares that you were using for your repository off of the on board ZFSSA. This standardized naming is a pre-requisite for using scirt.sh to update your repository with each QFSDP(Quarterly Full Stack Download Patch).
This note will assist you in setting up a repository that matches this standard. This is mandatory if you do not have a local repository or if your existing one does not appear to function properly. Once complete you can delete any old shares that you were using for your repository off of the ZFSSA. Even if your repository is functioning and has the right content for Solaris , Custom Incorporations, and Exafamily then you should rebuild it to match with current best practices. The repository setup only needs to be done on one Solaris LDom on the SuperCluster. Once it is created you can simply set the publishers in all other Solaris LDoms to point to it. This standardized naming enables the use of scirt.sh (a tool contained in the QFSDP) to update the repository.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document assumes you have reviewed the contents of the SuperCluster Supported Versions document for your hardware type as well as the SuperCluster Critical Issues document.|
|1) List existing package publishers|
|2) Evaluate existing repository contents|
|3) Remove certain or all current publishers if your repository is not functional, points to a non-local repository or if you just want to change it so it looks identical to best practices.|
|4) Create new shares on the ZFSSA and populate the repositories|
|5) Verify your package publishers with step 2) above|