Home issueshttps://community.opengroup.org/osdu/platform/home/-/issues2020-03-25T22:06:29Zhttps://community.opengroup.org/osdu/platform/home/-/issues/1Merge changes to the core services2020-03-25T22:06:29ZStephen Whitley (Invited Expert)Merge changes to the core servicesThe OSDU core services contributed by Schlumberger were from a snapshot in August 2019. Since then, the OSDU copy has been ported to multiple platforms and the Schlumberger Internal version has been enhanced with new features and bug fi...The OSDU core services contributed by Schlumberger were from a snapshot in August 2019. Since then, the OSDU copy has been ported to multiple platforms and the Schlumberger Internal version has been enhanced with new features and bug fixes. We need to merge the updates from the two branches.
M1 - Release 0.1Stephen Whitley (Invited Expert)Chris ZhangStephen Whitley (Invited Expert)2020-04-30https://community.opengroup.org/osdu/platform/home/-/issues/2Populate Backlog from SLB Contributions2022-08-23T13:29:45ZStephen Whitley (Invited Expert)Populate Backlog from SLB ContributionsPopulate the Backlog issues list with the list of additional services that SLB is contributing during the R3 development phase.Populate the Backlog issues list with the list of additional services that SLB is contributing during the R3 development phase.M1 - Release 0.1Chris ZhangAn NgoMichael CleminsonChris Zhang2020-02-28https://community.opengroup.org/osdu/platform/home/-/issues/5Schema Service2020-03-25T21:47:10ZStephen Whitley (Invited Expert)Schema ServiceM1 - Release 0.1Hrvoje MarkovicChris ZhangAn NgoMichael CleminsonHrvoje Markovichttps://community.opengroup.org/osdu/platform/home/-/issues/6[Reference and Helper Services] CRS Catalog and Conversion2020-03-25T13:59:48ZStephen Whitley (Invited Expert)[Reference and Helper Services] CRS Catalog and Conversion**Objective**:
1. The main goals of the Spatial Reference Catalog service are to offer
- *Coordinate Reference Systems* (CRSs) to enable end-users to make a CRS selection.
- * Search for CRSs given a number of constraints.
- * ...**Objective**:
1. The main goals of the Spatial Reference Catalog service are to offer
- *Coordinate Reference Systems* (CRSs) to enable end-users to make a CRS selection.
- * Search for CRSs given a number of constraints.
- * Download of the entire catalog for local caching and when the cache has to be refreshed.
- * Access to various sub-sets of the catalog.
- * Once a CRS is found, produce a persistable reference to be stored with the data, which fully describes the CRS; this persistable reference string becomes catalog independent. This means any consumer will be able to understand the CRS definition even if a different catalog is used in the future context.
- More details captured [here](https://community.opengroup.org/osdu/documentation/-/wikis/OSDU-(C)/Design-and-Implementation/API-Specifications/Documentation/core-services/CRSCatalogService)
2. The main goals of the conversion service is to provide spatial reference conversions for coordinates.
- Coordinates are represented by an array of 3D points.
- The measurement and unit associated with the axes, is given by the CRS definitions.
- In most of the cases, the CRS definition is 2D.
- In both the geographic and projected CRS types, the Z-axis is passed through unchanged, and its unit is only known to the client.
- More details captured [here](https://community.opengroup.org/osdu/documentation/-/wikis/OSDU-(C)/Design-and-Implementation/API-Specifications/Documentation/core-services/CRSConversionService)
M1 - Release 0.1Chris ZhangAn NgoMichael CleminsonChris Zhanghttps://community.opengroup.org/osdu/platform/home/-/issues/7[Reference and Helper Services] Unit Service2020-03-25T13:39:16ZStephen Whitley (Invited Expert)[Reference and Helper Services] Unit ServiceThe Unit service provides dimension/measurement and unit definitions. Given two unit definitions, the service also offers conversion parameters in two different parameterizations.
**Concepts**:
- Measurements are organized in a hierarc...The Unit service provides dimension/measurement and unit definitions. Given two unit definitions, the service also offers conversion parameters in two different parameterizations.
**Concepts**:
- Measurements are organized in a hierarchy.
- The *Dimension* is the root measurement;
- A *ChildMeasurement* has a parent *Measurement*, which can be another *ChildMeasurement* or a *Dimension*.
- *Units* are associated with a *Dimension* (root or base measurement)
- Unit conversions are possible if the two units belong the the same *Dimension*.
- The catalog may contain definitions from multiple source catalogs. Namespaces are used to distinguish the contributions.
- Mappings are defined where a measurement or a unit has the same meaning in different namespaces.
Further details are elaborated [here](https://community.opengroup.org/osdu/documentation/-/wikis/OSDU-(C)/Design-and-Implementation/API-Specifications/Documentation/core-services/UnitService)M1 - Release 0.1Chris ZhangChris Zhanghttps://community.opengroup.org/osdu/platform/home/-/issues/8[Seismic DDMS] Deliver Seismic DDMS2020-03-25T13:46:09ZStephen Whitley (Invited Expert)[Seismic DDMS] Deliver Seismic DDMS**Objective**:
- Deliver an optimized bulk/brick accessor for seismic data to include open formats such as SEGY, OpenVDS and open ZGY formats.
- Provide type-safe accessors to seismic header entities.
**Details**:
- Integration with...**Objective**:
- Deliver an optimized bulk/brick accessor for seismic data to include open formats such as SEGY, OpenVDS and open ZGY formats.
- Provide type-safe accessors to seismic header entities.
**Details**:
- Integration with system services and impact of reference systems in particular – CRS, units, elevation references (including SRD). This is key to nail down even if we cant do conversions in R3, so the interfaces expose and consume standard FoR.
- Seismic DMS and bulk data handling rationalization with Schlumberger and Bluware – important that we can land one DMS for both Open VDS and ZGY.
- [Schlumberger] to complete contribution the ZGY specification and source code as an extension to the library and API documentation contributed in R2. M1 - Release 0.1CyrilPhil HodgsonCyrilhttps://community.opengroup.org/osdu/platform/home/-/issues/9[Wellbore DDMS] Deliver the WellBore DDMS2020-03-25T13:34:00ZStephen Whitley (Invited Expert)[Wellbore DDMS] Deliver the WellBore DDMS**Objective**:
- Define the Wellbore Domain Management Service (DDMS) to cover the well, wellbore, LogSet, Log, Trajectory, Marker data objects initially available in R2 and provide type-safe APIs and optimized bulk accessors for array ...**Objective**:
- Define the Wellbore Domain Management Service (DDMS) to cover the well, wellbore, LogSet, Log, Trajectory, Marker data objects initially available in R2 and provide type-safe APIs and optimized bulk accessors for array data (logs, trajectories).
**Detailed Scope**:
The Wellbore Domain Data Management Service will deliver type-safe entity access and optimized accessors for bulk data such as logs, trajectories, checkshots. The scope for the R3 delivery will be API's for the following data entities: Wellbore, Logset and Log.
- A valid Logset is a group of logs with a common reference. The values for the reference need to be in decreasing order.
- A valid Log is a series of numerical values (no support today for alphanumeric logs) in n columns.M1 - Release 0.1Dror DahanDror Dahanhttps://community.opengroup.org/osdu/platform/home/-/issues/10Complete Entitlements APIs for R3 development2022-08-23T13:29:45ZStephen Whitley (Invited Expert)Complete Entitlements APIs for R3 developmentM1 - Release 0.1Dania Kodeih (Microsoft)JoeChris ZhangDania Kodeih (Microsoft)2020-03-31https://community.opengroup.org/osdu/platform/home/-/issues/12Schema service2020-05-20T02:51:06ZChris ZhangSchema serviceM1 - Release 0.1Chris ZhangMichael CleminsonChris Zhanghttps://community.opengroup.org/osdu/platform/home/-/issues/13WKS transformation service2020-03-25T12:53:36ZChris ZhangWKS transformation serviceM1 - Release 0.1Hrvoje MarkovicChris ZhangAn NgoMichael CleminsonHrvoje Markovichttps://community.opengroup.org/osdu/platform/home/-/issues/14[Platform] Support OSDU Global Deployment2020-06-18T18:25:21ZStephen Whitley (Invited Expert)[Platform] Support OSDU Global Deployment**Objective:**
- This requirement is to ensure OSDU data platform can support highly available multi-region/geographical deployment.
An OSDU Region is defined as an independent and highly available geographical deployment of the full O...**Objective:**
- This requirement is to ensure OSDU data platform can support highly available multi-region/geographical deployment.
An OSDU Region is defined as an independent and highly available geographical deployment of the full OSDU design. It provides full functionality and there is no need for deploying multiple OSDU regions for high availability or disaster recovery requirements. Strict latency, data sovereignty or local legislation requirements may result into the need for additional OSDU deployments. OSDU deployments are preferably public cloud based. In situation where in-country OSDU deployment is required and no public cloud region is available, physical edge capabilities from the public cloud provider will be used. In any case, the exposed OSDU APIs deployed in the different OSDU regions will provide identical functionality.
**OSDU Regions**
An OSDU Region is an independent and complete deployment of all infrastructure and application services required to provide OSDU Data Platform (DP) services. Whilst every OSDU Region will have a homogeneous DP service deployment, a few types of OSDU regions can be identified:
- “*OSDU Standard Hosted Region*”: This is the common type of OSDU Region and will host all data platform services, including security, ingest, logging and monitoring. Platform, application and workflow services will be deployed based on need in this standard OSDU Region.
- “*OSDU Central Region*”: One of the standard OSDU regions will be assigned as a central region and will be hosting the development, integration test and performance test environments and Continuous Integration (CI)/ Continuous Delivery (CD) services. If required, it may host a central logging service. It will also host global OSDU application.
- “*OSDU Admin Region*”: One of the standard OSDU regions will be assigned as an admin region and this is a configured parameter in the OSDU metadata, namely the 'Admin Management' parameters. Subsurface Master Data System (SMDS) Master and Reference Data as well as OSDU management parameters stored in SMDS can only be updated in this configured OSDU Admin Region. All Admin APIs are available in all OSDU regions, though the call will be rejected (or redirected) if the API is not hosted in the OSDU Admin Region.
- “*OSDU In-Country Region*”: When public cloud infrastructure cannot be leveraged to deploy an OSDU Region for data sovereignty or latency reasons, an in-country OSDU deployment takes place with the consideration of incurring least management and operating overhead. Public cloud edge capabilities will be leveraged to most possible extent to increase the consistency and lower the overhead. The closest “OSDU Standard Region” will be configured as a proxy for in-country region's Subsurface Work Product Services (SWPS) metadata represent files within the in-country OSDU Region and providing home region replication.
List of OSDU Regions, and the identification of the Central and Admin OSDU Region will be part of the SMDS Master Data and will be administered as part of the Admin service.
M1 - Release 0.1Stephen Whitley (Invited Expert)Hrvoje MarkovicFerris ArgyleRaj KannanDania Kodeih (Microsoft)JoeStephen Whitley (Invited Expert)https://community.opengroup.org/osdu/platform/home/-/issues/15Wellbore data object2020-03-25T12:49:43ZDror DahanWellbore data objectProvide CRU APIs for the Wellbore data object Provide CRU APIs for the Wellbore data object M1 - Release 0.1Dror DahanDror Dahan2020-06-01https://community.opengroup.org/osdu/platform/home/-/issues/16Logset Data object2020-03-25T12:49:23ZDror DahanLogset Data objectProvide CRU APIs to manipulate the Logset data objectProvide CRU APIs to manipulate the Logset data objectM1 - Release 0.1Dror DahanDror Dahan2020-06-01https://community.opengroup.org/osdu/platform/home/-/issues/17Log Data object2020-03-25T12:48:23ZDror DahanLog Data objectProvide various APIs to manipulate Log data:
The specific APIs will be listed shortly.
Provide various APIs to manipulate Log data:
The specific APIs will be listed shortly.
M1 - Release 0.1Dror DahanDror Dahan2020-06-01https://community.opengroup.org/osdu/platform/home/-/issues/18[Platform] Move common code base to GitLab2022-08-23T13:29:45ZStephen Whitley (Invited Expert)[Platform] Move common code base to GitLabMigrate from Azure DevOps (code) and internal gitlab (data models, data) to community gitlab for R3 development.
Move the Core services for Legal and Entitlements (4 providers) ported in Release 2 from ADO to GitLab
- System Services
...Migrate from Azure DevOps (code) and internal gitlab (data models, data) to community gitlab for R3 development.
Move the Core services for Legal and Entitlements (4 providers) ported in Release 2 from ADO to GitLab
- System Services
- [x] Core Common
- [x] AWS Lib
- [x] Azure Lib
- [x] GCP Lib
- [x] IBM Lib
- [x] Storage
- [x] Search
- [x] Indexer
- [x] indexer queue
- Security and Compliance
- [x] Legal
- [x] AWS Entitlement
- [x] AZure Entitlement
- [x] GCP Entitlement
- [x] IBM Entitlement
Participants:
- @dkodeih, MSFT
- @fargyle, GCP
- @babeal, AWS
- @wladmirf. IBM
See [Code Freeze](https://community.opengroup.org/osdu/documentation/-/wikis/OSDU-R2-code-freeze) ActivitiesM1 - Release 0.1David Diederichd.diederich@opengroup.orgethiraj krishnamanaiduFerris ArgyleDania Kodeih (Microsoft)Wladmir FrazaoJoeBrandt BealDavid Diederichd.diederich@opengroup.org2020-05-29https://community.opengroup.org/osdu/platform/home/-/issues/19Upgrade Indexer-queue from App Engine Task Queues to Cloud Tasks2021-06-16T22:20:04ZFerris ArgyleUpgrade Indexer-queue from App Engine Task Queues to Cloud TasksThis service is currently dependent on Task Queues, which are [no longer recommended](https://cloud.google.com/appengine/docs/standard/java/taskqueue).
This will require regression testing since Cloud Tasks and Task Queues had [differen...This service is currently dependent on Task Queues, which are [no longer recommended](https://cloud.google.com/appengine/docs/standard/java/taskqueue).
This will require regression testing since Cloud Tasks and Task Queues had [different design briefs](https://cloud.google.com/tasks/docs/migrating), and will have potentially different behaviours for SLB's use case.ethiraj krishnamanaiduDmitriy Rudkoethiraj krishnamanaiduhttps://community.opengroup.org/osdu/platform/home/-/issues/20OSDU Data Platform Documentation2022-09-15T23:49:36ZStephen Whitley (Invited Expert)OSDU Data Platform DocumentationOSDU Data Platform Documentation
- [ ] OSDU System Architecture and Design
- [ ] Service Provider API Standards for OSDU (cloud-vendor specific)OSDU Data Platform Documentation
- [ ] OSDU System Architecture and Design
- [ ] Service Provider API Standards for OSDU (cloud-vendor specific)M1 - Release 0.12020-07-31https://community.opengroup.org/osdu/platform/home/-/issues/21Tag platform projects to capture the migration and validation of R2 code to G...2022-08-23T13:29:44ZStephen Whitley (Invited Expert)Tag platform projects to capture the migration and validation of R2 code to GitLabWe need to tag the R3 code at the point of validation migration from ADOWe need to tag the R3 code at the point of validation migration from ADOM1 - Release 0.1David Diederichd.diederich@opengroup.orgethiraj krishnamanaiduDavid Diederichd.diederich@opengroup.org2020-05-15https://community.opengroup.org/osdu/platform/home/-/issues/22Definition of Done for R3 Clarification2022-09-15T23:49:36ZDania Kodeih (Microsoft)Definition of Done for R3 ClarificationWhat is the meaning of "at runtime" in this page: https://community.opengroup.org/osdu/platform/home/-/wikis/Planning/R3/DoneWhat is the meaning of "at runtime" in this page: https://community.opengroup.org/osdu/platform/home/-/wikis/Planning/R3/DoneStephen Whitley (Invited Expert)Stephen Whitley (Invited Expert)https://community.opengroup.org/osdu/platform/home/-/issues/29Java 8 Upgrade2021-06-16T22:20:02ZBrandt BealJava 8 UpgradeRelease 2.0