patches/opnfv-fuel/0021-Build-bootstrap-image-for-arm64.patch

   1 From: Stanislaw Kardach <stanislaw.kardach@caviumnetworks.com>
   2 Date: Thu, 3 Mar 2016 19:04:07 +0100
   3 Subject: [PATCH] Build bootstrap image for arm64
   4
   5 For now the arch is hardcoded for simplicity. We should detect this
   6 but how? If we're multi-arch then one bootstrap image should be built
   7 per supported arch. This requires Fuel refactoring.
   8 ---
   9  build/bootstrap_admin_node.sh.patch | 17 +++++++++++++++++
  10  1 file changed, 17 insertions(+)
  11
  12 diff --git a/build/bootstrap_admin_node.sh.patch b/build/bootstrap_admin_node.sh.patch
  13 index aeef3f7..c66b497 100644
  14 --- a/build/bootstrap_admin_node.sh.patch
  15 +++ b/build/bootstrap_admin_node.sh.patch
  16 @@ -53,6 +53,23 @@
  17    # Enable iptables
  18    systemctl enable iptables.service
  19  ***************
  20 +*** 484,490 ****
  21 +          local ret=1
  22 +          echo ${bs_progress_message} >&2
  23 +          set_ui_bootstrap_error "${bs_progress_message}" >&2
  24 +!         if fuel-bootstrap -v --debug build --activate >>"$bs_build_log" 2>&1; then
  25 +            ret=0
  26 +            fuel notify --topic "done" --send "${bs_done_message}"
  27 +          else
  28 +--- 484,490 ----
  29 +          local ret=1
  30 +          echo ${bs_progress_message} >&2
  31 +          set_ui_bootstrap_error "${bs_progress_message}" >&2
  32 +!         if fuel-bootstrap -v --debug build --target_arch arm64 --activate >>"$bs_build_log" 2>&1; then
  33 +            ret=0
  34 +            fuel notify --topic "done" --send "${bs_done_message}"
  35 +          else
  36 +***************
  37  *** 529,534 ****
  38  --- 541,556 ----
  39