Creating a Versioned Custom Software Source

• Console
• CLI
• API

• 1. Open the navigation menu and click Observability & Management. Under OS Management Hub, click Software sources.
  2. Under List scope, select the compartment to create the software source in.
  3. Click Create custom software source.
  4. On the Add basic details page, provide the following details, and then click Next:
     • Name: Enter a name for the source. You can change the name at any time. The name doesn't need to be unique, because an Oracle Cloud Identifier (OCID) uniquely identifies the custom software source.

     • Description: (Optional) Enter a description for the source.

     • Version: Enter an identifier. Adding a version disables the automatically update content option. To create custom software source, leave this value blank and instead follow Creating a Custom Software Source.

     • Automatically resolve dependencies: Enable auto-resolve to have the service automatically resolve package and module dependencies for any packages included in the source. Dependency resolution only includes packages from vendor software sources that are selected for the custom software source. If a dependent package resides in a software source that's not associated with the custom software source, the package will not be included.

     • Show advanced options: Click to add tags to this resource.

       If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you're not sure whether to apply tags, ask an administrator or skip this option. You can apply tags later.

  5. On the Select software sources page, select the vendor software sources to add, and then click Next:

     • OS vendor: Select the OS vendor. For example, Oracle.

     • OS version: Select the OS version. For example, Oracle Linux 8.

     • Architecture: Select the system architecture. For example, x86_64.

     • Compartment: Select the compartment containing the software sources.

     • Available software sources: Select the software sources to add.

     Tip
     
     

     Don't see any software sources? You might need to change the compartment or replicate vendor software sources.

  6. Select how to specify package content using Filters or a Package list. Specify the packages, and then click Next:

     • Only include the latest version: This option is required for versioned custom software sources. The service includes only the single latest available version of packages within constraints of your filters or package list. See Limiting Packages and Modules to the Latest Version.

     Create filters

     • Scope: Select either Include or Exclude.

     • Resource: Select one of the following options, and then provide additional values as required:

       • Package: To create a filter that includes or excludes the specified package from the selected vendor software source, enter the package name and optionally enter a version. If no version is specified, the service includes all versions. The acceptable package version format is 'epoch:version-release' or 'version-release'. For example, package name: edk2-ovmf and package version: 1:20210616-3.el8.
       • Group: To create a filter that includes or excludes the package group from the selected vendor software sources, select a yum or DNF package group.
       • Module: To create a filter that includes or excludes modular content from the selected vendor software sources, select the module name, stream, and stream profile.

     • + Another filter: Click to add more filters.

     Provide package list

     Run rpm -qa on a reference instance to create a list of packages. Either Upload or Paste the package list into the window.

     rpm -qa > /tmp/my-package-list.txt

     For example, the format of the packages would be:

     pam-1.3.1-27.el8.x86_64
     openssl-libs-1.1.1k-12.el8_9.x86_64
     libreport-filesystem-2.9.5-15.0.4.el8.x86_64

  7. On the Review page, review the details of the source, and make any changes as needed.
  8. Click Submit.

     Depending on the number of packages specified, the source can take a few moments to create.

     For troubleshooting, see Custom Software Source Creation Failed.

• Use the oci os-management-hub software-source create-versioned-custom-swsrc command and required parameters to create a versioned custom software source.

  oci os-management-hub software-source create-versioned-custom-swsrc  --compartment-id ocid --display-name name --software-source-version designator --vendor-software-sources software-source-ocids [OPTIONS]

  For a tutorial on using the CLI to generate a custom software source from an existing system, see Create Custom Software Sources with the OCI CLI.

  For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

• Run the CreateSoftwareSource operation to create a versioned custom software source.