This is the blog where Kris Buytaert points you to extremely interresting and totally irrelevant stuff that happens in Life , The Universe and Everything
Lots of new and interresting stuff on the web these days.
First of all the Centos community has a planet.centos.org now. Were I ran into the brand new feed of Field Commander Wieers Dag was long overdue setting up a blog but he finally made it and he already pointed me to interresting stuff :)
And last but not least I ran into Dev2Ops , upon sending that link to a collegue he asked me if I was behind that site .. I`m not :)
Dev2Ops clearly is tackling the stuff I`m involved with on a daily base. How do you deploy and upgrade software and it's configuration for different similar machines in the field.
The have a couple of nice polls on their site which interrest me: How do you disribute software releases for in-house developed applications? and How do you maintain
system configuration files?. Just go a head and vote . I`m interrested in the results.
My votes were on using pacakges (rpm/deb) using apt or yum and off course Puppet ! ;)
BTW.. It makes me wonder .. who is NOT using Drupal these days :))
bond1: error fetching interface information: Device not found
I had a machine with 4 nics that I wanted to bond 2 by to. I had no problem getting the bond0 device up witn any of the interfaces, however getting a bond1 up always resulted in the above error.
The friendly guys from #centos on freenode pointed me to the missing config.
options bonding mode=4 max_bonds=4
The important part being max_bonds
it seems that the default is 1 so adding one more fails.
So once in a while you get to take over the management of a machine someone installed with no documentation, with lots of playing around and no clue on how it should be reproducible. You're pretty sure that if you reboot the machine it won't come up with the right services, or in this case with the right Virtual machines up and running.
So I got this box with about 7 different xen configs in /etc/xen and none in /etc/xen/auto .. however different lvm volumes were created and 3 virtual machines were running. The different xen configs looked all the same.
web1, web, web.orig, web.working you know :(
So my challenge was to figure out the config of the running virtual machines
Luckily I bumped into some Redhat articles that tought me virsh dumpxml
Now I`m not really a fan of xml based config but it got me quite far.
Eg. on one of my own machines the output looks pretty good.
[root@core named]# xm list
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 619 1 r----- 1242.5
web.hs62.be 1 511 1 -b---- 4648.2
[root@core named]# virsh dumpxml 1
web.hs62.be f7cb62b9d3aa8a07489604285fe3d842 linux /boot/vmlinuz-2.6-xen /boot/initrd-2.6-xen.img /dev/sda1 rw selinux=0 3