1. 26 Jun, 2019 1 commit
    • chuck cranor's avatar
      add power support for IBM BladeCenter chassis · f66517f5
      chuck cranor authored
      Add power support for the IBM BladeCenter chassis (power_ibmbc.pm).
      This is the chassis used in the old Roadrunner cluster at LANL.  Each
      chassis has 14 blades in it.  The management IP API is accessed from
      boss via ssh.  A ssh keypair should be setup to allow for passwordless
      ssh access.  We assume the admin has installed the keypair on boss
      (in /usr/testbed/etc/{ibmbc,ibmbc.pub}) and on each chassis for
      the standard "USERID" account.  The key files should be owned by
      an account like "operator" to avoid ssh complaining about key file
      permissions in some cases.
      The module will end up running commands like:
            ssh USERID@chassis-mm power -on -T 'blade[1]'
            ssh USERID@chassis-mm power -off -T 'blade[1]'
            ssh USERID@chassis-mm power -cycle -T 'blade[1]'
      (we'll add "-i /usr/testbed/etc/ibmbc" to "ssh" if the key file is present)
      using this requires the following "mysql tbdb" cmds on boss:
        one-time operation:
           insert into node_types (class,type) values ('power', 'ibmbc');
        per-chassis operations:
           # assumes that "rr1" is blade1 of chassis "bch1"
           insert into nodes (node_id,type,phys_nodeid,role,priority,status,
           values ('bch1', 'ibmbc', 'bch1', 'powerctrl', 10001, 'down',
                              'ISUP', 'NONE', 'FREE_DIRTY');
           # adds IP of the chassis management module
           insert into interfaces (node_id,IP,mask,interface_type,iface,role) values
                ('bch1', '', '','','eth0','other');
        per-blade operation:
           insert into outlets (node_id,power_id,outlet)
                  values ('rr1', 'bch1', 1);   # outlet 1==blade1, etc.
  2. 19 Jun, 2019 2 commits
    • Leigh Stoller's avatar
    • Mike Hibler's avatar
      Further tweaks to jumbo frames code. · 571b4a14
      Mike Hibler authored
      Now use a sitevar, general/allowjumboframes, rather than MAINSITE
      to determine whether we should even attempt any jumbo frames magic.
      Use a per-link/lan setting rather than the hacky per-experiment
      setting to let the user decide if they want to use jumbos. In NS
      world, we already had a link/lan method (set-settings) to specify
      virt_lan_settings which is where it winds up now.
      Client-side fixes to make jumbos work with vnodes.
  3. 13 Jun, 2019 1 commit
  4. 12 Jun, 2019 1 commit
    • Leigh Stoller's avatar
      Small set of changes for os_setup on sdr nodes. · 58f2b014
      Leigh Stoller authored
      SDR nodes (type=sdr, but this applies to other similar types) are in the
      "pc" class, but really they are not pcs, they are more like blackboxes
      that can be power cycled and are always ISUP.
      So, I added a "sdr" package to libossetup, that basically just does a
      power cycle to put them into a known state, and makes sure the
      eventstate is ISUP.
      I added "blackbox" to the sdr type definition. Aside; when something is
      a blackbox, we should bypass all image/osinfo handling, but that's a
      tale for another day.
      I added a isblackbox() check in power, to skip any eventstate
      handling. Aside; node_reboot should possibly skip right to power cycle
      for blackbox nodes, instead of trying to ping it or ssh into it.
  5. 07 Jun, 2019 2 commits
  6. 04 Jun, 2019 1 commit
  7. 03 Jun, 2019 2 commits
  8. 31 May, 2019 1 commit
  9. 21 May, 2019 1 commit
  10. 07 May, 2019 1 commit
  11. 02 May, 2019 1 commit
  12. 30 Apr, 2019 1 commit
  13. 26 Apr, 2019 2 commits
  14. 15 Apr, 2019 2 commits
  15. 09 Apr, 2019 3 commits
  16. 29 Mar, 2019 1 commit
  17. 27 Mar, 2019 1 commit
  18. 25 Mar, 2019 1 commit
  19. 13 Mar, 2019 1 commit
  20. 06 Mar, 2019 5 commits
  21. 04 Mar, 2019 1 commit
  22. 28 Feb, 2019 1 commit
  23. 19 Feb, 2019 1 commit
  24. 15 Feb, 2019 1 commit
    • Leigh Stoller's avatar
      Fix the empty password on the user account we create on the dell · 69c75587
      Leigh Stoller authored
      switches, I must have forgot to deal with it.
      Basically, the FTOS manual says you can give it an MD5 or sha256 hash of
      the password. Well, FTOS must come from another dimension, cause the MD5
      and sha256 it generates, is different then what boss generates, for the
      same input string. So that makes it hard to set up an account with a
      password, unless I send over the cleartext. Which is okay, it stores it
      internally as the hash (I cannot seem to generate). So we send over the
      cleartext per-node root password that is regenerated for each time it is
      allocated to an experiment. Not a big deal, we load the user's ssh keys,
      they should not need to use passwords.
  25. 12 Feb, 2019 1 commit
    • Leigh Stoller's avatar
      Recovery mode: · bde6c94d
      Leigh Stoller authored
      * Add a new Portal context menu option to nodes, to boot into "recovery"
        mode, which will be a Linux MFS (rather then the FreeBSD MFS, which
        99% of user will not know what to do with).
      * Plumb all through to the Geni RPC interface, which invokes node_admin
        with a new option, to use the recovery mfs nodetype attribute.
      * recoverymfs_osid is a distinct osid from adminmfs_osid, we use that in
        the CM to add an Emulab name space attribute to the manifest, that
        tells the Portal that a node supports recovery mode (and thus gets a
        context menu option).
      * Add an inrecovery flag to the sliver status blob, which the Portal
        uses to determine that a node is currently in recovery mode, so that
        we can indicate that in the topology and list tabs.
  26. 07 Feb, 2019 1 commit
  27. 03 Jan, 2019 1 commit
  28. 02 Jan, 2019 1 commit
  29. 14 Dec, 2018 1 commit