Friday, 2017-01-27

sdakei get genconfig generates the config -that step is done00:00
kfox1111sec...00:00
kfox1111let me just see if I can send you this whole thing...00:00
sdakebmace_ do you have further questions?00:00
kfox1111darn... unfortunately, this config file is heavily modified from a previous upgrade attempt. :/00:01
bmace_sdake: i just need to debug why my container pulls are failing now :/00:01
kfox1111sdake: I'd recommend pulling kolla 3.x and running a genconfig from there. should be able to get a horizon config set that should work I think.00:01
bmace_sdake: mariadb / rabbitmq look to be up, but that is it00:01
sdakekfox1111             "source": "/var/lib/kolla/config_files/local_settings",00:02
sdake            "dest": "/etc/openstack-dashboard/local_settings",00:02
sdake            "owner": "horizon",00:02
sdake            "perm": "0644"00:02
sdakekfox1111 so looking at that, the source is /var/lib/kolla/config_files - the ocntinaer isn't going to ha ethat directory at all00:02
kfox1111it should00:02
bmace_sdake: well, maybe not "up", just the init-element for both.. still getting a feel for the full deploy process.00:02
sdakekfox1111 let me check it out00:03
kfox1111we mount the configmap at that location.00:03
*** lamt has quit IRC00:03
kfox1111do a: helm install kolla/horizon-deployment --dry-run --debug00:03
*** lamt has joined #openstack-kolla00:04
kfox1111should see a volumeMounts: section with that mount point.00:04
*** lamt has quit IRC00:04
sdakekfox1111 - ok i have found the files inside the container00:04
*** saneax is now known as saneax-_-|AFK00:04
*** harlowja has quit IRC00:04
sdakethe files copied INTO the container in /var/lib/kolla are wrong00:04
kfox1111wrong how?00:05
sdakemoment00:05
sdakegroan can't fpaste00:05
sdakekfox1111 as an eample, just debugging locally, /var/lib/kolla/local_settings contains the line:00:07
sdake#POLICY_FILES_PATH = '/etc/openstack-dashboard'00:07
sdakethat line should not be commented00:07
sdakethat file is coming from kolla-ansible genconfig i assume - let me check what it is inside kolla-ansible00:07
kfox1111yeah. kolla-kubernetes doesn't do any config there.00:09
sdakekfox1111 it apparently copies the files into emptydir right?00:10
sdakewhen the configmaps are generated?00:10
sdakerather to be more precise, the config maps are created from kolla-genconfig artifacts00:11
sdakeand kolla-kubernetes does the config from the config maps00:11
sdakerather kubernetes00:11
sdakewow too tired to compose a straight sentence ;)00:11
kfox1111sdake, the process is as follows:00:11
kfox1111kolla-ansible genconfig generates /etc/kolla/horizon.00:11
kfox1111kollakube res create configmap horzion00:12
kfox1111# takes stuff from /etc/kolla/horizon/* and makes a k8s configmap out of it all and uploads it to k8s as configmap name 'horizon'00:12
kfox1111helm install horizon....00:12
kfox1111loads up a deployment object that creates pods that mount configmap 'horizon' at /var/lib/kolla00:13
kfox1111if you do a kubectl get configmaps --namespace=kolla you can see them.00:13
kfox1111and a kubectl get configmap <configmapname> -o yaml --namespace=kolla to look at it if your curious.00:14
sdakehrm00:14
sdakewell here is the contents of the genconfig tempalte:00:14
sdake#POLICY_FILES_PATH = '/etc/openstack-dashboard'00:14
sdakefrom here : /root/kolla-kubernetes/kolla-ansible/ansible/roles/horizon/templates00:14
sdakeso it looks like genconfig is incompatible with kolla-kubernetes00:15
sdakenot entirely sure which version of kolla-ansible is installed00:15
sdakesince for some odd reaosn its installed ina venv00:15
sdakeprobably 3.0.200:15
kfox1111I could believe trunk broke it.00:16
kfox1111its not been tested in a while.00:16
sdakehere is master: https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/horizon/templates/local_settings.j2#L45800:16
kfox1111yeah.00:16
kfox1111try genconfig from kolla 3.0.2 or 3.0.100:17
sdakei'll have to talk to Jeffrey4l_ about this patch: https://github.com/openstack/kolla-ansible/commit/f3ea03d88f3adce4e28c0394e48418251df026b200:17
sdakeits chines enew year and i think he is out for 3-4 days00:18
*** goldyfruit has quit IRC00:18
kfox1111ah.00:18
sdakeok - well in the meantime i'll revert that in my local env - since we dont care about murano at this point in time in kolla-kbuernetes00:18
kfox1111sdake: so...00:18
sdakeok - tiem for dinner00:18
kfox1111edit /etc/kolla/horizon/local_settings,00:18
sdakebmace_ if your around later, i'll be happy to help you out with what i know - but i must feed my children now00:18
bmace_sdake: i think it is an issue with the container pull logic.  inside the dev container there is no docker, which pull_container.sh assumes exists.00:18
kfox1111remove the #,00:18
kfox1111and kubectl create res configmap horzion00:19
sdakekfox1111 ya i've done that00:19
sdakekfox1111 i've actually got horizon working already00:19
kfox1111then delete/recreate horzion deployment.00:19
kfox1111ah. ok.00:19
bmace_sdake: it should really probably be remoting somehow into the kubeX remote hosts it is deploying into to do the container pulls00:19
sdakekfox1111 i was understanding why its busted00:19
kfox1111sdake: ok. didn't know you figured that out.00:19
kfox1111so, its that one line thats broken, thats all?00:19
sdakebmace_ no idea on that one - but i have to admit i am doing a different deployment method then the continer based dev env deploy00:20
sdakekfox1111 pretty sure :)00:20
sdakeits a regression in master from what i can tell00:20
kfox1111bmace_: true.00:20
sdakea critical one - i doubt horizon works in kolla-ansible as well00:20
sdakeinc0 if you manage to get kolla-ansible running can you try horizon00:20
kfox1111bmace_: though I think there was a flag set to have it skip the pulls.00:20
sdakeinc0 try to actually log into it00:20
sdakeok be back in about 45 mins :)00:20
kfox1111sdake: +1. we need to fix it asap.00:20
*** sdake has quit IRC00:20
bmace_kfox1111: but how could it possibly work without the pulls?  is there something else that would get the images pulled onto the kubeX boxes?00:21
kfox1111bmace_: the pulls were to make it less likely to hit the timeout.00:21
kfox1111kube itself will pull the containers.00:21
bmace_kfox1111: after running the entire dev_workflow.sh script they are definitely not there on any of the kubeX systems00:22
kfox1111with the pull, the timeout for waiting for containers doesn't start until its sure all the containers are already downloaded.00:22
kfox1111kubectl get pods --namespace kolla #shows them in what state?00:22
bmace_kfox1111: doesn't show any pods :/00:23
bmace_+ pull_containers00:23
bmace_+ '[' x1 == x ']'00:23
bmace_+ /opt/kolla-kubernetes/tools/wait_for_pods.sh kolla00:23
bmace_containers failed to start.00:23
bmace_NAME                          READY     STATUS              RESTARTS   AGE00:23
bmace_rabbitmq-init-element-c7k0b   0/1       ContainerCreating   0          3m00:23
bmace_that is what i get at the end00:23
bmace_but i see the helm install for all of the services proceeding..00:24
kfox1111kubectl describe pod rabbitmq-init-element-c7k0b --namespace=kolla00:24
bmace_i'm guessing since docker doesn't exist in the container the pull_containers just finishes immediately00:24
kfox1111I think the latest ps makes pull containers do nothing.00:24
kfox1111noop.00:24
*** crushil has joined #openstack-kolla00:25
bmace_  FirstSeenLastSeenCountFromSubObjectPathTypeReasonMessage00:25
bmace_  ------------------------------------------------------------00:25
bmace_  46m46m1{default-scheduler }NormalScheduledSuccessfully assigned rabbitmq-init-element-c7k0b to 172.16.35.1200:25
bmace_  46m46m1{kubelet 172.16.35.12}spec.containers{main}NormalPullingpulling image "docker.io/kolla/centos-binary-rabbitmq:2.0.2"00:25
bmace_  43m43m1{kubelet 172.16.35.12}spec.containers{main}NormalPulledSuccessfully pulled image "docker.io/kolla/centos-binary-rabbitmq:2.0.2"00:25
bmace_  43m43m1{kubelet 172.16.35.12}spec.containers{main}NormalCreatedCreated container with docker id ad837226a459; Security:[seccomp=unconfined]00:25
bmace_  43m43m1{kubelet 172.16.35.12}spec.containers{main}NormalStartedStarted container with docker id ad837226a45900:25
bmace_  43m43m1{kubelet 172.16.35.12}WarningFailedSyncError syncing pod, skipping: failed to "TeardownNetwork" for "rabbitmq-init-element-c7k0b_kolla" with TeardownNetworkError: "Failed to teardown network for pod \"54286bbd-e420-11e6-a08e-52540030c43f\" using network plugins \"cni\": required env variables missing"00:25
kfox1111paste.openstack.org please00:25
kfox1111is that all thats in there, or is there more?00:26
bmace_kfox1111: http://paste.openstack.org/show/596656/00:26
kfox1111seems like the network wasn't inited yet.00:29
kfox1111kubectl get pods --namespace=kube-system00:29
bmace_kfox1111: http://paste.openstack.org/show/596657/00:30
kfox1111is rabbit still stuck?00:31
kfox1111looks like your using weave. never played with it.00:32
kfox1111the gate's testing with canal.00:32
kfox1111not sure it will make a difference. but might.00:33
bmace_well, this is whatever the default is for the halycon-kubernetes stuff00:33
kfox1111yeah.00:33
kfox1111just saying. :)00:33
kfox1111in uncharted waters there. :)00:33
bmace_hrm.. not sure how that is to change, but i can give it a go.. lots of uncharted waters going on here, lol00:34
kfox1111true, true. :)00:34
bmace_i see some logic at least that mentions canal in the kube-deploy stuff for halycon-kubernetes so maybe it won't be too bad.00:35
kfox1111would be interesting to hear what sdake used.00:35
bmace_sdake: what are you using in your k8s environment?00:35
bmace_lol, yeah, same idea00:35
kfox1111but, he's not here it would seem. :/00:35
kfox1111but anyway, for some reason it looks liek the network wasn't ready before the iscsi_workflow was started.00:36
kfox1111the gate blocks running that script until it is ready.00:36
kfox1111so, that might be part of the problem.00:36
bmace_kk, well, i'll see what it takes to get canal working.  would be nice to use the same thing as we do in the gate.00:36
kfox1111yeah. couldn't hurt.00:39
kfox1111if we get a lot of requets for weave support, we could add a weave version of the gates too.00:39
kfox1111canal was just the thing I knew best at the time.00:39
*** sayantani01 has quit IRC00:41
*** MasterOfBugs has quit IRC00:42
*** PramodJ has joined #openstack-kolla00:42
*** pramodrj07 has quit IRC00:42
*** MasterOfBugs has joined #openstack-kolla00:42
*** inc0 has quit IRC00:46
*** hfu has joined #openstack-kolla00:47
*** hfu has quit IRC00:49
v1k0d3nkfox1111: just an observation....00:49
v1k0d3nsounds like the gates are very complicated.00:50
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Adding cleanup service for cinder  https://review.openstack.org/42587500:50
v1k0d3nthe instructions  for kolla-k8s...are they up to date?00:50
sbezverkkfox1111: please check cinder clean up service..00:50
*** lrensing has joined #openstack-kolla00:51
sbezverkkfox1111: I tested it on my cluster, looks ok00:51
v1k0d3nare things able to run? i heard that kolla-k8s is being used in production.00:51
kfox1111v1k0d3n: gates are complicated, but well worth it. they prevent a lot of breakage/regression.00:52
kfox1111the instructions are not up to date. :/ but are actively being woked on by several people right now. should be up to date in the next few days.00:53
kfox1111there is likely to be a production system soonish.00:53
kfox1111sbezverk: will do.00:53
kfox1111sbezverk: please review https://review.openstack.org/#/c/425836/00:53
*** jtriley has joined #openstack-kolla00:54
kfox1111v1k0d3n: the gate is currently running probably dozens of openstack deployments a day now.00:54
kfox1111including testing vm launching, network connectivity, volume attachment/moving/reattachment, etc.00:55
kfox1111so regressions are cought really quickly.00:55
*** sdake has joined #openstack-kolla00:58
kfox1111sdake: ping00:58
v1k0d3ni thought i heard sdake mention there was a production deployment...00:58
sdakewound me00:58
v1k0d3nwhere is that...00:58
sdakewhich?00:58
kfox1111sdake: which network plugin you using for the dev env?00:58
sdakekfox1111 whatever the devenv sets up by default00:58
kfox1111sdake: ok. so, weave.00:58
sdakekfox1111 oh - actually not sure - whatever kubeadm sets up by default00:59
v1k0d3nhttps://sdake.io/00:59
v1k0d3nfront page "and there now are real, production deployments of the kolla-kubernetes deliverable of the OpenStack Kolla project"00:59
sbezverkwow sdake now has his own io domain00:59
sdakev1k0d3n that was my understanding at the time i wrote that blog post00:59
sdakev1k0d3n that kfox1111 had placed his site into production01:00
sdakev1k0d3n it may not be accurate given teh fact horizon doesn't work01:00
kfox1111sbezverk: ok. I can add elementname. it wasn't requried to fix the issue, so i didnt' touch it.01:00
v1k0d3nouch01:00
v1k0d3nok01:00
v1k0d3ndidn't know.01:00
kfox1111sdake: yeah, not quite yet. but soon.01:00
sdakekfox1111 good to hear01:00
sdakev1k0d3n no mal-intent meant, i got impression from kfox1111 he put 0.4.0 in production in the channel01:01
kfox1111horizon works, jujst not with kolla-ansible trunk.01:01
sdakealthough i guess I shouldn't used the word deployments either as that is plural01:01
v1k0d3nit's cool.01:01
sbezverkkfox1111: please do01:01
sbezverkin this case I can remove it completely from my PS01:01
v1k0d3ndoesn't bother me. i just was just curious.01:01
kfox1111sbezverk: ok.01:01
v1k0d3ninstructions would be nice  for you guys though.01:01
v1k0d3nseems like things are moving...too fast for instructions.01:02
sdakev1k0d3n ya - as you know , I don't like to speka about people's personal or professional business specifically01:02
sdakev1k0d3n quickstart is on teh way - hoepfully by monday :)01:02
v1k0d3nit's all good.01:02
sdakebmace_ hows it going on your end bro - arey ou all good?01:03
*** adrian_otto has quit IRC01:03
sdakebmace_ or all bad?01:03
bmace_sdake: i think kfox1111 helped me figure out where my last attempt borked and it seemed to be around the networking, so i'm re-building my kube environment using canal rather than weave.01:04
bmace_canal is what is used in the gate, so more likely to work01:04
sdakesbezverk you cn get your own domain too - 99$ /yr01:04
kfox1111v1k0d3n: yeah. the problem is we need the dev env to be gated too. :/01:04
kfox1111v1k0d3n: that way, if we break something, we catch it, so other devs dont.01:04
kfox1111v1k0d3n: but openstack's normal gates are vm's and nested virutalization is not available. :/01:05
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: PS fixes issue discovered with keystone service package  https://review.openstack.org/42596401:05
sdakenested virt works with qemu mode01:05
sdakehowever the gate machines only have 8gb of ram01:05
sdakei've begged and pleaded for more ram in the vms01:05
sbezverksdake: what a waste of money ;)01:05
kfox1111sdake: yeah. it works for really trivial things like cirros. which the gate does.01:05
*** jrobinson-afk is now known as jrobinson01:06
kfox1111sdake: it fails misurably to run all of openstack in. :/01:06
sdakehowever, in the shoes of the infra folks, putting 16gb across all 9 cloud providers woudl reduce capacity in half01:06
sbezverkkfox1111: I removed overlapping part from my PS01:06
sdakekfox1111 right -the gate oOMS01:06
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Keystone-admin external support  https://review.openstack.org/42583601:06
kfox1111sbezverk: added the search path stuff to mine.01:07
sdakeand until zuul v3, ther is no way to make special snowflake 16gb ramvms01:07
sdakeits not clear if uul v3 comes out if that would b ethe case01:07
v1k0d3nkfox1111: we brought  this up as a concern in barcelona01:07
kfox1111sdake: for this use case we really need bare metal. :/01:07
sdakerather if infra would make 16b vms01:07
sdakev1k0d3n which concern01:07
v1k0d3nin fact, as sdake and inc0 are both aware, we offered to gate as a third party donation to kolla.01:07
sdakei've never been a big fan of 3rd party gating, however, if someone added third party gating its not like we can stop it :)01:08
v1k0d3nsizes, vm-based, no nested, etc to infra.01:08
sdakenor would I stop it01:08
sdakehowever, third party gating can't be voting01:08
sdakealthough the rest of our gates arenot voting01:08
sdakethey are advisory at present01:08
v1k0d3nwell, it would've helped and we offered it. it was being worked out.01:08
sdakev1k0d3n i guess i am missing some context because i just came on the channel01:09
v1k0d3ni just asked if things were working and if instructions were up to date. that's all.01:09
v1k0d3nit's no big deal01:10
kfox1111working, yes. instructions up to date, no, but close.01:10
sdakev1k0d3n working = yes but not keystone - instructions = no not up to date except dev env01:10
sdakev1k0d3n the dev env you put together and portdirect documented is fantastic from my pov01:10
sdakeand the docs have been perfected for that part01:10
kfox1111sdake: keystone's working. just not when used in particular ways that there's a ps for.01:10
v1k0d3nstill working for you guys? actually caught the docker issue, but want to merge in soon. waiting for a second reviewer who's centos-based.01:11
sdakekfox1111 i didn't say it wasn't working :)01:11
v1k0d3nactually sdake, you want to review, try and pass?01:11
kfox1111sdake: btw, https://review.openstack.org/#/c/425836/ please. :)01:11
sdakev1k0d3n sure i can review the centos change when i return home from my folks01:11
sdakekfox1111 getting ready to eat - let me look01:11
*** sayantani01 has joined #openstack-kolla01:12
v1k0d3nsounds good. let me know01:12
sdakekfox1111 that is going to tkae a bit to review ;)01:12
sdakekfox1111 can you wait until after dinner? (about 1 hr)01:12
kfox1111sdake: sure.01:12
sdakev1k0d3n what does try/pass mean there01:12
sdakev1k0d3n you mean test the patch that was submitted?01:12
sdakev1k0d3n if that is what you mean, then yup happy to do that when i get home - i don't have access to my lab here01:13
sdakev1k0d3n my wife is out of town at devconf until tuesday - so pretty much parents offered to help cook dinner a few days this week01:13
sdakev1k0d3n two kids at home + work = overload :)01:14
v1k0d3nsdake: yes, this is the PR that is waiting.01:14
v1k0d3nhttps://github.com/aric49/halcyon-kubernetes/tree/CentOS_issues01:14
v1k0d3ni already passed but we like to have two pass on it.01:14
sdakev1k0d3n looking01:14
v1k0d3ni don't use it anymore.01:14
v1k0d3nkeeping it for whoever needs it now.01:14
v1k0d3nand the gluster folks...they use it for their kubernetes deployments.01:14
v1k0d3ni think port may use it for kolla-k8s.01:15
v1k0d3nwe just use minikube now01:15
*** Syffs has quit IRC01:15
kfox1111yeah. most of the time minikube gets the job done. and is really simple.01:16
sdakev1k0d3n you dont need which - the dev env?01:16
sdakev1k0d3n two tests sounds good - happy to provide a test of it when i get home01:17
sdakelooking at the review, looks like many changes01:17
sdakev1k0d3n the ultimate test is a human test - not a a gate test01:18
sdakev1k0d3n they both go hand in hand01:18
kfox1111sdake: agree/disagree. humans only scale so far.01:23
kfox1111humans got to be able to deploy it, for sure.01:23
sdakekfox1111 agreed01:23
kfox1111but gotta use automation to test things or else things are easily forgotten to be tested.01:24
sdakekfox1111 totally agree on that point, that is why kolla-ansible gating is so weak01:24
kfox1111speaking of testing... your going to love this next ps... :)01:24
sdakedinenr is on - bbiaf01:27
*** sdake has quit IRC01:32
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Check to see if Horizon is working in the gate.  https://review.openstack.org/42602501:43
v1k0d3nkfox1111: true...some humans don't scale01:50
*** v1k0d3n has quit IRC01:51
*** v1k0d3n has joined #openstack-kolla01:53
*** sayantan_ has joined #openstack-kolla01:53
*** sayantani01 has quit IRC01:56
kbaegisHey guys, does anyone know how do disable a horizon plugin on a running environment?02:00
kbaegistacker-horizon has a defective i18n script that is now returning 500s02:00
kbaegishere's the traceback: https://hastebin.com/ikiviladif.sql02:01
*** sdake has joined #openstack-kolla02:04
sdakev1k0d3n looking over that review, the syntax looks correct  -although I'm not sure how that fixes the docker versioning problem02:05
*** hfu has joined #openstack-kolla02:05
sdakev1k0d3n although i have heard that docker-engine 0.13.1 fixes the problem02:06
sdakev1k0d3n althoug hthat ptach coesn't use docker-engine, it uses docker from centos02:07
sdakev1k0d3n i notice pull request #43 fixes the docker version problem02:08
*** MasterOfBugs has quit IRC02:11
*** dims_ has joined #openstack-kolla02:14
*** PramodJ has quit IRC02:14
*** dims has quit IRC02:14
sdakev1k0d3n reviewable looks pretty cool02:17
sdakelike a more hipster version of gerrit ;-)02:17
sdakekfox1111 around?02:21
sdakeI recall having this discussion before about documetnting the syntax of : https://review.openstack.org/#/c/425836/3/helm/microservice/keystone-create-endpoints-job/templates/keystone-create-endpoints.yaml02:21
sdakekfox1111 specifically kolla_get_val_get_str02:22
*** tonanhngo has quit IRC02:27
*** lrensing has quit IRC02:32
sdakesbezverk what was the fix for trunk ?02:32
sdakeinc0 sort that out?02:32
*** zhubingbing has joined #openstack-kolla02:36
openstackgerritMerged openstack/kolla-kubernetes: Keystone-admin external support  https://review.openstack.org/42583602:37
*** zhubingbing has quit IRC02:38
kfox1111back.02:42
*** absubram has joined #openstack-kolla02:43
kfox1111sdake: https://raw.githubusercontent.com/openstack/kolla-kubernetes/master/helm/kolla-common/templates/_common_val_get.rst02:44
sdakekfox1111 cool - thanks :)02:44
sdakekfox1111 i think we need to sort out how to get that linked in to the mian docs somehow, although no idea how02:45
kfox1111yeah.02:45
sdakekfox1111 - how did the trunk problem get fixed?02:45
kfox1111the keystone-admin patch that just merged.02:45
kfox1111still a few race conditions left I think.02:46
*** dims_ has quit IRC02:47
kfox1111sdake: check this one out... https://review.openstack.org/#/c/426025/ :)02:47
*** absubram has quit IRC02:48
*** absubram has joined #openstack-kolla02:49
*** dims has joined #openstack-kolla02:50
sdakekfox1111 - thought that was related to the docker images?02:51
sdakeget me the anestaphine from the medlock!02:51
sdakebrb02:51
kfox1111sdake: no. its a test for checking horizon login works and whatever else we want to check in horizon.02:52
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Check to see if Horizon is working in the gate.  https://review.openstack.org/42602502:54
sdakekfox1111 - will review whne i get back to my house in 30 mins - brb02:56
*** yuanying has quit IRC02:56
*** sdake has quit IRC03:00
*** goldyfruit has joined #openstack-kolla03:10
*** jtriley has quit IRC03:11
*** sdake has joined #openstack-kolla03:26
*** severion has joined #openstack-kolla03:27
*** crushil has quit IRC03:28
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Check to see if Horizon is working in the gate.  https://review.openstack.org/42602503:28
*** crushil has joined #openstack-kolla03:28
sdakekfox1111 that test looks pretty cool !03:29
sdakekfox1111 not sure how it works in detail03:29
sdakekfox1111 i don't see anything popping out at me as in error03:29
*** jrobinson has quit IRC03:31
*** jrobinson has joined #openstack-kolla03:35
kfox1111sdake: yeah. selenium is really slick.03:37
kfox1111even more awesome when combined with k8s.03:37
kbaegisHow does k8s do with ceph?03:38
openstackgerritcaoyuan proposed openstack/kolla-ansible: Optimize reconfigure action for telegraf  https://review.openstack.org/42420203:41
kfox1111sdake: https://review.openstack.org/#/c/425847/ please.03:41
kfox1111sdake: its passed all tests at least once.03:41
kfox1111(I'm still working on stabilizing the gate. this ps is part of that)03:42
kfox1111kbaegis: not sure what your asking.03:42
kfox1111sdake: if we can get that through before tomorrow morning, we should have some cached containers to help stabilize the gate.03:42
kfox1111sbezverk: can you review https://review.openstack.org/#/c/425847/ too please.03:43
portdirect_travlkfox1111: re selium, great work - but should it be in with the other services?03:44
portdirect_travlkfox1111: this is only a testing/gate tool right?03:44
kfox1111portdirect_travl: in microservices you mean?03:46
kfox1111yeah, intended just for testing.03:46
portdirect_travlthis one: https://review.openstack.org/#/c/426025/03:46
kfox1111portdirect_travl: if you have a sec, could you do https://review.openstack.org/#/c/425847/ too please?03:46
portdirect_travlwas thinking that im not sure the chart should be in helm/service, but tests or somewhere else?03:47
kfox1111portdirect_travl: yeah. wasn't sure where to put it. :/03:48
*** prameswar has joined #openstack-kolla03:48
kfox1111sdake: http://www.seleniumhq.org/docs/07_selenium_grid.jsp :)03:50
sdakesup portdirect_travl03:51
sdakehows brno besides freezing cold03:51
sdakeportdirect_travl my recommendation to you is to HOLD ON TO YOUR CHANGE03:51
sdakeits more valuable then currency there ;-)03:52
sdakeportdirect_travl good news - mostly have the dev environment working locally03:52
sbezverkportdirect_travl: please see clean up thing I put together: https://review.openstack.org/#/c/425875/03:52
sdakeportdirect_travl needs a bit of love03:52
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Check to see if Horizon is working in the gate.  https://review.openstack.org/42602503:53
*** kbaegis has quit IRC03:54
sdakehey fellas, that temporary issue with the gate (4.0.0b2) is about to be permanent as kolla-ansible is getting ready to release)03:55
kfox1111when is the final release?03:56
kfox1111it still has the horizon bug too.03:56
sdakekfox1111 sbezverk portdirect_travl and others - note the recheck on this patch: https://review.openstack.org/#/c/425809/103:56
sdakeit should be green this time around03:57
sdakesince kfox1111 fixed the problem with keystone admin03:57
kfox1111sdake: yeah. it needs rebasing.03:57
kfox1111its still using the wrong endpoint.03:57
openstackgerritMerged openstack/kolla-kubernetes: Fix for the periodic kolla-kubernetes processes.  https://review.openstack.org/42584703:59
kfox1111nice. thanks. :)03:59
kfox1111I've gotta head out.03:59
*** sdake_ has joined #openstack-kolla03:59
kfox1111sbezverk: I'll finish reviewing your ps tomorrow. from what I've read so far, it looks good. :)03:59
*** sdake has quit IRC04:02
*** eaguilar has joined #openstack-kolla04:08
openstackgerritSteven Dake proposed openstack/kolla-ansible: Revert part of a murano patch which breaks horizon  https://review.openstack.org/42604804:10
sdake_kfox1111 what needs rebasing?04:10
sdake_kfox1111 it hasn't finished the recheck yet04:10
sdake_kfox1111 what i am pointing out is patches don't need rebases - once a patch merges, the infrastructure rebases automatically04:11
*** sdake has joined #openstack-kolla04:22
*** sdake_ has quit IRC04:23
*** goldyfruit has quit IRC04:29
*** mdnadeem has joined #openstack-kolla04:30
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Check to see if Horizon is working in the gate.  https://review.openstack.org/42602504:31
*** prameswar has quit IRC04:37
*** eaguilar has quit IRC04:42
sdakekfox1111 you will notice no rebsae, yet the gate is passing with your change and keystone endpoint list: https://review.openstack.org/#/c/425809/04:42
sdakekfox1111 rebases are not necessary ^^04:43
sdakethe only time a rebase is necessary is if there is a merge conflict04:43
*** absubram has quit IRC04:55
kfox1111sdake: weird. I could have swarn I've seen that not work before.04:58
kfox1111oh well. good to know. thanks.04:58
sdakekfox1111 its been working like that for atleast 3 years ;-)04:58
sdakekfox1111 nonintuitve  Iknow04:58
*** tonanhngo has joined #openstack-kolla05:03
sdakesup tonanhngo05:05
sdakeyo - bmace_ check out this issue: https://github.com/att-comdev/halcyon-vagrant-kubernetes/issues/5005:05
sdakebmace_ it may be what your running into05:05
*** tonanhngo has quit IRC05:07
*** skramaja has joined #openstack-kolla05:15
kfox1111sdake, it can be normal for that to hapen for a bit until the cni driver loads.05:20
kfox1111usually things settle down after a while.05:20
sdakekfox1111 its been 30 minutes same result05:20
kfox1111ah. shouldn't take that long for sure.05:20
kfox1111a couple minutes to pull all the cni containers tops.05:21
sdakeyup i suspect somethign is busted05:21
sdakewhich is why i filed the issue :)05:21
sdakei'm going to look at debugging it today i guess-  my son slept all damn day and i have to stay up with him now05:21
kfox1111k. good luck. :)05:22
sdakeya05:22
kfox1111heading to bed. nite all.05:22
sdakelater dude05:22
bmace_sdake: that is exactly the same issue i am hitting05:24
sdakebmace_ should log an issue for me to read about ;-)05:24
sdakebmace_ plus others05:24
bmace_sdake: i tried swapping from weave to canal and it didn't fix it.05:24
sdakebmace_ i have an old vagrant environment here that works05:24
sdakewant a tarball of it to help me debug it? :)05:24
bmace_tarball of the one that isn't working?  i have that myself :)05:25
sdakeno th etarball of the working one05:25
sdakewithout vms in it05:25
sdakegit diff ftw05:25
sdakeor diff :)05:25
bmace_ah, what does it have in it exactly? it is just the halycon-kubernetes repo?05:25
sdakeor something - it canbe fixed05:25
sdakeif it workedd before it will work again05:25
sdakeits halcyon-vagrant-kubernetes and halcyon-kubernetes05:26
sdakeas a submdoule05:26
sdakefull working environment05:26
bmace_even if you know what revision it is at, i can just check them out from there05:26
bmace_commit hash05:26
sdakeportdirect logged into m ybox and made some chagnes to the code05:27
bmace_based on the diffs between the hash and current we might be able to figure out why it broke too05:27
sdakei suspect the changes are why it is working05:27
sdakenot regressions in the codebase05:27
bmace_ah, so you can just generate a diff?05:28
bmace_or he did non code related changes?05:28
sdakei can give it a go - let me see git status05:28
sdakevagrant: http://paste.fedoraproject.org/537385/54949391/ -> http://paste.fedoraproject.org/537385/5494939105:29
sdakeagainst the submodule in that repo05:29
bmace_hrm, those are both the same paste?05:30
sdakehere are the changes to the submoduel: http://paste.fedoraproject.org/537386/85494993/ -> http://paste.fedoraproject.org/537386/8549499305:30
sdakeya its a bug in fpaste05:30
sdakeit prints out the url twice05:30
sdakeits supposed to use an url shortener, not sure what happend with the url shorterner05:30
bmace_interesting.. moving calico rather than weave or canal05:30
sdakeits been broken for like a year05:30
sdakemake it harder ;-)05:31
bmace_let me give the all.yml changes a try05:31
sdakeglad you spotted something i am bleary eyed05:31
bmace_although, you are using iscsi right, and this says to setup ceph05:31
sdakethats a different environment actually :)05:32
bmace_maybe that doesn't matter.. in the older / working env it was using ceph?05:32
sdakei am pretty sure yo ucan setup ceph05:32
bmace_maybe i need to go back to that05:32
sdakeand it will be ok05:32
sdakemy other environment is as follows:05:32
sdakekubeadm + kubernetes on bare metal - not in vms05:32
sdakethat is the one i've been developing the iscsi_workflow.sh patch on05:33
sdakeit is possible iscsi_workflow doesn't work with the development environment05:33
sdakei really haen't tested that at all05:33
sdakeif it doesn't should be easy to fix05:34
bmace_but this kube based one was working for you also?  if so, i'll go down this path05:34
sdakeit is but i have no idea how it is setup05:34
bmace_seems semi-obvious based on the config. most of it was the same as mine other than calico and ceph05:35
sdakecool let me try that in the master version of the dev env too05:36
sdakethen we can get the workflow working on that05:36
sdakei'd like the workflow to be flexible so we can figure out how to use this thing outside the gate :)05:36
openstackgerritSajauddin proposed openstack/kolla: Kolla support for power server  https://review.openstack.org/42323905:37
sdakei am really struggling to figure out how to operate kolla-kubernetes however have leraned a bunch doing the workflow05:37
bmace_yup, and being able to quickly redeploy kolla-k8s changes into a vagrant environment like this would be great for dev / testing.05:37
sdakeagreed05:38
bmace_yeah.. i do have to say, ansible is far simpler05:38
sdakethe bare metal setup is super pokey turnaround times05:38
bmace_at least to run / debug.. which is saying something, because ansible can be sort of annoying to debug at times too, but not nearly as bad as kolla-k8s.. but maybe better once i spend more time with it.05:38
sdakeit would be cool to rework all that in ansible i think for the short term instead of shell05:38
bmace_it will be a lot more work to make it easy to diagnose for operators though05:39
sdakeya - i do want an operator based approach or a entrypoint based approach (both)05:39
sdakei think I am finding i see alot of stuff that could be codified more easily in something besides shell05:39
sdakeansible for our gates - whee ;)05:39
bmace_yeah.. i really don't like shell :/  python is heaven in comparison imo05:40
*** saneax-_-|AFK is now known as saneax05:40
sdakeanyway going to give calico a go first - then calco + ceph05:40
sdakei'm not sure what the defaults re05:40
sdakere storage05:40
bmace_yeah, that is a good plan. i may also.. it seems like a networking type complaint so maybe calico alone will fix it05:41
sdakei ahven't played with the halcyon dev enviornment much - but think it is solid from what i've done with it05:41
*** prameswar has joined #openstack-kolla05:45
*** david-lyle has quit IRC05:46
*** crushil has quit IRC06:07
*** crushil has joined #openstack-kolla06:09
*** crushil has quit IRC06:15
*** prameswar has quit IRC06:39
openstackgerritSurya Prakash Singh proposed openstack/kolla: Docs updated to get coverage report  https://review.openstack.org/42503206:44
*** unicell1 has quit IRC06:46
*** sayantan_ has quit IRC06:54
openstackgerritJoseph Robinson proposed openstack/kolla-ansible: Build deploy guide files and tox environment  https://review.openstack.org/42610507:00
*** bmace_ has quit IRC07:07
*** bmace_ has joined #openstack-kolla07:07
*** hfu has quit IRC07:09
*** hfu has joined #openstack-kolla07:17
*** msimonin has quit IRC07:18
*** jrobinson has quit IRC07:22
*** sdake has quit IRC07:33
*** prameswar has joined #openstack-kolla07:45
*** msimonin has joined #openstack-kolla08:04
*** mgoddard has joined #openstack-kolla08:34
*** egonzalez has joined #openstack-kolla08:44
*** msimonin has quit IRC08:44
*** msimonin1 has joined #openstack-kolla08:44
*** matrohon has joined #openstack-kolla08:50
*** shardy_afk is now known as shardy08:52
*** msimonin1 has quit IRC08:56
*** Serlex has joined #openstack-kolla08:59
*** rmart04 has joined #openstack-kolla09:01
*** mgoddard has quit IRC09:05
*** zioproto has joined #openstack-kolla09:05
*** papacz has joined #openstack-kolla09:37
*** mgoddard has joined #openstack-kolla09:37
egonzalezJeffrey4l_: around?09:43
*** hfu has quit IRC09:47
*** hfu has joined #openstack-kolla09:47
*** hfu has quit IRC09:48
*** hfu has joined #openstack-kolla09:48
*** hfu has quit IRC09:49
*** hfu has joined #openstack-kolla09:49
*** hfu has quit IRC09:49
*** hfu has joined #openstack-kolla09:50
*** hfu has quit IRC09:50
*** hfu has joined #openstack-kolla09:51
*** hfu has quit IRC09:51
*** hfu has joined #openstack-kolla09:51
*** hfu has quit IRC09:52
egonzalezpomac: ping09:54
pomacegonzalez: pong =)09:55
egonzalezmy issue was that keystone db was in latest schema and keystone container in previous version09:55
pomacegonzalez: oh - humm... This included the NoneType?09:55
egonzalezin master, when there is not defualt domain_id is automatically added09:56
egonzalezbut need to add under identity section default_domain_id09:56
*** msimonin has joined #openstack-kolla09:58
pomacegonzalez: default_domain_id should default to 'default' according to the documentation afair09:58
egonzalezyep09:58
egonzalezfor back compatible with v2 where default was added everywhere09:59
pomacegonzalez: we think that our problem started when we changed it to something else - but we're not certain10:00
*** absubram has joined #openstack-kolla10:02
pomacafk, bbl10:02
*** absubram has quit IRC10:07
*** prameswar has quit IRC10:15
*** zhubingbing has joined #openstack-kolla10:20
egonzalezzhubingbing: happy new year :)10:24
zhubingbinghi10:24
zhubingbingthank you  very muc10:24
zhubingbingmuch10:24
zhubingbing;)10:24
zhubingbingthanks10:24
*** pbourke has quit IRC10:30
*** pbourke has joined #openstack-kolla10:31
openstackgerritMerged openstack/kolla-ansible: Optimize reconfiguration for grafana  https://review.openstack.org/42415810:35
*** prameswar has joined #openstack-kolla10:39
openstackgerritzhubingbing proposed openstack/kolla-ansible: Add freezer ansible role  https://review.openstack.org/40222410:42
*** msimonin1 has joined #openstack-kolla10:43
*** msimonin has quit IRC10:44
*** shardy has quit IRC10:45
*** shardy has joined #openstack-kolla10:46
openstackgerritMerged openstack/kolla-ansible: Optimize reconfiguration for solum  https://review.openstack.org/42416710:53
openstackgerritzhubingbing proposed openstack/kolla-ansible: Add freezer ansible role  https://review.openstack.org/40222410:53
openstackgerritzhubingbing proposed openstack/kolla-ansible: Add freezer ansible role  https://review.openstack.org/40222410:56
*** gfidente has joined #openstack-kolla10:56
*** gfidente has quit IRC10:56
*** gfidente has joined #openstack-kolla10:56
openstackgerritzhubingbing proposed openstack/kolla-ansible: Add freezer ansible role  https://review.openstack.org/40222411:02
openstackgerritzhubingbing proposed openstack/kolla-ansible: Add freezer ansible role  https://review.openstack.org/40222411:10
*** bachp has quit IRC11:10
*** vcn[m] has quit IRC11:10
*** retr0h has quit IRC11:10
*** hfu has joined #openstack-kolla11:13
*** sambetts|afk is now known as sambetts11:14
openstackgerritzhubingbing proposed openstack/kolla-ansible: Add freezer ansible role  https://review.openstack.org/40222411:19
*** retr0h has joined #openstack-kolla11:22
*** saneax is now known as saneax-_-|AFK11:24
*** boycer has joined #openstack-kolla11:26
*** boycer has quit IRC11:32
des_consoladohey I'm trying to follow this http://docs.openstack.org/newton/networking-guide/config-bgp-dynamic-routing.html11:45
des_consoladoI've used kolla-ansible though and have everything running in containers11:45
des_consoladocan anybody advise me on how I'm supposed to do this? I mean I can change the neutron.conf to have that extra ',bgp' easy enough, but this bgp agent ...11:45
*** jtriley has joined #openstack-kolla11:45
des_consoladoI guess I need to set up a new container? Does this mean I need to build a new image too?11:45
mliimahi guys11:47
des_consoladohi11:49
egonzalezdes_consolado: yed, for bgp agent will need another container11:53
des_consoladoegonzalez: would this be a good thing to add to the project as a PR?11:54
egonzalezabout config, you can use merge_configs, being said in /etc/kolla/config/neutron.conf you can apply your changes and will be merged11:54
des_consoladoah yes I've seen that11:54
des_consoladomaybe there is like a neutron agent base image or something... will have a look11:55
des_consoladoyeah there is a neutron base image11:55
des_consoladoso I guess maybe I need to look at the Dockerfile for that and then edit it appropriately and tag it as a neutron bgp speaker image?11:56
des_consoladoand then I need to write all the ansible playbooks in the right places for the various kolla-ansible actions?11:56
*** bachp has joined #openstack-kolla11:56
*** vcn[m] has joined #openstack-kolla11:56
egonzalezmostly that, create a dockerfile inside neutron/neutron-bgp-agent/Dockerfile or somename similar11:57
egonzalezand modify neutron role to apply changes whn bgp is enabled11:58
des_consoladoyeah and use a var in globals and a default in group vars :))11:58
des_consoladocool, exciting stuff, I will give this a shot11:58
*** zhubingbing has quit IRC11:58
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible: Implement Keystone zero-downtime upgrade  https://review.openstack.org/42544612:00
*** tonanhngo has joined #openstack-kolla12:02
*** Penfold has joined #openstack-kolla12:06
*** tonanhngo has quit IRC12:06
*** jtriley has quit IRC12:11
*** severion has quit IRC12:11
openstackgerritMerged openstack/kolla-ansible: Add freezer ansible role  https://review.openstack.org/40222412:12
*** shardy is now known as shardy_lunch12:18
*** kbaegis has joined #openstack-kolla12:21
*** kbaegis has quit IRC12:23
*** kbaegis has joined #openstack-kolla12:23
*** eaguilar has joined #openstack-kolla12:23
*** zhubingbing has joined #openstack-kolla12:27
*** eaguilar has quit IRC12:29
*** rhallisey has joined #openstack-kolla12:47
openstackgerritNenad Radojevic proposed openstack/kolla-ansible: Use neutron user in neutron_lbaas.conf and overwrite defaults  https://review.openstack.org/42515012:49
openstackgerritcaoyuan proposed openstack/kolla-ansible: Fix the undefined error for vmtp_vm_availability_zone  https://review.openstack.org/42571512:53
openstackgerritcaoyuan proposed openstack/kolla-ansible: Optimize reconfiguration for octavia  https://review.openstack.org/42384613:02
*** srwilkers has joined #openstack-kolla13:03
*** srwilkers has quit IRC13:03
*** srwilkers has joined #openstack-kolla13:04
openstackgerritzhubingbing proposed openstack/kolla: Fix code format ceilometer_compute dockerfile  https://review.openstack.org/42622413:04
openstackgerritcaoyuan proposed openstack/kolla-ansible: Fix the missing  certificate files  https://review.openstack.org/42622513:06
openstackgerritcaoyuan proposed openstack/kolla-ansible: Fix the missing certificate files for octavia  https://review.openstack.org/42622513:07
srwilkersmorning gents13:08
*** mgiles has joined #openstack-kolla13:09
des_consoladohi13:11
egonzalezzhubingbing: why abandoned the PS?13:11
*** goldyfruit has joined #openstack-kolla13:11
zhubingbing;)13:11
*** goldyfruit has quit IRC13:11
Jeffrey4l_egonzalez, do u have any idea about https://bugs.launchpad.net/kolla-ansible/+bug/1659799 ?13:13
openstackLaunchpad bug 1659799 in kolla-ansible "containers are not replaced while upgrading" [Critical,New]13:13
zhubingbingis only applied at binary install atm13:13
egonzalezJeffrey4l_: when is copy_always only a restart is applied https://github.com/openstack/kolla-ansible/blob/master/ansible/library/kolla_docker.py#L58013:15
Jeffrey4l_egonzalez, oh, right.13:15
egonzalezdon't really know how to proceed on that, just changed mine to copy_once to finish keystone upgrade13:15
Jeffrey4l_need fix the restart_or_recreate_container method.13:16
egonzalezbtw, happy new year13:16
Jeffrey4l_egonzalez, thanks13:16
Jeffrey4l_i will push a fix later.13:16
*** shardy_lunch is now known as shardy13:17
*** mdnadeem has quit IRC13:23
sbezverkJeffrey4l_: I think I have a good news for you ;) rememeber that iscsi issue?13:34
*** sdake has joined #openstack-kolla13:34
sdakemorning peeps13:35
sbezverksrwilkers: good morning! do you mind to review a couple of my PS please?13:35
Jeffrey4l_sbezverk, hrm. which error?13:35
Jeffrey4l_morning13:35
sbezverkJeffrey4l_: when you have iscsi initiator utils installed on the host then cinder volume fails13:35
Jeffrey4l_have u solved it?13:35
sdakeJeffrey4l_ i thought you would be on pto13:36
sdakeJeffrey4l_ since its chinese new year - grats!13:36
sdakeJeffrey4l_ since your here - can you look at this 1 liner13:36
Jeffrey4l_sdake, yep.13:36
Jeffrey4l_thanks.13:36
sbezverkJeffrey4l_: I think so :) instead of completely removing it completely, you need to stop iscsid.socket.13:36
Jeffrey4l_sbezverk, hrm. iscid should not be run on the host.13:37
sdakehttps://review.openstack.org/#/c/426048/13:37
sbezverksystemd is listening on it and that is what prevents iscsid in the container to start properly13:37
srwilkersmorning sdake13:37
srwilkerssbezverk, of course dude! good morning!13:37
sdakeJeffrey4l_ note i dont know if it works or not13:37
sdakesup srwilkers13:37
srwilkerssdake, not me yet13:37
sdakeJeffrey4l_ it looks to me by talking with dave-lyle yesterday that horizonz is completely busted in master13:38
Jeffrey4l_sdake, i know the issue. but move POLICY_FILES_PATH to /etc/openstack-dashboard may cause other issue.13:38
sbezverkJeffrey4l_: for kube case, I must have initizator tools on the host as it is required to support kubernetes iscsi backend13:38
sdakeJeffrey4l_ they are already there per the json descriptor13:38
sbezverkso I need to dig deeper than just removing it comepltely from the host13:38
Jeffrey4l_I think /etc/openstack-dashboard is OK. but need copy the horizon policy, which located in openstack-dashboard/conf/*.policy to /etc/o-d13:39
sdakeJeffrey4l_ however if yo uahve a better way to fix it, i'm all ears )13:39
Jeffrey4l_sdake, this merged yours. and add "moving all horizon policy to /etc/o-d folder" in kolla13:39
sdakeJeffrey4l_ looking inside the images, they are actually in /etcopensack-dashboard already13:39
Jeffrey4l_let me check..13:40
sdakeJeffrey4l_ note i was using the 2.0.2 images13:40
sdakeand i htink i looked at 3.0.2 too13:40
*** prameswar has quit IRC13:40
*** jheroux has joined #openstack-kolla13:40
sdakethis may be a version incompatibility with horizon and different versions of kolla13:41
sdakei wasn't sure hence asked for you to take a look )13:41
sdake;)13:41
Jeffrey4l_sdake, yep. you are correct.13:41
Jeffrey4l_+2ed for your patch.13:41
sdakeJeffrey4l_ i think the ultimate test - which i didnt do - was to test that patch against masater13:41
sdakeJeffrey4l_ i don't want to break kolla-ansible :)13:42
Jeffrey4l_you fixed it ;)13:42
sdakeJeffrey4l_ kolla-kuberfnetes has a gate job incoming for testing horizon - and a login thereof13:42
sdakeif we can cross repo gate both repos over itme, it will be super powerful13:43
Jeffrey4l_sbezverk, iscsid mount /run:/run:shared in kolla-ansible.13:43
sdakewe will have two deliverables all gating each other13:43
sdakerather 313:43
sdaketime for bed :)13:43
openstackgerritMerged openstack/kolla-ansible: Optimize reconfigure action for cloudkitty  https://review.openstack.org/42251613:43
sdake;-)13:43
Jeffrey4l_yep. hoping that.  kolla-k8s deployment gate should be ran in kolla project.13:43
Jeffrey4l_sdake, night13:43
sdakei just woke up13:44
sdakejust can't compose a sentence13:44
sdake;-)13:44
Jeffrey4l_sdake, could u approve https://blueprints.launchpad.net/kolla/+spec/add-chrony-service , it is already implemented.13:45
egonzalezJeffrey4l_: done13:47
*** sdake_ has joined #openstack-kolla13:48
Jeffrey4l_egonzalez, thanks.13:48
*** sdake has quit IRC13:48
sbezverksrwilkers: do you need links?13:50
openstackgerritJeffrey Zhang proposed openstack/kolla: Fix the murano policy file path  https://review.openstack.org/42623713:52
srwilkerssbezverk, nope. poking through them slowly :)13:52
sbezverksrwilkers: replied to your first review :)13:53
openstackgerritJeffrey Zhang proposed openstack/kolla: Add neutron vpnaas code into neutron-server container  https://review.openstack.org/41997713:54
*** lrensing has joined #openstack-kolla13:54
openstackgerritMerged openstack/kolla-ansible: Fix the undefined error for vmtp_vm_availability_zone  https://review.openstack.org/42571513:56
*** prameswar has joined #openstack-kolla13:56
openstackgerritMerged openstack/kolla-ansible: Revert part of a murano patch which breaks horizon  https://review.openstack.org/42604813:56
*** goldyfruit has joined #openstack-kolla13:58
openstackgerritJeffrey Zhang proposed openstack/kolla: Add neutron vpnaas code into neutron-server container  https://review.openstack.org/41997714:00
*** lamt has joined #openstack-kolla14:01
sdake_srwilkers re the dev env, there  is issue #5014:10
sdake_srwilkers bmace_ foudn out last night from my diff while i was bleary eyed that the dev env onlly works with calico for some reason14:11
sdake_any thoughts on that?14:11
sdake_it doesn' tappear to work with weave or flannel iiuc ;)14:11
sdake_but maybe its not flanenl14:11
sdake_I can't keep all the CNI layers straight :)14:11
sdake_rather implementations14:11
sdake_https://github.com/att-comdev/halcyon-vagrant-kubernetes/issues/5014:13
srwilkerssdake_, let me look at the issue. tl;dr though, if its not working, it needs to be fixed asap. let me finish reviewing sbezverk's patch sets then ill see what's up with it14:13
sdake_srwilkers when using calico - it works :)14:13
sdake_srwilkers i think portdirect_travl had kne wabou t this issue earlier14:13
sdake_srwilkers as he had loggedin to my box remotely a few weeks ago and set  that setting14:14
sdake_srwilkers and he mentioned something about it - which i have since forgotten14:14
*** absubram has joined #openstack-kolla14:14
sdake_srwilkers atleast now its in an issue tracker ;-)14:14
sdake_srwilkers also the submoduel needs an update14:15
sdake_srwilkers i don't know how to do that without -dirty being appended to the submodule for whatever reason14:15
srwilkerssdake_, yeah, thats a start. but need to look at ensuring this is managed long term. i mentioned getting gates set up to make sure it's compatible with kolla-kubernetes on our end14:15
srwilkersi need to make sure that process is expedited14:15
sdake_srwilkers there are ways to gate inside github14:16
sdake_srwilkers i have seen them used by other projects14:16
sdake_srwilkers i dont know how its done - i know travis-ci is one option14:16
srwilkerssdake_, yep, actually part of whats had me busy lately14:16
srwilkerssdake_, sbezverk brb coffee14:18
*** srwilkers is now known as srwilkers_coffee14:18
*** absubram has quit IRC14:18
*** rhallisey has quit IRC14:21
*** absubram has joined #openstack-kolla14:24
*** msimonin1 has quit IRC14:26
*** rhallisey has joined #openstack-kolla14:28
*** rhallisey has quit IRC14:28
*** rhallisey has joined #openstack-kolla14:28
*** saneax-_-|AFK is now known as saneax14:29
*** rhallisey has quit IRC14:30
*** fguillot has joined #openstack-kolla14:31
openstackgerritzhubingbing proposed openstack/kolla: Fix code format ceilometer_compute dockerfile  https://review.openstack.org/42622414:38
*** jtriley has joined #openstack-kolla14:39
*** saneax is now known as saneax-_-|AFK14:40
*** lrensing has quit IRC14:40
openstackgerritzhubingbing proposed openstack/kolla: Fix code format ceilometer_compute dockerfile  https://review.openstack.org/42622414:40
*** boycer has joined #openstack-kolla14:41
*** srwilkers_coffee is now known as srwilkers14:42
*** lrensing has joined #openstack-kolla14:43
boycerHello all. Looking into using kolla to deploy a cloud in a production environment. Any advice? Any gotchas? Any other deployment method I should use instead?14:43
sdake_boycer kolla-ansible is super stable, kolla-kubernetes is a work in progress14:44
sdake_boycer if you ar edeploying a production cloud use kolla-ansible14:44
sdake_boycer the quickstart in the docs should get you going14:44
sdake_boycer the docs are here http://docs/openstack/org/developer/kolla14:45
sdake_boycer note several folks are working on cleaning up the kolla-ansible docs to make them more consumable14:45
boycersdake_: great, thanks a lot. I'll go read the kolla-ansible doc.14:46
matrohonhi14:47
boycersdake_: I may be back ;)14:48
matrohonwe test deployments with kolla 3.0.3, and we meet an issue with kolla-toolbox14:48
sdake_srwilkers i noticed you changed the etherpad to "collobartion between openstack operators and helm"14:48
sdake_srwilkers which sounds fine to me - however, most of the people on the workgroup arenot operators14:48
matrohonit's like the kolla-start cmd is not run with the ansible user14:48
sdake_srwilkers here: https://etherpad.openstack.org/p/openstack-helm14:49
sdake_srwilkers what was your thinking behind that change - I'd like that workgroup to be more of a neutral ground for openstack to comunicate with helm14:49
sdake_indepndent of whatever project we have14:50
sdake_however i'm not sure operators in genreeal care ;)14:50
matrohonbut with a user that only exists on the host!14:50
matrohondoes anybody know a corresponding bug in kolla?14:50
matrohonsdake_, ^14:51
sdake_matrohon have to get son ready for school no time to debug sadly14:51
matrohonsdake_, np we keep investigating...14:51
sdake_matrohon then have meetings in the morning14:51
sdake_matrohon generally overloaded :)14:51
matrohonsdake_, I just wanted to know if it was a known bug at kolla14:52
sdake_srwilkers ya thats kind of weird to oand so was deployment projects :)14:53
srwilkerssdake_, yeah, fair point on operators14:53
srwilkerstrying to think of a better wording for that14:53
sdake_srwilkers ya - I think the workgroup is what we make of it as a community14:53
sdake_and that hsould be one community (openstack)14:53
sdake_how about OpenStack upstreams?14:54
srwilkerswell, its key to remember that some of these groups are outside of the openstack community. it should ideally be a general call where anyone interested in leveraging helm for openstack deployments can participate, even if they're using a solution not under the openstack umbrella14:54
srwilkersthat works14:54
sdake_srwilkers ya i totally ge tthat, and want neutral groudn as I stated14:55
openstackgerritzhubingbing proposed openstack/kolla: remove /var/log/trove in trove dockerfile`  https://review.openstack.org/42625414:55
sdake_language can be overly powerful sometimes14:55
sdake_and this is one of those casees :)14:55
*** athomas has joined #openstack-kolla14:55
srwilkerssdake_, yes it can :)14:55
sdake_anyway thats the best suggestoin i've got for now14:56
srwilkerssdake_, works for me. i think you nailed it14:56
sdake_someone may come along and want us to change it yet again :)14:56
*** crushil has joined #openstack-kolla15:01
openstackgerritzhubingbing proposed openstack/kolla: Fix swift dockerfile  https://review.openstack.org/42626015:01
sbezverksrwilkers: any feedback on my cleanup service ;) ??15:02
srwilkerssbezverk, looking through it now, almost done :)15:04
*** absubram has quit IRC15:06
*** sayantani01 has joined #openstack-kolla15:09
*** zhubingbing has quit IRC15:10
openstackgerritJeffrey Zhang proposed openstack/kolla: rootwrap filters is removed in networking-sfc  https://review.openstack.org/42626315:13
*** l4yerffeJ_ has joined #openstack-kolla15:14
*** dasTor_ has joined #openstack-kolla15:14
srwilkerssbezverk, left a few comments inline but looks good to me otherwise :)15:14
*** l4yerffeJ has quit IRC15:15
*** dasTor has quit IRC15:15
*** zhubingbing has joined #openstack-kolla15:15
*** msimonin has joined #openstack-kolla15:17
openstackgerritzhubingbing proposed openstack/kolla: remove /var/log/trove in trove dockerfile  https://review.openstack.org/42625415:19
openstackgerritMerged openstack/kolla-ansible: Optimize reconfiguration for kuryr  https://review.openstack.org/42416115:21
*** hieulq_ has joined #openstack-kolla15:23
*** srwilkers is now known as srwilkers_brb15:23
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Adding cleanup service for cinder  https://review.openstack.org/42587515:26
sayantani01Hi Jeffrey4l_ Can you please review this patch when you have time? :) https://review.openstack.org/#/c/424384/15:27
sdake_well gotta sya kolla-kubernetes is looking good :)15:28
sdake_it works - which is the first step :)15:28
sdake_kfox1111 sbezverk since the gate is your babies, I wanted your input on the work there15:29
sdake_kfox1111 sbezverk how do you feel about ansible to run the gate jobs longer term15:29
sdake_i find the current shell script to be super duper complicated to process mentally15:29
Jeffrey4l_sayantani01, done.15:30
openstackgerritMerged openstack/kolla-ansible: Optimize reconfigure action for telegraf  https://review.openstack.org/42420215:30
kfox1111heh.15:30
sdake_its not a criticism - shell is always hard :)15:31
kfox1111ansible based orchestration was the origional plan.15:31
sdake_yup i hear ya15:31
*** zioproto has quit IRC15:31
kfox1111theres a lot of progress on the helm+kuberntees-entrypoint workflow.15:31
kfox1111is that more understandable?15:32
sdake_i think that was a case of too many people making decisions wihtout understanding what was there15:32
kfox1111heh. thats for true. :/15:32
sdake_kfox1111 i havent 'taken a look at that yet - been lazer focused on iscis workflow15:32
kfox1111sdake_: do have a look at ceph_workflow_service.sh15:32
kfox1111the top half will look just like iscsi_workflow.15:33
kfox1111but the bottom half should look much more simple.15:33
sdake_i have been reviewing that code actually and know what is there15:33
*** lamt has quit IRC15:33
kfox1111ideally, we can combine it all to one helm install kolla/compute-kit15:33
sdake_if you meant entrypoint workflow by that - then yup thats alot simpler15:33
kfox1111yeah.15:33
sdake_i thitnk we still want to maintian the gate jobs for the microcharts15:34
kfox1111agreed.15:34
sdake_that provides alot more coverage of the system15:34
kfox1111the majority of the remaining complexity is in the configmap/secret stuff.15:34
*** ipsecguy has quit IRC15:34
kfox1111we haven't migrated that stuff to helm yet.15:34
sdake_ya i'm going to take a look at unwinding that into kolla itself15:34
kfox1111once that's done, it should be a lot simpler.15:34
sdake_rather kolla-kubernetes15:34
sdake_after the docs are in working order15:34
sdake_we need to exit genconfig imo15:35
sdake_although ansible does a fine job of getting us there15:35
kfox1111having to setup a bunch of python stufff, run genconfig, configure things, fix up some config, and load them is really complicated.15:35
sdake_i agree15:35
kfox1111yeah.15:35
kfox1111I have some thoughts on how to get there, but need to prototype things and/or talk about it at the ptg.15:36
sdake_i'm not sure if i will start on that work prior to ptg15:36
sdake_so it may be an opportune time to look at it then15:36
sdake_although I may get started earlier - depends on my workload :)15:36
kfox1111yeah. I just usually like to have a good idea of some options before I go into a discussion. :)15:37
kfox1111I talked trhough some options with Jeffrey4l_ to see what oslo could support.15:37
sdake_my current work is as follows15:37
*** satyar has joined #openstack-kolla15:37
sdake_1. sort out the dev env to ramp people up15:37
sdake_2. sort out the docs so peopel can actualluy install kolla-kubernetes15:37
sdake_3. drop the dep on kolla-ansible15:38
sdake_gotta take kid to school brb15:38
satyarhi sdake_15:38
kfox1111me too.15:38
satyarHi SamYaple15:38
kfox1111sdake_: I think if we can get the dev env mostly into a container, and a helm package added to kubernetes/charts,15:40
kfox1111it would be super easy to get started with the dev env.15:40
kfox1111spawn up a simple k8s system, helm install stable/kolla-dev-env15:40
kfox1111kubectl exec -it kolla-dev-env /bin/bash15:40
kfox1111and go.15:40
kfox1111nothing to install.15:40
Serlexthat would be nice15:41
*** zhubingbing has quit IRC15:41
sbezverksdake_: absolutely against it15:43
sayantani01Thanks Jeffrey4l_15:43
sayantani01:)15:43
Jeffrey4l_np.15:43
sbezverksdake_: I think after we clean up and use common code at the gate, it will be perfect.15:44
sbezverkkfox1111: about your comment. the reason thise keystone vars are there baecuase I did not want to polute all.yaml15:45
*** srwilkers_brb is now known as srwilkers15:45
matrohonegonzalez, hi15:47
egonzalezmatrohon: sup15:47
matrohonegonzalez, I'm trying to figure out what's going wrong with latest dnsmasq in fedora15:48
matrohonhttps://bugs.launchpad.net/kolla/+bug/165579415:48
openstackLaunchpad bug 1655794 in kolla "dnsmasq dhcp lease is not cleaned up after instance termination" [Undecided,New]15:48
*** absubram has joined #openstack-kolla15:49
*** saneax-_-|AFK is now known as saneax15:49
matrohonegonzalez, can you confirm that can't hit the bug with centos 7.3 and dnsmasq 2.66?15:49
*** hieulq_ has quit IRC15:49
sdake_sbezverk it may be perfect for the gate, but no tperfect for a dev env15:49
sdake_anyway have a meeting will be back :)15:50
sdake_kfox1111 dev env added to kubernetes helm charts would be interesting to me15:50
sdake_kfox1111 not sure if that is something the helm maintainers would tkae or not15:51
egonzalezmatrohon: deploying15:51
srwilkerssdake_, ive been thinking about development environment lately too. when you get back, we should chat15:53
openstackgerritMerged openstack/kolla-ansible: Optimize reconfiguration for octavia  https://review.openstack.org/42384615:53
sbezverksdake_: if you talk about dev env, why you suggest it for the gate?15:53
sdake_srwilkers the hwole world thinks bout dev env :)15:54
sdake_sbezverk at present the scripts are integrated15:54
sdake_sbezverk i'll be back in 1 hr, we can chat then15:54
sbezverkskake_ ok15:54
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Adding cleanup service for cinder  https://review.openstack.org/42587516:02
*** robcresswell has joined #openstack-kolla16:04
*** adrian_otto has joined #openstack-kolla16:05
*** v1k0d3n has quit IRC16:06
*** adrian_otto has quit IRC16:09
*** rhallisey has joined #openstack-kolla16:11
*** adrian_otto has joined #openstack-kolla16:12
*** lamt has joined #openstack-kolla16:12
*** adrian_otto has quit IRC16:13
*** crushil has quit IRC16:15
*** crushil has joined #openstack-kolla16:16
*** v1k0d3n has joined #openstack-kolla16:16
*** v1k0d3n has quit IRC16:21
*** saneax is now known as saneax-_-|AFK16:21
*** v1k0d3n has joined #openstack-kolla16:21
*** prameswar has quit IRC16:25
*** zioproto has joined #openstack-kolla16:28
*** david-lyle has joined #openstack-kolla16:29
*** zioproto has quit IRC16:32
*** zioproto has joined #openstack-kolla16:33
egonzalezmatrohon: is working fine for me http://paste.openstack.org/show/596747/16:35
egonzalezthere are my centos and dnsmasq versions16:35
egonzalezin both container and host16:35
matrohonok, thanks16:36
matrohonegonzalez, ubuntu 16.04, dnsmasq 2.7616:37
matrohonegonzalez, I'm not sure wether dnsmasq is faulty here16:38
matrohonegonzalez, if it is, the bug should have been reported for a long time in neutron16:39
kfox1111back.16:39
srwilkerskfox1111, wb16:41
bmace_sdake_: looks like the swap to calico may not have fixed it.  going to look at my env shortly but wasn't working when i went to sleep.16:41
*** egonzalez has quit IRC16:41
kfox1111sdake_: doesn't hurt to ask them.16:41
kfox1111sdake_: worst case, we maintain the package ourselves. still would be easier then deploying that part by hand I think.16:41
sbezverkkfox1111: clean up comment.16:41
kfox1111lookin16:42
sbezverkkfox1111: I think the root of this issue is common/global/ etc.. if all.yaml had global section in a normal way, then all these would not be necessary16:43
kfox1111srwilkers: would not searching for 'delete' still work as its in the package name?16:44
*** srwilkers has quit IRC16:44
kfox1111sbezverk: just for context, we're talkg about the values.yaml issue I raised?16:44
*** srwilkers has joined #openstack-kolla16:44
sbezverkkfox1111: it looks to me that all.yaml is less global api16:44
srwilkersback, dropped16:44
sbezverkkfox1111: correct16:44
kfox1111sbezverk: k.16:45
kfox1111sbezverk: I think the issue woudl be resolved if we made an example user's values.yaml16:45
kfox1111alot of the stuff you want to put in services/*/values.yaml would be more clear there I think?16:45
kfox1111the same file coudl then be used for all services too.16:45
kfox1111I see the service packages largly as just for launching the sets of microservices with deps.16:46
sbezverkkfox1111: do not follow, where you want to have user's values.yaml?16:46
kfox1111the config belongs to either the microservices, or the users values.yaml.16:46
kfox1111so, back in the before helm time, we had an /etc/kolla-kubernetes/kolla-kubernetes.yaml.16:47
sbezverkkfox1111: can we have two values.yamls?16:47
kfox1111it was a single place for the user to configure everything.16:47
*** absubram has quit IRC16:47
kfox1111I think we shoudl provide an example of something like that, similr to16:47
kfox1111tests/bin/common_workflow_config.sh but just as a flat yaml.16:48
kfox1111with all the default settings in it?16:48
kfox1111then if a user wants to tweak inidividual settings, they know which settings they can tweak.16:48
kfox1111then we make it a documented standard practice to allways pass that values.yaml file when launching.16:48
sbezverkkfox1111: I get the idea of user's values.yaml what I do not get where you want to put it?16:48
kfox1111oh. in the repo?16:49
sbezverkkfox1111: which folder?16:49
kfox1111not sure.16:49
sbezverkand how user/service will know where it is16:49
kfox1111make an /examples dir?16:49
kfox1111services wont know. user shoudl always pass.16:49
kfox1111but the user should be informed  via docs.16:49
kfox1111the dev env guide for example.16:50
sbezverkkfox1111: but look, you said you want vlaues.yaml with user configurable default16:50
kfox1111which values.yaml?16:50
kfox1111(too many. :/ )16:50
kfox1111maybe we make the example's one have everythign commented out?16:50
sbezverkthere should be a location where this customized file is stored for the service to use it when it gets installed16:50
kfox1111that way they know what the defaults are, but they arnt overriding whtas in the packages by default?16:51
kfox1111user should specify it when launching the service. helm install kolla/neutron --values examples/mycloud.yaml16:51
sbezverkkfox1111: I think we again talk about different things.. it seems you talk about documenting for the use, I talk about this practical issue I have now with supplying bunch of default but confiugrable vars to a specific service16:52
sbezverkcan we address one thing at the time?16:52
kfox1111k.16:52
kfox1111the problem I saw in your review,16:52
kfox1111is you had a bunch of values that you set, that weren't overrides.16:52
kfox1111so extra code, that we have to maintain, whith no benifit?16:52
sbezverkkfox1111: ok I agree it does not look great16:53
sbezverkkfox1111: how about changing all.yaml and instead of using common/global/kolla use just global/kolla ...16:53
kfox1111I believe your reasoning, was to make it easier to dicover the settings that coudl be overridden?16:53
sbezverkin this case vars in global/kolla in all.yaml will become visible to the service16:54
kfox1111sbezverk: oh. just pull the onen common section back a level?16:54
sbezverkyes16:54
*** crushil has quit IRC16:54
kfox1111It is visible to the service now I think.16:54
sbezverkget rid of common tag completely16:54
kfox1111that won't change anything I think.16:54
kfox1111it just puts them in the microservices packages.16:55
kfox1111are you wanting to generate the service values.yaml's too?16:55
sbezverkkfox1111: but would it not all.yaml be searchable from service poi9nt of view?16:55
*** unicell has joined #openstack-kolla16:55
*** unicell has quit IRC16:55
*** unicell has joined #openstack-kolla16:55
kfox1111currently no.16:56
kfox1111service has a static values.yaml file.16:56
kfox1111it then calls each microservice package.16:56
kfox1111which has its own values.yaml file.16:56
kfox1111that values.yaml file is generated from all.yaml16:56
kfox1111the service values and the microservice values are merged at thtat point, I believe,16:56
kfox1111so it ends up using global.kolla.all.* from all.yaml16:57
kfox1111unless overridden in the services values.yaml or the users values.yaml.16:57
sbezverkkfox1111: in this case microsercice needs to have all common values, basically each microservice needs to have all keystone related parameters16:57
kfox1111yeah. and each microservice gets its own values from all.yaml.16:58
sbezverkin this case services's values.yaml will not need them16:58
kfox1111right.16:58
sbezverkkfox1111: I think the problem is in "its own"16:58
kfox1111the user can still override them in their own values.yaml.16:58
sbezverkI think its own needs to be extended to include some16:58
kfox1111I don't quite follow.16:58
kfox1111some what?16:59
*** inc0 has joined #openstack-kolla16:59
sbezverkok to be able to get keystone_user_name I have two options16:59
sbezverk1. add it to service's values.yaml16:59
sbezverk2. get it somehow from microservice17:00
kfox1111sorry. there is some abbiguity there. lets try and clarify.17:00
sbezverkcurrently if I do not specify it in service's values.yaml I do NOT get it from the microservice17:00
kfox1111what hat do you have on for that use case? a dev, or an operator deploying k8s?17:00
sbezverkcleanup service17:00
kfox1111oh.17:01
kfox1111I think I know the issue.17:01
kfox1111common-create-keystone-admin17:01
kfox1111the values you want are in common-create-keystone-admin section, not common. so they aren't automatically added to the microservice.17:01
sbezverkkfox1111: right17:01
inc0o/17:01
kfox1111your microservices that need those types of common values need to be added to tools/helm_prebuild_microservices.py in the list common_create_keystone_admin17:02
kfox1111then it should work.17:02
kfox1111won't need anything in the servie package's values then.17:02
kfox1111(and we really need a subpackage values include feature from helm. :/ )17:03
sbezverkkfox1111: we have great API now I think what you suggested (I will do it) is more like a workaround17:03
*** matrohon has quit IRC17:04
sbezverkwould be great to be able to use API and search without any software tools/tricks17:04
kfox1111sbezverk: if we don't manage it in one place, all_values.yaml, then we will have to remember to make changes to lots of individual packages. it will be a pain to maintain, and cause bugs. :/17:04
kfox1111its a partial workaround until helm gets a feature natively to help with the issue. :/17:04
kfox1111+117:05
kfox1111that needs helm to mature some more though. :/17:05
kfox1111its being worked on though.17:05
sbezverkkfox1111: the way you suggested, would it require adding items to all.yaml as well?17:05
sbezverkkfox1111: I would really like not to do it from safety perspective17:06
kfox1111no. should just need to add it to the list, and remove the values from services.yaml related to keystone17:06
*** eaguilar has joined #openstack-kolla17:06
sbezverkkfox1111: ok17:06
kfox1111and region.17:06
*** zioproto has quit IRC17:07
kfox1111maybe we can generate an example/mycloud.yaml from all the microservices.yaml...17:07
*** zioproto has joined #openstack-kolla17:08
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Adding cleanup service for cinder  https://review.openstack.org/42587517:10
sbezverkkfox1111: region needs to be removed too?17:11
*** athomas has quit IRC17:11
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Adding cleanup service for cinder  https://review.openstack.org/42587517:12
*** eaguilar has quit IRC17:12
sbezverkkfox1111: this morning cleanup service helped me. I installed cinder on my cluster using service package and then lvm using microservice17:13
mliimaJeffrey4l_, can you review it https://review.openstack.org/#/c/422157/17:13
kfox1111sbezverk: yeah. it also comes in with that common-create-keystone-admin: section.17:14
sbezverkthen I noticed that cinder service installs 2.0.2 images by default and volume was crashing insce it runs 3.0.217:14
sbezverkremoving cinder with cleanup was nice and quick :)17:14
kfox1111sbezverk: yeah. we need to finish up that multiversion patch I had started I think. then we can make a versions.yaml file for 2.x and 3.x with all the right settings.17:15
kfox1111right know its a bit half and half. :/17:15
kfox1111sbezverk: cool. :)17:15
kfox1111would be interesting to get the gate stuff to use the cleanup stuff.17:15
sbezverkkfox1111: I wish I had the same for keystone yesterday ;)17:15
kfox1111at the end of the gate run, run throuh the cleanup scripts17:15
kfox1111and see if everythign goes away. :)17:15
kfox1111should be really quick so shouldn't add much time to the gate.17:16
sbezverkkfox1111: I wanted to add it to the workflow, install cinder remove cinder re-install cinder and see if basic tests work17:16
kfox1111ah.17:17
kfox1111was thinking about doing something similar with the gate upgrade job17:17
kfox1111think that would work to kill two birds with one stone? or is that a different use case?17:17
kfox1111ugg... still haven't made a common section for mariadb stuff. :/17:20
kfox1111man I really want helm to fix this. :/17:20
sbezverkkfox1111: do not follow upgrade case, if you could clarify a bit17:20
kfox1111we have 2.x and 3.x working in the gate now.17:21
kfox1111so we should be able to start with the 2.x gate, and then helm upgrade everything to 3.x.17:21
sbezverkkfox1111: right but during upgade we do not delete anything I thought17:22
kfox1111hmm... true.17:22
kfox1111I guess they are seperate then.17:22
kfox1111but, would it be essentially the same code if we had a second varient that,17:23
kfox1111everywhere it had helm upgrdae, it did a helm delete; helm install instead?17:23
inc0Jeffrey4l_, you up?17:23
sbezverkkfox1111: I am not sure yet how it will work, as db manage needs to be smart enough to understand it is upgrade scenario17:23
*** Jeffrey4l_ has quit IRC17:24
*** unicell has quit IRC17:24
srwilkerssbezverk, yep. thats the challenge17:24
kfox1111I think all things but maybe neutron, its just a "foo-manage db_sync"17:24
kfox1111so there is no difference between init and upgrade.17:24
*** Jeffrey4l_ has joined #openstack-kolla17:24
kfox1111though I think that may bring up an issue with helm service upgrades....17:25
kfox1111it probably wont rerun the managedb job. :/17:25
sbezverkkfox1111: Unless I miss something, I do not think upgrade is doable now with the code we have17:25
kfox1111microservices upgrades, yes.17:25
kfox1111service packages, maybe not.17:25
*** sayantan_ has joined #openstack-kolla17:26
sbezverkkfox1111: right with microservices you just skip step create db and maybe replace manage db step by upgrade db step17:27
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Periodic gate fix #2  https://review.openstack.org/42631817:28
kfox1111yeah.17:28
sbezverkkfox1111: I have never done upgrade myself, my upgrade practice was wipe out and start new from scratch ;)17:28
kfox1111not many folks have successfully upgraded an openstack. :/17:28
*** egonzalez90 has joined #openstack-kolla17:29
kfox1111sbezverk: I wana make sure the delete stuff works individually as well as with the service package.17:29
*** rmart04 has quit IRC17:29
kfox1111There's a bit of refactoring of all_values I think would help with that.17:29
*** sayantani01 has quit IRC17:29
kfox1111let me whip up a ps real quick that does that. shouldn't take but a few minutes.17:29
*** egonzalez90 has quit IRC17:30
openstackgerritMerged openstack/kolla-ansible: Optimize reconfigure action for cinder  https://review.openstack.org/42238417:30
*** tonanhngo has joined #openstack-kolla17:30
openstackgerritMerged openstack/kolla-ansible: Fix RabbitMQ server error in bifrost  https://review.openstack.org/42438417:30
sbezverkkfox1111: it does, if you provide values.yaml17:30
*** shardy has quit IRC17:31
kfox1111oh... I see why I didn't roll up the mariadb stuff...17:33
kfox1111two of the fields are service specific.17:33
kfox1111I could roll up 2 of the fields though...17:33
kfox1111would make it easier to change the db's location/port globally...17:34
*** tonanhngo has quit IRC17:35
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla: Allow the use of previously built parent images  https://review.openstack.org/42632217:36
*** Penfold has quit IRC17:36
*** srwilkers is now known as srwilkers_lunch17:37
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla: Allow the use of previously built parent images  https://review.openstack.org/42632217:38
inc0pbourke, do you have multinode around?17:38
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Make common config section for mariadb packages  https://review.openstack.org/42632417:38
pbourkeinc0: yeah17:38
inc0did you rebuild/redeploy lately?17:38
kfox1111meeting. bbiab.17:38
inc0with fresh images?17:39
*** zioproto has quit IRC17:40
pbourkeinc0: hmm probably not for a day or two17:42
pbourkeinc0: heading home now but if you have something you want me to check let us know and I'll get to it monday17:42
inc0hmm I'm having strange issues17:42
inc0well, galera fails for me17:42
pbourkenetworking by any chance?17:42
pbourkeoh17:42
*** adrian_otto has joined #openstack-kolla17:43
*** Penfold has joined #openstack-kolla17:49
*** mgoddard has quit IRC17:50
*** unicell has joined #openstack-kolla17:54
kfox1111back.17:54
openstackgerritMerged openstack/kolla: Docs updated to get coverage report  https://review.openstack.org/42503217:54
*** crushil has joined #openstack-kolla17:55
kfox1111sbezverk: couple of things. could you rebase the cleanup ps on https://review.openstack.org/#/c/426324 . also, could you file a blueprint for cleanup packages? would be nice to be able to track that.17:55
sbezverkkfox1111: I have already bp for cleanup services17:56
sbezverkit is attached to my PS17:56
kfox1111sbezverk: ah. cool.17:56
kfox1111just was blind then.17:56
kfox1111I see it now.17:56
sbezverkkfox1111: since everytime when I try to rebase one ps on another I get into troubles, I will wait for you to merge and then remove mariadb related 2 lines17:58
*** lrensing has quit IRC17:59
kfox1111ok. works for me.17:59
*** harlowja has joined #openstack-kolla18:02
*** hfu has quit IRC18:02
sbezverkkfox1111: I do not get databe_name and database_user from all.yaml18:04
sbezverkkfox1111: I explained why I think adding delete related tags in all.yaml is dangerous18:05
kfox1111sbezverk: the package has to be added to the list to get it.18:05
kfox1111I really want to fix this with subpackages. :/18:06
kfox1111asking the helm folks how hard that would be.18:06
sbezverkkfox1111: it will not be now, it will take wekks at best, are you suggesting to put no hold then?18:06
*** sambetts is now known as sambetts|afk18:07
kfox1111no, I think we fix it to be consistent with the other ones we've got in the mean time.18:07
kfox1111I really don't like this hack, but consistency is best.18:07
*** tonanhngo has joined #openstack-kolla18:08
sbezverkkfox1111: you see if we had one section of global/kolla/all which would not require tool to be avaialbe to microservice it would have been much much easier18:09
sbezverkkfox1111: if you check all.yaml each microservice has duplicated bunch of keystone related vars18:10
sbezverkthey are identical18:10
sbezverkhttp://paste.openstack.org/show/596765/18:11
sdake_david-lyle thanks for the horizon review and the assistance!18:12
kfox1111sbezverk: yeah. those should be merged up into a common config too. :/18:12
kfox1111that part is still kind of a mess. :/18:12
jascott1kfox1111 if you want to hit a pastebin I can form it up into proposal18:13
jascott1i know you to be busy sir18:13
kfox1111k.18:13
jascott1brb18:14
*** l4yerffeJ_ has quit IRC18:14
*** l4yerffeJ_ has joined #openstack-kolla18:15
*** m1dev has joined #openstack-kolla18:19
*** JoseMello has joined #openstack-kolla18:21
*** Syffs has joined #openstack-kolla18:22
kfox1111sbezverk: https://review.openstack.org/#/c/426318/18:25
kfox1111wow. two ps's in a row all green first time.18:27
kfox1111seems like the gate stabilization work is finally starting to kick in. :)18:27
kfox1111any other kolla-kubernetes cores awake?18:27
*** mgoddard has joined #openstack-kolla18:28
inc0ok guys, fire alarm, mariadb is confirmed broken18:30
inc0deploying 3.0.2 works, deploying 4.0.0 breaks18:30
inc0ubuntu source18:30
sdake_kfox1111 i'm barely alive18:31
kfox1111is it a clustering issue?18:31
inc0seems like it18:31
inc0first node stands18:31
kfox1111sdake_: https://review.openstack.org/#/c/426324/ and https://review.openstack.org/#/c/426318/18:31
inc0rest of nodes dont18:31
kfox1111sdake_: both shoudl be easy reviews.18:31
kfox1111sdake_: the first is blocking sbezverk18:31
inc0that's why it didn't show up in gates I bet18:31
sdake_roger18:31
sbezverkkfox1111: I think we should keep keystone user vars in service values.yaml18:32
kfox1111sdake_: thanks.18:32
kfox1111sbezverk: I'm very much against putting any values in services values.yaml other then for deps.18:32
*** vhosakot has joined #openstack-kolla18:32
kfox1111sbezverk: microservices need values too.18:32
kfox1111sbezverk: so lets set them in one place, in microservices.18:32
sbezverkkfox1111: ok fine, I will then create tags for delete in all vlaues yaml18:33
kfox1111otherwise, we risk introducing bugs, when we fix something in microservices values and forget about services, or visa versa.18:33
kfox1111yes please.18:33
kfox1111thanks.18:34
*** gfidente has quit IRC18:37
openstackgerritsayantani proposed openstack/kolla: Fix pushing images to local registry  https://review.openstack.org/42633818:37
sdake_bmace_ - if your around -could you report your finidngs on teh halcyon issue tracker?18:38
sdake_bmace_ i guess i took your feedback last night and ran with it and said calico works when in fact it does not18:38
*** david-lyle has quit IRC18:39
*** ipsecguy has joined #openstack-kolla18:40
bmace_sdake_: last night i just said i would try it.  in the end the outcome was the same.  none of the 3 network options seemed to make a difference.  weave, canal / calico18:40
sdake_bmace_ roger i guess i misunderstood18:41
sdake_bmace_ kind of passed out at the keyboard ;)18:41
openstackgerritMerged openstack/kolla-kubernetes: Make common config section for mariadb packages  https://review.openstack.org/42632418:41
openstackgerritsayantani proposed openstack/kolla: Fix pushing images to local registry  https://review.openstack.org/42633818:41
portdirect_travlo/18:42
openstackgerritMerged openstack/kolla-kubernetes: Periodic gate fix #2  https://review.openstack.org/42631818:42
portdirect_travlhey peeps18:42
portdirect_travlbmace_:  not got context but may be able to help with CNI options in halcyon - whats up?18:42
sdake_portdirect_travl https://github.com/att-comdev/halcyon-vagrant-kubernetes/issues/5018:43
sdake_portdirect_travl the env you setup on my box works like a champ18:43
sdake_portdirect_travl using master does nto work like a champ18:43
sdake_portdirect_travl i dumped a diff of the repo and submodule for bmace_ to replicate18:43
sdake_portdirect_travl that you setup18:43
bmace_portdirect_travl: https://github.com/att-comdev/halcyon-vagrant-kubernetes/issues/5018:44
bmace_damn, you beat me18:44
sdake_bmace_ i already had it open18:44
sdake_was correcting my incorrect commenatry18:44
sdake_bmace_ if you still hve the links handy - otherwise i have to disconnect from irc to dump it quickly18:44
sdake_bmace_ maybe portdirect_travl will see something in the diffs18:44
bmace_portdirect_travl: sdake_ : https://paste.fedoraproject.org/537385/54949391/18:45
portdirect_travlsdake_:  that was my thought :/ - I'll check now18:45
bmace_portdirect_travl: sdake_: https://paste.fedoraproject.org/537386/85494993/18:45
sdake_portdirect_travl current speculation is that the config is different, not that master is broken18:45
jascott1kfox1111 can you edit that issue to prepend "proposal:" in the title ? i would but dont have perms to your issue18:45
bmace_based on the changes in there i assume that env is indeed using ceph?  did we verify that sdake?  would be odd if ceph vs. iscsi made a diff with that kind of error but, once you eliminate everything else, what is left must be the problem? :)18:46
sdake_bmace_ we haven' teven got to ceph yet with the instructions to launch busybox18:47
sdake_bmace_ although kubernetes does require some type of baacking storagef system such as ceph18:47
sdake_bmace_ did you change your config to iscsi?18:47
sdake_bmace_ the first step we are after is launching busybox - and that works in one environment and not in another18:48
sdake_sweet my fsa paid for my new glasses :)18:48
*** mliima has quit IRC18:49
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Adding cleanup service for cinder  https://review.openstack.org/42587518:50
bmace_i have my dev env stuff set up in the same was as the current upstream dev review, which is using iscsi / isci_workflow rather than ceph18:51
bmace_the original version of the review was written to use ceph18:51
bmace_and ceph_workflow18:51
sbezverkkfox1111: added changes.. but man what you suggested will explode the size of all_values.yaml it is huge now but this will make it even bigger :(18:52
kfox1111sbezverk: yeah. its a temporary thing. :/18:55
kfox1111sbezverk: please weigh in on: https://github.com/kubernetes/helm/issues/188318:55
kfox1111I'm hoping we can get that through pretty quickly.18:55
portdirect_travlbmace_/sdake_  any chance you could paste your ./halcyon-kubernetes/kube-deploy/group_vars/all.yml file?18:55
kfox1111then we can fix this much more helm natively.18:55
sdake_portdirect_travl you got it -need to reconnect18:57
bmace_portdirect_travl: http://paste.openstack.org/show/596771/18:57
openstackgerritsayantani proposed openstack/kolla-ansible: [WIP] Update Kolla-Ansible documents  https://review.openstack.org/42635218:57
bmace_portdirect_travl: swapped that calico value between weave, calico and canal and all had the same behavior18:57
*** sdake_ has quit IRC18:58
openstackgerritsayantani proposed openstack/kolla-ansible: [WIP] Update Kolla-Ansible documents  https://review.openstack.org/42635218:58
portdirect_travlbmace_:  just set up a fresh clone now - 10 mins and I'll hopefully be able to repoduce, if it works for me thats when i sad panda18:59
*** sdake has joined #openstack-kolla18:59
sdakeportdirect_travl working: http://paste.fedoraproject.org/537826/43583148/ -> http://paste.fedoraproject.org/537826/4358314819:00
bmace_yeah, hopefully you break like us :)19:00
sdakeportdirect_travl broken: http://paste.fedoraproject.org/537827/48554364/ -> http://paste.fedoraproject.org/537827/4855436419:01
*** srwilkers_lunch is now known as srwilkers19:01
portdirect_travlsake just found typo in dev doc - could you fix?19:01
sbezverkkfox1111: I suggested an alternative solution ;) in the proposal19:01
portdirect_travl./setup-halcyon.sh \19:02
portdirect_travl    --k8s-config kolla \19:02
portdirect_travl    --k8s-version v$KOLLA_KUBERNTES_VERSION \19:02
portdirect_travl    --guest-os centos19:02
kfox1111k. looking19:02
portdirect_travlKOLLA_KUBERNTES_VERSION is spelt wrong - we all missed it :(19:02
srwilkerstheres a patch set that needs one more +2 to merge to fix that portdirect_travl19:03
srwilkershttps://review.openstack.org/#/c/425946/19:03
portdirect_travlcheers srwilkers :)19:04
kfox1111sbezverk: just skimmed through it. looking good to me. goign over one more time.19:05
openstackgerritMerged openstack/kolla-kubernetes: Fix typos in development environment documentation  https://review.openstack.org/42594619:05
kfox1111sdake: portdirect_travl awesome. does that mean the dev env works?19:08
kfox1111the docs for it I mean.19:08
sdakewow i'm a bunch of fial19:08
sdakefail19:08
kfox1111I'd reallly like to see that var name changed.19:09
kfox1111its not the version of kolla-kubernetes thats being specified, but the version of kubernetes.19:09
sdakekfox1111 which var name19:09
sdakeright19:09
sdakei'll fix that in the change19:09
kfox1111thanks. :)19:09
sdakethanks portdirect_travl for the diag19:09
*** lrensing has joined #openstack-kolla19:09
sdakewe need to fix that at a minimum - still no idea if that fixes the whole schebang19:10
sdakesubmitting patch shortly19:10
*** absubram has joined #openstack-kolla19:10
portdirect_travl2 mins - your and bmaces configs did not show the symptoms of it though19:10
*** unicell has quit IRC19:12
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Adding cleanup service for cinder  https://review.openstack.org/42587519:12
kfox1111sbezverk: looks great. thanks for working on that, and bearing with me. I think that triggered a good discussion on the helm side. hopefully it will speed up the implementation.19:14
*** absubram has quit IRC19:15
sbezverkkfox1111: thanks :) I hope devs will find it useful when start playing with services package...19:18
*** absubram has joined #openstack-kolla19:18
* srwilkers nods19:19
sdakebmace_ when I started heat years ago I had a dream of gating the docs19:19
sdakebmace_ in terms of are they functional19:19
sdakebmace_ we tried, and the community never got it rolling - even 5 years later :(19:19
sdakeoh well - thats what humans arefor :)19:19
sdakemust pick up son from school19:20
*** l4yerffeJ_ has quit IRC19:22
*** l4yerffeJ_ has joined #openstack-kolla19:23
openstackgerritsayantani proposed openstack/kolla-ansible: Update Kolla-Ansible documents  https://review.openstack.org/42635219:24
sayantan_Hi everyone19:25
sbezverkkfox1111: one more question. about explicit and implicit dependencies19:25
sayantan_There is a huge duplication of Kolla-ansible related documents in both Kolla and Kolla-ansible repositories. Changes have been made to these docs in Kolla repo and corresponding changes have not been made in Kolla-ansible19:26
sayantan_I have ported the changes made to these docs in Kolla to Kolla-ansible19:26
sbezverkkfox1111: srwilkers and myself were discussing this ps, appreciate your input here: https://review.openstack.org/42596419:27
jascott1hi sayantan_19:27
portdirect_travlsdake/bmace_  sad panda :( https://paste.fedoraproject.org/537844/14855452/raw/19:27
sayantan_Hi jascott119:27
sayantan_how is it going?19:27
jascott1good good. we have sunshine today :)19:27
sayantan_jascott1 I hope you get to enjoy it :)19:28
sayantan_Don't spend too long indoors :P19:28
sayantan_sdake, inc0 can you please take look when you have time https://review.openstack.org/#/c/426352/19:29
Serlexdgonzalez can you take a look at https://review.openstack.org/#/c/425148/19:29
jascott1this is truer than people realize https://www.youtube.com/watch?v=BBUxZdWJ_zE19:29
Serlexor sdake19:29
sayantan_jascott1 That is scary in a way for people back in Texas19:30
jascott1yeah we lack some sun but also dont have TX hail, tornadoes and floods and even hurricanes so pros/cons :)19:32
jascott1of course we will fall off into the sea someday but every silver lining has a touch of grey19:32
portdirect_travlbmace_: could you paste the output of (set -x; kubectl version; ansible --version; vagrant --version)19:34
kfox1111sbezverk: looking19:35
portdirect_travlhttps://www.irccloud.com/pastebin/ENmcSF99/19:35
sbezverkkfox1111: what I still fail to undersatnd how it worked at the gate with these dependecies :(19:37
*** crushil has quit IRC19:37
bmace_portdirect_travl: will do once i have things deployed again.  was trying to rebuild my kubeX env to try out running with ceph_workflow rather than iscsi_workflow as your initial review had it implemented19:39
*** crushil has joined #openstack-kolla19:40
kfox1111the before change deps?19:40
kfox1111lets see...19:41
kfox1111the endpoint creation job, required a mariadb to be up and reposive, which should be fine...19:42
kfox1111but keystone-admin/public/internal too...19:42
*** unicell has joined #openstack-kolla19:42
kfox1111that does seem like a problem.19:42
*** jheroux has quit IRC19:43
kfox1111well...19:44
kfox1111oh.19:44
kfox1111lets see..19:44
sbezverkdependency on service should never work as the backend is provided by keystone api19:44
kfox1111keystone-create-endpoints actually just registers keystone endpoints into keystone.19:44
sbezverkand in my cluster I saw it right away19:45
kfox1111well... it "kolla_keystone_bootstrap's...19:45
kfox1111yeah. this seems broken.19:45
kfox1111but it is working in the gate?19:45
openstackgerritsayantani proposed openstack/kolla-ansible: Update Kolla-Ansible documents  https://review.openstack.org/42635219:45
sbezverkkfox1111: look create_keystone_endpoint: depends on keystone-admin service19:45
kfox1111yeah. that should cause the dep container to fail I think.19:46
sbezverkkeystone-admin-svc object is there but it does not have endpoint associated19:46
kfox1111the endpoints in keystone and the svc endpoints are completely seperate things.19:46
kfox1111not sure they really depend on each other.19:46
sbezverkkfox1111: exactly, that is what I saw in my cluster.. I cannot see how it worked at the gate19:46
kfox1111but  Ido think api needs t ohappen after endpoints creation.19:46
kfox1111the gate is passing though. so something is wrong elsewhere...19:47
sbezverkkfox1111: for sure api needs to wait for endpoint, but not for services19:47
kfox1111true.19:47
sbezverkas it is an actual provider of these services19:47
kfox1111that shoudl always fail.19:47
kfox1111right.19:47
sbezverkkfox1111: anyway this change resolved the issue in my cluster19:48
SamYaplekfox1111: ive been using cephfs with good results recently19:48
sbezverkand it makses sense, I do not know what I was thinking when was specifying these dependencies, I guess I was drunk ;)19:49
SamYapleits not great for databases though. but having storage tier options is certainly doable19:49
kfox1111sbezverk: I'd believe it. the only question in my mind is do we leave service:mariadb in the create_keystone_endpoints list.19:49
kfox1111sbezverk: I can see maybe a case for it.19:49
kfox1111SamYaple: yeah. we've been using it for about a year and a half now. awesome stuff. :)19:49
sbezverkkfox1111: I do not think it is needed as create_keystone_endpoints depends on create db and manage db19:50
sbezverkso it implicitely also depends on mariadb19:50
kfox1111SamYaple: ever seen a cephfs backed by 2x replication and ssd's? maybe that would be suitable for db's?19:50
SamYaplekfox1111: cephfs will not be sutiable for highperformance databases. like ever. at least in my opinion19:51
kfox1111sbezverk: could there be a time when the keystone-create-db/managedb heppens, and then there's a long delay till create_keystone_endpoitns?19:51
SamYapleive been using it for about a year. but i just hooked it into kubernetes as a storageclass and it works well19:51
kfox1111and in between mariadb drops out?19:51
SamYapleat least as well as krbd in my opinion19:51
kfox1111probably won't matter too much, as the create endpoitns job will just keep rerunning.19:52
sbezverkkfox1111: possible but very very unlikely19:52
SamYaplekfox1111: my cephfs is bked by nvme, and it is very spikey in perforamcen19:52
kfox1111SamYaple: I was contimplating implementing fernet tokens on top of cephfs.19:52
kfox1111SamYaple: then can have keystone read the fernet dir read only,19:52
kfox1111SamYaple: and do a scheduled job as the roller.19:52
kfox1111SamYaple: oh really? I would have expected nvme to be awesome perfomrance, not so spiky.19:53
*** david-lyle has joined #openstack-kolla19:53
kfox1111very good to know though.19:53
SamYaplecephfs is spikey though19:53
kfox1111ah.19:53
SamYaplecertain jobs run on schedules and can lock things up19:53
*** david-lyle has quit IRC19:53
SamYaplewhen multi-master MDS are a stable thing, it should be better19:53
*** david-lyle has joined #openstack-kolla19:54
SamYaplebut htat likely wont happen until N release19:54
*** unicell has quit IRC19:55
kfox1111SamYaple: ah. that makes sence.19:55
kfox1111lustre fought for many years to get multi mds to work. its really a hard problem.19:56
SamYaplebtw performance increased 50% with bluestore19:56
kfox1111we still don't run it anywhere.19:56
kfox1111sweet.19:56
SamYapleim running bluestore in my test cluster19:56
SamYapleits still experimental in Kraken19:56
kfox1111when is bluestore going to be considered stable?19:56
SamYaplebut should be stable in L19:56
kfox1111when's tthe next lts?19:56
SamYapleL19:56
kfox1111cool.19:56
SamYaplein 4 months19:56
SamYapleso give it 6-7 months :P19:57
SamYaplethey committed to providing an upgrade path from the K release moving forward for bluestore19:57
SamYapleso i would call it Beta right now19:57
SamYapleanyway, its signficiantly faster for all HDD19:58
sbezverkkfox1111: so what do we do with mariadb dependency?19:59
*** mgoddard has quit IRC19:59
kfox1111writing a response.20:00
kfox1111random thought....20:00
kfox1111tangent.20:00
*** david-lyle has quit IRC20:01
kfox1111what happens to a kubernetes-entrypoint dep check on a service, when its a pure pointer svc?20:01
kfox1111IE, the service is pointing to an external mariadb?20:01
kfox1111it can't check the pod state in that case.20:01
*** david-lyle has joined #openstack-kolla20:01
kfox1111does it work, or does it break?20:01
openstackgerritsayantani proposed openstack/kolla-ansible: Fix MySQL DB error in bifrost container  https://review.openstack.org/42439120:01
sbezverkkfox1111: it fails20:02
kfox1111we might want to put in a issue to kubernetes-entrypoint for that case.20:02
sbezverkit really check if there is end point associated20:02
sbezverkkfox1111: I think it is right behavior20:03
kfox1111oh. if it only checks for an endpoint ip, then maybe it would work then.20:03
sbezverkif there is no backend then this service is useless20:03
kfox1111so, it doesn't check for pod being ready, it checks for an enttry in the svc endpoint list?20:03
sbezverkkfox1111: endpoint ip appears only when backend provided container starts and in running state20:03
kfox1111sbezverk: there is a way to startup a svc with an external unmanaged ip as an endpoint I believe a20:04
sbezverkkfox1111: based on my observation it check at minimum that service has one backend associated20:04
kfox1111so it basically just becomes a dns entry.20:04
sbezverkkfox1111L right headless thing, but I am not sure if entrypoint is mart enough for headless20:05
sbezverkkfox1111: what could help is to collect logs even on a sucessful run at the gate20:06
sbezverkthen we could see why dependency were sutisfied20:06
sbezverkfor keystone when it should not20:06
portdirect_travlkfox1111: https://github.com/portdirect/harbor/blob/latest/kubernetes/ingress/freeipa.yaml#L1-L3520:07
kfox1111sbezverk: yeah. I think some folks will want external db's / rabbits. so we should verify that works, or file a bug with entrypoint.20:07
kfox1111sbezverk: I contemplated that. but it ends up producing a lot of data. mabye a switch in the gate to make it easy to submit a patch that just sets the flag to true for testing?20:08
*** aric49 has joined #openstack-kolla20:08
kfox1111portdirect_travl: not sure what your showing me?20:09
portdirect_travlhow to set up a external service in k8s, thought it may be relivant20:09
openstackgerritMerged openstack/kolla-kubernetes: Adding cleanup service for cinder  https://review.openstack.org/42587520:09
openstackgerritSteven Dake proposed openstack/kolla-kubernetes: Fix documentation error in development environment  https://review.openstack.org/42638020:10
openstackgerritSteven Dake proposed openstack/kolla-kubernetes: Change Kubernetes version in docs  https://review.openstack.org/42638120:10
*** lrensing has quit IRC20:10
sbezverkkfox1111: yeah switch would work as this is not required always20:10
kfox1111portdirect_travl: not an external service, but a service that is external? :)20:10
portdirect_travlk8s entrypoint checks that a service has at least one endpoint attached, so in therory should be fine with headless  https://github.com/stackanetes/kubernetes-entrypoint/blob/master/dependencies/service/service.go#L2820:11
kfox1111portdirect_travl: oh. yeah, actually, I think your right. that is what I was asking for. miss read it.20:11
portdirect_travlnp20:11
kfox1111thanks. :)20:12
*** MasterOfBugs has joined #openstack-kolla20:12
sbezverkortdirect_travl: how do you see from that code that it is ok with headless, for my education ;)??20:13
kfox1111yeah. the documentation made it sound like it actually looked for pods.20:13
kfox1111but logically it would be much more work to do that, then just look for endpoins on the service.20:13
*** jtriley has quit IRC20:14
kfox1111and most users wouldn't know the difference.20:14
sdakebmace_ those patches shoudl fix the issue - can you test20:14
sdakebmace_ you can run tox -e doc to generate the docs locally for cut and past eaction20:14
*** pramodrj07 has joined #openstack-kolla20:15
sbezverkkfox1111: so back to mariadb dependency ;) ??20:15
portdirect_travlsbezverk:  from the way  im reading it - its just checking to see if an endpoint is attached to a service , the type of service is irrelivant in that case20:15
sbezverkportdirect_travl: I have never seen output of kubectl describe svc for headless case20:16
kfox1111sbezverk: I reviewed.20:16
sbezverkso I do not know what it would return..20:16
kfox1111portdirect_travl: cool. thanks for verifying.20:16
kfox1111sbezverk: its not quite headless. headless I think means no iptables rules for lb.20:17
*** srwilkers has quit IRC20:17
kfox1111sbezverk: this is kind of an, external endpoint case.20:17
inc0SamYaple, around?20:17
kfox1111which is interesting.20:17
kfox1111so you could still potentially use the lb with more then one external endpoint.20:17
kfox1111which is pretty cool. :)20:17
sbezverkkfox1111: I see, I will need to read more about them20:18
portdirect_travlkfox1111: yeah i've driven services  endpoints with some really ugly python before to drive an ingress controller20:18
*** MasterOfBugs has quit IRC20:18
kfox1111sbezverk: yeah. I haven't played with them too much either. but seeing what this can do, I think I'll be switching some tthings from neturon lbaas v1 to k8s asap. :)20:19
portdirect_travldo it :) you'll be super happy kfox111120:19
kfox1111portdirect_travl: ah. interesting.20:19
bmace_sdake: so you guys think it is an issue with the kubernetes version being wrong?20:19
sdakebmace_ noope, the variable is spelled wrong20:19
kfox1111portdirect_travl: I'm just a little leary of connection lenght.20:19
sdakebmace_ in the docs20:20
bmace_sdake: sure, the variable in the docs?  what if i didn't cut and paste from the docs?20:20
kfox1111portdirect_travl: I have some tcp streams that last days/weeks. neutron lbaasv1 didnt' work with them until I patched them.20:20
sdakebmace_ then tell us that and let us know :)20:20
sdakebmace_ if your variable is spelled correctly it may be adifferent problem20:20
sbezverkkfox1111 portdirect_travl would be very interested to see any prototyping with ingress for kolla kube20:20
sdakebmace_ clearly the variable being spelled wrong is a problem :)20:20
sdakeif you c&p fro mthe docs20:21
portdirect_travlkfox1111: ah - yeah I've only really used them in anger for websites20:21
kfox1111sbezverk: +120:21
sdakewhich is how the docs are structured20:21
portdirect_travlsbezverk: all my old stuff uses ingress exclusively20:21
bmace_sdake: what do you expect that variable being wrong in the docs to cause as an actual problem? some version of something being wrong?20:21
kfox1111portdirect_travl: yeah. neutron lbaasv1 (and v2 really) assumes http connections.20:21
sdakebmace_ portdirect_travl pointed it out20:21
sbezverkportdirect_travl: could you please review this one so we could cloe this topic: https://review.openstack.org/#/c/425964/220:21
kfox1111which are short lived tcp connections. so they really struggle with longer running data transfers. :/20:21
sdakebmace_ i exepct the whole thing would crater20:21
*** portdirect_travl is now known as portdirect20:21
sdakebmace_ I don't know the code in detail enough to say - portdirect_travl does and srdoes as well20:21
kfox1111I asked neutron 2+ years ago for an lbaas option to configure stream times.20:22
sdakewell srwilkers that is :)20:22
kfox1111still isn't a thing. :/20:22
sdakekfox1111 your irc client is broke nagain20:22
portdirectsdake: just looksed at that ps 1.5.2 will break k8s20:22
kfox1111sdake: your renaming too often again. ;)20:22
*** goldyfruit has quit IRC20:22
portdirectsdake: as there is no controller manager image published by att20:22
portdirectif we go there we should update to use kolla controller manager20:23
sdakeportdirect i got impression from v1k0d3n but can't confirm that the at&t effort on openstack helm is moving off halcyon and on to minikube20:23
Serlexw00t20:25
portdirectthats correct at the moment for local dev - though will be using it for storage work20:25
bmace_portdirect: hey, so, the doc bug.  with that error what do you expect the actual effect would be?  an improper kubernetes version right?  what is the optimal version to be using?20:25
sdakeportdirect if the 15.2 change is busted - -2 it so I can figure out how to solve it :)20:26
sdakerather -1 i mean20:26
sdakeportdirect i think we have the controller image in kolla already right?20:26
portdirectsdake: you gave me permission for my 1st -2, you brought this on yoursel :)20:26
*** jmccarthy has joined #openstack-kolla20:26
sdakeportdirect it wa a typo20:26
sdakedon't make me switch to slack ;-)20:26
kfox1111very interesting... lustre just got uid/gid mapping...20:27
portdirectsdake: lol - i chickened out anyway :)20:28
portdirectbmace_: the controller manager would be down, which may cause the errors you were seeing, but im not sure tbh20:29
portdirectsdake: yeah the correct image is in kolla - though we'd need to work out how to get it in20:30
bmace_portdirect: the k8s manager?  would all 4 nodes still show as ready?20:30
sdakeportdirect get it in where20:30
portdirectbmace_:  i dont know :( I think they might - but hinestly not sure20:32
portdirectsdake: inject it into halcyon20:32
bmace_portdirect: would this cause a failure to deploy anything in the k8s cluster?  i can try to deploy something else into it that is simpler than the full kolla-k8s20:33
portdirectbmace_: best way to test a cluseter is this : (paste incoming)20:33
sdakebmace_ the k8s manager in my env now is 1.5.1-beta20:34
bmace_my server is at 1.5.120:34
sdakebmace_ the k8s manager as specified in the firt rev of those docs would be 1.5.120:34
portdirecthttps://www.irccloud.com/pastebin/kBffn4o1/20:34
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: PS fixes issue discovered with keystone service package  https://review.openstack.org/42596420:34
*** jtriley has joined #openstack-kolla20:34
sdakebmace_ the k8s manaager for 1.5.2 doesnt work at all20:34
sdakeso for the moment we need to stick to 1.5.120:34
bmace_well, that isn't my problem then.  1.5.1 achieved.20:35
sdakeportdirect what does this k8s manager do btw20:35
portdirectsdake: you should have a 1.5.1 image? can you get git commits for vagrant and submodule20:35
kfox1111why doesn't 1.5.2 work?20:35
sdakebmace_ did you not cut and paste from the document?20:35
sbezverkkfox1111: it is missing rbd binaries20:35
sbezverkso the dynamic pvc do not work20:35
portdirectkfox1111/sbezverk  just dont have one upstream in att quay repo20:35
kbaegisinc0: Hey, did you guys manage to figure out the MariaDB issue?20:36
bmace_sdake: nope.. i looked at the code and typed it in by hand, because i knew we were supposed to be at 1.5.120:36
inc0kbaegis, negative, but I narrowed it down to images20:36
kfox1111sbezverk: we dont use them?20:36
inc0which makes me more worried20:36
sbezverkkfox1111: nope atm20:36
kbaegisinc0: Well, at least it was caught :)20:36
sbezverkwe use explicit pv/pvc20:36
kfox1111oh. so, its about the dynamic pvc ceph support?20:36
sbezverkkfox1111: right20:37
kfox1111we don't have any code in kolla-kubernetes for that yet. :/20:37
inc0issue is, I have no idea what causes it yet20:37
kfox1111so 1.5.2 should work?20:37
sdakebmace_ ok - i have to pick up my daughter from school - then have torture session the ndinner time20:37
inc0I just deployed stable and it works20:37
sdakebmace_ not sure when i will be back on - probably around 720:37
sbezverkkfox1111: it is working :) do not forget the gate20:37
bmace_so i don't think the kubernetes version is the issue.. at least it isn't my issue, if it is expected the 1.5.1 vs. 1.5.2 version was the issue20:37
sdakebmace_ there are two patche there, one is wrong20:37
sdakelet me workflow -1 it :)20:38
kfox1111sbezverk: cool. I +2'd it. figured the person wf'ing should verify the gate.20:38
portdirectboth 1.5.1 and 1.5.2 should be fine kfox1111, its just the lack of 1.5.2 images in att's quay repo that causes issues20:38
kfox1111but I believe it is good as the previous gate ran, and nothing substantial changed.20:38
sbezverkkfox1111: it is just in in portdirect's script I think he uses them..20:38
*** crushil has quit IRC20:38
kfox1111portdirect: so does it force k8s to alwayus use att's repos then?20:38
kfox1111doesn't find 1.5.2 and fail?20:38
*** crushil has joined #openstack-kolla20:39
portdirectkfox1111: we are talking about halycon - not kolla-k8s20:39
*** jmccarthy has quit IRC20:39
sbezverkportdirect: what I fail to undersatnd is if sdake env uses iscsi workflow, how dynamic ceph pvc come to the picture.20:40
kbaegisinc0: Least useful approach, but still valid: b-search commits back from last known working version20:40
portdirectsbezverk: its just this: https://github.com/att-comdev/halcyon-kubernetes/blob/master/kube-deploy/roles/kube-prep/tasks/patch-kube.yml#L1820:40
sbezverkthere should not be any ceph and as a result there should not be ANY need for att repo20:40
kfox1111portdirect: yeah. just trying to figure out in what ways does 1.5.2 not work in that env, and why.20:40
kbaegisinc0: Is there testing for something like that? Do you guys deploy?20:41
kfox1111portdirect: ah. that explains it. thanks. :)20:41
inc0kbaegis, we do have gates, but this seems to be clustering issue20:41
inc0which might not be caught by gates20:41
inc0and yeah, we do deploy and test;) myself included20:41
sbezverkportdirect: my question still stands, why you need att image with iscsi?20:42
kbaegisinc0: Hard to catch then?20:42
sbezverkwhy not just to use normal 1.5.2 kube controller?20:42
kbaegis:020:42
portdirectsbezverk: good point 2 sec20:43
*** tonanhngo has quit IRC20:43
*** tonanhngo has joined #openstack-kolla20:43
inc0no idea really, for me it's pretty consistent fail20:43
kfox1111sbezverk: because the code's hardcoded to look there.20:43
inc0but for others not really20:43
*** jemcevoy has joined #openstack-kolla20:43
kfox1111theres' not an override to pull from non attcomdev repo.20:44
sbezverkkfox1111: man if hardcoding causes issue, it is just needs to be UN hardcoded20:44
jemcevoyinc0, are you there?20:44
portdirectthere is an override: sed -i "s/^patch_kube_ceph: true/patch_kube_ceph: false/" halcyon-kubernetes/kube-deploy/group_vars/all.yml20:44
sbezverkthere are so much activity because of that?!?!?20:44
inc0jemcevoy, here20:44
kfox1111portdirect: ah. ok.20:44
sbezverkportdirect: can you do a condition if backend iscsi do not use that image?20:45
sbezverkthe problem solved..20:45
portdirectthough the main problem is that sdake must be working from a vold repo to have a 1.5. beta image being loaded20:45
kfox1111so there are 2 workarounds.20:45
kfox11111, pin to 1.5.1 if you want dynamic pvc.20:45
kfox11112, switch off patch_kube_ceph.20:45
sbezverkkfox1111: dynamic pvc are not supported with iscsi20:46
jemcevoyThere are a couple of meetups on docker and OpenStack... https://www.meetup.com/Docker-Portland-OR/    https://www.meetup.com/openstack-pdx/20:46
sdakesbezverk define not supported20:46
kfox1111sbezverk: I get thought that some folks may want to start developing dynamic pvc support in the dev env.20:46
inc0cool, thanks!20:46
sbezverksdake: n.o.t s.u.p.p.o.r.t.e.d :)20:46
kfox1111so both options are valid.20:46
sdakesbezverk suppported by who20:46
sbezverkkuberentes20:47
sdakekubernetes, halycon, where is it not supported?20:47
sdakewhta about the other storage drivers like nfs and gce/etc?20:47
kfox1111it only affects ceph rbd dynamic pvc's.20:47
kfox1111requires ceph in the controller manager container.20:47
kfox1111we're pretty far off track.20:48
jemcevoyinc0, For the docker meetup at puppet the MAX (light rail) stops right at the front door.20:48
sbezverkkfox1111: I chatted yesterday with one of kube storage developer and he told me for dynamic pvc on iscsi, I would need to use another custom controller20:49
sbezverkso natively like ceph dynamic pvc, kube does not support iscsi dynamic pvc20:49
portdirectsbezverk: if that came from rootfs, then its pretty much gospel20:49
sbezverkfrom him20:49
kfox1111sbezverk: yeah. the problem is all iscsi devices have their own api's.20:49
kfox1111sbezverk: thats what cinder was created for, in the first place.20:50
kfox1111to manage the different api's and make them available as one unified api.20:50
*** goldyfruit has joined #openstack-kolla20:50
inc0I think next openstack meetup is in same day as kubernetes roadshow thingy20:50
sbezverkkfox1111: I am sorry but using cinder to host backend for kubernetes cluster to run opensatck with another cinder, no thank you :-)20:50
kfox1111sbezverk: yeah. not recommending that. just saying, its a huge amount of work to implement. cinder is basically the end of that particular rabbit trail. :/20:51
portdirectand the opening of another rabbit hole20:52
portdirect:)20:52
sbezverkkfox1111: I think we should not jump on dynamic pvc until they get wider support..20:52
kfox1111if dynamic iscsi is to be a thing, it will have to reimplemnt basically cinder from scratch.20:52
kfox1111I think dynaic pvc for ceph woudl be awesome.20:52
sbezverkkfox1111: not really20:52
kfox1111I'm getting more and more worried about ceph rbd kernel support though.20:52
kfox1111portdirect: you have some connections...20:53
kfox1111portdirect: when I've been building up the gate, I've run into one issue with ceph kernel rbd,20:53
kfox1111portdirect: and in production another.20:53
sbezverkrequesting iscsi storage to created volume and then to add it as a target should not be more complex than with ceph20:53
portdirectright - i was talking about this today20:53
kfox1111portdirect: generally kernel rbd seems... less then production ready at times. what have you seen?20:53
*** fguillot has quit IRC20:53
kfox1111sbezverk: yeah it is, because each vendor has a differnt api. ceph has one.20:54
portdirectwill bring it up with some peeps tomorrow but the sound of it was - that if moving to plain rbd was gonna make people happy then wfthem20:54
kfox1111portdirect: yeah. its worked pretty well here, but hit some bumps that make me worried to run it in production.20:55
kfox1111the reboot gate locks up after boot sometimes. wont ever recover.20:55
kfox1111and saw a process on a prod system dstate due to rbd mount not working. writes to one particular file lock up. never recovered without rebooting the node.20:56
portdirectI think we may be the heaviest users of it in k8s20:56
kfox1111yeah.20:56
kfox1111SamYaple seemed to think it was unstable too.20:56
portdirectSamYaple thinks too much20:56
portdirect:)20:57
kfox1111I think the saem could be said of us all. ;)20:57
kfox1111and probably has been. :)20:57
* portdirect waits for sam to take the bait20:57
portdirect:)20:57
* kfox1111 chuckles.20:57
kfox1111yeah, see if you have seen anyone else with instability problems with it. I'm very curious.20:58
kfox1111be back in a bit.20:58
*** haplo37_ has quit IRC21:05
*** vhosakot has quit IRC21:08
*** jmccarthy has joined #openstack-kolla21:08
*** satyar has quit IRC21:08
*** vhosakot has joined #openstack-kolla21:08
openstackgerritMerged openstack/kolla-kubernetes: PS fixes issue discovered with keystone service package  https://review.openstack.org/42596421:12
*** Serlex has quit IRC21:15
*** haplo37_ has joined #openstack-kolla21:16
*** vhosakot has quit IRC21:18
kfox1111back.21:23
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: PS Adds keystone cleanup service  https://review.openstack.org/42640021:28
*** zioproto has joined #openstack-kolla21:30
*** zioproto has quit IRC21:31
*** absubram has quit IRC21:33
*** l4yerffeJ has joined #openstack-kolla21:34
kfox1111sbezverk: https://github.com/kubernetes/helm/issues/188321:34
*** l4yerffeJ_ has quit IRC21:35
*** Jeffrey4l_ has quit IRC21:35
sbezverkkfox1111: I was reading just that :)21:37
kfox1111I think if we did it that way, we could move all the values out of all_values.yaml that are specific to packages to their own native values.yaml21:40
kfox1111and all the common stuff could be broken up per shared chunk into parent_vars,21:40
kfox1111and then included in the packages as needed in the dep to kolla-common.21:40
*** vhosakot has joined #openstack-kolla21:40
*** Jeffrey4l_ has joined #openstack-kolla21:41
kfox1111would still be easy to edit all the common config values in one place, kolla-common/parent_values/* :)21:41
kfox1111and wouldn't be one big yaml file, so easier to edit.21:41
sbezverkkfox1111: sounds reasonable21:42
kfox1111between that, and local repo's, we could probably get rid of pretty much all the custom stuff,21:43
kfox1111but a build_all helper script. (just for ease of building it all)21:44
sbezverkkfox1111: kolla-common/parent_values would have a single file with common values right?21:45
kfox1111the initial proposal would be that. kolla-common/parent_values.yaml.21:45
kfox1111the latest idea I just posted would be,21:45
kfox1111kolla-common/parent_values/<name>.yaml21:45
*** unicell has joined #openstack-kolla21:46
kfox1111where the parent could select <names>'s out of the child chart to merge.21:46
kfox1111so could do common, or mariadb, or python-haproxy, etc.21:46
*** unicell has quit IRC21:46
kfox1111and/or.21:46
kfox1111so we could replicate the functiionalyt of prebuild now, with helm native.21:47
bmace_sdake: fyi, got busybox deploying on the halycon-kubernetes environment just fine21:47
kfox1111does the busybox networkign work?21:47
bmace_sdake: hitting some volume / mount issues now in my helm / mariadb / rabbitmq containers now.21:48
bmace_kfox1111: nslookup kubernetes seems happy enough21:48
kfox1111what about nslookup google.com21:48
kfox1111(had a problem where kubernetes dns worked but not google for a while.)21:48
bmace_hrm, perhaps not to much21:49
bmace_resolve failed21:49
mgilesthat's not going to work behind a proxy...21:49
kfox1111yeah. kubernetes dns is resolved intoernally to k8s and the vm.21:49
kfox1111google is resolved outside.21:49
*** unicell has joined #openstack-kolla21:50
bmace_well, it says the dns server it is using is the kubernetes dns server.  does the k8s dns service need to be configured differently due to the proxy that isn't handled already via the proxy config stuff in config.rb for halycon-vagrant-kubernetes?21:51
mgilesIn my setup I can nslookup other hosts that are inside the corp firewall, but it makes sense I can't nslookup google.com.  Our internal dns servers will not resolve that.21:52
bmace_no curl in base busybox? how dare they!21:53
bmace_yeah, at least i can tell networking in the busybox is generally working.. i can ping our proxy server21:54
kfox1111mgiles: ah. ok. that makes sense.21:54
*** adrian_otto has quit IRC21:54
kfox1111hehe. busybox is tiny. :)21:54
*** JoseMello has quit IRC21:55
mgilesWhat I get annoyed at is the images that don't have nslookup (or dig, or host, etc)21:55
bmace_but, curl is tiny too! ;)21:55
kfox1111yeah. but tiny + tiny = 2xtiny. :)21:55
*** absubram has joined #openstack-kolla21:55
bmace_true21:56
kfox1111but, nslookup, and ifconfig, and tcpdump, and... :)21:56
kfox1111down hill from there. :)21:56
kfox1111thats where something like alpine comes in.21:56
bmace_but.. I need X!! ;)21:56
inc0ubuntu trunk is broken :(21:56
kfox1111bmace_: then build a container with x in it. ;)21:57
inc0ahh the sadness, ahh the pain21:57
jascott1mgiles can you pull the trick where you mount the binary from host into container? i havent tried in k8s but useful quick hack w docker21:57
kfox1111jascott1: aahh..21:57
kfox1111jascott1: there be draggons. :)21:57
mgileshaven't tried that21:57
kfox1111but can work, sometimes, perhaps.21:57
kfox1111ldd it on the host and make sure all the libs are in the container.21:57
kfox1111if so, you have a chance.21:57
kfox1111oh. and the container and the host have the same os.21:58
inc0I usually do docker exec -it -u root21:58
inc0bash21:58
jascott1for me its always vim and I just mount tiny-vim and it works but the others dont seem to21:58
inc0and then apt-get stuff as I need them21:58
mgilesAgain, it's harder behind a corp firewall since then you have to configure apt to work through the firewall.  Not that hard, but makes a simple task more difficult21:59
kfox1111yeah.22:00
mgilesanyway, the point is that bmace_ shouldn't complain too much.  At least busybox has nslookup :)22:00
mgilesnext he'll be saying he can't handle vi and needs emacs.  Let the holy wars start22:01
*** breitz has quit IRC22:01
*** absubram has quit IRC22:01
*** zioproto has joined #openstack-kolla22:02
*** breitz has joined #openstack-kolla22:02
kfox1111hmm...22:03
bmace_well, lets not push it.. plus, i'm a vi guy.. so i'm all good.. it is more like dropping vi and expecting folks to use ed22:03
*** rmart04 has joined #openstack-kolla22:03
*** rmart04 has left #openstack-kolla22:04
kfox1111sbezverk: got a script going to generate an exapmle cloud values.yaml. :)22:05
kfox1111it produces: http://paste.openstack.org/show/zTlWpAkxph9x9ELmLNxK/22:06
*** zioproto has quit IRC22:06
kfox1111oops. one extra value in it needs removing...22:06
kfox1111element_name.22:06
*** zioproto has joined #openstack-kolla22:06
*** vhosakot_ has joined #openstack-kolla22:08
*** vhosakot has quit IRC22:12
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Add a script to build an example cloud yaml  https://review.openstack.org/42641722:14
sbezverkkfox1111: yeah, I like this file not huge and with easy structure22:15
kfox1111:)22:15
*** crushil has quit IRC22:16
sbezverknow the question is how to use it? do you think a user will make a copy, changes variable and then use it in command line for each microservice/service?22:16
kfox1111yeah. or for the service packages.22:17
kfox1111yeah.22:17
*** vhosakot_ has quit IRC22:17
sbezverkyeah really nice, now config cane be stored/moved reused much much easier22:18
kfox1111yeah. it worked that way for a while, but wasn't really obvious thats how it was inteneded. this makes it much clearer I hope.22:20
sbezverk+122:20
kfox1111still gotta get the gate switched over to doing it this way too. got ground work in place, but the final swithc takes touching like 80% of the file.22:20
openstackgerritsayantani proposed openstack/kolla: [TEST] DO NOT MERGE  https://review.openstack.org/40836822:23
*** lrensing has joined #openstack-kolla22:27
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Check to see if Horizon is working in the gate.  https://review.openstack.org/42602522:30
kfox1111sbezverk: this one is ready again: https://review.openstack.org/#/c/333996/22:30
*** PramodJ has joined #openstack-kolla22:31
*** mgiles has quit IRC22:32
*** pramodrj07 has quit IRC22:34
*** simon-AS559 has joined #openstack-kolla22:36
*** jmccarthy has left #openstack-kolla22:36
*** zioproto has quit IRC22:45
*** kbaegis has quit IRC22:48
*** kbaegis has joined #openstack-kolla22:49
*** goldyfruit has quit IRC22:49
*** kbaegis has quit IRC22:49
kfox1111so, is the horizon rolling upgrade too scary to review?22:56
*** saneax-_-|AFK is now known as saneax22:59
*** aric49 has quit IRC22:59
sbezverkkfox1111: just replied23:00
kfox1111sbezverk: thanks. :)23:00
sbezverkwhen I looked at .dot file I wanted to shutdown my workstation23:00
sbezverkand run away ;)23:01
kfox1111heh. grephviz is an interesting beast.23:01
kfox1111looks like I messed up the formatting a bit though... I should fix that.23:01
sbezverkkfox1111: what is this selenium thing?23:02
kfox1111sbezverk: selenium is a browser automation framework.23:03
sbezverksounds like a chemical weapon to me23:03
kfox1111hehe23:03
kfox1111lets you create a pool of browsers, then remote control them with a standard api to do things.23:03
kfox1111such as login to horizon and see if it works. :)23:03
SamYapleportdirect: i dont think too much. i dont think at all! you take that back!23:03
sbezverkkfox1111: Ah so you try to answer sdake request23:03
kfox1111sbezverk: yeah. :)23:04
kfox1111should be able to actually test if horizon is working instead of just that the initial reposnse comes back.23:04
sbezverkkfox1111: never heard that before, running bunch of browsers from the container %)23:04
kfox1111seleinium + k8s = awesome.23:05
kfox1111can scale out a browser cluster really easily. :)23:05
kfox1111then use it to do all sorts of things... :)23:05
sbezverkkfox1111: it is mostly used for testing, right I cannot see other application of this?23:06
sdakewhat request did i do23:06
sdakesbezverk ^23:07
sdakekfox1111 reviews that are longer in nature sit longer23:07
sdakekfox1111 its a time commitment to do a review23:07
sdakekfox1111 the best analogy I have herd on the matter is this23:07
sdakecore reviewers wait for a review to fatten up a little bit23:07
sdakeand then once they think its ready swim in like sharks and pick at it:)23:08
inc0guys I really need help with this one23:08
sdakeinc0 not sure sbezverk or kfox1111 can help although other s in teh cnannel cha help23:08
inc0let me publish a bug with steps to reproduce23:08
sdakeJeffrey4l_ is gone for the weekend i assume23:08
sbezverksdake you are forcing kfox1111 to run browser in the container!! it is just cruel23:08
sdakeinc0 emea is mostly asleep :)23:08
sdakesbezverk i dont think i forced that?23:08
sdakesbezverk anyone can doanything they like :)23:09
sbezverksdake: man you have short memory!! who asked to properly test horizon?23:09
*** sdake_ has joined #openstack-kolla23:12
*** simon-AS559 has quit IRC23:14
*** sdake has quit IRC23:14
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Check to see if Horizon is working in the gate.  https://review.openstack.org/42602523:15
*** lrensing has quit IRC23:16
kfox1111sdake_: yeah. was trying to triger the actual reviews. as it had been a while.23:17
sdake_kfox1111 i have an easy review u pther ethat sits too - renaming everything from 0.4.0 to 0.5023:18
sdake_its literally a one line sed operation applied tothe repository23:18
sdake_kfox1111 i can attempt looking today - althoug hthis mariadb thing on ubuntu is a problem and i need to help inc0 there23:18
kfox1111sdake_: I actually reviewed it though.23:18
sdake_kfox1111 oh cool didn't know that 0.40->0.5.0 had been reviewed :)23:19
sdake_kfox1111 so much stuff going on in my life - hard to keep track :)23:19
kfox1111sdake_: the review I asked for eyes on hadn't gotten a comment yet.23:19
kfox1111sdake_: the short answer is, your ps changes a bunch of stuff that makes one of my ps's need rebasing, yet again. the ps that I just asked for reviews on.23:20
kfox1111while your ps can be easily regenerated at any time.23:20
kfox1111so it would be nice if it waited till after the other ps is merged, or its reabased on that ps.23:20
inc0https://bugs.launchpad.net/kolla/+bug/165998123:20
openstackLaunchpad bug 1659981 in kolla "galera deployments fails on ubuntu" [Critical,Confirmed] - Assigned to Michał Jastrzębski (inc007)23:20
kfox1111+1 to helping inc023:21
kfox1111galera's important.23:21
*** sayantan_ has quit IRC23:21
inc0yeah I'm trying to debug it for 2 days now23:21
inc0without success23:21
kfox1111git bisect time?23:22
inc0I already tried reverting patches23:22
kfox1111see if you can find the ps for when it stopped working?23:22
kfox1111all the way back to when it was branched off of 3?23:22
inc0most likely candidates -  I already tried23:22
inc0no, I haven't got that far23:23
kfox1111"Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth.23:23
kfox1111:)23:23
inc0well, I'll write script for that23:23
sbezverkkfox1111: yeah live long and prosper ;)23:24
kfox1111so, I see two options... 1, a patch to kolla-ansible/kolla broke things.23:24
kfox1111sbezverk: :)23:24
inc0build, deploy, git revert23:24
inc0until success23:24
inc0kolla images23:24
inc0I narrowed it down to images23:24
kfox1111too bad irc doesn't support unicode23:24
kfox1111http://emojipedia.org/raised-hand-with-part-between-middle-and-ring-fingers/23:24
kfox11112. some binary package broke things23:25
inc0negative, fresh build of stable/newton fails23:25
inc0and binary packages are the same there23:25
kfox1111newton or ocata?23:25
inc0stable/newton works*23:25
inc0one idea, I'll do binary search ;)23:26
inc0gonna build ocata-223:26
kfox1111inc0: thats what git bisect is. ;)23:26
inc0ah23:26
inc0fun awaits23:26
kfox1111https://git-scm.com/docs/git-bisect23:26
kfox1111:)23:26
inc0you learn something new every day23:27
kfox1111gits really an awesome tool. :)23:27
*** jtriley has quit IRC23:29
kfox1111git bisect run is particularly fun. :)23:30
kfox1111you can automate the whole process.23:30
sbezverkkfox1111: when it asks you about commit everytime how can you be sure whether this specific commit is good or bad?23:31
sbezverklike in their exmaple23:32
kfox1111problem being debugged dependent.23:33
kfox1111so, in one example, say the problem is the code doesn't build.23:33
sbezverkif you need to run test for each commit where is the value?23:33
openstackgerritJoseph Robinson proposed openstack/kolla-ansible: Build deploy guide files and tox environment  https://review.openstack.org/42610523:33
sbezverksince even without it you could do the same test23:33
kfox1111you could run 'make' and if it works, its good, if it doesn,t' its bad.23:33
kfox1111or you could run 'make; make test' if you have a unit testing framework.23:33
kfox1111with git bisect run, you can give it a script to run on each commit tested for you, so you don't have to manually test.23:34
sbezverkah ok its value that it allows you to go step by step changing your workspace23:34
kfox1111yeah. it lets you not have to manually implement a binary search.23:35
sbezverkso instead of manually rolling back each commit from the top23:35
sbezverkit does it for you23:35
kfox1111it does it in a binary search.23:35
kfox1111so say you have 100 commits that are suspect,23:35
kfox1111it might start at 50.23:35
kfox1111if that fails, it will go to 25.23:35
*** Penfold has quit IRC23:36
kfox1111if that suceeds, 37,23:36
kfox1111etc.23:36
sbezverkok instead of doing 100 iterations it will optimize it23:36
kfox1111yeah. logrightmic amount of tests.23:36
sbezverkok got it..23:36
kfox1111:)23:36
kfox1111so for this case, you know 3.x works, and master doesn.t so you give it those two.23:37
sbezverkcool hopefully inc0 will use it, would be curious to know if it helps to nail it23:38
sdake_inc0 git bisect rocks - i use it all the time23:39
sdake_inc0 you do git bisect good23:39
sdake_and git bisect bad23:39
sdake_and it finds the commit that broke things23:40
sdake_although in this case, it maybe breakage from an upstream repo that has changed rather than something in master23:40
sdake_inc0 i'll be around tonight to pitch in23:40
sdake_inc0 usually it tkes 7-8 bisect operations to find the commit that broke something within a full 6 month release23:41
sdake_sometimes 923:41
sdake_that is better then manually doing it with guessing :)23:41
kfox1111sdake_: yeah. so might be good to try it with essentially 3.x kolla-ansible and 4.x kolla containers.23:42
kfox1111if that works, then its probably kolla-ansible somewhere in between.23:42
sdake_i think inc0 said it was in teh images23:42
sdake_ok - gotta eat23:42
sdake_bbl - then i'll be around to help you inc023:42
kfox1111ah.23:43
*** pramodrj07 has joined #openstack-kolla23:44
*** sayantani01 has joined #openstack-kolla23:46
kfox1111hehe. selenium is so much fun...23:47
kfox1111    driver.get_screenshot_as_file('/tmp/google.png')23:47
*** PramodJ has quit IRC23:48
*** sdake_ has quit IRC23:48
*** lamt has quit IRC23:49
*** lamt has joined #openstack-kolla23:49
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Check to see if Horizon is working in the gate.  https://review.openstack.org/42602523:50
*** lamt has quit IRC23:54
inc0I gtg now23:56
inc0I'll be back on it tomorrow23:56
inc0leave comment under bug plz if you manage to find anything23:56
*** inc0 has quit IRC23:56
*** lrensing has joined #openstack-kolla23:58

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