Wednesday, 2017-05-31

*** gouthamr has joined #openstack-kuryr00:10
*** salv-orlando has joined #openstack-kuryr00:15
*** gouthamr has quit IRC00:16
*** salv-orlando has quit IRC00:19
*** neiljerram has quit IRC00:27
*** feisky has joined #openstack-kuryr00:31
*** c00281451_ has quit IRC00:45
*** c00281451_ has joined #openstack-kuryr00:45
*** gouthamr has joined #openstack-kuryr01:12
*** yedongcan has joined #openstack-kuryr01:34
*** hongbin has quit IRC01:51
*** salv-orlando has joined #openstack-kuryr02:15
*** salv-orlando has quit IRC02:20
*** janki has joined #openstack-kuryr03:37
*** salv-orlando has joined #openstack-kuryr03:50
*** salv-orlando has quit IRC03:54
*** yamamoto has joined #openstack-kuryr04:13
*** aojea has joined #openstack-kuryr04:18
*** hongbin has joined #openstack-kuryr04:21
*** aojea has quit IRC04:22
*** salv-orlando has joined #openstack-kuryr04:39
*** gouthamr has quit IRC04:51
*** hongbin has quit IRC04:57
openstackgerritFrederick F. Kautz IV proposed openstack/kuryr-kubernetes master: Add support for USE_SCREEN and default to screen if USE_SYSTEMD is not set  https://review.openstack.org/46928004:58
*** xiangxinyong is now known as edison06:08
*** edison is now known as edisonxiang06:08
*** yamamoto has quit IRC06:30
*** ltomasbo|away is now known as ltomasbo06:41
*** atoth has quit IRC06:41
*** atoth has joined #openstack-kuryr06:42
*** yedongcan has quit IRC07:00
*** yedongcan has joined #openstack-kuryr07:08
*** dimak_ has joined #openstack-kuryr07:09
*** yamamoto has joined #openstack-kuryr07:13
*** neiljerram has joined #openstack-kuryr07:22
*** pcaruana has joined #openstack-kuryr07:26
*** aojea has joined #openstack-kuryr07:26
*** salv-orl_ has joined #openstack-kuryr07:27
*** salv-orlando has quit IRC07:30
*** dimak_ has quit IRC07:40
*** egonzalez has joined #openstack-kuryr07:44
*** kzaitsev_ws has joined #openstack-kuryr08:02
*** garyloug_ has joined #openstack-kuryr08:49
*** yedongcan has left #openstack-kuryr08:50
*** dmellado_ has joined #openstack-kuryr09:00
*** dmellado has quit IRC09:01
*** limao has joined #openstack-kuryr09:03
apuimedokzaitsev_ws: A day late, sorry. But the "Unexpected command output Device "eth0" does not exist" is usually just a race between kubelet and docker for checking devices. It is not really an error and can happen without any adverse effects09:05
dmellado_apuimedo: o/09:08
dmellado_do you folks know where does our devstack plugin puts the kube/config file?09:11
kzaitsev_wsapuimedo: yeah. I had to recheck every step of the flow. it seems the problem was in ovs-agent<->neutron communication in the end.09:14
kzaitsev_wsat least the problem went away after I restarted those & the rabbit09:14
apuimedodmellado_: it doesn't put it09:17
apuimedoit's hardcoded from the kubectl client we use09:17
apuimedo(extracted from hyperkube)09:18
dmellado_hmmm I see09:18
apuimedodmellado_: but you can pass kubectl --config09:18
apuimedoiirc09:18
dmellado_apuimedo: I was trying to have the python kubernetes client load them09:18
apuimedokzaitsev_ws: so long story short. You can pretty much always ignore the stupid eth0 can't be found09:18
dmellado_in order to setup the client base class09:18
apuimedoI think in 1.7 it's just a warning09:18
apuimedodmellado_: nah, nah09:19
apuimedowe can just configure the client with the snippet I passed you09:19
apuimedodo you still have it?09:19
dmellado_apuimedo: it could've been lost in time09:19
apuimedodmellado_: either that, or we generate a config in /opt/stack/.kube/config09:20
dmellado_just like the teenage mutant ninja turtles09:20
apuimedoand then generate it09:20
dmellado_I was thinking about config.load_kube_config()09:20
apuimedosorry, and then use it for both09:20
apuimedodmellado_: you lazy man09:20
apuimedoxD09:20
dmellado_yeah, I am xD09:20
apuimedook, so let's generate the config then09:20
apuimedoone sec09:20
kzaitsev_wsapuimedo: true =)09:21
kzaitsev_wsit was just a symptom of smth different09:22
kzaitsev_wsjanonymous: what did you mean by "Reference should be [1]..etc currently #" I actually copied the approach from some other spec. Can convert it to more link-friendly, just gotta lookup how that's done09:28
kzaitsev_wsah, you probably meant the list in the end09:28
janonymousyup09:28
janonymouskzaitsev_ws: it has hashes instead of numbers09:28
kzaitsev_wswell, they're translated into numbered list =)09:29
kzaitsev_wsthe hashes I mean09:29
*** limao has quit IRC09:29
janonymousohh cool, didn't knew that :D09:30
kzaitsev_wsI think there should be some syntax in rst to make it more friendly. currently [1]... are not even links. should be smth wiki-like09:30
apuimedodmellado_: I'll send the patch now09:30
dmellado_apuimedo: ack09:30
apuimedoI was just trying it out09:31
kzaitsev_wsah, footnotes they're called09:31
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: devstack: Generate kubeconfig for kubectl and test  https://review.openstack.org/46940009:45
apuimedodmellado_: ^^09:45
apuimedovikasc: ping09:45
vikascapuimedo, pong09:46
dmellado_apuimedo: got it09:46
*** dmellado_ is now known as dmellado09:46
apuimedodid you finally get to review those patches I asked you on monday?09:46
apuimedoI'd like to start merging stuff before they get stale09:46
dmelladoapuimedo: now I need to struggle on how to mix the k8s client with the tempest plugin structure09:46
apuimedohttps://review.openstack.org/#/c/468100/ was one of them09:46
dmelladoI might go a bit off in this case to have at least a working test09:47
apuimedodmellado: why?09:47
apuimedoDo you really need to wrap it?09:47
dmelladoapuimedo: because the way a service client is defined in tempest09:47
apuimedoCan't you have the base class create the CoreV1Api object09:47
dmelladoI might create a class with some methods already defined09:47
apuimedoput it in self.api09:47
apuimedoand then just use api.foo09:47
dmelladoi.e KubernetesClient09:47
apuimedofrom tests09:47
vikascapuimedo, i am sorry , got caught up in another high priority internal work item.09:47
dmelladothen def create_pod(foo)09:47
dmelladoand so09:47
vikascapuimedo, i will do it today for sure09:48
dmelladoapuimedo: that'd be the fastest path09:48
apuimedodmellado: which?09:48
dmelladoso I might go for 'functionality first'09:48
dmelladothen 'make it nice' second09:48
dmelladojust like 'america first' but in the test case09:48
dmelladoxD09:48
dmelladoimporting it directly09:48
apuimedovikasc: can I help you somehow so we get it in the next hour or so?09:48
apuimedo(before lunch in my case :P )09:48
apuimedodmellado: test first09:48
apuimedokzaitsev_ws: please, review https://review.openstack.org/#/c/468962/09:49
apuimedogaryloug_: ping09:49
kzaitsev_wsapuimedo: it should work )09:50
kzaitsev_wsthey actually have -f shell, but I'm not sure if I like it more09:50
vikascapuimedo, thanks , i will let you know if i need help.09:51
apuimedoip -4 r add garyloug_ via mchiappero09:51
apuimedomchiappero: ping09:51
apuimedo:-)09:51
kzaitsev_wsit gives smth-like "cidr=value" for -c cidr09:51
apuimedovikasc: ok09:51
garyloug_apuimedo, hi09:51
apuimedogaryloug_: :-)09:51
apuimedogaryloug_: can you give me some insight into the issues you were experiencing that caused you to w-1?09:52
apuimedokzaitsev_ws: I don't like -f shell09:52
apuimedo:-)09:52
dmellado(all-plugin) [fedora@devstackrdo  tempest(master)]$ tempest list-plugins09:52
dmellado+---------------------+--------------------------------------------------------------+09:52
dmellado|         Name        |                          EntryPoint                          |09:52
apuimedoit's lazy programming09:52
dmellado+---------------------+--------------------------------------------------------------+09:52
dmellado|    keystone_tests   |     keystone_tempest_plugin.plugin:KeystoneTempestPlugin     |09:52
dmellado|     cinder_tests    |       cinder.tests.tempest.plugin:CinderTempestPlugin        |09:52
dmellado|    neutron_tests    |      neutron.tests.tempest.plugin:NeutronTempestPlugin       |09:52
dmellado|    neutron_lbaas    | neutron_lbaas.tests.tempest.plugin:NeutronLbaasTempestPlugin |09:52
dmellado| kuryr_tempest_tests |        kuryr_tempest_plugin.plugin:KuryrTempestPlugin        |09:52
dmellado+---------------------+--------------------------------------------------------------+09:52
dmellado\o/09:52
dmelladonow let's add the dreaded test09:52
kzaitsev_wsme to )09:52
apuimedodmellado: does that mean that to run our tests first it will run all the other tests or just that it loads the plugin in case we want to check stuff created on those?09:53
apuimedobtw, you can take cinder out of the list09:53
apuimedowe ignore it until fuxi-k8s is a thing09:53
dmelladoapuimedo: that just means that it loads the entry point from our plugin09:54
dmelladoalongside any another plugins that might be installed there09:54
apuimedook09:54
apuimedodmellado: the good thing is that this approach and using the k8s client should work for both k8s and any downstream like openshift09:55
apuimedo(even for downstream only objects)09:55
dmelladoapuimedo: yeah, that's my idea09:55
openstackgerritJaivish Kothari(janonymous) proposed openstack/kuryr-kubernetes master: [WIP]Kubernetes client usage from upstream Changed: - watch draft - configuration draft - unicode data/type change  https://review.openstack.org/45455509:56
apuimedodmellado: can I get a nice +1 :-) https://review.openstack.org/#/c/469400/09:56
apuimedo?09:56
dmelladooh, do you deserve it?09:57
dmelladoxD09:57
dmelladobtw, when will you be heading off to IL?09:57
openstackgerritJaivish Kothari(janonymous) proposed openstack/kuryr-kubernetes master: [WIP]Kubernetes client usage from upstream  https://review.openstack.org/45455509:57
apuimedoSunday 00:05 IIRC10:00
dmelladoouch10:02
dmelladothat looks late10:02
apuimedodmellado: indeed10:06
apuimedored eye flight10:06
janonymousivc_: i pushed a draft of change #45455510:06
apuimedoit's the best I could get to go there, speak and go back home10:06
apuimedothanks janonymous!10:06
apuimedoI'll review right away10:06
janonymous:D Heh..10:06
janonymousnot with red eyes :P10:06
janonymousapuimdeo: i had some questions with ivc_, so uploaded a very drft version to get comments10:07
apuimedojanonymous: yes. I read your exchange with ivc_ this morning10:08
janonymousapuimedo: would you have a link of that presentation too?10:10
*** feisky has quit IRC10:11
apuimedojanonymous: which presentation?10:11
janonymousapuimedo: IL one i guess10:11
vikascapuimedo, changes look goog to me, https://review.openstack.org/#/c/468100/310:12
vikascapuimedo, should we update sample localrc also?10:12
ltomasboapuimedo, I tested again the devstack-heat patch, and it works10:12
apuimedojanonymous: yes. As soon as irenab and I deliver it I'll put it on slideshare10:12
apuimedothe video I don't know when it will be posted10:12
janonymousapuimedo: Cool! :)10:13
ltomasboapuimedo, I even use it to deploy your infra k8s API patch too, and it created the lbaas without any problem10:13
apuimedovikasc: we should only update the undercloud/overcloud ones10:13
apuimedoI'll do it in a follow-up patch10:13
apuimedoso that when people use overcloud, they don't add the kubelet ifaces10:14
apuimedoltomasbo: I really want to merge that too10:14
apuimedobut there's no +2s to that10:14
vikascapuimedo, cool10:14
apuimedoI'm considering that since it is contrib. I'll just merge it10:14
apuimedo(referring to devstack-heat)10:14
apuimedovikasc: https://review.openstack.org/#/c/467241/ would be very useful to get merged too?10:20
apuimedos/?//10:20
vikascapuimedo, reviewing it10:24
openstackgerritMerged openstack/kuryr-kubernetes master: devstack: Add configuration for kubelet probes  https://review.openstack.org/46810010:29
openstackgerritMerged openstack/kuryr-kubernetes master: contrib: Add devstack-heat  https://review.openstack.org/46629110:29
*** atoth has quit IRC10:38
dmelladoapuimedo: it feels good when dependant patches gets merged so soon xD10:46
*** salv-orl_ has quit IRC10:59
*** yamamoto has quit IRC11:02
*** rwallner has joined #openstack-kuryr11:23
*** atoth has joined #openstack-kuryr11:39
*** rwallner has quit IRC11:40
*** rwallner has joined #openstack-kuryr11:41
*** yamamoto has joined #openstack-kuryr11:43
*** rwallner has quit IRC11:46
*** rwallner has joined #openstack-kuryr11:47
*** janki has quit IRC12:26
*** rwallner has quit IRC12:30
*** rwallner has joined #openstack-kuryr12:31
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Nested vlan vif pool driver extension to precreate reusable subports  https://review.openstack.org/43689412:36
ltomasboapuimedo, I directly included the modifications to take into account irenab's patch about config options13:00
ltomasbothey are moved to the vif_pool driver13:00
*** gouthamr has joined #openstack-kuryr13:18
apuimedoltomasbo: perfect thanks!13:19
apuimedos/perfect /perfect, /13:19
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Add kuryr-sriov spec proposal  https://review.openstack.org/46566113:23
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Nested vlan vif pool driver extension to precreate reusable subports  https://review.openstack.org/43689413:24
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Add kuryr-sriov spec proposal  https://review.openstack.org/46566113:26
*** rwallner has quit IRC13:28
mchiapperoapuimedo: pong13:39
mchiapperoapuimedo: sorry for the delay13:39
mchiapperothe change in the config file on nested is a bit slowing us down13:40
mchiapperowell, actually I'm a bit busy with other stuff at the moment13:40
mchiapperothere is of course a workaround that is ugly. The other options would be to merge the two MACVLAN related patches, or invert their order13:41
mchiapperodid you manage to test is correctly BTW?13:41
openstackgerritOpenStack Proposal Bot proposed openstack/kuryr master: Updated from global requirements  https://review.openstack.org/46210613:46
openstackgerritOpenStack Proposal Bot proposed openstack/kuryr-kubernetes master: Updated from global requirements  https://review.openstack.org/46948913:47
*** rwallner has joined #openstack-kuryr13:52
mchiapperoapuimedo, irenab & co.: what would you do at this stage? In theory it would be better to refactor the hierarchy of driver first and add macvlan later. Or merge into a single change. But it's another round of reviews14:00
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Add kuryr-sriov spec proposal  https://review.openstack.org/46566114:01
*** salv-orlando has joined #openstack-kuryr14:10
*** dell has joined #openstack-kuryr14:13
dmelladomchiappero: I'd go for the refactor first14:13
dmelladootherwise you may risk getting yourself frustrated by a ton of rebases :\14:13
apuimedomchiappero: I'd rather merge as is if it works14:14
apuimedowe're a bit short handed this week on core reviewers14:15
dmelladoapuimedo: we've a creature to be ramping up14:15
dmelladoxD14:15
dmelladomchiappero: in any case I'll review the patches14:15
apuimedo?14:15
* dmellado isolated himself from anything but reviews tomorrow14:15
apuimedodmellado: no more refactors14:15
apuimedoI want the big patch in finally14:16
dmelladohmmm, let's wait for the reviews xD14:16
apuimedoand then we can clean up14:16
dmelladomchiappero: pls add me to whichever approach you follow in the end and I'll review it ;)14:18
*** hongbin has joined #openstack-kuryr14:25
dellapuimedo:hi, I am zengchen. Several days ago, I committed a path which wanted to add a new sub-project of Fuxi-golang to Kuryr. In the maillist, Spyros said Rexray had integrated Cinder to supply volume for Docker and it is implemented in go language. So Fuxi-golang conflicts with it. What's your opinion about adding Fuxi-golang. Thanks.14:26
*** dell is now known as zengchen14:27
apuimedoHi zengchen! Nice to see you here14:27
zengchenapuimedo:sorry, foget to change my nick name.14:27
zengchenapuimedo:nice to talk to you14:27
apuimedozengchen: can you get me a link to this conflicting cinder golang project?14:27
zengchenapuimedo:ok, wait a moment.14:28
apuimedobrb14:28
zengchenapuimedo:https://github.com/codedellemc/rexray/releases/tag/v0.9.014:28
apuimedozengchen: this is not part of openstack14:29
zengchenapuimedo: yes, it is. but it had finished part of work of Fuxi-golang.14:30
apuimedozengchen: there's also https://github.com/j-griffith/cinder-docker-driver14:30
apuimedoI mean, this rexray is not on big tent or anything14:30
zengchenapuimedo: yes, it is. So you mean Fuxi-golang should be worked on?14:32
zengchenapuimedo: john had implemented the work of converting Cinder to supply volume for Docker. But imo, he will not say no to Fuxi-golang.14:35
zengchenapuimedo:you can see the discussing on the maillist with title of '[openstack-dev] [fuxi][kuryr] Where to commit codes for Fuxi-golang'14:36
hongbinapuimedo: toni, from what i understood, rexray assume you run docker on a nova instance, which is very different from what fuxi is trying to do for the baremetal use cases14:46
hongbinapuimedo: and yes, it is not a openstack project14:46
zengchenhongbin:to my understanding rexray can work on baremetal. you can see the doc on https://github.com/codedellemc/rexray/blob/master/.docs/user-guide/docker-plugins.md14:51
kzaitsev_wsivc_: apuimedo: irenab: I think I'll implement just the tip of multi-vif handler, i.e. being able to work with multiple vifs, but not the exact mechanism for requesting them14:54
kzaitsev_wsexcept for the sriov, where I've defined the mechanism =)14:55
apuimedosorry. I was afk15:02
apuimedozengchen: ^^15:02
zengchenapuimedo::)15:02
apuimedohongbin: zengchen: You both know cinder much better than me15:03
apuimedofrom my limited context, rexray looks like flocker15:04
zengchenapuimedo: yes, flocker is another volume plugin for docker.15:04
apuimedothat also supports cinder15:04
zengchenapuimedo:sorry, i don't know much about flocker. let me check.15:05
apuimedoI am fine if fuxi people decide to just contribute to rexray or flocker instead. As long as fuxi people can implement their use cases, we'll all be happy15:06
apuimedojgriffith: could you weigh in on the above?15:07
zengchenapuimedo: ok. for me i hope fuxi-golang can be implemented.15:09
zengchenapuimedo: thanks very much for your suggestion.15:10
jgriffithapuimedo reading scroll back15:11
apuimedothanks jgriffith15:11
jgriffithOh, the RexRay debate huh?15:11
jgriffithSo that's fine if people go that route, but the reality is as I pointed out on the ML, the fact that it's owned/maintained by Dell/EMC most storage folks aren't going to be contributing to that15:12
jgriffithso that's your trade-off15:12
*** limao has joined #openstack-kuryr15:12
jgriffithalso, I'm frankly not clear why the extra layer of RexRay/Libstorage would be desirable but that's just me15:13
apuimedojgriffith: I lack all the context15:13
jgriffithapuimedo no worries15:13
apuimedoI'm not up to date on storage15:13
apuimedojgriffith: so this project is mostly EMC?15:14
jgriffithapuimedo There's RexRay, Cinder-Docker-Driver, Flocker (RIP), Rancher, and a whole host of other options out there15:14
jgriffithapuimedo not mostly "is"15:14
jgriffithwhich is fine, and they do a fine job15:14
apuimedojgriffith: I was saying mostly in case they got outside contributions15:14
jgriffithbut their goal is also a bit different IMO15:14
jgriffithThey aim to be a Cinder for Containers15:15
jgriffithSo their abstraction is a number of EMC/Dell products (and maybe others), as well as GCE, AWS and OpenStack/Cinder15:15
zengchenjgriffith: yes. totaly agree.15:15
apuimedohow do they differ from the now deceased Flocker?15:15
jgriffithThey don't :)15:15
apuimedobecause it sounds the same to me15:16
jgriffithI mean, in a nut shell15:16
apuimedoit's just a middle layer for any cloud storage15:16
jgriffiththere's a lot of technical differences and implementation differences, but in terms of the goal it's pretty similar15:16
jgriffithapuimedo cloud or bare-metal15:16
*** limao_ has joined #openstack-kuryr15:16
apuimedoright15:16
jgriffithapuimedo but it also doesn't have support for things like stand-alone cinder etc15:17
*** limao has quit IRC15:17
jgriffithit's cloud-provider or not cloud-provider15:17
apuimedoI jgriffith: I don't think products with so many backends can be expected to give the most of cinder15:17
jgriffithanyway, the biggest detractors IMO are:15:17
jgriffith1.  The limited nature of building a community around it15:18
jgriffith2. The architecture of abstractions on top of abstractions15:18
jgriffithapuimedo yeah, I think they do a fine job, but I think it's much more than what we'd need15:18
jgriffithapuimedo honestly the Docker interface impl is quite simple15:19
jgriffithand these days not so interesting15:19
jgriffithwhat's more interesting to folks is orchestrators like K8's or even Habitat at some point15:19
jgriffithand of course you can use the docker volume api's in Swarm and even DCOS contexts15:19
jgriffithanyway... I'm rambling :)15:20
apuimedofrom my perspective, which lacks any enterprise ambition, what I'd like is to follow the same path we hvae with kuryr15:20
apuimedoone simple but powerful docker driver15:20
apuimedothen a good k8s integration15:20
jgriffithYeah, I would really like ot be vendor agnositc15:20
apuimedo(both efforts unrelated)15:20
jgriffithand honestly the K8's component can be obtained upstream anyway15:20
jgriffithalready a lot of work going on there15:20
apuimedoobviously vendor agnostic15:21
apuimedozengchen: jgriffith: hongbin: I'd go forward with fuxi-golang15:21
apuimedoif there are things that the rexray impl has better, it's apache license 2 as well15:21
zengchenapuimedo: great!15:21
apuimedojust like j-griffith's15:21
apuimedolet's start anew in community15:22
jgriffithapuimedo I think so, honestly it's pretty simple... the missing piece is the connection stuff for stand-alone and that's missing in the alternatives as well15:22
apuimedojgriffith: the brick?15:22
apuimedoos-brick15:22
jgriffithapuimedo yes.. connections outside of a nova context15:22
apuimedoright15:23
apuimedozengchen: hongbin: jgriffith: One thing we didn't talk through for fuxi-golang is the core team15:23
zengchenapuimedo: jgriffith: hongbin said he will work on os-brick to reimplement it in go language.15:23
apuimedoI see that in the submission it has a different core team than fuxi15:23
apuimedothat is fine for me15:23
apuimedozengchen: but I wouldn't like the core team to be single vendor15:24
zengchenapuimedo: we can change it to fuxi core team.15:24
apuimedojgriffith should be in both fuxi-golang and the os-brick golang subprojects15:24
apuimedozengchen: I don't mind about that15:24
apuimedobut make sure that all the parties have somebody from the start15:25
apuimedootherwise this is just going to be a Huawei thing15:25
jgriffithapuimedo agreed15:25
hongbinapuimedo: i have no problem of that15:25
jgriffithapuimedo I plan to participate, I think others will as well15:25
zengchenapuimedo: agree15:25
jgriffithCinder folks that is15:25
apuimedojgriffith: if you have some other candidate for core, I think starting with 3-4 cores would be ideal15:26
apuimedoI assume hongbin will be a core too15:26
jgriffithapuimedo let me bring it up at cinder meeting and see if there some folks interested15:26
apuimedoI could be if there is really lack of reviewers, but I'm quite busy as it is15:26
*** kzaitsev_ws has quit IRC15:27
apuimedozengchen: hongbin: are you both going to be driving this?15:27
apuimedojgriffith: that sounds good15:27
apuimedootherwise starting projects with lack of cores gets painful in merge times15:27
zengchenapuimedo: i am15:27
hongbinapuimedo: i will drive the core team of gos-brick, i believe zengchen will found the core team of fuxi-go15:27
apuimedohongbin: you should probably get other cores from cinder/manila in gos-brick15:28
apuimedotoo15:28
*** kzaitsev_ws has joined #openstack-kuryr15:28
hongbinapuimedo: sure, i would love to add them if some of them are interested15:28
apuimedojgriffith: when is the next cinder meeting?15:29
apuimedocould you add that to the agenda?15:29
jgriffithtoday15:29
jgriffithyes15:29
apuimedojgriffith: in half an hour, right?15:31
jgriffithYes, agenda item added15:32
apuimedothanks jgriffith15:32
hongbinjgriffith: i think we can add the whole cinder core team as a sub-team of gos-brick if they would love to be part of the project15:33
jgriffithhongbin agree15:36
apuimedoagreed15:36
jgriffithhongbin and honestly I think it should have some coupling to the Cinder team regardless15:36
zengchenapuimedo: Fuxi also integrate Manila. so it is better to ask some cores of Manila to join.15:37
hongbinjgriffith: yes, it should, for me, the goal is to hand it to cinder team after it is matured (if they like to take it).15:37
jgriffithhongbin I certainly hope the rest of the team is an interested as I am15:38
hongbinyes :)15:38
apuimedo:-)15:39
hongbinfor fuxi-go, it might belong to a different team, likely to be a kuryr subteam as it is right now15:40
hongbinbut it doesn't matter too much for me15:40
apuimedoit doesn't matter much to me either15:40
apuimedoas long as there's a healthy project in openstack opening the way for cinder and manila to containers15:41
zengchenapuimedo: agree.15:41
zengchenapuimedo: hongbin: jgriffith: i have to leave for sleeping. Thanks very much for your sugestions on Fuxi-golang.15:42
*** rwallner has quit IRC15:42
apuimedoyou're welcome zengchen15:43
apuimedohave a good night15:43
zengchenapuimedo: thanks.15:43
*** rwallner has joined #openstack-kuryr15:43
*** zengchen has quit IRC15:44
jgriffiththank you zengchen!!15:51
*** aojea has quit IRC15:59
*** limao_ has quit IRC16:07
openstackgerritLuis Tomas Bolivar proposed openstack/kuryr-kubernetes master: Nested vlan vif pool driver extension to precreate reusable subports  https://review.openstack.org/43689416:12
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: devstack: Use config file generation  https://review.openstack.org/46955716:21
apuimedodmellado: ^^16:22
*** ltomasbo is now known as ltomasbo|away16:32
openstackgerritOpenStack Proposal Bot proposed openstack/kuryr master: Updated from global requirements  https://review.openstack.org/46210616:37
openstackgerritOpenStack Proposal Bot proposed openstack/kuryr-libnetwork master: Updated from global requirements  https://review.openstack.org/46137616:37
*** rwallner has quit IRC16:38
*** pcaruana has quit IRC16:50
*** rwallner has joined #openstack-kuryr16:55
*** salv-orlando has quit IRC16:55
*** rwallner has quit IRC16:58
*** rwallner has joined #openstack-kuryr17:02
*** egonzalez has quit IRC17:09
*** garyloug_ has quit IRC17:24
*** aojea has joined #openstack-kuryr17:29
*** tonanhngo has joined #openstack-kuryr17:31
*** aojea has quit IRC17:50
*** aojea has joined #openstack-kuryr17:51
*** atoth has quit IRC17:53
*** aojea has quit IRC17:55
*** aojea has joined #openstack-kuryr17:57
*** aojea has quit IRC18:03
*** aojea has joined #openstack-kuryr18:18
*** aojea has quit IRC18:22
*** dimak_ has joined #openstack-kuryr19:01
*** rwallner has quit IRC19:12
*** rwallner has joined #openstack-kuryr19:16
*** rwallner_ has joined #openstack-kuryr19:17
*** rwallner has quit IRC19:21
*** aojea has joined #openstack-kuryr19:28
*** yamamoto has quit IRC19:33
*** dimak_ has quit IRC19:37
*** egonzalez has joined #openstack-kuryr19:45
*** pcaruana has joined #openstack-kuryr19:45
*** rwallner_ has quit IRC19:53
*** salv-orlando has joined #openstack-kuryr20:00
*** pcaruana has quit IRC20:02
*** salv-orlando has quit IRC20:09
*** salv-orlando has joined #openstack-kuryr20:11
*** yamamoto has joined #openstack-kuryr20:33
*** yamamoto has quit IRC20:43
*** pcaruana has joined #openstack-kuryr21:12
*** aojea has quit IRC21:13
*** rwallner has joined #openstack-kuryr21:14
*** salv-orlando has quit IRC21:16
*** rwallner has quit IRC21:18
openstackgerritFrederick F. Kautz IV proposed openstack/kuryr-kubernetes master: Add support for USE_SCREEN and default to screen if USE_SYSTEMD is not set  https://review.openstack.org/46928021:28
*** pcaruana has quit IRC21:29
hongbinjgriffith: apuimedo : john and cinder ptl were added to this group, please feel free to add someone who also interest in this project21:47
hongbinjgriffith: apuimedo https://review.openstack.org/#/admin/groups/1781,members21:47
openstackgerritFrederick F. Kautz IV proposed openstack/kuryr-kubernetes master: Add support for USE_SCREEN.  https://review.openstack.org/46928022:06
*** neiljerram has quit IRC22:09
*** gouthamr has quit IRC22:20
*** egonzalez has quit IRC22:21
*** limao has joined #openstack-kuryr22:39
*** limao_ has joined #openstack-kuryr22:42
*** limao has quit IRC22:44
*** gouthamr has joined #openstack-kuryr23:11
*** limao_ has quit IRC23:40
*** limao has joined #openstack-kuryr23:44
*** limao has quit IRC23:50

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