Temporary storage for the mock work that is pywbemcli addon.
Each mock is represented by three files: A py file (Python program), an xml file and a mof file.
- The python program is named [Profile Name]MockLoad.py. Examples are ArrayMockLoad.py and NASHeadMockLoad.py.
- The xml file is named [Org]_[Profile Name]_leaflist.xml. Examples are SNIA_Array_leaflist.xml and SNIA_NAS Head_leaflist.
- The mof file is named Mock[Org]_[Profile Name]Instances.mof. Examples are MockSNIA_ArrayInstances.mof and MockSNIA_NAS HeadInstances.mof.
The xml leaflist file holds all the leaf classes for a complete implementation of an autonomous profile. That is, all classes in the autonomous profile and its component profiles. It is based on all classes identified by SMI-S 1.8.0.
The mof files contain instance mofs for all instances that are to be mocked.
The python program (py file) is to be used to establish (and name) a mock. The program reads in the class lists for both the WBEM Server Profile and the SNIA Server Profile and combine those lists with the list for the device profile (e.g., Array or NAS Head). It uses the combined list to load class definitions in the mock. It then reads the mof file to load instances into the mock.
The script directory contains pdf files. The pdf files are Quick Start Guides for finding information in the mocks. The guides include text describing what we are looking for, the pywbemcli commands to get that information and the output produced from the mocks.