[10:09] <otubo> blackboxsw: tribaal well, we don't have a specific plan right now, but we're in terms of having one pretty soon. I'm working together with the Fedora maintainer so we can have a better policy for updating the package, so that could be extended to CentOS as well.
[10:10] <otubo> I'll send an email to the group once we have a plan. Thanks for asking about that :-) And sorry for the delay on the replay, I was on vacation :-)
[10:59] <tribaal> otubo: oh, that's good to hear! in the mean time, what would you suggest to be the best course of action? For context, we're a cloud provider maintaining several OS base images - CentOS beingone of them - and we recently (in 19.3) have our own cloud-init datasource that we'd like to use instead of the more generic former one
[11:00] <tribaal> so, ubuntu images have their cloud-init version SRU'd, and for debian 10 we will inject a deb from testing and do our own QA pass over it, but I'm not too sure what the best course of action is here for CentOS/Fedora (having personally had less exposure to those ecosystems)
[11:06] <tribaal> otubo: also - "an email to the group" -> I'd be very interested to be part of that group if I'm not there already via e.g. the cloud-init mailing list :)
[11:26] <otubo> tribaal: https://launchpad.net/~cloud-init there's a mailing list section at the bottom :)
[11:27] <otubo> tribaal: if I understand you correctly, all you need is more or less an updated package version for CentOS so you can use your DataSource?
[11:46] <tribaal> otubo: yes, correct. We could build a new package ourselves (of course) but would rather help test/contribute if appropriate
[11:47] <tribaal> we don't (currently) maintain public archives for rpms either, so skipping the cost of setting that up would be welcome. But again, if needed, we can.
[11:48] <otubo> tribaal: what are the issues when using your DS with current available packages?
[11:51] <tribaal> otubo: so, in 18.5 (or generally, before 19.3) the datasource we use is racy in specific conditions, resulting in a portion of cloud-init runs to fail to bring up networking. Note: that's specific to our platform.
[11:53] <tribaal> since we want to have the liberty to diverge from our previously-used datasource (cloudstack), we created an Exoscale specific one, the first fix being that specific race condition
[12:13] <otubo> tribaal: I understand. Well I can't promise you any dates, but I'm positive we're going to update at least Fedora in February.
[12:13] <otubo> tribaal: I still need to work on CentOS
[12:16] <tribaal> otubo: understood - let me know if/how we can help
[13:11] <otubo> tribaal: what about a small vps on your infrastructure for running tests? :-)
[14:53] <robjo> rharper: ping
[15:23] <rharper> robjo: here
[15:24] <robjo> rharper: received a bug w.r.t. mixing "static" and DHCP IP addresses, i.e. IPv4 may be static and IPv6 dynamic or vice versa
[15:25] <robjo> I think we have reached the breaking point of trying a non-differentiated write of ifcfg-eth*
[15:25] <robjo> OK with introducing a "flavor" into the sysconfig dict that configures the renderer?
[15:26] <robjo> BOOTPROTO setting needs to be handled differently between SLES and RHEL?
[15:33] <rharper> reading
[15:33] <robjo> https://bugs.launchpad.net/cloud-init/+bug/1858808
[15:34] <robjo> RHEL will complain about BOOTPROTO setting of dhcp4 and dhcp6, I think
[15:34] <rharper> yes
[15:34] <rharper> I'm updating bug with doc details
[15:35] <robjo> I'll add the SLES doc
[15:35] <rharper> Ive done that
[15:36] <robjo> lol
[15:36] <rharper> currently looking for why we set BOOTPROTO="static"
[15:36] <rharper> as that doesn't seem to have any affect; I suspect none is the right setting instead
[15:36] <robjo> In newer versions, per comment in the code we do not set static
[15:36] <rharper> ok
[15:37] <robjo> Well "none" is implied "static", I am not a fan of this being implicit
[15:37] <rharper> sure; but I suspect it's better to follow documentation of the distro
[15:40] <robjo> Well, "none" if we write that actually has a meaning:
[15:40] <robjo> none
[15:40] <robjo>                      For bonding slaves, to .....Note:  Do not use to just skip the IP setup -- use
[15:40] <robjo>                      BOOTPROTO="static"  without  any  addresses in the IPADDR
[15:40] <robjo>                      variables (or routes) instead.
[15:40] <rharper> hrm
[15:40] <rharper> that's troublesome; I don't see any code that checks the static value
[15:41] <robjo> we really do want "static" when that's what we get from the config ;)
[15:43] <rharper> nm, I totally missed the first line
[16:16] <ananke> so this is a fun error. running '/usr/bin/cloud-init status --wait' on amazon linux 2 results in a 'NameError: global name 'PermissionError' is not defined'
[16:17] <ananke> full error: http://dpaste.com/3NEB0AS
[16:25] <rharper> https://bugs.launchpad.net/cloud-init/+bug/1831146
[16:34] <blackboxsw> ananke: what distro again CentOS 7?
[16:35] <Odd_Bloke> blackboxsw: "on amazon linux 2"
[16:36] <blackboxsw> which is python3 ?
[16:36] <Odd_Bloke> Is it?
[16:36] <blackboxsw> I thought it wasn't as we heard in cloud-init summit I think?
[16:37] <blackboxsw> heh, and right (I was oblivious to the "on amazon linux 2" and jumped straight to the error
[16:37] <blackboxsw> https://forums.aws.amazon.com/message.jspa?messageID=870220
[16:38] <blackboxsw> AL2  default looks to be py2 per that thread and the faq for core packages maintained https://aws.amazon.com/amazon-linux-2/faqs/
[16:39] <blackboxsw> sooo Odd_Bloke with us dropping py2.7 in trunk, where does that leave AL2 and it's python2 default
[16:39] <blackboxsw> s/trunk/tip
[16:40] <Odd_Bloke> It leaves Amazon needing to get into this^Wlast decade. :3
[16:40] <blackboxsw> maintaining their own cloud-init py2 compat support I suppose
[16:40] <blackboxsw> yeppers, unfortunately
[16:40] <ananke> figures that I'd dig up another issue :)
[16:40] <Odd_Bloke> For a non-sarcastic answer, I'm not entirely sure.
[16:41] <blackboxsw> yeah and not one this time that upstream would be likely to address ananke :/ it's still worth a bug https://bugs.launchpad.net/cloud-init/+filebug
[16:41] <Odd_Bloke> Well, the bug is in 18.5, right?
[16:41] <ananke> /bin/cloud-init 18.5-2.amzn2
[16:41] <Odd_Bloke> Which was advertised as supporting 2.7.
[16:41] <ananke> yep
[16:41] <blackboxsw> Odd_Bloke: ahh right. :/
[16:42] <blackboxsw> so that'd be us patching the last py2 support branch
[16:42] <ananke> this is whatever the latest amazon linux 2 btw
[16:42] <Odd_Bloke> Yeah, though there's not much benefit to doing that if Amazon aren't going to use that branch.
[16:42] <blackboxsw> minor changeset to fix that for python2 :/
[16:43] <Odd_Bloke> So we probably need to reach out to Amazon and talk to them about how they want to handle this sort of issue, as they're one of the last places that has Python 2 in their most recent release.
[16:47] <ananke> with amazon pushing cloud-init, I imagine they'd be receptive
[17:04] <Odd_Bloke> blackboxsw: rharper: BTW, realised I hadn't actually done the thing: https://github.com/canonical/cloud-init/pull/159
[17:04] <blackboxsw> haha Odd_Bloke
[17:04] <blackboxsw> man
[17:04] <blackboxsw> oops broke protocol
[17:05] <blackboxsw> btw rharper https://github.com/canonical/cloud-init/pull/77 has a nit if you'd like to add it to the comment
[17:05] <blackboxsw> we can land that then ^
[17:05] <Odd_Bloke> Haha, was just about to point that out.
[17:05] <Odd_Bloke> blackboxsw: If you want it fixed, should it be Approved?
[17:05] <blackboxsw> since you are making the rules Odd_Bloke you can break them :)
[17:06] <blackboxsw> Odd_Bloke: I guess that falls into "Aprrove (with nits)"
[17:06] <blackboxsw> I can make the change then :)
[17:06] <rharper> blackboxsw: I think so, I have allow edits enabled
[17:06] <blackboxsw> will try that out now
[17:10] <blackboxsw> hrm so should I be able to git push ryan's github repo  fix/network-static6-rendering
[17:11]  * blackboxsw reads the docs
[17:11] <blackboxsw> as I don't think I can add a comment to a file that wasn't touched by the original PR via the github PR web UI
[17:17] <blackboxsw> got it
[17:19] <blackboxsw> git checkout <rh-remote>/<pr_branch_name> -b <local_branch>; add nits; git commit -am 'nits' ; git push <rh-remote> <local_branch>:<pr_branch_name>
[17:33] <blackboxsw> oops, clicked the merge button before fully scrubbing the squashed commit message. Odd_Bloke rharper when we have Co-authored-by references in a squash merge commit, should we be using our @canonical or personal emails?
[17:34] <blackboxsw> it seems Dan and I have a default email set as personal
[17:35] <blackboxsw> not sure it matters much as our merge markers are all authored as @canonical
[17:36] <blackboxsw> I've switched my primary email address in my github profile to<EMAIL_ADDRESS>but then I need to remember to change/override that for any external opensource projects I would touch.
[18:14] <blackboxsw> meena: I think the only thing blocking one of your PRs is dropped the integration test test_boottime from the PR (and maybe addressing an integration testt as a separate PR) https://github.com/canonical/cloud-init/pull/53/files#r360061164
[18:38] <Odd_Bloke> blackboxsw: I don't think it particularly matters, TBH.
[18:40] <blackboxsw> Odd_Bloke: as in we can land as is, or maybe add a comment #TODO(move to cloud_tests) for that test?
[18:40] <Odd_Bloke> blackboxsw: No, I meant the thing you pinged me about. :)
[18:41] <blackboxsw> ahh email
[18:41] <blackboxsw> right
[19:39] <meena> friends, it's late here( 20:38)so I'm in bed already and very sleepy
[19:40] <meena> I'll clean this up tomorrow
[19:40] <wyoung> nn
[21:31] <ananke> is there a recommended solution for running 'runcmd' items as a specific user?
[21:36] <ananke> say I have just a few commands, so not worth creating a discrete script. I could prepend each one with sudo, but it would seem there would be an easier way
[21:39] <Odd_Bloke> runcmd doesn't have support for it, from looking at the code.
[21:41] <Odd_Bloke> We could consider adding such support, though we would need to think about the security/correctness implications of not using sudo (or, I suppose, we could just call sudo).
[21:41] <Odd_Bloke> ananke: You could do `sudo sh -c "...; ..."`, which simplifies things a little.
[21:54] <ananke> Odd_Bloke: thanks for the suggestions!
[22:15] <Odd_Bloke> :)
[22:52] <smoser> ananke: yaml anchors are useful
[22:52] <smoser> http://paste.ubuntu.com/p/35DFhjsGYP/
[22:53] <smoser> thats the kind of stuff that smoser wastes time on.
[23:01] <robjo> smoser: What does this mean in Ubuntu? in a netplan
[23:01] <robjo> eth1:
[23:01] <robjo>                         match:
[23:01] <robjo>                             macaddress: cf:d6:af:48:e8:80
[23:01] <robjo>                         set-name: eth1
[23:02] <robjo> does the interface get brought up but get no IP address?
[23:02] <robjo> or does dhcp magically run?
[23:14] <powersj> hmm I thought you had to have a dhcp4: true or a addresses:
[23:26] <blackboxsw> yowsa smoser that is a hefty bit of cloud-config. me saves it to grok a bit later
[23:27] <blackboxsw> I don't use anchors nearly enough (and probably need to check it out via the cloud-init devel schema annotation stuff to make sure we can annotate properly)
[23:28] <blackboxsw> s/nearly enough/at all/


