Monday, 2017-07-10

*** lrensing has joined #openstack-kolla00:01
*** manheim has quit IRC00:11
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible master: Clear all l3 related namespace before starting neutron-l3-agent  https://review.openstack.org/48196900:23
*** zhubingbing_ has joined #openstack-kolla00:34
openstackgerritJeffrey Zhang proposed openstack/kolla stable/ocata: Bump OpenStack service version  https://review.openstack.org/48197000:35
*** duonghq has joined #openstack-kolla00:46
duonghqmorning guys00:46
*** zhurong has joined #openstack-kolla00:47
*** tovin07_ has joined #openstack-kolla00:52
*** caoyuan has joined #openstack-kolla00:53
*** kbaegis has joined #openstack-kolla01:02
*** dixiaoli has joined #openstack-kolla01:04
*** lyang__ has joined #openstack-kolla01:06
duonghqsup kbaegis01:21
*** lrensing has quit IRC01:25
*** dave-mccowan has joined #openstack-kolla01:33
openstackgerritfupingxie proposed openstack/kolla master: Replace http with https  https://review.openstack.org/48197501:40
*** manheim has joined #openstack-kolla01:46
*** goldyfruit has joined #openstack-kolla01:47
*** manheim has quit IRC01:50
*** ducttape_ has joined #openstack-kolla01:54
*** ducttape_ has quit IRC01:59
*** schwicht has quit IRC02:00
*** kevzha01 has joined #openstack-kolla02:10
*** kevzha01 is now known as kevinz02:15
*** caowei has joined #openstack-kolla02:20
openstackgerritfupingxie proposed openstack/kolla master: Replace http with https  https://review.openstack.org/48197502:41
*** zhurong has quit IRC02:43
*** schwicht has joined #openstack-kolla02:46
spsuryamorning03:17
spsuryaduonghq: morning03:18
openstackgerritjimmygc proposed openstack/kolla-ansible master: Add ceph rgw object store support into trove  https://review.openstack.org/47155303:30
*** schwicht has quit IRC03:34
*** ducttape_ has joined #openstack-kolla03:38
*** ducttap__ has joined #openstack-kolla03:40
*** ducttape_ has quit IRC03:40
*** goldyfruit has quit IRC03:40
*** ducttap__ has quit IRC03:44
duonghqmorning spsurya03:57
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible master: Clear all l3 related namespace before starting neutron-l3-agent  https://review.openstack.org/48196903:58
*** dave-mccowan has quit IRC04:05
spsuryaduonghq:   https://review.openstack.org/#/c/48197504:17
spsuryais this https://stackalytics.com/?module=kolla-group&metric=commits working for you04:17
spsuryanot in my domain ;)04:18
duonghqhmm, not in mine too04:22
duonghqbut I'm not sure about reason04:22
duonghqspsurya,04:22
spsuryaduonghq: seems server is not supporting SSL04:27
spsuryaso http is fine04:27
*** jascott1 has quit IRC04:28
*** mdnadeem has joined #openstack-kolla04:28
*** lrensing has joined #openstack-kolla04:38
*** ducttape_ has joined #openstack-kolla04:42
*** jascott1 has joined #openstack-kolla04:43
*** kbaegis has quit IRC04:43
*** ducttape_ has quit IRC04:44
*** ducttape_ has joined #openstack-kolla04:44
*** zhurong has joined #openstack-kolla04:46
*** ducttape_ has quit IRC04:46
*** ducttape_ has joined #openstack-kolla04:49
*** ducttape_ has quit IRC04:53
openstackgerritYotaro Konishi proposed openstack/kolla-ansible master: Fix an invalid variable name  https://review.openstack.org/48199905:05
*** lrensing has quit IRC05:07
*** janki has joined #openstack-kolla05:08
*** skramaja has joined #openstack-kolla05:20
*** unicell has quit IRC05:23
*** unicell has joined #openstack-kolla05:23
*** prateek has joined #openstack-kolla05:36
*** jbadiapa has joined #openstack-kolla05:43
openstackgerritfupingxie proposed openstack/kolla master: Replace http with https  https://review.openstack.org/48197505:45
*** ducttape_ has joined #openstack-kolla05:49
*** ducttape_ has quit IRC05:55
*** manheim has joined #openstack-kolla06:10
*** manheim has quit IRC06:14
*** dixiaoli has quit IRC06:18
*** dixiaoli has joined #openstack-kolla06:18
*** magicboiz has joined #openstack-kolla06:35
*** lpetrut has joined #openstack-kolla06:37
*** janki has quit IRC06:38
*** asalkeld has joined #openstack-kolla06:41
*** lpetrut has quit IRC06:43
*** coolsvap has joined #openstack-kolla06:47
*** harlowja has quit IRC07:11
*** magicboiz has quit IRC07:12
*** shardy has joined #openstack-kolla07:14
*** jascott1 has quit IRC07:14
*** serlex has joined #openstack-kolla07:24
*** jascott1 has joined #openstack-kolla07:24
*** reidrac has joined #openstack-kolla07:32
reidracgood morning07:32
*** egonzalez has joined #openstack-kolla07:38
*** masber has quit IRC07:40
*** YuYangWang has joined #openstack-kolla07:42
*** reidrac has quit IRC07:45
*** dixiaoli has quit IRC07:45
*** dixiaoli has joined #openstack-kolla07:46
*** sambetts is now known as sambetts|afk07:47
*** YuYangWang has quit IRC07:47
*** masber has joined #openstack-kolla07:53
*** sambetts|afk is now known as sambetts07:57
*** ducttape_ has joined #openstack-kolla07:58
*** reidrac has joined #openstack-kolla08:00
*** ducttape_ has quit IRC08:03
*** shardy has quit IRC08:06
*** shardy has joined #openstack-kolla08:07
openstackgerritzhouya proposed openstack/kolla-ansible master: Support assigning HA traffic to dedicated interface  https://review.openstack.org/48150308:10
*** manheim has joined #openstack-kolla08:18
*** jistr|off is now known as jistr08:25
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: [DNM] Test depends kolla changes  https://review.openstack.org/48205308:38
*** hieulq has quit IRC08:39
*** daidv has quit IRC08:39
*** duonghq has quit IRC08:40
*** tovin07_ has quit IRC08:40
*** gfidente has joined #openstack-kolla08:49
*** gfidente has quit IRC08:49
*** gfidente has joined #openstack-kolla08:49
*** tvignaud has quit IRC08:58
*** ducttape_ has joined #openstack-kolla08:59
*** ducttape_ has quit IRC09:04
*** lpetrut has joined #openstack-kolla09:07
*** magicboiz has joined #openstack-kolla09:10
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: [DNM] Test depends kolla changes  https://review.openstack.org/48205309:11
*** tvignaud has joined #openstack-kolla09:11
openstackgerritMerged openstack/kolla stable/ocata: Bump OpenStack service version  https://review.openstack.org/48197009:14
*** leni1 has joined #openstack-kolla09:15
*** hieulq has joined #openstack-kolla09:15
*** daidv has joined #openstack-kolla09:16
*** duonghq has joined #openstack-kolla09:16
*** mgoddard_ has joined #openstack-kolla09:21
*** daidv has quit IRC09:21
*** magicboiz has quit IRC09:23
openstackgerritfupingxie proposed openstack/kolla master: Replace http with https  https://review.openstack.org/48197509:25
*** kbaegis has joined #openstack-kolla09:27
*** magicboiz has joined #openstack-kolla09:27
kbaegisduonghq: Morning!09:28
*** kbaegis1 has joined #openstack-kolla09:30
*** leni1 has quit IRC09:32
*** kbaegis has quit IRC09:32
duonghqhi kbaegis109:33
kbaegis1Ahh, I got the 1 on the end of my name?09:33
kbaegis1That's what I get for disconnecting every 5 minutes :)09:34
duonghq:)09:34
*** daidv has joined #openstack-kolla09:34
*** kbaegis has joined #openstack-kolla09:34
kbaegisBetter?09:35
kbaegisNIce.09:35
duonghqya09:35
kbaegisExcited. On Friday I get to start playing around with my new 10G mesh09:35
duonghqnice09:36
duonghqkbaegis, currently, which distro are you using?09:37
duonghqand how many do you have?09:37
*** leni1 has joined #openstack-kolla09:37
kbaegisduonghq: Technically a 4 node cluster w/ Gentoo09:37
duonghqnice09:38
*** kbaegis1 has quit IRC09:38
kbaegisThe real trouble I've been having has been setting kolla up on ovs internal ports.09:38
kbaegisDoesn't seem to like clustering in that context09:38
leni1Hello. Trying to build a kolla image using this guide: https://docs.openstack.org/kolla/latest/image-building.html. I wanted to know if I am to clone the kolla repo, I should do it thus: git clone https://github.com/openstack/kolla.git09:44
leni1Would that be correct?09:44
leni1Because I ran into a situation similar to this: https://ask.openstack.org/en/question/93967/kolla-build-command-not-found/09:45
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Fix depends-on kolla gates  https://review.openstack.org/48205309:45
*** YuYangWang has joined #openstack-kolla09:45
leni1And that seemed to be the proposed solution to the error: ERROR: toxini file 'tox.ini' not found09:46
egonzalezleni1, have you installed kolla after clone the repo or want to use master without installing?09:46
leni1egonzalez, I want to install kolla09:49
*** rwallner has quit IRC09:49
leni1I would like to build an image as per the instructions in the guide and so on.09:50
leni1I certainly don't think my situation suits just using master without installing, as far as I can tell.09:50
egonzalezleni1, if not want to use master branch, install kolla from pip09:51
egonzalezpip install kolla09:51
egonzalezwithout cloning git repo and that stuff09:51
leni1egonzalez, thank you very much for that clarification. Let me go do that.09:53
leni1egonzalez, ran `pip install kolla`. Still the error of toxini file not found still appears09:56
leni1I guess that means I should clone the repo, right?09:56
egonzalezleni1, nope09:57
egonzalezchange directory out of the repo cloned and install kolla09:57
egonzalezmaybe is trying to install local content09:57
leni1egonzalez, I haven't cloned anything. So far I have been using pip to install what is required.09:58
egonzalezleni1, what steps you followed? what is installed? I just made a "pip install kolla" and succeed10:00
*** asalkeld has quit IRC10:00
*** caoyuan has quit IRC10:02
*** ducttape_ has joined #openstack-kolla10:02
leni1egonzalez, so far I have run `pip install tox`10:02
leni1After that I have run `tox -e genconfig`10:03
leni1And that is giving me the error that tox.ini is not found10:03
*** ducttape_ has quit IRC10:04
*** ducttape_ has joined #openstack-kolla10:05
leni1egonzalez, as far as I can tell, there are no dependencies that I was supposed to install, according to the guide.10:07
egonzalezleni1, if is installed with pip there is not kolla-build file generated nor tox.ini to create it10:07
egonzalezleni1, I think is a bug, let me dig into it10:07
egonzalezleni1, each option can be used in kolla-build command, what are you custom options want to use?10:08
*** caowei has quit IRC10:08
leni1egonzalez, I really don't know. I just wanted to build container images for OpenStack Glance and Cinder.10:09
leni1I was pointed to this guide as a way to do that.10:09
*** ducttape_ has quit IRC10:10
egonzalezleni1, push to any registry, namespace for the images, linux distribution and install type(source/binary)?10:10
leni1egonzalez, Any registry will work I guess. No idea about namespace. Linux distribution would be CentOS. Install type I think would be binary because I want it to be stable. I could be wrong though ;)10:12
egonzalezie, this command would build your images for centos, binary under my registry:/kolla namespace with tag 4.0.110:13
egonzalezleni1, kolla-ansible --base centos --type binary --namespace 192.168.100.1:4000/kolla --tag 4.0.1 --push cinder10:14
egonzalez*kolla-build rather kolla-ansible10:15
*** kevinz has quit IRC10:16
leni1egonzalez, okay. Let me give it a shot and see.10:17
openstackgerritMerged openstack/kolla master: Switch to Cryptography over pycrypto  https://review.openstack.org/47370210:19
kbaegis*sigh* So many of the scripts are hardcoded to assume that modules are available for loading/unloading10:21
kbaegisAnd if they aren't, they just fail. :/10:21
openstackgerritEduardo Gonzalez proposed openstack/kolla master: DNM: test master branch  https://review.openstack.org/45610810:21
kbaegisi.e. iscsid starts just fine on my system, but hangs at "created". I have to manually start it. Also, keepalived looks for ip_vs10:21
kbaegisDocumenting all those as modules10:22
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Fix depends-on kolla gates  https://review.openstack.org/48205310:22
leni1egonzalez, by the way, should I do this for each component of OpenStack that I would like a container for? E.g. Glance and Neutron.10:29
egonzalezleni1, nope, if want to build all, not add cinder at the end10:29
egonzalezcinder,glance will build all images matched by a regex with those names10:30
*** omenvlad has quit IRC10:30
leni1egonzalez, so if I want to build Glance and Neutron, the --push option should look like `--push glance,neutron`?10:36
egonzalezleni1, push is the option to push build images to the registry, image names are the last option10:37
leni1egonzalez, understood.10:45
leni1so just `glance,neutron` will work?10:45
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: WIP: Implement tacker-conductor service  https://review.openstack.org/47751710:48
*** caoyuan has joined #openstack-kolla10:53
*** xinliang has quit IRC10:53
*** kbaegis has quit IRC10:54
*** hieulq has quit IRC10:57
openstackgerritTaeha Kim proposed openstack/kolla master: Fixed the invalid link in the kolla/image/build.py  https://review.openstack.org/48145710:57
*** pbourke has quit IRC10:57
openstackgerritTaeha Kim proposed openstack/kolla master: Fixed the invalid link in the kolla/image/build.py  https://review.openstack.org/48145710:58
*** ansmith has quit IRC10:58
*** daidv has quit IRC10:58
*** pbourke has joined #openstack-kolla10:59
*** duonghq has quit IRC10:59
*** duonghq has joined #openstack-kolla11:00
*** dixiaoli has quit IRC11:00
*** xinliang has joined #openstack-kolla11:05
*** ducttape_ has joined #openstack-kolla11:06
*** ducttape_ has quit IRC11:10
*** daidv has joined #openstack-kolla11:12
*** hieulq has joined #openstack-kolla11:12
*** rwallner has joined #openstack-kolla11:13
*** omenv has joined #openstack-kolla11:15
*** rwallner_ has joined #openstack-kolla11:15
*** rwallne__ has joined #openstack-kolla11:16
*** caoyuan has quit IRC11:16
*** rhallisey has joined #openstack-kolla11:16
*** rwallner has quit IRC11:17
*** rwallner_ has quit IRC11:20
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Fix depends-on kolla gates  https://review.openstack.org/48205311:28
egonzalezmind people review this change? https://review.openstack.org/#/c/482053/ fixes ansible gates with a depends-on kolla changes11:30
*** kbaegis has joined #openstack-kolla11:36
kbaegisHuh. So ip_vs is a module11:38
kbaegisAnd I'm still getting could not insert 'ip_vs': Invalid argument from the keepalived container11:38
kbaegis:/11:38
leni1I ran `kolla-ansible --base centos --type binary --namespace 192.168.100.1:4000/kolla --tag 4.0.1 --push cinder` and got this after the build: https://ghostbin.com/paste/f3dwn. Has it failed and if so, what should I do?11:39
egonzalezkbaegis, this sounds like a registry or auth issue "Get https://192.168.100.1:4000/v2/"11:40
egonzalezleni1, ^^11:40
kbaegisegonzalez: It's a kernel/modprobe issue unfortunately11:41
egonzalezkbaegis, wrong name :) i'm out of the background of your issue, mind explain?11:41
egonzalezleni1, is your local registry bind in 192.168.100.1:400011:42
kbaegisegonzalez: keepalived will fail on load if it can't first do modprobe ip_vs. What if ip_vs is builtin?11:42
egonzalezleni1, that sound that you are using my local registry IP address ;)11:42
leni1egonzalez, I don't know. I haven't had to interact with my local registry.11:42
egonzalezleni1, do you have a local registry running?11:43
leni1How can I check what my local registry is? I think it is still set to the defaults though.11:43
egonzalezguess no have a registry if  you didnt configured it11:44
leni1I have never run a registry, so unless it is running in the background, I don't think so.11:44
leni1Yes.11:44
kbaegisleni1: For what it's worth, I can't think of anything less intuitive (for beginners) than what the docker community has chosen to do with their registries. Once you get it set up it works flawlessly though.11:44
egonzalezleni1, is an allinone or multinode?11:44
egonzalezif is multinode will need one for share images between all nodes11:44
leni1I think it is an all-in-one. I am going to be using the containers on one machine11:45
egonzalezleni1, so no need a registry at all, remove --push from the command, also, the other images how are named? docker images | grep nova11:46
egonzalezkbaegis, modprobe is done in extend_start of keepalived, in which cases ip_vs is builtin?11:48
kbaegisegonzalez: Sure. What if it's built directly into the kernel, and modprobe won't work?11:49
leni1egonzalez, the other images are named thus: 192.168.100.1:4000/kolla/centos-binary-cinder-api11:49
kbaegisegonzalez: There's no handling whatsoever for that case. Just fails11:49
egonzalezleni1, i mean, the other images not built, you only build cinder,glance and neutron right? but need a bunch more of images11:50
openstackgerritEduardo Gonzalez proposed openstack/kolla master: [wip] Implement tacker-conductor image, rework all tacker  https://review.openstack.org/47749411:51
*** caoyuan has joined #openstack-kolla11:52
leni1egonzalez, yes.11:52
leni1Only cinder has built. I am going to do glance and neutron next11:52
leni1I hope the `192.168.100.1:4000/` part in the image name won't cause me problems, right?11:53
egonzalezleni1, all images need to be under the same namespace <in your case 192.168.109.1:4000/lokolla>11:54
egonzalezbut if some images are from dockerhub are only kolla/<image>11:54
leni1okay. Understood. Thank you.11:54
egonzalezleni1, what i try to say is, all need to share the same namespace, adjust --namespace in kolla-build command to match your other images11:55
*** dave-mccowan has joined #openstack-kolla11:55
leni1egonzalez, understood. So my namespace should be kolla/<image>, right? Since all my other images are from Docker Hub11:56
*** janki has joined #openstack-kolla11:56
egonzalezleni1, yep only --namespace kolla (is default iirc)11:58
leni1I think that also means I will have to build each image for cinder, glance, and neutron individually, not all at once.11:58
leni1Oh... Yes. So --namespace kolla will work for all of them at once?11:58
egonzalezleni1, you can use cinder neutron glance at the end of the kolla-build command to build those images12:02
*** pradk has joined #openstack-kolla12:02
egonzaleznote the spaces between image names12:02
*** hieulq has quit IRC12:04
*** daidv has quit IRC12:04
*** duonghq has quit IRC12:04
*** kevinz has joined #openstack-kolla12:05
*** schwicht has joined #openstack-kolla12:05
*** kevzha01_ has joined #openstack-kolla12:08
*** kevinz has quit IRC12:12
openstackgerritMichel Rode proposed openstack/kolla-ansible master: Added open-iscsi to default removals  https://review.openstack.org/47922612:15
*** brad[] has quit IRC12:16
leni1egonzalez, thank you very much12:17
*** brad[] has joined #openstack-kolla12:18
*** daidv has joined #openstack-kolla12:19
*** krtaylor_ has joined #openstack-kolla12:19
*** hieulq has joined #openstack-kolla12:19
*** duonghq has joined #openstack-kolla12:19
*** caoyuan has quit IRC12:20
*** krtaylor has quit IRC12:20
*** eaguilar has joined #openstack-kolla12:22
*** caoyuan has joined #openstack-kolla12:26
*** hrw has quit IRC12:31
*** hrw has joined #openstack-kolla12:32
*** zhurong has quit IRC12:36
*** kbaegis has quit IRC12:36
*** sambetts has quit IRC12:38
*** schwicht has quit IRC12:42
*** sambetts has joined #openstack-kolla12:42
manheimhi12:42
*** ansmith has joined #openstack-kolla12:44
*** leni1 has quit IRC12:44
serlexhi12:44
*** awiddersheim has joined #openstack-kolla12:45
manheimi have some questions, they may seem conceptual12:47
manheimwhy put the libvirt process in a container?12:47
manheimwhy not let it on the host12:47
*** awidders_ has quit IRC12:49
*** rwallne__ has quit IRC12:50
*** rwallner_ has joined #openstack-kolla12:53
openstackgerritMerged openstack/kolla master: Fixed the invalid link in the kolla/image/build.py  https://review.openstack.org/48145712:53
*** goldyfruit has joined #openstack-kolla12:56
*** mdnadeem has quit IRC12:59
*** schwicht has joined #openstack-kolla13:00
*** wahnsinn has joined #openstack-kolla13:02
*** masber has quit IRC13:06
*** goldyfruit1 has joined #openstack-kolla13:06
*** caoyuan has quit IRC13:07
*** goldyfruit has quit IRC13:08
wahnsinnHey, I have a question regarding the network configuration after a kolla install:13:08
manheimhi, shoot13:08
wahnsinnon my controller node neither br-ex nor br-tun are UP and the vm's have no internet connection13:09
*** kristian__ has joined #openstack-kolla13:09
wahnsinnif i tcpdump vxlan_sys_4789 I can see the ping requests but no replys13:09
wahnsinnis it normal that the bridge devices are down?13:10
wahnsinn(my environment consists of one controller node and one compute with two NICs each, eth0 is connected to the outside)13:12
egonzalezwahnsinn, is normal to be down in the host, but if you use docker exec openvswitch_vswitchd ovs-vsctl show should be there up13:13
wahnsinntrue13:15
egonzalezwahnsinn, is ping going outside the q-router qvo* interface?13:15
wahnsinndo I have to check that inside the container?13:16
*** hieulq has quit IRC13:16
egonzalezwahnsinn, in the namespaces, do ip netns in network node13:16
*** daidv has quit IRC13:17
*** trozet has joined #openstack-kolla13:17
egonzalezthere you can find a qrouter namespace, do ip netns exec qrouter<id> ip a to find the qvo interface13:17
*** duonghq has quit IRC13:17
*** omenvl has joined #openstack-kolla13:20
*** mmehan has joined #openstack-kolla13:20
wahnsinnI don't have a qvo interface there, only qr-* and qg-*13:21
egonzalezwahnsinn, sorry, qg is the one13:22
*** omenv has quit IRC13:23
wahnsinnand how can I run tcpdump on that interface?13:24
*** ducttape_ has joined #openstack-kolla13:24
egonzalezwahnsinn, the same as a physical interface, you can use every command present in the host in the namespaces13:25
*** karimb has joined #openstack-kolla13:25
karimbhello buddies, how does kolla handle missing bridge namespace in network related containers ?13:26
*** ducttap__ has joined #openstack-kolla13:26
egonzalezkarimb, im not getting the question, refer to how bridges are created?13:27
karimbegonzalez actually, i m referfing to the logical happening when launching an instance13:27
karimbas part of the process, sysctl -N net.bridge seems to be launched , which fails on containers as bridge namespace isnt exposed13:28
karimbegonzalez maybe you re running those containers with host network13:28
karimb?13:28
egonzalezkarimb, yep, all containers runs with host networking13:29
*** ducttape_ has quit IRC13:29
karimbegonzalez then in this case, the question is how do you handle dns for those containers13:29
karimbcause using host network means you miss kubernetes service discovery features13:29
karimb( when running on kubernetes)13:30
openstackgerritMerged openstack/kolla-ansible master: Fix an invalid variable name  https://review.openstack.org/48199913:30
sdakemorning peeps13:30
egonzalezkarimb, you talking about k8s, not idea about that sorry13:30
openstackgerritMerged openstack/kolla-ansible master: Use latest docker engine in gate  https://review.openstack.org/48021213:30
karimbegonzalez that s fair :)13:30
karimbegonzalez no one using kolla containers on k8s?13:31
egonzalezmorning sdake13:31
sdakekarimb yes indeeed http:/github.com/openstack/kolla-kubernete13:31
sdakes13:31
*** hieulq has joined #openstack-kolla13:36
*** duonghq has joined #openstack-kolla13:36
*** daidv has joined #openstack-kolla13:36
openstackgerritMerged openstack/kolla-ansible master: Avoid launching "local" actions too many times  https://review.openstack.org/48025613:40
openstackgerritMerged openstack/kolla-ansible master: Set neutron RPC workers and state report workers  https://review.openstack.org/44415113:44
*** schwicht has quit IRC13:44
wahnsinnegonzales, I can see a ping request from <vm-private-ip> to 8.8.8.8 and a unreachable reply from <controllernode> to <vm-private-ip>13:46
wahnsinnso the ping is going outside13:46
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla-ansible master: Update cinder sanity check to use built in shade  https://review.openstack.org/43792013:46
*** caoyuan has joined #openstack-kolla13:47
*** iniazi_ has joined #openstack-kolla13:48
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla-ansible master: Make glance filesystem_store_datadir configurable.  https://review.openstack.org/45209413:48
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla-ansible master: Only start one glance_api when using file backend  https://review.openstack.org/44865413:48
pbourkeberendt: zhubingbing_: hi, can you please revisit https://review.openstack.org/#/c/448654/13:48
*** rwallner_ has quit IRC13:50
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla-ansible master: Add dev mode for Murano  https://review.openstack.org/46760813:50
*** omenvl has quit IRC13:50
*** iniazi has quit IRC13:50
openstackgerritNoboru Iwamatsu proposed openstack/kolla-ansible master: delete delimiter from init fernet condition check  https://review.openstack.org/48085313:51
*** schwicht has joined #openstack-kolla13:51
wahnsinnegonzales, I'm starting to belive that I have a made mistake in the initial config: assuming that I have to NIC's, eth0/<public ip to internet> and eth1/<private ip between nodes>: is network_interface: eth0 and neutron_external_interface: eth1 right?13:51
*** omenv has joined #openstack-kolla13:51
*** rwallner has joined #openstack-kolla13:52
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Fix zun-api logging and state_path  https://review.openstack.org/48096313:52
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Fix tools/cleanup-images script error  https://review.openstack.org/48062813:53
*** rwallner has quit IRC13:53
egonzalezwahnsinn, exacly the other way, eth0 neutron_external_interface and eth1 network_interface13:53
*** rwallner_ has joined #openstack-kolla13:54
egonzalezwahnsinn, note that you connection to the hosts with ansible should be through eth113:54
wahnsinnokay, but will the controller node than still be availabe at eth0 ip?13:54
*** tonyjun01 has joined #openstack-kolla13:54
egonzalezwahnsinn, eth0 will be managed by ovs, and lost connectivity once is added to br-ex13:55
wahnsinnand horizon will be available than at eth1 ip?13:55
egonzalezwahnsinn, all services will be available at haproxy VIP bind at eth113:57
*** omenv has quit IRC13:59
*** rmichel has joined #openstack-kolla13:59
*** pbourke has quit IRC14:01
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Fix bandit tests directory  https://review.openstack.org/48101614:01
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible stable/ocata: Add heat_stack_owner role to admin project  https://review.openstack.org/47417314:01
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible stable/ocata: Add warning while upgrading with dockerhub images N->O  https://review.openstack.org/47580214:02
*** skramaja has quit IRC14:02
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Implement blazar ansible role  https://review.openstack.org/45475214:02
*** tonyjun01 has quit IRC14:06
openstackgerritsean mooney proposed openstack/kolla-ansible master: introduce contrib playbook for ovs-dpdk  https://review.openstack.org/40887214:08
*** janki has quit IRC14:13
*** ducttap__ has quit IRC14:13
*** hongbin has joined #openstack-kolla14:14
*** ducttape_ has joined #openstack-kolla14:14
*** pbourke has joined #openstack-kolla14:18
*** [tony] has joined #openstack-kolla14:19
openstackgerritHongbin Lu proposed openstack/kolla-ansible master: Upgrade from docker-py to docker  https://review.openstack.org/47594114:19
*** ducttape_ has quit IRC14:25
*** ducttape_ has joined #openstack-kolla14:27
*** rmichel has quit IRC14:29
*** omenv has joined #openstack-kolla14:29
*** zhurong has joined #openstack-kolla14:30
openstackgerritJuan Badia Payno proposed openstack/kolla master: Changed fluentd repository for CentOS/RHEL  https://review.openstack.org/46721914:30
*** rmichel has joined #openstack-kolla14:30
*** omenvl has joined #openstack-kolla14:30
openstackgerritJuan Badia Payno proposed openstack/kolla master: Changed fluentd repository for CentOS/RHEL  https://review.openstack.org/46721914:32
*** dixiaoli has joined #openstack-kolla14:33
*** dixiaoli has quit IRC14:33
*** omenv has quit IRC14:34
*** caoyuan_ has joined #openstack-kolla14:35
*** karimb has quit IRC14:36
*** caoyuan has quit IRC14:37
*** [tony] has quit IRC14:38
openstackgerritEduardo Gonzalez proposed openstack/kolla master: Fix gnocchi in version_check script  https://review.openstack.org/48216214:42
*** jamesbenson has joined #openstack-kolla14:44
*** hieulq has quit IRC14:51
*** daidv has quit IRC14:51
*** duonghq has quit IRC14:52
openstackgerritEduardo Gonzalez proposed openstack/kolla master: Remove ignore tempest project in version-check  https://review.openstack.org/48217114:54
openstackgerritAndy Smith proposed openstack/kolla-ansible master: Add support for hybrid messaging backends  https://review.openstack.org/46896614:55
*** jtriley has quit IRC14:56
*** zhurong has quit IRC14:56
*** manheim has quit IRC14:57
*** manheim has joined #openstack-kolla14:57
*** manheim has quit IRC14:58
*** manheim has joined #openstack-kolla14:58
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Clean some Boolean condition checks  https://review.openstack.org/48022515:00
openstackgerritEduardo Gonzalez proposed openstack/kolla master: Remove empty line in config.py  https://review.openstack.org/48217415:01
*** kevzha01__ has joined #openstack-kolla15:01
*** klindgren has joined #openstack-kolla15:01
*** klindgren_ has joined #openstack-kolla15:02
*** rmichel has quit IRC15:03
*** tony_ has joined #openstack-kolla15:03
*** klindgren has quit IRC15:04
openstackgerritAndy Smith proposed openstack/kolla-ansible master: Add qdrouterd role for messaging infrastructure component  https://review.openstack.org/46946215:04
*** kevzha01_ has quit IRC15:05
*** kevzha01__ has quit IRC15:06
openstackgerritRich Wellum proposed openstack/kolla master: Add a section on building custom kolla images from source.  https://review.openstack.org/48112715:07
*** omenvl has quit IRC15:08
*** daidv has joined #openstack-kolla15:08
*** duonghq has joined #openstack-kolla15:08
*** hieulq has joined #openstack-kolla15:09
*** tony_ has quit IRC15:11
sbezverkkfox1111: ping15:13
*** manheim has quit IRC15:14
*** karimb has joined #openstack-kolla15:18
kolla-slack<kfox1111> At the gas station. Driving in. What's up?15:18
sbezverkkfox1111: :) need to discuss one solution, would you have 10-15 minutes sometime today?15:19
kolla-slack<kfox1111> Yeah. Will be at work in about 15min15:19
*** ducttape_ has quit IRC15:19
kolla-slack<kfox1111> Will ping you when I get in15:19
*** vhosakot has joined #openstack-kolla15:20
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla-ansible master: Add dev mode for Horizon  https://review.openstack.org/47459515:20
*** unicell1 has joined #openstack-kolla15:21
*** unicell has quit IRC15:23
inc0good morning15:24
egonzalezmorning inc015:25
vhosakotmornin all!15:25
egonzalezmind checking https://review.openstack.org/#/c/482053/ is a gate fix15:25
rwellumvhosakot: inc0  - deadline for submissions in the 14th correct?15:26
vhosakotrwellum: yes, correct15:27
inc0yup15:27
inc0we need to do it asap, today?;)15:27
*** hieulq has quit IRC15:28
rwellumYup - can you guys look at the etherpad and sketch out changes according to our discussion last week?15:28
vhosakotrwellum: cool, will do15:28
*** daidv has quit IRC15:28
*** klindgren__ has joined #openstack-kolla15:29
*** duonghq has quit IRC15:29
rwellumQQ for anyone. When we change code, are we supposed to pull a branch - or work directly off Master?15:30
*** ducttape_ has joined #openstack-kolla15:30
sbezverkrwellum : I prefer to work on the branch and then rebase on the master when master gets changed15:31
*** klindgren_ has quit IRC15:33
inc0guys fyi, our gates will be broken for a while15:33
vhosakotrwellum: upstream has "fix master first, backport later to an older/stable branch if needed" policy :)15:33
inc0(short hopefully)15:33
inc0our tarballs overloaded infra static server15:33
vhosakotinc0: yeah, I'm seeing messages about it in the infra channel.15:34
vhosakotinc0: what overload? disk or network traffic?15:34
*** klindgren_ has joined #openstack-kolla15:34
rwellumvhosakot: well I meant a local branch - like sbezverk is suggesting I think. Because when you commit with git review - it leaves your workspace behind master I was just trying to figure out if my workflow was wrong.15:34
vhosakotrwellum: ah, yeah, local branch is always good (which shows up as a topic in gerrit UI).15:35
*** klindgren__ has quit IRC15:36
rwellumok noted - cool thanks guys.15:36
vhosakotrwellum: our worksapce is always behind, cannot help that :)  sometimes, we may need to rebase multiple times a day depending on which latest merged  fix is needed.15:36
rwellumvhosakot: 'our workspace' - meaning you have forked or branched kolla - and make changes from there?15:37
inc0vhosakot: network15:37
vhosakotrwellum: our workspace = the workspace we've cloned in which we're branched to fix something.15:37
egonzalezrwellum, I always use git review -f to cleanup, or will end up with thousand local branchs15:37
vhosakotrwellum: no need to fork (thankfully) as openstack upstream does not need "pull requests in GitHub".  Gerrit does not need forks/pull requests.15:38
vhosakotI'm not a fan ot forking because we may end up carry fat forks that diverge from upstream very fast.15:39
vhosakotinc0: ah I see, network is always the issue ;)15:39
kfox1111sbezverk: ping15:40
*** wahnsinn has quit IRC15:40
vhosakotegonzalez: you do "git review -f" _after_ the new branch is merged right :)15:40
sbezverkkfox1111: I was working on adding lioadm as iscsi helper, some people wants to get rid of tgtd15:40
sbezverkand I got most of things figured out and working, but15:41
egonzalezvhosakot, nope, if have to change something i fetch the change. if I wait until is merged i'll forget to clean up ;)15:41
sbezverktgtd used username and password authentication and lioadm/target uses username/password and iqn15:41
sbezverkin our model nova-compute uses iscsd container to carry out requests for attaching15:42
vhosakotegonzalez: ah, if you forget to cleanup.. cool.. yeah, I clean up regularly as .ansible and .tox all take up a lot of space... neutron's .tox is like ~500 M or something :O15:42
sbezverkiscsi targets and these two containers happen to have different iqn15:42
sbezverkso I see authentication failer15:42
kfox1111hmm...15:42
sbezverknow I see two solutions15:42
sbezverk1: make iscsd as a sidfe car container to nova-compute15:43
sbezverkin this case they can share /etc/iscsi/initiator name15:43
*** daidv has joined #openstack-kolla15:43
*** duonghq has joined #openstack-kolla15:43
*** hieulq has joined #openstack-kolla15:43
sbezverk2. use hosts /etc/iscsi/initiator name15:43
sbezverkwhat do you think would work better for ops folks?15:44
kfox1111I kind of like #2 a little better.15:44
kfox1111by coupling iscsid and nova-compute, if you want to update nova-compute you have to do iscsid too.15:44
kfox1111I think nova-compute is purely controlplane, but iscid is dataplane too?15:45
sbezverkkfox1111: iscsid here is control plane too, since it is just a vehicle for nova-compute but 2  works for me too15:46
kfox1111k15:46
*** mgoddard_ has quit IRC15:46
rwellumegonzalez: ah -f is fetch not force :)15:47
kfox1111yeah, either probably works then. #2's probably simpler too.15:47
sbezverkkfox1111: so the logic would be nova-compute, cinder-volume and iscsid will use host maps for /etc/iscsi15:47
kfox1111hmm... what else is in there?15:47
kfox1111should we do a /var/lib/kolla/xxxxx thing instead?15:47
egonzalezrwellum, nope -f means if the change is pushed to gerrit, remove local branch and checkout to origin branch (most of times master)15:47
jamesbensonmorning all :-)15:48
sbezverkif initiator file does not exist, which is possible if initiator tools are not installed on the host, then one of this will generate one15:48
sbezverkand the other will start using it15:48
rwellumegonzalez: that's really a neat idea thanks.15:48
jamesbensoninc0: I think I know what's up with ceph15:49
sbezverkkfox1111: /etc/iscsi is default location, I am not sure if everything can be customized to use /var/lib/kolla/xxx15:49
kfox1111sbezverk: its a container. can host mount it there to /var/lib/kolla/xxx in the container.15:49
kfox1111 /etc/iscsi in the container I mean.15:50
kfox1111I'm a little leary of letting stuff on the host leach into the containers.15:50
inc0jamesbenson: do tell please15:50
kfox1111if the host has a different iscsi version or something then the containers, it might cause problems.15:50
kfox1111maybe the iscsi container does the creating of the files, and the other containers have an init container that waits till the file exists?15:51
sbezverkkofx1111: ok you mean we keep file in var/lib/kolla/iscsi on the host but mount it to /etc/iscsi in the containers?15:51
jamesbensonI did a manual deploy and having issues as well, but I eventually got it working.  The solution was how I had my network configured in ceph (and that's something that changed here as well when I was deploying kolla).15:51
kfox1111sbezverk: yeah.15:51
inc0jamesbenson: what was the change?15:52
jamesbensonCeph default options failed for me.  I had to explicitly state my public and cluster network in my .conf file along with mon_host was set to internal by default and needed to be external.15:52
inc0right...well, you can do this with kolla-ansible too15:53
jamesbensonI still need to play a little bit more to see exactly what failed, but with those 3 things it work15:53
inc0but since you have ceph working15:53
*** jascott1 has quit IRC15:53
inc0just keep it;)15:53
sbezverkkfox1111: ok, sounds good.. will try to check first in common initiator name will actually resolve the authentication failure I see.15:53
kfox1111ah. good plan. :)15:54
jamesbensonis public and cluster in kolla the storage_interface & cluster_interface specifically for ceph?15:54
*** harbie has quit IRC15:55
sbezverkkfox1111: cool thanks for discussion!15:55
inc0jamesbenson: yes15:56
inc0cluster = mon to mon (and osd to mon) communication15:57
*** jtriley has joined #openstack-kolla15:57
inc0storage is for vm to rbd communication15:57
*** unicell1 has quit IRC15:57
inc0well storage iface is also used with other storage backends (so not techincally ceph specific;)))15:57
*** kristian__ has quit IRC15:57
*** kristian__ has joined #openstack-kolla15:58
*** harbie has joined #openstack-kolla15:58
egonzalezjamesbenson, https://github.com/openstack/kolla-ansible/blob/master/doc/production-architecture-guide.rst#interface-configuration15:58
*** rhallisey is now known as rhallisey-biab15:58
jamesbensonthanks egonzalez :-)15:59
*** rhallisey-biab has quit IRC15:59
*** egonzalez has quit IRC16:03
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: Allow tmp path to download registry  https://review.openstack.org/47594016:05
vhosakotjamesbenson: storage_interface defaults to network_interface (which is the public interface or kolla_external_vip_interface) as the default behavior in kolla -->  https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml#L127  and  https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml#L125.   But, in production, yes, storage is a separate network/segment.16:06
openstackgerritBradley Jones proposed openstack/kolla-kubernetes master: (WIP) Deploy playbook using microservices  https://review.openstack.org/47358816:08
vhosakotjamesbenson: the official openstack docs also mention that storage network must be a separate non-public segment that just connects the computes to the storage nodes - https://docs.openstack.org/arch-design/design-storage/design-storage-concepts.html16:08
vhosakotjamesbenson: I observed a lot less traffic drop when I enabled jumbo frames with ceph -- https://communities.cisco.com/community/developer/openstack/blog/2017/01/13/jumbo-mumbo-in-openstack16:10
*** serlex has quit IRC16:10
vhosakotceph_mon kills TCP on the storage nodes when parallel writes into volumes start :)16:11
jamesbensonthanks for the info vhosakot16:12
vhosakotjamesbenson: cool, I'm about write another blog about OpenStack and ceph (hopefull in the next 2-3 weeks).16:13
openstackgerritBradley Jones proposed openstack/kolla-kubernetes master: (WIP) Deploy playbook using microservices  https://review.openstack.org/47358816:13
openstackgerritBradley Jones proposed openstack/kolla-kubernetes master: (WIP) Deploy playbook testing with nova PV  https://review.openstack.org/47982616:14
jamesbensonhere we've never done anything special for ceph, just sort of let it do it's thing....  :-/ We will have to investigate more.   Currently our machines are only wired for 2 ports, public and internal (all of them have 4 or 8 ports though)16:14
inc0jamesbenson: but you had same issues with ceph-deploy right?16:16
inc0so it doesn't seem to be kolla specific?16:16
*** coolsvap has quit IRC16:16
jamesbensonwell once I got the networking correct, ceph is healthy with 3 osd and 1 mon (http://paste.openstack.org/show/614949/ on our dev cluster)16:18
jamesbensonI haven't finished a kolla deploy with external ceph though16:18
jamesbensonright now looking at the kolla details16:18
*** jascott1 has joined #openstack-kolla16:19
openstackgerritMerged openstack/kolla master: Fix mock order  https://review.openstack.org/48043416:19
jamesbensonvhosakot: how do you set the jumbo frames, is that solely in the configs in kolla/ceph, or do you need to modify switch settings as well?  (Just trying to look ahead once I get things sorted out)16:20
*** caoyuan_ has quit IRC16:20
openstackgerritBradley Jones proposed openstack/kolla-kubernetes master: (WIP) Deploy playbook using microservices  https://review.openstack.org/47358816:20
vhosakotjamesbenson: no need to do anything on the switch/TOR (as they will/should not be in the path of the storage network between the compute node and the storgae/rbd node).  Jumbo on all OpenStack nodes can be configured by tweaking configs in neutron.conf/ml2_conf and OVS config.16:22
openstackgerritBradley Jones proposed openstack/kolla-kubernetes master: (WIP) Deploy playbook testing with nova PV  https://review.openstack.org/47982616:22
*** reidrac has quit IRC16:22
vhosakotjamesbenson: in my case, I had Cisco FEX (Fabric Extenders) and FI's (Fabric Interconnects) between computes nodes and ceph nodes, so I just configured jumbo frames on them manually using NXOS CLIs.16:23
*** mgoddard_ has joined #openstack-kolla16:23
vhosakotjamesbenson: keeping the ceph/storage/rbd nodes as nearest as possible to the computes nodes gave me best perf (have minimum or zero L2/L3 hops between compute node and storage nodes).16:24
vhosakotevery hop must have jumbo, else PMTU descovery (if turned on) will default to non-jumbo (1,500 bytes) :)16:25
sbezverkkfox1111: that was it, sharing iqn between nova-compute and iscsd, now lioadm is working :)16:25
jamesbensonvhosakot, always interested in what others think, but we plan on (and let me know if this is crazy because we always do it this way - but are willing to change), 3 controller/network/storage combo; 3 storage/compute combo; 25 compute nodes. (Total nodes are 32)16:32
*** jascott1 has quit IRC16:33
jamesbensoninc0: in regards to the ll kernel, once I know that I can get consistent deploys here, and I'll try a few deploys back to back... I'll try the only change is the kernel and let you know.16:34
SamYaplejamesbenson: dont run ceph-mon on the same nodes as the ceph-osds16:34
SamYaplebut otherwise, that looks good16:34
SamYaplehyperconveraged storage/compute is all the rage these days16:34
vhosakotjamesbenson: also, dont run ceph osd on compute nodes (I know a team that does that :))16:35
openstackgerritSerguei Bezverkhi proposed openstack/kolla master: Adding new iscsi-target image to support lioadm  https://review.openstack.org/48185816:35
SamYaplevhosakot: its defintely fine to run ceph-osds on compute nodes. that has been the majority of my deploys16:35
vhosakotjamesbenson: the number of ceph nodes depends on how much data the customer wants to write in the volumes...16:35
sbezverkinc0: wrt lioadm I will need ^^^ these changes, could you please check when you have time..16:35
vhosakotSamYaple: in that case, if the compute node crashes, we lose a storage node, plus, computes need a lot of disks in that case.16:36
*** hieulq has quit IRC16:36
*** daidv has quit IRC16:36
*** duonghq has quit IRC16:36
SamYaplevhosakot: yea. thats what would happen. not sure how seperating computes and storage is going to fix that16:36
*** shardy is now known as shardy_afk16:37
SamYaplegiven the goal is to have as many nodes as possible, running storage on all the computes is really useful16:37
vhosakotSamYaple: separating computes nodes and storages, atleast we do not lose customer data in vloume when a compute node crashes.16:37
*** harlowja has joined #openstack-kolla16:37
SamYapleyou should _never_ be losing data when you lose a node16:38
SamYapleif you are, you have setup your cluster wrong16:38
jamesbensonand our storage nodes have a ton of space, compute has less.16:38
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169016:38
ReepicheepI have taken kinda a hybrid for compute nodes and osds16:38
vhosakotSamYaple: what if a compute node dies before ceph has replicated/rebalanced?16:38
ReepicheepI have a few osds on each compute node but they are fast disks that are writeback cache16:39
SamYaplevhosakot: thats not how ceph works. it is "strongly consistent" which means before the client gets an ack on the write, it has written it to the entire cluster16:39
jamesbensonwe use raid on everything (old hard drives but when a drive goes, we replace quick)16:39
SamYaplevhosakot: also, remember, you may not be writing any data to the node the compute is on16:39
jamesbensonperformance isn't super critical for us, we try our best of course to make it fast, but staying up and not dying is important, hence the raid.16:42
ReepicheepI took this advice "Do enable RBD caching on Nova compute nodes" from:16:42
Reepicheephttps://www.hastexo.com/resources/hints-and-kinks/dos-donts-ceph-openstack/16:42
Reepicheephopefully it's not to crazy.. it seems to work16:43
vhosakotSamYaple: yeah, in our case, osd was on a compute node, compute node died due to disk failure, ceph hadn't rebalanced fully, any many volumes were lost, could not be recovered.16:44
SamYaplevhosakot: like i said, if you lost data with ceph it was not because the node was also a compute node16:46
SamYapleto lose data with a proper ceph cluster you need to have 3 complete disk failures without having rebalanced16:46
vhosakotSamYaple: ah I see16:47
jamesbensonSamYaple, and to chime in with the little knowledge that I know, 3 complete disk failures where the data happens to be on those three nodes.... if the data is still scattered it might not be a complete loss.16:48
rwellumReepicheep: good article that16:49
SamYaplejamesbenson: "properly" setup ceph would not allow the data to exist on one node, so yes. it would have to be three disk failures on different nodes at the same time16:49
Reepicheeprwellum: yeah.. the one advice I haven't followed is "put all-flash OSDs in a separete CRUSH root"16:50
kfox1111SamYaple: and even then, depending on number of disks per host, it still may not end up loosing data.16:50
Reepicheepit's not so easy with kolla-ansible short of using external ceph16:50
jamesbensonyes, I've recovered where we were dismantling and realized we did something wrong, recovered some, not all, but we were lucky and got what we needed.16:50
kfox1111but you need a good sized ceph at that point. :)16:50
Reepicheepwhich I haven't taken that jump yet16:50
jamesbensonno flash in our datacentre16:51
SamYaplekfox1111: to get to that range is something like 1500 disks though. but yea16:51
rwellumAre there any viable distributed storage alternatives to Ceph? Like Gluster etc.16:51
*** daidv has joined #openstack-kolla16:51
*** hieulq has joined #openstack-kolla16:51
*** duonghq has joined #openstack-kolla16:51
rwellumJust curious as I know several large companies that refuse to use Ceph.16:51
SamYaplerwellum: the real "win" for ceph is the distributed block storage. Gluster is all file based16:52
rwellumAh16:52
rwellumThe negatives I head are 'it's a development project', 'not supported', 'too complicated' etc.16:53
rwellumheard :)16:53
kfox1111rwellum: perception issue. :/16:54
Reepicheepyears ago I tried to use file based block devices stored in gluster.. it didn't go well16:54
kfox1111its a developemnt project is false. lots of production usage.16:54
kfox1111not supported. false. you can pay redhat or others to support it.16:54
SamYaplerwellum: ceph is older that openstack16:54
kfox1111too complicated? perhaps. less complicated then other ha storage systems I've played with though.16:54
SamYaplethats my go to when people talk about ceph being young16:55
rwellumbradjones: regarding your review 473588 - were you looking at the other ansible pb going through review to see if they can be merged at all?16:55
rwellumSamYaple: that I did not know :)16:55
kfox1111yeah. I remember a guy here kicking the tires on ceph/gluster I wana say 2 years before we started playing with openstack.16:55
*** jascott1 has joined #openstack-kolla16:55
kfox1111they really were green then though.16:56
rwellumjascott1: hi16:56
jascott1rwellum hey! hows it going?16:56
rwellumNot bad :) - I am curious - have you looked at bradjones ansible solution?16:57
bradjonesrwellum, which other review?16:57
jascott1I have, actually working on cramming it into a container with "all the things" to automate kk8s setup16:59
*** daidv has quit IRC16:59
*** hieulq has quit IRC16:59
SamYaplejascott1: a container starting a container orchestration to start containers?16:59
*** duonghq has quit IRC16:59
jascott1how perverse17:00
jascott1whatup SamYaple!17:00
SamYapleo/17:00
rwellumbradjones: I don't think it's in review yet, jascott1 correct me if I'm wrong.17:01
*** dciabrin has quit IRC17:01
kfox1111a container at its core really is just a software distribution mechanism.17:02
*** dciabrin has joined #openstack-kolla17:02
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: Enable proxy cache for tarballs download  https://review.openstack.org/48221717:02
kfox1111with that definition, the above isn't as perverse as it seems.17:02
jamesbensonbtw, thank you vhosakot, SamYaple, Reepicheep, inc0.  Your knowledge is impressive and took many pearls from that convo.  :-)17:02
SamYaplejamesbenson: i made it all up. trust no one17:03
jamesbensonha!17:03
vhosakotjamesbenson: cool, I still need a PhD in ceph :)17:03
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: Enable proxy cache for tarballs download  https://review.openstack.org/48221717:03
vhosakotjamesbenson: ceph is addictive :)17:03
jamesbensonhey, I started a phd, not worth the hype ;-)17:03
vhosakotjamesbenson: :)17:03
jamesbenson2 MS's instead17:04
vhosakotI got 1 MS17:04
vhosakotstill no use ;)17:04
jascott1kfox1111 i was quoting C3PO17:04
inc0vhosakot: as in, when you start to use it it's hard to get out? You watch your life wasted and opportunities missed, you really really want to get out but it's just too hard...17:04
jamesbenson(I could have had a third, but no point in having 2 both in physics)17:04
inc0one...more...osd...17:04
kfox1111jascott1: ah. I guess that means I need to go watch again... my quote capability is slipping. :)17:04
jascott1haha dont worry it was in a prequel :)17:05
SamYapleinc0: have you seen in 17.06 docker you can do a FROM {{ buildarg }} ?17:05
kfox1111jascott1: ah. that might explain it. ;)17:05
inc0wow that's awesome17:05
SamYapleSo you *could* do a kolla base image with set_config and the like, then build LOCI images17:05
inc0did they enable "templating"?17:05
SamYapleinc0: no17:06
jascott1rwellum are you talking about this? https://review.openstack.org/#/c/457317/17:06
SamYapleits the standard build-arg system17:06
SamYaplethis might make merging the two projects back together more... possible though17:06
jascott1rwellum oh you are prob talking about the conainer thing I was talking about... i am working off inc0's PS17:06
inc0SamYaple: yeah, possible today with overrides but I hear ya, if we'd add one more image layer for *just tini/set_config* we could do that...17:07
inc0well still would need to include all the extended starts17:07
rwellumYeah jascott1 there seem to be about 3 very similar efforts.17:07
SamYapleinc0: *possible* sure, but i think we can both agree injecting the scripts with overrides isnt that best17:08
SamYaplewe just included that as a stop gap until 17.06 and this feature17:08
rwellumBut maybe they should be separate - not sure.17:08
inc0worth thinking about for sure17:08
jascott1rwellum we should probably coordinate at some point :/17:09
SamYaple$ cat Dockerfile17:10
SamYapleARG FROM=gcr.io/google_containers/ubuntu-slim:0.1217:10
SamYapleFROM $FROM17:10
SamYapleSHELL ["/bin/bash", "-c"]17:10
SamYaple$ docker build --build-arg FROM=ubuntu .17:10
SamYapleoops17:10
SamYaplemeant to pastebin that17:10
SamYapleinc0: http://paste.openstack.org/show/614952/17:11
bradjonesrwellum the main difference between 457317 and my patch is that mine isn't trying to setup kubernetes for you it's just about deploying kolla, the other main differences is using microcharts vs service charts to make upgrading in the future easier & also to remove the dependency on entrypoing17:11
bradjonesso they are different approaches17:11
bradjonesbut both valid, 457317 is a great all in one deployment playbook17:12
kfox1111should reduce duplication if we can and share as much as possible.17:12
inc0SamYaple: if we'd move tini/set_config to end-containers17:12
kfox1111its hard to keep lots of implmentations up to date.17:12
inc0as nova-api17:12
inc0and do FROM loci-nova17:12
inc0that would work too17:12
rwellumbradjones: ah thanks -good to know17:13
inc0and we wouldn't need to wait for this docker change17:13
SamYapleinc0: but then you have to add a layer to _all_ the images and rebuild everything ontop of things17:13
SamYaplethis way its one layer17:13
inc0yeah, but extended-starts are also needed17:13
rwellumbradjones: I also agree with kfox1111  - good to share where possible. Or at very least document the heck out of each tool so the user can see and understand the differences.17:15
sbezverkinc0: please review  https://review.openstack.org/48185817:17
bradjonesyeah I agree on both points, especially around docs, that's something i'll add shortly17:17
inc0sbezverk: why new container?17:19
rwellumbradjones: thanks17:19
sbezverkinc0: we need a container hosting targets, it activates target kernel module and restores saved targets on container restarts17:21
*** manheim has joined #openstack-kolla17:22
vhosakotSamYaple: so, from the time a nova VM writes data to a volume, to the time this data is replicated/balanced on all the osds, how much is this time window?  like micro seconds/milli seconds/seconds?  also, does this time window increase if ceph is busy due to a lot of nova VMs simultaneuosly writing to volumes?17:22
sbezverkinc0: I got PoC wokring with lioadm so I think I am on the right track17:24
inc0cool, thanks!17:25
*** manheim has quit IRC17:26
*** manheim has joined #openstack-kolla17:26
*** lpetrut has quit IRC17:26
*** Mannheim has joined #openstack-kolla17:27
*** ducttape_ has quit IRC17:28
sean-k-mooneySamYaple: is thier a specific reason not to run ceph mons on same nodes as osd if you have the cpus free?17:29
sean-k-mooneySamYaple: just reading back over ceph convo17:30
vhosakotSamYaple: let me know what you think when you get a chance about the time window question.17:31
vhosakotsean-k-mooney: yeah, ceph_mon does not consume a lot of CPU/mem/disk I've seen, you can fit them on the osd boxes if you have enough resources.17:32
vhosakotactually, ceph_mon gets busy when too many writes happen.17:32
sean-k-mooneyvhosakot: i run my 3 controllers as allinone nodes (openstack contorler+ ceph mon+ ceph osd+ nova compute) seams to work fine17:33
kfox1111it depends more on the size of your boxes and size of the overall cluster.17:34
kfox1111if you only have 3 nodes, shared mon is usually fine.17:34
sean-k-mooneythen again they are 48 core servers so they are not exactly resource starved and i only have 12 osd in my cluster for it to manage.17:34
kfox1111unless they have a huge amount of storage. in which case, you can afford a few more thin nodes.17:35
*** manheim has quit IRC17:35
vhosakotsean-k-mooney: I'm kinda those people who think compute node should not have anything other than hypervisor :) hahaha, it's just a arch design I think.   we keep storage (osd's) nodes separate17:35
kfox1111vhosakot: yeah. we did shared ceph/compute for a while.17:35
kfox1111it was fine right up until it wasn't. :)17:35
vhosakotyeah, our computes and controllers are almost diskless (very minimum disks as needed)17:36
sean-k-mooneyvhosakot: i started my cluster with 3 nodes all in one, then adde 3 as storage + compute and add another 3 later as just compute. i have another 30 or so to add soon that will just be compute17:36
vhosakotkfox1111: yeah, many people do share osd on compute design, and it works for them in prod.17:36
kfox1111had good luck with that until recovery kicked in. then it was really disruptive to services. :/17:38
*** rhallisey has joined #openstack-kolla17:38
sean-k-mooneykfox1111: vhosakot i guess the main think if you do share is to make sure you have a dedicated nic for cpehs replication and that you addjust the vcpu_pin_set in nova to ensure that you have enough coures reserved for the system to handel the ceph recovery17:39
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla-ansible master: Enable proxy cache for tarballs download  https://review.openstack.org/48221717:39
*** daidv has joined #openstack-kolla17:39
vhosakotkfox1111: ceph's vulnerability is == if the usecase increases the time window from the time a nova VM writes something into a volume, to the time ceph_mon replicates/rebalances that data onto all the osds, and this time window is a function of how busy ceph_mon is and the number of osds ceph_mon needs to replicate the data onto.17:39
*** duonghq has joined #openstack-kolla17:40
*** hieulq has joined #openstack-kolla17:40
kfox1111yeah.17:40
sean-k-mooneyvhosakot: provided your not doing asycn io in the gust i whould have assumed the rbd device would not have completed the right until ceph had singneled that it had been completed  which it should not do until it has atleast been written to the journal17:42
sean-k-mooneyvhosakot: there may be a delay betwenn getting to your dsired level of replication but that would likely be load dependent and hevily influnced by your ceph config17:43
*** hieulq has quit IRC17:43
vhosakotsean-k-mooney: yeah, I have not looked into ceph config's tuning much... tried to just make it lose volume in my scale testing :)17:44
*** duonghq has quit IRC17:44
vhosakotsean-k-mooney: yes, faster dedicated NIC for storage fastens replication.17:45
inc0vhosakot rwellum let's make summit proposals today, we can always edit stuff afterwards17:45
rwellumWFM inc017:45
rwellumI've gotta rack some switches in 15m for a couple of hours - but will be back17:46
vhosakotwe're like customer data, customer data, customer data.. so ended up having separate osd nodes.17:46
vhosakotinc0: rwellum cool, ready when you are :)17:46
inc0https://etherpad.openstack.org/p/kolla-sydney-custom-repo-talk17:47
sean-k-mooneyinc0: is https://review.openstack.org/#/c/466132/ relevent to ^17:49
inc0yeah17:49
sean-k-mooneyinc0: ill fix the typo and reupload that shortly17:49
inc0cool17:49
inc0sean-k-mooney: can you review odl patch?17:50
sean-k-mooneysure which one. i notice it was not building correctly17:50
inc0https://review.openstack.org/#/c/416367/17:50
SamYaplevhosakot: re: time window question17:51
SamYaplewhen the write is ack'd by the cluster it is replicated everywhere. so if you do a 'sync' in the vm, when that returns everything is sync'd17:52
SamYaplewhen something is actually commited to the backing storage and not _only_ in ram is up to the kernel17:52
*** kristia__ has joined #openstack-kolla17:52
rwellumsbezverk: have you seen any oddities with openvswitch lately - in my setup - everything comes up but 'neutron-openvswitch-agent-network'.17:53
vhosakotSamYaple: cool, thanks for the info17:53
sean-k-mooneyinc0: oh the ansible role, cool do you know if the guy working on ovn are planing to submit a role for that also?17:54
inc0no idea17:54
sbezverkrwellum nope, I am using latest kolla-k8s, seems to be working fine17:54
sbezverkrwellum : what is it complaining about? bad weather ;) ??17:54
SamYaplesean-k-mooney: if you run the osds on the same nod as the ceph mon and that node _crashes_ the cluster locks up for ~30 seconds17:55
rwellumsbezverk - maybe! :) https://www.irccloud.com/pastebin/dqgvyekd/17:56
SamYaplesean-k-mooney: when an osd dies, its a topology change that the mons have to agree on. when a mon dies a new election is called (to ensure quorum). when both die at the same time the cluster freezes to call an election and then update the topology17:56
*** kristian__ has quit IRC17:56
sean-k-mooneySamYaple: ah ok that makes sense17:56
*** wahnsinn has joined #openstack-kolla17:57
sean-k-mooneySamYaple: so colocating compute nodes and ceph_osd should be ok but not ceph_mons and ceph_osd to avoid the quorum sync latency on a node failure17:57
sbezverkrwellum : you need to check docker log for that container, last paste only shows that it was crashing.. not very useful..17:58
*** duonghq has joined #openstack-kolla17:58
*** hieulq has joined #openstack-kolla17:58
*** ducttape_ has joined #openstack-kolla18:00
*** dmellado has quit IRC18:02
*** dmellado has joined #openstack-kolla18:02
*** schwicht has quit IRC18:02
rwellumdocker logs <name of container> sbezverk ?18:03
jamesbensonvhosakot & sean-k-mooney: I'm reading Learning Ceph by Singh right now, they have some interesting info in there...18:03
*** kristia__ has quit IRC18:03
vhosakotSamYaple: when the primary ceph_mon died, we saw the nova vm was not able to read data too, as reading also first contacts ceph_mon to find out which osd to read from.  for a long time, I thought reading does not involve ceph_mon at all and that reading is just compute<-->osd interaction without involving ceph_mon...18:04
vhosakotjamesbenson: link please :)18:05
*** sambetts is now known as sambetts|afk18:05
*** schwicht has joined #openstack-kolla18:07
jamesbensonvhosakot: https://www.packtpub.com/virtualization-and-cloud/learning-ceph. (but google the title, you might find it else where ;-) )18:07
sbezverkrwellum docker ps -a | grep neutron-openvswitch-agent18:07
jamesbensonand keep an eye out on packt.... They have a free book every day https://www.packtpub.com/packt/offers/free-learning18:08
vhosakotjamesbenson: cool, thanks18:08
inc0vhosakot rwellum I wrote some abstract in etherpad, feel free to comment/fix language/repeal and replace it alltogether18:08
vhosakotinc0: don't worry, we won't repeal-and-replace bigly ;)18:09
rwellumsbezverk https://www.irccloud.com/pastebin/DgYamAOY/18:11
vhosakotsean-k-mooney: what about orchestration for the out-of-tree non-kolla external images built -->  https://review.openstack.org/#/c/466132/   the user mus have his/her own orchestration mechanism right using ansible/k8s/whatever?18:12
sean-k-mooneyvhosakot: basically you can replicate https://review.openstack.org/#/c/408872/ for the kolla-ansible case18:13
sean-k-mooneyvhosakot: for k8s i guess you would jsut have a chart18:14
jamesbensonvhosakot: http://paste.openstack.org/show/614956/18:14
vhosakotsean-k-mooney: I see, cool, thanks for the info18:14
SamYaplesean-k-mooney: correct. but in that scenario it is just a delay, you dont lose data. so in some situations (if you know the risks) its ok to run the mons and osds18:15
vhosakotjamesbenson: yes, separate mon nodes is the recommendation I've read.. coo18:15
*** kristian__ has joined #openstack-kolla18:15
vhosakotcool*18:15
*** tonanhngo has joined #openstack-kolla18:15
*** kristian__ has quit IRC18:15
*** lpetrut has joined #openstack-kolla18:15
sbezverkrwellum : I do not see it on the list18:16
SamYaplevhosakot: it gets a copy of the cluster map from the ceph mon and just needs to verify that is up to date18:17
sbezverkrwellum : but do you see it in kubectl get pods in kolla?18:17
sbezverkas crashing right?18:17
rwellumYes18:18
sean-k-mooneywas there an issue with tarballs.openstack.org today http://logs.openstack.org/72/408872/12/check/gate-kolla-ansible-dsvm-deploy-centos-binary-centos-7-nv/1cf0d29/console.html#_2017-07-10_14_21_21_86421718:18
rwellumSorry sbezverk  - I got pulled off for an hour or so - will be back to debug18:18
vhosakotSamYaple: right, so compute<-->ceph_mon is pure ceph control plane, right, not data plane (in which VM's app's data written to volume travels)... we saw it, and hence ended up having slower NICs for compute<-->ceph_mon links as they need not be super fast like compute<-->osd links18:19
openstackgerritsean mooney proposed openstack/kolla master: enable the kolla build system to use out of tree docker files  https://review.openstack.org/46613218:20
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169018:21
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Fix designate-api listen interface  https://review.openstack.org/48223818:22
openstackgerritSerguei Bezverkhi proposed openstack/kolla master: Adding new iscsi-target image to support lioadm  https://review.openstack.org/48185818:26
*** unicell has joined #openstack-kolla18:29
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169018:31
*** lpetrut has quit IRC18:35
*** karimb has quit IRC18:39
*** lpetrut has joined #openstack-kolla18:42
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Fix searchlight nova resources indexation  https://review.openstack.org/48224318:47
*** mgoddard_ has quit IRC18:49
*** rwallner_ has quit IRC18:52
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Searchlight: activate Ironic resources  https://review.openstack.org/48224818:54
SamYaplevhosakot: im not entirely sure what you are saying there18:54
vhosakotSamYaple: I meant, does ceph_mon see any data? :)18:55
SamYaplevhosakot: the "public_network" is where all the clients talk ot mons _and_ read data over18:58
SamYaplebut no data from a vm will exist in the mons18:58
vhosakotSamYaple: not "exist".  does ceph_mon forward any data?  receive data from nova VM and send it to the right osd?18:59
*** shardy_afk is now known as shardy18:59
*** rwallner has joined #openstack-kolla18:59
SamYaplevhosakot: the clients talk directly to the osds, there is never any data forwarding19:00
vhosakotSamYaple: right, so, compute<-->ceph_mon can have slow links vs compute<-->osd must be super fast links, is what I meant/asked :)19:01
jamesbensonSamYaple, I thought compute/storage wasn't recommended due to the high CPU/RAM used when rebalancing OSD, backfill or recovery...19:02
SamYaplevhosakot: if you mean 1gb and 10gb, yea that mihgt be ok19:02
SamYaplejamesbenson: thats why most people have a bad _experince_ with hyperconveraged compute/storage. but if you are aware of it you can avoid it causing issues19:02
vhosakotSamYaple: yep, few of our kits have 10G compute<-->ceph_mon and 40G compute<-->osd.19:03
SamYaple1gb of ram per TB of storage in reserve19:03
SamYaplevhosakot: perfect. that sounds great19:03
*** rwallner has quit IRC19:04
jamesbensonour computes have 1200gb, (4x300gb), is it even worth to put 1-2 OSD's there?19:05
vhosakotjamesbenson: well, don't "hyperconveraged" does not necessarily mean compute+storage combined into one box, is it?  I thought hyperconveraged means all network, compute, storage all combined into a nice-looking, easy-installable "rack" like flexpod/vblock.  I've seen separate storage nodes at least in vblock.19:06
sdakehey folks - ptl election is about a month out19:06
SamYaplejamesbenson: so the deal with that is if you have dedicated storage boxes that will not be running computes then you should _not_ run the osds on your compute (probably)19:07
sdakeelections19:07
jamesbensongah, just trying to figure out a good model for our production that is still being designed...19:07
SamYaplebut each situation is differnet19:07
vhosakotsdake: thanks for the info19:07
SamYaplejamesbenson: do you have a list of hardware and specs?19:08
vhosakotjamesbenson: 2 OSDs with 1.2TB == 600 GB per OSD.  not bad for a few volumes IMO.  really depends on how much data the VMS want to write into volumes.19:10
*** manheim has joined #openstack-kolla19:10
*** manheim has quit IRC19:10
*** manheim has joined #openstack-kolla19:11
jamesbensonwe have 28, dell r410's (4HD, 300GB); 11 dell r610's (4HD, 300GB); 7 Dell r710's (6HD, 2TB); we also have a SAN that we want to connect, but not sure if it is possible  Dell equalogic PS6510.   The servers all have 4 nics minimum, but only 2 wired, all 1G.19:11
jamesbensonWe typically put the 41019:12
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Fix designate-api listen interface  https://review.openstack.org/48223819:12
jamesbenson's as compute, 710's at controller/storage, and 610's as compute19:12
jamesbensonsorry!  Typo! 14 R410's, not 28....19:14
SamYaplejamesbenson: youre going to get hurt pretty bad with the 1GB nics. minimum you need to have a cluster_network for all the ceph replication traffic19:14
vhosakotyeah, I'd cards faster than 1G19:14
jamesbensonthe 410's cant have a 10g card in them... but we could wire up a 3rd port for ceph19:14
SamYaplewith that collection of different disks and networking as it is, i would recommend running as many osds as possible19:14
SamYapleon as many different boxes19:15
*** blallau has joined #openstack-kolla19:15
jamesbensonwe have 10g cards, just can't insert them in... no space..19:15
SamYaplejamesbenson: thats _really_ going to hurt you19:15
vhosakotjamesbenson: you can google "Walmart OpenStack architecture"... I remember they showed great topo's in one of their talks at OpenStack summits.19:16
*** blallau has quit IRC19:16
*** rhallisey is now known as rhallisey-biab19:16
*** Mannheim has quit IRC19:17
vhosakotfrankly, OpenSTack has a very simple topology requirement, and that is what I love about it :)19:17
jamesbensonyeah, I/we know the lack of 10g isn't good... hoping to eventually move the 410's to a different area but budgets are no capable of that atm19:17
jamesbensondefinitely vhosakot, just trying to find optimal :-).19:18
vhosakotjamesbenson: the most I"ve seen is like api network, management network, neutron network (provider network, tenant network), storage network, some OOB network, all boxes uplinked to redundant TOR box in VPC.19:19
jamesbensonand we always used mirantis before, so it was a simple, select your controller, compute, storage and go....19:19
vhosakotyou can get experimental near/in the TOR area like adding FEX, Fabric Interconnects, Cisco VTS/ACI, etc etc19:20
jamesbensonwe've got juniper switches here... I'll have to check if they have anything like that but I've never heard of this before :-/19:22
*** ducttape_ has quit IRC19:23
*** ducttape_ has joined #openstack-kolla19:23
vhosakotjamesbenson: actually, simple dual TOR'ing works great for OpenSTack IMO.19:24
manheimhttp://paste.openstack.org/show/614958/19:28
manheimmy neutron metadata agent is in error19:29
manheimeverything else works19:29
manheimhave you seen this before?19:29
*** omenvl has joined #openstack-kolla19:33
*** kristian__ has joined #openstack-kolla19:34
*** gfidente is now known as gfidente|afk19:36
SamYaplemanheim: yea19:36
SamYaplekeystone issues *maybe*, more likely is misconfiguration of neutron19:37
SamYapleor the vip19:37
*** prateek has quit IRC19:38
*** daidv has quit IRC19:38
*** hieulq has quit IRC19:38
*** duonghq has quit IRC19:38
*** kristian__ has quit IRC19:39
manheimok19:40
*** kristian__ has joined #openstack-kolla19:45
*** trozet has quit IRC19:51
*** kristian__ has quit IRC19:52
*** kristian__ has joined #openstack-kolla20:01
*** trozet has joined #openstack-kolla20:04
*** jtriley has quit IRC20:07
*** goldyfruit1 has quit IRC20:07
vhosakotI'll tell you an openstack joke, but you'll have to build all the missing parts yourself to make it funny.20:13
kfox1111indeed.20:15
*** lpetrut has quit IRC20:17
rwellumvhosakot: inc0 - made small corrections to the abstract20:19
vhosakotrwellum: cool20:19
rwellumsbezverk - you can see the neutron-openvswitch container crashing. https://www.irccloud.com/pastebin/GqFo8JZR/20:20
*** tonanhngo has quit IRC20:27
*** manheim has quit IRC20:28
*** manheim has joined #openstack-kolla20:28
*** rhallisey has joined #openstack-kolla20:30
*** ducttape_ has quit IRC20:31
*** tonanhngo has joined #openstack-kolla20:31
*** manheim has quit IRC20:33
*** ducttape_ has joined #openstack-kolla20:34
*** tonanhngo has quit IRC20:35
*** tonanhngo has joined #openstack-kolla20:35
*** vhosakot has quit IRC20:37
*** vhosakot has joined #openstack-kolla20:37
*** ansmith has quit IRC20:38
*** goldyfruit has joined #openstack-kolla20:40
*** tonanhngo has quit IRC20:40
vhosakotinc0: I'm creating an etherpad for the upgrade talk.  Will send it once it is done.  will need feedback from you and duong.20:40
*** lpetrut has joined #openstack-kolla20:40
*** tonanhngo has joined #openstack-kolla20:42
*** manheim has joined #openstack-kolla20:43
*** Mannheim has joined #openstack-kolla20:44
*** tonanhngo has quit IRC20:46
Mannheimis there a known issue with the metadata service in stable/ocata? 4.0.0 ubuntu source20:46
*** lpetrut has quit IRC20:47
*** tonanhngo has joined #openstack-kolla20:54
*** lpetrut has joined #openstack-kolla20:54
*** jtriley has joined #openstack-kolla20:55
vhosakotMannheim: I see the the ocata gate is broken https://review.openstack.org/#/c/474173/20:56
vhosakotinc0: is this due to the ZUUL network traffic issue?20:57
*** tonanhngo has quit IRC20:58
vhosakotno jobs running in http://zuul.openstack.org20:58
sbezverkrwellum : try to get kubectl logs neutron-openvswitch-agent-network-5jjpv -n kolla20:59
*** tonanhngo has joined #openstack-kolla21:00
jascott1sbezverk have you run into the 'helm delete hangs' issue?21:01
sbezverkjascott1 I noticed when daemonset's pod is crashing sometimes helm delete takes very very long time but it kills it finally21:02
sbezverknever seen forever hang scenario21:02
kfox1111I personally haven't, but I have a co-worker who has.21:02
kfox1111I have seen daemonsets fail to delete nicely when a node's down though.21:02
sbezverkwith earlier k8s version I hit kubectl issue when it was hanging forever deleting something21:03
jascott1earlier==?21:03
sbezverkthe only workaround was to ctrlC and then manually delete from etcd21:03
sbezverk1.4.X21:04
jascott1well for helm, restarting tiller pod fixes it temporarily (so it seems)21:04
jascott1k thanks21:04
*** tonanhngo has quit IRC21:04
sbezverkcool, will keep an eye on it21:04
kfox1111the tiller hang my co-worker reported was with 1.6.x21:04
jascott1ya ive still got 1.621:05
jascott1and helm 2.521:05
jascott1its getting to be a problem https://github.com/kubernetes/helm/issues/256021:05
inc0yeah, but I think if you hit recheck it should be better now21:05
sbezverkkfox1111: was he deleting something special ;) ??21:05
inc0or not21:05
*** jtriley has quit IRC21:06
sbezverkinc0: FYI without new target image I will not be able to complete lioadm thing.  please keep that in mind ;)21:07
jascott1i was running tiller local in IDE with debug and eventually it just stops responding. initially I do a `helm delete` and i hit my breakpoint normally but after a few it just stops all together. wont even hit main.init breakpoint21:07
*** jtriley has joined #openstack-kolla21:08
sbezverkjascott1 but tiller should have been still alive, otherwise k8s controller probably killed it,no?21:09
vhosakotzuul is coming back up21:09
inc0sbezverk: no worries, I trust you with this one21:10
sbezverkinc0: do not need trust ;), need review :)21:10
jascott1so i killed all the tiller things in the cluser and was just running local. it was still creating pods on my cluster so I know it was working21:11
Mannheimunfortunately I cannot debug the metadata issue atm21:11
*** bmace has quit IRC21:11
*** bmace has joined #openstack-kolla21:12
Mannheimcould it be be a dhcp service issue?21:12
*** jtriley has quit IRC21:14
vhosakotMannheim: docker logs <metadata_container>21:15
Mannheimthe container was ok from docker pov21:16
Mannheimit was running21:16
Mannheimit's true, i did not run that21:16
Mannheimdo you think i could have seen something there?21:17
*** dklyle has joined #openstack-kolla21:18
vhosakotMannheim: you should see neutron-metadataagent's stdout there.  could have errors?21:18
*** david-lyle has quit IRC21:19
*** Teck72 has joined #openstack-kolla21:21
Mannheimunfortunately I do not have access to the env anymore21:22
*** rfxn has joined #openstack-kolla21:23
*** tonanhngo has joined #openstack-kolla21:24
*** Teck7 has quit IRC21:24
*** Teck7 has joined #openstack-kolla21:25
*** Teck72 has quit IRC21:26
*** jtriley has joined #openstack-kolla21:26
*** oanson has quit IRC21:28
*** tonanhngo has quit IRC21:28
*** oanson has joined #openstack-kolla21:29
*** rfxn has quit IRC21:29
*** tonanhngo has joined #openstack-kolla21:32
*** jtriley has quit IRC21:33
*** trozet has quit IRC21:33
*** jtriley has joined #openstack-kolla21:34
jamesbensonto use external ceph in kolla, you need to follow these directions:  https://docs.openstack.org/kolla-ansible/latest/external-ceph-guide.html; question is, those are on the deploy node correct?  The glance-api.conf, ceph.conf, ceph.client.glance.keyring?21:35
*** pc_m has quit IRC21:35
*** mmehan has quit IRC21:35
inc0jamesbenson: these are config overrides21:36
inc0so all on deploy nodes21:36
jamesbensoninc0; so on all of the deployed nodes in the cluster, not the kolla deploy node, right?21:37
*** kristian__ has quit IRC21:38
*** tonanhngo has quit IRC21:38
inc0kolla deploy node21:38
inc0node you run kolla-ansible from21:38
jamesbensonokay,21:38
*** tonanhngo has joined #openstack-kolla21:39
jamesbensonokay, just wanted to make sure, because the  config dir doesn't exist.... so I'll have to make this pathway then.21:39
*** tonanhngo has quit IRC21:43
jamesbensonwhen I made the ceph cluster, it never spit out a glance keyring, where do you get the key from?21:45
*** pc_m has joined #openstack-kolla21:48
*** jamesbenson has quit IRC21:51
*** iniazi has joined #openstack-kolla21:51
*** jtriley has quit IRC21:52
*** jamesbenson has joined #openstack-kolla21:53
*** daidv has joined #openstack-kolla21:53
Reepicheepjamesbenson: did you use a tool to create your ceph cluster?21:54
*** hieulq has joined #openstack-kolla21:54
SamYaplejamesbenson: you have to create the glance keyring21:54
*** duonghq has joined #openstack-kolla21:55
SamYaplejamesbenson: or, more acurately, a key with access to the glance pool21:55
*** iniazi_ has quit IRC21:55
SamYaplejamesbenson: technically you can just use the admin key if you update the client name and such21:55
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169021:56
*** Teck72 has joined #openstack-kolla21:56
Reepicheepjamesbenson: yeah the point is that more then likely an external tool is not responsible to connect it to glance21:56
*** jascott1 has quit IRC21:56
*** jascott1 has joined #openstack-kolla21:56
*** tonanhngo has joined #openstack-kolla21:57
*** jamesbenson has quit IRC21:58
*** duonghq has quit IRC21:58
*** jascott1 has quit IRC21:58
*** lpetrut has quit IRC21:58
*** jascott1 has joined #openstack-kolla21:58
*** Teck7 has quit IRC21:59
*** jascott1 has quit IRC22:00
*** tonanhngo has quit IRC22:01
*** jascott1 has joined #openstack-kolla22:01
*** tonanhngo has joined #openstack-kolla22:02
*** jascott1 has quit IRC22:03
*** jascott1_ has joined #openstack-kolla22:03
Mannheimi was looking on how the volumes are mounted for the nova services and i found this "/run/:/run/:shared"22:06
Mannheimwhat does share mean exactly? i mean it's not shared by default?22:06
kfox1111its a mount namespace flag.22:07
kfox1111by default a mount copied in only affects the one volume and submounts/events are not propigated.22:07
*** tonanhngo has quit IRC22:07
kfox1111so, /run on the host would be /run in the container normally, but22:08
*** jascott1_ has quit IRC22:08
kfox1111if the user mounted /dev/cdrom to /run/mycd, it would be on the host, but not in the container.22:08
*** jtriley has joined #openstack-kolla22:08
kfox1111shared syncs mount events from the host <->container both ways.22:08
kfox1111so the container would see /run/mycd/*.22:08
kfox1111and could further change it like unmount it, and the host would see it unmounted too.22:08
kfox1111slave is a different argment that is host -> container only.22:09
kfox1111so the container would see mounts, but the container unmounting something wouldn't show up on the host.22:09
*** daidv has quit IRC22:12
*** hieulq has quit IRC22:12
*** schwicht has quit IRC22:12
*** jtriley has quit IRC22:13
*** Teck7 has joined #openstack-kolla22:14
*** Teck72 has quit IRC22:15
Mannheimmakes perfect sense, thank you22:17
*** duonghq has joined #openstack-kolla22:18
*** gfidente|afk has quit IRC22:19
*** deep-book-gk_ has joined #openstack-kolla22:20
*** deep-book-gk_ has left #openstack-kolla22:20
*** tonanhngo has joined #openstack-kolla22:20
*** shardy has quit IRC22:22
*** Teck72 has joined #openstack-kolla22:23
*** tonanhngo has quit IRC22:25
*** Teck7 has quit IRC22:26
*** jtriley has joined #openstack-kolla22:26
*** Teck7 has joined #openstack-kolla22:27
*** daidv has joined #openstack-kolla22:27
*** hieulq has joined #openstack-kolla22:27
SamYaplekfox1111: container unmounting sometihng in a shared mount namespace will absolutely affect the host22:28
*** Teck72 has quit IRC22:28
*** schwicht has joined #openstack-kolla22:28
SamYaplekfox1111: otherwise the host would have lots of neutron network namespaces that never unmount22:29
*** manheim has quit IRC22:29
SamYaplekfox1111: oh sorry. my buffer is all messed up. i see you said just that22:31
*** Mannheim has quit IRC22:32
*** tonanhngo has joined #openstack-kolla22:32
*** manheim has joined #openstack-kolla22:33
*** ducttape_ has quit IRC22:37
*** tonanhngo has quit IRC22:37
*** manheim has quit IRC22:37
*** jascott1 has joined #openstack-kolla22:38
jascott1i messed my buffer up in '9522:38
*** manheim has joined #openstack-kolla22:39
*** ducttape_ has joined #openstack-kolla22:45
*** ducttape_ has quit IRC22:50
*** schwicht has quit IRC23:07
*** ducttape_ has joined #openstack-kolla23:12
*** Teck72 has joined #openstack-kolla23:16
*** Teck7 has quit IRC23:19
*** rhallisey has quit IRC23:20
*** ducttape_ has quit IRC23:20
*** manheim has quit IRC23:26
*** hongbin has quit IRC23:42
*** goldyfruit has quit IRC23:45
*** caowei has joined #openstack-kolla23:55
*** oanson has quit IRC23:59
*** jtriley has quit IRC23:59

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