Could I mech up multiple machines with a single Mechfile?

[lochuan]

No description provided.

[ColdHeat]

Don't believe this is possible in the current implementation. Mechfiles don't really refer to multiple VMs/boxes. Not sure if it even makes sense to do so.

[lochuan]

It's so tedious every time when I try to set up a distribution system emulation environment. It saves a lot since I found Vagrant, but the vm booting time in Vagrant is so slow, the performance is also very poor when I take Vagrant with VirtualBox. According to my feeling, the booting time in combination of mech box and VMware Fusion is at least 3x faster than Vagrant with VirtualBox. Hope the multi-machine feature appearing in up coming version.

[derhornspieler]

I 2nd that feature for multi boxes within mechfile

[derhornspieler]

For time being I've just created individual directories for each box and run mechfile via mech init in each directory. Seems to be working fine so far. I agree with the faster performance. Well done ColdHeat!

[Kronuz]

To support multiple Mech boxes we need to change the internal directory where the boxes are put. I believe we can simply add an extra layer inside .mech, instead of uncompressing directly there. About configuration, I think we could make it so Mechfile also supports an array of objects, not only object. I’ll see if I get the time to work on this

[mkinney]

Sharing a repo that shows how you can have Mechfiles in separate directories: https://github.com/mkinney/multiple-mech

[mkinney]

I mis-understood this issue. The repo above shows how to have a single instance of various different images - not multiple instances of the same image.