Walex | what does 'juju sync-tools' do? Is it related to 'juju upgrade-tools'? | 08:46 |
---|---|---|
Walex | my issue is: I upgraded the Juju packages 1.23.3 to 1.24.5 on the "control" node but the '/var/lib/juju/tools/' directories on the state nodes are not being updated | 08:48 |
luqas | hi, I might be hitting https://bugs.launchpad.net/juju-core/+bug/1417875 on juju-core 1.24.5 | 10:47 |
mup | Bug #1417875: ERROR juju.worker runner.go:219 exited "rsyslog": x509: certificate signed by unknown authority <canonical-bootstack> <logging> <regression> <juju-core:Fix | 10:47 |
mup | Released by wwitzel3> <juju-core 1.21:Fix Released by wwitzel3> <juju-core 1.22:Fix Released by wwitzel3> <https://launchpad.net/bugs/1417875> | 10:47 |
luqas | wwitzel3: I'm trying your manual workaround but I can't find the "good" certificate | 10:48 |
=== scuttle|afk is now known as scuttlemonkey | ||
ssmoCoffee | We are installing Openstack per the single installer guide ubuntu-cloud-installer.readthedocs.org/en/latest/single-installer.guide.html. Bootstrapping Juju fails with an error message about kvm-ok and cpu-checker packages needing to be installed. | 15:49 |
ssmoCoffee | The packages cpu-checker and qemu-kvm are installed on both the host server and the bootstrap container. | 15:50 |
ssmoCoffee | Anyone run into the same issue? | 15:50 |
ssmoCoffee | I reproduce the error attaching the bootstrap container and running juju --debug bootstrap -e local | 15:51 |
ssmoCoffee | ERROR juju.cmd supercommand.go:430 there was an issue examining the environment: failed verification of local provider prerequisites: kvm-ok is not installed. Please install the cpu-checker package. | 15:52 |
firl | anyone able to possibly help me diagnose why my landscape isn’t installing via the openstack-install? I am looking in the JuJu files and I can’t seem to figure out which error to try to research. | 16:11 |
lazyPower | dpb1_: ping | 16:33 |
lazyPower | ssmoCoffee: thats... odd. Which version of ubuntu/openstack installer? | 16:33 |
lazyPower | Walex: Did you get an answer out of band? | 16:34 |
ssmoCoffee | lazyPower: OpenStack Installer v0.99.19 | 16:36 |
lazyPower | firl: i'm pending a response from a landscape charmer, however - if you could send over the juju log from that landscape node we should be able to track down whats happening | 16:38 |
lazyPower | ssmoCoffee: is this on trusty? | 16:39 |
ssmoCoffee | lazyPower: running kvm-ok from the bootstrap container fails | 16:39 |
ssmoCoffee | vivid | 16:39 |
lazyPower | @ddellav - can you check on this? kvm-ok on a bootstrap node in vivid? | 16:39 |
lazyPower | ssmoCoffee: which version of juju? | 16:39 |
firl | lazyPower: sure will do. I tried on 2 different systems, and a VM with embedded. Do you know if I deploy landscape automatically ( not openstack-installer ) if I get the openstack-beta tab still? | 16:39 |
lazyPower | firl: i'm not positive, but i would *think* so | 16:40 |
sparkiegeek | firl: you do :) | 16:40 |
ssmoCoffee | 1.24.5-vivid-amd64 | 16:40 |
lazyPower | perfect, latest stable. thanks ssmoCoffee | 16:40 |
firl | lazyPower: sparkiegeek: so the openstack-installer is just a “nice” wrapper so you don’t have to create your own juju file and environment? | 16:40 |
lazyPower | 1 sec while i poke around and try to get some output. | 16:41 |
sparkiegeek | firl: that and setting up of MAAS | 16:41 |
firl | which can be done post install | 16:41 |
firl | kk | 16:41 |
sparkiegeek | (which is the hard part that the installer automates [some of] for you) | 16:41 |
firl | that makes me feel a little better | 16:41 |
sparkiegeek | so if you're comfortable getting MAAS setup, you can quite easily deploy Landscape using Juju | 16:41 |
firl | lazyPower: http://pastebin.com/U8TeqYAK | 16:41 |
sparkiegeek | https://help.landscape.canonical.com/LDS/JujuDeployment15.01 | 16:41 |
firl | nice, yeah I will do that | 16:42 |
ssmoCoffee | lazyPower: thanks. Should /proc/cpuinfo be empty on the bootstrap contianer? | 16:42 |
lazyPower | ssmoCoffee: not at all | 16:42 |
lazyPower | the /proc/cpuinfo should be filled out always due to procfs | 16:42 |
lazyPower | and thats part of ubuntu core | 16:43 |
firl | sparkiegeek: do you know if the openstack-beta installer has been upgraded to vivid/kilo? | 16:43 |
ssmoCoffee | lazyPower: on the host /proc/cpuinfo is populated and kvm-ok returns that KVM acceleration can be used | 16:44 |
sparkiegeek | firl: there's Work In Progress on trusty/kilo - we don't target the interim releases (vivid, wily ...) | 16:44 |
firl | kk | 16:44 |
firl | I just liked the idea of lxc containers that came with vivid | 16:45 |
sparkiegeek | what do you mean? LXD? | 16:45 |
ssmoCoffee | lazyPower: so the lxc bootstrap container isn't valid | 16:45 |
firl | ya LXD sorry | 16:46 |
firl | https://insights.ubuntu.com/2015/04/22/here-comes-kilo-15-05-containers-will-never-be-the-same-again/ | 16:46 |
sparkiegeek | firl: ah, containers in your OpenStack - right we're excited by that too, but you'll have to wait for 16.04 (next LTS) before we integrate it | 16:47 |
sparkiegeek | (in the autopilot I mean) | 16:47 |
firl | I figured :) | 16:47 |
firl | are the openstack charms also only targetted for lts? | 16:47 |
sparkiegeek | there's some rounding out of nova-compute-lxd that still needs to happen - an LTS is the best place to do that :) | 16:47 |
sparkiegeek | no, the charms will support vivid/kilo | 16:48 |
sparkiegeek | s/will/do/ | 16:48 |
firl | oh really? | 16:48 |
firl | I can deploy via the juju ui and get vivid/kilo right now? | 16:48 |
sparkiegeek | beisner: ^^ do you guys have a bundle somewhere for vivid/kilo? | 16:51 |
beisner | sparkiegeek, firl - while there isn't an official V:K bundle published in the charm store, we do have test bundles which exercise that. it would need to be tailored to you desired topology and machine/service placement, however. | 16:52 |
sparkiegeek | beisner: sure, I expect firl could start with them as a drag/drop into Juju GUI and then tailor from there? | 16:53 |
sparkiegeek | machine view for placement + any other tweaks | 16:53 |
firl | beisner,sparkiegeek: yeah that doesn’t scare me. I ran into an issue last month where I had to commit the ceph config before adding the units because of having to specify all the drives | 16:54 |
firl | I am using a custom deployed openstack bundle on my machines at home | 16:55 |
beisner | sparkiegeek, firl - i'm not as familiar with the gui. i generally tune the yaml in advance, with the desired deployment completely described before even bootstrapping. | 16:55 |
beisner | but, i think you can do some pretty cool things like that in the gui | 16:55 |
firl | beisner: that would work great actually for the deployment I am going for | 16:55 |
sparkiegeek | beisner: sure | 16:55 |
* beisner fetches a ymmv bundle as a starting point for ya | 16:55 | |
firl | :) | 16:57 |
beisner | flir - caveat - these aren't vetted for production, they are the topologies we test with in charm and package development. | 16:59 |
beisner | http://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/baremetal/7-default.yaml | 16:59 |
beisner | juju-deployer --bootstrap -c default.yaml -d vivid-kilo | 17:00 |
beisner | rather | 17:00 |
beisner | juju-deployer --bootstrap -c 7-default.yaml -d trusty-juno | 17:00 |
beisner | ah bugger | 17:00 |
beisner | copy paste fail | 17:00 |
firl | haha | 17:00 |
sparkiegeek | 7-default.yaml, vivid-kilo :) | 17:00 |
beisner | juju-deployer --bootstrap -c 7-default.yaml -d vivid-kilo | 17:00 |
beisner | yagotit | 17:00 |
beisner | lol | 17:00 |
beisner | thankfully, it is friday | 17:00 |
firl | beisner: thanks! I will definitely be trying this later, there is a 40 node maas cluster I am trying to work with currently | 17:01 |
sparkiegeek | firl: so not sure how familiar you are with Juju + bundles, but that one is a v3 bundle format (contains multiple targets) the latest/greatest format that the GUI supports is v4 so you'll have to use juju-deployer to ... deployt it :) | 17:02 |
firl | sparkiegeek: I can still manage it post install via the juju-gui right? | 17:02 |
sparkiegeek | firl: sure | 17:02 |
firl | very cool | 17:02 |
beisner | firl, sparkiegeek - ++caveat: there is a known issues with pxc (percona-cluster) on vivid. you can substitute lp:charms/trusty/mysql | 17:03 |
beisner | bug 1481362 | 17:03 |
mup | Bug #1481362: pxc server 5.6 on Vivid and Wily does not create /var/lib/mysql <amulet> <openstack> <uosci> <percona-xtradb-cluster-5.6 (Ubuntu):New> <percona-cluster (Juju Charms Collection):New> <https://launchpad.net/bugs/1481362> | 17:03 |
beisner | oh wait | 17:04 |
beisner | i already did that via inheritance in the bundle :-) | 17:04 |
beisner | http://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/baremetal/7-default.yaml#L314 | 17:04 |
firl | haha | 17:04 |
beisner | firl, ah cool 40 nodes. happy deploying! | 17:11 |
firl | beisner: haha thanks should be fun | 17:11 |
beisner | o/ thanks sparkiegeek lazyPower | 17:12 |
firl | and whoever set the title of the room scared me, the dates seem to be 17-18 | 17:13 |
sparkiegeek | firl: 10 points for attention to detail | 17:14 |
sparkiegeek | lazyPower: ^^ topic has wrong dates for the summit :) | 17:14 |
firl | haha, well I am about to book travel so I got scared | 17:14 |
firl | beisner: do you have a help article on how to get the new environment ready for juju as well? I had quite a pain prepping my environment, and that is one thing I liked that landscape did | 17:19 |
beisner | firl, you already have maas with machines enlisted and ready to go to work? | 17:20 |
firl | ya | 17:20 |
firl | I meant the vivid/kilo OS prepped for juju deployments | 17:20 |
sparkiegeek | ah, Juju on the inside? | 17:21 |
firl | yeah | 17:21 |
firl | that’s one thing landscape did, deployed tools, and prepped the juju | 17:21 |
beisner | oh to use juju with the openstack provider on the deployed cloud | 17:21 |
firl | ya | 17:21 |
sparkiegeek | https://jujucharms.com/docs/stable/howto-privatecloud is the documented way | 17:22 |
firl | yeah … I am very familar with that page, hope it works out better than last time haha | 17:23 |
=== wendar_ is now known as wendar | ||
beisner | also https://jujucharms.com/docs/devel/config-openstack for the openstack-provider specific environment.yaml options | 17:23 |
firl | thanks, yeah I’ve been through it. I will try again, hopefully with the latest juju it’s a little easier now | 17:24 |
firl | 1.24 caused issues / frustrations | 17:25 |
beisner | firl, as reference, my environments.yaml looks like this, sanitized: http://paste.ubuntu.com/12215832/ | 17:29 |
firl | beisner: thanks, I appreciate it | 17:30 |
sparkiegeek | firl: FWIW in my experience you don't have to put tools in to your OpenStack - what the Autopilot does is "just" put things in Swift to tell Juju where to find the Ubuntu images (e.g. Glance) | 17:31 |
beisner | firl, you're welcome | 17:31 |
sparkiegeek | i.e. just the Image Metadata Contents section of that doc page | 17:33 |
=== scuttlemonkey is now known as scuttle|afk | ||
=== lazyPower changed the topic of #juju to: Welcome to Juju! || Juju Charmer Summit Sept. 17-18 US Washington DC - http://ubunt.eu/KorUSN || Docs: http://juju.ubuntu.com/docs || FAQ: http://goo.gl/MsNu4I || Review Queue: http://review.juju.solutions || Unanswered Questions: http://goo.gl/dNj8CP | ||
pmatulis | does 'enable-os-upgrade' affect just 'apt upgrade' or 'apt full-upgrade'? | 18:41 |
pmatulis | lazyPower, wallyworld, marcoceppi: ? ↑ | 18:41 |
lazyPower | pmatulis: that stops the apt-get update && apt-get upgrade when spinning up a new instance iirc. | 18:42 |
pmatulis | lazyPower: ok, so just upgrade and not full-upgrade | 18:42 |
lazyPower | aiui, correct | 18:42 |
pmatulis | thanks | 18:43 |
=== JoshStrobl is now known as JoshStrobl|Busy | ||
=== scuttle|afk is now known as scuttlemonkey | ||
=== mwenning is now known as mwenning-rr5 | ||
=== natefinch is now known as natefinch-afk | ||
bdx | core, dev: Does anyone here know how to add custom cloud-config to maas provisioning....i.e. curtin_userdata preseeed or custom preseed?? | 22:16 |
=== mup_ is now known as mup |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!