Globus Research Data Management: Endpoint Configuration and Deployment. Steve Tuecke Vas Vasiliadis

Transcription

1 Globus Research Data Management: Endpoint Configuration and Deployment Steve Tuecke Vas Vasiliadis

2 Presentations and other useful information available at globusworld.org/tutorial 2

3 Agenda Globus Connect Server overview Demonstration and exercise 4: Installing Globus Connect Server Exercise 5: Configuring Globus Connect Server Common Globus Connect Server configurations Advanced endpoint configuration Deployment best practice: Science DMZ Wrap-up and general Q&A 3

4 Globus Connect Server Overview 4

5 Globus Connect Server Globus Connect Server MyProxy CA OAuth Server GridFTP Server Local Storage System (HPC cluster, campus server, ) Local system users Create endpoint in minutes; no complex software install Enable all users with local accounts to transfer files Native packages: RPMs and DEBs 5

6 6

7 What we are going to do: Server (AWS EC2) ssh 1 Install Globus Connect Server Access server as: rccadmin/gw2015 Update repo Install package Setup Globus Connect Server 2 Log into Globus (using Globus username) Test Endpoint 3 4 Access the newly created endpoint (as user researcher ) Transfer a file 7

8 Globus Connect Server Demonstration 8

9 Exercise 4: Set up a Globus Connect Server endpoint and transfer files Goal for this session: turn a storage resource into a Globus endpoint Each of you is provided with an Amazon EC2 server for this tutorial Step 1: Create a Globus account (if you do not have one already) 9

10 Step 2: Log into your host Your slip of paper has the host information Log in as user rccadmin : Ssh rccadmin@ec2-x-x-x-x.compute-1.amazonaws.com The password is gw2015 NB: Please sudo su before continuing User rccadmin has passwordless sudo privileges 10

11 Step 3: Install Globus Connect Server Cheat sheet : globusworld.org/tutorial $ sudo su $ curl LOs $ dpkg i globus-connect-server-repo_latest_all.deb $ apt-get update $ apt-get -y install globus-connect-server $ globus-connect-server-setup Use your Globus username/password here You have a working Globus endpoint! 11

12 Step 4: Access your Globus endpoint Go to Manage Data à Transfer Files Access the endpoint you just created Enter: <username>#ec2- in Endpoint field Log in as user researcher (pwd: gw2015); you should see the user s home directory Transfer files Between esnet#???-diskpt1 and your endpoint 12

13 Exercise 5: Configuring Globus Connect Server Globus Connect Server configuration is stored in: /etc/globus-connect-server.conf To enable configuration changes you must run: globus-connect-server-setup Rinse and repeat NB: Please sudo su before continuing 13

14 Configuration file walkthrough Structure based on.ini format: [Section] Option Most common options to configure Name Public RestrictedPaths Sharing SharingRestrictedPaths IdentityMethod (CILogon, Oauth) 14

15 Changing your endpoint name Edit /etc/globus-connectserver.conf Set [Endpoint] Name = dtn Run globus-connect-server-setup Enter your username/password when prompted Access the endpoint in your browser using the new endpoint name You may need to refresh your browser to see the new name in the endpoint list 15

16 Making your endpoint public Try to access the endpoint created by the person sitting next to you You will get the following message: Could not find endpoint with name dtn owned by user <neighbor s username> 16

17 Making your endpoint public Edit: /etc/globus-connect-server.conf Uncomment [Endpoint] Public option Replace False with True Run globus-connect-server-setup Try accessing your neighbor s endpoint: you will be prompted for credentials you can access the endpoint as the researcher user 17

18 Common Globus Connect Server Configurations 18

19 Firewall configuration Allow inbound connections to port 2811 (GridFTP control channel) 7512 (MyProxy CA) or 443 (OAuth) Allow inbound connections to ports (GridFTP data channel) If transfers to/from this machine will happen only from/ to a known set of endpoints (not common), you can restrict connections to this port range only from those machines If your firewall restricts outbound connections Allow outbound connections if the source port is in the range

20 Using MyProxy OAuth server MyProxy without OAuth (we just did this!) Site passwords flow through Globus to site MyProxy server Globus does not store passwords Still a security concern for some sites Web-based endpoint activation Sites run a MyProxy OAuth server o MyProxy OAuth server in Globus Connect Server Users enter username/password only on site s webpage to access an endpoint Globus gets short-term X.509 credential via OAuth protocol 20

21

22 Enable sharing on your endpoint Edit: /etc/globus-connect-server.conf Uncomment [GridFTP] Sharing = True Run globus-connect-server-setup Go to the Web UI Start Transfer page* Select the endpoint* Create shared endpoints and grant access to other Globus users* * Note: Creation of shared endpoints requires a Globus Provider plan for the managed endpoint Contact support@globus.org for a one-month free trial 22

23 Advanced Endpoint Configuration 23

24 Select configuration scenarios Customizing filesystem access Using host certificates Using CILogon certificates Enabling sharing on GT GridFTP server Configuring multiple GridFTP servers Setting up an anonymous endpoint 24

