Thursday, 2015-01-15

*** sigmavirus24_awa is now known as sigmavirus2400:27
*** VW_ has quit IRC00:33
*** plaurin_ has quit IRC00:38
*** SridharRamaswamy has quit IRC00:38
*** ivar-lazzaro has quit IRC01:03
*** banix has joined #openstack-meeting-401:06
*** banix has quit IRC01:16
*** Rockyg has quit IRC01:27
*** sbalukoff has quit IRC01:28
*** jyuso has quit IRC01:31
*** jyuso has joined #openstack-meeting-401:34
*** sigmavirus24 is now known as sigmavirus24_awa01:42
*** qwebirc71232 has joined #openstack-meeting-401:42
*** david-lyle has joined #openstack-meeting-401:43
*** sarob has quit IRC01:47
*** sigmavirus24_awa is now known as sigmavirus2401:47
*** s3wong has quit IRC01:53
*** david-lyle has quit IRC02:06
*** ivar-lazzaro has joined #openstack-meeting-402:15
*** david-lyle has joined #openstack-meeting-402:16
*** ivar-lazzaro has quit IRC02:17
*** david-lyle has quit IRC02:19
*** Rockyg has joined #openstack-meeting-402:21
*** david-lyle has joined #openstack-meeting-402:23
*** salv-orlando has quit IRC02:38
*** Rockyg has quit IRC02:38
*** Rockyg has joined #openstack-meeting-402:40
*** david-lyle has quit IRC02:42
*** david-lyle has joined #openstack-meeting-402:43
*** Rockyg has quit IRC02:45
*** jyuso has left #openstack-meeting-402:45
*** david-lyle has quit IRC02:49
*** david-lyle has joined #openstack-meeting-402:56
*** watanabe_isao has quit IRC03:02
*** yamahata has quit IRC03:15
*** sigmavirus24 is now known as sigmavirus24_awa03:22
*** VW_ has joined #openstack-meeting-403:28
*** david-lyle has quit IRC03:32
*** salv-orlando has joined #openstack-meeting-403:38
*** salv-orlando has quit IRC03:56
*** asselin_ has joined #openstack-meeting-403:58
*** sbalukoff has joined #openstack-meeting-404:04
*** VW_ has quit IRC04:04
*** VW_ has joined #openstack-meeting-404:04
*** yamahata has joined #openstack-meeting-404:07
*** asselin_ has quit IRC04:32
*** palendae has joined #openstack-meeting-404:38
*** VW_ has quit IRC04:53
*** asselin_ has joined #openstack-meeting-405:06
*** s3wong has joined #openstack-meeting-405:12
*** s3wong has quit IRC05:14
*** carl_baldwin has joined #openstack-meeting-405:16
*** asselin_ has quit IRC05:20
*** carl_baldwin has quit IRC05:32
*** carl_baldwin has joined #openstack-meeting-405:32
*** numan has joined #openstack-meeting-405:54
*** salv-orlando has joined #openstack-meeting-405:56
*** salv-orlando has quit IRC06:14
*** carl_baldwin has quit IRC06:24
*** salv-orl_ has joined #openstack-meeting-406:30
*** salv-orl_ has quit IRC06:32
*** kobis has joined #openstack-meeting-407:25
*** belmoreira has joined #openstack-meeting-407:29
*** salv-orlando has joined #openstack-meeting-407:44
*** yamahata has quit IRC08:01
*** yamahata has joined #openstack-meeting-408:01
*** salv-orlando has quit IRC08:02
*** salv-orlando has joined #openstack-meeting-408:10
*** matrohon has joined #openstack-meeting-408:11
*** salv-orlando has quit IRC08:17
*** yamahata has quit IRC08:36
*** pkoniszewski has joined #openstack-meeting-408:48
*** pkoniszewski has quit IRC09:00
*** pkoniszewski has joined #openstack-meeting-409:01
*** pkoniszewski has quit IRC09:06
*** salv-orlando has joined #openstack-meeting-409:19
*** salv-orlando has quit IRC09:26
*** evgenyf has joined #openstack-meeting-409:34
*** igordcard has joined #openstack-meeting-409:35
*** qwebirc71232 has quit IRC09:37
*** pkoniszewski has joined #openstack-meeting-409:41
*** pkoniszewski has quit IRC09:49
*** gmatefi has joined #openstack-meeting-410:15
*** salv-orlando has joined #openstack-meeting-410:22
*** gmatefi has quit IRC11:09
*** gmatefi has joined #openstack-meeting-413:05
*** gmatefi has quit IRC13:09
*** pkoniszewski has joined #openstack-meeting-413:22
*** pkoniszewski has quit IRC13:29
*** gmatefi has joined #openstack-meeting-413:31
*** pkoniszewski has joined #openstack-meeting-413:35
*** pkoniszewski has quit IRC13:43
*** gmatefi has quit IRC13:56
*** jokke_ has joined #openstack-meeting-413:57
*** pkoniszewski has joined #openstack-meeting-413:57
*** mfedosin has joined #openstack-meeting-413:59
kragnizglancers?14:00
*** sigmavirus24_awa is now known as sigmavirus2414:00
mfedosinyep14:00
*** ivasilevskaya has joined #openstack-meeting-414:00
sigmavirus24o/14:00
kragniznikhil_k: around?14:01
nikhil_kyes yes...14:01
jokke_o/14:01
nikhil_k#startmeeting Glance14:02
openstackMeeting started Thu Jan 15 14:02:22 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
openstackThe meeting name has been set to 'glance'14:02
nikhil_kwe can continue the roll call for a bit14:02
kragnizo/14:02
pkoniszewskio/14:02
mfedosino/14:02
*** krykowski has joined #openstack-meeting-414:03
nikhil_kok14:03
sigmavirus24o/14:03
nikhil_k#info https://etherpad.openstack.org/p/glance-team-meeting-agenda14:04
nikhil_k#topic Updates14:04
nikhil_k#info +1 to the enabling of logging14:04
nikhil_k#action cindy to request the infra team for its impl14:05
* kragniz hides from jokke_ 14:05
*** mclaren has joined #openstack-meeting-414:05
nikhil_kCLI sorting standard for OpenStack projects14:06
nikhil_khttps://review.openstack.org/#/c/145544/14:06
nikhil_kThat change looks good overall14:06
mfedosini've already said my opinion :)14:06
* sigmavirus24 thinks he's read this already14:06
mfedosinlooks good14:06
nikhil_kand we've a corres. patch from mfedosin14:07
sigmavirus24Ah yeah. This is something the APIWG is discussing on the API side too14:07
nikhil_kLet's start working on the server side changes14:07
mfedosini'll add multiple sort dirs to glance server and change the client's syntax14:07
jokke_I looked it through ... I prefer the nova syntax there, but tbh it does not look consistent with the rest of the options14:07
jokke_I do like short and simple cli options, but all the rest are really verbose in our clients14:08
mfedosini thought i would do it today and tomorrow but artifacts take a lot of time14:08
sigmavirus24mfedosin: anyway I can help?14:08
mfedosinsigmavirus24, review it please, when it'll done14:09
nikhil_kok, cool14:09
nikhil_kseems like the train is on right track14:09
mfedosinI'll do it at the weekend14:09
nikhil_kVancouver Design Summit format changes14:09
*** wayne__ has joined #openstack-meeting-414:09
sigmavirus24mfedosin: I'm not sure you know what the weekend is actually for ;)14:09
nikhil_kyou may personally let me know your thoughts as well14:10
jokke_+all what I got ... I think that format change is really good direction14:10
mfedosinsigmavirus24, my girlfriend away for the weekend, so...14:10
nikhil_k#topic Reviews/Bugs/Releases14:11
*** pennerc has joined #openstack-meeting-414:11
*** rosmaita has joined #openstack-meeting-414:11
nikhil_kbot doesn't seem to be working14:11
pennerco/14:11
nikhil_khttps://review.openstack.org/#/c/146651/14:11
nikhil_ksigmavirus24: please take over14:12
sigmavirus24That's mine. I have ideas to add tests that I'll get to today or tomorrow, but I wanted to address the other proxy objects in the policy module14:12
sigmavirus24For each of them we pass an empty dictionary as a target which disables everything but the RoleCheck essentially14:12
sigmavirus24So you can't restrict an action based on tenant/tenant_id etc. I was wondering if people had ideas for *Target objects for the rest of the objects in glance.api.policy (ImageRepoTarget, MemberTarget, etc.)14:13
mclarensigmavirus24: other projects handle individual tenant ids if sent in the dictionary?14:13
sigmavirus24mclaren: I haven't checked every project but I'm pretty sure Keystone does14:13
mclarenok, thx14:13
sigmavirus24The target, to be clear, is just a representation of the object we're trying to interact with. The context holds the authenticated user's information and other things14:14
jokke_sigmavirus24: does that have any effect on the role checks?14:14
sigmavirus24jokke_: no14:14
nikhil_ksigmavirus24: we prolly should discuss this about metadefs with someone actually using it14:15
jokke_I think the next big thing is, how much we take performance hit by that14:15
nikhil_kwayne__: ^ ?14:15
wayne__yes14:15
nikhil_kif you compare it with the join of image-properties table, the performance hit would minimal; no?14:16
sigmavirus24jokke_: the enforcer already supports user-defined rules and checks and will follow them down regardless. There shouldn't be a significant performance hit (if any) by passing a target14:16
mclarensigmavirus24: it's a really minor thing but a link to the officially supported policy format/options might be useful as a reference for folks14:17
jokke_sigmavirus24: so the target is not a huge lump of data (sorry, this is part of the code I'm really not familiar with)14:17
sigmavirus24mclaren: okay. It's an oslo-inc project at the moment so it mainly exists in the module doc-string14:17
*** krykowski has quit IRC14:17
sigmavirus24jokke_: the target for the ImageTarget is just a wrapper/proxy around an models.Image instance so you can do target['owner'] => tenant_id14:18
jokke_sigmavirus24: ah ok ... thnx14:18
sigmavirus24jokke_: no need to apologize :)14:18
sigmavirus24mclaren: I'll get a link though right now14:18
sigmavirus24#link https://github.com/openstack/glance/blob/master/glance/openstack/common/policy.py#L16..L7614:19
jokke_we just get so much nagging of glance being the performance bottleneck that I would prefer us not at least increasing the delays :D14:19
sigmavirus24ayoung and morganfainberg are pulling it out of the incubator though into oslo.policy this cycle but we probably shouldn't transition to it until L14:19
sigmavirus24jokke_: that's understandable14:19
jokke_++14:19
sigmavirus24And to be transparent, I only found this bug because os-ansible-deployment was trying to set different defaults for Rackspace Private Cloud customers and we found no matter what we did, it 403'd (because the targets were empty)14:20
nikhil_kI'm a little worried if operators keep this as expected behavior and have things running14:20
mclarensigmavirus24: thx!14:20
sigmavirus24nikhil_k: the bug was originally reported in 2012, so people who try may just give up while others never change policy.json14:21
sigmavirus24I suspect some operators expect the defaults in policy.json to be secure instead of relaxed14:21
nikhil_ksigmavirus24: agree to make them more _granular_14:21
*** krykowski has joined #openstack-meeting-414:21
sigmavirus24Anyway, I just wanted people's eyes and thoughts. I'm not familiar with the other objects but it should be simple to write proxy objects like ImageTarget (or one generic Target object) for the rest of the "targets"14:22
sigmavirus24We can move on14:22
nikhil_ksigmavirus24: may be a ML discussion on this ?14:22
sigmavirus24Also, let me know if I should write the ML about this for further input14:22
sigmavirus24hah14:22
nikhil_kwe can start working on a spec too, for keeping the upgrade to K smooth14:23
sigmavirus24Sounds fair14:23
nikhil_khttps://review.openstack.org/#/q/topic:bp/drop-namespace-packages+owner:kragniz%2540gmail.com,n,z14:23
kragnizthis is a fairly trivial update to the oslo library's namespaces14:24
kragnizbut it would be nice if they could be merged swiftly to avoid any conflicts arising14:24
*** numan has quit IRC14:25
kragnizmoving out of the oslo namespace avoids the bugs with picking up the globally installed version of the libraries, rather than the ones in the local venv14:25
mclarenkragniz: I can try to review (remind me if I forget)14:26
kragnizmclaren: sure!14:26
nikhil_kok, next?14:26
kragniznikhil_k: yup, that all for that14:27
nikhil_ksigmavirus24: do we need to discuss the defaults here?14:27
nikhil_kguess no?14:27
*** plaurin_ has joined #openstack-meeting-414:27
sigmavirus24no sorry. that won't work anyway until that target issue is resolved14:27
nikhil_kthanks!14:27
nikhil_k#topic Glance's developer docs14:28
sigmavirus24oh yeah that's me too14:28
nikhil_k#info Nova's DevRef: http://docs.openstack.org/developer/nova/devref/development.environment.html14:29
sigmavirus24So while we were debugging an issue with sqlalchemy-migrate we found that we don't tell developers what they need installed (other than Python dependencies) to get a test/dev setup running14:29
sigmavirus24Nova has DevRef (Developer Reference) and we discussed potentially adding something similar. For example, our tests expect "curl" to be installed on the system but if you don't have that, your tests will fail locally14:29
kragnizthis is a great idea14:30
sigmavirus24That particular example is what led to the discussion. I can get a first draft up based on Nova's DevRef if we all think it's a beneficial document14:30
nikhil_kmfedosin: does your work on the doc cover some of this?14:30
jokke_Actually I think this would be brilliant to bring to ML14:30
mfedosinyes14:30
kragnizif we just start with something simple and exand it later, it would be good14:30
mfedosinwe will got 4 elements there14:31
mfedosinarchitecture, components, domain and db14:31
rosmaitahow different would it be from the nova doc?14:31
jokke_I think it would be way more beneficial if we get cross OS doc (even with project specific sections) rather than every project having their own14:31
rosmaitajokke_: +114:31
mclarenyeah, maybe just track the delta for each project14:31
kragnizjokke_: there is value in "run these commands to start hacking on glance", though14:31
mfedosinrosmaita, some elements will be equal14:31
*** VW_ has joined #openstack-meeting-414:31
rosmaitado you think a "delta" doc would be sufficient, or would it be confusing?14:32
jokke_kragniz: thus the project specific sections to that global doc14:32
nikhil_kmfedosin: just need to add "tests" element to it14:32
sigmavirus24rosmaita: for totally new openstackers, probably more confusing than helpful14:32
jokke_if all agree14:32
jokke_that's what I thought as well ...14:33
mfedosinnikhil_k, okay14:33
sigmavirus24jokke_: where should the global doc live though?14:33
nikhil_krosmaita: hard to contribute and keep that in sync globally14:33
mclarennot sure. (I was thinking sometimes these kind of docs can become stale over time). Docs in any form sound great!14:33
sigmavirus24I can start a discussion on the ML if we want14:33
rosmaitasigmavirus24: +114:33
nikhil_ksure14:33
kragnizsigmavirus24: +114:33
sigmavirus24See how people feel about making it a global thing with project deltas14:33
mfedosini suppose this doc will be about inner glance, instaed of nova where some common things are described14:34
jokke_sigmavirus24: docs.openstack.org - Contribute to OpenStack14:34
nikhil_ksigmavirus24: chat after the meeting on this topic ?14:35
*** VW__ has joined #openstack-meeting-414:35
sigmavirus24nikhil_k: sure14:35
nikhil_k#topic Generating config files with oslo-config-generator14:35
nikhil_kkragniz: go go14:35
*** VW__ has quit IRC14:35
*** VW_ has quit IRC14:35
kragnizso currently, we're manually syncing the config options in code and in the sample config files14:36
*** TravT_ has joined #openstack-meeting-414:36
kragnizwe have the capability to generate these files automatically14:36
*** VW_ has joined #openstack-meeting-414:36
kragniz(see tox -e genconfig)14:36
kragnizso I think we should drop the config files from master and just generate them14:36
kragnizthis is what nova, cinder, ceilometer and others currently do14:37
sigmavirus24I ran this to generate the glance-manage.conf file and it re-generated the others. The delta was rather large if my memory is correct14:37
mclarensounds like a good idea. I guess a lot of projects are already doing that?14:37
kragnizsigmavirus24: the deta is due to formatting changes14:37
kragniziirc14:37
jokke_kragniz: -1 ... if you look through the meeting logs over last year this has been discussed quite a few times already14:37
* kragniz hasn't seen those logs14:38
sigmavirus24I'm +1 on the idea but the first pass should be done carefully (I'm rather paranoid)14:38
kragnizjokke_: what are your reasons, other than that's what happened last time it was discussed?14:38
nikhil_kalso, it would nice to chck the bahcior with new adidtions and deletions14:38
kragnizsigmavirus24: I agree14:38
jokke_kragniz: the reasoning having the configs in the master is to be able to refer to the config files at github and so far we haven't been able to figure out way to generate them to the repo automatically14:38
nikhil_kbehavior*14:38
sigmavirus24jokke_: I'm not sure I follow14:39
jokke_kragniz: the auto update has been on discussions quite a lot, we just havent found a way to do it14:39
kragnizjokke_: but those values in the config files are duplicated from where the oslo.config option is declared14:39
kragnizjokke_: and keeping these files up to date is a lot of contributor effort14:40
jokke_sigmavirus24: we'd like to have access to the example configs without the need to clone the repo and generating them every time you need to refer to them for new folks etc.14:40
sigmavirus24jokke_: kragniz is talking about generating the ones that exist in-tree and committing them I think14:40
mclarendo other projects have non-generated reference config files?14:40
kragnizand it's not happening in some places14:41
kragnizglance-cache.conf hasn't been updated with the glance_store options, for example14:41
*** flaper87 has joined #openstack-meeting-414:41
sigmavirus24mclaren: they have https://github.com/openstack/keystone/tree/master/etc .conf.example configs14:41
* flaper87 is late to the party14:41
mclarenok, thx. Wonder what their magic is?14:41
* jokke_ thought that the example configs we have are actually the generated ones ... the commit was just supposed to be manual process14:42
* flaper87 acts as if he knows what we are discussing14:42
kragnizhttps://github.com/openstack/nova/blob/master/etc/nova/README-nova.conf.txt14:42
sigmavirus24jokke_: the example configs we have aren't auto-generated and if you do generate them, I think some of the defaults may even be different (or values aren't commented out)14:43
sigmavirus24But yeah, they're pretty much equivalent at the moment. The ordering may be the only delta (I trust kragniz to be right about this)14:44
flaper87sigmavirus24: mmh, then we need to fix auto-generation14:44
flaper87I mean, it should work14:44
flaper87(TM)14:44
sigmavirus24flaper87: "Just Work" is a trademark the OpenStack Foundation hasn't been allowed to license yet ;)14:44
kragnizflaper87: you keep config files out of tree in zaqar, right?14:44
jokke_yup ... zhiyan has put lots of effort to get the generation working ... thus I thought that the confs were actually iteration of the output14:44
flaper87kragniz: correct14:44
flaper87you just tox -egenconfig14:45
flaper87one of the points behind having auto-gen is not having samples14:45
flaper87:)14:45
nikhil_kflaper87: would the documentation and description be covered so thoroughly?14:45
flaper87because lets face it, we keep failing at keeping them updated14:45
flaper87nikhil_k: as in explaining how to generate them?14:45
flaper87yes14:45
mclarenanyone know of a project using auto-gen that also has samples?14:45
nikhil_k:D14:45
sigmavirus24nikhil_k: the docs.openstack.org/{{project}}/ docs have to be updated manually though no matter what14:46
flaper87https://github.com/openstack/zaqar#running-a-local-zaqar-server-with-mongodb14:46
flaper87we even put it in the README14:46
sigmavirus24Cinder does mclaren https://github.com/openstack/cinder/tree/master/etc/cinder14:46
kragniznikhil_k: do you mean descriptions for each option?14:46
flaper87mclaren: nope14:46
jokke_:)14:46
nikhil_kflaper87: I meant the comments on the configs14:46
nikhil_kkragniz: yeah14:46
*** asselin_ has joined #openstack-meeting-414:46
flaper87nikhil_k: ah yea, they are kept14:46
flaper87it's a matter of keeping the help text updated14:47
flaper87:D14:47
jokke_iirc cinder reasoning for that was the same why we decided to keep em, to have easy access to example configs14:47
kragniznikhil_k: yes, since it grabs whatever text you use when you declare the oslo.config option14:47
nikhil_kflaper87: heh, so that will proly never happen :P14:47
flaper87mmh, well, it's part of reviewers task to enforce useful help texts14:47
sigmavirus24jokke_: actually, I was half right: cinder.conf isn't kept https://github.com/openstack/cinder/blob/master/etc/cinder/README-cinder.conf.sample14:47
nikhil_kkragniz: it's not that great compared to what's mentioned in the sameple14:47
nikhil_kthough it can be corrected14:48
kragnizjokke_: cinder removed their configs from tree14:48
sigmavirus24everything else is probably really not much more configurable14:48
flaper87as for the existing ones, it'd be a good exercise to update our code base14:48
nikhil_kflaper87: yeah, I understand14:48
kragnizjokke_: https://github.com/openstack/cinder/blob/master/etc/cinder/README-cinder.conf.sample14:48
flaper87if we want to keep them, then we better add a test that the sample is updated14:49
flaper87that verifies*14:49
kragnizflaper87: +114:49
jokke_oh gr8 :(14:49
flaper87Having samples means that people will use them as reference14:49
jokke_flaper87: +214:49
flaper87I've had people pointing me to an option that doesn't exist anymore14:49
flaper87and I was like: "So well, how do I put it in a nice way... mmhh... the sample is outdate... /me RUN"14:50
mclarena test sounds like it might work. I think we already have some tests for options14:50
nikhil_ksounds like an agreement (somewhat)14:50
flaper87(and that *just* after cutting the release)14:50
flaper87mclaren: afair, cinder has (had?) something to do exactly this14:50
flaper87we might want to check what they do(did?)14:50
flaper87(may?)14:51
nikhil_kcan we move on to the next one?14:51
* flaper87 will never get those 2 right14:51
* flaper87 crashed this one so... I guess?14:51
flaper87:P14:51
kragnizwhatever we do, I don't think we should be manually updating the configs14:51
kragniznikhil_k: sure14:51
nikhil_k#topic Glance upgradeability14:51
pkoniszewskithat's me14:51
nikhil_kpkoniszewski: that's you ^14:51
mclarenflaper87: cinder...not sure tbh14:52
pkoniszewskinova is working on smooth updates between versions of openstack, is there anything being done in glance or is there any plan to make support for upgrades in glance/14:52
pkoniszewski?14:52
pkoniszewskiespecially versioned objects, any plan for K or L release?14:53
nikhil_kpkoniszewski: nothing for K14:53
nikhil_kwe can plan for L after nova has tried and tested it, I sup?14:53
pkoniszewskithat sounds good14:54
kragniznikhil_k: let nova be the guinea pig :P14:54
flaper87a good thing to do in advance would be working out a spec explaining how you see this being implemented in glance14:54
pkoniszewskisure14:54
pkoniszewskiI plan to14:54
flaper87I'm not sure how many of us are familiar with what nova is doing14:55
flaper87:(14:55
jokke_flaper87: I thought you know nova inside out by now :P14:55
pkoniszewskiwell I'd like to write blueprint with explanation, but need some time for that14:55
flaper87jokke_: oh man, you have no idea. I wish I didn't...14:55
flaper87:P14:56
*** gmatefi has joined #openstack-meeting-414:56
nikhil_kpkoniszewski: Thanks for bringing that up, I think this would be a great change.14:56
kragnizflaper87: I think it involves equal doses of magic and semver14:56
nikhil_k#topic Open Discussion14:56
mclarenflaper87: cinder have tools/config/check_uptodate.sh so maybe some prior art14:57
nikhil_kDo we want to keep meeting next week before the mid cycle meetup?14:57
nikhil_kIf not, would like to cancle Jan 22 and Jan 29 meetings14:57
kragnizmclaren: that looks useful14:57
flaper87mclaren: yeah, that. They used to call that script in the gate14:57
sigmavirus24nikhil_k: is there a good reason to not keep next week's meeting?14:58
jokke_nikhil_k: would be great to have them14:58
jokke_nikhil_k: specially recap after the meetup14:58
flaper87lets keep meeting14:58
* flaper87 won't be at the mid cycle meetup14:58
pkoniszewskiyep, lets keep the next week meeting14:59
nikhil_kI thought people don't like meetings, guess not true14:59
pennercI agree.14:59
kragnizI'd rather keep them14:59
sigmavirus24nikhil_k: just because I don't like them doesn't mean they're not valuable ;)14:59
nikhil_kok cool14:59
nikhil_kanything else?14:59
* jokke_ agrees with sigmavirus24 14:59
*** wayne__ has quit IRC14:59
sigmavirus24^5 jokke_15:00
nikhil_kThanks all!15:00
nikhil_k#endmeeting15:00
kragnizthanks!15:00
openstackMeeting ended Thu Jan 15 15:00:21 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-01-15-14.02.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-01-15-14.02.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-01-15-14.02.log.html15:00
jokke_thanks15:00
mclarenthanks!15:00
*** mclaren has quit IRC15:00
*** carl_baldwin has joined #openstack-meeting-415:00
*** flaper87 has left #openstack-meeting-415:01
*** carl_baldwin has quit IRC15:01
*** wayne__ has joined #openstack-meeting-415:01
*** carl_baldwin has joined #openstack-meeting-415:02
* TravT_ sorry to only be able to be a fly on the wall this morning - getting kids ready for school15:02
nikhil_knp15:03
nikhil_kTravT_: we'r in other channel now15:03
pennerclater15:03
*** pennerc has quit IRC15:04
TravT_Yeah on my phone so I think my update took awhile to send15:04
*** jokke_ has left #openstack-meeting-415:04
*** TravT_ has quit IRC15:05
*** pkoniszewski has quit IRC15:06
*** yamahata has joined #openstack-meeting-415:06
*** wayne__ has left #openstack-meeting-415:07
*** asselin_ has quit IRC15:11
*** cloudnull has joined #openstack-meeting-415:18
*** mestery has quit IRC15:24
*** mestery has joined #openstack-meeting-415:28
*** gmatefi has quit IRC15:35
*** dboik has joined #openstack-meeting-415:36
*** Shrews has joined #openstack-meeting-415:39
*** banix has joined #openstack-meeting-415:39
*** VW_ has quit IRC15:41
*** krykowski has quit IRC15:43
*** VW_ has joined #openstack-meeting-415:44
*** alextricity has joined #openstack-meeting-415:48
*** dboik has quit IRC15:48
alextricityMorning/afternoon15:48
*** mattt has joined #openstack-meeting-415:53
cloudnullmorning15:53
*** b3rnard0 has joined #openstack-meeting-415:54
mattt\o15:57
cloudnull#startmeeting openstack-ansible15:57
openstackMeeting started Thu Jan 15 15:57:18 2015 UTC and is due to finish in 60 minutes.  The chair is cloudnull. Information about MeetBot at http://wiki.debian.org/MeetBot.15:57
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:57
openstackThe meeting name has been set to 'openstack_ansible'15:57
alextricity#help15:57
alextricityfail15:57
*** carl_baldwin has quit IRC15:59
*** andymccr has joined #openstack-meeting-415:59
cloudnullso , lets get started.16:00
sigmavirus24o/ cloudnull16:00
*** kobis has quit IRC16:00
cloudnullfirst on the agenda is our milestones16:00
*** Sam-I-Am has joined #openstack-meeting-416:00
cloudnullwe have 10.1.2 and 9.0.6 that needs to be prioritized.16:00
cloudnullI think that we can commit to dev readyness for these "releases" in 2 weeks.16:01
cloudnullthoughts ?16:01
palendaecloudnull: Do we have a list of what's going to be on those milestones?16:02
mattti'm not aware of much happening in 9.0.x, quite a few things are in the pipeline for juno branch right now tho, so that will need a fair bit of testing16:02
cloudnullpalendae: im looking at https://launchpad.net/openstack-ansible/+milestone/9.0.616:02
andymccrcloudnull: i think logging is a big "must go" for that release16:02
cloudnulland https://launchpad.net/openstack-ansible/+milestone/10.1.216:02
palendaeOk16:03
b3rnard0cloudnull should we do a roll call first :-)16:03
cloudnullandymccr Agreed. i think logging needs love and is a must go.16:03
palendaeI htink this could be pulled off of the milestones, since RBAC is evidently broken - https://bugs.launchpad.net/openstack-ansible/+bug/140836316:03
cloudnullb3rnard0: we're already moving along :)16:04
cloudnullpalendae: i tend to agree those changes were recently reverted.16:04
cloudnullsigmavirus24: was working on that a bit, sigmavirus24 thoughts?16:05
sigmavirus24Glance is terribly broken and can't support what we want.16:05
cloudnullandymccr: how far are we on making logging happy ?16:05
palendaeUnless we want to keep them open and fix it when Glance is fixed16:05
sigmavirus24The revert patchset made it through this morning for master. The other two patchsets were abandoned16:05
andymccrcloudnull: we're pretty close odyssey4me basically has it going, we're fixing some bugs on a fresh install i did today16:05
sigmavirus24palendae: we can do that too but the glance fix was discussed in the glance meeting this morning and will take some time to work through the process (spec, adding more to the change, etc.)16:06
andymccrso i'd say 2 weeks i no problem.16:06
palendaesigmavirus24: yeah, I figured it'd be a while16:06
sigmavirus24So it won't be feasible for either of these next milestones16:06
cloudnullandymccr: for juno or icehouse ?16:06
palendaeRight16:06
andymccrcloudnull:  its on master but the backport shouldnt be too bad, its mostly changing logstash filters and adjusting some ownerhsip on log dirs16:06
palendaesigmavirus24: My guess is Kilo at the soonest, but likely L release16:06
andymccrso the filters would be the same for both16:06
sigmavirus24No I think we'll make this change in Kilo but it will take a couple of weeks16:07
sigmavirus24I need to prioritize writing the spec today or tomorrow etc16:07
palendaeok16:07
sigmavirus24That's a bit off topic though16:07
palendaeSure16:07
cloudnullok, sigmavirus24 palendae we'll pull "https://bugs.launchpad.net/openstack-ansible/+bug/1408363" for the time being and put it to "next" noting that its broke upstream .16:08
*** rosmaita has left #openstack-meeting-416:08
*** dboik has joined #openstack-meeting-416:09
sigmavirus24cloudnull: ++16:09
cloudnullwith the other open items on 10.1.2 do we think we can get ready for release in 2 weeks ?16:09
cloudnullmattt. mancdaz, odyssey4me?16:10
matttcloudnull: i'm not aware of any blockers16:10
palendaeBased on the currently in progress tickets, I think so16:10
cloudnullok. well then thats what we'll shoot for.16:11
cloudnullandymccr do you have a specific launchpad issue for the logging bits you guys have been working on ?16:12
*** d34dh0r53 has joined #openstack-meeting-416:12
andymccrcloudnull: i think it comes off the back of the logstash: parse swift logs issue16:12
cloudnullok, ill add that to 9.0.6 and 10.1.2. can we change the heading of that issue for more general logstash work?16:14
andymccrim sure we can or create a new one to handle the "pre swift" stuff16:14
cloudnullok.16:14
cloudnullon to our new bugs:16:15
cloudnullhttps://bugs.launchpad.net/openstack-ansible/+bugs?search=Search&field.status=New16:15
cloudnullwe need to prioritize and triage all 27 of these16:15
cloudnullidk that we cover each bug in our meeting here. but we needs to do it and stay on top of it16:16
*** hughsaunders has joined #openstack-meeting-416:16
*** mancdaz has joined #openstack-meeting-416:16
sigmavirus24cloudnull: +116:17
sigmavirus24if a few people want to volunteer to look at them once a day that'd probably make it manageable16:17
b3rnard0cloudnull: i would start at the top and go down the list unless someone has a bug we should look at first16:17
cloudnullill be doing it for sure moving forward and that im not on vacation , but it would be great to get some people to commit to review/triaging16:18
b3rnard0cloudnull: sounds like sigmavirus24 is stepping up to the plate again16:18
matttwonder if we need to leverage the affects me thing a bit more16:18
d34dh0r53I'll work on review/triaging16:18
mancdazyes I'm happy to do that16:18
matttto guage who wants what etc.16:18
sigmavirus24b3rnard0: don't make me hurt you16:18
cloudnullhaha16:19
sigmavirus24mattt: the affects me can help "confirm" a bug16:19
sigmavirus24but the bug should be "triaged" once a bug owner verifies it and determines import16:19
matttsigmavirus24: right but we need a way to determine how many people are interested in a feature/functionality16:19
sigmavirus24mattt: for new features, yes16:19
sigmavirus24and if it's clearly a feature, just mark it wishlist and move on16:19
sigmavirus24=P16:19
mattt:)16:20
cloudnullthe only three bugs that i want to talk about here to get triaged are the "undecided" bugs.16:20
d34dh0r53are we targeting bugs to milestones?16:20
cloudnullspecifically gating is not enabled on non-master branches16:20
cloudnullhughsaunders do we know how/when we can get that going ?16:20
*** SridharRamaswamy has joined #openstack-meeting-416:21
mancdazcloudnull odyssey4me should be able to sort that out16:21
hughsaunderscloudnull: we can enable aio or multi node checks16:21
mancdazhe put the original review to disable them in the gate16:21
cloudnullwhere is odyssey4me?16:21
mancdazand I've put a review in to get the gate scripts synced into those branches as a precursor to turning it back on16:21
cloudnullok.16:22
*** odyssey4me has joined #openstack-meeting-416:22
cloudnullok so if we can get gatting going on the branches sooner than later it would be great.16:23
matttodyssey4me: do you want hugh/i to pick taht up if you're tied up w/ other stuff ?16:23
mancdazcloudnull yep. hughsaunders and I were also talking this morning about enabling voting as soon as the gates are stable16:23
mancdazso that it's actually a gate, as opposed to something people mostly ignore16:24
odyssey4meI'm happy to do that - the aio appears to be stable now16:24
hughsaundersodyssey4me: do you plan to add tempest to the aio?16:24
odyssey4meI take it that we want to get it voting on the non=master branches too?16:24
odyssey4mehughsaunders: yeah, that would be ideal - but afaik we don't have a properly working set of tempest tests do we?16:24
*** dboik has quit IRC16:24
cloudnullodyssey4me: i'd say yes.16:24
mancdaz+116:25
cloudnullother than that, i'm done with bugs , unless there are a few that people want to talk about specifically?16:25
hughsaundersodyssey4me: sadly not since the glance issues kicked off16:26
*** markvoelker has joined #openstack-meeting-416:26
cloudnullanything?16:27
*** SridharRamaswamy has quit IRC16:27
cloudnullok, moving.16:27
cloudnullnext on the agenda "Making everything more generic".16:27
*** carl_baldwin has joined #openstack-meeting-416:28
cloudnullthis was the biggest ask from people replying to the original mailing list post16:28
cloudnullpresently we have rpc, rackspace, and rax all over the place.16:28
*** markvoelker has quit IRC16:28
cloudnullmost people have said they want that gone before they begin using it.16:29
cloudnulladditionally it was asked if we can make the roles less lxc dependent and more galaxy like .16:29
cloudnullwhich is all part of the separating the rax product release we have into a more community project.16:30
d34dh0r53so those  two things should be though of as one task?16:30
odyssey4meshould we kill two birds with one stone and do it at once, or should we dig into doing it with the current method first?16:30
cloudnulli've taking the route of killing the multiple birds16:30
cloudnullbut that could be done as a step by step process.16:30
andymccrcloudnull: agree but thats not a simple thing so we need some kind of plan - i also want to avoid a situation where its one persons task and nobody else has any idea. Or a situation where there is a month period where any improvements are wasted because its a wholesale change.16:31
andymccradditionally we have to consider how current installs would upgrade - although if we do it right that shouldn't be a problem.16:31
cloudnullandymccr: agreed.16:31
cloudnullif we do it right.16:32
cloudnullthere are multiple blueprints on this, which I would like people to participate in16:32
sigmavirus24You can #link them here so they're included in the notes ;)16:32
cloudnullsadly the blueprints were created "2014-12-10" and nobody but myself has even looked at the,16:32
*** belmoreira has quit IRC16:33
cloudnullhttps://blueprints.launchpad.net/openstack-ansible/+spec/galaxy-roles16:33
cloudnullhttps://blueprints.launchpad.net/openstack-ansible/+spec/rackspace-namesake16:33
cloudnullhttps://blueprints.launchpad.net/openstack-ansible/+spec/inventory-cleanup16:33
cloudnullnow, i've started the rax namesake and galaxy roles which can be seen here. https://github.com/os-cloud and now that im formally asking i'd like people to look at and help out with getting that done.16:34
palendaeI looked at the inventory cleanup, but it's been a while16:34
cloudnulllike andymccr said we need a plan .16:34
cloudnulland not just my plan16:34
matttyeah how do we split this up?16:34
b3rnard0let's add an action item to come up with a plan16:35
palendaeWe've got a start on broken-out roles16:35
palendaeBut we need more people than cloudnull looking at them. I've done some very brief work, but need to dive further16:35
cloudnullmattt like palendae said, we've started on the broken out roles. i've not done or looked at logging, neutron, horizon, or swift.16:36
odyssey4meI would guess that we need to review existing infrastructure galaxy roles and see if they suit our needs and are responsive to our PR's. It's either that or we develop our own infrastructure service galaxy roles and maintain them within the community.16:36
matttcloudnull: cool but i've not seen any reviews for this stuff?16:37
matttor did i miss them?16:37
palendaemattt: They're at https://github.com/os-cloud16:37
matttwhat is that?16:37
odyssey4meI took a brief look through some related to galera earlier today.16:37
palendaeI think part of cloudnull's logic was he wasn't sure how many repos it would be, and didn't want to bug stackforge infra until he did16:37
cloudnullmattt there have been no reviews for them . because we need to decied if we want to have the roles in sub repos in stackforge or in a master repo like we have now.16:37
*** git-harry has joined #openstack-meeting-416:38
cloudnullalso yes. we've bothered infra enough for now16:38
matttok i just worry about going off to the side to develop stuff16:38
matttseems a bit counter-productive16:38
cloudnullif we follow the puppet, and cookbooks they have sub repos so it shouldnt be a big ask to have them make the additional repos16:39
hughsaunderscould we gradually convert our existing roles into galaxy roles in the current stackforge repo?16:39
hughsaundersthen split out into separate repos at a later point?16:39
palendaeThat sounds reasonable to me16:39
cloudnullhughsaunders, we could however pulling the roles in with a galaxy requirements file would be a bit cumbersome16:39
cloudnullwith static and remote roles16:39
hughsaundersinitially yes, but better than a big-bang switchover?16:41
odyssey4mecould we not do a set of basic starting repo's in stackforge - empty as placeholders16:41
cloudnullmattt its counter productive to have a side repo, im not saying we use the test things i've created. but they exist to see how it worked is a collective whole.16:41
*** Shrews has left #openstack-meeting-416:42
cloudnullodyssey4me: i say we should be able to maintain a few place holders that we gradually migrate to .16:42
matttcloudnull: i know what you're getting at16:42
odyssey4meinitially we just create repo's per openstack project we work with - let them be blank to start with, then we transition code into them and start adjusting them16:43
odyssey4meand also start adjusting the 'parent' repo to work with them16:43
*** miguelgrinberg has joined #openstack-meeting-416:44
sigmavirus24quick, voluntell miguelgrinberg to do something since he's late ;)16:44
cloudnullhughsaunders, agreed. a big ban switchover would be hard to swallow. but we need to do something so other people, not rackspace, begin contributing.16:44
cloudnullmiguelgrinberg: your on code review for 2 weeks. :)16:44
d34dh0r53how is the upgrade process for moving from our traditional roles to the galaxy roles (from a user perspective)?16:44
miguelgrinbergcloudnull: sorry, last minute ETO16:45
cloudnullhahaha16:45
cloudnullj/k miguelgrinberg16:45
cloudnulld34dh0r53 they need to get the roles using the ansible-glaxey command16:45
cloudnullwhich exist in a yaml file.16:45
hughsaundersConverting our current roles to be galaxy compliant, with the repo, and removing rax branding at the same time could work16:46
d34dh0r53but can those roles be run on an existing cluster?16:46
hughsaunders*within16:46
cloudnulld34dh0r53: ie https://github.com/os-cloud/os-ansible-deployment/blob/master/ansible-role-requirements.yml16:46
matttcloudnull: so could we create roles under os-cloud and link to them from our existing os-ansible-deployment repo?16:46
cloudnulld34dh0r53: yes, if we like andymccr said do it right.16:46
odyssey4meIt would seem that I need to do some playing to understand how the galaxy-based roles work first.16:46
matttodyssey4me: heh same16:46
cloudnullmattt yes.16:46
d34dh0r53that was a major concern that the directorator had in discussions with logging, we need to ensure that we can in-place upgrade existing clusters without losing anything16:47
cloudnulld34dh0r53 odyssey4me https://github.com/os-cloud/os-ansible-deployment/blob/master/bootstrap.sh#L74-L77 thats essentilly the change to get the roles.16:47
matttcloudnull: i guess that makes sense, and we can bring roles from os-cloud into stackforge as we see fit16:48
d34dh0r53+1 I like that idea16:48
matttbecause presumably the infrastructure-related roles wouldn't need to live under stackforge (galera/rabbit/etc)16:48
odyssey4mecloudnull so does that essentially cache the role locally, then operate it similarly to how we work now?16:48
cloudnullodyssey4me yes.16:49
odyssey4meso an approach could be that we actually convert to using galaxy roles for the infrastructure first, then look at the openstack stuff later (or in parallel)16:49
cloudnullit also makes it so that we can pull different version of the role as needed.16:49
cloudnulli'd do it one at a time. and would like to have the roles in stackforge for the whole review process.16:50
hughsaundersincluding github modules in stackforge leads to different review/contribution processes for parts of the same project.16:50
cloudnullif we take a staggered approach16:50
odyssey4meso we create new blank repo's for any openstack project roles in stackforge as placeholders16:50
cloudnulli want to avoid what hughsaunders said .16:50
odyssey4methen we divide up the tasks of transitioning the existing roles (both infra and openstack) to make use of galaxy roles (in stackforge and outside for infra)16:51
andymccrif we do it staggered can we create a set of guidelines on the first one, that are followed on the following conversions - we can adjust the guidelines/backport changes as required to the already changed ones.16:51
cloudnullodyssey4me yes, but to do so we need to ask infra, which i'd like to limit so we should figure out how many repos we'll need leave them blank and gradually migrate to them as we see fit.16:51
palendaeThere's also the question of removing rax/rpc mentions in the repo; I think this can be done without moving any repos16:52
palendaeAnd should probably be done prior to separating roles16:52
*** igordcard has quit IRC16:52
cloudnullpalendae well thats the hardest part. we have rpc rax rackspace everywhere.16:52
odyssey4mesurely we need just one for each openstack project, ie nova, glance, heat, keystone, swift, openstack-client16:52
palendaecloudnull: Yeah16:53
cloudnullodyssey4me, yes nova galnce ...16:53
cloudnull*glance16:53
cloudnullwhich collapses our logic into a role.16:53
cloudnullinstead of the play which is what we have.16:53
odyssey4mewe just call them 'ansible-openstack-nova', etc16:53
hughsaundersif we're not sure how many repos we need, why not create these roles as dirs in the existing repo, then migrate to separate repos once the roles have stabilised?16:54
cloudnullodyssey4me id say yes.16:54
cloudnullyou can see an example of collapsed logic here https://github.com/os-cloud/opc_role-os_nova/blob/master/tasks/main.yml16:54
cloudnullhughsaunders we could do that.16:54
mattti think that is a good idea16:54
matttgives us some room to experiment16:55
hughsaunderswe may need multiple roles for some projects16:55
matttwhile still keeping everything in stackforge16:55
odyssey4meyeah, I must say that for simplicity's sake it would be easier to evolve as far as possible in one repo before splitting it out16:55
*** yamahata has quit IRC16:55
andymccrif they are truly independent then it will be no problem to move the directory into its own repository if we decide that is better16:55
andymccrat that point we know exactly what we need though16:55
andymccrif thats possible i think we should do that16:56
cloudnullok, well make the roles as galaxy roles and keep them in the main repo until such a point where we migrate them to separate repos.16:56
*** galstrom has joined #openstack-meeting-416:56
odyssey4meit may not technically be galaxy compatible to start with, but to evolve the roles to a place where the logic in them is compatible is quite a big first step16:56
hughsaundersif we move to primarily using role dependancies rather than playbooks to tie everything together, then we may end up with quite a lot of roles16:56
cloudnulli estimate that we'll have 16+ odd roles.16:57
cloudnulland thats with removal of all of the *_common roles and such16:57
odyssey4meif that is the case, having them all as seperate repo's makes packaging/testing/branching/tagging a nightmare16:57
odyssey4mewe really need to limit the number of sub-repo's as far as is practical16:58
d34dh0r53just throwing this out there but in the interest of time it seems like the rpc* cleanup is a rather quick easy win which we could do decoupled from the galixyifying of everything, that may quell some of the request in the short term while we work on the other16:58
matttd34dh0r53: kind of agree w/ you there16:59
cloudnullwe're out of time people. well have to continue this in the channel and into our next meeting16:59
hughsaunderssed16:59
odyssey4med34dh0r53 agreed - I do think it'll be easier to de-rax in the current structure/method as we already know it16:59
matttalright, thanks cloudnull16:59
d34dh0r53ty cloudnull16:59
hughsaundersyep well chaired cloudnull :)16:59
odyssey4mety cloudnull16:59
cloudnullok , thanks guys.17:00
mancdaz\o/17:00
b3rnard0thank you dearest ptl17:00
sigmavirus24dont' forget to #endmeeting ;)17:00
cloudnull#endmeeting17:00
openstackMeeting ended Thu Jan 15 17:00:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible/2015/openstack_ansible.2015-01-15-15.57.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible/2015/openstack_ansible.2015-01-15-15.57.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible/2015/openstack_ansible.2015-01-15-15.57.log.html17:00
*** dboik has joined #openstack-meeting-417:00
*** git-harry has left #openstack-meeting-417:00
*** mwang2_ has joined #openstack-meeting-417:01
*** odyssey4me has left #openstack-meeting-417:01
*** alextricity has quit IRC17:01
*** gmatefi has joined #openstack-meeting-417:02
*** andymccr has left #openstack-meeting-417:03
*** mwang2 has quit IRC17:04
*** Sam-I-Am has left #openstack-meeting-417:04
b3rnard0mattt: yes sir. we'll be using more of the meetbot features next time too17:07
*** dboik has quit IRC17:07
*** alextricity has joined #openstack-meeting-417:07
*** dboik has joined #openstack-meeting-417:07
*** alextricity has left #openstack-meeting-417:08
*** dboik has quit IRC17:11
*** emagana has joined #openstack-meeting-417:13
*** galstrom has left #openstack-meeting-417:21
*** dboik has joined #openstack-meeting-417:24
*** gmatefi has quit IRC17:27
*** carl_baldwin has quit IRC17:31
*** ivasilevskaya has left #openstack-meeting-417:38
*** matrohon has quit IRC17:42
*** cloudnull has left #openstack-meeting-417:54
*** mwang2__ has joined #openstack-meeting-417:56
*** dboik has quit IRC17:56
*** SumitNaiksatam has joined #openstack-meeting-417:57
*** mwang2_ has quit IRC18:00
*** carl_baldwin has joined #openstack-meeting-418:03
*** s3wong has joined #openstack-meeting-418:04
*** dboik has joined #openstack-meeting-418:10
*** ChuckC_ is now known as ChuckC18:17
*** SridharRamaswamy has joined #openstack-meeting-418:19
*** krtaylor has quit IRC18:26
*** evgenyf has quit IRC18:26
*** emagana has quit IRC18:46
*** krtaylor has joined #openstack-meeting-418:52
*** carl_baldwin has quit IRC19:00
*** carl_baldwin has joined #openstack-meeting-419:03
*** evgenyf has joined #openstack-meeting-419:03
*** ivar-lazzaro has joined #openstack-meeting-419:04
*** emagana has joined #openstack-meeting-419:08
*** SumitNaiksatam has quit IRC19:13
*** SumitNaiksatam has joined #openstack-meeting-419:17
*** yamahata has joined #openstack-meeting-419:21
*** yamahata has quit IRC19:31
*** yamahata has joined #openstack-meeting-419:31
*** carl_baldwin has quit IRC19:45
*** [1]evgenyf has joined #openstack-meeting-419:46
*** evgenyf has quit IRC19:46
*** [1]evgenyf is now known as evgenyf19:46
*** carl_baldwin has joined #openstack-meeting-419:47
*** sarob has joined #openstack-meeting-419:49
*** david-lyle has joined #openstack-meeting-419:49
*** emagana has quit IRC19:51
*** emagana has joined #openstack-meeting-419:52
*** ivar-lazzaro has quit IRC19:52
*** ivar-lazzaro has joined #openstack-meeting-419:55
*** [1]evgenyf has joined #openstack-meeting-419:56
*** emagana has quit IRC19:56
*** emagana has joined #openstack-meeting-419:57
*** evgenyf has quit IRC19:58
*** [1]evgenyf is now known as evgenyf19:58
*** sarob has quit IRC20:01
*** banix has quit IRC20:08
*** mestery_ has joined #openstack-meeting-420:09
*** kobis has joined #openstack-meeting-420:09
*** mestery has quit IRC20:11
*** SumitNaiksatam has quit IRC20:12
*** david-lyle has quit IRC20:15
*** kobis has quit IRC20:15
*** evgenyf has quit IRC20:18
*** ChuckC has quit IRC20:19
*** ChuckC_ has joined #openstack-meeting-420:19
*** dboik has quit IRC20:20
*** banix has joined #openstack-meeting-420:25
*** s3wong has quit IRC20:28
*** s3wong has joined #openstack-meeting-420:32
*** VW_ has quit IRC20:34
*** VW_ has joined #openstack-meeting-420:35
*** s3wong has quit IRC20:42
*** s3wong has joined #openstack-meeting-420:42
*** ChuckC has joined #openstack-meeting-420:45
*** ChuckC_ has quit IRC20:46
*** mattt has left #openstack-meeting-420:51
*** ivar-lazzaro has quit IRC20:53
*** mestery_ is now known as mestery21:01
*** sarob has joined #openstack-meeting-421:03
*** dboik has joined #openstack-meeting-421:06
*** ChanServ sets mode: +o openstack21:11
*** evgenyf has joined #openstack-meeting-421:20
*** dboik has quit IRC21:27
*** dboik has joined #openstack-meeting-421:28
*** matrohon has joined #openstack-meeting-421:31
*** [1]evgenyf has joined #openstack-meeting-421:33
*** SridharRamaswamy has quit IRC21:35
*** ivar-lazzaro has joined #openstack-meeting-421:36
*** SridharRamaswamy has joined #openstack-meeting-421:36
*** evgenyf has quit IRC21:36
*** [1]evgenyf is now known as evgenyf21:36
*** carl_baldwin has quit IRC21:39
*** carl_baldwin has joined #openstack-meeting-421:41
*** banix has quit IRC21:42
*** dboik has quit IRC21:45
*** david-lyle has joined #openstack-meeting-421:46
*** SumitNaiksatam has joined #openstack-meeting-421:55
*** sarob has quit IRC22:05
*** dboik has joined #openstack-meeting-422:08
*** igordcard has joined #openstack-meeting-422:08
*** krtaylor has quit IRC22:11
*** carl_baldwin has quit IRC22:11
*** matrohon has quit IRC22:21
*** matrohon has joined #openstack-meeting-422:22
*** david-lyle has quit IRC22:27
*** SridharRamaswamy has quit IRC22:35
*** david-lyle has joined #openstack-meeting-422:37
*** openstack has joined #openstack-meeting-423:01
*** kragniz_ has joined #openstack-meeting-423:05
*** jemangs has joined #openstack-meeting-423:05
*** ekarlso has joined #openstack-meeting-423:05
*** csd has joined #openstack-meeting-423:05
*** crinkle_ has joined #openstack-meeting-423:05
*** nikhil_k_ has joined #openstack-meeting-423:05
*** david-lyle has joined #openstack-meeting-423:05
*** blogan has joined #openstack-meeting-423:05
*** salv-orlando has joined #openstack-meeting-423:05
*** jwang_ has joined #openstack-meeting-423:05
*** VW__ has joined #openstack-meeting-423:05
*** ptoohill has joined #openstack-meeting-423:05
*** dvorak has joined #openstack-meeting-423:05
*** kfjohnson_ has joined #openstack-meeting-423:05
*** ChuckC_ has joined #openstack-meeting-423:05
*** igordcard has joined #openstack-meeting-423:05
*** evgenyf has joined #openstack-meeting-423:05
*** mestery has joined #openstack-meeting-423:05
*** yamahata has joined #openstack-meeting-423:05
*** mwang2__ has joined #openstack-meeting-423:05
*** mancdaz has joined #openstack-meeting-423:05
*** b3rnard0 has joined #openstack-meeting-423:05
*** plaurin_ has joined #openstack-meeting-423:05
*** dhellmann has joined #openstack-meeting-423:05
*** jackmccann has joined #openstack-meeting-423:05
*** serverascode has joined #openstack-meeting-423:05
*** sballe_ has joined #openstack-meeting-423:05
*** jcook has joined #openstack-meeting-423:05
*** nikhil_k has joined #openstack-meeting-423:05
*** wznoinsk has joined #openstack-meeting-423:05
*** fungi has joined #openstack-meeting-423:05
*** sigmavirus24 has joined #openstack-meeting-423:05
*** ttx has joined #openstack-meeting-423:05
*** anteaya has joined #openstack-meeting-423:05
*** sweston has joined #openstack-meeting-423:05
*** miguelgrinberg_ has joined #openstack-meeting-423:06
*** miguelgrinberg_ is now known as miguelgrinberg23:06
*** dvorak has quit IRC23:07
*** sballe_ has quit IRC23:07
*** wznoinsk has quit IRC23:07
*** nikhil_k has quit IRC23:07
*** kragniz_ is now known as kragniz23:08
*** hughsaunders has joined #openstack-meeting-423:09
*** dboik has joined #openstack-meeting-423:10
*** wznoinsk has joined #openstack-meeting-423:12
*** SergeyLukjanov has joined #openstack-meeting-423:12
*** mfedosin has joined #openstack-meeting-423:12
*** emagana has joined #openstack-meeting-423:12
*** cgoncalv1s has joined #openstack-meeting-423:12
*** HenryG has joined #openstack-meeting-423:12
*** dvorak has joined #openstack-meeting-423:13
*** krtaylor has joined #openstack-meeting-423:13
*** SridharRamaswamy has joined #openstack-meeting-423:13
*** sballe__ has joined #openstack-meeting-423:13
*** palendae has joined #openstack-meeting-423:13
*** sbalukoff has joined #openstack-meeting-423:13
*** ivar-lazzaro has joined #openstack-meeting-423:14
*** dougwig has joined #openstack-meeting-423:23
*** david-lyle has quit IRC23:24
*** VW__ has quit IRC23:26
*** VW__ has joined #openstack-meeting-423:26
*** dboik has quit IRC23:29
*** dboik has joined #openstack-meeting-423:29
*** wznoinsk has quit IRC23:30
*** wznoinsk has joined #openstack-meeting-423:30
*** sballe__ has quit IRC23:31
*** sballe__ has joined #openstack-meeting-423:31
*** ivar-lazzaro has quit IRC23:31
*** ivar-lazzaro has joined #openstack-meeting-423:31
*** watanabe_isao has joined #openstack-meeting-423:31
*** dougwig has quit IRC23:31
*** dougwig has joined #openstack-meeting-423:31
*** SumitNaiksatam has joined #openstack-meeting-423:32
*** sigmavirus24 is now known as sigmavirus24_awa23:41
*** markmcclain has joined #openstack-meeting-423:47
*** crinkle_ is now known as crinkle23:51
*** carl_baldwin has joined #openstack-meeting-423:54

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