Installing and Administering Solaris Container Manager 3.6.1

Chapter 2 Container Manager Installation and Setup

This chapter contains procedures for installing, setting up, and uninstalling the Solaris Container Manager 3.6.1 (Container Manager) software with wizards. For information about using the command line for these procedures, see Appendix A, Installing At the Command Line.

For the latest information about installing, setting up, and using the software, see the Solaris Container Manager 3.6 Release Notes.

This chapter discusses the following topics:

Container Manager Software Description

Container Manager is installed as an add-on product to the Sun Management Center 3.6.1 software with the latest patch applied. The add-on software is installed on the Sun Management Center server layer or agent layer, depending on the function of the host. Sun Management Center is a three-tier application that consists of the following three layers: server, console, and agent. For more information about the three-tier architecture, see Sun Management Center Overview in Sun Management Center 3.6.1 Installation and Configuration Guide.


Note –

Container Manager requires that you install several additional software products. You must read all related documentation before beginning installation. You might need to apply software patches or plan for a reboot of the system to complete installation of other products. Also plan for the size requirements of these products before starting installation.


The following table provides a summary of Sun Management Center and Solaris Container Manager requirements.

For specific information about determining the total amount of resources needed, see Appendix C, Determining Hardware Resources, in Sun Management Center 3.6.1 Installation and Configuration Guide.

Table 2–1 Sun Management Center and Solaris Container Manager System Requirements

Base Layer 

Operating System 

Disk Space 

RAM 

Swap Space 

Sun Management Center Server (SPARC) 

Solaris 8, Solaris 9, and Solaris 10 Solaris Developer Software Group installation 

800 Mbytes total 

300 Mbytes in /opt

500 Mbytes in /var/opt

512 Mbytes minimum 

1 Gbyte recommended for small to large servers 

2 Gbytes recommended for extra-large servers 

1 Gbyte recommended 

Sun Management Center Agent (SPARC) 

Solaris 8, Solaris 9, and Solaris 10 

18 Mbytes per agent in /opt/SUNWsymon

2 Mbytes per agent in /var/opt/SUNWsymon

10 to 29 Mbytes per agent depending on modules loaded and system type 

 

Sun Management Center Agent (x86) 

Solaris 9 and Solaris 10 

18 Mbytes per agent in /opt/SUNWsymon

2 Mbytes per agent in /var/opt/SUNWsymon

10 to 29 Mbytes per agent depending on modules loaded and system type 

 

Solaris Container Manager Server (SPARC) 

Solaris 8, Solaris 9, and Solaris 10 

300 Mbytes 

512 Mbytes minimum 

1 Gbyte recommended for small to large servers 

2 Gbytes recommended for extra-large servers 

 

1 Gbyte recommended 

Solaris Container Manager Agent (SPARC and x86) 

Solaris 8, Solaris 9, and Solaris 10. 

Solaris Container Manager requires Solaris Resource Manager 1.3 on Solaris 8. Share memory is supported from Solaris 9 Update 5. 

18 Mbytes per agent in /opt/SUNWsymon

2 Mbytes per agent in /var/opt/SUNWsymon

10 to 29 Mbytes per agent depending on modules loaded and system type 

 

Performance Reporting Manager Server (SPARC) 

Solaris 8, Solaris 9, and Solaris 10 

Depends on reporting options selected. 

  • Small configuration: 5 Gbytes

  • Medium configuration: 12 Gbytes

  • Large configuration: 24 Gbytes

1 Gbyte 

1 Gbyte recommended 

Performance Reporting Manager Agent (SPARC and x86) 

Solaris 8, Solaris 9, and Solaris 10 

8000 Kbytes minimum 

80 Mbytes needed for 1000 properties logged at five-minute intervals 

   

The Container Manager software runs on the following versions of the Solaris operating system.

Table 2–2 Container Manager Features by Solaris OS Version

OS Version 

Container Manager Features 

Solaris 8 6/00 through Solaris 8 2/02 (SPARC® only)

Together with the Solaris Resource Manager 1.3 software, features include the ability to specify a minimum CPU reservation and a memory cap. 

Solaris 9 FCS through Solaris 9 8/03 (SPARC and x86) 

