Creating a Versioned Custom Software Source

Create a versioned custom software source to use in a lifecycle environment in OS Management Hub.

Important

Carefully select the packages and modules in the versioned custom software source. When promoted to a lifecycle stage, the service installs all content in the source to the target instances.

To create a versioned custom software source, you must first add vendor software sources to the service. Then, select the vendor software sources and use filters or a package list to specify the packages and modules to include in the source.

  • On the Software Sources list page, from the Actions menu, select Create Custom Software Source.

    If you need help finding the list page, see Listing Software Sources.

    1. Add Basic Details

    Provide the basic information and settings for the versioned source, and then select 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 update content: Disabled. Versioned sources are immutable and can't be updated.

    • 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: 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.

    2. Select Software Sources

    Select the vendor software sources to add to the custom source, and then select 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.

    3. Select Package Content

    Specify the packages in the custom software source, either by using Filters or a Package list, and then select Next.

    • Only include the latest version: Enabled. 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: Select to add more filters.

    Provide Package List

    Either Upload or Paste the package list into the window.

    Valid formats include N (package name), NVRA (name, version, release, architecture), or NEVRA (name, epoch, version, release, architecture)

    For example, the format of the packages would be:

    python2
    libselinux-2.8-6.el8.x86_64
    NetworkManager-adsl-1:1.30.0-13.0.1.el8_4.x86_64

    4. Review

    Review the details of the source. Make any changes as needed, and then select Submit.

    Tip

    Software source creation failed? See Custom Software Source Creation Failed for troubleshooting.
  • 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.