| vibol | Hello, Why do Juju doc recommend to install Juju vai ppa. Can i install both juju and maas without ppa ? | 17:27 |
|---|---|---|
| pmatulis | vibol, b/c the better juju is in the PPA | 17:29 |
| pmatulis | which will soon be in the regular archives | 17:29 |
| vibol | Is ppa perform good after a major upgrade example from lts to next lts ? | 17:30 |
| pmatulis | vibol, what ubuntu version are you currently running? | 17:31 |
| vibol | I'm running 14.04 | 17:32 |
| pmatulis | and when do you intend on upgrading to 16.04? | 17:33 |
| vibol | I'm on a testing purpose.. | 17:34 |
| vibol | And... i'm notice that. Upgrading a whole infrastrure is not a good idea | 17:34 |
| pmatulis | vibol, then i would recommend using 16.04 | 17:34 |
| vibol | i trying to understand one by one about upgrading a major version with a work software juju, maas, landscape also openstack | 17:35 |
| vibol | i'm just to come here for some recommendation | 17:35 |
| pmatulis | recommendation is to use 16.04 from the start and avoid upgrading | 17:37 |
| vibol | so what happen when the current version has reach EOL ? | 17:43 |
| vibol | destroy the whole environment ? | 17:43 |
| === vila is now known as wasnt-me | ||
| === wasnt-me is now known as vila | ||
| pmatulis | upgrade it, but why not start with the latest LTS to avoid an upgrade as long as possible? | 18:57 |
| bdx | stokachu: ping | 19:56 |
| twitch | Question watching an older video on juju, https://www.youtube.com/watch?v=9h5hgfnZcBQ in the current state when a deploy is run against a local lxc provider is it deployed as a container or an instance? | 21:03 |
| zeestrat | twitch: If by current state, you mean today, then the default local provider in Juju 2.0 is lxd (which is like lxc 2.0 just with some nicer wrapping) so deploying with that would get you lxd containers | 21:22 |
| twitch | And on amazon prime? | 21:23 |
| twitch | aws sorry | 21:23 |
| zeestrat | On AWS you would spin up instances. Note, if you want, you can actually you can deploy lxd containers on those AWS instances as well. | 21:29 |
| zeestrat | See https://jujucharms.com/docs/stable/clouds for some more info on the different clouds supported by Juju. | 21:30 |
| twitch | awesome ty | 21:31 |
| zeestrat | No worries. I recommend checking out https://jujucharms.com/docs/stable/getting-started which starts you out with the local lxd provider/cloud. | 21:34 |
| zeestrat | The cool things is when you get the feel for how to deploy locally with juju, you can basically just switch to the AWS cloud in juju, bootstrap a new controller there, and deploy the exact same thing in the cloud. | 21:34 |
| twitch | will the container tech always be focused on lxd containers or is work being done on other container software like docker? | 21:38 |
| zeestrat | I'm not affiliated with juju so take it with a grain of salt, but I think the main focus for local providers/clouds is on lxd containers at the moment. However one of the flagship juju charms is for deploying Kubernetes (https://jujucharms.com/canonical-kubernetes/) and I know there are people who are using docker containers in juju charms. | 21:44 |
| zeestrat | I suggest checking back in here next week and/or ask the mailing list (https://lists.ubuntu.com/mailman/listinfo/juju) if you have some more questions regarding docker and juju. | 21:46 |
| zeestrat | I'm off so good luck! | 21:47 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!