SuperCluster- Best Practices for Local Image Packaging System (IPS) Software Package Repository

Asset ID:	1-71-2037729.1
Update Date:	2017-03-06
Keywords:

Solution Type Technical Instruction Sure

Solution 2037729.1 : SuperCluster- Best Practices for Local Image Packaging System (IPS) Software Package Repository

Applies to:

SPARC SuperCluster T4-4 Half Rack - Version All Versions and later
Oracle SuperCluster M6-32 Hardware - 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 SuperCluster T5-8 Half Rack - 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).

Goal

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.

Solution

Note: The IP address used in this document is the IP address of the storage network on the 8503 partition of the Infiniband . Replace with your IP address.

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.

Oracle SuperCluster Supported Software Versions - All Hardware Types <Document 1567979.1>
SuperCluster Critical Issues <Document 1452277.1>

1) List existing package publishers

Note: If your repositories look similar to the top one without an embedded OpsCenter running or the second one with an embedded OpsCenter running then proceed to "Validating Repository Contents" section. Please be aware that embedded OpsCenter was an early delivery model until EM OpsCenter 12 C r2 was released. EM OpsCenter 12C r2, on a separate management server, is now the supported configuration. Your repository is not invalid if you do not have these local cacao mp-re and opscenter local repos. In fact if you do have them and the old install you should open an SR to see how to get to the current supported model with the OpsCenter Enterprise Controller and repos off the SuperCluster.

# pkg publisher

PUBLISHER                   TYPE     STATUS P LOCATION
exa-family                  origin   online F file:///net/192.168.28.1/export/IPS-repos/exafamily/repo/
solaris                     origin   online F file:///net/192.168.28.1/export/IPS-repos/solaris11/repo/

PUBLISHER                   TYPE     STATUS P LOCATION
exa-family                  origin   online F file:///net/192.168.28.1/export/IPS-repos/exafamily/repo/
solaris                     origin   online F file:///net/192.168.28.1/export/IPS-repos/solaris11/repo/
cacao                       origin   online   file:///var/opt/sun/xvm/images/IPS/ac-ips-repo/
mp-re                       origin   online   file:///var/opt/sun/xvm/images/IPS/ac-ips-repo/
opscenter                   origin   online   file:///var/opt/sun/xvm/images/IPS/ac-ips-repo/

2) Evaluate existing repository contents

Note: Modify the path to your Solaris 11 repo if the publisher output shows the share path and name is different from the example.

Note: There is a tool named scirt.sh that is part of the QFSDP. In the April 2015 QFSDP this tool is located in 20761732/Infrastructure/SuperClusterMaintenanceUpdate/SCMU_2015.04/tools. This tool can be used to update the repo with the incremental changes represented in the QFSDP. Please note that the QFSDP can be installed without updating the repo. Failure to update the repo results in downstream issues with things such as zone creation and maintenance. For scirt.sh to function properly the repos must be in the proper format. scirt.sh expects the repo to be in a project named IPS-repos. scirt.sh expects the mount point to be /export/IPS-repos. scirt.sh expects the automounter to mount the repo.

2a) Use pkg list to get your current entire version to match to the repository contents.

# pkg list entire
NAME (PUBLISHER) VERSION IFO
entire 0.5.11-0.175.3.14.0.6.0 i--

2b) You can use the pkgrepo command to check the contents and verify the structure of your repository. The example below meets the requirements for a functional solaris repository.

Note: Your versions may vary based off your Quarterly Full Stack Download Patch level, SRU level and Custom Incorporations applied. Also you may have more listed if you have been though several upgrades.
At a minimum you require the base Solaris 11.3 image and your current installed SRU and Custom Incorporations

# pkgrepo list -s file:///net/192.168.28.1/export/IPS-repos/solaris11/repo/ | grep entire
solaris entire 0.5.11,5.11-0.175.3.14.0.6.0:20161110T164958Z
solaris entire 0.5.11,5.11-0.175.3.11.0.6.0:20160815T002341Z
solaris entire 0.5.11,5.11-0.175.3.7.0.6.0:20160519T170917Z
solaris entire 0.5.11,5.11-0.175.3.4.0.5.0:20160114T213235Z
solaris entire 0.5.11,5.11-0.175.3.1.0.5.0:20151006T140051Z
solaris entire 0.5.11,5.11-0.175.2.15.0.5.0:20151019T195625Z

