/srv/irclogs.ubuntu.com/2015/08/28/#juju.txt

Walexwhat does 'juju sync-tools' do? Is it related to 'juju upgrade-tools'?08:46
Walexmy 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 updated08:48
luqashi, I might be hitting https://bugs.launchpad.net/juju-core/+bug/1417875 on juju-core 1.24.510:47
mupBug #1417875: ERROR juju.worker runner.go:219 exited "rsyslog": x509: certificate signed by unknown authority <canonical-bootstack> <logging> <regression> <juju-core:Fix10:47
mupReleased 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
luqaswwitzel3: I'm trying your manual workaround but I can't find the "good" certificate10:48
=== scuttle|afk is now known as scuttlemonkey
ssmoCoffeeWe 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
ssmoCoffeeThe packages cpu-checker and qemu-kvm are installed on both the host server and the bootstrap container.15:50
ssmoCoffeeAnyone run into the same issue?15:50
ssmoCoffeeI reproduce the error attaching the bootstrap container and running juju --debug bootstrap -e local15:51
ssmoCoffeeERROR 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
firlanyone 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
lazyPowerdpb1_: ping16:33
lazyPowerssmoCoffee: thats... odd. Which version of ubuntu/openstack installer?16:33
lazyPowerWalex: Did you get an answer out of band?16:34
ssmoCoffeelazyPower: OpenStack Installer v0.99.1916:36
lazyPowerfirl: 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 happening16:38
lazyPowerssmoCoffee: is this on trusty?16:39
ssmoCoffeelazyPower: running kvm-ok from the bootstrap container fails16:39
ssmoCoffeevivid16:39
lazyPower@ddellav - can you check on this? kvm-ok on a bootstrap node in vivid?16:39
lazyPowerssmoCoffee: which version of juju?16:39
firllazyPower: 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
lazyPowerfirl: i'm not positive, but i would *think* so16:40
sparkiegeekfirl: you do :)16:40
ssmoCoffee1.24.5-vivid-amd6416:40
lazyPowerperfect, latest stable. thanks ssmoCoffee16:40
firllazyPower: 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
lazyPower1 sec while i poke around and try to get some output.16:41
sparkiegeekfirl: that and setting up of MAAS16:41
firlwhich can be done post install16:41
firlkk16:41
sparkiegeek(which is the hard part that the installer automates [some of] for you)16:41
firlthat makes me feel a little better16:41
sparkiegeekso if you're comfortable getting MAAS setup, you can quite easily deploy Landscape using Juju16:41
firllazyPower: http://pastebin.com/U8TeqYAK16:41
sparkiegeekhttps://help.landscape.canonical.com/LDS/JujuDeployment15.0116:41
firlnice, yeah I will do that16:42
ssmoCoffeelazyPower: thanks.  Should /proc/cpuinfo be empty on the bootstrap contianer?16:42
lazyPowerssmoCoffee: not at all16:42
lazyPowerthe /proc/cpuinfo should be filled out always due to procfs16:42
lazyPowerand thats part of ubuntu core16:43
firlsparkiegeek: do you know if the openstack-beta installer has been upgraded to vivid/kilo?16:43
ssmoCoffeelazyPower: on the host /proc/cpuinfo is populated and kvm-ok returns that KVM acceleration can be used16:44
sparkiegeekfirl: there's Work In Progress on trusty/kilo - we don't target the interim releases (vivid, wily ...)16:44
firlkk16:44
firlI just liked the idea of lxc containers that came with vivid16:45
sparkiegeekwhat do you mean? LXD?16:45
ssmoCoffeelazyPower: so the lxc bootstrap container isn't valid16:45
firlya LXD sorry16:46
firlhttps://insights.ubuntu.com/2015/04/22/here-comes-kilo-15-05-containers-will-never-be-the-same-again/16:46
sparkiegeekfirl: 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 it16:47
sparkiegeek(in the autopilot I mean)16:47
firlI figured :)16:47
firlare the openstack charms also only targetted for lts?16:47
sparkiegeekthere's some rounding out of nova-compute-lxd that still needs to happen - an LTS is the best place to do that :)16:47
sparkiegeekno, the charms will support vivid/kilo16:48
sparkiegeeks/will/do/16:48
firloh really?16:48
firlI can deploy via the juju ui and get vivid/kilo right now?16:48
sparkiegeekbeisner: ^^ do you guys have a bundle somewhere for vivid/kilo?16:51
beisnersparkiegeek, 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
sparkiegeekbeisner: sure, I expect firl could start with them as a drag/drop into Juju GUI and then tailor from there?16:53
sparkiegeekmachine view for placement + any other tweaks16:53
firlbeisner,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 drives16:54
firlI am using a custom deployed openstack bundle on my machines at home16:55
beisnersparkiegeek, 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
beisnerbut, i think you can do some pretty cool things like that in the gui16:55
firlbeisner: that would work great actually for the deployment I am going for16:55
sparkiegeekbeisner: sure16:55
* beisner fetches a ymmv bundle as a starting point for ya16:55
firl:)16:57
beisnerflir - caveat - these aren't vetted for production, they are the topologies we test with in charm and package development.16:59
beisnerhttp://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/baremetal/7-default.yaml16:59
beisnerjuju-deployer --bootstrap -c default.yaml -d vivid-kilo17:00
beisnerrather17:00
beisnerjuju-deployer --bootstrap -c 7-default.yaml -d trusty-juno17:00
beisnerah bugger17:00
beisnercopy paste fail17:00
firlhaha17:00
sparkiegeek7-default.yaml, vivid-kilo :)17:00
beisnerjuju-deployer --bootstrap -c 7-default.yaml -d vivid-kilo17:00
beisneryagotit17:00
beisnerlol17:00
beisnerthankfully, it is friday17:00
firlbeisner: thanks! I will definitely be trying this later, there is a 40 node maas cluster I am trying to work with currently17:01
sparkiegeekfirl: 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
firlsparkiegeek: I can still manage it post install via the juju-gui right?17:02
sparkiegeekfirl: sure17:02
firlvery cool17:02
beisnerfirl, sparkiegeek - ++caveat:  there is a known issues with pxc (percona-cluster) on vivid.   you can substitute lp:charms/trusty/mysql17:03
beisnerbug 148136217:03
mupBug #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
beisneroh wait17:04
beisneri already did that via inheritance in the bundle :-)17:04
beisnerhttp://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/baremetal/7-default.yaml#L31417:04
firlhaha17:04
beisnerfirl, ah cool 40 nodes.  happy deploying!17:11
firlbeisner: haha thanks should be fun17:11
beisnero/ thanks sparkiegeek lazyPower17:12
firland whoever set the title of the room scared me, the dates seem to be 17-1817:13
sparkiegeekfirl: 10 points for attention to detail17:14
sparkiegeeklazyPower: ^^ topic has wrong dates for the summit :)17:14
firlhaha, well I am about to book travel so I got scared17:14
firlbeisner: 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 did17:19
beisnerfirl, you already have maas with machines enlisted and ready to go to work?17:20
firlya17:20
firlI meant the vivid/kilo OS prepped for juju deployments17:20
sparkiegeekah, Juju on the inside?17:21
firlyeah17:21
firlthat’s one thing landscape did, deployed tools, and prepped the juju17:21
beisneroh to use juju with the openstack provider on the deployed cloud17:21
firlya17:21
sparkiegeekhttps://jujucharms.com/docs/stable/howto-privatecloud is the documented way17:22
firlyeah … I am very familar with that page, hope it works out better than last time haha17:23
=== wendar_ is now known as wendar
beisneralso https://jujucharms.com/docs/devel/config-openstack  for the openstack-provider specific environment.yaml options17:23
firlthanks, yeah I’ve been through it. I will try again, hopefully with the latest juju it’s a little easier now17:24
firl1.24 caused issues / frustrations17:25
beisnerfirl, as reference, my environments.yaml looks like this, sanitized:  http://paste.ubuntu.com/12215832/17:29
firlbeisner: thanks, I appreciate it17:30
sparkiegeekfirl: 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
beisnerfirl, you're welcome17:31
sparkiegeeki.e. just the Image Metadata Contents section of that doc page17: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
pmatulisdoes 'enable-os-upgrade' affect just 'apt upgrade' or 'apt full-upgrade'?18:41
pmatulislazyPower, wallyworld, marcoceppi: ? ↑18:41
lazyPowerpmatulis: that stops the apt-get update && apt-get upgrade when spinning up a new instance iirc.18:42
pmatulislazyPower: ok, so just upgrade and not full-upgrade18:42
lazyPoweraiui, correct18:42
pmatulisthanks18: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
bdxcore, 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!