virgoStaging Status F.Carbognani, S. Cortese, E. Pacaud

virgoStaging Status Summary of what we want: New development workflow: developers work on their home directory, update CVS and then install in /virgoStaging for integration testing Any Virgo user (possibly restricted into a group) should be able to install a version of a “Cmtized” package from CVS in /virgoStaging the Virgo user is not able to modify anything in the /virgoStaging area except than via a set of dedicated scripts

virgoStaging Status Dedicated scripts first developed based on ssh and the authorized keys certificate mechanism. This solution poses security issues and a problem of key management, for example the need to distribute the private key itself to all the users ( and redistribute it when changing the password or when adding new users) Explored then the use of sudo which seems satisfactory. In particular sudo configuration allows the use of centralized groups, therefore changing the roles would be simply matter of moving users through a NIS (or future IDM system) group

virgoStaging Status All embedded into the PackageManagement package providing 2 scripts: PmInstall and PmShow. PmInstall is for the installation of a set of packages in /virgoStaging PmShow shows the status of a package. A new dedicated user (pm_user) has been created, with: the appropriate file access permission (it should be read only for all other users, PROBABLY NOT YET TRUE) access to the CVS repository (for source checkout) The CMTPATH of this user is set to /virgoApp:/virgoStaging.

virgoStaging Status Sudo implementation specificities: sudo allow only the execution of absolute path executables so we set symbolic links in /virgoDev/PackageManagement (to become /virgoApp/PackageManagement). Those symbolic links will points to the latest production versions of those executables installed in the same directory, ex: /virgoDev/PackageManagement/PmInstall -> /virgoDev/PackageManagement/v1r0/scripts/PmInstall Those links will need to be updated at every PackageManagement upgrade In order to get the right environment variables setup (the Virgo environment + pm_user setting) there is the need to use the sudo -i option which imply that the called script must be a csh one (this because the full Virgo Environment is not yet available on bash, it will be, one day...). Porting of PackageManagement scripts from sh to csh is ongoing

virgoStaging Status Sudo implementation specificities: sudo must be used at the top level calling the shell wrapper scripts. Two alias have been introduced into the Virgo Environment: PmInstall (sudo -i -u pm_user /virgoDev/PackageManagement/PmInstall) PmShow (sudo -i -u pm_user /virgoDev/PackageManagement/PmShow) With this setup things seems working nicely and a standard user can login into farmn1 and issue directly commands like: PmInstall GWOLLUM v0r2p0 Emmanuel currently working and doing tests on its side. As soon as ready, a beta-testing phase can start with other users

virgoStaging further developments For the moment compilation on different platforms must be done by the user. It should be possible to improve the PmInstall script in order to take a list of hosts, allowing to automatically compile on a set of machines with one command.