Thursday, 2017-03-16

*** vhosakot has quit IRC00:05
*** yingjun has joined #openstack-kolla00:07
*** yuanying has quit IRC00:10
*** yuanying has joined #openstack-kolla00:15
*** sbezverk has quit IRC00:21
*** japestinho has joined #openstack-kolla00:22
openstackgerritMerged openstack/kolla master: Refactor and enable shell access  https://review.openstack.org/44569000:25
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: DNM: Test of master kolla-kubernetes  https://review.openstack.org/44623700:30
sdakemasber could you expand on teh issues you ahve heard of?00:31
sdakemasber ironic is working in kolla-kubernetes with teh 4.0.0 images, although i'm not sure its been tested on kolla-ansible00:32
*** duonghq has joined #openstack-kolla00:39
duonghqmorning guys00:39
*** sayantan_ has joined #openstack-kolla00:41
*** gfidente|afk has quit IRC00:43
*** sayantani01 has quit IRC00:44
*** sayantan_ has quit IRC00:45
*** eaguilar has quit IRC00:46
openstackgerritMohammed Naser proposed openstack/kolla stable/newton: Refactor and enable shell access  https://review.openstack.org/44624900:46
*** eaguilar has joined #openstack-kolla00:47
*** sayantan_ has joined #openstack-kolla00:52
*** deadnull has quit IRC00:52
*** sambetts_ has quit IRC00:53
*** rhallisey has quit IRC00:55
*** sambetts_ has joined #openstack-kolla00:55
*** eaguilar has quit IRC00:56
*** sayantan_ has quit IRC00:56
*** sbezverk has joined #openstack-kolla00:56
*** eaguilar has joined #openstack-kolla00:58
*** zhuzeyu has quit IRC00:59
*** cuongnv has joined #openstack-kolla00:59
*** eaguilar has quit IRC01:08
sdakesup duonghq01:10
*** sayantani01 has joined #openstack-kolla01:11
*** sayantani01 has quit IRC01:11
*** sayantan_ has joined #openstack-kolla01:11
duonghqmorning sdake01:12
openstackgerritSteven Dake proposed openstack/kolla-kubernetes master: DNM: Test of master kolla-kubernetes  https://review.openstack.org/44623701:13
sdakesup duonghq01:13
duonghqdidn't see you in today meeting :)01:14
masberkolla-ansible I am talking about01:20
*** zhubingbing_ has joined #openstack-kolla01:20
duonghqsdake, around?01:38
*** unicell has quit IRC01:40
sdakeduonghq shoot01:41
*** zioproto has quit IRC01:41
duonghqabout crontab drop root, you said that we cannot drop it?01:41
masberI could install openstack using kolla-ansible and I am testing it now01:42
sdakeduonghq no idea01:42
*** sbezverk_ has joined #openstack-kolla01:42
masberI can see that it does not comes with any flavour, is that right?01:42
masberjust checking I have it right01:43
duonghqsdake, the bug: https://bugs.launchpad.net/kolla/+bug/156074401:43
openstackLaunchpad bug 1560744 in kolla "drop root for crontab" [Medium,Confirmed]01:43
*** sbezverk has quit IRC01:43
duonghqif it cannot be run as normal user, I think we can close it01:43
sdakeduonghq agreed it can be closed01:44
duonghqsdake, roger01:44
*** caowei has joined #openstack-kolla01:44
*** caowei has quit IRC01:51
*** caowei_ has joined #openstack-kolla01:51
*** caowei_ is now known as caowei01:54
*** l4yerffeJ_ has quit IRC01:56
*** l4yerffeJ_ has joined #openstack-kolla01:56
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: WIP: Fernet Token Support  https://review.openstack.org/44627402:07
*** tovin07_ has joined #openstack-kolla02:09
openstackgerritzhubingbing proposed openstack/kolla-ansible master: Fix separate bug in cleanup-containers  https://review.openstack.org/44480702:32
openstackgerritzhubingbing proposed openstack/kolla-ansible master: Fix separate bug in cleanup-containers  https://review.openstack.org/44480702:32
*** erlon has joined #openstack-kolla02:49
spsuryaduonghq: can we close keyston one too ?02:49
spsuryasdake: morning02:50
spsuryamornig all02:50
*** goldyfruit has joined #openstack-kolla02:50
spsuryaduonghq: yesterday meeting priority has become medium02:51
duonghqspsurya, not yet, we still have some solution02:53
duonghqbut opinion is not in consensus yet02:54
duonghqguess that we can leave it alone till somebody interested02:54
spsuryaduonghq: you mean leave it unassigned02:55
duonghqguess so, do you interested?02:56
spsuryayes I am interseted and would love to work on this, yeh it little challenging but doesn't matter02:58
spsuryaduonghq:02:58
spsuryaduonghq: seems like you didn't slept after meeting02:58
duonghqspsurya, nice02:58
duonghqI slept for about 5hrs02:59
duonghqbut not enough,02:59
duonghqI'm finding why02:59
spsuryaget some sleep duonghq02:59
spsuryaand BRB03:00
duonghqIt's my working hour now :), hope that tonight I can got full sleep03:00
spsurya;)03:00
*** jrobinson has quit IRC03:01
duonghqhmm, not sure why 5hrs is not enough03:01
duonghq5.5hrs indeed03:01
spsuryabecoz you still sleepy ;P03:01
spsurya:)03:02
duonghqlaggy, huh? :P03:02
spsuryayes03:02
spsuryaduonghq:  have you given presentation proposal for boston summit ?03:03
spsuryai mean any ?03:03
duonghqya, one is accepted03:03
spsuryasame is here03:04
spsuryaduonghq: US Visa is main concern for me03:04
duonghqhmm, me too, and also TSP03:04
spsuryanot approved last time03:04
spsuryayeh TSP too.03:05
*** yuanying has quit IRC03:06
*** goldyfruit has quit IRC03:06
openstackgerritzhubingbing proposed openstack/kolla-ansible master: Fix separately removed contaiers bug in cleanup-containers  https://review.openstack.org/44480703:14
*** dave-mcc_ has quit IRC03:29
*** daidv has joined #openstack-kolla03:32
openstackgerritchenyingnan proposed openstack/kolla master: Typo fixing  https://review.openstack.org/44629003:33
*** lamt has joined #openstack-kolla03:34
*** unicell has joined #openstack-kolla03:36
*** unicell has quit IRC03:40
*** caowei has quit IRC03:41
*** zhurong has joined #openstack-kolla03:44
openstackgerritMerged openstack/kolla master: Load iscsi_tcp module when starting ironic-conductor  https://review.openstack.org/44469904:05
*** jascott1- has joined #openstack-kolla04:05
*** cuongnv has quit IRC04:16
*** cuongnv has joined #openstack-kolla04:16
*** unicell has joined #openstack-kolla04:19
*** unicell has quit IRC04:20
*** shasha_t_ has joined #openstack-kolla04:21
*** skramaja has joined #openstack-kolla04:35
*** lamt has quit IRC04:41
*** klindgren_ has joined #openstack-kolla04:42
*** klindgren__ has quit IRC04:44
*** yuanying has joined #openstack-kolla04:46
*** lamt has joined #openstack-kolla04:47
*** klindgren has joined #openstack-kolla04:54
*** klindgren_ has quit IRC04:55
*** tonanhngo has joined #openstack-kolla05:04
spsuryaduonghq: around ?05:05
*** erlon has quit IRC05:15
*** lamt has quit IRC05:15
*** tonanhngo has quit IRC05:22
*** daidv has quit IRC05:24
*** zhurong has quit IRC05:25
*** unicell has joined #openstack-kolla05:26
*** daidv has joined #openstack-kolla05:28
*** palexster has quit IRC05:30
openstackgerritZeyu Zhu proposed openstack/kolla master: Optimize the code  https://review.openstack.org/44630305:30
*** Jeffrey4l__ has joined #openstack-kolla05:30
*** palexster has joined #openstack-kolla05:32
*** l4yerffeJ_ has quit IRC05:34
*** Jeffrey4l_ has quit IRC05:34
*** saneax-_-|AFK is now known as saneax05:34
spsuryaduonghq:  AFAIK this is completed, https://review.openstack.org/#/c/425446/16 ,  I mean implementation, testing is left and gate is the main issue to merge the depend patch in kolla .05:39
*** fooliouno has joined #openstack-kolla05:54
fooliounoHello looking for help on kolla-kubernetes05:55
fooliounoWhen I create the openvswitch-vswitchd-network pod, I lose connectivity to Horizon05:55
fooliounoWould appreciate any tips on what may have gone wrong05:56
fooliounokfox1111, duonghq. Help, please :)05:58
masberHi, I am trying to install openstack using kolla-ansible, the bootstrap-server step fails, I think because the names of the nics on the servers does not match. http://pastebin.com/raw/SZrjgJHu06:00
masberI tried to tell kolla the right nic to use by editing the multinode file, but somehow didnt work, I am wondering what I am doing wrong?06:00
*** skramaja_ has joined #openstack-kolla06:19
*** skramaja_ has quit IRC06:19
*** skramaja has quit IRC06:22
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Add new section "Log delivery" in CONTRIBUTING.rst  https://review.openstack.org/44617406:24
*** sayantan_ has quit IRC06:26
*** david-lyle_ has joined #openstack-kolla06:26
*** david-lyle has quit IRC06:26
*** caowei has joined #openstack-kolla06:27
*** jrobinson has joined #openstack-kolla06:34
duonghqspsurya, kolla ps must be merged 1st06:58
duonghqya, forgot bring in this week meetingg06:58
spsuryaduonghq: if i see gate is working fine for kolla ps06:59
spsuryaduonghq: is the work left in kolla-ansible ps ? I think testing is left once it gets merged.07:01
spsuryaduonghq: sorry before h getting merge07:02
duonghqspsurya, guess that no07:03
spsuryaduonghq: you mean more optimised implementation ?07:04
*** jmccarthy has joined #openstack-kolla07:13
*** unicell has quit IRC07:19
*** manheim has joined #openstack-kolla07:27
*** manheim has quit IRC07:28
*** manheim has joined #openstack-kolla07:28
*** Jeffrey4l__ has quit IRC07:41
*** caowei has quit IRC07:45
*** haplo37 has quit IRC07:48
*** matrohon has joined #openstack-kolla07:55
*** haplo37 has joined #openstack-kolla07:57
*** mpansky has joined #openstack-kolla08:07
*** shardy has joined #openstack-kolla08:09
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Update Fluentd config to log in Kibana dashboard  https://review.openstack.org/44634208:10
*** yuanying has quit IRC08:19
*** jrobinson has quit IRC08:22
*** caowei has joined #openstack-kolla08:26
openstackgerritMerged openstack/kolla-ansible master: Access glance through vip rather than multi glance ips in ironic  https://review.openstack.org/44455208:28
*** skramaja has joined #openstack-kolla08:28
*** pcaruana has joined #openstack-kolla08:30
*** Jezekus has joined #openstack-kolla08:35
*** ArchiFleKs has quit IRC08:36
*** skramaja_ has joined #openstack-kolla08:37
*** skramaja has quit IRC08:38
*** egonzalez has joined #openstack-kolla08:38
*** jascott1 has quit IRC08:38
zhubingbing_sup egonzalez08:39
*** jascott1 has joined #openstack-kolla08:39
egonzalezsup zhubingbing_08:39
zhubingbing_;)08:40
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Optimize reconfiguration for ironic  https://review.openstack.org/42390108:40
*** caowei has quit IRC08:42
*** jascott1 has quit IRC08:44
*** cu5 has joined #openstack-kolla08:46
*** nea1 has joined #openstack-kolla08:46
nea1hi, what distro would you recommend / which one is tested the best?08:47
egonzaleznea1, all depends of the preferences of the guy recommending a distro ;)08:48
duonghqspsurya, sorry,08:48
duonghqspsurya, I think it's acceptable atm08:48
egonzaleznea1, I prefer RPM based distros08:49
spsuryaduonghq: its ok08:49
openstackgerritMerged openstack/kolla-ansible master: Trove: add oslo_messaging_notifications config  https://review.openstack.org/44442208:50
spsuryaduonghq: I think inc0 can review this08:50
duonghqspsurya, yep08:50
*** yuanying has joined #openstack-kolla08:55
*** deadnull has joined #openstack-kolla08:55
thomas_oneillmorning all :D08:56
thomas_oneillcould anyone review this? https://review.openstack.org/#/c/443747/ ty08:56
*** athomas has joined #openstack-kolla08:56
spsuryainc0: it would be great if you review these patches https://review.openstack.org/#/c/425446/16    which was depend on this   https://review.openstack.org/#/c/425833/    Seems like gate is green now08:57
*** david-lyle_ has quit IRC08:58
*** qiliang28 has joined #openstack-kolla08:59
*** qiliang27 has quit IRC09:02
*** qiliang28 is now known as qiliang2709:02
*** Serlex has joined #openstack-kolla09:03
*** skramaja_ is now known as skramaja09:03
*** strigazi_AFK is now known as strigazi09:04
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Update Fluentd config to log in Kibana dashboard  https://review.openstack.org/44634209:06
*** jbadiapa_ has quit IRC09:11
*** skramaja has quit IRC09:13
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Add new section "Log delivery" in CONTRIBUTING.rst  https://review.openstack.org/44617409:14
*** skramaja has joined #openstack-kolla09:16
*** mgoddard has joined #openstack-kolla09:19
openstackgerritThomas O'Neill proposed openstack/kolla-ansible master: Add neutron-bgp-dragent playbooks and sensible defaults.  https://review.openstack.org/44374709:21
thomas_oneill(just rebased)09:21
egonzalezthomas_oneill, check the comment on PS 5, was rebased while was reviewing heh09:23
*** skramaja_ has joined #openstack-kolla09:24
*** skramaja has quit IRC09:25
*** Jeffrey4l has joined #openstack-kolla09:25
*** skramaja_ has quit IRC09:28
*** tovin07_ has quit IRC09:29
*** skramaja_ has joined #openstack-kolla09:31
duonghqbye guys09:31
*** duonghq has quit IRC09:31
*** cu5_ has joined #openstack-kolla09:35
*** yingjun has quit IRC09:37
*** skramaja has joined #openstack-kolla09:42
*** cu5 has quit IRC09:42
*** skramaja_ has quit IRC09:43
*** porzech has joined #openstack-kolla09:45
thomas_oneillegonzalez: thanks for that, this group_vars file seems a complete mess tbh09:52
thomas_oneillwe have all these Networking options, and then now I could add Neutron options but that seems... hmmm...09:52
thomas_oneilland the other service options aren't in alphabetical order!! dun dun dunnnnn lol09:52
thomas_oneillit feels a bit weird having both "Networking options" and "Neutron options"09:53
thomas_oneillmaybe some of the "Networking options" should actually be put into "Openstack options" or "Kolla options" and the rest should be "Neutron options" ?09:53
thomas_oneillI'm not sure, I'm going to keep looking at the file and see if I can come up with a decent idea09:53
thomas_oneillmy question though: if I did try to re-arrange/clean-up this file, I guess that would have to be in a separate PS right?09:54
egonzaleznot all networking options are neutron options ;)09:54
egonzalezdns_interface is not neutron, network_interface is not too. most of them are for global networking09:55
thomas_oneillso if I made Neutron options, neutron_external_interface should go there I suppose?09:56
egonzalezimo not, should be a networking section for all interfaces configuration, the other is more to trick a value like the bgp ID09:57
egonzalezbut i'm concern that we have to clean up all the mess in globals, too many options that are not "global"09:59
thomas_oneilldo you think the spacing between the sections should be 1 or 2 line breaks?10:00
thomas_oneillthere's inconsistency with that too10:01
egonzalez2 is cleaner10:02
openstackgerritThomas O'Neill proposed openstack/kolla-ansible master: Add neutron-bgp-dragent playbooks and sensible defaults.  https://review.openstack.org/44374710:03
*** jbadiapa has joined #openstack-kolla10:03
thomas_oneillokay I just revised what was suggested for now, those other concerns shouldn't be addressed in this PS I suppose10:04
thomas_oneillalso I think you misused the word trick egonzalez :p10:04
*** pbourke has quit IRC10:04
*** pbourke has joined #openstack-kolla10:04
egonzalezthomas_oneill, probably I misuse a lot of words (like des_consolado ;) )10:05
*** cuongnv has quit IRC10:06
*** qiliang27 has quit IRC10:08
*** qiliang27 has joined #openstack-kolla10:10
*** daidv has quit IRC10:10
*** mnasiadka has joined #openstack-kolla10:12
*** deadnull has quit IRC10:13
*** manheim_ has joined #openstack-kolla10:14
*** manheim has quit IRC10:16
*** Jeffrey4l has quit IRC10:23
*** caowei has joined #openstack-kolla10:24
*** caowei has quit IRC10:40
*** jascott1 has joined #openstack-kolla10:40
openstackgerritEduardo Gonzalez proposed openstack/kolla master: Add None value to service.description attribute  https://review.openstack.org/44599010:43
*** Jeffrey4l has joined #openstack-kolla10:46
*** jascott1 has quit IRC10:46
*** mpansky has quit IRC10:47
thomas_oneillcould anyone confirm this bug https://bugs.launchpad.net/kolla/+bug/167342010:48
openstackLaunchpad bug 1673420 in kolla "Bifrost image's mysqldb module is broken" [Undecided,New]10:48
thomas_oneillit's very strange10:48
*** rwellum has quit IRC10:48
thomas_oneillactually I should try doing a rebuild first and see if it's still the same10:51
egonzalezthomas_oneill, may be related this PS https://review.openstack.org/#/c/424391/10:54
-openstackstatus- NOTICE: paste.openstack.org is down, due to connectivity issues with backend database. support ticket has been created.10:58
*** ChanServ changes topic to "paste.openstack.org is down, due to connectivity issues with backend database. support ticket has been created."10:58
openstackgerritMarcin Juszkiewicz proposed openstack/kolla master: ironic-pxe: handle non-x86 architectures  https://review.openstack.org/43481710:59
openstackgerritMarcin Juszkiewicz proposed openstack/kolla master: debian: enable all images enabled for Ubuntu  https://review.openstack.org/43278710:59
openstackgerritMarcin Juszkiewicz proposed openstack/kolla master: Add support for non-x86 architectures (aarch64, ppc64le)  https://review.openstack.org/43094010:59
openstackgerritMarcin Juszkiewicz proposed openstack/kolla master: openstack-base/kolla-toolbox: use mariadb-devel for CentOS and !x86-64  https://review.openstack.org/44483210:59
openstackgerritMarcin Juszkiewicz proposed openstack/kolla master: nova-libvirt: handle ppc64le  https://review.openstack.org/43481010:59
openstackgerritMarcin Juszkiewicz proposed openstack/kolla master: ceph: move ceph-fuse package to cephfs-fuse image  https://review.openstack.org/44063410:59
openstackgerritMarcin Juszkiewicz proposed openstack/kolla master: kubernetes: disable for architectures other than x86-64  https://review.openstack.org/44563810:59
openstackgerritMarcin Juszkiewicz proposed openstack/kolla master: nova-compute: handle rtslib(-fb) for debian-binary builds too  https://review.openstack.org/43594110:59
openstackgerritMarcin Juszkiewicz proposed openstack/kolla master: debian: move to stretch  https://review.openstack.org/43445310:59
*** skramaja has quit IRC11:01
hrw~curse ubuntu11:02
hrwhi all11:02
nea1Hi, can someone help me with "kolla/centos-binary-kolla-toolbox:4.0.0 not found" full log: http://termbin.com/8h1711:02
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Change heat cfn service description  https://review.openstack.org/44645311:03
nea1the thing i noticed was there is no 4.0.0 on https://hub.docker.com/r/kolla/centos-binary-kolla-toolbox/tags/11:03
hrwnea1: can you pull it by hand?11:03
nea1hrw: I ran kolla-ansible pull11:03
nea1according to the instructions on https://docs.openstack.org/developer/kolla-ansible/quickstart.html11:04
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Change heat cfn service description  https://review.openstack.org/44645311:05
hrwnea1: no idea are 4.0.0 got pushed to hub11:05
hrwcan someone tell me how to run gate jobs on local machine?11:05
nea1hrw: I don't understand what is going on or why it is trying to request 4.0.011:06
hrwnea1: kolla master branch uses 4.0.0 tag.11:06
nea1it isn't in my config /etc/kolla and a grep on /usr/share/kolla-ansible/ didn't have any hits too11:06
nea1ah, ok11:06
nea1and from where should one pull?11:07
egonzalezhrw, gates cannot be run locally. you can simulate using setup_<distro> and allinone.sh, but some things have to be changed before11:07
hrwnea1: stable/ocata branch?11:07
hrwegonzalez: ;(11:07
hrwegonzalez: I would like to check can ubuntu mysql-server-5.7 failure be reproduced in some way11:08
egonzalezhrw, at least that's what I think, maybe im wrong. Jeffrey4l can confirm that11:08
hrwit makes all my patches look bad due to jenkins -1 patches11:08
egonzalezhrw, what is failing while deploying? or building?11:09
egonzalezyou can always execute allinone locally or building to check11:10
egonzaleznea1, docker images with tag 4.0.0 are not pushed to dockerhub yet.11:10
hrwegonzalez: https://review.openstack.org/#/c/444832/ has ubuntu/source fail: http://logs.openstack.org/32/444832/8/check/gate-kolla-dsvm-build-ubuntu-source-ubuntu-xenial/2da6acf/console.html which is bifrost-base failure due to mysql-server-5.7 postinstall failure11:11
nea1hrw: egonzalez I'm just going threw https://docs.openstack.org/developer/kolla-ansible/quickstart.html - there is nothing written there about how / where to select the branch11:11
hrwif I run ubuntu container and call 'apt update;apt mysql-server' then it just works11:11
egonzaleznea1, here you have 3 options, wait until are pushed(don't know when), build your own images or use a registry created with each merged commit on ocata https://tarballs.openstack.org/kolla/images/ (note this registries are latest commit merged on each branch, are not created from 4.0.0 tag (not stable))11:12
egonzalezhrw, bifrost is going to be a hard image to build, since most of the stuff is installed with an internal call with ansible11:14
egonzalezhrw, maybe that have to be fixed in bifrost project11:15
hrwegonzalez: this bug is beyong kolla imho11:15
thomas_oneillegonzalez: I don't think the bug I raised is to do with which python is being used, because when re-installing the package it is fixed11:18
nea1egonzalez: ok, and how do I select a other branch?11:18
thomas_oneillbifrost-base is based on openstack-base, and that's why MySQL-python is installed. I tested in that image and there isn't the same problem. So that's strange as well.11:19
thomas_oneillI'm going to inspect my bifrost-deploy image to see which layer installed that package and what might have gone wrnog.11:19
thomas_oneills/wrnog/wrong/11:19
hrwI started build of ubuntu based images in meantime11:20
hrwplane boarding in 5 minutes ;D11:20
egonzaleznea1, installed with pip install kolla-ansible right?11:21
thomas_oneillnea1: I was a beginner recently as well, building the images from source is usually the more reliable option.11:21
nea1yea11:21
egonzaleznea1, docker tag version is 4.0.0, but images are not in dockerhub yet11:21
egonzaleznea1, 4.0.0 = ocata release11:21
nea1ok, so how do I get 3.x?11:22
thomas_oneillspecify the --tag option in kolla-build11:22
nea1kolla-ansible seams only to have 4.0.0 acording to the git tags11:22
thomas_oneillor have the kolla-build.conf sit in the correct directory (/etc/kolla or ./etc/kolla I think) and that specify the tag11:22
egonzaleznea1, kolla-ansible was included in kolla before ocata11:23
thomas_oneillthe oslo common config stuff (see kolla/common/config.py and kolla/image/build.py in the kolla repo) will read either of those and then use the tag from there11:23
nea1thomas_oneill: -bash: kolla-build: command not found11:23
nea1egonzalez: yea, so how do I downgrade?11:24
*** deadnull has joined #openstack-kolla11:24
thomas_oneillcd kolla; pip install .; tox -e genconfig; ## edit the etc/kolla/kolla-build.conf or have it in /etc/kolla11:24
nea1thomas_oneill: and /etc/kolla only contains globals.yml and passwords.yml11:24
thomas_oneilland then sudo kolla-build with a bunch of cli opts or just sudo kolla-build if you've edited the kolla-build.conf file11:24
thomas_oneillcd kolla == the kolla repo btw, not the kolla-ansible repo11:25
thomas_oneillgit clone https://github.com/openstack/kolla.git11:25
nea1ah, ok11:26
nea1thomas_oneill: wasn't that "Install Kolla for development"11:27
egonzaleznea1, to use stable version, better uninstall kolla-ansible11:27
egonzalezand then pip install kolla==3.0.211:27
egonzaleznea1, are the same steps but with different version and installing kolla instead of kolla-ansible11:28
nea1egonzalez: ah, ok so I just started in the wrong place11:30
nea1how stable is ocata?11:30
egonzaleznea1, nope, the only issue is that ocata images are not pushed to dockerhub yet and following the guide fails due missing images11:31
egonzaleznea1, ocata is running fine11:31
nea1I'll see if I have any errors, and if so then I'll go with reinstalling with kolla on mitaka11:32
*** athomas has quit IRC11:32
*** athomas has joined #openstack-kolla11:33
*** rwellum has joined #openstack-kolla11:34
nea1does kolla-build --type source mean that it will compile all packages it self or what?11:37
*** rhallisey has joined #openstack-kolla11:37
thomas_oneillyeah from the tarballs at tarballs.openstack.org11:39
nea1ah, ok11:40
*** ChanServ changes topic to "support: ask.openstack.org | New to Kolla: docs @ http://docs.openstack.org/developer/kolla/ | | Kolla IRC meetngs on Wednesdays @ 16:00 UTC - see agenda @ https://goo.gl/OXB0DL - IRC channel is *LOGGED* @ http://goo.gl/3mzZ7b"11:46
-openstackstatus- NOTICE: paste.openstack.org service is back up - turns out it was a networking issue, not a database issue. yay networks!11:46
*** zhubingbing_ has quit IRC11:46
*** dave-mccowan has joined #openstack-kolla11:53
thomas_oneillare the docker image tags global like... if one of you guys tries to inspect this image: 3d2b2e6a0745 does it work?12:02
thomas_oneillsorry not tag uhh hash I guess?12:02
thomas_oneillI'm going through a docker history and I've identified the layer causing the problem with mysql_db module12:02
thomas_oneillif the hashes are generated locally on my kolla-build though, I'm not sure how to communicate which layer this is :P12:03
sdakemorning peeps12:05
thomas_oneillmorning12:05
*** skramaja has joined #openstack-kolla12:05
thomas_oneillso this is the issue https://github.com/openstack/kolla/blob/master/docker/bifrost/bifrost-base/Dockerfile.j2#L30 I've updated https://bugs.launchpad.net/kolla/+bug/167342012:06
openstackLaunchpad bug 1673420 in kolla "Bifrost image's mysqldb module is broken" [Undecided,New]12:06
mnasermorning12:06
thomas_oneillsean-k-mooney: i git-blame u :p what is this terrible sed hack and how can we fix it12:07
*** fooliouno has quit IRC12:07
mnaserwould anyone be able to chime in regarding this? https://review.openstack.org/#/c/446249/ -- the configure_user macro is missing in newton (should i backport the macro *or* manually add RUN chsh -s /bin/bash <user>) ?12:07
mnasercc pbourke ^12:08
*** jascott1 has joined #openstack-kolla12:11
pbourkemnaser: i think RUN chsh is ok for this12:13
*** mpansky has joined #openstack-kolla12:13
*** jascott1 has quit IRC12:15
*** schwicht has joined #openstack-kolla12:16
*** eaguilar has joined #openstack-kolla12:20
*** schwicht has quit IRC12:23
spsuryasdake: morning12:23
*** cu5_ is now known as cu512:25
*** schwicht has joined #openstack-kolla12:26
*** MarisK has joined #openstack-kolla12:27
openstackgerritOpenStack Proposal Bot proposed openstack/kolla-kubernetes master: Updated from global requirements  https://review.openstack.org/44508912:28
MarisKHello! We had a running Kolla (centos-binary) cluster running without a central logging in Elasticsearch and Kibana. We decided to start using it, change the preferences in globals.yml and ran kolla-ansible reconfigure12:29
MarisKBoth elasticsearch and Kibana containers are now running, but no logs are written to Elasticsearch. Could you please advice what should I look into?12:29
*** athomas has quit IRC12:32
*** rwallner has joined #openstack-kolla12:33
*** rwallner has quit IRC12:33
*** rwallner has joined #openstack-kolla12:34
spsuryapbourke: portdirect anyone   please check this  command  http://paste.openstack.org/show/602955/12:37
spsuryacommand output12:37
spsurya*12:37
pbourkeMarisK: did you deploy with central logging enabled from scratch or deploy then enable it12:37
*** goldyfruit has joined #openstack-kolla12:38
spsuryacouldn't find the exact solution for this12:38
*** athomas has joined #openstack-kolla12:38
pbourkespsurya: I dont recommend vagrant12:38
MarisKpbourke: We deployed without central logging. Enabled it afterwards with "kolla-ansible reconfigure".12:38
pbourkeMarisK: unfortunately I dont think reconfigure works for central logging :/12:39
manheim_hi, vlan tenant network type is not supported?12:39
pbourkeMarisK: would you be able to destroy and redeploy from scratch?12:39
spsuryapbourke: thanks, i see12:39
pbourkemanheim_: it is supported12:39
pbourkespsurya: Im not saying it wont work, but I dont like it for the exact kind of reasons you're seeing12:40
MarisKpbourke: Yes, will do that. But what is suggested best practice for changing major parts of the cluster while keeping the data? For example if we want to add additional openstack services on a production cluster?12:40
pbourkeMarisK: reconfigure works for the most part, but there's gaps in it as you've discovered12:40
pbourkeMarisK: we should raise a bug about the central logging part im sure its fixable12:41
thomas_oneillhttps://github.com/openstack/kolla/blob/master/requirements.txt#L6 2.9.5 is out now so this is fucked... worth just pinning this at 2.8.* ?12:41
MarisKpbourke: Got it. Thanks!12:42
thomas_oneillsame in the kolla-ansible repo12:42
*** gfidente has joined #openstack-kolla12:42
*** gfidente has quit IRC12:42
*** gfidente has joined #openstack-kolla12:42
pbourkethomas_oneill: whasts the problem12:45
thomas_oneillpbourke: when you pip install . it upgrades to jinja 2.9.5 which breaks stuff12:46
thomas_oneillnot a major problem just having to roll my jinja2 back after every time I pip install . in the kolla repo to try a new kolla-build :P12:46
thomas_oneillpbourke: I see you are a kolla-ansible core, maybe you could review this if you have time? https://review.openstack.org/#/c/443747/ :D12:47
pbourkesure12:47
*** manheim has joined #openstack-kolla12:48
pbourkethomas_oneill: the jinja thing sounds bad, can you raise a kolla-ansible bug with what you're seeing?12:49
*** shardy is now known as shardy_lunch12:50
*** schwicht has quit IRC12:50
*** manheim_ has quit IRC12:51
*** goldyfruit has quit IRC12:51
thomas_oneillpbourke: well I'm not seeing any particular error currently and I don't remember what it was before, obviously the ' !=2.9.0,!=2.9.1,!=2.9.2,!=2.9.3,!=2.9.4,>=2.8 ' stuff is there for this reason though12:52
thomas_oneillwas just thinking it'd probably be nicer to just pin it at 2.8 rather than exclude all the 2.9's when the minor version could go up again at any given time in pypi12:52
pbourkethomas_oneill: well, that's maintained by openstack/requirements and periodically pulled into kolla12:52
pbourkethomas_oneill: so maybe we were hasty at taking in that change12:52
thomas_oneillwhoa12:53
thomas_oneillnever knew about this openstack/requirements thing lol12:53
*** MarisK has quit IRC12:53
*** zhubingbing has joined #openstack-kolla12:55
thomas_oneillyeah commit f0fb896f4416fe100b18826444b6583a42fab46e on openstack/requirements, exception when string contains curly braces12:55
thomas_oneill"This patch pins the jinja2 release at a version less than 2.9" no it doesn't if a new one comes out -.- will submit a ps to the requirements thing if I have time then thanks12:56
*** rhallisey has quit IRC12:57
*** rhallisey has joined #openstack-kolla12:58
*** zhubingbing__ has joined #openstack-kolla13:00
*** zhubingbing has quit IRC13:01
nea1thomas_oneill: http://termbin.com/98s9 i think I can ignore those or? as I think that don't need them13:02
egonzaleznea1, are you using a binary install right?13:03
*** schwicht has joined #openstack-kolla13:06
nea1egonzalez: yes13:06
nea1other question: can kolla_external_vip_address be a IPv6 Address?13:06
egonzalezthose packages does not have a binary package in their distro repositories, can be ignored13:07
*** goldyfruit has joined #openstack-kolla13:08
thomas_oneillnea1: you only need images for the services you'll be using as specified in your inventory file :)13:08
SamYaplenea1: no, must be ipv413:09
*** jbadiapa has quit IRC13:12
*** jtriley has joined #openstack-kolla13:18
rwallnerhey guys, is there a recommended way to add an additional compute or storage node after an initial kolla deploy. Is it simply adding a node to the inventory and running "kolla-ansible deploy" again? Will this touch any existing config containers?13:19
*** scheuk has joined #openstack-kolla13:20
*** lamt has joined #openstack-kolla13:21
SamYaplerwallner: its as easy as that13:25
rwallnerThanks !13:25
SamYapleit _will_ mess with configs if, for example, you add a new monitor for ceph13:25
SamYapleor a  new database13:25
SamYapleor a new rabbitmq13:25
rwallnergot it13:25
SamYaplefor compute, it shouldn't add configs to any other host though13:25
thomas_oneillbleh I'm still getting this damned bug, even with the changes proposed in the change https://bugs.launchpad.net/kolla-ansible/+bug/166101313:26
openstackLaunchpad bug 1661013 in kolla-ansible "Bifrost documentation need to be updated with correct path to inventory files" [Undecided,In progress] - Assigned to Mark Goddard (mgoddard)13:26
thomas_oneillit's like ansible/jinja2 doesn't recognise the ''' ''' syntax13:26
thomas_oneilljust ansible, jinja2 isn't used here actualy13:26
*** shardy_lunch is now known as shardy13:31
dimsfolks, there's #openstack-golang if you are interested in the things mentioned in https://etherpad.openstack.org/p/go-and-containers13:31
dimsanyone interested in standalone docker-machine for openstack? ping me :)13:32
*** Jeffrey4l has quit IRC13:34
*** jbadiapa has joined #openstack-kolla13:37
*** srwilkers has joined #openstack-kolla13:42
*** Jeffrey4l has joined #openstack-kolla13:47
spsuryapbourke: yes not finding the solution for it  http://paste.openstack.org/show/602955/13:47
spsuryapbourke: vagrant giving pain13:48
*** srwilkers has quit IRC13:56
*** yingjun has joined #openstack-kolla13:56
*** lamt has quit IRC14:00
*** eaguilar has quit IRC14:04
openstackgerritMohammed Naser proposed openstack/kolla stable/newton: Refactor and enable shell access  https://review.openstack.org/44624914:13
*** MarisK has joined #openstack-kolla14:13
mnaserpbourke ^ there :>14:13
MarisKpbourke: As per your advice I have destroyed and created the new cluster from scratch, but there are still no indices in ElasticSearch. Can you please clarify how the logs are collected and pushed to elasticsearch?14:14
sbezverk_pbourke: do you know when complete set of 4.0.0 images will be pushed to docker hub?14:15
*** saneax is now known as saneax-_-|AFK14:16
pbourkemnaser: thanks for your hard work :)14:16
pbourkemnaser: two nits14:16
*** sbezverk_ is now known as sbezverk14:16
pbourkeMarisK: try putting '*' in the indicies box rather than the documented 'log-*'14:16
pbourkesbezverk: no, we dont have any mechanisms in place for that yet14:17
pbourkesbezverk: the existing ones have just been pushed by some of the core team14:18
pbourkesbezverk: you could probably push ones if you like, check with inc0 for permissions14:18
mnaserpbourke would it be possible to add it to line 18 instead (i feel like it fits the context more)14:19
mnaserfor https://review.openstack.org/#/c/446249/2/docker/keystone/keystone-ssh/Dockerfile.j214:19
mnasersorry, line 1514:19
mnaserso with the ssh related commands instead of the kolla_start ones14:19
*** manheim has quit IRC14:19
pbourkemnaser: sure whatever you like14:21
pbourkemnaser: so long as we combine where possible14:21
sbezverkpbourke: thanks got it.. I saw centos been pushed but not ubuntu, so my ubuntu gate job is failing14:21
*** satyar has joined #openstack-kolla14:22
*** srwilkers has joined #openstack-kolla14:22
MarisKpbourke: I am checking with ElasticSearch API directly: curl http://INTERNAL_IP:9200/_cat/indices?v and it only shows .kibana's index. And all logs are collected within /var/log/kolla volume inside containers. Looks like the collection isn't working.14:22
pbourkesbezverk: some helpful core must have pushed it14:22
*** lucasxu has joined #openstack-kolla14:23
openstackgerritMohammed Naser proposed openstack/kolla stable/newton: Refactor and enable shell access  https://review.openstack.org/44624914:23
mnaserdonezo :)14:23
*** pcaruana has quit IRC14:24
pbourkemnaser: looks good14:24
mnaseris stable/ocata broken in ci?14:27
mnaserit looks like it tried to build images for tag 4.0.1 and pull 4.0.014:27
mnasershould the openstack_version be updated in stable/ocata?14:28
mnaserhttp://logs.openstack.org/48/446248/1/check/gate-kolla-dsvm-deploy-centos-binary-centos-7-nv/c84e70f/console.html#_2017-03-16_01_29_44_32036914:28
*** mpansky has quit IRC14:28
*** erlon has joined #openstack-kolla14:31
pbourkehmm thought Jeffrey4l had done that14:32
*** mpansky has joined #openstack-kolla14:32
Jeffrey4lpbourke, i thought i solved it by load the version number dynamic. but apparently not now. ;(14:33
*** sayantani01 has joined #openstack-kolla14:33
*** sayantani01 has quit IRC14:33
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla-ansible master: Use ansible from within the kolla_toolbox virtualenv  https://review.openstack.org/43502414:33
*** sayantani01 has joined #openstack-kolla14:34
mnaserbecause this backport failed that's why https://review.openstack.org/#/c/446248/14:34
mgoddardthomas_oneil: hi, just seen your mention of a bug I'm assigned to14:34
*** lamt has joined #openstack-kolla14:36
mgoddardthomas_oneill: that error happens if the script fails to execute. what happens is ansible will try to treat the file as a standard hosts format file if execution fails. The problem is that the format is obviously not a standard hosts file format, so it complains but shows you that error rather than the original script execution error14:36
mgoddardthomas_oneill: you should be able to execute the inventory script on its own to see the real error14:37
*** yingjun has quit IRC14:45
*** logan- has quit IRC14:46
*** logan- has joined #openstack-kolla14:46
*** manheim has joined #openstack-kolla14:47
*** manheim has quit IRC14:52
*** papacz has quit IRC14:55
*** MarisK has quit IRC14:56
thomas_oneillmgoddard: aha, ty14:59
thomas_oneillsayantani01: hmmm I've made a fix locally for the issue but it's completely different to yours15:00
*** yingjun has joined #openstack-kolla15:03
*** mpansky has quit IRC15:03
thomas_oneillmine's pretty awful though, just added && pip uninstall -y MySQL-python to the sed line that causes the breakage in the image15:06
*** sayantani01 has quit IRC15:06
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: WIP: Split bind9 into its own role  https://review.openstack.org/44658815:07
*** mpansky has joined #openstack-kolla15:08
*** manjeets has joined #openstack-kolla15:11
kfox1111morning.15:12
*** sbezverk has quit IRC15:13
inc0morning:)15:17
*** Jezekus has quit IRC15:18
Serlexyo15:18
srwilkersmorning15:18
*** lucasxu has quit IRC15:22
mnasershould kolla-ansible be updated to use 4.0.1 tag?  what's the solution to get things not to fail under stable/ocata?15:27
spsuryamorning15:27
mnaseri dont mind taking on the work if we can get that resolved :X15:27
inc0mnaser: any particular bug you're talking about?15:33
inc0we will release 4.0.1 soon15:33
mnaserinc0 this fail http://logs.openstack.org/48/446248/1/check/gate-kolla-dsvm-deploy-centos-binary-centos-7-nv/c84e70f/console.html#_2017-03-16_01_29_44_32036915:34
mnaserit tries to pull image 4.0.0 but the tagged ones are 4.0.115:34
*** hrw has quit IRC15:34
mnaser(note that this is a patch for stable/ocata)15:34
inc0hmf15:34
mnaseri think what happens is15:35
mnaserit uses pbr to get kolla-ansible version which is 4.0.015:35
mnaserhttp://logs.openstack.org/48/446248/1/check/gate-kolla-dsvm-deploy-centos-binary-centos-7-nv/c84e70f/console.html#_2017-03-16_01_28_05_15215815:35
mnaserbut the images that it pulls are 4.0.115:35
*** hrw has joined #openstack-kolla15:36
inc0yeah, I think I know what happened15:36
inc0and thats critical bug15:36
inc0pbr...15:36
inc0let me check something15:39
*** goldyfruit has quit IRC15:39
sean-k-mooneythomas_oneill: when i intorduced the bifrost support the fact we used the upstream mariadb repo broke bifrost.15:39
sean-k-mooneythomas_oneill: when i was discussing this i first suggested activating the repo in the mariabdb container but it was instead suggesed to use sed to remove it for the sources.list.15:40
sean-k-mooney~15:40
thomas_oneillaha15:41
inc0right15:41
*** goldyfruit has joined #openstack-kolla15:41
*** lamt has quit IRC15:41
inc0mnaser: so issue is, once we released 4.0.0 (last week)15:41
inc0pbr automatically bumps version to next-to-be released15:42
mnaserinc0 in the deploy job, the images are retrieved from tarballs.o.o ?15:43
inc0I need to think how to solve this15:43
*** goldyfruit has quit IRC15:43
inc0yes15:43
*** goldyfruit has joined #openstack-kolla15:43
sean-k-mooneythomas_oneill: if birfost can deploy with the upstream repo now then we could remvoe the sed command. its really just an artifact of the fact that we inerit form the base container.15:44
mnaserinc0: the deploy job seems fine (it looks for 4.0.0) but the images it downloads are tagged at 4.0.1.. it sounds like the version detection is not the same in kolla and kolla-ansible15:44
inc0we need some mechanism to detect version of kolla in kolla-ansible15:44
mnaserbecause kolla-ansible detects 4.0.0 and kolla detects 4.0.1 (when building)15:45
inc0there is no version detection in kolla-ansible really15:45
sean-k-mooneyinc0:  cant you get the version from pip15:45
sean-k-mooneypip info kolla or pip show kolla15:45
inc0sean-k-mooney: question is if that works for gates15:46
inc0yup - you can't get version from git-repo installed kolla-ansible15:46
sean-k-mooneyit will show you the info for installed package15:46
egonzalezin kolla gates images are built for deployment too, registry is not downloaded. iirc15:47
inc0to do it properly we'd need to rewrite kolla-ansible to python15:47
thomas_oneillhow do you name your bug fixing branches?15:47
sean-k-mooneyinc0: why?15:48
inc0egonzalez: in deployment jobs images are downloaded from tarballs15:48
inc0sean-k-mooney: in kolla-build we have --version flag which uses pbr to detect version15:48
inc0I think I have solution15:49
mnaserok silly question but15:49
*** jascott1 has joined #openstack-kolla15:49
mnaserare kolla and kolla-ansible releases "tied" together15:49
inc0we can write ansible module that will detect version with pbr15:49
mnaseraka 4.0.1 kolla release implies 4.0.1 kolla-ansible is out?15:49
inc0mnaser: well yes15:49
inc0there is very little overlap15:50
inc0but that's mode we operate15:50
mnaserhttp://logs.openstack.org/48/446248/1/check/gate-kolla-dsvm-deploy-centos-binary-centos-7-nv/c84e70f/console.html#_2017-03-16_01_29_28_01055515:50
mnaserit already attempts to detect the version15:50
thomas_oneillah, bug/nnnnnnnn15:50
inc0by overlap I mean it's rare that something changes in images/ansible that would make other images non-deployable15:50
egonzalezi though kolla gates build images no for deploy too. and kolla-ansible download registry15:50
*** furlongm has quit IRC15:51
inc0egonzalez: yeah,you're right15:51
*** david-lyle has joined #openstack-kolla15:52
*** lamt has joined #openstack-kolla15:52
inc0I misunderstood you, however if kolla builds images with 4.0.1, same issue will appear with tarballs15:52
mnaseri think like15:53
openstackgerritThomas O'Neill proposed openstack/kolla master: Dependency fixes for bifrost image.  https://review.openstack.org/44660915:53
*** lucasxu has joined #openstack-kolla15:53
mnaserdecision needs to be taken if15:53
mnaserthe problem is @ kolla or kolla-ansible15:53
inc0I think problem is in kolla-ansible frankly15:53
inc0pbr detects 4.0.015:53
mnasershould images be tagged 4.0.0 or should kolla-ansible be pulling 4.0.115:53
inc0it should detech 4.0.115:54
mnaserokay so i guess the tagging logic15:54
mnaserisnt matching15:54
*** david-lyle_ has joined #openstack-kolla15:55
*** sayantani01 has joined #openstack-kolla15:55
*** david-lyle has quit IRC15:55
inc0ok so kolla-ansible has correct version too15:56
inc0if I download it locally15:56
egonzalezhrm, kolla-ansible pbr told me is 4.0.1 in ocata :/15:56
*** david-lyle__ has joined #openstack-kolla15:57
egonzalezmaster is 4.0.015:57
*** rhallisey is now known as rhallisey-brb15:57
*** rhallisey-brb has quit IRC15:57
mnaserso in stable/ocata in a venv running python -c "import pbr.version; print(pbr.version.VersionInfo('kolla-ansible'))" gives you 4.0.1?15:57
-openstackstatus- NOTICE: The Gerrit service on review.openstack.org is being restarted to address hung remote replication tasks, and should return to an operable state momentarily15:57
inc0yes15:57
mnaserwelp15:58
mnaseryep same here15:58
*** mnasiadka has quit IRC15:58
mnaserhow is kolla-ansible installed, it is possible that it is installed by pip?15:58
mnaserooo15:59
mnaseregonzalez i think you were onto something15:59
*** david-lyle has joined #openstack-kolla15:59
mnaserif master is 4.0.0 and ocata is 4.0.1, seems like we're installing kolla-ansible from master all the time15:59
mnaserinstead of installing from $branch15:59
egonzaleznope, executing inside git repo15:59
*** david-lyle__ has quit IRC15:59
mnaserbut we're talking about a project in the kolla repo, not kolla-ansible16:00
mnaserdoes it know to detect?16:00
mnaseroh wait, for ocata ansible is out of tree16:00
*** david-lyle_ has quit IRC16:00
mnaserits cloning master kolla-ansible16:00
sayantani01thomas_oneill I had tried uninstalling and installing but it hadn't worked for me back then. Yours looks like a more elegant solution, I must agree. I will try it again.16:01
egonzalezi've no idea about zuul, but may be using master branch instead of stable/ocata for deploy gates16:01
mnaserhttps://github.com/openstack/kolla/blob/master/tools/deploy_aio.sh#L18-L2016:01
mnaserit is exactly that egonzalez16:01
mnaserbut the problem is we cant checkout $BRANCH because there is no stable/{mitaka,newton}16:02
*** jascott1 has quit IRC16:03
mnaserZUUL_BRANCH will give the current branch16:03
egonzalezhow about --branch https://docs.openstack.org/infra/zuul/cloner.html#usage16:03
mnaseryeah but that would fail for stable/newton or stable/mitaka16:04
mnaserbecause those branches dont exist in kolla-ansible16:04
inc0beauty of if statements?;)16:04
egonzalezmnaser, newton and mitaka uses old code, that is not applied16:04
mnaserso i propose this: small if statement, if branch != stable/{mitaka,newton} { zuul-clone $ZUUL_BRANCH }16:04
mnaseroh true16:05
egonzalezgates files are per branch16:05
mnaseryou're right16:05
*** david-lyle has quit IRC16:05
mnaserwould you like me to propose something quick for master and then backport to ocata?16:05
mnaseractually16:05
mnaser"The Zuul cloner reuses Zuul parameters such as ZUUL_BRANCH"16:05
egonzalezmnaser, actually i don't think is necessary go for master16:05
mnaserso technically, it should be cloning it16:06
inc0also technically master should return 5.0.0 not 4.0.016:06
mnaserhttp://logs.openstack.org/48/446248/1/check/gate-kolla-dsvm-deploy-centos-binary-centos-7-nv/c84e70f/console.html#_2017-03-16_01_07_46_38580116:06
inc0egonzalez: I just checked, master kolla-ansible witll return 4.0.016:06
mnaserso it is cloning stable/ocata :<16:06
inc0so behavior is correct16:07
mnaserhttp://logs.openstack.org/48/446248/1/check/gate-kolla-dsvm-deploy-centos-binary-centos-7-nv/c84e70f/console.html#_2017-03-16_01_27_17_96357416:08
mnaserit does clone master16:08
egonzalezno, images have tag 4.0.1, but ocata ansible detect 4.0.016:08
inc0mnaser: for requirements it clones ocata16:08
mnaser"Falling back to branch master"16:08
egonzalezif was using ocata ansible would also have tag 4.0.116:08
mnaserits cloning master16:08
nea1new error "manifest for kolla/centos-binary-fluentd:4.0.0 not found"16:08
inc0egonzalez: what I did is in kolla-ansible git reset master -> pip install -e . ->python -c "import pbr.version; print(pbr.version.VersionInfo('kolla-ansible'))"16:08
inc0for stable/ocata it shows 4.0.1, for master 4.0.016:09
mnasersame what inc0 did and i did get 4.0.116:09
nea1but kolla-build was run successfully16:09
mnaserfor stable/ocata16:09
mnasernea1 is this in stable/ocata?16:09
nea1and fluentd isn't in the failed images list16:09
nea1yep16:09
mnaserthis conversation16:09
mnaseris literally about this right now :p16:09
nea1mnaser: kolla-ansible16:09
egonzalezI mean decect ocata ansible in gates, locally I have same of you :)16:09
nea1oh :D16:09
*** japestinho has quit IRC16:10
*** lamt has quit IRC16:10
inc0nea1: check docker images if tag is 4.0.116:10
mnaserim going to grab something to eat but i can get to the bottom of this16:10
mnaserkolla-ansible is being cloned from master but zuul should detect ZUUL_BRANCH16:10
inc0if it is, change globals.yml openstack_release="4.0.1"16:10
mnaserwhich is stable/ocata16:10
nea1docker images | grep fluentd didn't find anything16:10
*** jascott1 has joined #openstack-kolla16:10
mnaseri think its because 4.0.1 images havent been released16:10
mnaser(stable/ocata latest)16:11
*** lamt has joined #openstack-kolla16:11
inc0nea1: you build images right?16:11
inc0mnaser: btw when I see you, remind me to buy you a beer16:12
mnaser:-P16:12
mnaserill bbl to grab something to eat16:12
mnaserbut i'll get to the bottom of this if there isnt progress, i asked folks at -infra to see why its not cloning16:12
nea1inc0: oh, I just noticed on error, I had first started with stable/newton so it build all the images with 3.0.3, even trough I did a tox -e genconfig after switching back16:15
mnaserthere we go16:15
openstackgerritMohammed Naser proposed openstack/kolla stable/newton: Refactor and enable shell access  https://review.openstack.org/44624916:15
mnaseralso thanks for the catch egonzalez ^16:15
egonzalezmnaser, I think is only add --branch ${{ZUUL_BRANCH}} in zuul clone16:22
thomas_oneillmerge_yaml always removed quote marks and removes the --- at the top of the yaml?16:24
thomas_oneills/removed/removes16:24
*** lucasxu has quit IRC16:30
*** lamt has quit IRC16:31
*** sayantani01 has quit IRC16:35
*** sayantani01 has joined #openstack-kolla16:35
*** g3ek has quit IRC16:39
openstackgerritSayantani Goswami proposed openstack/kolla master: Install InfluxDB Plugin in Grafana  https://review.openstack.org/44662416:40
*** vhosakot has joined #openstack-kolla16:41
openstackgerritSayantani Goswami proposed openstack/kolla master: Install InfluxDB Plugin in Grafana  https://review.openstack.org/44662416:47
*** bmace has quit IRC16:47
*** bmace has joined #openstack-kolla16:48
*** g3ek has joined #openstack-kolla16:49
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: WIP: Split bind9 into its own role  https://review.openstack.org/44658816:51
openstackgerritSayantani Goswami proposed openstack/kolla master: Install InfluxDB Plugin in Grafana  https://review.openstack.org/44662416:51
*** rwsu has joined #openstack-kolla16:56
*** unicell has joined #openstack-kolla16:56
*** unicell has joined #openstack-kolla16:56
*** mpansky has quit IRC16:57
*** rhallisey has joined #openstack-kolla16:59
*** egonzalez has quit IRC17:00
spsuryanight allllll17:06
jascott1good night!17:06
*** sayantani01 has quit IRC17:14
*** matrohon has quit IRC17:15
thomas_oneillah dammit... the bifrost container is finally deployed and ironic is even running, but ironic driver-list shows no drivers are available17:16
thomas_oneilland it doesn't look like this bifrost image even logs to the logs D:17:16
thomas_oneillenabled_drivers in the ironic.conf had agent_ipmitool and agent_ipminative17:17
mnasercaught it inc017:21
mnasertox runs sudo /home/jenkins/workspace/gate-kolla-dsvm-deploy-centos-binary-centos-7-nv/tools/deploy_aio.sh centos binary17:21
mnasersudo deletes env17:21
inc0yay17:26
inc0nice catch17:26
inc0sude -E17:27
mnaserinc0 im thinking ill drop sudo in the tox17:27
mnasertools/deploy_aio.sh does sudo when it needs17:27
mnaserso there's no need to sudo twice17:27
inc0yeah check it out17:27
inc0makes sense17:27
inc0nice catch17:27
mnaserthanks to help of -infra and zuul :)17:28
*** gfidente is now known as gfidente|afk17:31
openstackgerritMohammed Naser proposed openstack/kolla master: Remove global privilege escalation for deploy_aio.sh  https://review.openstack.org/44664517:31
*** athomas has quit IRC17:37
*** jmccarthy has left #openstack-kolla17:38
openstackgerritMerged openstack/kolla-ansible master: Multi-regions Support  https://review.openstack.org/43165817:42
*** shardy has quit IRC17:46
openstackgerritMerged openstack/kolla stable/newton: Refactor and enable shell access  https://review.openstack.org/44624917:47
*** notmyname has joined #openstack-kolla17:50
notmynameI'm looking at kolla for the first time. am I correct in understanding that kolla is installing distro packages (ie instead of building/installing from source)?17:51
*** zhubingbing__ has quit IRC17:54
*** satyar has quit IRC17:57
*** mgoddard has quit IRC17:59
openstackgerritMohammed Naser proposed openstack/kolla master: Remove global privilege escalation for deploy_aio.sh  https://review.openstack.org/44664517:59
*** Serlex has quit IRC18:04
*** david-lyle has joined #openstack-kolla18:05
inc0notmyname: we do both18:06
inc0if you do kolla-build --type source  then it will pull down source for openstack services18:06
notmynameinc0: depending on the project? or you do both for every project depending on a config or something?18:06
notmynameah ok18:06
inc0--type build uses packages18:06
notmynamewhere in the kolla repo is that part?18:06
inc0you mean packages?18:07
inc0or config?:)18:07
notmynameI found the install from packages part in the jinja-fied docker files. where's the install from source part?18:07
inc0this is a bit more complicated, let me walk you through process18:08
inc0https://github.com/openstack/kolla/blob/master/kolla/common/config.py#L289-L29218:08
notmynameok :-)18:08
inc0you have configs like this18:09
inc0tarballs.openstack.org hosts tared code for each service18:09
inc0our build script pulls down this tarball on build18:09
notmynameok18:10
notmynamewhere's the build script?18:10
inc0https://github.com/openstack/kolla/blob/master/docker/heat/heat-base/Dockerfile.j2#L47 then this line creates dir in container from tar18:10
notmynamebut didn't the line right above that install from distro packages?18:11
inc0https://github.com/openstack/kolla/blob/master/kolla/image/build.py18:11
notmynameline 45?18:11
notmynameI guess I don't understand enough to know what the macros.install_packages does, followed by a macros.install_pip18:13
inc0notmyname: we still need packages like python-dev and such18:14
mnaserinc0 woo looking at logs: 2017-03-16 18:07:00.507866 | INFO:zuul.Cloner:Prepared openstack/kolla-ansible repo with branch stable/ocata at commit f6823a5e067b95c0d06becbe2cbb00b2b2995e0918:14
mnaserhttps://review.openstack.org/#/c/446645/ and https://review.openstack.org/#/c/446648/ (backport)18:15
mnaser#makegatesvoteagain18:15
*** sayantani01 has joined #openstack-kolla18:16
notmynameinc0: ah, ok, I think I got it. I wasn't parsing the if blocks correctly18:16
*** tonanhngo has joined #openstack-kolla18:18
notmynameinc0: does kolla install-from-source any repo that isn't python? ie something that would have a compile step?18:18
inc0notmyname: negative18:18
notmynameinc0: ok18:19
notmynameinc0: what changes would be necessary to do that? something in build.py?18:19
mnasernotmyname kolla downloads the tarballs at tarballs.o.o18:20
mnaserso would you be looking at adding a new service or modifying an existing one to install from another source?18:20
notmynamemnaser: i'm not sure I follow you question. a new service instead of tarballs.o.o? or a new openstack service? or what?18:21
mnasernotmyname my question was mostly at what your final end goal that you're trying to accomplish is and perhaps we can help hint at the best way to get there18:22
notmynamemnaser: the source would still be at tarballs.o.o. but it eg could be c files18:22
*** sbezverk has joined #openstack-kolla18:22
mnaserso there is a part which downloads the tarball locally (let me get you the code)18:22
*** tonanhngo has quit IRC18:22
notmynamemnaser: I've got two thoughts. the lesser is liberasurecode, which is a c-lang project but doesn't seem to be on tarballs. it's a dependency for swift18:22
notmynamebut actually, the real reason I'm asking is to prep for when parts of swift are in golang18:23
notmynamewith the basic question of "what needs to happen so that deployment tools (like kolla) are happy?"18:23
mnasernotmyname: okay so that's an interesting problem because its a library.  the code that builds images (kolla/images/build.py) is more on the lines of downloading source packages that are the software themselves18:23
mnaserthe runtime dependencies are pulled in the actual docker images, so for example18:24
mnaserhttps://github.com/openstack/kolla/blob/master/docker/neutron/neutron-base/Dockerfile.j2#L49-L8318:24
notmynamein the libec case, what happens when the version dependency hasn't been updated by canonical or red hat yet, but the current release of pyeclib depends on it?18:24
*** tonanhngo has joined #openstack-kolla18:25
mnaseri would imagine that instead of installing it manually, you'd have swift-base and in the swift-base image, you'd have your golang tooling which can install it18:25
notmynameit's the "golang tooling" which is the big question, isn't it? :-)18:25
mnaserso the swift parts that are in golang can have a swift-base-golang18:26
mnaserwith all the tooling installed with docker18:26
notmynamewhen you say the "swift-base image" is that the kolla/docker/swift/swift-base/Dockerfile.j2"?18:26
*** lamt has joined #openstack-kolla18:26
mnaserfor example, yes.  i'd imagine given that not all components would be based on golang, you could have swift-base-golang based on swift-base18:27
mnaserand then those components would base off of swift-base-golang18:27
mnaserthen when installing from rdo/etc, it can do a simple yum install .. when installing from source, i believe golang has the concept of dependencies already in place18:28
*** MasterOfBugs has joined #openstack-kolla18:28
mnaserso once you do go install or whatever, it'll fetch the dependencies and install/build them.. if i'm not wrong about golang18:28
notmynametypical `./configure && make && sudo make install`18:28
notmynamedoesn't matter if go or c or whatever18:29
mnaserwell i guess in the swift-{insertcbasedcomponent} image, you can do that if the install type is source18:29
notmynameok, thanks. this is very helpful18:30
mnaserthe concern is.. where does it fetch the source from and would it be hardcoded to tarballs.openstack.org18:30
notmynamewhat about the library situation (c in this case)18:30
mnaserthat's an interesting problem, i dont think we support multiple sources for a container for example18:30
notmynameok18:30
mnasernotmyname - https://github.com/openstack/kolla/blob/master/doc/image-building.rst#build-openstack-from-source18:31
mnaserim sure others can chime in, thats just my thoughts based off how much i know and howd id solve this18:32
notmynameI thought I heard something somewhere a discussion about kolla dockerfiles being moved into their respective projects. what's the status on that? is it a thing or not?18:32
notmyname(awesome specificity there)18:33
mnasernotmyname that has been a thought which has been on my mind which i think would be a huge win to kolla down the live (good bye devstack and hello faster dev envs?) but that's as far as i know :(18:33
notmynameok18:34
inc0well thing about that is it's knowing how docker works is knowledge harder to obtain than knowing how to deploy projects18:37
notmynamemnaser: inc0: thanks for your help18:37
inc0so we don't plan to move dockerfiles to projects just yet18:37
inc0as for devstack replacement - it's something we quietly talk about18:38
inc0the way I'd develop services with kolla is18:39
inc0to deploy with kolla18:39
inc0stop service you're working on (for example keystone) and run it in screen/tmux locally18:39
inc0connecting to all the databases and stuff deployed by kolla18:40
openstackgerritSayantani Goswami proposed openstack/kolla-ansible master: Add InfluxDB as a data source in Grafana  https://review.openstack.org/44668918:43
*** mgoddard has joined #openstack-kolla18:44
*** jtriley has quit IRC18:53
mnaseri've proposed this so we can get visiblity on the % of failures for our jobs - https://review.openstack.org/#/c/446697/18:53
mnaserso maybe and hopefully deploys can be voting (at some point)18:54
mnaseralso re: docker 1.13.1 -- it works, but setenforce 0 has to be called - https://review.openstack.org/#/c/446158/18:56
openstackgerritMohammed Naser proposed openstack/kolla master: Speed up builds by increasing threads for builds  https://review.openstack.org/44670119:12
openstackgerritMohammed Naser proposed openstack/kolla master: Speed up builds by increasing threads for builds  https://review.openstack.org/44670119:16
*** skramaja has quit IRC19:37
*** lamt has quit IRC19:39
*** lamt has joined #openstack-kolla19:45
*** lamt has quit IRC19:46
*** lamt has joined #openstack-kolla19:47
*** kbaegis has joined #openstack-kolla19:49
kbaegisHi guys. Is config drive supported in the nova-compute/nova-libvirt containers?19:50
*** scheuk has quit IRC19:50
inc0kbaegis: hmm, I never tried it tbh, it should tho19:51
kbaegisinc0: Cool. As I understand it genisofs has to be in $PATH19:51
mnaserkbaegis install from source or binary?19:51
kbaegis"https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/html/End_User_Guide/config-drive.html"19:51
kbaegismnaser: source19:52
kbaegisbuilt my own too ;)19:52
mnasercause binary for sure the dep will be pulled down19:52
inc0kbaegis: if it's not, you can try to use template override to install it and check if it's the case19:52
kbaegisinc0: Cool. Thought I'd ask before trying to play around with it19:53
kbaegisI have no basis to compare; never used it before19:53
kbaegisJust init scripts19:53
inc0yeah same here19:53
inc0looking at nova bindep and no genisofs there19:53
mnaserit should work19:53
mnaserhttps://github.com/openstack/kolla/blob/master/docker/nova/nova-compute/Dockerfile.j219:53
mnasergenisoimage is installed19:53
mnaserunder: {% elif install_type == 'source' %}19:53
inc0yup mnaser is right, we have genisoimage there19:54
*** mgoddard has quit IRC19:54
mnaserand the configdrive is stored in /var/lib/nova/instances/<uuid>/disk.config so compute should acces sthat19:55
mnaserand on ceph it gets stored in rbd (and compute should have access to it)19:55
mnaserso i believe it should be okay19:55
*** kbaegis has quit IRC19:55
*** kbaegis has joined #openstack-kolla19:58
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding virtualbmc to the gate  https://review.openstack.org/44155019:59
*** mpansky has joined #openstack-kolla20:02
openstackgerritQin Wang (qwang) proposed openstack/kolla-kubernetes master: [WIP] Condition and tags in requirements.yaml for keystone service  https://review.openstack.org/44446120:04
*** Jeffrey4l has quit IRC20:06
*** Jeffrey4l has joined #openstack-kolla20:07
*** lamt has quit IRC20:09
*** kbaegis has quit IRC20:09
*** kbaegis has joined #openstack-kolla20:09
*** lamt has joined #openstack-kolla20:11
*** eaguilar has joined #openstack-kolla20:13
*** fooliouno has joined #openstack-kolla20:15
*** eaguilar has quit IRC20:16
fooliounoAre there any known issues with using Weave as the overlay network for kolla-kubernetes20:17
*** eaguilar has joined #openstack-kolla20:17
fooliounoWhen I bring up the openvswitch-vswitchd-network pod, it seems to mess up the connectivity to Horizon20:17
kfox1111fooliouno: haven't tried. no known issues. but you may be one of the first to try.20:18
*** jascott1 has quit IRC20:19
vhosakotsbezverk, kfox1111: I'm still trying to get my k8s cluster up and seeing vagrant issue.  How did you guys deploy kubeadm manually without vagrant or https://docs.openstack.org/developer/kolla-kubernetes/development-environment.html?  did you guys use https://etherpad.openstack.org/p/kolla-kubernetes-deploy-guide-BP ?20:20
fooliounokfox1111: Thanks. Soon after the openvswitch pod is brought up, Wireshark ARP fails when I do a curl on the horizon dashboard IP from Kube master.20:20
fooliounoI'm ready to give up on Weave and move to Flannel.20:20
kfox1111vhosakot: I've manually deployed usually. so not sure if the guides are accurite.20:22
*** eaguilar has quit IRC20:22
kfox1111fooliouno: hmm.... the settings may be pulling your nic into the openvswitch bridge?20:23
*** notmyname has left #openstack-kolla20:23
kfox1111fooliouno: I don't know what weave requires of the underlying node.20:23
vhosakotkfox1111: how did you do it?  which doc did you refer? :)  https://kubernetes.io/docs/getting-started-guides/centos/centos_manual_config/  or  https://kubernetes.io/docs/getting-started-guides/kubeadm/ ?20:23
kfox1111vhosakot: for test systems, usually https://kubernetes.io/docs/getting-started-guides/kubeadm/ with canal.20:24
kfox1111vhosakot: for my production systems, really manually deployed. static pods for the api stuff and a hand build ca.20:24
vhosakotkfox1111: cool, after doing the steps in https://kubernetes.io/docs/getting-started-guides/kubeadm/, how can we deploy kolla-k8s on it?  run build_dev_image.sh and run_dev_image.sh that are at the end in https://docs.openstack.org/developer/kolla-kubernetes/development-environment.html#containerized-development-environment-requirements-and-usage ?20:25
vhosakotkfox1111: do we need to deploy kubeadm for kolla-k8s?20:26
*** otavio has left #openstack-kolla20:27
kfox1111vhosakot: the docs currently have a gap for deploying aproduction system. inc0 and I were planning on filling that out a bit but havent yet.20:28
kfox1111for kolla-kubernetes, you need a working k8s.20:28
kfox1111how that is stood up, kolla-kubernetes doesn't really care.20:28
vhosakotkfox1111: I want to help you and inc0 with that effort to add good docs too.  but, I need a working cluster first :)20:28
kfox1111kubeadm is one of the easier ways today.20:28
kfox1111vhosakot: cool. :)20:28
vhosakotkfox1111: ok, can I do https://kubernetes.io/docs/getting-started-guides/kubeadm/.. is it good/updated?20:29
kfox1111yeah. thats a good doc.20:29
vhosakotkfox1111: thanks a lot, I'll try it :)20:29
kfox1111ok. cool. ping me if you need some help.20:30
*** lamt has quit IRC20:32
*** lamt has joined #openstack-kolla20:35
qwanghi kfox111120:42
kfox1111qwang: hi20:43
*** mpansky has quit IRC20:44
vhosakotkfox1111: cool, how many nodes do you have? how many masters and how many workers?20:44
*** rwsu has quit IRC20:44
qwangkfox1111: I have an issue here at gate. I intercept the ceph_workflow_service to run the standalone keystone install test. the keystone chart can be installed, but after that the mariadb in the original flow can't be installed successfully.20:45
kfox1111my largest system today is 1 master, 2 ingress, 1 controller, 20 compute, and 4 vm nodes.20:45
kfox1111should be gaining multiple masters and controllers soon,20:45
qwangkfox1111: I printed out the kubectl log and it shows  something around here: http://logs.openstack.org/61/444461/6/check/gate-kolla-kubernetes-deploy-centos-binary-2-helm-entrypoint-nv/a788a4e/console.html#_2017-03-16_20_23_40_98389720:46
vhosakotcool, thanks for the info kfox111120:46
kfox1111and once I finish helmizing my condor k8s objects, aI'll put about 130 more nodes in it.20:46
sbezverkvhosakot: man I thought you already past point of playing with kubeadm ;)20:46
kfox1111qwang: looking...20:47
qwangkfox1111: thank you20:47
vhosakotsbezverk: I have been doing in the past 3 weeks, CPU, disk, RAM, vagrant issues... I will reach the point soon :)20:47
vhosakotsbezverk: how did you deploy?  let me ask you the same Q as I asked kfox1111 :)20:47
sbezverkvhosakot: I do not look for a magic button which you click and everything working, in my mind it is a waste of time. I do installation manually and it pays off.20:48
vhosakotsbezverk: acgreed, totally.. which link did you follow.. can you send it please? :)20:49
sbezverkvhosakot: it has not changed since I pasted to you last time, it is kubeadm installation20:49
vhosakotsbezverk: cool, https://kubernetes.io/docs/getting-started-guides/kubeadm/ you mean?20:49
sbezverkvhosakot: yes20:50
vhosakotsbezverk: thanks.. cool20:50
kfox1111qwang: did you ever override the element name in the mariadb?20:50
qwangkfox1111: no i did not20:50
kfox1111if not you may need to do that in the keystone service package's values.yaml20:50
qwangkfox1111: can you explain the reason for that a little bit plz?20:51
kfox1111oh. I guess that will probably need to be backed with a ceph volume too. so in the script that creates volumes, may need to create/format another one.20:51
kfox1111So, each mariadb needs a unique name  or else they will step on each other.20:52
kfox1111the element_name  value lets you customize which unique name will be used for that instance of mariadb.20:53
kfox1111so by default the global one is just called mariadb.20:53
kfox1111but a keystone one should be element_name=mariadb-keystone or something.20:53
kfox1111then it wont conflict with element_name=mariadb-glance20:53
qwangkfox1111: I delete the keystone install before I install mariadb. Isn't the first mariadb going to be deleted by helm?20:53
kfox1111its got some state that I think helm delete will leave behind.20:54
*** eaguilar has joined #openstack-kolla20:54
kfox1111I don't think helm delete currently deletes pv's?20:55
qwangi tested on my local env. it deletes pv most of time. i found one time it did not20:55
qwangdon't know the reason20:56
kfox1111I'd go ahead and just use the existing keystone chart in that test suite, and use element_name to allow the mariadb's to co'exist. If we want to test both service mariadb's and global mariadb, we can make a second gate job that does the other.21:02
qwangqwang: thanks for verifying it. I think it makes sense to split the gate job21:04
qwangkfox1111: ^^21:05
*** rwallner has quit IRC21:06
*** Pavo has joined #openstack-kolla21:12
sbezverkkfox1111: for security group issue, would you be ok to not use default group? and then start test instances with a custom sec group?21:12
*** Pavo has quit IRC21:12
kfox1111sbezverk: the fix in the ps I pointed at doesn't work?21:15
kfox1111it took me a couple days to get working.21:15
kfox1111qwang: k. go ahead and tweak it to work like its the split mariadb version, and before merge, we'll get the second gate job added.21:15
sbezverkkfox1111: oh it is working, I just thought getting non default sec group is make things a bit more robust as we do not depend what comes with new openstack release21:18
sbezverkkfox1111: if neutron decides to drop default sec group then we will be independent21:19
kfox1111neutron better not, or I'll trhow a fit. :)21:19
kfox1111I think last I tried, it was easier to get the default one tweaked, then add another.21:20
sbezverkkfox1111: could you then push ps for it ;) ??21:20
*** eaguilar has quit IRC21:25
*** eaguilar has joined #openstack-kolla21:26
kfox1111sbezverk: done21:32
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: Ocata security group fix  https://review.openstack.org/44675121:32
*** Jeffrey4l has quit IRC21:34
sbezverkkfox1111: cool thanks!21:38
*** schwicht has quit IRC21:39
kfox1111np. :)21:40
*** jrobinson has joined #openstack-kolla21:42
*** eaguilar has quit IRC21:47
*** fooliouno has quit IRC21:47
*** rwellum has quit IRC21:47
*** Jeffrey4l has joined #openstack-kolla21:48
*** eaguilar has joined #openstack-kolla21:49
*** Jeffrey4l has quit IRC21:50
*** Jeffrey4l has joined #openstack-kolla21:50
*** eaguilar has quit IRC21:59
*** eaguilar has joined #openstack-kolla22:00
*** eaguilar has quit IRC22:08
*** mpansky has joined #openstack-kolla22:09
*** rhallisey has quit IRC22:10
*** eaguilar has joined #openstack-kolla22:12
sbezverksrwilkers: portdirect: ping22:12
*** mpansky has quit IRC22:16
*** eaguilar has quit IRC22:16
inc0bach22:28
*** eaguilar has joined #openstack-kolla22:28
inc0back22:28
inc0Bach is cool too, but not what I meant22:28
inc0anyone has quickstart etherpad for k8s handy22:28
inc0?22:28
*** ggillies has joined #openstack-kolla22:30
openstackgerritMerged openstack/kolla-kubernetes master: Ocata security group fix  https://review.openstack.org/44675122:34
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding virtualbmc to the gate  https://review.openstack.org/44155022:36
*** furlongm has joined #openstack-kolla22:36
*** gfidente|afk has quit IRC22:42
*** kbaegis has quit IRC22:48
*** manheim has joined #openstack-kolla22:51
openstackgerritOpenStack Proposal Bot proposed openstack/kolla master: Updated from global requirements  https://review.openstack.org/44677122:52
openstackgerritOpenStack Proposal Bot proposed openstack/kolla-ansible master: Updated from global requirements  https://review.openstack.org/44677222:52
openstackgerritOpenStack Proposal Bot proposed openstack/kolla-kubernetes master: Updated from global requirements  https://review.openstack.org/44508922:52
kfox1111https://github.com/kubernetes-incubator/external-storage/tree/master/ceph/cephfs interesting.23:03
portdirectsbezverk: pong23:05
*** Pavo has joined #openstack-kolla23:07
vhosakotsbezverk: kfox1111, ok! my kubeadm k8s cluster is up --> http://paste.openstack.org/show/603032/.  I followed https://kubernetes.io/docs/getting-started-guides/kubeadm/ and the steps worked great! :)23:08
*** eaguilar_ has joined #openstack-kolla23:08
vhosakotsbezverk, kfox1111: what is the next step? how can I deploy kolla-k8s on top of my empty kubeadm-based k8s cluster?  should I run build_dev_image.sh and run_dev_image.sh at the end in https://docs.openstack.org/developer/kolla-kubernetes/development-environment.html#containerized-development-environment-requirements-and-usage ?23:09
*** eaguilar has quit IRC23:10
vhosakotsbezverk: kfox1111: I'm logging off for the day, and will check your replies later in the IRC logs.  thanks for all the help today! :)23:13
*** Jeffrey4l has quit IRC23:14
*** jrobinson is now known as jrobinson-afk23:19
*** vhosakot has quit IRC23:20
sbezverkvhosakot: same thing for me. I just go through step by step manually, using script just as a guideline and for copy/change and paste commands23:20
*** yingjun has quit IRC23:20
*** Pavo has quit IRC23:21
*** Jeffrey4l has joined #openstack-kolla23:29
spsuryamorning all23:33
*** kbyrne has quit IRC23:34
*** masber has quit IRC23:36
*** kbyrne has joined #openstack-kolla23:38
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding virtualbmc to the gate  https://review.openstack.org/44155023:38
*** lamt has quit IRC23:41
*** jrobinson-afk is now known as jrobinson23:42
*** zioproto has joined #openstack-kolla23:44
*** dave-mccowan has quit IRC23:45
*** manheim has quit IRC23:45
*** srwilkers has quit IRC23:53

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