Gents [ @olivierlambert @fohdeesha], let me reply to both of you and finish this unfortunate (part of) the discussion.
It took this drastic downturn and I am not enjoying it at all [!] as both you as well.
Your active engaged in community forum is admirable and I mean it! (especially because of your position, Olivier).
I was directed to XO project because of very favorable opinions about the support and robust community.
That being said - please do not hold it against me though that I am disappointed that I received answers which were not helpful.
You do not have to have malicious intent to do so and that is - unfortunately - my experience.
I can see though how my post might be read this way - I could phrase it better - my bad! I am sorry - that inappropriate.
To end up this negative chain - I respect you guys and it was not my intention to make it such a sour experience for everyone.
If I may propose one thing though - If you reply to the post with X number of questions try to reply to all of them.
Even if that would be just one sentence that would put requestor on the right path. That would be very appreciated.
Going back to the cloud-init itself.
Explanation that it caused a lot o issues in the past very well explains my experience with it and feel that I got from XO and cloud-init implementation of it.
- is default config for NoCloud "should" make VM responsive to it or there are some additional steps I should go through?
(I will be going back to testing with CentOS before trying Deb 10 just to be sure I am working on something that I may expect to work)
- do you support or plan to support Ignition or another project that would do the trick of on-the-fly config for cloud purposes?
- (if you do) is there any documentation for it?
Thanks for help and have a good one, Gents!