IBM Content Manager OnDemand for i

Transcription

1 IBM Content Manager OnDemand for i Network File System Support April 8, 2014

2 Using a Network File System with Content Manager OnDemand for i OnDemand for i Common Server can now mount a Network File System (NFS) exported directory as a disk pool. This document applies to OnDemand v5.4 and v6.1. Beginning at OnDemand v7.1, refer to the OnDemand information center or publications for information regarding the use of NFS. Overview of NFS NFS is an acronym for Network File System, a product developed by Sun Microsystems. This is a distributed file system implementation providing remote, transparent access to files and directories. A few key points: You make a directory or an object available to NFS clients by exporting it. Therefore, you have very specific control over which parts of your system you will make available to NFS clients in your network. When you export, you can specify which clients have access to the objects. You identify a client by system name or IP address. You make a directory or an object available on your NFS client by mounting it. When you mount remote server file systems over local client directories, you allow System i servers to work with file systems that have been exported from a remote server. The mounted file systems will act and perform as if they exist on the local server. The NFS does not provide password protection. It is designed and intended for data sharing within a trusted community of systems. When a user requests access, the server receives the user s User ID number (UID). The UID is used to determine the permissions of the user. The use of synchronous writes is recommended. The use of asynchronous writes can result in data loss in the event of a system failure on either the archive or storage system. Each NFS mount (across all instances and logical partitions (LPARs)) must use a unique NFS directory. The IBM i Save (SAV) and Restore (RST) commands do not support data in an NFS mount. You must perform save and restore operations on the NFS system itself, using its commands. More information on NFS can be found within the IBM i information centers at: Overview of OnDemand Support for NFS Software prerequisites The following software prerequisites are required for OnDemand NFS support: Updated April 8, 2014 Page 2 of 10

3 OnDemand PTFs applied. The required OnDemand PTF for v5.4 is SI28328 (or its superseding PTF). NFS support is included in the general availability code beginning at v6.1. Limitations The following limitations apply to OnDemand for i NFS support. NFS support does not apply to, nor support, OnDemand Spool File Archive. Directories located in an Independent ASP (IASP) can not be mounted over an NFS exported directory. This limitation will affect only customers at v6.1 who locate a complete instance, including library, within an IASP. Configuration A special program must be run to create the needed configuration entries within OnDemand. The program to call is QRLCASMNFS in library QRDARS. It has 4 required parameters: Parameter Values Notes Instance name Existing instance Pool number 2 through 32 If you use an existing pool number, its contents will not be accessible after the file system is mounted. We recommend that you use a pool number that is not in use by a physical ASP on your system. Pool Type P for primary B for backup NFS path hostname:path The directory specified by the path must already exist. Calling the QRLCASMNFS program will not create it for you. For example, to create: a primary disk pool for instance QUSROND with pool number 32 on host system RDR400S.RTP.RALEIGH.IBM.COM over path /NFSSTG/Z/QUSROND/PRIMARY use the following command: CALL PGM(QRDARS/QRLCASMNFS) PARM('QUSROND' '32' 'P' 'RDR400S.RTP.RALEIGH.IBM.COM:/NFSSTG/Z/QUSROND/PRIMARY') The following messages will be sent to your job log: Adding Disk Pool 32 Type P as 'RDR400S.RTP.RALEIGH.IBM.COM:/NFSSTG/Z/QUSROND/PRIMARY' Add was successful The first time you call the QRLCASMNFS program, new configuration entries are created. Subsequent calls to the program for the same configuration will update the existing configuration entry, which allows you to change an incorrect path, for example. Updated April 8, 2014 Page 3 of 10

4 Example Scenario In our example NFS scenario we will use two System i servers. One server is labeled the Archive System, where OnDemand for i Common Server is running and where the NFS directory is mounted. The other server is labeled the Storage System, where the NFS directory is exported, and where OnDemand stores objects. Archive System RDR400Z OnDemand for i Common Server is running here. NFS directory is mounted. Storage System RDR400S NFS directory is exported. OnDemand objects are stored here. System RDR400Z is running V6R1 of OnDemand for i. The instance name is QUSROND. System RDR400S is running V5R4 of i5/os. On the Storage System (RDR400S) We created a user profile with the same UID as the instance profile on the archive system. Objects created on the storage system will be owned by that user profile. On the archive system QUSROND has a UID of 588. Following is the command we used to create the companion user profile on the storage system. Note that we specified the same language parameters as used on the archive system. CRTUSRPRF USRPRF(ZQUSROND) USRCLS(*PGMR) INLPGM(*NONE) INLMNU(*SIGNOFF) LMTCPB(*NO) TEXT('ONDEMAND NFS MOUNT PROFILE') SPCAUT(*IOSYSCFG *JOBCTL *SAVSYS) GRPPRF(QRDARS400) LANGID(ENU) CNTRYID(US) CCSID(37) CHRIDCTL(*JOBCCSID) SETJOBATR(*CCSID *DATFMT *DATSEP *DECFMT *SRTSEQ *TIMSEP) LOCALE('/QSYS.LIB/EN_US.LOCALE') UID(588) If the needed UID is already in use, see the topic Special Consideration for UIDs for information on changing the UID of an existing user profile. We created the following directory tree for use with NFS. /PRIMARY /NFSSTG /Z /QUSROND /BACKUP To automatically export the file systems when the NFS server is started, update the /etc/exports file in IFS on the Storage System (which is RDR400S in our example). Updated April 8, 2014 Page 4 of 10

