Documentation sugests using proprietary VMWare Fusion

[Tomasz 'Zen' Napierala]

Documentation only explains how to set up devstack on VMWare Fusion. This is proprietry and quite expensive product. Moreover it only runs on Mac OS X. It might be a barrier for contributors. Instead, there should be documentation for some more universal product like VirtualBox - available on all platforms, open source and free.

[ruhe (ruhe)]

I'm the author of that document and I think it should be removed. Sahara docs shouldn't be a place to document Devstack installation and configuration.

But, there is a reason we used VMWare Fusion - it's the only virtualisation software (in pair with other VMWare products for Linux and Windows) which supports nested virtualisation. Nested virtualisation is crucial for running Hadoop jobs inside nested VMs.

So, there should just be a note about virtualisation platforms capable of running Sahara/Hadoop loads inside nested VMs.

[ruhe (ruhe)]

I should also note that KVM also supports nested virtualisation, but it is Linux-only.

[Michael McCune (mimccune)]

VMWare Fusion is mentioned in http://docs.openstack.org/developer/sahara/devref/devstack.html

This appears to be the only mention of it in the docs.

[Andrew Lazarev (alazarev)]

Doc is useful, so it is good to keep it somewhere. But agree, DevStack installation with Sahara is not a proper place for it.

[Sergey Lukjanov (slukjanov)]

I think it could be extremely useful for mac-based newcomers (part re fusion) and for all new comers too (part about how to install devstack with working sahara)

[Andrew Lazarev (alazarev)]

May be resolve bug by adding instructions for other hypervisors?

[Sergey Lukjanov (slukjanov)]

We could add instructions on how to run it on kvm on Linux, for the OS X VMvare Fusion is the only choice because it supports nested virt.

[Sergey Lukjanov (slukjanov)]

This bug is > 180 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

[Sergey Reshetnyak (sreshetniak)]

This bug is > 60 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.