Monday, 2018-10-29

openstackgerritJake Yip proposed openstack/magnum-ui master: fix text for master flavor / node flavor  https://review.openstack.org/61382101:16
*** jaewook_oh has joined #openstack-containers01:55
*** jaewook_oh has quit IRC02:10
*** hongbin has joined #openstack-containers02:24
openstackgerritFeilong Wang proposed openstack/magnum master: Add server group for cluster worker nodes  https://review.openstack.org/61382502:40
openstackgerritFeilong Wang proposed openstack/magnum master: Add server group for cluster worker nodes  https://review.openstack.org/61382502:42
*** Nel1x has joined #openstack-containers02:45
*** jaewook_oh has joined #openstack-containers02:59
*** Nel1x has quit IRC03:09
openstackgerritMerged openstack/magnum-ui master: fix text for master flavor / node flavor  https://review.openstack.org/61382103:09
*** Nel1x has joined #openstack-containers03:09
openstackgerritMerged openstack/magnum stable/queens: Fix the heat-container-agent docker image  https://review.openstack.org/61344103:29
*** ramishra has joined #openstack-containers03:32
*** udesale has joined #openstack-containers03:54
*** janki has joined #openstack-containers04:34
*** Nel1x has quit IRC04:47
*** hongbin has quit IRC04:52
*** Bhujay has joined #openstack-containers05:46
*** ykarel has joined #openstack-containers06:03
*** Bhujay has quit IRC06:15
*** ramishra has quit IRC06:18
*** ramishra has joined #openstack-containers06:32
*** ykarel is now known as ykarel|lunch07:34
*** pcaruana has joined #openstack-containers07:46
*** lpetrut has joined #openstack-containers07:49
*** pvradu has joined #openstack-containers08:04
*** pvradu has quit IRC08:06
*** pvradu has joined #openstack-containers08:06
openstackgerritinspurericzhang proposed openstack/magnum-tempest-plugin master: [Trivial Fix] update home-page url  https://review.openstack.org/61385908:28
*** ykarel|lunch is now known as ykarel08:40
*** mattgo has joined #openstack-containers08:53
*** flwang1 has joined #openstack-containers09:29
flwang1strigazi: around for a sync?09:29
strigaziflwang1: yes, can you also have a quick look to https://review.openstack.org/#/c/612727/409:45
flwang1strigazi: sure, looking now09:47
flwang1strigazi: it looks good for me09:49
flwang1strigazi: do you want to address ricardo's comment?09:49
flwang1i think we have discussed that before09:49
strigaziflwang1: I replied. The only version atm is magnum's version. What we have a magnum tag we can put the version and commit.09:50
flwang1comparing with a number version, personally, i prefer using 'release-dev/stable' for reasons: 1. number version is hard to remember and maintain09:50
strigaziflwang1: it is definately for another patch.09:50
flwang1strigazi: ok09:51
flwang1strigazi: i have a question about this https://gitlab.cern.ch/cloud/atomic-system-containers/blob/cern-qa/.gitlab-ci.yml#L5209:51
flwang1why do you need a special image here?09:52
strigazithere is nothing special about this image09:52
strigazibut you need some image09:52
strigazithat has the docker client09:52
strigazionly the client09:52
strigaziflwang1: makes sense?09:53
flwang1so technically, i just need an image including docker client?09:53
strigaziamm, you don't need any image. If you just copy the script section to a bash script you can run it anywhere09:54
strigazieg in your laptop09:55
flwang1strigazi: ok, cool. what's this line for https://gitlab.cern.ch/cloud/atomic-system-containers/blob/cern-qa/.gitlab-ci.yml#L54 ?09:55
flwang1it downloads the kubelet binary, but i can't see it's used anywhere09:55
strigazithe apiserver system container needs to expose kubectl to the host. in the containers from gcr.io the apiserver container doesn't contain kubectl09:56
*** salmankhan has joined #openstack-containers09:57
flwang1strigazi: ok, good to know09:58
flwang1strigazi: i can see from line 70-109, it's trying to push the image to gitlab-registry.cern.ch, so if i just want to build the image and reuse the gitlab registry, i don't need the job from line 70, right?10:01
strigazithe second job is to tag the image with the version. The first job tags and pushed with the commit id as the image tag10:02
strigaziso yes to your question.10:02
flwang1strigazi: cool10:03
strigaziflwang1: locally I'm using smth like this https://paste.fedoraproject.org/paste/qRjftn4U6TIHFWnUV1vnkw/raw10:03
flwang1strigazi: haha, that's the magic script i wanna ask10:04
flwang1because each time when i asked for new images, you can build then in minutes10:04
strigaziflwang1: it took me sometime to figure that you needed this.10:04
flwang1so i believe there are some magic10:04
flwang1strigazi: sorry for the confusing, actually, i need both10:05
flwang1we do need a formal pipeline to build those images, and I also want to know the handy, informal way10:06
strigaziflwang1: we just need to finish this https://review.openstack.org/#/c/585420/, to add the publish job10:07
flwang1strigazi: anything else we need?10:08
flwang1how can i know if it's working or not from the jobs of jenkins?10:08
strigaziI'm pushing the enable_tiller label and we need some input for the nodegroups spec.10:09
strigazihow can i know if it's working or not from the jobs of jenkins? Not sure what do you mean10:09
flwang1for this one  https://review.openstack.org/#/c/585420/10:13
flwang1i think it will automatically build k8s images and push to openstackmagnum repo, no?10:14
strigazion push it will test if the containers are getting built10:14
strigazion merge it will push to docker.io10:14
flwang1but at this moment, how can i know if the patch is working?10:16
flwang1how can i check the jobs' log to make sure that?10:16
strigazithey where here: http://logs.openstack.org/20/585420/16/check/magnum-container-build-base/8fd5cf8/10:17
strigaziif the built is done the playbook will be green10:18
strigazione sec10:18
flwang1no urgent10:25
flwang1so we still need to merge the tiller first? i was confused10:25
openstackgerritSpyros Trigazis proposed openstack/magnum master: WIP: build images in the ci  https://review.openstack.org/58542010:28
strigaziflwang1: we can see now the result of the build ^^10:29
flwang1strigazi: cool, if it passed, can we say this patch is ready to go?10:29
flwang1i mean ready for merging?10:29
strigaziflwang1: I'll revert this https://review.openstack.org/#/c/585420/17/.zuul.yaml I put it there to not run things that we don't need.10:30
strigaziflwang1: I just need one more playbook to pusblish10:30
flwang1ok, just add a comment and @ me if it's ready to go10:31
strigazitiller and nodegroups are separate tasks but important :)10:31
flwang1no problem10:31
flwang1but i probably don't have time until summit10:31
flwang1i will leave on Friday10:31
strigaziOK10:31
flwang1do you still have a moment for a feature request?10:34
strigazisure10:34
flwang1do you remember the overlay2 + docker_volume_size issue?10:34
flwang1now user have to let docker share the root disk of the node10:35
strigaziok10:35
flwang1but if the root disk of flavor is small, then user may run out of disk soon10:36
flwang1because in Magnum, we're booting VM based on image and doesn't create new volume10:36
flwang1so the feature request is, could we create new volume when booting node and set the size based on a label passed by user10:37
strigaziflwang1: you mean a new lvm in the vm?10:39
flwang1in nova, when user boot a server10:39
flwang1on dashboard, you can select boot from image, volume, volume snapshot, etc10:40
flwang1when select boot from  image, user can set create a new volume or not10:40
flwang1if user select boot from image and create a new volume, then nova will create a new volume firstly and copy the image to that volume, and set the volume size based on user input10:41
flwang1back to the problem10:42
flwang1if you already got a flavor with big root disk size, that's not a problem10:42
flwang1because nova can use that big size10:43
flwang1but for public cloud, generally, the default root disk size in flaovr is 10Gb10:43
flwang1like us, we have 10Gb10:43
flwang1as the root disk size10:43
flwang1which is not enough for sharing between docker and the OS10:44
flwang1does that make sense for you?10:44
tobias-urdinsame here 10gb :) strigazi there is about 10 patches pending release for rocky, could we release 7.0.2? seems like there is atleast one fix still open https://review.openstack.org/#/q/project:openstack/magnum+branch:stable/rocky+is:open10:44
strigazihttps://review.openstack.org/#/c/612791/2 +210:46
strigazihttps://review.openstack.org/#/c/603603/ not needed10:46
strigazitobias-urdin: ^^10:46
strigaziflwang1 ok, so you need to have an external volume for docker storage, correct?10:47
flwang1strigazi: no10:47
flwang1no external volume because it won't work for overlay210:47
strigaziflwang1:  ok10:47
flwang1i just want to create a big root disk10:47
strigaziflwang1: you want boot from volume?10:48
flwang1let me explain from another view, what's the root disk size in cern's flavor?10:48
strigaziflwang1: with overlay2 the root disk and the docker storage are taking the full 10GB10:48
flwang1strigazi: yep, but that's not enough i think10:49
flwang110GB is too small10:49
strigaziflwang1: at CERN we give 2 cores 4 gb ram and 20gb as defaults for k8s10:49
flwang1and currently, there is no way to change it without changing flavor10:49
flwang1how can you create a node with 60GB disk?10:49
*** dave-mccowan has joined #openstack-containers10:51
strigaziif you need 60GB you get another flavor10:51
strigaziopenstack coe cluster create --flavor foo-with-60gb10:52
*** salmankhan has quit IRC10:52
strigaziflwang1: at least at CERN we manage this with flavors10:53
flwang1strigazi: no, not really10:53
flwang1all our flavors have same root disk size10:53
flwang1tobias-urdin: ^10:54
strigaziflwang1 so what is the proposed solution for you?10:54
*** salmankhan has joined #openstack-containers10:57
tobias-urdinflwang1: we too have 10gb for all flavors since we are relying on volumes10:57
flwang1tobias-urdin: do you understand the problem we're talking about?10:58
flwang1strigazi: pls wait a sec, i''m find some code10:58
flwang1to show you10:58
strigaziflwang1: sure, I got the problem. I never thought that all flavors would have the same disk size.10:58
openstackgerritMerged openstack/magnum master: Add heat_container_agent_tag label  https://review.openstack.org/61272710:59
flwang1because you guys are private cloud10:59
flwang1just like blizzard, they have 32GB root disk by default10:59
flwang1strigazi: https://github.com/openstack/magnum/blob/master/magnum/drivers/k8s_fedora_atomic_v1/templates/kubeminion.yaml#L48711:00
strigaziit is a matter of choice I think. In aws I can ask whatever I want for disk.11:00
strigaziyes, this is the image/11:00
flwang1just need to remove the image and create a volume based on the image before booting instance11:00
strigaziok, so boot from volume that I mentioned11:01
flwang1strigazi: ok, then yes11:01
tobias-urdini assume we are talking about the root disk being too small for something? we are relying on the extra "docker" volume for space11:01
flwang1tobias-urdin: and what's the docker_storage_driver you're using?11:01
* strigazi will be back in 3'11:01
flwang1tobias-urdin: we have seen problems with overlay2/overlay + docker_volume_size > 011:02
tobias-urdinwe are using the devicemapper driver11:04
tobias-urdini ended up doing the same as blizzard, hiding cluster templates in horizon from users to simplify the usage11:04
tobias-urdinstill can use it though11:04
flwang1tobias-urdin: ok11:10
flwang1for devicemapper, it's ok11:11
strigazitobias-urdin: flwang1: anything else before I go for lunch?11:13
flwang1strigazi: if you don't object, i'd like to propose a patch11:14
strigaziflwang1: for boot from volume?11:14
flwang1yes11:14
strigaziflwang1: if it is an opt-in feaure it is fine for me. The templates will become a bit complicated though.11:15
flwang1strigazi: ok, i can see your point, i will think about it11:16
flwang1it's not super urgent11:16
strigaziflwang1: I just want to ask, are you sure the shared file system will cope with the load.11:16
flwang1our presentation is urgent ;)11:16
strigaziflwang1: k8s will become slow11:16
*** spsurya has quit IRC11:16
flwang1you mean ceph?11:16
strigaziyes11:16
flwang1i don't know11:17
flwang1i need your experience and tobias-urdin's11:17
strigazitobias-urdin's case is a little different, it is not the full node in a volume11:17
strigaziI'll start today with the presentation. I'll ping you11:18
strigazisee you later.11:18
*** spsurya has joined #openstack-containers11:18
flwang1coo11:18
flwang1cool11:18
flwang1ttyl11:18
*** ramishra has quit IRC11:24
*** ramishra has joined #openstack-containers11:24
*** udesale has quit IRC11:26
*** jaewook_oh has quit IRC11:30
*** janki has quit IRC11:32
*** ramishra_ has joined #openstack-containers11:40
*** ramishra has quit IRC11:43
*** serlex has joined #openstack-containers11:48
strigaziflwang1: i'm back11:59
*** ppetit has joined #openstack-containers12:27
*** jmlowe has quit IRC12:34
*** udesale has joined #openstack-containers12:47
*** zul has joined #openstack-containers12:48
*** munimeha1 has joined #openstack-containers13:02
*** jmlowe has joined #openstack-containers13:22
openstackgerritSpyros Trigazis proposed openstack/magnum master: k8s_fedora: Deploy tiller  https://review.openstack.org/61233613:45
*** hongbin has joined #openstack-containers14:09
*** jmlowe has quit IRC14:16
openstackgerritMerged openstack/magnum stable/rocky: Add prometheus-monitoring namespace  https://review.openstack.org/61279114:30
*** jmlowe has joined #openstack-containers14:37
kaiokmohi everyone. I'm trying to create a k8s cluster using magnum (6.2.0, from stable/queens), but the creation does not seems to complete.14:41
kaiokmoI can see, however, that the heat stack creation is completed.14:42
kaiokmothe cluster status is stuck at "CREATE_IN_PROGRESS". nothing wrong in magnum-conductor or magnum-api logs.14:44
kaiokmoany idea from where I can track down the issue?14:45
openstackgerritMerged openstack/magnum master: Trivial code cleanups  https://review.openstack.org/60190414:45
kaiokmobtw, I'm using fedora-atomic 27 (2018_04_19)14:46
*** shrasool has joined #openstack-containers14:57
*** pvradu has quit IRC15:06
*** itlinux has quit IRC15:09
*** jmlowe has quit IRC15:14
*** mattgo has quit IRC15:19
*** ykarel is now known as ykarel|away15:20
*** jmlowe has joined #openstack-containers15:29
*** lpetrut has quit IRC15:40
*** ppetit has quit IRC15:43
*** ykarel|away has quit IRC15:43
*** jmlowe has quit IRC15:56
*** jmlowe has joined #openstack-containers15:58
*** itlinux has joined #openstack-containers16:01
*** zul has quit IRC16:14
*** shrasool has quit IRC16:15
*** ykarel|away has joined #openstack-containers16:23
*** shrasool has joined #openstack-containers16:24
openstackgerritSpyros Trigazis proposed openstack/magnum master: k8s_fedora: Deploy tiller  https://review.openstack.org/61233616:35
*** graysonh has quit IRC16:42
*** shrasool has quit IRC16:46
*** shrasool has joined #openstack-containers16:50
*** udesale has quit IRC17:00
*** jmlowe has quit IRC17:01
*** zul has joined #openstack-containers17:01
*** shrasool has quit IRC17:12
*** mattgo has joined #openstack-containers17:24
*** jmlowe has joined #openstack-containers17:37
*** salmankhan has quit IRC17:40
*** shrasool has joined #openstack-containers17:50
*** mattgo has quit IRC17:54
*** lpetrut has joined #openstack-containers17:54
*** shrasool has quit IRC17:59
*** ykarel|away has quit IRC18:17
flwang1kaiokmo: still around?18:27
flwang1kaiokmo: check this https://github.com/openstack/magnum/blob/master/magnum/conf/drivers.py#L33   make sure it's False18:28
kaiokmoflwang1: thanks. it's "default=True" for me. changing it to False now18:37
kaiokmoflwang1: is this a condition to a cluster creation to be completed or something?18:38
*** jmlowe has quit IRC18:46
kaiokmoflawn1: it worked. the cluster creation is now completed. thank you18:54
*** jmlowe has joined #openstack-containers18:55
flwang1it's a known issue18:57
*** flwang1 has quit IRC18:57
*** jmlowe has quit IRC19:08
*** lpetrut has quit IRC19:18
*** salmankhan has joined #openstack-containers19:37
*** salmankhan has quit IRC19:41
*** jmlowe has joined #openstack-containers19:46
*** ramishra_ has quit IRC20:01
*** shrasool has joined #openstack-containers21:17
*** salmankhan has joined #openstack-containers21:30
openstackgerritErik Olof Gunnar Andersson proposed openstack/magnum master: Removed admin_ setings  https://review.openstack.org/61403421:38
openstackgerritErik Olof Gunnar Andersson proposed openstack/magnum master: Removed admin_* from devstack config  https://review.openstack.org/61403421:39
*** itlinux has quit IRC21:46
*** pcaruana has quit IRC21:57
*** shrasool has quit IRC22:01
*** serlex has quit IRC22:05
*** shrasool has joined #openstack-containers22:17
*** munimeha1 has quit IRC22:23
*** shrasool has quit IRC23:03
*** salmankhan has quit IRC23:25
*** itlinux has joined #openstack-containers23:37
*** hongbin has quit IRC23:43

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