16:00:21 #startmeeting oslo 16:00:22 Meeting started Mon Nov 9 16:00:21 2015 UTC and is due to finish in 60 minutes. The chair is dims. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:26 The meeting name has been set to 'oslo' 16:00:30 courtesy ping for GheRivero, amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dougwig, e0ne, flaper87, garyk, harlowja, haypo, 16:00:30 courtesy ping for ihrachyshka, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lifeless, lintan, ozamiatin, redrobot, rpodolyaka, spamaps 16:00:31 o/ 16:00:31 courtesy ping for sergmelikyan, sreshetnyak, sileht, sreshetnyak, stevemar, therve, thinrichs, toabctl, viktors, zhiyan, zzzeek 16:00:31 ./ 16:00:35 o/ 16:00:39 hola 16:00:44 hello all 16:00:47 hi 16:00:49 o/ 16:00:53 hi 16:01:09 howdy -- already practicing for austin 16:01:25 Wow, over achiever 16:01:35 howdy y'all - you mean? :) 16:01:45 I was going to go with pardner 16:01:46 #topic Red flags for/from liaisons 16:02:03 Nothing in my camp to mention 16:02:04 none for keystone 16:02:09 thanks johnsom and bknudson 16:02:10 nothing from trove 16:02:13 none for neutron 16:02:19 thanks amrith and ihrachys 16:02:27 o/ 16:02:42 #topic Releases for Mitaka 16:02:43 #link https://review.openstack.org/#/c/242793/ 16:03:05 messaging, reports and service on deck for today... 16:03:19 please let me know if we need to cut anything else 16:03:54 last week, we added the stable compat jobs so these releases should not break liberty 16:04:05 cross my fingers 16:04:37 so stable uses mitaka releases? 16:04:42 my travis ci for testing unit tests of different projects against oslo.* master seems happy too https://travis-ci.org/dims/ 16:04:52 (if so shouldn't call the topic "Releases for Mitaka") 16:04:56 bknudson y, no caps in the g-r for stable/liberty 16:05:18 bknudson good poinr 16:05:43 k moving on 16:05:46 #topic openstack spec reviews 16:05:46 #link https://review.openstack.org/#/c/243114/ (Pluggable CMDB for oslo.config) 16:06:14 i remember we talked about similar stuff in vancouver, bnemec remember? 16:07:00 o/ 16:07:06 Sorry, got pulled into another meeting. 16:07:11 Yeah, I thought harlowja_ had a spec open for that already. 16:07:18 no worries jungleboyj 16:07:31 bnemec hmm, will hunt for that 16:08:35 harlowja_ around today? 16:08:55 bnemec please leave some notes if you get a chance on that review...others too 16:09:02 #topic Steps to cleanup oslo-incubator 16:09:02 #link https://etherpad.openstack.org/p/mitaka-oslo-incubator-cleanup 16:09:17 "There is `another proposal `" 16:09:21 who is interested in helping with this? (lots of reviews!) 16:09:49 bknudson thanks 16:10:08 i just started taking notes on what all we need to do for cleanup 16:10:17 in the etherpad above 16:10:28 should be easy reviews. 16:10:58 bknudson right, just yank stuff out and/or rename them 16:12:28 #topic First doc sprint for Mitaka 16:12:32 hi 16:12:38 yottatsa hi 16:12:57 anyone interested in organizing a virtual doc sprint? 16:13:06 when's a good time? 16:13:36 2 days just like last time and we make sure that all reviews are merged by end of the sprint 16:14:45 y'all are too quiet :) 16:15:16 dims I'm interested because I have a great plans for this cycle 16:15:31 yottatsa in doc sprint? 16:16:05 * dims opening up the floor 16:16:07 #topic Open discussion 16:16:07 Any stuck reviews? or specs? 16:16:18 Yep, actually mihgen asked me to write docs not code 16:16:19 ./ 16:16:23 pretty much any time works for me for a doc sprint 16:16:43 dims, did anything come of the conversation in tokyo re: oslo.messaging driver for zaqar? 16:16:46 bknudson ack, will ping harlowja_ and dhellmann later and throw out some dates 16:16:52 amrith nope 16:17:03 yottatsa nice! 16:17:08 #link https://blueprints.launchpad.net/oslo.config/+spec/oslo-config-db could you please look on the idea 16:17:50 dims, thanks. could I consider the conversation dead in that case? 16:17:57 yottatsa want to explain a bit about the spec you filed? 16:18:04 's/could/should/' 16:18:10 amrith unless someone from zaqar shows up... 16:18:17 ok, thanks. 16:18:20 nothing else for me 16:18:37 amrith thanks! 16:18:39 dims sure 16:19:17 yottatsa bknudson pointed to https://review.openstack.org/#/c/130047/ - you probably saw that one before too 16:20:02 We're trying to run OpenStack services in containers, and this requires to inject config files to dockerized software bundles. 16:21:02 This could be done by messing with mounting config dirs or layering containers 16:21:47 so you'd rather "pull" 16:22:03 Instead of this I introduced --config-db=provider://conn_string option to oslo.config's CLI. It enables pulling configuration directly from database. 16:22:30 yottatsa just once during initialization? 16:22:46 do you have any examples of other servers that can use etcd? 16:22:52 For now -- yes. 16:22:53 maybe apache httpd? 16:23:44 bknudson etcd and consul came up during the tooz/dlm discussions too 16:23:45 does it store individual config options for the whole config file? 16:24:04 bknudson I have no examples of apache httpd using cmdb, but I have an example of RabbitMQ using consul https://github.com/aweber/rabbitmq-autocluster 16:24:37 bknudson it stores individual config options hierarhically 16:25:06 This brings up interesting questions. We use config drive to push out TLS certs into the service VMs. I wonder how the security would work in a pull model. 16:25:09 like --config-db=zk://192.168.99.100:2181/openstack -> /openstack/DEFAULT/admin_token for example 16:25:25 (along with an oslo config) 16:26:34 you still have to get zk://192.168.99.100:2181/openstack to the container 16:27:13 bknudson a single url is easily sent to the docker container 16:27:25 through ENV variable for example 16:27:58 dims bknudson I've checked out 130047 before and I've mentioned this in bp. It could be an alternative, if rescoped. 16:28:38 yottatsa so my advice, ping harlowja_ later and ask his opinion as well. 16:28:49 bknudson providing configuration entry point seems acceptable for docker 16:28:49 yottatsa thanks for walking us through 16:29:12 can you make it handle the replacement vars in configs like ${compute_port}s 16:29:29 actually, would probably be better if it didn't handle replacements. 16:29:51 I'm always looking for a reason to get rid of that "feature" 16:29:56 :) Anyone else have anything to discuss? 16:30:21 going once 16:30:35 going twice 16:30:43 thanks everyone. talk to you all next week 16:30:45 bknudson speaking about replacements, if you layer --config-file and --config-db, you may actually handle a replacement out-of-the-box. I should verify this, th8 16:30:53 * dims hangs on 16:31:31 chef, ansible, and other tools already make it easy to set up your config without using replacement 16:31:44 so I think we should get rid of it. 16:32:00 there are other reasons to get rid of it that I won't go into 16:32:38 bknudson : let's do a spec (should be easy!), it's more for gathering +2's from everyone 16:33:28 #link actually, there is a spec in bp https://review.openstack.org/#/c/243114/ 16:34:02 yottatsa that was for dropping the replacement syntax 16:34:16 dims got it 16:34:34 k thanks everyone 16:34:42 #endmeeting