5 Contents of /etc/exports for our example scenario: /NFSSTG/Z/QUSROND/PRIMARY root=rdr400z.rtp.raleigh.ibm.com, \ access=rdr400z.rtp.raleigh.ibm.com, \ rw=rdr400z.rtp.raleigh.ibm.com \ #HOSTOPT HostName=RDR400Z.RTP.RALEIGH.IBM.COM, \ /NFSSTG/Z/QUSROND/BACKUP root=rdr400z.rtp.raleigh.ibm.com, \ access=rdr400z.rtp.raleigh.ibm.com, \ rw=rdr400z.rtp.raleigh.ibm.com \ #HOSTOPT HostName=RDR400Z.RTP.RALEIGH.IBM.COM, \ Start the NFS servers using System i Navigator or with this command: STRNFSSVR SERVER(*ALL) The joblog contains these messages: Notes Start of NFS server daemon or daemons of type *RPC was successful. Start of NFS server daemon or daemons of type *BIO was successful. 2 entries exported, 0 entries not exported. Start of NFS server daemon or daemons of type *SVR was successful. Start of NFS server daemon or daemons of type *MNT was successful. Start of NFS server daemon or daemons of type *NSM was successful. Start of NFS server daemon or daemons of type *NLM was successful. Start NFS server command completed successfully. 1. The user starting NFS servers must have input/output (I/O) system configuration (*IOSYSCFG) special authority to use this command. 2. The user starting NFS servers must be enrolled in the system distribution directory. Use the Add Directory Entry (ADDDIRE) command to enroll the user. To determine if an NFS server is running, use the Work with Active Jobs (WRKACTJOB) command and look in the subsystem QSYSWRK for existence of the following jobs: QNFSRPCD The RPCBind daemon QNFSBIOD The block I/O (BIO) daemon QNFSNFSD The NFS server (SVR) daemon QNFSMNTD The mount (MNT) daemon QNFSNSMD The network status monitor (NSM) daemon QNFSNLMD The network lock manager (NLM) daemon If necessary, you can manually export or unexport the directories. To export all entries in /etc/exports EXPORTFS OPTIONS('-A') To unexport all entries in /etc/exports EXPORTFS OPTIONS('-A -U') You can also use System i Navigator to export or unexport directories. Updated April 8, 2014 Page 5 of 10

6 On the Archive System (RDR400Z) Configure OnDemand to use the NFS disk pools. To create the primary disk pool, use the following command: CALL PGM(QRDARS/QRLCASMNFS) PARM('QUSROND' '32' 'P' 'RDR400S.RTP.RALEIGH.IBM.COM:/NFSSTG/Z/QUSROND/PRIMARY') To create the backup disk pool, use the following command: CALL PGM(QRDARS/QRLCASMNFS) PARM('QUSROND' '32' 'B' 'RDR400S.RTP.RALEIGH.IBM.COM:/NFSSTG/Z/QUSROND/BACKUP') Create or update a Common Server migration policy to use the NFS disk pools. Migration Policies must be created using System i Navigator. For more information on disk pools and migration policies, see the IBM Content Manager OnDemand for i Common Server Administration Guide. Normally the NFS mounts are done automatically, when required by Archive Storage Manager (ASM) to migrate or retrieve data. Message queue QSYSOPR will contain message CPCA1B0 when the NFS mount is performed by ASM. For example: File system /NFSSTG/Z/QUSROND/PRIMARY was successfully mounted over directory /QIBM/USERDATA/ONDEMAND/QUSROND/ASMASP32/PRIMARY. If you need to manually mount the NFS, use the MOUNT command. The mount must be done exactly as it was defined when you created your NFS disk pool. For example: MOUNT TYPE(*NFS) MFS('rdr400s.rtp.raleigh.ibm.com:/NFSSTG/Z/QUSROND/PRIMARY') MNTOVRDIR('/QIBM/UserData/OnDemand/QUSROND/ASMASP32/PRIMARY') File system mounted. If you need to manually unmount the NFS, use the UNMOUNT command, for example: UNMOUNT TYPE(*NFS) MNTOVRDIR('/QIBM/UserData/OnDemand/QUSROND/ASMASP32/PRIMARY') File system or directory unmounted. To verify that the NFS is mounted, use either of the STATFS or DSPMFSINF commands. STATFS OBJ('/QIBM/UserData/OnDemand/QUSROND/ASMASP32/PRIMARY') Output from the STATFS and DSPMFSINF commands will be similar to the following: Display Mounted FS Information Object : /QIBM/UserData/OnDemand/QUSROND/ASMASP32/PRIMARY File system type : Network File System (NFS) (If File system type : "root" (/) then the NFS is not mounted) Updated April 8, 2014 Page 6 of 10

