What we should do is have an overrides option in maven itself to override the default cfg file with a developer's own config file. The reason it is set to 192.168.56.1 is that most developers (or users if they are trying to checkout cloudstack) workflow would be to run mgmt server and db server on their host os and use DevCloud just as recycle-able host+storage.
Not objecting, just that we should fix it in maven so if a devcloud.cfg.override is available (or some other name), it would read that file only while deploysrvr is done. Regards. On 09-Jan-2013, at 4:11 PM, Marcus Sorensen <shadow...@gmail.com> wrote: > Unless anyone objects, I'm going to change the devcloud.cfg for marvin to > add 192.168.56.10 as the 'host' global config. Without this, you don't get > the tinylinux template. With it, and a restart after applying the config, > you get the template as soon as the secondary storage vm is provisioned. > > > On Sun, Jan 6, 2013 at 8:55 PM, Marcus Sorensen <shadow...@gmail.com> wrote: > >> I had the exact same thing as well following devcloud2 instructions. It >> seems the ssvm only connects to the host-only network. That's probably fine >> for basic testing since there is already a tinylinux template, but we >> should consider setting the default zone up such that the ssvm will connect >> to the NAT so it can get DNS/internet for actual functional testing >> >> >> On Sun, Jan 6, 2013 at 2:36 PM, Sebastien Goasguen <run...@gmail.com>wrote: >> >>> Jamshid, I don't think anyone answered you ? >>> >>> Are you having issues starting instances ? >>> >>> -Sebastien >>> >>> On Dec 28, 2012, at 8:50 PM, Jamshid Afshar <jamshid.afs...@caringo.com> >>> wrote: >>> >>>> I built and am running the management server inside the devcloud2 vm. >>>> I had to change "host" in Global Settings to 192.168.56.10, do I need >>>> to change other settings? >>>> >>>> Maybe this expected, but I see this error on Secondary Storage system >>>> vm "s-1-vm" in /var/log/cloud/systemvm.log: >>>> >>>> WARN NfsSecondaryStorageResource Error in configuring route to >>>> internal ip err=RTNELINK answers: Invalid Argument >>>> >>>> The script /usr/local/cloud/systemvm/ssvm-check.sh reports "ERROR: DNS >>>> not resolving download.cloud.com". If I comment the "exit" out the >>>> other tests succeed (ie, it sees management server at >>>> 192.168.56.10:8250). >>>> >>>> Should a DNS server be running on my (all-in-one) management server / >>>> host 192.168.56.10? >>>> >>>> Should I be able to ping 169.254.1.1 from s-1-vm? I can't. "route" >>> shows: >>>> >>>> 192.168.56.0 * 255.255.255.0 eth1 >>>> 192.168.56.0 * 255.255.255.0 eth2 >>>> 192.168.56.0 * 255.255.255.0 eth3 >>>> link-local * 255.255.0.0 eth0 >>>> default 192.168.56.1 0.0.0.0 eth2 >>>> >>>> Thanks, >>>> Jam >>> >>> >>
