Provide staging/development lava server instances
Bug #904796 reported by
Alexandros Frantzis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| LAVA Validation Lab |
Won't Fix
|
Critical
|
Zygmunt Krynicki | ||
Bug Description
It would be very useful to have some kind of staging/development lava server instances, so that extension developers can share their progress with others and get feedback before moving their code to production. Some thoughts/
1. The instances should be isolated and provide the minimum required rights (eg no job scheduling).
2. It should be possible to upgrade the code the instance is running (either core lava or extensions).
3. It should be possible to update the data stored in the instance (eg sync with data from the production server).
4. Ideally, it should be possible to limit access to the server to only a selected set of people (if content is sensitive).
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #1 |
| Changed in lava-lab: | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
| assignee: | nobody → Zygmunt Krynicki (zkrynicki) |
| milestone: | none → 2012.01 |
| Changed in lava-lab: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
This smells like a blueprint but let's keep it as a bug for now