[Quick Launcher] Quick Launcher service

[SilinPavel]

trafficstars

Background

Cloud Pipeline could be configured to provide separate functionality to:

• Organize and view rstudio tools and rshiny apps (quick-launcher UI)
• Provide mechanism to scale resources automatically (based on hot node pools)

Such big peace of functionality seems to be great candidate for integration in default deployment process. However right now all configuration should be done manually.

Approach

The next steps should be considered to be implemented:

• Fix bugs related to quick-launcher
• Unify this approach to be able to host not only shiny or rstudio
• Solution to integrate this functionality to default deployment (f.e. with -s quick-launcher automatically done the next) :
  • "sys" cloud-pipeline cron job for creating cloud home dirs is configured
  • required system user and its infrastructure is created automatically (e.g. SHINY_PORTAL user)
  • edge configured to serve additional external-app (e.g. quick-launcher)
  • quick-launcher is configure with required parameters (could have default values or be overwritten)
  • optimized images should be build and tagged (mechanism to use default images should be in place as well)

Linked issues

List of sub-issues related to this one:

Bugs:

#2599 Quick Launcher fail to find shiny apps for user with @ in the name

Enhancements:

#2603 Refactor quick launcher settings for tools #2604 Include Quick Launcher as a service in deployment process