DO Ideas 2

Document new droplet initial configuration process

It would be useful to know exactly which files are rewritten during this process so that it is possible to convert those files to a new format when needed (eg. after upgrading the distribution or installing a distribution not available by default, ..)

For a Fedora 17-based image, it seems to rewrite :
/etc/passwd (whether or not a SSH key has been specified - which is a bit annoying as there's then no way to know the root password when a key has been specified)

Any other?
Is the distribution auto-detected by the configuration-rewriting script (so that it rewrites what it thinks works for that distro) or somehow the initial distribution used to create the snapshot is stored by DO as well?

  • Cedric
  • Sep 11 2018
  • Attach files
  • Moisey Uretsky commented
    September 11, 2018 19:03

    The create script modifies access : /etc/passwd and root keys

    As well as networking

    Dependent on the distribution that is selected.

  • Ben commented
    September 11, 2018 19:03

    I'll agree, the documentation is needed. Knowing what *is* changed is important, as well as what isn't changed, but might need attention (e.g. sshd server keys).

  • Cedric commented
    September 11, 2018 19:03

    I understand that, but it would be nice to document which files do you specifically touch when creating a droplet from a snapshot.

    It would be more transparent to users, I honestly did not expect the contents of a snapshot would be modified by the host [resizing a disk image does not touch content], and, coming from other cloud providers, I expected the network config to be set up with DHCP [with the host kvm taking care of the permanent vm/mac<->ip addressing].

    Not that I have any problem with the way DO does it but it would be nice to know exactly what it's done within the snapshot :-)

    This would also allow users to easily know what to look for when they need/want to use their distro/setup of choice.

    Eg. for a Fedora 17 image, are you touching only the files listed in the original post or is there others I missed?

  • Moisey Uretsky commented
    September 11, 2018 19:03

    Each distribution is treated differently and detected and the necessary files to restore to a base state are updated which vary between distros depending on how they are set up.

  • Cedric commented
    September 11, 2018 19:03

    Ideally, a pointer to documentation should be displayed at droplet creation, perhaps something like :

    "The new droplet will have some configuration files rewritten, see <a href="/some/doc/page.html">documentation</a> for details."

    at the same location as "The root password will be emailed to you", when creating a droplet from an image.