looks like a totally different  setup then I have. I will give it a
try tomorrow. Did you try this with 4.4 yet? Can you please?

On Tue, May 13, 2014 at 11:05 PM, Ian Duffy <i...@ianduffy.ie> wrote:
> Hi Daan,
>
> Took a quick look at this this evening as promised earlier on IRC.
>
> I've stopped using the Ubuntu + XenAPI setup, I never felt it worked well.
> My alternative solution/setup is below, I can get a full environment up in
> about 15mins.
>
> I have made a vagrant box of XenServer, the packer files that build this
> box can be found at: https://github.com/imduffy15/packer-xenserver
>
> I have placed the .box file on the github page of the project
> https://github.com/imduffy15/packer-xenserver/releases/tag/0.0.1
>
> In brief it brings up XenServer 6.2 with two interfaces, NAT and host-only.
> The host only interface has the IP address 192.168.56.10 and I did some
> iptables stuff to enable them to get internet access via the NAT interface.
> (It takes a bit of time to boot)
>
> I've been looking at using the chef scripts by cloudops to create a Mysql +
> NFS box. You can see a vagrant file for this over here:
> https://github.com/imduffy15/GSoC-2014/tree/master/MySQL_NFS this comes up
> on the same host interface as the XenServer box and gets 192.168.56.5, it
> supplies NFS for /exports on this IP. MySQL is exposed via virtualbox port
> forwarding due to ease with deploydb. I need to improve this to get the
> systemvms on there for the moment I use the download-templates.sh from
> https://github.com/djs55/cloudstack-dev-vms/tree/master/cloudstack-infrastructure
>
> I run the Cloudstack 4.3 ( commit c0cf817f1b2a53a23253679aa785f0db3219619a
> ) manager on my host machine which is joined to the host only network on
> 192.168.56.1. I compile it with: mvn -P impatient,systemvm clean install
> -DskipTests=true -T2C
>
> I use a slightly modified devcloud.cfg
> https://github.com/imduffy15/GSoC-2014/blob/master/devcloud.cfg
>
> General flow is as follows:
>
> 1) Start xenserver vm
> 2) Start nfs/mysql vm
> 3) Compile cloudstack deploy db
> 4) ssh into nfs vm, download systemvm templates
> 5) start up jetty
> 6) marvin to get devcloud going
>
> Planning to clean a lot of these up with CLOUDSTACK-6114.
>
> Hope this is useful.
>
>
>
> On 7 May 2014 20:32, Daan Hoogland <daan.hoogl...@gmail.com> wrote:
>
>> I am setting up a test env on my laptop using devcloud2 v4.3. I am
>> running the ms v4.4 in eclipse and the db on my laptop. I get the
>> following error:
>>
>> daan:~/cloudstack-4.4/cloudstack (4.4)> python
>> tools/marvin/marvin/deployDataCenter.py -i
>> tools/devcloud/devcloud-advanced.cfg
>> Traceback (most recent call last):
>>   File "tools/marvin/marvin/deployDataCenter.py", line 579, in <module>
>>     deploy.deploy()
>>   File "tools/marvin/marvin/deployDataCenter.py", line 561, in deploy
>>     self.loadCfg()
>>   File "tools/marvin/marvin/deployDataCenter.py", line 523, in loadCfg
>>     mgtDetails.apiKey, mgtDetails.securityKey = self.registerApiKey()
>>   File "tools/marvin/marvin/deployDataCenter.py", line 492, in
>> registerApiKey
>>     listuserRes = self.testClient.getApiClient().listUsers(listuser)
>>   File
>> "/Users/daan/cloudstack-4.4/cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py",
>> line 600, in listUsers
>>     response = self.connection.marvinRequest(command,
>> response_type=response, method=method)
>>   File
>> "/Users/daan/cloudstack-4.4/cloudstack/tools/marvin/marvin/cloudstackConnection.py",
>> line 266, in marvinRequest
>>     method=method)
>>   File
>> "/Users/daan/cloudstack-4.4/cloudstack/tools/marvin/marvin/cloudstackConnection.py",
>> line 196, in request
>>     raise c
>> requests.exceptions.ConnectionError:
>> HTTPConnectionPool(host='192.168.56.10', port=8096): Max retries
>> exceeded with url:
>> /client/api?account=admin&command=listUsers&response=json (Caused by
>> <class 'socket.error'>: [Errno 61] Connection refused)
>>
>> telnet port 8091 locally on my laptop works and from the devcloud to
>> my laptop as well but the port is not opened on the dev. So it makes
>> sense that the connection is refused. Not that it is opened. I set the
>> 'host' config item to the virtualbox gateway address, 192.168.56.1.
>> That didn't help. I don't see what config I should change.
>>
>> What should I change? Where didn't I look?
>>
>> --
>> Daan
>>



-- 
Daan

Reply via email to