Thursday, 2017-06-15

*** aojea has quit IRC00:20
*** aojea has joined #openstack-kuryr00:21
*** limao has joined #openstack-kuryr00:40
*** yedongcan has joined #openstack-kuryr01:48
*** hongbin has joined #openstack-kuryr02:03
*** dougbtv__ has quit IRC02:22
*** aojea has quit IRC02:25
*** aojea has joined #openstack-kuryr02:26
*** vikasc has joined #openstack-kuryr03:12
*** hongbin has quit IRC03:55
*** tonanhngo has joined #openstack-kuryr04:15
*** salv-orlando has joined #openstack-kuryr04:16
*** salv-orlando has quit IRC04:21
*** gouthamr has quit IRC04:24
*** salv-orlando has joined #openstack-kuryr04:28
*** tonanhngo has quit IRC04:37
*** tonanhngo has joined #openstack-kuryr04:41
*** limao has quit IRC04:44
*** tonanhngo_ has joined #openstack-kuryr04:56
*** limao has joined #openstack-kuryr04:58
*** tonanhngo has quit IRC04:59
*** salv-orl_ has joined #openstack-kuryr05:05
*** salv-orlando has quit IRC05:08
*** tonanhngo_ has quit IRC05:17
*** tonanhngo has joined #openstack-kuryr05:18
*** tonanhngo has quit IRC05:23
*** janki has joined #openstack-kuryr05:26
*** salv-orl_ has quit IRC06:02
*** ltomasbo|away is now known as ltomasbo06:13
*** tonanhngo has joined #openstack-kuryr06:28
*** dims has quit IRC06:44
*** dims has joined #openstack-kuryr06:46
*** rwallner has joined #openstack-kuryr06:51
*** rwallner has quit IRC06:55
*** pcaruana has joined #openstack-kuryr06:58
*** roeyc has joined #openstack-kuryr07:06
*** salv-orlando has joined #openstack-kuryr07:12
irenabltomasbo, morning07:15
ltomasboirenab, good morning!07:15
irenabI have a question for running overcloud07:15
irenabsomehow it fails to stack07:15
irenabin plugin.sh prepare_kuberentes_files07:16
ltomasboumm, that is one of the 'recent' additions, right?07:17
ltomasbonot sure I've tried that yet07:18
dmelladoirenab: with which patch are you using it07:18
ltomasbowhat error do you get?07:18
dmelladoit failed to stack for me too, with the PS507:18
dmelladoI'll retry, as it could've been due to rdo cloud misbehaving yesterday07:18
dmelladodns issues07:18
dmelladoirenab: if you experience such issues, please do change dns on your image07:19
ltomasboirenab, did you set up this: KURYR_CONFIGURE_BAREMETAL_KUBELET_IFACE=False07:19
ltomasbonot sure if it is related, but for the overcloud some of the steps need to be skipped07:19
dmelladoltomasbo: interesting, is that on the README?07:21
ltomasbodmellado, yes, it is in the local.conf example for the overcloud07:22
dmelladoltomasbo: btw, how's life back in Madrid07:22
dmelladodid you melt?07:22
ltomasbowaaarrrmmmm07:22
ltomasboalmost!07:22
* dmellado goes back this afternoon and is scared07:22
ltomasboit was hotter here when I arrived yesterday midnight, than the top temperature I got in Stockholm during the 3 days07:23
ltomasboyep, it will be +40 on Saturday...07:23
dmelladoajjjj07:23
*** tonanhngo has quit IRC07:23
apuimedoirenab: I think I fixed that problem in the last patchset07:28
apuimedotry to stack with --override-keystone07:28
dmelladoapuimedo: I'm going to -1 as there are some options in the local.conf that are not explained07:29
apuimedoy=ー( ゚д゚)・∵.07:29
apuimedoyou're killing me07:29
apuimedoxD07:29
*** neiljerram has joined #openstack-kuryr07:30
dmelladoxD07:31
*** ltomasbo is now known as ltomasbo|away07:32
irenabapuimedo, I already have VM deployed. Do you have local.conf of the overcloud to share?07:33
dmelladoirenab: shouldn't that be in the lines of https://review.openstack.org/#/c/472763/7/devstack/local.conf.pod-in-vm.overcloud.sample07:34
dmellado?07:34
apuimedoirenab: well... it is usually better to have ./devstack-overcloud-heat deploy the VM for you07:36
apuimedootherwise you have more manual steps to take07:36
irenabapuimedo, I had to tweek DF to enable communication to VM, since we have some issue to fix with DNAT.07:37
irenabin parallel I am checking your patch on reference ovs07:37
*** egonzalez has joined #openstack-kuryr07:37
apuimedook07:38
apuimedowell, so then the steps are07:38
apuimedocloning devstack and kuryr-kubernetes on the VM07:38
apuimedoget my latest patchset07:38
apuimedoget a keystonerc from the undercloud07:39
apuimedosource it07:39
apuimedoand edit the local.conf that dmellado pointed you to07:39
apuimedo(you should create some nets, subnets and LB resources in the undercloud as well07:39
apuimedo)07:39
apuimedoThere is a good reason I made ./devstack-overcloud-heat. It's a PITA to set this up by hand :P07:40
apuimedoirenab: what kind of tweaks did you do?07:40
apuimedoMaybe I can put them optional in the patch07:40
apuimedoltomasbo|away: ping07:44
apuimedodmellado: how are your viruses?07:45
dmelladoapuimedo: still so-so07:45
apuimedoor rather... Who's winning?07:45
dmelladobetter than yesterday, though07:45
dmelladowe're still in a stalemate07:45
apuimedo:-)07:45
apuimedoI am happy I managed to sleep with the window open07:45
dmelladofrenadol gets me better but gets me really, really sleepy07:45
apuimedothe pollen counts must be lowering07:45
apuimedodmellado: did I tell you how bothering lazy consensus is?07:46
apuimedoI thought we'd already have the tempest repo :/07:46
dmelladoapuimedo: we do07:46
dmelladoI just need to add the gate to kuryr07:46
apuimedobut the patch doesn't have w+107:46
dmelladolol, what happened due to consensus07:47
apuimedodoes it?07:47
dmelladoahhh you mean the governance one07:47
apuimedoyeah07:47
dmelladowell, no worries about it07:47
dmelladothe repo itself it's already up 'n running on the openstack infra07:47
dmelladothe governance thing, well07:47
dmelladotbh idk how long it'd take...07:47
dmelladobut the repo is now here07:48
dmelladohttps://github.com/openstack/kuryr-tempest-plugin07:48
apuimedoit takes a week07:48
apuimedodmellado: irenab: https://hub.docker.com/r/kuryr/controller/07:49
apuimedoI made a new container image (taking over vikasc containerization patch)07:50
dmelladoapuimedo: where are the descriptions? -1 xD07:50
apuimedodmellado: my parser doesn't understand07:50
apuimedodesc... what?07:50
vikascapuimedo, i am just working on that patch to address review comments07:50
dmelladoapuimedo: I see that it was really vikasc patch07:50
dmelladoas I'm still waiting for the documentation xD07:51
apuimedovikasc: I thought you were not working on that one anymore07:51
dmelladothat said, I do also need to edit the docs for the new repo and didn't do that yet07:51
apuimedoI'm working on splitting into two different images07:51
apuimedothe controller one07:51
apuimedorunning as use07:51
vikascapuimedo,  i was about to push07:51
apuimedo*user07:51
apuimedoand the cni one07:51
apuimedothat I still didn't start07:51
apuimedoI also took some measures to reduce the container size07:52
vikascapuimedo, sorry about the delay07:52
apuimedoit would help if you keep us updated07:52
apuimedootherwise I assume that you're busy with other things and take over07:53
vikascapuimedo, IIRC i told you privately07:53
vikascapuimedo, that i will be busy a week or so07:53
dmelladomaybe we could do some kind of quick status on the weekly meeting07:53
vikascapuimedo, can i continue that patch now07:54
vikascapuimedo, or if you want to continue thats also fine with me07:54
*** aojea has joined #openstack-kuryr07:54
apuimedovikasc: please, send what you were about to push07:55
apuimedowe can converge with my changes later07:55
vikascapuimedo, ok, iwas testing again and addressing review comments such as templating variables in config map07:55
vikascapuimedo, you just pushed controller image, right?07:56
*** neiljerram has quit IRC07:57
vikascapuimedo, built with some changes on top of dockerfile in my patch07:57
vikascapuimedo, i am thinking how it would be if i test with the container image that you pushed07:57
vikascapuimedo, rather building local docker image and adapt my patch to this image which you pushed. WDYT?07:58
vikascapuimedo, its just two week old patch man, you taking over without notifying :)07:59
apuimedovikasc: yes. It's in the kuryr organization on docker hub07:59
vikascapuimedo, cool07:59
apuimedovikasc: well. You'd need to make a change to the deployment07:59
apuimedoso that the sections are mounted in /etc/kuryr/08:00
apuimedoI'm not using the bash file for startup08:00
apuimedoI changed the configmap and mounts so that we have08:00
vikascapuimedo,  where is the dockerfile for this image08:00
apuimedo /etc/kuryr/neutron.conf /etc/kuryr/neutron_defaults.conf08:00
vikascapuimedo, which  you created08:00
apuimedo(from your sections)08:00
vikascapuimedo, so that i can understand08:00
*** neiljerram has joined #openstack-kuryr08:01
apuimedoI'll send the patchset with a different changeid so you can see08:01
vikascapuimedo, cool08:01
*** aojea has quit IRC08:01
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: Add support to install Kuryr as a network addon  https://review.openstack.org/47447808:01
vikascapuimedo, i would like to continue my patch08:15
vikascapuimedo, i dont think i delayed that long08:15
apuimedovikasc: please continue08:16
vikascapuimedo, i worked a lot to figure out things on this patch08:16
*** ltomasbo|away is now known as ltomasbo08:17
vikascapuimedo, thanks08:17
dmelladovikasc: what about the documentation? xD08:22
vikascdmellado, documentation means steps to use it?08:23
apuimedovikasc: how to make the build08:23
apuimedoit should probably have a description of what the kuryr.yml is for (the one you put is for pod-in-vm, for example)08:24
vikascapuimedo, dmellado will add more details to READMe08:24
apuimedovikasc: please, don't forget to take the '.dockerignore' from the patch I sent08:25
vikascapuimedo, sure08:25
apuimedootherwise the image is 1GiB instead of 327MiB08:25
apuimedo(depending on the amount of tox in your system, of course)08:26
apuimedoltomasbo: I checked and in baremetal I didn't experience the failure to delete the ports08:26
irenabapuimedo, I deployed the VM with heat patch, so trunk and all the subnets are defined. The issue was to ssh into this VM08:28
*** garyloug has joined #openstack-kuryr08:29
apuimedoirenab: a problem with the FIP DNAT?08:32
apuimedoirenab: or did it also affect the user_data for the VM ?08:32
irenabyes, with FIP. What do you mean by user_data?08:34
irenabI created local conf like this: https://pastebin.com/1atBxeNy08:35
ltomasboapuimedo, then it could be due to a missing dependency on the kuryr-lib08:40
*** kzaitsev_ws has joined #openstack-kuryr08:40
ltomasboapuimedo, perhaps the call failing is the one releasing the vlan_id08:40
ltomasbothere is one fast thing you can try08:40
ltomasbocomment out this line: https://github.com/openstack/kuryr-kubernetes/blob/master/kuryr_kubernetes/controller/drivers/nested_vlan_vif.py#L10908:41
ltomasboand try again08:41
apuimedoirenab: the thing is that you shouldn't need to create a local.conf08:42
apuimedoif your cloud's metadata works08:42
apuimedoit should already be done in the VM thanks to the user-data I put in the heat template08:42
apuimedoltomasbo: what do you plan on working next?08:43
ltomasboxD08:43
ltomasbotwo follow up patches I'll send later today08:43
apuimedo'bout?08:43
dmelladoabout documentation? xD08:44
ltomasboreadme documentation regarding vif_pool utilization08:44
ltomasboand another one to ensure no leftovers of ports08:44
apuimedodmellado: you keep bringing up these non-existing words08:44
ltomasbowhen kuryr-controller is rebooted08:44
dmelladoapuimedo: but I was right!08:44
dmelladoxD08:44
apuimedomust be some invented word from Madrid08:44
dmelladoyou all know that you can now propose patches to the awesome new repo08:44
dmelladoand yes, that another word is tests!08:45
dmelladoxD08:45
apuimedowe know about tests08:45
apuimedounit tests08:45
dmelladoI'll be putting up the gate as non-voting first08:45
apuimedonext you are going to tell me other kinds of tests exist08:45
dmelladobut be prepared08:45
dmelladomuahahaha08:45
dmelladoxd08:45
kzaitsev_wsdmellado: apuimedo: speaking about docs — would appreciate if you would look at https://review.openstack.org/#/c/472653/ and tell me if it's the good direction =)08:45
apuimedoltomasbo: what is next after that?08:45
ltomasboapuimedo, good question08:45
apuimedo:O08:46
dmelladokzaitsev_ws: will totally do! thanks!08:46
apuimedokzaitsev_ws: you're doing God's work08:46
ltomasbomulti nic support and/or the possibility of using different subnets08:46
dmelladomulti nic/multi cni08:46
apuimedoltomasbo: there's already kzaitsev_ws doing multivif08:46
dmelladowould be nice08:46
* dmellado wonders how rdo cloud dsvm can be sooo slow...08:47
irenabapuimedo, so no local.conf in VM?08:47
apuimedodmellado: it runs on Athlon6408:47
apuimedoirenab: it should already have been created by cloud-init08:47
dmelladoapuimedo: I bet it runs on 486SX208:47
dmelladowithout math co-processor08:47
apuimedodmellado: just in case, ask them if they are using qemu or qemu-kvm08:48
apuimedoxD08:48
dmelladoI'd say than more than 'qemu'08:48
dmelladothey're using 'quemal'08:48
dmelladoxD08:48
apuimedo#dadjokes08:48
dmelladolol08:48
dmelladoxD08:48
apuimedovikasc: did you read the comment I put to my patch?08:49
apuimedoabout using a debian container to build the binary08:49
vikascapuimedo, about cni? yes08:49
apuimedoand then put that binary into the cni container that writes it into the host file system?08:49
apuimedo(just like docker-compose does with their scripts/build/linux08:50
vikascapuimedo, i will get to it, once i have adressed existing review comments and incorporated changes you made in dockerfile08:50
apuimedook08:50
apuimedoof course, that wouldn't be that necessary if we were good folks and had already split CNI08:51
vikascapuimedo, yep08:51
vikascapuimedo because it is working with existing changes, will improve it in steps08:52
vikascapuimedo, i mean cni08:52
*** kzaitsev_ has joined #openstack-kuryr08:53
janonymouskzaitsev_ws: ping08:53
kzaitsev_sry my colleagues dragged me off to lunch08:53
vikascapuimedo, so you want kuryr.conf to get created directly via config map?08:54
kzaitsev_will be back in 15 min :))08:54
dmelladoapuimedo: with your patch, on dsvm08:54
dmelladothe kuryr-kubernetes service is not working for me08:54
dmellado-1 'al canto'08:54
dmelladoxD08:54
apuimedovikasc: no08:55
apuimedowhat my patch does is create a .conf file for each section08:55
apuimedoand place those on /etc/kuryr/08:55
vikascapuimedo, i see that you are passing --config-dir08:55
dmelladolooks like some kind of requirements issue08:55
dmelladoJun 15 08:50:15 devstackrdo.novalocal python[6761]: 2017-06-15 08:50:15.065 6761 ERROR kuryr-kubernetes ImportError: No module named generic_vif08:55
apuimedothen, instead of using --config-file /etc/kuryr/kuryr.conf08:55
apuimedowe just pass --config-dir08:55
apuimedoso all of them will be read by oslo08:55
vikascapuimedo, thats why my kryr.yml also does08:55
vikascs/what08:56
apuimedovikasc: but you do one extra step08:56
apuimedoof putting it in /tmp08:56
apuimedoand then on container start putting it all into a /etc/kuryr/kuryr.conf08:56
apuimedowhich is unnecessary08:56
vikascapuimedo, i was not aware that oslo will read directly08:56
apuimedovikasc: neutron uses --config-dir for some time08:56
vikascapuimedo, and was creating kuryr.conf myself08:56
apuimedodmellado: can I get more details?08:57
dmelladoapuimedo: I'll comment on the review, hold on08:57
vikascapuimedo, cool, so instead of tmp it those sections are to be copied in config-dir08:57
apuimedonot copied08:57
vikascapuimedo, thanks08:57
vikascapuimedo, created08:57
apuimedothey are mounted directly there08:57
vikascapuimedo, yep08:57
ltomasbodmellado, are you deploying with last master patches?08:58
dmelladoltomasbo: yep, just fresh vm08:58
ltomasbothat generic_vif seems to be due to the renaming to neutron_vif08:58
ltomasboperhaps kuryr.conf has the wrong driver then08:59
ltomasbocan you check? if you have something there saying generic_vif?08:59
ltomasbootherwise we may have some leftovers...08:59
dmelladoltomasbo: that could be09:00
dmelladoapuimedo: ltomasbo I put the trace on the commit comments09:01
ltomasbolink?09:01
vikascapuimedo, i will also work on templating config parameters, that are used in config map09:01
dmelladohttps://review.openstack.org/#/c/47276309:02
apuimedodmellado: what command exactly did you use with ./devstack-overcloud-heat ?09:02
dmelladoapuimedo: I didn't even get to that09:03
dmelladojust stacking09:03
apuimedoah... YOu used my patch also for stacking the "undercloud"?09:03
* dmellado is stupid09:03
dmelladogit pull --rebase origin master09:04
dmelladoover your patch09:04
dmelladonvm09:04
dmelladofrenadol--09:04
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: contrib: devstack-overcloud-heat  https://review.openstack.org/47276309:04
*** kzaitsev_ has quit IRC09:05
dmelladoapuimedo: yeah, I had that on the GITREF form kuryr-k8s dsvm plugin09:05
apuimedoah09:10
dmelladoI rebased it09:11
apuimedoI saw09:17
*** dougbtv__ has joined #openstack-kuryr09:22
openstackgerritJaivish Kothari(janonymous) proposed openstack/kuryr-kubernetes master: Stopping Thread from oslo_service  https://review.openstack.org/47451909:32
kzaitsev_wsltomasbo: yeah, I have a small initial patch for the multi-vif. It adds just the ability to handle it, but not the mechanism to request it.09:36
kzaitsev_wsjanonymous: pong =)09:37
ltomasbokzaitsev_ws, nice! I'll take a look!09:39
ltomasbois it this one: https://review.openstack.org/#/c/471012/09:39
kzaitsev_wsltomasbo: yep. I based my sriov patches on top of it09:41
ltomasbogreat! I'll take a look later today09:41
*** limao has quit IRC09:41
ltomasboso, what is missing is the controller-driver side?09:41
ltomasboto requests the cni different vifs?09:41
kzaitsev_wsthnks =)09:42
kzaitsev_wsltomasbo: the mechanism to actually request them09:42
ltomasbook09:42
kzaitsev_wsltomasbo: I mean. for sriov the mechanism is to request opaque-int-resource in k8s09:42
ltomasbohttps://github.com/Huawei-PaaS/CNI-Genie09:42
ltomasboperhaps we can take a look at how they deal with that there, and do something similar09:43
ltomasbofor requesting different vifs09:43
kzaitsev_wsyou say — I want 2 opir physnet3 and vif-handler says — take these 2 direct ports09:43
ltomasbothat in the pod template, right?09:44
ltomasbokzaitsev_ws, ^^09:44
ltomasboso perhaps we can use annotations to specify the pod will use 2 vifs, similarly how they decide to use 2 cnis09:45
kzaitsev_wsltomasbo: cni-genie is probably a dead end. it simply a proxy, that asks several cni drivers for ips.09:45
kzaitsev_wsif we want all the IPs to be managed by kuryr — there's no point in using cni-genie (or multus-cni)09:45
ltomasbokzaitsev_ws, I didn't mean to use it, but to have a similar approach into how to request multiple vifs09:45
kzaitsev_wsI guess they're very similar09:45
apuimedoyes, it should be metadata09:45
apuimedoprobably customresources as well09:46
apuimedobut that comes with 1.7.009:46
apuimedoand there's no fscking documentation on them09:46
ltomasbo:(09:46
kzaitsev_wsltomasbo: yeah. for sriov the pod asks for opaque int resources in the pod spec.09:46
kzaitsev_wsone option would be to request ports by specifying port-id's09:46
ltomasboI was thinking in something like: metadata: annotations: vifs: 209:47
kzaitsev_wsin the annotation09:47
kzaitsev_ws^^ is also an option, yeah.09:48
kzaitsev_wsI specifically left the thing out of scope of https://review.openstack.org/#/c/471012/ patch, because there are several options to do it, while the mechanism to pass from controller to cni and for cni to handle multi-vif annotation doesn't really depend on the way vifs are requested09:49
ltomasbokzaitsev_ws, sounds good!09:50
*** rwallner has joined #openstack-kuryr09:51
kzaitsev_wsltomasbo: the way to request multiple vifs would probably require some discussion and compromises anyway =)09:51
ltomasbokzaitsev_ws, sure!09:51
ltomasbosomething to discuss in a call or during the kuryr weekly IRC meeting09:52
*** rwallner has quit IRC09:56
kzaitsev_wsltomasbo: apuimedo: even for mechanism there is one thing to agree. instead of a list of vifs I pass a dict {ifname:vif}, so it's responsibility of the handler to decide what would be the interface name09:56
kzaitsev_wsthat's not what's described in the bp, but we have discussed that at some point inside sriov spec with ivc_ (his suggestion =)) and I liked it and went with it09:57
kzaitsev_wsanyway =) ltomasbo: would really appreciate if you would take a look at the patch and see if there'09:58
kzaitsev_wsthere's smth to improve there09:58
ltomasbokzaitsev_ws, sure, I'll do it later today10:05
dmelladofolks, I'm hopping to the train to hot city10:06
* dmellado sighs10:06
dmelladottyl!10:06
openstackgerritvikas choudhary proposed openstack/kuryr-kubernetes master: Add support to install Kuryr as a network addon  https://review.openstack.org/46667510:17
apuimedokzaitsev_ws: I'm a bit surprised by having a dict instead of list10:18
apuimedobut it makes sense10:18
apuimedoI haven't fully thought this through10:18
vikascapuimedo, irenab kzaitsev_pi ^10:18
apuimedothanks vikasc10:18
vikascapuimedo, yw! i will now work to complete what you said about cni build10:19
apuimedothanks10:22
vikascirenab, kzaitsev_pi : i did not change configmap to template the variables because i am not sure exactly what is your expectation by that. is that for each kuryr.conf section, we should have a template/sample file in kuryr-kubernetes/ and then those should be read in configmap?10:23
apuimedovikasc: I don't think it should be templated10:23
vikascinstead of directly changing configmap in yaml10:23
apuimedothere should just be a README explaining which values should be changed10:23
apuimedoand with what10:24
vikascapuimedo, i too felt so thats why asking again10:24
janonymouskzaitsev_ws:I think this might be required for the bug : https://review.openstack.org/#/c/474519/ , but have to test locally...10:24
vikascapuimedo, may be we can add tox generated sample kuryr.conf10:24
apuimedovikasc: maybe instead of concrete example values, we can have something like10:24
apuimedomy_subnet_id10:25
apuimedoetc10:25
vikascapuimedo, how about adding tox generated10:25
apuimedovikasc: I'd rather not have the tox generated example10:25
apuimedothe only option I consider is that we'll have a one-off pod that will use neutron to create the resources if there is no config map10:25
apuimedocreate the config map10:25
apuimedoand that will retrigger the controller deployment10:26
mchiapperohi guys10:26
apuimedobut we can leave this improvement for later10:26
apuimedomchiappero: Hi!10:26
mchiapperoI'm afraid unstack.sh in many cases doesn't correctly clean up the load balancer10:26
mchiapperoapuimedo: hi! :)10:26
vikascapuimedo, cool10:27
apuimedomchiappero: interesting10:27
vikascapuimedo, let me figure out cni part, will get back if face confusion10:27
apuimedoplease. Report a bug and assign it to me10:27
mchiapperoI have to say I'm stacking and unstacking very often..10:27
apuimedomchiappero: no excuse for not cleaning up10:27
mchiapperoI'll try to see if I find a consistent way to reproduce10:27
apuimedosame I tell my son after lego10:27
mchiapperolol10:28
mchiapperotoday I'm busy but tomorrow I should be able to continue on macvlan and investigate this10:28
*** irena has joined #openstack-kuryr10:30
apuimedoperfect10:31
apuimedothanks mchiappero10:31
kzaitsev_wsfolks also a small heads up — I'll be travelling next week. I'll try my best to attend the weekly meeting, but I might have limited connectivity10:38
kzaitsev_wsjanonymous: yeah, I'll try to test it too ) just need to restore sonme of my devstacks =)10:39
apuimedothanks for the heads up kzaitsev_ws10:43
kzaitsev_wsapuimedo: about the dict — it potentially gives us more power (i.e. user will be able to request vifs with specific names). And in the end either CNI or the handler would have to decide ifnames anyway. However I might be missing smth, so yeah this needs to be thought through10:45
irenabapuimedo, let me know if you need me to host next weekly10:49
apuimedoI can host Monday 19th, but I'll need you to host Monday 26th10:51
apuimedoI'll be on a plane10:51
irenabok, just let me know10:52
*** salv-orlando has quit IRC10:56
mchiapperoI'm facing a problem10:58
mchiapperoRequiredOptError: value required for option project in group [neutron_defaults]10:58
mchiapperowhen trying to handle load balancer events10:59
mchiapperowhat is the required config option?10:59
mchiapperofrom File "/opt/stack/kuryr-kubernetes/kuryr_kubernetes/controller/drivers/default_project.py", line 51, in get_project10:59
mchiapperofrom File "/opt/stack/kuryr-kubernetes/kuryr_kubernetes/controller/handlers/lbaas.py", line 74, in _generate_lbaas_spec11:00
janonymouskzaitsev_ws: yup, i tried locally and seems to work.11:02
apuimedomchiappero: let me check11:02
apuimedomchiappero: of these, which are you missing11:03
apuimedoproject, pod_subnet, pod_security_groups, service_subnet, ovs_bridge11:04
apuimedothe project one, right?11:04
mchiapperolet me check...11:05
irenaapuimedo, I hit this error in overcloud VM11:06
irena/opt/stack/kuryr-kubernetes/devstack/plugin.sh:prepare_kubernetes_files:393 :   openstack --os-cloud devstack-admin --os-region RegionOne subnet show k8s-service-subnet -c cidr -f value ResourceNotFound: No Subnet found for k8s-service-subnet11:06
openstackgerritYuval Brik proposed openstack/kuryr-kubernetes master: devstack: fix dragonflow gate  https://review.openstack.org/47454411:07
mchiapperooh my... sorry.. i just restacked and my config file has been replaced, it seems11:07
mchiapperobut IIRC it used to preserve pre-existing config files, am I wrong?11:08
apuimedoirena: did you use the --override-keystone?11:11
mchiapperoBTW, another issue I have with devstack is that if docker is already installed and commented unstack will stop it11:11
apuimedomchiappero: which kuryr.conf or local.conf?11:11
mchiapperokuryr.conf11:11
apuimedomchiappero: it probably did preserve before11:12
apuimedobecause it was not using the oslo-generator11:12
apuimedoit was just doing iniset11:12
mchiapperook, wrong assumption on my side then, sorry11:12
apuimedowe added oslo-generator there so that the stacking grabs any new options (and also so it tests that the config generation is not broken)11:12
mchiapperoI see, it's cool actually11:13
irenaapuimedo, I run the overcloud VM on devstack. As you suggested, no local.conf11:13
apuimedogotta go for lunch now11:20
apuimedowill ping you later irena11:20
irenabapuimedo, ok. Its in the poart that was added to enable k8s api service/router11:21
irenabdmellado, does the overcloud VM works for you?11:22
mchiapperoapuimedo: sorted, thanks :)11:24
*** salv-orlando has joined #openstack-kuryr11:34
openstackgerritvikas choudhary proposed openstack/kuryr-kubernetes master: Add support to install Kuryr as a network addon  https://review.openstack.org/46667512:00
*** dougbtv__ has quit IRC12:03
openstackgerritvikas choudhary proposed openstack/kuryr-kubernetes master: Add support to install Kuryr as a network addon  https://review.openstack.org/46667512:06
openstackgerritvikas choudhary proposed openstack/kuryr-kubernetes master: Add support to install Kuryr as a network addon  https://review.openstack.org/46667512:07
apuimedoirenab: the thing is. That part should not run if you called ./devstack-overcloud-heat with --override-keystone flag12:25
*** rwallner has joined #openstack-kuryr12:27
*** rwallner has quit IRC12:28
irenabapuimedo, I didn't since its on devstack.12:35
irenabcurrently I prefer to change settings inside the VM and not to re-run the devstack-overcloud-heat12:36
irenabapuimedo, any advice on this?12:36
apuimedolet's have a call in 30min and check it?12:36
apuimedoor is it too late?12:36
irenabI will need to leave in 20 mins ...12:37
apuimedo:(12:37
apuimedoI'm in a call now12:37
*** atoth has joined #openstack-kuryr12:40
*** edisonxiang has quit IRC12:49
*** rwallner has joined #openstack-kuryr12:53
*** rwallner has quit IRC12:54
*** rwallner has joined #openstack-kuryr12:55
*** irena has quit IRC12:58
*** gouthamr has joined #openstack-kuryr13:12
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Delete or recover precreated ports upon controller restart  https://review.openstack.org/47457613:27
*** yedongcan has quit IRC14:02
*** yedongcan has joined #openstack-kuryr14:03
*** aojea has joined #openstack-kuryr14:06
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Add ports pool configuration information at README  https://review.openstack.org/47458914:09
*** tonanhngo has joined #openstack-kuryr14:11
*** tonanhngo has quit IRC14:15
*** limao has joined #openstack-kuryr14:51
*** roeyc has quit IRC14:52
*** limao_ has joined #openstack-kuryr14:56
*** limao has quit IRC14:56
*** janki has quit IRC15:12
*** hongbin has joined #openstack-kuryr15:28
*** limao_ has quit IRC15:31
*** yedongcan has left #openstack-kuryr15:33
*** aojea has quit IRC15:56
*** egonzalez has quit IRC16:00
*** garyloug has quit IRC16:37
*** ltomasbo is now known as ltomasbo|away16:56
*** neiljerram has quit IRC17:03
*** roeyc has joined #openstack-kuryr17:04
*** salv-orl_ has joined #openstack-kuryr17:14
*** pcaruana has quit IRC17:16
*** salv-orlando has quit IRC17:17
*** kzaitsev_ws has quit IRC17:31
*** roeyc has quit IRC18:59
*** roeyc has joined #openstack-kuryr19:00
*** zengchen has quit IRC19:04
*** zengchen has joined #openstack-kuryr19:04
*** egonzalez has joined #openstack-kuryr19:13
*** roeyc has quit IRC19:16
*** neiljerram has joined #openstack-kuryr20:23
*** rwallner has quit IRC20:28
*** rwallner has joined #openstack-kuryr20:32
*** egonzalez has quit IRC20:35
*** rwallner has quit IRC20:51
*** oanson has quit IRC21:23
*** lihi has quit IRC21:23
*** gouthamr has quit IRC21:23
*** lihi has joined #openstack-kuryr21:25
*** oanson has joined #openstack-kuryr21:26
*** rwallner has joined #openstack-kuryr21:37
*** gouthamr has joined #openstack-kuryr21:42
*** rwallner has quit IRC21:53
*** oanson has quit IRC22:38
*** salv-orl_ has quit IRC22:39
*** oanson has joined #openstack-kuryr22:39
*** neiljerram has quit IRC22:47
*** neiljerram has joined #openstack-kuryr23:06

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