Features include the ability to specify a minimum CPU reservation. Memory control is not supported. 

Solaris 9 12/03, or later (SPARC and x86) 

Features include the ability to specify a minimum CPU reservation and a memory cap. Resource Pool management is also supported. 

Solaris 10 (SPARC and x86) 

Features include the ability to specify a minimum CPU reservation and a memory cap, zone management, dynamic resource pools, and IP Quality of Service. 

The Container Manager agent runs on all the hardware platforms that Sun Management Center 3.6.1 supports for the agent layer. For more information, see Chapter 3, Late-Breaking News, in Sun Management Center 3.6 Release Notes.

The Container Manager software consists of the following architecturally neutral software packages for both SPARC and x86:


Note –

The Container Manager module is automatically loaded after installation and setup of the software is complete. The module is not visible in the Sun Management Center Java or web console. You do not need to manually load this module in Sun Management Center as with other add-on software.


Installing Container Manager Software


Note –

(Solaris 10 only) Install Container Manager in a global zone.


You can install the Container Manager add-on software either by using the Sun Management Center 3.6.1 installation wizard or the command line. This section discusses how to install the software by using the installation wizard. For more information about installing at the command line, see Appendix A, Installing At the Command Line.

The Container Manager software can be installed at the following times:

The Performance Reporting Manager software must also be installed if you want to use the performance and accounting data features of Container Manager. For more information about installation and setup of this software, see the Sun Management Center 3.6.1 Performance Reporting Manager User’s Guide. If you do not intend to use these features, you do not need to install this add-on software.

ProcedureTo Install Container Manager During Upgrade to Sun Management Center 3.6.1

Step

    For more information and upgrade steps, see the Sun Management Center 3.6 Installation and Configuration Guide. You can also install additional add-on software, such as Performance Reporting Manager, at the same time.

ProcedureTo Install Container Manager Individually

Steps
  1. As superuser (su -), start the Sun Management Center installation wizard by typing:


    # /opt/SUNWsymon/sbin/es-guiinst
    

    where /opt is the directory in which Sun Management Center 3.6.1 is installed. Substitute the name of the actual directory if it is different on your system.

    The Sun Management Center installation wizard appears and guides you through the installation process for the software. Click the Next button to move through the wizard.

  2. Provide the source directory of the Container Manager software files when prompted.

    • On SPARC systems, choose from the following:

      • If installing from the software CD, type:


        # /<DiskMountDir>/image
        
      • If installing from a directory to which the software has been copied, type:


        # disk1/image
        

        where disk1 is the location where the software was copied.

    • On x86 systems, choose from the following:

      • If installing from the software CD, type:


        # /<DiskMountDir>/x86/image
        
      • If installing from a directory to which the software has been copied, type:


        # disk1/x86/image
        

        where disk1 is the location where the software was copied.

  3. Select the check box Install Product Documentation if you want to install the documentation.


    Note –

    The documentation installed in this step is the Sun Management Center 3.6 collection. The Solaris Container Manager 3.6.1 documentation is not included in this collection. The Solaris Container Manager 3.6.1 documentation collection is at http://docs.sun.com/app/docs/coll/810.6.


    You can view installed documentation from a browser at /var/opt/sun_docs/sundocs.html.

  4. If installing the server layer, select the desired languages from the Select Language Support panel. This panel only appears when installing the server layer.


    Note –

    Translated documentation installed in this step is for Sun Management Center 3.6 only. Translated documentation for Solaris Container Manager 3.6.1 is at http://docs.sun.com/app/docs/coll/810.6 only.


    The Checking for Available Products panel appears. When the progress bar is finished, the Products Already Installed panel appears.

  5. Review the list of products already installed.

    The Select Add-on Products panel appears.

  6. Select Solaris Container Manager 3.6.1 from the list of add-on software to be installed.

    The Add-on Products License Agreement panel appears.

  7. Read the license agreement.

    • If you agree to the license agreement, click I Agree. The Confirmation panel appears.

    • If you do not agree to the license agreement, click I Do Not Agree. The installation wizard exits and installation quits.

    You must click the I Agree button to proceed with installation.

  8. Review the Confirmation panel.

    The Installation Complete panel appears when the software installation is complete.

    After installation of the Container Manager software is complete, the setup wizard guides you through the setup process for the software. For more information, see Setting Up Container Manager Software.

