...
The BardFrame is a general application piece for managing contexts, bean sessions, data, etc and will need to be extended for each specific use case if the use case requires an entirely new application (e.g. e-AIRS and e-Spine have different use cases ways in which they will launch HPC jobs and might require two separate BardFrame's implementations). All application bean types should register with BardFrame and the BardServiceRegistry should provide the right instance of BardFrame. Alternatively, BardFrame could be made to allow applications to register their bean types.
...
| Code Block | ||
|---|---|---|
| ||
private String osName; // host os name
private String osVersion; // host os version
private String architecture; // host architecture
private String id; // host id
private Set<PropertyBean> envProperties; // environment properties on host
private Set<NodeBean> hpcNodes; // properties of each node
|