cf-charmers team mailing list archive

[Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>]

blocker to what? a dev setup?

do we have a deployer file/bundle that can deploy cloud foundry to multiple
machines? my understanding is yes.

i won't be able to help this week.

-k



On Wed, Apr 9, 2014 at 8:36 AM, Manuel Garcia <mgarciap@xxxxxxxxx> wrote:

> Is this issue 100% blocker?
>
>
> On Apr 9, 2014, at 9:27 AM, prismakov@xxxxxxxxx wrote:
>
> Hi Kapil,
>
> Results of trying to use KVM for DEA
>
> 1. From vagrant:
> vagrant@vagrant-ubuntu-trusty-64:~/host/trusty/cf-cloud-controller$ juju
> add-machine kvm:0 --debug
> 2014-04-09 12:20:33 INFO juju.cmd supercommand.go:297 running
> juju-1.18.0-trusty-amd64 [gc]
> 2014-04-09 12:20:33 DEBUG juju api.go:171 trying cached API connection
> settings
> 2014-04-09 12:20:33 INFO juju api.go:238 connecting to API addresses: [
> 192.168.122.1:17070]
> 2014-04-09 12:20:33 INFO juju apiclient.go:114 state/api: dialing "
> wss://192.168.122.1:17070/"
> 2014-04-09 12:20:33 INFO juju apiclient.go:124 state/api: connection
> established
> 2014-04-09 12:20:33 ERROR juju.cmd supercommand.go:300 cannot add a new
> machine: machine 0 cannot host kvm containers
>
> 2. From trusty on bare metal:
>
> environment: local
> machines:
>   "1":
>     agent-state-info: '(error: template container "juju-trusty-template" did not stop)'
>     instance-id: pending
>     series: trusty
> services:
>   cc:
>     charm: local:trusty/cf-cloud-controller-3
>     exposed: false
>     units:
>       cc/0:
>         agent-state: pending
>         machine: "1"
>
> in both cases used trusty with all updates, juju 1.18, kvm 1.7.91
>
> Comments, ideas?
>
> -Alex Prismakov
>
>
> On Apr 8, 2014, at 17:13, Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>
> wrote:
>
> with juju's builtin local provider (running 1.18) if you have btrfs @
> /var/lib/lxc and install squid-deb-proxy on the host, and run juju set-env
> apt-http-proxy="http://10.0.3.1:8000";  you should be able to use the
> local provider with significant speed improvements. (clone for containers
> package caches, you also need to modify the squid deb proxy conf to allow
> for ppa access), but that won't include nested containers, you can however
> use add-machine kvm:0 to get a kvm machine in local provider for dea agents
> that will support warden containers. you'll need to configure the
> 'network-bridge' option in environments.yaml to point to virbr0 so lxc and
> kvm come up on the same network.
>
>
> I put together an ansible script on my separate workflow with manual
> provider + lxc which does allow nesting but its not polished, and i don't
> think i can recommend it.
> https://github.com/kapilt/juju-lxc/blob/master/ec2.yml
>
> having issues logging into pivotal tracker will resolve later.
>
> http://www.pivotaltracker.com/story/show/68893338
>
> cheers,
>
> Kapil
>
> --
> Mailing list: https://launchpad.net/~cf-charmers
> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~cf-charmers
> More help   : https://help.launchpad.net/ListHelp
>
>
> --
> Mailing list: https://launchpad.net/~cf-charmers
> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~cf-charmers
> More help   : https://help.launchpad.net/ListHelp
>
>
>