GitLab

This can be used to specify a URI hosting a Windows answer file to be
injected to the image during deployment. Depending on the image (windows
or windows-legacy) this file can either be an xml file (unattend.xml) or
an inf one (sysprep.inf). The file gets higher priority than the file
that may be hosted inside the image.

This can be used to specify the time zone in the answer file that will
be injected to the Windows Image.

If a windows-legacy image does not host a sysprep.inf file, then add
one during the deployment. The default one is hosted by snf-image-host
and is passed to snf-image-helper through the configuration floppy. The
same mechanism is used for unattend.xml, where the default file is moved
to snf-image-host.

The administrator password in Windows XP is a special case. If the
AdminPassword entry of the GuiUnattended section is missing, then the
installation is not unattended.

In InstallUnattend task, check if the image is sysprepped. If this is
not the case, then fail.

If the OSFAMILY is 'windows', the NT Version must be at least 6.0. If
the OSFAMILY is 'windows-legacy', the NT Version must be less than 6.0.

Move there the offline resize code of NTFS. It's better to perform this
after the customization has finished since ntfsresize will mark the file
system as dirty as mounting it is not safe.

Theoretically, if an image contains an XFS filesystem with no free
space, the deployment will fail unless the FilesystemResizeMounted
tasks runs before any other mounted task. The only exception to this
is InstallUnattend which the task depends on.

Product key is a 25-character code and not a 20-character one.

Fix a bug where the created result file of the helper VM was created
under /usr.

This can be used to license a Windows deployment

Make sure that the file always contains a "[Commands]" section.

Do not expect the ChangeAdminPassword.cmd and diskpart.exe
RunSynchronousCommand entries to be present in the Unattend.xml file.
Check for their presence and add them if needed.

The DisableRemoteDesktopConnection task is nowadays self-standing. It
will make sure that RDP will be enabled in the first boot if it gets
disabled by this task. There is no need to have this entry in the
default unattend.xml file.

If a needed unattend.xml component like 'Microsoft-Windows-Shell-Setup'
is needed but missing, add it.

There is no need to log it. We only want to check if the file system
is clean.

* Add processorArchitecture="x86" entries in the default Unattend.xml
* Detect the image's architecture and apply the unattend.xml changes to
  the suitable components

 * Use the default namespace instead of defining it
 * Fetch the wcm namespace from the unattend.xml file
 * Add the needed XML nodes if missing

In jessie, awk by default is mawk and some features like the "match"
function are not present there.

Remove the following entries from the default unattend.xml:
 * DoNotOpenInitialConfigurationTasksAtLogon=true
 * DoNotOpenServerManagerAtLogon=true
 * CopyProfile=true
 * DoNotCleanTaskBar=true

They are not required for having an unattended installation and they
define a policy.

Check if a user exists before assigning a password in ChangePassword
task.

If the user has not provided an OSFAMILY, snf-image will try to detect
it. On Windows, check the registry key:
'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' to determine if the
correct OSFAMILY is 'windows' of 'windows-legacy'.

Otherwise the log file gets filled with control characters and progress
info that is useless.

Add a new OSFAMILY for Windows OSes prior to Windows Vista that use the
old Windows NT sysprep format. For now, this is only tested in Windows
Server 2003 and Windows XP

There is no reason to treat it different from any other Configuration
Tasks that needs to run after InstallUnattend and before
EnforcePersonality.

Fix the code for OFFLINE_NTFSRESIZE and OFFLINE_NTFSRESIZE_NOCHECK
image properties.

The main goal of this patch set is to add support for Windows XP/Server
2003 Images.  In the process, it also adds:

 * The ability for a simple debug shell under KVM, so a developer or the
   administrator can access the helper VM directly for simpler debugging,
 * Robust helper shutdown and mounting/un-mounting of NTFS, fixing the
   remote possibility of data loss.

Conflicts:
	docs/interface.rst
	snf-image-helper/common.sh.in
	snf-image-helper/tasks/50AssignHostname.in
	snf-image-host/kvm-common.sh

Add a mechanism were scripts from within the image can be executed
instead of the original Configuration Tasks.

The ComputerName in Windows has strong restrictions:
    https://technet.microsoft.com/en-us/library/ff715676.aspx
If the name we set in the unattend.xml is not valid, then sysprep
will fail during the first boot.

This resolves #81

Make them comply with the rest of the variable names

Though this image property a user may define a base64 encoded executable
that will run as configuration task during the image deployment. In
order to support this, a new RunCustomTask configuration task has been
created.

Allow making a whole disk as SWAP. To do this, you need to define the
SWAP image property with a letter, denoting a hard disk numbering. If
you use: SWAP=b then snf-image will configure the second disk of the
image as swap.

This resolves #63

If parted supports the resizepart command, use it to enlarge a
partition in favor of removing and recreating it.

If this option is specified, the resulting helper image will not be
shrank to reduce its size. This is useful when debugging. If the image
is shrank to his minimal size, then altering files inside the image
after mounting is not possible.

Check if the provided file exists and is an snf-image-helper package

 * Add an kernel configuration file that can be used to construct the
   helper image
 * Add instructions under the "Development" section on how to build a
   stripped down kernel for snf-image-helper