| 2019-03-20 13:29:43 |
Dan Watkins |
description |
Platform: FreeBSD 11.2-RELEASE amd64, FreeBSD 12.0-RELEASE amd64
cloud-init 18.3 from official ports tree: https://www.freshports.org/net/cloud-init/
seed sample:
network-config:
--
version: 1
config:
- type: physical
name: enp0s4
subnets:
- type: static
address: 172.17.0.98/24
gateway: 172.17.0.98
- type: nameserver
address:
- 8.8.8.8
search:
- my.domain
meta-data:
--
instance-id: cloud2-fbsd-01
local-hostname: cloud2-fbsd-01.mycloud.com
guest cloud.cfg settings:
..
system_info:
..
distro: freebsd
..
at cloudinitlocal startup i see:
..
running command ['blkid', '-odevice', '/dev/sr0'] with allowed return codes [0, 2] (
..
cloud-init for some reason doesn't recognize distro settings and try to use Linux-specific command ('glabel' or 'gpart show' for FreeBSD should be used).
Also, when media found, further work leads to:
--
init.py[WARNING]: apply_network_config is not currently implemented for distribution '<class 'cloudinit.distros.freebsd.Distro'>'. Attempting to use apply_network
--
user-data also ignored.
I know that you are not interested in supporting FreeBSD on your own, but why do you hinder the community from improving your product? There are patches to support FreeBSD from different people. Therefore, this issue is also called “feature request” to support FreeBSD. Some large cloud / hosting organizations provide their clients with the FreeBSD platform. |
The NoCloud data source appears to not correctly search for available seed devices on FreeBSD.
=== Original Report ===
Platform: FreeBSD 11.2-RELEASE amd64, FreeBSD 12.0-RELEASE amd64
cloud-init 18.3 from official ports tree: https://www.freshports.org/net/cloud-init/
seed sample:
network-config:
--
version: 1
config:
- type: physical
name: enp0s4
subnets:
- type: static
address: 172.17.0.98/24
gateway: 172.17.0.98
- type: nameserver
address:
- 8.8.8.8
search:
- my.domain
meta-data:
--
instance-id: cloud2-fbsd-01
local-hostname: cloud2-fbsd-01.mycloud.com
guest cloud.cfg settings:
..
system_info:
..
distro: freebsd
..
at cloudinitlocal startup i see:
..
running command ['blkid', '-odevice', '/dev/sr0'] with allowed return codes [0, 2] (
..
cloud-init for some reason doesn't recognize distro settings and try to use Linux-specific command ('glabel' or 'gpart show' for FreeBSD should be used).
Also, when media found, further work leads to:
--
init.py[WARNING]: apply_network_config is not currently implemented for distribution '<class 'cloudinit.distros.freebsd.Distro'>'. Attempting to use apply_network
--
user-data also ignored.
I know that you are not interested in supporting FreeBSD on your own, but why do you hinder the community from improving your product? There are patches to support FreeBSD from different people. Therefore, this issue is also called “feature request” to support FreeBSD. Some large cloud / hosting organizations provide their clients with the FreeBSD platform. |
|
