Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

JIRA Associated

CBS HTTPS support DCAEGEN2-1515 - Getting issue details... STATUS

  1. CBS expose both secure/insecure + AAF cert DCAEGEN2-1549 - Getting issue details... STATUS
  2. Deployment update DCAEGEN2-1550 - Getting issue details... STATUS
  3. SDK impact (java - DCAEGEN2-1552 - Getting issue details... STATUS / python - DCAEGEN2-1551 - Getting issue details... STATUS )

Problem Statement :

CBS Api’s are used by all Service components to retrieve the configuration from consul during startup (and for periodic polling after). To support ONAP S3P security needs, Configbinding Service apis should be switched to HTTPS. As this has impact across all DCAE services, this has to be introduced in phased manner. El-Alto focus will on getting CBS HTTPS deployed and corresponding libraries updated.

Assumptions

  • Not all service will switch to TLS interface for El-Alto
  • CBS deployments must support both HTTPS and HTTP in-parallel
  • SDK library (python and java) have separate api/version to let application choose migration
  • *Can* deploy two instances in the same pod (CBS http and CBS HTTPS) under the same K8S service

Migration Plan

Following are impacts to components to be done in specified order


CBS Enhancement  (DCAEGEN2-1549)

  1. Support HTTPS enablement via environment variable
    • USE_HTTPS: set to “1” to use HTTPS, anything else is HTTP
    • HTTPS_KEY_PATH: path to the TLS private key
    • HTTPS_CERT_PATH: path to the TLS certificate
  2. Use port 10443 if USE_HTTPS is set to “1”, otherwise  port 10000


Deployment Enhancement (Helm chart updates) DCAEGEN2-1550

  1. Modify existing dcae-config-binding-service charts to support the new environment and new CBS container version.
    1. Modify values.yaml service property to include two services: secure and insecure. Each service has the following properties:
      1. enabled - boolean flag to allow enabling and disabling the service.  Allows running HTTP only, HTTPS only, or both.  The default setting for El Alto is that both are enabled.
      2. internalPort - the container port (10000 for HTTP, 10443 for https)
      3. externalPort - the port used by other components inside the cluster to reach the service (10000 for HTTP, 10443 for https)
      4. nodePort – the last two digits of the node port number (15 for HTTP, 14 for HTTPS)
    2. Modify  deployment.yaml to deploy:
      1. if the secure service enable flag is set to true:
        1. the tls-init initContainer that sets stores certs in a volume in the pod
        2. a container with an instance of the config-binding-service image, with the USE_HTTPS, HTTPS_KEY_PATH, and HTTPS_CERT_PATH  environment variables set to enable TLS
        3. a container with an instance of the filebeat logging forwarder, configured to read logs generated by the TLS-enabled instance of the config-binding-service
      2. if the insecure service enable flag is set to true:
        1. a container with an instance of the config binding service image, with the USE_HTTPS environment variable set to 0, to enable non-TLS (HTTP) operation
        2. a container with an instance of the filebeat logging forwarder, configured to read logs generated by the non-TLS instance of the config-binding-service (this prevents problems that would be caused if both containers tried to write into the same logging volume)
    3. Modify service.yaml to deploy a Service named config-binding-service with port definitions based on the service property in the values.yaml.   The default service configuration will create a NodePort service with two ports, one for HTTP (inside the cluster on port 10000, outside the cluster on port 30415) and one for HTTPS (inside the cluster on port 10443, outside the cluster on port 30414).

K8s plugin updates (DCAEGEN2-1550)

  1. Cloudify deployments of service components should include following environments
    • CONFIG_BINDING_SERVICE=<cbs_k8s_service_name>
    • CONFIG_BINDING_SERVICE_CLIENTCERT=<path>
  2. Enable AAF cert distribution by default on path identified by CONFIG_BINDING_SERVICE_CLIENTCERT.
    1. This step to be done regardless of tls_info setting in blueprint (tls_info to be used for components supporting HTTPS as server; in this case certificate are required to be mounted also application specific path specified – this can be created as softlink to path specified by CONFIG_BINDING_SERVICE_CLIENTCERT).

Bootstrap pod (DCAEGEN2-1550)

  1. Add new k8s plugin version including R4 version (1.4.13) in CM deployments
  2. To keep existing components from breaking, continue to register “config-binding-service” and “config_binding_service” as services in Consul, with port 10000 as the service port.

Note: Service registration on Consul will not be done for CBS TLS service.  As components change to use TLS, they should just use the Kubernetes DNS name for the service along with port 10443.

Library Enhancement (CBS java sdk - DCAEGEN2-1552, CBS python util - DCAEGEN2-1551)

(Below to be confirmed based on K8s Plugin updates)

  1. Verify if the new environment setting for TLS (below) added by K8s plugin is visible within POD.
    • CONFIG_BINDING_SERVICE_TLS=<https_cbs_service_name>
    • CONFIG_BINDING_SERVICE_CLIENTCERT=<path>
  2. If defined, use the secure end-point to interface with CBS (port 10443)
  3. If TLS envs are undefined, use R4 service name and port (10000) to interface with CBS

Note: Libraries should stop using Consul service discovery to find CBS.

ServiceComponents (Optional for E release)

  1. Switch to newer version of libraries (CBS SDK for java and python CBS utils)
  2. Update blueprint to use newer version of k8s plugin in blueprints


  • No labels