Adding more people will help with some of our issues, but we are planning to focus on paying down some very long term technical debt in our OpenStack environment and doing more outreach to our current and future customers in the coming year's plan. We are currently down one Operations Engineer ( we are hiring!) and we plan to add one more person to the team in the upcoming Wikimedia Foundation fiscal year (July 2017-June 2018). Unfortunately, the cloud-services-team does not currently have the resources to work on the PaaS project for the foreseeable future. The hoped for long term solution is still to select a FLOSS Platform as a Service solution that works with Kubernetes as a backend ( T136264). Since building a giant monolith container is now off of the table as an intermediate solution, we need to rethink the near term plan for Kubernetes. The outcome there is not well documented, but it failed badly. About six months ago finally got around to trying to build such a container ( T152089). We have about 230 tools using Kubernetes today which is about 1/3rd of the tools that probably could move over with minimal changes to the tool's code.Ī year ago we thought that we would be able to create a giant Docker container that replicated the 'everything for everyone' setup that the grid engine hosts have been using. The Docker containers we are making available are limited to a single language runtime and install a very minimal set of additional libraries and binaries. The current webservice -backend=kubernetes system is a reasonable match for the use case of a tool that runs a single web process and can use language specific library management (composer for PHP, pip + virtualenv for Python, etc) to get all the things it needs. We are at an awkward phase of the project today however due mostly to a lack of staff to work on proper solutions for the new platform. Kubernetes is certainly hoped to be the more stable and full-featured replacement for grid engine. If that's the case I may try to stick with K8s, make same trick to pdftotext utility, and when things will be sorted out, I'll just have to delete those modified files, and app will automatically switch to system wide binaries. If there's a way for me to mount/call those utilities from inside of Kubernetes virtualenv, I'd be thankful for a hint on how to do that.Īs far as I understand in long term we plan to move from Grid Engine to K8s. (venv) we please install those utilities? They're legit, open source utilities, already available in main Toolforge shell, so I expect no issues on this side. If you don't see a command prompt, try pressing python3 -m venv source ~/www/python/venv/bin/activate Pdftotext: /usr/bin/pdftotext /usr/bin/X11/pdftotext whereis djvutoxmlĭjvutoxml: /usr/bin/djvutoxml /usr/bin/X11/djvutoxml webservice -backend=kubernetes python shell
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |