Acme-Globus
view release on metacpan or search on metacpan
rather than covering all the capabilities of the Globus CLI. It istherefore very stubtastic.This module also relies very much on SSH, and thus the rules of privateand publickeys. Therefore, using it as a shared tool would beill-advisedifnot impossible.SYNOPSISmy$g= Globus->new($username,$path_to_ssh_key) ;$g->endpoint_add_shared('institution#endpoint',$directory,$endpoint_name) ;$g->acl_add($endpoint.'/','djacoby@example.com') ;METHODSBASICSnewCreates a new Globus object. Takes two options:
deletermCurrently stubsscptransferBoth commands take a source, or from path (including endpoint), adestination, or to path (includint endpoint), and a boolean indicatingwhether you're copying recursively or not.FILE MANAGEMENTlsWorks?rename
acl_addacl_listacl_removeacl-* is the way that Globus refers to permissionsBy the interface, Globus supports adding shares by email address, byGlobus username or by Globus group name. This module sticks to usingemail address. acl_add() takes an endpoint, an email address you'resharing to, and a boolean indicating whether this share isread-only orread-write. acl_add() returns a share id.acl_remove() uses that share id to identify which shares are to beremoved.acl_list() returns an array of hashes containing the information abouteachuserwithaccess to an endpoint, including the share ID andpermissions.endpoint_add_sharedendpoint_listendpoint_searchendpoint_removeendpoint_add_shared() handles the specific case of creating an endpointfrom an existing endpoint, not the general case. It takes the endpointwhere you're sharing from, the path you're sharing, and the endpointyou're creating. If you are user 'user' and creating the endpoint'test', the command takes'test', not'user#test'.endpoint_remove and endpoint_list, however, take a full endpoint name,like'user#test'.Current usage is endpoint_listfora list of allourshares, andendpoint_searchfordetails ofeachindividual sharelist_my_endpointssearch_my_endpointslist_my_endpoints() and search_my_endpoints() were added once Idiscovered the failings of existing list and search. These toolsreturna hashref of hashrefs holding the owner, host_endpoint,host_endpoint_name, credential_status, and most importantly, the id,legacy_name and display_name.For older shares, legacy_name will be something like'purduegcore#hr00001_firstshare'and display_name will be'n/a',whilefornewer shares, legacy_name will be'purduegcore#SAME_AS_ID'anddisplay_name will be like older shares' legacy_name,'purduegcore#hr99999_filled_the_space'. In both cases, the value youUUID.endpoint_activateendpoint_addendpoint_deactivateendpoint_modifyendpoint_renameStubsOTHERhelphistoryman
lib/Acme/Globus.pm view on Meta::CPAN
rather than covering all the capabilities of the Globus CLI. It istherefore very stubtastic.This module also relies very much on SSH, and thus the rules ofprivate and publickeys. Therefore, using it as a shared tool wouldbe ill-advisedifnot impossible.=head1 SYNOPSISmy $g = Globus->new($username,$path_to_ssh_key) ;$g->endpoint_add_shared( 'institution#endpoint', $directory, $endpoint_name ) ;$g->acl_add( $endpoint . '/', 'djacoby@example.com' ) ;=head1 METHODS=head2 BASICS=head3 B<new>Creates a new Globus object. Takes two options:the username and path to the SSH key you use to connect to Globus.
lib/Acme/Globus.pm view on Meta::CPAN
=head3 B<delete>=head3 B<rm>Currently stubs=head3 B<scp>=head3 B<transfer>Both commands take a source, or from path (including endpoint),a destination, or to path (includint endpoint), and a boolean indicatingwhether you're copying recursively or not.=cutsubdelete{ }subrm { }subscp {my($self,$from_path,$to_path,$recurse) =@_;$recurse=$recurse?'-r':'';
lib/Acme/Globus.pm view on Meta::CPAN
=head3 B<acl_add>=head3 B<acl_list>=head3 B<acl_remove>acl-* is the way that Globus refers to permissionsBy the interface, Globus supports adding shares by email address,by Globus username or by Globus group name. This module sticks tousing email address. acl_add() takes an endpoint, an email addressyou're sharing to, and a boolean indicating whether this share isread-only or read-write. acl_add() returns a share id.acl_remove() uses that share id to identify which shares are to beremoved.acl_list() returns an array of hashes containing the information abouteach user with access to an endpoint, including the share ID and permissions.=cutsubidentity_details {my($self,$identity_id) =@_;my$command=qq{identity-details $identity_id };my$result= _globus_action($command,$self->{username},$self->{key_path} ) ;return{}unless$result=~ m{\w} ;my$obj= decode_json$result;returnwantarray?%$obj:$obj;}subacl_add {my($self,$endpoint,,$rw) =@_;my$readwrite='rw';$readwrite='r'unless$rw;my$command=qq{acl-add $endpoint --identityusername=${email}--perm$readwrite};my$result= _globus_action($command,$self->{username},$self->{key_path} ) ;my($id) =reversegrep{m{\w}}splitm{\s},$result;return$id;}subacl_list {my($self,$endpoint) =@_;my$command=qq{acl-list $endpoint};my$result= _globus_action($command,$self->{username},$self->{key_path} ) ;my$slist= decode_json$result;my@list=grep{$_->{permissions} ne'rw'}@$slist;returnwantarray?@list: \@list;}subacl_remove {my($self,$endpoint_uuid,$share_uuid) =@_;my$command=qq{acl-remove $endpoint_uuid --id $share_uuid};my$result= _globus_action($command,$self->{username},$self->{key_path} ) ;return$result;}=head3 B<endpoint_add_shared>=head3 B<endpoint_list>=head3 B<endpoint_search>=head3 B<endpoint_remove>endpoint_add_shared() handles the specific case of creating an endpointfrom an existing endpoint, not the general case. It takes the endpointwhere you're sharing from, the path you're sharing, and the endpointyou're creating. If you are user 'user' and creating the endpoint 'test',the command takes 'test', not 'user#test'.endpoint_remove and endpoint_list, however, take a full endpoint name, like 'user#test'.Current usage is endpoint_list for a list of all our shares, and endpoint_searchfor details of each individual share=head3 B<list_my_endpoints>=head3 B<search_my_endpoints>list_my_endpoints() and search_my_endpoints() were added once I discoveredthe failings of existing list and search. These tools return a hashrefof hashrefs holding the owner, host_endpoint, host_endpoint_name,credential_status, and most importantly, the id, legacy_name and display_name.For older shares, legacy_name will be something like 'purduegcore#hr00001_firstshare'and display_name will be 'n/a', while for newer shares, legacy_name will be'purduegcore#SAME_AS_ID' and display_name will be like older shares' legacy_name,'purduegcore#hr99999_filled_the_space'. In both cases, the value you wantto use to get details or to remove a share is the id, which is a UUID.=cutsubendpoint_add_shared {my($self,$sharer_endpoint,$path,$endpoint) =@_;# my $command# = qq{endpoint-add --sharing "$sharer_endpoint$path" $endpoint } ;# my $command# = qq{endpoint-add -n $endpoint --sharing "$sharer_endpoint$path" } ;my$command=join' ',q{endpoint-add},q{--sharing},"$sharer_endpoint$path",q{-n},$endpoint,;my$result= _globus_action($command,$self->{username},$self->{key_path} ) ;return$result;}# sub endpoint_list {# my ( $self, $endpoint ) = @_ ;# my $command ;# if ($endpoint) {# $command = qq{endpoint-list $endpoint } ;# }# else {# $command = qq{endpoint-list} ;# }# my $result# = _globus_action( $command, $self->{username}, $self->{key_path} ) ;# my @result = map { ( split m{\s}, $_ )[0] } split "\n", $result ;# return wantarray ? @result : \@result ;# }#lists all my endpointsubendpoint_list {my($self) =@_;my$command='endpoint-search --scope=my-endpoints';my$result= _globus_action($command,$self->{username},$self->{key_path} ) ;my@result=map{ s{\s}{}g ;$_}map{ (reversesplitm{:} )[0] }grep{m{Legacy}}splitm{\n},$result;returnwantarray?@result: \@result;}subendpoint_search {my($self,$search) =@_;return{}unless$search;my$command=qq{endpoint-search $search --scope=my-endpoints};my$result= _globus_action($command,$self->{username},$self->{key_path} ) ;my%result=map{chomp;my($k,$v) =splitm{\s*:\s},$_;$k=>$v}splitm{\n},$result;returnwantarray?%result: \%result;}sublist_my_endpoints {my($self) =@_;my$command='endpoint-search --scope=my-endpoints';my$result= _globus_action($command,$self->{username},$self->{key_path} ) ;my%result=map{my$hash;%$hash=map{my($k,$v) =splitm{\s*:\s*} ;$k=~ s{\s+}{_}gmx ;$k=lc$k;$k=>$v}
lib/Acme/Globus.pm view on Meta::CPAN
my$id=$hash->{display_name} ne'n/a'?$hash->{display_name}:$hash->{legacy_name} ;$id=>$hash;}splitm{\n\n},$result;returnwantarray?%result: \%result;}subsearch_my_endpoints {my($self,$search) =@_;my%result;my$command=qq{endpoint-search $search --scope=my-endpoints};my$result= _globus_action($command,$self->{username},$self->{key_path} ) ;%result=map{my$hash;%$hash=map{my($k,$v) =splitm{\s*:\s*} ;$k=~ s{\s+}{_}gmx ;$k=lc$k;$k=>$v}
lib/Acme/Globus.pm view on Meta::CPAN
my$id=$hash->{display_name} ne'n/a'?$hash->{display_name}:$hash->{legacy_name} ;$id=>$hash;}splitm{\n\n},$result;returnwantarray?%result: \%result;}subendpoint_remove {my($self,$endpoint) =@_;my$command=qq{endpoint-remove $endpoint};my$result= _globus_action($command,$self->{username},$self->{key_path} ) ;return$result;}# Sucks. Use endpoint_search insteadsubendpoint_details {my($self,$endpoint) =@_;my$command=qq{endpoint-details $endpoint};my$result= _globus_action($command,$self->{username},$self->{key_path} ) ;my%result=map{chomp;my($key,$value) =splitm{\s*:\s*},$_;$key=>$value}splitm{\n},$result;returnwantarray?%result: \%result;}=head3 B<endpoint_activate>=head3 B<endpoint_add>=head3 B<endpoint_deactivate>=head3 B<endpoint_modify>=head3 B<endpoint_rename>Stubs=cutsubendpoint_activate { }subendpoint_add { }subendpoint_deactivate { }subendpoint_modify { }subendpoint_rename { }=head2 OTHER=head3 B<help>=head3 B<history>=head3 B<man>=head3 B<profile>
( run in 0.618 second using v1.01-cache-2.11-cpan-49f99fa48dc )