Set up long-running test environment for oq-engine
Bug #977810 reported by
Lars Butler
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenQuake (deprecated) |
Fix Released
|
Medium
|
Lars Butler |
Bug Description
[et=24h]
[at=16.5h]
- Cut a separate VPS (bug # 977811) for the new infrastructure
- Duplicate the existing setup of ci.openquake.org (postgres/postgis, rabbitmq, redis, celery)
- No need to install jenkins
- The long-running test configuration will still be managed at ci.openquake.org, in jenkins.
- The new test configuration (oq-engine-LRT) will need to remotely pull the latest code on to the LRT VPS and restart services.
- Shell commands can simply be executed remotely using ssh.
- For more sophisticated operations, we may be able to use Fabric (fabfile.org).
description: | updated |
Changed in openquake: | |
status: | New → Confirmed |
milestone: | none → 0.7.0 |
assignee: | nobody → Lars Butler (lars-butler) |
importance: | Undecided → Medium |
description: | updated |
description: | updated |
Changed in openquake: | |
status: | Confirmed → In Progress |
Changed in openquake: | |
status: | In Progress → Fix Committed |
description: | updated |
Changed in openquake: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Remote commands will need to be execute as a user. I plan to create a `jenkins` user on ci2 for this purpose.