Number 2 of N.

This one only goes explicitly to the internal folks, though there's 
nothing sensitive in it, and it will still be archived externally.

--Mark



-------------------- cut here --------------------
To: on-all at sun.com, onnv-gate at onnv.eng.sun.com
Subject: Flag day: Mercurial: What to expect: nis maps and access paths

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/elpaso.sfbay.sun.com/export/onnv-gate
        /net/elpaso.sfbay.sun.com/export/onnv-gate
        ssh://elpaso.sfbay.sun.com//export/onnv-gate
        ssh://elpaso.sfbay.sun.com//export/onnv-gate/usr/closed

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

        Note: 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/elpaso.sfbay.sun.com/export/onnv-tw-gate
        /net/elpaso.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.

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