Deploy Edge Applications to Multiple Sites Using Marketplace Catalog Sync

you can use the synchronization feature in the marketplace catalog to deploy a common list of edge device applications to multiple sites this feature allows you to centralize the deployment and availability of applications to all litmus edge (le) instances, even if they are in air gapped networks create and distribute a new containerized application to multiple sites in a simple and scalable way update a containerized application and send those updates securely to multiple sites notes the synchronization feature is part of the marketplace catalog inside the litmus edge manager it is available in litmus edge manger 2 11 0 and later overview at a centralized location, the admin user who is responsible for distributing applications can create a primary catalog then, an end user at an individual site can create a secondary catalog to synchronize with the primary catalog an authorization process is used to establish a secure relationship between the two catalogs the end user can sync the secondary catalog with the primary to receive new or updated applications after the synchronization process is complete, the secondary catalog will have identical applications and registries as the primary catalog this feature ensures that all sites have access to the same applications that can be deployed to edge devices as a result, local it teams will experience fewer maintenance and troubleshooting issues, reducing overhead costs user scenario syncing application updates to global manufacturing sites a global manufacturing company has recently released version 2 of its analytics application the application is part of the company's suite of tools offered through the primary marketplace catalog and is critical for its customers' day to day operations the company must ensure that all its clients worldwide, operating in different site locations, receive this update in a timely and secure manner primary site headquarters (canada) the company's it administrator logs into the litmus edge manager (lem) with the primary marketplace catalog at their headquarters located in canada they upload the new version of the application into the primary catalog the administrator notifies all secondary catalog admins of available updates via email secondary site customer location (japan) the local it staff at the japan site receive a notification that a new application version is ready for synchronization the local it staff logs into their local lem with the secondary marketplace catalog they manually initiate a sync with the primary catalog to pull the new application version the new version is then deployed across all local edge devices within the site outcome all le devices at the japan site are successfully updated to version 2 of the minio application, with minimal disruption to the site's operations the cascade catalog sync feature ensures that the updated application in the primary catalog is available to all global sites, maintaining consistency and efficiency across the company's vast operations before you begin ensure you have two working instances of lem to set up a primary (canada) and secondary (japan) site if you are ready for the user scenario, proceed with the first article listed below this process includes the following steps step 1 create primary catalog with list of applications docid\ qbozmpgvaqv8 jm5vyv step 2 create secondary catalog docid\ zo8hyyhjolaeih2thm7 w step 3 establish secure connection between primary and secondary catalog docid\ s8jgesigupfpehtdb cfv step 4 synchronize secondary catalog to primary catalog docid\ ilfe6vhxxhgsqhuisb8dl step 5 deploy an application from secondary catalog to edge devices docid\ rhjyecj3pt9wzlbssptmy step 6 (optional) update an application version docid\ iq9xxw9m86q7kzajimqqt