search

nielsboecker / HoloRepository-Core

A system for transforming medical imaging studies into holograms, storing them in the cloud and providing them to other systems.
GNU Affero General Public License v3.0
7 stars 8 forks source link

HoloRepository Demo Setup #60

Closed boonwj closed 5 years ago

boonwj commented 5 years ago

This PR is for the creation of a HoloRepository Demo setup.

It includes the steps, demo data and changes to the tools necessary to set it up. The following provides an overall view of what is included in.

TODO: UI end is not tested with the demo data. @fanbomeng97 or @nbckr, to look into it

boonwj commented 5 years ago

Oh yes, the demo FHIR EHR service is currently spun up as https://holoehr-demo.azurewebsites.net/

boonwj commented 5 years ago

Sorry, just noticed the comments here. It seems the error with the accessor and comments on the poor data is due to the accessor being configured to the old blobstorage.

I will post the configurations required to connect to the accessor in teams.

nielsboecker commented 5 years ago

Alright. I cannot get my React dev server to run atm, but I actually had the same 500 when I did the PR for Fanbo, and then I got valid data when I changed the config to the demo endpoint. So should be fine.

nielsboecker commented 5 years ago

image Hologram titles are better, but I would prefer them not having the "Hologram" prefix (minor issue).

The other thing is that I'm still getting the 500 though, when trying the download endpoint. Btw, is it okay to test the delete endpoint or will it mess you up on your end? :)

http://51.141.224.131/api/v1/holograms/h101/download

=> 
{
"errorCode": "500",
"errorMessage": "-> github.com/Azure/azure-storage-blob-go/azblob.newStorageError, /go/src/github.com/Azure/azure-storage-blob-go/azblob/zc_storage_error.go:42\n===== RESPONSE ERROR (ServiceCode=BlobNotFound) =====\nDescription=The specified blob does not exist.\nRequestId:d483c229-301e-0016-74e8-5b48b0000000\nTime:2019-08-26T08:31:22.2762751Z, Details: \n   Code: BlobNotFound\n   GET https://holoblobdemo.blob.core.windows.net/holograms/h101?timeout=61\n   Authorization: REDACTED\n   User-Agent: [Azure-Storage/0.7 (go1.12.7; linux)]\n   X-Ms-Client-Request-Id: [f008fdde-0528-461e-45f3-bd5e75604e57]\n   X-Ms-Date: [Mon, 26 Aug 2019 08:31:22 GMT]\n   X-Ms-Version: [2018-11-09]\n   --------------------------------------------------------------------------------\n   RESPONSE Status: 404 The specified blob does not exist.\n   Content-Length: [215]\n   Content-Type: [application/xml]\n   Date: [Mon, 26 Aug 2019 08:31:21 GMT]\n   Server: [Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0]\n   X-Ms-Error-Code: [BlobNotFound]\n   X-Ms-Request-Id: [d483c229-301e-0016-74e8-5b48b0000000]\n   X-Ms-Version: [2018-11-09]\n\n\n"
}
boonwj commented 5 years ago

image Hologram titles are better, but I would prefer them not having the "Hologram" prefix (minor issue).

The other thing is that I'm still getting the 500 though, when trying the download endpoint. Btw, is it okay to test the delete endpoint or will it mess you up on your end? :)

http://51.141.224.131/api/v1/holograms/h101/download

=> 
{
"errorCode": "500",
"errorMessage": "-> github.com/Azure/azure-storage-blob-go/azblob.newStorageError, /go/src/github.com/Azure/azure-storage-blob-go/azblob/zc_storage_error.go:42\n===== RESPONSE ERROR (ServiceCode=BlobNotFound) =====\nDescription=The specified blob does not exist.\nRequestId:d483c229-301e-0016-74e8-5b48b0000000\nTime:2019-08-26T08:31:22.2762751Z, Details: \n   Code: BlobNotFound\n   GET https://holoblobdemo.blob.core.windows.net/holograms/h101?timeout=61\n   Authorization: REDACTED\n   User-Agent: [Azure-Storage/0.7 (go1.12.7; linux)]\n   X-Ms-Client-Request-Id: [f008fdde-0528-461e-45f3-bd5e75604e57]\n   X-Ms-Date: [Mon, 26 Aug 2019 08:31:22 GMT]\n   X-Ms-Version: [2018-11-09]\n   --------------------------------------------------------------------------------\n   RESPONSE Status: 404 The specified blob does not exist.\n   Content-Length: [215]\n   Content-Type: [application/xml]\n   Date: [Mon, 26 Aug 2019 08:31:21 GMT]\n   Server: [Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0]\n   X-Ms-Error-Code: [BlobNotFound]\n   X-Ms-Request-Id: [d483c229-301e-0016-74e8-5b48b0000000]\n   X-Ms-Version: [2018-11-09]\n\n\n"
}

This is because the accessor that is currently deployed is different from the one in this branch. It does not add the '.glb' extension when looking for holograms in the blobstorage.