patches/opnfv-fuel/0004-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/f_isoroot/f_bootstrap/bootstrap_admin_node.sh | 2 +-
  10  1 file changed, 1 insertion(+), 1 deletion(-)
  11
  12 --- a/build/bootstrap_admin_node.sh.patch
  13 +++ b/build/bootstrap_admin_node.sh.patch
  14 @@ -53,6 +53,23 @@
  15    # Enable iptables
  16    systemctl enable iptables.service
  17  ***************
  18 +*** 484,490 ****
  19 +          local ret=1
  20 +          echo ${bs_progress_message} >&2
  21 +          set_ui_bootstrap_error "${bs_progress_message}" >&2
  22 +!         if fuel-bootstrap -v --debug build --activate >>"$bs_build_log" 2>&1; then
  23 +            ret=0
  24 +            fuel notify --topic "done" --send "${bs_done_message}"
  25 +          else
  26 +--- 484,490 ----
  27 +          local ret=1
  28 +          echo ${bs_progress_message} >&2
  29 +          set_ui_bootstrap_error "${bs_progress_message}" >&2
  30 +!         if fuel-bootstrap -v --debug build --target_arch arm64 --activate >>"$bs_build_log" 2>&1; then
  31 +            ret=0
  32 +            fuel notify --topic "done" --send "${bs_done_message}"
  33 +          else
  34 +***************
  35  *** 529,534 ****
  36  --- 541,556 ----
  37