*** caoyuan has joined #openstack-qinling | 00:40 | |
*** huntxu has joined #openstack-qinling | 01:16 | |
*** jiangyuan has joined #openstack-qinling | 01:35 | |
*** caoyuan has quit IRC | 02:33 | |
*** caoyuan has joined #openstack-qinling | 03:11 | |
*** caoyuan has quit IRC | 03:16 | |
*** caoyuan has joined #openstack-qinling | 04:17 | |
*** kevinz has quit IRC | 05:05 | |
*** rakhmerov has joined #openstack-qinling | 05:54 | |
openstackgerrit | Hunt Xu proposed openstack/qinling master: tests: add unit tests covering qinling.orchestrator https://review.openstack.org/550014 | 07:16 |
---|---|---|
openstackgerrit | zhongshengping proposed openstack/qinling master: Follow the new PTI for document build https://review.openstack.org/550374 | 07:35 |
openstackgerrit | zhongshengping proposed openstack/qinling master: Don't run tempest jobs when patching unit test and releasenote https://review.openstack.org/550376 | 07:37 |
*** celebdor has joined #openstack-qinling | 10:12 | |
*** celebdor is now known as apuimedo | 10:12 | |
apuimedo | kong: Hi! I'm apuimedo from Kuryr | 10:12 |
apuimedo | yesterday I was checking the outreachy projects (I was a mentor this past cycle) and I saw that you have a project listed there | 10:13 |
apuimedo | never having heard of qinling before I checked your repo | 10:13 |
apuimedo | and I saw that you have some devstack support for deploying kubernetes | 10:13 |
apuimedo | we also have that and we were in process of splitting it out to a separate devstack plugin | 10:14 |
apuimedo | so it would live in git.openstack.org/openstack/devstack-plugin-kubernetes | 10:14 |
apuimedo | I was wondering if you'd be interested in collaborating with that | 10:14 |
kong | apuimedo: hi | 10:21 |
kong | yes, i have a very ugly ansible script for installing k8s | 10:21 |
kong | using kubeadm | 10:21 |
kong | :-) | 10:21 |
kong | i'm willing to help when i'm available | 10:22 |
apuimedo | kong: so here's what I propose | 10:23 |
apuimedo | your playbooks are based on kubeadm | 10:23 |
kong | apuimedo: any doc for now for that devstack plugin? | 10:23 |
kong | yeah | 10:23 |
apuimedo | my bash is based hyperkube | 10:23 |
apuimedo | so yesterday, before I saw your ansible, I had started doing a kubeadm based devstack plugin | 10:24 |
apuimedo | so how about we create the project | 10:24 |
apuimedo | we put some kuryr and qinling folks as cores | 10:24 |
apuimedo | probably you and me as starters | 10:24 |
kong | apuimedo: sounds like a plan :-) | 10:24 |
apuimedo | I would personally prefer not to require ansible, if you're okay with that | 10:24 |
apuimedo | So the target I have is kubeadm installation with multinode devstack support | 10:25 |
apuimedo | and if you see I miss something for your use cases | 10:25 |
apuimedo | we can add that as well | 10:25 |
kong | apuimedo: ok | 10:25 |
apuimedo | cool | 10:25 |
kong | btw, there is another project called kubespray which is also aimed at installing k8s | 10:25 |
kong | but it's also using ansible | 10:25 |
kong | anyway, let's see what we could do for the integration with devstack | 10:26 |
apuimedo | I heard of kubespray but I've never tried it | 10:26 |
apuimedo | what do you think about it? | 10:26 |
apuimedo | and how well would it interact with devstack? | 10:27 |
kong | it's ansible playbook that install k8s on various cloud, e.g. aws, google, azure, and of course, openstack | 10:27 |
apuimedo | that assumes an openstack deployment and it would use nova instances, right? | 10:28 |
apuimedo | I think it would be more for the baremetal target | 10:28 |
kong | yep | 10:28 |
apuimedo | since I suppose qinling does not need nova instances | 10:28 |
apuimedo | does it? | 10:28 |
apuimedo | which openstack components do you use? | 10:29 |
kong | no, it doesn't. | 10:29 |
kong | hah, actually, the basic installation only needs keystone | 10:29 |
apuimedo | I saw in devstack you have rabbit, mysql and keystone | 10:29 |
apuimedo | so I suppose keystone is the main thing | 10:29 |
kong | in future, swift, aodh, ceilometer, etc. | 10:29 |
kong | that's right for now | 10:29 |
apuimedo | swift for the k8s registry? | 10:29 |
apuimedo | I'm not familiar with aodh | 10:30 |
kong | nope, for object creation/update notification | 10:30 |
kong | which will trigger qinling functions | 10:30 |
apuimedo | ah, interesting | 10:30 |
apuimedo | that's really cool | 10:30 |
kong | aodh for event trigger | 10:30 |
kong | they are all needed for qinling's functional test in future | 10:30 |
apuimedo | kong: are you gonna do that with tempest? | 10:31 |
kong | yeah, will be inside qinling-tempest-plugin | 10:32 |
kong | apuimedo: btw, i have a question for kuryr | 10:32 |
kong | does kuryr support multi-tenancy? | 10:32 |
kong | i mean, when you create pods, do all the pods connect to a same subnet which belongs to a same tenant? | 10:33 |
kong | from kuryr's config file? | 10:33 |
apuimedo | nice | 10:34 |
apuimedo | :-) | 10:34 |
apuimedo | is there some blog post of doing some example work with qinling | 10:34 |
apuimedo | like a sample function and so on | 10:35 |
apuimedo | kong: usually, for k8s+kuryr deployments, you make one k8s cluster per kuryr deployment | 10:35 |
apuimedo | so it works with k8s namespaces and with openshift projects | 10:36 |
apuimedo | but openstack tenant wise | 10:36 |
apuimedo | we usually work on behalf of a single tenant | 10:36 |
kong | ok, i got you | 10:36 |
kong | apuimedo: for your question, currently, you can refer to qinling's ugly doc https://docs.openstack.org/qinling/latest/ | 10:36 |
apuimedo | so yes, all the pods to the same tenant | 10:36 |
apuimedo | not necessarily on the same subnet | 10:36 |
*** lenka has joined #openstack-qinling | 10:37 | |
kong | and a video from Sydney Summit https://youtu.be/NmCmOfRBlIU a live demo inside | 10:37 |
apuimedo | we'll add a multi subnet driver this cycle | 10:37 |
kong | cool | 10:37 |
apuimedo | but until k8s has more multi tenancy support, that's all | 10:37 |
apuimedo | thanks for the video kong! | 10:38 |
kong | apuimedo: another youtube video(which was recorded very earlier) https://youtu.be/K2SiMZllN_A | 10:38 |
kong | apuimedo: np | 10:38 |
apuimedo | kong: I'll ping you once I make some initial version of the devstack plugin | 10:38 |
apuimedo | so you can give a review before we create it in openstack | 10:39 |
apuimedo | hopefully next week | 10:39 |
kong | apuimedo: lovely | 10:39 |
*** huntxu has quit IRC | 10:46 | |
*** huntxu has joined #openstack-qinling | 10:46 | |
*** huntxu has quit IRC | 10:56 | |
*** huntxu has joined #openstack-qinling | 10:57 | |
*** huntxu has quit IRC | 10:57 | |
*** huntxu has joined #openstack-qinling | 10:58 | |
*** hunt_ has joined #openstack-qinling | 11:01 | |
*** huntxu has quit IRC | 11:03 | |
*** lenka has quit IRC | 11:19 | |
openstackgerrit | Merged openstack/qinling master: Don't run tempest jobs when patching unit test and releasenote https://review.openstack.org/550376 | 12:09 |
*** hunt_ has quit IRC | 12:19 | |
*** huntxu has joined #openstack-qinling | 12:20 | |
*** caoyuan has quit IRC | 12:20 | |
openstackgerrit | Merged openstack/qinling master: Follow the new PTI for document build https://review.openstack.org/550374 | 12:39 |
*** jiangyuan has quit IRC | 12:41 | |
*** caoyuan has joined #openstack-qinling | 13:28 | |
*** huntxu has quit IRC | 13:54 | |
*** caoyuan has quit IRC | 17:03 | |
*** apuimedo has quit IRC | 17:49 | |
*** celebdor has joined #openstack-qinling | 17:50 | |
*** celebdor has quit IRC | 18:29 | |
*** celebdor has joined #openstack-qinling | 18:55 | |
*** openstackstatus has quit IRC | 22:13 | |
*** openstack has joined #openstack-qinling | 22:16 | |
*** ChanServ sets mode: +o openstack | 22:16 | |
*** openstackstatus has quit IRC | 22:42 | |
*** openstack has joined #openstack-qinling | 22:45 | |
*** ChanServ sets mode: +o openstack | 22:45 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!