cf-charmers team mailing list archive

[Manuel Garcia <mgarciap@xxxxxxxxx>]

Hi Dustin, 

As we agreed in one of our latest email the target deployment escenario is Local Environment (instead of one single AWS node)
We manage to make this work. However, it only works with Ubuntu as a host OS. We are unable to make it work with Ubuntu as a guest OS within Vagrant with Virtualbox as a virtualisation provider given that it doesn’t support nested virtualisation (guys, correct me if I am wrong)
We haven’t tried VMWare (Workstation or Fusion - Mac OS) yet given that it is paid (Mac OS)

Do you consider that Ubuntu as a host OS for local environment deployment is the only way to go? In this case we won’t be giving the opportunity to non-ubuntu users to try the CF Juju bundle, which I think it is not good.

BTW, in our last weekly meeting Matt offered support on LXC + Warden. If your answer is the same as my suggestion we should contact him right away.

Please let me know: Ubuntu host OS only or not?

Manuel




On Apr 16, 2014, at 9:54 AM, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:

> 
> 
> Forwarded conversation
> Subject: Dealing with Warden-within-LXC issue.
> ------------------------
> 
> From: Alexander Lomov <lomov.as@xxxxxxxxx>
> Date: 14 April 2014 23:42
> To: Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>, Benjamin Saller <benjamin.saller@xxxxxxxxxxxxx>
> Cc: cf-charmers@xxxxxxxxxxxxxxxxxxx
> 
> 
> Hey, all.
> 
> Since we need to implement deployment DEA to local environment and I'm not sure that I see problem clearly, I'd like to start discussion of this topic. 
> 
> 1. First question for me is:
> Is it worth to try to deploy DEA into juju kvm local environment? I mean something like approach described in this article: http://astokes.org/juju-deploy-to-lxc-and-kvm-in-the-local-provider/. Deploying to kvm can solve this issue.
> 
> 2. Strategy to solve LXC/Warden problem:
> We can perform following steps in order to solve this issue:
>         a. create lxc container
>         b. deploy Warden to it 
>         c .try to create Warden container using warden shell
>         d. after that we will change configuration step by step depending on errors we will get. 
> 
> It will require us to change default LXC settings, so we will need to provide user of juju charms with list of changes to LXC settings.
> Is it OK for now to make user change his defaults? 
> What do you think about strategy for solving this task? 
> What are your suggestions on this point?
> 
> 
> Thank you,
> Alex L.
> 
> ----------
> From: Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>
> Date: 15 April 2014 02:04
> To: Alexander Lomov <lomov.as@xxxxxxxxx>
> Cc: Benjamin Saller <benjamin.saller@xxxxxxxxxxxxx>, "cf-charmers@xxxxxxxxxxxxxxxxxxx" <cf-charmers@xxxxxxxxxxxxxxxxxxx>
> 
> 
> 
> 
> 
> On Mon, Apr 14, 2014 at 4:42 PM, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:
> Hey, all.
> 
> Since we need to implement deployment DEA to local environment and I'm not sure that I see problem clearly, I'd like to start discussion of this topic. 
> 
> 1. First question for me is:
> Is it worth to try to deploy DEA into juju kvm local environment? I mean something like approach described in this article: http://astokes.org/juju-deploy-to-lxc-and-kvm-in-the-local-provider/. Deploying to kvm can solve this issue.
> 
> yes, that article describes the technique to use for containers for most things, and kvm just for the dea, that's a good workflow and can be captured into a deployer config as well  (to: kvm:0)
> 
> make sure to install uvtool package for the kvm support.
> 
> 
> 2. Strategy to solve LXC/Warden problem:
> We can perform following steps in order to solve this issue:
>         a. create lxc container
>         b. deploy Warden to it 
>         c .try to create Warden container using warden shell
>         d. after that we will change configuration step by step depending on errors we will get. 
> 
> It will require us to change default LXC settings, so we will need to provide user of juju charms with list of changes to LXC settings.
> Is it OK for now to make user change his defaults? 
> What do you think about strategy for solving this task? 
> What are your suggestions on this point?
> 
> 
> for now go with #1 (it works and can be captured to bundle), when local provider has app armor profiles configurable for lxc we can consider debugging #2.
> 
> cheers,
> 
> Kapil
> 
> ----------
> From: Alexander Lomov <lomov.as@xxxxxxxxx>
> Date: 15 April 2014 05:10
> To: Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>
> Cc: cf-charmers@xxxxxxxxxxxxxxxxxxx
> 
> 
> This makes sense. I guess we will start to work on it today-tomorrow.
> Thank you for answering, Kapil.
> 
> ----------
> From: <prismakov@xxxxxxxxx>
> Date: 15 April 2014 09:50
> To: Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>
> Cc: Alexander Lomov <lomov.as@xxxxxxxxx>, "cf-charmers@xxxxxxxxxxxxxxxxxxx" <cf-charmers@xxxxxxxxxxxxxxxxxxx>
> 
> 
> Guys, FYI
> 
> According to my results:
> 
> $ egrep -c '(vmx|svm)' /proc/cpuinfo
> 0
> 
> $ juju deploy --to kvm:0 --repository=../../ local:trusty/cf-dea dea --debug
> 2014-04-15 06:37:27 INFO juju.cmd supercommand.go:297 running juju-1.18.0-trusty-amd64 [gc]
> 2014-04-15 06:37:27 DEBUG juju api.go:171 trying cached API connection settings
> 2014-04-15 06:37:27 INFO juju api.go:238 connecting to API addresses: [192.168.122.1:17070]
> 2014-04-15 06:37:27 INFO juju apiclient.go:114 state/api: dialing "wss://192.168.122.1:17070/"
> 2014-04-15 06:37:27 INFO juju apiclient.go:124 state/api: connection established
> 2014-04-15 06:37:27 INFO juju.utils http.go:62 hostname SSL verification disabled
> 2014-04-15 06:37:28 INFO juju.cmd cmd.go:113 Added charm "local:trusty/cf-dea-1" to the environment.
> 2014-04-15 06:37:28 ERROR juju.cmd supercommand.go:300 cannot assign unit "dea/0" to machine: cannot add a new machine: machine 0 cannot host kvm containers
> 
> and this https://www.virtualbox.org/ticket/4032
> it is not possible to run kvm inside VirtualBox/Vagrant
> 
> Will try to implement it on my Ubuntu PC.
> 
> 
> -Alexander Prismakov
> 
>> -- 
>> 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
> 
> 
>