← Back to team overview

cf-charmers team mailing list archive

Re: Deploing CF inside one machine

 

On Tue, Apr 15, 2014 at 12:47 PM, Alex Prismakov <prismakov@xxxxxxxxx>wrote:

> Hi gays,
>
> I want to share my results here:
>
> 1. VirtualBox doesnt support nested virtualization (
> https://www.virtualbox.org/ticket/4032)
> 2. Solution with mixing LXC and KVM works well on regular (hardware)
> machine. At least it works well without using deployer.
> 3. Deployer also works for me but with couple of issues:
>   - when I use -B(bootstrap) switch I get
>
> $ juju deployer -WvdBc bundle_v001_local.yaml
> 2014-04-15 14:43:04 [DEBUG] deployer.cli: Using runtime GoEnvironment on
> local
> 2014-04-15 14:43:04 [INFO] deployer.cli: Using deployment cloudfoundry-base
> 2014-04-15 14:43:04 [INFO] deployer.cli: Starting deployment of
> cloudfoundry-base
> 2014-04-15 14:43:04 [INFO] deployer.env: bootstraping, this might take a
> while...
> Traceback (most recent call last):
>   File "/usr/bin/juju-deployer", line 9, in <module>
>     load_entry_point('juju-deployer==0.3.6', 'console_scripts',
> 'juju-deployer')()
>   File "/usr/lib/python2.7/dist-packages/deployer/cli.py", line 127, in
> main
>     run()
>   File "/usr/lib/python2.7/dist-packages/deployer/cli.py", line 225, in run
>     importer.Importer(env, deployment, options).run()
>   File "/usr/lib/python2.7/dist-packages/deployer/action/importer.py",
> line 181, in run
>     self.env.bootstrap()
>   File "/usr/lib/python2.7/dist-packages/deployer/env/base.py", line 74,
> in bootstrap
>     self.get_cli_status()
>   File "/usr/lib/python2.7/dist-packages/deployer/env/go.py", line 100, in
> get_cli_status
>     status["machines"]["0"]["dns-name"])
> KeyError: 'dns-name'
> ERROR exit status 1
>


This bootstrap feature was community contributed, i believe ben a patch for
that that he hasn't pushed/submitted for merge.



> actually I see that environment bootstraped so next time I just run
> without 'B' switch:
> all goes normal but at the end:
>
> 2014-04-15 19:06:45 [INFO] deployer.import: Adding relations...
> 2014-04-15 19:06:45 [INFO] deployer.import:  Adding relation nats <-> cc
> 2014-04-15 19:06:45 [INFO] deployer.import:  Adding relation nats <-> uaa
> 2014-04-15 19:06:45 [INFO] deployer.import:  Adding relation nats <->
> router
> 2014-04-15 19:06:45 [INFO] deployer.import:  Adding relation nats <-> dea
> 2014-04-15 19:06:45 [INFO] deployer.import:  Adding relation router <-> cc
> 2014-04-15 19:06:45 [INFO] deployer.import:  Adding relation router <-> uaa
> 2014-04-15 19:06:45 [INFO] deployer.import:  Adding relation router <-> dea
> 2014-04-15 19:06:45 [DEBUG] deployer.import: Waiting for relation
> convergence 60s
> 2014-04-15 19:07:45 [ERROR] deployer.import: Reached deployment timeout..
> exiting
> 2014-04-15 19:07:45 [INFO] deployer.cli: Deployment stopped. run time:
> 6210.79
> ERROR exit status 1
>
>
you can increase the timeout, this is still quite a long time for a deploy,
which service takes such a long time to come up?



> but all relations set and I able to deploy an app!
>

awesome.

-k


> checked on 2 machines (on home and office's PC)
>
> used bundle file -
> http://bazaar.launchpad.net/~cf-charmers/charms/bundles/cloudfoundry/bundle/revision/29/bundle_v001_local.yaml
>
> -Alex Prismakov
>

Follow ups

References