Thursday, 2013-05-09

*** spzala has joined #openstack-meeting00:02
*** jlucci has quit IRC00:04
*** esker has quit IRC00:04
*** vipul is now known as vipul|away00:05
*** dontalton has quit IRC00:05
*** Yada has quit IRC00:06
*** vipul|away is now known as vipul00:07
*** adjohn_ has joined #openstack-meeting00:10
*** amyt has joined #openstack-meeting00:12
*** lloydde_ has quit IRC00:13
*** adjohn has quit IRC00:14
*** markpeek has joined #openstack-meeting00:15
*** lloydde has joined #openstack-meeting00:18
*** salv-orlando has quit IRC00:27
*** spzala has quit IRC00:28
*** zzs has left #openstack-meeting00:32
*** markpeek has quit IRC00:32
*** mattray has quit IRC00:33
*** ryanpetrello has joined #openstack-meeting00:34
*** lloydde has quit IRC00:35
*** ayoung-afk is now known as ayoung00:35
*** zhuadl has joined #openstack-meeting00:35
*** lloydde has joined #openstack-meeting00:36
*** lloydde has quit IRC00:40
*** bdpayne has quit IRC00:42
*** ladquin_brb has quit IRC00:43
*** cyeoh_ is now known as cyeoh00:49
*** zul has quit IRC00:50
*** Ramix has joined #openstack-meeting00:51
*** markpeek has joined #openstack-meeting00:55
*** sean_s has joined #openstack-meeting00:59
hartsocksHello everyone. Who's in the room for the VMwareAPI meeting?01:00
*** Swaminathan has joined #openstack-meeting01:01
hartsocksirc://irc.freenode.net:6667/#startmeeting VMwareAPI01:03
*** zhuadl has quit IRC01:03
*** MarkAtwood has quit IRC01:03
hartsocksHello and welcome to the first meeting of the VMwareAPI subteam. I chose this time on short notice so I am very glad for whomever could attend.01:04
*** maoy has quit IRC01:04
*** reed has quit IRC01:05
hartsocksThis sub-team is dedicated to creating better support for the Nova compute driver for vSphere but I also want to hold the door open to helping launch other projects that might find additional uses for various VMwareAPI inside OpenStack.01:06
*** barefoot has left #openstack-meeting01:07
hartsocksWe wanted to make sure we kicked off a meeting this week before Havana-1 was too close. We will have these weekly through Havana release.01:07
hartsocks#topic Grizzly Bug Triage01:08
hartsocksBefore we start in on Havana though, let's see if anyone has anything to say about open bugs in Grizzly.01:08
*** maoy has joined #openstack-meeting01:11
*** maoy has quit IRC01:12
*** zb has joined #openstack-meeting01:13
hartsocksOkay. Since I seem to be talking to an empty room. I'll just record a few things here.01:13
hartsocksOur team at VMware is ramping up and we are using https://bugs.launchpad.net/nova/+bugs?field.tag=vmware to look for bugs and contributions to make.01:14
hartsocksI'll be delegating some of these to our internal team as they come up to speed.01:14
*** mauilion has joined #openstack-meeting01:15
hartsocksI'm initially assigning myself to bugs that I think are high priority. So if you see something not assigned at all, we're either unaware of it or we didn't think it was that important.01:16
*** zaneb has quit IRC01:16
hartsocks#topic Havana Blueprint Discussion & Priority ordering01:20
hartsocksCan we start using vmware or VMware in the names of all blueprints dealing with VMware API integrations. This should include vSphere or any thing like vSAN or other "v" tools that might be useful.01:21
hartsocksJust in case someone snuck in the room with me… any comments here? (otherwise I'll just tick off some notes for the record)01:22
SwaminathanVMware should work01:24
hartsocksAgreed.01:25
hartsocksI have identified 5 blueprints associated with VMware...01:27
hartsockshttps://blueprints.launchpad.net/nova?searchtext=vmware01:27
hartsocksThese are easy enough to spot.01:27
hartsocksYou'll see 4 there.01:27
hartsocksBut there's a 5th01:27
hartsockshttps://blueprints.launchpad.net/nova/+spec/fc-support-for-vcenter-driver01:27
*** terry7 has quit IRC01:28
hartsocksif you search vCenter you find more...01:28
hartsockshttps://blueprints.launchpad.net/nova/+spec/accurate-capacity-of-clusters-for-scheduler01:28
hartsockshttps://blueprints.launchpad.net/nova/+spec/deploy-vcenter-templates-from-vmware-nova-driver01:29
*** jaypipes has quit IRC01:29
hartsocks… and for the record I'll list out the others ...01:30
hartsockshttps://blueprints.launchpad.net/nova/+spec/multiple-clusters-managed-by-one-service01:30
hartsockshttps://blueprints.launchpad.net/nova/+spec/esx-resource-pools-as-compute-nodes01:30
hartsocksso … that's all I've spotted.01:31
hartsocksDoes anyone have comments on these?01:31
*** acfleury has quit IRC01:32
*** ladquin has joined #openstack-meeting01:33
hartsocksI am concerned about the number of blueprints, and the number of actual contributors. I would like to have some clarity on time-lines as well. It would be nice to be able to coordinate efforts.01:36
*** ladquin is now known as ladquin_away01:39
hartsocksI think https://blueprints.launchpad.net/nova/+spec/multiple-clusters-managed-by-one-service is our highest priority blueprint to iron out.01:42
hartsocksCan anyone present talk about this?01:42
hartsocksHey… I know I'm not in the room alone. One of you made the mistake of talking to me. :-p01:44
hartsocks#topic TestCoverage01:45
hartsocksSpecifically for the VCDriver… our internal team wants to see this get to 80% but it's pretty low now...01:46
hartsocksIf anyone can help or give feedback on this topic it's appreciated.01:47
hartsocksIn particular I'm trying to figure out how to write a test for an interaction between the VMwareVCDriver and the scheduler filters.01:49
hartsocksThat kind of interaction is hard to model.01:49
hartsocks#topic Regular Meeting time?01:51
hartsocksI chose this time because it was convenient to our Palo Alto team. I also hoped to catch some of our colleagues in Australia and China.01:52
hartsocksI was also on short notice… so… I'll announce the next meeting time now and on the list.01:52
hartsockshttp://www.timeanddate.com/worldclock/fixedtime.html?iso=20130515T170001:52
hartsocksHow is this?01:53
*** rwsu-away has quit IRC01:54
*** ryanpetrello has quit IRC01:57
*** Mandell has quit IRC01:58
*** Ramix has left #openstack-meeting01:58
*** ryanpetrello has joined #openstack-meeting01:58
hartsocksWell, we didn't accomplish much in this "meeting"01:59
*** mattray has joined #openstack-meeting01:59
hartsockswe did manage to fill the channel with some information and I'll be able to setup for our next meeting.01:59
*** rwsu has joined #openstack-meeting02:00
hartsocksThis will be May 15th at 10:00 am in San Francisco … or 1700 UTC if you prefer.02:00
*** mattray has quit IRC02:00
hartsocksThank you and good night.02:00
hartsocks#endmeeting02:01
hartsocksOkay, srsly… did you leave MeetBot?02:02
*** gongysh has joined #openstack-meeting02:04
*** fnaval_ has joined #openstack-meeting02:04
hartsocks#endmeeting02:04
*** dwcramer has joined #openstack-meeting02:04
*** fnaval has quit IRC02:05
*** danwent has quit IRC02:05
hartsocks#startmeeting02:06
openstackhartsocks: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'02:06
*** ryanpetrello has quit IRC02:07
hartsocksI've made a huge mistake.02:08
*** hartsocks has left #openstack-meeting02:08
*** beagles has quit IRC02:11
*** MarkAtwood has joined #openstack-meeting02:12
*** sean_s has quit IRC02:13
*** anniec has quit IRC02:14
*** hartsocks has joined #openstack-meeting02:15
hartsocks#startmeeting honeybooboo02:15
openstackMeeting started Thu May  9 02:15:48 2013 UTC.  The chair is hartsocks. Information about MeetBot at http://wiki.debian.org/MeetBot.02:15
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.02:15
*** openstack changes topic to " (Meeting topic: honeybooboo)"02:15
openstackThe meeting name has been set to 'honeybooboo'02:15
hartsocks#endmeeting02:16
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"02:16
openstackMeeting ended Thu May  9 02:16:01 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)02:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/honeybooboo/2013/honeybooboo.2013-05-09-02.15.html02:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/honeybooboo/2013/honeybooboo.2013-05-09-02.15.txt02:16
openstackLog:            http://eavesdrop.openstack.org/meetings/honeybooboo/2013/honeybooboo.2013-05-09-02.15.log.html02:16
*** hartsocks has left #openstack-meeting02:16
*** amyt has quit IRC02:25
*** gyee has quit IRC02:26
*** rowleyaj has joined #openstack-meeting02:27
*** jlucci has joined #openstack-meeting02:29
*** markmcclain has joined #openstack-meeting02:29
*** markmcclain has quit IRC02:39
*** _ozstacker_ has quit IRC02:40
*** ozstacker has joined #openstack-meeting02:41
*** noslzzp has quit IRC02:50
*** noslzzp has joined #openstack-meeting02:52
*** fnaval_ has quit IRC02:54
*** koolhead17 has joined #openstack-meeting02:54
*** mauilion has quit IRC02:54
*** fnaval has joined #openstack-meeting02:54
*** ctracey has quit IRC02:56
*** ctracey has joined #openstack-meeting03:01
*** SergeyLukjanov has joined #openstack-meeting03:01
*** Swaminathan has quit IRC03:03
*** novas0x2a|laptop has quit IRC03:04
*** ashwini has quit IRC03:04
*** dwcramer has quit IRC03:08
*** reed has joined #openstack-meeting03:08
*** mikal has quit IRC03:10
*** pleia2 has quit IRC03:11
*** mikal has joined #openstack-meeting03:11
*** uvirtbot has quit IRC03:11
*** pleia2 has joined #openstack-meeting03:11
*** ryanpetrello has joined #openstack-meeting03:13
*** ryanpetrello has quit IRC03:13
*** jlucci has quit IRC03:15
*** adjohn_ has quit IRC03:15
*** rowleyaj has left #openstack-meeting03:18
*** ijw has quit IRC03:25
*** esker has joined #openstack-meeting03:27
*** esker has quit IRC03:27
*** esker has joined #openstack-meeting03:27
*** ayoung has quit IRC03:29
*** stevemar has joined #openstack-meeting03:31
*** anniec has joined #openstack-meeting03:33
*** Ramix has joined #openstack-meeting03:36
*** uvirtbot has joined #openstack-meeting03:36
*** anniec_ has joined #openstack-meeting03:39
*** anniec has quit IRC03:40
*** anniec_ is now known as anniec03:40
*** Mandell has joined #openstack-meeting03:46
*** MarkAtwood has quit IRC03:46
*** MarkAtwood has joined #openstack-meeting03:47
*** MarkAtwood has quit IRC03:52
*** danwent has joined #openstack-meeting03:54
*** yaguang has joined #openstack-meeting03:55
*** dwcramer has joined #openstack-meeting03:58
*** Ramix has quit IRC03:59
*** Ramix has joined #openstack-meeting04:00
*** Ramix has quit IRC04:04
*** amyt has joined #openstack-meeting04:05
*** fnaval_ has joined #openstack-meeting04:05
*** fnaval has quit IRC04:05
*** SergeyLukjanov has quit IRC04:07
*** Ramix has joined #openstack-meeting04:12
*** fnaval_ has quit IRC04:13
*** fnaval has joined #openstack-meeting04:14
*** resker has joined #openstack-meeting04:17
*** amyt has quit IRC04:17
*** anniec has quit IRC04:18
*** amyt has joined #openstack-meeting04:19
*** esker_ has joined #openstack-meeting04:20
*** amyt has quit IRC04:20
*** bdpayne has joined #openstack-meeting04:21
*** amyt has joined #openstack-meeting04:21
*** esker has quit IRC04:21
*** resker has quit IRC04:23
*** amyt has quit IRC04:23
*** amyt has joined #openstack-meeting04:24
*** Ramix has quit IRC04:24
*** nati_ueno has joined #openstack-meeting04:31
*** amyt has quit IRC04:31
*** amyt has joined #openstack-meeting04:32
*** koolhead17 has quit IRC04:33
*** esker_ has quit IRC04:35
*** amyt has quit IRC04:35
*** amyt has joined #openstack-meeting04:36
*** markpeek has joined #openstack-meeting04:37
*** resker has joined #openstack-meeting04:38
*** amyt has quit IRC04:38
*** amyt has joined #openstack-meeting04:39
*** resker has quit IRC04:42
*** stevemar has quit IRC04:44
*** amyt has quit IRC04:44
*** amyt has joined #openstack-meeting04:45
*** koolhead17 has joined #openstack-meeting04:46
*** amyt has quit IRC04:46
*** amyt has joined #openstack-meeting04:47
*** Ramix has joined #openstack-meeting04:49
*** glikson has joined #openstack-meeting04:52
*** Ramix has quit IRC04:54
*** ijw has joined #openstack-meeting04:55
*** topol has joined #openstack-meeting04:55
*** MarkAtwood has joined #openstack-meeting04:57
*** amyt has quit IRC04:57
*** amyt has joined #openstack-meeting04:57
*** sandywalsh has quit IRC04:58
*** ayurchen has quit IRC05:05
*** ayurchen has joined #openstack-meeting05:05
*** bdpayne has quit IRC05:07
*** amyt has quit IRC05:07
*** amyt has joined #openstack-meeting05:08
*** MarkAtwood has left #openstack-meeting05:09
*** amyt has quit IRC05:09
*** dwcramer has quit IRC05:09
*** amyt has joined #openstack-meeting05:10
*** sacharya has quit IRC05:11
*** amyt has quit IRC05:11
*** bdpayne has joined #openstack-meeting05:12
*** amyt has joined #openstack-meeting05:13
*** nati_ueno has quit IRC05:17
*** lloydde has joined #openstack-meeting05:20
*** amyt has quit IRC05:20
*** amyt has joined #openstack-meeting05:21
*** vipul is now known as vipul|away05:35
*** Mandell has quit IRC05:35
*** sandywalsh has joined #openstack-meeting05:36
*** sjing has joined #openstack-meeting05:41
*** vipul|away is now known as vipul05:41
*** ijw has quit IRC05:44
*** amyt has quit IRC05:44
*** amyt has joined #openstack-meeting05:45
*** sjing has quit IRC05:52
*** amyt has quit IRC05:52
*** amyt has joined #openstack-meeting05:53
*** sjing has joined #openstack-meeting05:54
*** amyt has quit IRC05:54
*** amyt has joined #openstack-meeting05:55
*** markpeek has quit IRC05:57
*** yaguang is now known as yaguang_afk05:57
*** sjing has quit IRC05:59
*** amyt has quit IRC05:59
*** sjing has joined #openstack-meeting05:59
*** amyt has joined #openstack-meeting06:00
*** amyt has quit IRC06:04
*** sjing has quit IRC06:07
*** garyk has joined #openstack-meeting06:09
*** adjohn has joined #openstack-meeting06:20
*** juice_otg has joined #openstack-meeting06:23
*** adjohn has quit IRC06:23
*** juice_ot_ has joined #openstack-meeting06:24
*** danwent has quit IRC06:26
*** juice_otg has quit IRC06:28
*** salmon_ has joined #openstack-meeting06:32
*** topol has quit IRC06:32
*** salmon_ has left #openstack-meeting06:33
*** koolhead17 has quit IRC06:36
*** juice_ot_ has quit IRC06:37
*** yuanz has joined #openstack-meeting06:45
*** koolhead17 has joined #openstack-meeting06:48
*** vipul is now known as vipul|away06:48
*** vipul|away is now known as vipul06:48
*** mkollaro has joined #openstack-meeting06:48
*** mkollaro has quit IRC06:48
*** nati_ueno has joined #openstack-meeting06:49
*** glikson has quit IRC06:51
*** jcoufal has joined #openstack-meeting06:54
*** jtomasek has joined #openstack-meeting06:56
*** yongli has joined #openstack-meeting06:58
*** bdpayne has quit IRC06:59
*** lloydde has quit IRC07:01
*** afazekas has joined #openstack-meeting07:06
*** ozstacker has quit IRC07:12
*** ozstacker has joined #openstack-meeting07:12
*** glikson has joined #openstack-meeting07:16
*** eglynn has joined #openstack-meeting07:17
*** FnordDownUnder has quit IRC07:19
*** shardy_afk is now known as shardy07:20
*** eglynn has quit IRC07:25
*** johnthetubaguy has joined #openstack-meeting07:28
*** mkollaro has joined #openstack-meeting07:29
*** salv-orlando has joined #openstack-meeting07:29
*** juice_otg has joined #openstack-meeting07:31
*** lloydde has joined #openstack-meeting07:31
*** adjohn has joined #openstack-meeting07:34
*** ndipanov has joined #openstack-meeting07:38
*** adjohn has quit IRC07:38
*** eglynn has joined #openstack-meeting07:39
*** lloydde has quit IRC07:41
*** Mandell has joined #openstack-meeting07:41
*** juice_otg has quit IRC07:44
*** jhenner has joined #openstack-meeting07:46
*** mkollaro has quit IRC07:47
*** psedlak has joined #openstack-meeting07:52
*** boris-42 has joined #openstack-meeting07:52
*** afazekas has quit IRC07:54
*** afazekas has joined #openstack-meeting07:54
*** jhenner has quit IRC07:57
*** jhenner has joined #openstack-meeting07:58
*** boris-42 has quit IRC08:01
*** ndipanov has quit IRC08:03
*** jcoufal has quit IRC08:05
*** jcoufal has joined #openstack-meeting08:06
*** kpavel has joined #openstack-meeting08:06
*** afazekas has quit IRC08:10
*** ndipanov has joined #openstack-meeting08:19
*** afazekas has joined #openstack-meeting08:22
*** nati_ueno has quit IRC08:26
*** nati_ueno has joined #openstack-meeting08:27
*** nati_ueno has quit IRC08:31
*** lloydde has joined #openstack-meeting08:32
*** alpha_ori has quit IRC08:32
*** alpha_ori has joined #openstack-meeting08:32
*** lloydde has quit IRC08:36
*** Mandell has quit IRC08:41
*** shengjie has joined #openstack-meeting08:49
*** jhenner has quit IRC08:59
*** jhenner has joined #openstack-meeting09:01
*** afazekas has quit IRC09:01
*** ndipanov has quit IRC09:08
*** boris-42 has joined #openstack-meeting09:12
*** ndipanov has joined #openstack-meeting09:22
*** gitanshi has joined #openstack-meeting09:32
*** lloydde has joined #openstack-meeting09:33
*** ryanpetrello has joined #openstack-meeting09:34
*** lloydde has quit IRC09:37
*** gitanshi has quit IRC09:40
*** gitanshi has joined #openstack-meeting09:41
*** gitanshi has joined #openstack-meeting09:41
*** zaro has quit IRC09:43
*** gitanshi has left #openstack-meeting09:44
*** gitanshi has joined #openstack-meeting09:44
*** ryanpetrello has quit IRC09:50
*** johnthetubaguy1 has joined #openstack-meeting09:51
*** afazekas has joined #openstack-meeting09:55
*** johnthetubaguy has quit IRC09:55
*** yaguang_afk has quit IRC10:07
*** mkollaro has joined #openstack-meeting10:14
*** koolhead17 has quit IRC10:16
*** koolhead17 has joined #openstack-meeting10:16
*** ozstacker has quit IRC10:18
*** ozstacker has joined #openstack-meeting10:19
*** alexpilotti has joined #openstack-meeting10:20
*** SergeyLukjanov has joined #openstack-meeting10:21
*** johnthetubaguy1 is now known as johnthetubaguy10:26
*** lloydde has joined #openstack-meeting10:33
*** dprince has joined #openstack-meeting10:34
*** lloydde has quit IRC10:38
*** koolhead17 has quit IRC10:45
*** koolhead17 has joined #openstack-meeting10:46
*** jcoufal has quit IRC10:46
*** jcoufal has joined #openstack-meeting10:49
*** dprince has quit IRC10:50
*** kirankv has joined #openstack-meeting10:50
*** beagles has joined #openstack-meeting10:59
*** topol has joined #openstack-meeting11:03
*** SergeyLukjanov has quit IRC11:04
*** gongysh has quit IRC11:16
*** Yada has joined #openstack-meeting11:16
*** SergeyLukjanov has joined #openstack-meeting11:29
*** dperaza has joined #openstack-meeting11:30
*** pcm__ has joined #openstack-meeting11:31
*** ayurchen has left #openstack-meeting11:32
*** dprince has joined #openstack-meeting11:32
*** ijw has joined #openstack-meeting11:33
*** lloydde has joined #openstack-meeting11:33
*** dperaza has quit IRC11:37
*** lloydde has quit IRC11:38
*** matiu has quit IRC11:38
*** ayurchen has joined #openstack-meeting11:39
*** mikal has quit IRC11:39
*** ayurchen has left #openstack-meeting11:40
*** mikal has joined #openstack-meeting11:41
*** dperaza has joined #openstack-meeting11:47
*** sandywalsh has quit IRC11:57
*** SergeyLukjanov has quit IRC11:58
*** SergeyLukjanov has joined #openstack-meeting11:59
*** ijw has quit IRC12:05
*** sandywalsh has joined #openstack-meeting12:10
*** sandywalsh has quit IRC12:10
*** sandywalsh has joined #openstack-meeting12:10
*** flaper87 has joined #openstack-meeting12:12
*** ryanpetrello has joined #openstack-meeting12:14
*** vlad-msc has joined #openstack-meeting12:20
*** primeministerp has quit IRC12:25
*** ryanpetrello has quit IRC12:26
*** vlad-msc has left #openstack-meeting12:27
*** SergeyLukjanov has quit IRC12:28
*** anniec has joined #openstack-meeting12:30
*** anniec_ has joined #openstack-meeting12:33
*** lloydde has joined #openstack-meeting12:34
*** anniec has quit IRC12:35
*** anniec_ is now known as anniec12:35
*** AlanClark has quit IRC12:35
*** SergeyLukjanov has joined #openstack-meeting12:37
*** adalbas has joined #openstack-meeting12:38
*** acfleury has joined #openstack-meeting12:38
*** ndipanov has quit IRC12:38
*** lloydde has quit IRC12:40
*** primeministerp has joined #openstack-meeting12:44
*** sacharya has joined #openstack-meeting12:50
*** ndipanov has joined #openstack-meeting12:51
*** dwcramer has joined #openstack-meeting12:56
*** martine has joined #openstack-meeting12:57
*** adalbas has quit IRC12:58
*** acfleury has quit IRC12:58
*** eharney has quit IRC13:03
*** acfleury has joined #openstack-meeting13:12
*** adalbas has joined #openstack-meeting13:12
*** radez_g0n3 is now known as radez13:13
*** salv-orlando has quit IRC13:16
*** rnirmal has joined #openstack-meeting13:24
*** ladquin_away is now known as ladquin13:28
*** lbragstad has joined #openstack-meeting13:28
*** mkollaro1 has joined #openstack-meeting13:28
*** mkollaro has quit IRC13:28
*** afazekas_ has joined #openstack-meeting13:29
*** afazekas_ has joined #openstack-meeting13:30
*** dwcramer has quit IRC13:30
*** afazekas has quit IRC13:31
*** jecarey has joined #openstack-meeting13:33
*** lloydde has joined #openstack-meeting13:34
*** changbl has quit IRC13:36
*** lloydde has quit IRC13:39
*** ayoung has joined #openstack-meeting13:40
*** eharney has joined #openstack-meeting13:40
*** ryanpetrello has joined #openstack-meeting13:47
*** boris-42 has quit IRC13:50
*** markmcclain has joined #openstack-meeting13:50
*** stevemar has joined #openstack-meeting13:51
*** sacharya has quit IRC13:52
*** AlanClark has joined #openstack-meeting13:52
*** maoy has joined #openstack-meeting13:55
*** markpeek has joined #openstack-meeting13:57
*** HenryG has joined #openstack-meeting13:59
*** topol has quit IRC14:03
*** ttx has quit IRC14:03
*** ttx has joined #openstack-meeting14:06
*** ttx has joined #openstack-meeting14:06
*** mrodden has joined #openstack-meeting14:06
*** acfleury has quit IRC14:09
*** adalbas has quit IRC14:10
*** ayoung has quit IRC14:12
*** salv-orlando has joined #openstack-meeting14:19
*** ttx has quit IRC14:20
*** ttx has joined #openstack-meeting14:21
*** ttx has joined #openstack-meeting14:21
*** adalbas has joined #openstack-meeting14:23
*** dwcramer has joined #openstack-meeting14:24
*** acfleury has joined #openstack-meeting14:24
*** ayoung has joined #openstack-meeting14:27
*** jaypipes has joined #openstack-meeting14:28
*** acfleury has quit IRC14:28
*** hartsocks has joined #openstack-meeting14:32
*** garyk has quit IRC14:33
*** amyt has joined #openstack-meeting14:33
*** spzala has joined #openstack-meeting14:33
*** ndipanov has quit IRC14:36
*** topol has joined #openstack-meeting14:36
*** zyluo has joined #openstack-meeting14:39
*** diogogmt has joined #openstack-meeting14:41
*** dolphm has joined #openstack-meeting14:42
*** fnaval has quit IRC14:42
*** fnaval has joined #openstack-meeting14:43
*** diogogmt has quit IRC14:47
*** fnaval has quit IRC14:47
*** apmelton1 has quit IRC14:48
*** ndipanov has joined #openstack-meeting14:48
*** diogogmt has joined #openstack-meeting14:49
*** boris-42 has joined #openstack-meeting14:50
*** SergeyLukjanov has quit IRC14:50
*** salv-orlando_ has joined #openstack-meeting14:50
*** mattray has joined #openstack-meeting14:50
*** mrodden has quit IRC14:50
*** salv-orlando has quit IRC14:53
*** salv-orlando_ is now known as salv-orlando14:54
*** otherwiseguy has joined #openstack-meeting14:57
*** garyk has joined #openstack-meeting14:58
*** woodspa has quit IRC14:58
*** lbragstad has quit IRC14:59
*** danwent has joined #openstack-meeting15:00
*** kirankv has quit IRC15:01
*** woodspa has joined #openstack-meeting15:01
*** changbl has joined #openstack-meeting15:02
*** jlucci has joined #openstack-meeting15:04
*** lbragstad has joined #openstack-meeting15:04
*** mkollaro1 has quit IRC15:04
*** salv-orlando has quit IRC15:07
*** mrodden has joined #openstack-meeting15:07
*** markmcclain has quit IRC15:10
*** jcoufal has quit IRC15:12
*** jamespage_ has joined #openstack-meeting15:13
*** ttrifonov is now known as ttrifonov_zZzz15:13
*** flaper87 has quit IRC15:15
*** mkollaro has joined #openstack-meeting15:17
*** jamespage_ has quit IRC15:17
*** SergeyLukjanov has joined #openstack-meeting15:19
*** amyt has quit IRC15:19
*** amyt has joined #openstack-meeting15:20
*** dwcramer has quit IRC15:20
*** lloydde has joined #openstack-meeting15:20
*** zul has joined #openstack-meeting15:21
*** sacharya has joined #openstack-meeting15:22
*** Mandell has joined #openstack-meeting15:27
*** zyluo has quit IRC15:27
*** adjohn has joined #openstack-meeting15:30
*** dwcramer has joined #openstack-meeting15:32
*** ayoung has quit IRC15:33
*** writerDiane has joined #openstack-meeting15:34
*** dtynan has left #openstack-meeting15:37
*** hemna has joined #openstack-meeting15:39
*** lloydde has quit IRC15:40
*** lloydde has joined #openstack-meeting15:43
*** ociuhandu has quit IRC15:46
*** MarkAtwood has joined #openstack-meeting15:48
*** dperaza has quit IRC15:49
*** bdpayne has joined #openstack-meeting15:49
*** fnaval has joined #openstack-meeting15:49
*** Mandell has quit IRC15:50
*** ayoung has joined #openstack-meeting15:50
*** salv-orlando has joined #openstack-meeting15:53
*** armax has joined #openstack-meeting15:54
*** mattray has quit IRC15:59
*** ayoung has quit IRC16:00
*** ayoung has joined #openstack-meeting16:01
*** jcoufal has joined #openstack-meeting16:01
*** gyee has joined #openstack-meeting16:02
*** zaro has joined #openstack-meeting16:04
*** ttrifonov_zZzz is now known as ttrifonov16:04
*** salv-orlando has quit IRC16:06
*** mdenny has joined #openstack-meeting16:07
*** randy_perryman has joined #openstack-meeting16:10
*** kpavel has quit IRC16:10
*** danwent has quit IRC16:11
*** dolphm has quit IRC16:13
*** danwent has joined #openstack-meeting16:16
*** ttrifonov is now known as ttrifonov_zZzz16:16
*** hub_cap has left #openstack-meeting16:17
*** dprince has quit IRC16:19
*** salv-orlando has joined #openstack-meeting16:20
*** dolphm has joined #openstack-meeting16:22
*** zul has quit IRC16:22
*** lloydde has quit IRC16:22
*** lbragstad has quit IRC16:23
*** ttrifonov_zZzz is now known as ttrifonov16:24
*** jamespage_ has joined #openstack-meeting16:27
*** lbragstad has joined #openstack-meeting16:27
*** zul has joined #openstack-meeting16:28
*** jamespage_ has quit IRC16:30
*** mrodden has quit IRC16:31
*** mrodden has joined #openstack-meeting16:34
*** SergeyLukjanov has quit IRC16:34
*** glikson has quit IRC16:36
*** adjohn has quit IRC16:36
*** salv-orlando has quit IRC16:40
*** jasondotstar has joined #openstack-meeting16:41
*** salv-orlando has joined #openstack-meeting16:42
*** ttrifonov is now known as ttrifonov_zZzz16:43
*** garyk has quit IRC16:43
*** mattray has joined #openstack-meeting16:43
*** torandu has joined #openstack-meeting16:45
*** pentae has joined #openstack-meeting16:45
*** ndipanov has quit IRC16:45
*** dperaza has joined #openstack-meeting16:46
*** ravikumar_hp has joined #openstack-meeting16:46
*** salv-orlando has quit IRC16:47
*** anniec has quit IRC16:47
*** ndipanov has joined #openstack-meeting16:47
*** johnthetubaguy has quit IRC16:50
*** salv-orlando has joined #openstack-meeting16:51
*** markmcclain has joined #openstack-meeting16:53
*** terry7 has joined #openstack-meeting16:54
*** ttrifonov_zZzz is now known as ttrifonov16:54
*** eglynn has quit IRC16:56
*** malini has joined #openstack-meeting16:57
*** garyk has joined #openstack-meeting16:58
*** dwcramer has quit IRC16:59
*** mlavalle has joined #openstack-meeting17:00
*** ashwini has joined #openstack-meeting17:01
*** dwalleck has joined #openstack-meeting17:02
*** afazekas_ is now known as afazekas17:02
sdaguewho's around for the qa meeting?17:02
afazekashi17:02
mlavalleI am17:02
psedlakhi17:03
ravikumar_hphi17:03
malinihi17:03
dwalleckhere17:03
sdague#startmeeting qa17:03
openstackMeeting started Thu May  9 17:03:29 2013 UTC.  The chair is sdague. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: qa)"17:03
openstackThe meeting name has been set to 'qa'17:03
sdague#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_May_9_2013_meeting17:04
sdagueok, proposed agenda for today, lets get rolling17:04
sdague#topic Blueprint check in for everyone with H1 blueprints17:04
*** openstack changes topic to "Blueprint check in for everyone with H1 blueprints (Meeting topic: qa)"17:04
sdague#link https://launchpad.net/tempest/+milestone/havana-117:04
*** adjohn has joined #openstack-meeting17:05
sdagueso we have a few of those blueprints with a status of Unknown, we're half way through H1, anyone have updates to share?17:05
*** mkollaro has quit IRC17:05
*** nati_ueno has joined #openstack-meeting17:05
sdagueguess not :)17:06
ravikumar_hpout of 15 , 2 blueprints are already implemented17:06
sdaguethe directory restructure bits are underway17:06
sdague#link https://review.openstack.org/#/q/topic:bp/tempest-repo-restructure,n,z17:07
sdaguewould appreciate some reviews so we can keep those moving17:07
*** hurricanerix has joined #openstack-meeting17:07
ravikumar_hpsdague: I proposed some changes. can you address that?17:07
sdagueravikumar_hp: proposed where?17:07
ravikumar_hpas review for patch 3/417:07
ravikumar_hphttps://review.openstack.org/#/c/28453/17:08
*** jamespage_ has joined #openstack-meeting17:08
sdagueok, so scenario tests may be part of the gate17:08
sdaguehonestly, right now, except for the stress directory, we're not kicking anything out of the gate by default17:09
sdaguethis is about making what we have in tree already clearer17:09
sdagueso it's easier for people to extend and contribute to17:09
sdagueit's also subject to evolution over time, but we needed a starting place17:09
afazekasI wonder can we extend the stress tests to collect performance data ?17:10
sdagueafazekas: probably17:10
sdaguethat would be a good exercise17:10
*** salv-orlando has quit IRC17:11
sdagueok, but the series needs at least another +2 to move it forward, so that would be appreciated if people are good with it17:11
*** dprince has joined #openstack-meeting17:11
*** masayukig has joined #openstack-meeting17:11
afazekasProbably I can add some system tap scripts to the tools/ folder for tracing same kernel event , for example for cpu usage accounting17:11
sdagueany other blueprint updates from the list?17:11
sdagueotherwise I'll jump to next topic17:11
ravikumar_hpok17:11
sdague#topic Obsoleting blueprints in new/unknown with no series nomination17:12
*** openstack changes topic to "Obsoleting blueprints in new/unknown with no series nomination (Meeting topic: qa)"17:12
*** adjohn has quit IRC17:12
sdagueok, so we said that we'd clean up the blueprints, and drop everything that people didn't series nominate (with a milestone)17:12
sdagueI'm going to hold folks to that tomorrow17:12
sdaguehttps://blueprints.launchpad.net/tempest is the whole list, I expect it to shrink a bunch17:13
sdagueso if there is a blueprint you are actually going to champion, please propose for a havana milestone17:13
*** donaldngo_hp has joined #openstack-meeting17:14
sdaguethere are also way too many Quantum blueprints in there, do we have a volunteer to consolodate them a little?17:14
mlavallesdague: I can do that17:14
sdaguemlavalle: thank you!17:14
sdague#action mlavalle to consolidate tempest blueprints17:15
sdague#action mlavalle to consolidate tempest quantum blueprints17:15
sdaguemlavalle: ping me in -qa if there is anything you need to get that done17:15
mlavallesdague: ok17:15
sdaguelast scheduled topic17:16
sdague#topic Critical reviews tied to blueprints17:16
*** openstack changes topic to "Critical reviews tied to blueprints (Meeting topic: qa)"17:16
sdaguenow is fair game for any reviews you want to pimp that are tied to a blueprint :)17:16
sdagueor a bug17:16
davidkranzstress test add/remove17:16
sdaguedavidkranz: cool, url?17:16
*** danwent has quit IRC17:17
*** RAX_Sam has joined #openstack-meeting17:17
davidkranzhttps://review.openstack.org/#/c/28554/17:17
davidkranzhttps://review.openstack.org/#/c/28553/17:17
sdaguealso can we get a blueprint for it? just to help us keep track of things. As one of our goals out of summit was to be more organized :)17:17
*** salv-orlando has joined #openstack-meeting17:17
davidkranzhttps://blueprints.launchpad.net/tempest/+spec/stress-tests17:17
afazekas'There may be cases where multiple actions interact with each other'17:17
sdaguesweet17:17
afazekasdavidkranz: how the action will be able to interact with each other ?17:18
sdaguedavidkranz: if you put bp:stress-tests in the commit messages, they'll auto link back to that as well. Useful for keeping track17:18
sdagueI'll take a look at the stress tests again this afternoon17:18
davidkranzsdague: Thx17:18
sdagueany others from folks?17:18
sdagueok, we'll assume not17:19
davidkranzafazekas: I don't have a detailed scenario.17:19
sdague#topic open discussion17:19
*** openstack changes topic to "open discussion (Meeting topic: qa)"17:19
davidkranzafazekas: The point was just that when the killing starts, the test is already complete.17:19
psedlakare there any rules for contributing or backporting to tempest/stable-*?17:20
sdaguepsedlak: my feeling is that we should be the same as other projects17:20
sdagueso17:20
sdague1) it needs a bug17:20
sdague2) it needs to be fixed in master first17:20
davidkranzsdague: Gotta go again17:20
*** longshot_rax has joined #openstack-meeting17:20
sdague3) the stable patch should be a cherry pick of master17:21
sdaguewe are definitely only fixing bugs in stable, not adding new test cases17:21
*** shengjie has quit IRC17:22
psedlaksdague: so it's not possible to get new test cases covering some stable feature added to master and backported to stable?17:22
sdagueI don't think so, as it would have implications on the gate17:22
sdagueI think we can take it as a case by case basis17:22
sdaguebut my instinct would be not to do that17:23
psedlaksdague: what kind of 'implications'?17:23
sdaguewe are changing the criteria for the stable gate17:23
*** amyt has quit IRC17:23
afazekasis jaypipes here ?17:23
psedlaksdague: like not covering thinks that are actually already in use/production ... that should not break things much/at all ...17:24
*** amyt has joined #openstack-meeting17:24
*** Mandell has joined #openstack-meeting17:24
sdaguepsedlak: it's always fair to propose a change like that, and see what folks think17:24
sdaguehonestly, until recently there wasn't any backport activity to tempest17:24
*** jose-idar has joined #openstack-meeting17:24
sdagueso it's sort of a new problem for us to figure out as we go17:24
sdaguedefinitely needs to be artifact tracked though17:25
*** danwent has joined #openstack-meeting17:25
maurosrI have one point/question to you guys17:25
maurosrsdague and guys: cyeoh and I were talking how we're going to test nova-api-v3 in tempest during our port process to v3 tree... there are other projects with 2 apis right? how is the process to test those cases?17:25
psedlaksdague: ok, thanks17:25
afazekassdague: I am planing to backport tests to the folsom and grizzly branches17:25
sdaguemaurosr: we just have both versions in tree17:25
sdagueafazekas: folsom? really?17:26
afazekasyes :)17:26
sdagueok :)17:26
sdaguewell lets start with some detailed bugs17:26
*** mattray has quit IRC17:26
maurosrsdague: so no problem duplicating the number of tests then?17:26
sdaguemaurosr: for now, no. but we're going to need to get a little stricter on what we are accepting in the gate17:27
sdaguebecause we're at 45m right now17:27
sdagueso it may be that not all of them get run in the gate, and we go to periodic runs17:27
sdagueespecially for experimental APIs17:27
maurosrright, make sense17:28
maurosrsdague: do I need to write a bp about it?17:28
*** ttrifonov is now known as ttrifonov_zZzz17:28
*** mattray has joined #openstack-meeting17:28
sdaguefor nova v3 tests? yes please17:28
sdagueit helps keep us organized17:28
maurosrok, thanks17:28
sdagueother discussion topics?17:29
sdaguegoing once...17:29
afazekasWe should document somehow the existing test cases17:29
*** ttrifonov_zZzz is now known as ttrifonov17:29
sdagueafazekas: sure, can you explain more what you mean?17:30
afazekasFor new camers it is difficult to see what is not tested by tempest17:30
*** SergeyLukjanov has joined #openstack-meeting17:30
sdaguedo you have a suggestion about how we could do that well?17:31
afazekasThe RTFS is not a good answer for everyone17:31
sdagueI definitely agree with you, I've just not come up with a good idea there17:31
afazekassdague: I think we should use the wiki or an rst files in the repository17:31
sdaguerst file in the repo sounds like a good idea, then when people make commits they could take stuff off the list17:32
afazekasI do not have exect plans, may be we should discuss it on the next meeting17:32
sdagueafazekas: sure17:32
sdagueyou want to take an action to come up with a proposal to discuss for the next meeting?17:32
afazekassdague: cool17:32
sdagueor we can do it on the mailing list17:32
*** HenryG has quit IRC17:32
sdagueI think it's a good goal17:32
afazekasWe should start in the ML17:33
ravikumar_hpyes17:33
sdagueok, lets do that. I'll give you the todo to start the thread17:33
dwalleck+117:33
sdague#action afazekas to start mailing list thread on documenting test cases we need for new contributors17:33
ravikumar_hpas routine - Email on Thursday after this meeting ,and due by Wednesday17:33
sdagueany other topics?17:34
sdaguegoing once...17:34
sdaguegoing twice...17:35
sdagueok, lets call it17:35
sdague#endmeeting17:35
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:35
openstackMeeting ended Thu May  9 17:35:17 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-05-09-17.03.html17:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-05-09-17.03.txt17:35
openstackLog:            http://eavesdrop.openstack.org/meetings/qa/2013/qa.2013-05-09-17.03.log.html17:35
sdaguethanks folks17:35
*** RAX_Sam has quit IRC17:35
*** malini has left #openstack-meeting17:35
*** longshot_rax has quit IRC17:35
*** dwalleck has quit IRC17:35
*** ravikumar_hp has quit IRC17:36
*** donaldngo_hp has quit IRC17:36
*** zul has quit IRC17:37
*** jhenner has quit IRC17:37
*** psedlak has quit IRC17:38
*** hurricanerix has quit IRC17:39
*** jimbaker has joined #openstack-meeting17:39
*** jamespage_ has quit IRC17:40
*** afazekas has quit IRC17:43
*** ttrifonov is now known as ttrifonov_zZzz17:46
*** bruce_ has joined #openstack-meeting17:46
*** martine has quit IRC17:49
*** glikson has joined #openstack-meeting17:50
*** Shree-HP has joined #openstack-meeting17:50
*** jamespage_ has joined #openstack-meeting17:50
*** Bruce__ has joined #openstack-meeting17:52
*** jlucci has quit IRC17:53
*** jlucci has joined #openstack-meeting17:53
*** Mandell has quit IRC17:53
*** zzs has joined #openstack-meeting17:54
*** Bruce__ has quit IRC17:54
*** bruce_ has quit IRC17:54
*** chair6 has joined #openstack-meeting17:54
*** Mandell has joined #openstack-meeting17:54
*** bpb has joined #openstack-meeting17:55
*** rnirmal has quit IRC17:55
*** jamespage_ has quit IRC17:57
*** mlavalle has quit IRC17:58
*** ttrifonov_zZzz is now known as ttrifonov17:58
bdpayne#startmeeting OpenStack Security Group18:00
openstackMeeting started Thu May  9 18:00:04 2013 UTC.  The chair is bdpayne. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: OpenStack Security Group)"18:00
openstackThe meeting name has been set to 'openstack_security_group'18:00
bdpaynegood morning / afternoon / evening to OSSG18:00
hyakuheiHey bdpayne18:00
bdpaynelet's get started with a role call18:00
bdpayneBryan from Nebula is here18:00
bpbHi bdpayne18:01
hyakuheiRob from HP here.18:01
bpbBruce from APL18:01
*** rwsu_ has joined #openstack-meeting18:01
*** markmcclain has quit IRC18:01
bdpayneanyone else here for the OSSG meeting?18:02
*** rellerreller has joined #openstack-meeting18:02
chair6Jamie from HP18:02
bdpaynewell, hi everyone18:02
*** HenryG has joined #openstack-meeting18:02
bdpaynethanks for attending18:02
bdpaynelet's get started18:03
bdpayneanyone have an item to put on the agenda?18:03
hyakuheiNothing new18:03
*** writerDiane has quit IRC18:03
*** rwsu has quit IRC18:04
noslzzphere..18:04
bpbHow about the pros and cons of a centralized message security key server -18:04
pentaeHeath here from HP also18:04
bdpayneok, I'd like to discuss the documentation sprint, open security tickets, and get updates on some ongoing projects (volume encryption, key manager, rpc security)18:05
bdpaynebob sounds good, we'll add that too18:05
bdpaynethat's bpb18:05
bpbyes18:05
bdpayne#topic documentation sprint update18:05
*** openstack changes topic to "documentation sprint update (Meeting topic: OpenStack Security Group)"18:05
bdpayneJust a quick update on the doc sprint18:06
bdpaynelooks like we are locked in for June 24-2818:06
bdpaynewill be happening in Maryland18:06
bdpayneI'm working to finalize the attendee list this week18:06
hyakuheiSounds good18:06
noslzzpYep.18:07
bdpayneb/c it will be time for people to arrange travel shortly18:07
*** markmcclain has joined #openstack-meeting18:07
bdpayneif you'd like to be involved and are not already chatting with me, please drop me an email18:07
bdpayneany questions about the doc sprint?18:07
bdpayneexcellent, I'll move ahead18:08
bdpayne#topic open security tickets18:08
*** openstack changes topic to "open security tickets (Meeting topic: OpenStack Security Group)"18:08
bdpaynehttps://bugs.launchpad.net/openstack/+bugs?field.tag=security18:08
bdpaynethat link is a useful one18:08
*** IlyaE has joined #openstack-meeting18:08
bdpayneif you're on the openstack-security mailing list, you'll be seeing chatter on some of these too18:08
hyakuheiThere's only 1918:08
hyakuheiA few of which are due to be closed off.18:09
bdpayneyep18:09
bdpaynethis is a great place for people to contribute to the discussion18:09
bdpayneif you'd like to do some security reviews, etc18:09
bdpayneso I just wanted to call it out18:09
bdpayne#topic ongoing projects18:10
*** openstack changes topic to "ongoing projects (Meeting topic: OpenStack Security Group)"18:10
*** jhullinge has joined #openstack-meeting18:10
hyakuheiI don't suppose eric is lurking here somewhere?18:10
bdpaynecould we get some updates on volume encryption, key management, and the roc security discussions?18:10
bdpayneif you're involved in any of the above, please just chime in18:10
hyakuheiI heckle a little on the first two18:11
rellerrellerVolume encryption is progressing18:11
rellerrellerWe are still shooting for Havana-1.  We are deciding on the interface for the key manager.18:12
*** mdomsch has joined #openstack-meeting18:12
rellerrellerOur first release will use a stubbed out KM for POC purposes.  Then we plan to integrate with barbican when they have a working prototype.18:12
hyakuheiI think that's really exciting work. Do you have a documented set of assurance requirements that you're meeting?18:12
rellerrellerNo, but you can email me more about what you are looking for.18:13
rellerrellerI think the barbican/KM team is looking to have something by Havana-318:13
hyakuheii.e protect disks if they're physicaly taken away from the DC etc? I ask because I'm already getting questions from customers about this stuff and while I can tell them abit about what you're doing it'd be good to have a better picture18:13
*** Mandell has quit IRC18:14
hyakuheirellerreller: ping me your email and I'll follow-up18:14
bdpayneI'd be interested in that too18:14
*** ladquin is now known as ladquin_brb18:14
rellerrellerOK, I understand what you mean.  We can get in contact with you to see if we can get you something.18:14
bdpayneperhaps it could just be done on the openstack-security list?18:14
bdpayneor at least loop me in ;-)18:14
rellerrellerI think that would be ok.18:14
rellerrellerWill do18:15
hyakuheiSure18:15
*** salv-orlando has quit IRC18:15
bdpaynegreat, so can anyone speak to the rpc discussions ?18:16
*** eglynn has joined #openstack-meeting18:16
hyakuheiI've not been involved in that for the last week. I've still got a bunch of concerns. I was hoping Eric might be here.18:17
bpbThe immediate need for secure RPC lends itself to a customized local key manager, but the design could include barbican later.  Since the keys are short lived, just curious how folks feel if this make sense?18:17
hyakuheiOk, lets see if we can get some discussion of the RPC stuff on openstack-security ML18:17
hyakuheibpb: define short lived?18:18
bdpaynebob can you elaborate?18:18
bpbShort lived meaning maybe a few hours?  point of discussion18:18
*** reed has quit IRC18:18
bdpayne(sorry, my client keeps autocorrecting bpb and bob)18:18
bpbThere's an opportunity to build an interface for barbican, but the use case needs to make sense.18:19
bdpaynebpb can give some context about how these keys are being used?18:19
*** jtomasek has quit IRC18:19
hyakuheiI don't think you can because that's not been worked out yet18:19
bpbThere are separate keys used for the RPC authentication (each direction) and optional encryption (each direction)18:20
hyakuheiThe CMS proposal and the two-key AES symettric are both on the table18:20
*** mlavalle has joined #openstack-meeting18:20
bdpaynegot it18:20
hyakuheiboth have (I think) quite different key requirements18:21
*** mlavalle has left #openstack-meeting18:21
bdpaynethat email thread has scared me as I haven't had the time to keep up with it so now I have a pretty big backlog of reading to do18:21
hyakuheiboth of which are largely invalidated without some sort of host attestation18:21
*** lloydde has joined #openstack-meeting18:21
hyakuheiYeah it's pretty horrible18:21
bpbI think it's different also, and it makes sense from efficiency persective to have these separate18:21
hyakuheiTo have what separate bpb ?18:22
bpbSeparate key managers18:22
hyakuheiSure, we're all about choice after all18:22
bpbSo we need to consider some use cases to support different types of key managers I think18:23
bdpayneperhaps we also need to lay down what we are and are not trying to achieve with the rpc security?18:24
*** Mandell has joined #openstack-meeting18:24
hyakuheiyarp18:24
bpbCharacterizing the threats would be a good start18:24
*** masayukig has quit IRC18:25
hyakuheiThat sounds like an action to me18:25
bdpayne#action guide the rpc discussion with some actual threat models18:26
bdpaynevery well then18:26
bdpayneanything else for today?18:26
randy_perryman:q18:26
bdpaynewell, thanks for stopping by18:27
bdpaynehave a great day everyone18:27
bdpayne#endmeeting18:27
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"18:27
openstackMeeting ended Thu May  9 18:27:52 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-05-09-18.00.html18:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-05-09-18.00.txt18:27
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_security_group/2013/openstack_security_group.2013-05-09-18.00.log.html18:27
*** jhullinge has quit IRC18:28
*** randy_perryman has quit IRC18:28
*** chair6 has left #openstack-meeting18:29
*** ttrifonov is now known as ttrifonov_zZzz18:31
*** jaypipes has quit IRC18:31
*** rellerreller has quit IRC18:31
*** mtesauro has joined #openstack-meeting18:32
*** mtesauro has left #openstack-meeting18:33
*** writerDi_ has joined #openstack-meeting18:33
*** writer___ has joined #openstack-meeting18:33
*** zul has joined #openstack-meeting18:34
*** ttrifonov_zZzz is now known as ttrifonov18:36
*** jaypipes has joined #openstack-meeting18:36
*** writerDi_ has quit IRC18:38
*** IlyaE has quit IRC18:38
*** markpeek has quit IRC18:39
*** martine has joined #openstack-meeting18:42
*** danwent has quit IRC18:43
zynzelire18:43
*** eharney has quit IRC18:43
*** Shree-HP has quit IRC18:45
*** Yada has quit IRC18:45
*** novas0x2a|laptop has joined #openstack-meeting18:46
*** mkollaro has joined #openstack-meeting18:46
*** eharney has joined #openstack-meeting18:46
*** eharney has quit IRC18:46
*** eharney has joined #openstack-meeting18:46
*** danwent has joined #openstack-meeting18:50
*** lloydde has quit IRC18:51
*** eharney has quit IRC18:52
simobdpayne: sorry, didn;t know there was OSSG security meeting today, or I could have chimed in19:00
simobdpayne: I guess I'll subscribe to openstack-security and contribute there where I can19:00
*** dwcramer has joined #openstack-meeting19:02
*** zul has quit IRC19:05
*** IlyaE has joined #openstack-meeting19:06
*** jose-idar has left #openstack-meeting19:07
*** vipul is now known as vipul|away19:09
*** vipul|away is now known as vipul19:09
*** jcoufal has quit IRC19:09
*** dolphm has quit IRC19:12
*** spzala has quit IRC19:12
*** nati_ueno has quit IRC19:13
*** dperaza has quit IRC19:17
*** lloydde has joined #openstack-meeting19:18
*** lloydde has quit IRC19:20
*** lloydde has joined #openstack-meeting19:20
*** Swami has joined #openstack-meeting19:20
*** Swami has left #openstack-meeting19:22
*** garyk has quit IRC19:23
*** vipul is now known as vipul|away19:24
*** dperaza has joined #openstack-meeting19:25
*** sandywalsh has quit IRC19:34
*** manip_ has joined #openstack-meeting19:36
*** manip_ has quit IRC19:38
*** manip_ has joined #openstack-meeting19:38
*** manip_ has quit IRC19:40
*** rnirmal has joined #openstack-meeting19:44
*** mkollaro has quit IRC19:44
*** manip has joined #openstack-meeting19:45
*** manip has quit IRC19:46
*** sandywalsh has joined #openstack-meeting19:46
*** salv-orlando has joined #openstack-meeting19:48
*** salv-orlando_ has joined #openstack-meeting19:51
*** adrian_otto has joined #openstack-meeting19:52
*** mattray has quit IRC19:52
*** salv-orlando has quit IRC19:53
*** salv-orlando_ is now known as salv-orlando19:53
*** salv-orlando_ has joined #openstack-meeting19:54
*** salv-orlando has quit IRC19:57
*** salv-orlando_ is now known as salv-orlando19:57
*** pcm__ has quit IRC20:00
harlowja#startmeeting state-management-goodness20:00
openstackMeeting started Thu May  9 20:00:44 2013 UTC.  The chair is harlowja. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: state-management-goodness)"20:00
openstackThe meeting name has been set to 'state_management_goodness'20:00
harlowjahowdy everyone!20:00
changblhello~20:01
harlowjaanyone interesting in state management stuff (previously orchestration) let me know20:01
harlowja*rollcount20:01
*** esheffield has joined #openstack-meeting20:01
harlowja*role count i mean, ha20:01
hemnasup20:01
harlowjaso today i might have some what of an agenda :)20:02
adrian_ottohi20:02
harlowjahowdy20:02
esheffieldhello20:02
harlowja#link https://wiki.openstack.org/wiki/Meetings/StateManagement#Agenda_for_next_meeting20:02
*** HenryG has quit IRC20:03
*** vipul|away is now known as vipul20:03
* alaski lurks20:03
harlowjaso i was thinking about how to better define what i and others are trying to do, does that seem like it would help others :)20:03
* sandywalsh stalks alaski20:03
harlowjasince there are many wikis, and not everyone gets the time to read them, so a TLDR might be useful20:04
harlowjathen we can talk about some of the primitives that i put up, some of the placement of this 'taskflow' library20:04
harlowjaand discuss on some of the ML topics that were brought up regarding usage, core people support and such20:05
harlowjaand then anything else people want to talk about20:05
harlowjasound good?20:05
changblok20:05
harlowja#topic summary20:05
*** openstack changes topic to "summary (Meeting topic: state-management-goodness)"20:05
*** dprince has quit IRC20:05
harlowjaso the TLDR version that i have sorta been thinking about is….20:06
*** topol has quit IRC20:06
*** lloydde has quit IRC20:07
*** glikson has quit IRC20:07
harlowjabasically alot of actions that occur in various openstack projects can be simplified into a set of actions on resources (virtual or real) and states of those resources, such things could be called workflows ontop of said resources to fullfill said action20:07
maoyhola20:07
maoyi thought we liked "taskflow" instead of workflow from last week. :) anyway. keeping going harlowja~20:08
harlowjasorry, just giving an overview TLDR of my whole grand vision thingy :-P20:09
harlowjathx20:09
harlowjadue to the evolutionary development process that openstack has gone through there hasn't be a strong focus on this simplification into actions and states, just due to the organic growth of the different openstack core projects, the underlying code is there to do most of the actions and states but the simplification into actions and states hasn't really occured, which is nothing to be ashamed of20:09
*** [1]glikson has joined #openstack-meeting20:10
harlowjaso my idear was to move toward said simplification, which is starting to occur for example with nova conductor work, but instead of just moving code around also rethink some of the primitives that are needed to structure these actions and states into a model that when simplified allows for advanced things to occur on said actions and states20:11
*** [1]glikson is now known as glik20:11
harlowjataskflow, at least from what i think is the foundation of said work20:11
*** esker has joined #openstack-meeting20:11
harlowjaso thats my TLDR summary, haha20:11
harlowja*i hope that made it a little more understandable20:12
harlowjamaoy and changbl  have done similar work i think in there previous at&t research (which was neat)20:12
*** toanster has quit IRC20:12
changblwhich project are we gonna start with? Nova, Oslo, or Heat?20:13
harlowjaso thats a very interesting question20:13
hemnaDo you have a BP on how you are going to go about simplifying things?20:13
*** AlanClark has quit IRC20:13
harlowjathe amount of info doesn't really fit in one BP :)20:14
hemnaWe in Cinder are interested in state management as well and are looking at a "state machine/object" as well20:14
harlowja#link https://wiki.openstack.org/wiki/StructuredStateManagement is sorta my entry point into this20:14
harlowjahemna i think alot of core projects want this, or at least want to get to something like this20:14
adrian_ottoI edited that yesterday to add a link to the primitives document in the bottom section20:14
*** bpb has quit IRC20:14
harlowjaadrian_otto thanks20:15
adrian_ottohemna: have you seen that yet?20:15
hemnanot yet20:15
*** glik has quit IRC20:15
hemnathanks for the link20:15
adrian_ottohttps://wiki.openstack.org/wiki/StructuredWorkflowPrimitives20:15
adrian_ottothat's a pretty breif description of what gets built first20:15
harlowjasure, so placement is a very good question and releates a little bit to adrian_otto and similar conversations on the ML20:15
maoyso, from the mailing list discussion, it seems to be prefered to not start from Oslo, then move to Oslo20:15
*** spzala has joined #openstack-meeting20:16
adrian_ottothis will definitely end up in Oslo20:16
adrian_ottothere is no doubt. It's just a matter of when it's at the right maturity level to enter there.20:16
harlowjaagreed20:16
maoywe just need to figure out which non-oslo to begin with20:16
maoyheat, cinder, nova?20:16
jgriffithcinder :)20:16
maoyreddwarf?20:16
hemna:)20:16
harlowjaand i think myself and others want to get it into oslo, but there is still alot of experimentation and work to get it to that stage i think20:17
maoyjgriffith: great!20:17
adrian_ottoRedDwarf can use it probably sooner than Heat will be ready. That's my sense of it.20:17
jgriffithmaoy: harlowja what about a joint nova/cinder first round20:17
harlowjaso the question is what can be done to do heat, cinder, nova, reddwarf at once :)20:17
jgriffithafter that's proven out a bit we push to oslo20:17
*** anniec has joined #openstack-meeting20:17
adrian_ottowell, even before that possible20:17
jgriffithharlowja: insists on asking hard questions20:17
harlowjahaha20:17
adrian_ottowe just need it in one project, and a pull request for a second20:17
adrian_ottobut let's not put the cart before the horse20:18
jgriffithadrian_otto: that's fine but I think we need some up front coordination and collab on the design20:18
hemnacinder has a BP for a "state machine/object" for Havana.  https://blueprints.launchpad.net/cinder/+spec/cinder-state-machine20:18
adrian_ottoI'd like to take a moment to see if the current plan would meet Cinder's needs.20:18
*** toanster has joined #openstack-meeting20:18
harlowjahemna interesting, did not know about that20:18
harlowjaso a potential plan could be…20:18
hemnaIt's not much, mostly a placeholder for a desired state mgmt for cinder20:19
jgriffithadrian_otto: sorry I was late, is there a wiki or some docs on the current plan you referred to?20:19
*** toanster has quit IRC20:19
harlowjasay we form a group of devs that want to work on this, have active core members of said sub-projects involved (maybe not coding it, but involved) and start said project in stackforge to encourage rapid development on said project20:19
hemnajgriffith, https://wiki.openstack.org/wiki/StructuredWorkflowPrimitives20:19
jgriffithhemna: thanks20:20
adrian_ottois "https://launchpad.net/%7Ewalter-boring" in this chat?20:20
hemna<--20:20
adrian_ottook, cool20:20
changbl+1 to harlowja20:21
adrian_ottoand is "https://launchpad.net/%7Ejohn-griffith" also here?20:21
harlowjai personally just feel that if we start in stack forge, we can prototype really fast, have active core members from say reddwarf, nova, heat involved in the ideas (maybe not code)20:21
hemnaharlowja, +1 I'm ok with that.20:21
harlowjawe could even publish a pypi package of this (when it reaches some level of maturity) that those core projects can use20:21
adrian_otto+120:21
harlowjaand when its more stabilized shift to oslo20:21
maoyharlowja: i'm not sure we need to start from stackforge given cinder's strong demand. why not directly into cinder?20:21
adrian_ottousing stackforge comes with advantages of the CICD resources form OpenStack20:22
*** dwcramer has quit IRC20:22
adrian_ottos/form/from/20:22
harlowjamaoy i think other projects also have strong demands for this so its not just 1 strong demand i feel20:22
maoyfair enough.20:22
maoyso let me get the procedure right:20:23
*** jamespage_ has joined #openstack-meeting20:23
jgriffithjust fyi from my perspective I"m fine with either approach but I would likely suck things in to cinder earlier anyway20:23
harlowjai agree, sucking in early would be the goal20:23
adrian_ottohemna: woudl something implementd in a library that lets you have a local state machine fork for your use case, or are you looking for an API controlled service?20:23
maoycommit into stackforge, copy paste into cinder, convert cinder code to using the library?20:23
harlowjacopy paste20:23
harlowjaeck20:23
jgriffithadrian_otto: lib for state machine is what I had planned for now at least20:24
jgriffithhemna: agree?20:24
adrian_ottook, good, that's what we will ahve first20:24
harlowjai was thinking that we could directly publish a pypi library no?20:24
hemnayah that's fine.20:24
hemnadon't have strong feelings either way about that20:24
hemnaan API might be better long term...dunno20:24
*** salv-orlando has quit IRC20:24
harlowjacopy paste scares me :)20:24
jgriffithharlowja: I'm debating that same thing with the idea of brick but I don't know that it's important to weigh in right now (because I can't) :)20:25
adrian_ottoso it looks like using Cinder's blueprint as the first one would make sense. I'm really happy to have more eyeballs on this.20:25
harlowjaya, its new ground20:25
*** salv-orlando has joined #openstack-meeting20:25
*** done__ has joined #openstack-meeting20:25
*** markpeek has joined #openstack-meeting20:25
harlowjaso does everyone think that process would be a good first step?20:25
adrian_ottoRedDwarrf and Heat should be close after.20:25
*** lloydde has joined #openstack-meeting20:26
*** toanster has joined #openstack-meeting20:26
hemnahopefully before H3 we could get this in oslo though20:26
harlowjastackforge, have interested core members involved in library, work partially toward cinders BP as a potential first target20:26
adrian_ottoNova may end up being later, but we can start small there, and iterate toward the more demanding task flows20:26
harlowjaadrian_otto agreed20:26
maoysounds like a great plan20:27
harlowjahemna agreed to20:27
changblsoudns good to me20:27
jgriffithwow, folks are in a good mood today :)20:27
harlowjamaximal code, minimal red tape is my goal :)20:27
hemnasweet.20:27
maoyalthough for the record, i do prefer to start from cinder directly..20:27
maoyjust better focus and easier to debug20:27
*** glikson_ has joined #openstack-meeting20:27
hemnaI'm ok with it living in cinder for now as well.20:27
harlowjamaoy this is where i think having said core memebers involved in said library comes into play20:28
jgriffithI think if we advertise the effort it works fine20:28
jgriffithand we get gating and unit testing which is critical20:28
adrian_ottoawesome, that may actually reduce complexity too20:28
jgriffithharlowja: although to be fair I'm not all that familiar with using stackforge20:29
harlowjaits pretty simple, u get the gating and unittests also20:29
*** jamespage_ has quit IRC20:29
jgriffithahh... yeah, looking at it now20:29
adrian_ottolet's not bother with StackForge if working in Cinder is preferred20:29
maoyharlowja: IMO it's just slightly more painful to have two projects in the beginning.20:29
adrian_ottothe sooner this makes it to Oslo the better it will be for all the stakeholders20:30
jgriffithI prpose we at least try it and if it seems problematic revist the decision20:30
jgriffithcinder that is ^^20:30
changbl+1 to maoy20:30
changblbetter 1 project to start20:30
adrian_otto+120:30
hemnaok +1 for cinder20:30
maoyadrian_otto: good point. if we get attractions in cinder, we might skip stackforge and go directly to olso20:30
harlowjaok, so seems like we have some consensus :)20:31
maoyif we don't, we can still use stackforge..20:31
harlowja#agreed attempt at developing taskflow in cinder to start20:31
harlowjasound good?20:31
adrian_ottowe might use stackforge to kickstart the API service built on the taskflow library's state machine code20:31
maoyyeah20:31
*** markpeek has quit IRC20:31
adrian_ottoas that's probably more than Cinder's charter calls for20:32
harlowjaya, there is a whole transition to oslo that i'm not sure about20:32
harlowjabut i guess we can hit that when we get there20:32
*** reed_ has joined #openstack-meeting20:33
maoyharlowja: agreed20:33
*** lloydde has quit IRC20:33
harlowjaok, so thats good news, it would still be useful to me to have interested other core members involved20:34
harlowjaat least in design i think :)20:34
*** eharney has joined #openstack-meeting20:34
jgriffithharlowja: +1 I think that's a requirement20:34
harlowjacool, then it won't become so cinder specific we will be like oops, that might not work so well over there in X project20:35
*** sacharya has quit IRC20:35
jgriffithyup20:35
maoyabsolutely20:35
harlowjacool20:35
adrian_ottohub_cap agreed to be on it20:35
jgriffithwe can even have lazy rules about +2/A for cinder core folks20:35
maoypardon my ignorance. do we have heat core in the room?20:35
adrian_ottoshardy: yt?20:36
harlowja#agreed have core 'sponsors' from other projects that want to use said taskflow library (starting in cinder) be involved from the start in design (and even code if they have time)20:36
harlowjaso thats cool, great news to me :)20:37
harlowjamaybe i can send a ML email to get interested parties (that might not have shown up here)20:37
harlowjasound good?20:38
jgriffithharlowja: sounds good to me20:38
changblyes20:38
*** mriedem1 has joined #openstack-meeting20:38
adrian_ottomaoy: looks like no, heat code (shardy) is not here20:38
harlowja#action harlowja send email to ML to get other interested core people involved20:38
adrian_ottos/code/core/20:38
maoyadrian_otto: ack. np20:38
anniecsounds good harlowja, will be good to get a nova core volunteer ;P20:38
harlowjaof course20:39
maoyjgriffith: which API(s) in cinder (or prodedures, workflows, taskflows) do you see has the potentials to be the early adoptor?20:40
jgriffithmaoy: My primary focus to start is state transistion on the volume life-cycle20:40
jgriffithmaoy: hemna may have additional input for FC20:40
*** ttrifonov is now known as ttrifonov_zZzz20:41
*** lloydde has joined #openstack-meeting20:41
jgriffithmaoy: currently like most we just fill in a string at various points in the code20:41
maoyjgriffith: does cinder have a state transition graph like this in nova? http://docs.openstack.org/developer/nova/devref/vmstates.html20:41
maoyoops. the graph is not rendered.20:41
harlowja#link ttp://docs.openstack.org/developer/nova/devref/vmstates.html20:42
harlowja#link http://docs.openstack.org/developer/nova/devref/vmstates.html20:42
harlowja#topic cinder-primitives20:42
*** openstack changes topic to "cinder-primitives (Meeting topic: state-management-goodness)"20:42
hemnaI don't think I've seen one20:42
jgriffithmaoy: harlowja we do not20:42
jgriffithso there's the first task :)20:42
harlowja:)20:42
maoyhehe20:42
harlowjaya, that is expected i think, gotta figure out what its doing first ;)20:42
harlowjathen how to map it to taskflow20:43
harlowjaand this is where the primitives might come in handy20:43
harlowja#link https://wiki.openstack.org/wiki/StructuredWorkflowPrimitives20:43
jgriffithk... we'll have to move pretty quick and get some of this put together20:44
harlowja*others feel free to add any ones that they think are useful also*20:44
harlowjajgriffith agreed, quickness is part of the fun20:44
jgriffith:)20:44
jgriffithhemna: and I can sort that out20:44
hemnaok20:44
jgriffithat least the initial pieces20:44
*** zul has joined #openstack-meeting20:44
harlowjathat be very useful, at least then we can sorta discuss as to how it might fit20:44
* jgriffith likes to volunteer hemna for things :)20:44
harlowjaand adjust from there20:44
hemna:P20:45
harlowjaand debate about any new primitives, or removing other ones and so on20:45
harlowjai was sort of forming this for these types of things20:46
harlowja#link https://wiki.openstack.org/wiki/StructuredWorkflows20:46
jgriffithsounds good... maoy, adrian_otto ?20:46
harlowjathat could be the multi-project main page for this kind of stuff20:46
jgriffithharlowja: sure20:46
maoyjgriffith: great. look forward to it20:47
harlowja#action jgriffith hemna document a possible taskflow,workflow to take, then reconvine via ML (or email or IRC) about how library (which is slightly in progress) may have to be adjusted to accomdate20:47
jgriffith#action cinder team to provide cinder workflow data20:47
jgriffithhaha!20:47
harlowja:)20:47
*** shengjie has joined #openstack-meeting20:48
*** shengjie has quit IRC20:48
hemnarock on!20:48
*** adalbas has quit IRC20:48
harlowjait'd be very interesting to start collecting what the other taskflows other core projects think would be useful to 'attack' on there end20:48
harlowjasince the more knowledge we can gather, then better we can design20:48
harlowja*the better20:48
harlowjanova is an interesting one that has many potential paths20:49
harlowja*and is the one i am most familiar with, although maoy i would think knows best20:49
harlowjamaoy or russellb or others20:49
harlowjabut not an immediate need i guess :)20:50
harlowja#topic open-dicussion20:50
*** openstack changes topic to "open-dicussion (Meeting topic: state-management-goodness)"20:50
harlowjaany other things people want to talk about?20:50
harlowjano question turned away :)20:50
adrian_ottoI hve a question about backends20:51
adrian_ottothe current patch (sorry no link on hand) implements a ZX backend20:51
adrian_ottoI saw a Dummy.py in there20:51
adrian_ottothere was discussion of in-memory in the past meeting20:52
harlowjayup, i think dummy -> in-memory20:52
adrian_ottodo we need a simple on-disk version?20:52
harlowjacould be, i guess it depends on which primitive u want to back by disk20:52
*** tpatil has joined #openstack-meeting20:52
harlowjabut i could imagine a task-log being backed by sqllite for example20:53
harlowjaa locking mechanism also, could be using filelocks20:53
harlowjaa type of job 'availability' board though would be a little odd to just have in-memory, but for testing it seems important20:53
*** glikson_ is now known as glikson20:54
harlowjaso adrian_otto  i think we could have that :)20:54
harlowjabut might need to know more about which piece u are thinking about20:55
adrian_ottoso just about every workflow in Nova is vulnerable to a service restart20:55
harlowjayup20:55
harlowja*or power failure20:55
adrian_ottoand we won't likely take a ZK dependency by default20:55
harlowjayup20:55
adrian_ottoso having something that works well on a single node, and survives restarts (even if crash recovery process is needed) will be useful20:55
harlowjaso i think it would be local, in-memory, DB impl, then maybe a ZK impl20:55
*** salv-orlando has quit IRC20:56
harlowja*in-memory mainly for testing20:56
adrian_ottothe DB impl might be sketchy for stuff like locks20:56
harlowjayup20:56
adrian_ottoso it might need to be a combination20:56
harlowjaagreed20:56
adrian_ottoI trust fcntl() and flock() but not MySQL GET_LOCK or whatever20:56
harlowjacan u expand on that idea, like i think i know the scenario u are thinking of, but might not be :)20:56
jlucciI think we only need a DB impl for completed jobs20:57
harlowja*as time runs out :(20:57
jluccian executing job doesn't need to persist in a DB20:57
adrian_ottoindeed. where can we capture this as an item for further discussion?20:57
harlowjai can capture, but might be useful to continue on another channel, or ML?20:57
harlowjaso many good idears :)20:58
harlowja*would rather not wait a week to talk about them20:58
adrian_ottook, tx, that's it for now on this subject20:58
adrian_ottowill follow up after meeting to keep it moving20:58
harlowjacool20:58
harlowja1 minute left!20:59
harlowjai'll capture this stuff and send it out20:59
gliksongood progress :-)20:59
harlowjadef20:59
harlowjathx all!20:59
harlowja#endmeeting20:59
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:59
openstackMeeting ended Thu May  9 20:59:51 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/state_management_goodness/2013/state_management_goodness.2013-05-09-20.00.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/state_management_goodness/2013/state_management_goodness.2013-05-09-20.00.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/state_management_goodness/2013/state_management_goodness.2013-05-09-20.00.log.html20:59
*** rerngvit has joined #openstack-meeting21:00
*** lloydde has quit IRC21:00
*** markmcclain has quit IRC21:01
russellb#startmeeting nova21:02
openstackMeeting started Thu May  9 21:02:11 2013 UTC.  The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
*** johnthetubaguy has joined #openstack-meeting21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: nova)"21:02
openstackThe meeting name has been set to 'nova'21:02
russellbwho's around to talk nova?21:02
dansmitho/21:02
cburgess<--21:02
cyeohhi21:02
rerngvithi21:02
hartsockshey21:02
n0anoo/21:02
alaskio/21:02
beagleshi21:02
russellb#link https://wiki.openstack.org/wiki/Meetings/Nova21:02
russellb#topic release status - havana-121:02
*** openstack changes topic to "release status - havana-1 (Meeting topic: nova)"21:02
russellb#link https://blueprints.launchpad.net/nova/havana21:02
russellb#link https://launchpad.net/nova/+milestone/havana-121:03
*** spzala has quit IRC21:03
russellbhavana-1 is scheduled for 3 weeks from today, which means patches need to be in in less time than that21:03
russellbprobably may 2121:03
*** mikal has quit IRC21:03
russellbso with that said, we need to be watching our goals for havana-121:03
devananda\o21:03
russellbthe blueprint list is looking pretty aggressive21:03
*** sacharya has joined #openstack-meeting21:04
russellbtake a look at the havana-1 list and let me know if the status needs updating on any21:04
russellbor if you feel like it should be pushed back, let me know that too21:04
*** esheffield has left #openstack-meeting21:04
*** melwitt has joined #openstack-meeting21:04
russellbif you're the assignee, you *should* be able to update the status along the way yourself, so please do21:04
*** mikal has joined #openstack-meeting21:05
*** tpatil has quit IRC21:05
*** johnthetubaguy1 has joined #openstack-meeting21:05
russellbany comments/questions on release / havana-1 status?21:05
russellbas we get closer, i will start hounding people for updates :-)21:06
devanandai'm not going to make https://bugs.launchpad.net/nova/+bug/1078080 happen soon21:06
uvirtbotLaunchpad bug 1078080 in nova "libvirt rescue doesn't respect image_meta passed in" [High,Triaged]21:06
russellbstill want it on you?21:07
*** johnthetubaguy has quit IRC21:07
russellbor unassign?21:07
*** johnthetubaguy1 is now known as johnthetubaguy21:07
devanandaactually, no. it doesn't really apply to ironic21:07
russellbk, removed you21:07
devanandaid consider it a feature for baremetal at this point21:07
russellbso someone else can grab it21:07
devanandak21:07
russellbsounds like i can change it to wishlist then?21:08
russellbhigh is == "High if the bug prevents a key feature from working properly for some users (or with a workaround)"21:08
*** ashwini has quit IRC21:08
russellb"Wishlist if the bug is not really a bug, but rather a welcome change in behavior:]21:09
russellbfrom https://wiki.openstack.org/wiki/BugTriage21:09
russellbk, on to bugs21:09
russellb#topic bugs21:09
*** openstack changes topic to "bugs (Meeting topic: nova)"21:09
russellbwe had a bug day!21:09
russellbmikal: how was it?21:09
mikalIt seemed to go ok even!21:09
mikalTriage worked well21:09
*** senhuang has joined #openstack-meeting21:09
mikalWe didn't seem to _close_ many more bugs than normal though21:10
russellbtriage uncovered a few important things though21:10
mikalBut we found some imporant stuff in the triage process21:10
russellbthat's quite valuable21:10
mikalAgreed21:10
russellbhow many did we triage?21:10
russellb-ish21:10
*** adrian_otto has left #openstack-meeting21:10
mikalLast I looked (yesterday) about 60 bugs21:10
russellbcool, i like numbers21:10
russellbso shall we do it again?21:10
mikalYes, for sure21:11
driptonKeep review lag in mind; we may have closed some bugs that just aren't all the way through the pipeline.21:11
russellbif we do it regularly, maybe there will be less in triage, and more time can be spent fixing21:11
mikalI think we said every two weeks?21:11
russellbmikal: sounds good to me21:11
mikaldripton: I was tracking "in progress", which happens when the review is sent21:11
russellbdripton: yeah, indeed.  we can look at how many go to "in progress" though ... yes what mikal said :)21:11
mikalIts ok though21:11
driptonmikal: you're anticipating my suggestions before I can make them21:12
mikalPerhaps its because triage was such a mess21:12
mikalBaby steps21:12
melwittfrom mikal's email I thought most of the focus was intended to be on triage so I think I misunderstood21:12
russellbyeah that took all of my bug time21:12
russellbtriage is step 1 really21:12
mikalmelwitt: I think triage was important, so I'm not sad if people focussed on that21:12
cburgessWhere did we end up doing all the triage and discussion? Was it openstack-nova? Did I miss it because I was busy?21:12
* comstud lurks21:13
senhuangcould non-core deveveloper do triage?21:13
mikalcburgess: there was an irc chanell (openstack-bugday) but it was basically idle when I was awake21:13
* russellb talked in #openstack-nova the whole time ...21:13
russellbi think we should just use -nova21:13
cyeohsenhuang: could do some confirming of bugs or asking for more info etc...21:13
mikalsenhuang: to my understanding yes, someone was during the day (he could mark things incomplete at least)21:13
cburgessOpps.. ok my bad. I'll be sure to join it next time. russellb did give me a bug yesterday that I got a review up for today but I had wanted to help more.21:13
russellbanyone is welcome to do triage21:13
senhuangcyeoh: mikal: thanks!21:13
russellbtriage instructions here: https://wiki.openstack.org/wiki/BugTriage21:14
russellb#link https://wiki.openstack.org/wiki/BugTriage21:14
mikalWe also ended up with a wiki page with suggestions on how to write a good bug report, so that's cool21:14
russellbnice21:14
alaskisenhuang: I think you need to join https://launchpad.net/~nova-bugs to triage, but it's open to non-core21:14
*** armax has quit IRC21:14
russellbalaski: good point21:14
russellbforgot about that21:14
senhuangalaski: that is cool. will do21:15
russellbmikal: thanks for organizing / posting stats21:15
*** ryanpetrello has quit IRC21:15
mikalWe should add that to the triage instructions21:15
melwittyeah, I'm not core but I was able to confirm a few/add comments, resolve inconsistent state21:15
mikalrussellb: NP21:15
russellbany more comments/questions on bugs?21:15
russellbcburgess: i saw your patch go up today btw, haven't had a chance to look, but thanks a lot!  will look as soon as i can21:16
cburgessNo worries21:16
russellbhave a link for the log?21:16
cburgessSorry what?21:16
russellblink to the review21:17
cburgesshttps://review.openstack.org/#/c/28717/21:17
russellb#link https://review.openstack.org/#/c/28717/21:17
russellbthanks21:17
russellbalrighty, onwards21:17
russellb#topic sub-team reports21:17
*** openstack changes topic to "sub-team reports (Meeting topic: nova)"21:17
senhuangrussellb: have you had a chance to the proposed fix for bug https://bugs.launchpad.net/nova/+bug/104924921:17
uvirtbotLaunchpad bug 1049249 in nova "Remove plugging of internal classes from configuration" [High,Confirmed]21:17
russellb#link https://wiki.openstack.org/wiki/Teams#Nova_subteams21:17
russellbsub-teams are listed there21:17
russellbi'd like to start getting quick reports from these teams when there's useful info to report21:18
russellbso any representatives want to recap what you're up to?21:18
harlowjasuree21:18
harlowjaso there was talk about where to have the placement of said 'taskflow' library to start21:19
harlowja*a place where it can be rapidly worked on21:19
harlowjaand where it solves an immediate need21:19
*** zul has quit IRC21:19
*** chuck_ has joined #openstack-meeting21:19
johnthetubaguyin XenAPI, we went over lots of blueprints, and some hotish bugs, making progress21:20
johnthetubaguy#help https://blueprints.launchpad.net/nova/+spec/xenapi-vif-hotplug needs some help21:20
russellbwhat kind of help21:20
russellbsomeone to do it?21:20
johnthetubaguyyup, ideally21:20
harlowjaso there was some consensus that cinder might be a good place for that, but also consensus that it would be very useful to have core memebers of different openstack subprojects involved in reviewing said code, the design process and so on, so that said library does not just become only useful for nova21:20
russellbharlowja: thinking of trying something on stackforge?21:21
harlowjathere was some talk about stackforge21:21
johnthetubaguyOn more XenAPI thing, poeple are working on SmokeStack and getting that working, that is all from me. Sorry to inteject.21:21
russellbjohnthetubaguy: +1 :-)21:21
gliksonharlowja: you mean, "only useful for Cinder"21:21
harlowja*yes thx21:21
*** radez is now known as radez_g0n321:22
johnthetubaguystackforge could work, I guess its that copy you are trying to avoid? oslo incubator?21:22
harlowjawell not just the copy, the red tape is part of it21:22
russellbcould start in stackforge, maybe eventually it goes to oslo later once it materializes21:22
johnthetubaguymakes sense21:23
russellbcool, well thanks for the updates21:23
hartsocks… just want to announce a VMwareAPI subteam meeting next week … #link21:23
n0anoFor the scheduler we're basically doing a first pass throught21:23
n0anothe ~11 subjects brought up at the conference, there'll be more21:23
n0anodetail coming soon.21:23
n0anoOne interesting issue is `future of scheduler' which is21:23
n0anoreally an idea to have the scheduler find the nodes but21:23
hartsocks#link https://wiki.openstack.org/wiki/Meetings/VMwareAPI21:23
n0anonot actually start the instances, have an orchestrator do21:23
n0anothat.21:23
harlowjarussellb so there might be some ongoing discussion about placement, but there was mostly agreement that it might fit best in cinder for now, its a tricky one though21:23
harlowjai am fine with it on stackforge, with core people from the different teams providing input21:24
senhuangharlowja: is this placement about selecting a node for volume?21:24
*** jamespage_ has joined #openstack-meeting21:24
devanandaharlowja: what's the problem with stackforge?21:24
harlowjaunsure, jgriffith has an AI to help flush that out21:24
russellbn0ano: re: future of the scheduler, https://blueprints.launchpad.net/nova/+spec/query-scheduler ?21:24
harlowjadevananda so there was disussion about how starting on stackforge may create a project that is useful for all, but useful for none :-p21:24
alaskirussellb: yeah, that was it21:25
russellbcool21:25
n0anorussellb, yeah, that's it21:25
russellbalright, couple of quick announcements, then open discussion (and can talk more about these teams activities if needed)21:25
russellb#topic other announcements21:25
*** openstack changes topic to "other announcements (Meeting topic: nova)"21:25
hartsocksah.21:25
hartsocksI should have waited for here to announce sorry.21:25
russellbI updated a wiki page to describe support states of virt drivers21:25
russellb#link https://wiki.openstack.org/wiki/HypervisorSupportMatrix21:26
*** diogogmt has quit IRC21:26
russellbjohnthetubaguy says they're working to move XenAPI up quickly back to group B, and eventually group A21:26
russellbi know there's work on baremetal testing, too21:26
russellbwould like to see all drivers move out of group C eventually21:26
russellbother note ... i started a "virt driver architecture" thread today, check it out21:27
russellbi don't want to go into it too much here and fragment the conversation21:27
johnthetubaguy:-) trying21:27
russellb#topic open discussion21:27
*** openstack changes topic to "open discussion (Meeting topic: nova)"21:27
rerngvitmay I ask about a direction for one particular patch?21:27
russellbhartsocks: sorry, didn't mean to cut you off if you had more to say about your team meeting21:27
russellbrerngvit: yes21:28
hartsocksrusselb: y'all type fast.21:28
harlowjaso would any nova core members like to join in help said taskflow library be the best it can be, i know some about nova, but not as much as everyone else, and i'd like the library to be able to plug-in to the future of nova21:28
rerngvitthis patch(https://review.openstack.org/#/c/18462/ ) is postponed from Grizzly because we don't know how this should be implemented21:28
russellbhartsocks: irc meetings can get crazy, heh21:28
rerngvitis it still the case? that I should wait of decision or I can progress on with it?21:29
johnthetubaguyharlowja: I am not core, but interested in taskflow from the live-migration refactor blueprint sense21:29
*** jasondotstar has quit IRC21:29
russellbrerngvit: that was blocked because of the grizzly feature freeze, so it's fine now21:29
devanandaharlowja: i'll probably lurk on the taskflow stuff, not sure how actively i'll contribute though21:29
harlowjajohnthetubaguy agreed, i can help u sync up if u want about what is happning21:29
russellbrerngvit: there were a few people working on that ... need to check for duplication21:29
alaskiharlowja: I also want to lurk, but can't commit to much help atm21:30
johnthetubaguyharlowja: +1 its just the meeting time sucks in my timezone21:30
harlowjajohnthetubaguy ya21:30
rerngvitok, thank you.21:30
russellbrerngvit: actually looks like the blueprint in the havana plan is assigned to you, i think we're good.21:30
russellbhttps://blueprints.launchpad.net/nova/+spec/utilization-based-scheduling21:30
russellbrerngvit: so yes, please re-propose when you're ready :-)21:30
harlowjaalaski devananda great to have u guys21:30
eharneyre: blueprints - i am starting to look at https://blueprints.launchpad.net/nova/+spec/glusterfs-native-support21:31
*** jamespage_ has quit IRC21:31
devanandaalso, any -core folks interested in join in on Ironic?21:31
rerngvitok thanks21:31
eharneyi emailed the original author, he said he didn't have time to work on it21:31
harlowjadevananda i'm not core but i'd like to help make sure u get whatever u need from y! people21:31
russellbdevananda: certainly an interested observer ... my hands are a bit full atm though21:31
*** jlucci has quit IRC21:32
*** lloydde has joined #openstack-meeting21:32
*** rerngvit has left #openstack-meeting21:32
russellbdevananda: where will you discuss things?  openstack-dev with [Ironic], #openstack-ironic?  code on stackforge?21:32
devanandarussellb: ofc :)21:32
devanandarussellb: yes. openstack-dev [ironic], also there is an #openstack-ironic channel, and the code will be on gerrit (not stackforge) once the name passes trademark checks21:33
russellbI can't believe I forgot to mention Ironic in this meeting!21:33
devananda:)21:33
russellbso yeah, if you didn't follow ... the Technical Committee approved Ironic as a new incubated project for the split out of baremetal from Nova21:33
russellbI think it's really exciting stuff21:33
russellbcongrats to devananda and crew21:34
devananda\o/21:34
harlowjadevananda +121:34
devanandafirst meeting will be monday 1900 utc21:34
comstudwoot.21:34
russellbif all goes well, we will be marking the current baremetal driver as deprecated in havana, and remove it in I21:35
*** SergeyLukjanov has quit IRC21:35
russellbwe'll see how it goes, but I have a ton of faith in the guys that have been driving it :-)21:35
mriedem1russellb: going back to the group c comment on the hypervisor support matrix, just curious what the red indicates in the x'ed cell for powervm here? https://wiki.openstack.org/wiki/HypervisorSupportMatrix#Hypervisor_feature_support_matrix21:35
*** MarkAtwood has quit IRC21:35
russellbmriedem1: ask sdague, he did that21:35
dansmithhah21:36
sdagueheh21:36
dansmithmriedem1: just color testing21:36
dansmithmriedem1: fear not :)21:36
sdaguesorry, I was chatting with dan earlier about making the x's pop more21:36
dansmithmy fault21:36
sdagueso figured out how to make them red21:36
russellbbusted21:36
dansmithyes, busted indeed21:36
sdaguepay no attention to the man behind the curtain....21:36
jog0I know I am coming really late to the meeting, but since its in open discussion I thought I would plug the work Bluehost has done to nova.  I haven't had time to dig in but it looks interesting as there cloud is 16k nodes.  Slides http://www.slideshare.net/junparkearth/blue-host-openstacksummit2013  code https://github.com/UpooPoo/nova21:37
mriedem1sdague: no problem - was just wondering if i needed to take something back to my team21:37
mriedem1thanks21:37
devanandare: ironic, i could use a few ppl with deeper openstack knowledge to at least review, if not contribute, to the framework, once there is some code on gerrit21:37
russellbUpooPoo?21:37
harlowjalol21:37
asadoughiwanted to mention https://blueprints.launchpad.net/nova/+spec/nova-network-legacy going to start up patchsets for modifiy libvirt and baremetal(ironic, now?) that i had abandoned previously21:37
devanandawhich i'm thinking should be any day now21:37
jog0yeahhhh21:37
russellbasadoughi: great21:38
mikaldevananda: I'm happy to review, but I'm maxed out on other stuff coding wize21:38
devanandato help align it with other openstack services and APIs and stuff21:38
*** chuck_ has quit IRC21:38
devanandamikal: that'd be awesome21:38
jog0russellb: with 16k node cluster  they can call it whatever they want21:38
russellbjog0: lol, fair enough21:39
mriedem1harlowja: was there anything you wanted to bring up in the meeting for default AZ? re: https://review.openstack.org/#/c/28645/ - i thought you mentioned that in #openstack-nova earlier today21:39
russellbbut yes, really want to talk to them more ...21:39
jog0they have a quantum patch set too https://github.com/JunPark/quantum/tree/bluehost/master21:39
mikaldevananda: the project is called openstack/ironic, right?21:39
devanandamikal: yes21:39
devanandamikal: it's in LP. just not in gerrit yet21:39
russellbironic may get the award for most clever codename yet21:39
harlowjamriedem1, oh yes thanks!21:39
russellb(hopefully it passes)21:40
devanandarussellb: let's just hope it passes lawyer checks!21:40
harlowjaso there was https://review.openstack.org/#/c/28645/ but i am slightly confused as to which AZ we should actually select for an instance21:40
*** lloydde has quit IRC21:41
harlowjathe instance db entry has a AZ field, but then the current code uses the host which the compute node is on, and then there is aggregates, and ...21:41
devanandaI am hacking on it here https://github.com/devananda/ironic until it has a Real Home (tm)21:41
*** gyee has quit IRC21:41
russellb#note ironic is here until it has a real home: https://github.com/devananda/ironic21:41
asadoughidevananda: would you prefer nova baremetal patches in the interim or wait for ironic to happen?21:42
harlowjaany thoughts on which az we should really be using  would be appreciated21:42
devanandaasadoughi: if they are fixing bugs in baremetal, yes please!21:42
devanandawhich reminds me, lifeless has been a bug-reporting machine the last few days21:42
gliksonany particular reason why AZ should be a field of an instance?21:42
*** ryanpetrello has joined #openstack-meeting21:43
lifelessdevananda: comes from trying to use it :)21:43
* lifeless doesn't mean that nastily21:43
gliksonmaybe just remove it from instance altogether, and use the one from host/whatever21:43
harlowjais there a reason/usage of it existing in the instance table though that i might not be aware of21:44
*** dwcramer has joined #openstack-meeting21:44
harlowjait sort of comes down to what is the defintion we are picking for an AZ21:44
harlowjaif an AZ is an aggregate, the hosts can be in multiple aggregates21:45
*** writer___ has quit IRC21:45
mroddenaggregates aren't user facing IIRC21:45
mroddenAZ is supposed to be the user facing choice21:45
russellbcorrect21:46
harlowjaso then whats in the instance table would be the one true AZ, and not the AZ of the host it sits on21:46
gliksonstill, it can be kept as a property of the host.. can different instances on the same host belong to different AZs? I hope not..21:46
russellblet's see if we can sort it out in gerrit, i need to refresh myself on the code some more to comment21:46
mroddenglikson: yeah that would kind of defeat the point of AZs21:47
mroddenif two instances with different AZs existed on the same host21:47
asadoughidevananda: well in the case of the baremetal patch i am thinking of .. it was a bug that turned into a blueprint and is targeted for havana-2. any differing thoughts?21:47
devanandaasadoughi: link?21:48
asadoughidevananda: https://blueprints.launchpad.net/nova/+spec/nova-network-legacy21:48
*** eglynn has quit IRC21:48
harlowjarussellb so any comments on https://review.openstack.org/#/c/28645/ would be appreciated, was trying to fix phils bug there, but it seems like there is more needed input than what i have21:48
harlowja#link https://bugs.launchpad.net/nova/+bug/117224621:48
uvirtbotLaunchpad bug 1172246 in nova "AZ reported wrongly until instance is scheduled" [Medium,In progress]21:48
devanandaasadoughi: that's a fix in my book :)21:49
russellbcool thanks21:49
*** salv-orlando has joined #openstack-meeting21:49
russellbalright, if anyone wants to chat further, #openstack-nova is always open21:50
russellbthanks for coming!21:50
russellb#endmeeting21:50
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"21:50
openstackMeeting ended Thu May  9 21:50:30 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-05-09-21.02.html21:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-05-09-21.02.txt21:50
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-05-09-21.02.log.html21:50
*** mriedem1 has left #openstack-meeting21:50
*** senhuang has quit IRC21:51
*** kebray has joined #openstack-meeting21:53
devanandaasadoughi: though it doesn't look like you addressed lifeless' concerns on the patch here https://review.openstack.org/#/c/21533/11/nova/virt/baremetal/pxe.py21:53
*** dolphm has joined #openstack-meeting21:54
*** dolphm has quit IRC21:54
lifelessindeed!21:54
*** dolphm has joined #openstack-meeting21:56
*** stevemar has quit IRC21:56
asadoughiah i haven't touched the code in a while, but i think the question i was pondering was a bugfix vs feature implementation. the main mission of the blueprint was to allow for ipv6 without ipv4 and i was resolving everything in its path to separate it out, wasn't interested in implementing features of handling extra subnets.21:57
*** martine has quit IRC21:58
asadoughidevananda: and the current code masks that away, as-is, when it converts from current to legacy formats. i'm not sure if lifeless 's issue was that it was becoming an explicit mishandling.21:59
lifelessasadoughi: right, at the moment 'using legacy implies not handling it'22:00
lifelessasadoughi: if we get rid of legacy, then something that was not buggy before becomes buggy22:00
lifelessunless we also handle the other changes implied by getting rid of legacy22:00
*** lbragstad has quit IRC22:00
lifelessasadoughi: you should be able to do ipv6 w/out ipv4 in other hypervisors without removing the legacy codepath22:00
asadoughilifeless: not the way code is shared between drivers22:01
lifelessasadoughi: if you want to do it in baremetal; I'll be very interested in how you're going to handle PXE :)22:01
asadoughilifeless: not sure i agree with "not buggy becomes buggy"22:01
*** jecarey has quit IRC22:01
lifelessasadoughi: perhaps -> nova?22:01
lifeless#nova I mean22:01
*** ayoung has quit IRC22:03
*** lloydde has joined #openstack-meeting22:05
*** sacharya has quit IRC22:05
*** glikson has quit IRC22:06
*** johnthetubaguy has quit IRC22:06
*** zul has joined #openstack-meeting22:09
*** maoy has quit IRC22:11
*** anniec has quit IRC22:12
*** mlavalle has joined #openstack-meeting22:14
*** mattray has joined #openstack-meeting22:14
*** koolhead17 has quit IRC22:23
*** hartsocks has quit IRC22:25
*** hartsocks has joined #openstack-meeting22:25
*** hartsocks has quit IRC22:31
*** ryanpetrello has quit IRC22:33
*** eharney has quit IRC22:33
*** rnirmal has quit IRC22:34
*** danwent has quit IRC22:35
*** vkmc has joined #openstack-meeting22:37
*** lloydde has quit IRC22:39
*** fnaval has quit IRC22:42
*** amyt has quit IRC22:46
*** lloydde has joined #openstack-meeting22:49
*** mattray has quit IRC22:50
*** reed_ is now known as reed22:50
*** changbl has quit IRC22:51
*** zul has quit IRC22:53
*** matiu has joined #openstack-meeting23:00
*** matiu has joined #openstack-meeting23:00
*** esker has quit IRC23:01
*** esker has joined #openstack-meeting23:02
*** dolphm has quit IRC23:04
*** esker has quit IRC23:07
*** zul has joined #openstack-meeting23:07
*** fnaval has joined #openstack-meeting23:08
*** danwent has joined #openstack-meeting23:08
*** mdenny has quit IRC23:10
*** pcm_ has joined #openstack-meeting23:15
*** mattray has joined #openstack-meeting23:15
*** ayoung has joined #openstack-meeting23:17
*** kebray has quit IRC23:19
*** jamespage_ has joined #openstack-meeting23:20
*** jamespage_ has quit IRC23:21
*** anniec has joined #openstack-meeting23:21
*** ashwini has joined #openstack-meeting23:24
*** shardy has left #openstack-meeting23:26
*** dwcramer has quit IRC23:27
*** dolphm has joined #openstack-meeting23:35
*** lloydde has quit IRC23:41
*** stevemar has joined #openstack-meeting23:46
*** reed has quit IRC23:53
*** jog0 has quit IRC23:57

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