 I'm Marko Tango, I work for Lixi Ritali, and here I'm going to present you the update of Laniakea. So Laniakea is a Galaxy on Demand platform, which is based on the Indigo Data Cloud Passlayer, but also on many Galaxy project tools, like the official Galaxy Docker Container or Ephemeris, but also on common open source tools like Bolt, Luxus, Larm or Cabernetis for example. A private cloud instance of Galaxy is recommended for those scenarios where the full administrative control of the instance is still needed, like for example training tools development or for example data privacy concerns. We provide also access to cloud resources to be used for the deployment of on-demand Galaxy instances through our pilot program, Laniakea Trekas. We currently have about 20 running Galaxy instances, for example some public servers like Vinyl, which was presented here like Plastiar, Corgaft, to align complete assemblies of SARS-CoV-2 genomes or ETS-1 Ruby, which have been accepted for publication and is dedicated to global taxonomic analysis of ecologic communities. So the service is commonly used for rapid development of bioinformatics tools, efficient delivery of training activities and provision of public bioinformatics services. I would recommend you the poster of Pietro Mandrioli during the poster session on this topic. During this year working side by side with researchers and clinicians will learn a lot on our users community and on our cloud providers. So the development of the next release of Laniakea have been deeply influenced by our community requirements, in particular at part-time level we need to update everything from Python 2 to Python 3, but also we need to update some important packages like Ansible. At service level we need a new service level agreement and the user's quota management. At development level we need to simplify the deployment strategy of Galaxy in order to reduce the maintenance effort and finally we have some requirements from our users like better container support and new applications. First of all at the past level we have this new service level agreement tool. SLA is a commitment between a cloud provider, in this case GAAR or RECASPARI for us, and a client, which in this case is of course Elixir Italy. And we need this to improve resource federation because we have many data centers in Italy and we want to use all these resources. In this case, as you can see in the figure on the bottom, we will introduce also per group and quota management in terms of course of number of instances, RAM, CPU and storage, which is now available in the current version only on, for example, PEST app level. For the Galaxy deployment, on Laniakea you can deploy Galaxy using Ansible, so you have a virtual machine and Ansible will install and configure everything for you. Or you can use a VM image, so you have this image with everything inside, you deploy it and everything is working. This procedure has been simplified using CVMFS volume to store tools and Galaxy database. So, we deploy this image with Galaxy inside, we restore the Galaxy tool database, the tool are on CVMFS and everything is working. We also contextually update everything from Python 2 to Python 3. Finally, from the user feedback, we need to implement RStudio and Jupyter and that now are available as a standalone application but also integrated in Galaxy and we are back porting these features to the current production version and this has been requested for training and development, but also it was required to support container because, for example, there is this R-Cask use case, which is a single cell and RSEC workflow that is developed only using the Docker container, so we need to provide them enough resources and we will do this with all mesos or Kubernetes, which are both now available as out of the box. So, we think this will be a great release of Laniakea, which is expected to be published by the end of the year and finally I would just to thank you all for your attention.