Uploaded image for project: 'Cloudify'
  1. CFY-6876

Isolation of RabbitMQ resources on a per-tenant basis

    Details

    • Type: Epic
    • Status: Closed
    • Priority: Unprioritized
    • Resolution: Fixed
    • Fix Version/s: 4.1
    • Labels:
    • Epic Name:
      RabbitMQ isolation
    • Sprint:
      Cloudify 4.2 Sprint 1

      Description

      To enhance multi tenancy isolation and boundaries, Cloudify should ensure agents belonging to deployments of tenant A are not be able to trigger any workflow or operation on deployments of tenant B.
      RabbitMQ isolation is required at tenant-level to ensure this is the case.
      Acceptance Criteria:
      1. Agent from tenant A cannot add anything to the queue that would affect any agent from tenant B
      2. Upgrade from 4.0 / 4.0.1 to 4.1 should be supported
      3. On the new architecture, it should be possible to add/remove tenants and the chosen solution should support it
      4. Agent-less deployments should be supported
      5. HA mode should be supported and tested
      6. Upgrade from 4.1 to later versions should be supported
      7. No API changes

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                pavel Pavel Brodsky
                Reporter:
                pavel Pavel Brodsky
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 3 weeks
                  3w
                  Remaining:
                  0m
                  Logged:
                  Time Not Required
                  Not Specified