cloud-init-dev team mailing list archive

[Ryan Harper <ryan.harper@xxxxxxxxxxxxx>]

On Wed, Nov 1, 2017 at 1:45 PM, Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>
wrote:

> > I'm not sure I understand the dropping of instance property from the
> NoCloud
> > KVM class vs. the LXD one.
>
> An Image does not have an instance associated with it.
>
> An 'Image' is something you can manipulate the contents of (execute,
> write_file, read_file) but is not booted.  Imagine it being a .img file
> that you can mount-image-callback on (as it is in nocloud-kvm).
>
> Currently the lxd Image is something that has to be booted in order to
> provide those operations. It uses an actual lxd.Instance to do that.
> There is nothing specifically wrong about this, and may well be how
> we have to do things on some platforms.
>

OK, IIUC, since NoCloud uses mount-image-callback, we can modify
the image without the need for an "instance" of it (aka, booted).


> --
> https://code.launchpad.net/~smoser/cloud-init/+git/cloud-
> init/+merge/333059
> Your team cloud-init commiters is requested to review the proposed merge
> of ~smoser/cloud-init:cleanup/cii-cleanup into cloud-init:master.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~cloud-init-dev
> Post to     : cloud-init-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~cloud-init-dev
> More help   : https://help.launchpad.net/ListHelp
>

-- 
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/333059
Your team cloud-init commiters is requested to review the proposed merge of ~smoser/cloud-init:cleanup/cii-cleanup into cloud-init:master.