We would need nodepool to craft specific images to boot instances from. First pass with Debian Jessie.
The minimum viable product is an image that boots on labs and that nodepool can ssh into to finish it is setup and thus flag it as READY.
We would need nodepool to craft specific images to boot instances from. First pass with Debian Jessie.
The minimum viable product is an image that boots on labs and that nodepool can ssh into to finish it is setup and thus flag it as READY.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | hashar | T102878 Create a Jessie image with diskimage-builder suitable for nodepool | |||
| Resolved | MoritzMuehlenhoff | T102880 Backport python-diskimage-builder 0.1.46 from testing to jessie-wikimedia | |||
| Resolved | hashar | T105152 diskimage cloud-init does not bring up network |
2015-06-17 22:14:52,744 DEBUG paramiko.transport: userauth is OK 2015-06-17 22:14:52,887 INFO paramiko.transport: Authentication (publickey) successful!
Progress!
Then nodepool bails out when asserting whether /etc/nodepool exists (it does not in the image):
2015-06-17 22:14:52,941 ERROR nodepool.NodeLauncher: Exception launching node id: 10 in provider: wmflabs-eqiad error: Exception: Unable to test for config dir command: ls /etc/nodepool
Thus the diskimage need a dummy /etc/nodepool which is writable by nodepoolmanager user.
I had an instance created for Jessie using diskimage-builder. It even booted in labs!
Now I have to puppetize it the magic recipe.
The bulk of the disk image config is in nodepool.yaml puppetized at https://gerrit.wikimedia.org/r/#/c/201728/16/modules/nodepool/templates/nodepool.yaml.erb,unified + some follow up changes.