Friday, 2018-05-25

*** threestrands has joined #openstack-containers00:05
*** threestrands has quit IRC00:05
*** threestrands has joined #openstack-containers00:05
*** yamamoto has joined #openstack-containers00:27
*** yamamoto has quit IRC00:34
*** dave-mccowan has joined #openstack-containers00:55
*** harlowja has quit IRC01:05
*** yamamoto has joined #openstack-containers01:05
*** yamamoto has quit IRC01:10
*** gyankum has joined #openstack-containers01:20
*** dave-mccowan has quit IRC01:21
*** fragatin_ has quit IRC01:24
*** fragatina has joined #openstack-containers01:25
*** fragatina has quit IRC01:28
*** yamamoto has joined #openstack-containers01:41
*** yamamoto has quit IRC01:48
*** fragatina has joined #openstack-containers02:16
*** yamamoto has joined #openstack-containers02:19
*** yamamoto has quit IRC02:25
*** PanFengyun has quit IRC02:38
*** ramishra has joined #openstack-containers02:56
*** yamamoto has joined #openstack-containers02:57
*** yamamoto has quit IRC03:01
*** zhubingbing has joined #openstack-containers03:08
*** threestrands has quit IRC03:10
*** zhubingbing has quit IRC03:12
*** threestrands has joined #openstack-containers03:13
*** threestrands has quit IRC03:13
*** threestrands has joined #openstack-containers03:14
*** threestrands has quit IRC03:15
*** threestrands has joined #openstack-containers03:15
*** yamamoto has joined #openstack-containers03:32
*** yamamoto has quit IRC03:38
*** janki has joined #openstack-containers04:05
*** yamamoto has joined #openstack-containers04:08
*** yamamoto has quit IRC04:12
*** ykarel|away has joined #openstack-containers04:17
*** yamamoto has joined #openstack-containers04:43
*** yamamoto has quit IRC04:44
*** yamamoto has joined #openstack-containers04:44
*** harlowja has joined #openstack-containers04:46
*** ykarel|away is now known as ykarel04:55
*** flwang1 has quit IRC04:58
*** harlowja has quit IRC05:11
*** chhagarw has joined #openstack-containers05:13
*** udesale has joined #openstack-containers05:21
*** yamamoto has quit IRC05:25
*** lpetrut has joined #openstack-containers05:33
*** mjura has joined #openstack-containers05:43
*** yamamoto has joined #openstack-containers05:51
*** iranzo has joined #openstack-containers05:52
*** iranzo has joined #openstack-containers05:52
*** gsimondon has joined #openstack-containers06:04
*** ricolin has joined #openstack-containers06:10
*** lpetrut has quit IRC06:16
*** ricolin has quit IRC06:39
*** ricolin has joined #openstack-containers06:43
*** lpetrut has joined #openstack-containers06:43
*** sfilatov has joined #openstack-containers06:58
*** sfilatov has quit IRC07:12
*** sfilatov_ has joined #openstack-containers07:15
*** lpetrut has quit IRC07:17
*** threestrands has quit IRC07:18
*** rcernin has quit IRC07:20
*** ricolin has quit IRC07:21
*** AlexeyAbashkin has joined #openstack-containers07:23
*** ricolin has joined #openstack-containers07:24
*** Alexey_Abashkin has joined #openstack-containers07:26
*** AlexeyAbashkin has quit IRC07:28
*** Alexey_Abashkin is now known as AlexeyAbashkin07:28
*** sfilatov has joined #openstack-containers07:29
*** sfilatov_ has quit IRC07:31
*** ykarel is now known as ykarel|lunch07:33
*** lpetrut has joined #openstack-containers07:34
*** lpetrut has quit IRC07:39
*** mgoddard has joined #openstack-containers07:40
*** sfilatov has quit IRC07:46
*** sfilatov has joined #openstack-containers07:47
*** yasemin has quit IRC07:51
*** sfilatov has quit IRC07:52
*** yasemin has joined #openstack-containers07:55
*** sfilatov has joined #openstack-containers07:58
*** lpetrut has joined #openstack-containers08:29
*** ricolin has quit IRC08:30
*** yasemin has quit IRC08:43
*** ykarel|lunch is now known as ykarel08:54
*** pcaruana has joined #openstack-containers08:54
sfilatovHey08:57
sfilatovI know probably some of you are on summit08:57
sfilatovBut I'd like to discuss a topic which I sent to a mailing list08:58
*** pcaruana is now known as pcaruana|call|08:58
sfilatovI’d like to initiate a discussion about this bug: [1].08:58
sfilatovTo resolve this issue we need to generate a secret cert and pass it to master nodes. We also need to store it somewhere to support scaling.08:58
sfilatovThis issue is specific for kubernetes drivers. Currently in magnum we have a general cert manager which is the same for all the drivers.08:58
sfilatovWhat do you think about moving cert_manager logic into a driver-specific area?08:58
sfilatovHaving this common cert_manager logic forces us to generate client cert with “admin” and “system:masters” subject & organisation names [2],08:58
sfilatovwhich is really something that we need only for kubernetes drivers.08:58
sfilatov[1] https://bugs.launchpad.net/magnum/+bug/176654608:58
openstackLaunchpad bug 1766546 in Magnum "Multi-Master deployments for k8s driver use different service account keys" [Undecided,New] - Assigned to SFilatov (sergeyfilatov)08:58
sfilatov[2] https://github.com/openstack/magnum/blob/2329cb7fb4d197e49d6c07d37b2f7ec14a11c880/magnum/conductor/handlers/common/cert_manager.py#L59-L6408:58
*** sfilatov has quit IRC09:00
*** sfilatov has joined #openstack-containers09:01
*** sfilatov has quit IRC09:04
*** yasemin has joined #openstack-containers09:06
*** sfilatov has joined #openstack-containers09:09
*** ktibi has joined #openstack-containers09:13
*** sfilatov has quit IRC09:15
*** salmankhan has joined #openstack-containers09:17
*** sfilatov has joined #openstack-containers09:23
*** sfilatov has quit IRC09:23
*** sfilatov has joined #openstack-containers09:24
*** sfilatov has quit IRC09:24
*** sfilatov has joined #openstack-containers09:26
*** parasitid has quit IRC09:26
*** sfilatov has quit IRC09:26
*** AlexeyAbashkin has quit IRC09:27
*** AlexeyAbashkin has joined #openstack-containers09:30
*** udesale_ has joined #openstack-containers09:30
*** dardelean has joined #openstack-containers09:31
*** udesale__ has joined #openstack-containers09:32
*** udesale has quit IRC09:33
*** udesale_ has quit IRC09:34
*** ktibi has quit IRC09:37
*** sfilatov has joined #openstack-containers09:37
*** lpetrut_ has joined #openstack-containers09:38
*** ktibi has joined #openstack-containers09:38
*** lpetrut has quit IRC09:39
*** sfilatov has joined #openstack-containers09:40
*** parasitid has joined #openstack-containers09:41
*** mgoddard has quit IRC09:48
*** sfilatov has quit IRC09:50
*** sfilatov has joined #openstack-containers09:51
*** sfilatov has quit IRC09:52
*** sfilatov has joined #openstack-containers09:57
*** sfilatov has joined #openstack-containers09:59
*** sfilatov has joined #openstack-containers10:00
*** sfilatov_ has joined #openstack-containers10:03
*** sfilatov has quit IRC10:03
*** gyankum has quit IRC10:03
*** sfilatov_ has quit IRC10:06
*** sfilatov has joined #openstack-containers10:06
*** sfilatov has quit IRC10:07
*** mgoddard has joined #openstack-containers10:08
*** sfilatov has joined #openstack-containers10:08
*** sfilatov has quit IRC10:09
*** zhubingbing has joined #openstack-containers10:13
*** sfilatov has joined #openstack-containers10:14
*** zhubingbing has quit IRC10:19
*** ktibi has quit IRC10:28
*** udesale__ has quit IRC10:36
*** udesale__ has joined #openstack-containers10:36
*** openstackgerrit has joined #openstack-containers10:41
openstackgerritPiotr Mrowczynski proposed openstack/magnum master: Strip signed certificate  https://review.openstack.org/57055710:41
*** AlexeyAbashkin has quit IRC10:44
*** sfilatov has quit IRC10:49
*** sfilatov has joined #openstack-containers10:58
*** sfilatov has quit IRC10:59
*** sfilatov has joined #openstack-containers10:59
*** olivenwk has joined #openstack-containers11:16
*** AlexeyAbashkin has joined #openstack-containers11:25
*** mikal has quit IRC11:26
*** udesale__ has quit IRC11:31
*** fragatina has quit IRC11:34
*** mikal has joined #openstack-containers11:43
*** parasitid has quit IRC11:58
*** zhubingbing has joined #openstack-containers12:15
*** parasitid has joined #openstack-containers12:16
*** zhubingbing has quit IRC12:20
*** ktibi has joined #openstack-containers12:23
strigazisfilatov: Do you have a proposed implementaion in mind? How to move the cert_manager? Add it to the driver interface?12:24
sfilatovstrigazi: Yes, something like this. Now we call cert_manager in cluster_conductor handler. I suggest we move it out to the driver interface12:30
sfilatovstrigazi: But I haven't really looked into it the implementation yet.12:31
sfilatovstrigazi: I'd like to know if magnum community is okay with this12:32
strigazisfilatov: There two things that you descibe. One is the key to sign the token and one is the difference in the client certs12:48
sfilatovstrigazi: Yes, I meant that both this features require cert_manager driver-specific enhancements12:56
sfilatovstrigazi: Right now we have admin and system:masters as common and organization name which has no point for drivers other than k8s12:57
sfilatovstrigazi: And we need some methods to generate keypair for signing tokens12:58
sfilatovstrigazi: I though we could have this method for Kubernetes cert_manager class12:59
strigazisfilatov: for the client cert ok12:59
strigazisfilatov: but for the second certificate, where is it going to be stored?12:59
strigazisfilatov: unless it is not stored at all13:00
strigazisfilatov: and lives only as a heat param13:00
sfilatovThat is an open case13:01
sfilatovWe do need to have it somewhere so we could properly scale a cluster13:02
strigazisfilatov: if it is in heat, it will be there13:02
strigazisfilatov: it won't get lost13:02
strigazisfilatov: scaling would work13:02
sfilatovYeah, but can we trust heat on storing it as a parameter13:03
sfilatovsince it is a secret for out cluster13:03
strigazisfilatov: if we don't pass it with heat, the magnum API needs to be extended13:03
sfilatovhmm13:04
sfilatovstrigazi: what kind of functionality?13:06
strigazisfilatov: at the moment we get the ca from the cluster13:06
sfilatovstrigazi: yes13:06
strigazisfilatov: at the moment we get the ca from the API13:06
strigazisfilatov: and we send cert requests for magnum to sign13:07
sfilatovstrigazi: yeah I see why we do that13:08
strigazisfilatov: we will need one more api request for the magnum api to be accepted13:08
strigazisfilatov: give me the private key to sign token13:09
sfilatovstrigazi: I'll get back to you in half an hour. Glad we could finally discuss this :)13:09
strigaziok13:11
*** sfilatov has quit IRC13:15
*** gyankum has joined #openstack-containers13:25
*** sfilatov has joined #openstack-containers13:34
sfilatovstrigazi: >give me the private key to sign token13:35
sfilatovstrigazi: is there a use case for this?13:35
sfilatovstrigazi: all I know is that you pass this to controller-manager and api server13:35
sfilatovstrigazi: So controller-manager would sign the token13:36
strigazisfilatov: yes but we need the same key in all masters13:38
sfilatovstrigazi: I thought we could store the keypair the same way we store ca and client cert13:40
sfilatovstrigazi: so we could retrieve it anytime we need it13:40
sfilatovstrigazi: Or are you referring to an API to retrieve so we could call it from cluster nodes?13:41
strigazisfilatov: this ^^13:41
*** gsimondon has quit IRC13:42
sfilatovstrigazi: what benefits do we have in API in comparison to passing it through heat?13:42
sfilatovstrigazi: Security?13:42
strigazisfilatov: security only. All the others are cons13:43
strigazisfilatov: slower, since the nodes will do api calls,13:43
strigazisfilatov: heat provides a way to encrypt the data in the db already13:44
strigazisfilatov: and we also pass the trustID with heat which has the same level of security concern13:44
strigazisfilatov: it sounds like passing it with heat is ok13:45
sfilatovstrigazi: Yes, I guess that's the way13:45
strigazisfilatov: a concern that I have is13:46
strigazisfilatov: at the moment openstack doesn't have scoped tokens13:46
strigazisfilatov: so the trust ID has maximum access in the project. certs and openstack APIs13:47
strigazisfilatov: I'm not sure if it a security improvement to introduce a new keypair instead if the ca.key when the trustID is in the cluster.13:48
strigazisfilatov: even without the trustID, with the trustee user and pass, one can access the magnum api which means admin access to the cluster.13:50
sfilatovstrigazi: I see your point. But one cannot get the ca.key even with all the trust info13:51
strigazisfilatov: no he can't but he can access the kube api as admin13:51
sfilatovstrigazi: Well basically I agree with you. We expose quite a lot of sensitive information. So there's no point in doing so many code changes for that13:55
*** olivenwk has quit IRC13:55
sfilatovstrigazi: but in this case we need to always expose ca.key13:55
sfilatovstrigazi: I'll commit this change and we can get to this topic with others later13:57
*** olivenwk has joined #openstack-containers13:58
*** openstacking_123 has joined #openstack-containers13:58
strigazisfilatov: I would create a new keypair and pass with jeat14:00
*** ykarel is now known as ykarel|away14:00
strigazisfilatov: I would create a new keypair and pass with heat14:00
strigazisfilatov: I would create a new keypair and pass it with heat :)14:01
*** olivenwk has quit IRC14:12
brtknrWhat do I need to do to get magnum working on devstack?14:16
*** zhubingbing has joined #openstack-containers14:17
brtknrWith all the default settings, I can get magnum to spawn VMs but they fail to start any of the kubernetes services during cloud-init14:19
*** AlexeyAbashkin has quit IRC14:19
brtknrBtw, it works fine on swarm-mode, only kubernetes fails14:19
brtknrIf this is a known issue, what is the recommended way to test new features for magnum?14:20
*** zhubingbing has quit IRC14:22
strigazibrtknr where it fails for kubernetes?14:23
brtknrstrigazi: all the kube*.service fail to start after configuring kube14:33
strigazibrtknr: journalctl -u kube-apiserver --no-pager14:33
brtknrthe thing is, the service does not exist because kubernetes is not installed inside my image14:34
*** armaan has joined #openstack-containers14:35
brtknr(or it fails to install)14:36
strigazicat /var/log/cloud-init-output.log14:39
brtknri checkout out the master branch and am currently running ./stack.sh so may be a little while, one sec14:40
*** armaan has quit IRC14:42
brtknrcurrently on part-00714:50
brtknrcloud-init-output says configuring kubernetes (master)14:51
*** AlexeyAbashkin has joined #openstack-containers14:56
brtknr... for the last 10 mins14:59
brtknrhttp://paste.openstack.org/show/721984/15:01
brtknractually, now it failed as before15:01
brtknrthat is my cloud-init-output.log15:01
brtknrlooks like it is timing out15:01
openstacking_123anyone now good way to figureout exactly what part of a cloud init script is throwing a warnig ? for example util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/part-005 [1] ? If I just manually execute the script using sh -x I don't see any issue.15:01
openstacking_123Trying to figure out if I need to execute the script using some util.py function to recreate the error?15:02
*** yamamoto has quit IRC15:02
brtknrhere's my cluster template and cluster create commands: http://paste.openstack.org/show/721985/15:04
openstacking_123brtknr are you on pike?15:05
brtknropenstacking_123: cat /var/log/cloud-init.log15:05
brtknropenstacking_123: no i am testing rocky15:05
openstacking_123Aww alright15:06
openstacking_123Was going to say switch to 26 if on pike15:06
brtknropenstacking_123: what do you mean switch to 26?15:06
brtknropenstacking_123: ahhh atomic?15:06
brtknri have managed to get k8s working on 27 on a different cluster, its just failing on devstack15:07
openstacking_123brtknr interesting15:07
brtknrbut the other cluster has openstack pike but magnum queens15:07
*** parasitid has quit IRC15:07
brtknrhttps://www.stackhpc.com/magnum-queens.html15:08
openstacking_123brtknr I think our issues are similar I none of my services start I think all related to ssl15:08
openstacking_123Im using openstack ansible pike15:08
brtknri see, we use kayobe to deploy openstack15:09
openstacking_123brtknr is your ssl dir populated ?15:09
brtknrinside the instance?15:09
strigazibrtknr do you have access to docker hub from the vm15:09
strigazi?15:09
openstacking_123yeah15:10
brtknrstrigazi: as in sudo docker ps?15:10
openstacking_123brtknr all my stuff fails [0;1;31mFAILED[0m] Failed to start kubernetes-kubelet. seemed related to tls not generating15:11
brtknrstrigazi: ping hub.docker.com is not responsive15:11
strigazibrtknr: try do docker pull docker.io/openstackmagnum/kubernetes-apiserver:v1.9.315:11
strigazibrtknr: this is the problem15:12
ykarel|awaystrigazi++15:12
strigazibrtknr: or this skopeo inspect docker://docker.io/openstackmagnum/kubernetes-apiserver:v1.9.315:13
brtknrlooks that that is the problem!15:13
ykarel|awaystrigazi, skopeo installed in vm?15:13
brtknri have no access to docker hub15:14
ykarel|awayin atomic vm15:14
strigaziykarel|away: yes15:14
ykarel|awayokk good15:14
strigaziatomic uses skopeo15:14
ykarel|awayohh good, didn't knew that15:14
* ykarel|away leaving15:15
brtknrstrigazi: do i need to do something special to configure instances to have access to docker hub15:15
strigaziopenstacking_123: pike needs fedora 26 it doesn15:16
strigaziopenstacking_123: pike needs fedora 26 it doesn't work with newer versions15:16
openstacking_123strigazi thanks for confirming15:16
strigazibrtknr: cluster template create --dns-nameserver <a dns that works>15:16
strigazibrtknr: that works for your cloud15:16
strigazibrtknr: or mirror all containers somewhere that the vms can pull from15:17
openstacking_123strigazi would you be kind enough to check out this error on part-0005 https://gist.githubusercontent.com/fritzstauff/3c296c03612108f3c8a54f1bde9a84cd/raw/ed4d58cdaf63c086f7fd581599d3033041060f1c/magnum%2520error15:19
*** ykarel|away has quit IRC15:19
strigaziopenstacking_123: more lines?15:20
openstacking_123Thats it15:20
strigaziwhich file is this?15:20
openstacking_123strigazi /var/log/cloud-init.log15:21
strigaziopenstacking_123 /var/log/cloud-init-output.log15:21
openstacking_123examining  /usr/lib/python3.6/site-packages/cloudinit/util.py", line 80215:21
openstacking_123Seems related to ssl15:21
*** chhagarw has quit IRC15:22
openstacking_123strigazi https://gist.github.com/fritzstauff/3c296c03612108f3c8a54f1bde9a84cd updated with comment15:23
*** iranzo has quit IRC15:23
*** parasitid has joined #openstack-containers15:26
brtknrstrigazi: i can ping 8.8.8.8 from the master node and my dns_nameserver is currently set to 8.8.8.815:26
*** pcaruana|call| has quit IRC15:27
brtknralthough my /etc/resolv.conf has nameserver set to 10.0.0.2 despite the fact that my cluster template has dns nameserver as 8.8.8.815:31
strigaziopenstacking_123 what is the file /var/lib/cloud/instance/scripts/part-005 ?15:31
strigaziopenstacking_123: the make-cert one?15:32
openstacking_123Yes sir15:32
strigazican you execute it from the node?15:32
strigazish -x /var/lib/cloud/instance/scripts/part-00515:32
strigazibrtknr in my env at cern this doesn't work either for devstack, I need to set our internal dns15:33
openstacking_123I think I am actually missing a python package15:34
openstacking_123Could be testing wrong but on my atomic host util.py15:34
openstacking_123ImportError: No module named yaml15:34
openstacking_123When manually run just using system python15:35
strigaziopenstacking_123 kubernetes or swarm-mode?15:35
strigaziwhich coe?15:35
openstacking_123Kubernetes15:35
strigaziatomic host status15:35
openstacking_123If I execute part-005 by hand no errors15:35
openstacking_123Version: 26.157 (2017-10-29 14:42:37)15:36
openstacking_123Commit: c099633883cd8d06895e32a14c63f6672072430c151de882223e4abe20efa7ca15:36
openstacking_123 GPGSignature: Valid signature by E641850B77DF435378D1D7E2812A6B4B64DAB85D15:36
strigaziwhich command exactly fail when you run /var/lib/cloud/instance/scripts/part-005 ?15:37
openstacking_123No idea since the log just refernce util.py lines that fail15:38
openstacking_123util.py", line 80215:38
strigazi. /etc/sysconfig/heat-paras15:39
strigazicurl $MAGNUM_URL15:39
strigazi. /etc/sysconfig/heat-params15:39
strigazicurl $MAGNUM_URL15:39
openstacking_123https://gist.githubusercontent.com/fritzstauff/3c296c03612108f3c8a54f1bde9a84cd/raw/0cf5034dd3be598279ca3ce64622a31d37aad86f/Magnum%2520details15:41
strigaziopenstacking_123: did you run this cmd:15:42
strigazish -x /var/lib/cloud/instance/scripts/part-00515:43
openstacking_123yup15:43
openstacking_123no bad output15:43
openstacking_123will test again15:43
openstacking_123install gcc so I can try adding that python yaml module as well15:43
strigazigive me all the output, I don't get where it fails, in which call15:43
brtknrstrigazi: thank you! all i had to do in the end was `openstack subnet set private-subnet --dns-nameserver 8.8.8.8` then reboot the instance15:43
strigaziopenstacking_123: that is not the point, you don't need to add anything15:44
openstacking_123strigazi will cancel15:44
strigaziI don't understand if it manages to get the ca from the magnum api15:46
openstacking_123Output https://gist.githubusercontent.com/fritzstauff/dc7568f395f6a80cacdf9498b00c815e/raw/831a3f90c24e5bf278d9ca8cc1f4b8c5aea43e5f/part-00515:46
openstacking_123strigazi ^15:46
strigaziopenstacking_123: it can not get a token from keystone15:47
strigaziopenstacking_123: http://paste.openstack.org15:49
openstacking_123strigazi Thank you! Can I think that past url is missing the end part?15:53
strigazidid that curl call work?15:55
openstacking_123Nope!15:56
openstacking_123strigazi recource not found15:57
openstacking_123Must be an issue with my public endpoint15:57
openstacking_123Thank you so much will report back soon15:57
openstacking_123going to test on internal endpoint15:57
openstacking_1233 days of off and on troubleshooting!15:58
openstacking_123same issue on internal guess I will need to double check my keystone / magnum integration16:01
*** yamamoto has joined #openstack-containers16:06
*** yamamoto has quit IRC16:10
*** mjura has quit IRC16:11
*** zhubingbing has joined #openstack-containers16:19
*** zhubingbing has quit IRC16:23
openstacking_123strigazi any idea where it is populating the token url? After some testing it all works if the url is 5000/v3/auth/tokens instead of :5000/auth/tokens16:24
*** salmankhan has quit IRC16:25
*** cliles has quit IRC16:27
*** cliles has joined #openstack-containers16:27
strigaziopenstacking_123: http://git.openstack.org/cgit/openstack/magnum/tree/magnum/drivers/common/templates/kubernetes/fragments/make-cert.sh?h=stable%2Fpike#n9616:30
openstacking_123strigazi seems like if I add v3 to my keytone endpoint it will work then16:33
openstacking_123Its odd because I have a working version that does not have that16:33
*** ramishra has quit IRC16:44
*** yamamoto has joined #openstack-containers16:50
*** fragatina has joined #openstack-containers16:54
*** mgoddard has quit IRC16:59
*** yamamoto has quit IRC17:00
*** lpetrut__ has joined #openstack-containers17:17
*** mgoddard has joined #openstack-containers17:20
*** lpetrut_ has quit IRC17:21
*** janki has quit IRC17:31
*** pcaruana has joined #openstack-containers17:35
*** iranzo has joined #openstack-containers17:39
*** iranzo has joined #openstack-containers17:39
*** sfilatov has quit IRC17:59
*** sfilatov has joined #openstack-containers18:05
*** gyankum has quit IRC18:07
*** AlexeyAbashkin has quit IRC18:10
*** iranzo has quit IRC18:12
*** pcaruana has quit IRC18:14
*** lpetrut__ has quit IRC18:14
*** zhubingbing has joined #openstack-containers18:20
*** zhubingbing has quit IRC18:25
*** mgoddard has quit IRC18:31
*** mikal has quit IRC18:34
*** mikal has joined #openstack-containers18:34
*** fragatina has quit IRC18:59
*** lpetrut__ has joined #openstack-containers19:08
*** pcichy has quit IRC19:12
*** sfilatov has quit IRC19:15
*** sfilatov has joined #openstack-containers19:16
*** sfilatov has quit IRC19:17
*** sfilatov has joined #openstack-containers19:18
*** pcichy has joined #openstack-containers19:19
*** sfilatov has quit IRC19:23
*** lpetrut__ has quit IRC19:35
*** sfilatov has joined #openstack-containers20:07
*** sfilatov has quit IRC20:12
*** harlowja has joined #openstack-containers20:16
*** ktibi has quit IRC20:26
*** dardelean has quit IRC20:32
*** yolanda has quit IRC20:34
*** fragatina has joined #openstack-containers20:43
*** fragatin_ has joined #openstack-containers20:44
*** fragatin_ has quit IRC20:44
*** fragatina has quit IRC20:44
*** fragatina has joined #openstack-containers20:44
*** fragatina has quit IRC20:45
*** fragatina has joined #openstack-containers20:46
*** fragatina has quit IRC20:46
*** fragatina has joined #openstack-containers20:47
*** fragatina has quit IRC20:47
*** fragatina has joined #openstack-containers20:47
*** zhubingbing has joined #openstack-containers21:22
*** zhubingbing has quit IRC21:27
*** pcichy has quit IRC21:43
*** flwang1 has joined #openstack-containers21:52
*** harlowja has quit IRC22:02
*** openstacking_123 has quit IRC22:14
*** openstacking_123 has joined #openstack-containers23:20
*** zhubingbing has joined #openstack-containers23:24
*** pcichy has joined #openstack-containers23:25
*** zhubingbing has quit IRC23:29
*** openstacking_123 has quit IRC23:39
*** kbyrne has quit IRC23:52
*** kbyrne has joined #openstack-containers23:56

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