search

terraref / computing-pipeline

Pipeline to Extract Plant Phenotypes from Reference Data
BSD 3-Clause "New" or "Revised" License
24 stars 13 forks source link

Point utilities to terraref.ncsa.illinois.edu/* #56

Closed dlebauer closed 8 years ago

dlebauer commented 8 years ago

Currently we are hosting two instances of BETYdb on pecandev.igb.illinois.edu. @robkooper is setting them up on the Nebula instance of OpenStack (#24, #65). Once he reports the ip addresses, We can point the production instances of Clowder and Bety to these URLs:

ghost commented 8 years ago

help+neteng host at NCSA instead of Github (nebula as vm?) Talk to Bill Glick about redirects

dlebauer commented 8 years ago

@robkooper thank you for getting the redirects working, but the redirects fail for API calls, e.g. using terraref.ncsa.illinois.edu/betydb/search?genus=Miscanthus should work but it just redirects to the pecandev url.

gsrohde commented 8 years ago

It’s https://www.betydb.org/api/beta/citations/50, and you have to add a query string with key=. I’ve thought about removing the requirement for a key so that you could easily view the result in a browser once logged in; or, if using curl, you could use the -u username:password option instead of a key. Though, actually, if you are logged in, even a bad key (or just ?key=) will work.

Regarding the API docs, it does refer to the path GET /api/beta/citations/:id, so it should be clear that you need a forward slash after citations. What’s not clear, perhaps because this automatically-generated documentation is too “Rails-developer-centric”, is that the placeholder of the id parameters is called “:id”, so that when you replace this with a number, you should be replacing the colon as well.

From: David LeBauer notifications@github.com<mailto:notifications@github.com> Reply-To: terraref/computing-pipeline reply@reply.github.com<mailto:reply@reply.github.com> Date: Wednesday, May 4, 2016 at 10:20 AM To: terraref/computing-pipeline computing-pipeline@noreply.github.com<mailto:computing-pipeline@noreply.github.com> Cc: Scott Rohde srohde@illinois.edu<mailto:srohde@illinois.edu>, Mention mention@noreply.github.com<mailto:mention@noreply.github.com> Subject: Re: [terraref/computing-pipeline] Point utilities to terraref.ncsa.illinois.edu/* (#56)

@robkooperhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_robkooper&d=CwMCaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=oJsSpSeia9tFOpzHxC6EpYUew62qA42qdvjRrEjQywI&m=kzu7Ez0X3KC9Qd3OqSj6iLTBDSWaD1Ey5390aMMSZXA&s=g9l-NlX2gYa92uZcEw73xEO8WKurcuGjkAiMvTtzVkE&e= thank you for getting the redirects working, but the redirects fail for API calls, e.g. using terraref.ncsa.illinois.edu/betydb/search?genus=Miscanthus should work but it just redirects to the pecandev url.

@gsrohdehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_gsrohde&d=CwMCaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=oJsSpSeia9tFOpzHxC6EpYUew62qA42qdvjRrEjQywI&m=kzu7Ez0X3KC9Qd3OqSj6iLTBDSWaD1Ey5390aMMSZXA&s=2wR5yTAdSQ92Z7f41kcWqSPpdVMx0MGNWNEUuY18ATM&e= it is not clear from the online docs (betydb.org/api/docs) how to construct an API call from the current api docs. e.g. shouldn't https://www.betydb.org/api/beta/citations:50https://urldefense.proofpoint.com/v2/url?u=https-3A__www.betydb.org_api_beta_citations-3A50&d=CwMCaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=oJsSpSeia9tFOpzHxC6EpYUew62qA42qdvjRrEjQywI&m=kzu7Ez0X3KC9Qd3OqSj6iLTBDSWaD1Ey5390aMMSZXA&s=7_0tH66B77bXvraSCM1Ruh4zenIEZ5umbl5Xd-Z3ML8&e= work?

max-zilla commented 8 years ago

Can this be closed now?

dlebauer commented 8 years ago

@max-zilla no, please do not close. Two urls for the BETYdb instances do redirect to pecandev.igb.illinois.edu, but we still need to

  1. [x] migrate BETYdb from pecandev.igb.illinois.edu to OpenStack on Nebula or Roger
  2. [ ] have daily backups of both instances, (#65)
  3. [ ] have the backups from the /bety instance added to the load.bety.sh scripts that are used for syncs so that the data we generate can be ingested by other teams. (#65)
  4. [x] the API endpoints on both http://terraref.ncsa.illinois.edu/bety and http://terraref.ncsa.illinois.edu/bety-test need to function
dlebauer commented 8 years ago

bety --> bety6 --> https://terraref.ncsa.illinois.edu/bety --> http://141.142.209.94/bety bety-test --> bety7 --> https://terraref.ncsa.illinois.edu/bety-test --> http://141.142.209.95/bety-test

dlebauer commented 8 years ago

closing this: remaining issues of backups are addressed in #65