| === wojdev_ is now known as wojdev | ||
| === Tribaal_ is now known as Tribaal | ||
| roaksoax | mpontillo: you dont sleep ? :) | 10:17 |
|---|---|---|
| mpontillo | good morning ;-) not today.. I keep thinking I should...! | 10:18 |
| mpontillo | (did you just wake up or do you stay up that late?) | 10:18 |
| roaksoax | mpontillo: haha its 2 for you isnt it? you should go get some rest :) | 10:18 |
| roaksoax | mpontillo: i just woke up | 10:19 |
| mpontillo | roaksoax: 5am is early for me, but I'm trying to think of how to shift my hours for optimal communication. I seem to do better staying up late than waking up early | 10:24 |
| roaksoax | mpontillo: yeah. we can talk about that later, although the only thing i could.offer is a pontential.early start | 10:25 |
| roaksoax | mpontillo: but we can talk later | 10:25 |
| roaksoax | mpontillo: go get some rest :) | 10:25 |
| mpontillo | will do - night all =) | 10:25 |
| dimitern | mpontillo, hey, welcome to the team! :) | 10:48 |
| gadago | hi | 12:27 |
| gadago | wonder if anyone can help... | 12:27 |
| gadago | I'm just trying to get started with maas, and have been following the guide here https://maas.ubuntu.com/docs/index.html | 12:28 |
| gadago | I've got to the point where my node PCE boots and appears to go through the commissioning stage | 12:29 |
| gadago | it now has a status of ready in the nodes list, but upon booting it, it just seems to go through the enlisting process again, then shuts down | 12:29 |
| gadago | now I'm stuck in that cycle and not sure what to do | 12:29 |
| gadago | could anyone help? | 12:30 |
| dimitern | gadago, what are you trying to do? | 12:37 |
| dimitern | gadago, once the node is in ready state, you can use it with juju or something else, but you need to acquire it via the MAAS API (juju will that for you); if you simply try to boot it, it won't work, as maas does not know you want to allocate this node and thinks it needs to re-enlist it | 12:38 |
| gadago | dimitern, I think the issue is cause I didn't allocate a SSH key to it yet | 12:39 |
| gadago | it seems to be doing something now | 12:40 |
| dimitern | gadago, you also need to allocate the node to yourself in maas, so it becomes "Allocated to myuser", rather than ready | 12:40 |
| gadago | I'm trying to understand the concept of maas... | 12:40 |
| dimitern | then you can safely boot it and maas won't interfere | 12:40 |
| gadago | will the server always pxe boot, or will it install one of the images to the local disk? | 12:41 |
| gadago | it seems to be going through the ubuntu installation process at the moment. | 12:42 |
| gadago | the ultimate objective here is to build an openstack environment, so I'm just trying to make sure I go in the right direction | 12:43 |
| dimitern | gadago, so the initial phase of discovery, when maas probes what nodes are on the network, via pxe booting, commissioning, etc. ends up with a node being "ready" to allocate for workloads | 12:45 |
| dimitern | gadago, then, when it's ready and allocated, you can start it via maas, which will trigger the machine to boot the image you requested (via the MAAS) api, and install that cleanly on the first boot | 12:46 |
| dimitern | gadago, then, maas releases the control to that machine to you to do whatever you see fit; rebooting the node after that process has completed will cause the node to boot from the local disk rather than the network | 12:47 |
| dimitern | gadago, and finally, when you're done with the node, you deallocate it via maas so it becomes ready again | 12:48 |
| gadago | dimitern, thank you for the explanation | 12:50 |
| gadago | dimitern, could you point me in the direction of where to go to do the openstack part? I'm after a quick-start guide just so I can grasp the basic concepts, bit of a howto if you like | 12:51 |
| dimitern | gadago, how many physical machines are you planing to deploy openstack with maas on? | 12:53 |
| gadago | I have 4 compute nodes, with another virtual environment to be able to set up controller/network nodes etc | 12:54 |
| dimitern | gadago, you could do it on 2 machines (even 1, but that's too extreme) - one for compute (with enough ram to be able to run nodes in kvm containers), one for everything else | 12:56 |
| dimitern | gadago, unfortunately I don't have ready links for how to do that in steps, but if you search for deploying openstack with maas on two machines, there are a bunch of guides | 12:57 |
| dimitern | gadago, also, consider looking into autopilot | 12:57 |
| dimitern | https://insights.ubuntu.com/2014/10/28/introducing-the-canonical-distribution-of-ubuntu-openstack-your-autopilot-for-rapid-customised-openstack-private-cloud-deployment-and-management/ | 12:57 |
| dimitern | you'll need a few more machines I think, but it lets you deploy openstack really easy on maas | 12:58 |
| gadago | dimitern, thank you for your help | 12:58 |
| dimitern | gadago, no worries, I hope you get it working | 12:59 |
| gadago | dimitern, is it best to install openstack (landscape) onto a different server to the maas server? | 13:05 |
| dimitern | gadago, I can't say for sure, but please join #ubuntu-autopilot and I'm sure somebody there can help you further | 13:07 |
| gadago | Looks like it can be a separate machine :) | 13:08 |
| kiko | morning! | 14:47 |
| === medberry is now known as med_ | ||
| === Noob is now known as Guest1765 | ||
| === kiko changed the topic of #maas to: MAAS: Ubuntu's bare-metal provisioning tool | 1.7.1 released: https://bugs.launchpad.net/maas/+milestone/1.7.1 | Docs: http://maas.ubuntu.com/docs1.7/ | Mailing list https://launchpad.net/~maas-devel | ||
| === roadmr is now known as roadmr_afk | ||
| === roadmr_afk is now known as roadmr | ||
| === wojdev_ is now known as wojdev | ||
| === mwenning is now known as mwenning-rr5 | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!