-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In working on the API for block reservations (VCL-78), I've realized there needs to be an owner for any block reservations created via the API. Additionally, when the backend uses the API to process an existing block reservation, it will need to use some userid to authenticate. Should we create a new user for such tasks in addition to the vclreload user? Should we rename the vclreload user? Should we just keep using the vclreload user for any system based tasks and just keep the name even though it doesn't reflect the use?
My thoughts: I don't really see why we need more than one system account. I think having an account named vclreload that is used for several other things could be confusing. I think it would be kind of difficult to rename the account since it'd have to be changed everywhere at the same time to keep things from breaking. So, that leaves me not really liking any of the options. What are others' thoughts? - -- - ------------------------------- Josh Thompson Systems Programmer Virtual Computing Lab (VCL) North Carolina State University josh_thomp...@ncsu.edu 919-515-5323 my GPG/PGP key can be found at pgp.mit.edu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJrEfMV/LQcNdtPQMRAuNTAJsGubBW3L83d1yGcR5SOi4+TgWwawCfXci+ LXGTRADwwhMFjA036aobP8U= =0Nz3 -----END PGP SIGNATURE-----
