Date   

Re: What's the correct best method for setting up ONiE development?

Sriram Ramkrishna
 

HIya!

Yep, did do the make distclean although I did hte make without the -j option to make sure there wasn't some race condition. I was reading about how you should run distclean in one of the issues that I saw - so I followed that guideline.

It's a clean clone - I setup DUE and then cloned the ONiE repository and then followed the instructions in DUE and in the instructions for my architecture.

I decided to follow your instructions precisely and so the end result of the build of using the ! make -j1 MACHINE-kvm_x86_64 all demo is this (note the breakage is still in the cross compiler):

[INFO ]  =================================================================
[INFO ]  Installing ISL for host
[ERROR]    make[4]: *** [Makefile:1397: isl_scheduler.lo] Error 1
[ERROR]    make[4]: *** Waiting for unfinished jobs....
[ERROR]    make[4]: *** [Makefile:1397: isl_sort.lo] Error 1
[ERROR]    make[4]: *** [Makefile:1397: isl_space.lo] Error 1
[ERROR]    make[3]: *** [Makefile:1505: all-recursive] Error 1
[ERROR]    make[2]: *** [Makefile:1110: all] Error 2
[ERROR]  
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Installing ISL for host'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@338]
[ERROR]  >>        called from: do_isl_backend[scripts/build/companion_libs/121-isl.sh@115]
[ERROR]  >>        called from: do_isl_for_host[scripts/build/companion_libs/121-isl.sh@62]
[ERROR]  >>        called from: do_companion_libs_for_host[scripts/build/companion_libs.sh@36]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@653]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>      '/home/sri/src/onie/build/crosstool-ng/crosstool-ng-1.23.0/docs/B - Known issues.txt'
[ERROR]  >>
[ERROR]  >>  If you feel this is a bug in crosstool-NG, report it at:
[ERROR]  >>      https://github.com/crosstool-ng/crosstool-ng/issues/
[ERROR]  >>
[ERROR]  >>  Make sure your report includes all the information pertinent to this issue.
[ERROR]  >>  Read the bug reporting guidelines here:
[ERROR]  >>      http://crosstool-ng.github.io/support/
[ERROR]  
[ERROR]  (elapsed: 4:25.78)
/home/sri/src/onie/build/crosstool-ng/crosstool-ng-1.23.0/ct-ng:147: recipe for target 'build' failed
make[1]: *** [build] Error 2
make[1]: Leaving directory '/home/sri/src/onie/build/x-tools/x86_64-g6.3.0-lnx4.9.95-uClibc-ng-1.0.22/build'
rm: cannot remove '/home/sri/src/onie/build/x-tools/x86_64-g6.3.0-lnx4.9.95-uClibc-ng-1.0.22/build/.config.2': No such file or directory
make/xtools.make:123: recipe for target '/home/sri/src/onie/build/x-tools/x86_64-g6.3.0-lnx4.9.95-uClibc-ng-1.0.22/stamp/xtools-build' failed
make: *** [/home/sri/src/onie/build/x-tools/x86_64-g6.3.0-lnx4.9.95-uClibc-ng-1.0.22/stamp/xtools-build] Error 1
sri@due-onie-build-debian-9:~/src/onie/build-config$


From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Alex Doyle via groups.io <adoyle@...>
Sent: Wednesday, February 10, 2021 8:00 AM
To: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io>
Subject: Re: [OCP-ONIE] What's the correct best method for setting up ONiE development?
 
Hi Sri
 Hm. Usually it rolls right through there, so I'm thinking it could be an environmental configuration or a code modification issue (and the first one would be particularly irksome as that is the sort of problem DUE is supposed to fix...).

 Your invocation looks correct, so I'm seeing no obvious reason for a failure here so we'll have to poke around a bit. A couple of thoughts, which may seem obvious but it's helpful for establishing a baseline...

Try running:
 make distclean ; make -jMACHINE=kvm_x86_64 all demo

The make distclean should clear out everything and re download components. If you'd had a previous compile fail somewhere the makefile logic might not be catching it and think that it had completed successfully.  I've seen this happen if I interrupt a build, then try to build again.

Note the -j1 there - it'll take longer to build, but it should be harder for errors to be hidden in the log output.

Other things to consider:

I've occasionally seen what looked like race conditions in parallel make, but this happens rarely for me, and I've never been able to reproduce them, as a make distclean and a rebuild usually works.

Is it an unmodified check out of ONIE? i.e. "git reset --hard" changes nothing? (I'd expect that since it is a tools build problem, but I've been surprised before)

