GitLab

average cluster.

needs to come from apt_aggregates_radioinfo table instead!

server, or figure out a work around. I made a ticket.

* The mibs live in a different place (/var) so the path stuff in the
  raritan file needed some changes.

* Need packages: snmp snmp-mibs-downloader libsnmp-perl

* Need PDU2-MIB.txt from the Mothership, to /var/lib/snmp/mibs/ietf

to the value of sitevar images/default_listed.

Last time we talked, I told you about a long standing change we needed
wrt delay node handling. That change stopped considering control network
interfaces in the list of possible interface speeds, as well as
interfaces that are not even wired up. This was bad, since well, it
makes no sense. Say we have a cluster with 1G control interfaces, but
all of the experimental interfaces are 10G. The mapper would think there
are 1G links for delay node handling and best effort (we would put the
minimum required speed into the vtop and let assign choose an interface).

The consequence of this at the Moonshot cluster is that a best effort
lan of many (say, 40) nodes would map using any set of nodes scattered
across the chassis' cause we were using 1G in the vtop file. But after I
made the change above, some experiments stopped mapping cause the ptop
was now getting 10G link speeds cause that is now the minimum, but there
is not enough interswitch BW to support a lan that big when it is
scattered across too many switches. Which is the whole reason for best
effort.

So now for a few new changes.

* Make best effort a first class flag, not a combo of things (speed=10,
  nobwshaping=1, uselinkdelay=0), on the lan database table. I've wanted
  to do this for a while.

* Now best effort is handled in the mapper, currently by putting in
  a 1G bandwidth in the vtop, and assign will pick any interface 1G or
  better. This gets us back to where we were before the changed described
  in the first paragraph above. Well except for the pc3000s on the
  Mothership, they have a mix of 100Mb and 1Gb interfaces, but I am going
  to wait and see if it actually causes problems for anyone.

  But to make this really correct, we need to change the CM to pass through
  something other then "10" BW for all best effort links, since what we
  really want is for the user to tell us a true minimum they need, so that
  we can pick the lowest speed physical devices required. But this will
  take some more thinking time. And it affects the problem with interswitch
  bandwidth above.

* Get rid of an inconsistency in linkdelay handling; at the experiment
  level we have use and force flags for linkdelays. But at the lan
  level we have just a use flag, and we were treating that as force. So
  I added a separate force flag to make things consistent, since with
  best effort we want to turn of BW shaping but otherwisw link delay is
  optional unless needed for some other reason (delay, loss).

delayreloadtillalloc options.

the noreport flag.

aggregate (whie would be everywhere except the Mothership).

(This is just to clear the ARP cache; we are not expecting a result
when this script is run, since the vif is not yet up.)

B210 is not MIA when the node boots.

a trailing slash (directory). Mostly this required using absolute paths
for some of the library includes and showing a minimal page that has no
other links. Simplest thing to do.

control:

1) Add a "listed" flag to images and to the image server to allow hiding
   images that users are able to use, but do not need to see in a
   listing of available images. For example, consider all the openstack
   images, which are not usable by themselves, but only when
   instantiating the openstack profile. We have dozens of such images
   that add a lot of noise.

2) Add a local update flag so that changes to metadata (listed, global)
   via the web interface actually get posted to the IMS via the daemon.

3) Various changes to the web UI in support of this stuff.

Work in progress, I need to get these changes out to all the clusters
before I can proceed further.

getting the imageable flag, but with delayed reloading, we have to watch
for the mustreload taint state, and allow that (since that taint state
is going to be cleared before the user gets control).