Thursday, 2011-02-10

*** alekibango has quit IRC01:52
*** zul has quit IRC03:02
*** zul has joined #openstack-meeting03:03
*** kpepple has joined #openstack-meeting03:10
*** kpepple has quit IRC03:11
*** kpepple has joined #openstack-meeting03:11
*** adjohn has joined #openstack-meeting03:12
*** kpepple has quit IRC03:17
*** kpepple has joined #openstack-meeting03:18
*** kpepple has quit IRC03:23
*** kpepple has joined #openstack-meeting03:24
*** kpepple has joined #openstack-meeting03:27
*** kpepple has quit IRC03:29
*** kpepple has joined #openstack-meeting03:29
*** kpepple has quit IRC03:32
*** kpepple has joined #openstack-meeting03:32
*** kpepple has quit IRC03:33
*** kpepple has joined #openstack-meeting03:33
*** kpepple has quit IRC03:35
*** kpepple has joined #openstack-meeting03:36
*** kpepple has quit IRC03:40
*** kpepple has joined #openstack-meeting03:41
*** kpepple has quit IRC03:45
*** kpepple_ has joined #openstack-meeting03:45
*** littleidea has joined #openstack-meeting03:46
*** kpepple_ has quit IRC03:47
*** kpepple has joined #openstack-meeting03:47
*** kpepple has quit IRC03:52
*** kpepple_ has joined #openstack-meeting03:52
*** kpepple_ has quit IRC03:54
*** kpepple has joined #openstack-meeting03:54
*** littleidea has quit IRC03:56
*** kpepple has quit IRC04:01
*** kpepple has joined #openstack-meeting04:02
*** kpepple has quit IRC04:02
*** kpepple has joined #openstack-meeting04:03
*** kpepple has quit IRC04:07
*** kpepple has joined #openstack-meeting04:08
*** kpepple has quit IRC04:09
*** kpepple has joined #openstack-meeting04:09
*** kpepple has quit IRC04:14
*** kpepple has joined #openstack-meeting04:14
*** kpepple has quit IRC04:19
*** kpepple has joined #openstack-meeting04:20
*** kpepple has quit IRC04:22
*** kpepple has joined #openstack-meeting04:22
*** kpepple has quit IRC04:24
*** kpepple has joined #openstack-meeting04:24
*** kpepple has quit IRC04:26
*** kpepple has joined #openstack-meeting04:27
*** kpepple has quit IRC04:28
*** kpepple has joined #openstack-meeting04:28
*** kpepple has quit IRC04:33
*** kpepple has joined #openstack-meeting04:33
*** kpepple has quit IRC04:34
*** kpepple has joined #openstack-meeting04:34
*** kpepple has joined #openstack-meeting04:36
*** kpepple has quit IRC04:37
*** kpepple has joined #openstack-meeting04:38
*** littleidea has joined #openstack-meeting04:41
*** kpepple has quit IRC04:42
*** kpepple has joined #openstack-meeting04:43
*** kpepple has quit IRC04:49
*** kpepple has joined #openstack-meeting04:50
*** kpepple_ has joined #openstack-meeting04:55
*** kpepple has quit IRC04:55
*** littleidea has quit IRC04:57
*** kpepple_ has quit IRC05:02
*** kpepple has joined #openstack-meeting05:03
*** kpepple has quit IRC05:04
*** kpepple has joined #openstack-meeting05:04
*** pvo has joined #openstack-meeting05:05
*** kpepple has quit IRC05:06
*** kpepple has joined #openstack-meeting05:06
*** pvo has quit IRC05:07
*** kpepple has quit IRC05:13
*** kpepple has joined #openstack-meeting05:13
*** kpepple has quit IRC05:18
*** kpepple has joined #openstack-meeting05:18
*** kpepple has quit IRC05:22
*** kpepple has joined #openstack-meeting05:23
*** kpepple has quit IRC05:24
*** kpepple has joined #openstack-meeting05:25
*** kpepple has joined #openstack-meeting05:27
*** kpepple has joined #openstack-meeting05:29
*** kpepple has joined #openstack-meeting05:31
*** kpepple has quit IRC05:35
*** littleidea has joined #openstack-meeting05:36
*** kpepple has joined #openstack-meeting05:36
*** littleidea_ has joined #openstack-meeting05:37
*** littleidea has quit IRC05:40
*** littleidea_ is now known as littleidea05:40
*** kpepple has quit IRC05:45
*** kpepple has joined #openstack-meeting05:45
*** kpepple has quit IRC05:50
*** kpepple has joined #openstack-meeting05:50
*** kpepple has quit IRC05:52
*** kpepple has joined #openstack-meeting05:52
*** kpepple has quit IRC05:54
*** kpepple has joined #openstack-meeting05:54
*** kpepple_ has joined #openstack-meeting05:59
*** kpepple has quit IRC05:59
*** kpepple_ has quit IRC06:04
*** kpepple has joined #openstack-meeting06:04
*** kpepple has quit IRC06:08
*** kpepple has joined #openstack-meeting06:09
*** kpepple has joined #openstack-meeting06:11
*** kpepple has quit IRC06:15
*** kpepple has joined #openstack-meeting06:16
*** kpepple has quit IRC06:20
*** kpepple has joined #openstack-meeting06:21
*** kpepple has quit IRC06:29
*** kpepple_ has joined #openstack-meeting06:29
*** kpepple_ has quit IRC06:34
*** kpepple has joined #openstack-meeting06:35
*** kpepple has quit IRC06:35
*** kpepple has joined #openstack-meeting06:36
*** kpepple_ has joined #openstack-meeting06:41
*** kpepple has quit IRC06:41
*** kpepple_ has quit IRC06:45
*** littleidea has joined #openstack-meeting07:19
*** kpepple has joined #openstack-meeting07:30
*** kpepple_ has joined #openstack-meeting07:38
*** kpepple has quit IRC07:39
*** kpepple_ is now known as kpepple07:39
*** kpepple has quit IRC07:40
*** kpepple has joined #openstack-meeting07:40
*** kpepple has quit IRC07:54
*** kpepple has joined #openstack-meeting07:54
*** kpepple has quit IRC07:59
*** kpepple has joined #openstack-meeting07:59
*** kpepple has quit IRC08:02
*** kpepple has joined #openstack-meeting08:03
*** kpepple has quit IRC08:10
*** kpepple has joined #openstack-meeting08:11
*** kpepple has quit IRC08:15
*** kpepple has joined #openstack-meeting08:16
*** littleidea has quit IRC08:16
*** littleidea has joined #openstack-meeting08:17
*** westmaas has quit IRC08:18
*** kpepple has quit IRC08:20
*** kpepple has joined #openstack-meeting08:21
*** kpepple has quit IRC08:27
*** kpepple has joined #openstack-meeting08:27
*** kpepple has quit IRC08:32
*** kpepple has joined #openstack-meeting08:32
*** kpepple has quit IRC08:33
*** kpepple has joined #openstack-meeting08:33
*** littleidea has quit IRC08:34
*** kpepple has joined #openstack-meeting08:34
*** kpepple has joined #openstack-meeting08:35
*** kpepple has quit IRC08:40
*** kpepple has joined #openstack-meeting08:40
*** kpepple has quit IRC08:51
*** kpepple has joined #openstack-meeting08:52
*** kpepple has quit IRC08:53
*** kpepple has joined #openstack-meeting08:54
*** kpepple has quit IRC08:58
*** kpepple has joined #openstack-meeting08:59
*** kpepple has quit IRC09:12
*** kpepple has joined #openstack-meeting09:14
*** kpepple has quit IRC09:18
*** kpepple has joined #openstack-meeting09:19
*** kpepple has quit IRC09:21
*** kpepple has joined #openstack-meeting09:21
*** kpepple has quit IRC09:25
*** kpepple has joined #openstack-meeting09:26
*** kpepple has quit IRC09:28
*** kpepple has joined #openstack-meeting09:28
*** kpepple has quit IRC09:33
*** kpepple_ has joined #openstack-meeting09:33
*** kpepple_ has quit IRC09:38
*** kpepple has joined #openstack-meeting09:38
*** kpepple has quit IRC09:40
*** kpepple has joined #openstack-meeting09:40
*** kpepple has quit IRC09:45
*** kpepple has joined #openstack-meeting09:45
*** kpepple has quit IRC09:50
*** kpepple has joined #openstack-meeting09:50
*** kpepple has quit IRC09:52
*** kpepple has joined #openstack-meeting09:52
*** kpepple has quit IRC09:56
*** kpepple has joined #openstack-meeting09:57
*** kpepple has quit IRC10:02
*** kpepple_ has joined #openstack-meeting10:02
*** kpepple has joined #openstack-meeting10:03
*** kpepple has joined #openstack-meeting10:04
*** kpepple has quit IRC10:11
*** kpepple has joined #openstack-meeting10:12
*** kpepple has quit IRC10:17
*** kpepple has joined #openstack-meeting10:18
*** kpepple has quit IRC10:23
*** kpepple has joined #openstack-meeting10:24
*** kpepple has quit IRC10:25
*** kpepple has joined #openstack-meeting10:26
*** kpepple has joined #openstack-meeting10:27
*** kpepple has quit IRC10:31
*** kpepple has joined #openstack-meeting10:32
*** kpepple has quit IRC10:33
*** kpepple has joined #openstack-meeting10:34
*** kpepple has quit IRC10:34
*** kpepple has joined #openstack-meeting10:35
*** adjohn has quit IRC10:37
*** kpepple has quit IRC10:41
*** kpepple has joined #openstack-meeting10:42
*** kpepple has quit IRC10:48
*** kpepple_ has joined #openstack-meeting10:49
*** kpepple_ has quit IRC10:53
*** kpepple has joined #openstack-meeting10:54
*** kpepple has quit IRC10:58
*** kpepple has joined #openstack-meeting10:59
*** kpepple has quit IRC11:03
*** kpepple has joined #openstack-meeting11:04
*** kpepple has quit IRC11:08
*** kpepple_ has joined #openstack-meeting11:09
*** kpepple_ has quit IRC11:13
*** kpepple has joined #openstack-meeting11:14
*** kpepple has quit IRC11:18
*** kpepple has joined #openstack-meeting11:19
*** kpepple has quit IRC11:20
*** kpepple has joined #openstack-meeting11:21
*** kpepple has quit IRC11:25
*** kpepple has joined #openstack-meeting11:26
*** kpepple has quit IRC11:31
*** kpepple_ has joined #openstack-meeting11:31
*** kpepple_ has quit IRC11:35
*** kpepple has joined #openstack-meeting11:36
*** kpepple has quit IRC11:40
*** kpepple has joined #openstack-meeting11:40
*** kpepple has quit IRC11:44
*** kpepple has joined #openstack-meeting11:45
*** kpepple has quit IRC11:46
*** kpepple has joined #openstack-meeting11:47
*** kpepple has quit IRC11:51
*** kpepple has joined #openstack-meeting11:52
*** kpepple has quit IRC11:56
*** kpepple has joined #openstack-meeting11:57
*** kpepple has quit IRC12:00
*** kpepple has joined #openstack-meeting12:01
*** kpepple has quit IRC12:05
*** kpepple has joined #openstack-meeting12:06
*** kpepple has quit IRC12:08
*** kpepple has joined #openstack-meeting12:08
*** kpepple has quit IRC12:12
*** kpepple has joined #openstack-meeting12:13
*** kpepple_ has joined #openstack-meeting12:20
*** kpepple has quit IRC12:20
*** kpepple_ has quit IRC12:25
*** kpepple has joined #openstack-meeting12:25
*** kpepple_ has joined #openstack-meeting12:30
*** kpepple has quit IRC12:30
*** kpepple_ has quit IRC12:34
*** kpepple has joined #openstack-meeting12:35
*** kpepple has quit IRC12:36
*** kpepple has joined #openstack-meeting12:36
*** kpepple has quit IRC12:39
*** kpepple has joined #openstack-meeting12:40
*** kpepple has quit IRC12:49
*** kpepple has joined #openstack-meeting12:49
*** kpepple has quit IRC12:54
*** kpepple has joined #openstack-meeting12:55
*** kpepple has quit IRC12:59
*** kpepple has joined #openstack-meeting13:00
*** kpepple has quit IRC13:04
*** kpepple_ has joined #openstack-meeting13:04
*** kpepple_ has quit IRC13:08
*** kpepple has joined #openstack-meeting13:09
*** kpepple has quit IRC13:13
*** kpepple has joined #openstack-meeting13:14
*** kpepple has quit IRC13:24
*** kpepple has joined #openstack-meeting13:25
*** kpepple has quit IRC13:29
*** kpepple has joined #openstack-meeting13:31
*** kpepple has quit IRC13:32
*** kpepple has joined #openstack-meeting13:32
*** kpepple has quit IRC13:37
*** kpepple has joined #openstack-meeting13:37
*** kpepple has quit IRC13:39
*** kpepple has joined #openstack-meeting13:40
*** zul has quit IRC13:40
*** zul has joined #openstack-meeting13:40
*** kpepple has quit IRC13:44
*** kpepple has joined #openstack-meeting13:45
*** dprince has joined #openstack-meeting13:46
*** kpepple has quit IRC13:52
*** kpepple has joined #openstack-meeting13:52
*** kpepple has quit IRC14:01
*** kpepple has joined #openstack-meeting14:01
*** adjohn has joined #openstack-meeting14:03
*** westmaas has joined #openstack-meeting14:04
*** kpepple has quit IRC14:05
*** kpepple has joined #openstack-meeting14:05
*** kpepple has quit IRC14:09
*** kpepple has joined #openstack-meeting14:10
*** kpepple has quit IRC14:15
*** kpepple has joined #openstack-meeting14:16
*** kpepple has quit IRC14:17
*** kpepple has joined #openstack-meeting14:17
*** kpepple has joined #openstack-meeting14:19
*** kpepple has quit IRC14:24
*** kpepple has joined #openstack-meeting14:24
*** kpepple has quit IRC14:28
*** kpepple has joined #openstack-meeting14:29
*** adjohn has quit IRC14:33
*** kpepple has quit IRC14:33
*** kpepple has joined #openstack-meeting14:35
*** kpepple has quit IRC14:38
*** kpepple has joined #openstack-meeting14:39
*** adjohn has joined #openstack-meeting14:40
*** adjohn has joined #openstack-meeting14:43
*** kpepple_ has joined #openstack-meeting14:46
*** kpepple has quit IRC14:46
*** kpepple_ has quit IRC14:47
*** kpepple has joined #openstack-meeting14:48
*** kpepple has quit IRC14:52
*** kpepple_ has joined #openstack-meeting14:52
*** kpepple_ has quit IRC14:56
*** adjohn has quit IRC14:57
*** kpepple has joined #openstack-meeting14:57
*** kpepple has quit IRC15:11
*** littleidea has joined #openstack-meeting15:11
*** kpepple has joined #openstack-meeting15:11
*** jsgotangco has joined #openstack-meeting15:20
*** dendrobates is now known as dendro-afk15:23
*** dendro-afk is now known as dendrobates15:24
*** littleidea has quit IRC15:27
*** kpepple has quit IRC15:29
*** kpepple_ has joined #openstack-meeting15:29
*** kpepple_ has quit IRC15:34
*** kpepple has joined #openstack-meeting15:34
*** kpepple has quit IRC15:39
*** kpepple has joined #openstack-meeting15:39
*** kpepple has quit IRC15:48
*** kpepple has joined #openstack-meeting15:49
*** kpepple has quit IRC15:50
*** kpepple has joined #openstack-meeting15:50
*** kpepple has quit IRC15:51
*** kpepple has joined #openstack-meeting15:51
*** kpepple has quit IRC15:53
*** kpepple has joined #openstack-meeting15:53
*** kpepple has quit IRC15:58
*** kpepple has joined #openstack-meeting15:58
*** kpepple has quit IRC16:03
*** kpepple has joined #openstack-meeting16:03
*** kpepple has quit IRC16:07
*** kpepple has joined #openstack-meeting16:07
*** kpepple has quit IRC16:12
*** kpepple has joined #openstack-meeting16:12
*** kpepple has quit IRC16:17
*** kpepple has joined #openstack-meeting16:18
*** kpepple_ has joined #openstack-meeting16:22
*** kpepple has quit IRC16:22
*** kpepple_ has quit IRC16:36
*** kpepple has joined #openstack-meeting16:37
*** kpepple has quit IRC16:44
*** GasbaKid has joined #openstack-meeting16:44
*** kpepple has joined #openstack-meeting16:44
*** kpepple has quit IRC16:46
*** kpepple has joined #openstack-meeting16:46
*** kpepple has quit IRC16:55
*** kpepple has joined #openstack-meeting16:56
*** kpepple has quit IRC17:00
*** kpepple has joined #openstack-meeting17:01
*** dprince has quit IRC17:05
*** kpepple has quit IRC17:05
*** kpepple has joined #openstack-meeting17:06
*** kpepple has quit IRC17:13
*** kpepple has joined #openstack-meeting17:14
*** kpepple has quit IRC17:16
*** kpepple has joined #openstack-meeting17:16
*** kpepple has quit IRC17:21
*** kpepple has joined #openstack-meeting17:21
*** kpepple has quit IRC17:22
*** kpepple has joined #openstack-meeting17:22
*** dprince has joined #openstack-meeting17:22
*** GasbaKid has quit IRC17:24
*** GasbaKid has joined #openstack-meeting17:25
*** kpepple has quit IRC17:27
*** dprince has quit IRC17:27
*** kpepple has joined #openstack-meeting17:27
*** dprince has joined #openstack-meeting17:29
*** kpepple has quit IRC17:44
*** kpepple has joined #openstack-meeting17:44
*** kpepple has quit IRC17:49
*** kpepple has joined #openstack-meeting17:49
*** kpepple has quit IRC17:51
*** GasbaKid has quit IRC18:09
*** dprince has quit IRC18:09
*** dprince has joined #openstack-meeting18:12
*** dendrobates is now known as dendro-afk18:19
*** dendro-afk is now known as dendrobates18:19
*** DigitalFlux has joined #openstack-meeting18:56
*** DigitalFlux has quit IRC18:58
*** dprince_ has joined #openstack-meeting19:01
*** dprince has quit IRC19:01
*** dprince_ has quit IRC19:08
*** dprince has joined #openstack-meeting19:10
*** dprince has quit IRC19:18
*** dprince has joined #openstack-meeting20:18
*** dprince has quit IRC20:20
*** jbryce has joined #openstack-meeting20:22
*** jmckenty has joined #openstack-meeting20:27
*** creiht has joined #openstack-meeting20:31
jmckentyAre we still on for a POC meeting in here in 28 minutes?20:32
creihtas far as I know20:48
*** sandywalsh_ has quit IRC20:50
jmckentyaight.20:50
*** sandywalsh_ has joined #openstack-meeting20:53
*** sandywalsh_ is now known as sandywalsh20:54
jbryceall right...let's get this started21:00
jbryce#startmeeting21:00
openstackMeeting started Thu Feb 10 21:00:43 2011 UTC.  The chair is jbryce. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:00
jmckentyola21:01
*** bcwaldon has joined #openstack-meeting21:01
* creiht bows21:01
jmckentyagenda?21:01
jbryceSo i see 6 of us here--looks like we're missing jesse, ewan and mark. jesse is supposed to be joining shortly21:01
jbryceagenda can be seen at the bottom of the page here: http://wiki.openstack.org/Governance/POC21:01
jbryce#topic 2011 scope and charter21:02
jmckentyah, cool21:02
*** openstack changes topic to "2011 scope and charter"21:02
jbryceso we discussed this on email and there were a few open questions that were raised21:02
jmckentycreiht: can you summarize what we've agreed to so far?21:02
jbryceone is around the inclusion of the draft service architecture21:03
jmckentyah, right. Yeah, I still think we should make that a separate action.21:03
jbrycethe other item up for discussion was around the specification of individual languages21:03
jbryceso on the service architecture, what specific points do you want to see separated out?21:04
jbrycehttp://wiki.openstack.org/Governance/Proposed/2011%20Charter%20and%20Scope - that's the current proposal state21:04
*** ewanmellor has joined #openstack-meeting21:04
jmckentyopening it now...21:04
jbrycehi ewan...we're just getting started21:04
ewanmellorhi21:04
ewanmellorSorry I'm late21:04
vishyjesse is on a plane21:05
jmckentyso on the service architecture21:05
vishy* on his way to a plane21:05
jmckenty1. No problem with public RESTful API as a req21:05
jmckenty2. No problem with RESTful admin API (not sure it should be required to be public)21:05
jmckentyAnd not sure that calling it out as protected by ACL/permissions should be part of the service arch21:06
jmckentysince I think there are some innovations I'd like to push forward this year on that front21:06
jbryceok...i can see that21:06
jmckentyDon't mind calling out pub/sub as a specific option, but would like to see webhooks mentioned as well21:06
jmckentye.g., programatic webhooks via pub/sub or some other notification mechanism (could be the new queueing stuff that Eric is starting on)21:07
jbryceok...i'm fine with those modifications21:07
jmckentyWould like to call out WSGI as a specific technology for the extension interface or service framework (don't know where exactly we should mention it)21:08
jmckentyI guess that's more between API and service framework21:08
jmckentyAnd the last concern was on the extension interface21:08
jmckentyI think we'll get ourselves into trouble (astronauting) if we start trying to spec out too much extensionability21:08
jmckentyIf we're going to describe it as an interface, maybe pointing specifically to what Ewan did with the Xen abstraction?21:09
jbrycei think in this document, though, we're not trying to get too low-level and specific and more describe in general terms the attributes that a project would have.21:09
jbrycei think the actual details could vary by project and should probably be driven more at that level21:10
jmckentye.g., implementations *must* vs., *can*, and how implementation-specific code gets calls. Extension interface can imply infinitely complex (e.g. XPCOM)21:10
jmckentysure21:10
vishyYes i think broad and general is best at this level21:10
jmckentyI just don't want projects to think they need to have XPCOM or a whole run-time scriptable language to qualify21:10
jmckentymonkey-patches are extensions, too21:11
jbryceas written, it leaves room for that21:11
jbrycehere's my proposal21:11
jbryce1. modify public management API to say optionally protected21:11
jbryce2. say "such as pub/sub" on the notification interface item21:12
jbryce3. remove the specific languages being called out21:12
jbrycethen approve this one and move on to other proposals like the process for incubation and project evaluation21:13
jmckentyCan we require services to be implemented as WSGI?21:13
jmckentyfor common auth or what have you21:13
creihtjmckenty: Not sure, since WSGI is python specific21:13
jmckentyyou can make Java / PHP talk WSGI21:14
jmckentyif you're crazy21:14
creihtnot within a python app stack21:14
creihtheh21:14
creihtat that level that is why we specify RESTful apis21:14
creihtto ensure common communication between services21:14
jmckentyk, fair enough. I'm good with your plan, jbryce21:15
jmckentycreiht: http://pythonpaste.org/wphp/21:15
creihtjmckenty: lol :)21:15
jbryceso as amended, let's vote on the 2011 scope charter21:15
jbryce+121:15
creiht+121:15
*** pvo has joined #openstack-meeting21:15
vishy+121:15
jmckenty+121:16
jmckentydendrobates?21:16
vishyand ewan?21:17
jmckentyand soren ?21:17
vishyoh yeah where is soren?21:18
ewanmellorI vote 0.21:18
vishyis that abstain?21:18
*** dabo has joined #openstack-meeting21:18
ewanmellorI'm uncomfortable with the idea of telling people how to architect their software in a_ charter_.21:18
jmckenty+0 or -0 ?21:18
ewanmellorI don't think that we should even be talking about software architecture, when it comes to a charter for OpenStack.21:19
ewanmellorBut I don't think that there's enough that's bad about the proposal on the table to give it -1.21:19
jbryceewanmellor: even at the broad level of having basic common api technology?21:20
jmckentywell, you can give it -0 which is non-blocking21:20
*** bcwaldon has left #openstack-meeting21:20
ewanmellorSo I'm happy for you to proceed, if it's helping something that you're trying to do.21:20
jbryceok21:20
jbrycewe've got 4 of 7, which is a majority and a quorum21:20
jmckentyIt gives us some common ground for evaluating proposed projects for inclusion into openstack. I think that's the big win21:20
ewanmellorI agree that public APIs should be RESTful, modulo a long and tedious discussion about what RESTful means.21:20
jbryce#agreed Approve the 2011 project charter and scope21:21
ewanmellorI disagree that RESTful is the right way to design all APIs.21:21
ewanmellorBut anyway, let's move on.21:21
* jmckenty and ewanmellor will drink beer and bemoan the bastardization of the term RESTful21:21
jbryce#info 4 approves, 3 abstentions21:21
jbryce#topic Image formats21:21
*** openstack changes topic to "Image formats"21:21
jmckentyah, fun21:21
jbrycethis was another proposal on publishing a stance on image formats21:22
jbrycehttp://wiki.openstack.org/Governance/Proposed/ImageFormats - that is the draft21:22
*** GasbaKid has joined #openstack-meeting21:22
ewanmellorWhy is this a governance issue, not just a blueprint for Glance / Nova?21:23
jbrycethe proposal had 3 main components:21:23
jmckentyCan I point us briefly to the Open Cloud Manifesto?21:23
jbryce1) we need a standardized exchange format--proposal is to define an ovf/ova for our use21:23
jbryce2) openstack should not specify preferred/default virtual disk format21:23
jbryce3) glance should be extended to include conversion capabilities (seems like a feature definition/blueprint)21:24
vishyboth of those points make sense to me21:24
vishya lot of this seems specific to glance21:24
jmckentyhttp://www.opencloudmanifesto.org/opencloudmanifesto6.htm - use and adopt existing standards where appropriate21:24
*** sirp_ has joined #openstack-meeting21:24
ewanmellorjmckenty: Does that mean "use something that exists if it's the right thing to do, but don't if it's not"?21:25
vishyjmckenty: isn't that what is being suggested?21:25
jmckentyon the ovf/ova layer, yes21:25
jmckentybut the specific statement that we *shouldn't* espouse a standard disk image format, I'm not sure about21:25
jmckentyI think perhaps we SHOULD espouse one, but support many21:25
jmckentyI don't know if this is a case, such as hypervisors, where there are complex tradeoffs and no clear best choice21:26
vishywhat is meant by standard? as in what is used on the backend?21:26
vishybecause I think that is very hypervisor-specific21:27
jmckentyThe disk format within the OVF21:27
jmckentye.g., within glance and for transport21:27
jmckentyanyway, I guess we dodge the issues this way21:27
jmckenty"This also sidesteps the potentially divisive topic of support for VHD and the Microsoft Open Promise licensin"21:27
jbrycei think what it said was "preferred or default" rather than standard for disk format21:27
ewanmellorI have nothing against OVF (my name is on the spec, after all), but just some points of info:21:27
ewanmellorOVF doesn't give you interoperability.  The metadata standard isn't standard enough to be interoperable.21:28
ewanmellorOVF doesn't specify a disk format, so you still need to handle all the disk conversions.21:28
jmckentyThere's a practice concern around defaults - in order for the install process to be manageable, we *need* defaults21:29
jmckentyI would propose the least optimum default - RAW21:29
jmckentyeveryone supports it, and most installs will switch to something else21:29
vishyi think publicly raw is the way to go, perhaps with gz compression21:29
sirp_sirp: raw within a tarball container seems like a sensible default21:30
vishybut internally i don't think there is a need to bless a format, and conversions between formats should be provided.21:30
jmckentyewanmellor: do you think it's reasonable to try and draft a restricted OVF definition that WOULD be portable?21:30
jbryceewanmellor: true, but if we put a stake in the ground for openstack, then at least openstack clouds would interop with each other and given enough critical mass may move to a broader adoption21:30
jbrycevishy: i agree21:30
jmckentye.g., *an* OVF, not *any* OVF21:30
ewanmellorjmckenty: Yes.  You could say "VMware's OVF" or "Citrix's OVF".21:31
jmckentyno, I meant "OpenStack's OVF"21:31
jmckentyis there a subset that's useful?21:31
ewanmellorNo, that's my point.21:31
jbrycejmckenty: that is what john is proposing21:31
jmckentyright. john is proposing it, ewanmellor is saying it's not possible21:31
jmckentyewanmellor, technically, would know ;)21:31
ewanmellor"OpenStack's OVF" would have to choose either VHD or VMDK, so at the least someone would have to convert the disk format for either VMware or Hyper-V/XenServer/QEMU.21:32
vishyewanmellor: can't it choose raw?21:32
ewanmellorvishy: Yes it can, I think, but then it's useless.21:32
jmckentypourquoi?21:32
ewanmellorThe OVF spec says "any published format", IIRC, so raw would be acceptable.21:33
jmckentySo how bout this - a proposed OVF spec that glance supports, along with transforms that convert that to the OVF-variant that's usefully executable by the particular hypervisor?21:34
ewanmellorBut you can't use that as a transport format: an empty virtual disk with a 100 GB filesystem would be 100GB in raw.21:34
jmckentyyes - we noticed that early on :)21:34
ewanmellorSo if you want to transport it between clouds, all your templates are much much larger than they ever need to be.21:34
ewanmellorSo it's useless as an interop format, because you can't use it for transport.21:34
jmckentywell, hence the tarball proposal, but that's not a supported disk format yet21:35
ewanmellorBecause the most important point of interop is from appliance vendors to customers, and those always have much more free space than used, to allow the customer to expand into the free space.21:35
vishyi see21:36
ewanmellorXenServer's XVA is basically raw, but skipping any 2MB block that's completely zero, and with checksums, and then a tarball wrapper, and then gzipped.21:36
ewanmellorIt's basically what you're getting at.21:36
jmckentyjbryce: I think we may have to take this back offline for more debate21:36
jbryceok...sounds like we need some more thought on this one21:36
ewanmellorBut then, of course, you're using XenServer's format, not a neutral one.21:36
jbryce#info need to re-evaluate proposal21:37
jmckentywho's on the glance team - any POC members?21:37
sirp_i am21:37
sirp_jaypipes as well21:37
jbryce#action jbryce to get with John Purrier21:37
jmckenty#action jbryce and John Purrier to get with glance devs as well?21:37
ewanmellorCitrix, of course, has lots of IP in the conversions-between-hypervisors space.21:38
jbryceyes21:38
jbrycelet's keep it moving21:38
jbryce#topic Versioning and minor releases21:38
*** openstack changes topic to "Versioning and minor releases"21:38
jmckentyooh, fun21:38
creihtheh21:38
jbrycedid you all get a chance to review theirry's presentation of the issue in his email?21:38
ewanmelloro21:38
ewanmellorNo21:38
creihtI did21:38
ewanmellorRecent email?21:39
creihta while ago21:39
jbrycehttps://lists.launchpad.net/openstack-poc/msg00036.html - it's in this message21:39
jbryceewanmellor: from tuesday when i sent out the agenda21:39
ewanmellorOh yeah, I read that.21:40
jmckentyMy take is that people will use packaged distibutions21:40
ewanmellorI wondered whether Canonical's new involvement changed anything.21:40
ewanmellori.e., what Josh just said.21:40
jmckentyI would also suggest we hold off on making a decision on this until the testing environment is running properly21:41
jmckentye.g., we can tell Canonical and RedHat that we think trunk is a good candidate for a stable bug-fix release when the tests are all passing21:41
vishyjust based on the number of bugfixes we put in post bexar, it would be nice to get that out somehow withoug making people use trunk.21:42
ewanmellorI think the biggest problem is security holes, because they're a PITA for everyone.21:42
jmckentyright, but to get coverage we're going to need to work with the upstream folks on that anyway21:42
jmckentyno?21:42
ewanmellorIf we had a security alert, could we rely on Ubuntu / Canonical to handle everything (CVE, etc) or are we going to have to do that ourselves?21:42
* jmckenty always confuses upstream and downstream21:42
jbrycenot everyone is going to be deploying from a distribution21:43
jmckentyThere's a good case for security (and integration testing, as well) to be managed by a parent openstack project21:43
jbryceand we really only have coverage in one distribution right now21:43
jmckentyand not left to individual components21:43
creihtIs this a question about distribution, or is it about having point releases?21:43
creihtthose seem like 2 separate questions21:43
jmckentyit's about whether we're responsible for point releases,21:44
jmckentyor whether the distribution channels are21:44
jbrycecreiht: the thinking is that the distros would handle those intermediate releases21:44
creihtThat seems a bit silly to me, do we have examples of other projects that do that?21:44
ewanmellorDo we have the capacity to handle point releases, even if we wanted to?  With 3 monthly cycle anyway, it will be hard to have point releases.21:44
creihtThe problem with that is that people that are trying to use a supposedly "stable" release are stuck without bug fixes until the next release21:45
jmckenty#action jbryce to get ahold of our upstream partners for clarification on distribution of security/point releases21:46
ewanmellorcreiht: I'm proposing that they get their bug fixes from the distro.  Assuming that the distro is happy with that!21:46
jmckentyAlso maybe a good idea to hash this out when soren can comment?21:46
creihtIs there an example of any other project that does that?21:46
jbryceyes21:46
ewanmellorcreiht: So we're cutting edge ;-)21:47
jmckentyit wouldn't be the first time21:47
creihtEvery project that I follow does its own releases, which distros pick up21:47
creihtlol21:47
creihtsounds pretty lazy to me21:47
ewanmellor3 monthly releases aren't lazy.21:47
jmckentynot lazy, efficient. We're better coders than packagers, right?21:47
ewanmellorIs anyone doing 3 monthly releases _and_ doing their own point releases?21:47
creihtIt is if you are trying ot implement what someone has released, but has to wait 3 months for a bugfix21:47
creihtWe already have people running 1.0 and 1.1 swift code21:48
jmckentyAgain, I think the testing environment will really help with this21:48
creihtmostly 1.1 now21:48
jmckentywe can tag trunk when things look reasonably good21:48
ewanmellorcreiht: Does Swift plan to keep going with 3 monthly releases?  It's obviously at a different maturity level than Nova.21:48
creihtPerhaps a better suggestion21:48
creihtPerhaps we can leave this to the project's disgretion?21:49
* jmckenty longs for the day when Nova gets split into volumes, compute, and networking.21:49
creihtthe default is that projects will have timed releases21:49
creihtif a project chooses to, allow them to manage point releases21:49
jbrycecreiht: i kind of like that21:50
creihtEven to support swift internally at RS, it is difficult to do this with out allowing us to make point releases21:50
jmckentyAs long as the full set of components (especially ones that interop heavily) work together every major upstream release, I think project-by-project point releases make sense21:50
jmckentyBut esp. between glance and nova, and probably the new queue stuff as well, I think we may end up with ugly point-to-point release dependencies21:51
creihtjmckenty: that's what packaging is for right? :)21:51
vishySo, we have one significant problem that needs to be solved21:52
vishybexar has some significant bugs21:52
* jmckenty hates packaging, and praises those who do it well21:52
jmckentyvishy: can we blame you for those?21:52
vishywhy not do a .1 release?21:52
vishyyes21:52
jmckentynova bugs, or swift bugs?21:52
vishynova21:52
vishyare we worried about having to support .0 and .1?21:52
creihtThe current bexar issue I think highlights the issue, what seems to me to be a very straight forward, yes fix it issue has turned into quite a debachle21:52
jmckentyso how do we decide we're ready for the .121:52
creihtand people are still downloading broken version21:53
vishyi think the teams could propose and vote on a .1 release (or we could nominate patches for backporting)21:53
creihtjmckenty: seems like that should be up to the project21:53
jmckentySo if we're going to support point releases, I think we should encourage folks to install from PPA and not a tarball21:54
creihtjmckenty: what's the difference?21:54
creihtand not everyone is on debian21:54
creiht /ubuntu21:54
creihtI agree that we should offer both21:55
jmckentywe're hosting the project on launchpad, so I think we've telegraphed our biases there a bit. Upgrading a PPA is easier, IMO.21:55
jmckentyditto for an APT repo, then21:55
creihtagreed, but we can't be blind to the rest of the linux community21:55
ewanmellorAt work, we fix the bug in trunk and then tag it with "candidate for backport" and let the release manager decide which ones should be backported into the next point release.  They then get the dev to backport as necessary, or just do the merges themselves.21:55
ewanmellorIs this something that we can do with Launchpad.21:56
ewanmellor?21:56
creihtewanmellor: yeah lp lets you tag bugs to other release milestones21:56
dendrobatesewanmellor: yes21:56
creihtand then has a separate set of fields for tracking21:56
creihtWe've done that with a couple of bugs in swift, and it works quite well21:56
ewanmellorSo would Thierry be the one to manage the point release?  When we have one, and which things go in it when we do?21:57
creihtlp actually makes the backport process pretty easy21:57
dendrobatesewanmellor: I think he would, yes21:57
creihtewanmellor: I think that should be up to the project, and the release manager helps facilitate it21:57
jmckentyewanmellor: I think anyone in the community should be able to petition the project21:57
*** annegentle has joined #openstack-meeting21:57
ewanmellorI'm fine with the project having point releases, as long as you guys think that you've got resources to do it.21:57
creihtthe release manager shouldn't be the one makeing those specific decisions21:57
jbryceok21:58
jmckentycreiht: I second that21:58
jbryceso let's see if there's a proposal here shaping up21:58
ewanmellorcreiht: We give the job to them, because they have to analyse risk vs impact.21:58
jbryce1) intermediate release policy is determined at the project level21:58
jbryce2) release manager helps facilitate intermediate releases if the project determines it's necessary21:59
creihtewanmellor: then we need release manager dedicated to each team that really knows what things will impact21:59
jmckentycreiht and ewanmellor: the release manager should default to saying no if they're unsure21:59
creihtotherwise how do they really know what is a risk and what isn't21:59
jmckentyand the dev or community member can do the merge and try and prove it's safe21:59
jmckentyor get core team members to weigh in22:00
ewanmellorcreiht: The release manager is expected to speak to the devs until they understand the risk.22:00
ewanmellorBut that's a commercial setting where we're all in the same room.  It's not necessarily going to work well in a global OSS setting.22:00
jbryceso we're right up to 4:00 now--i know there are some who have to leave22:00
jmckentyright, but we *are* going to run out of resources if we start having thierry spinning point releases22:00
jmckentyGSOC?22:01
jbryce#action jbryce to start email thread on release process for POC to continue discussion22:01
jbryce#topic next meeting time22:01
*** openstack changes topic to "next meeting time"22:01
jbrycesince we have a couple of unresolved issues, can we get together again same time next week?22:01
creihtsure22:01
vishy+122:01
jmckenty+122:02
creiht+122:02
*** pvo has quit IRC22:02
dendrobates+122:02
ewanmellor+122:02
ewanmellorWell, +0.522:02
ewanmellorI might not make it.22:02
jbryce21:00 UTC 2/1722:02
jmckentythanks everyone22:03
jbrycethanks guys...i'll send around a couple of emails and we can continue the discussion there22:03
creihtsounds good22:03
jbryceewanmellor: if there's a nearby time that works better, maybe we can adjust slightly22:03
ewanmellorDoes that mean that GSOC is floating for another week?22:03
* creiht has time if we wish to discuss22:03
jmckentyare we up against any deadlines there?22:03
ewanmellorjbryce: Thanks, but no, 10pm is just as bad as 9pm or 11pm.22:03
dendrobatesyes the gsoc is closing mar 10 I think22:04
dendrobatesfor submissions that is22:04
creihtdeadline in mar 1122:04
creihtsubmissions can't start until feb 2822:04
creihtso waiting a week probably isn't bad22:04
jbryceon GSOC, you guys can continue to discuss...i've got to run. if someone can just send out a note to the list of any major points we can continue there22:04
ewanmellorI have half-an-hour before my next call.  Does anyone want to discuss GSOC, or shall we postpone?  I'm fine either way.22:05
creihtsounds like postpone22:06
jbrycesee you guys. thanks for the time!22:06
jbryce#endmeeting22:06
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:06
openstackMeeting ended Thu Feb 10 22:06:15 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-02-10-21.00.html22:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-02-10-21.00.txt22:06
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-02-10-21.00.log.html22:06
*** ewanmellor has quit IRC22:06
*** jbryce has quit IRC22:06
*** dabo has left #openstack-meeting22:07
*** dendrobates is now known as dendro-afk22:08
*** dendro-afk is now known as dendrobates22:09
*** annegentle has left #openstack-meeting22:09
*** pvo has joined #openstack-meeting22:13
*** creiht has left #openstack-meeting22:14
*** jaypipes has quit IRC22:18
*** pvo has quit IRC22:19
*** Sandys has joined #openstack-meeting22:30
*** Sandys has quit IRC22:31
*** GasbaKid has quit IRC22:41
*** GasbaKid has joined #openstack-meeting22:42
*** jmckenty has quit IRC22:55
*** GasbaKid has quit IRC23:04
*** littleidea has joined #openstack-meeting23:10
*** littleidea has quit IRC23:38

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