NeCTAR Presentation


Published on

At the OpenStack Essex Conference (Oct. 2011)

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

NeCTAR Presentation

  1. 1. National eResearch Collaboration Tools and Resources<br /><br />NeCTAR is an Australian Government project conducted as part of the Super Science initiative and financed by the Education Investment Fund. The University of Melbourne has been appointed the lead agent by the Commonwealth of Australia, Department of Innovation, Industry, Science and Research. <br />Objectives: to enhance research collaboration through the development of eResearch infrastructure.<br />
  2. 2. The talk today<br />History<br />Community<br />Everett Toews<br />Steven Manos<br />Technology<br />Tom Fifield<br />
  3. 3. The birth of NeCTAR<br />The process of research can readily be described in term of how data flows<br />Computational modeling, data analysis, etc. (APAC, NCI, Pawsey)<br />Compute<br />Use tools & apps to work remotely and collaboratively - NeCTAR<br />Combine<br />Keep<br />Keep data and observations, describe, collect, share, find and re-use them – RDSI, ANDS<br />Access<br />
  4. 4. The Story<br />SuperScience Story from Rhys<br />National Infrastructure<br />4<br />
  5. 5. The Story<br />SuperScience Story from Rhys<br />National Infrastructure<br />5<br />
  6. 6. The Story<br />SuperScience Story from Rhys<br />National Infrastructure<br />6<br />
  7. 7. The Story<br />SuperScience Story from Rhys<br />National Infrastructure<br />7<br />
  8. 8. The Story<br />SuperScience Story from Rhys<br />National Infrastructure<br />8<br />
  9. 9. The Story<br />SuperScience Story from Rhys<br />National Infrastructure<br />9<br />
  10. 10. Shape of NeCTAR<br />
  11. 11. Why build itourselves?<br />1. Proximity – the honeypot – infrastructure attracts community<br />2. Local infrastructure is more responsive to research needs<br />3. Service offering and charging models suitable for research<br />4. Locality to instruments, research networks and other infrastructure.<br />
  12. 12. NeCTAR Research Cloud<br />An OpenStack Cloud<br /><ul><li>Any Researcher, Any Discipline, Anywhere
  13. 13. Some level of ‘instant access’</li></ul>A single national cloud <br /><ul><li>Up to six sites (called “nodes” – sorry!)
  14. 14. $1.5M per node</li></ul>Supporting Inward and Outward Federation<br /><ul><li>EC2/S3 API</li></li></ul><li>Cloud Use Cases<br />Particle Physics simulations powered by a distributed computing workflow tool to span Grid, Cloud and HPC [DIRAC]<br />Large-scale genome analysis using an interactive platform [Galaxy]<br />Collaboration toolse.g. Sakai/Wordpress/MediaWiki<br />Demographics/Sustainable Society - “Convicts and Diggers: a demography of life courses, families and generations”<br />Disaster Management -<br />Urban Research – using a geospatial information platform<br />Wave-Induced Turbidity Modeling, 3D Telemedicine, ...<br />
  15. 15. Research Cloud Timeline<br />National cloud<br />First node<br />Pilot<br />20,000 cores+<br />6 PB<br />3,000 cores+<br />1 PB<br />300 cores<br />195 TB<br />Now<br />Q1 2012<br />2013<br />
  16. 16. OpenStack feature interests<br />Zones and scheduling are important<br /><ul><li>We need to provide a single endpoint
  17. 17. We need to provide direct access to specific nodes or ‘special’ zones</li></ul>AAA is crucial<br /><ul><li>We have a nation-wide SSO service (AAF)
  18. 18. It’s based on shibboleth
  19. 19. Designing our code to be used anywhere</li></ul>15<br />
  20. 20. Melbourne Node<br />16<br />
  21. 21. Melbourne Node<br />Networking<br />17<br />
  22. 22. Collaborative operations<br />18<br />
  23. 23. Network<br />IPv4 address exhaustion<br />Most National Research Networks are IPv6 ready<br />OpenStack on IPv6<br />IPv6 Call to Arms!<br />19<br />
  24. 24. Community<br />Users helping users<br />Australian OpenStack User Group<br />Blog, file bugs, ask (and answer!) questions<br />Documentation<br />Code, code, code -<br />20<br />