919586 - Host the Summit App

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Engagement, task)

Description

[:Harald Kirschner :digitarald]

In bug 918949 jakem advises strongly against using stackato for hosting as they offer no availability or performance guarantee. Production-ready stackato instances are planned but might not be ready. Pardon the urgency, only 2 weeks are left to get this hosted and tested.

Our current requirements for hosting https://github.com/digitarald/firehug are  node.js 0.10.x and redis.

Bug 917938 tracks the security review.

Comment 1

[:Harald Kirschner :digitarald]

Jake, can you escalate this to whoever could help with this?

Comment 2

[Jason Crowe [:jd]]

Jake is on PTO this week but webops are aware of it and have started the process.

Comment 3

[Jason Crowe [:jd]]

The vm in under way and I wanted to check in and try to get deployment directions from you. I can intuit a git checkout and see the requirement for node and redis but need to know anything beyond that. Any Apache vhost requirements (rewrites etc)? Will this app require any netflows (AKA does it talk to any other sites or services)?  Database requirement? Cron jobs? Anything else you can think to tell me about it?

Thanks

Comment 4

[:Harald Kirschner :digitarald]

No Apache rewrites
No actual cron jobs, controlled by node.js: https://github.com/digitarald/firehug/blob/master/bin/index.js

External API requests:
https://spreadsheets.google.com
https://mozillians.org

The site will be mapped to summit.mozilla.org a few days before the event and has to be served exclusively via HTTPS.

Comment 5

[Jen Fong-Adwent [:ednapiranha]]

We also pull js files from Angular's CDN at //code.angularjs.org/1.2.0-rc.2/*.js

Comment 6

[Jason Crowe [:jd]]

Can I get the values for the local.json file?

Basically I think i just need the api app and keys.

Thanks

Comment 7

[Jason Crowe [:jd]]

Also if you are on a VPN you should be able to hit the web server directly here:

http://summitapp1.webapp.scl3.mozilla.com:5000/

You will notice an error which I will need to know how to solve for you.

Thanks

Comment 8

[:Harald Kirschner :digitarald]

