-- MarioReale - 12 Feb 2009

================================================================================================

1)

First step is to describe the testbed in Paris and Rome and show how we manage the DNS - how we risolve nodes IPv4 and IPv6. Let people understand clearly that we are deploying some components which have been ported to IPv6 (LFC,DPM, BDII), and others which aren't IPv6 compliant. Thus we expect different behaviors, and we will verify this with the audience. Also showing how we connect from Catania (we have both stacks there available)

======================================================================================

2) "Dual Stack"

We add the IPv6 layer to all nodes - thus implementing DualStack everywhere. Ideally now gLite choses its favourite stack (if we use the DNS with both records (A, AAAA) for each hostnames. Or we suggest gLite what to do if we use the { /etc/hosts & "hosts = files" (remove "dns") in nsswitch.conf } approach. We show at this step that some middleware components use IPv6 while others user IPv4, and the system is overall working, still.

We connect on a UI (Paris or Rome) and then we issue:

WMS:

- globus-job-run ce-ipv6-testbed.paris.urec.cnrs.fr /bin/pwd

- glite-job-list-match test.jdl

- glite-wms-job-delegate proxy -d myDelegation

- glite-job-submit test.jdl

- glite-wms-job-status

INFOSYS-BDII:

(Here we could even show them what happens if we use DNS, what happens if we use /etc/hosts - even swapping inside /etc/hosts from IPv4 addresses to IPv6 ones)

-ldapsearch -x -P2 -LLL -h bdii-4.dir.garr.it -p 2170 -b "mds-vo-name=local,o=grid"

-ldapsearch -x -P2 -LLL -h 193.206.106.51 -p 2170 -b "mds-vo-name=local,o=grid"

-ldapsearch -x -P2 -LLL -h bdii-ipv6-testbed.paris.urec.cnrs.fr -p 2170 -b "mds-vo-name=paris-urec-ipv6,o=grid"

- lcg-infosites --vo infngrid ce

- lcg-infosites --vo infngrid se

DATA MANAGEMENT:

(Here we could even show them what happens if we use DNS, what happens if we use /etc/hosts - even swapping inside /etc/hosts from IPv4 addresses to IPv6 ones) (One sets DPM_HOST=.. and LFC_HOST=.. on the UI)

- globus-url-copy file:///tmp/DualStackUsingIPv4 gsiftp://dpm1-4.dir.garr.it/tmp/TestFileDualStackUsingIPv4 - globus-url-copy -ipv6 file:///tmp/DualStackUsingIPv6flag gsiftp://dpm1-4.dir.garr.it/tmp/TestFileDualStackUsingIPv6flag

- globus-url-copy gsiftp://dpm1-4.dir.garr.it/tmp/TestFileDualStackUsingIPv4 gsiftp://dpm1-4.paris.urec.cnrs.fr/tmp/TestFileDualStackUsingIPv4 - globus-url-copy -ipv6 gsiftp://dpm1-4.dir.garr.it/tmp/TestFileDualStackUsingIPv6flag gsiftp://dpm1-4.paris.urec.cnrs.fr/tmp/TestFileDualStackUsingIPv6flag

- lfc-ping -h lfc-ipv6-testbed.paris.urec.cnrs.fr

- lfc-ls /grid

- lfc-mkdir /grid/infngrid/testDualStack

- dpm-ping -h dpm1-4.dir.garr.it

- dpm-qryconf

- dpns-ls /

NETWORKING SETUP: we switch on the IPv6 stack everywhere- on all used nodes of our testbed. We can use Etienne's script (SSH-keys) to do this - or we can also do it by hand: I think all addresses and gateways could be already there - one should only set the flag NETWORKING_IPV6=yes in the /etc/sysconfig/network file.

DNS SET UP: { /etc/hosts & "hosts = files" (remove "dns") in nsswitch.conf }

GLITE FUNCTIONALITY RELATED COMMANDSglobus-job-run, glite-wms-job-list-match, glite-wms-job-delegate-proxy, glite-wms-job-submit, glite-wms-job-status , ldapsearch, lcg-infosites, globus-url-copy, lfc-ping, lfc-ls, lfc-mkdir, dpm-ping, dpm-qryconf, dpns-ls

HOW TO PROVE WHAT IS HAPPENING: netstat -lnpt; /usr/sbin/lsof -i -n; iptables logs

=========================================================================

3) "IPv6-only"

We remove IPv4 from the UI node and from the top-level BD-II node. We can show in this way very immediately what works and what is broken using only IPv6: this also gives the (right) impression to people of an IPv6-compliance which is "work in progress" : something works, not all - as of today. This could have the effect also of stimulating both users and developers towards IPv6, for "ask for IPv6" (users) and for "let's hurry up with the porting" (developers).

All the clients we lauch from the IPv6-only UI have only IPv6 available: BDII, Data Management should work, WMS commands should fail.

If we have all nodes doubly registered in the DNS we could use the DNS, otherwise we can anyhow use the { /etc/hosts & "hosts = files" (remove "dns") in nsswitch.conf } approach. We show at this step that some middleware components use IPv6 without problems, while others, the non ported one - will produce a failure.

WMS:

- globus-job-run ce-4.dir.garr.it /bin/pwd [ should FAIL ]

- glite-job-list-match test.jdl [ should FAIL ]

- glite-wms-job-delegate proxy -d myDelegation [ should FAIL ]

- glite-job-submit test.jdl [ should FAIL ]

- glite-wms-job-status [ should FAIL ]

INFOSYS-BDII:

-ldapsearch -x -P2 -LLL -h bdii-4.dir.garr.it -p 2170 -b "mds-vo-name=local,o=grid"

-ldapsearch -x -P2 -LLL -h 193.206.106.51 -p 2170 -b "mds-vo-name=local,o=grid" [ should FAIL ]

-ldapsearch -x -P2 -LLL -h bdii-ipv6-testbed.paris.urec.cnrs.fr -p 2170 -b "mds-vo-name=paris-urec-ipv6,o=grid"

- lcg-infosites --vo infngrid ce

- lcg-infosites --vo infngrid se

DATA MANAGEMENT:

(One sets DPM_HOST=.. and LFC_HOST=.. on the UI)

- globus-url-copy -ipv6 file:///tmp/localTestFileIPv6only gsiftp://dpm1-4.dir.garr.it/tmp/TestFileIPv6only

- globus-url-copy -ipv6 gsiftp://dpm1-4.dir.garr.it/tmp/TestFileIPv6only gsiftp://dpm1-4.paris.urec.cnrs.fr/tmp/TestFileIPv6only

- lfc-ping -h lfc-ipv6-testbed.paris.urec.cnrs.fr

- lfc-ls /grid

- lfc-mkdir /grid/infngrid/testipv6

- dpm-ping -h dpm1-4.dir.garr.it

- dpm-qryconf

- dpns-ls /

NETWORKING SETUP:

DNS SET UP: { /etc/hosts & "hosts = files" (remove "dns") in nsswitch.conf } approach

GLITE FUNCTIONALITY RELATED COMMANDSglobus-job-run, glite-wms-job-list-match, glite-wms-job-delegate-proxy, glite-wms-job-submit, glite-wms-job-status , ldapsearch, lcg-infosites, globus-url-copy, lfc-ping, lfc-ls, lfc-mkdir, dpm-ping, dpm-qryconf, dpns-ls

HOW TO PROVE WHAT IS HAPPENING netstat -lnpt; /usr/sbin/lsof -i -n ; iptables logs

=========================================================================

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2009-02-17 - MarioReale
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback