You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I currently have been using vm-bhyve to set up and manage my deployments, I have custom zvols attached to my vms, assigned MAC addresses for the DHCP. Those two features are essential on my environments.
I couldn't find any reference on the documentation, are those scenarios supported or will be in the future?
Thanks and congratulations on what you have accomplished so far!
The text was updated successfully, but these errors were encountered:
The docs are lagging behind a little bit, because I am more focused on the code part for now 🙈
I could definitely look into the dhcp support, because it's used all around the place within the on-prem installations. And really the only part that needs to be changed is the CloudInit template, as right now it only supports the static IPs (which are being automatically generated).
The zvol part is a bit more tricky, because we're using the .raw files within the isolated datasets for a reason: atomic VM snapshots. No matter how many disks the VM has - if you rollback a snapshot data will always be consistent across all of them (otherwise the data might be just so slightly out of sync, think db+web server deployments on separate disks).
I could look into implementing the recursive snapshots, and placing the zvols under the VM's dataset, but it has to be tested and in the end I don't know if that'd solve your issue.
Hi,
Very interesting tool, l will start testing.
As I currently have been using vm-bhyve to set up and manage my deployments, I have custom zvols attached to my vms, assigned MAC addresses for the DHCP. Those two features are essential on my environments.
I couldn't find any reference on the documentation, are those scenarios supported or will be in the future?
Thanks and congratulations on what you have accomplished so far!
The text was updated successfully, but these errors were encountered: