1. 25 Oct, 2016 1 commit
    • David Johnson's avatar
      Parameterize hadoop wfas; change master flow setup; check master flows. · 73aca117
      David Johnson authored
      First, we add key-val parameters.  broker_name=foo sets the broker name
      to foo for registration and lookup (defaults to 'hadoop').
      runhadoop=False (or other False equivalents) will force the wfas to skip
      Hadoop config and run.
      
      We also separate out master<->slave flow setup and put it at the
      beginning of the allpairs flow mesh setup; this was for debugging.
      
      Finally, we also try and retry a simple parallel ssh task from the
      Hadoop master to all slaves, to "verify" and "wait" for them to all be
      up and reachable.  This helps us catch problems like when a VM can't
      fully boot because it failed to get its metadata, or whatever.
      73aca117
  2. 22 Sep, 2016 1 commit
  3. 31 Aug, 2016 3 commits
  4. 30 Aug, 2016 3 commits
  5. 23 Jun, 2016 1 commit
  6. 16 Jun, 2016 1 commit
  7. 13 Jun, 2016 2 commits
  8. 10 May, 2016 6 commits
  9. 09 May, 2016 4 commits
  10. 08 May, 2016 5 commits
  11. 05 May, 2016 2 commits
    • David Johnson's avatar
    • David Johnson's avatar
      Add a broker-aware allpairs service master and tenant master. · 48420535
      David Johnson authored
      This is the allpairs wfa again, but this time, the user-tenant-allpairs
      wfa looks up the "allpairs" service at the broker, and as it receives
      its own nodes, it send those caps to the allpairs service's RP that it
      got from the broker.
      
      The idea is that you run each of these wfas in a separate tenant.  For
      instance, run the service-tenant-allpairs in the new service-0 tenant:
      
        neutron capnet-wfagent-create --name service-0-wfa0 \
          --tenant-id <SERVICE_0_UUID> \
          --master --wfapp-path=/usr/bin/capnet-wfagent-service-tenant-allpairs
      
      Then, in the new tenant-0 tenant, do
      
        neutron capnet-wfagent-create --name tenant-0-wfa0 \
          --tenant-id <TENANT_0_UUID> \
          --master --wfapp-path=/usr/bin/capnet-wfagent-user-tenant-allpairs
      
      Then add some nodes into tenant-0, and they will be granted to the
      service-0 wfa0, which will add them to the allpairs mesh, i.e.
      
        nova boot --image trusty-server --flavor m1.small \
          --nic net-id=9bab982f-80d7-427f-a34b-0bf7d3dcd5bc t1
      
      where net-id is the id of the Capnet network, and you have changed
      the OS_PROJECT, OS_USERNAME, OS_PASSWORD, OS_TENANT env vars to send
      your resource request from the tenant-0 tenant (I can't see that nova
      boot supports an admin injecting resources on behalf of a tenant, like
      neutron does).
      48420535