Remove BESS patches and directly modify ONF's BESS with these changes

[gab-arrobo]

The goal of this patch is to apply the BESS patches directly into the ONF's BESS fork instead of having them here and apply them during the Docker build process.

ONF's BESS PR 1 include the patches that were removed from here. So, the changes here go along with ONF's BESS PR 1. That is, I expect the Pull Request task/check to fail until ONF's BESS PR 1 is merged

[omecproject]

Can one of the admins verify this patch?

[amarsri28]

@gab-arrobo just trying to understand benefit of this PR's . could you pls explain.

for me and other developers who complained about ( -security team team while developing sgx)-its being a big pain as i need to first file build bess for data plane changes, do corresponding changes in pfcp and then then fetch bess and do debugging in upf for every single patch. for small changes that might be ok but for big patches its a length process. lets discuss it

[gab-arrobo]

@gab-arrobo just trying to understand benefit of this PR's . could you pls explain.

for me and other developers who complained about ( -security team team while developing sgx)-its being a big pain as i need to first file build bess for data plane changes, do corresponding changes in pfcp and then then fetch bess and do debugging in upf for every single patch. for small changes that might be ok but for big patches its a length process. lets discuss it

@amarsri28, the goal of this PR is to try to simplify the whole development process. The first step is to apply the bess patches (patches/bess/*.patch) directly into the ONF's BESS repo. So, the process of applying these patches to create a new patch in BESS would not be needed anymore

[amarsri28]

@gab-arrobo @thakurajayL this patch set has broken compilation of upf-epc - (reported by community member ). better keep upf repo up unless we prepare bess in background , its ok even though migration take time .