canonical-ci-engineering team mailing list archive

[Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>]

forgot one bit, set apt-http-proxy: 10.0.3.1  in environments.yaml for the
env, there's a squid deb proxy on the host. if your pulling from ppas
you'll need to tweak the proxy conf to allow ppa.launchpad.net access.




On Fri, Apr 4, 2014 at 11:04 PM, Kapil Thangavelu <
kapil.thangavelu@xxxxxxxxxxxxx> wrote:

> I'm super busy and traveling till next friday. Quite alot of this is
> personal setup and works for me, its not productized yet for end users..
> but i've tried to automate the bulk in hopes that it will help you guys get
> started. I've dropped an ansible ec2.yaml playbook file into jlxc tools
> that automates 90% of the setup.
>
> grab a checkout of https://github.com/kapilt/juju-lxc
>
> edit ec2.yml  tweak instance_type, region, key, and trusty_image to taste.
> you must tweak session_id if sharing accounts or destroying server... its
> there for idempotent requests on ec2 server creation.
>
> ANSIBLE_HOST_KEY_CHECKING=False ansible-playbook -v ec2.yml
>
> after that  on the instance (use ipaddress from ansible output)
>
> lxc-clone -B btrfs precise-template myenv-boot
> sudo lxc-start -d -n myenv-boot
> sudo lxc-ls --fancy --running | grep myenv-boot
>
> grab ip address
>
> construct environments.yaml
>
>   environments:
>      myenv:
>         type: manual
>         bootstrap-user: ubuntu
>         bootstrap-host: $ip_address
>
> juju bootstrap -v --debug
>
> add 5 trusty containers
>
> jlxc-add -n 5 -b trusty-template --series=trusty -e myenv
>
> add 5 precise containers (precise is series default atm)
>
> jlxc-add -n 5 -b precise-template -e myenv
>
> jlxc-destroy -e myenv  will wipe all containers but the bootstrap from the
> environment..
>
> For ftesting charms or setting up dev environments. i typically do a
> reset.sh script with
>
> jlxc-destroy -e myenv
> juju-deployer -TW  # to clear out extraneous services with no untis
> jlxc-add -n 8  -e myenv -b precise-template
>
>
> and then either run juju-deployer again with a workload or use env as
> desired.
>
> hth,
>
> kapil
>
>
>
>
>
> On Fri, Apr 4, 2014 at 9:48 AM, Paul Larson <paul.larson@xxxxxxxxxxxxx>wrote:
>
>> Kapil said he would try to get us a walkthrough of what he did. It was
>> really hard to follow along on the hangout, and we pointed that out.
>> He agreed that it would be much easier to follow if he showed us a
>> scripted version of it.
>>
>> Kapil, do you have something like this you can share with us? I think
>> Vincent was able to capture a lot of the highlights, but wanted to see
>> if you had something that you work from.
>>
>> On Fri, Apr 4, 2014 at 7:54 AM, Vincent Ladeuil <vila+ci@xxxxxxxxxxxxx>
>> wrote:
>> >>>>>> Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx> writes:
>> >
>> >     > Did anyone take notes in the juju-lxc presentation by Kapil? Can
>> you
>> >     > add them here:
>> >
>> >     >
>> https://wiki.canonical.com/UbuntuEngineering/CI?action=diff&rev1=89&rev2=90
>> >
>> > Done with what I had, caveat: not pretty.
>> >
>> >      Vincent
>> >
>> > --
>> > Mailing list: https://launchpad.net/~canonical-ci-engineering
>> > Post to     : canonical-ci-engineering@xxxxxxxxxxxxxxxxxxx
>> > Unsubscribe : https://launchpad.net/~canonical-ci-engineering
>> > More help   : https://help.launchpad.net/ListHelp
>>
>
>