Separating generic systems and site specific systems

[pearce8]

Site specific systems are named site-name-system, and contain site specific details about package versions and locations.

Generic systems define the bare minimum for Benchpark to work, and are intended to be a starting point of a system specification for a specific hardware, that can be built upon to describe a site specific system.

[scheibelp]

The naming system seems reasonable although I'm not sure if lack-of-site means we should use the term "generic". I'd prefer "nosite"

Also, it looks like the move for HPECray-zen3-MI250X-Slingshot is incomplete (more on that in specific comment). (edit: I was wrong about that, there is no longer a HPECray-zen3-MI250X-Slingshot directory)

[pearce8]

The naming system seems reasonable although I'm not sure if lack-of-site means we should use the term "generic". I'd prefer "nosite"

Also, it looks like the move for HPECray-zen3-MI250X-Slingshot is incomplete (more on that in specific comment).

I can live with nosite. I hope we will be able to do per-site directories in the long run; would the generic/nosite specs live in the base directory then, or in the generic/nosite directory?

[scheibelp]

I hope we will be able to do per-site directories in the long run; would the generic/nosite specs live in the base directory then, or in the generic/nosite directory?

The latter: in the nosite directory(which is I think how things are organized now).

If I understand correctly, by the "base" directory you mean something like HPECray-zen3-MI250X-Slingshot, which no longer exists in this PR - I think we should remove those (i.e. keep things as they are now in this PR).

[pearce8]

I hope we will be able to do per-site directories in the long run; would the generic/nosite specs live in the base directory then, or in the generic/nosite directory?

The latter: in the nosite directory(which is I think how things are organized now).

If I understand correctly, by the "base" directory you mean something like HPECray-zen3-MI250X-Slingshot, which no longer exists in this PR - I think we should remove those (i.e. keep things as they are now in this PR).

Sounds good. I renamed generic to nosite. When we can do nested directories, we will plan to have SiteName directories, and a nosite directory for the nosite-* systems.