Install Chef Manage

The Chef management console enables the management of nodes, data bags, roles, environments, and cookbooks by using a web user interface. In addition, access to nodes, data bags, roles, environments, and cookbooks is configurable using role-based access control (RBAC).

Requirements

The Chef management console add-on has the following requirements:

  • Enterprise Chef version 11.0.1 (or later)
  • The existing legacy Chef management console web user interface must be disabled
  • TCP protocol ports 443

Install the Server

The Chef management console is installed as a premium feature of the Chef server and can be enabled in both standalone or high availability configurations.

Standalone

To set up Chef management console for a standalone configuration:

  1. Contact Chef and get the package that is appropriate for the Chef server platform and operating system

  2. Install the package on the same server that is running Chef server 11.0.1 or higher. For example on Ubuntu:

    $ dpkg -i opscode-manage_1.0.0-1.ubuntu.10.04_amd64.deb
    
  3. Disable the legacy web interface. Modify the private-chef.rb file (located at /etc/opscode/private-chef.rb) to disable the existing opscode-webui service.

    opscode_webui['enable']=false
    

    If the private-chef.rb file does not exist, then create the file and add this setting to it.

  4. Reconfigure the Chef server:

    $ private-chef-ctl reconfigure
    
  5. Reconfigure the Chef management console:

    $ opscode-manage-ctl reconfigure
    

High Availability

To set up the Chef management console server for a high availability configuration:

  1. Contact Chef and get the package that is appropriate for the Chef server platform and operating system.

  2. Install the package on the same frontend servers that are running Chef server, version 11.0.1 or higher. For example on Ubuntu:

    $ dpkg -i opscode-manage_1.0.0-1.ubuntu.10.04_amd64.deb
    
  3. Disable the legacy web interface. Modify the private-chef.rb file (located at /etc/opscode/private-chef.rb) to disable the existing opscode-webui service:

    if PrivateChef['servers'][node['fqdn']]['role'] == 'frontend'
      opscode_webui['enable'] = false
    end
    

    If the private-chef.rb file does not exist, then create the file and add this setting to it. This step is required for each of the frontend servers in the Enterprise Chef deployment.

  4. Reconfigure the Chef server:

    $ private-chef-ctl reconfigure
    

    This step is required for each of the frontend servers in the Chef server deployment. For example, in a configuration with two backend servers and three frontend servers, this command would need to be run on all three frontend servers.

  5. Reconfigure the Chef management console server:

    $ opscode-manage-ctl reconfigure
    

    This step is required for each of the frontend servers in the Chef server deployment.

Upgrade the Server

Chef management console can be upgraded as part of a standalone or high availability configuration:

  1. Contact Chef and get the package that is appropriate for your Enterprise Chef server’s platform and operating system.

  2. Install the package on the same machines that are currently running Enterprise Chef. For example on Ubuntu:

    $ dpkg -i opscode-manage_1.0.0-1.ubuntu.10.04_amd64.deb
    
  3. Reconfigure the Enterprise Chef server:

    $ opscode-manage-ctl reconfigure
    

    This step is required for each of the front end servers in the Enterprise Chef deployment. For example, in a configuration with two back end servers and three front end servers, this command would need to be run on all three front end machines.