I actually would prefer to continue developing/running on my laptop and use the xen hosts only as hypervisors. So in the 2 dom0 case below, I feel it is less awkward to use the native dev environment.
Where running the code on inside vBox helps is that developers always run "ant run" or "ant debug" rather than do the full rpm deploy and install. Being able to use DevCloud as the final verification environment for such a deployment pre-check-in would help a lot. -- Chiradeep On 7/25/12 11:11 AM, "Edison Su" <[email protected]> wrote: > > >> -----Original Message----- >> From: Edison Su [mailto:[email protected]] >> Sent: Wednesday, July 25, 2012 10:51 AM >> To: Rohit Yadav; [email protected] >> Subject: RE: Development with multiple devclouds >> >> >> >> > -----Original Message----- >> > From: Rohit Yadav >> > Sent: Wednesday, July 25, 2012 2:44 AM >> > To: Edison Su; [email protected] >> > Subject: Development with multiple devclouds >> > >> > Hi Edison and everyone, >> > >> > Devcloud works fine as one hypervisor/xen host. But, in order to >> > develop/test certain features of CS such as migration among hosts in >> a >> > cluster, you would require at least two hypervisor hosts. >> > >> > To solve this problem, using VBox's NAT and host-only adapter I tried >> > various combinations, but none of them are working. >> > >> > I tried VBox's; 1. host-only adapter in place of NAT, keeping the >> same >> > gateway and network (my system crashed); 2. the default NAT + one >> > host-only adapter; with another devcloud vm which is only used as a >> > hypervisor/xen host. >> >> The last method(NAT + one host-only adapter) should work: >> >> > >> > @Edison: On the wiki page, you mention not to reinitialize the NAT. >> Is >> > the NAT's mac and dom0/xen's IP values tightly coupled with the >> present >> > devcloud image? >> >> If the MAC address is changed, then the default eth0 will be disabled, >> as there is a udev rule >> In devcloud, which binds eth0 on a specific MAC address. I will remove >> the rule in the next devcloud release. >> FYI, the rule is in /etc/udev/rules.d/70-persistent-net.rules, you can >> remove it by yourself, then restart devcloud, >> Eth0 will be enabled again. >> >> > >> > How can I run run multiple devclouds/vms on VBox such that only one >> is >> > used for management/storage/xen and the others are just used as xen >> > hosts (as within a cluster the hypervisors hosts should be homogenous, >> > using the same devcloud vm should be fine). >> > >> > To solve this problem, now I've two separate Citrix XenServer vms on >> > VBox and trying to setup a management server/nfs-storage running on a >> > third Ubuntu desktop VM on VBox. >> > Comment/suggestions on this issue and my approach now? >> >> The following combination should work: >> 1. one devcloud VM has one NAT nic + one host-only nic >> 2. another one devcloud VM has one host-only nic, which uses the same >> host-only network as above devcloud. >> >> The first devcloud VM acts as both mgt server and xen host, the second >> one just as a xen host. >> The changes need to make in both VMs: >> In first devcloud VM, put xenbr0 on eth1(I assume it's the host-only >> network), instead of eth0. > >One more thing...: Need to join both vm1 and vm2 into a cluster with "xe >pool-join" >I'll have a try by myself at first, then give you a detailed instruction. > >> >> > >> > Thanks. >> > >> > Best regards, >> > Rohit
