DevCloud is the sandbox for CloudStack, it can be used in different mode:
- Full sandbox
- Development environment
- Cloud testbed
The full sandbox runs the CloudStack management server and acts as a host, using nested virtualization to start instances within DevCloud. This is great for testing and training.
The development environment is used when developers want to develop CloudStack, modify the source, build locally and deploy on a working setup. In this use case, they push their current development to DevCloud.
In the testbed version, you run the management server locally and use DevCloud as a host and NFS server. Of course multiple variations can be done: adding hosts, different storage backends (possibly) and adding different physical machines.
In the screencast below I demo the testbed setup, using a host-only interface, running the management server on OSX (mac book air) and starting tinylinux instances within DevCloud.
Below is the screencast that will say more than I can write in this blog
Testing CloudStack 4.1 with DevCloud from sebastien goasguen on Vimeo.
If you are interested in the first release of CloudStack: 4.0 Incubating, watch the screencast below, which shows you the testing procedure we followed to vote on the release.
CloudStack 4.0 testing procedure from sebastien goasguen on Vimeo.
That's awesome Sebastien, thanks for the post.ReplyDelete
Hey just watched the video, so we don't really need to restart the mgmt server after we deploy using marvin. Nevertheless, this works too.ReplyDelete
The video is missing. Is it available somewhere?ReplyDelete
Hi.. Having hell on earth setting up devcloud and cloudstack.. The links you refer to are dead and same for the videos..ReplyDelete
that's a 2 1/2 year old post, you should use 4.4 version not 4.1 which was shown here.ReplyDelete
and try this for devcloud:
if you want to try Docker, the cloudstack simulator is available:
docker pull runseb/cloudstack-simulator