Nothing interesting here for folks off of SWAN.  The onnv-gate repository 
on hg.opensolaris.org will not be changing or moving.



Tuesday, August 5 is a flag day for anyone accessing the internal ON 
Nevada workspaces, including gate and clone, open and closed, and Teamware 
and Mercurial, via any access method (nfs via /ws, nfs via /net, ssh):

The access paths for all such workspaces are changing on the morning (PDT) 
of Tuesday, August 5, as follows:

- The Mercurial gate and clone:

        /ws/onnv-gate
        /net/onnv.sfbay.sun.com/export/onnv-gate
        /net/onnv.sfbay.sun.com/export/onnv-gate/usr/closed
        ssh://onnv.sfbay.sun.com//export/onnv-gate
        ssh://onnv.sfbay.sun.com//export/onnv-gate/usr/closed

        /ws/onnv-clone
        /net/onnv.sfbay.sun.com/export/onnv-clone
        /net/onnv.sfbay.sun.com/export/onnv-clone/usr/closed
        ssh://onnv.sfbay.sun.com//export/onnv-clone
        ssh://onnv.sfbay.sun.com//export/onnv-clone/usr/closed

        Note: the second "//" in the ssh paths is note a typo.  That's how
        you tell ssh that you're accessing an absolute path on the target
        machine, rather than a home-directory-relative one.

        Note: all nfs gate and clone filesystems will be read-only.

        Note: gate and clone organization and policies will also change.
        That change will be described in a separate note.

        Note: ssh access will change for push vs pull from these
        repositories.  That change will be described in a separate note.

- The Teamware gate and clone, for archival and workspace conversion:

        /net/onnv.sfbay.sun.com/export/onnv-tw-gate
        /net/onnv.sfbay.sun.com/export/onnv-tw-clone

        Note: Codemgr_wsdata dirs will continue to be read-write via nfs,
        everything else will be read-only.

        Note: The onnv-tw-clone workspace will continue to be a valid
        parent for use with wx2hg, though it will no longer point to the
        active, Mercurial clone as its twin repository.

The propagation of some of these changes is outside of our control.  Most 
notably, the auto_ws nis map changes may need to be duplicated in other 
domains.  If you find, after Tuesday, that your ITOps managed nis maps are 
not up-to-date, please submit a service desk ticket under "Request a 
Service->Desktop Systems->HOST/NIS Entry Change," and refer to ticket 
5831684 [1].  The new maps should be:

        onnv-gate                                                       \
                /               onnv.sfbay:/export/onnv-gate            \
                /archives       onnv.sfbay:/export/archives             \
                /packages       onnv.sfbay:/export/packages             \
                /public         onnv.sfbay:/export/onnv-gate/public     \
                /proto          onnv.sfbay:/export/onnv-gate/proto

        onnv-clone                                                      \
                /               onnv.sfbay:/export/onnv-clone

Questions to gatekeeper at onnv.eng.sun.com.

--Mark

[1] http://sdesk.central:80/servlet/qmViewPrint?reqId=5831684

Reply via email to