State of the Galaxy Community Update 2018

Anton and James thoughts on Galaxy present and future presented at #GCCBOSC2018.

Transcript

1. Community Update
   

   View Slide

2. “The Galaxy platform… 2018 Update”, Nucleic Acids Research, doi:10.1093/nar/gky379
   

   View Slide

3. Genomics at “Scale”
   

   View Slide

4. What do we mean by scale?
   

   View Slide

5. Research is diverse
   

   View Slide

6. Dataset size and complexity
   Number of users
   

   View Slide

7. Dataset size and complexity
   Number of users
   Clinical
   High propensity
   for standardization
   Non clinical
   Low propensity
   for standardization
   

   View Slide

8. For example, NIH funding
   

   View Slide

9. Individual research projects
   

   View Slide

10. Dimensions of scale
    

    View Slide

11. Technical
    Dataset size
    Number of datasets
    Data and tool heterogeneity
    Level of privacy/security required
    Social
    Community size
    Global Reach
    

    View Slide

12. What’s special about Galaxy?
    

    View Slide

13. Philosophy
    Accessibility
    Extensibility
    Platform mindset
    User Engagement
    

    View Slide

14. How well are we reaching potential user
    communities?
    

    View Slide

15. Biological and biomedical research
    is a global endeavour
    

    View Slide

16. Publications worldwide (2012)
    

    View Slide

17. 2018: Year of the Global Galaxy
    usegalaxy . ★
    

    View Slide

18. View Slide

19. Not just about having Galaxy in multiple
    places, but about coordination
    

    View Slide

20. XSEDE, Indiana University
    XSEDE & CyVerse,
    TACC, Austin
    EU JRC, Ispra
    Penn State
    cvmfs0-tacc0
    ● test.galaxyproject.org
    ● main.galaxyproject.org
    cvmfs1-tacc0
    cvmfs1-iu0
    ● Stratum 0 servers
    ● Stratum 1 servers
    galaxy.jrc.ec.europa.eu
    de.NBI, RZ Freiburg
    cvmfs0-psu0
    ● singularity.galaxyproject.org
    ● data.galaxyproject.org
    cvmfs1-psu0
    cvmfs1-ufr0.usegalaxy.eu
    CVMFS server distribution
    Galaxy Australia, Melbourne
    cvmfs1-mel0.gvl.org.au
    

    View Slide

21. View Slide

22. View Slide

23. Galaxy Training
    

    View Slide

24. View Slide

25. View Slide

26. Where are we going?
    

    View Slide

27. Refocusing on the end user experience
    

    View Slide

28. Galaxy UI is unique advantage—let’s make it better!
    Dataset collections—first size, now heterogeneity
    Single-page application with histories, workflows, visualizations all in one place
    Multiple, connected windows (ala JupyterHub)
    Drag and drop all the things
    Extensible and generalizable like the rest of Galaxy
    Different levels of detail: Galaksio/Activities, current UI, command line/notebook
    

    View Slide

29. Are we sustainable?
    

    View Slide

30. View Slide

31. Federation and Bring Your Own X
    

    View Slide

32. Federated storage as a first step
    Galaxy Main Private Servers Public Servers Servers Cloud Galaxy Appliance
    User
    ∞
    ∞
    ∞
    ∞ ∞
    Azure
    BLOB
    AWS
    S3
    OpenStack
    Swift
    

    View Slide

33. Milky Way aka Galaxy-as-a-Service
    

    View Slide

34. Milky Way aka Galaxy-as-a-Service
    

    View Slide

35. Ways this helps us all
    Deploy Galaxy anywhere (and everywhere) more easily
    Allow users to bring whatever resources they have, use resources more efficiently
    Move compute to data, and compute over data that is never co-located
    Integrate with existing and emerging authn/authz systems enabling the analysis of
    large and protected datasets in place
    Bring the wealth of tools and analysis approaches developed in Galaxy to new datasets,
    and open up new datasets and resources to the research community
    

    View Slide

36. Discussion
    What should Galaxy be?
    

    View Slide

37. Want to work on any of these things with us?
    Next generation Galaxy UI
    Global Data/Compute Federation
    Interoperability with other platforms
    Creating and running training
    Talk to James, Anton, Dan, or Jeremy!
    

    View Slide

38. View Slide

39. (fin)
    

    View Slide