As we know, when you insert a chart based on a range data, the chart will update automatically while you change the data in the range.
In some cases, you just do not need the chart updating with the data.
In order to meet everyone's needs, there are four update strategies that we have developed based on feedback during our alpha period.
It's important to note that updates are always downloaded to the passive partition when they become available.
If you don't automatically load new Container Linux images into your PXE/i PXE server, your machines will never have new features or security updates.
An easy solution to this problem is to use i PXE and reference images directly from the Container Linux storage site.
The main goal behind this strategy is to allow for an update to be applied to a cluster quickly, without losing the quorum membership in etcd or rapidly reducing capacity for the services running on the cluster.
The reboot lock is held until the machine releases it after a successful update.
We don't recommend this strategy unless you reboot frequently as part of your normal operations workflow.
PXE/i PXE machines download a new copy of Container Linux every time they are started thus are dependent on the version of Container Linux they are served.
The number of machines allowed to reboot simultaneously is configurable via a command line utility: strategy works exactly like it sounds: the machine is rebooted as soon as the update has been installed to the passive partition.
If the applications running on your cluster are highly resilient, this strategy was made for you. The update will be installed onto the passive partition and await a reboot command to complete the update.
For information on how to obtain the latest build of Symantec Endpoint Protection, see Download the latest version of Symantec Endpoint Protection.