Tuesday, 2016-03-01

*** blahRus has quit IRC00:06
*** jtriley has quit IRC00:10
SamYaplesdake: gate doesnt like the pep800:13
openstackgerritSam Yaple proposed openstack/kolla: Remove keystone admin token  https://review.openstack.org/28562500:14
*** sdake has quit IRC00:14
*** rhallisey has joined #kolla00:16
dave-mccowani'm getting this error message on deploy: One or more undefined variables: 'nova_keystone_user' is undefined00:30
dave-mccowannova_keystone_user looks defined to me.  do i need to rebuild my containers?00:30
dave-mccowansdake samyaple ^^00:31
SamYapledave-mccowan: this was fixed recently00:38
SamYaplecheck mastr00:38
*** jtriley has joined #kolla00:41
openstackgerritHui Kang proposed openstack/kolla: Fix missing libraries for ceilometer  https://review.openstack.org/28627400:57
*** skape has joined #kolla01:00
skapeHi01:01
skapeI'm having problems running ./tools/kolla-ansible deploy and when I tried ./tools/kolla-ansible prechecks it failed also01:03
skapeTASK [prechecks : Checking Docker version]      fails but I have installed docker 1.8 with yum on centos 701:05
skapewhat is the correct version for docker ?01:05
SamYapleskape: for master the correct version is >=1.10.001:08
skapewith the command curl -sSL https://get.docker.io | bash will install this version ????01:09
*** jasonsb has joined #kolla01:12
skapetkanks for the info!01:16
*** iceyao has joined #kolla01:17
*** skape has left #kolla01:17
*** alisonh has joined #kolla01:19
*** prithiv1 has quit IRC01:29
*** iceyao has quit IRC01:32
*** iceyao_ has joined #kolla01:32
*** Jeffrey4l has joined #kolla01:47
*** tfukushima has joined #kolla01:51
*** tfukushima has quit IRC01:54
*** rhallisey has quit IRC02:04
*** rtmie has quit IRC02:04
*** dims has quit IRC02:04
*** iceyao has joined #kolla02:04
*** rtmie has joined #kolla02:04
*** iceyao_ has quit IRC02:06
*** dims has joined #kolla02:08
*** dims has quit IRC02:13
*** Marga__ has joined #kolla02:16
*** dims has joined #kolla02:17
*** jtriley has quit IRC02:19
*** Marga_ has quit IRC02:19
*** tfukushima has joined #kolla02:19
*** tfukushima has quit IRC02:22
*** tfukushima has joined #kolla02:24
*** tfukushima has quit IRC02:26
*** jtriley has joined #kolla02:28
*** tfukushima has joined #kolla02:35
*** pbourke_ has quit IRC02:46
*** iceyao_ has joined #kolla02:47
*** pbourke_ has joined #kolla02:47
*** jtriley has quit IRC02:47
*** iceyao has quit IRC02:50
*** Allen_Gao has quit IRC02:50
*** Allen_Gao has joined #kolla02:51
*** jtriley has joined #kolla02:58
*** jtriley has quit IRC03:18
*** dims has quit IRC03:19
*** yuanying has joined #kolla03:21
*** yuanying_ has quit IRC03:23
*** Marga__ has quit IRC03:26
*** yuanying has quit IRC03:27
*** Marga_ has joined #kolla03:30
*** Marga_ has quit IRC03:35
*** iceyao has joined #kolla03:35
*** iceyao_ has quit IRC03:40
*** Marga_ has joined #kolla03:43
*** klint has joined #kolla03:44
*** dave-mccowan has quit IRC03:45
*** jtriley has joined #kolla03:45
openstackgerritHui Kang proposed openstack/kolla: Fix missing libraries for ceilometer  https://review.openstack.org/28627403:47
*** Marga_ has quit IRC03:47
*** iceyao has quit IRC04:06
*** yuanying has joined #kolla04:10
*** Marga_ has joined #kolla04:16
*** Marga_ has quit IRC04:16
*** Marga_ has joined #kolla04:17
*** daneyon_ has quit IRC04:26
*** vhosakot has joined #kolla04:46
*** phuongnh has joined #kolla04:56
openstackgerritMD NADEEM proposed openstack/kolla: Manila ubuntu binary container  https://review.openstack.org/28637904:59
*** Allen_Gao has quit IRC05:08
*** jtriley has quit IRC05:16
*** salv-orl_ has joined #kolla05:19
*** Marga_ has quit IRC05:20
*** Allen_Gao has joined #kolla05:20
*** salv-orlando has quit IRC05:22
*** daneyon has joined #kolla05:25
*** Marga_ has joined #kolla05:30
*** Allen_Gao has quit IRC05:35
*** Allen_Gao has joined #kolla05:40
openstackgerritMerged openstack/kolla: Remove keystone admin token  https://review.openstack.org/28562506:11
*** sdake has joined #kolla06:11
asalkeldthe gate is unhappy06:16
nihiliferbut only for kolla-mesos :/06:16
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Restart daemons if their config changes  https://review.openstack.org/28466406:17
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Make write_file return if the contents changed  https://review.openstack.org/28639806:17
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Move generate_configs into the Command class  https://review.openstack.org/28639906:17
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Extend kolla-mesos-config to be able to set zookeeper variables  https://review.openstack.org/28640006:17
asalkeldsome package has a broken wheel06:18
*** daneyon has quit IRC06:23
*** sdake has quit IRC06:27
*** sdake has joined #kolla06:33
sdakeevening06:35
sdakeis gate still  bsuted?06:37
sdakethere were changes to requirements.txt recently06:37
sdakeone of them was setuptools06:38
sdakeasalkeld ^^06:38
sdakethat might interact with wheel06:38
asalkeldna, it's local too06:39
asalkeldseems like someone uploaded a broken package06:39
nihiliferumm... local too? i removed .tox/py27 dir, runned tests, and they work perfectly06:42
asalkeldhttps://pypi.python.org/pypi/portalocker#downloads06:42
asalkelduploaded on 2016-02-2906:42
nihiliferdo we know which of our deps depend on portalocker?06:44
asalkelddcos i think06:44
nihilifer:/06:44
nihiliferyes, you're right06:45
asalkeldi think 0.5.4 portalocker works06:46
asalkeldmaybe we can restrict it to that06:46
nihilifersure. but it's not in our openstack deps06:46
sdakehard pins will be removed y global requirements bot06:47
nihiliferso we can only pin in mesosphere's repo06:47
asalkeld~/work/requirements$ (master) git grep portalocker06:47
asalkeldupper-constraints.txt:portalocker===0.5.506:47
sdakeoh ya upper constrInts06:47
nihiliferah, ok06:47
asalkeldgit pull and now ...06:47
nihiliferasalkeld: you will prepare a patch to reqirements or should i do this?06:47
asalkeldgit grep portalocker06:48
asalkeldupper-constraints.txt:portalocker===0.5.706:48
asalkelddoh06:48
asalkeldlet's see who did that06:48
nihiliferopenstack proposal bot :P06:48
openstackgerritSteven Dake proposed openstack/kolla: DO NOT MERGE  https://review.openstack.org/28640906:49
asalkeldnihilifer: worth asking infra what to do, as that job may just revert our change06:50
nihiliferok06:51
sdakeit wont remove it if we dont a pprove the changes06:51
sdakeif this is some short term pain06:51
asalkeldnihilifer: getting to 5pm here - need to take a break (have a meetings later :( )06:51
sdakejust revert it and send a note asking foks not to merge the proposal ot for the shor tterm06:51
asalkeldnihilifer: maybe email the author Wolph@wol.ph06:52
asalkeldif he uploads a new one, it might save some time06:53
nihiliferasalkeld: ok, will do this today06:53
mdnadeemnihilifer, Jeffrey4l , if get time, please review it : https://review.openstack.org/#/c/285138/06:54
Jeffrey4lmdnadeem, roger06:55
sdakeJeffrey4l evening06:57
sdakeJeffrey4l nice job on the fast turnaround on reconfigure06:57
sdaketbh I didn't think it would be ready to go ;)06:57
*** Marga_ has quit IRC06:57
sdakedid glance merge yet?06:57
Jeffrey4lsam found some issue about the reconfigure. I should fix that first.06:58
*** achanda has quit IRC06:58
Jeffrey4lit impact keystone too. sdake06:59
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: [WIP] Add heka support  https://review.openstack.org/28630106:59
*** daneyon has joined #kolla06:59
sdakeJeffrey4l  could you expand please06:59
sdakeyes please get keysstone fied, then make glance the reference implementation that people can copy07:00
*** tfukushima has quit IRC07:00
Jeffrey4lsdake, see the sam's comment https://review.openstack.org/#/c/285873/3/ansible/roles/glance/tasks/do_reconfigure.yml07:00
sdakeif eveyroen copies 2 or 3 in the core team, we should be able to hit the 2-4th with it07:00
*** tfukushima has joined #kolla07:00
Jeffrey4lthe process should be ok. now need improve the 1) docker restart command to kolla_docker 2) docker exec <> printenv to kolla_docker07:01
sdakeJeffrey4l right i just read the review07:01
sdakeJeffrey4l if you coudl make that your top priority i'd super appreciate it :)07:02
Jeffrey4lsdake, i am working on it.07:02
sdakedo you have other kolla work you think is higher priority?07:02
Jeffrey4labout reconfigure? or some thing else?07:02
sdakebugs -> RC07:02
sdakeanything else07:02
Jeffrey4lno.07:02
sdakepretty much jerked aroud with getting my kids computer back to the manufactuer today07:03
sdakeALL DAY07:03
*** daneyon has quit IRC07:04
sdaketomorrow morning i am putting my lab back together, then tearing it apart on the 15th07:04
Jeffrey4lshould buy a new one. lol07:04
sdakeso i'll have 2 weeks of multinode availale07:04
sdakeit cost 10k07:04
sdakenot buying a new one ;)07:04
Jeffrey4l:o07:05
sdakehttps://drive.google.com/file/d/0B8q6xDPETSkHUlJjQWtFVzhPb2s/view?usp=sharing07:06
Allen_Gaosdake: looks great!07:06
sdakethe ups guy complimented us on how well we packaged the palette ;)07:06
sdakehe said normally when they do pallette pickups at peoples homes its a disaster07:07
Jeffrey4lwater-cooled ? cool07:07
sdakehe was in and out in 5 mins07:07
sha_Hi guys...07:07
sdakesha_ if you have a bug to report, please use passtebin :)07:07
sha_I have created local repository for docker..07:07
sha_ha.. sure :)07:07
mdnadeemsdake, Please let me know if https://blueprints.launchpad.net/kolla/+spec/ansible-unit-tests can be merge in Mitaka ?07:08
sdake1% power, gotta run07:08
sdakemdnadeem the answer is yes07:08
sdakeget it in good progress state (the blueprint)07:08
mdnadeemsdake, ok, i will try to cover all test case with in this week07:08
sdakemdmit looks like your blueprint is in good progress to me07:08
mdnadeemsdake, if possible please enroll my name in kolla team list on launch pad, my launchpad id is mail2nadeem92, Thanks :)07:10
*** sdake has quit IRC07:10
*** daneyon has joined #kolla07:10
sha_I have created local registry for docker images.  But when I tried building the images using ./tools/build.py -b ubuntu -t source --registry 172.22.2.81:4000 --push07:10
sha_Iam getting this error:07:11
sha_07:11
*** iceyao has joined #kolla07:12
*** sdake has joined #kolla07:12
sha_failed: [localhost] => {"failed": true} msg: Unknown error message: Error while pulling image: Get http://172.22.2.81:4000/v1/repositories/kollaglue/ubuntu-source-kolla-toolbox/images: dial tcp 172.22.2.81:4000:07:13
sha_getsockopt: connection refused07:13
Jeffrey4lsha_, paste, paste, paste07:13
Jeffrey4lsha_, http://paste.openstack.org/ http://paste.openstack.org/ http://paste.openstack.org/07:13
Jeffrey4lpls07:13
nihiliferyes, we told about this yesterday, didn't we?07:13
nihilifersecond thing07:13
nihilifer1) check whether docker registry is running07:14
Jeffrey4lmany times.07:14
nihilifer2) check where it's running, what's its IP address / hostname / hwatever07:14
nihilifer3) set it in /etc/kolla/globals.yml07:14
nihiliferand once again, paste plz07:14
sdakesha_ run docker ps07:14
sdakeinto a paste plz07:14
sdakeif your on centos you can run docker ps | fpaste07:15
sha_http://paste.openstack.org/show/488702/07:15
sdakei dont know if ubuntu has a paste service built into the distro07:15
*** achanda has joined #kolla07:15
*** mikelk has joined #kolla07:16
sdakesha_ I need to see docker ps - to see how you started your registry07:16
*** Allen_Gao has quit IRC07:17
vhosakotgood night!07:17
sdakevhosakot night :)07:17
sha_docker ps07:17
sha_http://paste.openstack.org/show/488704/07:17
*** vhosakot has quit IRC07:18
sdakesha_ try telnet host_ip_of_registry 400007:18
sdakesha_ what ip is your registry running on?07:19
sha_I have kept in /global.yml as docker_registry: "172.22.2.81:4000"07:19
Jeffrey4lmemcached container is up. the docker-registry should be ok.07:19
sdakeis 172.22.2.81 the node where your registry is running?07:19
sdakemy first guess would be a firewall problem07:20
sha_When i do telnet  it is giving : http://paste.openstack.org/show/488706/07:21
sdakeis 172.22.2.81 a machine in your network?07:21
*** Allen_Gao has joined #kolla07:24
sha_sdake : able to ping that ip07:24
sdakewhere is your registry running?07:24
sha_on  172.22.2.81:400007:25
sdakeon the machine 172.22.2.81 your running docker?07:25
sha_No docker is not running on that machine07:26
sdakewell how could the registry possibly run there?07:26
sdakewhat machine is docker running on - ip address07:26
sha_on local machine07:26
sdakeok well that is where your registry is running07:26
sdakewht is the ip addresss of your local machine07:26
sdakeip link show will show you07:27
sdakeeth0 is what your looking for07:28
sdakepaste ip link show if you need help parsing it07:28
sha_http://paste.openstack.org/show/488707/07:28
sha_can I run docker registery on local system?07:29
sdakeis eth0 on a virtual machine?07:29
sha_No..07:29
sdakerun ifconfig and paset it07:29
sdakeeth0 has no ip address assigned to it07:29
sdakeaccording to ip link show07:29
sdakealso you have to turn off libvirtd to run kolla07:30
sdakei can tell yourrunning libvirt from virbr007:30
sha_http://paste.openstack.org/show/488708/07:30
sdakesha_ your registry is running at 172.16.73.114:400007:32
sdaketry telnet 172.6.73.114 400007:32
sdakethe registry doesn't run at sosme random address just because its in globals.yml07:32
sdakethe registry runs on the ip address of the machine docker is running on07:32
sdake./build.py --regisstry 172.6.73.114:4000 --type source --base ubuntu07:33
sha_ok..Then I will change the Ip address and build it07:33
sdake./build.py --registry 172.6.73.114:4000 --push07:34
sdakerun those two comamnds07:34
sha_Thank you soo much!!07:34
sdakethat will put your images in your registry07:34
sdakeroger your welcome07:34
*** Allen_Gao has quit IRC07:34
sdakeonce you get your images in your regisstry, you need to change globals.yml to pull form it07:35
sdakeit takes me 12 minutes to build and 5 minutes to push07:35
sdakebut I am on gige to the internet with PCIE NVMe SSD07:35
sdakeso look at 17 mins upwards of one hour if your net/gear is slow07:35
sdakealso i dont know if master is unbroken yet07:36
sdakei have a gate test running now to find out07:36
sdakebut the gate has a 2-3 hour lag because its deadline time so eveyrone jamming on patch submissions07:36
*** akwasnie has joined #kolla07:41
sdakeok 1am time to ptfo07:41
sdakenight all07:41
sdakehi akwasnie :)07:41
sdakeakwasnie elemoine can you both give me a quick update on the state of EHK07:42
sdakei saw there is a patch to integrate them07:42
sdakeis that all that is needed?07:42
openstackgerritMartin André proposed openstack/kolla: Add a new tool to help find the latest versions  https://review.openstack.org/24848107:43
elemoine_sdake: yes07:43
akwasniehi sdake07:43
sdakenice07:43
sdakewell i can sleep well knowing that is done ;)07:43
elemoine_that patch connects Heka, Elasticsearch and Kibana together07:44
akwasniesdake we tested it and it is ok:)07:44
sdakeare logs stored on the local nodes as well?07:44
sdakethat was an unexpressed requirement07:44
elemoine_I've tested it in both AIO and multinode modes07:44
elemoine_sdake: yes07:44
sdakenice07:44
elemoine_in the kolla_logs volume07:44
sdakesweet07:44
sdakei will check it out tomorrow when I reassemble my lab07:45
sdakeworking in vms just not viable07:45
akwasniegood, thanks07:45
elemoine_out of curiosity, how machines do you use for kolla? do you test in multinode?07:45
sdake3 machines for deploy plus 1 to deploy from07:46
*** sdake has quit IRC07:48
*** Allen_Gao has joined #kolla07:49
openstackgerritEric Lemoine proposed openstack/kolla: Set graphics_ip and _port in Vagrantfile  https://review.openstack.org/28642707:54
*** fgimenez has joined #kolla08:00
*** fgimenez has joined #kolla08:00
*** achanda_ has joined #kolla08:02
*** achanda has quit IRC08:04
*** achanda_ has quit IRC08:04
*** chandankumar has joined #kolla08:06
*** slagle has quit IRC08:06
*** achanda has joined #kolla08:08
*** ccesario has quit IRC08:09
*** akwasnie has quit IRC08:10
*** daneyon has quit IRC08:17
*** akwasnie has joined #kolla08:19
*** achanda has quit IRC08:27
*** britthouser has quit IRC08:29
*** britthouser has joined #kolla08:30
openstackgerritRodolfo Alonso Hernandez proposed openstack/kolla: Add required packages to ironic-conductor container  https://review.openstack.org/28615008:32
*** ccesario has joined #kolla08:38
*** salv-orl_ has quit IRC08:47
*** openstackgerrit has quit IRC08:48
*** openstackgerrit has joined #kolla08:48
*** salv-orlando has joined #kolla08:48
openstackgerritMD NADEEM proposed openstack/kolla: Manila ubuntu binary container  https://review.openstack.org/28637908:56
openstackgerritMartin André proposed openstack/kolla: Add a new tool to help find the latest versions  https://review.openstack.org/24848108:57
*** gfidente has joined #kolla08:58
*** athomas has joined #kolla09:01
*** chandankumar has quit IRC09:02
*** mbound has joined #kolla09:06
*** chandankumar has joined #kolla09:09
*** salv-orlando has quit IRC09:11
*** iceyao has quit IRC09:15
*** iceyao has joined #kolla09:16
*** Serlex has joined #kolla09:22
*** prithiv has joined #kolla09:34
*** prithiv has quit IRC09:35
*** Allen_Gao has quit IRC09:41
*** amnk has joined #kolla09:48
*** prithiv has joined #kolla09:53
*** kproskurin has joined #kolla09:54
*** tfukushima has quit IRC10:27
-openstackstatus- NOTICE: Gerrit is going to be restarted due to poor performance10:34
*** ChanServ changes topic to "Gerrit is going to be restarted due to poor performance"10:34
*** prithiv has quit IRC10:36
*** prithiv has joined #kolla10:38
*** ChanServ changes topic to "Kolla IRC meetings on Wednesday 16:30 UTC (Day light savings doesn't apply) - Agenda @ https://wiki.openstack.org/wiki/Meetings/Kolla - IRC channel is *LOGGED* @ http://eavesdrop.openstack.org/irclogs/%23kolla/"10:40
-openstackstatus- NOTICE: gerrit finished restartign10:40
*** prithiv has quit IRC10:42
*** kproskurin_ has joined #kolla10:43
*** prithiv has joined #kolla10:43
*** kproskurin has quit IRC10:43
*** kproskurin_ is now known as kproskurin10:43
*** phuongnh has quit IRC10:45
openstackgerritMerged openstack/kolla-mesos: Add ANSIBLE_NOCOLOR to chronos job  https://review.openstack.org/28464810:46
openstackgerritMerged openstack/kolla-mesos: Add explicit calls to extend_start and skip the default  https://review.openstack.org/28335610:47
*** iceyao has quit IRC10:48
openstackgerritMerged openstack/kolla-mesos: Fix the running of apache based services  https://review.openstack.org/28397210:48
*** dims has joined #kolla11:03
openstackgerritMD NADEEM proposed openstack/kolla: WIP: Added unit test for kolla_docker  https://review.openstack.org/28513811:10
*** Sara_ has joined #kolla11:19
Sara_Hi11:19
*** vhosakot has joined #kolla11:19
*** vhosakot has quit IRC11:19
*** vhosakot has joined #kolla11:20
*** Allen_Gao has joined #kolla11:21
openstackgerritMD NADEEM proposed openstack/kolla: WIP: Added unit test for kolla_docker  https://review.openstack.org/28513811:22
openstackgerritMD NADEEM proposed openstack/kolla: Added unit test for check container  https://review.openstack.org/28651311:28
sha_Hi..11:33
*** akwasnie has quit IRC11:33
sha_I am facing problem with keystone during Kolla deploy11:33
sha_Error : http://paste.openstack.org/show/488737/11:34
sha_Can anyone help me?11:34
*** iceyao has joined #kolla11:34
*** iceyao_ has joined #kolla11:38
*** salv-orlando has joined #kolla11:41
*** iceyao has quit IRC11:42
*** akwasnie has joined #kolla11:46
*** Jeffrey4l has quit IRC11:51
*** prithiv has quit IRC11:54
*** prithiv has joined #kolla11:57
*** salv-orlando has quit IRC11:58
openstackgerritMauricio Lima proposed openstack/kolla: Update cleanup-containers to remove ceph containers  https://review.openstack.org/28245111:59
*** limamauricio has joined #kolla11:59
limamauriciomorning guys12:00
*** prithiv has quit IRC12:05
*** prithiv has joined #kolla12:06
*** prithiv has quit IRC12:08
*** Jeffrey4l has joined #kolla12:09
*** ccesario has quit IRC12:24
sha_Hi guys..12:24
sha_I am facing problem with keystone during Kolla deploy12:24
sha_Error : http://paste.openstack.org/show/488737/12:24
sha_Can anyone help me?12:24
*** dave-mccowan has joined #kolla12:27
*** jtriley has joined #kolla12:28
*** iceyao has joined #kolla12:32
*** iceyao_ has quit IRC12:35
*** jtriley has quit IRC12:36
*** iceyao has quit IRC12:36
*** iceyao_ has joined #kolla12:36
limamauricioHey Jeffrey4l :)12:43
*** rhallisey has joined #kolla12:43
Jeffrey4llimamauricio, hi12:43
Jeffrey4lsup12:43
limamauricioI updated my patch, check if everything is ok :)12:43
limamauriciohttps://review.openstack.org/#/c/269688/12:43
nihilifersha_: i'd start with doing12:44
limamauricioyour review is important12:44
limamauricio^^12:44
nihilifersource openrc12:44
nihiliferand trying to execute some basic cli commands to verify whether keystone is working at all12:44
nihiliferin example12:44
nihiliferopenstack user list12:44
nihiliferopenstack project list12:44
nihiliferetc.12:44
nihiliferyou may use --debug option for that12:45
Jeffrey4llimamauricio, Cannot Merge? you need a base first.12:45
nihiliferand after executing these commands, check the loks of keystone - "docker logs keystone"12:45
Jeffrey4llimamauricio, the gate is OK now. So ensure all the jenkins check is green.12:45
nihilifersha_: and please don't repost the same thing in hour period...12:45
sha_ok12:46
*** shardy has quit IRC12:47
*** macsz has joined #kolla12:51
Jeffrey4llimamauricio, you patch can not merge now. Please rebase to master. leave a recheck is not a good idea.12:52
elemoine_the services' initial logs can be viewed using "docker logs <container_name>", but keep in mind that the services logs now are in the kolla_logs  volume (/var/lib/docker/volumes/kolla_logs/_data)12:52
limamauricioi know12:52
limamauriciojust wait ;)12:52
Jeffrey4l:D12:52
*** salv-orlando has joined #kolla12:55
openstackgerritMerged openstack/kolla: Add required packages to ironic-conductor container  https://review.openstack.org/28615012:59
openstackgerritMerged openstack/kolla: Move ironic-discoverd to ironic-inspector  https://review.openstack.org/28065513:00
*** m3m0 has joined #kolla13:00
openstackgerritJeffrey Zhang proposed openstack/kolla: Add kolla_docker action for reconfigure  https://review.openstack.org/28657013:01
*** dims has quit IRC13:02
*** jmccarthy has quit IRC13:05
*** jmccarthy has joined #kolla13:06
*** dims has joined #kolla13:08
*** prithiv has joined #kolla13:13
openstackgerritMauricio Lima proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968813:14
limamauricioJeffrey4l, Done :)13:14
Jeffrey4lcool13:15
*** sdake has joined #kolla13:16
*** ccesario has joined #kolla13:18
openstackgerritJeffrey Zhang proposed openstack/kolla: Reconfigure glance service  https://review.openstack.org/28587313:18
*** sdake has quit IRC13:21
*** akwasnie has quit IRC13:21
*** sdake has joined #kolla13:21
*** kproskurin has quit IRC13:24
limamauriciomorning sdake, manila have many drivers, maybe can be interesting to think of a way to make the kolla support these drivers in the future13:25
limamauricioSamYaple ^13:25
sdakelimamauricio yes i'd like to sort out plugins in the future in a reasonable way13:25
sdakeatm we don't hve them sorted out13:25
sdakewe have an austin summit session on plugins13:25
*** alger has joined #kolla13:26
limamauriciosdake, interesting13:26
*** amnk has quit IRC13:28
*** Serlex has quit IRC13:33
*** slagle has joined #kolla13:33
limamauricio2016-03-01 13:33:59.617 | ERROR:kolla.cmd.build:keystone:Error'd with the following message 2016-03-01 13:33:59.617 | ERROR:kolla.cmd.build:keystone:The command '/bin/sh -c yum -y install         httpd         mod_wsgi     && yum clean all     && sed -i -r 's,^(Listen 80),#\1,' /etc/httpd/conf/httpd.conf' returned a non-zero code: 113:35
limamauriciogate-kolla-dsvm-deploy-centos-source ^13:36
limamauricio:/13:36
*** iceyao_ has quit IRC13:38
sdakelima thanks i'll look at the source13:40
sdakelimamauricio ^13:40
Jeffrey4llimamauricio, done13:43
limamauricioi think someone needs to define when and where to use two blank lines13:44
limamauricioin some files are one in the other are two13:44
limamauriciois one*13:45
sdakelimamauricio  the code looks correct13:46
limamauriciook, sdake13:46
*** Marga_ has joined #kolla13:46
sdakebut clearly something is wrong13:46
sdakelimamauricio let me connect to not my vpn and run a build there13:49
*** Marga_ has quit IRC13:50
*** shardy has joined #kolla13:50
*** sdake_ has joined #kolla13:50
*** chandankumar has quit IRC13:52
*** sdake has quit IRC13:54
*** Serlex has joined #kolla13:55
*** mbound has quit IRC13:56
SamYaplemorning13:56
sdake_limamauricio centos source builds for me13:56
sdake_keystone atleast13:56
*** rmart04 has joined #kolla13:56
sdake_limamauricio try a recheck13:56
sdake_limamauricio do you have a link tothe review in question?13:56
*** limamauricio_ has joined #kolla13:57
sdake_hey SamYaple13:57
*** limamauricio has quit IRC13:57
sdake_gate is green from last night https://review.openstack.org/#/c/286409/ yay ;)13:57
limamauricio_sdake_ gate-kolla-dsvm-deploy-centos-source was finished successfully13:57
sdake_which gate is failing for you lima?13:58
*** klint has quit IRC13:59
limamauricio_It was this gate that the error occurred sdake_13:59
sdake_oh so you mean the error is on and off?13:59
limamauricio_maybe, i don't know13:59
SamYaplesdake_: gates not actually all good13:59
SamYapleit mostly works but i need to finish out the v3 keystone or horizon will still have issues14:00
limamauricio_ I do not know how this gate works14:00
sdake_limamauricio_ where did you see the error you pasted above14:00
SamYaplelimamauricio_: it just runs the playbooks and launches an instance14:00
SamYapleif all of that is successfully it passes14:00
limamauricio_i understood :)14:01
limamauricio_I have to change a lot in pacth manila now. God, it has no end :D14:02
sdake_SamYaple well the v3 keystone missing from horizon doesn't appear to impact the gate14:02
*** vhosakot has quit IRC14:03
*** chandankumar has joined #kolla14:03
*** chandankumar has quit IRC14:05
*** chandankumar has joined #kolla14:05
SamYapleit does not14:07
*** akwasnie has joined #kolla14:11
*** mbound has joined #kolla14:15
openstackgerritMerged openstack/kolla: Update cleanup-containers to remove ceph containers  https://review.openstack.org/28245114:16
*** XuChao918 has joined #kolla14:16
SamYaplesdake_: 1.1.014:18
SamYaplekeeping the gate stable while we are merging into that branch feels nigh impossible14:18
SamYapleat least with the time available14:18
sdake_http://logs.openstack.org/73/285873/4/check/gate-kolla-pep8/c35e63a/console.html#_2016-03-01_13_30_29_16614:18
*** XuChao918 has quit IRC14:19
*** sdake_ is now known as sdake14:19
sdakeSamYaple i hear what your saying14:19
sdakeif we can have a patch stream14:19
sdakewhere at the end is a green gate14:19
SamYapleso is a long patchset that gets it from where it is to stable is that ok?14:19
sdakei think thatwould be good enough14:19
SamYapleok that works for me14:19
SamYapleso block the first one, get all approved, then merge first14:19
sdakeyup14:19
SamYapleok i can make that work14:20
sdakethis is atypical, but since we don't have voting gates it doesn't matter ;)14:20
sdakeSamYaple please take a look at that pep8 failure14:20
sdakeits in kolla_docker.py looks like a simple resolution14:20
*** Xu_Chao has joined #kolla14:20
sdakei think some pep8 tools are running differently on different notes14:20
sdake(the link above)14:20
SamYaplesdake: why?14:20
sdakei would have thought kolla_docker was in the exclude lsit14:21
SamYapleno14:21
SamYaplewe havent exluded ansible modules for a long time14:21
sdakebecause pep8 works in some cases and not in others14:21
SamYaplethat patch you were looking at added that funciton...14:21
SamYapleits a valid failure14:21
sdakeoh duh14:21
sdakeso used to invalid failures :)14:21
sdakeand just woke up ;)14:22
Xu_Chao openstack-ansible project support the deployment of it HA architecture?14:22
SamYapleXu_Chao: of course!14:23
SamYaplei use it almost exlusively14:23
sdakeXu_Chao  you mean kolla or openstack-ansible?14:23
sdakeI don't know what openstack-ansible does14:23
SamYapleXu_Chao: yea sorry i missted that. i read Kolla. but yes both projects support HA14:24
SamYapleI use Kolla almost exlusively :)14:24
Xu_ChaoI mean openstack-ansible14:25
Xu_Chaothanks14:25
sdakeXu_Chao openstack-ansible has a irc channel if you want to follow up14:25
sdake#openstack-ansible14:25
Xu_Chaothanks.:-)14:27
*** mbound has quit IRC14:30
*** stvnoyes has quit IRC14:32
*** shardy has quit IRC14:33
sha_Hi.. Where to specify domain for keystone while creating admin, project and role during Kolla?14:33
sha_am getting error for that14:33
sdakesha_ are you using msater?14:33
*** stvnoyes has joined #kolla14:33
sdakeas in master from t-6 hours ago14:33
sdakeif not, git pull --rebase14:33
sdakeand copy over the new config files14:33
sdakeand rebuild14:34
*** mbound has joined #kolla14:34
sha_ansible14:34
sha_yes.. master14:35
*** shardy has joined #kolla14:35
*** akwasnie has quit IRC14:41
sha_its using v2/.. as per my knowledge it doesnt require domain (for v2)..even then it is throwing error for "could not find domain"14:41
SamYaplesha_: after rebuild did you reset your environment?14:42
SamYaplemaster is a constantly changing thing you need to build new containre and deploy a _new_ environment14:42
sha_which environment?14:43
sha_Kolla?14:43
sha_I built thrice..14:44
*** chandankumar has quit IRC14:44
*** akwasnie has joined #kolla14:44
*** jtriley has joined #kolla14:45
SamYaplesha_: it sounds like you didnt remove the existing environment then14:45
dave-mccowansdake what do you kolla folks do on Friday of summit?14:46
sha_ok.. I will check14:46
SamYapledave-mccowan: thats where we do most planning14:47
dave-mccowanwe don't know yet if kolla will have the AM or PM slot, right?  /me is booking plane tickets14:47
*** sdake has quit IRC14:49
openstackgerritSam Yaple proposed openstack/kolla: [WIP] Fix Keystone v3 and Horizon  https://review.openstack.org/28663714:49
Jeffrey4lSamYaple, what do you want about the {{ container_name }} in the kolla_docker restart PS?14:50
SamYapleJeffrey4l: remove it and use with_items14:50
Jeffrey4luse with_items with include ?14:51
SamYapleno14:51
SamYapleinside do_reconfigure14:51
openstackgerritMerged openstack/kolla-mesos: Add state info to commands  https://review.openstack.org/27142214:51
SamYaplelike we do everywhere else14:51
Jeffrey4lBut it will be only one item forever.14:51
SamYapleyou can include multiple items14:52
Jeffrey4lI want to restart/reconfigure the service, one by one.14:52
SamYaplei dont agree with that14:52
SamYapleand i certainly do agree with this variable abstraction14:52
SamYaplewe have (mostly) gotten away from that14:52
SamYapleit broke many times before we learned our lesson14:53
SamYaplethe only place we still use it is for ceph pools14:53
*** sdake has joined #kolla14:56
sdakedave-mccowan friday is the contributor meetup14:56
sdakedave-mccowan my hotel I think is until friday morning iirc14:56
sdakeI haven' tbooked my flgiht yet14:57
sdakeI may change my hotel to leave saturday14:57
sdakesince it looks like we can get a full day contributormeetup friday14:57
sdakeat the contributor meetup last time we sorted out how to do upgrades in a general fashion14:57
*** dwalsh has joined #kolla14:57
sdake4 hours of upgrade discussion :)14:57
*** shardy has quit IRC15:00
Jeffrey4lSamYaple, you mean , using the varilabe in module argument will be the same using variable in task name?15:00
dave-mccowani always seem to regret my travel plans.  when i leave early on Friday, i'm regret I may have missed a good session.  if i stay, i wonder why i stayed behind in a mostly empty room with (other project) folks who can't wait to get out and go touring. :-)15:01
sdakedave-mccowan usually we have a 4 hour half day contributor meetup followed by profuse drinking15:02
sdakethe half day contributor meetup will be packed with action im sure15:02
sdakeit was actuallh our best session at summit last cycle ;)15:02
Jeffrey4lthe hardest part is this https://review.openstack.org/#/c/286050/1/ansible/roles/cinder/tasks/reconfigure.yml15:03
openstackgerritHui Kang proposed openstack/kolla: Fix missing libraries for ceilometer  https://review.openstack.org/28627415:03
Jeffrey4lno all serice running on one host.15:04
Jeffrey4lconfig.yml do some wrong that, it will copy the cinder-backup configure file to the master even it is not used.15:04
Jeffrey4lSamYaple, https://github.com/openstack/kolla/blob/master/ansible/roles/cinder/tasks/config.yml15:05
Jeffrey4lreconfigure is not the same.15:06
SamYapleoh yea i forgot to go back and add that filter Jeffrey4l15:13
SamYapleyou can do a when filter on the item15:13
SamYapleso when: {{ item.in_group }}15:13
SamYaplethats for pointing that back out15:13
Jeffrey4lyea.15:13
SamYapleim suprised no one has noticed it for this long15:14
SamYaplei made a comment when i did the merge_configs thing about that and it jsut slipped my mind15:14
Jeffrey4lIn that way, there will be much of duplicated and long when: xxxx15:15
Jeffrey4lit doesn't raise any issue. So no one notice it :D15:15
SamYaplethats probably true15:15
SamYapleso for the skipped conditionals it wont raise any (unless you arent running that service i suppose)15:15
SamYaplesince its inline15:16
Jeffrey4lI still doubt, why we can not use variable like the way i used? will raise issue?15:16
SamYapleyou werent around before the merge_config stuff, but it always caused issues for people15:17
SamYapleit never worked _quite_ right15:17
SamYapleand it was also confusing to read15:17
SamYaplewith_items was far easier to read, even if it does generate some "skipped" tasks15:17
*** spisarski has joined #kolla15:18
Jeffrey4ljust one variable, not that hard to read. with_items will increate the duplicated code and the number of the lines.15:19
Jeffrey4lbut anyway, i will try the with_item, and see the feedback.15:19
*** sdake_ has joined #kolla15:20
Jeffrey4lone last question: in my implemention, the reconfigure is run one service by one service, then one node by node. it is slow and will can cause bit down time.15:21
SamYaplei would tend to agree with you Jeffrey4l, thats why the initial implementation used what you are doing all over the place15:21
SamYaplebut we changed it for a reason15:21
SamYapleJeffrey4l: is there a question in there?15:22
*** sdake has quit IRC15:23
Jeffrey4lbut in the with_item, the reconfigure will run one node by node. it is fast but will make all service(for example, all the nova related service on the controller) on one node crashed( because, all the nova related container may be removed at the same time on one node)15:24
Jeffrey4l(I do not like this.)15:24
Jeffrey4lSamYaple, ^15:24
*** haplo37 has joined #kolla15:27
*** spisarski has quit IRC15:28
*** akwasnie has quit IRC15:28
sdake_mdnadeem ping re https://review.openstack.org/#/c/286379/15:28
sdake_mdnadeem sam had a question about manilla-share, can you answer so we can either merge or you can submit a new patch?15:29
*** spisarski has joined #kolla15:30
openstackgerritJeffrey Zhang proposed openstack/kolla: Add kolla_docker action for reconfigure  https://review.openstack.org/28657015:30
SamYapleJeffrey4l: well it wont be at the same time15:31
SamYapleit still goes service by serivice15:31
Jeffrey4lSamYaple, we have two tasks now. one is remove the container, another is `include start.yml`. I do think it will remove all the container, then start all the container.15:32
Jeffrey4lI will leave keystone implementation as it, and change the glance's implementation by using with_items.15:33
*** blahRus has joined #kolla15:33
SamYaplethats only if you use COPY_ONCE15:34
Jeffrey4lSamYaple, yep.15:34
SamYaplestupid COPY_ONCE it shouldnt be used15:34
SamYapleno one likes it and it causes problems15:34
Jeffrey4llol15:34
SamYapleoperators hate it since it breaks the nor15:34
SamYaplenorm*15:34
SamYaplesdake_: ^15:34
openstackgerritPaul Bourke proposed openstack/kolla: Add new gates for oraclelinux  https://review.openstack.org/24643715:34
SamYapleso yea Jeffrey4l if you use copy once that will happen15:34
SamYaplesuggest you dont use COPY_ONCE15:35
sdake_SamYaple read all the scrollback15:35
sdake_what specifically was the question15:35
sdake_pbourke_ thx ;-)15:35
SamYaplejust pointing out COPY_ONCE is causing problems yet again15:35
sdake_well we have two options (in newton)15:36
sdake_remove config-strategy15:36
sdake_or make copy_once work properly15:36
pbourke_sdake_: thanks for the reminder about it! is there anyway to test these before adding them to infra?15:36
sdake_in fact, copy once should work properly in mitaka ;)15:36
sdake_pbourke_ you can make an experimental job15:37
sdake_then run check experimental15:37
SamYaplesdake_: it works properly, it just means more downtime15:37
sdake_once that is going well you can add it to always be in the check15:37
SamYaplebut i would vote remove it15:37
Jeffrey4lcopy_once is a little wired, do not see this kinda concept in other place.15:37
sdake_if it works properly with more downtime we can document that15:37
SamYapleJeffrey4l: agreed15:37
sdake_what is the downtime caused by, the container removal?15:37
SamYapletwo tasks15:37
SamYapleremoval then creation15:38
SamYaplethats also more IO intensive15:38
*** chandankumar has joined #kolla15:38
sdake_so that is like 1 second ? :)15:38
SamYapleno its ansible15:38
Jeffrey4l( i will submit the code )15:38
SamYapleso like 10 or more seconds15:38
sdake_ok15:38
SamYapleand it depends on your backend15:38
SamYapleand your ssh connections15:38
SamYapleits a bad default for sure15:38
sdake_well its way too late to remove it for newton, so lets shelve that conversation until summit15:38
sdake_open to changing the default prior to newton15:39
SamYapleJeffrey4l: what about that?15:39
Jeffrey4lbut SamYaple , I still want use my variable version :D. it will not cause this kinda issue.15:39
SamYapleJeffrey4l: but it will cause all the other issues15:39
sdake_rather too late to remove for mitaka15:39
SamYaplesdake_: i agree with removal15:39
SamYaplei mean too late for removal15:39
SamYapleJeffrey4l: really what we want is blocks, but thats ansible 2.015:39
*** mbound has quit IRC15:40
SamYaplehow about we do it with with_items for mitaka, and ansible 2.0 we switch to blocks, that resolves all issues15:40
sdake_the problem with removing it completely is then the containers are not immutable15:40
SamYaplei do understand your concerns about it15:40
Jeffrey4lSamYaple, for example? i do not meet any issue. it just a normal variable, like those in the globals.15:40
*** mbound has joined #kolla15:40
sdake_ok lets get out on the table what the issue with using the variabls in do_configure are?15:40
SamYapleJeffrey4l: as i said before, we encoutnered many issues doing this that didnt pop out at first15:40
SamYapleJeffrey4l: i also did what you were doing _at_ _first_, but had to change due to one issue after another15:41
SamYapleand then the ansible bugs....15:41
SamYaplethere are many edge cases here, but we moved away from this and im not keen to move back15:41
sdake_the issues we ran into with the variables were related to the docker module15:41
* Jeffrey4l go to rush the code.. two edition will be submited and compare.15:41
SamYaplesdake_: you are wrong15:41
SamYaplesdake_: i am specifically refering to the merge_config predecessor15:41
SamYapleit was a big variable include thing too15:41
sdake_i see15:42
SamYapleand it always had some issue15:42
SamYaplethats why it was replaced with merge_config and with_items15:42
sdake_i was referring to the fact that we had the inheritence thing with variables which didn't work with iirc host=pid mode15:42
Jeffrey4lSamYaple, I only know, use the variable in name with the with_items will raise issue.15:42
SamYapleJeffrey4l: no it wont15:42
SamYaplefeel free to test it15:42
SamYaplebut it works fine15:42
sdake_ok so the question here is does jeffrey's do_reocnfgiure work when someone types kolla-ansible reconfigure15:43
sdake_yes/no?15:44
*** inc0 has joined #kolla15:44
SamYapleyea it should work, until you hit those edge cases that broke the config playbook :)15:44
SamYapleyou know, the bonafide ansible bugs15:44
inc0good mornign15:45
sdake_hey inc0 hows your fine morning doing15:45
sdake_Jeffrey4l SamYaple i'd like something merged *today* so people can start c&p the work15:45
inc0started out my day by 2 political meetings, so it's a breeze15:45
sdake_if it means more downtime, i dont really care15:45
sdake_for the copy-once case15:45
sdake_inc0 welcome to your third political meeting :)15:45
inc0duh15:46
inc0I guess you have something in your mind sdake_ ?15:46
sdake_copy-once gurantees immutability, if there is some pain involved with that guaranatee, we can docuemnt it15:46
Jeffrey4lSamYaple, you are right, it works fine.. ( I really meet some similar issue)15:47
sdake_copy-alwlays does not gurantee immutability, if there is less pain with the lack of that guarantee, we can document it15:47
Jeffrey4lsdake_, I will push the code soon.15:47
sbezverkis python-magnumclient part of any magnum related containers?15:47
SamYapleJeffrey4l: im just trying to make sure we dont hit all those edge cases we just took out again15:47
inc0sdake_, copy once by no means guarantee immutabilitu15:47
SamYapleJeffrey4l: i know it seems arbitrary but the with_items we know will work, the include we know doesnt always work15:47
sdake_inc0 it gurantees immutability of the config15:48
inc0if image changes, containers gets rebuild just the same15:48
Jeffrey4lcool15:48
sdake_inc0 yes that is an upgrade15:48
inc0ok15:48
SamYaplei agree with you about it not being ideal Jeffrey4l, but i dont have another suggest at this time15:48
sdake_sbezverk i think its part of openstack-base but not certain15:48
Jeffrey4llet's make it clear about the edge cases. it will help us to make choice.15:49
Jeffrey4lSamYaple, ^15:49
sdake_Jeffrey4l i think Sam was mentioning bugs in ansible15:49
sdake_which bugs they are, is unknown15:49
sdake_arguablity merge_configs was much more complex then do_reconfigure15:50
*** chandankumar has quit IRC15:50
sdake_we shouldn't repeat past mistakes15:50
sdake_unless something in the environment has changed15:50
Jeffrey4lsdake_, i known. I don't miunderstand. I am talking the ansible bug too.15:50
sdake_(for example moving to ansible 2.0)15:50
*** shardy has joined #kolla15:51
sbezverksdake_ if it were, then I should have been able to run magnum cli commands on my host, but it is not the case..15:51
openstackgerritSam Yaple proposed openstack/kolla: Change default CONFIG_STRATEGY  https://review.openstack.org/28667115:51
SamYaplethere sdake_ https://review.openstack.org/28667115:51
sdake_we can trust SamYaple that if he says there are ansible bugs, there are ansible bugs15:51
inc0hey shardy :) since you're here15:51
inc0I have question for you15:51
sdake_sup shardzofglass15:51
inc0should we enable convergence as default in Mitaka kolla?15:51
sdake_inc0 try to make it harder plz ;)15:52
SamYapleJeffrey4l: i do not have time to run back through, but if you look through the bugs in kolla youll see 10-20 around this whole variable include stuff. one of those bugs contains links to ansible bugs, and some of them we just said "we dont know what the issue is, we are switching to with_items"15:52
Jeffrey4lSamYaple, ok. i will check it.15:52
sdake_Jeffrey4l the bottom line with ansible is 1.9.5 iss never coming15:53
sbezverksdake_ http://paste.openstack.org/show/488779/15:53
SamYaplesdake_: i was promised!15:53
sdake_so if there are ansible bugs, we need to avoid them15:53
SamYaplemultiple times!15:53
sdake_SamYaple first i've heard of it, ill ask around15:53
SamYaplelol its not ive told you about it several times15:53
sdake_sbezverk why don't you pip install python-magnumclient15:53
SamYaplethat said i am also doubtful about 1.9.5 even after th promise15:53
sdake_ansible is hiring more cats15:54
sdake_their budget is big and their burn is small15:54
sdake_so 1.9.5 could be possible - who knows15:55
sdake_but I bitch daily at them about abanodning 1.9.z series15:55
sbezverksdake_ as a workaround I will, but should it not be installed during kolla deployment?15:55
openstackgerritMauricio Lima proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968815:55
sdake_nothing during kolla deployment should instlal the clients15:57
sdake_the clients run on a different machine then the target deployment nodes15:57
sdake_let me correct15:57
sdake_a cieint may be instlaled in a container for use by the service15:57
sdake_for example nova, installs python-neutronclient15:57
sdake_and a bunch of others15:57
sdake_but these are not for end user usage15:57
sdake_they are for integration with nova15:58
*** vhosakot has joined #kolla15:58
sbezverksdake_ ok, what then in containerized deployment can be use to run nova service-list for example? Or you exepect everything should be done via horizon?!?!16:01
*** chandankumar has joined #kolla16:01
sdake_no here is how i operate16:02
sdake_i have a lpatop16:02
sdake_i install all my cleints on my laptop16:02
sdake_i have 4 machines16:02
sdake_1 of my machines is a deployment host16:02
sdake_the other 3 are deployment targets16:02
sdake_i ansible deploy from my deployment host16:02
sdake_i connect to openstack from my laptop16:02
*** Xu_Chao has quit IRC16:02
sdake_clients can go on the all-in-one machine16:02
sdake_or htey can g anywhere else16:02
SamYaplesbezverk: clients go anywhere. you can install them whereever you want16:03
sdake_all that is sepcial about the above is i have n openrc file16:03
SamYaplekolla doesnt determine where your clients run16:03
sdake_the openrc file specifies my keystone server16:03
sbezverksdake_ SamYaple, got it so clients are not part of deployment for user's usage, only for internal things..16:04
sdake_roger16:04
*** haplo37 has quit IRC16:04
sdake_for exxample, nova needs to communicate to neutron so it instals neutroncleint16:04
sdake_heat needs to communicate to everything so it installs all clients16:04
sdake_these clients are installed in the related containers16:05
sdake_but for the end user, there is no toolbox container with all of the clients16:05
sdake_good feature idea16:05
sdake_but hasn't been done yet16:05
sdake_has been suggested before16:05
sdake_Jeffrey4l are we all set then?  what is the course of action you intend to take?16:07
Jeffrey4lwhat's it?16:08
Jeffrey4lsdake_, ^16:09
sdake_Jeffrey4l what i mean is the course of action to just go with the more downtime, or what?16:09
sdake_Jeffrey4l tht isn't to say i don't like your implementation, i think the idea rocks16:10
sdake_but if ansible is busted - we can't use it16:10
*** macsz has quit IRC16:10
Jeffrey4lbase on the ansible bug, this is the only option technically.16:11
Jeffrey4lsdake_, i have no other ideat now.16:11
sdake_whcih is the only option, the more downtime?16:12
Jeffrey4lyep16:12
sdake_ok well lets make it so16:12
sdake_and deal with optimizing downtime in newton16:12
*** macsz has joined #kolla16:12
Jeffrey4lyea16:12
sdake_put a docimpact in the commit log please16:12
sdake_so someone can document the imapct ;)16:12
Jeffrey4lok.16:13
sdake_i'll document the impact if your commit message is soid enough16:13
sdake_i suspect we will be going to nasible 2.0 in newton16:14
sdake_although unknown16:14
Jeffrey4l roger that.16:14
Jeffrey4lI'd like to move to ansible 2 ASAP in newton.16:14
Jeffrey4lI should not so hard.16:14
*** haplo37 has joined #kolla16:16
sdake_Jeffrey4l https://bugs.launchpad.net/kolla/+bug/1551314 please  respodn quilcly16:18
openstacksdake_: Error: malone bug 1551314 not found16:18
sdake_SamYaple that info from clarkb is pretty sweet huh, we dont have to rebases everything16:19
sdake_that is not how i thought it worked ;)16:19
sdake_may be a recent change16:20
SamYaplesdake_: im of the opinion that needs to be tested16:20
sdake_agree16:20
sdake_i found an old patch and rechecked it, watching for the results16:20
* Jeffrey4l reading16:20
inc0pbourke_, around16:21
inc0?16:21
pbourke_inc0: hey16:21
inc0hey Paul, do you want mariadb upgrades?16:21
inc0;)16:22
inc0we have fire going and I won't be able to handle it16:22
*** daneyon has joined #kolla16:25
pbourke_not really! but if there's noone else I'll take it16:25
inc0soo...my dear kolla community, show of hands16:26
*** daneyon_ has joined #kolla16:26
inc0we need someone to take on mariadb16:26
Jeffrey4lsdake_, done16:26
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Autodetect number of instances  https://review.openstack.org/28464316:26
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Support dependencies inside one host  https://review.openstack.org/28473716:26
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: [WIP] Add heka support  https://review.openstack.org/28630116:26
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Dependency between nova-libvirt and nova-compute inside host  https://review.openstack.org/28481516:26
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Use constraints only on multinode deployment  https://review.openstack.org/28597016:26
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Allow to override resources in globals.yml  https://review.openstack.org/28483616:26
pbourke_inc0: have you looked at it much, how hairy is it16:27
inc0SamYaple, will have most of info16:27
inc0it's not super trivial, but not too hard as well16:27
inc0will require a bit more than just include start.yml16:28
inc0and logic will be similar to what I'm working on - rabbitmq16:28
pbourke_go on then16:28
pbourke_I'll have a look16:28
inc0ok, I'll let you know as soon as I push anytihn up16:29
sbezverkSamYaple after getting organized client I am trying to get magnum service-list and I get Not Authorized (admin-openrc.sh is loaded). In keystone log I see this error every time I try to execute magnum commands: "Expecting to find domain in project - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error." Do you16:30
sbezverkthink something might be missing in magnum configutation?16:30
*** daneyon has quit IRC16:30
*** chandankumar has quit IRC16:32
*** absubram has joined #kolla16:32
*** absubram_ has joined #kolla16:33
*** absubram has quit IRC16:37
*** absubram_ is now known as absubram16:37
Jeffrey4lSamYaple, sdake_ see this implementation for cinder reconfigure. https://gist.github.com/jeffrey4l/d18ff4c6b841f7d523bd16:37
Jeffrey4l1. code become more complicated   2. code can not run, with follow error ERROR: [DEPRECATED]: include + with_items is a removed deprecated feature16:38
Jeffrey4lSamYaple, sdake_ any idea?16:38
*** iceyao has joined #kolla16:38
sdake_Jeffrey4l busy can't context switch at the moment, perhaps SamYaple can help you out with the include nd with_items deprecation problem16:39
Jeffrey4lSamYaple, around?16:41
*** iceyao has quit IRC16:43
SamYapleJeffrey4l: yea include + with_items is deprecated16:46
sdake_Jeffrey4l interested in joining the kolla-coresec team (VMT)16:47
SamYaplebut you can variablize the start16:47
Jeffrey4lSamYaple, found a solution.16:47
Jeffrey4lwill push later.16:47
SamYaplepbourke_: inc0: i have mariadb16:47
SamYapleill post a WIP moment16:47
sdake_i'll be looking for volunteers for kolla-coresec, sending out mail in a bit16:47
pbourke_SamYaple: cool thanks16:48
inc0what's kolla-coresec?16:48
SamYaplesdake_: ill volunteer, that should be no suprise though16:48
sdake_sounds good sam16:48
SamYapleinc0: sdake is getting a security team together16:48
sdake_i'll add you16:48
inc0add me too plz16:48
SamYaplesbezverk: that sounds like the partial v3 implementation we have16:49
SamYaplei have a WIP patch to fix that16:49
SamYaplehorizon alo suffers16:49
Jeffrey4lI think i can. but do not know what's kolla-coresec?16:49
rhalliseysdake_, I'll join also16:50
sdake_ok so i need to limit this tema to about 4 people16:50
sdake_let me send out email to mailing list describing what the responsiblities are16:51
sdake_which i am in process of adding16:51
sdake_its just that Jeffrey4l had found a VMT bug potentially16:51
*** chandankumar has joined #kolla16:51
sdake_process of writing16:52
rhalliseyI don't need to be on the team, but plan on writing selinux policy for kolla16:52
elemoine_question about docker image documentation: would it make sense to have each Dockerfile directory include a README file documenting on the image should be used? Has this been discussed already? I am currently writing some documentation for the Heka image and I was wondering if that documentation could go to Kolla.16:52
Jeffrey4lbtw, VMT means?16:53
sbezverkSamYaple, it looks like I was using old globals.yml where new variables like kolla_internal_fqdn were not defined in globals.yml but were used in magnum/defaults/main.yml16:53
inc0elemoine_, more docs will not hurt16:53
pbourke_elemoine_: I think you should just add an entry for heka the same as the ones at the bottom of http://docs.openstack.org/developer/kolla/16:54
pbourke_elemoine_: or actually maybe an over all "logging in kolla" under the main section would be better, depends on the angle you're going for16:54
elemoine_I agree that a "logging in kolla" page would be useful16:55
vhosakotJeffrey4l: sdake_, I have started neutron reconfig work... shall I update the bp with steps to test reconfiguring services in https://blueprints.launchpad.net/kolla/+spec/kolla-reconfig ?16:55
elemoine_but this is not what I was referring to in my initial question16:55
elemoine_my initial question relates to documenting the kolla images (what they provide, their usage, what volumes they expect to run, etc.)16:56
sdake_steps to test would be great - in the whiteboard or in an etherpad linked from the blueprint16:56
sdake_etherpad would be preferrable16:56
Jeffrey4lvhosakot, please, that will be helpful.16:56
vhosakotJeffrey4l: sdake_ ok16:56
*** mikelk has quit IRC16:56
vhosakotJeffrey4l: I want you to review the steps to test, please :)16:56
Jeffrey4lvhosakot, np16:56
sdake_rhallisey please respond to that email16:57
sdake_vhosakot moment letme make you an etherpad to start with16:57
vhosakotJeffrey4l: sdake_, cool, I think all BPs should have well documented/updated steps to test that work :)16:57
elemoine_that docker image discussion is also related to making our images more visible and useful to others (who do not necessarily deploy using kolla-ansible or kolla-mesos)16:57
pbourke_elemoine_: that sounds good to me. Though I think something under the doc/ directory would be best16:58
sdake_vhosakot https://etherpad.openstack.org/p/kolla-mitaka-testing-reconfigure16:58
vhosakotsdake_: I was going to add under the "reconfigure services on a redeploy" section in the Mitaka midcycle roadmap etherpad at https://etherpad.openstack.org/p/kolla-mitaka-midcycle-roadmap16:58
vhosakotsdake_: cool, thanks!16:58
pbourke_elemoine_: just my opinion :)16:58
openstackgerritJeffrey Zhang proposed openstack/kolla: Reconfigure glance service  https://review.openstack.org/28587316:59
elemoine_pbourke_: yeah, not scattering the docs across the repo makes sense to me as well16:59
vhosakotsdake_: Jeffrey4l, so, let us add for each service like "how to test reconfiguring keystone",  "how to test reconfiguring glance",  "how to test reconfiguring neutron"  blah  blah16:59
sdake_vhosakot don't put stuff in the midcycle docs plz16:59
vhosakotsdake_: ok, sure.. won't :)16:59
*** jtriley has quit IRC16:59
sdake_there is a link at the blueprint now to use16:59
sdake_on etherpad16:59
vhosakotawesome!17:00
SamYaplesdake_: thats not a VMT bug i told you that in the review17:00
vhosakotthe deadline for implemeting reconfig is March 4th ?17:00
sdake_SamYaple are you subscribed to the bug?  VMT dicssion shoudl happen in bugs, not in gerrit17:00
SamYaplesdake_: auth is not a security hole17:01
sdake_in fact, from whati understand gerrit should not be used at all - the vmt handles merging the changes17:01
SamYaplethe bug is superfolus17:01
elemoine_pbourke_: but having a doc/images directory where only one or two images are documented is a bit ridiculous. By using README files in the Dockerfile directories we make it less official…17:01
*** mbound has quit IRC17:01
pbourke_elemoine_: it can be a work in progress17:01
sdake_vhosakot more or less17:01
elemoine_pbourke_: so this would be my preference until we have a decent number of documented images17:02
sdake_kolla has a bunch of outstanding work17:02
sdake_upgrades is #!17:02
elemoine_pbourke_: just my opinion :)17:02
sdake_diagnostics is #@17:02
pbourke_elemoine_: there can also be a doc describing overall approach17:02
pbourke_elemoine_: including the jinja mechanisms etc.17:02
sdake_reconfigure is #317:02
sdake_security is #417:03
sdake_I think :)17:03
sdake_I think we should have a design document in the main docs, not in readmes17:03
elemoine_pbourke_: true17:03
*** jtriley has joined #kolla17:03
sdake_lets not clutter up the repos with a whole slew of readmes17:03
sdake_because nobody will read them or keep them up to date17:03
vhosakotsdake_: you mean that VMT... :)  I was the one who added the spec for it the the security-doc repo :)   https://github.com/openstack/security-doc/blob/master/README.rst17:03
sdake_we can't even keep the vagrant docs up to date17:03
vhosakotsdake_: do you think kolla team-members need to join VMT ?17:04
elemoine_sdake_: would you accept doc/images/ with just heka.rst in a Change Request?17:04
sdake_vhosakot its limited to core reviewers by the tag17:05
sdake_or I'd ask dave-mccowan to join17:05
vhosakotah ok... got it :)17:05
elemoine_sdake_: if I do that I will also add a general doc file explaining the overall approach that pbourke_ mentioned17:05
sdake_I might ask dave-mccowan to execute a security audit in any regard ;-)17:05
*** bmace has quit IRC17:05
vhosakotI did some work for vulnerability testing and incorporating security notes for neutron17:06
sdake_doc/diagnostics.rst17:06
sdake_doc/design.rst17:06
vhosakotyep17:06
*** bmace has joined #kolla17:06
elemoine_so I'd create a CR that adds two files : doc/images/heka.rst and doc/images/general.rst17:06
sdake_no17:06
sdake_its not heka to document, its diagnostics to document17:06
sdake_doc/diagnostics.rst17:06
elemoine_sdake_: as I said my main goal here is to describe the kolla images17:06
elemoine_doc/diagnostics.rst makes a lot of sense, I totally agree17:07
sdake_if you want to describe the kolla images, we might as ewll get started ona kolla/design.rst17:07
elemoine_but it's not what I am referring to here17:07
sdake_or kolla/doc/implementation.rst17:07
elemoine_sdake_: I want to describe each image individually as well17:07
sdake_i htink that becomes difficult to maintain17:08
limamauricio_sdake_, SamYaple -> https://review.openstack.org/#/c/269688/17:08
pbourke_" If there are more then 4 individuals interested in joining this team, I will form the team from the most active members based upon liberty + mitaka commits, reviews, and PDE spent.17:08
pbourke_"17:08
sdake_perhaps it makes more sense to describe our implementation in terms of best practices and  go fro mthere17:08
pbourke_SamYaple you're screwed :p17:08
dave-mccowanvhosakot why did you add a security-doc repo?17:08
sdake_pbourke lol17:08
elemoine_my primary goal is to describe the heka image, which other folks are going to use outside kolla-ansible17:08
openstackgerritMerged openstack/kolla: Change default CONFIG_STRATEGY  https://review.openstack.org/28667117:08
SamYaplepbourke_: why what?17:08
sdake_SamYaple he was obviously being sarcastic ;)17:09
vhosakotdave-mccowan: I did not add the repo.. I added the spec doc describing VMT and security practices in OpenStack when I worked on testing disabling neutron port-secutiry for multicast in neutron17:09
SamYapleohh i didnt see the quote17:09
SamYaplelol17:09
elemoine_ sdake_ it's a "private" goal, but I was wondering it it could benefit kolla17:09
SamYaplewow. that was the quickest merge in history https://review.openstack.org/28667117:09
sdake_elemoine_ i think it is a slipperly slope - we dont want to document how all 115 of our containers work17:10
sdake_we want to tlak in general terms17:10
vhosakotdave-mccowan: did you have any specific Qs about the security-doc repo ?17:10
sdake_i dont want to set a precedent where we are encouraged to write those docs for every container17:10
sdake_just look at what has happened with the guide discussion on the nova review17:10
*** achanda has joined #kolla17:10
openstackgerritJeffrey Zhang proposed openstack/kolla: Add kolla_docker action for reconfigure  https://review.openstack.org/28657017:11
sdake_we have 15-20 guides to write, and there is pushback on that, i dont want "115 container docs to write"17:11
elemoine_sdake_: yeah, I fully understand this17:11
sdake_how will people use the heka container outside kolla?17:11
sdake_you mean for other purposes?17:11
elemoine_sdake_: I just find it strange/stupid to document my heka image outside kolla17:12
sdake_well if you think it matters to the design, document it in the implementation.rst file17:12
elemoine_sdake_: I mean outside kolla-ansible17:12
SamYapleelemoine_: i think it should be documented in kolla if it relates to kolla17:13
Jeffrey4lglance reconfigure by using with_items https://review.openstack.org/285873 keystone reconfigure by using variable https://review.openstack.org/286570  two edition feel free to make comments.17:13
Jeffrey4lSamYaple, sdake_ ^17:13
elemoine_SamYaple: it's documentation about an image whose Dockerfile is in Kolla17:13
elemoine_this is how it related to kolla17:13
sdake_elemoine_ I have thought about the separate guides documentation, and prefer separate guides, but we can roll them into one file17:15
sdake_why not with the images in the implementation.rst17:15
sdake_elemoine_ we are after scalability for new develoeprs here, not for getting eople to reuse our containers17:15
sdake_elemoine_ what you ask is to allow people to reuse the heka container for their own purpose, which is great17:16
sdake_but it goes against our scalability goals for ramping up new devlopers17:16
sdake_because if there are 115 READMEs to read (and for us to write) that will be constalty dated17:16
elemoine_sdake_: yes exactly, I want to document how to use that image. period17:16
sdake_we have been down this road before with kubernetes and documetning the environment variabless, and that experiment imo was a failure17:16
elemoine_sdake_: my idea was to create docker/heka/readme.txt without setting any precedent17:17
*** dims_ has joined #kolla17:17
sdake_if its inconsistent it sets precedent!17:17
sdake_documenation belongs in the docs directory17:17
Jeffrey4lSamYaple, are you going to fix the config.yml issue we talked just now?17:17
sdake_in the doc directory17:18
elemoine_sdake_: it will be inconsistent, as I am not going to document the 100+ image we have :)17:18
elemoine_sdake_: ok for the doc directory, I understand17:18
sdake_ya but someone will see that and go "yay 115 commits i can make"17:18
sdake_and then we have to deal with why we made an *exception* for heka17:18
sdake_which to date, I haven't heard a good argument for17:18
elemoine_sdake_: exactly17:18
sdake_why not just document it on your blog post or somehting17:18
*** dims has quit IRC17:19
sdake_we dont make exceptions in kolla ;-)17:19
*** salv-orl_ has joined #kolla17:19
elemoine_sdake_: no problem for me17:19
sdake_because it leads exactly to the disaster I outlined above17:19
elemoine_sdake_: but it's also a shame17:19
sdake_do it once, have to do it again17:19
sdake_and again17:19
sdake_we make compromises, this is a normal part of democratic process17:19
sdake_but exceptions are not17:20
elemoine_sdake_: have you thought about publishing the kolla images to the official docker hub?17:20
SamYapleJeffrey4l: i doubt ill have time17:20
sdake_elemoine_ yes if you check the thrads, I've been tryin without much success to get infra to host a registry server17:20
SamYapleJeffrey4l: its not breaking anything, and i wont block somoen else fixing it17:20
SamYaplegoing to lunch17:20
SamYaplebbl17:20
Jeffrey4lok17:20
elemoine_sdake_: I know, so you never considered pushing the images to the official Docker hub, right?17:21
*** athomas has quit IRC17:21
sdake_elemoine_ we have considered it17:21
elemoine_sdake_: I was asking because the standard is to have docs for the images you push17:21
sdake_the problem we have atm is we can't get credentials in the vm securely17:21
sdake_we dont hvae to follow that "standard" ;-)17:22
*** salv-orlando has quit IRC17:22
elemoine_sdake_: I would find it strange to publish images without instructions on how to use those images17:22
sdake_we have instructions right on docs.openstack.org17:22
elemoine_no17:22
sdake_teh containers are to be used as a whole17:22
elemoine_yes17:22
sdake_greater then sum of parts ;)17:22
elemoine_not what docker hub users expect17:23
sdake_well we dont publis hto docker hub atm, so its a moot discussion at this point17:23
sdake_but even if we did, i think one link to our upstream docs would do the trick17:23
sdake_the only readme in the repo I want personally is in the TLD17:24
sdake_other then that,I'd prefer no readmes, and all doc/*rst files17:24
elemoine_I disagree, because that link would point to our Ansible/how to deploy kolla documentation, not to the image's documentation17:24
elemoine_not what people expect17:24
sdake_elemoine_ i am just one person17:24
sdake_start a mailing list thread plz17:24
sdake_get the community to weigh in17:24
sdake_i dont speak for the community i speak form yself in this case17:25
elemoine_ok let's close the discussion for now, thanks a lot17:25
sdake_the only time I represent the community is when I'm on stage or in an interview17:25
sdake_and I try not to touch on topics where there is not wide agreement17:25
sdake_try/dont17:25
elemoine_I may write to the mailing list about that, and see if people are interested in that topic17:25
*** athomas has joined #kolla17:26
sdake_we should probably have a midcycle session on pushing to the docker hub or a registry hostd by openstck.org17:26
sdake_rahter not midcycle but austin ODS summit17:26
elemoine_sure17:26
sdake_we have a meeting wednesday at 23:00 UTC17:27
elemoine_again if we push kolla images to docker hub users will rightly expect documentation for theses images (and not a link to the kolla deploy documentation)17:27
elemoine_pushing to a registry hosted by openstack.org is another story17:28
limamauricio_Jeffrey4l, can you review it again https://review.openstack.org/#/c/269688/17:28
Jeffrey4llimamauricio_, sorry, i really need to go need. it is 1:30 AM ;D. I will review it tomorrow.17:30
Jeffrey4lgo bed*17:30
limamauricio_ok17:30
*** limamauricio_ is now known as mlima17:31
*** fthiagogv_ has quit IRC17:31
*** ftgomvier has joined #kolla17:32
*** ftgomvier is now known as fthiagogv17:34
sdake_elemoine_ because we are near the end of mitaka-3, we can't take up this topic during the meeting, but we will be adding austin summit discussions there17:34
sdake_we can't take up the topic because I think we will be short on time just taking care of normal business17:34
*** Serlex has left #kolla17:36
openstackgerritJeffrey Zhang proposed openstack/kolla: Reconfigure glance service  https://review.openstack.org/28587317:37
*** Jeffrey4l has quit IRC17:43
*** prithiv has quit IRC17:44
*** absubram has quit IRC17:48
*** sdake_ has quit IRC17:51
*** fgimenez has quit IRC17:57
*** kproskurin has joined #kolla18:01
*** kproskurin has quit IRC18:02
*** dwalsh has quit IRC18:09
*** jmccarthy1 has joined #kolla18:09
openstackgerritMerged openstack/kolla: Fix missing libraries for ceilometer  https://review.openstack.org/28627418:10
*** macsz has quit IRC18:14
*** rmart04 has quit IRC18:15
vhosakotI've added the steps to test reconfigure bp  in  https://etherpad.openstack.org/p/kolla-mitaka-testing-reconfigure   Could folks review it when there is a chance.  Thanks!18:17
*** openstackgerrit has quit IRC18:18
vhosakotI have added an example how to reconfigure neutron-server and a generalized example for any service that needs to be reonfigured18:18
*** openstackgerrit has joined #kolla18:18
vhosakotThe directory  /etc/kolla/config  does not exist on the host.  Is this expected ?  I just see /etc/kolla/  and not  /etc/kolla/config/18:18
mlimasdake, gate-kolla-dsvm-build-centos-binary -> http://pastebin.com/UR49gPXy18:18
*** dwalsh has joined #kolla18:19
*** JoseMello has joined #kolla18:23
*** akwasnie has joined #kolla18:26
*** serverascode has quit IRC18:26
*** serverascode has joined #kolla18:28
*** d_code has joined #kolla18:31
d_codeif I want to expand compute resources in my OpenStack deployment using Kolla…do I just add it to the [compute] group and run kolla-deploy?18:31
*** chandankumar has quit IRC18:32
d_codeand can I scale out a compute node by the same measure?18:34
d_codei.e. reduce my compute resources18:34
*** dLobatog has joined #kolla18:35
*** dLobatog has left #kolla18:35
SamYapled_code: ye18:39
SamYapleyes*18:39
d_codesweet. thanks!18:39
*** d_code has quit IRC18:41
*** d_code has joined #kolla18:41
*** dims has joined #kolla18:45
*** haplo37 has quit IRC18:46
*** jmccarthy1 has quit IRC18:52
*** dims_ has quit IRC18:52
*** jmccarthy1 has joined #kolla18:52
*** alger has quit IRC18:54
*** openstack has joined #kolla19:14
*** inc0 has quit IRC19:15
*** openstackstatus has joined #kolla19:16
*** ChanServ sets mode: +v openstackstatus19:16
*** inc0 has joined #kolla19:18
*** openstackgerrit has joined #kolla19:19
ccesarioSamYaple, is there any estimated date for kolla documentation!?  Scenarios, best practices, HA ....19:19
inc0ccesario, probably we'll do some after M319:20
inc0but is there any specific thing you want to ask about?19:20
inc0in quickstart guide we basically described what in our opinion is best deployment19:21
ccesarioinc0, yes I know about quickstart ....yes yes... I already did some tests using all in one deployment...... now I 'm looking for by advanced docs, as HA by example.... and the best way to usage the hardware and do not spent resources as physical deployments.... if you understand me...19:25
*** harmw has quit IRC19:25
inc0so, kolla will deploy HA by default19:25
inc0what you want to do is to specify multiple controllers19:26
inc0best - odd number, but that's described in openstack ha guide itself19:26
ccesarioyes, in theory I know.... therefore I 'm asking about documents, like how to desgin a good scenario using kolla/containers ... and do not waste resources :)19:29
inc0ccesario, well...as I said, use multiple controllers and kolla will solve the rest19:29
inc0basically deploying ha in kolla is just deploying multinode with more than 1 controller19:30
inc0it's all default19:30
*** harmw has joined #kolla19:31
ccesarioyes yes19:31
*** elmiko has joined #kolla19:32
elmikohi, i'm curious if there is a recommended host distro to install kolla on? (i've been trying fedora21-23 and i keep getting errors)19:33
openstackgerritThiago Gomes proposed openstack/kolla: Cleanup-images with images with duplicate id  https://review.openstack.org/28679119:34
inc0elmiko, so generally don't mix distros19:34
inc0centos on fedora should work19:34
inc0but ubuntu on fedora/centos had all sorts of issues19:34
inc0selinux and systemd usually19:34
elmikook, so if i run f23 as the host i should be ok for centos images?19:35
elmikoi had it go through the kolla-build, but then it kept failing to make the keystone image (it was missing a file i didn't recognize)19:35
inc0well....logs plz19:36
elmikoyea, i'm gonna run it again and see what happens. this was all over the weekend, and i know i should have kept the logs... but, well, weekend ;)19:37
elmikoinc0: thanks for the advice, i'll come back with some logs =D19:37
openstackgerritAndrey Pavlov proposed openstack/kolla-mesos: Initial commit for python library and CLI  https://review.openstack.org/28679919:42
openstackgerritBlake Smith proposed openstack/kolla: Fixed tool file path in image-building.rst Updated tools/build.py to tools/kolla-build.py Signed-off by: Blake Smith <blaksmit@cisco.com>  https://review.openstack.org/28680019:43
*** vhosakot has quit IRC19:46
*** vhosakot has joined #kolla19:46
openstackgerritBlake Smith proposed openstack/kolla: Fixed tool file path in image-building.rst  https://review.openstack.org/28680019:49
*** akwasnie has quit IRC19:51
inc0SamYaple, around?19:54
SamYapleinc0: momentarily19:54
inc0so, my setup looks like that19:54
inc0I have 2 nets, one for mgmt and other one for openstack stuff19:55
*** akwasnie has joined #kolla19:55
inc0hostname of host bounds myhostname to mgmt19:55
inc0and my rabbit bounds to openstack stuff19:55
SamYaplei started working on this for ceph19:55
inc0which renders clusterer broken19:55
SamYaplei know its broken19:56
SamYaplelook at ceph storage_hostname thing19:56
dave-mccowansdake samyaple  any thoughts on this bug i opened related to two VIP support? https://bugs.launchpad.net/kolla/+bug/155045519:56
openstackLaunchpad bug 1550455 in kolla "Keepalive configuration can cause black hole with two VIPs" [Undecided,New] - Assigned to Dave McCowan (dave-mccowan)19:56
inc0maybe we should have hostnames inside dockers?19:56
SamYapleinc0: thats not why its broken19:56
SamYapleit has nothing to do with docker19:56
SamYapleit has to do with your hostname resolution19:56
inc0I know19:56
inc0but inside docker we can have our own /etc/hosts19:56
SamYapleit copies the host /etc/hosts19:56
inc0and it's not working19:57
inc0we can try to generate hostnames, but that will be hacky19:57
SamYapleits not working because we havent implemneted it for rabbit19:57
SamYaplecheck ceph out its implemented tehre19:57
SamYapledave-mccowan: thats not possible since they both use the same check script19:57
inc0SamYaple, so storage_hostname should be defined per node>19:58
inc0in inventory19:58
inc0?19:58
dave-mccowansamyaple  ok.  i'll setup a test it to prove to myself one way or the other.19:59
SamYapleinc0: no its looked up on the host itself19:59
SamYapledave-mccowan: if the same script fails for one vip but not the other we have a bigger problem _however_ it would still flip to a new host19:59
vhosakotCan somebody confirm is enable_haproxy is removed and not needed anymore in globals.yml19:59
SamYaplevhosakot: the default is haproxy is on20:00
SamYapleso you dont have t oenable it20:00
SamYapleif you want to explicitly _disable_ it you must20:00
inc0ok I see it20:00
inc0hmm20:00
vhosakotbut, the field enable_haprosy is missing in globals.yml20:00
inc0ok I'll implement it for rabbit20:00
SamYapleinc0: no it doesnt work20:00
SamYapleinc0: i already tried it20:00
SamYapleerlang does its own hostname fetching20:00
inc0damn20:00
SamYapleyou have to do other hacky stuff20:00
SamYaplei havent worked it all out yet20:01
vhosakotSamYaple: shall I add the enable_haproxy field back into globals,.yml ?20:01
SamYaplefor now, the only abstraction that works is storage and tunnel i think20:01
vhosakotand submit for review ?20:01
SamYaplevhosakot: no it was never there20:01
SamYaplevhosakot: it doesnt belong there20:01
SamYapleyou can set it in your globals.yml to false if you want20:01
SamYaplebut it defaults to true20:01
vhosakotah, ok.. I thgout it was always there and commented out, per the wording in quickstart  http://docs.openstack.org/developer/kolla/quickstart.html20:02
inc0SamYaple, and let me guess, clusterer doesn't work with IPs right?20:02
SamYapleinc0: it *might* but its pretty late in the game to be changing that around20:03
*** alger has quit IRC20:04
*** sdake has quit IRC20:05
inc0yeah, just thinking of options20:06
inc0I'll just make hostnames20:06
*** akwasnie has quit IRC20:11
*** akwasnie has joined #kolla20:12
*** ssurana has joined #kolla20:16
*** sdake has joined #kolla20:16
*** alger has joined #kolla20:17
*** jmccarthy1 has quit IRC20:17
*** jasonsb has quit IRC20:18
*** The_Ball has joined #kolla20:24
openstackgerritSam Yaple proposed openstack/kolla: Bump to latest stable ansible and deps  https://review.openstack.org/28682020:24
openstackgerritThiago Gomes proposed openstack/kolla: Deleting only images from kolla  https://review.openstack.org/28682320:31
*** sdake has quit IRC20:31
*** akwasnie has quit IRC20:36
*** sdake has joined #kolla20:43
vhosakotSamYaple: can you comment on the script to automate kolla when you have a chance20:49
*** sdake has quit IRC20:56
*** sdake has joined #kolla20:59
*** esimone has joined #kolla21:02
The_BallIs it easy to deploy just cinder and required services (keystone, mariadb) with kolla?21:03
SamYaplevhosakot: i think the review you are talking about was blocked with -221:04
SamYapleThe_Ball: yea its fairly simple. you need to look at ansible/group_vars/all.yml and disable all the services you dont want by setting "enable_<service>: 'no'" in your globals.yml before deploy21:05
vhosakotSamYaple: I have not even submitted for review... I needed to know if the script I am _planning_ to submit to automate steps in quickstart to install, build, and deploy kolla from scratch has not duplicated script in kolla :)21:05
vhosakotSamYaple: I see many shell scripts for gate and vagrant (like tools/deploy_aio.sh,  toos/setup_gate.sh  and  dev/vagrant/ubuntu-bootstrap.sh),  but none of them install, build and deploy kolla from scratch...21:05
The_BallSamYaple, ah, that does sound simple :) I'll give it a try21:05
SamYaplevhosakot: there was one like this already that got blocked21:05
vhosakotah, why ?21:06
SamYaplelet me see if i can find it21:06
vhosakotthe script I have written will install kolla in just one command from scratch on a new server21:06
vhosakotcool, thanks!21:06
sdakevhosakot there is already a review up for this21:09
sdakevhosakot last i saw the -2 was removed with the idea of making it ansible down the road21:09
sdakewith possibly a kolla-host repo or something similar to be discussed at ODS21:09
*** akwasnie has joined #kolla21:11
vhosakotah ok.. cool...21:11
sdakea script in  the repo that does the setup job isn't all that onerous21:16
sdakei dont really want to automate the building step though21:16
sdakei want people to understnad how that works21:16
sdakeotherwise it looks like a bunch of black magic "CONTAINERS"21:17
vhosakotyes, agreed.. running each command by hand, we learn a lot.. true21:17
vhosakotyep21:17
vhosakot:)21:17
sdakeyu dont learn alot by turnning off seinux or that kind of stuff21:17
sdakeor turning off libvirt21:17
sdakeor configuring docker properly21:17
sdakeetc21:17
sdakethese are all steps that get in the way of an evaluation21:17
vhosakotright21:17
sdakeand we need to automate those, shell works for now but not down the road21:18
vhosakotso, are you saying a script is needed to _setup_ the env until kolla-build ?21:18
sdakethe purpose of that script in my mind is to get peopel to build.py faster21:18
sdakeya and there is a patch in the repo for centos for jut that21:18
sdakeits not intended forproduction21:18
sdakeits intended for evaluation21:18
vhosakotfor centOS, shall I submit for Ubuntu... wanted to make sure I don't submit something the community does not want :)21:19
sdakei like the idea21:19
sdakenot sure where others stnd on it21:19
vhosakotyep, all for eval and dev21:19
sdakeinc0 wants it as ansible21:19
openstackgerritSam Yaple proposed openstack/kolla: Bump to latest stable ansible and deps  https://review.openstack.org/28682021:19
sdakebut i thnk he will accept a scriptfrist approach21:19
SamYaplethere you go sdake ^^ ansible bump21:19
SamYapleno git cloning21:19
*** macsz has quit IRC21:20
sdakeSamYaple what is the privs:USAGE thing21:22
sdakenever seen that before21:22
sdakeya that git clone of a unstable beta no bueno :)21:23
SamYaplesdake: thats the mysql "no privleges" option21:26
sdakeSamYaple even though i already added you to the coresec team can you respond on thread and say "count me in"or something else that you like21:26
SamYaplebasically it just lets haproxy sign into mysql and do nothing else21:26
sdakesoundsgood21:26
SamYaple(its what weve been doing, this is just explictly granting priv because module changed)21:27
*** dims_ has joined #kolla21:31
*** dims has quit IRC21:33
SamYapleso sdake...21:39
SamYaplethe shade domain module only exists in latest ansible-dev21:39
sdakei have a patch that doesn't use shade in progress21:39
SamYapleright. but we want to use shade21:40
sdakesomewhre on one of these damn vms on my laptop ;)21:40
SamYapleits not _can_ we do it without shade, its we dont want to21:40
sdakewell if you get ansible-dev in there, that wfm, as long as its pinned to a specific tag21:40
SamYapleit can be pinned to a commit21:40
sdakei its not pinned to a specific tag, we can always rework it down the road21:40
sdakepin to commit works too21:40
SamYapleok. let me do that quick like then21:41
sdakeas long as its reproducible21:41
SamYaplewe can pin to tag before mitaka most likely21:41
SamYaplebut even if we cant, if it works it works21:41
SamYapleso thats fine21:41
*** akwasnie has quit IRC21:49
elmikoinc0: still around?21:51
elmikohey all, i am following the quickstart guide, Hhttp://docs.openstack.org/developer/kolla/quickstart.html21:53
elmikoi have a fedora 23 host setup and have followed those instruction for a all-in-one install21:53
elmikobut, i get this right out of the gate when i run kolla-build Hhttp://paste.openstack.org/show/488856/21:53
elmikoany ideas?21:53
*** rhallisey has quit IRC21:55
openstackgerritSam Yaple proposed openstack/kolla: Bump to latest ansible and deps  https://review.openstack.org/28682021:57
SamYaplealright sdake that pins to a commit the best way we can (unfortantely that removes teh depth option)21:57
SamYaplewe can remove this once 2.1 lands21:57
SamYapleand with that we have all the shade modules we need to switch entirely over to shade21:58
SamYaplem/win 4821:58
*** rhallisey has joined #kolla21:59
sdakerhallisey re you wanting to joi nthe security team21:59
sdakerhallisey did you read he VMT document in the governance repository?21:59
rhalliseyya I did21:59
sdakebasically the team attaches patches to bugs21:59
sdakeand then I think the security VMT team in openstack merges them in one go once the OSSA is ready22:00
sdakebut i'm not really sure22:00
sdakeits not about securitzing kolla, its about fixing security bugs we fuond and publishign them in a controlled coordinated fashion22:00
sdakewe/community/anyone22:01
sdakeI think it will take us a couple months to get up to speed22:01
rhalliseyright.  I figured I'd add that because it was my goal22:01
sdakei think the next step is a security audit of the code base by a third party22:02
sdakered hat has a great security audit team - would be nice if we could get them to audit the codebase22:02
rhalliseyI figured I'd volunteer either way22:02
sdakeonly 25k lines of code22:02
elmikomight be worth looking at some of the work that the OSSP is doing with regards to threat analysis too22:02
sdakeshould be pretty straightforward to tak them into it :)22:02
elmiko(sorry to bud in)22:02
*** dims_ has quit IRC22:02
sdakeelmiko welcome aboard :)22:02
elmiko=)22:02
elmikoi'm still climbing on, kolla-build is fighting me22:03
sdakeelmiko where areyou stuck22:03
sdakei think we need some docs that indicate that you should have separate build and push steps and both require the --registry option22:03
sdakei think that trips people up22:03
elmikowell, i'm on round 3 of doing a clean quickstart install. but now kolla-build fails with http://paste.openstack.org/show/488856/22:04
sdakeelmiko fedora may not be all that functioanl unfortunately22:04
elmikoahh, ok22:04
sdakei'd go with centos or ubuntu or oracle linux at this time22:05
sdakedebian/fedora coming down the road i would hope22:05
elmikook, i'll give this a try with centos. is centos7 a good candidate?22:05
elmikocool22:05
sdakethe big prbolem with fedora is the yum to dnf change22:05
sdakeyup centos722:05
sdakebuild.py --base centos -t source --registry reginfo22:05
sdakeor if you want binary jsut22:06
sdakebuild..py --base centos --registry reginfo22:06
elmikois fed23 ok for the host though?22:06
sdakethe nbuild.py --registry reginfo --push22:06
sdakeelmiko at one point fedora22 as a host was incompatible because the kernel mdoulse were compressed and something couldn't read them in the centos container22:06
sdakethis was on centos 7.022:06
elmikointeresting22:07
elmikoso, centos for host is recommended?22:07
sdakei run centos on host22:07
elmikocool, i'll give that a try22:07
sdakeit would be cool to try fedora23 as a host22:07
sdakeso we can update the instructions22:07
sdakeits possible centos has updated their builds of guestfs or whatever was reading the modules to work prpoerly22:07
sdakei dont recall the exact issue22:07
elmikoi almost had it working this weekend, but the keystone container kept failing to build22:07
sdakeya keystone is fixed now22:08
elmikoany idea what the image dir error is about?22:08
sdaketry centos on fedora 23 - should work if centos is updated for the one binary22:08
sdakeno clue, but i'd recommend the following22:08
sdakepip uninstall kolla22:08
sdakego to the kolla directory22:08
sdakesudo pip unisntall kolla i mean22:08
sdakeand run tools/build.py directly22:08
sdakeI think the pip installing kolla causes people all sorts of confusion22:09
sdakeespecially since it looks like you have run into a bug of some kind22:09
elmikook, gonna try the build.py directly22:09
sdakemake sure to uninstall kolla first22:09
sdakebecause the buid tools are made to look in /usr/share/kolla/docker first then the local cwd second22:10
elmikogot it22:10
sdakesame with kolla-ansible22:10
*** dims has joined #kolla22:10
sdake(iirc, this stuff changes all the time, have hard time keeping up ;)22:10
elmikohehe, it has that feeling to it ;)22:10
elmikogotta love the cutting edge!22:10
elmikook, well it's building now =)22:12
elmikosdake++22:12
sdake1000 commits since liberty22:12
sdakeonly 25k lines of code22:12
elmikowhoa22:12
sdakeincluding documentation22:12
sdakeand specs22:12
sdakewhich alone are 5k of the codebase22:12
sdakeyou can run ./loc to see for yourself22:12
elmikoi applaud the team's effort to keep it tidy ;)22:13
sdakeya we are moving past gold plating into solid gold ;)22:14
elmikohaha22:14
*** shardy has quit IRC22:15
sdakeSamYaple re https://blueprints.launchpad.net/kolla/+spec/mariadb-lights-out22:20
sdakewhat is your thinking on this?22:20
sdakeI was thinking a "recovery" action in the playbooks which does whatever recovery is needed22:20
sdakefor mariadb this could recover by running the upgrade playbook22:21
sdakeneutron needs recovery of some sort as well22:21
sdakeafter a reboot22:21
sdakeelemoine ping22:23
sdakere https://blueprints.launchpad.net/kolla/+spec/heka22:23
sdakeshouldn't that be in needs review since you have finished the last patch needed?22:23
*** achanda has quit IRC22:23
vhosakotneutron coming out of lights out, I have seen that none of the agents come up until neutorn-server is up... neutron-server is up, virtual bridge agent is up next (neutron-linux-bridge agent or OVS agent), then, l3-agent and dhcp-agent... this order worked for me, although the order is not well documented anywhere about neutron recovering after lights out22:25
sdakeasalkeld what is status of https://blueprints.launchpad.net/kolla/+spec/zookeeper - good progress or compelte or what?22:26
sdakevhosakot we may have to put recovery in a rc or punt it entirely22:26
sdakevhosakot but reconfigure is ready to go - recommend focusing any development there ;)22:27
vhosakotyep, I'm rebuilding with latest code...22:27
*** jtriley has quit IRC22:27
sdakerhallisey is this implemented: https://blueprints.launchpad.net/kolla/+spec/nfs-support-in-cinder22:27
vhosakotsdake:   https://etherpad.openstack.org/p/kolla-mitaka-testing-reconfigure22:28
sdakevhosakot rockin :)22:29
vhosakotcool :)22:29
vhosakotJeffrey will review it tomorrow22:29
sdakecan you do more services?22:29
sdakeyou mentioned you would do nova as well iirc22:30
vhosakotyep, neutron, nova and horizon22:33
vhosakotsdake: we need all those services in bp implemented with reconfig before march 4th ?22:35
vhosakotis marth 4th the right date (deadline) ?22:36
vhosakotmarch*22:36
*** achanda has joined #kolla22:36
*** JoseMello has quit IRC22:38
*** inc0 has quit IRC22:40
rhalliseysdake, yes22:42
rhalliseyjust changed it22:42
rhalliseybrb22:43
*** rhallisey has quit IRC22:43
sbezverksdake I still get Not authorized, when I run any magnum commands. Something is not right in keystone as it generates these messages for every attempt: http://paste.openstack.org/show/488862/22:43
sbezverksdake anybody managed to get magnum working with kolla deployment?22:44
sdakesbezverk uncler if magnum is working at this time22:44
sdaketry a different service plz22:45
sdakeif magnum is busted which is likely file a bug22:45
sdakethere are some keystone changes which i didn't see make their way into any of the non-compute-kit containers like murano and heat etc22:45
sbezverksdake other services including horizon seems to be working fine.. I will file a bug then..22:47
SamYaplesdake: neutron is fine after reboot22:47
SamYaplesdake: for mariadb thats a _full_ lights out which cannot be automatically recovered22:47
SamYapleaio is fine for lights out right now22:47
*** dwalsh has quit IRC22:47
SamYaplethe best I can give is a helper playbook and some docs22:48
SamYaplesbezverk: dont file a bug22:49
SamYapleits a known issue from the keystone stuff22:49
SamYaplesbezverk: _when_ the keystone patch upstream merges your issue will be fixed, but also it should be fixed after https://review.openstack.org/#/c/286637/22:49
*** vhosakot has quit IRC22:51
sdakeSamYaple re neutron, I got impression from vhosakot that neutron needs its services restarted in a specific horder22:51
sdakehorder/order22:51
SamYaplesdake: for ubuntu 14.04 you have to reapply the /run shared fix22:51
SamYaplemy suggestion would be an init script upgrade, but thats just what i do to solve the issue22:51
sdakeSamYaple is he running ubuntu 14.04?22:52
SamYaplei believe so22:52
sdaketoo bad he just dropped off22:52
sdakeok so the answer is we dont at this time need a recover action I think from what you said22:52
sdakebut we need some documentation and a special lights out playbook22:52
SamYaplenot for kolla-ansible no22:52
SamYaplesome specific playbook for mariadb to assist in lights out, yes22:53
SamYaplebut its mostly going to be docs and the operator22:53
sdakeok i'll add that to he blueprint22:53
SamYaplebasically with like a datacenter outage what will happen is the operator will need to essentially pick a random mariadb server to serve as new master22:53
SamYaplewe have a playbook that _might_ help there, but there is no gaurantee with a power outage it will have the needed info22:54
sbezverksdake I have filed a new bug: 155199222:54
openstackbug 1551992 in kolla "After successful deployment any magnum commands return ERROR: Not Authorized" [Undecided,New] https://launchpad.net/bugs/155199222:54
sdakesbezverk i think sam said don't file a bug22:54
sdakebut ok ;)22:54
sdakei doubt magnum works out of the box as is anyway22:55
SamYapleits ok sbezverk its just not a kolla bug22:55
sdakeit probably needs a rescrub22:55
sdakeit worked in kilo, notsure about liberty tbh22:55
SamYapleoh. wait no thats magnum22:55
sdakei think it worked in liberty22:55
SamYaplethats using keystone v222:55
SamYaplemagnum doesnt support v3 yet22:55
sdakemagnum hasn't got v3 implemented yet?22:55
*** dims has quit IRC22:55
SamYaplenope22:56
SamYaplehttps://review.openstack.org/#/c/274239/22:56
sdakegroan22:57
sdakeit was almost a year ago that work was slatd to be done22:57
SamYapleyup22:57
SamYaplei found this funny https://blueprints.launchpad.net/magnum/+spec/magnum-keystone-v322:57
SamYapleread the comments22:57
sdakeSamYaple join #openstack-containers22:58
sbezverkSamYaple, sorry I missed your comment about bug :-(22:59
SamYapleno problem sbezverk22:59
SamYapleits not a big deal22:59
sbezverkSamYaple, in theory if I change OS variable to V2 it should fix magnum issue then?23:00
sdakesomething needs to be done about magnum, we will just repurpose that bug for doing so23:00
SamYapleno we arent setting up v2 keystone at all23:00
SamYapleso its likely not to work23:00
*** dims has joined #kolla23:00
asalkeldsdake: yip it's done (the zk bp)23:02
sdakeasalkeld can you mark it as so23:02
asalkelddone23:02
sdakehttps://bugs.launchpad.net/kolla/+bug/155199223:03
openstackLaunchpad bug 1551992 in kolla "Make Magnum use Keystone v3" [Undecided,New]23:03
sdakethere, bug repurposed23:03
SamYaplethats still wrong but ok23:03
sdakeSamYaple you said your working on that one?23:03
SamYaplewe arent setting up v3 properly at _all_23:03
SamYapleits only partially working23:04
sdakeyou mean with magnum23:04
SamYapleno i mean period23:04
sdakeor in general23:04
sdakegot it23:04
elmikosdake: quick question, is kolla using, or planning to use, kubernetes?23:04
sdakeelmiko some folks have tlked about it23:04
sdakei think for that to happen - it would take a team of 3-4 cats working full time on it uninterrupted23:04
sdakeasa was done with kolla-mesos23:04
elmikocurrently it is just docker+ansible though?23:05
sdakewhen asalkeld proposed it, he said they would be brining 6 developers to the party to implement it23:05
elmikooh, kolla-mesos, that sounds interesting... ;)23:05
sdakeelmiko we also have a work in progress kolla-mesos implementation23:05
elmikoneat!23:05
sdakei'd like to see that working well before kubernetes is tackled23:05
elmikomakes sense23:05
sdakebut if it was done in parallel that would wfm ;)23:05
sdakeI have alot of kubernetes experience23:06
sdakeand think the job is impossible23:06
openstackgerritMauricio Lima proposed openstack/kolla: [WIP] Make Heka collect Manila logs  https://review.openstack.org/28687623:06
sdakebut things have changed23:06
sdakewhich may make it possible23:06
elmikoi'll take your word for it ;)23:06
sdakeand asalkeld has thought up ideas i didn't during our initial go of making kolla worko n kubernetes23:06
sdake(when the project started, it was kolla on kubernetes on fedora atomic ;)23:06
* elmiko nods23:06
sdaketalk about a whisky tango charlie foxtrot23:06
elmikohaha23:06
elmikoi know atomic has been making a lot of progress, but i haven't used it outside of openshift for some time now23:07
sdaketheir upstream seemed pretty non-engaged23:07
sdakewhen i worked on magnum quite a bit23:07
sdakedon't know if that has changed or not23:07
elmikothat's sad =(23:07
*** intr1nsic has quit IRC23:08
sdakethis is why coreos is clobbering atomic23:08
elmikointeresting...23:08
sdake(IMNSHO:)23:08
SamYaplepbourke_: yo23:08
elmikototally fair, i'm honestly just curious about this stuff. i am doing an internal tech talk about containers in openstack, and i've found kolla to be a very exciting project23:08
elmikomagnum too23:09
elmikoalthough, i would love to switch from using devstack to using kolla. and, i'd really like to get see if we can get a sahara playbook submitted to the project.23:10
sdakeelmiko we will absolutely take any big tent project playbooks + containers23:10
elmiko\o/23:11
elmikoi need to talk with our team, but i'm gonna bring it up at summit23:11
sdakeelmiko which place is your gig located23:11
sbezverkvhosakot quick question, if I need to reconfigure neutron's ml2 I just create ml2_conf.ini with new configuration and follow the same steps reconfiguring netron-server container?23:12
elmikosdake: not sure i follow, my day job?23:12
sdakeya where do you work23:12
elmikored hat =)23:12
sdakecool23:12
sdakewe have alot of red hat core reviewers23:12
elmikonice, i should be bugging them!23:13
elmiko;)23:13
sdakei think kolla is generally well known internally at RHT, but another tech talk wouldn't hurt :)23:13
elmikoit's new for our group (emergin tech)23:13
*** haplo37 has quit IRC23:14
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Extend kolla-mesos-config to be able to set zookeeper variables  https://review.openstack.org/28640023:18
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Move generate_configs into the Command class  https://review.openstack.org/28639923:18
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Restart daemons if their config changes  https://review.openstack.org/28466423:18
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Make write_file return if the contents changed  https://review.openstack.org/28639823:18
*** salv-orl_ has joined #kolla23:19
*** Jeffrey4l has joined #kolla23:21
*** salv-orlando has quit IRC23:22
*** blahRus has quit IRC23:26
*** Jeffrey4l has quit IRC23:31
*** intr1nsic has joined #kolla23:32
*** spisarski has quit IRC23:43
*** sdake has quit IRC23:47
*** salv-orlando has joined #kolla23:50
*** salv-orlando has quit IRC23:50
*** salv-orl_ has quit IRC23:50
*** salv-orlando has joined #kolla23:50
*** unicell has joined #kolla23:55

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