GitLab

For persistent blockstores, is based on the value of the "readonly"
virt_blockstore_attributes attribute if it exists. The RO attribute
is set by libvtop when an attempt is made to use a lease that is in
the 'grace' state.

network to see if we can catch when a node is never going to boot
cause XEN created a broken control vif; tear down the VM and try
again, which seems to solve the problem most of the time.

for elabinelab (multicast, apod).

say to do that instead of bridge mode. Sadly, the xen script that does
this is broken and so here is our version.

the resource mapper. To add a node restriction:

boss> node_exclude pcXXX

To remove the restriction:

boss> node_exclude -r pcXXX

start of a page to create new profiles, lots of other changes
and additions.

add an extra ssh pub key to elabman so that the user can log into
new boss, since when setting up a rack all existing accounts are
deleted. Store this key as ~/.ssh/elabinelab.pub.

https://github.com/vlamanna/BootstrapFormHelpers

This is either because we could not get the lock or because it was in use
and could not be destroyed. A subsequent pass of the daemon should try again.

1. Add set-readonly method to a NS blockstore object.
2. Make sure that dataset blockstores (leases) in the 'grace' state can
   *only* be accessed read-only.

What has not been done yet is to pass the attribute to the storage server
and client so they can actually enact read-only-ness.

Based on suggestions from <ahelsing@bbn.com>.

This gives us a way to always CC a particular address (note that
this is different from archivemail, which makes a separate message)

A closer inspection of the 'fedora' case that I had been using revealed
that a few changes needed to be made for the CentOS 6 environment.  This
is loosely based on the fedora15 case, but stripped down and cleaned up
some.