Closed yomimono closed 7 years ago
I guess we should wait to merge this until Mirage 3 is out, right?
If you want master
to be buildable with the current stuff in opam-repository
, yes. For testing integration, we can just as easily build against another branch -- just let me know what you'd prefer.
Yeah, let's keep it on a branch for now then.
I can change the requested target branch of a PR, but apparently I can't request that a PR be merged to an entirely new branch. It's up to you, mirage-qubes-owner
!
OK, we have an ipv4 branch now.
Thanks very much! I'll close this out, then.
Qubesdb_ipv4 is intended for use with the
mirage
frontend tool as a replacement for static or dynamic IPv4 configuration. As QubesOS doesn't provide a DHCP server for VMs and doesn't surface IP configuration information before the VM exists, a nice interface for statically configuring the interface with the information looked up from QubesDB is required for MirageOS unikernels to be good network citizens on QubesOS.This module just wraps the
Static_ipv4
module fromtcpip
to build anipv4
with the supplied parameters from QubesDB. It makes no attempt to monitor the database for changes or sync the unikernel's IP configuration with them.