Wednesday, 2015-04-01

*** flaper87 has quit IRC00:11
*** flaper87 has joined #openstack-meeting-400:15
*** ibiris_away is now known as ibiris00:16
*** salv-orlando has quit IRC00:18
*** SumitNaiksatam has quit IRC00:19
*** emagana has quit IRC00:19
*** ibiris is now known as ibiris_away00:25
*** xingchao_ has joined #openstack-meeting-400:30
*** Swami has quit IRC00:33
*** SumitNaiksatam has joined #openstack-meeting-400:55
*** shwetaap has quit IRC01:11
*** ChuckC has quit IRC01:16
*** banix has quit IRC01:16
*** shwetaap has joined #openstack-meeting-401:22
*** xingchao_ has quit IRC01:27
*** banix has joined #openstack-meeting-401:35
*** salv-orlando has joined #openstack-meeting-401:44
*** ChuckC has joined #openstack-meeting-401:47
*** ChuckC has quit IRC01:51
*** ChuckC has joined #openstack-meeting-401:52
*** ChuckC has quit IRC02:10
*** ChuckC has joined #openstack-meeting-402:10
*** rfolco has joined #openstack-meeting-402:15
*** yamahata has quit IRC02:15
*** xingchao_ has joined #openstack-meeting-402:28
*** bharath has joined #openstack-meeting-402:34
*** xingchao_ has quit IRC02:36
*** shwetaap1 has joined #openstack-meeting-402:36
*** bharath has quit IRC02:38
*** shwetaap has quit IRC02:40
*** eghobo has joined #openstack-meeting-402:43
*** dims_ has quit IRC02:55
*** eghobo has quit IRC02:58
*** salv-orlando has quit IRC02:59
*** david-lyle has joined #openstack-meeting-403:13
*** SumitNaiksatam has quit IRC03:13
*** SumitNaiksatam has joined #openstack-meeting-403:14
*** SumitNaiksatam has quit IRC03:24
*** SumitNaiksatam has joined #openstack-meeting-403:33
*** xingchao_ has joined #openstack-meeting-403:35
*** xingchao_ has quit IRC03:41
*** carl_baldwin has joined #openstack-meeting-403:52
*** galstrom_zzz is now known as galstrom03:53
*** rushiagr_away is now known as rushiagr03:54
*** salv-orlando has joined #openstack-meeting-403:58
*** galstrom is now known as galstrom_zzz04:03
*** emagana has joined #openstack-meeting-404:07
*** eghobo has joined #openstack-meeting-404:20
*** rushiagr is now known as rushiagr_away04:22
*** banix has quit IRC04:29
*** salv-orlando has quit IRC04:32
*** xingchao_ has joined #openstack-meeting-404:40
*** xingchao_ has quit IRC04:46
*** carl_baldwin has quit IRC04:47
*** garyk has quit IRC04:48
*** krtaylor has quit IRC04:48
*** krtaylor has joined #openstack-meeting-404:50
*** emagana has quit IRC05:04
*** emagana has joined #openstack-meeting-405:05
*** emagana has quit IRC05:10
*** rushiagr_away is now known as rushiagr05:14
*** rushiagr is now known as rushiagr_away05:23
*** shwetaap1 has quit IRC05:29
*** yamahata has joined #openstack-meeting-405:30
*** shwetaap has joined #openstack-meeting-405:30
*** garyk has joined #openstack-meeting-405:39
*** xingchao_ has joined #openstack-meeting-405:47
*** xingchao_ has quit IRC05:52
*** salv-orlando has joined #openstack-meeting-406:19
*** kobis has joined #openstack-meeting-406:28
*** eghobo has quit IRC06:42
*** flaper87 has quit IRC06:45
*** flaper87 has joined #openstack-meeting-406:45
*** xingchao_ has joined #openstack-meeting-406:50
*** salv-orlando has quit IRC06:54
*** xingchao_ has quit IRC06:57
*** markvoelker has quit IRC07:09
*** bharath has joined #openstack-meeting-407:22
*** vishwanathj has quit IRC07:24
*** rushiagr_away is now known as rushiagr07:30
*** matrohon has joined #openstack-meeting-407:34
*** wojdev has joined #openstack-meeting-407:36
*** rushiagr is now known as rushiagr_away07:37
*** wojdev has quit IRC07:48
*** dims_ has joined #openstack-meeting-407:50
*** dims_ has quit IRC07:55
*** xingchao has joined #openstack-meeting-407:57
*** xingchao has quit IRC08:02
*** yamahata has quit IRC08:02
*** salv-orlando has joined #openstack-meeting-408:03
*** bobmel has joined #openstack-meeting-408:06
*** ibiris_away is now known as ibiris08:14
*** ibiris is now known as ibiris_away08:29
*** garyk1 has joined #openstack-meeting-408:40
*** garyk has quit IRC08:41
*** garyk1 has quit IRC08:44
*** ibiris_away is now known as ibiris08:44
*** garyk has joined #openstack-meeting-408:45
*** garyk has quit IRC08:45
*** garyk has joined #openstack-meeting-408:46
*** numan has joined #openstack-meeting-408:49
*** garyk has quit IRC08:50
*** kobis has left #openstack-meeting-408:59
*** xingchao_ has joined #openstack-meeting-409:00
*** rushiagr_away is now known as rushiagr09:01
*** shwetaap has quit IRC09:02
*** xingchao_ has quit IRC09:07
*** numan has quit IRC09:12
*** britthou_ has joined #openstack-meeting-409:16
*** britthouser has quit IRC09:17
*** sdake has joined #openstack-meeting-409:18
*** salv-orl_ has joined #openstack-meeting-409:19
*** sdake_ has quit IRC09:22
*** sdake has quit IRC09:22
*** salv-orlando has quit IRC09:22
*** wojdev has joined #openstack-meeting-409:28
*** amotoki has quit IRC09:31
*** bharath has quit IRC09:33
*** numan has joined #openstack-meeting-409:34
*** wojdev has quit IRC09:39
*** dims_ has joined #openstack-meeting-410:00
*** dims__ has joined #openstack-meeting-410:01
*** ibiris is now known as ibiris_away10:01
*** dims_ has quit IRC10:04
*** wojdev has joined #openstack-meeting-410:05
*** rushiagr is now known as rushiagr_away10:19
*** rushiagr_away is now known as rushiagr10:22
*** ibiris_away is now known as ibiris10:31
*** wojdev has quit IRC10:40
*** matrohon has quit IRC10:42
*** rushiagr is now known as rushiagr_away11:28
*** rushiagr_away is now known as rushiagr11:28
*** matrohon has joined #openstack-meeting-412:01
*** kobis has joined #openstack-meeting-412:06
*** wojdev has joined #openstack-meeting-412:11
*** xingchao_ has joined #openstack-meeting-412:13
*** markvoelker has joined #openstack-meeting-412:14
*** matrohon has quit IRC12:19
*** xingchao_ has quit IRC12:22
*** wojdev has quit IRC12:29
*** salv-orl_ has quit IRC12:32
*** bharath has joined #openstack-meeting-412:34
*** bharath has quit IRC12:38
*** shwetaap has joined #openstack-meeting-412:42
*** matrohon has joined #openstack-meeting-412:42
*** salv-orlando has joined #openstack-meeting-412:53
*** klamath has joined #openstack-meeting-413:01
*** klamath has quit IRC13:02
*** carl_baldwin has joined #openstack-meeting-413:02
*** klamath has joined #openstack-meeting-413:02
*** galstrom_zzz is now known as galstrom13:04
*** bknudson has quit IRC13:10
*** jckasper has joined #openstack-meeting-413:16
*** xingchao_ has joined #openstack-meeting-413:20
*** wojdev has joined #openstack-meeting-413:23
*** xingchao_ has quit IRC13:26
-openstackstatus- NOTICE: gerrit has been restarted to restore event streaming. any change events missed by zuul (between 12:48 and 13:28 utc) will need to be rechecked or have new approval votes set13:28
*** wojdev has quit IRC13:36
*** VW_ has joined #openstack-meeting-413:37
*** wojdev has joined #openstack-meeting-413:40
*** larsks has left #openstack-meeting-413:46
*** sigmavirus24_awa is now known as sigmavirus2413:48
*** matrohon has quit IRC13:49
*** wojdev has quit IRC13:50
*** sigmavirus24 is now known as sigmavirus24_awa13:55
*** ChuckC has quit IRC13:57
*** sigmavirus24_awa is now known as sigmavirus2414:04
*** galstrom is now known as galstrom_zzz14:11
*** rushiagr is now known as rushiagr_away14:14
*** sdake has joined #openstack-meeting-414:16
*** bobmel_ has joined #openstack-meeting-414:25
*** xingchao_ has joined #openstack-meeting-414:27
*** bobmel has quit IRC14:28
*** bknudson has joined #openstack-meeting-414:28
*** xingchao_ has quit IRC14:31
*** carl_baldwin has quit IRC14:33
*** patrickeast has joined #openstack-meeting-414:46
*** yamahata has joined #openstack-meeting-414:48
*** galstrom_zzz is now known as galstrom14:52
*** galstrom is now known as galstrom_zzz14:55
*** ctlaugh has joined #openstack-meeting-414:55
*** emagana has joined #openstack-meeting-414:58
*** daneyon_ has joined #openstack-meeting-414:59
*** numan has quit IRC14:59
krtaylor#startmeeting third-party15:01
openstackMeeting started Wed Apr  1 15:01:15 2015 UTC and is due to finish in 60 minutes.  The chair is krtaylor. 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: third-party)"15:01
openstackThe meeting name has been set to 'third_party'15:01
patrickeasthi15:01
krtaylorwho's here for third party ci working group meeting?15:01
krtaylorhi patrickeast15:01
* ctlaugh is here15:01
swestono/15:01
krtaylorhi sweston15:01
*** daneyon has quit IRC15:01
krtaylorhi ctlaugh15:01
zz_ja|arwe here15:02
krtaylorhi zz_ja|15:02
mmedvedehi15:02
krtaylorhey mmedvede15:02
*** carl_baldwin has joined #openstack-meeting-415:02
*** asselin has joined #openstack-meeting-415:02
krtaylorhow is everyone, hopefully there were not too many pranks played on you today15:02
ctlaughnot yet15:03
krtaylorhehheh15:03
krtaylorhere is the agenda15:03
krtaylor#link https://wiki.openstack.org/wiki/Meetings/ThirdParty#4.2F1.2F15_1500_UTC15:03
krtaylor#topic Topics for discussion at Liberty summit in Vancouver15:04
*** openstack changes topic to "Topics for discussion at Liberty summit in Vancouver (Meeting topic: third-party)"15:04
krtaylorI created an etherpad for everyone to put their topic ideas15:04
krtaylorif you put an idea there, please put your nick next to it15:05
krtaylorlike last time, we'll prioritize and select a few things to discuss15:05
zz_ja|krtaylor, what does this mean: With functional testing moving back to the projects, what does this mean for third party CI?15:05
krtaylor#action krtaylor will see about getting a design session for TPCIWG discussion15:05
zz_ja|might be that I've seen this using different keywords and just don't recognize it15:06
krtaylorzz_ja|, thats a question about what CI will be required to test since test suite is shrinking15:07
asselinhi15:07
krtaylorit may be nothing, just wanted to see if we need to work with the projects to figure that out15:07
krtaylorhi asselin15:07
zz_ja|you mean b/c "tempest" tests are moving to "nova-tempest" and such?15:07
krtaylorthat is certainly a lower priority  topic, not sure we need to discuss that at summit, but put it there to keep it15:08
zz_ja|I took those threads to mean just a change of repo, rather than what tests would have to run15:08
krtayloryes, functional tests are being removed back to the projects, not in tests run per patch, or required to test per patch anyway15:09
krtaylorit may be that we just run a weekly periodic, but may not even be required at all15:09
krtaylor#link https://etherpad.openstack.org/p/liberty-third-party-ci-working-group15:10
krtaylorfor completeness15:10
zz_ja|I guess I assumed that nova would say "every patch must run nova-tempest" and so on15:10
*** rushiagr_away is now known as rushiagr15:11
krtaylorI'm not sure we can assume that is a requirement15:11
krtayloranyway, we can discuss that with the projects, it may be discussed in a QA session, so we may not need to worry about it in a TPCIWG session15:12
krtaylorany questions about adding session topics to the etherpad?15:12
krtaylor#topic In-tree 3rd party ci solution (downstream-puppet)15:12
*** openstack changes topic to "In-tree 3rd party ci solution (downstream-puppet) (Meeting topic: third-party)"15:12
krtaylorlots of patches, this is moving nicely!15:13
krtaylor#link https://review.openstack.org/#/q/topic:downstream-puppet,n,z15:13
asselinyes, I'd like to get some reviews on the log server patches15:13
krtaylorsure asselin, link?15:13
asselinthere were quite a few ppl interested to participate in the effort: Please take a look as I'd like this to be the 'model' to help do the others15:14
asselin#link https://review.openstack.org/#/q/topic:downstream-puppet+owner:%22Ramy+Asselin+%253Cramy.asselin%2540hp.com%253E%22+status:open,n,z15:14
ctlaughcould I get a brief description of what this is?15:14
swestonasselin: +115:14
asselinctlaugh, the log server?15:14
krtayloror the effort overall?15:15
ctlaughsorry, downstream-puppet15:15
*** vishwanathj has joined #openstack-meeting-415:15
asselin#link http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html15:16
asselinctlaugh, ^^15:16
ctlaughthank you15:16
asselinidea is to get scripts reusable by all. eventually get a 'common' ci solution15:17
ctlaughI love that idea15:17
asselinctlaugh, great! :)15:17
krtaylor++15:18
krtaylorit will be great going forward, unify the work15:18
krtaylorasselin, thanks again for all your leadership in this effort15:18
ctlaughOne of my biggest concerns setting our system up (using an external repo such as asselin's) is that changes upstream do not comprehend any of the downstream systems that are using it.15:18
zz_ja|we will be jumping on this the instant we have our "hw" procured15:19
krtayloryes, exactly, or how they will potentially be impacted15:19
krtaylorok, any other questions on the downstream-puppet work?15:20
krtaylor#topic Repo for third party tools15:20
*** openstack changes topic to "Repo for third party tools (Meeting topic: third-party)"15:20
asselinyes. please review, download patches and try them out. See if they would work in 'your' environment.15:20
krtaylorinternally, I was trying to get permission to add our tools to the index via our personal github accounts, but that is going to be too painful15:21
krtaylorso I am going to start up the process for creating a stackforge repo for us to share configs, tools, things we need to share for TPCIWG, to help each other15:22
krtaylorI was hoping to have the bandwidth by now, silly day job...15:22
krtaylorbut we do have the TPCIWG wiki index, if anyone wants to add to it for now15:23
krtaylor#link https://wiki.openstack.org/wiki/ThirdPartyCIWorkingGroup#Third_Party_CI_System_Tools_Index15:23
krtaylorok, probably not much to discuss there, any questions?15:24
krtaylor#topic monitoring dashboard15:24
*** openstack changes topic to "monitoring dashboard (Meeting topic: third-party)"15:24
krtaylorgreat progress here, thanks for the re-write sweston!15:25
asselin+115:25
*** erikmwilson has joined #openstack-meeting-415:25
krtaylor#link https://review.openstack.org/#/c/135170/15:25
swestonyou bet ... just need to respond to jhesketh's comments, and this might merge soon ;-)15:25
patrickeastdefinitely good progress, i really like the updates15:25
swestonpatrickeast: thanks15:25
krtayloryes, but even with thoses, he supported it as is15:26
swestonkrtaylor, asselin: thanks for your help as well15:26
krtaylorno porblem, thanks sweston for putting it on a diet and getting it rolling again15:26
swestonkrtaylor: you're welcome15:27
krtaylorok, so any questions for the monitoring dashboard effort?15:28
krtayloralright, on to my favorite part of the meeting15:29
krtaylor#topic Highlighting Third-Party CI Service15:29
*** openstack changes topic to "Highlighting Third-Party CI Service (Meeting topic: third-party)"15:29
krtaylortoday we have ctlaugh presenting on Linaro CI system for ARM testing15:29
*** ajmiller has quit IRC15:29
krtaylorctlaugh, the floor is yours15:30
ctlaughthank you15:30
ctlaughI am working with Linaro to setup a 3rd-party CI system to test Openstack on arm64.  Our intent is to ultimately just run as much of Tempest as we reasonably can, given the compute resources that we have available to scale with.  Currently, I am triggering off of changes to openstack/nova and openstack-dev/devstack.15:30
*** banix has joined #openstack-meeting-415:30
ctlaughThe hardware we are using is an HP Moonshot enclosure filled with a combination of HP Proliant m300 (amd64) nodes (about 15) and HP Proliant m400 (arm64) nodes (about 20).15:30
ctlaughI am using asselin’s os-ext-testing fork on github to deploy the setup.15:30
ctlaughThe Openstack cloud we are using is deployed using Juju mainly on the amd64 nodes, with the compute nodes deployed on the arm64 nodes.15:31
ctlaughThe various Openstack CI components are also all deployed on amd64 nodes.15:31
ctlaughI started out by first setting up the entire system all on amd64 nodes in order to make sure  everything was setup and working properly.15:31
ctlaughAfter a lot of help from asselin, a few patches to his fork, and a bit of tweaking, everything seemed to be running ok for a start.  The main problem I kept experiencing was Jenkins failures:  about 30-40% of the time, Jenkins would throw an exception and fail the test saying it lost connectivity with a slave.15:31
* sweston does not want to see ctlaugh's power bill15:31
ctlaughhe he15:32
krtaylorctlaugh, are you initially focused on running against nova patches15:32
ctlaughYes - for now15:32
*** xingchao_ has joined #openstack-meeting-415:32
ctlaughWe aren't entirely sure what the best thing will be to trigger off of long-term, since we aren't necessarily focused on testing a specific project.15:32
ctlaughNova is probably the one single project we are most interested in (for now), but we also want to be able to demonstrate that everything runs on arm64.15:33
swestonctlaugh: are you using single use slaves?  this was an issue I had when I was starting out with CI .. cruft from previous runs was causing instability15:33
krtaylorctlaugh, we are in a similar situation for PowerKVM, since we are re-using the existing libvirt driver15:33
ctlaughsweston: yes, using single-use slaves15:34
ctlaughkrtaylor: right now, we are focused on KVM + libvirt, but in time, we might also be interested in Xen on arm64 as well.  There is a concern that it will become unsupported by Openstack since no one is testing it.15:35
asselinctlaugh, currently i'm experimenting with disabling c-states in the bios & power management. seems to be helping so far.15:35
ctlaughasselin: helping with what?15:35
krtaylorctlaugh, yes, we have a different need to show openstack works on our platform instead of just testing a single driver as most third party ci is focused on15:35
asselinctlaugh, running jenkins slaves15:36
* asselin looks up link15:36
ctlaughasselin: ah -- interesting15:36
asselin#link http://support.citrix.com/article/CTX12739515:36
*** xingchao_ has quit IRC15:37
asselingot my ideas from this ^^, although we have different HW, etc.15:37
ctlaughRight now, I am now in the process of replacing the amd64 compute nodes I have been testing with far far, and switching to arm64 compute nodes.  I am currently working on the nodepool scripts to get them to deploy on arm64 correctly, and that is probably what will require the most changes to get right.15:37
ctlaughI have already submitted a change to openstack-infra/puppet-jenkins in order to correct the JDK deployment to not be amd64-specific.  It is currently awaiting review.15:38
*** ajmiller has joined #openstack-meeting-415:38
ctlaughI have also identified (I think) a few changes that need to be made to openstack-infra/system-config and openstack-infra/project-config that are also needed (related to how puppet gets installed), though I am still doing some testing.15:38
ctlaughI don’t know yet if that’s all that is going to be required, or if I will run into other problems once I try to run on arm64.15:38
krtaylorctlaugh, link? I'll review15:38
ctlaughA big concern is with Jenkins - whether the problems I was seeing there will be about the same as before, or be worse.15:38
* ctlaugh is looking...15:39
ctlaugh#link https://review.openstack.org/#/c/168222/15:39
krtaylorperfect, tnaks15:40
ctlaughSo that's about it...15:40
krtaylorthanks too15:40
*** ChuckC has joined #openstack-meeting-415:40
ctlaughAny other questions (or suggestions)?15:40
krtaylorctlaugh, so any ideas on the 30-40% failures, lost connection problems15:41
ctlaughkrtaylor: not yet.  At one point, I thought it might have been related to how much load each of the nodes was under.  It _seemed_ to get worse the more VMs I had running on a single nova-compute node.15:42
asselinctlaugh, in my case I was looking at the nova console.log files for the jenkins slave which led my to that article about adjusting power states15:42
*** bharath has joined #openstack-meeting-415:42
ctlaughThe amd64 nodes I have are not that great -- the processors are actually atom-based.15:42
krtaylorctlaugh, are they the same failures each time, or transient?15:43
ctlaughWhen it fails, it's the same each time.  I'll post a link to the failure as soon as I find an example.15:43
ctlaughMy hope is that when I start using the more capable arm64 nodes, I'll have less failures.15:44
ctlaughI don't have a convenient way to grab the error text at the moment.15:45
krtaylorctlaugh, we had increase in stability and test execution (reducing skips) by reducing IO blocks15:45
*** bharath has quit IRC15:46
krtaylormmedvede on my team has been driving that effort for us, may be a good contact for you15:46
*** bharath has joined #openstack-meeting-415:46
ctlaughgreat - thank you15:46
*** kobis has quit IRC15:47
mmedvedectlaugh: I can look at errors/logs if you'd like15:47
krtaylorctlaugh, any tools you use in your environment that really help you?15:48
krtaylorctlaugh, anything you came up with that may help others?15:48
ctlaughkrtaylor: not really anything extra.  I use MAAS and Juju to manage deployment of all of the hardware, mainly because that's the easiest way to do it.15:48
ctlaughOtherwise, so far it's just the bits deployed by asselin's scripts.15:49
ctlaughIf Jenkins doesn't work out, that might change and I may have a replacement to share with others :)15:49
*** yamahata has quit IRC15:50
*** yamahata has joined #openstack-meeting-415:50
krtaylorctlaugh, ok, thanks, thats good to know, feel free to add anything you come up with to the tools index15:50
ctlaughok, I will15:51
krtaylorasselin, one more successful deployment from your repo :)15:51
asselingreat! :)15:51
asselinctlaugh, thanks for the pr's15:52
krtaylorok, so any other questions for ctlaugh about his ARM64 test environment?15:52
krtaylorctlaugh, thanks for coming and talking about your environment, it's really good to get to know more about other's systems15:53
asselinctlaugh, thanks for sharing15:53
ctlaughyou're welcome -- it was a pleasure15:54
krtaylorok, then15:54
krtaylor#topic Open Discussion15:54
*** openstack changes topic to "Open Discussion (Meeting topic: third-party)"15:54
krtayloranything anyone wants to discuss?15:54
* krtaylor notes it is rare that we have time to get to Open Discussion15:55
*** dannywilson has joined #openstack-meeting-415:56
*** carl_baldwin has quit IRC15:56
krtaylorok, well if nothing else, then I'll wrap this up15:57
krtaylordon't forget to add your summit topics to the etherpad15:57
krtaylorthanks everyone, thanks ctlaugh, another great meeting!15:58
swestonthanks, krtaylor15:58
asselinthanks15:58
ctlaughthank you, everyone15:58
krtaylor#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings"15:59
openstackMeeting ended Wed Apr  1 15:59:01 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-04-01-15.01.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-04-01-15.01.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-04-01-15.01.log.html15:59
*** eghobo has joined #openstack-meeting-416:00
*** bharath_ has joined #openstack-meeting-416:01
*** bharath has quit IRC16:02
*** bharath_ has quit IRC16:03
*** bharath has joined #openstack-meeting-416:03
*** carl_baldwin has joined #openstack-meeting-416:03
*** patrickeast has quit IRC16:09
*** SumitNaiksatam has quit IRC16:13
*** erikmwilson has quit IRC16:20
*** erikmwilson has joined #openstack-meeting-416:20
*** erikmwilson has quit IRC16:20
*** shwetaap has quit IRC16:20
*** asselin has quit IRC16:24
*** ivar-lazzaro has joined #openstack-meeting-416:25
*** aduarte has quit IRC16:27
*** ivar-lazzaro has quit IRC16:30
*** ivar-lazzaro has joined #openstack-meeting-416:30
*** larsks has joined #openstack-meeting-416:31
*** xingchao_ has joined #openstack-meeting-416:36
*** carl_baldwin has quit IRC16:36
*** shwetaap has joined #openstack-meeting-416:36
*** SumitNaiksatam has joined #openstack-meeting-416:39
*** xingchao_ has quit IRC16:41
*** sigmavirus24 is now known as sigmavirus24_awa16:43
*** sigmavirus24_awa is now known as sigmavirus2416:43
*** Swami has joined #openstack-meeting-416:47
*** banix has quit IRC16:50
*** dims__ has quit IRC16:53
*** dims_ has joined #openstack-meeting-416:53
*** shwetaap has left #openstack-meeting-416:55
yamahatahello17:01
*** sbalukoff has quit IRC17:02
*** sdake_ has joined #openstack-meeting-417:02
*** emagana has quit IRC17:04
*** sdake has quit IRC17:05
*** VW_ has quit IRC17:06
*** sridhar_ram has joined #openstack-meeting-417:06
*** dannywilson has quit IRC17:08
*** carl_baldwin has joined #openstack-meeting-417:12
*** daneyon has joined #openstack-meeting-417:14
*** yamahata has quit IRC17:16
*** daneyon_ has quit IRC17:17
*** Salman_ has joined #openstack-meeting-417:17
*** s3wong has joined #openstack-meeting-417:19
*** eghobo has quit IRC17:28
*** ajmiller has quit IRC17:30
*** emagana has joined #openstack-meeting-417:31
*** aduarte has joined #openstack-meeting-417:34
*** eghobo has joined #openstack-meeting-417:35
*** yamahata has joined #openstack-meeting-417:38
*** xingchao_ has joined #openstack-meeting-417:40
*** ajmiller has joined #openstack-meeting-417:45
*** xingchao_ has quit IRC17:47
*** VW_ has joined #openstack-meeting-417:49
*** sridhar_ram has quit IRC17:57
*** ivar-laz_ has joined #openstack-meeting-418:02
*** ivar-laz_ has quit IRC18:03
*** dannywilson has joined #openstack-meeting-418:04
*** banix has joined #openstack-meeting-418:04
*** ivar-lazzaro has quit IRC18:06
*** carl_baldwin has quit IRC18:06
*** sbalukoff has joined #openstack-meeting-418:09
*** carl_baldwin has joined #openstack-meeting-418:13
*** sdake has joined #openstack-meeting-418:13
*** salv-orl_ has joined #openstack-meeting-418:13
*** rfolco has quit IRC18:16
*** sdake_ has quit IRC18:16
*** salv-orlando has quit IRC18:17
*** isq has quit IRC18:24
*** nkrinner has joined #openstack-meeting-418:24
*** sridhar_ram has joined #openstack-meeting-418:26
*** ivar-lazzaro has joined #openstack-meeting-418:29
*** claired has joined #openstack-meeting-418:29
*** claired has quit IRC18:29
*** rfolco has joined #openstack-meeting-418:31
*** ivar-lazzaro has quit IRC18:43
*** xingchao_ has joined #openstack-meeting-418:46
*** emagana has quit IRC18:50
*** isq has joined #openstack-meeting-418:51
*** xingchao_ has quit IRC18:51
*** ekudryashova has joined #openstack-meeting-419:00
*** VW_ has quit IRC19:00
*** VW_ has joined #openstack-meeting-419:02
*** eghobo has quit IRC19:05
*** emagana has joined #openstack-meeting-419:09
*** VW_ has quit IRC19:12
*** VW_ has joined #openstack-meeting-419:13
*** Rockyg has joined #openstack-meeting-419:17
*** eghobo has joined #openstack-meeting-419:19
*** rushiagr is now known as rushiagr_away19:21
*** nkrinner has quit IRC19:28
*** matrohon has joined #openstack-meeting-419:32
*** VW_ has quit IRC19:36
*** Nikolay_St has joined #openstack-meeting-419:37
*** rm_work is now known as rm_work|away19:43
*** mwang2 has joined #openstack-meeting-419:49
*** Nikolay_St has quit IRC19:49
*** Nikolay_St has joined #openstack-meeting-419:50
*** VW_ has joined #openstack-meeting-419:58
Rockygo/19:59
Nikolay_Sto/19:59
Rockyggonna wait a few minutes to see if anyone else turns up20:01
ekudryashovaHi!20:01
Rockygstill didn't get the spec in.  Too busy here at my day job20:01
RockygWelcome!!!!!20:01
Nikolay_Stoh, new face :)20:02
Nikolay_Stwelcome20:02
RockygOK.  I guess we might at well start, then20:02
Rockyg#startmeeting log_wg20:03
openstackMeeting started Wed Apr  1 20:03:06 2015 UTC and is due to finish in 60 minutes.  The chair is Rockyg. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: log_wg)"20:03
openstackThe meeting name has been set to 'log_wg'20:03
bknudsonhi20:03
Nikolay_Sto/20:03
RockygHey there.  We have a new attendee...ekudryashova20:03
RockygI believe she started the API error codes debate on the ML20:04
jokke_o/20:04
RockygYay, jokke_ !20:04
RockygSo, old business20:04
jokke_"It's alive!" :P20:04
Rockyg#topic old business20:04
*** openstack changes topic to "old business (Meeting topic: log_wg)"20:04
RockygI got swamped at work and haven't gotten the spec in.  jokke_: if I email it to you, can you push it to git review?  I haen't had time to get that working on the new 'puter20:05
RockygIt's not as complete as I'd like it, but getting it out there with comments is more important as the meat is all there20:06
jokke_Rockyg: sure, I'll try to find time for that20:06
ekudryashovaYes, I'm interesting in error-codes direction. Also while we have freeze and all of thoose things I'll be glad to help with improving log consistency. If you have some "todo" lists for this please share with me20:07
Rockygjokke_:  Thanks.  Should just be the add to cloned repository and git review20:07
Rockygekudryashova:  Reviewing the spec will go a long way.  We also are looking to get some other focused specs out there.20:08
jokke_Rockyg: cool, sure20:08
jokke_ekudryashova: good to see you here. Maybe we get that one finally moving as well20:09
RockygAny other old business?20:09
RockygOK.  New business20:10
Rockyg#topic API logging spec available20:10
*** openstack changes topic to "API logging spec available (Meeting topic: log_wg)"20:10
RockygEverett Toews just pushed out a spec and we need to jump on it.20:10
jokke_do we have a link?20:11
Rockyg#link  https://review.openstack.org/16779320:11
Rockyg"A guideline for errors"20:12
bknudsonclippy go away20:12
RockygThis is for format in the message body, the "payload"20:12
Nikolay_StI've taken a look at it. Looks good at first glance20:13
bknudsonhopefully all the projects can use this and have a consistent error document...20:13
jokke_I'll review that after this meeting20:13
Rockygbknudson:  how come I get clippy, too?20:14
bknudsonclients need to understand it, too.20:14
bknudsonand CLI20:14
RockygI think devs and ops do, too ;-)20:14
jokke_4/1/15 :)20:14
bknudsonthere's a couple of reasons that the error doc from keystone is generally useless --20:15
RockygThis proposal is for all APIs across OpenStack willing to play nice and head towards consistency20:15
bknudson1) don't want to give away info20:15
bknudson2) poor code design so we don't always have the right error20:15
bknudsonerrors in keystone are generally pretty basic, though... user didn't exist or whatever.20:15
bknudsonI like that it's a list of errors since if you're doing input validation there can be multiple errors20:16
bknudsonalthough we'd need to enhance input validation to get a list of problems rather than just a generic 400 error.20:16
Rockygbknudson:  ++20:17
*** emagana has quit IRC20:17
Nikolay_Stbknudson: you're right20:17
RockygSo, everyone, please review and *comment*  Once you comment, you'll get  notification of all comments and changes20:17
RockygWe can discuss progress at next meeting, or add to the ml thread20:18
RockygAnd we need to advertise to ops ml once we think it's ready for their input20:18
Rockyganything else on this?20:19
*** fnaval has joined #openstack-meeting-420:19
jokke_could someone decode that spec for me and tell what the heck is proposed?20:20
bknudsonit's the document that gets returned when there's an error...20:22
bknudsoncurrently I think every service does their own thing.20:22
bknudsone.g., if the server returns a 500 error or 400 or whatever.20:22
RockygIt looks like error codes *in error body* is being proposed?20:22
RockygOr am I misreading?20:23
Nikolay_Sti tjink not20:23
bknudsonyes, error codes in the entity-body of the response.20:23
RockygHmmm.  error codes should be part of header with body containing details of error instance20:24
bknudsonthe 500 or 400 code in the status line doesn't provide enough info.20:24
*** Swami has quit IRC20:24
ekudryashovaIn my opinion the biggest fix there is every project will return one type payload(json) instead of string, dict or everything else returned now in response20:24
jokke_I'm surprised that it's not proposed to be base64 encoded for even worse readability ;)20:26
Rockygekudryashova: error codes aren't in guidelines *yet*  That's what our spec (out soon) will be20:26
RockygWell, let's get our spec out there and post to the thread as part of the response?20:27
ekudryashovaThey is in payload, as I understood they not actually pay attention on structure of code itself and let it be another question20:27
RockygAh.  I think you are right20:28
*** VW__ has joined #openstack-meeting-420:28
*** zz_ja| is now known as zz_zz_ja|20:29
Rockygekudryashova: So, what we are attempting to do is define a structure for error messages through a series of cross project specs.  One is error codes.  Another is referrer ids20:29
RockygWe need someone to write the second.  There is a dev who already proposed a project specific spec for that that we should work with20:30
RockygI think referrer IDs will need to be part of the payload, not header20:30
*** emagana has joined #openstack-meeting-420:30
*** rfolco has quit IRC20:31
Rockyganyway, let's get our spec out and make a bunch of comments on this one.20:31
jokke_++20:31
Rockyg#topic hacking rules for oslo.log20:31
*** openstack changes topic to "hacking rules for oslo.log (Meeting topic: log_wg)"20:31
*** VW_ has quit IRC20:32
RockygNew ml thread on this.  appears a number of projects have hacking rules for log messages, and the discussion started yesterday on this.20:32
Rockygekudryashova: have you seen the wiki and etherpads for logging group?20:33
*** Swami has joined #openstack-meeting-420:33
ekudryashovaRockyg: I saw wiki but no etherpads20:34
*** sridhar_ram1 has joined #openstack-meeting-420:34
RockygAh.  the etherpads actually have more detail on the general consensus of where to go with getting logs more consistent and better20:34
RockygI think they are all linked on the main working group page:  #link https://wiki.openstack.org/wiki/LogWorkingGroup20:36
RockygI was/am trying to summarize them into something more consistent/readable20:36
ekudryashovaThanks, will take a look20:36
RockygBut, they help in getting on the same page and asking questions/suggesting actions20:37
jokke_so Rockyg about the hacking rules, what about it or was this just to promote the ml conv?20:37
*** sridhar_ram has quit IRC20:38
RockygSo, the thread has a list of checks that Cinder has put in.  Neutron says they have some, too.  I think maybe we can propose a list of these in a cross project spec20:38
RockygThen the projects can take them or not20:39
bknudsonthese changes are going to go in the global hacking checks20:39
RockygAnd we add new ones as specs get approved20:39
*** sballe has joined #openstack-meeting-420:39
Nikolay_StRockyg: where we can read about it??20:39
RockygLemme find the link to the mail....20:39
bknudsonat least in keystone we try to enforce all the global hacking checks.20:39
*** VW__ has quit IRC20:41
Rockyg#link http://lists.openstack.org/pipermail/openstack-dev/2015-March/060299.html20:41
Rockygand #link http://lists.openstack.org/pipermail/openstack-dev/2015-April/060361.html20:42
RockygThis could be a good, focused spec that ekudryashova could put together.20:42
RockygShould move through cross project quickly.  shouldn't be too controversial.20:43
ekudryashovaOk, give me a details and I'll be glad to make it20:44
RockygThen, they could go in the global and projects could turn on or off as they like.20:44
*** VW_ has joined #openstack-meeting-420:44
Rockygekudryashova: let's take the details to email... I might be slow until Monday.  Taking Friday off and in-house conference tomorrow.20:45
ekudryashovaRockyg: Thanks, will wait for email20:45
RockygAnyway, #action ekudryashova to put together spec with hacking rules for oslo.log stuff20:46
Rockyg#action ekudryashova to put together spec with hacking rules for oslo.log stuff20:46
Rockyg#action ekudryashova to put together spec with hacking rules for oslo.log stuff20:46
*** rm_work|away is now known as rm_work20:47
RockygHmmm.  Why doesn't that take?  Anyway, next topic20:47
*** VW_ has quit IRC20:47
Rockyg#topic Summit planning20:47
*** openstack changes topic to "Summit planning (Meeting topic: log_wg)"20:47
RockygWe've got to think about two tracks:  Ops and dev20:47
*** VW_ has joined #openstack-meeting-420:48
jokke_++20:48
RockygI think on Ops, we should plan to provide status of current efforts, then get some consensus on next items to focus effort on20:48
jokke_do we have any possibility to actually gather together and make a proper battle plan for Liberty? :P20:48
Nikolay_StI don't have plans to go on summit20:49
Nikolay_Stother guys from Sahara has it as I know20:49
RockygWe could meet Sunday or Monday and do some tactical planning, but I think we need to get strategy before then.20:49
Rockygnikolay_St: sorry to hear that.20:50
RockygSo, I think we need to go for a cross project slot for dev.  do we need more than one?20:50
RockygAnyone?20:51
*** mwang2 has quit IRC20:51
RockygAnd, one slot or two for ops?20:51
*** VW_ has quit IRC20:51
*** sdake_ has joined #openstack-meeting-420:52
RockygAnd, do we target projects to socialize our specs?20:52
RockygI know we don't have to worry about glance;-)20:52
Rockygcrickets20:53
*** rm_work is now known as rm_work|away20:53
Rockygtumbleweeds20:53
jokke_I'll be arriving to Vancouver Fri evening and have my talk at Mon (I think it was one of the last sessions) so I can meet up FE. earlier Mon (Long lunch maybe)20:54
bknudsonI'd try to attend a logging session.20:54
Nikolay_StI think Sahara is interesting :)20:54
RockygOK.  bknudson: can you socialize the specs we have out by then to Keystone?20:55
bknudsonsure.20:55
*** sdake has quit IRC20:55
RockygCool.20:55
jokke_Rockyg: I'd like to have x-proj slot and ops slot ... best case scenario would be x-proj slot, ops slot, x-proj slot but either of the x-proj slots could be replaced by unofficial20:55
RockygI know we can get an ops slot.  Teh xproject slot is a bit more iffy.  I'll go out to the ops etherpad and put up a proposal20:56
jokke_so that we could give ops update where we are, plan future and get their feedback and after that get togther and fix that feedback into the L-plans for us20:56
Rockygjokke_ that sounds great.20:57
RockygI think we need to educate ourselves on the current state of oslo.log and the syslog RFC.  Then we can see where we are and where we want to be.20:57
Rockygoslo.log has a lot more documentation now, from a dev perspective.20:58
jokke_Rockyg: ok, I clearly need update myself on oslo.log20:59
Rockygsyslog allows for *too much* flexibility, so we need to see what might be the right set of constraints to make logs consistent and usable to the collection of projects that is OpenStack.20:59
*** VW_ has joined #openstack-meeting-420:59
RockygYeah.  FYI: oslo.log is now 1.0.0 released20:59
*** emagana has quit IRC21:00
jokke_well with bit tent, don't hold your breath waiting that to happen, but if we could get the core services to reasonable state, that would be good21:00
Rockyg#link http://docs.openstack.org/developer/oslo.log/21:00
*** emagana has joined #openstack-meeting-421:00
jokke_problem seems to be that few projects and ever fewer people really seems to care about logging on our dev community21:01
Rockygjokke_: yeah.  I'm calling them foundational projects to get away from core21:01
RockygFolks, with the Product Team out there now, logs are going to get more attention.21:02
jokke_sorry to interrupt, but is there someone waiting for next slot, we're over time21:02
RockygThere will be more and more pushback to getting the projects more usable and productizable.21:02
RockygOops!  No one, but let's call it.21:02
Rockyg#endmeeting21:02
*** openstack changes topic to "OpenStack Meetings"21:02
openstackMeeting ended Wed Apr  1 21:02:58 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-04-01-20.03.html21:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-04-01-20.03.txt21:03
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-04-01-20.03.log.html21:03
Nikolay_Stbye21:03
jokke_Rockyg: I have zero confidence for that before I see it :)21:03
*** Nikolay_St has quit IRC21:03
jokke_thanks all and bye!21:03
RockygNext week and you will see email from me shortly21:03
jokke_good stuff ... take care21:03
ekudryashovaBye!21:03
*** emagana_ has joined #openstack-meeting-421:04
*** emagana has quit IRC21:04
RockygThanks all!!!21:05
*** ekudryashova has quit IRC21:05
*** sdake_ has quit IRC21:15
*** dims_ has quit IRC21:19
*** sdake has joined #openstack-meeting-421:37
*** ChuckC has quit IRC21:39
*** sdake_ has joined #openstack-meeting-421:41
*** Rockyg has quit IRC21:43
*** sdake has quit IRC21:45
*** sdake has joined #openstack-meeting-421:45
*** eghobo has quit IRC21:47
*** daneyon has quit IRC21:47
*** daneyon has joined #openstack-meeting-421:47
*** sdake_ has quit IRC21:49
*** eghobo has joined #openstack-meeting-421:49
*** ibiris is now known as ibiris_away21:53
*** bknudson has quit IRC21:54
*** banix has quit IRC21:58
*** emagana_ has quit IRC22:01
*** sigmavirus24 is now known as sigmavirus24_awa22:01
*** xingchao_ has joined #openstack-meeting-422:02
*** carl_baldwin has quit IRC22:02
*** VW_ has quit IRC22:06
*** xingchao_ has quit IRC22:07
*** klamath has quit IRC22:07
*** ChuckC has joined #openstack-meeting-422:09
*** asselin has joined #openstack-meeting-422:20
*** asselin has quit IRC22:25
*** sridhar_ram has joined #openstack-meeting-422:25
*** matrohon has quit IRC22:26
*** banix has joined #openstack-meeting-422:27
*** sridhar_ram1 has quit IRC22:28
*** daneyon has quit IRC22:30
*** daneyon has joined #openstack-meeting-422:31
*** banix has quit IRC22:31
*** banix has joined #openstack-meeting-422:32
*** igordcard_ has joined #openstack-meeting-422:32
*** eghobo has quit IRC22:35
*** Gavin_Pratt has joined #openstack-meeting-422:35
*** emagana has joined #openstack-meeting-422:35
*** Gavin_Pratt has quit IRC22:37
*** eghobo has joined #openstack-meeting-422:41
*** eghobo has quit IRC22:42
*** eghobo has joined #openstack-meeting-422:43
*** emagana has quit IRC22:43
*** banix has quit IRC22:44
*** banix has joined #openstack-meeting-422:49
*** rolandchan has joined #openstack-meeting-422:52
*** banix has quit IRC22:53
*** xingchao_ has joined #openstack-meeting-422:57
*** bknudson has joined #openstack-meeting-423:06
*** banix has joined #openstack-meeting-423:07
*** igordcard has quit IRC23:14
*** ajmiller_ has joined #openstack-meeting-423:22
*** ajmiller has quit IRC23:26
*** rolandchan has left #openstack-meeting-423:27
*** stevelle has joined #openstack-meeting-423:32
*** banix has quit IRC23:33
*** ajmiller_ is now known as ajmiller23:34
*** salv-orlando has joined #openstack-meeting-423:40
*** ajmiller has quit IRC23:41
*** bharath has quit IRC23:41
*** salv-orl_ has quit IRC23:42
*** SumitNaiksatam has quit IRC23:57

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