Red Hat Bugzilla – Bug 1020564
cloud-init requires documentation
Last modified: 2017-04-02 20:25:56 EDT
Description of problem: cloud-init was introduced in 6.4 http://rhn.redhat.com/errata/RHEA-2013-0535.html Currently, there is no RHEL cloud-init documentation (neither description nor configuration). Rudi thought that the likely place would be the Deployment Guide.
This is also important to RHEV, here is a bug for cross-referencing purposes. https://bugzilla.redhat.com/show_bug.cgi?id=977201
I initially raised this because, although cloud-init is used in OpenStack images (and elsewhere), it is included in RHEL packaging. Should at least have a basic intro somewhere?
Hello Giuseppe, I am working on a related bug for Atomic Host: BZ#1270656. This is a request to update the doc with the new features for Atomic. As I understand it, cloud-init is something like a Kickstart file for cloud images and does not apply only to Atomic, so more generic docs would be useful. Could you explain what cloud-init can be used for, so we can decide under which product it should be documented? Related to this, if it is only for cloud-images, why is it available in RHEL as an RPM? What is the use case there? Thanks!
Thanks Giuseppe, just to clarify, is there any benefit particularly for RHEL users? If there isn't anything significant, cloud-init will stay in the Atomic docs only.
cloud-init can still be used by RHEL users, but I think it makes more sense for Atomic users
My question would be, who delivers cloud-init? Other products use it as well, like OpenStack. So, whichever channel delivers it (RHEL?), the user will go to that product for information.
I'm no longer in docs, so referring this to Andrew, who can review it in light of other OpenStack docs. Andrew can also ensure that the OpenStack docs now correctly refer to the updated RHEL docs. Thanks for your work, Maxim. Nice to have it done. :) Andrew?
Hi Summer, Thank you for the needinfo request. Maxim - The list of resources looks good, but I wonder whether it would help reduce the maintenance cost if we were just to list the titles for each product and link to the documentation splash page for each product rather than the individual guides for specific versions. Whatever works easiest. :) Kind regards, Andrew
I've looked at the added stuff and it looks good to me