[00:04] <inkata> .
[00:06] <inkata> Hi all, I'm learning uvtool + ubuntu cloud images for my KVM machine. When creating a new guest with uvt-kvm create it ends up running two disks. Why is that?
[00:06] <inkata> thanks
[00:07] <tsimonq2> inkata: #ubuntu is probably the best place for this. I'd help you, but unfortunately, I'm on a machine with no VM capabilities at the moment, so I can't confirm or deny or test.
[00:07] <tsimonq2> (and I don't know the tools well enough)
[00:07] <sarnold> tsimonq2: I think the docs send uvtool users to this channel :)
[00:07] <tsimonq2> sarnold: oh?
[00:07] <sarnold> tsimonq2: yeah, see the bottom of https://help.ubuntu.com/lts/serverguide/cloud-images-and-uvtool.html
[00:08] <tsimonq2> then nevermind, stay around and wait for someone to answer, sorry about that inkata :)
[00:10] <sarnold> inkata: a quick read through the source gives me the impression that it's probably creating a cloud-init datasource
[00:10] <sarnold> inkata: you can find more information on cloud-init here https://cloudinit.readthedocs.io/en/latest/ though I've found it severely underdocumented how you actually -use- cloud-init :/
[00:10] <inkata> tsimonq2: thanks man, as sarnold mentions, the docs point here.
[00:11] <inkata> sarnold: roger
[00:21] <inkata> sarnold: can't make heads or tails of cloud-init :-/
[00:21] <sarnold> inkata: you either? :( sigh. it looks so useful but I can't ever find anything that says "put this file <here> and run <command> there in order to use it with libvirt" or something similar...
[00:22] <inkata> sarnold: exactly lol
[00:23] <inkata> maybe it's a partition with a magic file on it or something
[00:23] <sarnold> inkata: is it still visible in the resulting VMs? that might explain an awful lot about how to use the thing :)
[00:25] <inkata> sarnold: it's a disk, it shows on dmesg but it's not mounted. let me reboot the guest to try and see what's in it and report back
[00:25] <rbasak> inkata: Ubuntu cloud images are undifferentiated. The second disk is a cloud-init datasource which differentiates it (eg. has your ssh public key on it).
[00:26] <rbasak> It tells your instance what to do when it boots, essentially.
[00:28] <rbasak> See http://cloudinit.readthedocs.io/en/latest/topics/examples.html for details of what it can do. With uvtool, you can pass this in using --user-data, to save having to mess with creating the datasource manually.
[00:29] <inkata> rbasak: do I pass a local file to uvtool? a plain file ?
[00:32] <rbasak> inkata: you pass anything cloud-init will accept as userdata. That can be a shell script with an appropriate shebang, I believe, but usually it's in cloud-init's cloud-config format, which is yaml and covers pretty much anything you might need in a declarative format. Documentation at http://cloudinit.readthedocs.io/en/latest/topics/format.html
[00:32] <rbasak> inkata: re-reading your question, yes - a file.
[00:33] <inkata> rbasak: /me gasps in awe that's quite useful.. let me try with a simple touch /tmp/newfile
[00:34] <rbasak> smoser: IMHO, http://cloudinit.readthedocs.io/en/latest/topics/examples.html should have every example start with #cloud-config. Otherwise people in a hurry will miss that, which I think will cause mostly silent failure, right?
[00:35] <sarnold> omg yes, if #cloud-config is required for some reason that absolutely should be in every single example :)
[00:35] <rbasak> inkata: note that if using uvtool, if you specify --user-data then uvtool can no longer inject your ssh public key, since it uses cloud-init userdata to do that and you're overriding it.
[00:35] <smoser> rbasak, definitely true.
[00:36] <rbasak> inkata: so in that case, you should write to ~ubuntu/.ssh/authorized_keys yourself, or make alternative arrangements.
[00:36] <rbasak> inkata: if you use cloud-config then it's easier since there's a yaml key you can use to provide your ssh public key.
[00:40] <inkata> rbasak: cloud-init is a regular package I should install in my KVm host or in my regular desktop?
[00:40] <inkata> cloud-config* sorry
[00:43] <rbasak> inkata: cloud-config is a format that is defined by cloud-init that it accepts - not a package.
[00:44] <rbasak> The format is a YAML schema, essentially. It is straightforward to write and modify by example.
[00:44] <inkata> rbasak: roger that
[00:45] <rbasak> inkata: look at http://cloudinit.readthedocs.io/en/latest/topics/examples.html, but stick "#cloud-config" at the top of any file you create so cloud-init knows it's getting cloud-config data.
[01:51] <inkata> rbasak: Re: #cloud-config file, how can I get the name of the new guest to be used in my file? it used to say the new_guest_name in the login screen, now it only says ubuntu
[01:55] <rbasak> inkata: set the hostname and set manage_etc_hosts to localhost.
[01:57] <inkata> rbasak: but how to set the hostname dynamically in the cloud file? I need to catch uvt-kvm create THISHOSTNAME
[01:59] <rbasak> inkata: you'll need to wrap uvt-kvm and create a temporary --user-data file.
[01:59] <rbasak> inkata: if you override with --user-data, uvt-kvm cannot then do it for you.
[02:00] <inkata> rbasak: got it. This is getting to be more cumbersome than getting a fat server ISO and installing it from scratch lol
[02:01] <rbasak> Really? :)
[02:02] <inkata> kinda yeah :-P
[02:02] <sarnold> man the only thing less documented than how to use cloud-init is how to use preseeding :)
[02:04] <inkata> rbasak: I'm setting the hostname to blahblah and it works!, but ssh keys are borked.. working on it..
[02:09] <rbasak> Great!
[02:09]  * rbasak goes to bed now
[02:11] <inkata> rbasak: thanks man!
[02:16] <inkata> rbasak: sarnold it's aliiiiive!!! but needs mooar scripting than I anticipated or need right now. Thanks for your help guys, sleep tight!
[02:16] <sarnold> inkata: great! :D
[02:17]  * inkata goes home
[04:26] <lucas_ai> I'm at Stanford making a drone startup with AI (deep learning + SLAM) and I'm looking for people who're great at linux and systems to help out and learn AI. Is anyone in the Bay Area and interested?
[09:12] <wrksx> Wanted to upgrade from 14 LTS to 16 LTS, and got an issue with my /boot/grub/menu.slt
[09:13] <wrksx> it says the file changed, and the package maintainer's got a new version for this file.
[09:13] <wrksx> here is my old menu.lst http://paste.debian.net/hidden/b02dfb5f/
[09:14] <wrksx> This is a server I'm only able to access through ssh so I'm not sure I'm goin to use that grub menu at all.
[09:24] <rbasak> wrksx: this could be bug 1485685 if you're using a cloud image?
[09:28] <wrksx> rbasak, ubottu, how can I confirm I'm using a cloud image?
[09:31] <rbasak> wrksx: how do you install the system?
[09:32] <wrksx> rbasak, it was installed by my hoster. I just ran an upgrade
[09:33] <wrksx> I suppose that mean it uses some kind of image anyway (since the hoster has to deploy a lot). But is that what you refer to as a cloud image I dunno
[09:33] <rbasak> If you have an /etc/cloud/build.info then your system is based on a cloud image
[09:33] <rbasak> If your hoster installed the system, perhaps they modified menu.lst.
[09:34] <wrksx> rbasak, I have no /etc/cloud
[09:35] <wrksx> rbasak, is that /boot/grub/menu.lst used to boot the server?
[09:35] <rbasak> Then it seems likely to me that your host modified menu.lst.
[09:35] <rbasak> Yes, depending on your host environment.
[09:37] <wrksx> rbasak, two major diff between the two files, the hoster's one is referencing /initrd.img and /vmlinuz symlinks, and the package maintainer version is directly referncing inside /boot.
[09:38] <wrksx> the other diff is that the hoster hass a biosdevname=0 on the kernel lines, which looks like important even if I don't know the purpose of it
[09:44] <Andrew__> Looking to chat to someone about conjure-up and if it supports spaces defined in MAAS?
[09:49] <rbasak> stokachu: ^
[09:50] <wrksx> https://wiki.ubuntu.com/Booting says that "Grub will find the /boot/grub/menu.lst which configures its interactive menu". I don't understand why this should be used to boot a server since no one is there to see the menu at reboot time
[09:52] <rbasak> We don't use that any more I don't think.
[09:53] <rbasak> It's still commonly used though when a host wants to boot a kernel directly rather than by emulating a regular system boot.
[09:53] <wrksx> rbasak, do you know a way to check what is used at boot time?
[09:54] <rbasak> No, the guest can be fooled. Ask your host.
[09:54] <wrksx> rbasak, oh damn. I was afraid of hearing that
[09:54] <rbasak> You could eliminate some methods by confirming they're not configured on the guest I suppose. But I don't really have the time to go through that, sorry.
[09:55] <rbasak> It's not clear to me if your menu.lst modifications were made by an Ubuntu installer, by an Ubuntu bug or by your host.
[09:55] <wrksx> rbasak, that's alright thanks for the help, always appraciate it
[09:55] <rbasak> Look into net.ifnames=0 - you might need this after upgrade to stop your NIC names changing.
[09:56] <rbasak> Also the grub-legacy-ec2 package, which your host may (or may not) use to boot your kernel directly.
[10:21] <stokachu> Andrew__: it uses juju underneath but there is no way to tell conjure-up to use a certain space
[10:24] <Andrew__> Ok thanks - was trying to see if I could do all the network definitions in MAAS instead of doing in advanced configuration
[10:25] <Andrew__> I have raised a issue around not being able to get into advanced configuration for cinder
[10:25] <Andrew__> Is there a way to target nodes in MAAS from conjure up?
[10:26] <stokachu> Andrew__: re: cinder that should be fixed if you want to test ppa:conjure-up/daily-git
[10:26] <stokachu> Andrew__: there isn't a way to target specific maas nodes via conjure-up unfortunately
[10:27] <stokachu> Andrew__: the best you can do is set which node to bootstrap with using --bootstrap-to
[10:28] <Andrew__> ok
[10:39] <wrksx> Okay so I fucked up my system trying to go from LTS 14 to 16
[10:40] <wrksx> I was a bit careless because I thought there was no really important stuff on that box.
[10:40] <wrksx> Now it's gone I feel I underestimated the cost of that loss.
[10:41] <wrksx> System seemed not to boot
[10:41] <wrksx> Using an option from the hoster I've been able to restart in 'rescue' mode
[10:44] <Andrew__> stokachu - all working in daily - thanks
[10:46] <Andrew__> stokachu - I am going through and setting all the networks in conjure-up advanced configuration is there any way to share common network configurations?
[12:36] <diddledan> these docs seem to reference an installer (openstack-installer) that doesn't exist on 16.04: https://help.ubuntu.com/lts/clouddocs/installer/
[12:37] <diddledan> they're linked-to at the bottom of https://www.ubuntu.com/cloud/openstack
[12:47] <stokachu> diddledan: we need to fix that, openstack-installer is 14.04 only, http://conjure-up.io is for Xenial and above
[12:49] <diddledan> looks like these different docs (again linked on the openstack page) reference outdated juju commands https://help.ubuntu.com/lts/clouddocs/en/Installing-Juju.html
[12:50] <diddledan> specifically `juju generate-config` isn't available on 16.04 from what I can discern
[13:08] <ws2k3> is it save to delete the content of /var/cache/apt/archies ?
[14:01] <Freze> I've got a execuatable call it `hello`   doing ls  it says  `hello -> user/bin/hello*` , however I can't run it from the terminal by typing `hello`
[14:02] <Freze> oh wait
[14:02] <Freze> are links relative to the folder you  `ls`
[14:03] <RoyK> yes
[14:04] <RoyK> anyway - the current directory isn't normally in PATH, and shouldn't be
[14:07] <robert17> Hi.  I'm trying to setup an existing Ubuntu-Server 14.04.5 LTS instance with an attached RAID-1 array.  I do this all the time on all sorts of other boxes with no issue.  Here, though, try as I might, I can create the array, manually assemble is from shell -- all looks good --
[14:07] <robert17> BUT, I can't manage to get it to assemble/start on boot.
[14:07] <robert17> AFTER boot, I can simply 'mdadm --assemble --scan', and all's good. But auto-assemble?
[14:08] <robert17> No dice ....  Is there something unique, or not quite ready, in Trusty?
[14:22] <RoyK> robert17: did you mdadm --detail --scan >> /etc/mdadm/mdadm.conf && update-initramfs -u # ?
[14:22] <robert17> RoyK: Yep.  As always ....
[14:23] <robert17> "Quadruple-checked" superblocks, etc etc
[14:23] <RoyK> check mdadm.conf if it has some ghosts
[14:23] <robert17> 'ghosts'?
[14:23] <RoyK> old references to former arrays of the same name
[14:23] <robert17> Ah. It does not
[14:24] <robert17> No errors in boot log afaict.  Just no startup.  Kernel mod's loaded.  Like I said, after startup, reassemble works perfectly.
[14:25] <robert17> Just a quiet, no-start on boot.
[14:29] <RoyK> is the raid in any lvm config or in fstab?
[14:32] <robert17> Nope, not yet.
[15:03] <robert17> RoyK: appears to be unique to Trusty.  Mine, anyway.  Ubu16 works just fine.
[15:32] <RoyK> robert17: I don't think the raid will be activated until it's actually used
[15:33] <robert17> 'used' ?  as in ... it has to be mounted?
[15:33] <robert17> Works fine "everywhere else" ...
[15:38] <RoyK> as in accessed
[15:39] <robert17> hm. Worth a try ... doing so now.
[15:48] <robert17> RoyK: Completely unneeded on Ubu 16 -- autoassembly on boot works with no access/mount, just mdadm.conf config.  OTOH, on Ubu 14, no autoassembly on boot, UNTIL ... create an /etc/fstab mount for the array.  Works now.
[15:48] <robert17> IIUC, that's going to be a problem if I want to boot from the array ...
[15:49] <robert17> It's got to assemble in order to GET to the /etc/fstab ... unless there's sufficient info in the initramfs
[15:53] <RoyK> robert17: I've used raid1 for boot devices on most versions of debian/ubuntu, and never seen an issue with that
[16:08] <RoyK> robert17: As I said, it usually assembles correctly, but isn't activated unless it's being touched by lvm or a filesystem or similar
[16:10] <robert17> RoyK: Do you by anychance need to use "dolvm" or "lvmwait=" in grub cmd line?
[16:16] <RoyK> robert17: IIRC I've used lvwait once, but I don't remember the occation
[16:35] <robert17> RoyK: fwiw, setting "GRUB_CMDLINE_LINUX="dolvm lvmwait=/dev/mapper/VG_TEST-LV_TEST", where /dev/VG_TEST/LV_TEST is a VG+LV on PV=/dev/md1 seems to do the trick. No /etc/fstab mount or /etc/rc.local needed.  Of course, that still requires that there's a mountable FS somewhere on the array ...
[17:17] <Braven> hello
[17:18] <Braven> does anyone know how to prevent a IF that is configured for DHCP from registering in DNS
[17:19] <Freze> thanks Royk
[17:27] <Braven> ??
[18:15] <Guest8335> What is needed for the broadcom WiFi to work?
[18:24] <madprops> anyone has compiled apache's mod_wsgi for python3 on xenial?
[18:24] <madprops> the version in the repo has a bug
[18:34] <sarnold> madprops: what bug number?
[18:35] <madprops> https://bugzilla.redhat.com/show_bug.cgi?id=1345725
[18:45] <sarnold> madprops: you could download the patch from the github issue; apt-get source the mod_wsgi package, apt-get build-depends for the mod_wsgi package, and try applying the patch
[18:45] <sarnold> looks like our packages are quite a bit older than the patch on github, it might take some massaging, but it's worth a try
[18:46] <sarnold> madprops: and if it works for you, you could post a debdiff to the debian bug and ubuntu bug and see if you can get it fixed for everyone else, too :)
[19:03] <Guest8335> Expansem
[19:04] <sarnold> Guest8335: that's not a very good password.. hope it's not for anything important :)
[19:05] <Guest8335> Sarnold easy to say.
[19:07] <Guest8335> How can I find a kmod name?
[19:08] <Guest8335> Bcmwl-kernel-source looked to have built a module.
[19:08] <Guest8335> It appears it isn't loaded.
[19:09] <sarnold> Guest8335: it looks like that generates a file named wl.ko
[19:10] <sarnold> Guest8335: try running 'find /lib/ -name wl.ko -ls' and see if that finds anything
[19:12] <Guest8335> There was b43 it isn't a 43xx chip but it works on fedora.
[19:20] <Guest8335> sarnold: Whatever it built there's no recent wl .ko showing in /lib/
[19:21] <Guest8335> When the package was installed it looked like it built against the running kernel. Running make in use SRC doesn't work.
[19:25] <sarnold> Guest8335: how about 'dkms status'?
[19:29] <Guest8335> Sarnold status?
[19:29] <Guest8335> It was installed it looks like something to. Do with virtualbox.
[19:58] <inkata> rbasak: hi hi
[20:08] <inkata> .
[20:18] <jamespage> coreycb, hey I sycned nova 14.0.1 to proposed
[20:18] <coreycb> jamespage, thanks
[20:43] <bc2946088> Probably a silly question, but upgrading a 14.04.05 MAAS(1.9) that controls openstack nodes to the latest HWE for continued support shouldn't affect anything with MAAS, right?
[21:00] <roaksoax> bc2946088: what do you mean by to the latest HWE ?
[21:19] <bc2946088> roaksoax: using the 16.04 Xenial HWE Stack on 14.04
[22:06] <jamespage> coreycb, release note looks good
[22:18] <BrianBlaze420> I am trying to set up an openvpn server
[22:18] <BrianBlaze420> oh it came to me
[22:18] <BrianBlaze420> <3
[22:45] <minx> Hi anyone with experience setting up ubuntu servers on lunanode vps?