GNS3 checks the schema version, if the schema of an appliance is not supported it shows the error "Please update GNS3 in order to install this appliance".
* Support for `uefi_boot_mode` property in Qemu template properties.
* Possibility to have multiple set of settings to use with different image versions. Default settings are specified if
1. a `default` field set to `true` exists
2. there is only one set present.
**Notes**
A `template_type` field must be added to tell GNS3 what template to create (qemu, iou, dynamips or docker), mixing different template types is not supported at the moment.
All template specific properties are defined in a `template_properties` field.
**Example**
```json
"settings": [
{
"default": true,
"template_type": "qemu",
"template_properties": {
"platform": "x86_64",
"adapter_type": "e1000",
"adapters": 1,
"ram": 1024,
"console_type": "vnc"
}
},
{
"name": "i386 settings",
"template_type": "qemu",
"template_properties": {
"platform": "i386",
"adapters": 8
}
},
{
"name": "ARM settings",
"template_type": "qemu",
"template_properties": {
"platform": "arm",
"ram": 512
}
}
],
"versions": [
{
"name": "1.0",
"images": {
"hda_disk_image": "disk1.qcow2"
}
},
{
"name": "2.0",
"settings": "i386 settings",
"images": {
"hda_disk_image": "disk2.qcow2"
}
},
{
"name": "3.0",
"settings": "ARM settings",
"images": {
"hda_disk_image": "disk3.qcow2"
}
},
]
```
* The default settings are inherited by other settings set, this can be blocked by setting `inherit_default_properties` to `false`
* The controller template default is used if a template property is not defined or inherited from the default settings.
* The `md5sum` field is renamed `checksum`. The `md5sum` field is still accepted for easier migration from previous format versions.
* New optional `checksum_type` field for future development. The default and only checksum type remains MD5 for now.
* New optional `default_username` and `default_password` fields at the appliance and version levels.
* New optional `installation_instructions` field at the appliance and version levels to give download/unpack instructions to some appliances.
* New optional `compression_target` field to be used along with the compression field in future development.
* The `idlepc` field in versions section is moved to the `template_properties` for the `dynamips` template type
* The `first_port_name`, `port_name_format`, `port_segment_size` and `linked_clone` fields are moved to the `template_properties` for the qemu template type (these fields are only valid for Qemu templates).
* The `arch` field for qemu has been renamed `platform` to match the template properties on the controller side.
* The `kvm` field has been dropped and no longer required. Installing an appliance shouldn't take into account the available servers and their capabilities (e.g. capable of running kvm etc.)
* The `category`, `usage` and `symbol` fields can be defined in any `template_properties`. Defaults are at the appliance level or version level (they will be injected in `template_properties` if there aren't already defined there).
* The appliance version installed will be injected in the `version` field of the template (only controller version >= v3.0)
* Add `name` and `default_name_format` fields to all template properties.
* Add `console_resolution`, `extra_hosts` and `extra_volumes` to Docker template properties.
* Allow `spice+agent` in `console_type` for Qemu template properties.
