This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.
DevCloud is a virtual appliance shipped as an OVA image which runs on VirtualBox (an opensource type-2 or desktop hypervisor) and can be used for CloudStack’s development and testing. The original DevCloud required 2G of RAM, and ran Ubuntu Precise as dom0 over xen.org’s Xen server which runs as a VM on VirtualBox.
A developer would build and deploy CloudStack artifacts (jars, wars) and files to DevCloud, deploy database and start the management server inside DevCloud. The developer may then use CloudStack running inside DevCloud to add DevCloud as a host and whatnot. DevCloud is now used by a lot of people, especially during the first release of Apache CloudStack, the 4.0.0-incubating, DevCloud was used for the release testing.
DevCloud is now capable of using either the VirtualBox (and XenServer) or KVM hypervisors. You only need to choose one of these, and then following either the VirtualBox or Linux KVM "setting up" sections, below.
If you want to run XenServer as a nested hypervisor, see XenServer Hypervisor for CloudStack Development using Fusion
1. Get the new DevCloud 2.0 virtual appliance. The new image was created using this process. Note: it could take some time as the image is about 900MB. For the 4.3 release, get the updated DevCloud 2.0 appliance.
2. Install VirtualBox 4.2 or latest.
3. Create and config a "host-only" network in VirtualBox, if you don't have one (or have just installed VirtualBox).
3.1 To create a network, go to File -> Preferences -> Network -> "Add host only network", it would usually have a name like vboxnet0 etc. (Windows Only: You don't have to perform the Add host only network" step, move on to step 3.2)
3.2 To config the network created in step 3.1, right click and select "Edit host-only network", then uncheck "Enable server" in the "DHCP server" tab
3.3 (Windows only) Start Administrative Tools > Windows Firewall with Advanced Security. Click on the "Windows Firewall Properties" (central panel, possibly quite small print) and for each of the profiles (Domain, Private, Public) click on the Protected Network Connections "Customize..." button and uncheck the "Virtual Box Host only Network" so that the Windows Firewall does not block communications on that network.
4. Import the DevCloud ova image into VirtualBox.
4.1 Verify PAE mode is active. Under the VM settings, System > Processor Tab, make sure 'Enable PAE/NX' mode is checked.
5. Start the DevCloud VM. (Windows: It will complain that the virtual machine doesn't have vboxnet0. Click on Edit Network to match it up with the default host only network.)
6. After VM boots up, login into VM with username: root, password: password
The default IP of DevCloud is 192.168.56.10, if you want a different IP (say you want to work with multiple DevClouds), change in /etc/network/interfaces and reboot.
7. To run the management server on your laptop:
7.1. If required, Setup a CloudStack Development Envrionment
7.2. Checkout the latest master code
7.3. Start management server on your laptop:
Then wait until management server is up.
8. Deploy DevCloud (make sure mysql-connector-python is installed and that the management server is running)
The above will deploy a zone with settings defined in tools/devcloud/devcloud.cfg which sets some global settings and will take some time. After this, you should restart management server and destroy any system vms which may have started for the global settings to take effect.
9. You can also run your setup inside of DevCloud as a all in one box solution, "ssh email@example.com". All the build tools (git, java, maven, mkisofs, etc.), mysql and nfs is preinstalled and setup. The recommended way is to run the mgmt server on your host os, work with the code and debug using an IDE like IntelliJ or Eclipse and use DevCloud as a replacement/alternative to your hypervisor host, storage and network infra.
1. Prerequisites: You should have Linux with the KVM modules and libvirt utilities (virsh) installed.
2. Download devcloud KVM package from here
3. Extract devcloud.tar to the location you want to install it to, cd into devcloud directory
4. Define networks that devcloud will use (run as root or libvirt privileged account)
5. Open devcloud.xml, change location of qcow2 file to point to the location on your system. You may also need to modify a few definitions, depending on your version of libvirt.
6. Define, start virtual machine
7. Continue with the VirtualBox setup instructions, starting at step 6
You can skip step 7 above and use one of the advanced network marvin configurations. For full functionality, these require that you set up a DNS resolver on your devcloud so that the management network can resolve names:
or, if you want to run the management server in the devcloud:
Then restart your management server as mentioned in the basic setup.
Console proxy doesn't work in this configuration on the VirtualBox install (but does in KVM), due to VirtualBox's implementation of NAT networking model. While VMs can use the NAT to get out, your computer has no interface on the internal NAT network and cannot access it (that 10.0.3.2 is in the VirtualBox stack, not on your host). You can still connect to VNC manually on the devcloud,(e.g. 192.168.56.10:0) if you know which port the VM is listening on. We can get around this by utilizing a host-only network as public, but then the VMs won't have real public access, so it boils down to what you're wanting to test.
It's possible to run the management console in debug mode for interactive debugging with Eclipse or similar. Instead of running the jetty:run command in the previous section, run...
The issue above may appear as if the "tiny Linux" template isn't available to select.
If the global "host" setting is wrong, you will see errors like this in your system VM's /var/log/cloud/systemvm.log file:
com.cloud.api.doc.ApiXmlDocWriter ClassNotFound: modify build-apidoc.sh and edit line
If Jetty is not present by default, you can include the following lines in pom.xml under <plugins> to instruct maven to obtain it:
if the build fails because maven can't find python,
with error msg like this:
Do the build this way: