Dear Jeff,
On Thu, Mar 08, 2018 at 09:00:43AM -0500, Jeffrey Burke wrote:
Our current idea is to make restraint the default harness for RHEL8+ and therefore slowly phase out beah (as the default). That includes getting restraint to achieve feature parity with beah. I don't have an exact time frame for this yet and how we would pull this off, since I expect there are possibly higher priority items coming up.
That is a good plan. Do you have a list of features in BEAH that are not in Restraint to achieve parity?
At this moment we don't have a good overview of what specifically is missing. We do however have an epic:
https://projects.engineering.redhat.com/browse/BKR-2891
in which we track bugs and tasks to figure out what else we're missing to get feature parity. One missing feature we do know is captured in
https://bugzilla.redhat.com/show_bug.cgi?id=1206059 support testinfo.desc Environment in restraint
That will get us change our dogfood tests to use restraint by default. Once we have that, we will hopefully have a much better picture of what is missing.
Does that answer your question or at least goes in the right direction?
Partially, do you know who on your team will be SME for Restraint?
Matt Tyson mtyson@redhat.com has taken the lead on restraint so he'll be the SME for it.
Kind Regards,