Description
The Cloudvue release process involves multiple components and regions. In addition to the cloud software there are C2C, Cloudvue Manager, Cloudvue Mobile and Cloudvue Access. Generally, software will release to NA first and if no issues are detected to EMEA and AU a few days later. This pattern is followed for each component with C2C and Cloudvue Manager released together. The complete release cycle can take several weeks before all components to be completed.
Cloud
Engineering must supply a cab file containing all the cloud components such as OS, Database, anything that runs in the cloud to the SRE team for approval. Once approved it is then implemented by region, replacing all current Cloud components.
You can view the release summaries outlining what enhancements, fixes and integrations have been made by logging into Cloudvue Manager and going to https://dashboard.cloudvue.com/releases
Cloudvue Gateways
When available software updates can be manually applied to individual Cloudvue Gateways via Cloudvue Manager. In addition, Engineering can automatically push update to Cloudvue Gateways using the release manager. https://dashboard.cloudvue.com/releases/manage
C2C
Software updates for C2C devices are like Cloudvue Gateways with the exception that the updates are not automatically pushed. C2C devices must be manually updated.
Cloudvue Mobile
Software updates for Cloudvue Mobile are made available through the appropriate play store.
Cloudvue Access
Cloudvue Access consists of the mobile application which can be updated through the appropriate play store and the KT-1 controller software and firmware which can manually be updated from the devices page in Cloudvue Manager.