Open sina-masoud-ansari opened 13 years ago
Also may want 'Default directory' where folders like 'active-jobs' are stored.
"about" is just printing versions, support email, etc. only permanent stuff. archive location should probably be global.
agreed
@smas036, what do you mean with "Default directory"? active-jobs is a virtual folder, there is no one directory that can be accessed to get there. Jobs run all over NZ... Archive location is not so easy also, Jobs can be archived to different archive locations. There is a "default" one though, if the user doesn't specifies it explicitely (which is what happens when archiving a job via gricli). In what form should the archive location be displayed? grid://groups/nz/nesi grid://jobs/archived gsiftp://df.auckland.ac.nz:2811/home/markus.binsteiner ? Those all point to the same location (except grid://jobs/archived which is virtual and merges all archive locations)
I think grid://jobs/archived is easiest to remember and makes a lot of sense.
Not sure what I was suggesting with 'Default directory'. Probably looking at it from a documentation point of view, so that i could say 'look in your active-jobs dir, the location of which is defined in the about command' as it may be different between implementations of the Gricli?
Hm, not sure, really. One could also access an archived jobs via the datafabric, then grid://jobs/archived doesn't make sense.
True, perhaps another one to ask users.
News on this one?
Not yet unfortunately
Ok, moving this to next milestone then...
What about:
Archive location: grid://jobs/archived Archive web-link: http://df.auckland.ac.nz/BeSTGRID/home/sina.masoud-ansari/archived-jobs
"about" is more of a debugging tool. On the other hand, we could provide read-only global for web link.
On 19/01/12 18:32, Sina Masoud-Ansari wrote:
What about:
Archive location: grid://jobs/archived Archive web-link: http://df.auckland.ac.nz/BeSTGRID/home/sina.masoud-ansari/archived-jobs
Reply to this email directly or view it on GitHub: https://github.com/grisu/gricli/issues/112#issuecomment-3558249
Yeah I think we are going to re think how we approach docs, because the independent and NeSI docs need to be approached in a maintainable way, this may be something we introduce in user tutorials and not in the independent docs. Just mentioning that it is possible may be enough, people should be expected to have a look at their institution docs regarding the finer details ... ?
@mondkaefer
This will help clarify the distinction between Gricli the tool and Gricli the NeSI submission CLI. I can refer to this in the help and Gricli wiki and mention the the Data Fabric in NeSI / BeSTGRID user docs.