Server Tracking
26 views
Skip to first unread message
joe hobson
Oct 1, 2012, 2:15:11 PM10/1/12
to learnin...@googlegroups.com
I was going through setting up authentication on the sandbox and production node(s) this morning so that I can be sure to have everything in place for some new publish requests coming down the pipe. It looks like the public nodes that are running may have changed. Can someone verify which nodes are still running and will be supported for the next few months? This document is supposed to list them but is probably outdated: https://docs.google.com/spreadsheet/ccc?key=0AtOSW7g7E8Y5dFRsSW5HRFlSalFpZjFvMmVKNGdpd2c#gid=0
Having an up-to-date list of nodes and which release they're running would be very helpful. That doc is linked from the full Documentation list. If there's a better document to reference, let's update our links. thanks. ... .joe
-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
joe hobson, owner / director of technology & innovation
Navigation North Learning Solutions LLC
Jim Klo
Oct 1, 2012, 2:31:08 PM10/1/12
to <learningreg-dev@googlegroups.com>
I've updated with what I know at this point in time.
- Jim
Jim Klo
Senior Software Engineer
Center for Software Engineering
SRI International
t. @nsomnac
--
---
This message is posted from the Google Groups "Learning Registry Developers List" group.
To post: learnin...@googlegroups.com
To unsubscribe: learningreg-d...@googlegroups.com
joe hobson
Oct 2, 2012, 4:10:51 PM10/2/12
to learnin...@googlegroups.com
Thanks for the update.
node02.public.learningregistry.net is listed in the sheet but does not appear to be running. Is it just in hibernation?
Additionally, in troubleshooting errors on Brokers this week, we found issues accessing the production node using SSL. I haven't had great luck recreating what my one of my developer's was seeing (connection refused on publish when using SSL), but it looks like some of the configuration has probably changed on the public node. Is node01 requiring SSL to publish now? Doesn't seem to be, though I'm almost positive it was before.
-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
joe hobson, owner / director of technology & innovation
Navigation North Learning Solutions LLC
Jim Klo
Oct 2, 2012, 4:36:18 PM10/2/12
to <learningreg-dev@googlegroups.com>
I'm checking node02 now…
I'll take a look at SSL issues, it seems the config is mucked up… I'll take a look and see if I can fix. You should be able to connect via HTTP.
- Jim
Jim Klo
Senior Software Engineer
Center for Software Engineering
SRI International
t. @nsomnac
On Oct 2, 2012, at 1:10 PM, joe hobson <joeh...@gmail.com>
wrote:
Jim Klo
Oct 2, 2012, 6:13:46 PM10/2/12
to <learningreg-dev@googlegroups.com>
node02 should be back up.
I believe we removed the SSL requirement; the only thing that changed was that we now handle Basic Auth within the LR code instead of within NGINX. If you had a publishing account previously, you need to recreate it at:
Sign in with Persona, then set a password to enable Basic Auth (this is not your Persona password!!!) or you may switch to OAuth and use the provided token and secret.
- Jim
Jim Klo
Senior Software Engineer
Center for Software Engineering
SRI International
t. @nsomnac
On Oct 2, 2012, at 1:10 PM, joe hobson <joeh...@gmail.com> wrote:
Reply all
Reply to author
Forward
0 new messages