(In reply to Jason Crowe [:jd] from comment #6)
> Can I get the values for the local.json file?
> 
> Basically I think i just need the api app and keys.
> 
> Thanks

Email sent.

Comment 9

[Jason Crowe [:jd]]

I have those settings in the file now. The previous error remains. Any idea how to solve it?

Thanks

Comment 10

[Jen Fong-Adwent [:ednapiranha]]

Jason, I just tried accessing http://summitapp1.webapp.scl3.mozilla.com:5000/ while on VPN but the page never loads - just keeps hanging.

Comment 11

[:Harald Kirschner :digitarald]

Just send the latest local.json. Have you been able to update the server, Jason?

Comment 12

[Jason Crowe [:jd]]

Harald,
I am not sure what you are asking. I deployed the app the other day and have updated the json file each time you have sent it. By "update the app" is this what you mean or do you need a git pull from some branch?

Jen,
Which VPN are you on? There may be some issue depending on that. I will work on getting an IP and getting this served from a load balancer cluster today.

Comment 13

[Jen Fong-Adwent [:ednapiranha]]

Hey Jason:

I'm on Mozilla-MV-Office through Viscosity.

Comment 14

[:Harald Kirschner :digitarald]

I also can't access the app, I am in the MV office and tried yesterday from home using Viscocity. Both times the connection timed out.

Comment 15

[Jason Crowe [:jd]]

So to avoid the entire VPN issue I just set up all the load balancer stuff. This is currently running on a VIP called
https://summit-zlb.vips.scl3.mozilla.com

I created a port 80 VIP (http) and set up a server side redirect to 443 (https).

I also generated (purchased NOT self signed) an SSL cert for summit.m.o and installed it on the 443 VIP. Now this cert is only good for summit.m.o which of course is not being served here yet. So you will need to access the VIP directly for now and simply accept the "untrusted" connection (if you view the details you will note it will tell you the reason as I stated above).

Once this app is ready to go live you will need to file a bug requesting that the current DNS record for summit.m.o be changed to CNAME to the above named VIP (summit.mozilla.org IN CNAME summit-zlb.vips.scl3.mozilla.com).

Anyhow, probably all you really care about now is that you can access the app now via the VIP above after accepting the security trust.

You will note the same error that has persisted on the server since I initially set it up (TypeError: Cannot read property 'email' of undefined).

Finally, I still do not know what Harald meant by "Have you been able to update the server", please elaborate.

Comment 16

[:Harald Kirschner :digitarald]

(In reply to Jason Crowe [:jd] from comment #15)
> Finally, I still do not know what Harald meant by "Have you been able to
> update the server", please elaborate.

When have you pulled the latest version from github and pushed it to the server? We just started beta testing, so the code is nearing stable release. Can you please check if the github master works?

Comment 17

[Jason Crowe [:jd]]

After checkout HEAD on starting the app I get the following error:

module.js:340
    throw err;
          ^
Error: Cannot find module 'time'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (/data/www/summit.mozilla.org/summit/app.js:13:12)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.runMain (module.js:492:10)

Comment 18

[Jason Crowe [:jd]]

After running the install again I got the time module. Now the app started and is generating a new error on the web interface about:


TypeError: Cannot read property 'user' of undefined

Comment 19

[Jason Crowe [:jd]]

/data/www/summit.mozilla.org/summit/bin/getSchedule:111
    throw new Error('Error reading spreadsheets data: ' + err);
          ^
Error: Error reading spreadsheets data: Error: 139697246353184:error:0607907F:digital envelope routines:EVP_PKEY_get1_RSA:expecting an rsa key:../deps/openssl/openssl/crypto/evp/p_lib.c:288:

    at /data/www/summit.mozilla.org/summit/bin/getSchedule:111:11
    at module.exports (/data/www/summit.mozilla.org/summit/node_modules/google-spreadsheets/lib/spreadsheets.js:70:11)
    at Request.getFeed [as _callback] (/data/www/summit.mozilla.org/summit/node_modules/google-spreadsheets/lib/spreadsheets.js:41:13)
    at Request.init.self.callback (/data/www/summit.mozilla.org/summit/node_modules/request/request.js:129:22)
    at Request.EventEmitter.emit (events.js:96:17)
    at ClientRequest.Request.init.self.clientErrorHandler (/data/www/summit.mozilla.org/summit/node_modules/request/request.js:239:10)
    at ClientRequest.EventEmitter.emit (events.js:96:17)
    at CleartextStream.socketErrorListener (http.js:1394:9)
    at CleartextStream.EventEmitter.emit (events.js:96:17)
    at SecurePair.error (tls.js:963:22)

Comment 20

[:Harald Kirschner :digitarald]

Jason, could Jen answer all your questions? Did updating node to 0.10 fix the issues?

Comment 21

[Jason Crowe [:jd]]

Upgraded node and reinstalled everything, the app is running and pulling down the schedule.

Let me know if you have any additional issues.

Please open a new bug for any new work (like new pushes) with specific instructions (like new package requirements etc...)

Will also need a new bug when you are ready for the DNS switch to go live.

Cheers

Comment 22

[Jason Crowe [:jd]]

Also we should remember to turn on the front end caching when this goes live. I left it disabled for now to speed up the testing process but will get far better performance with it on. All of this assuming you are setting proper cache headers of course :)

Comment 23

[Jason Crowe [:jd]]

Hi,

I am curious if we can remove the VM hosting this app now that the DNS has been pointed to the blog site?

Thanks

Comment 24

[:Harald Kirschner :digitarald]

Yes; it can all be removed.

Comment 25

[Jason Crowe [:jd]]

Thanks, I will update see it is removed.