[20:01] <smoser> alexpilotti, around ?
[20:01] <alexpilotti> smoser: hey!
[20:04] <smoser> would you think it possible to install windows via :
[20:04] <smoser>  mkfs.ntfs(some.disk)
[20:04] <smoser>  mount some.disk
[20:04] <smoser>  tar -C moutpoint -Sxvzf my-windows-tarfile.tar.gz
[20:04] <smoser>  fixup_windows(mountpoint)
[20:04] <smoser>  reboot 
[20:05] <alexpilotti> if my-windows-tarfile.tar.gz is a preinstalled copy of WIndows, sure
[20:06] <alexpilotti> it's no different then ghosting a machine
[20:06] <smoser> and fixup_windows() is some amount of things that have to be done
[20:06] <smoser> right.
[20:06] <alexpilotti> not even
[20:06] <alexpilotti> but
[20:06] <alexpilotti> you'll have to consider that you need to expand the file system
[20:06] <alexpilotti> I mean, if your initial image is say, 15 GB
[20:07] <alexpilotti> and your target partition is 20GB
[20:07] <smoser> right. but that could be done in fixup_windows
[20:07] <smoser> right ?
[20:08] <alexpilotti> yep, I though you meant to fix only the MBR / UEFI boot, etc
[20:08] <smoser> well, whatever amount of "fix" required
[20:08] <alexpilotti> if it's an image with cloudbase-init installed you don't even have to care, as partitions get resized automatically on boot
[20:09] <smoser> but those are filesystem images
[20:09] <smoser> could you do the same wtih tar image ?
[20:09] <alexpilotti> can you give some context about where this could be needed?
[20:17] <smoser> mainly just wondering if i could install windows that way.
[20:17] <smoser> doesnt have to support a bunch of smart options, just get installed and boot.
[20:29] <cloud-init-n00b> hello everyone
[20:30] <cloud-init-n00b> i've been trying to get familiar with cloud-init for modifying image installs on openstack
[20:30] <cloud-init-n00b> but i'm having a really hard time getting it to work
[20:30] <cloud-init-n00b> and google is not being too helpful
[20:30] <cloud-init-n00b> i'm trying to do something simple first
[20:31] <cloud-init-n00b> basically create just a user and verify that it is actually being created
[20:31] <cloud-init-n00b> #cloud-config  users:   - default   - name: stack     plain_text_passwd: 'testPass'     lock_passwd: False     sudo: ["ALL=(ALL) NOPASSWD:ALL\nDefaults:stack !requiretty"]     shell: /bin/bash
[20:31] <cloud-init-n00b> whoa bad formatting
[20:32] <smoser> alexpilotti, thanks for your input.
[20:32] <cloud-init-n00b> http://pastebin.com/Nd7H6aHS
[20:32] <cloud-init-n00b> that is what my simple config looks like
[20:32] <cloud-init-n00b> any chance someone could give me a hand
[20:32] <cloud-init-n00b> i'm not sure what it is i'm missing
[20:32] <cloud-init-n00b> :/
[20:33] <alexpilotti> smoser: sorry, got interrupted
[20:33] <alexpilotti> smoser: to be sure, what do you mean with tar image?
[20:34] <alexpilotti> smoser: an OS installer image, like an ISO?
[20:34] <smoser> mount -t ntfs /dev/my-windows-partition /mnt
[20:34] <smoser> tar -C /mnt -Scpzf my-windows-tarball.tar.gz
[20:35] <smoser> umount /mnt
[20:35] <alexpilotti> got it
[20:35] <smoser> cloud-init-n00b, what you have there doesn't look completely unreasonable
[20:36] <smoser> with a recent cloud-init, you can poke around quicker by running the user-groups module manuall
[20:36] <alexpilotti> to be compliant with MSFT support, you need to sysprep the machine
[20:36] <smoser> sudo cloud-init single --frequency=always --name=user-groups
[20:36] <smoser> and then printf debugging that way (or looking at /var/log/cloud-init.log)
[20:36] <alexpilotti> but for a brutal "let's get it running" it works
[20:37] <cloud-init-n00b> smoser, if you have any links on how to run that module manually 
[20:37] <alexpilotti> it's no different than ghosting a physical machine in the end
[20:37] <cloud-init-n00b> i'd be very thankful
[20:37] <cloud-init-n00b> don't mind reading at all :)
[20:37] <smoser> sysprep would be ok. especially if it can be rebooted into sysprep and then rebooted automatically from there.
[20:37] <smoser> cloud-init-n00b, look there ^
[20:37] <smoser> sudo cloud-init single --frequency=always --name=user-groups
[20:38] <alexpilotti> the tricky part is that the only way to do that would be to inhect in the registry a script that would run sysprep on the next boot
[20:38] <alexpilotti> while normally you'd run the machine, sysprep, shutdown, copy the image
[20:39] <alexpilotti> if you can control the machine this way, it's fine
[20:39] <alexpilotti> s/inhect/inject/
[20:41] <cloud-init-n00b> smoser i'm afraid i did not understand your reference, where is it that you advised me to look into (thanks)
[20:44] <smoser> cloud-init-n00b: run: sudo cloud-init single --frequency=always --name=user-groups
[20:44] <smoser> that will re-run the user-groups m odule
[20:44] <smoser> that would read that data you gave
[20:45] <smoser> and then it should log some things to /var/log/cloud-init.log
[20:45] <cloud-init-n00b> got it. i'll give it a run then. Thanks!
[20:47] <cloud-init-n00b> i'm getting an error saying :
[20:47] <cloud-init-n00b> bad command single. use one of ('start', 'start-local')