Wednesday, 2019-02-27

*** sdake has quit IRC00:00
*** sdake has joined #openstack-containers00:03
*** sdake has quit IRC00:05
*** sdake has joined #openstack-containers00:06
*** sdake has quit IRC00:10
*** henriqueof has quit IRC00:15
*** sdake has joined #openstack-containers00:33
*** sdake has quit IRC00:59
*** _fragatina has quit IRC01:14
*** itlinux has joined #openstack-containers01:16
*** sdake has joined #openstack-containers01:34
*** _fragatina has joined #openstack-containers01:35
*** itlinux has quit IRC01:36
*** sdake has quit IRC02:09
*** sdake has joined #openstack-containers02:09
*** mrodriguez has quit IRC02:11
*** sdake has quit IRC02:13
*** sdake has joined #openstack-containers02:13
*** gyee has quit IRC02:15
*** sdake has quit IRC02:16
jakeyiphi eandersson you around?02:23
eanderssonyo02:24
jakeyipgot a min to chat about that commit?02:24
eanderssonsure02:24
jakeyipso, contents needs to be text02:24
eanderssonca_cert_contents?02:24
jakeyipall 3 of them, cos we are opening a tempfile with 'w+' mode02:25
eanderssonbut so decode will always change the file type to text02:28
jakeyipyes02:28
eanderssonthat is why you have the if statement there02:28
eanderssonif it already text it will just leave it-as02:29
eanderssonthat is why you don't need six.u02:29
jakeyipOH. I know what you mean now02:29
jakeyipi left the six.u in accidentally. :(02:30
eanderssonI would probably change magnum_key_contents and magnum_cert_contents02:30
eanderssonto use the if version as well02:30
jakeyipyeah, no idea what I was doing02:31
eanderssonactually can't you just move some of those up on top?02:31
eanderssone.g.02:31
eandersson> magnum_key_contents = magnum_cert.get_decrypted_private_key()02:31
eanderssonlooks like a dupe02:31
*** rcernin has quit IRC02:32
jakeyipI could but the tests will have to change02:32
eanderssonYea nvm lets just fix it and make it better later :p02:32
eanderssonGonna log off but I'll check in later tonight02:32
jakeyipthat was what I did originally but the tests test the number of calls02:32
jakeyipyeap, will fix this up. maybe even write a test02:32
*** hongbin has joined #openstack-containers02:38
*** sdake has joined #openstack-containers02:42
*** hongbin has quit IRC02:43
*** sdake has quit IRC02:45
*** _fragatina has quit IRC02:45
*** sdake has joined #openstack-containers02:47
*** sdake has quit IRC02:55
*** sdake has joined #openstack-containers02:55
*** sdake has quit IRC03:01
*** sdake_ has joined #openstack-containers03:02
*** sdake_ has quit IRC03:10
*** sdake has joined #openstack-containers03:13
*** sdake has quit IRC03:15
*** sdake has joined #openstack-containers03:15
*** sdake has quit IRC03:23
openstackgerritFeilong Wang proposed openstack/magnum master: Return instance ID of worker node  https://review.openstack.org/63905303:23
*** sdake_ has joined #openstack-containers03:23
*** sdake_ has quit IRC03:25
*** sdake has joined #openstack-containers03:27
*** sdake has quit IRC03:30
*** itlinux has joined #openstack-containers03:31
*** sdake has joined #openstack-containers03:31
*** sdake has quit IRC03:35
*** sdake has joined #openstack-containers03:36
*** sdake has quit IRC03:44
*** sdake_ has joined #openstack-containers03:44
*** sdake_ has quit IRC03:51
*** sdake has joined #openstack-containers03:52
*** sdake has quit IRC03:55
*** ramishra has joined #openstack-containers03:57
*** sdake has joined #openstack-containers03:58
*** sdake has quit IRC04:00
*** sdake_ has joined #openstack-containers04:03
*** sdake_ has quit IRC04:05
*** sdake has joined #openstack-containers04:06
*** sdake has quit IRC04:11
*** sdake_ has joined #openstack-containers04:11
*** spsurya has joined #openstack-containers04:15
*** sdake_ has quit IRC04:17
*** ykarel has joined #openstack-containers04:19
*** janki has joined #openstack-containers04:33
*** _fragatina has joined #openstack-containers04:52
*** itlinux has quit IRC05:01
*** dave-mccowan has quit IRC05:05
*** ricolin has joined #openstack-containers05:21
*** ricolin has quit IRC05:35
*** udesale has joined #openstack-containers05:42
*** ramishra has quit IRC05:43
*** ramishra has joined #openstack-containers05:45
*** ykarel has quit IRC05:54
*** ykarel has joined #openstack-containers05:55
*** ramishra has quit IRC05:55
*** ramishra has joined #openstack-containers06:03
*** ivve has joined #openstack-containers06:08
*** ttsiouts has joined #openstack-containers06:53
*** ramishra has quit IRC06:58
*** ramishra has joined #openstack-containers07:01
*** ivve has quit IRC07:17
*** belmoreira has joined #openstack-containers07:25
*** ttsiouts has quit IRC07:33
*** ttsiouts has joined #openstack-containers07:34
*** ivve has joined #openstack-containers07:34
*** ttsiouts has quit IRC07:38
*** pcaruana has joined #openstack-containers08:13
*** ttsiouts has joined #openstack-containers08:25
*** pcaruana has quit IRC08:28
*** ttsiouts has quit IRC08:30
*** pcaruana has joined #openstack-containers08:42
*** alisanhaji has joined #openstack-containers08:42
*** pcaruana has quit IRC08:51
openstackgerritJake Yip proposed openstack/magnum master: python3 fix: decode binary cert data if encountered  https://review.openstack.org/63833608:52
*** flwang1 has joined #openstack-containers08:55
flwang1strigazi: around?08:55
*** ttsiouts has joined #openstack-containers08:55
*** pcaruana has joined #openstack-containers08:58
*** pcaruana|afk| has joined #openstack-containers09:01
*** pcaruana has quit IRC09:03
strigaziflwang1: yeap09:07
strigaziflwang1: we just upgraded magnum to rocky09:07
strigaziflwang1: testing keystone-auth09:08
strigaziflwang1: Then I'm pushing09:08
*** ttsiouts has quit IRC09:08
flwang1cool, could you pls revisit https://review.openstack.org/623092 ?09:08
flwang1i would like to get it in asap09:09
openstackgerritFeilong Wang proposed openstack/magnum master: Add server group for cluster worker nodes  https://review.openstack.org/61382509:09
*** ttsiouts has joined #openstack-containers09:09
strigaziflwang1: looking09:09
flwang1strigazi: and could you please review https://review.openstack.org/#/c/613825/ and https://review.openstack.org/63905309:09
strigazihttps://review.openstack.org/613825 +209:10
*** ivve has quit IRC09:11
*** ttsiouts_ has joined #openstack-containers09:11
strigaziFor https://review.openstack.org/639053 We need to update the commit message, I think it must say the full story.09:12
*** ttsiouts has quit IRC09:12
flwang1strigazi: ok, then for https://review.openstack.org/639053 , pls feel free to post a patch to update the commit message09:13
strigaziyou can also the link for the story in the comments. It took me 30mins yesterday to explain it. People won't get it.09:13
strigaziok, I'll do it asap09:13
flwang1try https://review.openstack.org/#/c/639053/4//COMMIT_MSG,edit ?09:13
strigazijust need to check if keystone-auth works09:13
flwang1strigazi: i can paste your words into the comment09:14
strigaziok, I'll do it now then09:14
flwang1just added a comment09:15
*** ivve has joined #openstack-containers09:26
*** janki has quit IRC09:30
*** janki has joined #openstack-containers09:30
*** sapd1 has quit IRC09:33
openstackgerritSpyros Trigazis proposed openstack/magnum master: Return instance ID of worker node  https://review.openstack.org/63905309:39
strigaziflwang1: done09:39
flwang1strigazi: perfect, lgtm09:42
flwang1strigazi: let's merge it?09:42
*** ykarel is now known as ykarel|lunch09:44
strigaziflwang1: ok. I think without these comments the change would cause confusion. It's now enough to push the code and merge. Sorry for teh delay but it needed to be done. The code is not enough.09:46
flwang1strigazi: that's ok09:46
openstackgerritSpyros Trigazis proposed openstack/magnum master: Return instance ID of worker node  https://review.openstack.org/63905309:46
strigazi+209:48
flwang1strigazi: thanks09:49
strigaziflwang1: I want to push a change in the CI to check for storyboard links and releasenotes09:51
strigaziflwang1: thoughts?09:51
strigazibrtknr: ^^09:51
flwang1sure09:51
flwang1it's good to have09:51
flwang1strigazi: https://review.openstack.org/#/c/638069/ need your bless09:53
strigaziflwang1: -1 the ssh port is closed09:54
strigaziflwang1: I left a comment about it already09:54
flwang1why do you think we have to open the ssh port?09:54
strigaziso be able to login to the nodes09:54
strigazi;)09:55
flwang1strigazi: i know, but admin user of the cluster can open it manually when it's really necessary09:55
flwang1for the default state, we're trying to only open ports which are really necessary09:55
strigaziwe have in master nodes09:55
flwang1strigazi: i know, for master, that's another story09:56
flwang1for the perfect world, user shouldn't have permission to login the master as well09:56
flwang1they even won't be able to see the masters as we discussed before09:56
strigazi"hidden" masters is a completely different discussion09:57
flwang1just like using a loadbalancer service or a DB service, user don't have to, even shouldn't know the node, but just use the service09:57
flwang1strigazi: i know it's a different story09:58
flwang1i'm just saying user don't have to get the login BY DEFAULT09:58
flwang1they can enable it when they want09:58
strigaziI'm thinking. traefik won't work for users that have security groups09:59
brtknrstrigazi: I dont fully follow the context regarding check for storyboard links09:59
strigazibrtknr all commit must reference a story in story board09:59
brtknrstrigazi: As in, there must be a story/task id in the commit message for the Zuul gate to pass?09:59
strigazibrtknr all commits must reference a story in story board09:59
strigaziyes09:59
brtknrgotcha! sounds great09:59
openstackgerritMerged openstack/magnum master: Add reno for flannel reboot fix  https://review.openstack.org/63861310:00
strigaziflwang1: ok with a note in traefik docs and reno. let's take it.10:01
strigaziflwang1: ok with a note in traefik docs and in reno. let's take it.10:01
strigazimakes sense?10:01
flwang1strigazi: sure10:01
strigaziI'm doing it10:02
*** sdake has joined #openstack-containers10:02
flwang1more doc is always good10:02
*** sdake has quit IRC10:05
*** sdake has joined #openstack-containers10:07
*** sdake has quit IRC10:10
*** sdake has joined #openstack-containers10:12
*** sdake has quit IRC10:13
*** sdake has joined #openstack-containers10:14
*** sdake has quit IRC10:15
strigaziflwang1: example command to open the port?10:15
strigaziflwang1: can you paste it here10:15
flwang1openstack security group rule create     [--remote-ip <ip-address> | --remote-group <group>]     [--dst-port <port-range> | [--icmp-type <icmp-type> [--icmp-code <icmp-code>]]]     [--protocol <protocol>]     [--ingress | --egress]     [--ethertype <ethertype>]     [--project <project> [--project-domain <project-domain>]]     [--description <description>]     <group>10:16
flwang1are you going to add it into the doc?10:17
strigaziflwang1: ok, I can write it myself10:17
flwang1strigazi: sorry, generally, i just use the dashboard to add rule10:17
flwang1i don't have a cli in hand10:17
flwang1openstack security group rule create SECURITY_GROUP_NAME --protocol tcp --dst-port 22:22 --remote-ip 0.0.0.0/010:18
flwang1strigazi: ^10:18
*** sdake has joined #openstack-containers10:22
*** ykarel|lunch is now known as ykarel10:23
*** sdake has quit IRC10:25
openstackgerritSpyros Trigazis proposed openstack/magnum master: [k8s-fedora-atomic] Security group definition for worker nodes  https://review.openstack.org/63806910:25
*** sdake has joined #openstack-containers10:26
strigazibrtknr: can you have a look as well ^^10:27
strigaziflwang1: you connect to the dashboard? In our cloud as admins, we never login.10:28
strigaziflwang1: it will take a million years to do anything10:29
flwang1strigazi: we can only login dashboard in internal network10:29
flwang1with admin user10:29
flwang1why it takes long? because the bad performance of horizon?10:29
openstackgerritSpyros Trigazis proposed openstack/magnum master: [k8s-fedora-atomic] Security group definition for worker nodes  https://review.openstack.org/63806910:30
strigazibecause we have 40000 vms :)10:30
*** sdake has quit IRC10:30
brtknrLooking10:30
flwang1strigazi: o10:31
flwang1i'm jealous of that10:31
strigaziwell 3562610:31
brtknrWhy is icmp being blocked?10:32
brtknrIts useful to check if a node has come online10:32
*** sdake has joined #openstack-containers10:32
strigazi8848 hypervisors, I think mount everest has this high in meters10:32
strigazibrtknr: it is blocked, I missed that10:32
brtknrNot sure why its a security issue10:33
strigaziflwang1: ^^10:33
flwang1brtknr: that's a good point10:35
flwang1personally, i think ICMP is ok to open10:35
*** sdake has quit IRC10:35
strigazilet's open it then10:35
flwang1i asked our ops, and they also think ICMP is not a big problem10:36
*** sdake has joined #openstack-containers10:36
flwang1that could be useful for health check for some cases10:36
brtknryes, sometimes, there can be such a thing as too much security... like Trump's wall10:36
strigazitouche10:37
brtknr;)10:38
*** sdake has quit IRC10:41
*** sdake_ has joined #openstack-containers10:41
*** sdake_ has quit IRC10:45
flwang1strigazi: any other comment on https://review.openstack.org/#/c/623092/8 ?10:46
flwang1i'm going to post a new patchset to address you and brtknr's comment10:46
strigaziflwang1: I'm testing10:47
*** sdake has joined #openstack-containers10:47
brtknralso the point about no ssh hasnt been addressed10:47
brtknrwhats the reason to block ssh?10:48
strigazibrtknr: operators or users will have to open the port10:48
strigazibrtknr: https://review.openstack.org/#/c/638069/4/releasenotes/notes/k8s-nodes-security-group-9d8dbb91b006d9dd.yaml10:48
flwang1brtknr: i think public cloud and private cloud may have different PoV about security10:48
strigaziflwang1: not really10:48
strigaziit the same for us.10:49
flwang1strigazi: ok, no argument here10:49
strigazifor everyone10:49
flwang1i have explained above anyway10:49
flwang1brtknr: ^10:49
strigaziIf we were very well prepared we could disable even the daemon10:49
flwang1by default, we'd like close as much as possible ports10:49
*** sdake has quit IRC10:50
flwang1strigazi: let's don't argue details when you got my point10:50
brtknrDISABLE THE SSH DAEMON?10:51
*** sdake has joined #openstack-containers10:51
brtknroops10:51
strigazibrtknr: if10:51
brtknrbtw anyone else excited about RunAsGroup transitioning to beta in 1.14?10:53
strigaziflwang1:10:53
strigazitypo ^^10:53
*** udesale has quit IRC10:53
*** sdake has quit IRC10:55
*** sdake has joined #openstack-containers10:56
flwang1brtknr: TBH, generally i'm more care about the stability than new features ;)10:58
*** sdake has quit IRC11:00
openstackgerritFeilong Wang proposed openstack/magnum master: [k8s-fedora-atomic] Security group definition for worker nodes  https://review.openstack.org/63806911:00
*** sdake has joined #openstack-containers11:01
strigaziRunAsGroup is a big security improvement.11:05
brtknrstrigazi: What do you guys do about shared storage at Cern regarding file permissions etc. for volumes mounted in k8s pods?11:09
*** ttsiouts_ has quit IRC11:09
*** ttsiouts has joined #openstack-containers11:10
brtknrIts a big problem for us as the userspace uid/gid do not map to container uid/gid...11:10
brtknrI think RunAsGroup is a step in the right direction11:10
*** sapd1 has joined #openstack-containers11:11
brtknrI'm thinking of RBAC rules that only allow a service account credential to run pods with certain uid/gid11:11
openstackgerritLingxian Kong proposed openstack/magnum master: [k8s-fedora-atomic] Use ClusterIP for prometheus service  https://review.openstack.org/63900111:12
brtknrAlthough I am not sure whether thats currently possible11:13
openstackgerritLingxian Kong proposed openstack/magnum master: [k8s-fedora-atomic] Use ClusterIP for prometheus service  https://review.openstack.org/63900111:13
brtknrThis blog article appears to suggest its possible: https://medium.com/coryodaniel/kubernetes-assigning-pod-security-policies-with-rbac-2ad2e847c75411:15
flwang1lxkong: did you see our discussion about the security rules?11:20
lxkongflwang1: no, didn't look at irc11:20
* lxkong is scrolling up11:20
flwang1lxkong: then just take a look the patch set we proposed https://review.openstack.org/63806911:21
flwang1lxkong: let's know if you're happy with that11:21
flwang1in short, we're adding the icmp back11:21
lxkongicmp?11:21
lxkongyep, i'm ok with that11:21
flwang1and strigazi just updated some docs11:21
flwang1cool11:21
*** ttsiouts has quit IRC11:23
strigaziflwang1: brtknr https://review.openstack.org/#/c/623092/811:24
strigazihttps://review.openstack.org/#/c/623092/8/magnumclient/common/utils.py@24511:24
strigaziflwang1: brtknr ^^11:25
flwang1strigazi: yep, if you source the rc file on the same session, you will get this issue11:26
flwang1so yes, we probably need to use another different name11:26
strigaziflwang1: we will need the rc to generate the token11:26
strigazilet's hear from others?11:27
flwang1strigazi: yep, i know, can you try OS_AUTH_TOKEN ?11:27
strigaziOS_TOKEN is a standard name, we need to think about it before dropping the standard name11:27
strigaziOS_AUTH_TOKEN where?11:28
flwang1OS_AUTH_TOKEN is also standard name11:29
strigaziOS_AUTH_TOKEN works11:30
openstackgerritLingxian Kong proposed openstack/magnum master: [k8s-fedora-atomic] Security group definition for worker nodes  https://review.openstack.org/63806911:32
flwang1strigazi: so let's use OS_AUTH_TOKEN?11:33
strigaziok11:34
strigazidocs, reno?11:34
strigaziI can't find OS_AUTH_TOKEN anywhere in keystone docs11:34
flwang1you can find it when you generate a rc file on horizon11:35
flwang1doc in client side and reno also on client side?11:36
strigazihttps://github.com/openstack/horizon/search?q=%22OS_AUTH_TOKEN%22&unscoped_q=%22OS_AUTH_TOKEN%2211:36
flwang1or you're asking doc and reno on server side?11:36
strigaziI think people look at the server side docs11:38
flwang1strigazi: we have reno and doc at https://review.openstack.org/#/c/561783/11:39
flwang1are you asking a user guide about how to use this?11:40
strigaziflwang1: let's wait at least for Rircardo (I'll ping him) or someone else to reply about the var name11:40
flwang1strigazi: sure, https://github.com/hashicorp/packer/issues/441511:41
strigaziflwang1: how are we going to inform users about it?11:41
strigaziwe need to have docs about the client, no?11:42
flwang1strigazi: seems we don't have a doc in client, but i can write a doc on server side about how to use the keystone auth feature including client usage11:42
flwang1strigazi: seems OS_AUTH_TOKEN is an old veriable before OS_TOKEN https://sumitkgaur.wordpress.com/2014/05/14/openstack-object-storage-swift/11:44
brtknrflwang1: can you please help me understand why we're using OS_TOKEN?11:44
flwang1brtknr: for keystone auth feature, are you aware of we support it now?11:45
strigazithe why should have been in the commit message :)11:45
brtknryes but why are we using OS_TOKEN instead of OS_USERNAME and OS_PASSWORD?11:45
brtknror generate OS_TOKEN from the client using OS_USERNAME and OS_PASSWORD11:46
brtknrif not available in the environment11:46
strigazior generate OS_TOKEN from the client using OS_USERNAME and OS_PASSWORD this11:46
strigazibrtknr: people are using different auth methods like:11:47
strigazicertificates, kerberos, oauth some(?)11:47
strigazior creds11:47
strigaziuser/pass11:47
flwang1strigazi: hmm... we may be able to do it like this ' export OS_AUTH_TOKEN=$(openstack token issue -f value -c id)' in the config11:47
brtknrflwang1: yes, thats a good idea!11:48
strigaziflwang1: why ask for a token every time? is will be slower11:48
strigaziBetter not make k8s as fast as keystone11:48
flwang1we can check it first11:48
brtknrstrigazi: but thats what most clients do11:48
*** ttsiouts has joined #openstack-containers11:49
strigaziwe don't have to write a new client11:49
flwang1then there is no perfect solution11:49
strigaziThere is the option to use the token which means no new configuration, only in kubeconfig11:50
flwang1i have to offline in 10 mins11:50
strigaziif we want to use a client, in the cloud provider repo there is a client11:50
flwang1it's very late here11:50
flwang1true, like i do in initial patch11:51
strigaziflwang1: I'll ask Ricardo to review. Maybe we just fo with OS_TOKEN11:51
strigaziflwang1: the extra client is bad11:51
flwang1agree11:51
strigaziwe need to redistribute clients11:51
strigazipackage, test11:51
strigazirebuild on security11:52
strigaziwe can support it with a third parameter11:52
flwang1strigazi: i'd like to let openstack release a docker image for openstack clients, like i said in my TC nominaiton email11:52
strigazibrtknr: makes sense why we proposed OS_TOKEN?11:52
strigazidocker is a good plus11:53
strigazidocker image is a good plus11:53
strigazinot enough11:53
strigaziall users must have docker?11:54
flwang1no, don't get me wrong, i'm not saying only have the docker image11:55
flwang1i'm saying having a docker image will be a good one11:55
flwang1so people don't have to worry about python deps, etc, etc11:56
openstackgerritMerged openstack/magnum master: Return instance ID of worker node  https://review.openstack.org/63905311:57
strigaziflwang1: I understand. I'm not saying is bad or anything. It is good.11:58
strigazibut doesn't solve all problems. If opestack would release a single golang binary, that would solve many issues.11:59
flwang1strigazi: i have to go, i will propose patch about the action api for both resize and upgrade11:59
strigaziflwang1: just go for resize first11:59
*** ivve has quit IRC12:00
flwang1strigazi: yep, i mean, i will consider the case of upgrade as well12:00
flwang1the api will be v1/<cluster id>/action   and the POST body will be {"resize": {"node_count": 2}}12:01
strigaziyes12:01
strigazicool12:01
strigazithanks12:01
flwang1cool12:01
flwang1i have to go to bed now12:01
strigazigood night12:02
flwang1thank you, my friend, all good discussion12:02
* strigazi is going for lunch12:02
strigaziflwang1: cheers12:02
*** ramishra has quit IRC12:04
*** ramishra has joined #openstack-containers12:26
*** udesale has joined #openstack-containers12:26
openstackgerritMerged openstack/magnum master: Add server group for cluster worker nodes  https://review.openstack.org/61382512:32
*** ivve has joined #openstack-containers12:57
*** dave-mccowan has joined #openstack-containers13:02
*** pcaruana|afk| has quit IRC13:09
*** sdake has quit IRC13:16
*** jmlowe has quit IRC13:29
*** henriqueof has joined #openstack-containers13:45
*** janki has quit IRC13:53
*** mrodriguez has joined #openstack-containers13:57
*** sdake has joined #openstack-containers14:12
*** sdake has quit IRC14:12
*** jmlowe has joined #openstack-containers14:13
*** ykarel is now known as ykarel|afk14:20
brtknrstrigazi: yes kind of.... I am just thinking about the experience of using openstack credentials to generate kubeconfig... will I need to provide OS_TOKEN each time?14:44
brtknrand use OS_AUTH_TYPE=token14:44
brtknrand unset OS_USERNAME and OS_PASSWORD14:44
brtknrits kind of painful14:44
*** ttsiouts has quit IRC14:45
*** sdake has joined #openstack-containers14:48
*** sdake has quit IRC14:55
strigazibrtknr: this option is mostly for non admin users14:55
*** hongbin has joined #openstack-containers14:56
strigazibrtknr: if you are the cluster admin, just use the certs for authentication14:56
*** pcaruana has joined #openstack-containers14:57
strigazibrtknr: actually we can add all options14:58
*** itlinux has joined #openstack-containers14:59
*** sdake has joined #openstack-containers15:01
strigazibrtknr: one thing to take into account is that kubetl need a token only. so with password and so on, kubectl would issue a token first with the openstack client, parse it and then send it15:02
strigazitoken issue takes a full second. (not because of keystone server) but because of the python client15:03
strigazibrtknr: you can use the golang binary which is faster15:03
strigazibrtknr: in any case, users like Cern and blizzard, OS_PASSWORD is not an option. we use kerberos15:04
*** ykarel|afk is now known as ykarel15:06
*** ttsiouts has joined #openstack-containers15:06
brtknrstrigazi: any good actively developed golang client you know of?15:16
strigazibrtknr: https://github.com/kubernetes/cloud-provider-openstack/tree/master/cmd/client-keystone-auth15:18
*** hongbin has quit IRC15:18
*** hongbin has joined #openstack-containers15:20
*** imdigitaljim has quit IRC15:30
*** cbrumm_ has quit IRC15:30
*** schaney has quit IRC15:31
*** itlinux_ has joined #openstack-containers15:31
*** schaney has joined #openstack-containers15:32
*** cbrumm_ has joined #openstack-containers15:32
*** sdake has quit IRC15:33
*** itlinux has quit IRC15:34
*** sdake has joined #openstack-containers15:36
*** itlinux_ has quit IRC15:46
*** sapd1 has quit IRC15:46
*** ivve has quit IRC16:01
*** ykarel is now known as ykarel|away16:03
*** ykarel|away is now known as ykarel16:04
*** udesale has quit IRC16:10
*** ramishra has quit IRC16:25
*** hongbin has quit IRC16:33
*** _fragatina has quit IRC16:36
*** hongbin has joined #openstack-containers16:41
*** ykarel_ has joined #openstack-containers16:43
*** ykarel has quit IRC16:46
*** sdake has quit IRC16:52
*** sdake has joined #openstack-containers16:54
*** pcaruana has quit IRC16:57
*** _fragatina has joined #openstack-containers16:58
*** _fragatina_ has joined #openstack-containers16:59
*** ykarel_ is now known as ykarel|away16:59
*** rtjure has quit IRC17:00
*** sdake has quit IRC17:02
*** _fragatina has quit IRC17:02
*** _fragatina_ has quit IRC17:07
*** ttsiouts has quit IRC17:31
*** ttsiouts has joined #openstack-containers17:31
*** jmlowe has quit IRC17:34
*** dims has quit IRC17:35
*** ttsiouts has quit IRC17:36
*** ivve has joined #openstack-containers17:36
*** flwang1 has quit IRC17:48
*** dims has joined #openstack-containers17:48
*** ykarel|away has quit IRC17:51
*** _fragatina has joined #openstack-containers17:58
*** sdake has joined #openstack-containers18:26
*** _fragatina has quit IRC18:31
*** sdake has quit IRC18:33
*** _fragatina has joined #openstack-containers18:35
*** sdake has joined #openstack-containers18:38
*** ivve has quit IRC18:43
*** sdake has quit IRC18:44
*** sdake has joined #openstack-containers18:45
*** jmlowe has joined #openstack-containers18:47
*** jmlowe has quit IRC18:47
*** jmlowe has joined #openstack-containers18:48
*** sdake has quit IRC18:51
*** sdake has joined #openstack-containers18:56
*** alisanhaji has quit IRC19:20
*** ttsiouts has joined #openstack-containers19:36
*** spsurya has quit IRC19:52
*** henriqueof has quit IRC20:01
*** jmlowe has quit IRC20:29
*** dave-mccowan has quit IRC20:38
*** henriqueof has joined #openstack-containers20:57
*** ivve has joined #openstack-containers21:03
openstackgerritLingxian Kong proposed openstack/magnum master: [k8s-fedora-atomic] Security group definition for worker nodes  https://review.openstack.org/63806921:07
*** ivve has quit IRC21:14
*** jmlowe has joined #openstack-containers21:17
openstackgerritFeilong Wang proposed openstack/magnum master: [WIP] Support <cluster>/actions/resize API  https://review.openstack.org/63857222:04
openstackgerritFeilong Wang proposed openstack/magnum master: [WIP] Support <cluster>/actions/resize API  https://review.openstack.org/63857222:06
openstackgerritFeilong Wang proposed openstack/magnum master: [WIP] Support <cluster>/actions/resize API  https://review.openstack.org/63857222:11
openstackgerritLingxian Kong proposed openstack/magnum master: [k8s-fedora-atomic] Security group definition for worker nodes  https://review.openstack.org/63806922:12
openstackgerritLingxian Kong proposed openstack/magnum master: [k8s-fedora-atomic] Security group definition for worker nodes  https://review.openstack.org/63806922:16
flwangmnaser: around? recently, we're getting node failure for k8s api functional job22:31
*** sdake has quit IRC22:36
*** sdake has joined #openstack-containers22:54
mnaserflwang: oh thats no bueno23:03
mnaserflwang: let me dig in23:03
flwangmnaser: thanks23:04
*** rcernin has joined #openstack-containers23:06
*** sapd1 has joined #openstack-containers23:06
*** dave-mccowan has joined #openstack-containers23:17
*** itlinux has joined #openstack-containers23:26
*** ttsiouts has quit IRC23:32
*** sdake has quit IRC23:38
*** sdake has joined #openstack-containers23:41
*** sdake has quit IRC23:42
openstackgerritMerged openstack/magnum master: [k8s-fedora-atomic] Security group definition for worker nodes  https://review.openstack.org/63806923:59

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