cloud-init-dev team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

Louis,
I adjusted the subject line of the 'commit' message above.

In your commit message, you say: "DEP_NETWORK is removed since the network
config must run at each boot.".

The behavior described there "run at each boot." is actually a bug.
At this point, cloud-init is supposed to only render networking information
once per instance-id.  That way it won't stomp on users changes.

Normally, cloud-init will check "is this a new instance" before re-writing
networking infrormation.
The reason you probably are seeing "at each boot" is that Scaleway is
missing a 'check_instance_id'.

See as example the Azure definition:
    def check_instance_id(self, sys_cfg):
        # quickly (local check only) if self.instance_id is still valid
        return sources.instance_id_matches_system_uuid(self.get_instance_id())

We are actually doing some work right now to allow networking configuration
to be done more frequently than "per-instance", with the ultimate goal
of being able to have cloud-init handle hot-plug or new IP addresses available
in the metadata service.

So..
Do you *need* cloud-init to render this more than once per instance?
Will the result change in the life of an instance?

Scott

-- 
https://code.launchpad.net/~louis/cloud-init/+git/cloud-init/+merge/347973
Your team cloud-init commiters is requested to review the proposed merge of ~louis/cloud-init:enable_Scaleway_network_config into cloud-init:master.