New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No need to remove cloud-init #15
Comments
Hi @haphan, what would be your use case for keeping cloud-init around? |
The goal of removing cloud init here, as I see it, is to be compatible with
virtual env where cloud init server is unavailable.
To this end, simply disable the sevice is enough. By doing so, it allows
compatibility if moving to the cloud is needed.
Red hat offficial document also suggests to disable cloud init service when
using cloud rhel qcow2 in kvm host.
…On Sat, 9 Jun 2018 at 11:39 AM, Giovanni Torres ***@***.***> wrote:
Hi @haphan <https://github.com/haphan>, what would be your use case for
keeping cloud-init around?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAwIskknxzWs2dBX2qGYMmjUzbBaMuyTks5t60OAgaJpZM4UftH->
.
|
I don't see a problem disabling it. Would you point me to that redhat doc? |
giovtorres
added a commit
that referenced
this issue
Jun 13, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Instead of remove cloud-init, what about disable the cloud-init service only @giovtorres ?
Something like
The text was updated successfully, but these errors were encountered: