Uploaded image for project: 'Policy Framework'
  1. Policy Framework
  2. POLICY-43 Amsterdam Use Case Template
  3. POLICY-103

Implement dynamic A&AI Functionality

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Lowest Lowest
    • Amsterdam Release
    • None
    • None
    • None
    • Policy Sprint 3 - 8/7-8/21, Policy Sprint 4 - 8/21-9/4, Policy Sprint 5 - 9/6-9/20, Policy Sprint 6 - 9/21-9/28, Policy Sprint RC0 - 9/29-10/11

      The template needs to be able to determine when a lookup to A&AI is required. Or, when a pattern-match-replacement is required. In the 1.0.0 template, this was all hardcoded in the API call. But this is not feasible going forward as we cannot anticipate what VM/VNF an operations policy writer wishes to take an action upon.

      Initially, the user stories for vFirewall and vDNS are simple yet different. And the VOLTE and vCPE uses can be covered by any functionality we create for vFirewall and vDNS.

            jc2555 jc2555
            pdragosh pdragosh
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: