You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a lot of documentation that is needed for the python client, I seem to be searching through the code to find what I need most of the time. I'm adding stuff off the top of my head as I think of it, so feel free to add to the list as you see fit.
Plugins
Location they are loaded from
Directory structure
Architecture - i.e. how to make your own
Naming scheme
Functionality of existing plugins - options need to be documented
JunitXML
IUDatabase
TextFile
FooFlash
DefaultProfile
DefaultMTTDefaults
WWulf3
DefaultTestBuild
ModuleCmd
Copytree
Watchdog
Environ
ExecuteCmd
Logger
MPIVersion
Compilers
MTTVersion
IPMITool
ALPS
SLURM
OpenMPI
Hostfile
Autotools
Shell
Harasser
Git
AlreadyInstalled
combinatorial
sequential
Plugin parent classes - Most of these just need a line or two
ReporterMTTStage
LauncherDefaultsMTTStage
FirmwareMTTStage
ProfileMTTStage
MTTDefaultsMTTStage
TestGetMTTStage
MiddlewareGetMTTStage
MiddlewareBuildMTTStage
ProvisionMTTStage
TestBuildMTTStage
TestRunMTTStage
BIOSMTTStage
BaseMTTUtility
VersionMTTTool
CNCMTTTool
LauncherMTTTool
BuildMTTTool
HarasserMTTTool
FetchMTTTool
ExecutorMTTTool
Maybe this would fit well in @Jagaskak's github pages?
That is really, really long. Sorry about that, but I think it is important to have a checklist somewhere with the documentation that is needed.
The text was updated successfully, but these errors were encountered:
@PeterGottesman We are trying to get the documentation onto the MTT web site. @Jagaskak hasn't succeeded in getting Travis properly plumbed yet. Meantime, you can see the docs here:
There is a lot of documentation that is needed for the python client, I seem to be searching through the code to find what I need most of the time. I'm adding stuff off the top of my head as I think of it, so feel free to add to the list as you see fit.
Maybe this would fit well in @Jagaskak's github pages?
That is really, really long. Sorry about that, but I think it is important to have a checklist somewhere with the documentation that is needed.
The text was updated successfully, but these errors were encountered: