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>
It needs quite some hacks to get grub working inside a VM image,
but finally it basically works. \o/
Needs improvement WRT grub-mkimage from host vs. VM (core.img
differing and might cause syntax errors in some specific
situations) and the final integratation within grml-debootstrap,
our automated deployment and vm-builder. -> WIP
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>
Erhard Rank
Michael Prokop