Project

General

Profile

Feature #16190

Support Arista EOS ZTP bootstrap as an operating system

Added by Andrew Cooper over 5 years ago. Updated over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Unattended installations
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Arista Switches support a ZTP (Zero Touch Provisioning) deployment. Their implementation uses the dhcp bootfile-name as a url instead of a local tftp file which would be managed by foreman.

I attempted to create a new operating system class, but failed to make the bootfile configurable due to boot_filename method only being passed the context of the nic (Nic::Managed) and not the host. It seems the assumption was that only nic-related variables would be useful in the bootfile name.

I would like to use either the media path/url defined by the operating system/hostgroup, or use a global/host parameter. Both of these seem to require additional context passed to boot_filename method, or a different approach all-together.

Any ideas? Additional reading below.

https://eos.arista.com/intelligent-bootstrap-with-arista-eos-and-ztpserver/
http://ztpserver.readthedocs.io/en/master/install.html#configure-the-dhcp-service

subnet 192.168.100.0 netmask 255.255.255.0 {
range 192.168.100.200 192.168.100.205;
option routers 192.168.100.1;
option domain-name-servers <ipaddr>;
option domain-name "<org>";
option bootfile-name "http://<ztp_hostname_or_ip>:<port>/bootstrap";
}

History

#1 Updated by Dominic Cleal over 5 years ago

  • Category set to Unattended installations

Also available in: Atom PDF