{% from 'host/common.html' import edit_field %}

<h4 class="info-text-left">Select Software Packages: <span id="server-dialog-title"></span>

&nbsp;&nbsp;<a href="javascript://"><span class="glyphicon glyphicon-info-sign" style="color:dodgerblue" aria-hidden="true" data-toggle="popover_server_repo"></span></a>
</h4>
<div id="popover_packages" style="display: none">
  <pre>Note:
1. Only FTP, SFTP and TFTP server repositories are supported for migration.
2. Only two packages can be selected:
   a. You must select either a Golden ISO migration tar file or a mini ISO migration tar file.
      This file should contain the ASR9K-X64 Golden or mini ISO image and additional boot files.
      (For more details, refer to Help > ASR9K to ASR9K-X64 Migration > ASR9K-X64 Image.)
      The filename need to match wildcard expression 'asr9k*.tar*'; it must also contain the
      software version of ASR9K-X64, i.e., "6.1.3". The software version cannot be lower than
      6.1.3 as that is the minimal baseline ASR9K-X64 you can migrate to.
   b. If you are migrating with a k9 migration tar file, you can optionally select a crypto key
      generation text file if you wish that the system automatically generates crypto keys for you
      right after migration. This text file should enlist commands that generate crypto keys. The
      commands enlisted in the file will be automatically run in ASR9K-X64 as k9sec package loads.
      For more details, refer to Help > ASR9K to ASR9K-X64 Migration > Scheduling a Migration.
      If the file is named "crypto_auto_key_gen.txt", you can click Auto Select to select it.
   </pre>
</div>

{{ edit_field(schedule_form.server_dialog_server, field_width="col-sm-7", class="form-control") }}
          
{% set extra_field =
'<a href="javascript://">
<img id="server-dialog-move-up" src="/static/up_arrow.png" title="Go to Parent Folder">
<img id="server-dialog-reset-server-directory" src="/static/remove.png" title="Reset Server Directory">
</a>'
%}

{{ edit_field(schedule_form.server_dialog_server_directory, field_width="col-sm-7", class="form-control", extra_field=extra_field) }}
<legend></legend>


<div id="server-dialog-auto-select-software-panel">
  <button id="server-dialog-auto-select-software" class="btn btn-primary center-block">Auto Select</button>
</div>


<div class="form-group">
<select id="server-software-selector" name="server-software-selector" multiple="multiple" data-title="Packages" data-json=false></select>
</div>


<span class="browse-spinner">
  <center><img id="server-software-dialog-browse-spinner" src="{{ url_for('static', filename='spinner.gif') }}"></center>
</span>
<legend></legend>

<div class="row">
    <div class="pull-left">
        <h4 class="info-text-left" style="margin-left: 20px;">Select a custom ASR9K-X64 config file to be loaded after migration:
  &nbsp;&nbsp;      <a href="javascript://"><span class="glyphicon glyphicon-info-sign" style="color:dodgerblue" aria-hidden="true" data-toggle="popover_config_filename"></span></a>
        </h4>
    </div>
    <div class="pull-right" style="height: 20px;">
       <select class="form-control" id="config_filename" style="width: 300px;margin-top: 5px;margin-right: 20px" placeholder="Optional">
        <option value="" disabled selected style="display: none;">Optional</option>
        <option value=""></option>
      </select>
    </div>
</div>

<div id="popover_config" style="display: none">
  <pre>Note:
If no file is provided here, CSM Server will migrate the existing admin and IOS-XR config
files on device using the NoX tool. Then, during Migrate, when ASR9K-X64 boots, the device
will load the converted admin and IOS-XR config files automatically.

Alternatively, you can supply an IOS-XR config for the ASR9K-X64 image. Once the new 64 bit
image boots, during Migrate, the device will load the converted admin config file as well as
this customized IOS-XR config file.</pre>
</div>
<legend></legend>