Getting started doesn't have to demand lots of resources - personnel
time and equipment -
First suggestion - buy into an existing VCL. Paying the cost of
expansion will be more economically effective (remember "marginal cost")
than starting up a new one. Then get involved; participate in the
system, helping modify/develop code as well as using the VCL. You'll
have to cope with account generation which involves authentication and
authorization issues and interfacing with your own campus or
organization's Identity Management system. So there will be work, but
you can leverage the work done by others in the group.
That may not be possible - there may be no suitable VCL where you are.
However, remember that since the VCL is "virtual" - it's on the
Internet - that the choice of possible existing VCLs is broader than it
But what if there is no suitable choice? Then, the idea is to look to
start up a VCL which will be as large as possible - larger than your own
campus would ever need. Can you start up a multi-party organization? A
whole university system, a state-wide consortium, ... ? For some time,
as long as we are in the early years of cloud computing, there will be
many campuses and organizations which need such an organization.
If you join into an existing VCL, then a lot of the startup effort has
been finished, and there is a substantial experience base to draw on.
I.e., there are many benefits from doing it this way.