Install phantomjs on simian and get it running about aqua HOT 19 CLOSED

Continuing discussion on the issue mentioned above (or is it?)

from aqua.

2016-10-03 12:42:28 MDT - Dylan CanfieldComments
Matt / Sam,
Unforutnately Phantomjs cannot be built on simian because the project does not support RHEL5, and never will.
ariya/phantomjs#12773

Nodejs (with npm) is installed under /usr/local/nodejs.

Is there anything else that I can help you with?

-Dylan

from aqua.

2016-10-05 10:22:42 MDT - Dylan CanfieldComments
Matt / Sam,
Given that PhantomJS won't work on RHEL5, is there an alternative piece of software that you would like to use on simian?

Regards,
Dylan Canfield
OIT - Shared Infrastructure Services

from aqua.

I haven't seen phantom alternatives that provide the functionality we would like.

Is there any way to upgrade GLIBCXX and GLIBC on RHEL5? (The phantomjs page says we can use the built binary if the system has GLIBCXX_3.4.9 and GLIBC_2.7, http://phantomjs.org/download.html )

Alternatively, what options do we have for upgrading simian to a later OS? Can simian run an VM that supports phantomjs minimum requirements?

Best Regards,
Sam

from aqua.

I feel like @markmorlino might have some thoughts here since he is going to be helping us think about the architecture for Simian as DR

from aqua.

@samreid feel perhaps it might be useful to talk with @markmorlino and explain the requirements

from aqua.

Greetings @markmorlino! The requirements for phantomjs are enumerated on the download page: http://phantomjs.org/download.html

What do you recommend? Please reassign to me after you comment.

from aqua.

@samreid can you also give context, I think understanding exactly the problem you want to solve would be helpful as well

from aqua.

We would like a headless browser engine (webkit or better) that can run in a continuous integration system to help us identify issues in our simulations via automated testing.

from aqua.

It's not going to be practical to upgrade glibc, RHEL locks you into versions of core system components like glibc. The way to get on a newer version is to upgrade the OS. They do backport and release some bug fixes and security patches from later versions but almost never new features/functionality which is most likely what phantomjs needs. It's probably possible to use a VM but that would be a short-sighted solution.

RHEL 5 EOL is currently set for March 31, 2017. The hardware seems reasonable and from what I understand is supportable by the vendor for a few more years.

I don't think it makes sense to continue on with it running RHEL5, considering the planned uses of Simian moving forward: log processing for production, DR site, CI, etc (I think there is more but I can't remember what).

My recommendation would be to upgrade it to RHEL7. It might be a bit of a headache right now but I think it will save time and frustration in the future

from aqua.

@markmorlino are you sure RHEL7 will provide phantom minimum requirements? What would the steps be for updating to RHEL7?

from aqua.

Yes, RHEL7 meets the minimum requirements for phantomjs.
It would be a complete re-installation of the operating system: document what is installed and running on the system, backup relevant configuration and data, install new OS, install and configure applications.

from aqua.

Note to self: ask OIT what would would be involved in an upgrade, is it a clean install or do we keep data?

from aqua.

@jonathanolson needs advance notice if we are wiping the system. @jonathanolson is also running a process (for half a month so far) that needs to be completed or terminated.

from aqua.

I emailed OIT:

Dylan,

It appears that like RHEL 5 End of Production 3 Phase is currently set for March 31, 2017, we are wondering what would be involved in an OS upgrade?
https://access.redhat.com/support/policy/updates/errata

Best Regards,
Sam

On hold until we receive a response.

from aqua.

2016-10-06 14:56:40 MDT - Dylan CanfieldComments
Ariel,
Yes, it is possible for your group to do the upgrade yourself. However, I did not mean to imply that we were unable or unwilling to manage a system for your automated testing framework on a newer OS. I wanted to get a discussion started to see how we could most effectively provide a solution that met your requirements. If "disaster recovery" is a requirement of this rebuild, that definitely rules out a new VM as we are currently unable to run VMs in multiple locations (though we are working on that capability).

Also, we do have multiple OIT data-centers where we could rack systems. What are your plans for the current figaro? Would you be interested in racking it over at SPSC and leveraging it for "disaster recovery"?

Orrie,
Given the desire to fall back to this system during periods of data center downtime, do you have any suggestions?

Regards,
Dylan Canfield

from aqua.

We will reassign this after we have a new server.

from aqua.

Bayes is being tracked here: https://github.com/phetsims/special-ops/issues/53

from aqua.

No need for phantom, Bayes is using Chrome headless, closing.

from aqua.