[01:12] <Logos01> Howdy folks... got a touch of a stumper here... I ran __ echo "1" > /sys/kernel/mm/ksm/run __ about 50 minutes ago ... yet this remains the output of __ cd /sys/kernel/mm/ksm ; pwd ; grep '' * __ :  http://paste.ubuntu.com/6248607/
[01:12] <Logos01> full_scans remains 0
[01:13] <Logos01> Any thoughts?
[01:22] <MavKen> what is the easiest way to setup mail forwarding on ubuntu server?
[01:26] <Logos01> MavKen: I usually just use postfix for that.
[01:27] <MavKen> ok
[01:34] <MavKen> Logos01, from what I see you can only setup one domain...is it possible to have several domains using it?  I have several virtual domains on my apache server
[01:40] <Logos01> MavKen: Yeah it is. It's not trivial though
[01:41] <MavKen> ok
[01:50] <harushimo> I'm trying to install openstack
[01:50] <harushimo> I'm writing the nova.conf file and i'm getting an error about the for loop I copy on to the file
[03:01] <plars> matsubara: ping
[03:01] <plars> matsubara: still going to take a look at maas/juju tests on the current image?
[03:01] <plars> matsubara: I'm hoping this will be the last respin :)
[11:09] <Daviey> utlemming: The reason for switching to a new key is because it's signed by the Ubuntu Archive key? wtf?
[11:45] <Anomie_work> Is there a way to scan my VPS for malware?
[11:47] <koolhead17> zul: around
[11:47] <zul> koolhead17:  yep
[11:50] <koolhead17> Daviey: you never told me zul moved to rackspace :)
[11:51] <Daviey> :S
[12:07] <hxm> exists a imap reader daemon? for gmail
[12:07] <ndee> Hi there, I have a server which crashes in a weekly interval. I'm running 13.04 LTS. Where would the best place be to start searching for some clues? In which log files, etc.?
[13:31] <zul> jamespage: https://code.launchpad.net/~zulcss/heat/2013.2/+merge/191634
[13:32] <jamespage> zul, I was pondering 'New upstream release' -> 'Final upstream release'
[13:32] <jamespage> but I think its OK as is
[13:32] <jamespage> +1
[13:34] <zul> jamespage:  ack
[13:41] <zul> jamespage:  https://code.launchpad.net/~zulcss/ceilometer/2013.2/+merge/191637
[13:44] <jamespage> zul, +1
[13:44] <jamespage> I need an ack to upload spice-html5 to the Havana CA please
[13:44] <jamespage> nova-spicyproxy is uninstallable right now
[13:44] <jamespage> build test OK
[13:45] <plars> matsubara: ping
[13:45] <zul> jamespage:  url?
[13:45] <jamespage> zul: http://people.canonical.com/~jamespage/ca/havana/
[13:46] <zul> jamespage:  +1
[13:46] <zul> jamespage:  while you are at it https://code.launchpad.net/~zulcss/horizon/2013.2/+merge/191639
[13:46] <plars> matsubara: if you've tested maas on the current rc images already, could you mark the tests as completed on iso tracker at http://iso.qa.ubuntu.com/qatracker/milestones/305/builds/55947/testcases
[13:47] <jamespage> zul, +1
[13:47] <jamespage> pls make sure you merge your branches :-) that one looked odd but I understand why
[13:58] <matsubara> plars, sorry, I will. there's still one bug that's being worked on but I don't think that's going to make to the ISO. More likely a SRU
[13:58] <plars> matsubara: thanks!
[13:58] <matsubara> plars, bug 1240652, fwiw
[14:02] <zul> jamespage:  https://code.launchpad.net/~zulcss/cinder/2013.2/+merge/191645
[14:03] <zul> jamespage:  glance still building ;)
[14:04] <jamespage> zul, -1
[14:04] <jamespage> typo
[14:05] <zul> jamespage:  fixed
[14:06] <jamespage> zul, +1
[14:06] <ivoks> well, happy release day
[14:12] <zul> jamespage:  https://code.launchpad.net/~zulcss/glance/2013.2/+merge/191648
[14:12] <jamespage> zul, typo
[14:13] <zul> jamespage:  fixed
[14:15] <soahccc> Anyone knows what that mean? mdadm: add new device failed for /dev/sdf3 as 7: Invalid argument
[14:16] <jamespage> zul, +1
[14:16] <zul> merci
[14:24] <zul> jamespage:  https://code.launchpad.net/~zulcss/keystone/2013.2/+merge/191650
[14:24] <jamespage> zul, +1
[14:27] <zul> jamespage:  home stretch https://code.launchpad.net/~zulcss/swift/1.10/+merge/191651
[14:28] <jamespage> zul, +1
[14:53] <zul> jamespage:  https://code.launchpad.net/~zulcss/neutron/2013.2/+merge/191656
[14:54] <jamespage> zul, +1
[15:15] <zul> jamespage:  still building nova
[15:29] <zul> jamespage:  last one https://code.launchpad.net/~zulcss/nova/2013.2/+merge/191665
[15:32] <jamespage> zul, +1
[15:36] <zul> jamespage:  thanks now for the CA
[15:36] <jamespage> zul, nah - don't bother just yet
[15:36] <jamespage> I think we can afford to wait for the SRU cogs to turn
[15:37] <jamespage> rc-latest == release so its a no-change rebuild from my perspective
[15:37] <zul> cool
[15:39]  * Daviey ponders on the worth of an SRU.
[15:39] <Daviey> http://launchpadlibrarian.net/153998415/nova_1%3A2013.2~rc2-0ubuntu1_1%3A2013.2-0ubuntu1.diff.gz .. really?
[15:39] <jamespage> Daviey, this is purely  version change
[15:39] <jamespage> ...
[15:40] <jamespage> Daviey, so we can say we have the release of openstack - rather than the last RC
[15:40] <Daviey> Is it really worth the churn?
[15:45] <zul> Daviey:  optics is everytyhing
[15:45] <rbasak> People are going to be wondering and asking questions forever I think.
[15:45] <rbasak> "Why can't I update to the release version?"
[15:46] <rbasak> "You are on the release version."
[15:46] <rbasak> "Oh."
[15:46] <rbasak> ...
[15:46] <rbasak> ..."Why can't I update to the release version?"
[15:46] <rbasak> etc.
[15:47] <Daviey> rbasak: true
[15:47] <rbasak> "I used RH because Ubuntu wasn't fully up-to-date"
[15:47] <rbasak> "It is up to date - it's just this scheduling thing and the release candidate was released with no changes"
[15:47] <rbasak> "Oh well, too late"
[15:48] <rbasak> :)
[15:48] <Daviey> Yeah, it was annoying when people were asking for the latest stable point release.. which had ~2 patches different from our snapshot SRU.. only for those issues to not be a blocker for anyone.
[15:52] <zul> Daviey:  i would *love* to avoid that again ;)
[15:55] <jamespage> Daviey, they are all in the queue now if you would like to be our nominated SRU team representative
[15:55] <jamespage> :-)
[15:56] <jamespage> Daviey, I'm guessing that you might be on that already tho
[16:00] <Daviey> jamespage: already accepted them all :)
[16:02]  * jamespage gives Daviey a hug
[16:02] <jamespage> thanks
[16:20] <matsubara> plars, how do I submit the results to the iso tracker? I'm looking at this page: http://iso.qa.ubuntu.com/qatracker/testcases/1461/info but the only submit link is pointing to: http://iso.qa.ubuntu.com/qatracker/testcases/1461/results#add_result which returns a list of milestone releases but no form
[16:20] <plars> matsubara: you can't now, it's been released
[16:26] <matsubara> plars, ok. I'm pretty sure I got the same page yesterday when I clicked the submit link. Well, nm then. thanks.
[16:26] <plars> matsubara: could be that you had the page loaded before the respin and didn't click the new one when trying to post the results
[16:27] <plars> matsubara: it can be a pretty fickle tool - if there's been a respin you can't submit results on the old one, and if you could they wouldn't show up anyway
[16:27] <plars> matsubara: other than the bug for SRU later though, it was all ok though?
[16:34] <matsubara> plars, yes
[16:43] <rbasak> smoser: what's the canonical way of waiting for cloud-init to finish? Waiting for /var/lib/cloud/instance/boot-finished didn't work well for me in LXC, because it exists before the machine has started to boot (left over from a previous boot). But now I'm looking at KVM. Are there any guarantees about this that can be made from the point when ssh is open? Or is there an entirely different mechanism I can use?
[16:44]  * rbasak ponders asking upstart
[16:47] <smoser> rbasak, well you're "doing it wrong" sort of for lxc.
[16:47] <smoser> sort of.
[16:48] <smoser> don't boot a dirty instance, make a new one.
[16:48] <smoser> i guess you could check that the file exists and is newer than /proc/1 or something.
[16:49] <smoser> i think at one point i had ssh not starting until you could get in. but that i think is gone now or i'm just remembering wrong.
[16:49] <smoser> i kind of would like for ssh to not start until users were created and cloud-init had populated public and private keys.
[16:58] <rbasak> smoser: I'm fine with ssh opening late. I just want to make sure that the machine is ready to use. I had /tmp being cleaned while I was using it before (with LXC).
[16:58] <smoser> how were you using it?
[16:58] <rbasak> smoser: I want a developer to be able to modify an instance!
[16:58] <rbasak> (for LXC)
[16:58] <rbasak> adt-virt-lxc
[16:58] <smoser> but how were you using /tmp/
[16:58] <rbasak> autopkgtest uses /tmp. I need to know when the started container is ready for use.
[16:58] <rbasak> Putting stuff in it
[16:59] <rbasak> Then the /tmp cleaner gets to work
[16:59] <smoser> well, look for boot-finished
[16:59] <smoser> and use clean containers
[17:00] <smoser> or remove that before you start :)
[17:00] <rbasak> I can't use clean containers yet. lxc-create -t ubuntu-cloud doesn't really let me do that
[17:00] <smoser> ?
[17:00] <smoser> sure it does
[17:00] <smoser> use clone
[17:00] <smoser> i'm confused.
[17:00] <rbasak> Too slow
[17:00] <rbasak> I sometimes need to modify an image.
[17:00] <smoser> silly rbasak.
[17:01] <smoser> this is the saucy times
[17:01] <smoser> clone magic fast with overlayfs
[17:01] <rbasak> start-ephemeral is quick enough for me, but I want to modify the template into another template and give adt-virt-lxc that
[17:01] <rbasak> start-ephemeral does not nest, AFAIK
[17:01] <rbasak> (or does it?)
[17:01] <smoser> dont use start-ephemeral.
[17:01] <smoser> use clone with overlayfs
[17:02] <smoser> (overlayfs issues with inotify aside)
[17:02] <rbasak> Does that nest?
[17:02] <smoser> but how is clone slower than create . i'm still confused.
[17:02] <smoser> nest?
[17:02] <rbasak> How many layers can I have?
[17:02] <smoser> hallyn, ^
[17:03] <rbasak> I don't think this makes sense.
[17:03] <rbasak> What if I want to reboot a machine from the host? How do I know when it's finished booting then?
[17:03] <jrwren> anyone know why the python-boto package doesn't include the cli commands?
[17:03] <smoser> how do you ever know that ?
[17:03] <hallyn> nesting should be fine
[17:03] <hallyn> being called away for lunch, back in 25 mins
[17:03] <rbasak> I don't, but I'd like to know.
[17:03] <smoser> jrwren, because you haven't packaged them ;)
[17:04] <rbasak> Any tooling that runs synchronously from the host and relies on the guest booting needs to know to work reliably
[17:04] <jrwren> smoser: ;_;  I'll go do that, then.
[17:04] <smoser> jrwren, i think there is a bug on that in debian.
[17:04] <rbasak> I think it's a reasonable request.
[17:04] <smoser> we used to carry a larger delta on python-boto
[17:04] <smoser> and someone wanted to add the bin/ stuff
[17:04] <smoser> but i wanted to get our delta gone on python-boto
[17:04] <smoser> so i think i filed an upstream (debian) bug on that
[17:05] <rbasak> jrwren: the boto bin/ stuff is deprecated now in favour of aws-cli, isn't it?
[17:05] <jrwren> i'll blame smoser  :)
[17:05] <smoser> rbasak, we could write a boot-finished to /run
[17:05] <jrwren> rbasak: i don't know if it is officially deprecated. 12.04 LTS just has python-boto, no aws-cli.
[17:05] <rbasak> smoser: that would work well for me
[17:06] <smoser> you might be able to do that from user data
[17:06] <rbasak> jrwren: 12.04 LTS was released four years ago!
[17:06] <smoser> 13.10 - 12.04 == 4 years
[17:06] <smoser> (english people count funny)
[17:06] <rbasak> Um. Yeah. SOrry.
[17:06] <rbasak> Still, it's old.
[17:06] <smoser> is there aws-cli in ubuntu now? /me checks
[17:06] <rbasak> New stuff isn't going in. Not aws-cli, not boto bin/
[17:07] <jrwren> until today, its the only LTS :)
[17:07] <smoser> util 14.04 its the only lts
[17:07] <rbasak> RIght, but it's not relevant to a conversation about what to do between boto bin/ and aws-cli
[17:07] <jrwren> oh, oops, wrong LTS date :)
[17:07] <smoser> well, jrwren you woulndt easily get an SRU with those new files either.
[17:08] <jrwren> SRU?
[17:08] <rbasak> I disapprove of boto bin/ for personal reasons. It collides with me tool. It's version of bin/glacier is mostly useless
[17:08] <rbasak> my tool
[17:09] <jrwren> this is #ubuntu-server. I'm asking in context. I specifically asked about python-boto, the package, not boto in general
[17:09] <rbasak> I wouldn't mind having a /usr/bin/boto-* prefix or something though
[17:09] <jrwren> i'm not concerned. python -c "import boto;..." is just as easy
[17:09] <smoser> well, jrwren you can file a bug in debian . thats what i'd recommend. apparently i didn't do this.
[17:09] <rbasak> jrwren: sure, it's relevant here. I'm just saying that what was in a previous release isn't relevant to this discussion about changes in a future release.
[17:10] <smoser> but i do kind of agree with rbasak. we need the aws-cli tools packaged (thats been a TODO for like 12 montsh for me)
[17:11] <rbasak> IMHO, there are other tools (eg. aws-cli) that do a better job than boto/bin/*, so polluting /usr/bin/ isn't a good idea since that will just create collisions in some cases with inferior tools. aws-cli is the future.
[17:11] <rbasak> (but a prefix is fine)
[17:11] <rbasak> smoser: I'd be interested in packaging aws-cli for Debian if nobody else is doing it.
[17:11] <jrwren> even those scripts in /usr/share/boto would be useful.
[17:12] <smoser> google doesn't show me anything.
[17:12] <smoser> jrwren, you can go around rbasaks' back by going to debian.
[17:12] <smoser> :)
[17:12] <jrwren> i don't care enough. :)
[17:12] <rbasak> jrwren: sure, no objection to making it available _somewhere_. But that's up to the Debian maintainer really, not us :)
[17:12] <smoser> i dont have strong feelings about boto-foo in /usr/bin
[17:12] <jrwren> my original question was "anyone know why" and I have my answer :)
[17:13] <smoser> yeah. back when we had heavily pathced boto i would have probably just added it.
[17:13] <rbasak> EOD
[17:15] <roaksoax> jcastro: ping
[17:15] <jcastro> yo!
[17:15] <roaksoax> jcastro: do you know where did https://help.ubuntu.com/community/UbuntuCloudInfrastructure go?
[17:15] <jcastro> yikes! No.
[17:15] <jcastro> didn't know that
[17:15] <jcastro> looks like robbiew changed it?
[17:15] <roaksoax> yeah
[17:16] <jcastro> was there a deep link to stuff there?
[17:16] <roaksoax> jcastro: there was the whole "community" docs for deploy openstack with maas+juju
[17:16] <jcastro> indeed
[17:16] <roaksoax> robbiew: Howdy! By any chance did the content of https://help.ubuntu.com/community/UbuntuCloudInfrastructure got moved elsewhere?
[17:30] <hallyn> rbasak: do you still have a question on container snapshots?
[17:35] <sgran>         
[17:37] <sgran> sigh to lag
[19:25] <fedeisas> hello everyone, anyone saavy with permissions?
[19:34] <robbiew> roaksoax: yeah...I removed it...was all kinds of out of date...I can restore it
[19:37] <robbiew> roaksoax: changed it back
[20:34] <tarvid> 13.10 install freezes at language screen
[20:42] <roaksoax> robbiew: thanks! I was just wondering whether we had moved that information elsewhere since we don't really have any other public document on how to do a full deployment...
[20:43] <roaksoax> robbiew: i think it would be a good idea for us to provide an actual whitepaper or something instead
[20:45] <roaksoax> w/in 13
[20:52] <tarvid> tried the f6 options but with all off I can't get past the second langauge screen
[20:56] <tarvid> knoppix runs
[21:15] <tarvid> desktop installing
[21:16] <tarvid> server hangs on second language screen
[21:31] <robbiew> roaksoax: yeah, agreed
[21:31] <robbiew> we basically need to improve MAAS docs tremendously this cycle
[21:31] <robbiew> heading into 14.04 LTS...lots to clean up! :)
[21:35] <roaksoax> robbiew: thats gonna be fun!!
[23:45] <James_Epp> Hey guys. I'm in the process of trying to boot the ubuntu live discs over a network using nfs-kernel-server. Under my /etc/exports I have the following, however when clients boot they continue to give the error message "mount: Protocol not supported". What should I troubleshoot? http://paste.ubuntu.com/6233647/
[23:56] <hitsujiTMO> James_Epp: ubuntu needs to have nfs-common installed on the client