labnodepool1001.eqiad.wmnet has been setup as a proof of concept for Nodepool. @dduvall and @hashar have root access on it.
I think all the bits have been properly put in puppet now and it is time to reinstall the image and have it reconfigured solely via puppet.
There is a few blocking tasks though.
Potentially vacations will be a blocker. I have too look at the Debian packages available in apt.wikimedia.org since I think I have manually installed some ;-(
Will reinstall it with @Andrew on Wednesday 29th.
Gotta look at it tonight to figure out which .deb package might be missing, and prepare them for upload on apt.wm.o
Before rebuilding the system, I wanted to make sure all .deb package dependencies are on apt.wikimedia.org.
The Nodepool requirements.txt file list the python modules:
pbr>=0.6,!=0.7,<1.0 gear PyYAML python-jenkins paramiko>1.9.0 python-daemon>=2.0.4 extras statsd>=1.0.0,<3.0 apscheduler>=2.1.1,<3.0 sqlalchemy>=0.8.2,<0.9.0 pyzmq>=13.1.0,<14.0.0 python-glanceclient python-keystoneclient python-novaclient PyMySQL PrettyTable>=0.6,<0.8 six>=1.7.0 diskimage-builder voluptuous
We have some mismatches:
| Required | Jessie |
|---|---|
| statsd < 3.0 | python-statsd 3.0.1 |
| slqalchemy < 0.9.0 | python-sqlalchemy 0.9.8 |
| pyzmq < 14.0.0 | python-zmq 14.4.0 |
sqlalchemy and pyzmq are not an issue, I proposed a change upstream to soften the upper bound dependency ( https://review.openstack.org/#/c/173731/ ). The .deb package does not have the upper limit.
statsd is backward incompatible. We will need to bump Nodepool to include 5662105d (0.1.1-3-g5662105). Meanwhile I manually installed python-statsd 2.0.
I gathered all informations I needed. We can reimage the system.
I re-imaged labnodepool1001 and got a clean puppet run. Nice work! Hashar, you can verify that it's behaving adequately and then Chase or I will yank your root privs :)
Amazing thanks @Andrew . The daemon does not run right now because it depends on statsd 2.0 whereas Jessie has 3.0. Will try to get the patch backported tomorrow.
Kudos!