Brief update about temporal platform expriment on AWS cloud service

[sch...@mozilla.com]

Hi all,

I created a AWS free account for setting the open mhealth infrastructure by docker. You can login the console from here with user/pw : EirTesting/EirTesting. There are 2 instances created already:
 - omh-shimmer : For 3rd party services authentication and convert medical data into common schema. You can link to the shimmer console here for service authentication and fetch the data.
 - open-mhealth-test: For data storage. Please see the document (in "Using the resource server"section) on open mhealth if you want to insert some fake user and data.

For connecting to the instance, you can use ssh client and connect to:
 EirTe...@ec2-52-88-215-185.us-west-2.compute.amazonaws.com
with password : mozillaproject

Please don't abuse the service since it's only the free account with very limited ability and bandwidth. We'll try to setup the infrastructure in another account in the future. It's a playground for testing the ability of open mhealth and I already encounter some issues. I'll summarize the problems later, but please give it a try if you can't wait :)

Steve

[sch...@mozilla.com]

Quick follow up for the problems I encountered:

 - In shimmer, we'll need the credentials for 3rd party data services for crawling data. In this testing shimmer I setup 2 credentials, one is for google fit and another for iHealth(and you can see these in shimmer settings console page). The problem in google's credential is I got error instead of the access token while in authentication process. And for iHeath credential it still need additional verification from the official site to complete the credential process. You can also add other 3rd party service in settings and fetch the data through console by yourself.

 - In the open mhealth storage part, user creation and requesting the access token should work right now, but data insertion/deletion will return invalid access error. Will try to figure it out recently.

Please feel free to ask question or give feedback!


sch...@mozilla.com於 2016年3月1日星期二 UTC+8下午6時24分21秒寫道：

Hi all,

I created an AWS free account for setting the open mhealth infrastructure by docker. You can login the console from here with user/pw : EirTesting/EirTesting. There are 2 instances created already:

 - omh-shimmer : For 3rd party services authentication and convert medical data into common schema. You can link to the shimmer console here for service authentication and fetch the data.
 - open-mhealth-test: For data storage. Please see the document (in "Using the resource server"section) on open mhealth if you want to insert some fake user and data.

For connecting to the instance, you can use ssh client and connect to:

 EirTesting@ec2-52-88-215-185.us-west-2.compute.amazonaws.com

[Kumar Rishav]

Hi Steve,

Thanks for the setting up the docker infrastructure. I was new to the Docker and Aws , so it took sometime to figure out.  Below are some of experiments i did with Fitbit and issue faced.

1. I tried with Fitbit and create credentials to test how it works. Here, i hosted a sample node app to fetch the data of Fitbit user.  visit :  http://52.33.238.194:8080/

2. Regarding running shimmer on docker, i followed this document, i got the console running on my localhost (as well as on my Ec2 instance) and in settings i filled the credentials for fitbit, but still i am unable to fetch the data. After entering the login details, it throws out this error. I was unable to figure from where this error is coming. Is it related to this: https://github.com/openmhealth/shimmer/blob/master/docker-compose.yml#L5

3. I  tried open-mhealth-test and was able to run the authorization & resource on docker  as per this document (in "Using the resource server"section) on open mhealth but couldn't figure out how to insert and fetch fake data.

Also, i had issue with changing host in docker-machine on linux but it was working fine on Windows (Docker Toolbox).

ultron@ultron-Inspiron-3537:~$ eval "$(docker-machine env default)"

bash: set: -g: invalid option

set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]

bash: set: -g: invalid option

set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]

bash: set: -g: invalid option

set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]

bash: set: -g: invalid option

set: usage: set [-abefhkmnptuvxBCHP] [-o option-name] [--] [arg ...]

Thanks

On Wednesday, March 2, 2016 at 2:09:37 PM UTC+5:30, sch...@mozilla.com wrote:

Quick follow up for the problems I encountered:

 - In shimmer, we'll need the credentials for 3rd party data services for crawling data. In this testing shimmer I setup 2 credentials, one is for google fit and another for iHealth(and you can see these in shimmer settings console page). The problem in google's credential is I got error instead of the access token while in authentication process. And for iHeath credential it still need additional verification from the official site to complete the credential process. You can also add other 3rd party service in settings and fetch the data through console by yourself.

 - In the open mhealth storage part, user creation and requesting the access token should work right now, but data insertion/deletion will return invalid access error. Will try to figure it out recently.

Please feel free to ask question or give feedback!


sch...@mozilla.com於 2016年3月1日星期二 UTC+8下午6時24分21秒寫道：

Hi all,

I created an AWS free account for setting the open mhealth infrastructure by docker. You can login the console from here with user/pw : EirTesting/EirTesting. There are 2 instances created already:
 - omh-shimmer : For 3rd party services authentication and convert medical data into common schema. You can link to the shimmer console here for service authentication and fetch the data.
 - open-mhealth-test: For data storage. Please see the document (in "Using the resource server"section) on open mhealth if you want to insert some fake user and data.

For connecting to the instance, you can use ssh client and connect to:

 EirTe...@ec2-52-88-215-185.us-west-2.compute.amazonaws.com

[sch...@mozilla.com]

Hi Kumar,

Great job and thanks for the feedbacks!

About the shimmer error, I think it might be service(Fitbit) related, and any error you faced in login process will cause you unable to fetch data. Since I didn't try Fitbit yet, maybe you could create an issue on shimmer's github repo? I can take a look when I have free time, but they(ohm team) must be much more familiar with shimmer than me. And about the docker machine environment problem, could you confirm that default docker machine is set on you Linux?

BTW Greg already issued a request for advanced AWS account with more functionality, we can move our work to that account once the request is approved and ready.

Thanks,
Steve.

On Tuesday, March 1, 2016 at 6:24:21 PM UTC+8, sch...@mozilla.com wrote:

Hi all,

I created a AWS free account for setting the open mhealth infrastructure by docker. You can login the console from here with user/pw : EirTesting/EirTesting. There are 2 instances created already:
 - omh-shimmer : For 3rd party services authentication and convert medical data into common schema. You can link to the shimmer console here for service authentication and fetch the data.
 - open-mhealth-test: For data storage. Please see the document (in "Using the resource server"section) on open mhealth if you want to insert some fake user and data.

For connecting to the instance, you can use ssh client and connect to:

 EirTesting@ec2-52-88-215-185.us-west-2.compute.amazonaws.com