Thursday, 2016-02-04

*** mark_dunn has joined #openstack-kuryr00:01
*** yuanying has quit IRC00:09
*** yuanying has joined #openstack-kuryr00:16
*** yuanying has quit IRC00:19
*** yuanying has joined #openstack-kuryr00:22
*** shashank_hegde has quit IRC01:08
*** yuanying has quit IRC01:11
*** yuanying has joined #openstack-kuryr01:12
*** banix has joined #openstack-kuryr01:12
*** yuanying has quit IRC01:21
*** yuanying has joined #openstack-kuryr01:23
*** banix has quit IRC01:33
*** tfukushima has joined #openstack-kuryr01:40
*** banix has joined #openstack-kuryr02:10
*** tfukushima has quit IRC02:49
*** tfukushima has joined #openstack-kuryr03:01
*** banix has quit IRC03:04
*** yuanying has quit IRC03:15
*** yuanying has joined #openstack-kuryr03:19
*** yuanying has quit IRC03:24
*** yuanying has joined #openstack-kuryr03:35
*** yuanying_ has joined #openstack-kuryr03:41
*** yuanying has quit IRC03:44
*** mark_dunn has quit IRC03:44
*** shashank_hegde has joined #openstack-kuryr03:46
*** salv-orl_ has joined #openstack-kuryr03:54
*** salv-orlando has quit IRC03:58
*** shashank_hegde has quit IRC04:04
*** shashank_hegde has joined #openstack-kuryr04:05
*** yuanying_ has quit IRC04:06
*** yuanying has joined #openstack-kuryr04:07
*** yuanying has quit IRC04:08
*** yuanying has joined #openstack-kuryr04:08
*** shashank_hegde has quit IRC04:14
*** tfukushima has quit IRC04:34
*** shashank_hegde has joined #openstack-kuryr04:44
*** shashank_hegde has quit IRC05:26
*** tfukushima has joined #openstack-kuryr05:34
*** tfukushima has quit IRC05:40
*** tfukushima has joined #openstack-kuryr05:44
irenabbanix: cool!06:03
gsagiesalv-orl_ : do you have any link for the closing announcement ?06:19
gsagiefkautz: ping06:19
fkautzgsagie: pong06:32
gsagiefkautz: salv-orlando mentioned something about us not being able to use K8 watch APIs to read additional information from etcd that is not in the CNI API?06:35
fkautzI'm not sure what info is watchable and what should end up in cni just yet, we should inventory these and work out if anything is missing that we need06:38
fkautzI was told there is some info that is necessary that isn't in the standard cni interface06:39
gsagiewe can also directly watch etcd06:42
gsagieprobably not the best idea, but..06:42
fkautzi would expect that to eventually be locked down if it isn't already06:43
gsagiesounds like they dont really want it to be pluggable06:43
fkautzi think they do, but the interface would be centered around the watch api rather than etcd06:44
gsagieat least from networking stand of point, you want to be able to recieve the services information at least06:44
gsagieok, just was under the impression they are closing the watch api06:44
fkautzyea, i think tailing etcd will likely be restricted06:45
fkautza k8s watch api would allow more fine-grained acls to be implemented06:46
fkautzi don't have all the details yet, so i want to be careful saying this is absolutely the direction it is heading06:47
fkautzi have some confirming and digging to do06:47
fkautzi'll make sure to let you know what i find out and add it to the k8s etherpad06:47
gsagiethanks, do you have any link?06:50
fkautznot yet, this was from conversations i had with a k8s dev06:50
gsagieas long as we have some API to get the additional information its ok06:51
fkautzagreed, it's a question i want to work out early so that we can get the ball rolling on k8s if upstream work needs to be done06:52
fkautzhttps://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/network/cni/cni.go06:57
fkautza quick overview, there are at least three things passed in06:57
fkautzK8S_POD_NAMESPACE, K8S_POD_NAME, K8S_POD_INFRA_CONTAINER_ID06:57
fkautzgsagie: so we'll need to ensure we handle those in addition to the standard CNI interface06:58
gsagiefkautz: yep agreed07:00
gsagiewe talked about this in the meeting yesterday, the additional things we need07:01
gsagiemostly regarding services at first stage, but then also regarding labels/annotations when we want more policy07:01
fkautzgreat :)07:01
fkautzalso, i have time to contribute patches for this feature once we're ready to proceed07:03
gsagiesounds good :)07:03
*** salv-orl_ has quit IRC07:13
openstackgerritLiping Mao proposed openstack/kuryr: The device_id and device_owner of neutron port are null  https://review.openstack.org/27607807:47
*** apuimedo has joined #openstack-kuryr08:23
irenabgsagie: banix: apuimedo : I updated the k8s-kuryr integration blueprint:  https://blueprints.launchpad.net/kuryr/+spec/kuryr-k8s-integration. Please check/fix if I missed anything based on our discussion08:30
apuimedothanks irenab08:31
apuimedoStarting the morning strong!08:31
irenabapuimedo: I planned to finish it yesterday  ….08:32
apuimedoshhhh, it sounds much better "I woke up early to do it" :-)08:32
irenabapuimedo: he he08:41
openstackgerritLiping Mao proposed openstack/kuryr: The device_id and device_owner of neutron port are null  https://review.openstack.org/27607808:48
apuimedogsagie: look at this patch ^^08:52
apuimedo:-)08:52
reedipHey, any help in approval of this patch ? : https://review.openstack.org/#/c/272337/09:01
reedipit is a trivial-fix09:01
irenabreedip: checking09:03
reedipirenab : gr8, thanks :)09:03
irenabreedip: should not it have basepython  defined?09:05
apuimedoirenab: you mean limao should add some rally test?09:05
irenabat least it is defined for neutron09:05
irenabapuimedo: even unit test that verifies that created port has all required fields will be good to catch it later if removed once again09:06
apuimedoirenab: the problem was, I think, that were losing it on update09:06
reedipirenab: I was unable to understand your above comment.... checking the tox.ini for neutron09:07
apuimedobecause I think we still created with a device owner09:07
irenabapuimedo: so need test for update :-)09:07
irenabbut it should be more on the API requests level09:07
reedipirenab: is it not optional ?09:07
apuimedoleave a comment on that for limao so he finds it easier09:08
apuimedoplease09:08
reedipirenab: "basepython = python2.7"09:08
irenabreedip: yes, maybe its optional. I was not sure. Otherwise you patch is fine09:08
reedipirenab: nova, for example, does not have it https://github.com/openstack/nova/blob/master/tox.ini09:09
irenabapuimedo:  I will let him decide what level test he adds09:09
apuimedook09:09
reedipirenab: neither does python-neutronclient https://github.com/openstack/python-neutronclient/blob/master/tox.ini09:10
irenabreedip: ok, if there will be needed, can be added later09:10
reedipirenab: ok, sure. Thanks09:10
*** openstackgerrit has quit IRC09:17
*** openstackgerrit has joined #openstack-kuryr09:17
*** devvesa has joined #openstack-kuryr09:24
openstackgerritLiping Mao proposed openstack/kuryr: The device_id and device_owner of neutron port are null  https://review.openstack.org/27607809:32
*** tfukushima has quit IRC10:30
*** tfukushima has joined #openstack-kuryr10:32
*** salv-orlando has joined #openstack-kuryr10:54
*** tfukushima has quit IRC11:04
*** mark_dunn has joined #openstack-kuryr12:24
*** salv-orlando has quit IRC12:32
*** salv-orlando has joined #openstack-kuryr12:46
*** banix has joined #openstack-kuryr13:34
openstackgerritvenkatamahesh proposed openstack/kuryr: Fix misspellings  https://review.openstack.org/27625514:12
*** salv-orlando has quit IRC14:20
irenabbanix: hey14:22
banixirenab: hi14:23
irenabI wanted to ask your opinion on mapping of kube model with policies to neutron model14:23
*** salv-orlando has joined #openstack-kuryr14:24
irenabnot sure if mapping services to networks is good , this was mentioned yesterday during the meeting14:24
banixirenab: the new blueprint you proposed?14:25
irenabbanix: I didn’t add the mapping details yet14:25
banixi haven’t had a chance to look at that but I think that is not covered there14:25
banixyeah14:25
banixLet me spend more time on this and get back to you14:26
irenabsure, ping me if/once you want to discuss.14:27
banixwill do14:27
*** mark_dunn has quit IRC15:24
*** mark_dunn has joined #openstack-kuryr15:37
fkautzirenab: how do we gain access to the spec? i get "Sorry, you don't have permission to access this page or the information in this page is not shared with you."16:13
*** salv-orlando has quit IRC16:37
irenabfkautz: https://docs.google.com/document/d/1qAm-_oSap-f1d6a-xRTj6xaH1sYQBfK36VyjB5XOZug/edit16:57
fkautzthanks16:58
irenabfkautz: does the link work you?16:58
fkautzyea, that works16:58
*** shashank_hegde has joined #openstack-kuryr17:25
*** shashank_hegde has quit IRC17:36
*** salv-orlando has joined #openstack-kuryr17:39
*** salv-orlando has quit IRC17:44
*** salv-orlando has joined #openstack-kuryr18:24
*** salv-orlando has quit IRC18:28
*** devvesa has quit IRC18:39
*** shashank_hegde has joined #openstack-kuryr18:41
*** apuimedo has quit IRC18:49
*** mspreitz_ has joined #openstack-kuryr19:08
*** gsagie_ has joined #openstack-kuryr19:08
mspreitz_Why is Kuryr concerned with creating new Neutron networks?  That seems like an unnecessary heap of trouble, it would be better to just work with pre-existing Neutorn networks.19:09
mspreitz_@banix?19:22
mspreitz_@mestery?19:22
mspreitz_Is anybody alive in here?19:23
*** mspreitz_ has quit IRC19:31
irenabmspreitz_: you may want to check this https://review.openstack.org/#/c/254005/. Currently  connecting to preexisting networks is not supported19:35
*** mark_dunn has quit IRC19:37
openstackgerritKyle Mestery proposed openstack/kuryr: Vagrant: Workaround shebang insanities  https://review.openstack.org/27641319:38
mesterymspreitz has left :(19:39
*** salv-orlando has joined #openstack-kuryr19:54
*** gsagie_ has quit IRC20:37
*** lezbar has quit IRC20:38
*** dingboopt_ has joined #openstack-kuryr20:47
*** dingboopt has quit IRC20:47
*** dingboopt_ is now known as dingboopt20:47
*** dingboopt has quit IRC20:57
*** salv-orl_ has joined #openstack-kuryr22:39
*** salv-orlando has quit IRC22:42
*** banix has quit IRC23:04
*** banix has joined #openstack-kuryr23:05
*** banix has quit IRC23:08

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