Creating a Custom Software Source

Select specific content from vendor software sources to create a custom software source in OS Management Hub.

Note

For versioned custom software sources, see Creating a Versioned Custom Software Source. A versioned source is specifically for use in lifecycle environments.

To create a 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.

  • Add Basic Information

    Provide the basic information and settings for the custom software 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.

    • Create in compartment: Select the destination compartment for the source.
    • Enable versioning: Leave disabled unless creating a versioned custom software sources and instead follow Creating a Versioned Custom Software Source.

    • Tags: (Optional) 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.

    Select Software Sources

    Select the vendor software sources to add to the custom source.

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

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

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

    • Use the Search and filter field to identify the required software sources and select the software sources to add.
      • Compartment: In Applied filter, select the compartment containing the software sources.

    Tip

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

    Select Next.

    Select Package Content

    Select how to specify the packages to include in the custom software source from the following options:

    • Include all available packages
    • Select packages via filters: Follow the steps in Add Package Filters.
    • Provide package list: Selecting this option displays a further option to either Upload package list from file, or Paste package list. Follow the steps in Provide Package List.

    The following options display, depending on which method you selected:

    • Automatically update content: Enable auto-update to have the service automatically review the custom software source packages and update them to the latest versions available. The service does this once a day. When disabled, the packages remain at the versions available when the source was created.
    • Automatically resolve package and module 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.
    • Only include the latest version based on your filters: When enabled, 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.

    Select Next.

    Add Package Filters

    In the Package filters table, select Add filter.

    • Scope: Select either Include or Exclude.

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

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

    Select Add to add the package filter to the list. Repeat this process to add more package filters.

    Provide Package List

    Either upload a package file, or paste the package list into the window, depending on the option selected.

    Note

    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

    After you have provided the package file or list, select Next.

    Review

    Review the details of the source. Make any changes as needed, and then select Create custom software source.

    Tip

    Software source creation failed? See Custom Software Source Creation Failed for troubleshooting.
  • Use the oci os-management-hub software-source create-custom-swsrc command and required parameters to create a custom software source.

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

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

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