[01:30] nturner, theres a lot of variables there. [01:30] curtin basically suports 2 image formats: [01:31] a.) .tar.gz (root tarball of /). curtin in one way or another needs to know a lot about the internels of such a thing... it has to be able to create a filesystem , extract the tar, and then make the thing boot (by grub-install or something) [01:32] b.) dd-img this curtin will just 'dd' to the first disk, and fingers crossed. [01:32] you possibly have something that you can dd, but you possibly have somethign that would have no hope of booting on hardware. === frankban|afk is now known as frankban [10:50] hi [10:51] how can get details from node/details [10:51] client.get(u"nodes/%s/" % node_id, "details") => Giving bson data. how can i parse that data ? === Guest98782 is now known as spammy [12:23] http://askubuntu.com/questions/792289/bson-data-iteration [14:37] jojden, can you send me the raw BSON data somehow? [14:37] jojden, I'm writing an answer and wanted to test [14:37] jojden, I'm kiko@canonical.com if you can mail me the binary output [14:48] Bug #1596483 changed: [2.0b8] Support for IPv6 autoconfigured IP addresses , and avoid confusion with "auto" label [15:42] Bug #1594991 changed: [2.0RC1] MAAS logs every power query as a NodeEvent [15:50] jojden, yo === frankban is now known as frankban|afk === valeech_ is now known as valeech === valeech_ is now known as valeech [18:31] smoser, ok, so the component that actually deploys the image to the hardware is called curtin. I'll see if I can dig up some info on that. [18:34] I'm fairly confident my image will boot on the hardware I have (it's built using a process used to image real hardware via other means, so it has grub configured correctly on the MBR etc.) but I don't know the details of how maas (or curtin) wants the dd-tgz file to be laid out. [18:35] well, i'd start with https://maas.ubuntu.com/docs/os-support.html [18:35] smoser, that's where I started before I came here. I got far enough to realize I lacked key information. :) [18:36] the dd-tgz is a gzip compressed tarball for sparseness of a single file. [18:36] curtin selects which disk it thinks is "first" [18:36] do the tarball has a single member. does that member have to have a specific name? [18:36] (ie, which would be likely to have the bios boot from it) [18:36] s/do/so [18:36] and then uncompress tarball | extract file-to-stdout | dd if=- of=/dev/disk [18:37] i dont think so [18:37] checking [18:37] and by "disk" here we mean the whole disk (e.g. /dev/sda) not some partition? [18:38] it sounds like this is exactly what I had hoped [18:39] http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/view/head:/curtin/commands/block_meta.py#L75 [18:39] nturner, yes a disk. like /dev/sda [18:40] smoser, nice :) that is the kind of specific info i was looking for [18:55] Bug #1597044 opened: maas documentation is incorrect about the maas user home directory [18:58] smoser, thanks for the code pointer. I think I see my first problem (curtin expects the rootfs in the image to have a /curtin directory). [18:58] * nturner modifies the image creation process... [19:25] Bug #1547313 changed: newly enlisted nodes have no power type set. [19:30] mpontillo, I just sent you an email of my draft document [19:59] f1gjam: nice doc! looks like it would make a good blog post =) [20:37] Bug #1595304 changed: add Subnet fails with "Extra data: line 1 column 8 (char 7) [20:47] What is the difference between "Custom" image and "Generated" one? [20:49] found that in the docs, nevermind. Sorry for not looking there first. [21:02] mpontillo, thats what I am looking to do, then put a link on my linkedIn :) [23:34] landscape seem to ha=ng at 77%