Commit 4492b04
Curt Brune
Add switch silicon vendor string to the image discovery default paths
During image discovery, ONIE looks for installer names in the
following order:
1. onie-installer-<cpu_arch>-<hw_vendor>_<machine>-r<machine_revision>
2. onie-installer-<cpu_arch>-<hw_vendor>_<machine>
3. onie-installer-<hw_vendor>_<machine>
4. onie-installer-<cpu_arch>
5. onie-installer
With the advent of ONIE enabled systems supporting multiple switch
silicon vendors, step 4 has become ambiguous.
This patch adds an additional step to the ONIE waterfall that includes
the switch silicon vendor. In the above waterfall this new step would
be between steps 3 and 4. The new step looks like:
onie-installer-<cpu_arch>-<switch_silicon_vendor>
Before the change the kvm_x86_64 machine waterfall discovery looks
like this:
<cpu_arch> = x86_64
<hw_vendor>_<machine> = kvm_x86_64
Info: Fetching http://10.0.2.2/onie-installer-x86_64-kvm_x86_64-r0 ...
Info: Fetching http://10.0.2.2/onie-installer-x86_64-kvm_x86_64 ...
Info: Fetching http://10.0.2.2/onie-installer-kvm_x86_64 ...
Info: Fetching http://10.0.2.2/onie-installer-x86_64 ...
Info: Fetching http://10.0.2.2/onie-installer ...
After the changing, using a completely fictitious silicon vendor, the
waterfall looks like:
<switch_silicon_vendor> = qemu
Info: Fetching http://10.0.2.2/onie-installer-x86_64-kvm_x86_64-r0 ...
Info: Fetching http://10.0.2.2/onie-installer-x86_64-kvm_x86_64 ...
Info: Fetching http://10.0.2.2/onie-installer-kvm_x86_64 ...
Info: Fetching http://10.0.2.2/onie-installer-x86_64-qemu ...
Info: Fetching http://10.0.2.2/onie-installer-x86_64 ...
Info: Fetching http://10.0.2.2/onie-installer ...
Technically the same information is contained in step #3
"onie-installer-<hw_vendor>_<machine>", however the new file name is
more generic and will be easier for customers to maintain when using
multiple platforms.
Imagine the case of a customer who has multiple x86 hardware platforms,
from different hardware vendors, using different switch silicon. Also
imagine NOS installers that target a specific switch silicon.
The customer could maintain NOS installers named as in step #2 and be
OK, however, that is a lot of files to manage.
Using the new step "<cpu_arch>-<switch_silicon_vendor>" the end
customer could target all of the x86 platforms from a particular
silicon vendor with a single NOS image.
Signed-off-by: Curt Brune <[email protected]>1 parent 6e7366a commit 4492b04
File tree
4 files changed
+11
-0
lines changed- build-config
- make
- machine/kvm_x86_64
- rootconf/default/lib/onie
4 files changed
+11
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
181 | 181 | | |
182 | 182 | | |
183 | 183 | | |
| 184 | + | |
| 185 | + | |
| 186 | + | |
184 | 187 | | |
185 | 188 | | |
186 | 189 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
252 | 252 | | |
253 | 253 | | |
254 | 254 | | |
| 255 | + | |
255 | 256 | | |
256 | 257 | | |
257 | 258 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
18 | 18 | | |
19 | 19 | | |
20 | 20 | | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
21 | 27 | | |
22 | 28 | | |
23 | 29 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
31 | 31 | | |
32 | 32 | | |
33 | 33 | | |
| 34 | + | |
34 | 35 | | |
35 | 36 | | |
36 | 37 | | |
| |||
0 commit comments