This section describes how to set up the registry after Domain/OS has been successfully installed. Note that several of the procedures in this section must be performed by the root user.
Because the registry uses the NCS Location Broker to obtain information about network resources, this section assumes that your network is configured properly for Location Broker operation. Consult Managing NCS Software for considerations concerning Location Brokers in the network or internet. Consult Managing Domain/OS and Domain Routing in an Internet for information about using the registry in an internet.
7.1 Steps to Set Up the Registry
The following list summarizes the steps to set up the registry. The pages that follow describe the steps in more detail.
1. Plan the network configuration, considering which machines should run registry servers (rgyd), and which machine should run the master registry.
2. Ensure that the required Location Brokers are in place for the newly planned registry sites.
3. Create the registry database.
4. Start the master registry server.
5. Configure the registry database:
Set policies, properties, and passwords Add names and accounts
6. Create slave registry replicas.
7. Set up cron to run passwd_refresh on nodes not running Domain/OS to ensure that the local password and group files are kept consistent with the registry. (The registry automatically maintains consistency with the local registry for Domain/OS machines.) The passwd_refresh command is described in Chapter 4.
8. Ensure that the /etc/rgy/pname_resolve file exists on each node that does not run Domain/OS. This file will supply a Domain mount point substitution string for nodes that do not run Domain/OS.
This chapter also describes how to restart a registry server.
7.2 Planning a Configuration
To plan a configuration, choose a site for the master registry server and, if you decide to run several servers, choose sites for them. The master and slave registry servers (rgyd) can reside only on machines that run Domain/OS. Client software can run on machines that run Domain/OS; SunOS 3.4, 3.5, or 4.0; or VAX UL TRIX 2.2.
7.2.1 Registry Server Requirements
Use the following considerations to plan the configuration of registry servers for your site:
• The hardware requirements for the nodes that will run registry servers are proportionate to the size of the registry database and the load imposed on the server. Use the following considerations as general guidelines:
A node running a registry server should have free disk space equal to either 8 MB or 5 times the size of the registry database, whichever is greater.
A node running a registry server should have at least 4 MB of memory. If the virtual memory size of the registry process is greater than 4 MB, the node's memory should be as close to the process virtual memory size as possible. The closer the memory size is to the process size, the more efficiently the registry process will run. (Use the ps -v command to determine process virtual memory size.)
Take care to choose registry server nodes large enough to accommodate future growth of the registry.
7-2 Setting Up the Registry
• You can run more than one registry daemon (rgyd) on a network. In an internet, we recommend that you run at least one rgyd in every network.
• Nodes running rgyd should be up and available at all times. It is especially important that the node where the master server runs be available throughout the network or internet.
7.3 Ensuring Proper Location Broker Configurations
Machines in the network use Network Computing System (NCS) Location Broker servers to locate registry servers. In general terms, the Location Broker maps services and resources to network addresses. In this case, the Location Broker provides information about the network locations of registries.
To do this, the Location Broker uses two servers: a glbd (the replicatable Global Location Broker daemon) that provides information about the resources throughout the entire network or internet and a IIbd (Local Location Broker daemon) that provides information about the local machine's resources.
To run the registry server or any NCS-based server:
• At least one Global Location Broker (glbd) must run on the network.
• A Local Location Broker (lIbd) must run on every node that runs a glbd and on every node that will run a registry server (master or slave).
NOTE: In rare instances, a nrglbd (non-replicatable global location broker) may run in place of a glbd. We strongly recommend that you consult Managing NCS Software for detailed informa-tion on configuring, starting, and managing Locainforma-tion Brokers.
7.4 Creating a New Registry Database
If you are setting up a new network or internet that does not contain an existing registry, use the linstall/tools/rgy_create utility to create a new database. When rgy_create creates a new database, it also initializes it with reserved names and accounts. Typically the new registry is created as part of Domain/OS installation. See Installing Software with Apollo's Release and Installation Tools for more information about rgy_create.
Because rgy _create is setuid as root, you may want to implement tighter protections on
rgy_cr~ate after you create the new regitstry database.