Setting Up Container Manager Software

After installation is complete, you must run the Container Manager setup wizard to configure the server and agent layers. As with installation of the software, you can run the setup process at the time you setup the Sun Management Center 3.6.1 installation or upgrade. You can also setup the software individually at a later time.

The following configuration files are created in the following locations during the setup process:

If the /etc/pooladm.conf file already exists on a host, a backup of the existing file is created. This backup of the original file is named /etc/pooladm.conf.scmbak. If an active configuration exists on a host, all processor sets that are not associated with a resource pool are removed. The scheduling class for the resource pools is then set to fair share scheduler (FSS). Finally, the new configuration is committed and is stored in /etc/pooladm.conf.

If an active configuration does not exist on a host, a new configuration is discovered and stored in /etc/pooladm.conf. This discovered configuration is committed to make it active. The default pool scheduling class is set to FSS.

If the extended accounting files are active on a host at the time of setup, they remain the same. If the files are not active, they are then configured and activated. During configuration, the extending accounting file name is set to /var/adm/exacct/tasktimestamp.

Additionally, during the setup process the following changes are made to the host by the software:

For more information about resource pools, scheduling classes, and extended accounting, as well as other standard Solaris resource management concepts, see System Administration Guide: Network Services.


Caution – Caution –

Standard command-line commands in Solaris software resource management are not supported by Container Manager. Use the Container Manager GUI to manage the software.


ProcedureTo Set Up Container Manager During Sun Management Center Installation or Upgrade

Step

    For more information and detailed steps, see Chapter 6, Installing and Updating Agents and Installing on Microsoft Windows, in Sun Management Center 3.6.1 Installation and Configuration Guide.

ProcedureTo Set Up Container Manager Individually

Steps
  1. As superuser (su –), start the Sun Management Center setup wizard by typing:


    # /opt/SUNWsymon/sbin/es-guisetup
    

    where /opt is the directory in which Container Manager is installed. Substitute the name of the actual directory if it is different on your system.

    The Container Manager setup wizard appears and guides you through the setup process for the software. The Overview panel appears first. Click the Next button to move through the wizard. Use the Back button to make corrections by moving back through the wizard.


    Note –

    If you have installed more than one Sun Management Center add-on product, the setup wizard for each product appears automatically. Each wizard guides you through the setup process for its add-on product. Each new setup wizard appears automatically after the setup process is completed for the previous add-on product. The setup wizard for the Container Manager software might not be the first to appear.


  2. Review the list in the Stopping Components panel.

    The Sun Management Center components must be stopped before the setup process can continue. The Advanced Setup Options panel appears if you have completed the setup process for some of the add-on products installed. The remaining add-on software can be set up now.

  3. Select the Configure Add-ons option.

    The add-on software that was recently installed but not yet set up is now set up.

  4. Review the list of products in the Setup Complete panel.

    The Select Add-on Products panel appears. All products newly installed on the system that will be set up are listed. You can also run setup again on any product that was previously set up.

  5. Review the list of products to confirm that Container Manager appears as a product to be set up. Click Next to start the setup process.

    A progress panel appears while all components are being set up.

  6. When setting up the agent layer, if processor sets are detected that are not associated with a resource pool, a panel requests permission to delete these sets. Select from the following options:

    • Yes – These processor sets will be deleted from the system. In order for Container Manager to function correctly, any processor set that is not associated with a resource pool must be removed. This removal is necessary because projects need to be associated with the pools. After this selection, these processor sets are automatically deleted for you, and the setup process continues.

    • No – These processor sets will not be deleted from the system. After this selection, the setup wizard exits and the Container Manager software is not set up on the system. You are unable to use the Container Manager software on any host that has processor sets that are not associated with a resource pool.

    • Cancel – The setup wizard exits. The Container Manager software is not set up on the system.

  7. Type the valid user names separated by commas. These users must already be present in the /var/opt/SUNWsymon/cfg/esusers file on the server machine, and must be assigned to either esadm or esdomadm group.


    Note –

    Solaris Container Manager setup does not authorize the users.


  8. When setting up a server layer installation, provide the full path to a directory that has at least 300 Mbytes free disk space for the database and click Next.

  9. After the progress bar in the Container Manager DB Configuration panel completes, click Next.

  10. To invoke the Start Wizard, click Next.

    After the setup procedure is complete, you have the option to start the Sun Management Center processes. For more information, see Chapter 8, Starting and Stopping Sun Management Center, in Sun Management Center 3.6.1 Installation and Configuration Guide.

    For information about starting the Container Manager GUI, see To Start the Container Manager GUI.

