466 Commits (d689c13fc89c4c707853d365da4646e60e40df94)

 

All Branches   

Search

Author	SHA1	Message	Date
Michael Prokop	728aef882a	MT#4465 Stop prosody service with mounted /proc	12 years ago
Michael Prokop	1edd42441e	MT#4463 New boot option vagrant to support baseline vagrant configuration ... To reduce code execution in https://jenkins.mgm.sipwise.com/job/daily-build-matrix-runner/	12 years ago
Michael Prokop	d98899f9d7	Change "allow-hotplug" network setting into "auto" to get more consistent behaviour ... I sometimes get a failing network setup in Vagrant's ce-trunk VM where the default route is missing then: | # ip r | 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 | 192.168.88.0/24 dev eth1 proto kernel scope link src 192.168.88.234 | | # cat /etc/network/interfaces | # This file describes the network interfaces available on your system | # and how to activate them. For more information, see interfaces(5). | # The loopback network interface | auto lo | iface lo inet loopback | | # The primary network interface | allow-hotplug eth0 | iface eth0 inet dhcp | #VAGRANT-BEGIN | # The contents below are automatically generated by Vagrant. Do not modify. | auto eth1 | iface eth1 inet dhcp | post-up route del default dev $IFACE | #VAGRANT-END Of course the default route comes back on a manual refresh of eth0: | # ifdown eth0 | # ifup eth0 | # ip r | default via 10.0.2.2 dev eth0 | 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 | 192.168.88.0/24 dev eth1 proto kernel scope link src 192.168.88.234 The culprit seems to be the allow-hotplug where the device is handled different in the startup process: http://screeni.s3.amazonaws.com/screenshot.2013-09-17T11:43:37.png The ordering is important because of Vagrant's "post-up route del default dev $IFACE". While there's a workaround available within Vagrant: 73c8299ecd I don't think that's the proper way. Since we're using "auto" everywhere else in our setups anyway let's make this change, hopefully also fixing the Vagrant network issue.	12 years ago
Michael Prokop	8832daa7ee	Revert MIRROR switch, causing issues with apt-pinning ... ngcp-services-pro depends on linux-headers-3.2.0-4-all, which depends on linux-headers-3.2.0-4-all-amd64, which depends on linux-headers-3.2.0-4-amd64. linux-headers-3.2.0-4-amd64 is installed already in version 3.2.46-1+deb7u1 on our installation, being the current version from security.debian.org. Because this package depends on all the other packages being in version 3.2.46-1+deb7u1 as well this fails due to our apt-pinning. Our apt-pinning considers security.debian.org to be at it default pinning level 500 whereas deb.sipwise.com is pinned to 990. This results in package dependencies that can't be resolved by using packages from security.debian.org. We have to think further regarding the wanted behaviour before we actually make that MIRROR switch. :(	12 years ago
Michael Prokop	8400101b67	Do not fail on missing 680FBA8A.asc key	12 years ago
Michael Prokop	a1b3eb0fd3	Use Sipwise Debian mirror instead of debian.inode.at ... Since we have our very own squeeze + wheezy mirrors we no longer need to rely on debian.inode.at	12 years ago
Michael Prokop	477f76b2f8	Remove deprecated kantan deployment code	12 years ago
Michael Prokop	caf0e8a4c7	Also send 'o' key to actually poweroff the system when requesting to do so ... Thanks for the find, Alexander Lutay	12 years ago
Michael Prokop	449a2e1aa7	We don't have a label on swap space in LVM, adjust accordingly	12 years ago
Michael Prokop	67176c732c	Use label ngcp-swap for the swap partition no matter whether LVM or not ... This should resolve the /dev/sda vs /dev/vda issue with our VMs.	12 years ago
Andrew Pogrebennyk	640cf27bd9	Use installer version 0.11.5 for NGCP 3.0.	12 years ago
Andreas Granig	07ef018433	Add final 3.0 release.	12 years ago
Michael Prokop	1e3d5ad43d	Stop prosody service after installation finished ... Shipped as part of 3.0 release	12 years ago
Andrew Pogrebennyk	120ad3c372	Use new installer 0.11.3 for 3.0-rc2.	12 years ago
Michael Prokop	7db7939d2e	Choose tagged installer versions if no Debian release specific build is available ... Testing the current http://deb.sipwise.com/autobuild/pool/main/n/ngcp-installer/ situation during release time.	12 years ago
Andrew Pogrebennyk	aabd82c259	Use fixed installer v0.11.2 for 3.0-rc2.	12 years ago
Andrew Pogrebennyk	95ec8b6b1f	Use installer version 0.11.1 for 3.0-rc2.	12 years ago
Andrew Pogrebennyk	7c6b9d62ab	Use installer version 0.11.0 for 3.0-rc1.	12 years ago
Michael Prokop	daabddf927	Directly access autobuild directory and skip its debian directory ... On Jenkins host there was this symlink present: | cd /srv/repository | ln -s . debian To avoid unnecessary duplicates during repository search I removed the symlink, let's see whether this change is enough or if apt-get then still needs it.	12 years ago
Michael Prokop	6cdb6f6d05	Remove percona repository from release-* builds' sources.list	12 years ago
Michael Prokop	1ef383d6cc	Kill glusterd daemon ... Debian/wheezy setups provide the glusterd binary	12 years ago
Michael Prokop	53ae51e7f5	Exclude performance_schema database from list of databases for db-schema upload ... The performance_schema is part of mysql-5.5 as noted by Andreas Granig.	12 years ago
Michael Prokop	4786ebd86f	Stop glusterfs-server and monit processes ... Otherwise we've open file handles on /mnt	12 years ago
Michael Prokop	9d5d1169e5	Drop Sipdoc.net repository from sources.list ... TODO: handle percona repos for squeeze vs wheezy	12 years ago
Michael Prokop	28d837e165	Use LVM by default, disable it only for 2.* releases	12 years ago
Jon Bonilla	816e2b549a	Add fake fqdn to prevent Apache warnings ... Also don't duplicate 127.0.0.1 line	12 years ago
Michael Prokop	1be9a70f5b	Use grml-chroot for dkms actions ... dkms in Debian/wheezy fails when directly invoked via chroot(8): | /usr/sbin/dkms: line 1868: /dev/fd/62: No such file or directory | /usr/sbin/dkms: line 1799: /dev/fd/62: No such file or directory and returns with exit code 0. By invoking grml-chroot we get the according mount binds for devfs etc.	12 years ago
Michael Prokop	d5a93de19f	log dkms actions	12 years ago
Michael Prokop	59707fb601	write full puppet.conf to be compatible with puppet from Debian/wheezy	12 years ago
Michael Prokop	72d85cac05	Log puppet output	12 years ago
Michael Prokop	356c3943fc	Rework FQDN handling for puppet deployment ... This should¹ make default puppet deployments more comfortable. ¹ Testing....	12 years ago
Michael Prokop	4f62c5a995	Revert "Use 100% instead of '-1' to address end of disk" ... This reverts commit 4cc1f8e4bc.	12 years ago
Michael Prokop	4cc1f8e4bc	Use 100% instead of '-1' to address end of disk ... Otherwise parted fails with: | Error: Can't have the end before the start! (start sector=2067 length=-1843) on Proxmox with vmdk file format.	12 years ago
Michael Prokop	8245a49299	Drop unused profile support	12 years ago
Michael Prokop	62e84ca134	Disable rsyslog remote logs, graylog doesn't live anymore	12 years ago
Michael Prokop	e9e88494c6	Provide more descriptive error message when exiting during partition setup	12 years ago
Michael Prokop	c59b011d0e	Fail on errors during setup-storage, parted and mkswap ... Current daily VMs are known to fail because of switching from raw image to vmdk on proxmox. :( Abort installation immediately if actions during setup-storage, parted and mkswap fail.	12 years ago
Michael Prokop	3655404727	Adjust script version handling for Git	12 years ago
Michael Prokop	bce521dad0	Provide Makefile to check for syntax error ... Verify the script can be executed via netscript-unit-test before triggering script upload	12 years ago
Michael Prokop	1d2f4b66eb	deployment.sh: no longer run under set -e + report fatal errors via set_deploy_status ... Let's try to catch errors in daily builds immediately instead of waiting for the timeout. From: Michael Prokop <mprokop@sipwise.com>	12 years ago
Michael Prokop	0db5f3ae41	deployment.sh: adjust installer version detection for git + Debian multirelease support ... From: Michael Prokop <mprokop@sipwise.com>	12 years ago
Michael Prokop	13f2d09599	deployment.sh: export $TARGET_HOSTNAME as $HOSTNAME iff available ... The $HOSTNAME contains the dhcp client name during deployment otherwise :( From: Michael Prokop <mprokop@sipwise.com>	12 years ago
Michael Prokop	cfa2a73cbd	deployment.sh: set hostname before writing /etc/hosts ... From: Michael Prokop <mprokop@sipwise.com>	12 years ago
Michael Prokop	f243bc2e3b	deployment.sh: make sure `hostname` and `hostname --fqdn` return data from chroot ... Testing... From: Michael Prokop <mprokop@sipwise.com>	12 years ago
Michael Prokop	796a9c4e2a	deployment.sh: redirect HTTP server output to /tmp/status_server.log ... Otherwise grabbing a screenshot after deployment finished will include to much noise and not the useful data... From: Michael Prokop <mprokop@sipwise.com>	12 years ago
Michael Prokop	684cb80609	deployment.sh: set "$ip $ROLE $HOSTNAME" in /etc/hosts ... Let's try setting "ip fqdn short" to solve bootstrapping MySQL on PRO systems. From: Michael Prokop <mprokop@sipwise.com>	12 years ago
Michael Prokop	40b474a67a	deployment.sh: mention Debian release in deployment logo ... From: Michael Prokop <mprokop@sipwise.com>	12 years ago
Michael Prokop	cb66e7eb82	deployment.sh: assign debian releases to all present installer versions ... Make it obvious which platform releases use which underlying Debian release, once we have wheezy support the default will be changed and we don't want to have wrong assignments for existing releases then. From: Michael Prokop <mprokop@sipwise.com>	12 years ago
Andreas Granig	147ff5145e	Add 2.8 release and deprecate releases older than 2.4	12 years ago
Andrew Pogrebennyk	a210cc9507	deployment.sh: point 2.8-rc3 deployment to installer release 0.10.1	12 years ago