This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
haas:system:sokraits_halfadder.offbyone.lan [2014/10/04 13:44] – [xen-tools] wedge | haas:system:sokraits_halfadder.offbyone.lan [2014/10/04 14:41] (current) – [rsync to fileserver] wedge | ||
---|---|---|---|
Line 591: | Line 591: | ||
< | < | ||
- | resource xen_data | + | resource xen_data |
{ | { | ||
device | device | ||
disk /dev/md0; | disk /dev/md0; | ||
meta-disk | meta-disk | ||
- | |||
- | net | ||
- | { | ||
- | cram-hmac-alg sha1; | ||
- | shared-secret " | ||
- | } | ||
on sokraits | on sokraits | ||
- | { | + | { |
address | address | ||
- | } | + | } |
on halfadder | on halfadder | ||
- | { | + | { |
address | address | ||
- | } | + | } |
} | } | ||
</ | </ | ||
Line 1114: | Line 1108: | ||
Wait at least 5 minutes for data reporting to make it into graphable form. | Wait at least 5 minutes for data reporting to make it into graphable form. | ||
+ | |||
+ | =====Sync' | ||
+ | Since we've been successful running the systems out of a RAMdisk, care must be taken to preserve any changes in the event of a reboot or power failure. | ||
+ | |||
+ | ====rsync to disk==== | ||
+ | |||
+ | In this light, I first had the systems rsync' | ||
+ | |||
+ | < | ||
+ | 12 */8 * | ||
+ | </ | ||
+ | |||
+ | ====rsync to fileserver==== | ||
+ | |||
+ | This worked handily until sokraits lost its boot drive (again! In 2 months time!) so I decided to investigate netbooting using an NFSroot. | ||
+ | |||
+ | In the process, I may have finally made a breakthrough in my longtime desire to put the entire system IN the initial ramdisk (so it would be running in RAM from the get-go). Turns out, according to the manual page, you merely have to put the system IN the initrd file... obviously one needs adequate memory (2x at boot- enough for the initrd, and enough to decompress it). | ||
+ | |||
+ | My cron job changed as follows: | ||
+ | |||
+ | < | ||
+ | 24 */8 * | ||
+ | </ | ||
+ | |||
+ | I plan to rig up either some daily autogeneration of the initrd, or have a script on standby that can use to make it. This will then become the method of booting both sokraits and halfadder (and potentially freeing up a still-working SSD in the process! Which I can use in data2). | ||
+ | |||
+ | On the fileserver, I then obtain the latest copy of the hypervisor, kernel, and generate a new all-system initrd: | ||
+ | |||
+ | <cli> | ||
+ | data1:/ | ||
+ | data1:/ | ||
+ | data1:/ | ||
+ | data1:/ | ||
+ | data1:/ | ||
+ | </ | ||
+ | |||
+ | ====pxeboot file for sokraits/ | ||
+ | On the fileserver, in **/ | ||
+ | |||
+ | The file(s) contain: | ||
+ | |||
+ | < | ||
+ | default netboot | ||
+ | prompt 1 | ||
+ | timeout 2 | ||
+ | |||
+ | label netboot | ||
+ | kernel mboot.c32 | ||
+ | append netboot/ | ||
+ | |||
+ | label memtest | ||
+ | kernel distros/ | ||
+ | </ | ||
=====References===== | =====References===== | ||
Line 1157: | Line 1204: | ||
====/tmp as noexec==== | ====/tmp as noexec==== | ||
* http:// | * http:// | ||
+ | |||
+ | ====netboot system to nfsroot==== | ||
+ | * http:// | ||
+ | * this led me to the initrd man page which indicated we might be able to stick the entire system in the initrd and PXE boot that. So many things become simpler at that point. |