Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Wellbore Domain Services Wellbore Domain Services
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Domain Data Management Services
  • Wellbore
  • Wellbore Domain ServicesWellbore Domain Services
  • Issues
  • #17
Closed
Open
Issue created Aug 06, 2021 by Gisele Souza@gsouzaOwner

Wellbore DDMS v3 APIs

As part of the development of V3 APIs, a bulk data access has been added. The Wellbore APIs have been developed, however CSPs need to implement specific code to support the new APIs.

Copy from the slack post:

Vincent Rondot [SLB] 11:57 AM Hi, to follow-up on a topic raised some weeks ago slack post 1 & slack post 2, I am kindly reminding that we need the help of the different CSPs to implement a small CSP specific logic required for the new Bulk Data APIs (chunking APIs). So far, Azure and GCP implementation have been taken care of, and IBM and AWS are missing. The changes required are located in:

  • Cloud specific Libraries:

You need to create a factory method which returns a DaskStorageParameter object. (https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/lib/wellbore-core/wellbore-core-lib/-/blob/master/osdu/core/api/storage/dask_storage_parameters.py)

  • Cloud specific Injectors:

You need to enrich the Injector to create a DaskBulkStorage consmuning the DaskStorageParameter of the specific CSP. Placeholders have been added and need to be properly implemented

AWS: https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/blob/master/app/injector/aws_injector.py#L36

IBM: https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/blob/master/app/injector/ibm_injector.py#L28

Feel free to refer to the Azure or GCP implementation as a guideline:

Azure: https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/lib/wellbore-cloud/wellbore-azure-lib/-/blob/master/osdu_az/storage/dask_storage_parameters.py https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/blob/master/app/injector/az_injector.py#L36

GCP: https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/lib/wellbore-cloud/wellbore-gcp-lib/-/blob/master/osdu_gcp/storage/dask_storage_parameters.py https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/blob/master/app/injector/gcp_injector.py

You may refer to Dask documentation for further info: https://docs.dask.org/en/latest/remote-data-services.html

Also don't hesitate to contact us for any help and guidance for those changes. Thanks, Regards, Vincent

Link to video with code walk-through: https://opensdu.slack.com/archives/C015T1RC0Q6/p1628693191059100

Edited Oct 08, 2021 by Gisele Souza
Assignee
Assign to
Time tracking