| === EugenMayer593 is now known as EugenMayer59 | ||
| maxzor_ | Hello, do you know about the OVH service provider? | 18:55 |
|---|---|---|
| maxzor_ | I rent to them a VPS. They use cloud-init for their VMs that they rent as VPS, can I make a cross-reboot config from within the VM? | 18:56 |
| maxzor_ | I'm on debian 11 and their tutorial seems wrong to me https://docs.ovh.com/fr/vps/configurer-ipv6/ | 18:57 |
| minimal | maxzor~_: are you using OVH's Bare Metal Cloud? | 19:51 |
| minimal | maxzor_: ^^^ | 19:54 |
| maxzor_ | minimal, no I am on a VPS Virtual Private Server on their Cloud | 19:54 |
| minimal | ok, and what cloud-init DataSource does that use? | 19:54 |
| minimal | Openstack? | 19:55 |
| maxzor_ | minimal, you already lost me ':). There is a /var/lib/cloud/instance/ directory with user data and things | 19:55 |
| maxzor_ | I have no clue | 19:55 |
| minimal | what exactly are you trying to do? | 19:56 |
| maxzor_ | I am trying to disable the ipv4 interface and enable a 6. (while knowing virtually nothing about interfaces and ip tables and networks) | 19:56 |
| minimal | well assuming the VPS is using OpenStack as the cloud-init DataSource then OVH's infrastructure will be providing a ConfigDrive to cloud-init which tells it the network config to use | 19:57 |
| minimal | cloud-init will then set up the /etc/network/interfaces file in Debian based on that information | 19:58 |
| maxzor_ | yes /etc/network/interfaces.d/50-cloud-init which cats : http://ix.io/4jDk | 20:00 |
| minimal | did you check /var/log/cloud-init.log to see if it obtained configuration information ok from OVH? | 20:02 |
| maxzor_ | they enabled debug info so it's verbose but I don't see any error in there | 20:06 |
| minimal | maxzor_: I didn't ask about errors, I asked about whether it shows cloud-init obtaining configuration information from OVh (via ConfigDrive) | 20:06 |
| maxzor_ | I guess I'm confused by the 50-cloud-init prose which says "will not persist across an instance reboot", but I believe that in fact it's setup once-per-instance | 20:06 |
| minimal | that "prose~" refers to the fact that if you manually modify that file then any such changes would be potentially "lost" later | 20:08 |
| minimal | is this Debian image an official OVH one? | 20:09 |
| maxzor_ | looks like the VPS is under qemu supervision, and I don't find ConfigDrive in the logs, only lines with CloudConfigPartHandler | 20:10 |
| maxzor_ | yes this deb11 was installed by ovh | 20:11 |
| maxzor_ | the log http://ix.io/4jDo | 20:12 |
| minimal | so it is configured to use Openstack as the DataSource as expected, as can be seen in the line: | 20:15 |
| minimal | Looking for data source in: ['OpenStack', 'None'] | 20:16 |
| minimal | however it doesn't actually seem to be looking for am Openstack ConfigDrive | 20:17 |
| minimal | ah, its using the Openstack metadata server instead | 20:18 |
| minimal | the line: | 20:18 |
| minimal | open 'http://169.254.169.254/openstack' | 20:18 |
| minimal | and one of the URLs it fetchs is http://169.254.169.254/openstack/3028-08-27/network_data.json | 20:19 |
| minimal | so it is getting the network config info from the OVH metadata server | 20:19 |
| minimal | line: | 20:22 |
| minimal | DataSourceOpenStack.py[DEBUG]: network_config provided via network_json | 20:23 |
| minimal | and the network config it was told to use, line: | 20:23 |
| minimal | applying net config names for {'version': 1, 'config': ......... | 20:23 |
| minimal | so it is told to setup DHCP for IPv4 on ens3 and no IPv6 setup | 20:24 |
| minimal | so the resultant /etc/network/interface file matches what OVH told cloud-init to do | 20:24 |
| minimal | maxzor_: do you have access to the OVHcloud Manager? if you look there at this VPS' info it should show any IPv4 and/or IPv6 addresses allocated to it | 20:32 |
| maxzor_ | minimal, very nice insights, thank you | 20:53 |
| * maxzor[m] uploaded an image: (12KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/LLYvjZaqSiWjRCGTmdSYbYlj/image.png > | 20:55 | |
| maxzor[m] | @minimal this is my OVH manager info | 20:56 |
| * maxzor[m] uploaded an image: (44KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/NlUlXIvPzMQbVCrZZlWncpGg/image.png > | 20:57 | |
| maxzor[m] | but somehow the ipv6 on ens3 is different in the VM | 20:57 |
| waldi | you mean: unconfigured. there is not global ipv6 on ens3 | 20:57 |
| waldi | and the page you showed clearly tells: ipv6 needs to be configure manually | 20:58 |
| waldi | "Si vous devez configurer l'IPv6, vous devez le faire manuellement sur votre système." | 20:59 |
| * maxzor[m] uploaded an image: (29KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/oMCnEMifJUdOceEELfOJEVom/image.png > | 20:59 | |
| waldi | (also debian 11, at least if it is configured the way debian does, is not properly supporting cloud-init network config at all) | 21:00 |
| waldi | maxzor[m]: and now rename that fike to *.conf | 21:00 |
| maxzor[m] | true^ so I followed the tutorial, filled this config file, and now systemd fails to raise the networking service. But now this is not related to cloud-init at all anymore | 21:00 |
| waldi | then why is this file called "cloud-init", if it does not have anything to do with cloud-init? | 21:01 |
| waldi | ah, because they tell you to use that name, wow | 21:01 |
| maxzor_ | I suspect that they hired an average intern at OVH to write this tutorial : https://docs.ovh.com/fr/vps/configurer-ipv6/ | 21:02 |
| maxzor_ | I think I will write them a mail to ask ipv6 to be a first-class citizen directly from their cloud-init meta server | 21:02 |
| maxzor_ | This is somewhat peculiar for the best french cloud provider oO | 21:03 |
| waldi | that does not help, as debian disables network config. they need SLAAC, either stand alone or with dhcpv6 | 21:03 |
| maxzor[m] | waldi: precisely ':) | 21:03 |
| waldi | do they proivision multiple systems per /64? because the address ends not in a nice number | 21:04 |
| minimal | I am surprise that it seems to be using dhcpv4 to get the IPv6 address when their metadata server could specify the IPv4 address esplicitly | 21:33 |
| minimal | I am also surprised that their manager page does not indicate netmasks for either ~Ipv4 or IPv6 addresses | 21:34 |
| minimal | though they seem to be using a /32 for IPv4 | 21:34 |
| minimal | and they're using /128 for IPv6 it seems | 21:35 |
| minimal | maxzor_: what are the contents of the /etc/cloud/cloud.cfg.d/01_debian_cloud.cfg and /etc/cloud/cloud.cfg.d/00_debian.cfg files? | 21:38 |
| maxzor[m] | <minimal> "maxzor_: what are the contents..." <- 01: manage_etc_hosts: true | 00: syslog_fix_perms: root:adm | 21:55 |
| maxzor[m] | mount_default_fields: [~, ~, 'auto', 'defaults,nofail', '0', '2'] | 21:55 |
| maxzor[m] | <waldi> "do they proivision multiple..." <- I don't know | 21:59 |
| minimal | waldi: not sure what you mean by "debian disables network config" | 22:29 |
| minimal | OVH's metadata server should be able to indicate static IPv6 or DHCPv6, or SLAAC to cloud-init | 22:29 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!
