Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!samsung!sdd.hp.com!apollo!mk
From: mk@apollo.HP.COM (Mike Kong)
Newsgroups: comp.sys.apollo
Subject: Re: HELP separate registry data bases on same ethernet!
Summary: use location broker cells
Keywords: rgyd, glbd, llbd, ncs, confused
Message-ID: <4ca28172.20b6d@apollo.HP.COM>
Date: 5 Sep 90 23:10:00 GMT
References: <2490@naucse.cse.nau.edu>
Sender: root@apollo.HP.COM
Reply-To: mk@apollo.HP.COM (Mike Kong)
Organization: Hewlett-Packard Apollo Division - Chelmsford, MA
Lines: 53

In article <2490@naucse.cse.nau.edu> jdc@naucse.cse.nau.edu (John Campbell) writes:
>... It all looks something like this:
>
>      EGR                                              CHM
>Res   Ind   Cap                                 Hyd----Nit---Oxy---Car
> |     |     |                                   |
> +-----+-----+-----------------------------------+
>
>Where Hyd (//hydrogen) with two ethernet boards was to be a "gateway".
>
>... So my job is to try to keep the machines on the network together
>but isolate certain services from each other.  Especially registry
>services.

You can do this by partitioning the internet into two
Location Broker "cells", one containing the EGR hosts and
one containing the CHM hosts.  LB cells have disjoint GLB
databases, and since hosts locate registry servers via LB
lookup, LB cells also have disjoint registry databases.
In each cell, at least one host must run glbd and at least
one host must run rgyd.  At your site, it should suffice
to have one EGR host running both glbd and rgyd and one CHM
host running both glbd and rgyd.  Hosts in the EGR cell will
use only the EGR glbd and locate only the EGR rgyd, whereas
hosts in the CHM cell will use only the CHM glbd and locate
only the CHM rgyd.

In a network or internet that is partitioned into cells,
each cell uses a different GLB object identifier.  There is
a default GLB object id; at your site, presumably, every host
is currently using this default, so the entire internet is one
cell.  The default GLB object id can be overridden for any host
by an /etc/ncs/glb_obj.txt file containing an alternate GLB
object id; at your site, run /etc/ncs/uuid_gen once to generate
a glb_obj.txt file on one of the EGR hosts, then copy this file
to the other EGR hosts.  Hosts without a glb_obj.txt file use
the default GLB object id; at your site, the CHM hosts do not
need glb_obj.txt files.

Cell configurations are determined by the presence and
contents of glb_obj.txt files.  Cells need not correspond
in any way to physical or logical network topology.

Support for cells was introduced at SR10.2, I think, so
hosts in the "alternate" cell must be at SR10.2 or a later
release.

For details, see sections 4.6 and 5.3 of Managing NCS Software.
Once you've set up the LB cells, create a new registry in the
"alternate" cell.

Mike Kong
mk@apollo.hp.com