[01:00] <bdx> Quick question concerning nodes with multiple iterfaces....is there a best practice way to have all interfaces brought up after a node is deployed?
[10:43] <kiko> bmorriso, ping?
[12:15] <MassWindows> Hello all. I have a question about Windows and MAAS if I can ?
[12:19] <MassWindows> When I create a boot resource with Windows, I end up with a generated image that can't be deployed with maas -> Could not find kernel image windows/amd64/generic/win2012r2/no-such-image/boot-kernel
[12:20] <MassWindows> on this directory, I have only a root-dd file, which is certainly image content
[12:20] <MassWindows> can you helpme please ?
[13:10] <blideee> Hello guys, is it possible to build a DigitalOcean like service with MAAS and JUJU through an API ?
[13:15] <kiko> blideee, with maas, certainly, and some of our customers have done the same
[13:15] <kiko> blideee, juju would be more of a tool that your users could use to deploy applications to it
[13:16] <kiko> blideee, you'd need to add a few services around maas -- billing, more complex access control and limits
[13:16] <kiko> blideee, keep in mind that it would be more like, say, softlayer, as it would be bare-metal
[13:20] <blideee> Thank you for the advice kiko, one more think could something like this be done without much customization to MAAS or Juju ? -> (  MAAS + Juju -> API -> MyApp )
[13:21] <kiko> blideee, I don't think you'll need to customize maas at all -- you can just use the API and build around it
[13:22] <blideee> Sound amazing! , Thank you again Kiko, have a nice day :)
[13:22] <kiko> blideee, let us know how your testing goes -- have you tried maas out yet?
[13:26] <blideee> I've just checked the website minutes ago, and MAAS looks like the option me and my friends need for out project. I am going to show MAAS to our Tech Ninja :)
[13:26] <blideee> I will for sure :)
[13:35] <dao> where can i found centos boot image for maas 1.7
[13:42] <kiko> blideee, use 1.7.1 for your evaluation, btw
[23:18] <nashville> ok guys... so i have implemented my new server in our hyper-v environment and now when things pxe boot to the server in hyper-v they take FOREVER to load boot-kernel and init whatever the first two things it loads up
[23:19] <nashville> and it never gets registered as a node even if i wait it out completely
[23:19] <nashville> it appears to go through all the steps if i wait it out >20min at least
[23:19] <nashville> but it doesnt come up as a node on the frontend
[23:19] <nashville> anyone experienced anything like this?
[23:32] <catbus1> maas needs to know how to power control the nodes. For KVM VMs, we need to tell MAAS what and where the nodes are first.
[23:32] <catbus1> I have never tried hyper-v.
[23:44] <nashville> im only running the server as a vm in hyper v the node im booting up is a hardware box on the same subnet
[23:44] <nashville> and when it boots it takes FOREVER
[23:45] <nashville> i have this working on a vm on my laptop in the same subnet but for some reason i get this problem when trying it from the hyper-v vm/server
[23:52] <nashville> really pounding my head against the wall right now maybe ill just purge the whole thing and reinstall from the start
[23:52] <nashville> anyone think thats worth a go?