7 ... Path of mounted file system. : rdr400s.rtp.raleigh.ibm.com:/nfsstg/z/qusrond/primary Path mounted over : /QIBM/UserData/OnDemand/QUSROND/ASMASP32/PRIMARY Protection : Read-write... Notes 1. The NFS servers do not need to be running on the archive system. Special Considerations for UIDs You might discover that you need to change UIDs, even for IBM-supplied user profiles, to have compatibility with other systems in your network. When you change the UID for a user profile, you also need to change the UID for all the objects that the profile owns in either the root directory or the QOpenSrv directory. An API is available to make it easier to change the UID for a user profile. The QSYCHGID API automatically changes the UID in both the user profile and all the owned objects. Source code examples for a sample program and sample command using the QSYCHGID API are shown below. (The source is provided as an example only. It may not completely satisfy your specific requirements.) For more information on the QSYCHGID API, search on "security-related APIs" within the IBM i Information Center. Sample CL source code /* DISCLAIMER OF WARRANTIES. The following code is sample code */ /* created by IBM Corporation. IBM grants you a nonexclusive */ /* copyright license to use this sample code example to generate */ /* similar function tailored to your own specific needs. This sample */ /* code is not part of any standard IBM product and is provided to */ /* you solely for the purpose of assisting you in the development of */ /* your applications. This example has not been thoroughly tested */ /* under all conditions. IBM, therefore cannot guarantee nor may you */ /* imply reliability, serviceability, or function of these programs. */ /* The code is provided "AS IS", without warranty of any kind. IBM */ /* shall not be liable for any damages arising out of your or any */ /* other parties use of the sample code, even if IBM has been advised */ /* of the possibility of such damages. If you do not agree with these */ /* terms, do not use the sample code. */ /* Licensed Materials - Property of IBM */ /* 5770RD1 */ /* Copyright IBM Corp. 2006, 2009 All Rights Reserved. */ /* US Government Users Restricted Rights - Use, duplication or */ /* disclosure restricted by GSA ADP Schedule Contract with IBM Corp. */ /* The source code for this program is not published or otherwise */ /* divested of its trade secrets, irrespective of what has been */ /* deposited with the U.S. Copyright Office. */ Updated April 8, 2014 Page 7 of 10

8 /* Program: Change the UID of a user profile */ /* Language: ILE CL */ /* Description: NFS support requires UIDs to match between systems */ /* Sometimes this requires changing the UID of an */ /* existing user profile. The CHGUSRPRF command can */ /* can not do this if the user owns IFS objects. */ /* The QSYCHGID API changes the UID of the user profile */ /* and the IFS objects it owns. */ /* Parameters: The three parameters passed are */ /* USRPRF - The user profile to be changed */ /* UID - The desired UID */ /* GID - The desired GID, normally -1 */ /* -1 = GID does not change */ /* IBM i APIs: QSYCHGID - Change User Profile UID or GID */ /* To create this program in library QGPL use the following command: */ /* CRTBNDCL PGM(QGPL/CHGUIDC) SRCFILE(QRDARS/QSAMPLES2) */ /* DFTACTGRP(*NO) ACTGRP(*CALLER) REPLACE(*YES) */ /* Use command CHGUID, shipped with this program */ /* CHGUID USER(DBRYANT) UID(975) */ PGM PARM(&USRPRF &UID &GID) /* Input parameter variables */ DCL VAR(&USRPRF) TYPE(*CHAR) LEN(10) DCL VAR(&UID) TYPE(*DEC) LEN(10 0) DCL VAR(&GID) TYPE(*DEC) LEN(10 0) DCL VAR(&UID_NUM) TYPE(*DEC) LEN(11 0) DCL VAR(&GID_NUM) TYPE(*DEC) LEN(11 0) /* Message variables */ DCL VAR(&MSGID) TYPE(*CHAR) LEN(7) DCL VAR(&MSGDTALN) TYPE(*DEC) LEN(9 0) DCL VAR(&MSGDTA) TYPE(*CHAR) LEN(80) DCL VAR(&NO_ERR) TYPE(*CHAR) LEN(4) + VALUE(X' ') /* Change User Profile (QSYCHGID) variables */ DCL VAR(&USR_NAME) TYPE(*CHAR) LEN(10) DCL VAR(&USR_UID) TYPE(*CHAR) LEN(4) + VALUE(X' ') DCL VAR(&USR_GID) TYPE(*CHAR) LEN(4) + VALUE(X'FFFFFFFF') /* Error code variable */ Updated April 8, 2014 Page 8 of 10

