*** alekibango has quit IRC | 01:52 | |
*** zul has quit IRC | 03:02 | |
*** zul has joined #openstack-meeting | 03:03 | |
*** kpepple has joined #openstack-meeting | 03:10 | |
*** kpepple has quit IRC | 03:11 | |
*** kpepple has joined #openstack-meeting | 03:11 | |
*** adjohn has joined #openstack-meeting | 03:12 | |
*** kpepple has quit IRC | 03:17 | |
*** kpepple has joined #openstack-meeting | 03:18 | |
*** kpepple has quit IRC | 03:23 | |
*** kpepple has joined #openstack-meeting | 03:24 | |
*** kpepple has joined #openstack-meeting | 03:27 | |
*** kpepple has quit IRC | 03:29 | |
*** kpepple has joined #openstack-meeting | 03:29 | |
*** kpepple has quit IRC | 03:32 | |
*** kpepple has joined #openstack-meeting | 03:32 | |
*** kpepple has quit IRC | 03:33 | |
*** kpepple has joined #openstack-meeting | 03:33 | |
*** kpepple has quit IRC | 03:35 | |
*** kpepple has joined #openstack-meeting | 03:36 | |
*** kpepple has quit IRC | 03:40 | |
*** kpepple has joined #openstack-meeting | 03:41 | |
*** kpepple has quit IRC | 03:45 | |
*** kpepple_ has joined #openstack-meeting | 03:45 | |
*** littleidea has joined #openstack-meeting | 03:46 | |
*** kpepple_ has quit IRC | 03:47 | |
*** kpepple has joined #openstack-meeting | 03:47 | |
*** kpepple has quit IRC | 03:52 | |
*** kpepple_ has joined #openstack-meeting | 03:52 | |
*** kpepple_ has quit IRC | 03:54 | |
*** kpepple has joined #openstack-meeting | 03:54 | |
*** littleidea has quit IRC | 03:56 | |
*** kpepple has quit IRC | 04:01 | |
*** kpepple has joined #openstack-meeting | 04:02 | |
*** kpepple has quit IRC | 04:02 | |
*** kpepple has joined #openstack-meeting | 04:03 | |
*** kpepple has quit IRC | 04:07 | |
*** kpepple has joined #openstack-meeting | 04:08 | |
*** kpepple has quit IRC | 04:09 | |
*** kpepple has joined #openstack-meeting | 04:09 | |
*** kpepple has quit IRC | 04:14 | |
*** kpepple has joined #openstack-meeting | 04:14 | |
*** kpepple has quit IRC | 04:19 | |
*** kpepple has joined #openstack-meeting | 04:20 | |
*** kpepple has quit IRC | 04:22 | |
*** kpepple has joined #openstack-meeting | 04:22 | |
*** kpepple has quit IRC | 04:24 | |
*** kpepple has joined #openstack-meeting | 04:24 | |
*** kpepple has quit IRC | 04:26 | |
*** kpepple has joined #openstack-meeting | 04:27 | |
*** kpepple has quit IRC | 04:28 | |
*** kpepple has joined #openstack-meeting | 04:28 | |
*** kpepple has quit IRC | 04:33 | |
*** kpepple has joined #openstack-meeting | 04:33 | |
*** kpepple has quit IRC | 04:34 | |
*** kpepple has joined #openstack-meeting | 04:34 | |
*** kpepple has joined #openstack-meeting | 04:36 | |
*** kpepple has quit IRC | 04:37 | |
*** kpepple has joined #openstack-meeting | 04:38 | |
*** littleidea has joined #openstack-meeting | 04:41 | |
*** kpepple has quit IRC | 04:42 | |
*** kpepple has joined #openstack-meeting | 04:43 | |
*** kpepple has quit IRC | 04:49 | |
*** kpepple has joined #openstack-meeting | 04:50 | |
*** kpepple_ has joined #openstack-meeting | 04:55 | |
*** kpepple has quit IRC | 04:55 | |
*** littleidea has quit IRC | 04:57 | |
*** kpepple_ has quit IRC | 05:02 | |
*** kpepple has joined #openstack-meeting | 05:03 | |
*** kpepple has quit IRC | 05:04 | |
*** kpepple has joined #openstack-meeting | 05:04 | |
*** pvo has joined #openstack-meeting | 05:05 | |
*** kpepple has quit IRC | 05:06 | |
*** kpepple has joined #openstack-meeting | 05:06 | |
*** pvo has quit IRC | 05:07 | |
*** kpepple has quit IRC | 05:13 | |
*** kpepple has joined #openstack-meeting | 05:13 | |
*** kpepple has quit IRC | 05:18 | |
*** kpepple has joined #openstack-meeting | 05:18 | |
*** kpepple has quit IRC | 05:22 | |
*** kpepple has joined #openstack-meeting | 05:23 | |
*** kpepple has quit IRC | 05:24 | |
*** kpepple has joined #openstack-meeting | 05:25 | |
*** kpepple has joined #openstack-meeting | 05:27 | |
*** kpepple has joined #openstack-meeting | 05:29 | |
*** kpepple has joined #openstack-meeting | 05:31 | |
*** kpepple has quit IRC | 05:35 | |
*** littleidea has joined #openstack-meeting | 05:36 | |
*** kpepple has joined #openstack-meeting | 05:36 | |
*** littleidea_ has joined #openstack-meeting | 05:37 | |
*** littleidea has quit IRC | 05:40 | |
*** littleidea_ is now known as littleidea | 05:40 | |
*** kpepple has quit IRC | 05:45 | |
*** kpepple has joined #openstack-meeting | 05:45 | |
*** kpepple has quit IRC | 05:50 | |
*** kpepple has joined #openstack-meeting | 05:50 | |
*** kpepple has quit IRC | 05:52 | |
*** kpepple has joined #openstack-meeting | 05:52 | |
*** kpepple has quit IRC | 05:54 | |
*** kpepple has joined #openstack-meeting | 05:54 | |
*** kpepple_ has joined #openstack-meeting | 05:59 | |
*** kpepple has quit IRC | 05:59 | |
*** kpepple_ has quit IRC | 06:04 | |
*** kpepple has joined #openstack-meeting | 06:04 | |
*** kpepple has quit IRC | 06:08 | |
*** kpepple has joined #openstack-meeting | 06:09 | |
*** kpepple has joined #openstack-meeting | 06:11 | |
*** kpepple has quit IRC | 06:15 | |
*** kpepple has joined #openstack-meeting | 06:16 | |
*** kpepple has quit IRC | 06:20 | |
*** kpepple has joined #openstack-meeting | 06:21 | |
*** kpepple has quit IRC | 06:29 | |
*** kpepple_ has joined #openstack-meeting | 06:29 | |
*** kpepple_ has quit IRC | 06:34 | |
*** kpepple has joined #openstack-meeting | 06:35 | |
*** kpepple has quit IRC | 06:35 | |
*** kpepple has joined #openstack-meeting | 06:36 | |
*** kpepple_ has joined #openstack-meeting | 06:41 | |
*** kpepple has quit IRC | 06:41 | |
*** kpepple_ has quit IRC | 06:45 | |
*** littleidea has joined #openstack-meeting | 07:19 | |
*** kpepple has joined #openstack-meeting | 07:30 | |
*** kpepple_ has joined #openstack-meeting | 07:38 | |
*** kpepple has quit IRC | 07:39 | |
*** kpepple_ is now known as kpepple | 07:39 | |
*** kpepple has quit IRC | 07:40 | |
*** kpepple has joined #openstack-meeting | 07:40 | |
*** kpepple has quit IRC | 07:54 | |
*** kpepple has joined #openstack-meeting | 07:54 | |
*** kpepple has quit IRC | 07:59 | |
*** kpepple has joined #openstack-meeting | 07:59 | |
*** kpepple has quit IRC | 08:02 | |
*** kpepple has joined #openstack-meeting | 08:03 | |
*** kpepple has quit IRC | 08:10 | |
*** kpepple has joined #openstack-meeting | 08:11 | |
*** kpepple has quit IRC | 08:15 | |
*** kpepple has joined #openstack-meeting | 08:16 | |
*** littleidea has quit IRC | 08:16 | |
*** littleidea has joined #openstack-meeting | 08:17 | |
*** westmaas has quit IRC | 08:18 | |
*** kpepple has quit IRC | 08:20 | |
*** kpepple has joined #openstack-meeting | 08:21 | |
*** kpepple has quit IRC | 08:27 | |
*** kpepple has joined #openstack-meeting | 08:27 | |
*** kpepple has quit IRC | 08:32 | |
*** kpepple has joined #openstack-meeting | 08:32 | |
*** kpepple has quit IRC | 08:33 | |
*** kpepple has joined #openstack-meeting | 08:33 | |
*** littleidea has quit IRC | 08:34 | |
*** kpepple has joined #openstack-meeting | 08:34 | |
*** kpepple has joined #openstack-meeting | 08:35 | |
*** kpepple has quit IRC | 08:40 | |
*** kpepple has joined #openstack-meeting | 08:40 | |
*** kpepple has quit IRC | 08:51 | |
*** kpepple has joined #openstack-meeting | 08:52 | |
*** kpepple has quit IRC | 08:53 | |
*** kpepple has joined #openstack-meeting | 08:54 | |
*** kpepple has quit IRC | 08:58 | |
*** kpepple has joined #openstack-meeting | 08:59 | |
*** kpepple has quit IRC | 09:12 | |
*** kpepple has joined #openstack-meeting | 09:14 | |
*** kpepple has quit IRC | 09:18 | |
*** kpepple has joined #openstack-meeting | 09:19 | |
*** kpepple has quit IRC | 09:21 | |
*** kpepple has joined #openstack-meeting | 09:21 | |
*** kpepple has quit IRC | 09:25 | |
*** kpepple has joined #openstack-meeting | 09:26 | |
*** kpepple has quit IRC | 09:28 | |
*** kpepple has joined #openstack-meeting | 09:28 | |
*** kpepple has quit IRC | 09:33 | |
*** kpepple_ has joined #openstack-meeting | 09:33 | |
*** kpepple_ has quit IRC | 09:38 | |
*** kpepple has joined #openstack-meeting | 09:38 | |
*** kpepple has quit IRC | 09:40 | |
*** kpepple has joined #openstack-meeting | 09:40 | |
*** kpepple has quit IRC | 09:45 | |
*** kpepple has joined #openstack-meeting | 09:45 | |
*** kpepple has quit IRC | 09:50 | |
*** kpepple has joined #openstack-meeting | 09:50 | |
*** kpepple has quit IRC | 09:52 | |
*** kpepple has joined #openstack-meeting | 09:52 | |
*** kpepple has quit IRC | 09:56 | |
*** kpepple has joined #openstack-meeting | 09:57 | |
*** kpepple has quit IRC | 10:02 | |
*** kpepple_ has joined #openstack-meeting | 10:02 | |
*** kpepple has joined #openstack-meeting | 10:03 | |
*** kpepple has joined #openstack-meeting | 10:04 | |
*** kpepple has quit IRC | 10:11 | |
*** kpepple has joined #openstack-meeting | 10:12 | |
*** kpepple has quit IRC | 10:17 | |
*** kpepple has joined #openstack-meeting | 10:18 | |
*** kpepple has quit IRC | 10:23 | |
*** kpepple has joined #openstack-meeting | 10:24 | |
*** kpepple has quit IRC | 10:25 | |
*** kpepple has joined #openstack-meeting | 10:26 | |
*** kpepple has joined #openstack-meeting | 10:27 | |
*** kpepple has quit IRC | 10:31 | |
*** kpepple has joined #openstack-meeting | 10:32 | |
*** kpepple has quit IRC | 10:33 | |
*** kpepple has joined #openstack-meeting | 10:34 | |
*** kpepple has quit IRC | 10:34 | |
*** kpepple has joined #openstack-meeting | 10:35 | |
*** adjohn has quit IRC | 10:37 | |
*** kpepple has quit IRC | 10:41 | |
*** kpepple has joined #openstack-meeting | 10:42 | |
*** kpepple has quit IRC | 10:48 | |
*** kpepple_ has joined #openstack-meeting | 10:49 | |
*** kpepple_ has quit IRC | 10:53 | |
*** kpepple has joined #openstack-meeting | 10:54 | |
*** kpepple has quit IRC | 10:58 | |
*** kpepple has joined #openstack-meeting | 10:59 | |
*** kpepple has quit IRC | 11:03 | |
*** kpepple has joined #openstack-meeting | 11:04 | |
*** kpepple has quit IRC | 11:08 | |
*** kpepple_ has joined #openstack-meeting | 11:09 | |
*** kpepple_ has quit IRC | 11:13 | |
*** kpepple has joined #openstack-meeting | 11:14 | |
*** kpepple has quit IRC | 11:18 | |
*** kpepple has joined #openstack-meeting | 11:19 | |
*** kpepple has quit IRC | 11:20 | |
*** kpepple has joined #openstack-meeting | 11:21 | |
*** kpepple has quit IRC | 11:25 | |
*** kpepple has joined #openstack-meeting | 11:26 | |
*** kpepple has quit IRC | 11:31 | |
*** kpepple_ has joined #openstack-meeting | 11:31 | |
*** kpepple_ has quit IRC | 11:35 | |
*** kpepple has joined #openstack-meeting | 11:36 | |
*** kpepple has quit IRC | 11:40 | |
*** kpepple has joined #openstack-meeting | 11:40 | |
*** kpepple has quit IRC | 11:44 | |
*** kpepple has joined #openstack-meeting | 11:45 | |
*** kpepple has quit IRC | 11:46 | |
*** kpepple has joined #openstack-meeting | 11:47 | |
*** kpepple has quit IRC | 11:51 | |
*** kpepple has joined #openstack-meeting | 11:52 | |
*** kpepple has quit IRC | 11:56 | |
*** kpepple has joined #openstack-meeting | 11:57 | |
*** kpepple has quit IRC | 12:00 | |
*** kpepple has joined #openstack-meeting | 12:01 | |
*** kpepple has quit IRC | 12:05 | |
*** kpepple has joined #openstack-meeting | 12:06 | |
*** kpepple has quit IRC | 12:08 | |
*** kpepple has joined #openstack-meeting | 12:08 | |
*** kpepple has quit IRC | 12:12 | |
*** kpepple has joined #openstack-meeting | 12:13 | |
*** kpepple_ has joined #openstack-meeting | 12:20 | |
*** kpepple has quit IRC | 12:20 | |
*** kpepple_ has quit IRC | 12:25 | |
*** kpepple has joined #openstack-meeting | 12:25 | |
*** kpepple_ has joined #openstack-meeting | 12:30 | |
*** kpepple has quit IRC | 12:30 | |
*** kpepple_ has quit IRC | 12:34 | |
*** kpepple has joined #openstack-meeting | 12:35 | |
*** kpepple has quit IRC | 12:36 | |
*** kpepple has joined #openstack-meeting | 12:36 | |
*** kpepple has quit IRC | 12:39 | |
*** kpepple has joined #openstack-meeting | 12:40 | |
*** kpepple has quit IRC | 12:49 | |
*** kpepple has joined #openstack-meeting | 12:49 | |
*** kpepple has quit IRC | 12:54 | |
*** kpepple has joined #openstack-meeting | 12:55 | |
*** kpepple has quit IRC | 12:59 | |
*** kpepple has joined #openstack-meeting | 13:00 | |
*** kpepple has quit IRC | 13:04 | |
*** kpepple_ has joined #openstack-meeting | 13:04 | |
*** kpepple_ has quit IRC | 13:08 | |
*** kpepple has joined #openstack-meeting | 13:09 | |
*** kpepple has quit IRC | 13:13 | |
*** kpepple has joined #openstack-meeting | 13:14 | |
*** kpepple has quit IRC | 13:24 | |
*** kpepple has joined #openstack-meeting | 13:25 | |
*** kpepple has quit IRC | 13:29 | |
*** kpepple has joined #openstack-meeting | 13:31 | |
*** kpepple has quit IRC | 13:32 | |
*** kpepple has joined #openstack-meeting | 13:32 | |
*** kpepple has quit IRC | 13:37 | |
*** kpepple has joined #openstack-meeting | 13:37 | |
*** kpepple has quit IRC | 13:39 | |
*** kpepple has joined #openstack-meeting | 13:40 | |
*** zul has quit IRC | 13:40 | |
*** zul has joined #openstack-meeting | 13:40 | |
*** kpepple has quit IRC | 13:44 | |
*** kpepple has joined #openstack-meeting | 13:45 | |
*** dprince has joined #openstack-meeting | 13:46 | |
*** kpepple has quit IRC | 13:52 | |
*** kpepple has joined #openstack-meeting | 13:52 | |
*** kpepple has quit IRC | 14:01 | |
*** kpepple has joined #openstack-meeting | 14:01 | |
*** adjohn has joined #openstack-meeting | 14:03 | |
*** westmaas has joined #openstack-meeting | 14:04 | |
*** kpepple has quit IRC | 14:05 | |
*** kpepple has joined #openstack-meeting | 14:05 | |
*** kpepple has quit IRC | 14:09 | |
*** kpepple has joined #openstack-meeting | 14:10 | |
*** kpepple has quit IRC | 14:15 | |
*** kpepple has joined #openstack-meeting | 14:16 | |
*** kpepple has quit IRC | 14:17 | |
*** kpepple has joined #openstack-meeting | 14:17 | |
*** kpepple has joined #openstack-meeting | 14:19 | |
*** kpepple has quit IRC | 14:24 | |
*** kpepple has joined #openstack-meeting | 14:24 | |
*** kpepple has quit IRC | 14:28 | |
*** kpepple has joined #openstack-meeting | 14:29 | |
*** adjohn has quit IRC | 14:33 | |
*** kpepple has quit IRC | 14:33 | |
*** kpepple has joined #openstack-meeting | 14:35 | |
*** kpepple has quit IRC | 14:38 | |
*** kpepple has joined #openstack-meeting | 14:39 | |
*** adjohn has joined #openstack-meeting | 14:40 | |
*** adjohn has joined #openstack-meeting | 14:43 | |
*** kpepple_ has joined #openstack-meeting | 14:46 | |
*** kpepple has quit IRC | 14:46 | |
*** kpepple_ has quit IRC | 14:47 | |
*** kpepple has joined #openstack-meeting | 14:48 | |
*** kpepple has quit IRC | 14:52 | |
*** kpepple_ has joined #openstack-meeting | 14:52 | |
*** kpepple_ has quit IRC | 14:56 | |
*** adjohn has quit IRC | 14:57 | |
*** kpepple has joined #openstack-meeting | 14:57 | |
*** kpepple has quit IRC | 15:11 | |
*** littleidea has joined #openstack-meeting | 15:11 | |
*** kpepple has joined #openstack-meeting | 15:11 | |
*** jsgotangco has joined #openstack-meeting | 15:20 | |
*** dendrobates is now known as dendro-afk | 15:23 | |
*** dendro-afk is now known as dendrobates | 15:24 | |
*** littleidea has quit IRC | 15:27 | |
*** kpepple has quit IRC | 15:29 | |
*** kpepple_ has joined #openstack-meeting | 15:29 | |
*** kpepple_ has quit IRC | 15:34 | |
*** kpepple has joined #openstack-meeting | 15:34 | |
*** kpepple has quit IRC | 15:39 | |
*** kpepple has joined #openstack-meeting | 15:39 | |
*** kpepple has quit IRC | 15:48 | |
*** kpepple has joined #openstack-meeting | 15:49 | |
*** kpepple has quit IRC | 15:50 | |
*** kpepple has joined #openstack-meeting | 15:50 | |
*** kpepple has quit IRC | 15:51 | |
*** kpepple has joined #openstack-meeting | 15:51 | |
*** kpepple has quit IRC | 15:53 | |
*** kpepple has joined #openstack-meeting | 15:53 | |
*** kpepple has quit IRC | 15:58 | |
*** kpepple has joined #openstack-meeting | 15:58 | |
*** kpepple has quit IRC | 16:03 | |
*** kpepple has joined #openstack-meeting | 16:03 | |
*** kpepple has quit IRC | 16:07 | |
*** kpepple has joined #openstack-meeting | 16:07 | |
*** kpepple has quit IRC | 16:12 | |
*** kpepple has joined #openstack-meeting | 16:12 | |
*** kpepple has quit IRC | 16:17 | |
*** kpepple has joined #openstack-meeting | 16:18 | |
*** kpepple_ has joined #openstack-meeting | 16:22 | |
*** kpepple has quit IRC | 16:22 | |
*** kpepple_ has quit IRC | 16:36 | |
*** kpepple has joined #openstack-meeting | 16:37 | |
*** kpepple has quit IRC | 16:44 | |
*** GasbaKid has joined #openstack-meeting | 16:44 | |
*** kpepple has joined #openstack-meeting | 16:44 | |
*** kpepple has quit IRC | 16:46 | |
*** kpepple has joined #openstack-meeting | 16:46 | |
*** kpepple has quit IRC | 16:55 | |
*** kpepple has joined #openstack-meeting | 16:56 | |
*** kpepple has quit IRC | 17:00 | |
*** kpepple has joined #openstack-meeting | 17:01 | |
*** dprince has quit IRC | 17:05 | |
*** kpepple has quit IRC | 17:05 | |
*** kpepple has joined #openstack-meeting | 17:06 | |
*** kpepple has quit IRC | 17:13 | |
*** kpepple has joined #openstack-meeting | 17:14 | |
*** kpepple has quit IRC | 17:16 | |
*** kpepple has joined #openstack-meeting | 17:16 | |
*** kpepple has quit IRC | 17:21 | |
*** kpepple has joined #openstack-meeting | 17:21 | |
*** kpepple has quit IRC | 17:22 | |
*** kpepple has joined #openstack-meeting | 17:22 | |
*** dprince has joined #openstack-meeting | 17:22 | |
*** GasbaKid has quit IRC | 17:24 | |
*** GasbaKid has joined #openstack-meeting | 17:25 | |
*** kpepple has quit IRC | 17:27 | |
*** dprince has quit IRC | 17:27 | |
*** kpepple has joined #openstack-meeting | 17:27 | |
*** dprince has joined #openstack-meeting | 17:29 | |
*** kpepple has quit IRC | 17:44 | |
*** kpepple has joined #openstack-meeting | 17:44 | |
*** kpepple has quit IRC | 17:49 | |
*** kpepple has joined #openstack-meeting | 17:49 | |
*** kpepple has quit IRC | 17:51 | |
*** GasbaKid has quit IRC | 18:09 | |
*** dprince has quit IRC | 18:09 | |
*** dprince has joined #openstack-meeting | 18:12 | |
*** dendrobates is now known as dendro-afk | 18:19 | |
*** dendro-afk is now known as dendrobates | 18:19 | |
*** DigitalFlux has joined #openstack-meeting | 18:56 | |
*** DigitalFlux has quit IRC | 18:58 | |
*** dprince_ has joined #openstack-meeting | 19:01 | |
*** dprince has quit IRC | 19:01 | |
*** dprince_ has quit IRC | 19:08 | |
*** dprince has joined #openstack-meeting | 19:10 | |
*** dprince has quit IRC | 19:18 | |
*** dprince has joined #openstack-meeting | 20:18 | |
*** dprince has quit IRC | 20:20 | |
*** jbryce has joined #openstack-meeting | 20:22 | |
*** jmckenty has joined #openstack-meeting | 20:27 | |
*** creiht has joined #openstack-meeting | 20:31 | |
jmckenty | Are we still on for a POC meeting in here in 28 minutes? | 20:32 |
---|---|---|
creiht | as far as I know | 20:48 |
*** sandywalsh_ has quit IRC | 20:50 | |
jmckenty | aight. | 20:50 |
*** sandywalsh_ has joined #openstack-meeting | 20:53 | |
*** sandywalsh_ is now known as sandywalsh | 20:54 | |
jbryce | all right...let's get this started | 21:00 |
jbryce | #startmeeting | 21:00 |
openstack | Meeting started Thu Feb 10 21:00:43 2011 UTC. The chair is jbryce. Information about MeetBot at http://wiki.debian.org/MeetBot. | 21:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 21:00 |
jmckenty | ola | 21:01 |
*** bcwaldon has joined #openstack-meeting | 21:01 | |
* creiht bows | 21:01 | |
jmckenty | agenda? | 21:01 |
jbryce | So i see 6 of us here--looks like we're missing jesse, ewan and mark. jesse is supposed to be joining shortly | 21:01 |
jbryce | agenda can be seen at the bottom of the page here: http://wiki.openstack.org/Governance/POC | 21:01 |
jbryce | #topic 2011 scope and charter | 21:02 |
jmckenty | ah, cool | 21:02 |
*** openstack changes topic to "2011 scope and charter" | 21:02 | |
jbryce | so we discussed this on email and there were a few open questions that were raised | 21:02 |
jmckenty | creiht: can you summarize what we've agreed to so far? | 21:02 |
jbryce | one is around the inclusion of the draft service architecture | 21:03 |
jmckenty | ah, right. Yeah, I still think we should make that a separate action. | 21:03 |
jbryce | the other item up for discussion was around the specification of individual languages | 21:03 |
jbryce | so on the service architecture, what specific points do you want to see separated out? | 21:04 |
jbryce | http://wiki.openstack.org/Governance/Proposed/2011%20Charter%20and%20Scope - that's the current proposal state | 21:04 |
*** ewanmellor has joined #openstack-meeting | 21:04 | |
jmckenty | opening it now... | 21:04 |
jbryce | hi ewan...we're just getting started | 21:04 |
ewanmellor | hi | 21:04 |
ewanmellor | Sorry I'm late | 21:04 |
vishy | jesse is on a plane | 21:05 |
jmckenty | so on the service architecture | 21:05 |
vishy | * on his way to a plane | 21:05 |
jmckenty | 1. No problem with public RESTful API as a req | 21:05 |
jmckenty | 2. No problem with RESTful admin API (not sure it should be required to be public) | 21:05 |
jmckenty | And not sure that calling it out as protected by ACL/permissions should be part of the service arch | 21:06 |
jmckenty | since I think there are some innovations I'd like to push forward this year on that front | 21:06 |
jbryce | ok...i can see that | 21:06 |
jmckenty | Don't mind calling out pub/sub as a specific option, but would like to see webhooks mentioned as well | 21:06 |
jmckenty | e.g., programatic webhooks via pub/sub or some other notification mechanism (could be the new queueing stuff that Eric is starting on) | 21:07 |
jbryce | ok...i'm fine with those modifications | 21:07 |
jmckenty | Would 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 |
jmckenty | I guess that's more between API and service framework | 21:08 |
jmckenty | And the last concern was on the extension interface | 21:08 |
jmckenty | I think we'll get ourselves into trouble (astronauting) if we start trying to spec out too much extensionability | 21:08 |
jmckenty | If we're going to describe it as an interface, maybe pointing specifically to what Ewan did with the Xen abstraction? | 21:09 |
jbryce | i 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 |
jbryce | i think the actual details could vary by project and should probably be driven more at that level | 21:10 |
jmckenty | e.g., implementations *must* vs., *can*, and how implementation-specific code gets calls. Extension interface can imply infinitely complex (e.g. XPCOM) | 21:10 |
jmckenty | sure | 21:10 |
vishy | Yes i think broad and general is best at this level | 21:10 |
jmckenty | I just don't want projects to think they need to have XPCOM or a whole run-time scriptable language to qualify | 21:10 |
jmckenty | monkey-patches are extensions, too | 21:11 |
jbryce | as written, it leaves room for that | 21:11 |
jbryce | here's my proposal | 21:11 |
jbryce | 1. modify public management API to say optionally protected | 21:11 |
jbryce | 2. say "such as pub/sub" on the notification interface item | 21:12 |
jbryce | 3. remove the specific languages being called out | 21:12 |
jbryce | then approve this one and move on to other proposals like the process for incubation and project evaluation | 21:13 |
jmckenty | Can we require services to be implemented as WSGI? | 21:13 |
jmckenty | for common auth or what have you | 21:13 |
creiht | jmckenty: Not sure, since WSGI is python specific | 21:13 |
jmckenty | you can make Java / PHP talk WSGI | 21:14 |
jmckenty | if you're crazy | 21:14 |
creiht | not within a python app stack | 21:14 |
creiht | heh | 21:14 |
creiht | at that level that is why we specify RESTful apis | 21:14 |
creiht | to ensure common communication between services | 21:14 |
jmckenty | k, fair enough. I'm good with your plan, jbryce | 21:15 |
jmckenty | creiht: http://pythonpaste.org/wphp/ | 21:15 |
creiht | jmckenty: lol :) | 21:15 |
jbryce | so as amended, let's vote on the 2011 scope charter | 21:15 |
jbryce | +1 | 21:15 |
creiht | +1 | 21:15 |
*** pvo has joined #openstack-meeting | 21:15 | |
vishy | +1 | 21:15 |
jmckenty | +1 | 21:16 |
jmckenty | dendrobates? | 21:16 |
vishy | and ewan? | 21:17 |
jmckenty | and soren ? | 21:17 |
vishy | oh yeah where is soren? | 21:18 |
ewanmellor | I vote 0. | 21:18 |
vishy | is that abstain? | 21:18 |
*** dabo has joined #openstack-meeting | 21:18 | |
ewanmellor | I'm uncomfortable with the idea of telling people how to architect their software in a_ charter_. | 21:18 |
jmckenty | +0 or -0 ? | 21:18 |
ewanmellor | I don't think that we should even be talking about software architecture, when it comes to a charter for OpenStack. | 21:19 |
ewanmellor | But I don't think that there's enough that's bad about the proposal on the table to give it -1. | 21:19 |
jbryce | ewanmellor: even at the broad level of having basic common api technology? | 21:20 |
jmckenty | well, you can give it -0 which is non-blocking | 21:20 |
*** bcwaldon has left #openstack-meeting | 21:20 | |
ewanmellor | So I'm happy for you to proceed, if it's helping something that you're trying to do. | 21:20 |
jbryce | ok | 21:20 |
jbryce | we've got 4 of 7, which is a majority and a quorum | 21:20 |
jmckenty | It gives us some common ground for evaluating proposed projects for inclusion into openstack. I think that's the big win | 21:20 |
ewanmellor | I 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 scope | 21:21 |
ewanmellor | I disagree that RESTful is the right way to design all APIs. | 21:21 |
ewanmellor | But anyway, let's move on. | 21:21 |
* jmckenty and ewanmellor will drink beer and bemoan the bastardization of the term RESTful | 21:21 | |
jbryce | #info 4 approves, 3 abstentions | 21:21 |
jbryce | #topic Image formats | 21:21 |
*** openstack changes topic to "Image formats" | 21:21 | |
jmckenty | ah, fun | 21:21 |
jbryce | this was another proposal on publishing a stance on image formats | 21:22 |
jbryce | http://wiki.openstack.org/Governance/Proposed/ImageFormats - that is the draft | 21:22 |
*** GasbaKid has joined #openstack-meeting | 21:22 | |
ewanmellor | Why is this a governance issue, not just a blueprint for Glance / Nova? | 21:23 |
jbryce | the proposal had 3 main components: | 21:23 |
jmckenty | Can I point us briefly to the Open Cloud Manifesto? | 21:23 |
jbryce | 1) we need a standardized exchange format--proposal is to define an ovf/ova for our use | 21:23 |
jbryce | 2) openstack should not specify preferred/default virtual disk format | 21:23 |
jbryce | 3) glance should be extended to include conversion capabilities (seems like a feature definition/blueprint) | 21:24 |
vishy | both of those points make sense to me | 21:24 |
vishy | a lot of this seems specific to glance | 21:24 |
jmckenty | http://www.opencloudmanifesto.org/opencloudmanifesto6.htm - use and adopt existing standards where appropriate | 21:24 |
*** sirp_ has joined #openstack-meeting | 21:24 | |
ewanmellor | jmckenty: Does that mean "use something that exists if it's the right thing to do, but don't if it's not"? | 21:25 |
vishy | jmckenty: isn't that what is being suggested? | 21:25 |
jmckenty | on the ovf/ova layer, yes | 21:25 |
jmckenty | but the specific statement that we *shouldn't* espouse a standard disk image format, I'm not sure about | 21:25 |
jmckenty | I think perhaps we SHOULD espouse one, but support many | 21:25 |
jmckenty | I don't know if this is a case, such as hypervisors, where there are complex tradeoffs and no clear best choice | 21:26 |
vishy | what is meant by standard? as in what is used on the backend? | 21:26 |
vishy | because I think that is very hypervisor-specific | 21:27 |
jmckenty | The disk format within the OVF | 21:27 |
jmckenty | e.g., within glance and for transport | 21:27 |
jmckenty | anyway, I guess we dodge the issues this way | 21:27 |
jmckenty | "This also sidesteps the potentially divisive topic of support for VHD and the Microsoft Open Promise licensin" | 21:27 |
jbryce | i think what it said was "preferred or default" rather than standard for disk format | 21:27 |
ewanmellor | I have nothing against OVF (my name is on the spec, after all), but just some points of info: | 21:27 |
ewanmellor | OVF doesn't give you interoperability. The metadata standard isn't standard enough to be interoperable. | 21:28 |
ewanmellor | OVF doesn't specify a disk format, so you still need to handle all the disk conversions. | 21:28 |
jmckenty | There's a practice concern around defaults - in order for the install process to be manageable, we *need* defaults | 21:29 |
jmckenty | I would propose the least optimum default - RAW | 21:29 |
jmckenty | everyone supports it, and most installs will switch to something else | 21:29 |
vishy | i think publicly raw is the way to go, perhaps with gz compression | 21:29 |
sirp_ | sirp: raw within a tarball container seems like a sensible default | 21:30 |
vishy | but internally i don't think there is a need to bless a format, and conversions between formats should be provided. | 21:30 |
jmckenty | ewanmellor: do you think it's reasonable to try and draft a restricted OVF definition that WOULD be portable? | 21:30 |
jbryce | ewanmellor: 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 adoption | 21:30 |
jbryce | vishy: i agree | 21:30 |
jmckenty | e.g., *an* OVF, not *any* OVF | 21:30 |
ewanmellor | jmckenty: Yes. You could say "VMware's OVF" or "Citrix's OVF". | 21:31 |
jmckenty | no, I meant "OpenStack's OVF" | 21:31 |
jmckenty | is there a subset that's useful? | 21:31 |
ewanmellor | No, that's my point. | 21:31 |
jbryce | jmckenty: that is what john is proposing | 21:31 |
jmckenty | right. john is proposing it, ewanmellor is saying it's not possible | 21:31 |
jmckenty | ewanmellor, 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 |
vishy | ewanmellor: can't it choose raw? | 21:32 |
ewanmellor | vishy: Yes it can, I think, but then it's useless. | 21:32 |
jmckenty | pourquoi? | 21:32 |
ewanmellor | The OVF spec says "any published format", IIRC, so raw would be acceptable. | 21:33 |
jmckenty | So 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 |
ewanmellor | But 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 |
jmckenty | yes - we noticed that early on :) | 21:34 |
ewanmellor | So if you want to transport it between clouds, all your templates are much much larger than they ever need to be. | 21:34 |
ewanmellor | So it's useless as an interop format, because you can't use it for transport. | 21:34 |
jmckenty | well, hence the tarball proposal, but that's not a supported disk format yet | 21:35 |
ewanmellor | Because 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 |
vishy | i see | 21:36 |
ewanmellor | XenServer'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 |
ewanmellor | It's basically what you're getting at. | 21:36 |
jmckenty | jbryce: I think we may have to take this back offline for more debate | 21:36 |
jbryce | ok...sounds like we need some more thought on this one | 21:36 |
ewanmellor | But then, of course, you're using XenServer's format, not a neutral one. | 21:36 |
jbryce | #info need to re-evaluate proposal | 21:37 |
jmckenty | who's on the glance team - any POC members? | 21:37 |
sirp_ | i am | 21:37 |
sirp_ | jaypipes as well | 21:37 |
jbryce | #action jbryce to get with John Purrier | 21:37 |
jmckenty | #action jbryce and John Purrier to get with glance devs as well? | 21:37 |
ewanmellor | Citrix, of course, has lots of IP in the conversions-between-hypervisors space. | 21:38 |
jbryce | yes | 21:38 |
jbryce | let's keep it moving | 21:38 |
jbryce | #topic Versioning and minor releases | 21:38 |
*** openstack changes topic to "Versioning and minor releases" | 21:38 | |
jmckenty | ooh, fun | 21:38 |
creiht | heh | 21:38 |
jbryce | did you all get a chance to review theirry's presentation of the issue in his email? | 21:38 |
ewanmellor | o | 21:38 |
ewanmellor | No | 21:38 |
creiht | I did | 21:38 |
ewanmellor | Recent email? | 21:39 |
creiht | a while ago | 21:39 |
jbryce | https://lists.launchpad.net/openstack-poc/msg00036.html - it's in this message | 21:39 |
jbryce | ewanmellor: from tuesday when i sent out the agenda | 21:39 |
ewanmellor | Oh yeah, I read that. | 21:40 |
jmckenty | My take is that people will use packaged distibutions | 21:40 |
ewanmellor | I wondered whether Canonical's new involvement changed anything. | 21:40 |
ewanmellor | i.e., what Josh just said. | 21:40 |
jmckenty | I would also suggest we hold off on making a decision on this until the testing environment is running properly | 21:41 |
jmckenty | e.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 passing | 21:41 |
vishy | just 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 |
ewanmellor | I think the biggest problem is security holes, because they're a PITA for everyone. | 21:42 |
jmckenty | right, but to get coverage we're going to need to work with the upstream folks on that anyway | 21:42 |
jmckenty | no? | 21:42 |
ewanmellor | If 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 downstream | 21:42 | |
jbryce | not everyone is going to be deploying from a distribution | 21:43 |
jmckenty | There's a good case for security (and integration testing, as well) to be managed by a parent openstack project | 21:43 |
jbryce | and we really only have coverage in one distribution right now | 21:43 |
jmckenty | and not left to individual components | 21:43 |
creiht | Is this a question about distribution, or is it about having point releases? | 21:43 |
creiht | those seem like 2 separate questions | 21:43 |
jmckenty | it's about whether we're responsible for point releases, | 21:44 |
jmckenty | or whether the distribution channels are | 21:44 |
jbryce | creiht: the thinking is that the distros would handle those intermediate releases | 21:44 |
creiht | That seems a bit silly to me, do we have examples of other projects that do that? | 21:44 |
ewanmellor | Do 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 |
creiht | The problem with that is that people that are trying to use a supposedly "stable" release are stuck without bug fixes until the next release | 21:45 |
jmckenty | #action jbryce to get ahold of our upstream partners for clarification on distribution of security/point releases | 21:46 |
ewanmellor | creiht: I'm proposing that they get their bug fixes from the distro. Assuming that the distro is happy with that! | 21:46 |
jmckenty | Also maybe a good idea to hash this out when soren can comment? | 21:46 |
creiht | Is there an example of any other project that does that? | 21:46 |
jbryce | yes | 21:46 |
ewanmellor | creiht: So we're cutting edge ;-) | 21:47 |
jmckenty | it wouldn't be the first time | 21:47 |
creiht | Every project that I follow does its own releases, which distros pick up | 21:47 |
creiht | lol | 21:47 |
creiht | sounds pretty lazy to me | 21:47 |
ewanmellor | 3 monthly releases aren't lazy. | 21:47 |
jmckenty | not lazy, efficient. We're better coders than packagers, right? | 21:47 |
ewanmellor | Is anyone doing 3 monthly releases _and_ doing their own point releases? | 21:47 |
creiht | It is if you are trying ot implement what someone has released, but has to wait 3 months for a bugfix | 21:47 |
creiht | We already have people running 1.0 and 1.1 swift code | 21:48 |
jmckenty | Again, I think the testing environment will really help with this | 21:48 |
creiht | mostly 1.1 now | 21:48 |
jmckenty | we can tag trunk when things look reasonably good | 21:48 |
ewanmellor | creiht: Does Swift plan to keep going with 3 monthly releases? It's obviously at a different maturity level than Nova. | 21:48 |
creiht | Perhaps a better suggestion | 21:48 |
creiht | Perhaps 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 | |
creiht | the default is that projects will have timed releases | 21:49 |
creiht | if a project chooses to, allow them to manage point releases | 21:49 |
jbryce | creiht: i kind of like that | 21:50 |
creiht | Even to support swift internally at RS, it is difficult to do this with out allowing us to make point releases | 21:50 |
jmckenty | As 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 sense | 21:50 |
jmckenty | But 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 dependencies | 21:51 |
creiht | jmckenty: that's what packaging is for right? :) | 21:51 |
vishy | So, we have one significant problem that needs to be solved | 21:52 |
vishy | bexar has some significant bugs | 21:52 |
* jmckenty hates packaging, and praises those who do it well | 21:52 | |
jmckenty | vishy: can we blame you for those? | 21:52 |
vishy | why not do a .1 release? | 21:52 |
vishy | yes | 21:52 |
jmckenty | nova bugs, or swift bugs? | 21:52 |
vishy | nova | 21:52 |
vishy | are we worried about having to support .0 and .1? | 21:52 |
creiht | The 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 debachle | 21:52 |
jmckenty | so how do we decide we're ready for the .1 | 21:52 |
creiht | and people are still downloading broken version | 21:53 |
vishy | i think the teams could propose and vote on a .1 release (or we could nominate patches for backporting) | 21:53 |
creiht | jmckenty: seems like that should be up to the project | 21:53 |
jmckenty | So if we're going to support point releases, I think we should encourage folks to install from PPA and not a tarball | 21:54 |
creiht | jmckenty: what's the difference? | 21:54 |
creiht | and not everyone is on debian | 21:54 |
creiht | /ubuntu | 21:54 |
creiht | I agree that we should offer both | 21:55 |
jmckenty | we'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 |
jmckenty | ditto for an APT repo, then | 21:55 |
creiht | agreed, but we can't be blind to the rest of the linux community | 21:55 |
ewanmellor | At 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 |
ewanmellor | Is this something that we can do with Launchpad. | 21:56 |
ewanmellor | ? | 21:56 |
creiht | ewanmellor: yeah lp lets you tag bugs to other release milestones | 21:56 |
dendrobates | ewanmellor: yes | 21:56 |
creiht | and then has a separate set of fields for tracking | 21:56 |
creiht | We've done that with a couple of bugs in swift, and it works quite well | 21:56 |
ewanmellor | So 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 |
creiht | lp actually makes the backport process pretty easy | 21:57 |
dendrobates | ewanmellor: I think he would, yes | 21:57 |
creiht | ewanmellor: I think that should be up to the project, and the release manager helps facilitate it | 21:57 |
jmckenty | ewanmellor: I think anyone in the community should be able to petition the project | 21:57 |
*** annegentle has joined #openstack-meeting | 21:57 | |
ewanmellor | I'm fine with the project having point releases, as long as you guys think that you've got resources to do it. | 21:57 |
creiht | the release manager shouldn't be the one makeing those specific decisions | 21:57 |
jbryce | ok | 21:58 |
jmckenty | creiht: I second that | 21:58 |
jbryce | so let's see if there's a proposal here shaping up | 21:58 |
ewanmellor | creiht: We give the job to them, because they have to analyse risk vs impact. | 21:58 |
jbryce | 1) intermediate release policy is determined at the project level | 21:58 |
jbryce | 2) release manager helps facilitate intermediate releases if the project determines it's necessary | 21:59 |
creiht | ewanmellor: then we need release manager dedicated to each team that really knows what things will impact | 21:59 |
jmckenty | creiht and ewanmellor: the release manager should default to saying no if they're unsure | 21:59 |
creiht | otherwise how do they really know what is a risk and what isn't | 21:59 |
jmckenty | and the dev or community member can do the merge and try and prove it's safe | 21:59 |
jmckenty | or get core team members to weigh in | 22:00 |
ewanmellor | creiht: The release manager is expected to speak to the devs until they understand the risk. | 22:00 |
ewanmellor | But 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 |
jbryce | so we're right up to 4:00 now--i know there are some who have to leave | 22:00 |
jmckenty | right, but we *are* going to run out of resources if we start having thierry spinning point releases | 22:00 |
jmckenty | GSOC? | 22:01 |
jbryce | #action jbryce to start email thread on release process for POC to continue discussion | 22:01 |
jbryce | #topic next meeting time | 22:01 |
*** openstack changes topic to "next meeting time" | 22:01 | |
jbryce | since we have a couple of unresolved issues, can we get together again same time next week? | 22:01 |
creiht | sure | 22:01 |
vishy | +1 | 22:01 |
jmckenty | +1 | 22:02 |
creiht | +1 | 22:02 |
*** pvo has quit IRC | 22:02 | |
dendrobates | +1 | 22:02 |
ewanmellor | +1 | 22:02 |
ewanmellor | Well, +0.5 | 22:02 |
ewanmellor | I might not make it. | 22:02 |
jbryce | 21:00 UTC 2/17 | 22:02 |
jmckenty | thanks everyone | 22:03 |
jbryce | thanks guys...i'll send around a couple of emails and we can continue the discussion there | 22:03 |
creiht | sounds good | 22:03 |
jbryce | ewanmellor: if there's a nearby time that works better, maybe we can adjust slightly | 22:03 |
ewanmellor | Does that mean that GSOC is floating for another week? | 22:03 |
* creiht has time if we wish to discuss | 22:03 | |
jmckenty | are we up against any deadlines there? | 22:03 |
ewanmellor | jbryce: Thanks, but no, 10pm is just as bad as 9pm or 11pm. | 22:03 |
dendrobates | yes the gsoc is closing mar 10 I think | 22:04 |
dendrobates | for submissions that is | 22:04 |
creiht | deadline in mar 11 | 22:04 |
creiht | submissions can't start until feb 28 | 22:04 |
creiht | so waiting a week probably isn't bad | 22:04 |
jbryce | on 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 there | 22:04 |
ewanmellor | I 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 |
creiht | sounds like postpone | 22:06 |
jbryce | see you guys. thanks for the time! | 22:06 |
jbryce | #endmeeting | 22:06 |
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/" | 22:06 | |
openstack | Meeting ended Thu Feb 10 22:06:15 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 22:06 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-02-10-21.00.html | 22:06 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-02-10-21.00.txt | 22:06 |
openstack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-02-10-21.00.log.html | 22:06 |
*** ewanmellor has quit IRC | 22:06 | |
*** jbryce has quit IRC | 22:06 | |
*** dabo has left #openstack-meeting | 22:07 | |
*** dendrobates is now known as dendro-afk | 22:08 | |
*** dendro-afk is now known as dendrobates | 22:09 | |
*** annegentle has left #openstack-meeting | 22:09 | |
*** pvo has joined #openstack-meeting | 22:13 | |
*** creiht has left #openstack-meeting | 22:14 | |
*** jaypipes has quit IRC | 22:18 | |
*** pvo has quit IRC | 22:19 | |
*** Sandys has joined #openstack-meeting | 22:30 | |
*** Sandys has quit IRC | 22:31 | |
*** GasbaKid has quit IRC | 22:41 | |
*** GasbaKid has joined #openstack-meeting | 22:42 | |
*** jmckenty has quit IRC | 22:55 | |
*** GasbaKid has quit IRC | 23:04 | |
*** littleidea has joined #openstack-meeting | 23:10 | |
*** littleidea has quit IRC | 23:38 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!