M4 Creation of Own o²S²PARC Services

[elisabettai]

Facilitate and automate service creation by users and reduce the need for SIM-Core involvement, as well as the required manual work.
In Y5, SIM-Core established a basic integration library (ooil: o²S²PARC integration library) which provides a framework for managing the requirements and code structure for o²S²PARC services. In Y6, this integration library will be further expanded and documentation will be provided for third parties to perform local development testing of their potential services to ensure o²S²PARC compatibility. These tests can then be automated during the o²S²PARC integration step, which will greatly facilitate new service creation.

Deliverable: Template library (e.g., python cookiecutter) that users fills in and framework to build a docker service (continuous integration workflow). SIM-Core is expected to review the submitted service and provide guidance/support as needed. Associated documentation.
Deadline: Month 4

Wrike M5.1

[pcrespov]

Goal for sprint Athena

Some functionality in this case is needed to support the development of the optimizer

• enh. service integration (OOIL + cookiecutter)
  • Is3418/dot osparc layout: v1.0.0 cookiecutter-osparc-service#93
  • ✨ New python binder for function-services cookiecutter-osparc-service#94
  • release lifecycle with MaG (remember to create an issue!)

Review demo

• run cedric example from a notebook including the creation of a services used in the study to optimizef

[pcrespov]

Update on sprint Athena

• "fast python-service integration" (OOIL + cookiecutter)
  • Is3418/dot osparc layout: v1.0.0 cookiecutter-osparc-service#93
  • ✨ New python binder for function-services cookiecutter-osparc-service#94
• Started discussions on release life-cycle @mguidon @pcrespov

Open

• Design+Implement release life-cycle

[elisabettai]

@pcrespov, since this milestone is overdue (was for Dec.), EN would like to close it with the minimal effort possible.

Do you think we can finalize the work you've done on the function services so that a user can easily create services based on that? EN was proposing to wrap everything into a service.

fyi @mguidon

[pcrespov]

@pcrespov, since this milestone is overdue (was for Dec.), EN would like to close it with the minimal effort possible.

Do you think we can finalize the work you've done on the function services so that a user can easily create services based on that? EN was proposing to wrap everything into a service.

fyi @mguidon

@elisabettai We can continue after s4lite release

[esraneufeld]

yes, that would be after the release. my preference would be for a service on osparc that facilitates execution of process @pcrespov demonstrated, such that it can be used without being confronted with command lines, IDEs...
if that can be done with moderate effort.

[elisabettai]

Thanks @esraneufeld for the clarification. In the text of the milestone, we mention the python cookiecutter (template library). We already have the cookiecutter and it is quite advanced (@pcrespov, correct me if I'm wrong).
I recently used the python cookie cutter and worked quite well to create a new computational service (there are just some minor refinements and small bugs, which are listed in that repo).
In my opinion, it should be rather easy for an external user to create their own comp. services with the cookiecutter. Downside: some programming knowledge (and Docker?) is required. But I think we can also assume this knowledge, since presumably a user that wants to onboard his code as a service on oSPARC had to write code before.

[elisabettai]

This is closed for NIH, see update for Y6Q2 in wrike Wrike M5.1.
Should we close this one @pcrespov ?

[esraneufeld]

please, don't close yet, or create a follow up item.

[elisabettai]

We will create a follow up item once we create the corresponding issue from the Y7 milestones.

[elisabettai]

Closing, since we have a follow-up in #1092