=== CyberJacob is now known as CyberJacob|Away === menn0_ is now known as menn0 [04:33] how can i know when maas is done importing images ? [04:33] other than watching a web page. [04:33] i run [04:33] maas admin boot-resources import [04:33] but then want to somehow block for "all images imported" [05:23] hey, http://paste.ubuntu.com/9451736/ [05:24] i just ran through that mostly with 14.04 maas. [05:24] reasonably "cut and paste" your way to a virtual-maas setup with 1.7. [05:24] i'd appreciate any one's input on 'HELP' items there. [05:24] roaksoax, ^ [05:26] smoser ill look at that tomorrow im afk [05:26] (from phone) [05:27] on the image side, maas by default imports images [05:27] for trsuty u les you tell it otherwise [05:27] and you can track progress [05:27] blake_r: is the best to answer [05:28] i dont know how to track [05:28] and generally speaking i'd like to tell it not do do that. [05:28] as i probably want daily images and not to bother with other [05:28] that is what i do there. === jgrassler is now known as jgrass === jgrass is now known as jgrassler === frankban__ is now known as frankban [14:01] Hello [14:03] I'd like an hand to help me upload a boot image in maas 1.7. I know it's not the good spot, but can you help me find the good one ? [14:05] circ-user-kfdqZ: a custom boot image? [14:06] smoser: if you wait until "maas admin boot-images read $cluster_uuid" returns a json object with the images then the region and the cluster will have the images [14:06] Yes, more exactly a Windows boot image [14:07] as MAAS 1.7 is supposed to support it [14:10] circ-user-kfdqZ: what version of Windows? [14:18] blake_r At least 2012 to start and first of all understand how it works [14:18] circ-user-kfdqZ: "maas admin boot-resources create name=win2012 architecture=amd64/generic filetype=ddtgz content@=~/path/to/file" [14:19] circ-user-kfdqZ: each version of windows, "win2012", "win2012r2", "win2012hv", "win2012hvr2" [14:19] circ-user-kfdqZ: the windows image needs to be a compressed tar.gz of a dd [14:19] circ-user-kfdqZ: that is why "filetype=ddtgz" [14:20] Ok, at the end tar.gz content is a ISO file ? A bunch of files prepared with DISM ? [14:21] circ-user-kfdqZ: its not an ISO, the dd needs to be a syspreped image of Windows, with cloudbase-init installed [14:21] ok, thanks for all your help [14:53] anyone have an example of a maas new command with power parameters ? === jfarschman is now known as MilesDenver === jfarschman is now known as MilesDenver === roadmr is now known as roadmr_afk [16:33] smoser: to retrieve the power parameters? [16:33] well, i'd like to retrieve them, sure. [16:33] but i'd also like to 'new' to set them. [16:33] ie, i know them and want to load a new system into maas === roadmr_afk is now known as roadmr [16:35] blake_r, http://paste.ubuntu.com/9462288/ [16:35] for virsh i did somethin glike that [16:36] but i dont know how to say "ipmi_v2" [16:37] to power_parameters add [16:37] "power_driver": "LAN_2_0" [16:42] awesome. [16:42] and i just verified, getting them (i'd forgotten you can do that now) [16:42] $ maas $MAASNAME node power-parameters node-367baeb2-807c-11e4-93a8-2c768a4f56ac [16:43] thanks blake_r [16:43] smoser: np === CyberJacob|Away is now known as CyberJacob === matsubara is now known as matsubara-afk === roadmr is now known as roadmr_afk === menn0_ is now known as menn0 === roadmr_afk is now known as roadmr === jfarschman is now known as MilesDenver [21:02] hello, Is thos the good spot to ask question about windows images and MAAS 1.7? [21:06] circ-user-X19Qr_: feel free to ask, if it's not something we can help with, maybe we can point you in the right direction [21:17] roaksoax, blake_r: is it planned to be fixed that when you get into 'failed_deployment' or 'failed_commissioning' you have to do -> broken -> fixed to get it to come back to life? [21:17] i.e., is there a bug number? [21:34] dpb1: is there a bug I can track? [21:34] dpb1: iirc, when ti is in failed commissioning, you can try to commission again [21:34] roaksoax: that is what I was asking you. :) [21:35] dpb1: if not, then it makes sense to make it as broken [21:35] roaksoax: so, AIUI, if you get into failed-deployment or failed-comissioning, you have to mark broken then fixed to attempt the commissioning again [21:36] dpb1: well, i'll need to try to reproduce, but if you file a bug we can track that [21:36] ok [21:36] dpb1: but this is not taht cirtical for 1.7.1 [21:36] nope [21:36] it's a papercut if you get into that state, since a new user doesn't know about this secret to get out of it. :) [21:37] the actual workflow isn't bad, if it were guided in the UI somehow, for instnace [21:38] right [21:38] that makes sense [21:39] you should be able to retry commissioning from that state [21:39] at least the code says you can :) [21:39] heheh [21:40] Beret just hit that you couldn't. I know that if you hit failed-deployment, you have to mark broken-fixed, the same seemed to work for him as well, but I was doing remote hands [21:57] yeah [21:57] i'm pretty sure you can retry commissioning === menn0_ is now known as menn0