Home issueshttps://community.opengroup.org/osdu/platform/system/home/-/issues2022-06-22T17:17:14Zhttps://community.opengroup.org/osdu/platform/system/home/-/issues/68Automatically generate Open API spec from pipeline2022-06-22T17:17:14ZChris ZhangAutomatically generate Open API spec from pipelineThe Open API specs are now together with service source code in different repos. However, the specs are not generated automatically, and it brings potential risks of consistency between the API spec and source code. We need a reliable me...The Open API specs are now together with service source code in different repos. However, the specs are not generated automatically, and it brings potential risks of consistency between the API spec and source code. We need a reliable mechanism to generate API spec through pipeline and publish them into a central place. In this way, the API spec is always in sync with code, and users can navigate to the proper API spec for certain service.David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/home/-/issues/44Batch update user roles2021-06-16T22:20:11ZChris ZhangBatch update user rolesThis was discussed from the linked issue.This was discussed from the linked issue.https://community.opengroup.org/osdu/platform/system/home/-/issues/46Consolidating Http Clients used in OSDU services2021-06-16T22:20:10ZKishore BattulaConsolidating Http Clients used in OSDU servicesTo make calls to external services in OSDU two http clients are being used
- [IUrlFetchService](https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/blob/master/src/main/java/org/opengroup/osdu/core/common/http/...To make calls to external services in OSDU two http clients are being used
- [IUrlFetchService](https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/blob/master/src/main/java/org/opengroup/osdu/core/common/http/IUrlFetchService.java) - [Implementation](https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/blob/master/src/main/java/org/opengroup/osdu/core/common/http/UrlFetchServiceImpl.java)
- [IHttpClient](https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/blob/master/src/main/java/org/opengroup/osdu/core/common/http/IHttpClient.java) - [Implementation](https://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/blob/master/src/main/java/org/opengroup/osdu/core/common/http/HttpClient.java)
HttpClient is not a spring component and it is instantiated every time HttpClient needs to be used.
Below are some of the usages of both the clients
- https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/provider/storage-gcp/src/main/java/org/opengroup/osdu/storage/provider/gcp/credentials/StorageCredential.java#L56
- https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/provider/storage-azure/src/main/java/org/opengroup/osdu/storage/provider/azure/simpledelivery/integration/searchservice/SearchServiceFacade.java#L64
- https://community.opengroup.org/osdu/platform/system/search-service/-/blob/master/search-core/src/main/java/org/opengroup/osdu/search/smart/models/AttributeCollection.java#L71
- https://community.opengroup.org/osdu/platform/system/indexer-service/-/blob/master/indexer-core/src/main/java/org/opengroup/osdu/indexer/service/StorageServiceImpl.java#L63
These 2 http clients should be consolidated into single http client. The consolidated HttpClient must be a spring component and can be autowired at other places.
Maintaining one http client is easier to manage in longer term. Any enhancements going further can be made in only one client.https://community.opengroup.org/osdu/platform/system/home/-/issues/62Documentation Updates2024-01-11T12:37:38ZStephen Whitley (Invited Expert)Documentation UpdatesChris,
We need to follow up on Service documentation and **Open API** Specs for
- Entitlement services (Each CSP has their own implementation )
- the new E&O
- Delivery Service
- File Services and any extensions of such - dataset serv...Chris,
We need to follow up on Service documentation and **Open API** Specs for
- Entitlement services (Each CSP has their own implementation )
- the new E&O
- Delivery Service
- File Services and any extensions of such - dataset service
- etc.
Basically, anything that was developed new in Open Source needs to conform to the same structure as the contributed services.
Focus on the Open API spec - and see what drafts you can have by Nov 18th so it can be referred to be the conformance docs for review. Everyone knows the services will evolve, but the first pass is structurally complete documentation.
---
Still looking at gaps and we seem to be missing the docs for Unit and CRS. These were early services that were contributed before the docs folder structure was in place.
Thanks.Chris ZhangChris Zhanghttps://community.opengroup.org/osdu/platform/system/home/-/issues/67Elasticsearch version upgrade2021-03-11T04:38:52Zethiraj krishnamanaiduElasticsearch version upgradeCurrent Version
- Elastic Server: 6.8.1
- Elastic Client version(OSDU Indexer service): 6.6.1
Proposed Version upgrade
* Elastic Server: 7
* Elastic Client version(OSDU Indexer service): 7
we need to upgrade the client and ela...Current Version
- Elastic Server: 6.8.1
- Elastic Client version(OSDU Indexer service): 6.6.1
Proposed Version upgrade
* Elastic Server: 7
* Elastic Client version(OSDU Indexer service): 7
we need to upgrade the client and elastic server version, this would require the following changes...
* Update the Indexer service, code change + lib version upgrade.
* Upgraded Elastic server in all clouds(AWS, Azure, Google, and IBM..etc).
## Updates:
- MRs for Indexer and Search service changes are created and published
- New version of Elastic Search JDK **7.8.1**
## Important:
CSPs needs to plan migration of indexes on a new version of Elastic.
There are several options:
- Move indexes from instance Elastic 6 to instance of Elastic 7
- Reload data
- Do reindexM1 - Release 0.1ethiraj krishnamanaiduDmitriy Rudkoethiraj krishnamanaidu2021-01-25https://community.opengroup.org/osdu/platform/system/home/-/issues/29Label after GA merge v0.3.02020-07-02T18:56:14ZStephen Whitley (Invited Expert)Label after GA merge v0.3.0M1 - Release 0.1David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.org2020-06-29https://community.opengroup.org/osdu/platform/system/home/-/issues/14Need JNI layer code for OpenVDS Driver2021-06-16T22:20:21ZStephen Whitley (Invited Expert)Need JNI layer code for OpenVDS DriverIn order to use the OpenVDS driver from Java based software, we need some JNI code. The current OpenVDS driver software provides C++ code and Python bindings only.
More info about JNI can be found at this link: https://en.wikipedia.org...In order to use the OpenVDS driver from Java based software, we need some JNI code. The current OpenVDS driver software provides C++ code and Python bindings only.
More info about JNI can be found at this link: https://en.wikipedia.org/wiki/Java_Native_Interface
Impact: INT is using Java based code for our backend implementation.https://community.opengroup.org/osdu/platform/system/home/-/issues/43Notification service - Move IGoogleServiceAccount under SPI2020-12-14T21:36:24ZChris ZhangNotification service - Move IGoogleServiceAccount under SPIhttps://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/11https://community.opengroup.org/osdu/platform/system/notification/-/merge_requests/11https://community.opengroup.org/osdu/platform/system/home/-/issues/13Open VDS driver needs support for signed URL2021-06-16T22:20:22ZStephen Whitley (Invited Expert)Open VDS driver needs support for signed URLThe open VDS driver needs to support opening a dataset via a signed URL. This is the use case which is needed for OSDU R2. Currently, we believe the driver uses cloud user credentials which will not pass a security audit review (per Joe ...The open VDS driver needs to support opening a dataset via a signed URL. This is the use case which is needed for OSDU R2. Currently, we believe the driver uses cloud user credentials which will not pass a security audit review (per Joe N)
[Note: edited this issue on March 31 to apply to the open VDS driver instead of the commercial VDS driver]https://community.opengroup.org/osdu/platform/system/home/-/issues/16Relating horizons to seismic volumes requires workaround2021-06-16T22:20:19ZStephen Whitley (Invited Expert)Relating horizons to seismic volumes requires workaroundSeismic horizons are related to the seismic volume(s) through SeismicTraceDataID, srn:work-product-component/SeismicTraceData:[^:]+:[0-9]*$". The value of the SeismicTraceDataID is generated at ingestion. The value will be different ...Seismic horizons are related to the seismic volume(s) through SeismicTraceDataID, srn:work-product-component/SeismicTraceData:[^:]+:[0-9]*$". The value of the SeismicTraceDataID is generated at ingestion. The value will be different for each cloud provider, so the load manifest for horizons can not be populated with the value in advance. A workaround is to prepare the manifests after loading seismic volumes and recording the SeismicTraceDataIDshttps://community.opengroup.org/osdu/platform/system/home/-/issues/1[System/Core] Notification service2020-07-08T19:47:13ZChris Zhang[System/Core] Notification serviceM1 - Release 0.1ethiraj krishnamanaiduChris ZhangMichael Cleminsonethiraj krishnamanaiduhttps://community.opengroup.org/osdu/platform/system/home/-/issues/32[System/Core] Registration2020-07-08T19:48:04ZStephen Whitley (Invited Expert)[System/Core] RegistrationM1 - Release 0.1ethiraj krishnamanaiduethiraj krishnamanaiduhttps://community.opengroup.org/osdu/platform/system/home/-/issues/4[System] Merge changes to the core services2020-07-02T19:04:00ZStephen Whitley (Invited Expert)[System] 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.1ethiraj krishnamanaiduStephen Whitley (Invited Expert)Chris Zhangethiraj krishnamanaidu2020-07-03