Use > Get started with Chef Cookbooks in SA > Package repository for Chef

Package repository for Chef

Package installations in Chef rely on the native package manager to retrieve the packages and dependencies from the configured repositories. This requires that the managed server be connected to the internet directly or through an internet proxy.

If SA is deployed in an air-gapped environment, the only source of package content is the SA Software Repository. In this case, the package managers (PKGMGR) on the managed servers need to be configured to use the Software Repository as a package repository for Chef.

Specifying the package repository for Chef

This section describes how to make the Chef content (recipes) search for packages inside SA instead of the Internet.

Note
To perform this task, the system administrator must belong to a user group with the appropriate permissions to edit System Configuration Settings.

Caution Editing SA System Configuration settings is discouraged unless you have approval from HPE Support to make a specific change. Changes to the System Configuration settings can have adverse effects on all SA operations and cannot always be resolved. You may perform this specific task as explicitly stated, but do not change any other System Configuration settings without the express instructions from SA Support.

To modify the package repository setting:

  1. Log in to the SA Client as an Opsware System Administrator.
  2. Navigate to system configuration settings for the Command Engine:
    Administration > System Configuration > Command Engine
  3. Search for ‘way.chef.package_repository’.
  4. Enter the configuration state that works for your environment:
    • 0: SA package repository only (default)
    • 1: Both the SA package repository and external repositories configured on the managed server
    • 2: Repositories configured on the managed server only

Note
Setting SA as the package repository for Chef works only for managed servers that use yum as their package manager.