2017-02-07 09:57:43 +01:00
|
|
|
---
|
|
|
|
|
title: Rollout Management
|
2018-08-01 11:01:02 +02:00
|
|
|
parent: Concepts
|
|
|
|
|
weight: 54
|
2017-02-07 09:57:43 +01:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
Software update operations in large scale IoT scenarios with hundreds of thousands of devices require special handling.
|
2018-08-01 11:01:02 +02:00
|
|
|
<!--more-->
|
2017-02-07 09:57:43 +01:00
|
|
|
|
|
|
|
|
That includes:
|
2018-08-01 11:01:02 +02:00
|
|
|
- _Technical Scalability_ by means of horizontal scale of the hawkBit server cluster in the cloud.
|
2017-02-07 09:57:43 +01:00
|
|
|
- _Global_ artifact _content delivery_ capacities.
|
|
|
|
|
- _Functional Scalability_ by means of:
|
|
|
|
|
- Secure handling of large volumes of devices at rollout creation time.
|
|
|
|
|
- Monitoring of the rollout progress.
|
|
|
|
|
- Emergency rollout shutdown in case of problems on to many devices.
|
|
|
|
|
|
|
|
|
|
- Reporting capabilities for a complete understanding of the rollout progress at each point in time.
|
|
|
|
|
|
2018-08-01 11:01:02 +02:00
|
|
|
Eclipse hawkBit sees these capabilities under the term Rollout Management.
|
2017-02-07 09:57:43 +01:00
|
|
|
|
|
|
|
|
The following capabilities are currently supported by the _Rollout Management_:
|
|
|
|
|
- Create, update and start of rollouts.
|
|
|
|
|
- Selection of targets as input for the rollout based on _target filter_ functionality.
|
|
|
|
|
- Selection of a _DistributionSet_.
|
|
|
|
|
- Auto-splitting of the input target list into a defined number deployment groups.
|
2018-06-04 16:36:56 +02:00
|
|
|
- Approval workflow
|
|
|
|
|
- Has to be enabled explicitly in configuration.
|
|
|
|
|
- Enables a workflow that requires a user with adequate permissions to review any new or updated rollout before it
|
|
|
|
|
can be started.
|
|
|
|
|
- Allows integration with 3rd party workflow engines.
|
|
|
|
|
|
2017-02-07 09:57:43 +01:00
|
|
|
- Cascading start of the deployment groups based on installation status of the previous group.
|
|
|
|
|
- Emergency shutdown of the rollout in case a group exceeds the defined error threshold.
|
|
|
|
|
- Rollout progress monitoring for the entire rollout and the individual groups.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Cascading Deployment Group Execution
|
|
|
|
|
The cascading execution of the deployment groups is based on two thresholds that can be defined by the rollout creator.
|
|
|
|
|
- success condition by means of percentage of successfully installed targets in the current groups triggers.
|
|
|
|
|
- error condition by means of absolute or percentage of failed installations which triggers an emergency shutdown of the entire rollout.
|
|
|
|
|
|
|
|
|
|
## Rollout state machine
|
2018-05-04 09:32:35 +02:00
|
|
|
|
2017-02-07 09:57:43 +01:00
|
|
|
### State Machine on Rollout
|
2018-08-01 11:01:02 +02:00
|
|
|
|
2017-02-07 09:57:43 +01:00
|
|
|
|
|
|
|
|
### State Machine on Rollout Deployment Group
|
2018-08-01 11:01:02 +02:00
|
|
|
|
