networking: persistent trip ID to prevent purge loop in parallel install

The following tests have been performed: we have two sets: old install
(O) and new (N). O->N success N->N success N->O success N->N with the
same trip ID injected (success).

Platforms-Affected: all ttf
Tested: yes
Google-Bug-Id: 425490715
Tested: in progress.
Fusion-Link: fusion2 n/a
Change-Id: I28ed2957e6195d9dcbdca9cd0b714a288074774b
Signed-off-by: Mo Elbadry <elbadrym@google.com>
(cherry picked from commit 1d0a72b62246638b77037d23a38e70b02d388b37)
(cherry picked from commit a8801d24081bf7581a3cf3b7abe183d110210ca0)
3 files changed
tree: 7a8bacf4078fe219c564370281d1c2ee5b6fcb7b
  1. classes/
  2. conf/
  3. dynamic-layers/
  4. recipes-bsp/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-google/
  10. recipes-kernel/
  11. recipes-phosphor/
  12. recipes-support/
  13. recipes-tpm1/
  14. recipes-tpm2/
  15. LICENSE
  16. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.