Page History

...

It is divided into 4 functional areas which we describe futher in sections below:

• APP SDK - The SW development toolkit for App developers . That that allows Appdeveloper to build and package its application in oci, dac compliant AppContainer. This AppContainer is then the App binary that can be shared/exchanged with RDK-M and various RDK operators via an OCI container registry.
• OCI container registry: is a standard Cloud Native component that allowing allows storage and exchange of AppContainers. As described above this is the exchange point for the binary AppContainer between Appdeveloper App developer and consuming parties/operators
• DAC Cloud - Cloud 
  • These are cloud hosted software elements,
  typically run as
  • microservices
  that
  • that 
    • allow
  containerised Apps to be published, put in
  • • you to publish an App with appropriate metadata in an AppCatalog for specific distribution group/environment
    • automatically convert oci-image to so called oci bundles that run on STB
    • and
  securely delivered/downloaded to the STB box
  • • sign/encrypt binaries for securely delivery to STB/CPE models it serves. 
  • Each operator will manage its own AppCatalog and is free on how it chooses to distribute and package that towards its RDK STBs.
  • RDK-M operates
  such
  • a reference DAC cloud instance that serves an AppCatalog with DAC Appcontainers for all the RDK-M Video Accelerators
  that the
  • . It acts as a staging and test environment for App developers and RDK community
  and App developers then can use.  Source
  • , allowing App developers to publish their DAC native apps and test/run them on RDK Video Accelerators.
  •  Source code of µservices that exist in such reference DAC cloud instance are available in open source.
• STB / CPE - This is software components that run on set top box and co-ordinate to manage container installation and runtime life cycles

...

A DAC SDK has been developed to make it easier for AppDevelopers to develop and build oci, dac ompliant compliant containerized applications. The SDK is public, fully open source and uses standard Yocto 3.1 Dunfel Poky cross-compilation / build environment. The DAC SDK can run a developer workstation, does not require any proprietary or SoC specific code to be able to build your application. It is available on https://github.com/rdkcentral/meta-dac-sdk  The SDK allows developers to write Bitbake recipes that compile their code and produce an OCI It does NOT require you as an Appdeveloper to have any SoC or OEM specific SW/SDK for being able to compile and package your AppContainer, it is SOC/OEM agnostic. The SDK allows developers to cross compile their application sources, automatically add appropriate dependent libraries in AppContainer and produce oci, dobby, dac compliant AppContainer image. This OCI binary oci AppContainer image can then be uploaded to an OCI registry for sharing the binary AppContainer with possible consumers/distribution platforms. As Appdeveloper you can then also register and publish its application test and run your AppContainer on all RDK6.1 RDK-M Video Accelerators (when publishing the App to RDK-M DAC Cloud for Video Accelerator where it will be automatically converted to bundles that allow to be downloaded and run on any RDK6.1 Video Accelerator independent of its SoC beneath.VA DAC cloud instance)

The DAC APP SDK is available on https://github.com/rdkcentral/meta-dac-sdk and comes with many example AppContainers

For information on how to really make DAC app and use DAC SDK we refer to Fore more information on DAC SDK we refer to HOWTO to build your native App with DAC SDK and publish to RDK-M DAC cloud

...