MicroOS network configuration with cloud-init


I’m trying to configure MicroOS network with the help of cloud-init (DataSourceLocalDisk). I’ve managed to understand where to put the files (/cloud-init-config/) and which files (meta-data, user-data). I’m OK with the mecanics of updating the instance-id to make the change (along with the transactional-update bits, obviously), I’ve been able to figure out that it takes my meta-data and user-data into account, but it’s actually not configuring the network at all (I tried to set some ssh keys from user-data, which proved to work).

The doc from Kubic cloud-init does not help much (it doesn’t even say that the userdata files must be in /cloud-init-config), so I’m a little lost (not to say completely lost) on the exact process of configuring the network piece.

Can someone details this for me?


My first question would be what is the “MicroOS network”, a search on “MicroOS network cloud” points me to theMicrosoft Cloud OS Network but is that it?

Can you provide a link to the instructions that you used?

Hi, welcome

IMO you won’t find many Kubic users here. Better subscribe to the support mailing list, or contact the developer ( who happens to be our openSUSE chairman ). I’m aware of Kubic, yet haven’t had the time to start playing with it.

AH OK, I’ll try there, Thanks !

MicroOS is somewhat comparable to a JeOS image which is available in various guises in various technologies including docker (kubernetes and docker are both container technologies which makes some topics similar). IIRC there was some thoughts about exporting the MicroOS idea beyond just Kubic but haven’t seen or heard whether that has happened or not.

I probably need to take another look at openSUSE Kubic again, and I remember when I looked at it before the rather recent project re-organization that main efforts were in just making the technology work, and to support SLES specifically. Documentation for Kubic is very sparse (requires and assumes some rather advanced technical knowledge) and documentation for non-SLES setup, deployment and management is practically non-existent… So yes, if you can’t translate the SLES oriented documentation into Tumbleweed, that’s a problem.

If you still need help beyond what you can get on the ML, post what guides you’re following(and translating I’m sure) plus what you’ve done in detail, I’m sure we can figure it out.

My observations,