...
The difference between Tool and script is not helpful and makes the catalog more cumbersome to navigate. Let's make everything a tool. Do we need a way We can use Repos to relate the scripts to each other? Can we do it in some other way?. For example, there could be an ImageMagik repo with all of the related tools, or else the tools could simply be related by virtue of the category. More discussion needed on this.
Deployment is a Local Concern
...
Each service will have its own deployment workflow. We'll attempt to capture the most popular ones.
Deploy to a Local Clowder
We will make deploying to a local Clowder as easy as installing a plug-in to IntelliJ. User can copy a repo/tool reference from the tool catalog and just paste it into their Clowder UI deploy form.
This will mean migrating Clowder to a Docker Swarm deployment and adding a deployment page to the UI.
We will add queue binding functionality to the Clowder UI as well.
Deploy to a local Brown Dog Cluster
If a group have elected to use the Groups deploying entire Brown Dog suite then they can use a new Cluster Management tool to mange manage deployments and queue bindings across the entire cluster of Clowder and Polyglot. This will mean building a new tool for Brown Dog that will be for managing clusters.
...
- Deploy tools to a cluster
- Amend min/max instance settings
- Pause a tool
- Delete a tool
- Manage queue bindings
- Refresh tool versions
- View deployed tools and some metrics
Supporting Local Clowder Deployments Across Projects
We will make deploying to a local Clowder as easy as installing a plug-in to IntelliJ. User can copy a repo/tool reference from the tool catalog and just paste it into their Clowder UI deploy form.
This will mean migrating Clowder to a Docker Swarm deployment and adding a deployment page to the UI.
We will add queue binding functionality to the Clowder UI as well.