• 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
allpairs.py 2.52 KB