[00:27] <LLStarks> sup raof
[00:29] <RAOF> Tiredness, apparently.
[00:29] <RAOF> Also me accidentally suspending my IRC bouncer.
[00:49] <bryceh> thanks RAOF!
[03:18] <bryceh> interesting; my nouveau box OOPSed with mesa 8.0.2.  With 8.0.4 I still get an EQ overflow in X and X lockup, but no kernel OOPS
[03:18] <bryceh> just a lot of
[03:18] <bryceh> [  120.491370] [drm] nouveau 0000:05:00.0: Ctxprog is still running
[03:19] <RAOF> Odd.
[03:19] <RAOF> On the other hand, yay progress!
[03:35] <Sarvatt> nouveau is getting worse instead of better over time :(
[03:35] <ajmitch> nvidia as well, it seems
[03:35] <Sarvatt> really?
[03:36]  * ajmitch has a new system running quantal, gets multi-second pauses & occasional full X hang when running games
[03:36] <Sarvatt> i'm still on 295.xx on my rarely used nvidia box
[03:37] <ajmitch> from what I've read, it's a known problem & I'm on the latest drivers also
[03:38] <ajmitch> there's probably an LP bug about it, though it's not dumping anything useful to logs
[06:16] <mlankhorst> morning
[06:22] <tjaalton> yo
[06:47] <mlankhorst> oh great prime work was upstreamed, so I did miss something ;)
[06:49] <tjaalton> xrandr 1.4 isn't released yet though
[06:49] <mlankhorst> tjaalton: there's a patch we could use from airlied though, it automatically binds things
[06:54] <tjaalton> yeah I heard fedora has some
[06:54] <tjaalton> but we need ddx updates too
[06:55] <mlankhorst> do we really want to at this point?
[07:05] <tjaalton> if we want that stuff?
[07:05] <tjaalton> I don't know
[07:06] <tjaalton> intel 2.20.7 has it, so why not
[07:06] <tjaalton> no nouveau or ati releases
[07:06] <tjaalton> our ati is actually rather old
[07:11] <tjaalton> bug 1046759 is fun
[07:12] <tjaalton> -modesetting fail
[07:25] <mlankhorst> hm, modesetting should init as a matter of fact, but it should just pisss off afterwards
[07:26] <tjaalton> right
[07:26] <tjaalton> there are a couple of commits past 0.4 but dunno if they'd make a difference
[07:27] <mlankhorst> maybe it will though, platform bus stuff
[07:28] <tjaalton> oh we have that
[07:29] <mlankhorst> that's post 0.4.0 though
[07:29] <mlankhorst> would probably get rid of [     3.798] (WW) Falling back to old probe method for modesetting
[07:29] <tjaalton> yes, but rsalveti wanted it
[07:30] <tjaalton> hum
[07:30] <tjaalton> so we're missing something on x86?
[07:30] <mlankhorst> dno, likely modesetting is just destructing weirdly
[07:31] <mlankhorst> get a more complete backtrace?
[07:33] <mlankhorst> I'm surprised ati doesn't show up in the log, wonder why though
[07:59] <dj_ryan> so i am trying to make this intel q77 mobo do triple monitors, but its extremely resistent to google'n
[07:59] <dj_ryan> just pluggin in the Displayport cable doesnt do it alas
[08:00] <dj_ryan> (this board had 2*dvi, 1*dp on board, and apparently the intel 4000 hd can do triple monitor, and the intel xorg driver can support it, maybe?)
[08:00] <mlankhorst> intel's doing a some complete reworking of relevant code in their kernel git tree, so if you feel comfortable
[08:00] <mlankhorst> try drm-intel-next
[08:01] <dj_ryan> i dont think ican do that alas
[08:02] <dj_ryan> i need to be on a specific version of kernel so i can install zst
[08:02] <mlankhorst> would be just for testing
[08:03] <dj_ryan> well i'd also like to have my triple displays back
[08:03] <dj_ryan> maybe i'll co-install that ati 5000 card i have
[08:05] <dj_ryan> we had to ditch the ATI 4xxx-based desktops and go with these intels due to stability caused by what we think are xorg crashes
[08:07] <dj_ryan> oh my coworker is getting me a dvi splitter so the 3rd monitor can be connected via VGA...
[12:03]  * mlankhorst somehow read linux-image-3.4.0-1486-omap4 as linux-image-3.4.0-i486-omap4 and wtf'd for a bit until he realized it :)
[12:20] <mlankhorst> tjaalton: oh I think I know why it fails at least, it tries to add the second screen with prime, but modesetting doesn't handle that
[12:27] <mdeslaur> So...is there any way to get Quantal working with nouveau right now?
[12:27] <mlankhorst> mdeslaur: prime?
[12:28] <mdeslaur> is there a bug for the INVALID_OPCODE failures resulting in me being unable to login?
[12:28] <mdeslaur> mlankhorst: what do you mean by "prime"?
[12:28] <mlankhorst> optimus or general?
[12:29] <mdeslaur> general, it's a thinkpad T61 that worked fine with precise and all other previous releases
[12:30] <mlankhorst> unsure, not that I heard of at least
[12:32] <mdeslaur> mlankhorst: ok, let me try and figure out how to open a bug if I can't log in
[12:32] <mlankhorst> apport-bug ;)
[12:41] <mdeslaur> mlankhorst: LP: #1049088
[12:41] <mdeslaur> yeah, apport-bug is awesome until you get to the part where it wants to open a browser :)
[12:41] <mlankhorst> tjaalton: hm, did you push the 20.6 changes?
[12:43] <tjaalton> mlankhorst: oops, did now
[13:28] <mlankhorst> tjaalton: prime display failed here on that ;) should we push 20.7 and nouveau-ddx git?
[13:53] <tjaalton> mlankhorst: failed the same way?
[13:55] <mlankhorst> nah in a different way, addscreen failed
[13:55] <mlankhorst> but the bug is probably that modesetting didn't expect to be removed early or something
[14:26] <tjaalton> mlankhorst: sure, why not. intel has a release and nouveau not that many commits post 1.0.1
[14:28] <mlankhorst> tjaalton: yeah I asked darktama if i could release current git as 1.0.2
[14:29] <tjaalton> cool
[14:33] <jcristau> oh, chase left canonical?  /me catches up on email
[14:35] <tjaalton> yup, dunno where
[14:46] <mlankhorst> hm.. I wonder if at this point we should remove the nomodeset from recovery mode and attempt to use modesetting instead of fbdev
[15:02] <tjaalton> yes
[15:05] <mlankhorst> requires changing grub-common
[19:16] <bryceh> anyone got thoughts on if we might put mesa 9.1 into x-updates?  good idea / bad idea ?
[21:20] <mlankhorst> bryceh: hm couldn' t we do the same as we will do for mesa in quantal?
[22:19] <bryceh> mlankhorst, yeah probably.  Not sure what's in 9.1 vs. 9.0
[22:49] <RAOF> mlankhorst: re: nomodeset for recovery mode.
[22:51] <RAOF> mlankhorst: I think that VGA text mode is more likely to work, and we want a recovery mode that's as likely as possible to actually work.
[23:12] <bryceh> agreed
[23:14] <bryceh> btw I've set up a PPA for mesa 9 - https://launchpad.net/~ubuntu-x-swat/+archive/mesa9
[23:14] <bryceh> jordan at Intel took care of the packaging.  I've added him as member of ubuntu-x-swat, and invited him to do updates of it
[23:15] <RAOF> Ah, cool.
[23:15] <bryceh> I'm also thinking for x-updates we should think about carrying a mesa update as well.  The DDX's alone really aren't that interesting anymore
[23:15] <RAOF> +1
[23:15] <bryceh> RAOF, great
[23:16] <bryceh> figure we should include for precise the same package we'll behaving in quantal
[23:16] <bryceh> then after 12.04.2 is released we can up that to 9.1 or whatever if we want
[23:55] <Sarvatt> bryceh: problem is carrying a mesa update involves many other packages too ~1 month after a stable release releases.. wayland weston libxkbcommon are guaranteed, maybe llvm and libffi it needs, then tricky things like out of tree builds being broken for months or nouveau libdrm abi breaks. its always easiest right now where theres hardly any divergence but it will get stuck and stable updates will probably be better off for intel during that time be
[23:55] <Sarvatt> cause they backport so much to them
[23:56] <Sarvatt> just having it be drivers is a huge benefit for nvidia people


