TIP v3 - osparc-devteam-tasks

[SCA-ZMT]

### Tasks
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1439
- [ ] https://github.com/ITISFoundation/osparc-simcore/issues/5669
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1548

For the applet-developers tasks, see: https://github.com/ITISFoundation/osparc-issues/issues/1155

### Eisbock
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1620
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1517
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1611
- [ ] https://github.com/ITISFoundation/osparc-simcore/issues/5864
- [ ] https://github.com/ITISFoundation/osparc-ops-environments/issues/632
- [ ] https://github.com/ITISFoundation/osparc-ops-environments/issues/645
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1549
- [ ] Talk to Reboux about tip.itis.swiss future
- [ ] tip-product on aws-master and aws-staging
- [ ] Optimize image size MAG
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1618
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1450
- [ ] https://github.com/ITISFoundation/osparc-issues/issues/1516
- [ ] OM/MD Aggregated time in addition to credit indicator

[mguidon]

Resource Requirements:

• The pipeline consist of 5 dynamic nodes: electrode selector, personalizer, simulator, tip-postpro, s4l-postpro
• All services should be based on the same jupyter-smash version (good for caching) and simphony base image
• personalizer, tip-postpro and s4l-postpro require a GPU for rendering
• None of the services can fit on the currently buffered machine types
• The simulator will execute one remote job on a high RAM instance

Based on this requirements, the tool will be quite expensive and slow. I see two options:

• we prepare one node with all the software installed (@pcrespov we discussed this over coffee, see https://github.com/ITISFoundation/osparc-simcore/discussions/5593)
• we create a proper all-in-one service with a dedicated UI (based on s4l-postpro)

[mguidon]

• "Fix" license server IP address
• Create s4l-python runner with iSolve
• a fake or real billing center?

[drniiken]

[GitHK]

20240507 TIP - > AWS Meeting Attendees: Niels, Nik, Melanie, Dustin, Manuel, Odei, Matus

Meeting Minutes

• In the new tip.science UI:
  • The credits are the only difference compared to the current tip.itis.swiss. (perception to the user).
  • We need to play through and refine asap the billable scenario (free + payable tiers).
  • Startup time might be a bit slower.
• Melanie is currently testing the integration for V3 o The new pipeline consists of five services (machines).
  • Release is envisioned for "end of May" (V3, personalization, AWS).
  • Demo (today) showed still some details/issues to address. Ideally we have a 1st/beta version very soon to play around with and refine/iterate.
  • UX still needs various refinements.
• Decision:
  • We will pay for everything except the simulations.
  • Cost on us: about 60k pa.
  • We might be able to save some more cost by "choosing/optimizing" the right machines.
  • Personalization: simulation cost is charged to the users.
• Billing will likely be set up to have a zero burn rate for all services, with only the simulation being billable.
  • Find a good communication, perception of the "billing aspect" for the users.
• Decision:
  • We will not spend one+ month of development time migrating TIP to sim4lie.io deployment

[mrnicegyu11]

Linking related cases:

• various tip improvements https://github.com/ITISFoundation/osparc-issues/issues/1345
• tip v3 https://github.com/ITISFoundation/osparc-issues/issues/1155