Ubuntu 14.04.1 LTS with AoE driver/initiator. Block level Storage Area Network (SAN) driver/initiator based on the ATA over Ethernet (AoE) protocol.
The vblade container must be running before using this AoE initiator. See here for details: https://registry.hub.docker.com/u/symlogix/vblade/
This build of the AoE initiator container is suitable for demos, testing, evaluation, proof-of-concept and training.
sudo docker run -i -t --privileged symlogix/aoe_initiator bash --privileged is required to properly load and unload the aoe module
* Please note that there are two dashes before privileged *
|Quick start on a running aoe_initiator container|
1) Remove aoe module to clear old data
modprobe -r aoe
2) Load aoe module
3) See available AoE SAN targets
4) Create file system on AoE target (for this example shelf #2, slot #1)
5) Mount remote file system on AoE target
mount /dev/etherd/e2.1 /mnt
6) Change directory to /mnt and write a file
a) Like many SANs, there is usually a one-to-one relationship between a SAN target (e.g. vblade) and the initiator (in many places this could be a NAS or server). A vblade container should only be read/write accessed by a single AoE initiator. A clustered file system is required if you plan to have your vblade SAN target support multiple, simultaneous AoE initiators. On the other hand, a single AoE initiator can simultaneously access multiple vblade or AoE SAN targets. This makes distributed, network (gigabit per second speeds and higher) RAID very possible - powerful, flexible and fast.
a) aoe-discover, aoe-flush and other utilities seem to be malfunctioning within this build. To be investigated.
b) There is no automated build repository for this AoE initiator container at this time. Possibly a bug with the automated building process, Linux kernel headers or other? Docker tech support is investigating.
Questions? Contact us: https://www.symlogix.com/contact/