Surgient Success

As part of our QA test and release process, we've added a step where an ISO image of our product is added to the Surgient library so that we can attach it to a session (say a baseline OS application configuration) for installation testing. We've identified a directory on our library file server for this purpose and transfer the files via NFS. When I log onto the VAP as "admin" I can see the new ISO via the "Images" link.

If I log onto my tester account, however, I cannot access the ISO via the "Attach Media" link, unless I (as admin) first change permissions to permit the group to which I am a member "user" rights, or change the organization ownership from "Internal" to the my tester organization (R&D) or to the R&D parent organization (QAD) which also provides visibility to all the children organizations (R&D, Support, Services, etc.) and is actually preferred.

I can do this easily enough through the VAP GUI, but is there a vcsadmin (or other) command that will do the equivalent? Again, as admin, I can see the file using the vcsadmin command "filelist" or "libraryfilelist" but I cannot see anything to change the organization or permissions. I would like to implement a command line solution that can be applied as part of the test and release process so that it does not require human intervention (me) each time a new ISO image is released.

Hi Lou -

I am not sure if this is documented anywhere, but Surgient ships with an event module that can do what you are asking for a specific organization.  Under your templates directory, create a new subdirectory that is the exact name of the Organization that you wish to automatically have permissions to a file.  Then, do the following in vcsadmin:

eventmoduleadd FilePermissionModule -auto true "Automatically assigns permissions to new files" EventDispatcher Surgient.EventDispatcher.FilePermissionEventModule ExtensionFilter=iso

eventmodulestart FilePermissionModule

where ExtensionFilter=iso is really a semicolon (;) delimitated list of extensions that, when present in that folder, will be acknowledged by the library agent and automatically be visible to Administrators of your organization.  For example, if you wish the organization to see both VMDKs and ISOs, you could do:

ExtensionFilter=iso;vmdk

Unfortunately, I believe the limitation is that you can only set this up on a per organization/file basis. I have, however, put in a Feature Request to get an API that could help you out in the future so that you could write something to do it for multiple organizations yourself and a Feature Request to get the FilePermissionModule extended to support multiple organizations from a single directory.  I think these would be useful things to have.

Jackie.

Jackie, with the exception of a slight syntax change of the vcsadmin command, it worked perfectly! By setting up the directory with the parent organization name (QAD), not only could the QAD users see the iso's but the children organizations to QAD (R&D, Support, Services, IT) could also see them, which is precisely what we were looking for.

The option (-auto true) needed to come before the name (FilePermissionModule). I received an "index out of bound" with the command in the form given. I also realized that I needed to start the eventmodule (duh!) before items actually started appearing in the "Attach Media" pulldown.

Thank you! Goal achieved!