| *** banix has quit IRC | 00:00 | |
| *** dboik_ has quit IRC | 00:04 | |
| *** ChuckC_ has quit IRC | 00:18 | |
| *** SridharRamaswamy has quit IRC | 00:19 | |
| *** ChuckC_ has joined #openstack-meeting-4 | 00:25 | |
| *** SridharRamaswamy has joined #openstack-meeting-4 | 00:40 | |
| *** yamahata has joined #openstack-meeting-4 | 01:01 | |
| *** banix has joined #openstack-meeting-4 | 02:18 | |
| *** SridharRamaswamy has quit IRC | 02:39 | |
| *** banix has quit IRC | 02:54 | |
| *** sbalukoff has quit IRC | 02:57 | |
| *** banix has joined #openstack-meeting-4 | 03:06 | |
| *** shwetaap has joined #openstack-meeting-4 | 03:21 | |
| *** ivar-lazzaro has quit IRC | 03:53 | |
| *** bobmel has quit IRC | 04:22 | |
| *** banix has quit IRC | 04:34 | |
| *** SumitNaiksatam has quit IRC | 06:38 | |
| *** SumitNaiksatam has joined #openstack-meeting-4 | 06:39 | |
| *** [1]neatherweb has joined #openstack-meeting-4 | 07:09 | |
| *** neatherweb has quit IRC | 07:11 | |
| *** [1]neatherweb is now known as neatherweb | 07:11 | |
| *** kobis has joined #openstack-meeting-4 | 07:21 | |
| *** kobis1 has joined #openstack-meeting-4 | 07:39 | |
| *** kobis has quit IRC | 07:41 | |
| *** evgenyf has joined #openstack-meeting-4 | 07:43 | |
| *** SumitNaiksatam has quit IRC | 07:46 | |
| *** kobis1 has quit IRC | 07:46 | |
| *** kobis has joined #openstack-meeting-4 | 07:47 | |
| *** SumitNaiksatam has joined #openstack-meeting-4 | 07:49 | |
| *** kobis has quit IRC | 08:11 | |
| *** yamahata has quit IRC | 08:18 | |
| *** SumitNaiksatam has quit IRC | 08:51 | |
| *** SumitNaiksatam has joined #openstack-meeting-4 | 08:52 | |
| *** SumitNaiksatam has quit IRC | 08:56 | |
| *** SumitNaiksatam has joined #openstack-meeting-4 | 09:00 | |
| *** kobis has joined #openstack-meeting-4 | 09:12 | |
| *** yamahata has joined #openstack-meeting-4 | 09:45 | |
| *** evgenyf has quit IRC | 10:28 | |
| *** yamahata has quit IRC | 10:43 | |
| *** yamahata has joined #openstack-meeting-4 | 10:45 | |
| *** shwetaap has quit IRC | 11:05 | |
| *** evgenyf has joined #openstack-meeting-4 | 11:06 | |
| *** shwetaap has joined #openstack-meeting-4 | 11:09 | |
| *** shwetaap has quit IRC | 11:11 | |
| *** pkoniszewski has joined #openstack-meeting-4 | 12:08 | |
| *** banix has joined #openstack-meeting-4 | 13:01 | |
| *** banix has quit IRC | 13:04 | |
| *** mestery has quit IRC | 13:36 | |
| *** shwetaap has joined #openstack-meeting-4 | 13:50 | |
| *** shwetaap has quit IRC | 13:50 | |
| *** shwetaap has joined #openstack-meeting-4 | 13:50 | |
| *** yamahata has quit IRC | 13:50 | |
| *** kobis has left #openstack-meeting-4 | 13:51 | |
| *** yamahata has joined #openstack-meeting-4 | 13:51 | |
| *** mestery has joined #openstack-meeting-4 | 14:05 | |
| *** pkoniszewski has quit IRC | 14:08 | |
| *** shwetaap1 has joined #openstack-meeting-4 | 14:09 | |
| *** shwetaap has quit IRC | 14:13 | |
| *** mestery has quit IRC | 14:48 | |
| *** dboik has joined #openstack-meeting-4 | 14:52 | |
| *** mestery has joined #openstack-meeting-4 | 15:16 | |
| *** mgeldert has joined #openstack-meeting-4 | 15:47 | |
| *** mgeldert has quit IRC | 16:27 | |
| *** s3wong has joined #openstack-meeting-4 | 16:57 | |
| *** bobmel has joined #openstack-meeting-4 | 17:01 | |
| *** vishwana_ has joined #openstack-meeting-4 | 17:01 | |
| yamahata | hello | 17:01 |
|---|---|---|
| s3wong | hello | 17:01 |
| bobmel | Hi | 17:01 |
| *** SridharRamaswamy has joined #openstack-meeting-4 | 17:01 | |
| *** vishwana_ is now known as vishwanathj_ | 17:01 | |
| *** SridarK has joined #openstack-meeting-4 | 17:02 | |
| *** vishwanathj_ has quit IRC | 17:02 | |
| SridarK | Hi | 17:02 |
| *** vishwana_ has joined #openstack-meeting-4 | 17:02 | |
| *** vishwana_ is now known as vishwanathj_ | 17:02 | |
| SridharRamaswamy | hi all! | 17:02 |
| vishwanathj_ | hi | 17:02 |
| yamahata | hi all | 17:03 |
| yamahata | #startmeeting servicevm-device-manager | 17:03 |
| openstack | Meeting started Wed Nov 26 17:03:10 2014 UTC and is due to finish in 60 minutes. The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:03 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:03 |
| *** openstack changes topic to " (Meeting topic: servicevm-device-manager)" | 17:03 | |
| openstack | The meeting name has been set to 'servicevm_device_manager' | 17:03 |
| *** hareeshp has joined #openstack-meeting-4 | 17:03 | |
| yamahata | #chair s3wong bobmel | 17:03 |
| openstack | Current chairs: bobmel s3wong yamahata | 17:03 |
| yamahata | #link https://wiki.openstack.org/wiki/Meetings/ServiceVM agenda | 17:03 |
| yamahata | #topic Announcement | 17:04 |
| *** openstack changes topic to "Announcement (Meeting topic: servicevm-device-manager)" | 17:04 | |
| yamahata | #info neutron subteam charter page is created | 17:04 |
| yamahata | #link https://wiki.openstack.org/wiki/NeutronSubteamCharters | 17:04 |
| *** evgenyf has quit IRC | 17:05 | |
| yamahata | Should we list our team there? | 17:05 |
| *** ChuckC_ has quit IRC | 17:05 | |
| s3wong | yamahata: are we Neutron subteam? | 17:05 |
| SridharRamaswamy | yamahata: i was pondering the same! | 17:06 |
| yamahata | s3wong: No officially, I think. | 17:06 |
| yamahata | So I hesitate to do. | 17:06 |
| s3wong | yamahata: we are a stackforge project, so technically not part of Neutron... | 17:06 |
| bobmel | Maybe more important to be visible in adv.services | 17:07 |
| bobmel | Like, ensure we report on progress, updates etc | 17:07 |
| s3wong | (actually we aren't even a Neutron service plugin) | 17:07 |
| yamahata | bobmel: makes sense. | 17:07 |
| SridharRamaswamy | but it will be good to operate just like an official subteam ... with proper charter, deliverable for kil, exit criteria | 17:08 |
| SridharRamaswamy | s/kil/kilo/ | 17:08 |
| s3wong | bobmel: speaking of that --- from mestery 's latest comment, he now suggests that there will be multiple repos for advanced services (basically one per service type) | 17:08 |
| yamahata | SridharRamaswamy: So as sub-sub team of adv. service team? | 17:09 |
| SridharRamaswamy | yamahata: perhaps yeah | 17:09 |
| s3wong | yamahata: if advanced service becomes ONE team with one repo, I suppose tacker should eventually be part of this new advanced service project | 17:09 |
| bobmel | s3wong: Yes I saw that. | 17:09 |
| s3wong | yamahata: but the current thinking is that advanced services would be split into multiple repo | 17:10 |
| hareeshp | wondering if repos for each service is a good idea | 17:10 |
| SridarK | sorry just lurking - but at some point was it not said that service vm's could be of interest outside of neutron too ? | 17:10 |
| s3wong | hareeshp: I don't think it is, honestly (certainly not for VPNaaS :-) ) | 17:11 |
| s3wong | SridarK: we can go either direction, I suppose. But given the background of the team members here, it may make sense to put initial focus on only network services | 17:12 |
| s3wong | (but that is just my opinion, the team will decide in the long run :-) ) | 17:12 |
| yamahata | By looking at the charter page, it tracks spec/patch reviews. So it would make sense to put our neutron spec/patches | 17:12 |
| SridarK | s3wong: makes sense - and i also agree that most interest and need is on network services - just wanted throw that out there so there is no confusion later on | 17:13 |
| SridharRamaswamy | SridarK: i though that was reason used to throw tacker out of neutron ;-) | 17:13 |
| SridarK | SridharRamaswamy: yes that was the thought | 17:14 |
| s3wong | SridharRamaswamy: certainly a reason from the PTL's POV, but how the project moves forward is up to the team | 17:14 |
| SridharRamaswamy | on this subject .. does anyone know a non-networking, non-neutron use-case for tacker ? | 17:15 |
| *** pgpus has joined #openstack-meeting-4 | 17:15 | |
| *** pgpus is now known as pgpuany | 17:16 | |
| SridharRamaswamy | i keep hearing some hypothetical storage-service-vm.. | 17:16 |
| yamahata | I know none so far... | 17:16 |
| s3wong | SridharRamaswamy: kind of difficult to think that far given that the network services related use cases for tacker hasn't been ironed out yet :-) | 17:16 |
| SridharRamaswamy | if there is real need .. then we could include in the use-case | 17:17 |
| SridharRamaswamy | s3wong: okay, i guess it make sense to "live" under adv.services umbrella for the initial few iterations... | 17:17 |
| bobmel | SridharRamaswamy: +1 | 17:17 |
| SridarK | SridharRamaswamy: +1 | 17:18 |
| pgpuany | hi all Are we on workflow disucssions? | 17:18 |
| s3wong | yamahata: yes, let's move on :-) | 17:18 |
| bobmel | Do I dare raise the question about wsgi framework to use sometime during this irc? | 17:18 |
| yamahata | #agreed tacker "live" under adv. service for a while | 17:19 |
| * hareeshp wondering what is upto :) | 17:19 | |
| *** tholtzen has joined #openstack-meeting-4 | 17:19 | |
| yamahata | let's discuss it after action items | 17:19 |
| * hareeshp wondering what bobme is upto ;) | 17:19 | |
| yamahata | #topic Action Items from the last week | 17:19 |
| pgpuany | ok | 17:19 |
| *** openstack changes topic to "Action Items from the last week (Meeting topic: servicevm-device-manager)" | 17:19 | |
| bobmel | yamahata: yes.ok | 17:19 |
| *** vishwanathj_ has left #openstack-meeting-4 | 17:20 | |
| yamahata | The left action item is to determine webex meeting. | 17:20 |
| * s3wong would be interested to find out what bobmel has in store for wsgi framework discussion | 17:20 | |
| yamahata | The poll page is already created, so we can determine later. | 17:20 |
| yamahata | anything else? | 17:20 |
| yamahata | move on... | 17:21 |
| yamahata | #topic spec/code review | 17:21 |
| *** openstack changes topic to "spec/code review (Meeting topic: servicevm-device-manager)" | 17:21 | |
| yamahata | bobmel: please go ahead | 17:21 |
| bobmel | yamahata: you mean regarding wsgi to use? | 17:21 |
| yamahata | bobmel: yes. | 17:21 |
| yamahata | #link https://docs.google.com/document/d/1xs8TvEVMszzND5uoWTHtd1tJnu7105Ekgq9hxiyXABQ/edit?pli=1 | 17:22 |
| bobmel | Just a thought that came to me as in ways we're starting up tacker | 17:22 |
| s3wong | yamahata: that doesn't match the topic? :-) | 17:22 |
| yamahata | #undo | 17:22 |
| openstack | Removing item from minutes: <ircmeeting.items.Link object at 0x1e041d0> | 17:22 |
| yamahata | #topic api/workflow review | 17:23 |
| *** openstack changes topic to "api/workflow review (Meeting topic: servicevm-device-manager)" | 17:23 | |
| bobmel | and we started off from Neutron's code base (for natural reasons) but now Neutron is heading towards Pecan | 17:23 |
| bobmel | and seemingly other OS services too | 17:23 |
| bobmel | So, should we start with what we have? | 17:23 |
| bobmel | And later evaluate to adopt something like Pecan? | 17:24 |
| yamahata | bobmel: I agree we should decide the direction ASAP | 17:24 |
| yamahata | because the early development stage is a good chance to change it. | 17:25 |
| s3wong | bobmel: we have little to no dependency on any module, so it should be OK to switch from the get-go | 17:25 |
| yamahata | changing it later would require big effort. | 17:25 |
| bobmel | yamahata: That was my thinking too. If we are to change, then perhaps it is best to do it like now | 17:25 |
| pgpuany | Good idea to switch to light weight web framework Pecan now at early stage | 17:26 |
| SridharRamaswamy | bobmel: i wish api server infra goes to oslo so all the service can reuse it... | 17:26 |
| pgpuany | k1 timeframe we can catchup using Pecan | 17:26 |
| yamahata | What about other projects? nova? | 17:27 |
| bobmel | Do we have people in this team who are up to speed on Pecan? I'm a novice myself. | 17:27 |
| bobmel | yamahata: Ceilometer uses it | 17:28 |
| pgpuany | may be we can start with base application tempalte | 17:28 |
| pgpuany | https://pecan.readthedocs.org/en/latest/quick_start.html#base-application-template | 17:28 |
| yamahata | bobmel: so pecan sounds promising. | 17:28 |
| SridharRamaswamy | bobmel: just a thought.. can't we use adv.services or neutron endpoint for now for tacker | 17:29 |
| yamahata | okay I'll check pecan. | 17:29 |
| pgpuany | sure as dealing with less scss on hrizon /django can be avoided | 17:30 |
| bobmel | SridharRamaswamy: Technically I think tacker could be another service plugin | 17:30 |
| SridharRamaswamy | I'm worried we will be spinning pecan(!) in tacker before addressing actual use-cases tacker is going after | 17:30 |
| SridharRamaswamy | can't we let adv.services / neutron solve the switch over to pecan.. we can just leverage (copy!) the work | 17:31 |
| bobmel | SridharRamaswamy: That is a valid point | 17:31 |
| pgpuany | Afterall its just API & JSON rest is still retained even if we use Pecan | 17:31 |
| yamahata | Sure that's option. | 17:31 |
| bobmel | pgpuany: So you're saying the we can propbably reuse much of what is in Tacker repo? | 17:32 |
| pgpuany | I think chekout Pecan one of of them and rest continue on tracker | 17:33 |
| bobmel | pgpuany: I mean for DB stuff etc | 17:33 |
| pgpuany | yes looks like that to me | 17:33 |
| pgpuany | yes | 17:33 |
| SridharRamaswamy | i would suggest we wait for out mothership to do the switch over and then we follow .. deliberately delay to leverage.. | 17:34 |
| pgpuany | Although it is lightweight, Pecan does offer an extensive feature set for building HTTP-based applications, including: | 17:34 |
| pgpuany | Object-dispatch for easy routing | 17:34 |
| pgpuany | Full support for REST-style controllers | 17:34 |
| pgpuany | Extensible security framework | 17:34 |
| pgpuany | Extensible template language support | 17:34 |
| pgpuany | Extensible JSON support | 17:34 |
| pgpuany | Easy Python-based configuration | 17:34 |
| pgpuany | OK lets get one to play and report next week before taking decision | 17:35 |
| yamahata | pgpuany: volunteer? | 17:35 |
| pgpuany | OK I will review pecan and report back (I am pgpus) and pramchan@yahoo.com , will report next week on pecan | 17:36 |
| yamahata | pgpuany: cool | 17:36 |
| yamahata | #action pgpuany review pecan and report back | 17:36 |
| pgpuany | nop | 17:36 |
| bobmel | pgpuany: I think key is to figure out how much of existing code can be reused | 17:36 |
| pgpuany | OK I am new where is the ServiceVM code to review | 17:37 |
| bobmel | pgpuany: so adoption of pecan won't delay things too much | 17:37 |
| yamahata | pgpuany: the code is just strip down version of neutron. | 17:38 |
| pgpuany | after gerrit review of Service VM code and pecna will come with suggessions next wek | 17:38 |
| yamahata | okay seems settled down. | 17:38 |
| pgpuany | OK that's cool I have reviewed newutron plugin so when did we start Juno or havana? | 17:39 |
| pgpuany | 2014.1 or 2014.2 | 17:39 |
| yamahata | juno | 17:40 |
| yamahata | the fork point is not clean. | 17:40 |
| yamahata | I used the HEAD at the point. | 17:41 |
| pgpuany | OK so its in opesntack Juno main and not stackforge | 17:41 |
| pgpuany | Thats fine all we need is to see code to see if Pecan has a plavce for us to use | 17:42 |
| pgpuany | done - will reort next week, please proceeed with other items | 17:42 |
| yamahata | bobmel: I think you have other dicussion points according to google-doc. | 17:42 |
| bobmel | I need to open the doc... | 17:43 |
| pgpuany | Anyway this needs code rveiew so will help https://blueprints.launchpad.net/neutron/+spec/adv-services-in-vms | 17:44 |
| yamahata | physical topology and agent notification | 17:44 |
| *** sbalukoff has joined #openstack-meeting-4 | 17:45 | |
| pgpuany | Physical topology you mean like mininet node mode? | 17:45 |
| pgpuany | model | 17:45 |
| SridharRamaswamy | bobmel: those were good discussion points on physical topology.. are more things written somewhere on this topic .. | 17:45 |
| bobmel | SridharRamaswamy: No not really. | 17:46 |
| SridharRamaswamy | bobmel: they go into the realm of scheduling.. | 17:46 |
| yamahata | pgpuany: something like that. | 17:46 |
| bobmel | Do you folks think it belongs in Tacker? | 17:46 |
| yamahata | I think tacker is consumer of the info. | 17:47 |
| yamahata | I don't expect physical topology will be available in near term in any form | 17:48 |
| bobmel | yamahata: and to follow on that, it should then be like in Neutorn? | 17:48 |
| yamahata | So we can safely defer it. | 17:48 |
| SridharRamaswamy | yamahata: yes, lets differ it | 17:48 |
| pgpuany | Thats like snapshot as I see | 17:48 |
| bobmel | So we can place it last in the item list if we keep it. | 17:49 |
| pgpuany | ok | 17:49 |
| yamahata | bobmel: +1 | 17:49 |
| yamahata | #agreed defer physical topology and place it last in the item list if we keep it | 17:50 |
| bobmel | Have everybody gone thorugh the spec doc? | 17:50 |
| pgpuany | As long as a service is single node the physical topolgy attribs are limited but once multinode crreps in the snapshop will be complicated and agreed avoid in 1st cut | 17:50 |
| SridharRamaswamy | bobmel: i went thru' once ! | 17:51 |
| hareeshp | need to do it | 17:51 |
| SridharRamaswamy | it needs some "restructuring" IMO .. particularly the NFV / VNF texts | 17:52 |
| yamahata | sure I did :-). I'm biased, so it would be desirable for someone else to revise/re-edit it... | 17:52 |
| SridharRamaswamy | i can give it shot | 17:52 |
| pgpuany | I have just reviewed and would like to add comments for detailing APIs and VNFM lifecyle management or atleast review in next 2-3 days | 17:53 |
| s3wong | bobmel, yamahata: we would like to have more comments on the doc before having the webex session | 17:53 |
| pgpuany | sure sounds good | 17:53 |
| yamahata | s3wong: +1 for more comments/discussion before webex session | 17:53 |
| SridharRamaswamy | yamahata: i think VNF / NFV relations are quite relevant.. | 17:53 |
| SridharRamaswamy | yamahata: just suggesting to re-organize for clarity | 17:54 |
| yamahata | 5 min left. | 17:54 |
| pgpuany | VNFs have more than CRUD APIs as they deal with topology placnment etc. | 17:54 |
| pgpuany | Add review comments thic week +1 | 17:55 |
| yamahata | #action everyone review google-doc | 17:55 |
| pgpuany | you mean https://docs.google.com/document/d/1xs8TvEVMszzND5uoWTHtd1tJnu7105Ekgq9hxiyXABQ/edit?pli=1# | 17:55 |
| yamahata | pgpuany: yes | 17:55 |
| s3wong | Yes --- all these suggestions/discussions should be brought over to the Google doc | 17:56 |
| pgpuany | ok done we have long week end here to address this safely | 17:56 |
| yamahata | Let's open discussion before closing... | 17:56 |
| s3wong | I do expect a lot of comments (or additional suggestions inside the spec for those who can edit) over the next week or so (hopefully) | 17:56 |
| yamahata | #topic Open Discussion | 17:56 |
| *** openstack changes topic to "Open Discussion (Meeting topic: servicevm-device-manager)" | 17:57 | |
| pgpuany | Hope all you will Pardon the Turkey!!! not sure if this happens all over ... enjoy | 17:57 |
| bobmel | yamahata: timeline | 17:57 |
| bobmel | for Kilo | 17:57 |
| bobmel | for Tacker | 17:57 |
| yamahata | sorry for interrupting | 17:57 |
| pgpuany | spell ou | 17:57 |
| pgpuany | k1, k2? | 17:57 |
| pgpuany | k1=dec 18 | 17:57 |
| SridharRamaswamy | doodle for the timeslot for the webex shows early next week.. | 17:58 |
| pgpuany | ok | 17:58 |
| SridharRamaswamy | would we be ready early next week for the webex call ? | 17:58 |
| bobmel | Can we outline one on the tacker wiki, what we should aim for in terms of deliverables | 17:58 |
| yamahata | bobmel: What do you mean? do we want to set mile stone? | 17:58 |
| s3wong | SridharRamaswamy: then I suppose we should have our comments on the doc by early next week :-) | 17:58 |
| SridharRamaswamy | s3wong: yeah, then push webex to the week after ? | 17:58 |
| SridharRamaswamy | s3wong: alteast later in the week | 17:59 |
| yamahata | SridharRamaswamy: okay I will expand the range of doodle poll . | 17:59 |
| s3wong | SridharRamaswamy: probably make sense for the team to read the comments/additions before having a webex | 17:59 |
| yamahata | #action yamahata expand range of poll | 17:59 |
| pgpuany | OK do I have permission to update googledoc, or I need to be permitted by some one from your side? | 17:59 |
| s3wong | pgpuany: anyone can comment | 18:00 |
| pgpuany | thanks | 18:00 |
| yamahata | Time is coming. | 18:00 |
| s3wong | pgpuany: but if you feel you want to add content in there, you can ping yamahata to add you as an editor | 18:00 |
| yamahata | Given the recent meeting time, it will make sense to have 1hour slot instead of 30min. | 18:01 |
| s3wong | and for those that can edit, please put your IRC handle (for example [s3wong]:) on pieces that you edit | 18:01 |
| pgpuany | Is Service VM = Appliance? | 18:01 |
| s3wong | yamahata: +1 | 18:01 |
| bobmel | yamahata: +1 | 18:01 |
| SridharRamaswamy | yamahata: +1 | 18:01 |
| yamahata | #action yamahata increase timeslot from 30min to 1hour | 18:01 |
| s3wong | pgpuany: service "container", can be VM, software containers, or appliances | 18:01 |
| pgpuany | you mean incuding Docker | 18:02 |
| bobmel | yamahata: At some point not to distant future we probablyu need to have a reasonable idea what to aim for K1, k2 and k3 | 18:02 |
| s3wong | pgpuany: exactly | 18:02 |
| pgpuany | I see so any container, does API address that with container type or soemthing? | 18:02 |
| yamahata | bobmel: +1 | 18:02 |
| SridharRamaswamy | bobmel: +1, hopefully in line with what we agreed in the summit | 18:02 |
| bobmel | yamahata: We can revisit that question next time. | 18:03 |
| pgpuany | Container Type=VM, Docker,... | 18:03 |
| pgpuany | OK we will thanks | 18:03 |
| bobmel | SridharRamaswamy: Yes. Did we put that somewhere on the wiki? | 18:03 |
| SridharRamaswamy | bobmel: yep, use-case table has specific release target | 18:03 |
| s3wong | bobmel: didn't some of us take pictures of the whiteboard? :-) | 18:03 |
| SridharRamaswamy | s3wong: all that info is captured in the use-case table.. | 18:04 |
| yamahata | The items are all in etherpad. | 18:04 |
| s3wong | cool | 18:04 |
| pgpuany | link to etherpad? | 18:04 |
| bobmel | SridharRamaswamy: Oh yes, how could I miss that... :-) | 18:04 |
| SridharRamaswamy | etherpad correct.... it is distilled into the use-case release target | 18:04 |
| SridharRamaswamy | :) | 18:05 |
| SridharRamaswamy | perhaps that picture is worth preserving ;-) | 18:05 |
| SridharRamaswamy | pgpuany: #link https://etherpad.openstack.org/p/servicevm | 18:05 |
| pgpuany | thanks | 18:06 |
| yamahata | #endmeeting | 18:06 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 18:06 | |
| openstack | Meeting ended Wed Nov 26 18:06:57 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:07 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-11-26-17.03.html | 18:07 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-11-26-17.03.txt | 18:07 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2014/servicevm_device_manager.2014-11-26-17.03.log.html | 18:07 |
| yamahata | sorry for closing meeting during dicussion | 18:07 |
| yamahata | we can continue at #tacker channel | 18:07 |
| s3wong | thanks, guys | 18:07 |
| yamahata | thanks | 18:07 |
| *** tholtzen has quit IRC | 18:07 | |
| s3wong | yamahata: to be fair, this is #openstack-meeting-4, no one is forcing you out :-) | 18:07 |
| yamahata | s3wong: Oops. | 18:08 |
| SridharRamaswamy | bye folks, talk to u all next week | 18:08 |
| pgpuany | thanks | 18:09 |
| *** igordcard has joined #openstack-meeting-4 | 18:11 | |
| *** igordcard has quit IRC | 18:12 | |
| *** igordcard has joined #openstack-meeting-4 | 18:12 | |
| *** pgpuany has quit IRC | 18:24 | |
| *** SridharRamaswamy has quit IRC | 18:29 | |
| *** vishwana_ has joined #openstack-meeting-4 | 18:33 | |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 18:43 | |
| *** SridharRamaswamy has joined #openstack-meeting-4 | 18:56 | |
| *** yamahata has quit IRC | 18:59 | |
| *** banix has joined #openstack-meeting-4 | 19:16 | |
| *** SridharRamaswamy has quit IRC | 19:20 | |
| *** dboik has quit IRC | 19:25 | |
| *** banix has quit IRC | 19:28 | |
| *** vishwana_ has quit IRC | 19:32 | |
| *** banix has joined #openstack-meeting-4 | 19:36 | |
| *** dboik has joined #openstack-meeting-4 | 19:40 | |
| *** shwetaap1 has quit IRC | 19:43 | |
| *** SridharRamaswamy has joined #openstack-meeting-4 | 20:04 | |
| *** david-lyle has joined #openstack-meeting-4 | 20:40 | |
| *** SridharRamaswamy has quit IRC | 21:01 | |
| *** SridharRamaswamy has joined #openstack-meeting-4 | 21:02 | |
| *** mgeldert has joined #openstack-meeting-4 | 21:47 | |
| *** banix has quit IRC | 21:49 | |
| *** hareeshp has quit IRC | 21:50 | |
| *** SridharRamaswam1 has joined #openstack-meeting-4 | 22:00 | |
| *** SridharRamaswamy has quit IRC | 22:01 | |
| *** banix has joined #openstack-meeting-4 | 22:10 | |
| *** banix has quit IRC | 22:12 | |
| *** banix has joined #openstack-meeting-4 | 22:22 | |
| *** banix has quit IRC | 22:25 | |
| *** banix has joined #openstack-meeting-4 | 22:42 | |
| *** banix has quit IRC | 22:49 | |
| *** SridharRamaswamy has joined #openstack-meeting-4 | 22:49 | |
| *** SridharRamaswam1 has quit IRC | 22:49 | |
| *** hareeshp has joined #openstack-meeting-4 | 22:56 | |
| *** banix has joined #openstack-meeting-4 | 22:58 | |
| *** hareeshp has quit IRC | 23:01 | |
| *** igordcard has quit IRC | 23:04 | |
| *** SumitNaiksatam has quit IRC | 23:10 | |
| *** SumitNaiksatam has joined #openstack-meeting-4 | 23:10 | |
| *** SridharRamaswamy has quit IRC | 23:14 | |
| *** dboik has quit IRC | 23:24 | |
| *** SridharRamaswamy has joined #openstack-meeting-4 | 23:29 | |
| *** banix has quit IRC | 23:42 | |
| *** SumitNaiksatam has quit IRC | 23:42 | |
| *** banix has joined #openstack-meeting-4 | 23:42 | |
| *** mgeldert has left #openstack-meeting-4 | 23:42 | |
| *** SumitNaiksatam has joined #openstack-meeting-4 | 23:49 | |
| *** banix has quit IRC | 23:56 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!