Does your $PATH in DUE have anything unusual in it? (I've seen PATH settings trip up builds by accessing different component versions)
 A working one for ONIE would be (lifted from my current ONIE contiainer):
  /sbin:/usr/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

Is DUE running on the Debian 9 system you'd mentioned,  or Red Hat? Red Hat support is new, and while it should​ be the same by the time the containers are running there were a couple of differences in how it got set up vs Debian.

If none of that helps, can you post the output of a:
dpkg -l
...which will let me check the container component versions against what I'm using, and the full output of the -j1 build I'd suggested above

Let me know how it goes  - I'll roll whatever we find into the documentation to keep the next person through from getting burned 🙂

Thanks!

Alex Doyle
ONIE Project Lead

From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Sriram Ramkrishna <sriram.ramkrishna@...>
Sent: Wednesday, February 10, 2021 5:02 AM
To: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io>
Subject: Re: [OCP-ONIE] What's the correct best method for setting up ONiE development?
 
External email: Use caution opening links or attachments

Hi Alex! Thanks for your quick response!

I am in fact using DUE and I followed all the instructions that you so kindly documented below. My real problem is what happens after: 

make -j4 MACHINE=kvm_x86_64 all demo

Inside the debian9 container that DUE created. (lovely work btw) The cross compiler fails to build which is what I had even when I didn't use DUE. So I'm trying to debug the cross compiler issues. Basically this is the last bit:

/home/sri/src/onie/build/crosstool-ng/crosstool-ng-1.23.0/ct-ng:147: recipe for target 'build' failed

I had this with and without DUE on a Debian 9 system. Having exhausted other means of debugging I thought I would ask on the mailing list. 🙂

Here is the pastebin for that error:

Would love to hear your thoughts.

Best,
sri



From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Alex Doyle via groups.io <adoyle@...>
Sent: Tuesday, February 9, 2021 4:04 PM
To: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io>
Subject: Re: [OCP-ONIE] What's the correct best method for setting up ONiE development?
 
Hi Sri,
 
I really recommend DUE to set up the build environment using Docker containers for a couple of reasons:
  1. The standard configuration it applies is the same one I'm using for processing pull requests, development, and quarterly releases, so it should consistently provide the correct versions of everything needed to build.
  2. If there are problems, it provides a common frame of reference to debug them.
  3. And I'm using it for ONIE work, so any problems there get my attention pretty quick.
I'm getting the impression there are some weak points in the documentation for setting it up - yours isn't the first email asking setup questions - so if you can identify the things that are tripping you up, do let me know so I can make it clearer ( at this point I've been looking at things long enough to not see things that might be unclear to a set of fresh eyes. ) Hm. In writing out the rest of this, I'm thinking this 'quickstart' info needs to be more prominently featured in the documentation...

That aside, here's some actionable information:

So, DUE getting started:
  1. wget https://github.com/CumulusNetworks/DUE/releases/download/v2.3.0/due_2.3.0-1_all.deb  <-get latest release
  2. sudo dpkg -i due_2.3.0-1.all.deb  <- install it. Will throw missing dependency errors, that's fine
  3. sudo apt-get install --fix-broken    <- use APT to fix the missing dependencies. Will want to install Docker if you don't have it.

Then follow:
https://github.com/CumulusNetworks/DUE/blob/master/templates/onie/README.md

To use DUE to create an ONIE container. I'd recommend using the Debian 9 version (10 only works with the component-upgrade-2020 branch, which is not heavily tested yet, and probably breaks existing platforms at this point.)

./due --create --from debian:9 --description "ONIE Build Debian 9" --name onie-build-debian-9 --prompt ONIE-9 --tag onie --use-template onie

Then:
due --run 
...will let you select a container, or if there's only one, it'll run it and mount your home directory, at which point you should be able to build ONIE.

I've also got a tutorial video that should be mostly correct here:
https://www.youtube.com/watch?v=-5onRbZA0QQ

It's a number of DUE versions out of date, but I think the workflow still holds.

I'd also suggest starting by trying to build the kvm target
https://github.com/opencomputeproject/onie/tree/master/machine/kvm_x86_64
 (although you'll also need to install qemu if you want to run it. There is some help here:
https://github.com/opencomputeproject/onie/blob/master/machine/kvm_x86_64/mk-vm.sh,
and if that doesn't pan out let me know. I've got an upgraded version of that script that I'm working on because I can never remember what arguments qemu needs....)
Anyway:
  1. cd ./build-config
  2.  make -j4 MACHINE=kvm_x86_64 all demo

Let me know how it goes, and what things aren't clear in the documentation so I can get them straightened out.

Thanks
Alex Doyle
ONIE Project Lead


From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Sriram Ramkrishna <sriram.ramkrishna@...>
Sent: Tuesday, February 9, 2021 2:50 PM
To: ocp-onie@ocp-all.groups.io <ocp-onie@ocp-all.groups.io>
Subject: [OCP-ONIE] What's the correct best method for setting up ONiE development?
 
External email: Use caution opening links or attachments

I'm working on enabling a platform that was enabled before (Facebook Wedge 100) but has some issues. I'm trying to build the environment, but I'm currently having a lot of issues getting the cross compiler to get compiled. I've tried solutions like DUE - but I'm still having the same issues.

If there is a blog post, documentation, or video that I can look at - that would be very appreciated.

Cheers,
sri


ONIE Release 2021.02 is now available

Alex Doyle
 

Hi everyone.

The 2021.02 release of ONIE is now available.  Release notes follow. Note that this does not have any of the major changes that are on the component-upgrade-2020 branch, as that's not stable enough to be merged to master.

Thanks!

Alex Doyle
ONIE Project Lead

Release notes:
------------------------
2021.02 Public Release                                                  
                                                                         
This release was produced using the Debian 9 based                      
ONIE Docker build container configuration generated                      
using Dedicated User Environment (DUE) version 2.3.0                    
                                                                         
Instructions and source for replicating this ONIE build                  
environment are available at:                                            
https://github.com/CumulusNetworks/DUE                                  
                                                                         
                                                                         
New Hardware Platforms                                                  
======================                                                  
Delta:                                                                  
 delta_tx4810                                                            
 delta_agc7008s                                                          
                                                                         
Build and Release / Improvements                                        
================================                                        
Recommend users of the Docker build environment upgrade to DUE 2.3.0    
https://github.com/CumulusNetworks/DUE                                  
 This version should work on Red Hat systems as well.                    
                                                                         
                                                                         
Bug Fixes / Improvements                                                
=========================                                                
NONE                                                                    
                                                                         
Misc:                                                                    
=====                                                                    
NONE                                                                    


GIT Statistics
----------------------------
​3 employers found                                        
A total of 35504 lines added, 3 removed (delta 35501)    
                                                         
Developers with the most changesets                      
Alex Doyle                   2 (50.0%)                  
os-vincent.liu               1 (25.0%)                  
johnson                      1 (25.0%)                  
                                                         
Developers with the most changed lines                  
os-vincent.liu            35047 (98.7%)                  
johnson                    453 (1.3%)                    
Alex Doyle                   4 (0.0%)                    
                                                         
Developers with the most lines removed                  
                                                         
Developers with the most signoffs (total 5)              
Alex Doyle                   3 (60.0%)                  
johnson                      1 (20.0%)                  
os-vincent.liu               1 (20.0%)                  
                                                         
Developers with the most reviews (total 0)              
                                                         
Developers with the most test credits (total 0)          
                                                         
Developers who gave the most tested-by credits (total 0)
                                                         
Developers with the most report credits (total 0)        
                                                         
Developers who gave the most report credits (total 0)    
                                                         
Top changeset contributors by employer                  
Delta Networks               2 (50.0%)                  
alexddoyle@...         1 (25.0%)                  
NVidia                       1 (25.0%)                  
                                                         
Top lines changed by employer                            
Delta Networks            35500 (100.0%)                
NVidia                       3 (0.0%)                    
alexddoyle@...         1 (0.0%)                    
                                                         
Employers with the most signoffs (total 5)              
NVidia                       3 (60.0%)                  
Delta Networks               2 (40.0%)                  
                                                         
Employers with the most hackers (total 4)                
Delta Networks               2 (50.0%)                  
NVidia                       1 (25.0%)                  
alexddoyle@...         1 (25.0%)                  


Re: What's the correct best method for setting up ONiE development?

Alex Doyle
 

Hi Sri
 Hm. Usually it rolls right through there, so I'm thinking it could be an environmental configuration or a code modification issue (and the first one would be particularly irksome as that is the sort of problem DUE is supposed to fix...).

 Your invocation looks correct, so I'm seeing no obvious reason for a failure here so we'll have to poke around a bit. A couple of thoughts, which may seem obvious but it's helpful for establishing a baseline...

Try running:
 make distclean ; make -jMACHINE=kvm_x86_64 all demo

The make distclean should clear out everything and re download components. If you'd had a previous compile fail somewhere the makefile logic might not be catching it and think that it had completed successfully.  I've seen this happen if I interrupt a build, then try to build again.

Note the -j1 there - it'll take longer to build, but it should be harder for errors to be hidden in the log output.

Other things to consider:

I've occasionally seen what looked like race conditions in parallel make, but this happens rarely for me, and I've never been able to reproduce them, as a make distclean and a rebuild usually works.

Is it an unmodified check out of ONIE? i.e. "git reset --hard" changes nothing? (I'd expect that since it is a tools build problem, but I've been surprised before)

Does your $PATH in DUE have anything unusual in it? (I've seen PATH settings trip up builds by accessing different component versions)
 A working one for ONIE would be (lifted from my current ONIE contiainer):
  /sbin:/usr/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

Is DUE running on the Debian 9 system you'd mentioned,  or Red Hat? Red Hat support is new, and while it should​ be the same by the time the containers are running there were a couple of differences in how it got set up vs Debian.

If none of that helps, can you post the output of a:
dpkg -l
...which will let me check the container component versions against what I'm using, and the full output of the -j1 build I'd suggested above

Let me know how it goes  - I'll roll whatever we find into the documentation to keep the next person through from getting burned 🙂

Thanks!

Alex Doyle
ONIE Project Lead


From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Sriram Ramkrishna <sriram.ramkrishna@...>
Sent: Wednesday, February 10, 2021 5:02 AM
To: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io>
Subject: Re: [OCP-ONIE] What's the correct best method for setting up ONiE development?
 
External email: Use caution opening links or attachments

Hi Alex! Thanks for your quick response!

I am in fact using DUE and I followed all the instructions that you so kindly documented below. My real problem is what happens after: 

make -j4 MACHINE=kvm_x86_64 all demo

Inside the debian9 container that DUE created. (lovely work btw) The cross compiler fails to build which is what I had even when I didn't use DUE. So I'm trying to debug the cross compiler issues. Basically this is the last bit:

/home/sri/src/onie/build/crosstool-ng/crosstool-ng-1.23.0/ct-ng:147: recipe for target 'build' failed

I had this with and without DUE on a Debian 9 system. Having exhausted other means of debugging I thought I would ask on the mailing list. 🙂

Here is the pastebin for that error:

Would love to hear your thoughts.

Best,
sri



From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Alex Doyle via groups.io <adoyle@...>
Sent: Tuesday, February 9, 2021 4:04 PM
To: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io>
Subject: Re: [OCP-ONIE] What's the correct best method for setting up ONiE development?
 
Hi Sri,
 
I really recommend DUE to set up the build environment using Docker containers for a couple of reasons:
  1. The standard configuration it applies is the same one I'm using for processing pull requests, development, and quarterly releases, so it should consistently provide the correct versions of everything needed to build.
  2. If there are problems, it provides a common frame of reference to debug them.
  3. And I'm using it for ONIE work, so any problems there get my attention pretty quick.
I'm getting the impression there are some weak points in the documentation for setting it up - yours isn't the first email asking setup questions - so if you can identify the things that are tripping you up, do let me know so I can make it clearer ( at this point I've been looking at things long enough to not see things that might be unclear to a set of fresh eyes. ) Hm. In writing out the rest of this, I'm thinking this 'quickstart' info needs to be more prominently featured in the documentation...

That aside, here's some actionable information:

So, DUE getting started:
  1. wget https://github.com/CumulusNetworks/DUE/releases/download/v2.3.0/due_2.3.0-1_all.deb  <-get latest release
  2. sudo dpkg -i due_2.3.0-1.all.deb  <- install it. Will throw missing dependency errors, that's fine
  3. sudo apt-get install --fix-broken    <- use APT to fix the missing dependencies. Will want to install Docker if you don't have it.

Then follow:
https://github.com/CumulusNetworks/DUE/blob/master/templates/onie/README.md

To use DUE to create an ONIE container. I'd recommend using the Debian 9 version (10 only works with the component-upgrade-2020 branch, which is not heavily tested yet, and probably breaks existing platforms at this point.)

./due --create --from debian:9 --description "ONIE Build Debian 9" --name onie-build-debian-9 --prompt ONIE-9 --tag onie --use-template onie

Then:
due --run 
...will let you select a container, or if there's only one, it'll run it and mount your home directory, at which point you should be able to build ONIE.

I've also got a tutorial video that should be mostly correct here:
https://www.youtube.com/watch?v=-5onRbZA0QQ

It's a number of DUE versions out of date, but I think the workflow still holds.

I'd also suggest starting by trying to build the kvm target
https://github.com/opencomputeproject/onie/tree/master/machine/kvm_x86_64
 (although you'll also need to install qemu if you want to run it. There is some help here:
https://github.com/opencomputeproject/onie/blob/master/machine/kvm_x86_64/mk-vm.sh,
and if that doesn't pan out let me know. I've got an upgraded version of that script that I'm working on because I can never remember what arguments qemu needs....)
Anyway:
  1. cd ./build-config
  2.  make -j4 MACHINE=kvm_x86_64 all demo

Let me know how it goes, and what things aren't clear in the documentation so I can get them straightened out.

Thanks
Alex Doyle
ONIE Project Lead


From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Sriram Ramkrishna <sriram.ramkrishna@...>
Sent: Tuesday, February 9, 2021 2:50 PM
To: ocp-onie@ocp-all.groups.io <ocp-onie@ocp-all.groups.io>
Subject: [OCP-ONIE] What's the correct best method for setting up ONiE development?
 
External email: Use caution opening links or attachments

I'm working on enabling a platform that was enabled before (Facebook Wedge 100) but has some issues. I'm trying to build the environment, but I'm currently having a lot of issues getting the cross compiler to get compiled. I've tried solutions like DUE - but I'm still having the same issues.

If there is a blog post, documentation, or video that I can look at - that would be very appreciated.

Cheers,
sri


Re: What's the correct best method for setting up ONiE development?

Sriram Ramkrishna
 

Hi Alex! Thanks for your quick response!

I am in fact using DUE and I followed all the instructions that you so kindly documented below. My real problem is what happens after: 

make -j4 MACHINE=kvm_x86_64 all demo

Inside the debian9 container that DUE created. (lovely work btw) The cross compiler fails to build which is what I had even when I didn't use DUE. So I'm trying to debug the cross compiler issues. Basically this is the last bit:

/home/sri/src/onie/build/crosstool-ng/crosstool-ng-1.23.0/ct-ng:147: recipe for target 'build' failed

I had this with and without DUE on a Debian 9 system. Having exhausted other means of debugging I thought I would ask on the mailing list. 🙂

Here is the pastebin for that error:

Would love to hear your thoughts.

Best,
sri



From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Alex Doyle via groups.io <adoyle@...>
Sent: Tuesday, February 9, 2021 4:04 PM
To: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io>
Subject: Re: [OCP-ONIE] What's the correct best method for setting up ONiE development?
 
Hi Sri,
 
I really recommend DUE to set up the build environment using Docker containers for a couple of reasons:
  1. The standard configuration it applies is the same one I'm using for processing pull requests, development, and quarterly releases, so it should consistently provide the correct versions of everything needed to build.
  2. If there are problems, it provides a common frame of reference to debug them.
  3. And I'm using it for ONIE work, so any problems there get my attention pretty quick.
I'm getting the impression there are some weak points in the documentation for setting it up - yours isn't the first email asking setup questions - so if you can identify the things that are tripping you up, do let me know so I can make it clearer ( at this point I've been looking at things long enough to not see things that might be unclear to a set of fresh eyes. ) Hm. In writing out the rest of this, I'm thinking this 'quickstart' info needs to be more prominently featured in the documentation...

That aside, here's some actionable information:

So, DUE getting started:
  1. wget https://github.com/CumulusNetworks/DUE/releases/download/v2.3.0/due_2.3.0-1_all.deb  <-get latest release
  2. sudo dpkg -i due_2.3.0-1.all.deb  <- install it. Will throw missing dependency errors, that's fine
  3. sudo apt-get install --fix-broken    <- use APT to fix the missing dependencies. Will want to install Docker if you don't have it.

Then follow:
https://github.com/CumulusNetworks/DUE/blob/master/templates/onie/README.md

To use DUE to create an ONIE container. I'd recommend using the Debian 9 version (10 only works with the component-upgrade-2020 branch, which is not heavily tested yet, and probably breaks existing platforms at this point.)

./due --create --from debian:9 --description "ONIE Build Debian 9" --name onie-build-debian-9 --prompt ONIE-9 --tag onie --use-template onie

Then:
due --run 
...will let you select a container, or if there's only one, it'll run it and mount your home directory, at which point you should be able to build ONIE.

I've also got a tutorial video that should be mostly correct here:
https://www.youtube.com/watch?v=-5onRbZA0QQ

It's a number of DUE versions out of date, but I think the workflow still holds.

I'd also suggest starting by trying to build the kvm target
https://github.com/opencomputeproject/onie/tree/master/machine/kvm_x86_64
 (although you'll also need to install qemu if you want to run it. There is some help here:
https://github.com/opencomputeproject/onie/blob/master/machine/kvm_x86_64/mk-vm.sh,
and if that doesn't pan out let me know. I've got an upgraded version of that script that I'm working on because I can never remember what arguments qemu needs....)
Anyway:
  1. cd ./build-config
  2.  make -j4 MACHINE=kvm_x86_64 all demo

Let me know how it goes, and what things aren't clear in the documentation so I can get them straightened out.

Thanks
Alex Doyle
ONIE Project Lead


From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Sriram Ramkrishna <sriram.ramkrishna@...>
Sent: Tuesday, February 9, 2021 2:50 PM
To: ocp-onie@ocp-all.groups.io <ocp-onie@ocp-all.groups.io>
Subject: [OCP-ONIE] What's the correct best method for setting up ONiE development?
 
External email: Use caution opening links or attachments

I'm working on enabling a platform that was enabled before (Facebook Wedge 100) but has some issues. I'm trying to build the environment, but I'm currently having a lot of issues getting the cross compiler to get compiled. I've tried solutions like DUE - but I'm still having the same issues.

If there is a blog post, documentation, or video that I can look at - that would be very appreciated.

Cheers,
sri


Re: What's the correct best method for setting up ONiE development?

Alex Doyle
 

Hi Sri,
 
I really recommend DUE to set up the build environment using Docker containers for a couple of reasons:
  1. The standard configuration it applies is the same one I'm using for processing pull requests, development, and quarterly releases, so it should consistently provide the correct versions of everything needed to build.
  2. If there are problems, it provides a common frame of reference to debug them.
  3. And I'm using it for ONIE work, so any problems there get my attention pretty quick.
I'm getting the impression there are some weak points in the documentation for setting it up - yours isn't the first email asking setup questions - so if you can identify the things that are tripping you up, do let me know so I can make it clearer ( at this point I've been looking at things long enough to not see things that might be unclear to a set of fresh eyes. ) Hm. In writing out the rest of this, I'm thinking this 'quickstart' info needs to be more prominently featured in the documentation...

That aside, here's some actionable information:

So, DUE getting started:
  1. wget https://github.com/CumulusNetworks/DUE/releases/download/v2.3.0/due_2.3.0-1_all.deb  <-get latest release
  2. sudo dpkg -i due_2.3.0-1.all.deb  <- install it. Will throw missing dependency errors, that's fine
  3. sudo apt-get install --fix-broken    <- use APT to fix the missing dependencies. Will want to install Docker if you don't have it.

Then follow:
https://github.com/CumulusNetworks/DUE/blob/master/templates/onie/README.md

To use DUE to create an ONIE container. I'd recommend using the Debian 9 version (10 only works with the component-upgrade-2020 branch, which is not heavily tested yet, and probably breaks existing platforms at this point.)

./due --create --from debian:9 --description "ONIE Build Debian 9" --name onie-build-debian-9 --prompt ONIE-9 --tag onie --use-template onie

Then:
due --run 
...will let you select a container, or if there's only one, it'll run it and mount your home directory, at which point you should be able to build ONIE.

I've also got a tutorial video that should be mostly correct here:
https://www.youtube.com/watch?v=-5onRbZA0QQ

It's a number of DUE versions out of date, but I think the workflow still holds.

I'd also suggest starting by trying to build the kvm target
https://github.com/opencomputeproject/onie/tree/master/machine/kvm_x86_64
 (although you'll also need to install qemu if you want to run it. There is some help here:
https://github.com/opencomputeproject/onie/blob/master/machine/kvm_x86_64/mk-vm.sh,
and if that doesn't pan out let me know. I've got an upgraded version of that script that I'm working on because I can never remember what arguments qemu needs....)
Anyway:
  1. cd ./build-config
  2.  make -j4 MACHINE=kvm_x86_64 all demo

Let me know how it goes, and what things aren't clear in the documentation so I can get them straightened out.

Thanks
Alex Doyle
ONIE Project Lead


From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Sriram Ramkrishna <sriram.ramkrishna@...>
Sent: Tuesday, February 9, 2021 2:50 PM
To: ocp-onie@ocp-all.groups.io <ocp-onie@ocp-all.groups.io>
Subject: [OCP-ONIE] What's the correct best method for setting up ONiE development?
 
External email: Use caution opening links or attachments

I'm working on enabling a platform that was enabled before (Facebook Wedge 100) but has some issues. I'm trying to build the environment, but I'm currently having a lot of issues getting the cross compiler to get compiled. I've tried solutions like DUE - but I'm still having the same issues.

If there is a blog post, documentation, or video that I can look at - that would be very appreciated.

Cheers,
sri


What's the correct best method for setting up ONiE development?

Sriram Ramkrishna
 

I'm working on enabling a platform that was enabled before (Facebook Wedge 100) but has some issues. I'm trying to build the environment, but I'm currently having a lot of issues getting the cross compiler to get compiled. I've tried solutions like DUE - but I'm still having the same issues.

If there is a blog post, documentation, or video that I can look at - that would be very appreciated.

Cheers,
sri


Kernel config support for encryption on by default in upgraded ONIE kernel?

Alex Doyle
 

Hi everybody.
 I'm looking at the updated kernel configuration in the component-upgrade-2020 branch, and am thinking of having  configuration options around encryption enabled by default in the build-config/conf/kernel/<version>/linux.x86_64.config.
That would be options like (and not limited to):

CONFIG_ASYMMETRIC_KEY_TYPE 
CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE
CONFIG_X509_CERTIFICATE_PARSER 
CONFIG_PKCS7_TEST_KEY 
CONFIG_SIGNED_PE_FILE_VERIFICATION 

Machine configurations would, as usual, be able to override this if they did not want encryption features built in.

The reason this is coming up is that I'm working on component upgrade and ONIE tooling around secure boot support at the moment, and can't think of a good reason not to have encryption support as a default, but I'm also not an expert on both the kernel,  and everybody's use cases either. 🙂

Any thoughts?

Thanks!

Alex Doyle
ONIE Project Lead


Re: ARM N1 ONIE setup

Alex Doyle
 

Hi Kiel,

 I'd suggest taking a look at the Marvell a7020-comexp for reference - that looks like an armv8 system. There are a couple of armv7 platforms in there too for what it's worth.


Unfortunately the qemu_armv8 doesn't work at the moment, although once Secure Boot support is a thing, qemu_armv8  is the next project I'd like to see prioritized ( and if anybody out there has a pull request for it, the Q1 ONIE release should be out this week and pull request processing will start up again 🙂 ).


If you haven't yet got a build environment set up, I'd recommend using DUE - which configures a Docker container to create the same Debian 9 build environment that I'm using for releases, provided you've got a Debian or Red Hat Linux system to run it on:
https://github.com/CumulusNetworks/DUE/tree/master/templates/onie

The container configuration makes it easier to reproduce any build issues since everyone can use the same environment,  and it supports a new Debian 10 ONIE build environment that the new component-upgrade-2020 branch is being developed in, if you need newer component versions and aren't averse to stability risk 🙂
https://github.com/opencomputeproject/onie/tree/component-upgrade-2020

You'll probably want to go with the master branch, which has been pretty well exercised, and it's probably what the aforementioned a7020 is using.

Good luck!

Alex Doyle
ONIE Project Lead





From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Kiel Friedt <kiel.friedt@...>
Sent: Wednesday, February 3, 2021 3:12 PM
To: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io>
Subject: [OCP-ONIE] ARM N1 ONIE setup
 
External email: Use caution opening links or attachments

Hi All,

 

I work for ARM and I’ve been tasked with bring up SONIC on the latest N1 ARM cpu. I have been in talks with SONIC and they recommend installing ONIE on the N1 and using the KVM SONIC image once ONIE is installed. Browsing the platforms on ONIE, I do not see a generic ARM platform install. How would I install ONIE on a ARM machine? I understand that a qemu_armv8a is available is this recommended way of using ONIE on a ARM machine?

 

Thanks,

 

Kiel

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.


ARM N1 ONIE setup

Kiel Friedt
 

Hi All,

 

I work for ARM and I’ve been tasked with bring up SONIC on the latest N1 ARM cpu. I have been in talks with SONIC and they recommend installing ONIE on the N1 and using the KVM SONIC image once ONIE is installed. Browsing the platforms on ONIE, I do not see a generic ARM platform install. How would I install ONIE on a ARM machine? I understand that a qemu_armv8a is available is this recommended way of using ONIE on a ARM machine?

 

Thanks,

 

Kiel

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.


ONIE Monthly Status Call - Wednesday January 20 at 10AM, PST

Alex Doyle
 

Hi everyone.

The monthly ONIE project call is scheduled for Wed, January 20th at 10 AM, PST.

If that doesn't work, for some reason, here's the agenda:

Agenda

  • Published component-upgrade-2020 branch

  • Diverting to Secure Boot workflow validation

    • Create test/demo script for Secure Boot scenarios

  • Would like to see upgraded arm64 virtual machine work.

  • Default to using merge_config.sh as part of the kernel build in the component-upgrade branch, with an eye to merging it in to master later.

 Any objections?

Action Items

  • Some users are having difficulty setting up build environments. Need to figure out where the pain points are.

Notes and Status

  • Release candidate for the 2021-02 quarterly release is out



If you have a question but can't make the meeting, I'm also reachable as adoyle@...


...and if you're dialing in, see below.

Thanks!

Alex Doyle
ONIE Project Lead
adoyle@...

--------------------------------------------------------------------------
Dial in and Go To Meeting options:
United States: +1 (312) 757-3117
 Access Code: 564-377-669 

More phone numbers 
 Australia: +61 2 8355 1038 
 Austria: +43 7 2081 5337 
 Belgium: +32 28 93 7002 
 Canada: +1 (647) 497-9373 
 Denmark: +45 43 31 47 79 
 Finland: +358 942 72 0972 
 France: +33 187 210 241 
 Germany: +49 692 5736 7300 
 Ireland: +353 15 295 146 
 Italy: +39 0 230 57 81 80 
 Netherlands: +31 202 251 001 
 New Zealand: +64 9 913 2226
 Norway: +47 21 93 37 37 
 Spain: +34 932 75 1230 
 Sweden: +46 853 527 818 
 Switzerland: +41 315 2081 00 
 United Kingdom: +44 330 221 0097 

 Joining from a video-conferencing room or system? Dial: 67.217.95.2##564377669 Cisco devices: 564377669@... 
 First GoToMeeting? Let's do a quick system check: https://link.gotomeeting.com/system-check


Alpha ONIE component upgrade branch is available

Alex Doyle
 

Hi everybody,
 
I just added a development branch: component-upgrade-2020  to hold work on component upgrades to ONIE.*
https://github.com/opencomputeproject/onie/tree/component-upgrade-2020

The code is not production ready (see below) but unless it is made available for test and to get more eyes on it to find bugs, it never will be.
Once this stabilizes and supports ARM I'll consider merging it to master. Until that happens, pull requests and fixes will continue on the master branch.

So, what's in this code that I'm making an effort to set a really low bar for?

It builds on a Debian 10 system.
The x86 KVM target builds and runs.

So...yeah.
Oh, and it has the following new component versions:
automake:      1.15.1  
binutils:      2.32
crosstool-ng:  1.24.0
efivar:        37      
expat:         2.2.6
GCC version:   8.3.0  
Grub:          2.04
isl:           0.20
Kernel:        4.19.143
mokutil:       0.4.0
mpc:           1.1.0
mpfr:          3.1.6  
mpfr:          4.1.0
openssl:       1.1.1g
strace:        4.26    
uClibc-ng:     1.0.35  
zlib:          1.2.11

Caveats (or, where I think you'll find problems :) )
  • The configuration files for components could do with some more scrutiny. Given the amount of time that has elapsed since the last upgrade, there were a LOT of new configuration options. I have passing familiarity with the components, but am by no means an expert on all of them, so I'm hoping people will contribute fixes.
  • Not all patches were not ported forward. This was a combination of upgraded components already having the changes,  judgement calls, and probably missing things that did not cause fatal errors.
  • The kernel build is using the kernel's merge_config.sh script, so kernel configurations from the machine targets are no longer just appended. This has been a long standing pull request that I didn't merge to master because it broke about half the builds, but I feel it is best to use the tools provided by kernel developers going forward.
  • No upgrade work has been done for arm7 or arm8 - it's only x86 so far. I'm hoping that resolving issues in x86 will make the ARM transitions easier.
In conclusion, I wish the code was more polished, but as that's not going to happen without community input and I felt that getting it to a demonstrably functional state was a pre-requisite before asking other developers to start looking at it.

Let me know if you have any questions/comments.

Thanks!

Alex Doyle
ONIE Project Lead

*Why not 2021? Because the effort was started in 2020, and given how 2020 has set our expectations, it should be easy for the code to look good in comparison.


ONIE release candidate 2021.02-rc1 is available

Alex Doyle
 

Hi everyone, 
 
 I just tagged the February 2021 release candidate: 2021.02-rc1, so changes will be restricted for the next month or so.

There are no functional changes in this release. The build environment is still Debian 9, although the latest version of DUE
now supports Red Hat systems so they can run the same Debian 9 container I'm using for release builds.

I'm still hoping to publish a bunch of component upgrades and a Debian 10 build environment in the near future.

Thanks!
Alex Doyle
ONIE Project Lead

------------------------------- Release Candidate Notes -----------------------------


2021.02-rc1 Public Release                                                                                                                                                                  
                                                                                                                                                                                             
This release was produced using the Debian 9 based                                                                                                                                          
ONIE Docker build container configuration generated                                                                                                                                          
using Dedicated User Environment (DUE) version 2.3.0                                                                                                                                        
                                                                                                                                                                                             
Instructions and source for replicating this ONIE build                                                                                                                                      
environment are available at:                                                                                                                                                                
https://github.com/CumulusNetworks/DUE                                                                                                                                                      
                                                                                                                                                                                             
                                                                                                                                                                                             
New Hardware Platforms                                                                                                                                                                      
======================                                                                                                                                                                      
Delta:                                                                                                                                                                                      
 delta_tx4810                                                                                                                                                                                
 delta_agc7008s                                                                                                                                                                              
                                                                                                                                                                                             
Build and Release / Improvements                                                                                                                                                            
================================                                                                                                                                                            
Recommend users of the Docker build environment upgrade to DUE 2.3.0                                                                                                                        
https://github.com/CumulusNetworks/DUE                                                                                                                                                      
 This version should work on Red Hat systems as well.                                                                                                                                        
                                                                                                                                                                                             
                                                                                                                                                                                             
Bug Fixes / Improvements                                                                                                                                                                    
=========================                                                                                                                                                                    
NONE                                                                                                                                                                                        
                                                                                                                                                                                             
Misc:                                                                                                                                                                                        
=====                                                                                                                                                                                        
NONE  


ONIE Monthly Status Call is Wed, December 16th at 10AM, PST

Alex Doyle
 

Hi everyone.

The monthly ONIE project call is scheduled for Wed, December 16th at 10 AM, PST.


...but the big news is that I've finally got a first pass of ONIE component upgrades building and working for the KVM build, and what I'd 
be looking for feedback is how to make it available for testing. I'm thinking maybe a 'component-upgrade-2020' branch so that anyone
interested would be able to try it out for any particular platform without introducing potential instability into the mainline ONIE.  
Once it's had some test time, I'd then merge the branch in to master.

Looking forward I'm going to be pivoting to building up Secure Boot support with some demonstration and test tools with the goal of
establishing workflows that are flexible enough to apply to different use cases (manufacturer or NOS vendor, shim or no shim, etc...)

...and once that's cleared I'd like to get the ARM emulation working to follow through on component upgrade for platforms other
than x86.

If you have a question but can't make the meeting, I'm also reachable as adoyle@...


...and if you're dialing in, see below.

Thanks!

Alex Doyle
ONIE Project Lead
adoyle@...

--------------------------------------------------------------------------
Dial in and Go To Meeting options:
United States: +1 (312) 757-3117
 Access Code: 564-377-669 

More phone numbers 
 Australia: +61 2 8355 1038 
 Austria: +43 7 2081 5337 
 Belgium: +32 28 93 7002 
 Canada: +1 (647) 497-9373 
 Denmark: +45 43 31 47 79 
 Finland: +358 942 72 0972 
 France: +33 187 210 241 
 Germany: +49 692 5736 7300 
 Ireland: +353 15 295 146 
 Italy: +39 0 230 57 81 80 
 Netherlands: +31 202 251 001 
 New Zealand: +64 9 913 2226
 Norway: +47 21 93 37 37 
 Spain: +34 932 75 1230 
 Sweden: +46 853 527 818 
 Switzerland: +41 315 2081 00 
 United Kingdom: +44 330 221 0097 

 Joining from a video-conferencing room or system? Dial: 67.217.95.2##564377669 Cisco devices: 564377669@... 
 First GoToMeeting? Let's do a quick system check: https://link.gotomeeting.com/system-check


Re: ONIE on OCP Github

Rajeev Sharma
 

Alex, thanks for the great response. 

 --Rajeev


On Wed, Nov 18, 2020 at 11:02 AM Alex Doyle <adoyle@...> wrote:
Hi Rajeev,
 The answer to both questions is yes - but that's because there's some flexibility in how ONIE gets some of the components it builds.

There's the OCP GitHub:
https://github.com/opencomputeproject/onie
which is the starting point for an ONIE build, and if it becomes unavailable, then anybody who hasn't already cloned it is out of luck.

Then there is some flexibility in the rest of the process.

Provided one has the source, ONIE pulls specific versions of open source software to build - from crosstool-ng, which sets up all the cross compile tools, to versions of the kernel, to run time programs, like BusyBox and GRUB. 

Now it can go to the hosting pages of those projects (ONIE has the URLs) , and download from there ( which doesn't always work as some projects have moved around ), but first it tries the OCP mirror here:
http://mirror.opencompute.org/onie/
...which addresses the problem of finding older versions of software, and is far and away the most convenient option.

The only software I can think of that one wouldn't be able to get from the mirror is a proprietary, although the only example I have is 'linux-fsl-sdk*.tar.bz', versions 1.5 to 1.8 which is used by some PowerPC switches with FreeScale processors.  I did some digging for that a while back after my 'rebuild the world' audit to get a baseline of what platforms built under what conditions showed 5 switches failing without it, which got noted here:
https://github.com/opencomputeproject/onie/blob/d045b605851a07f390efc7c04d6e4776f9d39a0e/build-config/scripts/onie-build-targets.json#L17

Now, if one has to build without direct internet access, there are a couple of options
( See Cache of Downloaded Packages, here: https://opencomputeproject.github.io/onie/faq/index.html )
But briefly:

  1. If you have a local http server, you can configure ONIE to point to it:
    https://opencomputeproject.github.io/onie/faq/index.html?highlight=local%20mirror
  2. Or you can set up a cache on your build system under /var/cache/onie/downloads,  download the contents of the OCP mirror there, and then use a compiler flag to have ONIE go looking there for source.  
I've found the latter option to be really useful on a laptop, or in bandwidth restricted situations.

So in summary, once you have the ONIE code, you can have the build get the additional source packages from:
  • The OCP mirror
  • The hosting site of the package (ONIE holds the URLs for it
  • A local network mirror
  • A directory on your build system

...the latter two, of course, require some foresight to set up, since they obviously require Internet access to get set up to begin with.

Thanks,

Alex Doyle
ONIE Project Lead




From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Rajeev Sharma <rajeev@...>
Sent: Wednesday, November 18, 2020 7:47 AM
To: OCP-ONIE@ocp-all.groups.io <OCP-ONIE@ocp-all.groups.io>
Subject: [OCP-ONIE] ONIE on OCP Github
 
External email: Use caution opening links or attachments

I had a question for the OCP ONIE team.

Is all the ONIE source code located in the OCP Github repository and one can build executables from the makefiles? OR some part of the source code/build files are residing externally to the OCP repository. 
 

 --Rajeev


Re: ONIE on OCP Github

Alex Doyle
 

Hi Rajeev,
 The answer to both questions is yes - but that's because there's some flexibility in how ONIE gets some of the components it builds.

There's the OCP GitHub:
https://github.com/opencomputeproject/onie
which is the starting point for an ONIE build, and if it becomes unavailable, then anybody who hasn't already cloned it is out of luck.

Then there is some flexibility in the rest of the process.

Provided one has the source, ONIE pulls specific versions of open source software to build - from crosstool-ng, which sets up all the cross compile tools, to versions of the kernel, to run time programs, like BusyBox and GRUB. 

Now it can go to the hosting pages of those projects (ONIE has the URLs) , and download from there ( which doesn't always work as some projects have moved around ), but first it tries the OCP mirror here:
http://mirror.opencompute.org/onie/
...which addresses the problem of finding older versions of software, and is far and away the most convenient option.

The only software I can think of that one wouldn't be able to get from the mirror is a proprietary, although the only example I have is 'linux-fsl-sdk*.tar.bz', versions 1.5 to 1.8 which is used by some PowerPC switches with FreeScale processors.  I did some digging for that a while back after my 'rebuild the world' audit to get a baseline of what platforms built under what conditions showed 5 switches failing without it, which got noted here:
https://github.com/opencomputeproject/onie/blob/d045b605851a07f390efc7c04d6e4776f9d39a0e/build-config/scripts/onie-build-targets.json#L17

Now, if one has to build without direct internet access, there are a couple of options
( See Cache of Downloaded Packages, here: https://opencomputeproject.github.io/onie/faq/index.html )
But briefly:

  1. If you have a local http server, you can configure ONIE to point to it:
    https://opencomputeproject.github.io/onie/faq/index.html?highlight=local%20mirror
  2. Or you can set up a cache on your build system under /var/cache/onie/downloads,  download the contents of the OCP mirror there, and then use a compiler flag to have ONIE go looking there for source.  
I've found the latter option to be really useful on a laptop, or in bandwidth restricted situations.

So in summary, once you have the ONIE code, you can have the build get the additional source packages from:
  • The OCP mirror
  • The hosting site of the package (ONIE holds the URLs for it
  • A local network mirror
  • A directory on your build system

...the latter two, of course, require some foresight to set up, since they obviously require Internet access to get set up to begin with.

Thanks,

Alex Doyle
ONIE Project Lead




From: OCP-ONIE@OCP-All.groups.io <OCP-ONIE@OCP-All.groups.io> on behalf of Rajeev Sharma <rajeev@...>
Sent: Wednesday, November 18, 2020 7:47 AM
To: OCP-ONIE@ocp-all.groups.io <OCP-ONIE@ocp-all.groups.io>
Subject: [OCP-ONIE] ONIE on OCP Github
 
External email: Use caution opening links or attachments

I had a question for the OCP ONIE team.

Is all the ONIE source code located in the OCP Github repository and one can build executables from the makefiles? OR some part of the source code/build files are residing externally to the OCP repository. 
 

 --Rajeev


ONIE on OCP Github

Rajeev Sharma
 

I had a question for the OCP ONIE team.

Is all the ONIE source code located in the OCP Github repository and one can build executables from the makefiles? OR some part of the source code/build files are residing externally to the OCP repository. 
 

 --Rajeev


ONIE monthly status call is Wednesday, November 17th at 10:00 AM PST

Alex Doyle
 

Hi everyone.

The monthly ONIE project call is scheduled for Wed, November 18th at 10 AM, PST.
Not much new this month - the latest quarterly release is out, and I'm discovering workflows for debugging kernel/initrd problems which have
sidetracked me some from updating components, but I'll still be available to discuss any topics.

If you have a question but can't make the meeting, I'm also reachable as adoyle@...


...and if you're dialing in, see below.

Thanks!

Alex Doyle
ONIE Project Lead
adoyle@...

--------------------------------------------------------------------------
Dial in and Go To Meeting options:
United States: +1 (312) 757-3117
 Access Code: 564-377-669 

More phone numbers 
 Australia: +61 2 8355 1038 
 Austria: +43 7 2081 5337 
 Belgium: +32 28 93 7002 
 Canada: +1 (647) 497-9373 
 Denmark: +45 43 31 47 79 
 Finland: +358 942 72 0972 
 France: +33 187 210 241 
 Germany: +49 692 5736 7300 
 Ireland: +353 15 295 146 
 Italy: +39 0 230 57 81 80 
 Netherlands: +31 202 251 001 
 New Zealand: +64 9 913 2226
 Norway: +47 21 93 37 37 
 Spain: +34 932 75 1230 
 Sweden: +46 853 527 818 
 Switzerland: +41 315 2081 00 
 United Kingdom: +44 330 221 0097 

 Joining from a video-conferencing room or system? Dial: 67.217.95.2##564377669 Cisco devices: 564377669@... 
 First GoToMeeting? Let's do a quick system check: https://link.gotomeeting.com/system-check



ONIE 2020.11 release is now available.

Alex Doyle
 

Hi everyone.

The November 2020 quarterly release is now available, and I expect to start processing new pull requests shortly.   Release notes follow.

Thanks!
Alex Doyle
ONIE Project Lead


020.11 Public Release

This release was produced using the Debian 9 based
ONIE Docker build container configuration generated
using Dedicated User Environment (DUE) version 2.0.0

Instructions and source for replicating this ONIE build
environment are available at:
https://github.com/CumulusNetworks/DUE


New Hardware Platforms
======================
Pegatron common_bde
         ...and support for the FN-8032-BN-F series
Quanta   QuantaMesh COME CPU board
Delta    delta_tn48m

Build and Release / Improvements
================================
Recommend users of the Docker build environment upgrade to DUE 2.0.0
https://github.com/CumulusNetworks/DUE

ipmitool - upgraded from 1.8.15 to 1.8.18

Bug Fixes / Improvements
=========================
NONE

Misc:
=====
NONE


Commit statistics:

Developers with the most changesets
Wolf Lin                     2 (33.3%)
Alex Doyle                   1 (16.7%)
Audi Hsu                     1 (16.7%)
will_kuo                     1 (16.7%)
os-vincent.liu               1 (16.7%)

Developers with the most changed lines
os-vincent.liu            35081 (94.8%)
Wolf Lin                  1299 (3.5%)
will_kuo                   610 (1.6%)
Audi Hsu                     3 (0.0%)
Alex Doyle                   1 (0.0%)

Developers with the most lines removed

Developers with the most signoffs (total 12)
Alex Doyle                   5 (41.7%)
Max Lee                      2 (16.7%)
Wolf Lin                     2 (16.7%)
Audi Hsu                     1 (8.3%)
will_kuo                     1 (8.3%)
os-vincent.liu               1 (8.3%)

Developers with the most reviews (total 0)

Developers with the most test credits (total 0)

Developers who gave the most tested-by credits (total 0)

Developers with the most report credits (total 0)

Developers who gave the most report credits (total 0)

Top changeset contributors by employer
Quanta Cloud Technology      2 (33.3%)
wolf_lin@...    2 (33.3%)
NVidia                       1 (16.7%)
Delta Networks               1 (16.7%)

Top lines changed by employer
Delta Networks            35081 (94.8%)
wolf_lin@... 1299 (3.5%)
Quanta Cloud Technology    613 (1.7%)
NVidia                       1 (0.0%)

Employers with the most signoffs (total 12)
Cumulus Networks             3 (25.0%)
wolf_lin@...    2 (16.7%)
Quanta Cloud Technology      2 (16.7%)
NVidia                       2 (16.7%)
max_lee@...     2 (16.7%)
Delta Networks               1 (8.3%)

Employers with the most hackers (total 5)
Quanta Cloud Technology      2 (40.0%)
wolf_lin@...    1 (20.0%)
NVidia                       1 (20.0%)
Delta Networks               1 (20.0%)













OCP Networking Community - Don't miss your workshop @ OCP TECH WEEK!

Kali Burdette
 

OCP Networking Group,

Don't forget that OCP TECH WEEK starts today! We hope you'll join us for a day of updates and insights from the OCP Foundation and our volunteer leadership. 

If you haven't already, register here so that you can participate in the Networking workshop that will be held tomorrow, Tuesday from 7am-Noon PT and Friday, Nov 13 from 8am-Noon PT. 

Thanks and see you there!

Kali

Kali Burdette, CMP
Open Compute Project Foundation
Event Manager
Office: Lexington, KY (EST)
859.512.2366

Register today for our fall virtual event, OCP TECH WEEK – November Nov 9-10 & 12-13 – featuring OCP Foundation updates and technical deep dives into the OCP Project Groups!


ONIE 2020.11 release candidate is available.

Alex Doyle
 

Hi everyone,
 I just tagged the November 2020 release candidate: 2020.11-rc1, so changes will be restricted for the next month or so.

Apart from a few new platforms, the version of ipmitool has incremented to a more recent release, should any platforms
want to take advantage of that.

Thanks!
Alex Doyle
ONIE Project Lead

------------------------------- Release Candidate Notes -----------------------------

2020.11 Public Release                                                
                                                                     
This release was produced using the Debian 9 based                    
ONIE Docker build container configuration generated                  
using Dedicated User Environment (DUE) version 2.0.0                  
                                                                     
Instructions and source for replicating this ONIE build              
environment are available at:                                        
https://github.com/CumulusNetworks/DUE                                
                                                                     
                                                                     
New Hardware Platforms                                                
======================                                                
Pegatron common_bde                                                  
         ...and support for the FN-8032-BN-F series                  
Quanta   QuantaMesh COME CPU board                                    
Delta    delta_tn48m                                                  
                                                                     
Build and Release / Improvements                                      
================================                                      
Recommend users of the Docker build environment upgrade to DUE 2.0.0  
https://github.com/CumulusNetworks/DUE                                
                                                                     
ipmitool - upgraded from 1.8.15 to 1.8.18                            
                                                                     
Bug Fixes / Improvements                                              
=========================                                            
NONE                                                                  
                                                                     
Misc:                                                                
=====                                                                
NONE                                                                  


21 - 40 of 180