Actions
Feature #6963
openDecouple teuthology and Inktank's infrastructure
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
% Done:
0%
Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Description
Some planning required before we actually do this.
Updated by Anonymous over 10 years ago
We should probably decouple the workings of teuthology from all the Inktank/sepia lab infrastructure that is embedded in the code itself right now. This needs to be done before we release teuthology to the general public.
A major part of this would be making the locking code separate. We may have to develop an API that works between teuthology and our locking code. Other users may have different needs on their internal side so the API should be generalized to handle this.
There are other issues too that we need to consider. For example, there are hard-coded sepia references in teuthology currently. I suspect more issues will pop up in further discussions.
Updated by Dan Mick over 10 years ago
- Subject changed from teuthology and Inktank's infrastructure to Decouple teuthology and Inktank's infrastructure
Actions