Versions Compared

Old Version 4

changes.mady.by.user Dominic Lunanuova

Saved on

compared with

New Version 5

changes.mady.by.user Dominic Lunanuova

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

REFStatusDiscussion
1Open

DNS Update for inter-site routing

We have several examples of an edge component which needs to communicate to a central service. Mike suggested that edge DNS might be updated such that edge clients could resolve to central services. This might satisfy a common need across several components. e.g. access to central AAF comes to mind

2Open

Location discovery

Bus Controller manages dcaeLocations as the name of different sites. What mechanism can be used to: a) register dcaeLocations when each k8s cluster is deployed. b) serve as an attribute when MR and DR clients are provisioned. Current expectation is that there is some k8s info in A&AI API that might be useful.

3Open

Relying on Helm chart enabled flag

2/12:

"Mike,

Last week we discussed using a helm configuration override file to control which components get deployed at edge.

The idea being we would set enabled: false for a component that shouldn’t be deployed.

But dmaap chart actually consists of several sub-charts, each of these sub-charts correspond to a specific dmaap component which we may want to deploy at edge or not.

So, curious if you know the syntax for this – I haven’t been able to find a reference for how enabled is actually used, and I don’t see that value referenced in our charts so not clear what is reading it.

 

Wondering if our edge config override would be something like:

  dmaap:

    dmaap-message-router:

      enabled: true

    dmaap-bus-controller:

      enabled: false

    dmaap-dr-prov:

      enabled: false

    dmaap-dr-node:

      enabled: true

 

or, do charts for our individual components need to be top level  directories under oom/kubernetes in order to use the enabled flag?"

2/13: From Mike Elliot:

"I’ve been trying to allow for the conditional control over the dr-prov and dr-node as well, with no success.

Still investigating options for this. Hope to have a solution on this by EOD."





Development

  1. Helm configuration overrides will be collected in a single file (e.g. dmaap-edge.yaml) and delivered to oom/kubernetes/onap/charts/resource/environments.  Examples of what kinds of overrides will be present in this file include:
    1. Setting the standard enabled indicator to true for dmaap, but false for other components.
      dmaap:
        enabled: true
    2. Setting an edge indicator to drive any edge-specific logic.  TBD if this is really useful - hopefully other overrides in this file are edge specific.
    3. Setting the values for a central service which may be needed at the edge.  Known examples include:
      1. Message Router must be configured to access the central AAF instance.  (DR Node may have this requirement in the near future)
      2. Data Router Node must be configured to access the central DR Prov
      3. Both MR and DR Node must register with central Bus Controller
    4. Setting scaling values appropriate to the edge.  e.g. perhaps a single kafka broker is appropriate at the edge
  2. DMaaP Chart changes
    1. Reorder charts:
      1. Bus Controller must be up and running if other components are going to register with it.  Jira to remove any dependencies on MR.
      2. MR
      3. Mirror Maker
      4. DR Prov
      5. DR Node  (DR Prov must be up for Node to retrieve provisioning info)
    2. Post-install hooks:
      1. Bus controller:
        1. POST <central dmaap-bc>/webapi/dmaap
        2. POST <central dmaap-bc>/webapi/dcaeLocation (for central)
      2. MR:
        1. POST <central dmaap-bc>/webapi/mr_clusters  DMAAP-534  Jira to add kafka brokers to endpoint
      3. DR Node
        1. POST <central dmaap-bc>/webapi/dr_node   DMAAP-534

...