WP2 Overview (Technical architecture)


Published on

  • 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
  • To quote wikipedia: In computing, failover is the capability to switch over automatically to a redundant or standby computer server, system, or network upon the failure or abnormal termination of the previously active application, server, system, or network. Failover happens without human intervention and generally without warning. This means that, at the NHM, we will host the Scratchpads across multiple servers to ensure a high level of availability of the service. As I mentioned before, Walter will talk shortly about our intentions with mirroring.
  • We intend to provide a simple download and install package of the tools we develop as part of ViBRANT. This will specifically include a Scratchpad server one-click install package. In what exact form this will be, we’re not sure, although it could be an OS install image, or simply a pointer to a software repository.
  • One stop show to find the
  • As the core component of ViBRANT, and given that ViBRANT’s success will be measured on users and usage, it will be necessary for us to record and publish data usage. I’m open to suggestions on exactly how we should go about doing this.
  • WP2 Overview (Technical architecture)

    1. 1. WP2Technical architecture<br />S.Rycroft, Natural History Museum, London<br />s.rycroft@nhm.ac.uk<br />
    2. 2. Hosting architecture<br />Failover<br />Mirroring<br />Provide technical support<br />
    3. 3. What is failover? Do we need it? Will it make things quicker? Is it kewl?<br />Failover<br />
    4. 4. How do I install a Scratchpad? Where is the download? Your server sucks, can I host this on my Mac? PHP sauce?<br />Provide technical support<br />
    5. 5. Multisite integration<br />Dynamic site/service registry<br />Search portal<br />Measure & publish data usage<br />Research data citation metric for ViBRANT data<br />
    6. 6. Who will use this? How do I benefit? Doesn’t somebody else do this already?<br />Dynamic site/service registry<br />
    7. 7. Isn’t everybody doing this? What is usage?<br />Measure & publish data usage<br />
    8. 8. What is a citation metric? Does ViBRANT need one? Does taxonomy need one? Does my gran need one?<br />Research data citation metric for ViBRANT data<br />
    9. 9. Scratchpads interface<br />Lead technical integration<br />Automated code testing<br />Prioritise development from WP3<br />Manage training resources<br />
    10. 10. Are you going to build the jigsaw puzzle? Would you like some help?<br />Lead technical integration<br />
    11. 11. Does this involve unit testing? Can we just use an army of monkeys? Do we all need to do this?<br />Automated code testing<br />
    12. 12. What will come first? How do we prioritise? Can we skip the queue?<br />Prioritise development from WP3<br />
    13. 13. What training resources? Can we have more resources? Can I have my own Sandbox?<br />Manage training resources<br />
    14. 14. Sustainability<br />Develop a financial model sustaining ViBRANT<br />Provide a Service Level Agreement (SLA) for users <br />
    15. 15. Will we get paid? Can I gamble my ViBRANT money?<br />Develop a financial model sustaining ViBRANT<br />
    16. 16. Is this just during ViBRANT? What can we promise? What do our users want?<br />Provide a Service Level Agreement (SLA) for users<br />