[10:33] <jtv> rvba: does Django give Network.clean() any way to know whether & which field validations may have failed?
[10:34] <jtv> Or do I need to either re-compute or cache the knowledge inside the model object?
[10:34] <rvba> jtv: not sure about that.  I would think so because model validation is modelled after form validation.
[10:35] <jtv> I think I can just generate a double error in this case — one for the netmask field, and one global one.  Not ideal, but...
[10:46] <rvba> jtv: are you landing the validation branches?
[10:46] <jtv> Yes, but there were some conflicts to be resolved.
[10:46] <rvba> Ah, okay.
[10:47] <jtv> Hence the Django problems: even if all your fields fail validation, Django still wants you to validate your model.  Even if all of _that_ fails, it still wants you to validate uniqueness.
[10:48] <rvba> That's weird.
[10:48] <rvba> Are you sure that's how it works?
[10:48] <rvba> Doesn't make sense.
[10:48] <jtv> Pretty sure — from observation _and_ from reading the code.  :)
[10:48] <jtv> The documentation doesn't mention the whole issue AFAICS.
[10:49] <jtv> Have a look at /usr/lib/python2.7/dist-packages/django/db/models/base.py
[10:49] <jtv> Look for full_clean.
[10:50] <jtv> And be warned that exception.update_error_dict(errors) means “exception, add your errors to my errors dict,” not the other way around.
[10:50] <rvba> yep
[10:51] <rvba> Okay, you're right, apart from the fact that only fields that didn't fail the previous validation go through uniqueness validation.
[10:52] <jtv> Ah, that's what "exclude" is for!  Thanks.
[13:57] <tomixxx3> hi, if i want to add virtual nodes to my maas-environment, how much effort is this compared to add a single physical machine which is quite simple
[14:05] <jtv> tomixxx3: it's doable, but maas won't actually _create_ the VMs for you.
[14:05] <jtv> So you'll have to take care of that part yourself.
[14:05] <tomixxx3> jtv, ok i udnerstand
[14:06] <tomixxx3> jtv: would be nice if maas would do this :-)
[14:06] <jtv> Yes, and believe me it has come up!
[14:06] <jtv> But it's not really a priority since the way we see it, it's mostly something you'd want for debugging.
[14:06] <jtv> The point of MAAS is bare metal, after all.  :)
[14:10] <tomixxx3> jtv: at the moment, i have still the problem that my nodes cannot access the internet
[14:13] <jtv> tomixxx3: was it not an option to set up routing with your server as a bridge?
[14:14] <tomixxx3> jtv: yes, but i dont know exactly how to achieve this
[14:15]  * jtv searches...
[14:16] <tomixxx3> jtv: if eth0 is the private network and eth1 connects the server to the internet, can i put the route-statements to eth0?
[14:17] <tomixxx3> jtv: and what aobut the "router ip" in the cluster interface settings?
[14:17] <tomixxx3> jtv: i guess it is not sufficient to simply add the IP of eth1 ?
[14:17] <jtv> The router IP is not really a setting... just let MAAS discover it during commissioning.
[14:18] <tomixxx3> jtv: ok
[14:18] <jtv> Hmm...  A search came up with a video guide.  Not the ideal format for this stuff, but it may help: http://www.irongeek.com/i.php?page=videos/ethernet-bridge-ubuntu-linux
[14:18] <jtv> I think many people talking about setting up a bridge mean a bridged ethernet interface for virtual machines...
[14:19] <jtv> tomixxx3: if you need NAT, it's probably a bit more complicated.
[14:20] <tomixxx3> jtv: but when i bridge eth0 and eth1, does my prviate network resp. the dhcp server of my private network NOT interfere the internet-network?
[14:20] <tomixxx3> jtv: i mean the university network?
[14:21] <jtv> It depends a bit: did you use a network range that is unique within the university network?
[14:22] <jtv> If you hook up routing where multiple machines could have the same IP address, then that would cause trouble of course.  And it just plain wouldn't work very well.
[14:22] <tomixxx3> 10.0.0.100 to 10.0.0.200
[14:22] <jtv> Is that range still free on the university network?
[14:22] <tomixxx3> dunno
[14:23] <tomixxx3> jtv: assuming, i bridge eth0 and eth1: should i use dhcp then or static configuraiton in "interfaces" file
[14:23] <jtv> Important to know.  If you have a range that the admins give you to use as part of the uni network, then it's relatively simple — you can just hook up the networks.
[14:23] <tomixxx3> jtv: because eth0 is configured static now, and eth1 is configured dhcp
[14:24] <jtv> eth0 should remain static, but the nodes should use dhcp.
[14:24] <jtv> That's because if your server also becomes the gateway to the internet, it had better stay at one fixed address.  :)
[14:24] <tomixxx3> jtv: so the bridge looks like: auto br0
[14:24] <tomixxx3> iface br0 inet dhcp
[14:24] <tomixxx3>   bridge_ports eth0 eth1
[14:25] <jtv> I must admit, I no longer have any knowledge of how this part works.
[14:25] <jtv> It's been a long, long time.
[14:26] <tomixxx3> jtv: or: i need simpley to add the line "bridge_ports eth0" to eth1 ?
[14:26] <jtv> If you ask the admins "hey can I use 10.0.0.100 thru 10.0.0.200" (actually it works in powers of two, so probably not exactly that range) and they turn a light grey, breathe in sharply, and start to swear at you, then you can't just bridge and you'll need NAT (or a different range).
[14:29] <tomixxx3> hmm
[14:29] <tomixxx3> and with NAT, i can NEVER destroy my uni network?
[14:30] <jtv> Never say never!  If you work hard at it, I'm sure there's a way.  It's not my position to make promises.
[14:30] <jtv> (In case any lawyers are listening...)
[14:30] <tomixxx3> jtv: i mean, when i route dhcp-broadcasting out of my prviate network, does this not harm the network?
[14:31] <jtv> The main thing is never to pass DHCP requests between your network and the university's, and to make sure that the address range you expose externally is available for your use.
[14:31] <jtv> You should not route _that_ traffic.
[14:32] <jtv> I'm not sure (did I mention it was a while ago?) but I don't think you'd usually want to route broadcast traffic anyway.
[14:33] <tomixxx3> jtv: so i should avaoid that broadcast-stuff is send?
[14:33] <tomixxx3> jtv: some kind of package filter?
[14:33] <jtv> Yes.
[14:34] <tomixxx3> jtv: damn, it get quite complex then.....
[14:34] <jtv> Yes, networking is hard.  :)
[14:34] <tomixxx3> jtv: my vision was that maas takes care of this things :D
[14:34] <jtv> I guess that's why software-defined networking is becoming more popular.
[14:35] <jtv> I bet it'd be easier with an off-the-shelf router, but that costs you a router as opposed to a network card.
[14:35] <jtv> Maybe ufw ("uncomplicated firewall") can make this easier.
[14:36] <tomixxx3> jtv: ok, if we go back the roots: i have my 3 nodes and they are connected to the university network. maas is not managing dhcp and dns. the nodes has accees to the internet but the problem is, that they boot from another dhcp server, namely from that of the university
[14:36] <tomixxx3> jtv: is there not a simple "trick" to let nodes boot from the maas-server images?
[14:37] <tomixxx3> jtv: ahh
[14:37] <jtv> ahh?
[14:37] <jtv> There is a way to do that, but it requires a configuration tweak to the main dhcp server.
[14:38] <tomixxx3> jtv: ok, i thought the following: i boot from the maas-dhcp server, as soon as the nodes are deployed to maas in state "ready", i turn off the dhcp settings of maas server, nodes get now IPs from university and has access to internet
[14:38] <jtv> The MAAS documentation has something about this, but it will depend on the type of DHCP server.
[14:38] <jtv> Ooo clever, but also slightly nasty.  Two problems with it that I can see:
[14:39] <jtv> 1. Other machines belonging to innocent PhD students may request addresses just while you're doing this.
[14:39] <jtv> 2. When a machine has an address from DHCP, it will need to talk to the DHCP server periodically to renew it.
[14:40] <jtv> Ah, here's the documentation I was looking for.  Not a lot, because it all depends: http://maas.ubuntu.com/docs/configure.html#manual-dhcp-configuration
[14:41] <jtv> Actually I'm not even sure that's complete...  I thought there had to be a setting to make PXE get the images from the MAAS server, too.
[14:41] <tomixxx3> jtv: about 1.) i don't get it. all 3 nodes in my cloud get unique IP addresses as far as i know
[14:42] <tomixxx3> about 2.) so the machine is not able to recognize that the dhcp server changed?
[14:43] <jtv> True... but then it'd probably change its IP address.
[14:43] <jtv> (Also, you need this while booting the machine, not just while commissioning it)
[14:44] <jtv> A node in a MAAS is not supposed to change its IP address... that's an assumption we've used in several places.
[14:44] <tomixxx3> jtv: and if i let the node get the same IP like from the other dhcp server? ^^
[14:45] <jtv> If you can make it do that, then I think that would work.
[14:45] <tomixxx3> jtv: puhh
[14:45] <jtv> Not very simple either.  :/
[14:48] <tomixxx3> jtv: because i can only define a range and not concrete IP addresses?
[14:50] <tomixxx3> jtv: i will ask my admin if i can have a free range for my nodes, so that i can bridge the network interfaces. but assume i have bridged them: is then guruanteed that my nodes will access my prviate dhcp server and not the university- dhcp server again?
[14:53] <tomixxx3> jtv: but at least, i guess, i'am right if i say: AT LEAST the JUJU bootstrap node need a internet-connection?
[14:55] <jtv> tomixxx3: I don't _think_ it does, if your juju version is recent enough...  Then I think the machine where you run Juju needs internet.
[14:55] <jtv> IIRC it will upload its tools to MAAS, which has a file store.
[14:55] <jtv> Of course any machine where you want to issue juju commands to the environment will have to be able to access it.
[14:56] <tomixxx3> jtv: the problem is, i want to deploy multiple juju charms on a single node, so i need lxc-containers. but creating those lxc containers fails because the node answers" cannot get file http://cloud-images.ubuntu.com/..."
[14:57] <jtv> Ah!  I'm not sure but I think that may be lxc needing access to the archive.
[14:57] <jtv> What should work is to make it use your MAAS server as an http proxy.
[14:57] <tomixxx3> Yeah, sounds cool
[14:58] <jtv> Should also give you the benefit of caching!
[14:58] <jtv> Although... university network in the heart of Europe... probably not that important to you.  :)
[14:59] <tomixxx3> jtv: yeah, good network here :D
[14:59] <tomixxx3> jtv: but, nevertheless, i take it if it is for free ;)
[15:00] <jtv> :)
[15:08] <tomixxx3> jtv: do u know how i can configure juju so that it uses the maas server as a proxy?
[15:08] <jtv> No, sorry, haven't tried that.
[15:09] <tomixxx3> kk
[15:13] <tomixxx3> jtv: referring this article: http://askubuntu.com/questions/310153/how-do-i-get-maas-and-juju-to-recognize-proxy-settings-in-a-deployment is "my.proxy" the IP of the maas server?
[15:14] <jtv> Sounds like yes... let me read that.
[15:14] <tomixxx3> jtv: k, ty
[15:16] <jtv> tomixxx3: that looks like exactly what you need... but Gavin says he wrote an updated answer that makes it easier.
[15:16] <jtv> "In the settings page (the cog near the top right)" etc.
[15:16] <jtv> He uses http://example.com/ as the example, but your MAAS server should go in its place.
[15:17] <jtv> The format is: http://<host>:<port>
[15:17]  * jtv looks up the port
[15:18] <jtv> I think it was port 3128... you can try that out by telnetting to it:
[15:18] <jtv> telnet <maas-server-address> 3128
[15:20] <jtv> Yes, that would be port 3128 by default.
[15:20] <tomixxx3> it says "connected to 10.0.0.9"
[15:20] <tomixxx3> jtv: ok
[15:20] <jtv> Yes it won't tell you much, but if it's listening there, good chance it's the proxy.
[15:21] <jtv> (Fun tip: many TCP-based internet protocols are text-based so you can try them out manually through telnet.)
[15:21] <tomixxx3> hehe
[15:22] <tomixxx3> do i have to reboot now sth, after clicked "save"?
[15:22] <jtv> errr
[15:22] <jtv> It could be that you need to re-commission the nodes with that setting in place.
[15:23] <tomixxx3> oh , hopefully, it fixes the lxc-creation problem then xD
[15:23] <jtv> Let's hope so!
[15:24] <tomixxx3> ok, i will do it... as u said: let's hope the best
[15:25] <tomixxx3> cause it tried to deploy a juju charm and i got the same error
[15:28] <jtv> Yeah I think that method would take hold while installing the node.
[15:30] <tomixxx3> kk at least while booting the nodes will become able to resolve archive.ubuntu.com etc. so at least one thing is "fixed" ;)
[15:31] <jtv> Progress!  :)
[15:31] <tomixxx3> yeah
[15:40] <tomixxx3> ahh the node cannot resolve again "http://archive.ubuntu.com/..
[15:42] <jtv> :(
[15:42] <tomixxx3> there is still a chance for Juju to succeed ^^
[15:43] <tomixxx3> btw. "stopping landscape ..." is the only task always "FAIL"
[15:44] <jtv> May be worth having a look in Landscape's logs then.
[15:49] <tomixxx3> k, i get the following now: "bad archive mirror" when i deploy juju bootstrap node
[15:51] <tomixxx3> the http-proxy: which IP address is it? the one of the interface connected to the nodes or the the IP of the interface connected to uni-network?
[15:52] <jtv> It's the one on the nodes' side.
[15:52] <tomixxx3> ok :(
[15:52] <jtv> Because this tells the nodes: "here's where your http proxy is."
[15:52] <jtv> I'm afraid I'll have to leave it at that for tonight!
[15:53] <jtv> Tschüß!
[15:53] <tomixxx3> k, ty for help and hints!
[15:53] <jtv> np
[16:20] <tomixxx3> nooooooo, now i always get this bad archive mirror when i try to isntall the bootstrap juju node.... even if i remove the http proxy....
[16:30] <tomixxx3> matsubara: hi, are u online?
[16:33] <matsubara> tomixxx3, hi, I'm online. How can I help? (I'm a bit busy so expect some delay in my answers)
[16:34] <tomixxx3> matsubara: ty! i'am a little bit depressed: i have set the option "http proxy" in the maas dashport to be the maasserver+port 3128. then i tried to add nodes again. They become ready. however, when i try to setup the juju bootstrap node, i get a "bad arhcive mirror" now while booting.
[16:34] <tomixxx3> matsubara: and the problem is: even if i remove the http proxy in the dashboard, from now, i always get this "bad archive mirror" excpetion when a node in the cloud boots
[16:35] <tomixxx3> matsubara: i tried to set the proxy, because i need juju to create lxc-containers and they need internet-connection but the nodes have no internet-connection, so my hope was that the maas-server could be the proxy...
[16:36] <tomixxx3> matsubara: i dont know if u remember my old problem: private network (3 nodes) + university network to get internet-connection
[16:41] <matsubara> tomixxx3, so, let me see if I understand, you get the 3 nodes in the Ready state, then run juju bootstrap and juju returns with a "bad archive mirror" error? Or is that in the node console/screen? How did you setup that proxy? Is it a regular squid proxy or a squid-deb-proxy? (given the port it looks like it's a squid proxy)
[16:42] <tomixxx3> matsubara: yes, 2 nodes in ready state, 1 node is maas-server, the node which become the juju bootstrap server get stuck with a "bad archive mirror" in node console screen.
[16:43] <tomixxx3> matsubara: i set the proxy via the maas-dashboard : settings -> "Proxy for HTTP and HTTPS traffic" -> http://10.0.0.9:3128
[16:43] <tomixxx3> matsubara: in order words: the address of the proxy was the address of the maas-server
[16:43] <matsubara> tomixxx3, and how did you configure that proxy running on 10.0.0.9:3128?
[16:43] <tomixxx3> matsubara: i did not configure it at all...
[16:44] <tomixxx3> matsubara: i tried telnet 10.0.0.9 3128 and it was able to connect...
[16:46] <matsubara> tomixxx3, what do you get as the responde from that telnet? If you point your browser to  http://10.0.0.9:3128 do you get a squid error message?
[16:47] <tomixxx3> matsubara: i get "the requested URL could not be tretrieved"
[16:48] <matsubara> tomixxx3, can you paste /var/log/squid/access.log ?
[16:48] <tomixxx3> kk
[16:48] <tomixxx3> squid3?
[16:49] <matsubara> yep, sorry
[16:49] <matsubara> and error.log too
[16:49] <tomixxx3> np
[16:49] <tomixxx3> http://pastebin.ubuntu.com/6880076
[16:49] <matsubara> but I think you'd need to configure squid properly. I don't think MAAS, by default configures the standard proxy for you, just the squid-deb-proxy, which uses port 8000, IIRC
[16:50] <tomixxx3> matsubara: and even, if i remove the http proxy, remove the nodes from maas, and re-commission all nodes, i get this "bad archive mirror" in console output of the nodes
[16:50] <tomixxx3> matsubara: i never got that before!
[16:52] <tomixxx3> matsubara: sorry, i mean, i get this message in the console output of the juju bootstrap node
[16:52] <tomixxx3> matsubara: i have not tried so far the other nodes
[16:54] <matsubara> tomixxx3, sorry, don't know what could be wrong, maybe this might help: http://askubuntu.com/questions/295999/maas-juju-still-get-bad-archive-mirror
[16:55] <tomixxx3> matsubara: i have already written through this article
[16:55] <tomixxx3> matsubara: i always had "manage dhcp and dns"
[17:19] <matsubara> tomixxx3, does your maas server route traffic to the internet for your nodes? Maybe your nodes are trying to reach the external world through the MAAS server but that's not working?