Support

Contact

ZTPServer is an Arista-led open source community project. Users and developers are encouraged to contribute to the project. See CONTRIBUTING for more details.

Community-based support is available through:

Commercial support, customization, and integration services are available through the EOS+ team at Arista Networks, Inc. Contact eosplus-dev@arista.com for details.

Known caveats

The authoritative state for any known issue can be found in GitHub issues.

  • v1.1: The management interfaces may not be used as valid local interface names in neighbordb. When creating patterns, use any instead. (fixed in v1.2)
  • Only a single entry in a resource pool may be allocated to a node.
  • Users MUST be aware of the required EOS version for various hardware components (including transcievers). Neighbor (LLDP) validation may fail if a node boots with an EOS version that does not support the installed hardware. Moreoever, some EOS features configured via ZTPServer might be unsupported. Please refer to the Release Notes for more compatability information and to the Transceiver Guide .

Releases

The authoritative state for any known issue can be found in GitHub issues.

Roadmap highlights

The authoritative state, including the intended release, for any known issue can be found in GitHub issues. The information provided here is current at the time of publishing but is subject to change. Please refer to the latest information in GitHub issues by filtering on the desired milestone.

Release 1.3

Target: January 2015

  • validate all YAML files via ‘ztpserver –validate’ (247)
  • action which enables running arbitrary set of EOS CLI commands (211)
  • show server’s version in startup logs (207)
  • command-line option for clearing resource pools (163)
  • hook to run script after posting files on the server (132)
  • action which enables running arbitrary bash commands (108)

Release 2.0

Target: March 2015

  • configure HTTP timeout in bootstrap.conf (246)
  • all requests from the client should contain the unique identifier of the node (188)
  • dual-sup support for install_extension action (180)
  • dual-sup support for install_cli_plugin action (179)
  • dual-sup support for copy_file action (178)
  • action for arbitrating between MLAG peers (141)
  • plugin infrastructure for resource pool allocation (121)
  • md5sum checks for all downloaded resources (107)
  • topology-based ZTR (103)

Other Resources

ZTPServer documentation and other reference materials are below: