Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. Architecture Changes since Amsterdam

    1. as As part of the SDC project, we are continuing our work to enhance our modelling capabilities.
    2. SDC is creating a generic framework to allow us to onboard new plugins which enhance our modelling capabilities. 
    3. This framework will be used as the basis for integrating the following plugins:
      we are adding the
      1. DCAE-D designer
      that
      1. which is responsible for creating the monitoring templates used by DCAE
      we are continuing the integration process with the workflow
      1. .
      2. Workflow designer which is responsible for creating BPMN workflows used in SO.
    4. both Both components will be part of the SDC ECO system SDC ecosystem as a separate at plugins that plugins which are integrated with us.
    5. SDC is creating a generic framework to allow us to onboard new plugins which enhance our Modelling capabilities. 
  2. S3P Updates

    1. SDC as a Design-time application will fulfil the needed carrier-grade requirements.
    2. as part of our support of OOM of deployment using OOM in Beijing, we Support OOM based deployment in Beijing.
      We are rearranging the SDC deployment to allow a better deployment flow and a more K8-friendly way to check our docker status.
  3. DM Alignment

    1. according According to the agreement for R2, SDC is going to change the current Normative current normative types add added to support the VOLTE VoLTE use cases case in R1 with an updated version,
      according to the agreement with the modelling sub committe and there modelling subcommittee and their work on the new Data data model.
  4. API Updates

    1. SDC supports swagger supports Swagger by generating a new swagger Swagger file based on annotations in the code code.
      the swagger is accessible using this instruction External API SWAGGER