Tencent Cloud support for Flatcar Linux

[HeikoOnnebrink]

We are happily using Flatcar Linux on OpenStack and Google with Ignition and no problems .. :-) We have to expand the deployments also to China and later to Russia. As these american cloud provider are not available in these countries we will run our systems there on Tencent Cloud https://intl.cloud.tencent.com

Tencent has some support for CoreOS and there exists some old VERSION=1745.5.0 image which works.., but no Flatcar Images available. Ideally you provide also Flatcar images for Tencent for download.. Tencent is huge cloud provider like the big players in the US .. so might make sense to consider them.

At least some advice where we should/could start to upload images ourself and what we might have to tweak.. Not being expert I uploaded QEMU and OpenStack images hoping that they could somehow work.. they get accepted, I can launch a machine but no network connectivity at all and no debug info or logs to share..

Here some links to Tencent that might be helpful to get into that topic :

https://intl.cloud.tencent.com/document/product/213/4945 https://intl.cloud.tencent.com/document/product/213/9929

Thanks for any advice or even better official Tencent support..

[HeikoOnnebrink]

if you would support with some advice how to proceed here we would be glad to test and share our feedback so that at least we end up with some tech note how to get Flatcar up&running on Tencent .,,

[HeikoOnnebrink]

One more update as we struggle to use Ignition Tencent's metadata service seems not to run on 169.254.169.254. Instead they use metadata.tencentyun.com which resolves to 169.254.0.23 How can a Flatcar image be patched / configured to pull user_data from this different IP? Do we need a custom flatcar-metadata utility for Tencent?

[pothos]

Hi, can you please have a look at the CoreOS image and what contents you find in /usr/share/oem/oem-release and the other files there? This will tell us which image format was used.

The network is configured depending on the OEM ID kernel parameter passed by GRUB. The configuration is either done by afterburn or by networkd files that match for the OEM ID.

The user data is pulled by ignition depending on the provider. For OpenStack it's the IP you wrote, for CloudStack it's the DHCP server etc. But you can also overwrite this with either a custom kernel command line parameter via GRUB by adding set linux_append=ignition.config.url=http... to /usr/share/oem/grub.cfg or with an entry in the default ignition config to fetch the config from somewhere else.

Do you know what information the metadata server provides and if the network can be configured by DHCP?

[adriandav]

Hi, In /usr/share/oem there is only grub.cfg: cat grub.cfg set linux_append="$linux_append ipv6.disable=1"

The metadata Tencent provides can be found here: https://intl.cloud.tencent.com/document/product/213/4934

[HeikoOnnebrink]

to answer your question about networking :

I checked a vm created with old Tencent CoreOS image and found static networking in place :

cat eth0-static.network [Match] Name=eth0 [Network] Address=10.29.140.40/26 Gateway=10.29.140.1

Also as info : the Tencent Cloud is based on OpenStack (Pike).. see

https://www.openstack.org/marketplace/distros/distribution/tencent-cloud/tencent-cloud-tstack https://thenewstack.io/tencent-serving-billion-users-openstack/

Maybe this also helps to get Flatcar running there ..

[adriandav]

Hi, We have added linux_append="ignition.config.url=http://169.254.0.23/latest/user-data/" in grub.cfg, but ignition still cannot pull the user data (see attached file).