17:00:09 #startmeeting nova_cells 17:00:10 Meeting started Wed Jul 29 17:00:09 2015 UTC and is due to finish in 60 minutes. The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:14 The meeting name has been set to 'nova_cells' 17:00:49 anyone here today? 17:00:55 o/ 17:00:58 o/ 17:01:00 o/ 17:01:12 _o 17:01:16 \o even 17:01:43 great 17:01:53 #topic Tempest testing 17:02:02 melwitt: anything to report? 17:02:18 alaski: no, don't think so 17:02:35 we had some problems with the devstack install last night 17:02:41 (not speaking of tempest) 17:02:52 uh, last night EU time 17:03:06 what sort of problems? 17:03:16 alaski: sec, giving the URL 17:03:26 alaski: nothing related to cells, rather timeouts AFAICS 17:03:43 anyway, that's the only issue I spotted this week 17:04:24 http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiZXhpdCBjb2RlOiAxMzdcIiBBTkQgdGFnczpcImNvbnNvbGVcIiBBTkQgYnVpbGRfbmFtZTpcImdhdGUtZGV2c3RhY2stZHN2bS1jZWxsc1wiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI4NjQwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzgxODk0NTcwMzd9 17:04:38 but we can move on 17:04:48 okay. yeah, if not directly cells related 17:05:03 melwitt: thanks for the update, glad it's good 17:05:09 #topic Open discussion 17:05:45 just to update everyone, on my end I'm digging into the request spec stuff 17:06:05 I reworked my patch series to split it along different lines which took a bit, and bauzas reworking things hasn't helped :) 17:06:14 working on testing now and then I shoudl get some stuff up 17:06:33 thanks for the reviews on https://review.openstack.org/#/c/201606/ 17:06:37 alaski: yeah, sorry about that, but I had some good reviews :) 17:06:37 cool 17:06:49 alaski: so I had to work on some new PSs 17:07:03 alaski: that's the main problem when you have long series :) 17:07:24 belmoreira: np 17:07:42 bauzas: yeah, definitely understand. just makes my job harder :) 17:07:57 alaski: I have been travelling but should be good to continue the work now 17:08:16 alaski: eh eh, someone said in the midcycle that he was not happy with some SchedulerHints object so I had to rebase my whole series :p 17:08:38 belmoreira: great. that will be helpful 17:08:52 bauzas: I wouldn't listen to that guy 17:09:11 that does simplify things a bit though, so it's actually good 17:09:35 no worries :) 17:10:04 anyone else have a topic today? 17:10:21 until the summit we're likely to have a light agenda of just updates in this meeting 17:10:23 nothing apart saying I should be off for the next 2 weeks 17:10:32 again? :) 17:10:40 I have a question 17:10:42 I'm French, remember ? :) 17:11:09 we are populating instance_types with default flavors 17:11:23 belmoreira: in https://review.openstack.org/#/c/201606/ ? 17:11:44 oh, right. that's a terrible bit of code somewhere 17:11:51 should we continue with this in flavors table? 17:12:01 bauzas: is not there 17:12:44 belmoreira: I would like to say no. it's a bad thing we do currently and we should stop. but I don't know all the implications of that so we should probably bring this up at the nova meeting 17:12:52 belmoreira: alaski: oh ok, any code I could look at ? 17:13:21 oh, you mean when instanciating the instance_types table? 17:13:31 bauzas: I think it's in the 216_havana.py migration 17:13:32 isn't that a devstack-ish thing ? 17:13:39 I would be surprised if people are relying in those flavors 17:13:45 oh right 17:14:16 alaski: yep _populate_instance_types in 216_havana.py, correct 17:14:19 belmoreira: me too. but I'm often suprised 17:14:33 well, small clouds do 17:14:42 migration adds some flavors? that seems odd 17:14:43 as an operator, I was relying on those :) 17:14:56 melwitt: yeah, was thinking it was devstack or something else 17:15:01 melwitt: exactly. we bootstrap nova with some flavors 17:15:15 bauzas: yeah, I thought the same until alaski said it 17:15:27 bauzas: devstack would be the right place to do it, or maybe a nova-manage command though I don't really like that 17:15:42 alaski: devstack and/or package vendors 17:15:47 it feels like something we should just document, "add these flavors to get started" 17:16:05 that's just what we do for all the other data :) 17:16:13 alaski: +1 17:16:26 * bauzas remembers the early ages of deploying Diablo's debs :) 17:16:30 alaski: +! 17:16:56 alaski: yeah, nova-manage would have been as invasive as I'd think to go 17:17:24 melwitt: I would -1 a nova-manage hydrate-flavors 17:17:53 nova-manage is for providing something we can't do or won't do at the REST API level - very specific operations 17:17:54 okay, I'll add this to the nova meeting agenda and we can discuss it there. might need a ML post as well 17:18:25 I'd be surprised that operators would know about that - I would even bet that 99% of them think it's devstack 17:19:19 it also probably means that we(rax) have some code to strip those out when we bootstrap a new cell somewhere 17:19:58 bauzas: not sure... because is what they get in the DB when setup a cloud 17:20:40 at CERN they are available :) ...legacy 17:21:04 yeah, we don't use those canned flavors either so I guess we must delete them as part of the deployment automation 17:21:46 but we repopulate the tables with our flavors... 17:22:12 this would be a great chance to fix this 17:22:35 any other topics today? 17:23:09 oh, I have a question. since the meeting is going to be light until around the summit does it still feel useful to do weekly right now? 17:23:27 I'm happy to continue doing it 17:23:37 but don't want to waste peoples time 17:23:41 I'm cool with it not being weekly, but either way is fine 17:25:08 bauzas: belmoreira any thoughts? 17:25:16 otherwise melwitts one vote wins :) 17:25:26 meh 17:25:36 -_- 17:25:39 I may have some questions with flavors spec but I can ping you when needed 17:25:40 the 1700UTC is just family business 17:25:52 so I'd be happy to drop that one 17:25:58 unless urgent queries 17:26:05 vineetmenon: you get a vote as well :) 17:26:16 belmoreira: that works 17:26:43 how about we meet next week and if there's no resistance we'll alternate from then until summit 17:26:54 and drop the 1700 for now 17:27:09 1100UTC is too late for us in India.. but I don't want to disturb your family time. 17:27:32 vineetmenon: that's not really a PITA for me, just a matter of arranging my stuff :) 17:27:45 yeah, Vineet and Dheeraj connect from India 17:27:56 I'll read meeting log, meanwhile 17:28:32 we can drop either one, I just went with 1700 since bauzas spoke up 17:29:00 don't really look at me 17:29:13 bauzas: :) 17:29:16 if vineetmenon can't handle the 2100 one, I'm okay with keeping the 1700 one 17:29:27 I would prefer 1700, tbh. 17:29:45 okay. How about we reconvene in two weeks at this time? 17:29:45 I can hassle alaski anytime 17:29:48 2300UTC == 0230 IST, so it becomes terrible 17:30:03 bauzas and I overlap quite a bit anyways 17:30:58 #info Meeting will be held every two weeks at 1700 until summit 17:31:15 cool 17:31:15 should have include a timezone :( 17:31:25 you can do a #undo and do it again 17:31:28 I think 17:31:28 #undo 17:31:28 Removing item from minutes: 17:31:35 #info Meeting will be held every two weeks at 1700UTC until summit 17:31:37 melwitt: thanks 17:31:40 cool 17:31:44 anything else for today? 17:32:25 great. thanks everyone! 17:32:36 I will go continue to chase bauzas patch series now 17:32:40 #endmeeting