Juju chef cookbook

[Egor Medvedev]

Hello again.

>> For clarity - when you say generate manual configuration - is this going to be a manual provider environment?

Yes, I mean manual provider environment at this point.

>>  Where does the bootstrap server live? is this going to be a separate service defined in your infrastructure, controlled by chef?

In described use case I speak about VPS in DO, where chef bootstrapped and we run chef-solo with data bags support.
Juju will be installed along with chef and will take control over lxc-containers. Right now I'm thinking of local containers only.

In short, I'm trying to control my server with chef (configuration, software), and LXC-containers with juju.

I should admit, this case may look strange. But I like juju because of dynamic service manipulation. I can manage containers and it's data without additional chef instructions.

Now I'm watching your post and video. Nice work.

Thank you. 

--
Best Regards,
Egor


On Wednesday 17 December 2014 at 20:07, Charles Butler wrote:

> A few questions:
> 
> 
> 
> 
> 
> 
> When it comes to deploying the services - what were your thoughts there? Are these going to be data-attributes to the LWRP where you do something like:
> 
> juju_deploy "mediawiki mysql haproxy".join(",")
> 
> - which satisfies the deployment - yet relations would need some more finesse - as relations as charms mature change, evolve, and can sometimes confuse juju when you aren't implicit.
> 
> juju_relate("mediawiki", "mysql") - would cause a failure as it needs the scoped :db relation since 2 relations share the same interface but yield different configuration options.
> 
> 
> But it sounds like you'e done your research and you're on the right track.
> 
> and as promised: https://www.youtube.com/watch?v=bCvl-TsxVXA 
> 
> 
> 
> 
> On Wed, Dec 17, 2014 at 10:13 AM, Egor Medvedev <methodx at aylium.net (mailto:methodx at aylium.net)> wrote:
> > By the way, here is my first algorithm:
> > 
> > 1. Install juju on server
> > 2. Provide LXC-support
> > 3. Generate manual configuration
> > 4. Create at least one container for juju services
> > 5. Then create n+1 machines, described in data bag
> > 6. Add all of them to environment and make juju-deploy
> > 
> > --
> > Best Regards,
> > Egor
> > 
> > 
> > On Wednesday 17 December 2014 at 11:26, Egor Medvedev wrote:
> > 
> > > Hello, Charles.
> > > 
> > > Thanks for your response.
> > > I will wait for your blog post.
> > > 
> > > I'm going to play with chef and juju, and maybe it will give some interesting results.
> > > 
> > > Good luck to you! 
> > > 
> > > --
> > > Best Regards,
> > > Egor
> > > 
> > > 
> > > On Wednesday 17 December 2014 at 00:41, Charles Butler wrote:
> > > 
> > > > Egor,
> > > > 
> > > > With regards to Juju being a LWRP in the chef ecosystem, no cookbooks have been made thus far that expose juju. We've done some work on the opposite end of the spectrum orchestrating chef with Juju. However your use case certainly warrants additional exploration. As an already established Chef workshop you can build upon your hosts leveraging Juju - but you'll be moving into more experimental territory. Additionally to just fetching juju you will need to do some tweaking and tuning to get reach-ability into your LXC containers from outside the host. I'm actively working on a blog post about this very thing.
> > > > 
> > > > I'll make sure i follow up on the list when its completed. 
> > > > 
> > > > All the best,
> > > > 
> > > > Charles
> > > > 
> > > > On Mon, Dec 15, 2014 at 2:54 PM, Egor Medvedev <methodx at aylium.net (mailto:methodx at aylium.net)> wrote:
> > > > > Hello!
> > > > > 
> > > > > I was looking for chef cookbook, which can operate with juju using HWRP or LWRP.
> > > > > Maybe someone have it? Can't find anything on Github or at chef.io (http://chef.io).
> > > > > 
> > > > > Anyway, I want to deploy my server applications with chef, and some web applications with juju in LXC. So, I decided to write a cookbook that will install juju and use it with chef resources. So I can tell it what charms to install and expose.
> > > > > 
> > > > > What do you think about this use case? Is it acceptable?
> > > > > 
> > > > > Thanks! 
> > > > > 
> > > > > --
> > > > > Best Regards,
> > > > > Egor
> > > > > 
> > > > > http://aylium.net 
> > > > > --
> > > > > Juju mailing list
> > > > > Juju at lists.ubuntu.com (mailto:Juju at lists.ubuntu.com)
> > > > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
> > > > > 
> > > > 
> > > > 
> > > > -- 
> > > > All the best,
> > > > 
> > > > Charles Butler <charles.butler at canonical.com (mailto:charles.butler at canonical.com)> - Juju Charmer
> > > > Come see the future of datacenter orchestration: http://jujucharms.com
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > 
> 
> 
> -- 
> All the best,
> 
> Charles Butler <charles.butler at canonical.com (mailto:charles.butler at canonical.com)> - Juju Charmer
> Come see the future of datacenter orchestration: http://jujucharms.com
> 
> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20141218/def07e4a/attachment.html>