Enhancement: Lock a EC2 machine for a specific project

[sanderegg]

As a user of TIP where the osparc App mode is in use it would be more cost efficient and fast to keep a specific EC2 up for the duration a project is opened.

The idea would be to do the following to reserve a machine for a set of services with using the project uuid as a resource:

• modify dynamic scheduler to create a docker service using the project uuid as a placement constraint,
• autoscaling would recognize that specific placement constraint, start a machine, and once the machine is up add the specific label on the node,
• automatically all the services with that node constraint would then go to that specific machine,
• if more than one machine is needed, this should actually not prevent the autoscaler from creating more of them,
• if we want later to share the a machine data, then we would also need to make the autoscaling app wait a bit before creating a new one (until the current service is shutdown and leaves space for the next one),

Option:

• do not require shutdown of previous service by having service reservations low (since they do not run in parallel - this would need to be somehow guaranteed...)

[mguidon]

This just came up in another discussion and we most likely want to implement it

[matusdrobuliak66]

We should write implementation notes that consider the big picture of providing users with the option (including via the UI) to set up their own computers with multiple services, as well as the potential consequences for the current UI.

Questions:

• what about pipeline view?