Page MenuHomePhabricator

Evaluate Kubernetes based workflow replacement options for SGE
Open, LowPublic

Description

Transitioning from SGE to Kubernetes (k8s) will require new utilities and deployment workflows for Toolforge users. Initial efforts like T129309: Goal: Allow using k8s instead of GridEngine as a backend for webservices are focused on drop-in replacement for existing workflows, but do not take full advantage of the services offered by k8s.

Direct use of the k8s interface is possible, but it is relatively low level and not user friendly. There are several FLOSS projects that build on Kubernetes to provide a complete Platform as a Service (PaaS) system. A typical PaaS will provide tools to assist in managing multiple base containers, versioning container instances, and deploying containers to the k8s grid. Using a third-party product with an active user and developer community would provide benefits over inventing new home-grown tooling and processes. Two major benefits would be better documentation for our users and reduced maintenance burden for our Labs technical team.

Event Timeline

Restricted Application added subscribers: Zppix, Aklapper. · View Herald Transcript

Step one is to follow the lead of T106475: Evaluate a 'cluster solution' for use on Tool Labs and develop evaluation criteria. What features are must haves? What are desirable? These should cover both operational and end user concerns. Use T136265: Develop evaluation criteria for comparing Platform as a Service (PaaS) solutions to discuss your opinions.

bd808 updated the task description. (Show Details)

Step two involves evaluation, so we need to come up with a list of possible candidates. At the moment I'm aware of Deis and OpenShift. Are there others?

I would like to propose deploying a testing instance not only for the top solution, but (at least) the top two. Say a rough, but working installation takes two weeks engineer time each and a couple of out-of-warranty machines, then that's still a price worth to pay for an informed choice between multiple options that will need to last for several years.

Step two involves evaluation, so we need to come up with a list of possible candidates. At the moment I'm aware of Deis and OpenShift. Are there others?

There's Flynn and Dokku. Shipyard might be appropriate too.

I would like to propose deploying a testing instance not only for the top solution, but (at least) the top two. Say a rough, but working installation takes two weeks engineer time each and a couple of out-of-warranty machines, then that's still a price worth to pay for an informed choice between multiple options that will need to last for several years.

I agree, yeah. When we evaluated kubernetes vs mesos/marathon we setup test installations of both of them so we can do a handson evaluation, and I think we'll have to do the same here.

There's Flynn and Dokku. Shipyard might be appropriate too.

We should only consider things that run on top of Kubernetes, IMO.

There's Flynn and Dokku. Shipyard might be appropriate too.

We should only consider things that run on top of Kubernetes, IMO.

Oh, sorry, I didn't realise that.

I would like to propose deploying a testing instance not only for the top solution, but (at least) the top two. Say a rough, but working installation takes two weeks engineer time each and a couple of out-of-warranty machines, then that's still a price worth to pay for an informed choice between multiple options that will need to last for several years.

I agree, yeah. When we evaluated kubernetes vs mesos/marathon we setup test installations of both of them so we can do a handson evaluation, and I think we'll have to do the same here.

Summary steps updated to "Deploy testing instance of top two solutions based on evaluation for head to head testing".

valhallasw moved this task from Triage to Backlog on the Toolforge board.
bd808 renamed this task from Evalute Kubernetes based workflow replacement options for SGE to Evaluate Kubernetes based workflow replacement options for SGE.Jul 19 2016, 4:58 PM