Thursday, 2011-12-01

*** dragondm has quit IRC00:05
*** oubiwann has quit IRC00:06
*** adjohn has quit IRC00:12
*** nati2 has joined #openstack-meeting00:34
*** dendrobates is now known as dendro-afk00:39
*** danwent has joined #openstack-meeting00:50
*** rnirmal has quit IRC00:56
*** dolphm has quit IRC00:59
*** deshantm_laptop has joined #openstack-meeting01:04
*** nati2 has quit IRC01:14
*** nati2 has joined #openstack-meeting01:17
*** dragondm has joined #openstack-meeting01:22
*** vladimir3p has quit IRC01:24
*** beekhof has quit IRC01:26
*** hggdh has quit IRC01:30
*** beekhof_ has joined #openstack-meeting01:31
*** hggdh has joined #openstack-meeting01:34
*** rstarmer has quit IRC01:43
*** reed has quit IRC01:51
*** edconzel has left #openstack-meeting01:55
*** deshantm_laptop_ has joined #openstack-meeting02:05
*** deshantm_laptop has quit IRC02:08
*** jdurgin has quit IRC02:24
*** troytoman-away is now known as troytoman02:34
*** rnirmal has joined #openstack-meeting02:39
*** troytoman is now known as troytoman-away02:39
*** rnirmal has quit IRC02:39
*** shang has joined #openstack-meeting02:44
*** nati2 has quit IRC02:58
*** rnirmal has joined #openstack-meeting03:04
*** rohitk has quit IRC03:05
*** dolphm has joined #openstack-meeting03:15
*** dolphm has quit IRC03:15
*** dolphm has joined #openstack-meeting03:16
*** dwalleck has joined #openstack-meeting03:24
*** dragondm has quit IRC03:29
*** dragondm has joined #openstack-meeting03:31
*** dolphm has quit IRC03:39
*** dolphm_ has joined #openstack-meeting03:58
*** deshantm_laptop_ is now known as deshantm_laptop04:27
*** dragondm has quit IRC04:34
*** danwent has quit IRC04:39
*** deshantm_laptop has quit IRC05:07
*** rnirmal has quit IRC05:11
*** danwent has joined #openstack-meeting05:17
*** rohitk has joined #openstack-meeting05:20
*** dwalleck has quit IRC05:58
*** adiantum has joined #openstack-meeting06:12
*** bencherian has quit IRC06:29
*** dolphm_ has quit IRC06:41
*** lloydde has quit IRC06:50
*** nati2 has joined #openstack-meeting07:34
*** nati2 has quit IRC07:42
*** danwent has quit IRC07:55
*** adiantum has quit IRC08:39
*** rohitk has quit IRC09:45
*** rohitk has joined #openstack-meeting09:45
*** shang has quit IRC10:02
*** rohitk has quit IRC10:12
*** adiantum has joined #openstack-meeting10:14
*** wwkeyboard has left #openstack-meeting12:42
*** cdub has quit IRC13:01
*** AlanClark has joined #openstack-meeting13:52
*** bencherian has joined #openstack-meeting14:41
*** lloydde has joined #openstack-meeting14:47
*** dolphm has joined #openstack-meeting14:54
*** dolphm has quit IRC14:58
*** dolphm has joined #openstack-meeting15:34
*** adjohn has joined #openstack-meeting15:55
*** dragondm has joined #openstack-meeting16:04
*** rnirmal has joined #openstack-meeting16:07
*** rstarmer has joined #openstack-meeting16:08
*** danwent has joined #openstack-meeting16:14
*** adjohn has quit IRC16:27
*** reed has joined #openstack-meeting16:28
*** reed has quit IRC16:36
*** adiantum has quit IRC16:47
*** dolphm has quit IRC16:56
*** dolphm has joined #openstack-meeting16:58
*** bencherian has quit IRC16:59
*** AlanClark has quit IRC16:59
*** AlanClark has joined #openstack-meeting16:59
*** rnirmal has quit IRC17:05
*** dolphm has quit IRC17:05
*** vladimir3p has joined #openstack-meeting17:08
*** rnirmal has joined #openstack-meeting17:14
*** rstarmer has quit IRC17:14
*** rnirmal has quit IRC17:18
*** nati2 has joined #openstack-meeting17:32
*** nati2 has quit IRC17:32
*** nati2 has joined #openstack-meeting17:32
*** rohitk has joined #openstack-meeting17:38
*** adjohn has joined #openstack-meeting17:40
*** bencherian has joined #openstack-meeting17:43
*** reed has joined #openstack-meeting17:55
*** rstarmer has joined #openstack-meeting17:55
*** renuka has joined #openstack-meeting17:57
*** jdg_ has joined #openstack-meeting17:59
*** reed has quit IRC18:00
renukahello.. shall we start the openstack volumes meeting18:01
jdg_sure... unless it's just you and I today.18:01
vladimir3phey18:01
renukacool, we have three18:02
vladimir3p:-)18:02
renuka#startmeeting18:02
openstackMeeting started Thu Dec  1 18:02:36 2011 UTC.  The chair is renuka. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.18:02
renuka#topic openstack volumes18:02
*** openstack changes topic to "openstack volumes"18:02
renukaI mainly had to raise one point,about the usage of the host flag18:03
renukaso before that, do either of you have any updates or would like to discuss anything today?18:03
jdg_Nothing really from me.  I've been trying to set up a cloud in house the past week or so and that's about it.18:04
vladimir3pnope, I have no updates. stuck with integrating our stuff with keystone18:04
renukavladimir3p: so this week or so, you mentioned you can start on the scheduler, is that still on track?18:05
vladimir3phope to start it 1st week of Dec (next week)18:05
vladimir3pbut only if I'll succeed to bring up our keystone :-)18:06
renukaright, keep us in the loop :)18:06
renuka#topic host flag18:07
*** openstack changes topic to "host flag"18:07
renukaso I just wanted to ensure that everyone is aware of this...18:07
renukaso far we have been using the host flag in the code as if it is necessarily an IP address18:07
renukarecently with some upgrade work, it was proposed that it should be a GUID for a machine18:08
renukathat began to break some iscsi tests18:08
renukai believe we have a fix here: https://review.openstack.org/#change,198218:08
renuka#link https://review.openstack.org/#change,198218:08
vladimir3plet me take a look, I'm not sure if we ever experienced such issue...18:09
renukaso please keep in mind that the host flag, and therefore volume['host'] and iscsi_target['host'] may not be IP addresses and could well be some form of IDs18:09
renukayou may not have experienced it yet, because John from citrix is doing the upgrades changes... so they may not be upstream18:10
vladimir3phmm... volume['host'] is always a hostname, isn't it?18:10
renukawell it has been, so far18:10
jdg_So forgive me for the ignorant question, but where is the coorelation made back to an IP?  Assuming some link back to the database?18:10
renukaI am just pointing out that in the future it need not be18:10
renukain that patch on gerrit, we are populating "provider location" with the details of where to find the iscsi target18:11
jdg_Yes, sorry... I just read it in the change link you sent.18:11
*** reed has joined #openstack-meeting18:11
renukaright, so the definition of "host" has been clarified now18:12
vladimir3pok, I see...18:12
*** jdurgin has joined #openstack-meeting18:12
renukasince I would most certainly have read the code assuming volume['host'] is an IP address, I wanted to make it a bit more explicit that it need not be18:13
vladimir3pthis is irrelevant for us, because we never really used it. The IP is filled up from host-specific SW we install on every host and from there we create provider_location18:13
vladimir3prenuka, I still suppose that volume['host'] is just a hostname ...18:13
renukalast conversation I had about this change, it was decided that volume['host'] should continue to be whatever is in the host flag18:14
vladimir3pok18:14
renukain fact it has always been that... i dont think this change changes it18:14
renukalet me check18:14
renukaright, it doesn't18:15
renukaso whenever someone starts the services with the host flag set to something else that is not an IP address, we run the risk of misusing volume['host'] if we are not careful18:16
vladimir3punless this is set to default value, which is hostname18:17
vladimir3pand supposed to be unique18:17
renukait will be unique in either case...we just don't have a guarantee that it can be used as an IP address18:18
renukafor example, with the recent changes, the iscsiadm commands were failing, because the code does a "-p volume['host']"18:18
renukathat assumes it is an IP address18:19
renukaso any such lines of code, we need to watch out for18:19
vladimir3prenuka, just to understand ... if you override FLAGS.host with an IP address it means that on all levels (schedulers, API, etc) you are using IP and not a hostname18:20
vladimir3pwhich is fine, but it is on all levels18:20
renukayes18:20
vladimir3pFLAGS.host is kind of "global" param for Manager18:20
renukayes18:20
vladimir3pit means that all compute services and others are using it18:20
vladimir3pok18:20
renukathis caveat does apply to any other coding that you are doing also18:21
vladimir3phmm... not really18:21
vladimir3pwe don't care what exactly is set in host field18:22
jdg_cd vsa18:22
vladimir3pit just should be unique18:22
jdg_ls18:22
jdg_sorry18:22
vladimir3p:-)18:22
renuka#info FLAGS.host and therefore volume['host'] need not always be an IP address18:22
vladimir3pyeah :-)18:22
jdg_:)18:22
vladimir3pok, do we have anything else for today?18:23
renukaright, i didn't really have anything more for the meeting18:23
vladimir3punless you could tell me where I could find normal & stable keystone for Natty18:24
jdg_Nothing here really, just trying to actually stand up instances and connect to iscsi storage.18:24
vladimir3p(preferably in form of packages)18:24
jdg_I'll be finishing my blue-print and submitting properly next week.18:24
jdg_I've been using Kiall's script (which uses packages)18:24
renukavladimir3p: I haven't installed from packages before... have you looked at devstack? not sure if they use keystone18:25
renukaaah ok18:25
jdg_Trouble is I'm trying to do physical machines (multi-node)18:25
jdg_Kialls script gives keystone, glance, dashboard etc.18:25
jdg_Now I'm hosed though because none of the euca2ools stuff is configured.... anyway, that's going to be the rest of my week.18:26
renuka#keystone packages18:26
renukathis, for oniric http://packages.ubuntu.com/oneiric/keystone does not help?18:26
vladimir3pyes, I've seen this one for oneiric, but we are using Natty18:27
vladimir3pnot sure if it will work18:27
vladimir3palso, I was trying to use the latest stable/diablo branch from devstack, but it is behaving weird... the one from 1-2 weeks ago worked perfectly18:27
renukamaybe we should keep this out of the meeting and on the #openstack chat room where more people can help18:27
vladimir3pyeah, let's finish the volume one18:28
renuka#endmeeting18:28
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"18:28
openstackMeeting ended Thu Dec  1 18:28:11 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-01-18.02.html18:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-01-18.02.txt18:28
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-01-18.02.log.html18:28
vladimir3pok, folks, need to go18:28
vladimir3ptty next week.18:28
renukayup, bbye18:28
jdg_Thanks guys, sorry for my confusion there regardign pkg's installs.18:28
jdg_I'll catch on here eventually :)18:29
renukafeel free to use the mailing list ;)18:29
jdg_Good tip18:30
jdg_see ya18:30
*** jdg_ has quit IRC18:30
*** renuka has quit IRC18:30
*** GheRivero_ has joined #openstack-meeting18:42
*** hggdh has quit IRC18:48
*** hggdh has joined #openstack-meeting18:52
*** mattray has joined #openstack-meeting18:59
*** jakedahn has joined #openstack-meeting19:05
*** jakedahn has quit IRC19:05
*** jakedahn has joined #openstack-meeting19:05
*** adjohn has quit IRC19:10
*** nati2 has quit IRC19:24
*** rohitk has quit IRC19:25
*** gyee has quit IRC19:29
*** gyee has joined #openstack-meeting19:31
*** sleepsonthefloo has joined #openstack-meeting19:35
*** gyee has quit IRC19:40
*** gyee has joined #openstack-meeting19:41
*** rnirmal has joined #openstack-meeting19:43
*** rnirmal has quit IRC19:45
*** rnirmal has joined #openstack-meeting19:45
*** reed has quit IRC19:46
*** reed has joined #openstack-meeting19:48
*** mikeyp has joined #openstack-meeting19:56
*** n0ano has joined #openstack-meeting19:57
*** maoy has joined #openstack-meeting19:57
*** beekhof has joined #openstack-meeting19:58
*** rnirmal_ has joined #openstack-meeting19:59
sandywalsho/ anyone here for Orchestration?20:00
n0anojust us lurkers :-)20:00
maoyyes20:00
sandywalshlurkers are good :)20:00
sandywalsh#start-meeting20:01
mikeypmike's here20:01
n0anodo we have an agenda for today?20:01
sandywalsh#startmeeting20:01
openstackMeeting started Thu Dec  1 20:01:08 2011 UTC.  The chair is sandywalsh. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.20:01
sandywalsh#link http://wiki.openstack.org/Meetings/Orchestration20:01
sandywalsh#info Orchestration20:01
maoyI'll put another name up there: Task Management20:01
*** rnirmal has quit IRC20:01
*** rnirmal_ is now known as rnirmal20:01
sandywalshI just threw together that agenda since I've been out for the last couple of weeks20:02
sandywalshmaoy, k, let's tackle yours first ... can you explain a little about Task Management?20:02
sandywalsh#topic Task Management20:02
*** rnirmal has quit IRC20:02
*** openstack changes topic to "Task Management"20:02
maoyah.20:02
maoyi was referring to the new naming effort20:03
sandywalshah, heh ... gotcha20:03
sandywalshok, let's tackle naming20:03
sandywalsh#topic naming20:03
*** openstack changes topic to "naming"20:03
maoyi like transaction management, but it does sound like db lingo20:03
sandywalshSo, orchestration is causing trouble for people20:03
maoyso task might be more general alternative20:04
n0anonot for me, I'm beginning to like orchestration, do we really need to change?20:04
sandywalshI think it's ultimately about distributed state machine management20:04
sandywalshn0ano, I agree, but people think of it in the larger BPM / Workflow sense20:04
sandywalshand we're more tactical than that20:05
n0anoso we just need to make sure others know that it is tactical and not workflow20:05
sandywalshTactical Orchestration?20:05
* beekhof doesnt have a problem with Orchestration20:05
mikeypto add some background, 'Orchestration' is being confused with BPM, and larger cloud management frameworks.20:05
beekhofsandywalsh: sounds like a nuclear option :)20:06
sandywalshheh20:06
n0anoand scheduling is too specific20:06
maoylo20:06
sandywalshnaming issues suck :)20:06
maoyif we don't have a consensus we might just stay where we are..20:06
sandywalshthat's why I like State Management ... little room for interpretation20:06
*** bcwaldon has joined #openstack-meeting20:07
maoyaccording to wikipedia..Orchestration describes the automated arrangement, coordination, and management of complex computer systems, middleware, and services.20:07
beekhofwfm20:07
sandywalshcertainly sticking with orchestration is the easiest20:07
sandywalshI'll add a blurb to the working group description to highlight the distinction20:07
sandywalshvote to stick with orchestration?20:08
* n0ano aye20:08
sandywalsh+120:08
beekhof+120:08
maoylike20:08
mikeyp-1 - too many large implications20:08
mikeyp+1 for state management20:08
sandywalshvotes for state management?20:09
sandywalshvotes for other choices?20:09
sandywalsh#action stick with "orchestration" until we can come up with a better name :)20:09
* n0ano abstain for other choices20:09
sandywalsh#topic tactical scheduler changes20:10
*** openstack changes topic to "tactical scheduler changes"20:10
sandywalsh#link http://wiki.openstack.org/EssexSchedulerImprovements20:10
sandywalshSo, I emailed this out this morning20:10
sandywalshI know it's not directly related to Orchestration per se, but hopefully we can see a pattern here for how we can process events and get them back to the Scheduler20:10
maoyi think it's closely related..20:11
sandywalshI think if we get this mechanism in place, we can start to add the State Machine stuff20:11
sandywalshif you haven't read it, please do and offer feedback20:11
*** jamespage_ has joined #openstack-meeting20:11
maoyfor distributed scheduler, you mean the zone stuff, right?20:11
sandywalshwell, initially we need it for single zone, but multi zone will follow behind shortly20:12
mikeypThe idea of capacity cache as a summary table makes sense.20:12
mikeypwho wold 'own' that table in terms of updates ?20:12
n0anoI like the idea of putting the data in the DB, I'm concerned that using pre-defined columns would limit the extensibility of the scheduler20:13
sandywalshthe scheduler would update for new rows20:13
sandywalshand the compute nodes would update for changes to instance status20:13
sandywalsh(including delete)20:13
maoythe challenge I see for "orchestration" is to maintain that table up2date in the event of node crashes, and errors.20:13
*** jamespage_ has quit IRC20:13
beekhofi only just got up, havent read it yet20:14
sandywalshn0ano, good point ... something we need to consider ... how to extend what's in the table20:14
maoyagree on extensibility. scheduler is probably the most likely customized module in deployment imho..20:14
n0ano+1 on customizable module20:14
mikeypthe table should have an updated timestamp for each row.20:14
sandywalshmaoy, ideally the ComputeNode table will let us now about host failures20:15
mikeypcould then decide when info was stale20:15
n0anotimestamp is standard for all the current rows in the DB, that shouldn't change20:15
sandywalshmikeyp, all Nova tables have those common fields20:15
sandywalshmikeyp, nova.db.sqlalchemy.models.NovaBase20:16
sandywalsh#action give some consideration to extending CapacityCache table20:17
sandywalshOne other thing that came up from our meeting last week was the need to keep Essex stable20:17
sandywalshno radical changes20:17
sandywalshso we may need to do our orchestration stuff along side the current compute.run_instance() code20:18
n0anoI actually created a proof of concept scheduler based on cactus that put metrics in the DB and made decisions based on that, I can send an email to describe it in more deatil20:18
maoyif a compute node can't finish provision a vm, we need to find another node. is this included in the new scheduler?20:18
sandywalshperhaps like we did with /zones/boot initially20:18
sandywalshn0ano, that would be great20:18
sandywalsh#action n0ano to outline his previous scheduler efforts on ML20:18
sandywalshmaoy, not yet, no retries yet ... first it's just getting reliable instance state info20:19
n0anoif the goal is essex stability that would imply minimal changes to the current code, right?20:19
sandywalshas I was saying, we may need to do something like POST /orchestration/boot or something in the meanwhile to not upset nova while we get our state management in place20:19
maoysandywalsh, can you elaborate on what you did with /zones/boot initially?20:19
sandywalshlikely a simple state machine (not petri net) in the short term20:20
n0anoso something like moving to a DB base would have to wait for the F release20:20
sandywalshso, when we started with the scheduler we had a new POST /servers method that worked across zones20:20
sandywalshbut it had a different signature than POST /servers20:20
sandywalshso we created POST /zones/boot to use the alternate approach20:21
sandywalshand later, we integrated the two back into POST /servers20:21
sandywalshand ditched /zone/boot20:21
sandywalshwe may need to do the same thing with state-machine based boot20:21
sandywalshcan't upset the Essex apple cart20:21
maoyabout petrinet. from our previous email, it looks like most things are sequential so state machine is probably good enough..20:22
sandywalshmaoy, agreed ... won't really be an issue until we get into multiple concurrent instance provisioning requests20:22
beekhofagreed. petrinet looked cool but quit epossibly overkill20:22
sandywalshthat's why this event handling stuff is important now20:22
sandywalsh#action stick with a simple state machine for now ... revisit petrinets later when concurrency is required20:23
maoyone more q:20:23
maoyis all the steps in a job executed on the same node (compute?)20:23
maoyi guess some might be on network nodes or storage nodes?20:24
sandywalshmaoy, yes for run_instance() ... resize or migrate may be different (need to verify)20:24
sandywalshand yes, there are things that need to be done on the network/volume nodes20:24
sandywalshbut it's usually still all serial20:24
sandywalsh(sequential)20:24
*** adjohn has joined #openstack-meeting20:24
maoygot it20:24
sandywalshbeekhof, when you get a chance to read that wiki page, I'd be curious to know if the event notification stuff will work ok with pacemaker20:25
maoyin this case, the automatic rollback with predefined undo functions during failure seems to make sense20:25
sandywalshhopefully it should fit well?20:26
beekhofi think it would20:26
sandywalshcool20:26
sandywalshmaoy, do you mean hard-coded rewind functions?20:26
beekhofwould simplify a lot if there was a single table to go to20:26
sandywalshright20:26
maoyi mean for each step, the developer specify a undo step in case things happen later blow up20:27
sandywalshyes, right ... I think so too20:27
sandywalshk, so anything else anyone cares to bring up?20:27
sandywalshI need to review some of the communications from the last two weeks20:28
maoythis would prevent bugs like forget to un-allocate IP if VM doesn't boot20:28
sandywalshcorrect20:28
mikeypthe VM state managements are still in review20:28
beekhofthere was my compute-cluster idea, dunno if its worth discussing that20:28
mikeyphow / does that impact this work ?20:28
sandywalshmikeyp, I think they need to come to agreement on the VM states before we can really do much20:29
mikeypthats what I thought20:29
sandywalshbeekhof, I need to re-read it, but perhaps others are ready?20:30
beekhofwe can do next week20:30
sandywalsh#action discuss beekhok compute-cluster idea next meeting20:30
beekhofi've put it to one side since RH is going to take a diff approach anyway20:30
beekhofbut i still think its kinda neat :)20:31
sandywalsh*beekhof20:31
sandywalsh:) can you elaborate on the RH approach?20:31
beekhofnow or next week?20:32
sandywalshperhaps in an email and we can touch on it next week?20:32
sandywalsh(or did your last email already mention it?)20:32
beekhofsure20:32
maoyagreed. email has higher goodput20:32
beekhof10000-ft view...20:32
sandywalshk20:32
beekhofits a layered design20:33
beekhofsits on top of openstack instead of being a part of it20:33
sandywalshah, that'll be good to hear about20:33
sandywalshwell, let's wrap this one up and we'll see you on the lists!20:33
beekhofthat way it can also manage other stacks20:33
beekhofok20:33
sandywalshcool20:33
sandywalsh#endmeeting20:33
mikeypok20:33
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"20:34
openstackMeeting ended Thu Dec  1 20:33:58 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-01-20.01.html20:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-01-20.01.txt20:34
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-01-20.01.log.html20:34
*** n0ano has left #openstack-meeting20:36
*** mikeyp has left #openstack-meeting20:37
*** medberry is now known as mka20:37
*** mka is now known as medberry20:39
*** maoy has left #openstack-meeting20:40
*** gyee has joined #openstack-meeting20:43
*** nati2 has joined #openstack-meeting20:52
*** jakedahn has quit IRC20:53
*** hggdh has quit IRC21:01
*** lloydde has quit IRC21:06
*** rnirmal has joined #openstack-meeting21:10
*** hggdh has joined #openstack-meeting21:13
*** jakedahn has joined #openstack-meeting21:19
*** bencherian has quit IRC21:28
*** bencherian has joined #openstack-meeting21:30
*** bengrue has joined #openstack-meeting21:44
*** bencherian has quit IRC21:48
*** bencherian has joined #openstack-meeting21:53
*** nati2 has quit IRC21:59
*** nati2 has joined #openstack-meeting22:00
*** jaypipes has quit IRC22:04
*** dolphm has joined #openstack-meeting22:09
*** bcwaldon has quit IRC22:33
*** cmagina has quit IRC22:36
*** cmagina has joined #openstack-meeting22:39
*** blakeyeager has joined #openstack-meeting22:39
*** GheRivero_ has quit IRC22:42
*** rnirmal has quit IRC22:46
*** adjohn has quit IRC22:46
*** hggdh has quit IRC22:53
*** hggdh has joined #openstack-meeting22:56
*** mattray has quit IRC22:59
*** dolphm has quit IRC23:03
*** hggdh has quit IRC23:20
*** hggdh has joined #openstack-meeting23:21
yehudasavishy: did you see our changes to the https://blueprints.launchpad.net/nova/+spec/ceph-s3-gateway blueprint, it was pretty much rewritten last week23:22
yehudasa?23:22
*** cdub has joined #openstack-meeting23:23
*** bengrue has quit IRC23:30
*** bengrue has joined #openstack-meeting23:34
*** gyee has quit IRC23:34

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