Instead of providing the installation details to the screen and
sleep a certain amount let's log the data to
/tmp/installer-settings.txt instead.
While at it also make sure bootoption 'ngcpce' is used so it's
available in the logo screen as well as inside the script.
From: Michael Prokop <mprokop@sipwise.com>
When deploying inside Kantan we want to be able to skip certain
stuff while providing data to the outside host. The bootoption
'kantan' provides that option and since we want to be able to
halt the system after installation also support the 'ngcphalt'
bootoption.
From: Michael Prokop <mprokop@sipwise.com>
Using bootoption "ngcpvers=2.1" should install our platform
version 2.1 and needs to automatically be aware of installing
Debian/lenny.
I'm not entirely happy with hardcoding release vs. platform vs.
installer version, but that's the best we can do for now.
From: Michael Prokop <mprokop@sipwise.com>
We are providing it (and depend on it) on our pro installations
already, but if we're deploying a CE edition on a physical
server system and network doesn't work after deploying it's
just a waste of time. So just install it on all our own systems
by default.
Ack-ed by: Daniel
From: Michael Prokop <mprokop@sipwise.com>
define default values at beginning of file
move setting hostname to default after cmdline/profile scanning
load "ip=<client-ip>:<srv-ip>: ..." in array variable
re-orded and additional commandline output
remove more hardcoded parameters (devs, IPs, hostnames)
full profile for sppro/spce
Otherwise we're creating broken systems which don't work as supposed.
And while at it do not append variables to files but instead override
any existing values, otherwise we might have broken config files.
From: Michael Prokop <mprokop@sipwise.com>
With the current bridge setup for installing pro systems on Proxmox
we have to use ip=....:eth1:off for getting into the internet[tm].
Since the internal network device needs to be eth0 then we've
to check for the specificed ip=... device and use the other[tm] one
for configuration.
From: Michael Prokop <mprokop@sipwise.com>
get profile configuration from file(s) in directory (instead of from one file
only), assume there is a file "default.sh" which is sourced in deployment.sh
+ minimal example profile setting for my SPPRO/CE VMs
SP/CE version can be specified by ngcpvers=N.N in bootparms and commandline,
and as SP_VERSION in profile file
ngcp-installer version as ngcpinstvers=N.N.N in bootparms and commandline,
and as INSTALLER_VERSION in profile file
commandline overrides profile overrides bootparms
* do not hardcode deb.sipwise.com/kantan/
* do not remove profile file, instead store profile file under its profile name
* try to run wget multiple times before giving up
* drop duplicate ngcpprofile code
* send error messages to stderr
From: Michael Prokop <mprokop@sipwise.com>
Swap partition has been prepared already but wasn't
enabled through /etc/fstab.
Thanks to Richard for finding and reporting this issue.
Closes: https://bugtracker.sipwise.com/view.php?id=665
From: Michael Prokop <mprokop@sipwise.com>
This actually isn't necessary but it's nice to be able
to re-execute /tmp/netscript.grml without having to reboot.
So let's make sure rereading the partition table (and therefore
no processes running on /mnt/* are left behind) works.
From: Michael Prokop <mprokop@sipwise.com>
Initial step towards our network (re)design, as stated at
https://sipwise.titanpad.com/install-instructions
While at it add some further useful default settings
and drop getProxmoxBootParam workaround.
From: Michael Prokop <mprokop@sipwise.com>
Oh boy, finding this issue was everything but nice.
* USB pens: nice
* local deployment ISOs: nice
* CD drives (esp. by IBM and Lenovo): fsck you!
From: Michael Prokop <mprokop@sipwise.com>
And while at it adjust way we're calling ngcp-installer so we can
catch its pipe status. Also make sure logfiles are cleaned before
we store them for later usage (ha!).
From: Michael Prokop <mprokop@sipwise.com>
sfdisk fails on some special disk geometries and forcing the
partition schema using --force isn't relevant enough since
we can just use parted as for physical installations as well.
From: Michael Prokop <mprokop@sipwise.com>
This is what has been used as deployment of mgmt1a and mgmt1b in
full automated installation mode through the bootmenu without any
further manual intervention (except for pressing "r" for reboot
and mounting /mnt/glusterfs on rebooted sp1 :)) using
grml-sipwise_2011.05.16.iso:
ngcppro ssh=grml2011 netscript=http://deb.sipwise.com/kantan/deployment.sh ngcpsp1 \
ngcphostname=sp1 ip=192.168.1.101::192.168.1.1:255.255.255.0:sp1:eth0:off dns=195.58.160.194 \
ngcpip1=192.168.1.101 ngcpip2=192.168.1.102 ngcpeaddr=192.168.1.103 ngcpeiface=b0 ngcpmcast=226.94.1.1
ngcppro ssh=grml2011 netscript=http://deb.sipwise.com/kantan/deployment.sh ngcpsp2 \
ngcphostname=sp2 ip=192.168.1.102::192.168.1.1:255.255.255.0:sp2:eth0:off dns=195.58.160.194 \
ngcpip1=192.168.1.101 ngcpip2=192.168.1.102 ngcpeaddr=192.168.1.103 ngcpeiface=b0 ngcpmcast=226.94.1.1
From: Michael Prokop <mprokop@sipwise.com>
The netscript does more than just vmbuilder stuff nowadays,
therefore move it from the vmbuilder package to a separate
package. ngcp-deployment provides everything needed for the
deployment itself, whereas ngcp-vmbuilder takes care of just
building the VMware/Virtualbox images based on the disk image
which might be the result of ngcp-deployment.
While at it provide the netscript as /usr/sbin/ngcp-deployment so
it can be used offline on the deployment ISOs itself as well
(offline usage by using /srv/mirror as mirror being WIP).
From: Michael Prokop <mprokop@sipwise.com>
Michael Prokop
Erhard Rank