Create PAWS staging environment
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	Chicocvenancio
	Feb 27 2018, 7:23 PM

Description

To continue working on PAWS tasks and not risk bringing it down every other day it is advisable to build a staging environment that can test changes without having to bring the hub down for a redeploy and to test cosmetic and bolder changes to PAWS.

Decide where to set up PAWS-staging
Create kubernetes cluster
Run the deploy-hook image
Change repo in the image to point to dev branch
Push changes to dev branch

Due to the automagical way the deploy-hook works with helm and kubernetes it seems the hardest step is to setup a separate kubernetes cluster for PAWS-staging.

We discussed this briefly in the WMCS team meeting and decided to place this in toolsbeta Cloud VPS project.

Related Objects

Mentioned In: T188012: PAWS userhomes permission error
T188406: Provide access to user created databases in PAWS

Event Timeline

Chicocvenancio triaged this task as High priority.Feb 27 2018, 7:23 PM

Chicocvenancio created this task.

zhuyifei1999 subscribed.Feb 27 2018, 7:23 PM

Chicocvenancio mentioned this in T188406: Provide access to user created databases in PAWS.Feb 27 2018, 7:25 PM

Chicocvenancio updated the task description. (Show Details)Mar 1 2018, 8:37 PM

PAWS-beta is now ~~(almost)~~ live https://paws-beta.wmflabs.org
This should not be used as a place to run notebooks regularly but a way to test features and configuration changes.

I used Yuvi's magical deploy-hook image to make code from the dev branch in my repo.

I did find a few things that could be improved in PAWS during the course of this and will make tasks for them soon.

Chicocvenancio mentioned this in T188012: PAWS userhomes permission error.Mar 2 2018, 1:35 AM

Create PAWS staging environment Closed, ResolvedPublicActions

Description

Related Objects

Event Timeline

Create PAWS staging environment
Closed, ResolvedPublic
Actions