JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 11.1 Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information


Part I Oracle Solaris Resource Management

1.  Introduction to Resource Management

2.  Projects and Tasks (Overview)

3.  Administering Projects and Tasks

4.  Extended Accounting (Overview)

5.  Administering Extended Accounting (Tasks)

6.  Resource Controls (Overview)

7.  Administering Resource Controls (Tasks)

8.  Fair Share Scheduler (Overview)

9.  Administering the Fair Share Scheduler (Tasks)

10.  Physical Memory Control Using the Resource Capping Daemon (Overview)

11.  Administering the Resource Capping Daemon (Tasks)

12.  Resource Pools (Overview)

13.  Creating and Administering Resource Pools (Tasks)

14.  Resource Management Configuration Example

Part II Oracle Solaris Zones

15.  Introduction to Oracle Solaris Zones

16.  Non-Global Zone Configuration (Overview)

17.  Planning and Configuring Non-Global Zones (Tasks)

18.  About Installing, Shutting Down, Halting, Uninstalling, and Cloning Non-Global Zones (Overview)

19.  Installing, Booting, Shutting Down, Halting, Uninstalling, and Cloning Non-Global Zones (Tasks)

20.  Non-Global Zone Login (Overview)

21.  Logging In to Non-Global Zones (Tasks)

22.  About Zone Migrations and the zonep2vchk Tool

23.  Migrating Oracle Solaris Systems and Migrating Non-Global Zones (Tasks)

24.  About Automatic Installation and Packages on an Oracle Solaris 11.1 System With Zones Installed

Image Packaging System Software on Systems Running the Oracle Solaris 11.1 Release

Zones Packaging Overview

About Packages and Zones

About Adding Packages in Systems With Zones Installed

Using pkg in the Global Zone

Using the pkg install Command in a Non-Global Zone

Adding Additional Packages in a Zone by Using a Custom AI Manifest

About Removing Packages in Zones

Package Information Query

Proxy Configuration on a System That Has Installed Zones

Configuring the Proxy in the Global Zone

Overriding system-repository Proxies by Using https_proxy and http_proxy

Parallel Zone Updates

How Zone State Affects Package Operations

25.  Oracle Solaris Zones Administration (Overview)

26.  Administering Oracle Solaris Zones (Tasks)

27.  Configuring and Administering Immutable Zones

28.  Troubleshooting Miscellaneous Oracle Solaris Zones Problems

Part III Oracle Solaris 10 Zones

29.  Introduction to Oracle Solaris 10 Zones

30.  Assessing an Oracle Solaris 10 System and Creating an Archive

31.  (Optional) Migrating an Oracle Solaris 10 native Non-Global Zone Into an Oracle Solaris 10 Zone

32.  Configuring the solaris10 Branded Zone

33.  Installing the solaris10 Branded Zone

34.  Booting a Zone, Logging in, and Zone Migration



Proxy Configuration on a System That Has Installed Zones

Persistent proxies should be set in an image by using the --proxy option as described in Chapter 5, Configuring Installed Images, in Adding and Updating Oracle Solaris 11.1 Software Packages. If a persistent image proxy configuration is not used, and http_proxy and https_proxy environment variables are always used to access repositories when running the pkg command, then the system-repository services should also be configured to use those same proxies through SMF system-repository service properties. See the pkg(1) man page.

Access to repositories configured in the global zone is provided to non-global zones using the system-repository service. Any updates to proxies for origins in the global zone are automatically made to the system-repository configuration. Using this method, no modifications are required to the system-repository SMF service.

It is also possible to configure the proxies used by the system-repository SMF service, overriding any proxies configured on publishers in the global zone. The system-repository proxies can be set by using the config/http_proxy or config/https_proxy SMF properties.

For more information, see the pkg.sysrepo(1M) man page and Adding and Updating Oracle Solaris 11.1 Software Packages

Configuring the Proxy in the Global Zone

You can configure the proxy directly in the global zone, and any updates to proxies for origins in the global zone are automatically made to the system-repository configuration. The system-repository service does not require modification.

Example 24-2 Configuring the Proxy in the Global Zone

# pkg set-publisher --proxy http://www-proxy -g http://pkg-server pub

No port specification is required unless the proxy accepts connections on a port other than 80.

If zones are on the system, the system-repository service is restarted, and the proxy is used to provide access to pkg-server.

Overriding system-repository Proxies by Using https_proxy and http_proxy

It is recommended that proxies be set in an image, and that only the system-repository service proxy be set. The https_proxy and http_proxy should be set in the environment when running the pkg command.

The procedures in this section are used to set proxies in the system-repository service on an internal subnet that does not have a direct connection to the IPS publisher repository. Use of this procedure overrides any proxies configured by the pkg command in the global zone. Non-global zones communicate with the system-repository over HTTP. The system-repository then accesses the publishers using the protocol for that repository as configured in the global zone.

This configuration allows the solaris non-global zones to contact the publisher set in the global zone as well. Recursive pkg operations into the solaris zones will succeed.

Example 24-3 Using https_proxy and http_proxy To Override Global Zone Proxies

For example, assume that the software on a system running solaris non-global zones is managed by IPS and requires the use of the proxy server http_proxy= for access to both http and https URLs. The following steps show how to use http_proxy and https_proxy environment variables and SMF service properties to allow the global zone and non-global zones to access the IPS repositories.

Note that these variables override any proxy configuration set on the origin unless the user is running the pkg command from a non-global zone to connect to the Universal Resource Identifier (URI) for a system publisher. In this case, the command goes through the system-repository.

A host name that can be resolved can also be used.

  1. Type the following lines to set the proxy in the shell for the global zone:

    # export http_proxy=
    # export https_proxy=

    Setting the proxy allows pkg commands to reach the publisher through the proxy server. This affects pkg operations that use an https or http URL and do not go through the system-repository for the global zone.

  2. To allow the solaris zones on the system to use the configured system publishers directly accessible from the global zone, execute the following commands:

    # svccfg -s system-repository:default setprop config/http_proxy =
    # svccfg -s system-repository:default setprop config/https_proxy = 
  3. To make the change take effect in the live SMF repository, run:

    # svcadm refresh system-repository
  4. To confirm that the setting is operational, run:

    # svcprop -p config/http_proxy system-repository
    # svcprop -p config/https_proxy system-repository

For more information on the pkg command, see the pkg(1) man page.