Note Your versions will vary based on your QFSDP level and if a reactive upgrade was done to address a defect.

# pkgrepo list -s file:///net/192.168.28.1/export/IPS-repos/exafamily/repo/ | grep exa-family
exa-family system/management/eshm/osc 0.5.11,5.11-3.0.0.0.1191:20161005T000717Z
exa-family system/management/eshm/osc 0.5.11,5.11-2.2.0.1109:20160607T224937Z
exa-family system/platform/supercluster 0.5.11,5.11-2.3.0.945:20161004T212532Z
exa-family system/platform/supercluster 0.5.11,5.11-2.3.0.925:20160907T180143Z
exa-family system/platform/supercluster 0.5.11,5.11-2.2.0.907:20161104T190429Z
exa-family system/platform/supercluster 0.5.11,5.11-2.2.0.862:20160628T005802Z... ...

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.

3a) List out a publisher that may need help or adjustments

# pkg publisher
PUBLISHER                   TYPE     STATUS P LOCATION
solaris                     origin   online F file:///net/192.168.28.1/export/ssc/s11repo/
solaris                     origin   online F file:///var/tmp/idr808.4.p5p/
solaris                     origin   online F http://ipkg.us.oracle.com/solaris11/support/
exa-family                  origin   online F file:///net/192.168.28.1/export/ssc/exafamily/

Note: Unset any publishers pointing to an external repository or any other repository source not on the SuperCluster. These are no longer supported on SuperCluster in order to prevent accidentally upgrading the system beyond a tested and supported level. Also unset any publishers pointing to /var/tmp for standard SuperCluster IDRs. We will be using Custom Incorporations with the exafamily and Solaris 11 repository.

3b) To remove a targeted origin for a publisher you use the pkg set-publisher with the -G option

# pkg set-publisher -G http://ipkg.us.oracle.com/solaris11/support/ solaris
# pkg set-publisher -G file:///var/tmp/idr808.4.p5p/ solaris

3c) To remove all origins for a particular publisher use pkg unset-publisher <publishername>

Note: This will remove all publishers. Do not attempt to create any local zones or do any other maintenance operations until they have been rebuilt.

# pkg unset-publisher solaris
# pkg unset-publisher exa-family

3d) Next evaluate any OpsCenter based repositories. If you are not currently using an embeded OpsCenter on SuperCluster and you have OpsCenter based publishers you will need to un-publish them.

# pkg unset-publisher cacao
# pkg unset-publisher mp-re
# pkg unset-publisher opscenter

4) Create new shares on the ZFSSA and populate the repositories

Note: Follow this procedure to create a share for each item specified in step 4c) if your repositories do not exist or if you simply want to have the match SuperCluster best practices. If they do exist follow step 4b) for validating the setup of the shares. The share may already be created on your storage array.

4a)Login to the ZFSSA over the IB storage network and create the required NFS shares:

# ssh root@192.168.28.1
orlt5sn1:>configuration cluster show
Make sure the controller state is either AKCS_OWNER or AKCS_CLUSTERED before
proceeding.
orlt5sn1:>shares
orlt5sn1:shares>project IPS-repos (or skip if the project already exists)

orlt5sn1:shares IPS-repos (uncommitted)>set mountpoint=/export/IPS-repos orlt5sn1:shares IPS-repos (uncommitted)>set default_volblocksize="128k"
orlt5sn1:shares IPS-repos (uncommitted)>commit

orlt5sn1:shares>select IPS-repos
orlt5sn1:shares IPS-repos>filesystem solaris11
orlt5sn1:shares IPS-repos/solaris11 (uncommitted)>set root_permissions=755
orlt5sn1:shares IPS-repos/solaris11 (uncommitted)>set sharenfs="sec=sys,rw=@192.168.28.0/24,root=@192.168.28.0/24"
orlt5sn1:shares IPS-repos/solaris11 (uncommitted)>commit

