[13:03] <roaksoax> allenap: ping
[13:10] <allenap> roaksoax: otp, done soon.
[13:19] <guimaluf> is it possible to add maas server as a maas node? I would like to set up the maas server as the cloud-controller, glance and keystone.
[13:20] <roaksoax> guimaluf: yeah you can enlist localhost, but for juju is not gonna be usefull because the maas server is the onein chanrge of turning on the machines you need
[13:22] <allenap> roaksoax: Going to be a bit longer.
[13:22] <roaksoax> allenap: no worries, let me know when you done :)
[13:24] <guimaluf> roaksoax, so my maas server should be uniq for this purpose? cause I've a powerfull server and run only the maas server will be a waste of resources.
[13:25] <roaksoax> guimaluf: yeah, unless you deploy VMs with it
[13:25] <guimaluf> then should I put the maas server in a virtual machine ?
[13:25] <guimaluf> deploy vms with juju?
[13:25] <roaksoax> guimaluf: you could, or you could have VMs contorlled by maas
[13:25] <roaksoax> guimaluf: for juju they would only be nodes
[13:26] <guimaluf> hmm
[13:27] <guimaluf> I can't figure out how I'll use my 16 servers in juju + openstack IaaS
[13:29] <guimaluf> roaksoax, another issue: when I run juju status openstack-dashborad there is public-address:null
[13:30] <guimaluf> I dont know how will I make my cloud avaible.
[13:30] <guimaluf> when will my node get the hypervisor installed?
[13:31] <guimaluf> I'm bit confuse :(
[13:31] <guimaluf> and bothering you alot, I thin
[13:31] <guimaluf> think
[13:31] <roaksoax> TBH I have not done many openstack deployments with juju/MAAS
[13:31] <roaksoax> so I don't know much about those bits
[13:31] <roaksoax> guimaluf: someone who would be able to help you is adam_g
[13:32] <roaksoax> but he is at OSCON atm
[13:33] <guimaluf> :(
[13:46] <smoser> well, if juju doesn't have the address, it would seem a general juju<->maas issue.
[13:59] <allenap> roaksoax: What's up?
[13:59] <allenap> The stuff still hasn't gone upstream.
[13:59] <allenap> :)
[13:59] <roaksoax> allenap: ok, so, there's something wrong with maas-pserv
[13:59] <roaksoax> allenap: there's some weird thing happening. maas-pserv fails to start
[14:00] <roaksoax> but then magically, it starts
[14:00] <allenap> roaksoax: Do you have some logs for it?
[14:00] <roaksoax> allenap: there's nothing :)
[14:00] <roaksoax> allenap: can you spawn a canonicastack instace and install maas from quantal
[14:00] <roaksoax> and see it for yourself to see if you have any ideas of what it might be?
[14:00] <allenap> roaksoax: I wonder if this is still the celeryconfig problem?
[14:01] <roaksoax> allenap: might be, I imported the path
[14:01] <allenap> roaksoax: I've never used canonistack, so it might take me a while to figure it out.
[14:01] <allenap> roaksoax: If it's that, I'm working on it.
[14:01] <roaksoax> allenap: so upstart says twistd doesn't know who 'maas-pserv' is
[14:01] <roaksoax> allenap: so it is failing somewhere when the plugin does the import
[14:01] <allenap> roaksoax: Yeah, that sounds right. It can't import celeryconfig probably, but the import exception is being suppressed.
[14:02] <roaksoax> allenap: I added the path in provisioningserver/plugin.py so I know it is importing thepath correctly
[14:03] <allenap> roaksoax: Let me fix the celeryconfig thing. If the problem is still there then I'll spend more time on it. Will that block you?
[14:03] <roaksoax> allenap: yeah we have a broken maas in quantal :)
[14:04] <allenap> roaksoax: It's fairly broken in Precise too ;)
[14:05] <roaksoax> allenap: heh but precise at least works
[15:41] <guimaluf> roaksoax, when I expose a service I get the following error: http://pastebin.ubuntu.com/1098491/
[15:41] <guimaluf> I'm  completely discouraged
[15:42] <roaksoax> guimaluf: AFAIK, you cannot expose services with maas as that's like opening a port in ec2
[15:42] <roaksoax> that's only a feature with ec2 i thi nk
[15:43] <guimaluf> so how will I make my service avaible?
[15:51] <roaksoax> guimaluf: the service is available
[15:51] <roaksoax> guimaluf: if you are deploying instances with juju inside openstack, then you can use the expose command I believe
[15:52] <guimaluf> roaksoax, I have onde node on my juju environment, I deployed, related and exposed many services, but where will I access my service? I cant get the public-address value, and I got this error on node juju log
[15:54] <roaksoax> guimaluf: "Service exposing works by opening appropriate ports in the firewall of the cloud provider."
[15:54] <roaksoax> if you are deployimng in baremetal that ncommand is not necessary
[15:55] <guimaluf> but when I access my node address nothing happens
[15:55] <guimaluf> all my services have agent-state:pending
[15:55] <guimaluf> :/
[15:56] <roaksoax> that means that they are trying to get installed or something wrong is going on there
[16:12] <guimaluf> roaksoax, probabily something wrong in the node right?
[16:12] <roaksoax> guimaluf: yes in the node
[16:14] <guimaluf> there is nothing in /var/log/juju :/ only the error above
[16:16] <guimaluf> I'll install openstack without juju :/ time is near :(
[16:17] <roaksoax> guimaluf: is that on the client machines?
[16:17] <guimaluf> roaksoax, yep
[16:17] <guimaluf> /var/log/juju/provision.log
[16:17] <roaksoax> guimaluf: there's no machine-agent.log nor provision.log?
[16:17] <guimaluf> provision log http://pastebin.ubuntu.com/1098491/
[16:29] <roaksoax> rvba: bug #1026228
[16:29] <roaksoax> guimaluf: there was an error with juju apparently, do you have any cloud-init logs?
[16:39] <guimaluf> roaksoax, http://pastebin.ubuntu.com/1098589/
[17:17] <roaksoax> guimaluf: were you seeing this error? 2012-07-18 13:14:46,016:1882(0x7fe067770700):ZOO_ERROR@handle_socket_error_msg@1579: Socket [127.0.0.1:44068] zk retcode=-4, errno=111(Connection refused): server refused to accept the client
[17:19] <guimaluf> roaksoax, nop. only ZOO_INFO
[17:20] <roaksoax> sok
[17:21] <roaksoax> smoser: there seems to be an issue when importing the data source after the bootsrrap
[17:25] <smoser> roaksoax, ?
[17:25] <roaksoax> smoser: juju does not get installed after juju bootstrap with maas
[17:26] <roaksoax> i'm redploying
[17:26] <smoser> because cloud-init isn't getting its datasource
[17:26] <roaksoax> smoser: it is getting the ssh keys from MAAS
[17:26] <roaksoax> not the juju stuff though
[17:27] <smoser> roaksoax, can you give me more info and/or access?
[17:28] <roaksoax> smoser: is in my local environment, let me finish re-bootstrapping
[17:28] <roaksoax> smoser: apache: http://pastebin.ubuntu.com/1098663/
[17:31] <roaksoax> smoser: ah never mind I think I found the issue
[17:31] <roaksoax> it seems to be proxy
[17:34] <roaksoax> smoser: for some reason sources.list ends up with ubuntu-mirror
[17:34] <roaksoax> smoser is that done by cloud-init?
[17:35] <smoser> roaksoax, yes.
[17:35] <smoser> you have broken dns
[17:35] <smoser> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/974509
[17:36] <smoser> cloud-init noticed that you had a host on your network (named 'ubuntu-mirror') and assumed that you wanted to use that mirror.
[17:36] <roaksoax> smoser: I don't this is MAAS on a VM
[17:36] <smoser> your issue is that you also have a host named "roaksoax-uses-a-broken-dns-provider-that-does-dns-hijacking"
[17:36] <roaksoax> dns/dhcp is libvirt
[17:37] <smoser> try it.
[17:37] <smoser> thats the problem. cloud-init does a dns lookup and its getting a valid response for that 'ubuntu-mirror'
[17:38] <smoser> (rather than a not found response)
[17:38] <roaksoax> smoser: right, but it is libvirt the one controlling DNS
[17:38] <smoser> well libvirt is letting dns pass through
[17:38] <smoser> dnsmasq is cacheing only for libvirt.
[17:39] <smoser> change your hosts dns to use 8.8.8.8 and restart libvirt.
[17:39] <smoser> (note, it is annoying, and something that will get fixed in one way or another).
[17:41] <roaksoax> smoser: did you happen to figure out how to select a particular dns server on a wifi connection at all times?
[17:43] <Daviey> good luck with that
[17:43] <smoser> man dhclient-script
[17:43] <smoser> it would seem its possible there.
[17:43] <Daviey> possible == hack
[17:43] <smoser> but that will likely cause issues on public wifi
[17:44] <smoser> its not a hack. its explicitly listed as how to do it.
[17:44] <smoser> oh. or also
[17:44] <smoser>  /etc/dhcp/dhclient.conf
[17:45] <smoser> hm..
[17:45] <smoser> but no, with resolvconf that wont work
[17:45] <roaksoax> and againa another reason why I hate the change in resolvconf :)
[17:46] <roaksoax> smoser: but anyuways, any way to disable cloud-init trying to use a mirror? What If I don't really want it to automatically use one
[17:46] <smoser> you can feed it one with user-data.
[17:48] <roaksoax> smoser: right, but shouldn't default behavior be not to try to do that?
[17:48] <roaksoax> smoser: cause, in my cause for exmaple, is breaking my maas implementation and might be breaking others too
[17:50] <roaksoax> smoser: cuase either way, that's the reason why we pass http://pastebin.ubuntu.com/1098696/ to the preseed
[17:50] <roaksoax> s/to the/in the
[17:51] <smoser> roaksoax, shouldn't the default behavior be to not have broken dns?
[17:51] <roaksoax> smoser: then I guess we should go all the way to resolveconf :)
[17:51] <smoser> but having this feature off by default would essentially defeat its purpose.
[17:52] <smoser> the idea was to not have to modify the image and get magical selection of your local mirror
[17:52] <smoser> i'm confused though
[17:52] <smoser> oh.
[17:52] <smoser> yeah, that does suck
[17:53] <smoser> you preseed the install, and that gets it right
[17:53] <smoser> and then cloud-init finds a better mirror
[17:53] <smoser> you can fix it through late_command here.
[17:53] <roaksoax> smoser: right, then I guess we should have an option within MAAS to disable that
[17:54] <smoser> well, this [miss]feature is probably going to change.
[17:54] <roaksoax> smoser: cuase, for example, in my particular case, how was I supposed to know I had a broken DNS on a clean machine and when I haven't played with DNS?
[17:54] <roaksoax> i wouldn't have notice at all if it wasn't for what cloud init found
[17:54] <roaksoax> so that means, like me, there might be others with the same issue
[17:55] <roaksoax> having mirrors on a MAAS network, but not wanting to use them
[17:55] <smoser> so.. i'm told that the way chrome handles this is that it tries dnslookups of never-will-exist domains.
[17:55] <smoser> and then says "oh, you have broken dns"
[17:56] <smoser> roaksoax, so..
[17:56] <smoser> cobbler  cobbler/password  password xcobbler
[17:56] <smoser> is there any reason that i'd pre-seed that in quantal?
[17:57] <roaksoax> smoser: in pserv.yaml?
[17:57] <roaksoax> smoser: yeah it gets replaced on postinst
[17:57] <smoser> hm..
[17:57] <smoser> in zimmer-build
[17:57] <roaksoax> ah lol
[17:57] <smoser> i used to do that
[17:57] <smoser> to set a password for cobbler
[17:58] <roaksoax> no not really needed
[17:58] <roaksoax> maas should take care of settings its own user now
[17:58] <smoser> so should i remove that even if on precise?
[17:58] <roaksoax> I believe so
[17:59] <smoser> what about updating /var/lib/cobbler/snippets/maas_proxy
[17:59] <smoser> any reason to do that on quantal
[17:59] <smoser> ?
[18:00] <roaksoax> yeah it should probably stay
[18:00] <smoser> ok... what about /etc/cobbler/cobbler.conf ?
[18:00] <smoser> is that still around?
[18:00] <roaksoax> smoser: you mean settings? yes still needed until we drop it
[18:01] <smoser> i'm looking at zimmer-build/ud-build.txt
[18:01] <smoser> and there are hacks/modifications for cobbler that are done
[18:01] <smoser> and i was just trying to see if each is still necessary
[18:02] <roaksoax> smoser: I don't really think we need any since all the setup is done by maas itself
[18:02] <roaksoax> though we need to ensure that maas set's the correc tproxy, and next_server
[18:02] <smoser> it updates /var/lib/cobbler/snippets/maas_proxy ?
[18:03] <smoser> err... wait.
[18:03] <smoser> is there a way that i can tell maas to use my *other* proxy?
[18:03] <smoser> that is what the proxy hack was doing
[18:03] <roaksoax> smoser: nope there's not. so that's why we should keep that.
[18:03] <roaksoax> and making sure next_server and server and MAAS_DEFAULT_ULR are set correctly
[18:03] <smoser> and then the cobbler init hack
[18:04] <smoser> are you looking at this?
[18:04] <smoser> i make cobbler update its network address on start
[18:05] <roaksoax> smoser: so the cobbler network address update should be kept, + make sure it is updated on /etc/maas/maas_local_settings.py
[18:05] <roaksoax> cause they should be the same
[18:05] <smoser> so i should just change that hack to read it from /etc/maas/maas_local_settings.py ?
[18:06] <smoser> from DEFAULT_MAAS_URL ?
[18:06] <roaksoax> smoser: yes,
[18:06] <roaksoax> that could also be a way to fix this
[18:09] <smoser> PYTHONPATH=/etc/maas python -c 'import maas_local_settings, urlparse; print urlparse.urlsplit(maas_local_settings.DEFAULT_MAAS_URL)[1]'
[18:12] <roaksoax> smoser: looks good to me
[18:14] <smoser> roaksoax, http://paste.ubuntu.com/1098737/
[18:14] <smoser> i'm gonna test that
[18:15] <roaksoax> cool, looks good to me
[18:23] <smoser> roaksoax, wait.
[18:23] <smoser> does maas try to figure that value out on its own?
[18:23] <smoser> or how can i tell it to re-get it.
[18:24] <smoser> the problem is that i build the zimmer image, and then save it. and when it boots it has a new ip address.
[18:25] <roaksoax> smoser: ah riught, it tries to figure out on postinst, so you need to obtain it the way you were doing it, and update maas_local_settings, and update cobbler
[18:25] <smoser> bugger.
[18:31] <smoser> roaksoax, which of the /etc/init/maas-* files do i need to change so they dont start until MAAS_URL iset correctly?
[18:31] <roaksoax> smoser: actually that part is run by apache2
[18:31] <roaksoax> through the wsgi.py file
[18:32] <smoser> fun.
[18:41] <smoser> roaksoax, so what do you think.
[18:41] <smoser> i get the right address
[18:41] <smoser> and then what?
[18:41] <smoser> do i update /etc/maas/local_settings.py ?
[18:42] <smoser> and dpkg-reconfigure maas ?
[18:42] <smoser> will that do it?
[18:42] <roaksoax> smoser: dpkg-reconfigure maas updates maas_local_settings.py and cobbler settings
[18:42] <smoser> updates it from what?
[18:43] <roaksoax> smoser: is a debconf questions that asks for the IP address
[18:46] <smoser> ok. so i'm going to just go with this:
[18:46] <smoser>  sudo dpkg-reconfigure -pmedium maas
[20:48] <smoser> roaksoax,
[20:48] <smoser> in apt-get install of maas (during zimmer build for quantal)
[20:48] <smoser> /tmp/maas.config.12013: 32: /tmp/maas.config.12013: dbc_go: not found
[20:48] <smoser> maas failed to preconfigure, with exit status 127
[20:48] <smoser> Fetched 62.5 MB in 7s (8324 kB/s)
[20:48] <smoser> Selecting previously unselected package libavahi-common-data:amd64.
[20:48] <smoser> (Reading database ... 46830 files and directories currently installed.)
[20:48] <roaksoax> smoser: that seems like dbconfig-common is missing or failing or something
[20:49] <smoser> can you depend on that from config?
[20:49] <roaksoax> smoser: yeah