Ensuring access to VOB and view storage on Solaris 10 branded zones
Access to VOBs and dynamic views in a Solaris 10 branded zone imposes some restrictions
on storage locations of the VOBs and views. These restrictions do not apply to Solaris
11.
Creating accessible storage locations on Solaris 10 branded zones
Solaris 10 does not support NFS servers in non-global zones. Therefore, VOB and dynamic view
storage on a Solaris 10 branded zone is accessible only within that zone. If VOB and view storage
must be accessible across zones, create the storage in any of the following locations:
- The global zone of the computer that must access the VOBs and views
- A network-attached storage (NAS) device
- A remote computer that acts as the VOB or view server. (If that computer is configured with non-global zones, the VOB or view storage must be in the global zone or on a NAS device.)
If you create a local VOB or view within a Solaris 10 branded zone where a non-local registry server is specified, the view or VOB can appear to be accessible from other clients of that registry server. However, due to the NFS server restriction, the VOB or view storage is in fact inaccessible. As a result, users cannot work with that view or VOB. For example, a user cannot remove the view with the cleartool rmview command from another host that is registered on the same server.
For details about configuring VOB and view storage, see Administering DevOps Code ClearCase®.