orlt5sn1:shares IPS-repos> filesystem exafamily
orlt5sn1:shares IPS-repos/exafamily (uncommitted)>set root_permissions=755
orlt5sn1:shares IPS-repos/exafamily (uncommitted)> set sharenfs="sec=sys,rw=@192.168.28.0/24,root=@192.168.28.0/24"
orlt5sn1:shares IPS-repos/exafamily (uncommitted)>commit

If you are using Solaris Cluster:

orlt5sn1:shares IPS-repos> filesystem osc4
orlt5sn1:shares IPS-repos/osc4 (uncommitted)>set root_permissions=755
orlt5sn1:shares IPS-repos/osc4 (uncommitted)> set sharenfs="sec=sys,rw=@192.168.28.0/24,root=@192.168.28.0/24"
orlt5sn1:shares IPS-repos/osc4 (uncommitted)>commit

4b) If you did not create your shares using step 4a) check the setting on the shares. Check each share for each of the items in 4c).

Note: If they do not match modify them using the set root_permissions and set sharenfs settings from above. Modify the sharenfs setting for your IB storage network subnet if necessary.

# ssh 192.168.28.1 shares select IPS-repos select solaris11 get sharenfs
sharenfs = sec=sys,rw=@10.141.177.0/24:@192.168.28.0/22,root=@10.141.177.0/24:@192.168.28.0/22
# ssh 192.168.29.1 shares select IPS-repos select solaris11 get root_permissions
root_permissions = 755

4c) Create the files as a repository with the pkgrepo create

# pkgrepo create /net/192.168.28.1/export/IPS-repos/solaris11
# pkgrepo create /net/192.168.28.1/export/IPS-repos/exafamily

4d) Use scirt.sh to update your new repo. This will be in the patch bundle for your QFSDP. For April 2015 scirt.sh is in 20761732/Infrastructure/SuperClusterMaintenanceUpdate/SCMU_2015.04/tools .

If the IB IP address of the ZFS storage appliance is 192.168.28.1 and the current working directory is the location of scirt.sh , then:

ZFS_SA=192.168.28.1

====== to Check repository location
./scirt.sh shares -d ${ZFS_SA}
====== does the location match your publisher ?"
====== if not, break out (^C) and repair"
pause

======= check for a valid plan
./scirt.sh plan -d $ZFS_SA ../solaris/
======= update the repositories
./scirt.sh upload -d $ZFS_SA ../solaris/

4e) The Custom Incorporation for the January 2017 QFSDP is in 24918333/Infrastructure/SuperClusterMaintenanceUpdate/SCMU_2017.01/solaris/components/s11/sol-11_3_14_6_0.

For purpose of this example we will assume the patch location is /work/qfsdp_Jan_2017.

Please verify the proper Custom Incorporation level in the top level readme of your current or target QFSDP. In between QFSDP the recommended Custom Incorporation may be chnaged and if so will be documented in SuperCluster Recommended Custom Incorporations, IDRs, and CVEs Addressed (Doc ID 2086278.1))

cd to the Custom Incorporation location
# cd /work/qfsdp_jan_2017/24918333/Infrastructure/SuperClusterMaintenanceUpdate/SCMU_2017.01/solaris/components/s11/sol-11_3_14_6_0

Receive the Custom Incorporation into the solaris repository
# pkgrecv -s solaris-supercluster-solaris@11031406.10000106.p5p -d /net/192.168.28.1/export/IPS-repos/solaris11/repo/ '*'
Catalog the contents
# pkgrepo rebuild -s /net/192.168.28.1/export/IPS-repos/solaris11/repo

4f) Set your package publishers

Point the solaris publisher to the main s11repo location
# pkg set-publisher -g file:///net/192.168.28.1/export/IPS-repos/solaris11/repo/ solaris
Point the exa-family publisher to the exafamily repo location
# pkg set-publisher -g file:///net/192.168.28.1/export/IPS-repos/exafamily/repo/ exa-family

5) Verify your package publishers with step 2) above

Attachments

This solution has no attachment