Replace gums-host-cron uses in osg-configure with calls to JSON interface
In we added JSON interfaces to GUMS to provide an alternative to using gums-host-cron from the gums-client package.
We want to replace the use of gums-host-cron in osg-configure to remove the need for pulling in gums-client, particularly on EL7. (See also SOFTWARE-2415.)
In particular, the task is to replace the get_vos function in osg-configure, which will use the new python client code/module (from SOFTWARE-2380) that calls the JSON interface. That didn't make it into osg-configure for due to some unresolved questions; see this comment.
Sure, we can do that. The script is in the osg-vo-map package, which is separate from gums-client. We'll add that package as a dependency to osg-configure-misc and add code to osg-configure to call it.
so does that mean we should call check-vo-map in osg-configure when using the gums json interface?
, can you attempt to run check-vo-map against the user-vo-map you generated with the json interface, and see how the results compare to the one you generated with gums-host-cron ?
Yup. Aside from a final newline, running check-vo-map on the user-vo-map created by the gums json interface generates a vo map identical to the one gums-host-cron spits out.
Promoted osg-configure-1.9.0-1 to osg-3.3-el*-prerelease
Promoted osg-configure-2.1.0-2 to osg-3.4-el*-prerelease
Verified that removing the gums-host-cron and the user-vo-map file and then running osg-configure results in the user-vo-map file being created.--