1. 23 Jul, 2013 2 commits
  2. 11 Jul, 2013 3 commits
  3. 28 Jun, 2013 3 commits
    • Leigh B Stoller's avatar
      Changes for *remote* XEN shared nodes, as on the I2 pcpg nodes. · 4c091c96
      Leigh B Stoller authored
      Since the pcpg-i2 nodes are so very flaky, lets try something that
      does not require them to rebooted or imaged!
      The key change is that on these remote nodes, we do not bridge the
      physical control interface to the VM control interfaces. There is no
      point since there are no routable IPs we can use, nor is there a
      192.168 network that would be useful.
      However, we still want to give the VMs their 192.168 address and we
      still want multiple VMs on the same host to talk to each other, and we
      we still want the VMs to be able to access the outside world with NAT.
      So we still create the xenbr0 bridge, and give it the router address
      ( Any traffic heading out will be NAT's as normal, and
      you can ssh into the VM using the physical host IP and the per VM
      sshd port number.
    • Leigh B Stoller's avatar
      Don't use -P option to wget; breaks. · cbfa24fb
      Leigh B Stoller authored
    • Leigh B Stoller's avatar
  4. 20 Jun, 2013 1 commit
    • Leigh B Stoller's avatar
      A big set of changes to how we create XEN guest disks. · fbc26aea
      Leigh B Stoller authored
      Prior to this commit, XEN guests disks were single partition, no MBR,
      the bits dumped into the lvm. This makes a snapshot of a XEN node,
      look completely different then a physical disk image, especially if
      users want more disk space (mkextrafs) inside the guest, and then want
      to take a snapshot of that, and then run it on a physical node (which
      was not possible).
      With these changes, guests now use the same MBR layout as our version
      two MBR, which makes them interchangeable with physical disk images.
      In fact, the goal is to be able to switch back and forth as needed,
      based on physical resource availability.
  5. 19 Jun, 2013 2 commits
  6. 12 Jun, 2013 1 commit
  7. 07 Jun, 2013 1 commit
  8. 06 Jun, 2013 4 commits
  9. 04 Jun, 2013 2 commits
  10. 31 May, 2013 7 commits
  11. 29 May, 2013 1 commit
  12. 24 May, 2013 1 commit
    • Mike Hibler's avatar
      Whack! · 1fe8b203
      Mike Hibler authored
      Take care of an iSCSI race condition in Fedora15.
  13. 22 May, 2013 4 commits
  14. 18 May, 2013 1 commit
  15. 15 May, 2013 1 commit
    • Mike Hibler's avatar
      Another round of improvements including ZFS and striping support. · 0099a3a7
      Mike Hibler authored
      Use ZFS rather than gvinum as the LVM on 64-bit FreeBSD. One funkiness:
      if the blockstore has a mountpoint (implying a filesystem), we create a
      ZFS filesystem. If they do not, we create a ZFS zvol (a block device).
      The filesystem has much better performance than the zvol, hence using it
      when we can.
      In gvinum, if all disks are the same size, stripe them rather than
      concanonate them. For us, this would only happen on the d820s if you
      said NONSYSVOL (and you aren't using ZFS).
      Support the unspecified (zero) length blockstore which means "as much
      space as is available".
      Handle mounting of SAN-based storage. We cannot just throw the mount
      into /etc/fstab since the SAN device would not exist when fsck or
      mount is done at boot time. You could probably configure it to work
      on Linux, but I didn't see how on Ubuntu. The iSCSI initiator and
      associated infrastructure on FreeBSD is so primitive that there is
      no way you could do it automatically.
      Add a "fullreset" command to rc.storage for debugging help. It attempts
      to completely teardown the storage no matter what state it is in. The
      regular "reset" command is conservative and quits at the first sign of
  16. 14 May, 2013 6 commits