[02:12] <nashville> well guys i got it after much pain
[02:12] <nashville> 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] <nashville> thanks again for the help guys and letting me vent and rage in your channel (sorry)
[13:27] <kiko> heh
[16:27] <aless> Hey there, why is the minimum amount of server 7 machines?
[16:27] <aless> for a maas setup..
[16:28] <jhobbs> says who?
[16:29] <roadmr> 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] <roadmr> aless: if you manage virtual instances that should be it (not sure, never done it0
[16:30] <aless> jhobbs: i read it the other day on some maas doc-page, i cannot find it currently
[16:30] <roadmr> 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] <aless> roadmr: why do i need more than two machines for openstack?
[16:30] <aless> because it want install all the components on a single node?
[16:31] <roadmr> 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] <roadmr> 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] <aless> roadmr: I'm actually looking for an openstack setup on maas so you really got me there. :-)
[16:32] <roadmr> aless: :P I suspected it :)
[16:32] <aless> roadmr: i won't be a heavy ceph user
[16:32] <aless> backing glance thats about it for now. :-)
[16:32] <aless> thus i think the things could be mixed at first
[16:32] <roadmr> aless: you probably refer to this then: http://www.ubuntu.com/download/cloud/install-ubuntu-openstack
[16:33] <aless> roadmr: ah that was the one with seven machines
[16:33] <aless> exactly
[16:33] <roadmr> aless: I see. I've never used that installer so I'm not sure whether you could consolidate some services :(
[16:34] <aless> roadmr: thing is i'd really like to mix the maas controllers and and the openstack controller stuff
[16:34] <aless> like put it on the same machine
[16:34] <roadmr> aless: you can always manually deploy openstack services using juju
[16:34] <aless> because both are quite statuc
[16:34] <jhobbs> you might be able to get more help in #juju
[16:34] <aless> static
[16:34] <roadmr> aless: so you can juju deploy --to 1 keystone
[16:34] <roadmr> aless: then juju deploy --to 1 ceph
[16:35] <roadmr> aless: they'd both go to the same unit. I'm not saying it'd be a good idea though :)
[16:35] <roadmr> 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] <roadmr> 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] <aless> 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] <roadmr> 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] <aless> 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] <aless> if the number grows to more than four obviously things will change. But for a start this is a little tough. :-)
[16:40] <aless> roadmr: don't you think?
[16:44] <roadmr> 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] <aless> roadmr: its not that openstack forces this on you. OpenStack can be planted on whatever you want. :-)
[16:47] <roadmr> 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] <aless> its just a little weird because having 7 machines at hand just for testing is rare case i do think. :-)
[16:48] <stokachu> aless: what are you deploying
[16:49] <stokachu> i can get a full openstack deployment with a single machine in maas
[16:50] <aless> stokachu: i only want to deploy nova nodes dynamically
[16:50] <aless> the rest I can manage myself
[16:50] <stokachu> you want maas to do that?
[16:51] <aless> or rather could. :-) and i wonder whether it still make sense then to have maas and juju in place
[16:51] <aless> stokachu: yep i want maas to take care of the dynamic things which is nova in my case
[16:51] <stokachu> maas can boot bare metal or kvm
[16:52] <stokachu> there isn't a maas-nova driver yet that can do that
[16:52] <stokachu> nova would just create kvm instances on whatever machine it was placed on
[16:53] <stokachu> so you'd use maas to deploy a bare metal machine with nova-compute
[16:53] <stokachu> then nova would deploy those instances onto that bare metal
[16:53] <aless> stokachu: i dont want maas to control KVM nodes
[16:54] <stokachu> aless: maas would control the machine running nova-compute
[16:54] <aless> 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] <stokachu> there isn't a maas<->nova-compute driver for that
[16:55] <aless> stokachu: that deploys compute nodes and registers them?
[16:56] <stokachu> it would deploy bare metal machines that you'd have to register
[16:58] <stokachu> 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] <stokachu> you'd have to register the bare metal machines in maas then use nova-compute to deploy kvm's in those machines
[17:03] <aless> I'm fine with that
[17:06] <stokachu> so the easiest way to get maas+juju+openstack is to use our installer
[17:07] <stokachu> you'll want to have maas installed first
[17:07] <stokachu> http://ubuntu-cloud-installer.readthedocs.org/en/latest/
[17:07] <stokachu> 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] <aless> 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] <stokachu> ok you'll have to deploy the services by hand then
[17:08] <stokachu> using juju
[17:09] <stokachu> aless: yoou can use the scripts here https://github.com/Ubuntu-Solutions-Engineering/openstack-installer/tree/master/tools/cloud-sh
[17:09] <stokachu> to give you an idea
[17:10] <aless> is "by hand" still possible within the UI?
[17:10] <stokachu> what UI?
[17:11] <lborda_>  /script install buffers
[17:11] <aless> stokachu: https://maas.ubuntu.com/docs/_images/import-images.png
[17:11] <aless> Sorry the wrong one i meant landscape UI
[17:11] <aless> *the
[17:12] <stokachu> what are you wanting to do within the landscape ui?
[17:14] <aless> stokachu deploy the nova nodes onto the metal
[17:14] <stokachu> no
[17:15] <stokachu> aless: you want the horizon dashboard if you want to deploy compute instances onto the bare metal machines
[17:15] <aless> stokachu: we're not talking about the same then. :-)
[17:15] <stokachu> or if you're wanting to use juju, just juju deploy <charm>
[17:16] <aless> I'll try to the describe the setup that i imagine:
[17:16] <stokachu> aless: apparently not b/c you introduced landscape into the equation at the end
[17:17] <aless> I have 4 physical server currently. The number of them will eventually grow.
[17:19] <aless> 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] <aless> the natural answer was the controller part of openstack, as it will remain static in terms of resource usage for a while.
[17:20] <stokachu> why do you need to maas controllers for 4 systems?
[17:20] <aless> stokachu: because i'm just starting off
[17:20] <stokachu> two*
[17:21] <aless> eventually there may be 20-30 or even more
[17:21] <stokachu> just install maas on a single server and let that be the maas controller
[17:21] <stokachu> add a second maas controller later on
[17:21] <aless> stokachu: but that sucks in terms of HA :-)
[17:21] <stokachu> heh
[17:22] <stokachu> ok so 2 machines are in use for maas controllers, that leaves 2 machines for the rest of openstack
[17:22] <aless> stokachu: I'm just looking for a way to start small and grow without too much changes over time
[17:22] <stokachu> and to be clear im talking about 2 maas controllers, not 2 cloud-controllers
[17:22] <stokachu> which is what you are saying right now
[17:23] <aless> stokachu: what is a cloud controller?
[17:23] <stokachu> nova cloud controller
[17:24] <stokachu> part of an openstack deployment
[17:24] <aless> stokachu: ah thats the juju term for it i see
[17:25] <aless> and that is exactly the problem
[17:25] <aless> i'd like to mix the maas nodes with the cloud-controller node
[17:25] <aless> because i assume maas want take up _that_ much resources
[17:25] <stokachu> so you'd do juju deploy nova-cloud-controller
[17:26] <stokachu> or juju deploy --to lxc:1 nova-cloud-controller
[17:26] <stokachu> it'll deploy that to a container on machine 1
[17:26] <aless> stokachu: but i cannot do this on same node as the maas controller or can I?
[17:26] <aless> I mean deploy on the same.
[17:26] <stokachu> aless: not unless you create a VM on the maas controller to be managed by maas
[17:26] <aless> I see i see
[17:27] <stokachu> i usually create an additional VM on the maas machine for juju bootstrap to use
[17:27] <stokachu> to not waste a entire bare metal
[17:27] <stokachu> you could install all of openstack on a single machine
[17:27] <aless> stokachu: but is my assumption correct that the maas controller will be idling a lot with 2 physical nodes?
[17:27] <stokachu> then juju deploy additional cloud controllers to other machines
[17:27] <stokachu> or nova-compute
[17:28] <aless> stokachu: i see clearer now, thanks!
[17:28] <stokachu> np
[19:18] <mup> Bug #1426487 changed: Please ignore me, MAAS rocks <MAAS:Invalid> <https://launchpad.net/bugs/1426487>
[19:18] <niemeyer> kiko: ^^^
[19:38] <mup> Bug #1426531: Can't disable auto-image syncing <MAAS:New> <https://launchpad.net/bugs/1426531>


