[00:38] <greentux> hi
[00:39] <greentux> I whant to know more about Ubuntu Maas, some one know where I found documentation?
[00:39] <bigjools> maas.ubuntu.com
[00:40] <greentux> I will have to make a cloud using 30 servers, but I need to know more about cloud, this place (maas.ubuntu.com) it´s the best to start?
[00:43] <bigjools> not really, you want to start with the Juju web site
[00:44] <greentux> Ok, thank you
[00:48] <bigjools> no problem
[04:54] <roaksoax> bigjools: ok so "fixed" the problem
[04:55] <roaksoax> bigjools: now the upgrade would good smoothly
[04:56] <roaksoax> bigjools: the problem was that newer maas conflicts/replaces maas-provision in precise, but older maas depended on maas-provision which causes that 'maas' to not be installed. Additioanlly, because of the conflict with tftpd-hpa, since it was a dependency of maas-provision, it caused maas-cluster-controller
[04:56] <roaksoax> bigjools: but it seems that removing the conflict/replaces with maas-provision fixes this, byut doesn't uninstalled, nor uninstalls tftpd-hpa
[04:56] <bigjools> good
[04:57] <roaksoax> bigjools: so I'll upload packages for testing tomorrow, and upload to the SRU queue
[04:57] <roaksoax> and we should be good to go
[04:57] <bigjools> roaksoax: excellent
[04:58] <bigjools> will be happy to see the back of the old version
[04:58] <bigjools> we need to prepare release notes because it won't work out the box after the upgrade
[04:58] <bigjools> the dhcp/dns won't be configured
[04:58] <roaksoax> bigjools: yeah! DNS/DHCP will definitely need to be updated
[04:58] <roaksoax> ./configured
[04:58] <bigjools> unless you can script something to migrate the existing cobbler config to the db
[04:59] <bigjools> a little tough since the cluster won't have registered yet
[04:59] <bigjools> so anyone who upgrades will be broken
[04:59] <roaksoax> bigjools: yeah, I wouldn't rely on the migration though, that's more of an accident waiting to happen
[05:02] <raywang> Hello bigjools I'm have problem with dhcp issue with new stable maas
[05:02] <bigjools> a problem with an issue eh?
[05:02] <raywang> bigjools, the dhcpd is not started, and when I run 'sudo start maas-dhcp-server",   there is still not a dhcp daemon running
[05:03] <raywang> lol sorry
[05:03] <raywang> bad English
[05:03] <bigjools> :)
[05:03] <bigjools> that's ironic because I have an issue with a problem
[05:03] <raywang> heh
[05:04] <bigjools> raywang: what is in syslog when you start the service?
[05:04] <roaksoax> and upstart log too
[05:04] <raywang> bigjools, no log
[05:05] <roaksoax> raywang: there's no apparmor log either?
[05:05] <bigjools> so yeah, upstart next
[05:05] <raywang> let me check
[05:05] <roaksoax> bigjools: fixes for the ephemral proxy stuff have not been backported to 1.2 right?
[05:06] <raywang> /etc/maas/dhcpd.conf does not exist.  Aborting.
[05:06] <raywang> maas-dhcp-server stop/pre-start, process 15527
[05:06] <bigjools> roaksoax: no, because the proxy feature is not in 1.2 at all
[05:06] <raywang> in upstart log
[05:06] <raywang> dhcpd.conf is not present by default installation?
[05:06] <roaksoax> raywang: did you install maas-dhcp?
[05:06] <raywang> roaksoax, yes I did
[05:06] <roaksoax> raywang: and maas-dns?
[05:06] <bigjools> did you configure the cluster in the UI?
[05:06] <raywang> ii  maas-dhcp                 1.2+bzr1360+dfsg-0ubuntu1
[05:07] <bigjools> raywang: ^
[05:07] <roaksoax> bigjools: ok! cool! I think eventually we would need a fix for that, since that's one of the issues that were present in the drill
[05:07] <raywang> bigjools, i have no idea what else I  need to configure the cluster
[05:07]  * roaksoax off to bed
[05:07] <raywang> roaksoax, good night
[05:07] <bigjools> roaksoax: :/
[05:08] <bigjools> nn
[05:08] <bigjools> roaksoax: go into the settings page, find the cluster and edit it
[05:08] <bigjools> you need to set network params
[05:08] <bigjools> they are not migrated from old installations
[05:08] <bigjools> roaksoax: this is exactly what we just talked about :)
[05:09] <raywang> bigjools, your suggest is quite helpful, let me check how to configure dhcp from web UI
[05:09] <roaksoax> night all
[05:09] <roaksoax> bigjools: i meant the Proxy issue is what we found in the drills :)
[05:09] <bigjools> roaksoax: yeah, I know
[05:10] <roaksoax> :)
[05:10]  * roaksoax -> bed
[05:10] <roaksoax> goodnight
[05:10] <bigjools> feature not in 1.2 though ...
[05:10] <bigjools> :(
[05:14] <raywang> bigjools, so make change of eth to be manage DHCP and DNS, right?
[05:36] <bigjools> raywang: yes (sorry, was distracted)
[05:36] <bigjools> raywang: also set the network params
[05:36] <raywang> bigjools, what do you mean by newwork params e.g. ?
[05:37] <bigjools> there's a page of DHCP settings
[05:37] <bigjools> netmask etc
[05:37] <raywang> yes
[05:37] <raywang> bigjools,ok, not all the options are required, like broadcast, right ? :)
[05:38] <bigjools> raywang: it is required
[05:39] <raywang> bigjools, i see,
[05:39] <raywang> bigjools, what does "router IP" , is it "gateway"?
[05:39] <bigjools> yes
[05:40] <raywang> hmm, a bit confusing by the name :)
[05:40] <bigjools> you might think so but I could not possibly comment
[05:40] <raywang> bigjools,  lol , thanks anyway
[05:41] <bigjools> raywang: you are very welcome!
[05:41] <raywang> i'll try it right away
[06:07] <raywang> bigjools, hi you idea is extremely helpful, thanks :)
[06:07] <bigjools> great
[06:07] <raywang> bigjools, but there are a lot of error message during the enlish process, seems like there is no place to set dns server
[06:08] <bigjools> you have to do that bit yourself
[06:08] <raywang> bigjools, and which version of juju do you recommend to use? main or ppa:juju/pkg?
[06:08] <bigjools> maas runs a dns server but you need to make sure anything that needs to resolve node names has it in resolve.conf
[06:08] <raywang> bigjools, ok.... seems like where i can set the dns server for enlisted node
[06:08] <bigjools> resolv.conf even
[06:08] <bigjools> the nodes pick it up from the dhcp server
[06:09] <bigjools> I can't say about juju
[06:09] <raywang> bigjools, so , you mean set the nameserver in /etc/resolve.conf on maas server?
[06:09] <bigjools> that would be a good start yes
[06:10] <raywang> bigjools, i mean the client (enlisted node) fail to download packages from archive.ubuntu.com
[06:10] <raywang> bigjools, so I need to set a dns server (e.g. nameserver 8.8.8.8 in /etc/resolve.conf on maas server)
[06:10] <bigjools> raywang: ah, so by default it proxies through a squid on the maas host
[06:11] <bigjools> so if that can't look anything up then yes, you're broken
[06:13] <raywang> bigjools, but seems like the client is not using maas server as a proxy server during enlisting and commissioning  stage
[06:13] <raywang> bigjools, i understand client will use maas server as a proxy server during "allocated to root" (installation) stage
[06:15] <raywang> bigjools, let me clear it up. :)    there will be three stages, I will call them:
[06:16] <raywang> 1. enlisting stage (first boot)
[06:16] <raywang> 2. commissioning stage (second boot)
[06:16] <raywang> 3. installation stage (third boot, which need to be allocated to some user)
[06:17] <raywang> during the No.1 No2. stages, I see it is accessing archive.ubuntu.com for download something, but i guess i need to set the nameserver for it at somewhere
[06:18] <bigjools> it will go via the maas server
[06:18] <bigjools> so as long as your maas server can access the internets, it's all ok
[06:19] <bigjools> I have to go now
[06:19] <bigjools> good luck
[06:21] <raywang> bigjools, maas server can go online, but client can't resolve the dns name.
[06:21] <raywang> bigjools, ok, tons of thanks :D
[07:38] <raywang> hello bigjools,  still awake? :)
[08:16] <raywang> Hi guys, i have problem with new juju bootstrap with new maas & new juju, http://pastebin.ubuntu.com/5572716/   http://pastebin.ubuntu.com/5572706/, http://pastebin.ubuntu.com/5572785/, anyone can help me out? thanks a lot :)
[08:43] <de_munk> Is it possible to deploy multiple juju charms in one maas node?
[14:59] <roaksoax> rvba: howdy!! I'm fine with postponing the SRU< but please keep in mind that next week is Feature Freeze...
[15:00] <rvba> roaksoax: Yeah, I know this is less than ideal.  allenap and I are currently working on it.
[15:00] <roaksoax> rvba: ok awesome! thank you!
=== kentb-out is now known as kentb
[15:05] <allenap> roaksoax: We're trying to fix something that was incorrectly implemented under time pressure, and now we're under release time pressure to fix it. It's going to be wrong again if we do that, and we're going to be back chasing our tails again :-/
[15:06] <allenap> roaksoax: It's not your fault, don't get me wrong. I'm just venting a little :)
[15:08] <roaksoax> allenap: heh no worries, I do understand the frustration :)
=== matsubara is now known as matsubara-lunch
=== matsubara-lunch is now known as matsubara
=== kentb is now known as kentb-afk