baserock/baserock/definitions.git - gitlab.com: baserock/definitions.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	pxeboot.check: Check if nfs-server is running when is needed	Pedro Alvarez	2014-12-23	1	-0/+10
\|
*	pxeboot.check: Fail with a nice error if PXEBOOT_MODE is needed and not set	Pedro Alvarez	2014-12-23	1	-2/+9
\| \| \| \| \|	This is needed because now pxeboot.check doesn't fail if the options specified in the environment match more than one mode.
*	pxeboot.check: Multiple complete_matches is not an error	Pedro Alvarez	2014-12-23	1	-2/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The code was assuming that if there are more than one complete_match we were setting more options that needed and this is not always true. For example when setting 'PXEBOOT_DEPLOYER_INTERFACE' and 'PXEBOOT_VLAN', there will be more than one complete_matches, given that these options match the spawn-vlan and the spawn-novlan modes. My workaround consists on report warning messages instead of failing when this happens. The reason that I haven't removed the code is that I think that it could be fixable. For now this code will report "warnings" instead of failing.
*	pxeboot.check: Fix a couple of syntax errors in the code	Pedro Alvarez	2014-12-23	1	-2/+3
\|
*	Add pxeboot write extension.	Richard Maw	2014-11-14	1	-0/+69
	It has 4 modes. 1. Specify PXEBOOT_DEPLOYER_INTERFACE and PXEBOOT_VLAN to configure the target to pxeboot on a vlan and spawn a dhcp, nfs and tftp server. This is potentially the fastest, since it doesn't need to copy data to other servers. 2. Specify PXEBOOT_DEPLOYER_INTERFACE without PXEBOOT_VLAN to configure do 1, but without creating the vlan interface. This assumes that you have exclusive access to the interface, such as if you're plugged in to the device directly, or your interface is vlanned by your infrastructure team. This is required if you are serving from a VM and bridging it to the correct network via macvtap. For this to work, you need to macvtap bridge to a pre-vlanned interface on your host machine. 3. Specify PXEBOOT_DEPLOYER_INTERFACE and PXEBOOT_CONFIG_TFTP_ADDRESS to put config on an existing tftp server, already configured by the dhcp server. This spawns a tftp server and configures the local nfs server, but doesn't do a dhcp server. This is useful if you have already got a dhcp server that serves PXE images. 4. Specify at least PXEBOOT_CONFIG_TFTP_ADDRESS and PXEBOOT_ROOTFS_RSYNC_ADDRESS to specify existing servers to copy config, kernels and the rootfs to. The mode detection can be overridden by specifying PXEBOOT_MODE. Mode 1 is `spawn-vlan`. Mode 2 is `spawn-novlan`, Mode 3 is `existing-dhcp` and Mode 4 is `existing-server`.