1. 10 May, 2016 2 commits
  2. 09 May, 2016 1 commit
  3. 08 May, 2016 1 commit
    • David Johnson's avatar
      A simple port of Unni's Hadoop expect scripts to sh. · 25f12d8c
      David Johnson authored
      Also some Hadoop utility scripts, and wrappers to run jobs we care about
      for testing or whatever.
      These don't have the password login Unni had done in expect.  Right now
      we don't need that.  If we need that, we can add it as the "frontend"
      script and then use these for the rest.
      The other part of these scripts is the part that bakes the hadoop image,
      in ../setup-capnet-basic.sh .
  4. 07 May, 2016 2 commits
  5. 06 May, 2016 1 commit
  6. 05 May, 2016 4 commits
    • David Johnson's avatar
      Add a Capnet dhcp Dnsmasq wrapper to stop DNS recursive resolution. · fc2350ec
      David Johnson authored
      Capnet networks cannot get to the external world.  However, the default
      Cloudlab/OpenStack dnsmasq arrangment (of course) specifies an external
      resolver.  This slows all kinds of queries from the VMs, and slows bootup,
      while the local resolver waits for the remote one to timeout.
      Dnsmasq in openstack doesn't give up per-network config ability, so we
      add some of our own.  There is now a custom capnet dnsmasq config file
      sans external resolver; and the wrapper class strips out any --server
      CLI options that the base class might have added due to the dhcp/dnsmasq
      config file opts.  It warns when it does this.
      We may not want that behavior in the future; hopefully we remember to
      get rid of it then.  But there's no other way to allow recursive public
      resolution for non-capnet networks, and then disallow it for Capnet
      networks, without this.
    • David Johnson's avatar
    • David Johnson's avatar
    • David Johnson's avatar
      Autocreate Capnet networks, and user/service tenant projects. · 62951cfb
      David Johnson authored
      This script, setup-capnet-basic.sh, can be run as many times as you
      want... it checks to see if everything it creates already exists.
      We create 4 user/service project/user tandems by default.
      The idea is that each "user" project is where the project user allocates
      nodes, and its master wfa looks up another service wfa at the broker,
      and gives node caps to the service wfa.
      The projects and users are generically named for now... we still don't
      run any wfas by default.
  7. 03 May, 2016 1 commit
    • David Johnson's avatar
      Setup the OpenStack metadata service flows, depending on OS config. · 11d036b4
      David Johnson authored
      Users can configuration the metadata service to either hook into the
      dhcp server port, or into the router port.  In the Cloudlab openstack
      profile, I guess I set it up to run the metadata proxy through the
      router port.  So we just stick with that.
      This means that capnet/openstack in cloudlab users will have to always
      add a router to their capnet networks.
  8. 01 May, 2016 1 commit
  9. 30 Apr, 2016 2 commits
    • David Johnson's avatar
    • David Johnson's avatar
      Bring Cloudlab Capnet scripts up to speed; working; faster. · 7e96fcaf
      David Johnson authored
      Lots of little fixes... one important one is to make the Capnet physical
      LAN name 'capnetlan-N'... this means our OVS bridge (i.e.,
      br-capnetlan-1) has a name < 16 chars, which I believe is the Linux
      interface ID limit.
      Hopefully this is a pretty complete configuration; debug/verbose modes
      enabled by default for all our Neutron stuff (except the minor Nova
      plugin... that's not going to be any trouble).  We don't autocreate any
      tenant Capnet networks thus far, although we could now that we have the
      allpairs workflow app.  Next version.
      Since the compile times are so long (have to build protobuf main lib
      cause the Ubuntu version is too old for proto-c), we trot out pssh for
      some of this.
  10. 29 Apr, 2016 1 commit