...
Docker Swarm services are represented as running instances of tools. The Service Name is unique, but has no system significance. There can be multiple instances of a tool running since the queue name and service name are unique.
| Mockup | ||||||
|---|---|---|---|---|---|---|
|
And projects
...
In the first step you choose the tool by selecting a tool type and then enteringing the name of the tool. The form will attempt to auto-complete the tool name as you type.
| Mockup | ||||||
|---|---|---|---|---|---|---|
|
In the second step you can enter deployment parameters and select which projects you wish to immediatly bind the tool to. ClusterMan will generate a unique queue name that is based on the defaul queue name specified in the tool defintion.
Clicking Deploy will attempt to deploy the tool to the cluster.
| Mockup | ||||||
|---|---|---|---|---|---|---|
|
Once the tool has been successfully deployed, the user will be asked to manage bindings for the new tool to the existing projects.
For an extractor they will have some choices to make:
| Mockup | ||||||
|---|---|---|---|---|---|---|
|
For converters, there is no choice. Remind the user that the new converter has been bound to every project in the cluster.
| Mockup | ||||||
|---|---|---|---|---|---|---|
|
New Project
Authorized users can add new projects to the application when a new exchange is added to RabbitMQ. When the project is created, the user can specifiy which users have administrative rights over this project. They will be entitiled to bind and unbind tools within their project.
...