[10:19] <bluesabre> Can anybody run this test in a non-qemu/kvm/libvirt environment? I'm limited in my testing options right now, and 1861609 is giving me a hard time: https://iso.qa.ubuntu.com/qatracker/milestones/453/builds/300219/testcases/1628/results
[15:43] <arraybolt3> bluesabre: If no one else did it already, I can take it on.
[15:45] <arraybolt3> Pulling image now.
[16:12] -SwissBot:#xubuntu-devel- ::xubuntu-seed:: live: +cryptsetup @ http://git.launchpad.net/~xubuntu-dev/ubuntu-seeds/+git/xubuntu/commit/?id=97407165e62366d7ace0d0edb052ed2d5e5c19ff (by Dan Bungert)
[16:13] <bluesabre> Respinning now to fix LVM encrypted installs
[16:13] <bluesabre> ISOs spinning, head spinning, feels like the day before an LTS release to me!
[16:25] <arraybolt3> ah so the ISO I just pulled is probably no good :P
[16:29] <bluesabre> Maybe less so :D
[16:58] <bluesabre>  20240424.1 is live now
[17:36] <arraybolt3> got it installed already
[17:39] <arraybolt3> bluesabre: "To test desktop locking, a new user should be created with the User and Groups option from Settings menu" There is no Users and Groups option in XFCE that I can find in Xubuntu Minimal.
[17:41] <bluesabre> This is true, but I haven't created a separate test for minimal yet. Just create the user *somehow* to be able to test multi-user locking.
[17:41] <arraybolt3> kk, used adduser
[17:42] <arraybolt3> multi-user locking works just fine :D
[17:43] <arraybolt3> Submitted a "Passed" result on the ISO tracker.
[18:28] <arraybolt3> hmm, I can't run AppImages at all on Xubuntu Minimal.
[18:28] <arraybolt3> Not sure what I'm missing - I get "cannot execute: required file not found" when I try.
[18:29] <arraybolt3> oh wait, I downloaded the ia32 version.
[18:31] <arraybolt3> haha, whew, problem solved. I was scared there for a bit :P
[18:31] <arraybolt3> It was looking for i386 libraries.
[18:32] <bluesabre> That's a relief. :D
[18:58] <arraybolt3> bluesabre: Looks like you may need to seed cryptsetup on the Xubuntu Minimal ISO. Encrypted installations fail.
[18:59] <arraybolt3> Unexpected error while running command.
[18:59] <arraybolt3> Command: ['cryptsetup', 'luksFormat', '/dev/sda3', '/tmp/luks-key-nubsqc2w']
[18:59] <arraybolt3> Exit code: -
[18:59] <arraybolt3> Reason: [Errno 2] No such file or directory: 'cryptsetup'
[18:59] <arraybolt3> (typed across, may have typos)
[18:59] <arraybolt3> Filing bug report now.
[19:04] <arraybolt3> https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/2063366
[19:04] -ubottu:#xubuntu-devel- Launchpad bug 2063366 in xubuntu-meta (Ubuntu) "Xubuntu Minimal fails to install when using LVM + encryption" [Undecided, New]
[19:05] <bluesabre> It's there for the installer already: https://github.com/Xubuntu/xubuntu-seed/blob/40085c99cf44332784d1800f4bbd53240efe2cba/ship-live#L44
[19:05] <bluesabre> So probably need to raise an alarm over on Matrix
[19:05] <arraybolt3> If I run `cryptsetup` in a terminal, it tells me it couldn't find the command.
[19:06] <arraybolt3> Command 'cryptsetup' not found, but can be installed with:
[19:06] <arraybolt3> sudo apt install cryptsetup-bin
[19:08] <arraybolt3> bluesabre: Alarm raised.


[03:19] <OerHeks> ~~~~~~/\~~~~~~\0/~~~~~
[03:21] <daftykins> :D
[03:22] <daftykins> morning sir
[03:22] <daftykins> http://i.imgur.com/d6d1cos.jpg
[03:22] <daftykins> have a look at some RAM!
[03:45] <daftykins> http://i.imgur.com/Orfn61P.jpg
[03:45] <daftykins> more fun
[13:19] <BluesKaj> Hiyas all
[22:59] <pauljw> that's interesting, i've been banned in #ubuntu??  hmmm...
[23:01] <OerHeks> odd, ask in #ubuntu-ops pauljw
[23:01] <Bashing-om> pauljw: I can not imagine such a thing happening .., #ubuntu-ops for a sit-rep ?
[23:03] <pauljw> heheh, i just asked in there.
[23:04] <daftykins> :O
[23:04] <daftykins> perhaps you were caught chatting to me!
[23:05] <Bashing-om> daftykins: Paul left .. did you insult him ?
[23:06] <pauljw> okay, was my vpn ip address
[23:06] <pauljw> lol daftykins
[23:10] <daftykins> XD
[23:10] <daftykins> i hope to never send any of you away!
[23:10] <daftykins> though my pics of old kit could get annoying eventually ;D
[23:11] <pauljw> not to me they won't
[23:12] <Bashing-om> Nope on pics, me like too .
[23:12] <OerHeks> more pics please
[23:12] <OerHeks> even my silly flowers are allowed
[23:13] <OerHeks> * they are drying now, upside down
[23:13] <pauljw> :)
[23:16] <daftykins> i wanted to confirm a PSU wasn't faulty today, since i knew the mobo in the case was faulty... i took out the motherboard tray from the server type machine and plugged it in on top :)
[23:16] <daftykins> https://www.dropbox.com/sh/zdt3o7t609awl2m/AAC7rzWvIQGyZzlW9RlVGZ3oa?dl=0
[23:16] <daftykins> i love working with cases that have mobo trays
[23:17] <daftykins> just moved a couple more in there, they should appear on a refresh
[23:20] <pauljw> neat, never had such a setup.
[23:21] <daftykins> that machine used to be a small company's file server, they were contractually obligated to run a hideous Facilities Management product that required MS SQL server and a Windows Server OS :/
[23:22] <daftykins> looks like i had to go quite high end with the motherboard to get one with chipset RAID at the time - two 320GB WD's are in RAID-1 for the OS, both have power on hours of 40,000 now :)
[23:22] <daftykins> that's causing them to be flagged as bad in SMART
[23:22] <pauljw> ah
[23:23] <daftykins> the RAID controller, one of my faves, is hooked up to 4 x 1.5TB disks - or was until one popped and has been replaced with a 2TB WD Red which is still in warranty even now! i may keep it for myself
[23:23] <daftykins> though my own RAID is already 6 x 2TB
[23:25] <pauljw> :)
[23:26] <daftykins> anywho, thinking if i put that server setup's board into the case beneath it i can sell that as desktop #3
[23:26] <daftykins> i can only give it 4GB RAM though, boo!
[23:27] <pauljw> 4G is doable for a desktop
[23:28] <daftykins> it won't have a license that one, so perhaps it'll get a Linux!
[23:28] <daftykins> as lovely as server 2003 R2 x64 would be to push upon someone... a fully EOL OS XD
[23:28] <pauljw> :)
[23:33] <pauljw> OerHeks, here's what we're watching grow from our front porch these days...
[23:33] <pauljw> http://imgur.com/a/UHcR4
[23:35] <OerHeks> You can watch it grow too, i guess
[23:35] <daftykins> nice!
[23:36] <Bashing-om> pauljw: Coyottes make good neighbors ?
[23:37] <pauljw> heheh, yeah they're around, keep the rifle handy.
[23:37] <daftykins> i was hunting some in a game the other day!
[23:38] <Bashing-om> Yeah, have that here .. so 'fraid they are going to lure my dogs off .. thay are not big and bad enough to take care of themselves .
[23:39] <pauljw> the other day my wife and i got to see a doe and her young fawn playing in the fields, he was acting just like a puppy, romping around, kicking his hind legs up...
[23:41] <Bashing-om> pauljw: Yeah .. cute sight .. We used to have turkeys also .. I miss seeing them .. must have all got shot out .
[23:41] <pauljw> :(
[23:41] <pauljw> we still have tons of turkey, too.


[04:27] <mup> Bug #1713695 changed: QueryDict error when creating an iprange via the API <MAAS:Expired> <https://launchpad.net/bugs/1713695>
[04:27] <mup> Bug #1716494 changed: Admin certificate upload <MAAS:Expired> <https://launchpad.net/bugs/1716494>
[04:36] <mup> Bug #1713695 opened: QueryDict error when creating an iprange via the API <MAAS:Expired> <https://launchpad.net/bugs/1713695>
[04:36] <mup> Bug #1716494 opened: Admin certificate upload <MAAS:Expired> <https://launchpad.net/bugs/1716494>
[04:39] <mup> Bug #1713695 changed: QueryDict error when creating an iprange via the API <MAAS:Expired> <https://launchpad.net/bugs/1713695>
[04:39] <mup> Bug #1716494 changed: Admin certificate upload <MAAS:Expired> <https://launchpad.net/bugs/1716494>
[11:53] <if_gaga1> hello guys,i intalled maas on server with 2 network interfaces (eth0, eth1, for example), how i can bind all MAAS *network activity* to eth1
[11:55] <if_gaga1> ,
[11:55] <if_gaga1> ?
[18:13] <jac_cplane> I just upgraded to maas 2.2.2  and it seem custom images are no longer supported through this command.    maas admin boot-resource create name=custom/centos7-netfix title="Centos 7 - netfix" architecture=amd64/generic<EMAIL_ADDRESS>[18:13] <jac_cplane> can any help
[18:13] <jac_cplane> Hi narinder
[18:13] <jac_cplane> are you on?
[18:13] <jac_cplane> I just upgraded to maas 2.2.2  and it seem custom images are no longer supported through this command.    maas admin boot-resource create name=custom/centos7-netfix title="Centos 7 - netfix" architecture=amd64/generic<EMAIL_ADDRESS>[18:14] <jac_cplane> was is the latest way to install a custom image into maas
[18:21] <jac_cplane> anyone?
[18:22] <jac_cplane> how can i import a custom image into maas 2.2.2 since boot-resource create is no longer supported
[18:27] <jac_cplane> is read now the replacement command for create
[18:28] <jac_cplane> it seems that create is no longer available but read or delete is
[18:28] <jac_cplane> any place this is documented
[18:31] <mup> Bug #1731671 opened: Commissioning Composable Machine Fails <MAAS:New> <https://launchpad.net/bugs/1731671>