Uploaded image for project: 'Apache Knox'
  1. Apache Knox
  2. KNOX-2190

Cloudera Manager integration - advance service discovery handling on topology level

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.4.0
    • 1.4.0
    • Server
    • None

    Description

      With KNOX-2186, Knox is capable of processing a properties file (auto-discovery-advanced-configuration.properties) which CM generates with a list of boolean flags of enabled services. These boolean flags are valid to all descriptors (topologies) within all topologies listed in gateway.auto.discovery.expected.topology.names.
      It'd be beneficial to refine this behavior the following way:

      • the monitor would handle different properties files with auto-discovery-advanced-configuration file name prefix (it's also recommended that whoever generates these files the file name suffix would be the topology name. For instance: auto-discovery-advanced-configuration-topology1.properties).
      • a new property should be introduced in each property file: gateway.auto.discovery.topology.name to indicate the topology name (to not to rely on the file name suffix)
      • keep the existing list of boolean flags of service enablement
      • the existing gateway.auto.discovery.expected.topology.names property should be removed (it's no longer useful)

      The monitor then builds a map of properties where the key is the topology name and the value is a list of boolean flags (if service X is enabled or not) and notifies all AdvancedServiceDiscoveryConfigChangeListener instances when a change is detected.

      Attachments

        Issue Links

          Activity

            People

              smolnar Sandor Molnar
              smolnar Sandor Molnar
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 40m
                  40m