Uploaded image for project: 'Multicloud'
  1. Multicloud
  2. MULTICLOUD-913

Define APIs exposed by Traffic Controller

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • None
    • None

      1. Define API subset for Intercluster communication
      2. Define API subset for intracluster communication
      3. Define APIs for internal microservices to communicate with external services with TLS
      4. Define APIs for RBAC for services under Mesh

      Deliverable - Update the API s exposed by the traffic controller at https://wiki.onap.org/display/DW/L7+Proxy+Service+Mesh+Controller

      Internal Design details
      Guidelines that need to kept in mind
      Support for metrics that can be retrieved by Prometheus
      Support for Jaeger distributed tracing by including opentracing libraries around HTTP calls.
      Support for logging that is understood by fluentd
      Mutual exclusion of database operations (keeping internal modules accessing database records simultaneously and also by replication entities of the scheduler micro-service).
      Resilience - ensure that the information returned by controllers is not lost as the synchronization of resources to remote edge clouds can take hours or even days when the edge is not up and running and possibility of restart of scheduler micro service in the meantime.
      Concurrency - Support multiple operations at a time and even synchronizing resources in various edge clouds in parallel.
      Performance - Avoiding file system operations as much as possible.

            ritusood ritusood
            pramod pramod
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: