Please do T108210 again except for Kubernetes so that panoviewer can be migrated to the new job system.
Packages hugin-tools and python3-pil.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | dschwen | T319953 Migrate panoviewer from Toolforge GridEngine to Toolforge Kubernetes | |||
| Declined | None | T347446 Please install hugin-tools and pillow again |
Event Timeline
Comment Actions
I filed this task because it was suggested at wikitech:Toolforge Grid Engine deprecation. But after reading the comments on T166985: Install DjVuLibre and XPDF packages for Kubernetes containers on Toolforge, a similar installation request that's been stalled since 2017, it seems evident that it's not going to happen. @bd808 please correct me if I'm wrong.
Hugin has some heavy dependencies. apt-get install hugin-tools on a base Ubuntu install says it will need 206 MB of disk space. Probably most of the tasks in Toolforge (Software install/update) won't ever be done, but this one seems especially far down the list.
Apparently the real solution is to use a buildpack. But I'm not sure if it's worth doing since we're considering productionization of this tool. I'm trying to estimate the number of hours involved. The tool source is at https://github.com/toollabs/panoviewer/
Comment Actions
A buildpack is the only system we have today for a tool to create a custom container image. I do not have an understanding of the current panoviewer codebase that would allow me to quickly estimate the time needed to make it work under the buildpack paradigm. It has been softly on my "things to do list" to explore making a 'hello world' style buildpack tool combining PHP and extra apt packages which I think is the core of what would be needed here.
The alternative requested here is for either a custom image for this tool that the cloud-services-team maintains in perpetuity, or for us to walk back from single language runtime containers to make something that has PHP, Python, hugin-tools, python3-pil, and whatever parts haven't actually been identified yet that are missing from the existing PHP image. Way back in 2015 Yuvi hoped to make a single container that functionally had all of the software features of the grid engine environment. By 2016 we realized that such a thing was not really going to work. Initially this was because Docker at the time literally could not support a container of the size that all of the packages created. Later Docker gained the ability to work with larger images, but a >4GiB image is still quite problematic for deployment.