Systems and methods providing a processing device to receive, by a software build process executing in a trusted execution environment (TEE) of a first computer system, software source code from a second computer system. The processing device generates a software package by compiling the software source code. The processing device also generates a first signature of the software package and sends the first signature to the second computer system. Responsive to receiving, from the second computer system, a second signature comprising the first signature signed by the second computer system, the processing device further deploys the software package on the first computer system.

A system, comprising a memory and a processor, where the processor is in communication with the memory, is configured to receive a request to determine a compatibility of a first version of an application programming interface (API) with a second version of the API. Next, a model of the first version of the API and a model of the second version of the API is retrieved. Each of the models is parsed to determine a first set of functionality of the first version of the API and a second set of functionality of the second version of the API. The first set of functionality is mapped to the second set of functionality to determine differences between the first set of functionality and the second set of functionality. The compatibility of the first version of the API with the second version of the API is determined based on the differences.

Embodiments described herein are generally directed to an edge-CaaS (eCaaS) framework for providing life-cycle management of containerized applications on the edge. According to an example, declarative intents are received indicative of a use case for which a cluster of a container orchestration platform is to be deployed within an edge site that is to be created based on infrastructure associated with a private network. A deployment template is created by performing intent translation on the declarative intents and based on a set of constraints. The deployment template identifies the container orchestration platform selected by the intent translation. The deployment template is then executed to deploy and configure the edge site, including provisioning and configuring the infrastructure, installing the container orchestration platform on the infrastructure, configuring the cluster within the container orchestration platform, and deploying a containerized application or portion thereof on the cluster.

Embodiments described herein are generally directed to an edge-CaaS (eCaaS) framework for providing life-cycle management of containerized applications on the edge. According to an example, declarative intents are received indicative of a use case for which a cluster of a container orchestration platform is to be deployed within an edge site that is to be created based on infrastructure associated with a private network. A deployment template is created by performing intent translation on the declarative intents and based on a set of constraints. The deployment template identifies the container orchestration platform selected by the intent translation. The deployment template is then executed to deploy and configure the edge site, including provisioning and configuring the infrastructure, installing the container orchestration platform on the infrastructure, configuring the cluster within the container orchestration platform, and deploying a containerized application or portion thereof on the cluster.

A request to install a first version of a software application is received. The first version of the software application is stored in a first blockchain in a first distributed blockchain ledger. In response to receiving the request to install the first version of the software application, the first version of the software application is validated by running a hash of the first blockchain. In response to validating the first version of the software application, the first version of the software application is installed from the blockchain to a device. The software application may also be validated after being installed to the device.

A request to install a first version of a software application is received. The first version of the software application is stored in a first blockchain in a first distributed blockchain ledger. In response to receiving the request to install the first version of the software application, the first version of the software application is validated by running a hash of the first blockchain. In response to validating the first version of the software application, the first version of the software application is installed from the blockchain to a device. The software application may also be validated after being installed to the device.

Methods and apparatus provide for downloading application software from a server, including: downloading the application software from the server, where a first application software file contains only a portion of the application software, and a second application software file contains more than the portion of the application software; executing the application software and generating application images based thereon, where execution of the first application software file contains enough of the application software to execute a limited amount of the application software; and displaying the application images on a display screen based on the execution of the application software, where the acquisition unit begins downloading the second application software file in a background process after downloading the first application software file and at least partially during the execution of the first application software file.

A method for obtaining download information of an application includes: a first device reading tag data of a second device; a second server receiving a first request that carries identification information of the second device and application supporting capability information of the first device. The identification information is associated with the tag data and the first request is used for obtaining download information of a device management application from the second server.

A method for obtaining download information of an application includes: a first device reading tag data of a second device; a second server receiving a first request that carries identification information of the second device and application supporting capability information of the first device. The identification information is associated with the tag data and the first request is used for obtaining download information of a device management application from the second server.

A method includes, while an application is installed on a device and a representation of the application has a designated location in a respective portion of an application launching user interface, detecting an application-demotion request to delete the application from the device without deleting associated data for the application. In response to detecting the application-demotion request, deleting the application from the device without deleting the associated data for the application. After deleting the application from the device, detecting a request to display the respective portion of the application launching user interface and, in response to detecting the request to display the respective portion of the application launching user interface, displaying the respective portion of the application launching user interface, including displaying the representation of the application in the designated location in the respective portion of the application launching user interface.