Peter Wemm on Nostr: Dumb question for folks using #bhyve on #FreeBSD - are there any established ...
Dumb question for folks using #bhyve on #FreeBSD - are there any established cloud-init data generators for guests that could be used here?
I'm not talking about the cloud-init in the guest, but rather something to generate server-side templates for bhyve guests to use.
I have something I kludged together for my purposes to inject ssh keys, host names, etc. I'm using openstack config-drive metadata because it's what I was familiar with but it's kind of inconvenient. (For the unfamiliar, its an extra tiny block device containing either a fat or iso9660 fs, with json/yaml/files/etc inside).
I figured I should ask if I'm missing something that has already been done. Thoughts?
Slightly irritating: the openstack config drive MUST have the label "config-2". FreeBSD's makefs and libarchive will not do this. cdrtools mkisofs will allow this slightly-illegal name. I may have done a sed on the makefs-generated file system.
I'm not talking about the cloud-init in the guest, but rather something to generate server-side templates for bhyve guests to use.
I have something I kludged together for my purposes to inject ssh keys, host names, etc. I'm using openstack config-drive metadata because it's what I was familiar with but it's kind of inconvenient. (For the unfamiliar, its an extra tiny block device containing either a fat or iso9660 fs, with json/yaml/files/etc inside).
I figured I should ask if I'm missing something that has already been done. Thoughts?
Slightly irritating: the openstack config drive MUST have the label "config-2". FreeBSD's makefs and libarchive will not do this. cdrtools mkisofs will allow this slightly-illegal name. I may have done a sed on the makefs-generated file system.