Upgrade to Node 0.10

[nicolaasmatthijs]

http://joyent.com/blog/announcing-the-latest-node-update

Also run a performance test as part of this to make sure that it doesn't slow things down.

[simong]

Might want to hold off on that till nodejs/node-v0.x-archive#5015 (comment) has been resolved.

[nicolaasmatthijs]

It looks like 0.10.1 has a partial solution, but the final solution won't be there until 0.10.2

[mrvisser]

We should hold off until 0.10.2.

The newest joyent base images ship with node 0.10.1 ATM. Our provisioning scripts now uninstall the bundled nodejs package, and then the puppet scripts will install 0.8.22.

The act of "upgrading to 0.10" should just be a matter of bumping up the nodejs version installed in the hilary module of the puppet-hilary production branch (as well as README.md fixes where needed) and testing the provisioning process.

[nicolaasmatthijs]

Assigning to Branden, but putting on hold.

[stuartf]

0.10.6 is available now, should this be marked as to fix

[nicolaasmatthijs]

Setting to To Fix, but keeping out of R1. This needs performance testing + some investigation on whether or not we can more efficiently use the streaming API.

[nicolaasmatthijs]

@mrvisser : Are there any outstanding tasks before this can be resolved?

[mrvisser]

We can move forward on it now that we've validated the crypto stuff no longer causes a severe degradation. We should:

• Run in QA and sanity check things like PP and Etherpad which don't get good coverage in performance tests. A 30min bug bash should do
• Look at the streaming API changes as mentioned to see if we're using any soon-to-be-deprecated stuff and switch those around

[simong]

node 0.10 is now running on release0 and has been merged into puppet-hilary@master. Can this be closed?

[mrvisser]

Upgraded in release and in production