cf-charmers team mailing list archive
-
cf-charmers team
-
Mailing list archive
-
Message #00074
Re: AWS Single node deployment fails during installing apt-get packages
Thank you for answering.
Everything I wrote here is performed in AWS environment.
If I remove `lxc:` (nested lxc containers), I can deploy bundle, but I will
have error on `apt-get update` of `apt-get install` because all charms will
be installed simultaneously (everything works fine when I deploy them one
by one). I added nested lxc containers to separate charm installation.
On 15 April 2014 19:42, Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>wrote:
>
>
>
> On Tue, Apr 15, 2014 at 11:58 AM, Alexander Lomov <lomov.as@xxxxxxxxx>wrote:
>
>> Hi, Kapil.
>>
>> I have an issue during deployment of this bundle.yaml
>> https://gist.github.com/allomov/8866696a3c32f28ccafb (I deploy with
>> following command: juju deployer -WvdBc single-node-bundle-example.yaml
>> ).
>>
>
> your doing this in ec2 against the local provider? if so you should remove
> the to lxc:0 or your nesting lxc containers. are you using the libvirt
> bridge in your enviornments.yaml config (to use kvm for dea).
>
>
>
>> Every service has failed on `install` hook, each of them has problems
>> with accessing PPA (you can see logs examples here
>> https://gist.github.com/allomov/7dffecc850a27a722d7b, `juju status`
>> command output is here:
>> https://gist.github.com/allomov/7dffecc850a27a722d7b#file-juju-status-log).
>> There is no running LXC containers on machine 0, command `lxc-ls -f1` gives
>> empty list.
>>
>> This time I have following questions about deployer:
>> 1. What do you think about this issue?
>>
>
> try without nesting lxc containers.
>
>
>> 2. How can I specify constraints for bootstrapped machine in
>> bundle file, environment.yaml or with the command line?
>>
>
> juju bootstrap --constraints="mem=8G"
>
>
> cheers,
>
> Kapil
>
References