GitLab

  "Experiment names get embedded as a DNS name (as we all know)
   and labels which end with a hyphen are illegal."

for Nick! The output format needed some, uh, tweaks.

was driving me nuts that we do not have an easy way to see what is
going on *inside* the fabric.

So this one reports on traffic across trunk links and interconnects
out of the fabric.  Basic operation is pretty simple:

	Usage: switch_traffic [-rs] [-i seconds] [switch[:switch] ...]
	Reports traffic across trunk links and interconnects
	-h          This message
	-i seconds  Show stats over a <seconds>-period interval

So with no arguments will give portstats style output of all trunk
links and interconnects in the database. Trunk links are aggregate
numbers of all of the trunk wires that connect two switches.

The -i option gives traffic over an interval, which is much more
useful than the raw packet numbers, since on most of our switches
those numbers have probably rolled over a few times.

You can optionally specify specific switches and interconnects on the
command line. For example:

boss> wap switch_traffic -i 10 cisco3 ion
Trunk                    InOctets      InUpkts   InNUpkts   ...
----------------------------------------------------------- ...
cisco3:cisco10                128            0          1   ...
cisco3:cisco8                2681            7          4   ...
cisco3:cisco1                4493           25          7   ...
cisco3:cisco9                 192            0          1   ...
cisco3:cisco4                 128            0          2   ...
pg-atla:ion                     0            0          0   ...
pg-hous:ion                     0            0          0   ...
pg-losa:ion                     0            0          0   ...
pg-salt:ion                  2952            0         42   ...
pg-wash:ion                     0            0          0   ...

NOTE that the above output is abbreviated so it does not wrap in the
git log, but you get the idea.

Or you can specify a specific trunk link:

	boss> wap switch_traffic -i 10 cisco3:cisco8

Okay this is all pretty basic and eventually it would be nice to take
these numbers and feed them into mrtg or rrdtool so we can view pretty
graphs, but this as far as I can take it for now.

Maybe in the short term it would be enough to record the numbers every
5 minutes or so and put the results into a file.

Since SIGCHLD could be delayed due to blocking in progmode(), need to
be ready for those when they finally do happen (i.e., after the pid in
question may have been cleaned up or the global progpid var reset).

Also tweak the "did it fail immediately" timeout to be a bit longer.
Empirically, it now handles unresponsive IPMI SOL sessions better.

updated cert for a slice and we need to replace it in our
database. We were already doing this in the CM code, but we
missed a spot in the CMV2 code.

these do the obvious. Takes a list of lanids (not vlanids). So yesterday
when I did the switchover from the 1Gb to the 10Gb link I did this:

  snmpit_test -i procurveA -i procurve1 --clearvlanontrunks 1225665 1270247 ...

which removed the vlans from the trunk ports on procurve1 and procurveA.
Then I changed the wires table, and then I did:

  snmpit_test -i procurveA -i procurve1 --setvlanontrunks 1225665 1270247 ...

which added the vlans to the new trunk ports. Nifty.

VM. Note that the target script uses sudo, but not in all the places
it needs to, so lets just run the script as root, and yank the sudo
out later.

Since GUIDs are 16 bytes and our current interface MACs are only 12 bytes,
I agonized over whether to grow the mac column to 16 bytes and just treat
it as a unique identifier (which is all we use that column for anyway).
However, in the end I just added a new guid column as there were mac columns
in a variety of other tables and it wasn't clear what the relationship was
and what I might break.

So, the newnode MFS will now report back a GUID for interfaces it recognizes
as IB (FreeBSD-specific right now). The boss-side checkin code with stash
that value in new_interfaces (and later interfaces when added). For possible
backward compat, it will also generate a MAC address from that (possibly
Mellanox-specific) so that all entries in the interfaces table will have
a MAC (yes, it should really be the other way around--all interfaces should
always have a guid).

End of story. We don't do anything else with IB right now other than stash
an interface GUID.

hosts, since we are not using a prerouting rule like we do for XEN
containers. Note that I am using the dom0 ules rules on openvz
physical hosts, but might have to split it out if I get any more
special cases like this.

Needed when boss is the tip server (i.e., for IPMI consoles).

Somehow this vaguely feels like a potential flaw. Prior to this,
a misconfigured sshtb command that specified boss would fail.
Now it will succeed and run in the one place it can cause the
most damage.

Also, fix a couple of nits in the console code.

I changed the initscripts to use -e instead of -E since it seemed to
be common between both pkg_info and "pkg info". But alas, that was not
the case.

each container serially with vnodesetup, just do "xl shutdown -a -w"
cause it way faster. We catch that peoperly and save the state of
the VM when it exists this way.

1450. Note that inside a container, we get back regular interface
lines cause all the container sees is a plain interface, but we have
to reduce the MTU.

of gre so we can tell on the client to reduce the MTU. MTU is a pain.