Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P pypushflow
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • workflow
  • pypushflow
  • Merge requests
  • !1

WIP: Include and manage 'representation'

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed payno requested to merge payno/pypushflow:add_representation_project into master Jan 08, 2020
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 2

The goal of this PR is to perform execution of workflows defined by 'representation' with pypushflow.

A prototype using an old version 'pypushflow' was done: representationtest/instanciation and might be use back (https://gitlab.esrf.fr/workflow/representationtest)

Regarding the actual source code we should answer several questions before modifications:

  • Do we expect an application to execute any .ows or is this specific to the application using it (in this case pypushflow would be a library)

--> to start pypushflow will be a dependence of applications.

  • Does the 'joinActor', 'ForkActor', 'RouterActor' be defined at the representation test or should they be deduced from the 'representation scheme' (for me it should be second way)

-->It doesn't have to be defined in the 'moml' / 'ows' but could be deduced from it. Should be in 'representation scheme' or in 'pypushflow'. Like a 'interpret Scheme' which will embed the new actors. If embed in 'representation scheme' can be used by other tools.

  • Do we agree to insure all communication between actors with (serializable) dictionaries ? Would we like at one point to have more complex / better performance connection ?

--> to see later

  • Do we plan to 'move' the MongoDB part into an 'add-on' ?

--> yes, can / should be an add-on / plugin

  • What are the scenarii and typical use case ?
  • What should be the API

TODO list:

  • define concrete scenarii and use case
  • add some unittest
  • include representation in the project (/close #1 (closed))
  • define clearly the user API
  • add some tutorial
  • add some documentation
  • move mongodb part into an add-on (should be part of an other PR)
Edited Feb 14, 2020 by payno
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: add_representation_project