[02:12] well guys i got it after much pain [02:12] so the problem was i edited the file right as it got grabbed by a node and it corrupted some of the files bytes so i had to remake the file and im back off to the races [02:13] thanks again for the help guys and letting me vent and rage in your channel (sorry) [13:27] heh [16:27] Hey there, why is the minimum amount of server 7 machines? [16:27] for a maas setup.. [16:28] says who? [16:29] aless: it's not, really. At a minimum you need one machine to host maas (assuming you put region and cluster controller in one) [16:29] aless: if you manage virtual instances that should be it (not sure, never done it0 [16:30] jhobbs: i read it the other day on some maas doc-page, i cannot find it currently [16:30] aless: if you want to manage bare metal, then you need at least one other machine to manage :) now if you want to deploy *openstack* then you may need more [16:30] roadmr: why do i need more than two machines for openstack? [16:30] because it want install all the components on a single node? [16:31] aless: last time I tried it, it wanted to install each component in a node. You could consolidate some components, but others make no sense [16:31] aless: for instance, it'd be a good idea to deploy ceph (storage) and compute to different nodes, as they have different requirements [16:32] roadmr: I'm actually looking for an openstack setup on maas so you really got me there. :-) [16:32] aless: :P I suspected it :) [16:32] roadmr: i won't be a heavy ceph user [16:32] backing glance thats about it for now. :-) [16:32] thus i think the things could be mixed at first [16:32] aless: you probably refer to this then: http://www.ubuntu.com/download/cloud/install-ubuntu-openstack [16:33] roadmr: ah that was the one with seven machines [16:33] exactly [16:33] aless: I see. I've never used that installer so I'm not sure whether you could consolidate some services :( [16:34] roadmr: thing is i'd really like to mix the maas controllers and and the openstack controller stuff [16:34] like put it on the same machine [16:34] aless: you can always manually deploy openstack services using juju [16:34] because both are quite statuc [16:34] you might be able to get more help in #juju [16:34] static [16:34] aless: so you can juju deploy --to 1 keystone [16:34] aless: then juju deploy --to 1 ceph [16:35] aless: they'd both go to the same unit. I'm not saying it'd be a good idea though :) [16:35] aless: if you want to deploy openstack on a single machine, then read this: http://ubuntu-cloud-installer.readthedocs.org/en/latest/single-installer.guide.html [16:36] aless: this will apparently deploy the services without maas, using just juju and a local environment where each service lives in an lxc container (think a lightweight VM) [16:36] roadmr: i would put keystone, horizon and the other controllish' stuff on the same node as the MAAS Controllers, because i do think they are quite static in their nature. In contrast to the nova nodes which i'd like to deploy dynamically [16:37] aless: ohh, so that's a complex scenario :) I'd look at the single-installer, that way you could get a good idea of how juju is used to deploy the services. Then you can try replicating that in your topology [16:38] roadmr: is it really? ;-) i just do think that wasting a full pair of server for the openstack controller part, that is apparently only controlling 4 other physical nodes a bit of overkill [16:39] if the number grows to more than four obviously things will change. But for a start this is a little tough. :-) [16:40] roadmr: don't you think? [16:44] aless: I think it's a bit too much, but I'm not an openstack developer, so I don't know if they had a reason for that [16:45] roadmr: its not that openstack forces this on you. OpenStack can be planted on whatever you want. :-) [16:47] aless: true, if you know what you're doing you can deploy the services any way you want. I suppose the 7-machine installer is just pre-designed for a cloud that can later scale, but for people who want it up and running quickly [16:48] its just a little weird because having 7 machines at hand just for testing is rare case i do think. :-) [16:48] aless: what are you deploying [16:49] i can get a full openstack deployment with a single machine in maas [16:50] stokachu: i only want to deploy nova nodes dynamically [16:50] the rest I can manage myself [16:50] you want maas to do that? [16:51] or rather could. :-) and i wonder whether it still make sense then to have maas and juju in place [16:51] stokachu: yep i want maas to take care of the dynamic things which is nova in my case [16:51] maas can boot bare metal or kvm [16:52] there isn't a maas-nova driver yet that can do that [16:52] nova would just create kvm instances on whatever machine it was placed on [16:53] so you'd use maas to deploy a bare metal machine with nova-compute [16:53] then nova would deploy those instances onto that bare metal [16:53] stokachu: i dont want maas to control KVM nodes [16:54] aless: maas would control the machine running nova-compute [16:54] stokachu: i just want it to deploy Ubuntu-Juju-OpenStack-Nova-Compute Nodes onto Baremetal, and register them within Keystone and the likes. :-) [16:55] there isn't a maas<->nova-compute driver for that [16:55] stokachu: that deploys compute nodes and registers them? [16:56] it would deploy bare metal machines that you'd have to register [16:58] but again without a link between nova-maas there would be no way to power down/up the bare metal machines you'd want to deploy to [16:59] you'd have to register the bare metal machines in maas then use nova-compute to deploy kvm's in those machines [17:03] I'm fine with that [17:06] so the easiest way to get maas+juju+openstack is to use our installer [17:07] you'll want to have maas installed first [17:07] http://ubuntu-cloud-installer.readthedocs.org/en/latest/ [17:07] you'll want the multi install option or if you want to use landscape they give you 10 bare metal + 10 virtual seats for free [17:08] stokachu its really that i dont want maas/juju to deploy the openstack controller node(s), everything else can be managed by MAAS and juju [17:08] ok you'll have to deploy the services by hand then [17:08] using juju [17:09] aless: yoou can use the scripts here https://github.com/Ubuntu-Solutions-Engineering/openstack-installer/tree/master/tools/cloud-sh [17:09] to give you an idea [17:10] is "by hand" still possible within the UI? [17:10] what UI? [17:11] /script install buffers [17:11] stokachu: https://maas.ubuntu.com/docs/_images/import-images.png [17:11] Sorry the wrong one i meant landscape UI [17:11] *the [17:12] what are you wanting to do within the landscape ui? [17:14] stokachu deploy the nova nodes onto the metal [17:14] no [17:15] aless: you want the horizon dashboard if you want to deploy compute instances onto the bare metal machines [17:15] stokachu: we're not talking about the same then. :-) [17:15] or if you're wanting to use juju, just juju deploy [17:16] I'll try to the describe the setup that i imagine: [17:16] aless: apparently not b/c you introduced landscape into the equation at the end [17:17] I have 4 physical server currently. The number of them will eventually grow. [17:19] So for an initial setup the plan is to use two of them for maas (controllers) and because using them for maas only is a bit overkill i was looking for other loads to put on them. [17:19] the natural answer was the controller part of openstack, as it will remain static in terms of resource usage for a while. [17:20] why do you need to maas controllers for 4 systems? [17:20] stokachu: because i'm just starting off [17:20] two* [17:21] eventually there may be 20-30 or even more [17:21] just install maas on a single server and let that be the maas controller [17:21] add a second maas controller later on [17:21] stokachu: but that sucks in terms of HA :-) [17:21] heh [17:22] ok so 2 machines are in use for maas controllers, that leaves 2 machines for the rest of openstack [17:22] stokachu: I'm just looking for a way to start small and grow without too much changes over time [17:22] and to be clear im talking about 2 maas controllers, not 2 cloud-controllers [17:22] which is what you are saying right now [17:23] stokachu: what is a cloud controller? [17:23] nova cloud controller [17:24] part of an openstack deployment [17:24] stokachu: ah thats the juju term for it i see [17:25] and that is exactly the problem [17:25] i'd like to mix the maas nodes with the cloud-controller node [17:25] because i assume maas want take up _that_ much resources [17:25] so you'd do juju deploy nova-cloud-controller [17:26] or juju deploy --to lxc:1 nova-cloud-controller [17:26] it'll deploy that to a container on machine 1 [17:26] stokachu: but i cannot do this on same node as the maas controller or can I? [17:26] I mean deploy on the same. [17:26] aless: not unless you create a VM on the maas controller to be managed by maas [17:26] I see i see [17:27] i usually create an additional VM on the maas machine for juju bootstrap to use [17:27] to not waste a entire bare metal [17:27] you could install all of openstack on a single machine [17:27] stokachu: but is my assumption correct that the maas controller will be idling a lot with 2 physical nodes? [17:27] then juju deploy additional cloud controllers to other machines [17:27] or nova-compute [17:28] stokachu: i see clearer now, thanks! [17:28] np [19:18] Bug #1426487 changed: Please ignore me, MAAS rocks [19:18] Launchpad bug 1426487 in MAAS "Please ignore me, MAAS rocks" [Undecided,Invalid] [19:18] kiko: ^^^ [19:38] Bug #1426531: Can't disable auto-image syncing [19:38] Launchpad bug 1426531 in MAAS "Can't disable auto-image syncing" [Undecided,New] === roadmr is now known as roadmr_afk === roadmr_afk is now known as roadmr === lazyPower is now known as lp|away