1378383 - [OpenCloudConfig] - move as much processing as possible from instance startup into AMI initialisation

Status: RESOLVED INVALID

(Infrastructure & Operations :: RelOps: OpenCloudConfig, task)

Description

[Pete Moore [:pmoore][:pete]]

In order to reduce startup times of instances, we should move all workertype-specific setup to AMI creation time, such that the only initialisation that occurs at worker startup time is worker-specific (such as host renaming).

Comment 1

[Rob Thijssen [:grenade (EET/UTC+0300)]]

worker type setup is already occuring during ami creation.

occ does some checks and cleanup between tasks:
- occ validates instances still have their "desired state configuration" at each boot run but typically this takes about 30 seconds to complete. for the value added by being able to validate that the instance setup is still in its desired state after a task run that can alter or break system configuration, i believe 30 seconds is something we can live with in the context of the value provided by that validation.
- occ formats the task specific hard drive as a workaround to bug 1433854. this will be removed after that bug is fixed.
- occ resets cache permissions as a workaround for bug 1350956. this will be removed after that bug is fixed.

i believe there is nothing to be done here.

if there is some specific processing that is occuring on worker instances that should be occuring during ami creation (i am not aware of any), please raise a specific bug citing the item of processing that should be moved. there is very little value in a general statement that "as much processing as possible" should be moved as there is nothing implementable in that statement.