Creating Profiles

After setting up Solaris Container Manager, the user needs to do the following tasks to manage projects, pools, and zones:

Following are the necessary profiles:

Ensure that the user is associated with the necessary profiles by running the following command:

$ profiles <username>

(On Solaris 9 and 10)

Add the following line to the /etc/security/prof_attr file.

Pool Management:::Resource pool management profile:help=RtPoolMgmt

If Pool Management profile is not present in the /etc/security/prof_attr file, add the following lines to the /etc/security/exec_attr file.

Pool Management:suser:cmd:::/usr/sbin/pooladm:euid=0

Pool Management:suser:cmd:::/usr/sbin/poolcfg:euid=0

(On Solaris 8)

Add the following line to the /etc/security/prof_attr file.

Project Management:::Project management profile:help=RtPoolMgmt

If Project Management profile is not present in the /etc/security/prof_attr file, add the following lines to the /etc/security/exec_attr file.

Project Management:suser:cmd:::/usr/sbin/projadd:euid=0

Project Management:suser:cmd:::/usr/sbin/projmod:euid=0

Project Management:suser:cmd:::/usr/sbin/projdel:euid=0

Alternatively, you can create profiles using the Solaris Management Console or smprofile.

Run the following command to find if the user is a part of the local access user list for the SCM module.

<BASEDIR>/SUNWsymon/sbin/es-config -M scm-container -s

If user is not part of the access list, run the following command:

<BASEDIR>/SUNWsymon/sbin/es-config -M scm-container -l <user_name>

Backup and Restore

Use the Sun Management Center backup (es-backup) and restore (es-restore) scripts to back up or restore Container Manager data. For more information, see Sun Management Center Backup and Recovery in Sun Management Center 3.6.1 Installation and Configuration Guide.

Agent Update

If you want to upgrade the agent layer on multiple hosts with the Container Manager software, you can use the agent update feature. When using the agent update feature, it is best to keep all Container Manager agent machines that are in the same server context at the same Sun Management Center version levels. For more information about server context, see Sun Management Center Architecture in Sun Management Center 3.6.1 User’s Guide.

For more information about using the agent update feature during installation, see Creating Agent Installation and Update Images in Sun Management Center 3.6 Installation and Configuration Guide.

Uninstalling Container Manager Software

Uninstallation of the software follows standard Sun Management Center procedures. Accordingly, you can use either the command line or the uninstallation wizard. The following is removed in addition to the software packages: the module entry from base-modules-d.dat and the application registration from Sun Web Console. You have the option to retain or delete the data stored in the database during the removal process. System resource configuration changes made during installation are not removed when the Container Manager software is uninstalled.

For information about uninstalling the software using the command line, see Appendix A, Installing At the Command Line. For information about standard Sun Management Center removal procedures, see Appendix A, Uninstalling Sun Management Center, in Sun Management Center 3.6.1 Installation and Configuration Guide.

ProcedureTo Remove the Container Manager Software

Steps
  1. As superuser (su –), start the uninstallation wizard by typing:


    # /opt/SUNWsymon/sbin/es-guiuninst
    

    where /opt is the directory where Sun Management Center is installed. Substitute the name of the actual directory if it is different on your system. The Sun Management Center uninstallation wizard appears.

  2. Select Container Manager from the list of software, and click Next.

  3. Indicate whether to preserve the data files, and click Next.

    The software begins to uninstall. The Container Manager packages and configuration files are removed. If you chose not to preserve the date files, they are removed as well.

  4. Click Close to exit the wizard.