GitLab

Mostly ptopgen/libvtop changes to get things through assign.

Added a new virt_blockstore_attribute, 'prereserve' that can be applied to
a RW clone to pre-allocate the full amount of space allocated to the volume
being cloned. This is instead of the default "sparse" clone which could run
out of space at an inopportune time if the containing pool runs out of space.
But it doesn't work yet.

Everything is there in the front end to do the necessary capacity checks and
allocations of space, but then I discovered that ZFS doesn't readily support
a non-sparse clone! You can do this, I think, by tweaking the "refreserved"
attribute of the volume after it is created but that would have to be done
behind the back of FreeNAS and I would have to do some more testing before I
am willing to go here.

So for now, all clones are sparse and no one is charged for their usage.

Also, use new API call to create zvols.

support tables) so that we can do a better job of sending email on
errors.

morning.

crappy program that goes into loops quite readily.

fail (and generate a ton of email).

data and not sent us an image deletion, or we missed it somehow. And
when a new image with the same urn (different uuid) came in, our bug
messed up on deleting the old one. That is fixed and iminds is turned
back on.

Closes #161.

violation of what the reservation system says is allowed.

alternate for the portal.

Appeasing the Gods of 80 Columns...

The name always overran its field so all of the columns were out of alignment
and the lines too long and it was just a mess. So by default just print out
the basic stuff. Use '-l' to get the old, complete output.

we do not actually have it when we create the table row.

1. Fix max days, supposed to be 1000 but was getting set back to 365 in
   one missed place.

2. Add -P option; use the existing passphrase from the DB instead of a
   new one. This makes it easy to update someones encrypted certificate,
   reusing their key (-r) and their password.

Note to self; we do not give Portal users a UI for updating their
encrypted certificates, and we do not do it for them when they
expire. That will need to change real soon (like, by tomorrow morning
when the next user gets an expired certificate error).

slight delay filling in that table value, since we ask the backend
cluster(s) and fill in the value when it comes back.

max possible extension permitted. For a multisite experiment, return the
smaller of the dates.

while the monitor is running.

Using "set-rwclone" ala:

    set $bsobj [$ns blockstore]
    $bsobj set-lease "emulab-ops/bar"
    $bsobj set-node $node
    $bsobj set-rwclone 1
    ...

in your NS file will create a clone of the indicated persistent blockstore.

Somewhat limited in utility since you can only have one clone of a
particular blockstore per experiment.

Sets PERMS to one of RO, RW, or CLONE. Note that currently CLONE is only
seen by a blockstore VM. The node attached to the blockstore still sees RW
(to avoid backward compat problems).

release the physical node before the virtnodes on it. This has not been
a problem before cause physical nodes are not an actual sliver, it is
allocated internally by libvtop.

need to pass IsFeasible() a different variable.

Estimates the maximum possible extension for a slice.

change as I get further into it.

Fix for shifting labels on finalize step

Fix for issue #155 . The problem was in the ClearFormErrors function. Instead of hiding only the labels with '.control-error', all '.control-label's were instead being hidden

See merge request !15

A handful of code paths now use the new option to handle infrastructure
tasks where doing the right thing is more important than preserving
guarantees about future reservations (e.g., shuffling around holding
experiments, moving to hwdown, etc.).