At it's base a network is built off of the linux nftables kernel module.
An externally facing network has the ability to become a DHCP client, an internal network does not. It can however be a router with a static IP and serve a different DHCP server address to virtual machines attached to it.
Guest workloads can be connected to external storage, but Verge.io cannot leverage 3rd party storage architectures.
Verge.io is based on Debian/GNU Linux and uses a custom Linux Kernel to adhere to specific OS requirements.
At the current time the installer is designed to be run by Verge.io engineers due to the complexity of the network requirements.
Containers cannot be run natively in Verge.io. However running containers can be achieved by creating a virtual machine and running your specific containerization platform inside of the vm.
VxLAN capabilities within Verge.io do not extend outside of the environment. They are created specifically to control high availability of any network that exists inside of Verge.io.
Virtual disks use the .raw format since it is the most universal drive format.
A miniumum of two nodes are required to maintain high availability.
Bug fixes, hotfixes, security updates are released on an un-fixed schedule as needed. Platform updates with additional features are released quarterly.
The vSAN stores a SHA1 hash of every block of data that is written to it. When that data is read, it is re-hashed and validated for integrity. This technique protects against silent corruption and bit rot. In the event of finding a bad block of data, our algorithm will check for redundant copies locally within the environment. If that block of data cannot be found, DR/Backup sites will be checked in real time, and the data block will be retrieved and repaired seamlessly without user interaction with no down time.
Yes, Verge.io does not have a size limitation on drives. It is important to note that through extensive research and testing that drives larger than 8TB in size are not recommended. Typically the rebuild time in larger drives can take an extended period of time leaving the possibility for a single point of failure. Spinning disks aren't recommended for production (hot) data and are typically used for archive/backup environments or (cold) data.
Updates can be run in two forms, either a rolling update or a full environment reboot.
The Verge.io vSAN works as a Redundant Array of Independant Nodes (RAIN). This is accomplished by striping the data across all drives in a tier of storage while concurrently writing the data set to its mirror on another node participating in the same tier of storage thereby guaranteeing data integrity. However, to equate it to a RAID level, it would be RAID 10 (striping and mirroring).
Verge.io will not control anything within the guest. Port management of traffic, protocols, and services can be managed via the Verge.io firewall.
Creating different internal networks inside the Verge.io platform allows for the delivery of multiple manageable networks that are all completely isolated from one another.
No, all data is cryptohashed and cryptoverified on every disk Verge.io is installed on.
Data at rest (DARE) is AES 256bit encrypted if encryption is turned on at the time of install.
SSL encryption, and AES 256 for synchronization.
VxLAN and containerized networks. VxLANs give you the ability to segregate networks with the same IP address scheme.
The containers are designed to only have network functions running. The resources used to run them are extremely minimal.
Only if the vnet is the router and/or dhcp server for the network.
No, to view a list of supported auth sources please see the auth sources wiki page.