Tuesday, 2019-02-12

*** wuchunyang has joined #openstack-meeting-400:02
*** wuchunyang has quit IRC00:06
*** lemko has quit IRC00:20
*** TxGirlGeek has quit IRC00:25
*** macza has joined #openstack-meeting-400:29
*** macza has quit IRC00:34
*** iyamahat has joined #openstack-meeting-400:42
*** yamamoto has joined #openstack-meeting-400:51
*** yamamoto has quit IRC00:56
*** zeestrat has joined #openstack-meeting-400:59
*** mnasiadka has joined #openstack-meeting-400:59
*** sweston has joined #openstack-meeting-400:59
*** icey has joined #openstack-meeting-400:59
*** mrhillsman has joined #openstack-meeting-400:59
*** jayahn has joined #openstack-meeting-400:59
*** coreycb has joined #openstack-meeting-400:59
*** sdake has joined #openstack-meeting-401:01
*** macza has joined #openstack-meeting-401:08
*** macza has quit IRC01:13
*** markvoelker has quit IRC01:30
*** markvoelker has joined #openstack-meeting-401:31
*** markvoelker has quit IRC01:35
*** sdake has quit IRC01:37
*** sdake has joined #openstack-meeting-401:41
*** sdake has quit IRC01:43
*** yamamoto has joined #openstack-meeting-401:53
*** TxGirlGeek has joined #openstack-meeting-402:05
*** macza has joined #openstack-meeting-402:22
*** macza has quit IRC02:27
*** macza has joined #openstack-meeting-402:27
*** hongbin has joined #openstack-meeting-402:29
*** macza has quit IRC02:31
*** markvoelker has joined #openstack-meeting-402:31
*** iyamahat has quit IRC02:35
*** TxGirlGeek has quit IRC02:36
*** yamamoto has quit IRC02:48
*** wuchunyang has joined #openstack-meeting-402:52
*** wuchunyang has joined #openstack-meeting-402:52
*** markvoelker has quit IRC03:05
*** yamamoto has joined #openstack-meeting-403:14
*** sdake has joined #openstack-meeting-403:40
*** wuchunyang has quit IRC03:51
*** wuchunyang has joined #openstack-meeting-403:56
*** TxGirlGeek has joined #openstack-meeting-403:57
*** dave-mccowan has quit IRC03:58
*** sdake has quit IRC03:59
*** wuchunyang has quit IRC04:00
*** wuchunyang has joined #openstack-meeting-404:02
*** markvoelker has joined #openstack-meeting-404:02
*** wuchunyang has quit IRC04:06
*** diablo_rojo has quit IRC04:09
*** janki has joined #openstack-meeting-404:30
*** markvoelker has quit IRC04:34
*** hongbin has quit IRC05:30
*** markvoelker has joined #openstack-meeting-405:32
*** TxGirlGeek has quit IRC05:56
*** markvoelker has quit IRC06:05
*** gcheresh has joined #openstack-meeting-406:17
*** e0ne has joined #openstack-meeting-406:24
*** lemko has joined #openstack-meeting-406:30
*** e0ne has quit IRC06:35
*** Luzi has joined #openstack-meeting-406:53
*** ralonsoh has joined #openstack-meeting-406:59
*** markvoelker has joined #openstack-meeting-407:02
*** e0ne has joined #openstack-meeting-407:12
*** e0ne has quit IRC07:16
*** snapiri has joined #openstack-meeting-407:24
*** e0ne has joined #openstack-meeting-407:24
*** e0ne has quit IRC07:32
*** markvoelker has quit IRC07:35
*** e0ne has joined #openstack-meeting-407:42
*** slaweq has joined #openstack-meeting-407:44
*** gkadam has joined #openstack-meeting-408:08
*** gkadam_ has joined #openstack-meeting-408:15
*** gkadam has quit IRC08:17
*** k_mouza has joined #openstack-meeting-408:20
*** k_mouza has quit IRC08:28
*** markvoelker has joined #openstack-meeting-408:32
*** e0ne has quit IRC08:35
*** e0ne has joined #openstack-meeting-408:37
*** e0ne has quit IRC08:38
*** yboaron_ has joined #openstack-meeting-408:44
*** e0ne has joined #openstack-meeting-408:46
*** e0ne has quit IRC08:48
*** e0ne has joined #openstack-meeting-408:54
*** iyamahat has joined #openstack-meeting-408:54
*** e0ne has quit IRC08:56
*** wuchunyang has joined #openstack-meeting-409:04
*** markvoelker has quit IRC09:05
*** roman_g has joined #openstack-meeting-409:07
*** iyamahat has quit IRC09:19
*** e0ne has joined #openstack-meeting-409:25
*** e0ne has quit IRC09:26
*** yboaron_ has quit IRC09:26
*** yboaron_ has joined #openstack-meeting-409:27
*** k_mouza has joined #openstack-meeting-409:31
*** stephenfin_ is now known as stephenfin10:01
*** markvoelker has joined #openstack-meeting-410:02
*** k_mouza has quit IRC10:29
*** wuchunyang has quit IRC10:30
*** markvoelker has quit IRC10:35
*** salmankhan has joined #openstack-meeting-410:41
*** k_mouza has joined #openstack-meeting-410:49
*** salmankhan1 has joined #openstack-meeting-411:08
*** salmankhan has quit IRC11:09
*** salmankhan1 is now known as salmankhan11:09
*** lpetrut has joined #openstack-meeting-411:15
*** markvoelker has joined #openstack-meeting-411:32
*** k_mouza has quit IRC11:51
*** k_mouza has joined #openstack-meeting-411:52
*** markvoelker has quit IRC12:05
*** seajay has joined #openstack-meeting-412:10
*** k_mouza has quit IRC12:18
*** wuchunyang has joined #openstack-meeting-412:22
*** k_mouza has joined #openstack-meeting-412:25
*** coreycb has quit IRC12:36
*** coreycb has joined #openstack-meeting-412:37
*** lpetrut has quit IRC12:38
*** lpetrut has joined #openstack-meeting-412:39
*** janki has quit IRC12:44
*** janki has joined #openstack-meeting-412:44
*** wuchunyang has quit IRC12:53
*** markvoelker has joined #openstack-meeting-413:02
*** yamamoto has quit IRC13:03
*** k_mouza has quit IRC13:08
*** yamamoto has joined #openstack-meeting-413:08
*** yamamoto has quit IRC13:15
*** wuchunyang has joined #openstack-meeting-413:17
*** k_mouza has joined #openstack-meeting-413:17
*** wuchunyang has quit IRC13:17
*** wuchunyang has joined #openstack-meeting-413:18
*** wuchunyang has quit IRC13:21
*** Liang__ has joined #openstack-meeting-413:21
*** k_mouza has quit IRC13:30
*** k_mouza has joined #openstack-meeting-413:31
*** sdake has joined #openstack-meeting-413:32
*** markvoelker has quit IRC13:35
*** yamamoto has joined #openstack-meeting-413:46
*** yamamoto has quit IRC13:56
*** e0ne has joined #openstack-meeting-413:56
*** k_mouza_ has joined #openstack-meeting-414:02
*** sdake has quit IRC14:03
*** dave-mccowan has joined #openstack-meeting-414:04
*** nooryameen has joined #openstack-meeting-414:04
*** yamamoto has joined #openstack-meeting-414:06
*** k_mouza has quit IRC14:06
*** yamamoto has quit IRC14:06
*** k_mouza_ has quit IRC14:06
*** k_mouza has joined #openstack-meeting-414:06
*** dave-mccowan has quit IRC14:09
*** liuyulong has joined #openstack-meeting-414:15
*** howell_ has joined #openstack-meeting-414:16
*** howell_ has quit IRC14:17
*** premsankar has joined #openstack-meeting-414:18
*** Liang__ has quit IRC14:19
*** ktibi has joined #openstack-meeting-414:21
*** howell_ has joined #openstack-meeting-414:22
*** k_mouza has quit IRC14:24
*** sgrasley has joined #openstack-meeting-414:31
*** sgrasley_ has joined #openstack-meeting-414:31
*** markvoelker has joined #openstack-meeting-414:32
*** k_mouza has joined #openstack-meeting-414:33
*** sdake has joined #openstack-meeting-414:35
*** sdake has quit IRC14:37
*** sdake_ has joined #openstack-meeting-414:37
*** wuchunyang has joined #openstack-meeting-414:43
*** e0ne has quit IRC14:44
*** janki has quit IRC14:47
*** hongbin has joined #openstack-meeting-414:49
*** gkadam_ has quit IRC14:54
*** gkadam has joined #openstack-meeting-414:54
*** dustinspecker has joined #openstack-meeting-414:54
*** rha has joined #openstack-meeting-414:55
*** georgk has joined #openstack-meeting-414:55
*** witek has joined #openstack-meeting-414:56
*** snapiri has quit IRC14:56
portdirecto/15:01
portdirect#startmeeting openstack-helm15:01
openstackMeeting started Tue Feb 12 15:01:11 2019 UTC and is due to finish in 60 minutes.  The chair is portdirect. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: openstack-helm)"15:01
openstackThe meeting name has been set to 'openstack_helm'15:01
georgkhi15:01
mattmceueno/15:01
howell_o/15:01
srwilkerso/15:01
portdirectlets give it 5 mins for people to arrive - the agenda is here: https://etherpad.openstack.org/p/openstack-helm-meeting-2019-02-1215:01
roman_go/15:01
portdirectplease add to it liberally15:02
evrardjpo/15:04
*** howell_ is now known as howell15:04
*** wuchunyang has quit IRC15:05
*** jsuchome has joined #openstack-meeting-415:05
portdirectok - lets go!15:05
evrardjpwow I see one of our repos inside that list, not sure if it's ready for primetime yet :p15:05
portdirect#topic other projects making use of openstack helm15:05
*** openstack changes topic to "other projects making use of openstack helm (Meeting topic: openstack-helm)"15:05
*** markvoelker has quit IRC15:05
srwilkersevrardjp: :)15:05
portdirectits really awesome to see many projects either using openstack helm, or deploying the openstack helm charts15:05
portdirecttheres been much discussion and interaction from the airship team here over the last few months15:06
portdirectas airship was essentially born out of a need to manage helm packaged infrastructure15:06
portdirectand we've had some great sessions with the starling-x team - as they start to use osh to deploy and manage openstack (using armada from airship)15:08
*** arunkant has joined #openstack-meeting-415:08
portdirectand suse has also started an effort around deploying and managing osh15:09
portdirectI wonder how we could do a better job of supporting these projects?15:09
*** e0ne has joined #openstack-meeting-415:09
evrardjpmore presence on irc channels/ML would help15:09
*** hongbin has quit IRC15:09
portdirectI know both starlingx and suse would like to use image distos that are not ubuntu/debian based15:09
portdirectand there have been some efforts to get that going, but have essentially stalled15:10
evrardjpIt's not only you, portdirect, and srwilkers that can answer my noob questions -- we should scale the community15:10
evrardjpportdirect: I cam report on that staling15:10
evrardjpcan*15:10
evrardjpBasically we got results today!15:11
evrardjpWe can now finally deploy OSH with our current code.15:11
portdirectthe other thing that would be great is if we manage to get some of the work done in these projects upstreamed as fast as possible15:11
mattmceuennice!15:11
portdirectevrardjp: the floor is yours15:11
evrardjpSo now that the current code is "working",we'll be focusing on a last series of cleanups, and improving the CI, while the team will start building those images internally15:12
*** hongbin has joined #openstack-meeting-415:12
evrardjpassuming the images pass local testing, we'll be providing them upstream.15:12
evrardjp(no need to worry you with broken images)15:12
evrardjpwith that in mind, some of the people in our team will focus on OSH-images publishing too15:13
evrardjpso that docker hub will contain opensuse images15:13
evrardjpIt just takes time to put everything together :)15:13
evrardjpanyway, long story short, we'll be helping you there.15:13
evrardjpSadly -- there are hiccups15:13
portdirectawesome - i understand that sometimes a downstream approach is preferable for an org.15:14
srwilkersnice - thanks for the update evrardjp.  nice to know it's coming15:14
portdirectis there anything we can do in the meantime to reduce the deltas you need to do?15:14
evrardjpWe'll be working upstream first -- but we need to work in a dev environment :p15:14
mattmceuenyes, very exciting15:14
evrardjpSo yes, when we'll start working on openSUSE images, you'll see a few questions popup15:15
portdirectsweet15:15
evrardjpbecause openSUSE will be different than ubuntu images15:15
evrardjpI think it would be great to come with a common understanding on how we'll do multi distros15:15
evrardjp(or multi images, I don't really care the name we gave :p )15:15
portdirecti agree15:15
evrardjpAnd to be honest, we might have ideas, but you also have yours.15:15
portdirectit would be great to start a spec ther15:15
*** yamamoto has joined #openstack-meeting-415:16
evrardjpI think it would be great to sync first, and end up all together in that spec15:16
evrardjpusing your expertise would help us tremendously15:16
portdirectok - I'll make sure its a topic on next weeks adjenda15:16
portdirectother than images - are there any other ways we can assist?15:16
portdirecteg I've taken starlingx for a spin, is suse's project ready to kick the tyres on?15:16
evrardjpnot yet for now. We have to finish up the last bits :)15:17
evrardjpbut very close15:17
portdirectnice - I'd love to get running with it and provide some feedback15:17
portdirectits really great to see orgs using osh in so many different ways15:17
portdirectits more than we could have hoped for when we started this project :D15:18
portdirectI'll also reach out to the starlingx folks and see if i can get them to come along15:18
portdirectthey have some really nice patches for ceilometer etc, that i would love to see a ps for.15:19
evrardjpIn the long run, you'll probably see more involvement from SUSE,with new charts for projects that aren't deployed yet.15:19
evrardjpdeployed yet in OSH*15:19
portdirectis there a roadmap here at all? so we can co-ordinate these efforts? or to early to make public?15:20
portdirect(sorry to push you, I'm just excited)15:20
*** nishant_ has joined #openstack-meeting-415:20
evrardjpIt's too early and very internal. I can just give you where we want to go, and give you feedback update of our time upstream :p15:20
portdirectnp - i understand - cheers evrardjp15:21
evrardjpFor us having OSH very stable and very updated is important15:21
evrardjpdeploying OSH newton is not important for us :p15:21
evrardjpI guess you can read the rest between the lines.15:21
portdirectevrardjp: what version would you like? If its not communicated its hard to read minds :)15:22
evrardjpCurrently the helm charts are ocata, and we'd like to bump to at least Rocky.15:22
evrardjpthere was a community member yesterday that was interested by Queens. I think that's worth pursuing too.15:22
portdirectnice - they should work with that pretty much - I'll get rocky support done this week15:23
evrardjpI mean ... as a stop gap to Rocky15:23
evrardjpgreat!15:23
evrardjpthanks a lot there!15:23
portdirectnp dude15:23
*** TxGirlGeek has joined #openstack-meeting-415:23
portdirectat the other end of the colab spectrum i think srwilkers has been working on Monasca?15:24
srwilkersyeah - been working with it off and on since the PTG, but intermittent is the best way to put it.  as other things have been pulling me away15:24
evrardjpwitek: ^15:24
witekhi guys15:25
srwilkershey witek15:25
evrardjpsrwilkers: could you tell us more about your plan there?15:25
evrardjp(and the priorities for it, so we know the expectations...)15:25
*** yamamoto has quit IRC15:25
srwilkerssure.  the plan's pretty simple - i'd like to see what it'd take to get monasca to a point that can work with the current openstack-helm charts15:26
*** liuyulong has quit IRC15:26
evrardjpIs there a way I/we can help you?15:27
srwilkersas far as expectations, i'd defer to witek -- once i've finalized what it takes to get monasca to run with openstack-helm, what's the best way to move forward there?  is the plan that the monasca chart would continue to live in monasca-helm, or would you guys like to contribute it into openstack-helm?15:27
witekit would prefer to contribute it to OSH15:28
srwilkersawesome witek15:28
evrardjp:)15:29
witekis there still a lot missing to work with OSH?15:29
portdirectwhat is the current governance round monasca? I know it was in openstack for a bit, has it spun out like gnocchi?15:29
evrardjpthat was the right answer for this meeting... (god that would have been awkwaaaaard!)15:29
evrardjpit's in governance :)15:30
evrardjphttps://github.com/openstack/governance/blob/master/reference/projects.yaml#L175315:30
witekyes, monasca-docker and monasca-helm were started outside but they use the code from OpenStack repos15:30
srwilkerswitek: i wouldn't say there's a lot missing, it's more just updating the chart to include things that align it with the patterns used in our other charts.  things like keystone user jobs, jobs for database management, etc15:30
portdirectgotcha - thanks evrardjp and witek15:31
evrardjpportdirect: to me monasca-docker and monasca-helm don't exist there ! :p15:31
srwilkersas the monasca chart seems more like a macro chart, as opposed to a chart-per-service approach that openstack-helm takes15:31
evrardjpsrwilkers: would that be a problem?15:32
srwilkersie: the monasca chart has templates for a keystone deployment,  grafana, etc15:32
portdirectyeah we would want to dis-agregate that15:32
portdirectevrardjp: umbrella charts are awesome for day one - a nightmare every day after15:32
srwilkersportdirect: ++15:33
evrardjpI would have guessed too15:33
evrardjplet me rephrase my question15:33
*** e0ne has quit IRC15:33
evrardjpwould that be a no-go for starting to work together on upstreaming the monasca chart into OSH15:33
portdirectquite the opposite - i think it would be the place to start15:34
*** jamesgu has joined #openstack-meeting-415:34
portdirectsrwilkers/witek ?15:34
witek do you have some intermediate work, where we could help with15:34
srwilkersportdirect: agreed - would be the place to start, instead of cleaning it up externally before bringing it in15:34
portdirectwitek: are the current helm charts in openstack? I see them in github, is that under openstack governance?15:35
portdirectsorry to be so pernikity here - just dictates wheter we should go there and start work, or pull in as a ps in openstack-helm-addons15:36
witekportdirect: no, they are in monasca/monasca-helm repo15:36
portdirect*persnickety15:36
portdirectroger - who controls that? HP?15:36
evrardjpI think it's better to focus on the future than on the present of those charts15:37
witekno, I'm one of the project owners, but I would prefer to contribute the work to OSH15:37
witekHPE has started the effort15:37
portdirectawesome - if you made a ps to osh-addons we could start work there?15:37
srwilkersi think that'd be the best way to do it15:38
evrardjpportdirect: why not OSH, as this is a openstack project?15:38
evrardjp(while the kafka and other parts can be in addons or infra)15:38
portdirectthat would work too provided it used the openstack hosted parts15:38
srwilkersi think it would make sense to first pull in the macro chart to openstack-helm-addons, and once it's been updated to match our current patterns, we could then move the separate parts to the appropriate places15:40
evrardjpthanks for the clarification srwilkers and portdirect15:41
srwilkersas you mentioned evrardjp: kafka, zookeeper, etc in infra, monasca in osh, etc15:41
*** liuyulong has joined #openstack-meeting-415:41
witekshould I take the code as it is?15:41
evrardjpas long as there is a path towards being in governance, I feel better about it15:41
evrardjpwitek: can you? (licensing)15:41
*** Luzi has quit IRC15:41
witekapache215:41
*** e0ne has joined #openstack-meeting-415:41
evrardjpgood news :)15:41
*** macza has joined #openstack-meeting-415:42
portdirectwitek: where you involved in th development of those charts in their current home?15:42
witekno15:42
witekit was HPE work15:43
portdirectok - so we may need to sort out some issue here: https://wiki.openstack.org/wiki/OpenStackAndItsCLA#The_Developer_Certificate_of_Origin15:43
portdirectbut should be relativity simple15:43
portdirecti think point c should make this ok, provide one of the authors signs off on it15:44
witekas far as I understand, it confirms the origin of the commit, has nothing to do with the license15:44
portdirectah ok15:45
portdirectnice15:45
portdirectlook forward to seeing monasca in osh, it was really nice when i last played with it!15:46
witeknice to hear, OK, I'll push the code then to osh-addons15:46
portdirect++15:46
witek#action witek push monasca-helm code to openstack-helm-addons15:47
portdirectok to move on?15:47
*** diablo_rojo has joined #openstack-meeting-415:47
witekyes, thanks15:47
portdirect#topic new jobs in openstack-helm and openstack-helm-infra15:47
*** openstack changes topic to "new jobs in openstack-helm and openstack-helm-infra (Meeting topic: openstack-helm)"15:47
portdirectsrwilkers: floors yours15:47
evrardjpportdirect: witek is right there15:47
srwilkersso we've got some new jobs in openstack-helm and openstack-helm-infra15:48
srwilkerswe've now got periodic/experimental multinode jobs for:15:48
srwilkers1. deploying software via armada, then updating said software by updating the release-uuid annotation on the pods via a values change15:49
srwilkers2. deploying software via armada, then generating new passphrases for said software, and updating it via armada15:49
*** gcheresh has quit IRC15:50
srwilkersthe idea being, we could use these jobs as smoke tests for verifying we could essentially do an update of charts via updating the release-uuid annotation as well as verifying the charts support some manner of updating credentials for the services15:50
portdirectnice - how do the outcomes of those tests look atm?15:51
evrardjpthat is a nice idea.15:51
srwilkersthese jobs need a little more work (ideally something basic that exercises the services after the update), but i'm hoping this helps some of the outliers fall out so we can identify them15:51
portdirectyeah - id really like to see this end up in our periodic15:51
mattmceuenboth of those are excellent tests srwilkers - thanks man15:51
srwilkersportdirect: they look good right now -- the chart that stands out to me currently is mariadb, as we need to support updating the root password15:52
evrardjpsrwilkers: maybe a dumb question, but can't you just deploy, let's say keystone, twice for the same results (with different values overrides)15:52
srwilkersgrafana was another outlier, which resulted in: https://review.openstack.org/#/c/634521/15:52
portdirectok I can hit that this week, as we also need to fix the xtradb config15:52
srwilkersevrardjp: sure, you could.  this stood out as a sane approach though, as i think just triggering updates to everything with something like armada makes more sense15:53
srwilkersthat could just be me15:53
srwilkersanother reason i used armada is that the old armada-deploy job already generated passphrase overrides for each service.  it was fairly simple to just extend that15:54
*** k_mouza has quit IRC15:54
evrardjp:)15:54
evrardjpThanks for the clarification.15:54
portdirectthe other thing we get from this approach is an understanding of how services react when their supporting services admin credential change15:55
mattmceuenAs a heads-up srwilkers -- I'd heard that the release-uuid doesn't kick the ceph pods because the pod spec is left unchanged by it.  So I'd be interested in looking over your shoulder on that and confirming whether/which pods actually do cycle from the whole set15:56
portdirectyup - this is one of the things i expect to fall out of this15:56
srwilkersyup15:56
portdirectwhere we need to apply the annotation at the pod level, rather than just the controller15:56
srwilkers++15:57
portdirecti still vote for us getting a `./smash.sh` script :D15:57
srwilkersi mean15:57
portdirectthat simply deletes all pods in the cluster, and we can watch the fun unfold15:57
*** roman_g has quit IRC15:57
srwilkersjust use chaoskube or something -- i've got another, unrelated job that uses it15:57
portdirectits depressing how many times ive done this in a real world senario to 'shake-down' the world15:58
srwilkersjust let it go nuts on a deployment and see what falls apart15:58
srwilkersosh-donkey-kong15:58
portdirect:)15:58
*** roman_g has joined #openstack-meeting-415:59
portdirectok 1 min left15:59
portdirect#topic reviews15:59
*** openstack changes topic to "reviews (Meeting topic: openstack-helm)"15:59
portdirectwe have several patches that could benefit from some extra eyes15:59
portdirecthttps://www.irccloud.com/pastebin/oiO6PaPZ/15:59
portdirectplease lets hit them16:00
portdirectsorry to have run out of time, lets move over to #openstack-helm16:00
portdirectthanks everyone16:00
portdirect#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Tue Feb 12 16:00:23 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-02-12-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-02-12-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_helm/2019/openstack_helm.2019-02-12-15.01.log.html16:00
*** mjturek has joined #openstack-meeting-416:00
*** k_mouza has joined #openstack-meeting-416:01
*** markvoelker has joined #openstack-meeting-416:03
*** dustinspecker has left #openstack-meeting-416:03
*** lpetrut has quit IRC16:03
*** yboaron_ has quit IRC16:04
*** gkadam has quit IRC16:09
*** ktibi has quit IRC16:11
*** ktibi has joined #openstack-meeting-416:11
*** gkadam has joined #openstack-meeting-416:14
*** k_mouza has quit IRC16:16
*** k_mouza has joined #openstack-meeting-416:30
*** georgk has quit IRC16:32
*** markvoelker has quit IRC16:35
*** howell has quit IRC16:36
*** howell_ has joined #openstack-meeting-416:37
*** TxGirlGeek has quit IRC16:57
*** hongbin has quit IRC16:59
*** sdake_ has quit IRC17:01
*** sdake has joined #openstack-meeting-417:02
*** hamzy has quit IRC17:06
*** howell_ has quit IRC17:08
*** liuyulong has quit IRC17:09
*** howell_ has joined #openstack-meeting-417:10
*** howell_ has quit IRC17:18
*** gkadam has quit IRC17:19
*** howell_ has joined #openstack-meeting-417:21
*** howell_ has quit IRC17:21
*** howell has joined #openstack-meeting-417:21
*** e0ne has quit IRC17:27
*** markvoelker has joined #openstack-meeting-417:32
*** k_mouza has quit IRC17:35
*** spsurya has quit IRC17:40
*** e0ne has joined #openstack-meeting-417:43
*** yamamoto has joined #openstack-meeting-417:44
*** sdake has quit IRC17:44
*** sdake has joined #openstack-meeting-417:46
*** yamamoto has quit IRC17:48
*** k_mouza has joined #openstack-meeting-417:57
*** k_mouza has quit IRC18:01
*** salmankhan has quit IRC18:03
*** markvoelker has quit IRC18:06
*** yamamoto has joined #openstack-meeting-418:11
*** ktibi has quit IRC18:29
*** ralonsoh has quit IRC18:37
*** hamzy has joined #openstack-meeting-418:43
*** sdake has quit IRC18:44
*** georgk has joined #openstack-meeting-418:45
*** georgk has quit IRC18:50
*** georgk has joined #openstack-meeting-418:50
*** sdake has joined #openstack-meeting-418:51
*** slaweq has quit IRC18:59
*** markvoelker has joined #openstack-meeting-419:03
*** lemko_ has joined #openstack-meeting-419:03
*** Dantalion has quit IRC19:04
*** lemko has quit IRC19:04
*** stephenfin has quit IRC19:04
*** jroll has quit IRC19:04
*** mugsie has quit IRC19:04
*** yamahata__ has quit IRC19:04
*** tinwood has quit IRC19:04
*** lemko_ is now known as lemko19:04
*** tinwood has joined #openstack-meeting-419:04
*** yamahata__ has joined #openstack-meeting-419:05
*** mugsie has joined #openstack-meeting-419:05
*** stephenfin has joined #openstack-meeting-419:06
*** jroll has joined #openstack-meeting-419:07
*** lemko has quit IRC19:09
*** kgz has quit IRC19:10
*** kgz has joined #openstack-meeting-419:17
*** georgk has quit IRC19:21
*** k_mouza has joined #openstack-meeting-419:34
*** markvoelker has quit IRC19:36
*** k_mouza has quit IRC19:38
*** sdake has quit IRC19:42
*** slaweq has joined #openstack-meeting-420:19
*** e0ne has quit IRC20:25
*** markvoelker has joined #openstack-meeting-420:33
*** mjturek has quit IRC20:47
*** e0ne has joined #openstack-meeting-420:48
*** slaweq_ has joined #openstack-meeting-421:03
*** slaweq has quit IRC21:06
*** tinwood has quit IRC21:06
*** mugsie has quit IRC21:06
*** markvoelker has quit IRC21:06
*** mugsie has joined #openstack-meeting-421:06
*** tinwood has joined #openstack-meeting-421:06
*** mjturek has joined #openstack-meeting-421:08
*** sdake has joined #openstack-meeting-421:26
*** e0ne has quit IRC21:28
*** slaweq_ is now known as slaweq21:32
*** jsuchome has quit IRC21:33
*** roman_g has quit IRC21:40
*** howell has quit IRC21:41
*** howell has joined #openstack-meeting-421:45
*** hamzy has quit IRC21:46
*** howell_ has joined #openstack-meeting-421:48
*** howell_ has quit IRC21:48
*** mjturek has quit IRC21:48
*** howell_ has joined #openstack-meeting-421:48
*** sdake has quit IRC21:50
*** howell has quit IRC21:51
*** howell_ is now known as howell21:51
*** nishant_ has quit IRC21:52
*** howell has quit IRC22:00
*** markvoelker has joined #openstack-meeting-422:03
*** howell has joined #openstack-meeting-422:07
*** howell has quit IRC22:16
*** howell has joined #openstack-meeting-422:16
*** witek has quit IRC22:25
*** howell has quit IRC22:31
*** slaweq has quit IRC22:34
*** lathiat has quit IRC22:34
*** markvoelker has quit IRC22:36
*** seajay has quit IRC23:04
*** markvoelker has joined #openstack-meeting-423:33
*** k_mouza has joined #openstack-meeting-423:34
*** k_mouza has quit IRC23:39
*** macza has quit IRC23:42
*** macza has joined #openstack-meeting-423:42
*** sdake has joined #openstack-meeting-423:43
*** premsankar has quit IRC23:48

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