9 DCL VAR(&ERRCDE) TYPE(*CHAR) LEN(96) /* Change variables and call QSYCHGID */ CHGVAR VAR(&USR_NAME) VALUE(&USRPRF) CHGVAR VAR(&UID_NUM) VALUE(&UID) CHGVAR VAR(%BIN(&USR_UID)) VALUE(&UID_NUM) CHGVAR VAR(&GID_NUM) VALUE(&GID) CHGVAR VAR(%BIN(&USR_GID)) VALUE(&GID_NUM) CHGVAR VAR(%SST(&ERRCDE 1 8)) + VALUE(X' ') CALL PGM(QSYCHGID) PARM(&USR_NAME + &USR_UID &USR_GID &ERRCDE) IF COND(%SST(&ERRCDE 5 4) *NE &NO_ERR) + THEN(GOTO CMDLBL(ERROR_API)) /* Goto the end */ GOTO CMDLBL(ENDPGM) /* If an error occurs in the APIs */ ERROR_API: CHGVAR VAR(&MSGID) VALUE(%SST(&ERRCDE 9 7)) CHGVAR VAR(&MSGDTALN) VALUE(%BIN(&ERRCDE 5 4)) CHGVAR VAR(&MSGDTALN) VALUE(&MSGDTALN - 16) CHGVAR VAR(&MSGDTA) VALUE(%SST(&ERRCDE 17 &MSGDTALN)) SNDPGMMSG MSGID(&MSGID) MSGF(QCPFMSG) MSGDTA(&MSGDTA) + MSGTYPE(*DIAG) /* Send error message */ ERROR: SNDPGMMSG MSGID(CPF9899) MSGF(QCPFMSG) MSGTYPE(*ESCAPE) ENDPGM: ENDPGM Updated April 8, 2014 Page 9 of 10

10 Sample command source code /* DISCLAIMER OF WARRANTIES. The following code is sample code */ /* created by IBM Corporation. IBM grants you a nonexclusive */ /* copyright license to use this sample code example to generate */ /* similar function tailored to your own specific needs. This sample */ /* code is not part of any standard IBM product and is provided to */ /* you solely for the purpose of assisting you in the development of */ /* your applications. This example has not been thoroughly tested */ /* under all conditions. IBM, therefore cannot guarantee nor may you */ /* imply reliability, serviceability, or function of these programs. */ /* The code is provided "AS IS", without warranty of any kind. IBM */ /* shall not be liable for any damages arising out of your or any */ /* other parties use of the sample code, even if IBM has been advised */ /* of the possibility of such damages. If you do not agree with these */ /* terms, do not use the sample code. */ /* Licensed Materials - Property of IBM */ /* 5770RD1 */ /* Copyright IBM Corp. 2006, 2009 All Rights Reserved. */ /* US Government Users Restricted Rights - Use, duplication or */ /* disclosure restricted by GSA ADP Schedule Contract with IBM Corp. */ /* The source code for this program is not published or otherwise */ /* divested of its trade secrets, irrespective of what has been */ /* deposited with the U.S. Copyright Office. */ /* To create this command in library QGPL use the following command: */ /* CRTCMD CMD(QGPL/CHGUID) PGM(QGPL/CHGUIDC) */ /* SRCFILE(QRDARS/QSAMPLES2) */ /* To use this command: */ /* CHGUID USER(DBRYANT) UID(975) */ CMD PROMPT('CHANGE UID & GID') PARM KWD(USER) TYPE(*CHAR) LEN(10) MIN(1) + EXPR(*YES) PROMPT('User profile') PARM KWD(UID) TYPE(*DEC) LEN(10 0) DFT(*SAME) + RANGE( ) SPCVAL((*SAME -1)) + MIN(0) EXPR(*YES) PROMPT('New UID') PARM KWD(GID) TYPE(*DEC) LEN(10 0) DFT(*SAME) + RANGE( ) SPCVAL((*SAME -1)) + MIN(0) EXPR(*YES) PROMPT('New GID') Creating the sample CL program and command Use the sample commands in the source file comments to create (compile) the CHGUID CL program and command. Updated April 8, 2014 Page 10 of 10