<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="font-family: Calibri, sans-serif; font-size: 14px; ">Hi Eric,</span><br><span class="Apple-style-span" style="font-family: Calibri, sans-serif; font-size: 14px; "><span class="Apple-tab-span" style="white-space: pre; "> </span></span><span class="Apple-style-span" style="font-family: Calibri, sans-serif; font-size: 14px; ">sorry for the late reply, I had lots going on today...</span><br><font class="Apple-style-span" face="Calibri, sans-serif"><br></font><span class="Apple-style-span" style="font-family: Calibri, sans-serif; font-size: 14px; ">So yes, it would definitely possible for NCAR to wait to upgrade to a full P2P system, and still make your data available through the larger federation as everybody else moves to P2P. I believe these are the steps that should be taken:</span><br><font class="Apple-style-span" face="Calibri, sans-serif"><br></font><span class="Apple-style-span" style="font-family: Calibri, sans-serif; font-size: 14px; ">a) The NCAR data node is updated to the latest version and configuration of thredds. This would allow that data to be authorized with multiple authorization services, one at the NCAR gateway, and one at a P2P Index node</span><br><font class="Apple-style-span" face="Calibri, sans-serif"><br></font><span class="Apple-style-span" style="font-family: Calibri, sans-serif; font-size: 14px; ">b) The NCAR certificates and trust store are periodically updated to trust all other P2P nodes that dynamically join the federation</span><br><font class="Apple-style-span" face="Calibri, sans-serif"><br></font><span class="Apple-style-span" style="font-family: Calibri, sans-serif; font-size: 14px; ">c) NCAR's THREDDS catalogs are periodically harvested by a P2P Index Node - for example by PCMDI. </span><br><font class="Apple-style-span" face="Calibri, sans-serif"><br></font><span class="Apple-style-span" style="font-family: Calibri, sans-serif; font-size: 14px; ">This should allow NCAR data to be distributed as part of CMIP5, and minimize the work on the NCAR administrators. </span><div><span class="Apple-style-span" style="font-family: Calibri, sans-serif; font-size: 14px; ">If you decide to go down this path, we'll be happy to help you.</span><br><font class="Apple-style-span" face="Calibri, sans-serif"><br></font><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><span id="OLK_SRC_BODY_SECTION"><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>thanks, Luca</div><div><br></div></div></div></span></div><div><div>On Feb 8, 2012, at 7:24 AM, Eric Nienhouse wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi Luca,<br><br>We began discussing CMIP5 paths forward including phased roll-out of the <br>P2P nodes in the go-essp call yesterday. Bob described a phase 2 and 3 <br>which involve publishing catalogs to both the Gateway and a P2P index <br>node. In other words, an interim heterogeneous system.<br><br>You mentioned that nodes (eg. the NCAR data node) may *only* need to <br>publish to the Gateway and that these nodes could be harvested and <br>indexed by others within the P2P system. This would avoid the need to <br>doubly publish which is desirable.<br><br>I'm curious how might this work. Is it only certain nodes that could <br>function in this way? What would be required at the node to do so?<br><br>Thanks,<br><br>-Eric<br><br><br><br><br><br><br><br><br>_______________________________________________<br>GO-ESSP-TECH mailing list<br><a href="mailto:GO-ESSP-TECH@ucar.edu">GO-ESSP-TECH@ucar.edu</a><br>http://mailman.ucar.edu/mailman/listinfo/go-essp-tech<br></div></blockquote></div><br></div></body></html>