GitLab

Removed now unused variables from both as well.

Imageinfo hides the nastiness of what we need to do to get size or mtime
info about shared images for which the caller does not have direct access.
In these cases we need to make a proxied frisbee master server query and
parse its output.

This allows us to more easily disable a subboss in the event of a temporary
subboss outage (e.g., hardware failure). Previously we would have to remove
the related rows from the DB and restore them later.

Previously ISUP and TBFAILED were the two states that signified that a
node had rebooted to the satisfaction of libreboot (with waitmode==1).
Add RELOAD/RELOADING to that list since the frisbee MFS never sends either
of ISUP or TBFAILED.

Required a modification to TBNodeStateWait() to allow waiting for an
op-mode/state combo as well as just a state.

I made this change in anticipation that it would be useful for more
responsive monitoring of failure in tbswap/os_load. But now I am no so sure.

FreeNAS is basically a web frontend to BSD-backed ZFS volumes,
filesystems, and various ways to share them (i.e., iSCSI, NFS, etc).
It stores all its config info in a sqlite DB from which it configs
the BSD system.  It uses Django (a slightly weird MVC that exports a web
interface; logic/models/views are all in python, and there is an
HTML-based template interface.

What I did was basically to wrap the model/form parts of FreeNAS's
code -- so for the commands we want to support, we actually mock up
an HTTP request, and submit it directly to the correct handler function
that the FreeNAS Django config files specify.  This allows us to leverage
all the FreeNAS error checking code and automation (i.e., deleting an
interface would delete aliases on that interface too).

usage() prints this, at present:

Supply a command set class, an operation, and the necessary arguments.

  interface       Configure network interfaces
    add  <interface> <name> [<dhcp=X> <ipv6auto=X> <options=X> ] ...
    del  <interface>
    edit <interface> [<dhcp=X> <ipv6auto=X> <name=X> <options=X> ] ...
  ist             Configure ISCSI targets (a target binds SCSI attributes
         (i.e. serial number, r/w flags, queue depth, block size) to iSCSI
         attributes (i.e., a target portal, authorized initiator network ACLs,
         iSCSI authentication info)
    add  <name> <serial> <portalgroup> <initiatorgroup> [<authtype>
         <authgroup> ] [<alias=X> <flags=X> <logical_blocksize=X>
         <queue_depth=X> <type=X> ]
    del  <name>
    edit <name> [<serial> <portalgroup> <initiatorgroup> <authtype>
         <authgroup> ]
  ist_assoc       Associate extents with targets (final "link" between storage
         and network)
    add <target> <extent>
    del <target> <extent>
  ist_authcred    Configure ISCSI target authentication credentials (i.e.,
         users)
    add  <tag> <user> <secret1> [<peeruser> <peersecret1> ]
    del  <user>
    edit <tag> <user> <secret1> [<peeruser> <peersecret1> ]
  ist_authinit    Configure ISCSI initiator authorizations by hostname or
         network
    add  <tag> <initiators> [<auth_network> <comment> ]
    del  <tag>
    edit <tag> <initiators> [<auth_network> <comment> ]
  ist_config      Configure general ISCSI parameters
    edit [<basename=X> <defaultt2r=X> <defaultt2w=X> <discoveryauthgroup=X>
         <discoveryauthmethod=X> <firstburst=X> <iotimeout=X> <maxburst=X>
         <maxconnect=X> <maxoutstandingr2t=X> <maxrecdata=X> <maxsesh=X>
         <nopinint=X> <r2t=X> ]
  ist_extent      Configure ISCSI target extents (block devs or files exported
         via ISCSI)
    add      <name> <dev> [<comment> ]
    addfile  <name> <path> <filesize> [<comment> ]
    del      <name>
    edit     <name> <dev> [<comment> ]
    editfile <name> <path> [<comment> ] [<filesize=X> ]
  ist_portal      Configure ISCSI target portals (i.e., ip:port binding to
         associate with a target)
    add  <tag> [<comment=X> ] ...
    del  <tag>
    edit <tag> [<comment=X> ] ...
  network         Configure generic network settings
    config [<domain=X> <hostname=X> <ipv4gateway=X> <ipv6gateway=X>
         <nameserver1=X> <nameserver2=X> <nameserver3=X> ]
  pool            Configure ZFS storage pools
    add <volume_name> <volume_fstype> <group_type>  ...
    del <vol_name>
    mod <volume_add> <volume_fstype> <group_type>  ...
  route           Configure static routes
    add <destination> <gateway> [<description> ]
    del <destination> [<gateway> ]
  snapshot        Create, clone, rollback ZFS snapshots of volumes or clones
    add      <snap_name>
    clone    <cs_snapshot> <cs_name>
    del      <snap_name>
    rollback <snap_name>
  vlan            Configure vlan interfaces
    add <pint> <vint> <tag> [<description> ]
    del <vint>
  volume          Configure ZFS volumes (zvols) atop pools
    add <pool_name> <zvol_name> <zvol_size> <zvol_compression>
    del <pool_name> <vol_name>

and provide a web interface to look at them.

For InstaGeni, need to record and be able to search for history by
control net mac address. We now record this in the node_history table,
with corresponding change to the ShowNodeHistory web page.

The backend changes required are that we 1) actually generate a mac
address for VMs and stick it into the interfaces record, 2) return
that mac from tmcd in the jailconfig, and 3) have the openvz library
create the control net interface using that mac.

On the openvz image, needed to switch to using a control network
bridge for all interfaces (not just routable ones) so that traffic
leaves the node with the correct mac.

not 000000000000.

address that is assigned. For ProtoGeni.

* Get rid of all use of component_hops; this was our original syntax
  before the stitching path stuff was nailed down.

* Allow a vlan tag to be requested in the link statement:

    <link client_id="link0" vlantag="765">
      <interface_ref client_id="geni1:if0" />
  
* Support vlan tag requests in the stiching path part:

    <vlanRangeAvailability>765</vlanRangeAvailability>
    <suggestedVLANRange>765</suggestedVLANRange>

  This is the only support at the moment; none of the range stuff is
  done. Further, if you really want things to work, make sure all the
  hops have the same vlan tag cause we don't do vlan translation
  internally or at our edge points.

* Utah only change in the mapper; when trying to use a shared vlan
  whose tag is great then 1000, demand the "highvlan" feature on the
  nodes in the lan. Only some of our switches to high numbered vlans.

that are in the reserved_vlantags table, but are not referenced
by an actual lan object in the lans table.