[16:31] <ratliff> #startmeeting
[16:31] <meetingology> Meeting started Mon Jun 25 16:31:11 2018 UTC.  The chair is ratliff. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:31] <meetingology> Available commands: action commands idea info link nick
[16:31] <ratliff> The meeting agenda can be found at:
[16:31] <ratliff> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:32] <ratliff> [TOPIC] Announcements
[16:32] <ratliff> We welcome Alex Murray (amurray) to the Ubuntu Security Team today! Welcome Alex, we are thrilled that you are joining us to help continue improving security for Ubuntu users!
[16:32] <ratliff> The Ubuntu Security team is hiring. See https://grnh.se/8c0a6c1f1 for more details.
[16:32] <sbeattie> welcome ammuray!
[16:33] <jdstrand> welcome amurray` !
[16:33] <leosilva> welcome amurray` !!!
[16:33] <sarnold> welcome amurray` !!!!
[16:34] <ratliff> Any more !!!!! of delight? :)
[16:34] <leosilva> hehe
[16:34] <ratliff> [TOPIC] Weekly stand-up report
[16:34] <ratliff> jdstrand: you're up
[16:34] <ratliff> jdstrand: welcome back from vacation!
[16:34] <jdstrand> thanks!
[16:34] <jdstrand> This week I plan to work on:
[16:34] <jdstrand> * catching up on email, irc from last week
[16:34] <jdstrand> * snapd PR reviews
[16:34] <jdstrand> * follow up with Tyler on unsquashfs issue (ie, work on re-enabling resquashfs enforcement)
[16:34] <jdstrand> * adjust snap-confine to always use a device cgroup
[16:34] <jdstrand> * pick up review-tools snap USNs phase1/part ii work as have time
[16:35] <jdstrand> I'm not at all caught up on email yet, but I think sbeattie is up next
[16:35] <sbeattie> yep
[16:35] <sbeattie> I'm on bug triage this week
[16:35] <sbeattie> I have some kernel signoffs to do, and some kernel qrt test failures to look at
[16:36] <sbeattie> I'm working on finishing up the conversion of the cve-tracker to git
[16:36] <sbeattie> I have an internal project I'm working on
[16:37] <sbeattie> I also need to make some upcoming travel arrangements.
[16:37] <sbeattie> that's likely it for me.
[16:37] <sbeattie> no jj today, so.... sarnold? I think you're up?
[16:38] <sarnold> I'm in the happy place this week, working down the MIRs, and perhaps most likely to interact with amurray` in his mornings
[16:39] <sarnold> the libfprintd codebase is very trusting of input from the hardware. I'd like to file upstream bugs for all the cases where If eel it's *too* trusting. it's unlikely to get traction but still, I'm already here
[16:39] <sarnold> that's it for me, chrisccoulson?
[16:39] <chrisccoulson> I've got firefox updates this week
[16:40] <chrisccoulson> And I also need to update rust to 1.27
[16:40] <chrisccoulson> So that will probably be it for me, although I hope not
[16:40] <chrisccoulson> that's me done
[16:41] <ratliff> I'm on CVE triage this week.
[16:41] <ratliff> I will still be focused on internal work this week.
[16:41] <ratliff> leosilva: on to you
[16:41] <leosilva> I'm in the happy place this week :)
[16:42] <leosilva> I have an openssl to USN, but I'm postoning it since Marc will USN his openssl soon.
[16:42] <leosilva> Other than that I'm cve-researching hunting pkgs to update
[16:42] <leosilva> ratliff: it's back to you
[16:42] <ratliff> thanks!
[16:42] <ratliff> [TOPIC] Highlighted packages
[16:42] <ratliff> The Ubuntu Security team suggests that contributors look into merging Debian security updates in community-supported packages. If you would like to help Ubuntu but are not sure where to start, this is a great way to do so.
[16:43] <ratliff> See http://people.canonical.com/~ubuntu-security/d2u/ for available merges and https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details on preparing Ubuntu security updates. If you have any questions, feel free to ask in #ubuntu-hardened. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[16:43] <ratliff> [TOPIC] Miscellaneous and Questions
[16:43] <ratliff> Does anyone have any other questions or items to discuss?
[16:45] <ratliff> jdstrand, sbeattie, sarnold, chrisccoulson, leosilva: Thanks!
[16:45] <ratliff> #endmeeting
[16:45] <meetingology> Meeting ended Mon Jun 25 16:45:09 2018 UTC.
[16:45] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-06-25-16.31.moin.txt
[16:45] <leosilva> thanks ratliff!
[16:45] <sarnold> thanks ratliff!
[16:45] <sbeattie> ratliff: thanks!
[16:47] <jdstrand> ratliff: thanks! :)