Saturday, 2016-06-04

harlowja'The server name validator intercepts server instance create/update calls to validate whether the name that is given to the server adheres to GD standards, is constrained by length and characters, and is unique amongst all servers registered within Active Directory.'00:00
harlowjathats one example00:00
wirehead_Rackspace’s open source version: http://www.openrepose.org/00:00
harlowjanothing crazy (and yes it should be upstreamed, and yes, i'm working on that issue, haha)00:00
sdakerepose00:00
sdakei am familiar with that00:00
wirehead_Same ideas as Netflix Zuul.00:00
sdakejava00:00
* sdake groans00:00
*** absubram has joined #openstack-kolla00:00
harlowjahttps://pypi.python.org/pypi/wafflehaus00:00
harlowja'Cloud providers of all sizes have problems dealing with business-requirements of their cloud and diverging from upstream. By putting business logic into middleware providers can create special cases without changing upstream code.'00:00
harlowjawhich i call BS00:00
harlowjabut ok, whatever, it pre-exists me :-P00:01
sdakeok so how does this middleware get loaded into a typical openstack daemon00:01
sdakeconfig option?00:01
harlowjapaste.ini files (the normal ones openstack rest endpoints have)00:01
*** absubram_ has joined #openstack-kolla00:01
wirehead_Here’s another one: https://getkong.org/00:01
harlowjahttps://github.com/openstack/nova/blob/master/etc/nova/api-paste.ini#L1700:01
wirehead_The overall API networked thingie community is quite taken by things such as Kong and Zuul and there are commercial management frameworks like 3scale.00:02
harlowjaya, i mean i get the desire to have that00:02
harlowjait just feels up like a copout00:02
harlowjawhich is why i'm pushing back on any new ones00:02
sdakeharlowja totally agree on both parts00:02
harlowjabut ya00:02
sdakeanyway00:03
sdakeso some special code needs to get loaded in each container?00:03
harlowjaso i think (or the thinking is) that our waffles we will turn just into another pypi package00:03
*** ravig has joined #openstack-kolla00:03
harlowjathat we'll just have to put as a requirement of these projects when building them (so that the waffles gets pulled down)00:03
*** MarMat has quit IRC00:03
wirehead_Well, in Kolla-K8s, you can just run it as a sidecar container. :)00:03
harlowja(and that pypi project would be in our artifactory pypi repo where it can be accessed during container build time)00:03
sdakeharlowja another option is to use the customization work we are planning or newton and carry backports00:03
sdakehowever modifying an internal git repo's requirements.txt would also work00:04
sdakeand probably lower level of pain involved00:04
harlowjaya, either might be ok till i can get rid of this junk00:04
harlowja(which probably will take a while...)00:04
sdakewhat about the bare metal deployment part00:04
harlowjaya, deployment, working on exploring that :-P00:05
harlowjaphase-next00:05
-openstackstatus- NOTICE: Gerrit is offline for maintenance until 01:45 UTC (new ETA)00:05
*** absubram has quit IRC00:05
*** absubram_ is now known as absubram00:05
*** ChanServ changes topic to "Gerrit is offline for maintenance until 01:45 UTC (new ETA)"00:05
sdakeyou already have some bare metals deployed00:05
sdakeI assume yu plan to keep them00:05
harlowjayup yup00:05
Davieysdake: I was just asking about your upgrade documentation... should it include how to take a backup snapshot of the control plane data and possible rollback guide?00:05
harlowjasoooooo what we have right now is a bunch of puppet stuff that deploys out rpms and such00:06
sdakeDaviey right - there is no such ability in kolla00:06
sdakeDaviey go big or go home ;)00:06
Davieysdake: Well there is... it just might not be pretty. :)00:06
harlowjabut ya, the dropping puppet --> kolla not yet sure how it will go00:06
harlowjabut thats ok00:06
sdakeDaviey yes your right it is possible in the current implementation00:06
harlowja(for deployment)00:07
sdakeDaviey but i think its too advanced to document00:07
Davieyharlowja: Are you lookin to inplace migrate or create a new cloud?00:07
harlowjanone of that create new cloud juk00:07
Davieysdake: Yeah.. poop.00:07
harlowjanot expecting this to be easy, but then the worthwhile things are never easy :-P00:07
harlowjatis life00:07
harlowjaha00:07
sdakekolla is extremely easy00:08
harlowja:)00:08
sdakebut the data backup and loading into your existing deploy will be a challenge to sort out00:08
harlowjayup00:08
sdakemind I ask how big the team is?00:08
Davieyharlowja: I'm looking to create a new cloud and migrate instances into it.. growing the new region and shrink the old one, server by server.  (with some automation)00:08
harlowja4 that could be say involved in this :-P00:08
harlowjamaybe more, unsure yet00:08
sdakeharlowja sounds like a good headcount00:08
harlowjaya, depends on how much i can divert them all to help with this00:09
harlowjabut its a pain we have to take imho00:09
Daviey(but i also want to move from linuxbridge to ovs, cinder+lvm to ceph and use differnet IP allocation.. so doing inplace will suck)00:09
harlowjaso ya, i and another guy are messing around with the deploy stuff (among the other things i do)00:09
harlowjaso its slow going :-P00:10
harlowjathe kolla-deploy00:10
harlowjaand i think exploring the stuffs and thinking about how we go to the next steps00:10
harlowja(also btw this is just for the private GD cloud)00:10
harlowjaidk what the public GD cloud will do here (afaik they use the same puppet stuff)00:10
harlowjawhich if we also stop using puppet stuff, then will they (i should get this answered, ha)00:10
*** godleon has joined #openstack-kolla00:11
sdakesince your self supported, I don't see any real problems00:11
sdakein terms of implementation, kolla needs cells and regions then00:11
harlowjamaybe monday i can get mdorman (one of the other guys whose involved) to get in here also00:11
harlowjaand can u add a kolla-move-from-puppet-to-kolla command00:11
harlowjalol00:11
harlowjathxxx00:12
sdakeharlowja ha ha ha00:12
sdakeok00:12
sdakei dont think that is even possible to invent ;)00:12
harlowjalol00:12
harlowjabut ya, i think we can take certain hosts out of rotation (api servers); tear them down, then bring them back up with kolla00:12
sdakehaving a systemtized way of upgrading a brownfield to a kolla deploy would rock00:12
harlowjathat will probably be part of the plan00:12
sdake(in terms of documentation)00:12
sdakehow many contorl nodes do you have per region00:13
harlowjalet me see what i can find00:13
Davieysdake: I should JFDI to see.. but to be lazy.. Are there any issues with adding and removing servers from different roles.. and leaving mess on each server?  Ie, server A /was/ a control and becomes a compute?  or server b was storage and becomes control?00:13
sdakeDaviey nothing I'e personally tested00:14
sdakeI just got a 10 node clsuter last week00:14
sdakeand its still not deployed (because of hardware issues)00:14
harlowjaso i think 3 api servers per region, then a couple cells servers (for nova) per region, gotta get to u on the db server count, 2 glance servers (from the example i am looking at right now) and compute (and then some logging server?)00:14
sdakeDaviey that said, I'd try not to leave a mess ont eh server ;)00:14
harlowjathe 3 api servers run a bunch of all the various oepnstack apis00:14
Davieysdake: As i'm looking to create a small cluster of about 6 and grow it to about 200.. the personality of the config should change as it grows... but i'm worried about leaving mess on the server00:15
harlowjabut i think thats the common pattern of what i've seen00:15
sdakewell cells and regions together00:15
sdakeDaviey i hear ya, we are adding things like add-osd remove-osd add-compute remove-compute in newton00:15
sdakeand add-controller remove-controller00:16
harlowjaya when i can get mike in here sdake he can make sure i'm correct on all these numbers :-P00:16
harlowjabut its never like 1 of something00:16
harlowjawhich should make tearing down things easier and replacing them with containers now under kolla00:16
Davieysdake: Ah cool.  Well, i'm currently planning to deploy mitaka  (and migrate instances from juno)00:16
sdakeDaviey one word of cuation00:17
sdakeI have heard nova compute nodes can only communicate one level forward with nova conductor nodes00:17
harlowjai think most regions have celiometer on a 2-4 nodes also00:17
sdakeharlowja we lack a ceilometer implementation00:17
harlowjak00:17
harlowjanote to self00:17
sdakedid you say you are doing an in-place replacement00:18
Davieysdake: yeah.. i'm looking to experiment with dd'ing from lvm to ceph... scripted.. but still ugly00:18
sdakei was asking harlowja00:18
harlowja:)00:18
harlowjayes, thats the goal00:18
sdakesorry Daviey for confusion00:18
Daviey(sorry, that was a response about one level forward with nova)00:19
harlowjai only do hard things, lol00:19
sdakeDaviey oh got it00:19
sdakeharlowja I dont think it will be super hard to do an in place replacement00:19
Davieysdake: I can see you having to setup a counseling clinic for us to discuss issues. :)00:20
sdakebut it will take some time nd probablybe entirely manual00:20
harlowjayup00:20
sdakebasically you have to get whatever persistent data you have stored on the machines00:21
sdakeand stoe them in docker volumes instead00:21
harlowjaya, i'm hoping there isn't to much of that (outside of nova-compute)00:21
*** ssurana has quit IRC00:21
sdakemariadb00:21
sdakeelasticsearch00:21
*** ssurana has joined #openstack-kolla00:21
sdakeglance00:21
Davieysdake: So I have a few deployments stuck on icehouse due to the underlying OS being Centos6 (which has py26), and Juno doesn't support py26.  I personally feel that upgrading either py or the base OS, then jumping through the openstack releases to get to mitaka to do an inplace migration is more work than setting up a parallel cloud.00:22
harlowjaah,  good ole centos600:22
sdakeDaviey makes sense00:22
sdakeharlowja i'd make a record of all the data you ahve in the system00:23
sdakeharlowja whta i want to get at though is what you need in terms of implementation00:23
Davieyin /tmp/00:23
harlowjayup, afaik thats done (or should be already)00:23
sdakeso cells/regions00:23
harlowjasdake ya, i think that would be cool00:23
sdakeanything else?00:23
harlowjaunsure about keepalived, afaik we just use load-balancers but a guy that would know better can probably chime in on monday00:24
sdakeharlowja you can turn off keepalived and haproxy and just use your hardware load balancers if you like00:24
harlowjakk00:25
harlowjathe other thing that would be nice, is to have a kolla-deploy convert-compute or something00:25
harlowjacause i can imagine that will be the painful one00:25
Davieysdake: Do you think it is likely that kolla-kubernetes will take over from kolla-ansible?00:25
*** ssurana has quit IRC00:26
sdakeDaviey you mean ddisplace ansible ?00:26
Davieyyeah00:26
sdakeDaviey unlikely any time soon00:26
DavieyI mean.. am i going to bet on the wrong horse now and regret it in 6 months?00:26
sdakeDaviey but if it does, the migraiton path will be smooth00:26
Davieysuper00:26
harlowja(i'm thinking that would say take a existing compute installation/hypervisor and without taking it offline ? move it to kolla based? )00:26
sdakekolla-ansible will take atleast 12 months to make stable00:26
sdakeharlowja zero downtime vm migration?00:27
harlowjai may be dreaming, idk00:27
harlowjalol00:27
DavieyThat shouldn't be hard if you plug in your new kolla stuff to your old control plane?00:27
sdakei'll have a think but my inital response is dreaming :)00:27
sdakeI don't think its possible because of kernel reasons00:27
harlowjaya, not unexpected :-P00:28
sdakeharlowja there is always live migration ;-)00:28
harlowjalol00:28
Davieyhuh? surely a nova-compute via puppet or nova-compute via kolla should be treated as identical for scheduling / migration reasons?00:28
sdakei know what a charlie foxtrot of a featuer that is00:28
Davieyproviding you have the same cpu etc?00:28
harlowjaDaviey i think its more about the VMs that are actively running00:28
harlowjathe bunches of qemu-kvm stuff running00:29
sdakeyou can shut down nova-compute and the vms will remin running00:29
Davieywell they are just libvirt kvm machines?00:29
sdakeqemu-kvm will be adopted by systemd00:29
Davieysurely it doesn't matter if on the metal or via docker?00:29
harlowjaunsure, u guys let me know :-P00:29
sdakethe problem is the file that qemu-kvm loads00:29
sdakeit loads some files from disk and once they are loaded, they are locked00:29
Davieyi would be really surprised if it was a major headache00:29
Davieyhmm00:30
sdakewell the persistent storage for nova compute goes in a named volume00:30
sdakeperhaps a mv operation would work00:30
Davieythey aren't really locked.. you can do $ virsh edit instance-0010101 . and change the running vm without telling nova00:30
sdakeI am not certain00:30
sdakeDaviey i am talking about the files loaded by qemu-kvm00:30
harlowjain the kolla nova-compute, just want to check (since i'm not sure and haven't tried it yet) do the qemu-kvm processes run inside the nova-compute container00:30
sdakethe kernel has references to them open00:30
harlowjaor do they run outside the container00:31
sdakeharlowja we use pid=host00:31
sdakeso they run outside the container00:31
harlowjak00:31
sdakebut inside a docker named voluem00:31
Davieyhell, you could even just rsync.. run the vm and add a db entry.. but that way leads to a bad day out.00:31
sdakestill with all that cgroups black magic00:31
sdakedocker cant even stop a fork bomb ;)00:31
sdakeseriously though I'm not sure if cgroups will prevent access to moving the file into the odcker named volume00:32
sdakewhere it needs to go00:32
*** ravig has quit IRC00:32
harlowjai think folks here might be ok with nova-compute not responding to say a terminate request for a little, but don't think people would be happy if we had VM downtime (although there might be a way to make this ok, since I do get emails saying my vms might be inaccessible for a period)00:32
sdakeif that part works, that could be entirely automated in ansible in about 1-2 hours by the right person00:32
harlowjaya00:32
harlowjajust need to figure out the appropriate steps00:32
Davieysdake: if you can live mirgate from a docker nova-libvirt to a docker nova-libvirt, i can't see why you couldn't do it from bare metal to docker00:33
sdakeDaviey you can do live migration00:33
sdakeI think harlowja doesn't want to live migrate00:33
Davieywhat a loser.00:33
harlowjajust to clarify, this is the nova concept of live-migrate right?00:33
sdakeharlowja right00:33
harlowjak00:33
sdakewith qemu integration00:34
harlowjaright00:34
harlowjaya, don't think that can happen here00:34
sdakei dont eve nwant to know why :)00:34
harlowjanot everything running off of ceph ....00:34
harlowjaya00:34
harlowjaand various other things :-P00:34
sdakeceph00:34
harlowjathat i also don't want to know why, lol00:34
sdakeyou are using ceph?00:34
Davieyharlowja: why not bring up a kolla control plane... add a kolla compute node, migrate instances from a legacy compute node into it.. and then whn evac'd.. reprovision the old server as a kolla compute then GOTO 1000:35
Daviey?00:35
harlowjasdake well ummmm sort of afaik lol00:35
sdakeharlowja i highly recommend ceph for all your storage00:35
sdakebut you definately can't migrate your nova compute to ceph00:35
harlowjai know i know, i tried talking to the guys here about that ....00:35
harlowjathey got ceph-nightmares or something, idk00:36
sdakewell if it craters00:36
harlowjaDaviey that might work, unsure if the network here will work for that00:36
sdakeyour fucked00:36
sdakewherea if ext4 craters00:36
sdakeyou lose one node00:36
harlowjaya, i think they had it crater once, lol00:36
harlowjathats what i hear00:36
sdakelol00:36
harlowjaand then they ran away from ceph for all the storage00:37
harlowjaso hypervisors afaik use local storage for most things00:37
harlowjawhich will, really kills live-migration (among other things, ha)00:37
Davieycurrently we are using cinder+lvm with the nova compute always using localhost for storage (which gives no migration ability)... i need to prove that ceph will do what we need00:37
harlowjaDaviey let me know, maybe i can convince the ops guys here to not have nightmares00:37
sdakeharlowja in a kolla model hyeprvisors use named volumes00:37
harlowjalol00:37
Daviey(i know it will... but i need to prove it)00:37
harlowjasdake i guess then named volumes can ---> ceph or ...00:38
sdakeharlowja here let me erlog so i can access my serers00:38
Davieyharlowja: If my legacy compute nodes were running a newer version of openstack, that is how i'd do it... but i suspect i'll need to dd disks from lvm to ceph as part of my by-hand migration00:38
harlowja:-/00:39
harlowjafun fun00:39
harlowjaha00:39
Davieyi'll script it.. but it will still suck00:39
harlowjaya, no doubt00:39
Davieyharlowja: Do you have a timeline you are working towards?00:40
harlowjanot so clear yet00:40
harlowjasoon?00:40
harlowjalol00:40
harlowjalike this year?00:40
harlowjain the next 4 months ?00:40
harlowjalol00:40
harlowjathats about as much as i got00:40
harlowjato many variables to accurately predict timeline :-P00:41
Davieyhah.  Well i only started looking at kolla as part of the threat analysis stuff at the summit.. and playing with it 2 weeks ago.  I hope to start bringing dev/qa nodes into it in ~6 weeks.00:41
DavieyBut i suspect we are at about the same stage right now.00:41
harlowjapossibly00:41
*** sdake_ has joined #openstack-kolla00:41
harlowjau might have more free resources that can dedicate to this than i do :-P00:41
harlowjai'm like a fraction of a person, lol00:42
harlowjasplit across many things, ha00:42
sdake_who does for what00:42
DavieyI have 42 hour days.00:42
harlowjalol00:42
sdake_i have 84 hour days00:42
*** sdake has quit IRC00:42
sdake_harlowja i'mg goint o try to prototype a migration from one continaer to another of nova compute00:43
sdake_and see if it works in that regard00:43
sdake_if you can hang for 15 mins i willl show you results00:43
Davieysdake_: you mean a live migrate of a kolla compute node to another kolla node?00:43
sdake_Daviey no I am going to use the unix mv ommand to move the files around00:44
harlowjacool00:44
sdake_and see if that works00:44
harlowjai was just talking to my manager who is still around about the ceph 'problem'00:44
harlowjaand why there seems to be 2 camps around it00:44
sdake_'problem00:44
sdake_lol00:44
harlowjathe 'its the best thing ever camp'00:44
harlowjaand then the 'nightmare camp'00:44
harlowjai'm in no-thoughts-camp00:45
harlowjaand we were starting to wonder why this is00:45
sdake_harlowja my idea wont work00:45
harlowja(cause i don't really know)00:45
Davieysdake_: well the concern that some people have is latency and flodding the network.. but this is a general shared storage issue and not specific to ceph00:45
sdake_harlowja you can't use mv across filesystems00:45
Davieyand "it's new, don't know how to debug".. which was the same as ovs vs linuxbridge00:46
sdake_unix = fired00:46
harlowjaDaviey i think it may also be the 'i had it crater on me once and now i have PTSD from that event'00:46
Davieyharlowja: ha00:46
harlowjasdake_  is there anyway to say have the named volume just point to the existing 'folder' that the existing computes already run from00:47
harlowjaand then have a few minutes of the libvirt daemon being down?00:47
Davieysdake_: is this to mv it from the host (from legacy libvirt on host) to one within a kolla/docker container?00:47
sdake_Daviey actually it gets moved to /var/lib/docker00:47
sdake_but yup00:47
sdake_harlowja named volumes are stoerd in /var/lib/docker00:48
Davieyyeah, you can bind mount (not sure what it is called in docker), but you can mirror a folder like that00:48
harlowjais there a way to migrate without nova00:48
harlowjai think so00:48
harlowjalike local-to-the-machine-migrate, ha00:48
harlowjafrom one libvirt to the other00:48
harlowjathat should be ok right00:48
harlowja(although seems sorta crappy, ha)00:48
sdake_ya that might work - depends what version of qemu you have00:48
harlowjacentos7 stuffs00:49
sdake_the prbolem with live migration is lack of a standard binary format for qemu live migration00:49
sdake_harlowja we use the centos virt sig repos for qemu00:49
sdake_harlowja which is the latest cutting edge stuff from red hat with some features removed on purpose00:49
Davieydocker run -v /var/lib/nova/instances:/var/lib/docker/nova/instances ...00:49
sdake_harlowja centos7 typically ships with a really old(tm) version of qemu00:50
Davieysdake_: AIUI you can only run one instance of libvirt on the entire machine?00:50
harlowja:-p00:50
DavieyI don't think this is a qemu problem, is it?00:50
sdake_Daviey nah I htink you can run multipel copies of libvirt00:50
sdake_if you use networking00:51
Davieysdake_: Oh, i thought i read in the kolla docs that it didn't work00:51
sdake_what doesn't work00:51
sdake_oh multiple copies00:51
Davieylibvirt on the metal and libvirt in docker00:51
sdake_what I mean is it can be done00:51
sdake_if onfigured properly00:51
Davieyok00:51
harlowjawhat about not having the libvirt part running in a container?00:51
sdake_killing libvirt does not kill qemu-kvm processes00:51
sdake_harlowja probably your best option is to bindmount libvirt data rather then use a named volume00:52
sdake_we use a named volume because thats how you do htings in docker now00:52
sdake_bindmounts are untidy00:52
Davieyyeah, using docker -v HOST:MOUNT, or literally bind mounting outside of docker?00:53
sdake_but your system will already be untidy since you wont be doing a ffresh install00:53
sdake_Daviey ya our docker module has an option for that I think - if not its easy enough to add00:53
Daviey(i still think host evacuation from legacy to kolla is cleaner and easier)00:53
*** salv-orl_ has joined #openstack-kolla00:56
*** salv-orlando has quit IRC00:56
sdake_harlowja changing the ansible like this should work: http://paste.fedoraproject.org/374277/1758146/ -> http://paste.fedoraproject.org/374277/0175814600:56
sdake_Daviey i tend to agree - you can do a completely fresh host OS installation00:56
harlowjakk00:57
sdake_without all the crap on there that was there from openstack 3 versions ago :)00:57
sdake_harlowja in fact you could get rid of all the named volumes we use and just use bindmounts00:57
sdake_not all the named volumes00:57
harlowjawhats the benefit of doing that?00:57
sdake_but the onees related to persistent00:57
sdake_the benefit is you wont have ot migrate your data into the named volume00:58
harlowjak00:58
harlowjaya, for libvirt stuff that might be the way to go00:58
sdake_ya - only option00:58
sdake_i'd recommend nvme ssds for /var/lib/docker as well00:59
sdake_;)00:59
harlowjamight already be that, i'm not sure :-P00:59
harlowja(ssds that is)00:59
sdake_and i'd recomend btrfs for thir filesystem00:59
harlowjahmmmm00:59
harlowjaya, pretty sure its not that, lol00:59
sdake_i know, babies eaton00:59
Davieysdake_: Is IO going to be that much of an issue?00:59
sdake_Daviey which io where00:59
sdake_Daviey openstack is all about io:)00:59
sdake_harlowja btrfs is needed (I thiink) for upgrades01:00
Davieysdake_: why /var/lib/docker ssd?01:00
sdake_(to work in the future)01:00
harlowjak, will have to get person who knows more about this than me for that one :-P01:00
sdake_Daviey oh yes it makes a huge difference01:00
sdake_my build is 15 minutes, prior to intel 750 1.2tb ssd - my build was 45 minutes - I have gige to the internet01:00
Davieysdake_: for /everything?!/01:00
sdake_Daviey well here is the deal - I put /var/lib/docker on an ssd becuase I work on kolla 18 hrs a day01:01
Davieywell, sure for dev01:01
sdake_Daviey ifor me the cost benefit analysis was a no brainer01:01
harlowjaonly 18/8401:01
harlowjawhy u not working that much01:01
harlowjalol01:01
sdake_gotta recreate some time :)01:02
sdake_harlowja you might want to double check libvirt doesn't shut down qemu-kvm01:02
harlowjayup01:02
Davieybut mariadb, base OS and python code.. all on SSD is going to become a problem with either capacity and/or $$$01:02
sdake_you may have to teriminate it -901:02
harlowjasdake_ ya, its a good thing to figure out, the whole how is this whole process gonna work (and what are the steps) for nova-compute01:03
sdake_harlowja ya - and doing the same thing  for controller nodes01:03
harlowjaya, i think those are easier, cause those can get shot-in-the-head easier01:03
harlowjaless pita, lol01:03
sdake_harlowja it woudl be helpful for m e to ge ta copy of some configs that describe cells and regions01:04
sdake_I think this is probably in teh nova.conf files01:04
sdake_but i am not sure01:04
Davieyharlowja: planning to just add the kolla VIP to your legacy load balancer?  So that it serves old and kolla control plance concurrently ?01:04
harlowjaya, i can locate some of it01:04
harlowjaDaviey unsure01:04
sdake_harlowja how many nodes?01:05
harlowjaor just use the load-balancer directly?01:05
sdake_per region01:05
Davieyharlowja: you might not use keepalived?01:05
harlowjasdake_  will get that from someone who knows it better than me :-P01:05
sdake_cool01:05
sdake_the reason I ask is because haproxy has a limied amount of capacity01:05
sdake_I dont nwo what it is01:05
sdake_i haven't measured it01:05
sdake_haproxy is what does all the network IO01:06
sdake_keepalived just places the VIP in the correct controller node01:06
sdake_with 64 nodes, we had no prolems with any performance01:06
harlowjacool,, ya we have this 'OpenStack Regions/Environments ' confluence page, but its information is not so easy to decode01:06
harlowjai don't think i have the decoder ring for it, lol01:06
sdake_obviously that isn't 200-500 that a region can have01:06
sdake_brb relogging01:07
Davieysdake_: You could look to do layered HAproxy if one doesn't cope.01:07
Davieybut right now... bed.  Night chaps.. good talking x01:08
harlowjalata01:10
*** sdake_ has quit IRC01:11
*** sdake has joined #openstack-kolla01:12
*** salv-orlando has joined #openstack-kolla01:14
sdakeharlowja i'd recommend setting up a 10 node cluster using your current tooling01:15
sdakeharlowja loading it up with a workload01:15
sdakeand try to figure out how to migrate it to kolla01:15
harlowjaagreed01:15
sdaketiral and error will be best teacher01:15
sdakei know that seems obvious01:15
sdakebut it seemed like a flash of birilliance 5 minutes ago ;)01:15
harlowja:-P01:15
Davieyharlowja: One more q for you, are you looking to use puppet still to bring up your hosts.. install docker.. ssh keys etc?01:16
harlowjaunsure01:16
harlowjai would guess so?01:16
Davieysdake: and one more from you.. have you done all-in-one (- compute) and migrated it to multi-host after deployment?01:17
*** cu5 has joined #openstack-kolla01:17
sdakeDaviey i have in teh past01:17
sdakenot recently01:17
sdakekolla movess fast01:17
Davieysdake: any issues?01:17
sdakeit worked at the time01:17
*** salv-orl_ has quit IRC01:17
sdakerecommend validating yourself though01:17
Davieyright. yeah01:17
harlowjasdake monday i'll grab a more operator-puppet-man and hopefully can further flush out some questions/ideas here01:18
Davieyharlowja: I'm expecting to do my kolla-infra via chief.01:19
Davieychef*01:19
harlowjacool01:19
Daviey(or maybe ansible, tbc)01:19
harlowjaya pick your bootstrapper01:19
*** cu5 has quit IRC01:20
DavieyOur hosts are deployed via chef, but the workload via ansible... the division is, erm, unclear.  So i think kolla can sit in either for me01:20
*** ChanServ changes topic to "Kolla IRC meetngs on Wednesdays @ 16:30 UTC even weeks, 23:00 UTC odd weeks - see agenda @ https://goo.gl/OXB0DL - IRC channel is *LOGGED* @ http://goo.gl/3mzZ7b (old logs from #kolla http://goo.gl/VKpPzA)"01:21
-openstackstatus- NOTICE: Gerrit maintenance concluded successfully01:21
sdakefwiw , we are going to make bare metal setup a playbook in newton01:23
harlowjakolla folks really like 'Add a bug id or Trivial Fix' don't they :-P01:24
sdakewell trained i'd say :)01:24
harlowja:-P01:24
sdakeyou can use blueprints for big bodies of work01:24
harlowjajosh-random-stuff-blueprint01:24
harlowjalol01:24
sdakei usually rubber stamp blueprints unless they are obnoxious in some way01:24
sdakethe reason we need bug ids is  for backporting01:25
sdakeif yoru patch isn't going to be backported to a stable branch, you can use trivialfix if its not a blueprint01:25
sdakethat is the basic training we have in place ;)01:25
harlowjalol01:25
harlowjak01:25
sdakewithout bugids, the release team would probably scream at me wrt zstreams01:26
harlowjawhat if in the future it gets backported but i didn't expect it to be backported at the time of creation01:26
sdaketonyb would probably be unhappy01:26
harlowjacause i got no future prediction powers :-P01:26
sdakeand i wouldn't be able to execute01:26
sdakeharlowja usually the person that reviews it makes a call and says it shoudl be backported01:27
sdakebut thi doesn't always happen01:27
Davieysdake: a backport doesn't need a bug... but it doesn't hurt either.01:27
sdakeDaviey it does foru s :)01:27
harlowjai'm just wondering how that person predicts the future01:27
harlowjalol01:27
sdakeharlowja if its a bug, high or critical, it gets backported01:27
sdakeif its a feature, it doesn't get backported01:27
Davieysdake: well ok.. but i'm part of stable-maint-core and we've never pushed for it01:27
sdakeits simple as that01:27
harlowjak01:27
sdakeDaviey ok then you would know ;)01:28
harlowjawhat if its a feature that turns into a fix for a bug by accident01:28
harlowjalol01:28
sdakeDaviey my bad, didn't know you had experience in the area01:28
harlowjalike the feature turns out to fix all the bugs, via it being the best feature ever01:28
sdakeharlowja then it becomes very difficult to track, but we can still backport it01:28
harlowja:)01:28
sdakeya we are  doing that with lbaas01:29
sdakebecause magnum depends on it01:29
sdakeadn we shipped mitaka and liberty with magnum01:29
sdakebut it was busted01:29
sdakelbaas is cleary a feature01:29
*** thumpba has joined #openstack-kolla01:29
sdakebut in this case its a bug because it isn't present01:29
sdakeand magnum depends on it01:29
sdakeand magnum is busted without it01:29
sdake(and without other changes as well)01:29
harlowjagotcha01:29
sdakewhat we should have done is removed magnum form the repo01:29
sdakeand then reverted it after the  release01:29
sdakebut i didn't realize how big of a problem it was01:30
sdakebut we are stuck with it now01:30
harlowjaya, sounds similar to the other project that i had that turned source repos -> rpms that then get deployed (via this puppet stuff)01:30
harlowjait became a weird tangle of figuring out, oh well now u need that other project for this project to work also01:30
harlowjathus kolla will now figure all that out (instead of me, lol)01:31
sdakewell kolla relies on the upstream (in source biulds0 requirements and upper constraints to be correct01:31
harlowjahttps://github.com/openstack/anvil/tree/master/conf/personas/in-a-box (for example, these listed the pieces needed to work for a various set of things)01:31
sdakeif they are not, all bets are off ;)01:31
harlowjaya, stuff just gets weird when pieces are somewhat optional01:32
*** openstackgerrit has quit IRC01:33
*** openstackgerrit has joined #openstack-kolla01:33
harlowjaanvil also pre-existed the whole requirements and upper-constraints stuff so i had to years ago put a variant (crappy one) of a find-the-constraint set that will hopefully work in it01:34
harlowjau don't want to know, lol01:34
*** thumpba has quit IRC01:35
sdakehavne'et heard of anvil but i looked ath the repo01:54
sdake3k commits01:54
sdakeseems pretty active01:54
*** Jeffrey4l_ has quit IRC02:01
sdakeharlowja re cells02:05
sdakeharlowja i spoke with russellb today about cells and regions02:05
sdake(as scalability options)02:05
sdakehe told me that you install amqp+db for each cell02:06
sdakehe also told me you install all controllers per region02:06
sdakeand then make one database for keystone, and use fernet tokens02:06
sdakewith regions, we should be able to scale to several thousand nodes02:07
sdakenot sure how cells is helpful but if thats wht you have today then I dont see harm in implementing it and other will likely want it as well02:07
sdakeis this your understanding of how these deployments are structured?02:07
sdakecells will be harder then regions02:08
sdakesince it sound slie the only new dev you reallly require is cells plus regions, we should be able to get this done this cycle02:09
sdakewe have 130 node OSIC cluster coming online02:09
sdakewe are going to deploy kolla on it02:09
sdakethen we are going to deploy kolla on top of vms produced by that kolla02:09
sdaketo give us a couple thousand nodes to work with02:09
sdakeand do the development that way02:09
sdakenote this layering approach is JUST for dev02:10
sdakeso we can scale out our 130 nodes to something that is real02:11
*** papacz has quit IRC02:11
*** Jeffrey4l_ has joined #openstack-kolla02:13
sdakeJeffrey4l_ ping02:18
Jeffrey4l_sdake, pong02:19
sdakeJeffrey4l_ did you see the discussion i just hd with harlowja02:19
sdakeJeffrey4l_ if not check the logs plz02:19
sdakeit involved godaddy's requirements for kolla deployment02:20
sdakegodaddy is larger then our  typical deployment by several orders of magnitude02:20
Jeffrey4l_just saw this. I will check the whole log.02:21
sdakeJeffrey4l_ you probably wont be able to make the midcycle in july 12-13th right?02:21
Jeffrey4l_sdake, yes. :(02:21
sdakeJeffrey4l_ can you make the main summit?02:21
sdakeit is in barcelona iirc02:22
Jeffrey4l_possible, if i have no passport issue.02:22
sdakecan you get cracking on the paperwork02:22
sdakeif you need  a letter from the foundation for a visa they will provide iirc02:23
sdakethat way the govt knows your doing your day job and not moving countries :)02:23
Jeffrey4l_yep. I applied the letter.02:23
sdakenice already on the ball02:23
sdakechinese government aware of openstack as a thing02:24
Jeffrey4l_but still failed when applying the US visa. :(02:24
sdakeso if a letter comes from the foundation it should help your chances02:24
sdakeeurope isn't as rigid on visas as the US02:24
sdakethe letter helps02:25
sdakei needed one to get into china02:25
sdakei needed two in fact02:26
sdakeand every time i walked into the us they looked at me funny when they looked through my passport :)02:26
Jeffrey4l_lol02:26
Jeffrey4l_i will well prepared for the newton summit.02:27
sdakefortunately I have a fres hclean passport to damage ;)02:27
sdakeJeffrey4l_ we dont really prepare all that much except as a group for planning sessions02:27
sdakeJeffrey4l_ but do whatever makes your comfortable :)02:28
Jeffrey4l_OK.02:28
*** openstackgerrit has quit IRC02:32
*** openstackgerrit has joined #openstack-kolla02:33
*** daneyon_ has joined #openstack-kolla02:34
openstackgerritMerged openstack/kolla: adding else statement with empty string starting ansible 2.X it require a else statement.  https://review.openstack.org/32548302:39
*** daneyon_ has quit IRC02:40
*** ravig has joined #openstack-kolla02:58
*** ravig has quit IRC03:00
*** eaguilar has joined #openstack-kolla03:04
*** MarMat has joined #openstack-kolla03:08
*** eaguilar has quit IRC03:11
*** ravig has joined #openstack-kolla03:11
*** ravig has quit IRC03:19
*** ravig has joined #openstack-kolla03:20
*** sacharya has joined #openstack-kolla03:22
*** sacharya_ has quit IRC03:26
*** ravig has quit IRC03:31
*** ravig has joined #openstack-kolla03:31
*** ravig has quit IRC03:35
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/kolla: Make container kolla-toolbox build with debian  https://review.openstack.org/29710403:44
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/kolla: Make swift-base container build with debian  https://review.openstack.org/29712103:44
*** sacharya_ has joined #openstack-kolla03:48
*** sacharya has quit IRC03:51
*** ravig has joined #openstack-kolla04:24
openstackgerritJoshua Harlow proposed openstack/kolla: Delay opening a log file until first use  https://review.openstack.org/32234204:29
*** sacharya has joined #openstack-kolla04:32
*** sacharya_ has quit IRC04:36
*** thumpba has joined #openstack-kolla05:03
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/kolla: Make heka container build with debian  https://review.openstack.org/29773705:04
openstackgerritMerged openstack/kolla: Make container kolla-toolbox build with debian  https://review.openstack.org/29710405:07
openstackgerritMerged openstack/kolla: Make swift-base container build with debian  https://review.openstack.org/29712105:07
*** thumpba has quit IRC05:08
openstackgerritJoshua Harlow proposed openstack/kolla: Have more useful stdout with a progressbar (as well)  https://review.openstack.org/32552905:08
*** sacharya has quit IRC05:13
*** sacharya has joined #openstack-kolla05:15
*** daneyon_ has joined #openstack-kolla05:16
*** sacharya has quit IRC05:19
*** daneyon_ has quit IRC05:22
*** ravig has quit IRC05:36
*** sacharya has joined #openstack-kolla06:16
*** sacharya has quit IRC06:20
*** thumpba has joined #openstack-kolla07:00
*** thumpba has quit IRC07:05
*** salv-orl_ has joined #openstack-kolla07:15
*** salv-orlando has quit IRC07:18
*** fragatina has quit IRC07:26
*** MarMat has quit IRC07:35
*** fragatina has joined #openstack-kolla07:39
*** fragatina has quit IRC07:43
*** fragatina has joined #openstack-kolla07:45
*** fragatin_ has joined #openstack-kolla07:46
*** fragatina has quit IRC07:49
*** sdake has quit IRC08:07
openstackgerritBenedikt Trefzer proposed openstack/kolla: Make container dind unpin old docker relase  https://review.openstack.org/29743408:10
openstackgerritBenedikt Trefzer proposed openstack/kolla: Make heka container build with debian  https://review.openstack.org/29773708:12
*** fragatin_ has quit IRC08:12
*** sacharya has joined #openstack-kolla08:16
openstackgerritBenedikt Trefzer proposed openstack/kolla: Make nova-libvirt container build with debian  https://review.openstack.org/29716908:16
openstackgerritBenedikt Trefzer proposed openstack/kolla: make rabbitmq container build with debian  https://review.openstack.org/29772808:17
*** sacharya has quit IRC08:21
*** b_bezak has joined #openstack-kolla08:22
*** salv-orl_ has quit IRC08:23
*** salv-orlando has joined #openstack-kolla08:23
*** daneyon_ has joined #openstack-kolla08:53
*** salv-orlando has quit IRC08:54
*** salv-orlando has joined #openstack-kolla08:55
*** daneyon_ has quit IRC08:58
*** thumpba has joined #openstack-kolla09:01
*** thumpba has quit IRC09:06
*** dwalsh has joined #openstack-kolla09:11
*** dgonzalez has quit IRC09:37
*** mdnadeem has quit IRC09:48
*** mdnadeem has joined #openstack-kolla09:49
*** mdnadeem has quit IRC09:50
*** mdnadeem has joined #openstack-kolla09:51
*** dgonzalez has joined #openstack-kolla09:53
*** dwalsh has quit IRC10:07
*** godleon has quit IRC10:09
*** pbourke has quit IRC10:10
*** pbourke has joined #openstack-kolla10:11
*** SiRiuS has joined #openstack-kolla10:17
*** sacharya has joined #openstack-kolla10:17
*** sacharya has quit IRC10:22
*** SiRiuS has quit IRC10:35
*** daneyon has quit IRC11:03
*** SiRiuS has joined #openstack-kolla11:03
*** daneyon has joined #openstack-kolla11:36
*** daneyon has quit IRC11:40
*** sacharya has joined #openstack-kolla12:18
*** sacharya has quit IRC12:22
*** dave-mccowan has joined #openstack-kolla13:13
*** b_bezak has quit IRC13:14
*** salv-orl_ has joined #openstack-kolla13:15
*** salv-orlando has quit IRC13:18
openstackgerritMerged openstack/kolla: make rabbitmq container build with debian  https://review.openstack.org/29772813:36
*** ravig has joined #openstack-kolla13:36
openstackgerritMerged openstack/kolla: Make nova-libvirt container build with debian  https://review.openstack.org/29716913:37
openstackgerritMerged openstack/kolla: Make heka container build with debian  https://review.openstack.org/29773713:39
*** mdnadeem_home has joined #openstack-kolla14:18
*** sacharya has joined #openstack-kolla14:18
Mech422Hmm - it appears Kolla's ceph stuff gets confused if you use XFS, and tries to mount the partition with a btrfs 'compress' option?14:20
*** rhallisey has joined #openstack-kolla14:21
*** sacharya has quit IRC14:23
Mech422ahh - my bad... knob in globals needed turning :-P14:25
*** mdnadeem_home has quit IRC14:27
*** mdnadeem_home has joined #openstack-kolla14:29
*** mdnadeem_home has quit IRC15:03
*** thumpba has joined #openstack-kolla15:04
*** sacharya has joined #openstack-kolla15:04
*** thumpba has quit IRC15:09
*** daneyon has joined #openstack-kolla15:12
*** daneyon has quit IRC15:17
*** mdnadeem_home has joined #openstack-kolla15:19
*** inc0 has joined #openstack-kolla15:34
inc0hey15:34
*** sacharya has quit IRC15:40
*** inc0 has quit IRC15:45
openstackgerritRyan Hallisey proposed openstack/kolla: Spec: Deploy Kolla images using Kubernetes  https://review.openstack.org/30418215:51
*** sdake has joined #openstack-kolla16:02
*** mdnadeem_home has quit IRC16:02
*** esimone has quit IRC16:03
*** sacharya has joined #openstack-kolla16:08
*** sacharya has quit IRC16:13
*** mdnadeem_home has joined #openstack-kolla16:20
*** jmccarthy has quit IRC16:25
*** jmccarthy has joined #openstack-kolla16:25
openstackgerritChristian Berendt proposed openstack/kolla: Fix URL to Heka documentation in README file  https://review.openstack.org/32559516:37
*** mdnadeem_home has quit IRC16:38
*** rhallisey has quit IRC16:50
*** thumpba has joined #openstack-kolla17:04
*** thumpba has quit IRC17:09
*** sacharya has joined #openstack-kolla17:09
*** sacharya has quit IRC17:14
*** ravig has quit IRC17:16
*** dwalsh has joined #openstack-kolla17:19
openstackgerritChristian Berendt proposed openstack/kolla: Cleanup help string of install_type parameter  https://review.openstack.org/32560017:24
*** dwalsh has quit IRC17:48
*** ravig has joined #openstack-kolla17:49
*** ravig has quit IRC17:54
*** ssurana has joined #openstack-kolla17:55
Mech422so fresh source build/deploy of stable/mitaka using PARTIONS for ceph instead whole devices 'works' modulo 2 bugs: you need to run kolla-ansible deploy twice, and the OSDs get detected twice..17:55
Mech422so with 3 osds, you end up in 'WARN' state with 3/6 OSDs up17:56
Mech422investigating further now17:56
*** Jeffrey4l_ has quit IRC17:58
*** sacharya has joined #openstack-kolla18:10
*** ssurana has quit IRC18:10
Mech422it appears ./ansible/roles/ceph/tasks/start_osds.yml is looking for a 'changed' status in name: Looking up OSDs for Ceph (first play)18:12
*** ravig has joined #openstack-kolla18:12
Mech422can't see where its getting it from though18:12
*** sacharya has quit IRC18:15
*** sdake has quit IRC18:31
*** thumpba has joined #openstack-kolla18:34
*** ssurana has joined #openstack-kolla18:36
*** thumpba has quit IRC18:38
*** daneyon has joined #openstack-kolla18:49
*** daneyon has quit IRC18:53
*** fragatina has joined #openstack-kolla18:57
*** ravig has quit IRC19:04
*** ravig has joined #openstack-kolla19:05
*** salv-orlando has joined #openstack-kolla19:15
*** ssurana has quit IRC19:18
*** salv-orl_ has quit IRC19:18
*** fragatina has quit IRC19:29
*** fragatina has joined #openstack-kolla19:29
*** sacharya has joined #openstack-kolla19:34
*** godleon has joined #openstack-kolla19:35
*** ssurana has joined #openstack-kolla19:39
*** sacharya has quit IRC19:39
*** d_code has joined #openstack-kolla19:40
*** d_code has quit IRC19:44
*** sdake has joined #openstack-kolla19:45
*** sdake_ has joined #openstack-kolla19:54
*** sdake has quit IRC19:55
*** ssurana has quit IRC19:56
*** dwalsh has joined #openstack-kolla20:01
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Convert MariaDB to work without HostNetwork=True  https://review.openstack.org/32561320:06
openstackgerritKen Wronkiewicz proposed openstack/kolla-kubernetes: Convert MariaDB to work without HostNetwork=True  https://review.openstack.org/32561320:07
*** fragatina has quit IRC20:10
*** dwalsh has quit IRC20:11
*** ssurana has joined #openstack-kolla20:15
*** sdake_ has quit IRC20:24
openstackgerritMerged openstack/kolla-kubernetes: Add bootstrap method to the quickstart doc  https://review.openstack.org/32411320:25
openstackgerritMerged openstack/kolla-kubernetes: Break deployment procedure into two steps  https://review.openstack.org/32066820:28
*** fragatina has joined #openstack-kolla20:28
*** sacharya has joined #openstack-kolla20:40
*** ssurana has quit IRC20:41
*** cu5 has joined #openstack-kolla20:44
*** ssurana has joined #openstack-kolla20:45
*** ravig has quit IRC20:47
*** ssurana has quit IRC20:48
*** cu5_ has joined #openstack-kolla20:50
*** cu5_ has quit IRC20:52
*** ravig has joined #openstack-kolla20:52
*** cu5 has quit IRC20:55
*** cu5 has joined #openstack-kolla20:58
*** cu5 has quit IRC21:01
*** sdake has joined #openstack-kolla21:27
*** absubram has quit IRC21:38
*** sdake has quit IRC21:49
*** Jeffrey4l_ has joined #openstack-kolla22:30
openstackgerritJeffrey Zhang proposed openstack/kolla: Install keepalived in neutron_l3_agent container  https://review.openstack.org/32561822:36
*** Jeffrey4l_ has quit IRC22:42
openstackgerritMerged openstack/kolla-kubernetes: Add some hints for working with MariaDB.  https://review.openstack.org/32481222:48
*** SiRiuS has quit IRC22:57
*** ravig has quit IRC23:06

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!