[Swift-devel] Rename versions of Globus commands in swift/bin?

[Mihael Hategan]

On Wed, 2009-02-11 at 22:37 -0600, Michael Wilde wrote:
> These are cog-based versions of the commands.
> 
> The cool thing is that users get this core Globus functionality with no 
> compilation needed: just untar Swift, and poof, you can make proxies, 
> run jobs, move files (eg for setting this up on remote grid sites).

We rename them to cog-* then?

> 
> The issue I bumped into with proxies was cosmetic. The proxies are 
> totally compatible as far as I know.

Yes.

>   I just happened to have a 
> front-end script for running swift code that checked to make sure the 
> user has a valid proxy with some time left. And the time format returned 
> by the swift grid-proxy-info was slightly different than the Globus one.
> 
> That broke my brittle little script - its not a criticism of the cog 
> code version.

Though that may be possible to fix. url-copy not so much.

> 
> But its easy enough for us to refer, in swift docs, to swift-proxy-init, 
> swift-proxy-info with a * explaining that the Globus versions of these 
> are fine if you happen to have them.

Or the other way around. We use globus-* by default and then say that
the user could use the other ones.

> 
> - Mike
> 
> 
> On 2/11/09 10:31 PM, Ian Foster wrote:
> > Mike:
> > 
> > This begs the question for me as to why they are different. Are Swift 
> > proxies different from Globus proxies, for example? And if so, why?
> > 
> > Ian.
> > 
> > 
> > On Feb 11, 2009, at 10:29 PM, Michael Wilde wrote:
> > 
> >> Matt raises a good point below. Can we rename globus-url-copy, 
> >> grid-proxy-init, and other commands that have the same name as Globus 
> >> commands, to swift-url-copy, swift-proxy-init, etc?
> >>
> >> Especially for those that are not identical enough to the Globus 
> >> versions (where that is tbd).
> >>
> >> Its extremely handy to have these commands there, but perhaps 
> >> confusing for some users that get these in their paths ahead of the 
> >> Globus versions. I realize calling them swift-* causes its own kind of 
> >> confusion, but I'm excited that folks like Mats are installing Swift 
> >> for users, and I'd like to remove any barriers, even the small ones.
> >>
> >> This is likely to be a bigger issue for users with the OSG client 
> >> stack installed.
> >>
> >> On 2/11/09 10:18 PM, Michael Wilde wrote:
> >>> On 2/11/09 9:28 PM, Mats Rynge wrote:
> >>
> >> ...
> >>>>
> >>>> Regarding bin/, it is pretty evil to have a globus-url-copy under the
> >>>> swift bin/ which has a different set of command line options as the
> >>>> Globus one. I had a plan on adding swift to the default path on our
> >>>> submit node so all our users could use swift without doing anything
> >>>> special. But having a different globus-url-copy means it would break
> >>>> things for other users.
> >>> I know what you mean. I actually got bit the other day by our copy of 
> >>> grid-proxy-init - I was seeing the globus one, and one of my users 
> >>> was seeing the swift one, with a slightly different output that broke 
> >>> a script.
> >>> So I agree - if the swift version is not pretty near identical, its 
> >>> better to give it another name. I'll past your comment to the devel 
> >>> list with a suggestion that we rename it. Perhaps swift-proxy-init, 
> >>> swift-url-copy? (not sure how that will go over... ;)
> >>> - Mike
> >>
> >> Mats, I would just go ahead and remove or rename those, in the meantime.
> >>
> >> I dont think anything points to them.
> >>
> >> - Mike
> >>
> >> _______________________________________________
> >> Swift-devel mailing list
> >> Swift-devel at ci.uchicago.edu
> >> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel