[02:05] <bigjools> jtv: congraulations, your UI typo branch was r 3000 in trunk
[02:05] <jtv> \o/
[02:06] <jtv> Not what you'd want for such a bit milestone, is it?
[02:06] <bigjools> seems appropriate somehow :)
[06:03] <MasterPiece> moin all
[06:03] <MasterPiece> R a mirror available 4 maas?
[06:04] <MasterPiece> Can I create new mirror 4 it?
[06:10] <jtv> MasterPiece: a mirror of what?
[06:10] <bigjools> there r n0 mirr0rs
[06:11] <bigjools> he probably means the ephemerals
[06:11] <jtv> Well before we guess, let's find out.  :)
[06:11] <bigjools> someone asked this the other day so it's an *educated* guess :)
[06:11] <MasterPiece> mirrors so that more speed in downloading images, packages, etc
[06:12] <bigjools> you can use sstream-mirror dor the images
[06:12] <bigjools> package archives are configured in MAAS itself, just pick a mirror
[06:12] <MasterPiece> & in order to Product Line and local mirror :)
[06:12] <bigjools> dor?  I mean for
[06:12] <MasterPiece> And How Can I be a mirror 4 MAAS ?
[06:13] <jtv> You mean MAAS itself?  People get it from the package archive mirror.
[06:13] <jtv> So you're probably best off just picking an Ubuntu archive mirror near you, and maybe setting up a caching proxy.
[06:14] <jtv> Oh, we also have the PPA packages of course.  I think either an archive proxy (like squid-deb-proxy or apt-proxy) or a regular caching http proxy would be best for those.
[07:00] <MasterPiece> I wanna to be a new mirror for it, How this is possible ?
[07:06] <jtv> MasterPiece: I don't understand the question.  What _exactly_ do you want to be a mirror for?
[07:54] <rvba> jtv: quick question for you since you reviewed Julian's branch (https://code.launchpad.net/~julian-edwards/maas/apt-mirror-for-commissioning/+merge/234919).  Why is it okay to change the call to generate_user_data() to pass it a node when I see that it accepts only an optional nodegroup?  I'm probably missing something… ?
[07:56] <jtv> rvba: I don't think I understand the question...  It accepted an optional nodegroup, used only for testing, and now it accepts a node.
[07:57] <rvba> jtv: ah, right, my bad.  I misread the diff.  Sorry about that.
[07:58] <jtv> No worries.
[09:03] <MasterPiece> jtv, so that I have more and more speed in downloading them, local network is very faster than WWW network :)
[09:07] <jtv> MasterPiece: so you don't want to be a mirror of anything, so much as speed up downloads?
[09:07] <MasterPiece> jtv, Y
[09:08] <jtv> Okay, what operations specifically would you like to speed up?
[09:12] <MasterPiece> importing boot images
[09:13] <jtv> In that case, I'd go with what bigjools said: sstream-mirror.
[09:14] <jtv> We don't have a network of "official" mirrors as far as I know, but you can keep your own mirror that way and make it available to people you know locally.
[09:15] <jtv> I don't know the details about how that works, unfortunately.  But you can use the MAAS API to tell MAAS to download images from your mirrored server.
[09:15] <jtv> Look for "boot sources."
[09:52] <MasterPiece> Thanks jtv and bigjools
[09:56] <jtv> np
[12:28] <rvba> allenap: Could you please review https://code.launchpad.net/~rvb/maas/rename-monitoring/+merge/234950 ?
[12:38] <allenap> rvba: Sure. Do you want to talk Twisted too?
[12:43] <rvba> allenap: I think I manage to answer my own Twisted question :).
[12:43] <rvba> managed*
[12:51] <rvba> allenap: not so why I have these 'committed' conflicts.  I accidentally committed a couple of conflicts in the pre-req branches but it's all fixed now.
[12:51] <rvba> s/not so/not sure/
[12:52] <rvba> allenap: it's fine now, I just forgot to push a revision.
[17:58] <lamont> at what point does maas know the power type of the macine (assuming ipmi)?  I have a machine that's declining to have its power type show up by the time it's declared, which makes commissioning it a manual powercycle.
[18:02] <lamont> s
[18:03] <lamont> when I manually add the IPMI (2.0) info, commissioning happens at the click of a button
[18:36] <roaksoax> lamont: that'd mean that MAAS failed to discover IPMI for whatever reason.
[18:36] <roaksoax> lamont: what MAAS version are you using, (1.5?)
[18:37] <roaksoax> lamont: there might also be a cloud image issue, or even the commissioning environment is not accessing the network
[18:38] <smoser> hey
[18:38] <smoser> so i just added a source as doc'd in http://maas.ubuntu.com/docs/bootsources.html
[18:38] <smoser> how do i tell maas to import all sthos ?
[18:40] <roaksoax> smoser: maas <user> boot-resources import
[18:40] <smoser> http://paste.ubuntu.com/8366766/
[18:40] <roaksoax> blake_r: ^^
[18:41] <jhobbs> smoser: have you done 'maas refresh' lately?
[18:41] <roaksoax> smoser: yeah that's with the latest 1.7
[18:41] <lamont> roaksoax: 1.5.2+bzr2282-0ubuntu0.2
[18:42] <blake_r> roaksoax: yeah that only works with 1.7
[18:42] <lamont> and I want to say that it's an HP DL380 G7 or so
[18:42] <smoser> well, i showed the dpkg-query
[18:42] <smoser> that is from maas stable
[18:42] <roaksoax> lamont: yeah, so first thing to check is whether enlistment/commissioning can actually access the network
[18:42] <blake_r> smoser: you can start the import with boot-images
[18:42] <smoser> how ?
[18:43] <lamont> roaksoax: on 623, or on what port?  (after I manally teach maas how to talk to the ilo, it successfully turns thebox on for getting from declared => commissioning, and all is well
[18:43] <smoser> blake_r, i guess i can just ask.. if i'm going to try to install ppc64el, do i have a chance with 1.6 ?
[18:43] <roaksoax> lamont: right, so on enlistment/commissioning maas access the archives to download freeipmi tools to do IPMI discovery
[18:43] <smoser> or should i use 1.7
[18:44] <roaksoax> smoser: +1 on 1.7
[18:44] <smoser> so you would use daily  ppa ?
[18:44] <lamont> roaksoax: that may entirely be it
[18:44] <lamont> roaksoax: can you clarify "the archives"?
[18:44] <roaksoax> lamont: archive.ubuntu.com
[18:44] <lamont> archive.u.c I suspect?
[18:44] <blake_r> smoser: yes ppc64el should work on 1.6
[18:45] <roaksoax> lamont: correct!
[18:45] <lamont> roaksoax: that network has access to about 63% of the archive machines. :(
[18:45] <lamont> thank you
[18:45] <smoser> ok, blake_r then how do i import ?
[18:46] <lamont> roaksoax: that is, Ihave enough to let me get it sorted.  thanks
[18:47] <roaksoax> lamont: glad to help!
[18:47] <roaksoax> smoser: maas admin boot-resources import -> that will import the images to the Image store
[18:47] <roaksoax> smoser: and then the clusters will import the images themselves
[18:48] <blake_r> roaksoax: not on 1.6
[18:48] <roaksoax> blake_r: correct
[18:48] <roaksoax> smoser: on 1.7 that above will work
[18:49] <blake_r> smoser: maas admin node-group import-boot-images cluster-uuid
[18:49] <smoser> thank you blake_r .
[18:49] <smoser> roaksoax, i dont even have an ideal on where i would get 1.7
[18:49] <blake_r> smoser: maas-maintainers/experimental
[18:50] <roaksoax> blake_r: in 1.7, how can you tell the clusters to import the images from the image store?
[18:50] <blake_r> roaksoax: that same command I just gave smoser
[18:50] <blake_r> roaksoax: you have to do it for each cluster
[18:51] <smoser> blake_r, lets say i did that
[18:51] <roaksoax> blake_r: yeah, that makes sense
[18:51] <smoser> and i didn't see any disk space disappearing
[18:51] <smoser> where would i look for issue?
[18:52] <roaksoax> smoser: what do you mean by that? the import of images finished successfuly?
[18:52] <blake_r> smoser: /var/log/maas/celery.log
[18:55] <smoser> blake_r, ok. i had not specified a '*' for label
[18:55] <smoser> so it was not matchign anything
[19:22] <smoser> blake_r, http://paste.ubuntu.com/8367010/
[19:22] <smoser> what did i do wrong ther e?
[19:22] <smoser> all i have is trusty
[19:23] <smoser> shoot
[19:38] <smoser> ok. so that was my fault (no utopic ppc64el images in daily stream)
[19:38] <smoser> thats being fixed.