Skip to content

Commit e4b3480

Browse files
committed
[storage] auto-generate protos
Signed-off-by: Boris Glimcher <Boris.Glimcher@emc.com>
1 parent 2cb20c0 commit e4b3480

File tree

20 files changed

+1676
-211
lines changed

20 files changed

+1676
-211
lines changed

common/v1/autogen.md

Lines changed: 49 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -36,14 +36,14 @@
3636
<a name="opi_api-inventory-v1-BIOSInfo"></a>
3737

3838
### BIOSInfo
39-
39+
BIOS Information (Type 0)
4040

4141

4242
| Field | Type | Label | Description |
4343
| ----- | ---- | ----- | ----------- |
44-
| vendor | [string](#string) | | |
45-
| version | [string](#string) | | |
46-
| date | [string](#string) | | |
44+
| vendor | [string](#string) | | String number of the BIOS Vendor’s Name. |
45+
| version | [string](#string) | | String number of the BIOS Version. This value is a free-form string that may contain Core and OEM version information. |
46+
| date | [string](#string) | | String number of the BIOS release date. The date string, if supplied, is in either mm/dd/yy or mm/dd/yyyy format. If the year portion of the string is two digits, the year is assumed to be 19yy. NOTE: The mm/dd/yyyy format is required for SMBIOS version 2.3 and later |
4747

4848

4949

@@ -53,16 +53,18 @@
5353
<a name="opi_api-inventory-v1-BaseboardInfo"></a>
5454

5555
### BaseboardInfo
56-
56+
Baseboard (or Module) Information (Type 2)
57+
The information in this structure defines attributes of a system baseboard (for
58+
example, a motherboard, planar, server blade, or other standard system module)
5759

5860

5961
| Field | Type | Label | Description |
6062
| ----- | ---- | ----- | ----------- |
61-
| asset_tag | [string](#string) | | |
62-
| serial_number | [string](#string) | | |
63-
| vendor | [string](#string) | | |
64-
| version | [string](#string) | | |
65-
| product | [string](#string) | | |
63+
| asset_tag | [string](#string) | | Number of a null-terminated string |
64+
| serial_number | [string](#string) | | Number of null-terminated string |
65+
| vendor | [string](#string) | | Number of null-terminated string |
66+
| version | [string](#string) | | Number of null-terminated string |
67+
| product | [string](#string) | | Number of null-terminated string |
6668

6769

6870

@@ -72,13 +74,17 @@
7274
<a name="opi_api-inventory-v1-CPUInfo"></a>
7375

7476
### CPUInfo
75-
77+
Processor Information (Type 4)
78+
The information in this structure (see Table 21) defines the attributes of a single processor; a separate
79+
structure instance is provided for each system processor socket/slot. For example, a system with an
80+
IntelDX2™ processor would have a single structure instance while a system with an IntelSX2™ processor
81+
would have a structure to describe the main CPU and a second structure to describe the 80487 co1054 processor.
7682

7783

7884
| Field | Type | Label | Description |
7985
| ----- | ---- | ----- | ----------- |
80-
| total_cores | [int32](#int32) | | |
81-
| total_threads | [int32](#int32) | | |
86+
| total_cores | [int32](#int32) | | Number of cores per processor socket See 7.5.6. If the value is unknown, the field is set to 0. For core counts of 256 or greater, the Core Count field is set to FFh and the Core Count 2 field is set to the number of cores. |
87+
| total_threads | [int32](#int32) | | Number of threads per processor socket See 7.5.8. If the value is unknown, the field is set to 0. For thread counts of 256 or greater, the Thread Count field is set to FFh and the Thread Count 2 field is set to the number of threads. |
8288

8389

8490

@@ -88,17 +94,22 @@
8894
<a name="opi_api-inventory-v1-ChassisInfo"></a>
8995

9096
### ChassisInfo
91-
97+
System Enclosure or Chassis (Type 3)
98+
The information in this structure (see Table 16) defines attributes of the system’s mechanical
99+
enclosure(s). For example, if a system included a separate enclosure for its peripheral devices, two
100+
structures would be returned: one for the main system enclosure and the second for the peripheral device
101+
enclosure. The additions to this structure in version 2.1 of this specification support the population of the
102+
CIM_Chassis class.
92103

93104

94105
| Field | Type | Label | Description |
95106
| ----- | ---- | ----- | ----------- |
96-
| asset_tag | [string](#string) | | |
97-
| serial_number | [string](#string) | | |
98-
| type | [string](#string) | | |
99-
| type_description | [string](#string) | | |
100-
| vendor | [string](#string) | | |
101-
| version | [string](#string) | | |
107+
| asset_tag | [string](#string) | | Number of null-terminated string |
108+
| serial_number | [string](#string) | | Number of null-terminated string |
109+
| type | [string](#string) | | Bit 7 Chassis lock is present if 1. Otherwise, either a lock is not present, or it is unknown if the enclosure has a lock. Bits 6:0 Enumeration value; see below. |
110+
| type_description | [string](#string) | | Table 17 shows the byte values for the System Enclosure or Chassis Types field Number of null-terminated string |
111+
| vendor | [string](#string) | | Number of null-terminated string |
112+
| version | [string](#string) | | Number of null-terminated string |
102113

103114

104115

@@ -108,7 +119,7 @@
108119
<a name="opi_api-inventory-v1-DeviceInfo"></a>
109120

110121
### DeviceInfo
111-
122+
TODO: remove this message
112123

113124

114125
| Field | Type | Label | Description |
@@ -163,13 +174,15 @@ Empty
163174
<a name="opi_api-inventory-v1-MemoryInfo"></a>
164175

165176
### MemoryInfo
166-
177+
Physical Memory Array (Type 16)
178+
This structure describes a collection of memory devices that operate together to form a memory address
179+
space.
167180

168181

169182
| Field | Type | Label | Description |
170183
| ----- | ---- | ----- | ----------- |
171-
| total_physical_bytes | [int64](#int64) | | |
172-
| total_usable_bytes | [int64](#int64) | | |
184+
| total_physical_bytes | [int64](#int64) | | Maximum memory capacity, in kilobytes, for this array If the capacity is not represented in this field, then this field contains 8000 0000h and the Extended Maximum Capacity field should be used. Values 2 TB (8000 0000h) or greater must be represented in the Extended Maximum Capacity field. |
185+
| total_usable_bytes | [int64](#int64) | | TBD |
173186

174187

175188

@@ -179,18 +192,22 @@ Empty
179192
<a name="opi_api-inventory-v1-SystemInfo"></a>
180193

181194
### SystemInfo
182-
195+
System Information (Type 1)
196+
The information in this structure defines attributes of the overall system and is intended to be associated
197+
with the Component ID group of the system’s MIF. An SMBIOS implementation is associated with a single
198+
system instance and contains one and only one System Information (Type 1) structure. Table 10 shows
199+
the contents of this structure.
183200

184201

185202
| Field | Type | Label | Description |
186203
| ----- | ---- | ----- | ----------- |
187-
| family | [string](#string) | | |
188-
| name | [string](#string) | | |
189-
| vendor | [string](#string) | | |
190-
| serial_number | [string](#string) | | |
191-
| uuid | [string](#string) | | |
192-
| sku | [string](#string) | | |
193-
| version | [string](#string) | | |
204+
| family | [string](#string) | | Number of null-terminated string This text string identifies the family to which a particular computer belongs. A family refers to a set of computers that are similar but not identical from a hardware or software point of view. Typically, a family is composed of different computer models, which have different configurations and pricing points. Computers in the same family often have similar branding and cosmetic features. |
205+
| name | [string](#string) | | Number of null-terminated string |
206+
| vendor | [string](#string) | | Number of null-terminated string |
207+
| serial_number | [string](#string) | | Number of null-terminated string |
208+
| uuid | [string](#string) | | A UUID is an identifier that is designed to be unique across both time and space. It requires no central registration process. The UUID is 128 bits long. Its format is described in RFC4122, but the actual field contents are opaque and not significant to the SMBIOS specification, which is only concerned with the byte order. Table 11 shows the field names; these field names, particularly for multiplexed fields, follow historical practice. |
209+
| sku | [string](#string) | | Number of null-terminated string This text string identifies a particular computer configuration for sale. It is sometimes also called a product ID or purchase order number. This number is frequently found in existing fields, but there is no standard format. Typically for a given system board from a given OEM, there are tens of unique processor, memory, hard drive, and optical drive configurations. |
210+
| version | [string](#string) | | Number of null-terminated string |
194211

195212

196213

common/v1/gen/go/inventory.pb.go

Lines changed: 112 additions & 19 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)