Might become useful for low-mem VMs once, implemented while
figuring out installing an etch system for Andi :)
From: Michael Prokop <mprokop@sipwise.com>
Starting with recent trunk versions we no longer ship
kamailio init script but just our kamailio-lb + kamailio-proxy.
From: Michael Prokop <mprokop@sipwise.com>
Inside the pool there might be versions which have been released inside a
maintenance branch but which don't cover recent changes in trunk.
This caused current trunk installations to fail with:
| mv: cannot stat `/etc/ngcp-config/config.yml': No such file or directory
So get rid of every file without "svn" in the filename, so e.g.:
ngcp-installer-ce_0.7.2+0~1339173026.svn9034.165_all.deb (trunk version)
is preferred over:
ngcp-installer-ce_0.7.3_all.deb (release into 2.5 repository)
When we're installing trunk we don't care about released versions,
so get rid of them.
Tricky.
From: Michael Prokop <mprokop@sipwise.com>
This avoids the svn commits with the only change being:
| --- Dump completed on 2012-06-06 6:09:22
| +-- Dump completed on 2012-06-06 16:35:16
From: Michael Prokop <mprokop@sipwise.com>
The:
| ERROR 2002 (HY000): Can't connect to local MySQL server through socket ...
gets displayed several times, though it's not an issue.
Seems to be some async foo or race condition I couldn't identify
yet, until it's resolved display a message to the user so nobody
thinks that's a real error.
From: Michael Prokop <mprokop@sipwise.com>
Hopefully this solves our failing daily builds where we get:
| 06:09:57 curl: (28) Operation timed out after 30000 milliseconds with 0 bytes received
like in https://jenkins.mgm.sipwise.com/job/vmbuilder-ce/192/
From: Michael Prokop <mprokop@sipwise.com>
By default we use eth1 for the crosslink / interconnect device,
but there are VMs which use eth0 - so support this in the deployment
process so we get a happy heartbeat service...
From: Michael Prokop <mprokop@sipwise.com>
Pro looks different, at least for the 2nd node,
we might have to investigate on that, but for the time
being just stay at CE to keep svn logs sane...
From: Michael Prokop <mprokop@sipwise.com>
I don't see any reason why we shouldn't have openssh-server on
each system we install, if manually testing installations of
ngcp-installer on plain Debian systems with the deployment ISO
it's annoying to not be able to login after initial deployment,
so let's change this...
From: Michael Prokop <mprokop@sipwise.com>
Until we've according DHCP/DNS/VM infrastructure that's the easiest
solution...
Thanks for the template, Richard.
From: Michael Prokop <mprokop@sipwise.com>
This is hackish™ and we should figure out a way how to get
rid of this kill-foo in the long run.
Actually the installation still works but if you care about the
error messages or want to debug the resulting system in *live*
mode then it's annoying if you're not aware of what to do...
From: Michael Prokop <mprokop@sipwise.com>
We want to have /etc/fstab being up2date on the live
system after installation, so force processing the
according uevents between kernel and userspace...
From: Michael Prokop <mprokop@sipwise.com>
Booting with Debian installation and bootoption puppet=192.168.51.25
sets up the host for puppet node deployment.
From: Michael Prokop <mprokop@sipwise.com>