/srv/irclogs.ubuntu.com/2013/05/02/#maas.txt

bigjoolsif you alt-f8 (I think) you should see more output00:00
bigjoolsit takes a while00:00
bigjoolsit downloads some stuff from the repos00:00
TheChistosoit's been about 30 min.00:01
bigjoolsok00:01
bigjoolsit should be around 5-1000:01
TheChistosoalt-f8 didn't give me anything -- but then again, i'm using it over the bmc and the keystroke may or may not be getting across00:01
bigjoolsok00:01
bigjoolsone sec00:01
TheChistosoi don't suppose you know the default username/password?00:02
bigjoolsthere isn't one00:02
TheChistoso(let me guess -- password is generated?)00:02
bigjoolsbut there's a backdoor image that you can use to commission with that has a user/password set up00:02
* bigjools looks for it00:02
TheChistosowell i can't ssh w/ the key i provided in my preferences00:02
bigjoolsno, you can't log in at all with commissioning00:02
TheChistosoit's past commissioning00:03
bigjoolsit's not - otherwise it would be ready00:03
TheChistosoit's commissioned -- it's deployed00:03
bigjools...00:03
TheChistosothat is, the OS is installed, cloud-init reported as having completed00:03
bigjoolsok let's get the terminology straight00:03
TheChistosolol okay (c:00:03
* mwhudson was going to say :)00:03
bigjoolsyou were previously at the "ready" state?00:04
TheChistosoi was at whatever the name for the state is when you've brought up the machine, maas recognizes it, and then i hit "accept & commission" (or "start & commission")00:04
bigjoolsthat is, it enlisted, powered off, you clicked "accept and commission" and it powered up, did stuff and powered off again00:04
TheChistosothat ran -- the OS installed, it restarted, there's a login prompt, w/ some output indicating that cloud init completed00:05
bigjoolswait00:05
mwhudsonhow did you tell the os installed?00:05
mwhudsonit probably didn't00:05
TheChistosoi watched the os install00:05
bigjoolson the second boot, did it power down?00:05
bigjoolsit is not installing anything when it commissions00:06
bigjoolsnothing usable for you anyway00:06
TheChistosohonestly, there were a few reboots and i'm not sure when it powered down and when it didn't00:06
TheChistosoyes, i know00:06
bigjoolswhat state does it say that node has in maas now?00:06
TheChistosoit starts up and you throw something on there (enough to communicate w/ maas and provide it w/ information so the admin can review and decide to actually proceed)00:07
bigjoolswhat state does it say that node has in maas now?00:07
TheChistosoand then when you accept and commission, it reboots, and at that point the OS is actually installed00:07
TheChistosostatus shows "allocated to sysadmin"00:08
MarlincBut wait if I get it right. If I want MAAS to have another node I just boot it up ones from PXE and MAAS then handles it from then on?00:08
bigjoolsok so your story of events is incorrect somewhere00:08
TheChistosoi'm telling you exactly what i saw00:08
TheChistoso(as i recall it, granted :D )00:08
bigjoolsTheChistoso: if it says "allocated" you clicked something else00:08
bigjoolscan you "ssh ubuntu@<your node>"00:09
bigjoolsbecause you've commissioned it, it shut down, and now you clicked "start"00:09
TheChistosoyes -- i did forget that step00:09
bigjoolsright, so you have an installed node00:10
mwhudsonso is it possible that the node is in fact ready for use?00:10
bigjoolsso ssh to the ubuntu user00:10
MarlincMy node can't be booted up from the network (at least it doesn't seem to work) or another way. What could I do about that? Could the node still work with MAAS00:10
TheChistosoi can't ssh into the machine00:10
bigjoolsMarlinc: without control of PXE/DHCP you cannot use maas00:10
MarlincPXE and DHCP work00:11
bigjoolsTheChistoso: how are you trying to ssh in?00:11
MarlincIt cant start from poweroff state00:11
MarlincUsing WOL00:11
MarlincThats what I mean00:11
bigjoolsMarlinc: ok so just power up manually after maas requests a startup00:12
MarlincOkay great00:12
bigjools(in that order, specifically)00:12
bigjoolsif you try to boot a node that maas doesn't think should be starting, it'll do weird stuff00:12
TheChistosofrom the maas controller, logged in as "sysadmin" (w/ the same account name configured in maas as a super user and w/ the SSH key registered there that corresponds w/ my unix account), i type: ssh ubuntu@<ip of node>00:13
TheChistosoi've also tried it on port 2181...00:14
bigjoolsdid you add your public ssh key to the sysadmin account in maas *before* starting up the node?00:14
bigjoolsfwiw, juju makes this stuff much easier00:14
TheChistosoof course i can't be sure that's the ip of the machine b/c i can't configure it to use a static ip00:14
bigjoolsno, you can't because MAAS manages the DNS00:15
TheChistosoi'd love to use juju w/ this -- but i can't get nodes working in order to use juju w/ it (c:00:15
bigjoolsyou're looking at the problem incorrectly00:15
bigjoolsyou have got nodes working, you just think you don't00:15
bigjoolsit's a cloud-like resource, not an installer00:16
bigjoolsonce nodes are at "ready" you just set the API key in environments.yaml etc and then you can use juju00:16
bigjoolsare you using maas to manage DNS?00:17
MarlincShould a MAAS node have PXE boot as primary boot location?00:17
TheChistosoyes maas is managing dns00:17
bigjoolsMarlinc: you mean in the BIOS?  yes00:17
MarlincOkay00:18
TheChistosoi understand how it's supposed to work00:18
bigjoolsTheChistoso: ok so just resolve through there and ignore the IP - the DNS  entry will be the same as the node's name in the MAAS UI00:18
bigjoolsthe zone file will be named after the cluster's name00:18
TheChistosowell nslookup doesn't find it - looking at resolv.conf shows that you're not setting up the local machine to use itself for DNS name resolution00:20
bigjoolsTheChistoso: no, you have to do that00:22
bigjoolsmaas cannot set up resolv.conf for machines it doesn't boot, it's set via DHCP00:23
TheChistosoit can set the machine it's running on's network interfaces00:24
TheChistosoi'm doing these commands from the same machine that maas is running on00:24
bigjoolsthat machine is not managed by maas00:24
TheChistosoat any rate -- i added 127.0.0.1 to /etc/network/interfaces, restarted networking, and now i can ssh into the machine00:25
TheChistosoyou would think that maas itself would want to use its own DNS services (c:00:25
bigjoolsI just explained why it's how it is00:25
TheChistosoi understand what you said -- but i simply disagree that maas shouldn't use its own DNS service to resolve names locally00:26
bigjoolsI think you don't understand00:27
bigjoolsbut it;s working so goofd00:27
bigjoolsgood00:27
TheChistosowell please explain -- if i truly don't understand something, then a little education would be good (c:00:27
bigjoolsI explained above00:28
bigjools"maas cannot set up resolv.conf for machines it doesn't boot, it's set via DHCP"00:28
TheChistosoyes i understand all of that00:28
mwhudsoni think i would have been pretty upset if maas had started mutilating the networking of the host i installed it on00:28
bigjoolsso you understand why you need to set resolv.conf yourself?00:28
TheChistosobut when you install maas, you could configure the local machine to resolve against itself00:29
mwhudson(even if i was using maas-dns, which i'm not)00:29
TheChistosoat the very least, it would make sense to document this00:29
bigjoolsmaas should not mess with networking on non-managed machines00:29
bigjoolsI agree with the doc00:29
bigjoolswe should change it00:29
bigjoolssince you had trouble working this out00:30
TheChistosoit's certainly not immediately obvoius that the reason why something can't transition to ready is that nameservers aren't configured properly00:30
TheChistoso(assuming this is the ultimate culprit)00:31
bigjoolsyou are using the state names incorrectly00:31
bigjoolsready is when something is available in the pool00:31
bigjoolsnot something that's deployed00:31
bigjoolsand nameservers configuration has nothing to do with state transitions00:32
mwhudsonTheChistoso: there is no state transition in maas when the node is installed and ready for use00:32
TheChistosothe maas ui shows the node's deployed -- so what's the next state called that i want to get it to?00:32
MarlincI think MAAS isn't a toy but really it feels like it. Especially because I've never worked with PXE and never with machines that boot automatically when needed. Really this is just awesome00:32
mwhudsonit's just "allocated"00:32
MarlincI just connected another machine tot the network. Set PXE as default boot mode and enabled WOL00:32
MarlincAnd it works00:33
bigjoolsit transitions from "ready" to "allocated" when someone requests a node00:33
TheChistosomwhudson: the first screen (i have just 1 node) says "1 node deployed"00:33
bigjoolsMarlinc: great!00:33
bigjoolsTheChistoso: look at the detail node list00:33
TheChistosothe entire pie chart is blue00:33
TheChistosoyes -- that says "allocated"00:33
TheChistososo you need to get your verbage consistent00:33
bigjoolsthe pie chart is geared to managing 1000s of nodes at once00:33
mwhudsoneh, maybe the node list and the pie chart could use the same words...00:33
bigjoolsyeah, that's inconsistent00:34
* bigjools files a bug00:34
MarlincWow WOL is just magic00:34
bigjoolsMarlinc: WoL is a hack, you can't power down using it00:35
MarlincWell okay thats true00:35
bigjoolsit suffices for basic testing00:35
TheChistosookay, so what would my next steps be?00:36
TheChistosoi've defined .juju/environments.yaml and i ran juju bootstrap and it tells me that no matching nodes are available00:36
MarlincMmm the second machine doesn't do much but I'm thinking it is a hardware problem because it is a old computer00:36
bigjoolsTheChistoso: I presume you only have one node commissioned and it's already in use?00:37
TheChistosoby "in use" do you mean allocated to a user? then yes (although i'm fuzzy on how a node is allocated to a user -- it is tied to the user that accepts, commissions, and starts the node?)00:38
bigjoolsTheChistoso: no, it's the user who "starts" it00:38
TheChistoso(*is it)00:38
TheChistosookay -- that makes sense00:38
bigjoolsonly admins can accept for commissioning00:38
TheChistoso(minor feature request, although perhaps it already exists -- auto-accept, commission, and start, assigning it to a default user)00:39
bigjoolsthat won't be accepted as a feature00:39
bigjoolsit's not designed to work like that00:39
bigjoolsyou need to think cloud-like00:39
MarlincIt looks like the DNS is not working the way its supposed to work: 2013-05-02 02:39:13,994 ERROR Invalid host for SSH forwarding: ssh: Could not resolve hostname fqehy.master: No such file or director00:40
MarlincIt is managed at least it should be00:40
MarlincMy laptop is using the MAAS server's DNS server00:40
bigjoolswhere's that error from?00:41
MarlincJuju00:41
TheChistososince these are meant to serve physical machines, makes sense to me that if you've racked, cabled, and powered it up, then you want to commission it.00:41
MarlincWhen I try to run juju status00:41
bigjoolsTheChistoso: the commissioning process is more complicated than that in a DC, often people will want to do burn-ins, update firmware etc.00:42
bigjoolsMarlinc: can you manually look up that host?00:42
MarlincNope00:42
MarlincOr well00:42
MarlincIt doesn't work00:42
TheChistosowell my suggestion is for those people who don't want to babysit the process :D00:43
bigjoolscan you check to see if it's present in the zone file00:43
MarlincLet me take a look00:43
bigjoolsTheChistoso: we'll add a mass-accept at some point00:43
TheChistosothat would be better :D00:43
MarlincWhere's it stored?00:43
bigjoolsMarlinc: under /var/ib/maas IIRC00:43
TheChistosookay, so do you think that i'm at the point where i should be able to use juju?00:44
bigjoolsTheChistoso: yep00:44
bigjoolsyou need to release that node00:44
TheChistosohow do i do that?00:44
bigjoolssadly there's no way in the UI of doing it (don't ask...), you need to use maas-cli00:44
TheChistosoah...00:44
MarlincMm there's nothing related to DNS00:45
bigjoolsmaas-cli does API calls00:45
TheChistosocan you point this out in the documentation? b/c i did not see it. gotta have my eyes checked...00:45
bigjoolsTheChistoso: I think we have gaps in the docs00:45
TheChistosothis seems like a major one00:45
bigjoolswhich bit?00:45
TheChistosothat to actually use a node w/ juju you have to run a command00:46
bigjoolsyou don't00:46
TheChistoso?00:46
TheChistosowell i'm confused (c:00:46
bigjoolsjuju will use available nodes on maas00:47
bigjoolsbut you don't have any available00:47
bigjoolsbecause you started one manually already00:47
TheChistosoyou'll have to slow down there b/c i'm thoroughly confused00:47
bigjoolsbasically - just don't use "Start" in the UI00:47
TheChistosoi was just going to ask that00:48
bigjoolsit's completely unnecessary00:48
bigjoolsjuju manages everything00:48
bigjoolseven the SSH key00:48
TheChistosois that in the docs as well?00:48
bigjoolsit's in juju docs I expect00:48
TheChistosoit's natural, i think, to hit a "start" button when you see it (c:00:48
bigjoolsbut there's a section on juju in the maas docs IIRC00:48
TheChistosoi don't recall reading anything that says "don't press that button!"00:48
bigjoolsI think the problem here is that you've not really understood how it works from a higher level.  Maybe we need a doc section for that.00:49
TheChistosominor feature request: add a label or help text (or something) next to the button in maas when it says 'start" to prevent this from happening00:49
MarlincMmm.. None of the zone files contain any reference to the node bigjools00:50
TheChistosoi understand how juju is supposed to work (at a high level), but these are small details. c'mon now -- "don't hit start if you want to use it w/ juju"? that seems pretty confusing to anybody starting out.00:50
bigjoolsMarlinc: ok that means that something went wrong with parsing the dhcp leases00:51
bigjoolsTheChistoso: I think it's only confusing if you don't understand resource allocation concepts in maas00:51
bigjoolsMarlinc: please check the celery.log00:51
MarlincSure00:52
bigjoolsTheChistoso: which boils down to a higher-level doc that we need to explain these concepts00:52
TheChistosogiven the bad documentation and the fact that i don't work on the product, i don't think it's hard to see why not00:52
bigjoolsthis support stuff is largely done on an "as best" basis for non-paying customers00:53
TheChistosoi assumed juju worked w/ already running systems, simply orchestrating services atop already-installed OSes00:53
MarlincOkay the're one error in there but it isn't very clear http://pastebin.ubuntu.com/5624546/00:53
bigjoolsI think you need to read the juju docs00:53
TheChistosoyour paying customers don't read docs then, eh? (c:00:53
bigjoolsTheChistoso: no, they pay for consultants00:53
TheChistosohave you read your docs recently?00:53
bigjoolsYou're welcome for the help00:54
bigjoolsMarlinc: aha, that's the problem00:54
TheChistosoi do thank you for your help -- i'm not trying to be ungrateful :/00:54
bigjoolsMarlinc: well, an indication of the problem00:54
TheChistosobut it does seem likely that a newbie (such as myself) has read the docs more recently than somebody working on the product00:54
MarlincTrue00:54
bigjoolsTheChistoso: that's very likely00:55
bigjoolsthe product evolves and things get missed, but the vast majority of people don't have problems00:55
TheChistososo that experienmced somebody is trying to warn you that it's confusing.00:55
TheChistosohow do you know that? my previous attempt had me throwing my hands in the air and moving on to other solutions00:56
TheChistosoiow, you don't know how many people get frustrated w/ the product and leave w/o saying a word00:56
bigjoolsI know from speaking to many people they are happy with it. There will always be people with problems though - this is a complicated product solving a complicated problem.00:57
TheChistosoi know bind, dnsmasq, dhcp, cobbler, pxe, tftp, etc. and i found things confusing00:57
MarlincThere is a bug report with the same error but it is pretty old and I don't know if its still relevant00:57
bigjoolsMarlinc: are there log entries talking about leases?00:57
TheChistosoperhaps those folks have consultants who know the product and have been using it for a while? (c:00:57
MarlincWell in my syslog00:57
bigjoolsMarlinc: specifically in the celery.log00:58
Marlinc[2013-05-02 02:57:33,775: INFO/Beat] Scheduler: Sending due task provisioningserver.tasks.upload_dhcp_leases00:58
bigjoolsTheChistoso: like I said, it's best effort, like all OSS projects.00:58
bigjoolsMarlinc: ok cool, one sec00:58
Marlinc[2013-05-02 02:57:33,780: INFO/MainProcess] Got task from broker: provisioningserver.tasks.upload_dhcp_leases[****]00:58
MarlincThese things?00:58
MarlincOkay nice00:58
TheChistosois maas not backed by canonical?00:58
bigjoolsit is00:58
TheChistososo you have real dollars being thrown at it w/ staff dedicating at least some partial amount of their time to it. that's a great thing! now as an open source user of your product, i'm just trying to warn you that your documentation is lacking and you could be turning away users without knowing it.01:00
bigjoolsMarlinc: can you see your node's MAC/IP in the leases file?01:00
MarlincIt is01:01
bigjoolsTheChistoso: I'm sorry it wasn't up to scratch for you - people will try to make it better01:01
TheChistosookay, so what are my options at this point? can i "un-start" (or "un-use") it so i can use it from juju?01:01
bigjoolsMarlinc: can you look at the celery-region log for errors01:01
bigjoolsTheChistoso: look at maas-cli01:01
bigjoolsit has a release command01:02
MarlincThere are bigjools http://pastebin.ubuntu.com/5624558/01:03
bigjoolsMarlinc: did you install maas-dns?01:03
bigjoolsand maas-dhcp01:03
MarlincYes I did it is running because my laptop is using it right now01:03
MarlincAnd it is using the dhcp too01:03
bigjoolsweird01:03
MarlincI did need to edit the /etc/network/interfaces file in order to make the DHCP work01:04
bigjoolsis maas in /etc/sudoers?01:04
bigjoolsis "rndc" available?01:04
Marlincrndc is available01:04
MarlincBut maas is not in the sudoers file01:04
bigjoolsmmmm01:04
bigjoolswhich version of maas are you using?01:05
MarlincI've used the Ubuntu 13.04 install01:05
bigjoolsok01:05
bigjoolsmaas should be in sudoers anyway, which expains the other "omshell" failure01:06
bigjoolsnot sure why it's not there01:06
MarlincWell I don't know either01:06
MarlincJust add it or?01:06
bigjoolspackaging should have added it01:07
bigjoolsone sec01:07
Marlinck01:08
TheChistosookay awesome -- pie chart is now green showing "1 node queued" and the node list shows its status as "ready"01:10
TheChistososo at this point i can "juju bootstrap"?01:10
MarlincYes01:10
TheChistosoawesome!01:10
Marlincenvironments.yaml is setup?01:10
MarlincOr you could get the same problem as me :P the hostname's of nodes are not resolving01:11
TheChistosoi ran juju bootstrap and the node is now rebooting01:12
bigjoolsMarlinc: do you have a /etc/sudoers.d/99-maas-sudoers ?01:14
TheChistosoMarlinc: can you provide more information wrt your environment? network (including network mask), are these machines on the same L2 network, etc.01:14
bigjoolshis dns is not resolving because the node is not in the zone file01:15
MarlincAh that is available01:15
bigjoolsthere are a few causes for that01:15
MarlincI don't think it is my network setup01:15
bigjoolsMarlinc: have you got zone files in /etc/bind/maas/01:16
TheChistosowell bigjools has been working on the issue longer than i've paid attention so probably best for me to follow his line of thinking01:16
Marlincnamed.conf.maas  named.conf.rndc.maas  rndc.conf.maas  zone.1.168.192.in-addr.arpa  zone.2.168.192.in-addr.arpa  zone.master01:16
bigjoolsis your node in zone.master?01:17
bigjoolsthere should be a CNAME if so01:17
MarlincNope01:17
TheChistosohmmm -- well it prompted for the partitioning scheme again01:17
bigjoolsTheChistoso: I'd ask in #ubuntu-server about that, I've never had that01:17
MarlincIt is not bigjools :p01:20
bigjoolsMarlinc: one secx01:20
Marlincokay :)01:20
bigjoolsMarlinc: http://pastebin.ubuntu.com/5624592/01:21
bigjoolstry that and see what output you get01:21
MarlincOkay01:21
MarlincThe output is good01:22
Marlincip->mac mappings01:22
bigjoolsyou see your node?01:22
MarlincYep01:22
bigjoolsok so something went wrong where it writes out the zone file01:22
bigjoolslet's try: sudo service apache2 restart01:23
MarlincMmm okay01:24
MarlincRestarted01:24
bigjoolsit will reload the wsgi for maas which causes a job to rewrite the zone file01:24
bigjoolsso check the zone file(s) again01:24
bigjoolsand check celery-region.log to see if anything went wrong since you restarted01:25
MarlincNo new output in that log01:26
MarlincAnd it is still in none of the bind maas files01:26
bigjoolshmmm01:27
bigjoolscan you try renaming the node01:27
bigjoolsands watch the log01:27
MarlincSure01:28
MarlincIt did a 'upload_dhcp_release'01:29
MarlincIt did a 'upload_dhcp_leases'01:29
Marlinc*01:29
bigjoolsyeah that runs periodically01:29
MarlincOther then that nothing01:29
bigjoolsarey you looking in celery-region ?01:32
MarlincWell tailed both of them01:32
Marlinc[2013-05-02 02:05:34,807: INFO/MainProcess] Task provisioningserver.tasks.rndc_command[6499426a-eb2c-4b30-bfbc-0314632cef2f] retry: None01:32
MarlincNone01:32
MarlincIs the last01:32
bigjoolsI'm not sure what's going on, there are no errors but the file is not getting written01:37
MarlincI'll reboot the thing01:38
MarlincMaybe something is not working01:38
MarlincNow01:42
Marlinc[2013-05-02 03:40:27,551: INFO/MainProcess] Task provisioningserver.tasks.rndc_command[6499426a-eb2c-4b30-bfbc-0314632cef2f] retry: None01:42
MarlincNone01:42
MarlincRuns without issues01:42
MarlincBut there's still no entry01:43
Marlincbigjools, ^01:49
bigjoolsyeah#01:49
bigjoolstrying to think01:49
bigjoolssomeone else will be around soon that may have more ideas01:49
MarlincOkay01:49
MarlincWhat is soon? Because it is well time to sleep01:49
MarlincFor some hours already though01:50
MarlincUsage: time [-apvV] [-f format] [-o file] [--append] [--verbose]01:50
Marlinc       [--portability] [--format=format] [--output=file] [--version]01:50
Marlinc       [--quiet] [--help] command [arg...]01:50
Marlincdo mei  2 03:50:07 CEST 201301:50
bigjools!01:50
bigjoolsthere's a guy near your TZ and one about to start, so just ping later01:51
MarlincOkay01:51
MarlincI'll see tomorrow01:51
MarlincGood night01:51
bigjoolsgood night01:52
roaksoaxbigjools: howdy! just wanted to let you know that it seems there's not gonna be an sru anytime soon03:04
bigjoolsyay03:04
roaksoaxbigjools: MIR'ing the dependencies is not as easy as it seems, and will probably require TB intervention, meaning, request the TB to provide a exception for those dependencies03:05
bigjoolsjoy03:05
roaksoaxyep03:05
Dr{Who}Hmm. i changed the IP of my 13.04 maas box and it needs some reconfigureing but I cant figure out what to run or edit. dpkg-reconfigure maas does not seem do do anything on this release.04:34
bigjoolsDr{Who}: it's all done in the UI04:51
bigjoolsedit the cluster04:51
TheChistosookay, so i added a new machine to maas. i didn't hit "start node" yet. the machine is currently powered off. i should be able to just use it automatically from juju, correct?05:48
TheChistosoe.g. i want to just do "juju deploy mysql"05:48
TheChistosoit picks the right machine, but i don't see it turning on and installing the OS as expected05:48
TheChistosoany maas+juju users present?06:17
shangbigjools: ping06:44
shangbigjools: last time I check,the new maas still haven't been backported to 12.04 yet. Has this changed since?06:44
shangfew weeks ago06:44
TheChistososo, uh, anybody? :D07:04
MarlincHello08:06
MarlincMy Juju only finds one node. When I try to add a unit it says "ProviderError: No matching node is available." there is another node ready11:51
MarlincWhat could I do about this?11:51
rbasakbug 1064291 perhaps?11:56
ubot5bug 1064291 in juju "Default constraints make no sense on MAAS" [Undecided,New] https://launchpad.net/bugs/106429111:56
rbasakBut that's only one possibility11:57
rbasakI don't remember how to tell juju to use no constraints at all, but if you find out please add it to the bug.11:57
rbasakIt'd be nice to document the workaround.11:57
MarlincAh so.. I've specified i386 and now it works11:58
MarlincBut let me guess11:59
MarlincNow only 32 bit nodes will work11:59
melmothi m not sure how to remove a global constraint for arch, but for the node name, i use juju "set-constraints maas-name="11:59
rbasakYou can change the default constraints11:59
melmoththen i double check it s set to NULL again with juju get-constraint11:59
rbasakMarlinc: please mark bug 1064291 as "affects me too"12:01
ubot5bug 1064291 in juju "Default constraints make no sense on MAAS" [Undecided,New] https://launchpad.net/bugs/106429112:01
MarlincDone12:01
rbasakThanks!12:01
MarlincSo it looks like I'm not the only one12:01
MarlincIs it possible to allow multiple architectures using a constraint?12:03
rbasakI'm not sure. #juju might have more people who can help.12:04
MarlincMAAS should boot a machine when Juju requests it right?12:43
rbasakCorrect. Not only boot, but install.12:45
rbasak(thus it takes a while)12:45
MarlincWell the last works12:47
MarlincBut it is no longer starting the machine12:47
MarlincAh now it works12:49
MarlincThere's a little issue I think12:55
MarlincOne my machine's has needs a binary blob for the NIC. It can't boot connect without so it cannot install fully automatically12:56
rbasakI don't think maas will be able to support that case any time soon. You should be able to hack it though, by customizing the preseed.13:00
rbasakAlthough it wohn't be able to fetch the preseed. Hmm.13:00
rbasakIt can still be done. Perhaps by hacking the installer initrd. Perhaps more trouble than it's worth. I can't think of a non-trivial way to do it off the top of my head.13:01
MarlincMmm I kept the USB in the machine13:01
MarlincNow it works13:01
MarlincI guess I need to keep in the machine lol13:01
TeduardoHey is anyone around here that knows MAAS/JUJU?13:47
TeduardoI'm trying to figure something out; and that is.. if MAAS doesn't know the hardware specifications of the boxes it's managing how can I know whether certain juju charms are approriate to install?13:48
Teduardoerr, sorry how can IT know13:48
mgzit does know, see http://maas.ubuntu.com/docs/13:49
mgzsee particularly the tags section13:50
Teduardoah, when I login to maas it tells me all of my 4 core VMware machines have 32 cores13:51
mgzpresumably the underlyinf hardware has 32 cores?13:52
Teduardonope, it has 8 cores and 16 threads13:52
mgzanyway, you can look at the lshw output and #1 file a bug with it attached, #2 create your own tag for the bits you care about13:53
=== kentb-out is now known as kentb
Dr{Wh0}Q. I am trying to setup a multi-homed server for my maas box so I can manage it from my trusted network. I setup maas from 13.04 and then changed the trusted interface ip and now some pages still have links to the original dhcp'd ip it got at boot. How can i get it to reload or reconfigure itself?16:38
roaksoaxDr{Wh0}: sudo dpkg-reconfigure maas-region-controller16:42
roaksoaxDr/win 1416:42
=== matsubara is now known as matsubara-lunch
Dr{Wh0}so I did try that and it didnt seem to fix some links on the pages. going to try again.16:44
Dr{Wh0}nope. same thing the main page has a link on it with a warning "Some cluster controllers are missing boot images. Either the import task has not been initiated (for each cluster, the task must be initiated by hand the first time), or the import task failed. "16:44
Dr{Wh0}this link goes to the wrong ip.16:44
Dr{Wh0}not gone through all the code still learning it but it seems to be here in api.py "absolute_reverse("settings")"16:46
=== kentb is now known as kentb-afk
roaksoaxDr{Wh0}: ah so you need to sudo dpkg-reconfigure maas-cluster-controller on all the nodes that are the cluster controllers17:07
TheChistosoi'm using maas+juju. i added a new machine and it's shown as "ready" in the node list. when i try and deploy mysql, it never picks up the new machine17:26
TheChistosoi started the deploy last night and 10 hours later juju status is still showing it as "pending"17:26
roaksoaxTheChistoso: will first you need to verify that the bootstrap node is up and running17:51
=== matsubara-lunch is now known as matsubara
Dr{Who}roaksoax: sorry got disconnected. I dont have any other systems just this one MAAS system to start with.18:50
TheChistoso|2roaksoax: i just got back to this. my bootstrap node is up and running fine.20:57
TheChistoso|2i resolved my issue -- issue was that my juju bootstrap node was running precise w/ a known bug where you need to include the port # in the maas-server entry in your environments.yaml for juju22:01
Dr{Who}Well I have even grep'ed the entire hard drive for that ip address and other than a few pg files I dont see it anyplace yet the MAAS ui still knows about it.22:33
MarlincHow can I change the port of the MAAS interface?22:40
MarlincTo 8080 for example22:40
mwhudsonediting /etc/apache2/conf.d/mass.conf i assume?22:41
mwhudsonnote: i don't know if there is a better wya22:41
MarlincMm okay22:44
mwhudsonroaksoax: ping23:14
Dr{Who}Q. the /settings/ page has "Some cluster controllers are missing boot images. Either the import task has not been initiated (for each cluster, the task must be initiated by hand the first time), or the import task failed." but the url link on this line is to the wrong IP. it was the IP the box was initially setup on dhcp. Its now static. I have yet to find how to get the system to change this url. Ideas? I already tried dpkg-reconfigure maas-cluster-23:55
Dr{Who}controller . Is this a bug?23:55
bigjoolsedit the cluster23:55
Dr{Who}ok how do I do that. I only have 1 box so far this one MAAS box a 13.04 installed with "MAAS" as the install option.23:57
Dr{Who}ok found the cluster edit page in the ui looking now. done see any ip's yet.23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!