25 Path Restriction Default configuration: All paths allowed, access control handled by the OS Use RestrictPaths to customize Specifies a comma separated list of full paths that clients may access Each path may be prefixed by R (read) and/or W (write), or N (none) to explicitly deny access to a path '~ for authenticated user s home directory, and * may be used for simple wildcard matching. E.g. Full access to home directory, read access to /data: RestrictPaths = RW~,R/data E.g. Full access to home directory, deny hidden files: RestrictPaths = RW~,N~/.* 25

26 Sharing Path Restriction Further restrict the paths on which your users are allowed to create shared endpoints Use SharingRestrictPaths to customize Same syntax as RestrictPaths E.g. Full access to home directory, deny hidden files: SharingRestrictPaths = RW~,N~/.* E.g. Full access to public folder under home directory: SharingRestrictPaths = RW~/public E.g. Full access to /proj, read access to /scratch: SharingRestrictPaths = RW/proj,R/scratch 26

27 Control sharing access to specific accounts SharingStateDir can be used to control sharing access to individual accounts For instance, with SharingStateDir = "/var/globus/sharing/$user user "bob" would be enabled for sharing only if a path exists with the name "/var/globus/sharing/bob/" and is writable by bob. 27

28 Using a host certificate for GridFTP You can use your GridFTP server with non-globus clients Requires a host certificate, e.g. from OSG Comment out Set FetchCredentialFromRelay = True CertificateFile = <path_to_host_certificate> KeyFile = <path_to_private key_associated_with_host_certificate> TrustedCertificateDirectory = <path_to_trust_roots> 28

29 Single Sign-On with InCommon/CILogon Requirements Your organization s Shibboleth server must release the eppn attribute to CILogon Your local resource account names must match your institutional identity (InCommon ID) Set AuthorizationMethod = CILogon in the Globus Connect Server configuration Set CILogonIdentityProvider = <your_institution_as_listed_in_cilogon_i dentity_provider_list> Add CILogon CA to your trustroots /var/lib/globus-connect-server/grid-security/certificates/ Visit ca.cilogon.org/downloads for certificates 29

30 Enabling Sharing on a GT GridFTP Installation Get Globus Sharing CA certificates toolkit.globus.org/toolkit/docs/latest-stable/gridftp/ securityd2b.tar.gz Add to your trusted certificates directory (/etc/gridsecurity/certificates) Use '-sharing-dn' option in the server as follows: globusgridftp-server -sharing-dn "/C=US/O=Globus Consortium/ OU=Globus Connect User/CN= transfer Use '-sharing-rp' option to restrict the file paths allowed for sharing: globus-gridftp-server -sharing-rp <path> admin 30

31 Deployment Scenarios Globus Connect Server components globus-connect-server-io, -id, -web Default: -io and id (no web) on single server Common options Multiple io servers for load balancing, failover, and performance No -id server, e.g. third-party IdP such as CILogon -id on separate server, e.g. non-dtn nodes -web on either id server or separate server for OAuth interface 31

32 Setting up multiple io servers Guidelines Use the same.conf file on all servers First install on the server running the id component, then all others 1. Install Globus Connect Server on all servers 2. Edit.conf file on one of the servers and set [MyProxy] Server to the hostname of the server you want the id component installed on 3. Copy the configuration file to all servers /etc/globus-connect-server.conf 4. Run globus-connect-server-setup on the server running the id component 5. Run globus-connect-server-setup on all other servers 6. Repeat steps 2-5 as necessary to update configurations 32

33 Deployment Best Practice: Science DMZ 33

34 Researchers don t realize full benefits of existing IT infrastructure Impedance mismatch between research computing systems and the WAN Network misconfiguration (10 x 1Gb/s links 1 x 10Gb/s link) Indiscriminate security policies TCP: small amount of packet loss = huge difference in performance 34

35 Science DMZ Components Friction free network path Dedicated, high-performance data transfer nodes (DTNs) Performance measurement/test node User engagement and education LOTS of great info available at: fasterdata.es.net/science-dmz 35

36 Typical deployment Border Router perfsonar Enterprise Border Router/Firewall Science DMZ + WAN perfsonar 10G Clean, High-bandwidth WAN path 10GE 10GE Site / Campus access to Science DMZ resources Science DMZ Switch/Router 10GE Site / Campus LAN Globus 10GE Per-service security policy control points perfsonar High performance Data Transfer Node with high-speed storage Details at: fasterdata.es.net 36

37 Network paths Lab1 DTN security filters Lab1 DTN 10GE DTN TCP ports DATA DTN Lab2 DTN 10GE Lab2 DTN security filters Lab1 Science DMZ TCP ports 443, 2811, 7512 TCP ports 443, 2811, 7512 Lab2 Science DMZ 100GE Orchestration Orchestration 10GE Lab1 Border Router Lab2 Border Router 100GE Amazon AWS 10GE ESnet Router 100GE ESnet 100GE ESnet Router Logical data path Logical control path Physical data path Physical control path Lab1 DTN security filters Lab2 DTN security filters 37

38 Enable your campus systems Signup: globus.org/signup Enable your resource: globus.org/globusconnect-server Need help? support.globus.org Subscribe to help make Globus self-sustaining globus.org/provider-plans Follow 38