Thursday, 2014-01-16

*** amrith has joined #openstack-meeting-alt00:10
*** sarob has quit IRC00:13
*** michael-yu has quit IRC00:18
*** esker has quit IRC00:20
*** michael-yu has joined #openstack-meeting-alt00:21
*** xuhanp has quit IRC00:31
*** jecarey has quit IRC00:32
*** mtaylor is now known as mordred00:36
*** mordred has quit IRC00:36
*** mordred has joined #openstack-meeting-alt00:36
*** dripton has quit IRC00:46
*** dripton has joined #openstack-meeting-alt00:49
*** beyounn has quit IRC00:53
*** kebray_ has quit IRC00:54
*** beyounn has joined #openstack-meeting-alt00:56
*** sarob has joined #openstack-meeting-alt00:58
*** nmarchenko has quit IRC01:03
*** ashestakov has quit IRC01:03
*** boris-42 has quit IRC01:05
*** nmarchenko has joined #openstack-meeting-alt01:06
*** jcoufal has quit IRC01:08
*** mattgriffin has quit IRC01:20
*** jjmb has joined #openstack-meeting-alt01:20
*** shau7246 has joined #openstack-meeting-alt01:25
*** michael-yu has quit IRC01:27
*** shau7246 is now known as shaunak01:27
*** beyounn has quit IRC01:32
*** nosnos has joined #openstack-meeting-alt01:33
*** jjmb has quit IRC01:36
*** xuhanp has joined #openstack-meeting-alt01:37
*** jjmb has joined #openstack-meeting-alt01:38
*** gokrokve has quit IRC01:43
*** ijw has quit IRC01:43
*** gokrokve has joined #openstack-meeting-alt01:43
*** michael-yu has joined #openstack-meeting-alt01:45
*** ijw has joined #openstack-meeting-alt01:46
*** gokrokve has quit IRC01:48
*** ijw has quit IRC01:52
*** sarob has quit IRC01:54
*** julim has quit IRC01:54
*** sarob has joined #openstack-meeting-alt01:54
*** IlyaE has quit IRC01:57
*** sarob has quit IRC01:58
*** jjmb has quit IRC02:00
*** jjmb has joined #openstack-meeting-alt02:00
*** ijw has joined #openstack-meeting-alt02:04
*** carlp_ has quit IRC02:06
*** michael-yu has quit IRC02:06
*** jjmb has quit IRC02:07
*** jjmb1 has joined #openstack-meeting-alt02:07
*** ijw has quit IRC02:09
*** rakhmerov has quit IRC02:16
*** banix has joined #openstack-meeting-alt02:16
*** rakhmerov has joined #openstack-meeting-alt02:18
*** rakhmerov has quit IRC02:18
*** balajiiyer has joined #openstack-meeting-alt02:23
*** ijw has joined #openstack-meeting-alt02:25
*** tanisdl has quit IRC02:28
*** bill_az has quit IRC02:30
*** ijw has quit IRC02:30
*** rnirmal has joined #openstack-meeting-alt02:31
*** jjmb1 has quit IRC02:32
*** mattgriffin has joined #openstack-meeting-alt02:33
*** jjmb has joined #openstack-meeting-alt02:33
*** esker has joined #openstack-meeting-alt02:35
*** esker has quit IRC02:41
*** esker has joined #openstack-meeting-alt02:42
*** esker has quit IRC02:46
*** arnaud___ has quit IRC02:48
*** gokrokve has joined #openstack-meeting-alt02:48
*** obondarev_ has joined #openstack-meeting-alt02:48
*** arnaud__ has quit IRC02:48
*** dianefleming has joined #openstack-meeting-alt02:59
*** shaunak has quit IRC02:59
*** bnemec has quit IRC03:01
*** jjmb has quit IRC03:05
*** jjmb has joined #openstack-meeting-alt03:07
*** nati_ueno has joined #openstack-meeting-alt03:13
*** doug_shelley66 has quit IRC03:18
*** rsblendido has joined #openstack-meeting-alt03:24
*** rossella_s has joined #openstack-meeting-alt03:24
*** michael-yu has joined #openstack-meeting-alt03:37
*** wdennis_ has joined #openstack-meeting-alt03:38
*** obondarev_ has quit IRC03:41
*** SlickNik has quit IRC03:41
*** wdennis_ has left #openstack-meeting-alt03:42
*** SlickNik has joined #openstack-meeting-alt03:42
*** rakhmerov has joined #openstack-meeting-alt03:43
*** SlickNik has left #openstack-meeting-alt03:45
*** rsblendido has quit IRC03:48
*** hub_cap has quit IRC03:48
*** rsblendido has joined #openstack-meeting-alt03:49
*** rossella_s has quit IRC03:50
*** michael-yu has quit IRC03:56
*** rsblendido has quit IRC03:58
*** colinmcnamara has joined #openstack-meeting-alt04:08
*** ijw has joined #openstack-meeting-alt04:10
*** rnirmal has quit IRC04:12
*** ijw has quit IRC04:15
*** dguitarbite has joined #openstack-meeting-alt04:17
*** jecarey has joined #openstack-meeting-alt04:27
*** gokrokve has quit IRC04:28
*** IlyaE has joined #openstack-meeting-alt04:29
*** gokrokve has joined #openstack-meeting-alt04:30
*** boris-42 has joined #openstack-meeting-alt04:30
*** IlyaE has quit IRC04:34
*** banix has quit IRC04:36
*** ashaikh has joined #openstack-meeting-alt04:38
*** banix has joined #openstack-meeting-alt04:43
*** markwash has quit IRC04:45
*** shaunak has joined #openstack-meeting-alt04:53
*** shaunak_ has joined #openstack-meeting-alt04:54
*** shaunak has quit IRC04:54
*** coolsvap has joined #openstack-meeting-alt04:55
*** banix has quit IRC04:55
*** shaunak_ has quit IRC04:55
*** colinmcnamara has quit IRC04:58
*** SergeyLukjanov_ is now known as SergeyLukjanov04:59
*** doug_shelley66 has joined #openstack-meeting-alt05:01
*** markwash has joined #openstack-meeting-alt05:01
*** IlyaE has joined #openstack-meeting-alt05:01
*** markwash has quit IRC05:04
*** kebray_ has joined #openstack-meeting-alt05:04
*** IlyaE has quit IRC05:08
*** IlyaE has joined #openstack-meeting-alt05:10
*** michael-yu has joined #openstack-meeting-alt05:24
*** nosnos_ has joined #openstack-meeting-alt05:27
*** nosnos has quit IRC05:28
*** jmcbride has joined #openstack-meeting-alt05:29
*** balajiiyer has quit IRC05:31
*** jmcbride has quit IRC05:34
*** markwash has joined #openstack-meeting-alt05:37
*** esker has joined #openstack-meeting-alt05:38
*** gokrokve has quit IRC05:48
*** kebray_ has quit IRC05:54
*** mattgriffin has quit IRC06:03
*** IlyaE has quit IRC06:08
*** nosnos_ has quit IRC06:10
*** nosnos has joined #openstack-meeting-alt06:10
*** ijw has joined #openstack-meeting-alt06:11
*** shashank_ has joined #openstack-meeting-alt06:11
*** ijw has quit IRC06:15
*** coolsvap_away has joined #openstack-meeting-alt06:15
*** coolsvap has quit IRC06:16
*** coolsvap_away is now known as coolsvap06:20
*** denis_makogon has joined #openstack-meeting-alt06:22
*** SergeyLukjanov is now known as SergeyLukjanov_06:22
*** chandankumar has joined #openstack-meeting-alt06:23
*** chmouel has quit IRC06:24
*** dguitarbite has quit IRC06:25
*** chmouel has joined #openstack-meeting-alt06:27
*** dguitarbite has joined #openstack-meeting-alt06:29
*** mattgriffin has joined #openstack-meeting-alt06:31
*** mattoliverau has quit IRC06:35
*** mattoliverau has joined #openstack-meeting-alt06:36
*** kebray_ has joined #openstack-meeting-alt06:37
*** esker has quit IRC06:39
*** kebray_ has quit IRC06:40
*** sergmelikyan has quit IRC06:49
*** sergmelikyan has joined #openstack-meeting-alt06:49
*** sergmelikyan has quit IRC06:49
*** nadya_ has joined #openstack-meeting-alt06:51
*** dguitarbite has quit IRC06:56
*** dguitarbite has joined #openstack-meeting-alt06:56
*** mattgriffin has quit IRC07:01
*** SushilKM has joined #openstack-meeting-alt07:04
*** yogesh has joined #openstack-meeting-alt07:23
*** dguitarbite has quit IRC07:23
*** gokrokve has joined #openstack-meeting-alt07:24
*** dguitarbite has joined #openstack-meeting-alt07:27
*** ajo has quit IRC07:28
*** gokrokve has quit IRC07:29
*** nadya_ has quit IRC07:30
*** flaper87|afk is now known as flaper8707:35
*** doug_shelley66 has quit IRC07:37
*** doug_shelley66 has joined #openstack-meeting-alt07:38
*** shashank_ has quit IRC07:40
*** amcrn has quit IRC07:41
*** boris-42 has quit IRC07:43
*** denis_makogon has quit IRC07:43
*** gokrokve has joined #openstack-meeting-alt07:54
*** sarob has joined #openstack-meeting-alt07:56
*** harlowja_ is now known as harlowja_away08:02
*** michael-yu has quit IRC08:05
*** sarob has quit IRC08:08
*** jcoufal has joined #openstack-meeting-alt08:08
*** ijw has joined #openstack-meeting-alt08:12
*** markwash has quit IRC08:16
*** ijw has quit IRC08:17
*** pnavarro__ has joined #openstack-meeting-alt08:26
*** michael-yu has joined #openstack-meeting-alt08:29
*** jtomasek has joined #openstack-meeting-alt08:30
*** michael-yu has quit IRC08:33
*** sarob has joined #openstack-meeting-alt08:34
*** luqas has joined #openstack-meeting-alt08:35
*** SushilKM has quit IRC08:39
*** SushilKM has joined #openstack-meeting-alt08:40
*** sarob_ has joined #openstack-meeting-alt08:40
*** sarob has quit IRC08:42
*** ashaikh has quit IRC08:42
*** sarob_ has quit IRC08:45
*** aignatov has joined #openstack-meeting-alt08:47
*** yogesh has quit IRC08:50
*** dguitarbite has quit IRC08:50
*** dguitarbite has joined #openstack-meeting-alt08:55
*** _ruhe is now known as ruhe09:03
*** luqas has quit IRC09:06
*** luqas has joined #openstack-meeting-alt09:07
*** luqas has quit IRC09:08
*** stannie has left #openstack-meeting-alt09:10
*** luqas has joined #openstack-meeting-alt09:11
*** ijw has joined #openstack-meeting-alt09:17
*** vponomaryov has joined #openstack-meeting-alt09:18
*** ijw_ has joined #openstack-meeting-alt09:19
*** ijw has quit IRC09:23
*** ijw_ has quit IRC09:27
*** ijw has joined #openstack-meeting-alt09:28
*** nati_ueno has quit IRC09:33
*** sarob has joined #openstack-meeting-alt09:34
*** derekh has joined #openstack-meeting-alt09:37
*** yamahata has quit IRC09:38
*** jcoufal_ has joined #openstack-meeting-alt09:38
*** sarob has quit IRC09:39
*** jcoufal has quit IRC09:41
*** jcoufal_ is now known as jcoufal09:43
*** ityaptin has joined #openstack-meeting-alt09:44
*** nosnos has quit IRC09:51
*** ruhe is now known as ruhe_away09:59
*** boris-42 has joined #openstack-meeting-alt10:03
*** rakhmerov has quit IRC10:03
*** rakhmerov has joined #openstack-meeting-alt10:04
*** mestery_ has joined #openstack-meeting-alt10:05
*** mestery has quit IRC10:08
*** ruhe_away is now known as _ruhe10:09
*** sarob has joined #openstack-meeting-alt10:13
*** luqas has quit IRC10:15
*** jeblair has quit IRC10:17
*** sarob has quit IRC10:18
*** jeblair has joined #openstack-meeting-alt10:19
*** SergeyLukjanov_ is now known as SergeyLukjanov10:25
*** aignatov has quit IRC10:28
*** sarob has joined #openstack-meeting-alt10:34
*** SergeyLukjanov is now known as SergeyLukjanov_10:35
*** sarob has quit IRC10:39
*** obondarev_ has joined #openstack-meeting-alt10:41
*** luqas has joined #openstack-meeting-alt10:42
*** dmakogon_ is now known as denis_makogon10:44
*** dguitarbite has quit IRC10:48
*** SergeyLukjanov_ is now known as SergeyLukjanov10:51
*** _ruhe is now known as ruhe10:52
*** aignatov has joined #openstack-meeting-alt10:52
*** flaper87 is now known as flaper87|afk10:59
*** yamahata has joined #openstack-meeting-alt10:59
*** xuhanp has quit IRC11:03
*** ikhudoshyn has quit IRC11:11
*** ikhudoshyn has joined #openstack-meeting-alt11:13
*** dguitarbite has joined #openstack-meeting-alt11:13
*** jprovazn has joined #openstack-meeting-alt11:16
*** ozstacker has quit IRC11:19
*** ozstacker has joined #openstack-meeting-alt11:19
*** sarob has joined #openstack-meeting-alt11:34
*** sarob has quit IRC11:39
*** dguitarbite has quit IRC11:55
*** katyafervent_ is now known as katyafervent_awa11:56
*** IYozhikov_away is now known as IgorYozhikov12:03
*** dguitarbite has joined #openstack-meeting-alt12:03
*** jprovazn has quit IRC12:04
*** jprovazn has joined #openstack-meeting-alt12:04
*** jprovazn is now known as jprovazn_12:04
*** sirushti has quit IRC12:05
*** jjmb has quit IRC12:05
*** sirushti has joined #openstack-meeting-alt12:05
*** coolsvap has quit IRC12:08
*** jprovazn_ is now known as jprovazn12:12
*** katyafervent_awa is now known as katyafervent12:19
*** dguitarbite has quit IRC12:19
*** akuznetsov has quit IRC12:29
*** derekh has quit IRC12:29
*** akuznetsov has joined #openstack-meeting-alt12:29
*** sarob has joined #openstack-meeting-alt12:34
*** dguitarbite has joined #openstack-meeting-alt12:38
*** sarob has quit IRC12:39
*** derekh has joined #openstack-meeting-alt12:45
*** heyongli has joined #openstack-meeting-alt12:49
*** ruhe is now known as ruhe_away12:53
*** ruhe_away is now known as ruhe12:54
*** irenab has joined #openstack-meeting-alt12:55
*** ijw has quit IRC12:55
*** obondarev_ has quit IRC12:55
*** ijw has joined #openstack-meeting-alt12:55
*** banix has joined #openstack-meeting-alt12:56
*** sadasu has joined #openstack-meeting-alt12:59
*** BrianB_ has joined #openstack-meeting-alt13:00
*** baoli has joined #openstack-meeting-alt13:01
baoli#startmeeting PCI Passthrough13:01
openstackMeeting started Thu Jan 16 13:01:49 2014 UTC and is due to finish in 60 minutes.  The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: PCI Passthrough)"13:01
openstackThe meeting name has been set to 'pci_passthrough'13:01
heyonglihi13:03
irenabhi13:03
ijwyo13:03
BrianB_hi13:03
ijwHad a long coversation with baoli offline yesterday - I think the summary was that the proposal I put forward is more complicated than a group based proposal but we should do it if we're happy that nothing simpler will do the job and if the network issue is not a problem (for which irenab proposed a solution on the ML).   Are we in agreement?13:04
*** SushilKM has left #openstack-meeting-alt13:05
heyonglione question, for baoli's concern,13:05
ijw(Fwiw the answer is obviously the solution that's no more complicated than it absolutely has to be, as far as I'm concerned.)13:05
heyongliif the group as tag solve baoli's live migiration problem?13:05
*** julienvey_ has joined #openstack-meeting-alt13:06
ijwNo, it doesn't work with his networking method of attaching devices - and in fact it can't work if a device can be in two flavors.13:06
*** flaper87|afk is now known as flaper8713:06
*** banix has quit IRC13:06
heyonglii don't see why13:06
ijwBecause you make the networks in advance, and I'm not sure you could put a PCI device in two networks simultaneously.  Also, you're offloading the choice of the device that's mapped to libvirt if you do it that way.13:07
heyongliif you still can attach device a tag, say, group, why not?13:07
ijwirenab's proposal would work fine, though, as far as I can see (I would like baoli's opinion on that though) because it treats PCI devices individually.13:08
heyonglii don't see irenab's proposal when i leave office, sorry13:08
irenabheyongli: I suggested to rename the device to logical name based on neutron port UUID13:09
ijwIt renames the ethernet device to the same name as is in the libvirt.xml, so you can attach the migrated VM to the 'same' device while still getting to choose which device that is.13:09
baoliIrena, can you put together a complete describe on how it works? My guess is that you would name the interface with the same names on both the target node and the originating node.13:09
ijwThat's how I understood it13:09
irenabbaoli: yes13:09
ijwQuite a cool idea, actually ;)13:10
irenabbaoli: it would remane the device once it should be used as vNIC, not inadvance13:10
baoliIrena, then we need to do a through study on that. Because that involves nova to coordinate that13:10
*** pdmars has joined #openstack-meeting-alt13:11
baoliHave you tried it yourself?13:11
heyongliyeah, i'm not sure i understand the problem and the solution right13:11
irenabbaoli: I think we can take it later for advanced case, since we were OK with no live migration for now :-)13:11
irenabbaoli: yes, tried that13:12
baoliIrena, I'm afraid that we need to do migration. But I agree that we can put it aside for now13:12
ijwThe issue I would see is whether we have the opportunity to do the rename before the migration begins.13:12
irenabbaoli: I can share the details of the trial as a follow-up email13:12
baoliIrena, that sounds great13:12
baoliand Thanks for that13:13
irenabbaoli: no problem13:13
*** yamahata has quit IRC13:13
ijwSo are we all in agreement that we should do it this way?  If we need more in the way of documentation I can add to the spec13:14
*** yamahata has joined #openstack-meeting-alt13:14
irenabijw: I inserted the comments, still didn't check the answers. sorry13:15
baoliijw, let's go over a practical deployment case where only pci flavor can do the job13:15
heyonglii would like to see the live migration problem and possible solution in doc or mail thread.13:15
baoliAnd then let's try to map it to SRIOV13:15
ijwirenab: I did most of them this morning,there's a couple I answered rather than fixing it13:15
ijwheyongli: good point, stick a comment on there so I don't forget13:16
irenabijw: thanks, wil go over, may add  more13:16
baoliSorry that I haven't got a chance to look at your comments13:16
baoliIrena, you want to go over your comments?13:16
ijwThey were largely 'needs more text' so for those I've just done as instructed and resolved the comment.13:16
irenabbaoli: I prefer to go over deployment case as you suggested13:17
ijwThe only one that's a bit awkward is explaining in more detail where the changes would go and which processes they would affect.13:17
ijwI've done what I can but it's hard to structure.13:17
baoliIrena, agreed13:17
irenabijw: I think by covering this we can see if all items has owners and do the coding13:17
ijwYep, I agree13:17
heyongliagree13:18
ijwWe'll come back to this, let's do the example13:18
ijwbaoli: I think the point you had issue with is the changing of a flavor after initially setting them up is what drives most of the complexity in the solution.13:18
baoliijw, please address my request directly13:19
ijwbaoli: that being the case a worked example wants to include that13:19
irenabijw: can we start with case that no change is required, just initial setup13:19
ijwLet's start with irenab's because those are the easy cases.  The ones I would work through are the current case (selection by device/vendor) and the groups case (selection by backend marking).  We'll cover provider networks in a few minutes too because that's got open issues13:20
ijwSo, the current case assumes we set up 'flavors' - except they're not objects in their own right at the moment, they're matching expressions on the nova flavor - by expressing a device/vendor match13:21
ijwIn the proposal, we would use pci_information to do what the whitelist does now, and we wouldn't add any extra_attrs13:22
ijwWhere now we have extra_specs on the nova flavor with a set of matching expressions, we would instead have the administrator create a flavor with that matching expression and a friendly name and then use the flavor name and device count in a flavor.13:22
ijwThe pci attributes set for selection would be device and vendor ID.13:23
baoliijw, an example that is expressed with those things would be better than words, I would suggest13:23
ijwOK, so say all our compute nodes contain 1 GPU with vendor:device 8086:000113:24
irenabijw: is it SR-IOV case?13:24
ijwNo, this one's not going to be yet and we'll come to networking (which is the main SR-IOV driver) in a mo13:24
ijwSo on the compute nodes, pci_information would be { { device_id: "0x8086", vendor_id: "0x0001" }, {} }13:26
ijw(yes that format is awful, make suggestions on the document)13:26
ijwI forget the name of the config item for goruping, but let's say pci_attrs=device_id, vendor_id13:27
ijwSorry, I got the device/vendor the wrong way around, but you see the idea13:27
ijwSo, the compute node would ask the scheduler process for the groups to send and would be told 'device_id,vendor_id' from that config item13:27
ijwThe compute node would get the pci_infomation and run it over the PCI device tree to find matching devices and get a list of those devices13:28
ijwThe compute node would make buckets by device and vendor and file the devices into buckets (which I think it does now, but not on a variable list of attrs)13:28
ijwThe compute node would report pci_stats objects back to the scheduler - one stat: device_id=0x0001, vendor_id=0x8086, free count=113:29
ijwThat would come in from every compute node.13:29
ijwGood so far?13:29
*** yamahata has quit IRC13:29
heyonglipci_attrs=device_id, vendor_id should be golobal, right?13:29
baoliI think that you forgot the compute node provisions and stats report based on what you have described so far13:30
*** xuhanp has joined #openstack-meeting-alt13:30
*** jdob has joined #openstack-meeting-alt13:30
ijwYes - but I'm concerned that if we put it onto both control and compute config then a cocked up configuration would result in a really screwed up system.  The suggestion above that we tell the compute node what it is makes for better consistency.13:30
ijwbaoli: the pci_devices table, you mean?13:30
*** yamahata has joined #openstack-meeting-alt13:31
ijwYes, as things stand it would be pushing out the PCI device list to the conductor, just as it does now - I think that code remains the same as far as this case is concerned13:31
ijwSo at this point we have a live cloud on which we can run things.13:32
ijwThe administrator sets up a 'gpu' flavor with a matching expression { device_id -> 1, vendor_id -> 8086 }13:32
ijwPCI flavor even13:32
ijwThen he sets up a nova flavor saying 'gpu:1' in the extra_specs for PCI device requirements.  At this point end users can run machines with direct mapping.13:33
ijwFinally, the user attempts to start a machine with that flavor13:33
*** yamahata has quit IRC13:33
ijwThe scheduler as it is, PCI filter excluded, attempts to locate a list of machines and filters down the list of compute nodes to a subset of the whole list satisfying other requirements (CPU, RAM etc.)13:33
ijwThen the PCI filter kicks in.  And this is the horrible bit.13:34
ijwWe take the device filter from the PCI flavor required and find all the buckets that satisfy the request13:34
*** yamahata has joined #openstack-meeting-alt13:34
*** sarob has joined #openstack-meeting-alt13:34
ijwFor each machine, we attempt to find a bucket with available devices13:34
baoliijw, can you define the buckets and how they are populated?13:34
ijwbaoli: these 'buckets' are the pci_stats rows fed up from the compute node.13:35
ijwIn the first part of the explanation.13:35
heyonglithe stats pool, now, it calledd13:35
ijwIf we find one, then we can schedule on that machine.  If we can't, the machine is dropped from the available list.13:35
ijwThen, schedule filtering done, we have a preference list of machines (we haven't affected the preference order) and we make our scheduling attempts as usual.13:36
ijwFinally, when we schedule the machine, the nova-compute process is RPCed with the instance object.13:36
ijwThe instance object has the pci_stats row that we plan on using.  That contains the device and vendor attributes.13:36
ijwIn its own memory, it has the equivalent record, it decreases the available count by 113:37
ijwAnd it picks a device to allocate.13:37
ijwWe spawn the machine, and the PCI device handed to the spawn command.13:37
ijwDuring spawn (with libvirt) we add XML to direct map the device into memory.13:37
ijwAnd voila.13:38
ijwFrom here, we should look at the differing things we might be trying to do.  Case 2 we'll call 'grouping'13:38
ijwIn this, pci_attrs is 'group' and we're adding a 'group' attr at the pci_information stage13:39
*** sarob has quit IRC13:39
ijwSo, pci_information={ { device_id: 1, vendor_id: 0x8086}, { group => 'gpu' } }13:39
baoliwhat is device_id?13:40
ijwThe device ID of the whitelisted PCI device13:40
ijwDo I mean device ID?13:40
ijwYes, that's the right term13:41
*** ruhe is now known as ruhe_away13:41
baolibut we don't have a device_id13:41
heyongliproduct_id , i think it is13:41
heyonglithe standard pci property13:41
ijwOK, sorry - I'm looking at a (non-Openstack) page which calls it device ID, my apologies13:42
ijwSo, compute host gets 'group' for attrs when it requests it13:42
ijwAnd makes one PCI stat per 'group' value, rather than unique (vendor_id, product_id) tuple and reports that to the scheduler in this case13:43
ijwPCI flavor is going to be name gpu match expression { group: 'gpu' }13:43
ijwScheduling is as before13:43
ijwSorry, it will be 'e.group': 'gpu' per the spec about marking extra info when we use it13:44
*** ruhe_away is now known as ruhe13:44
ijwDifficult cases.13:44
ijwScheduling is harder when PCI flavors are vague and match multiple pci_stats rows, and particularly when they overlap13:44
*** coolsvap has joined #openstack-meeting-alt13:45
ijwSo, if I have two flavors, one is vendor:8086, device: 1 or 2 and one of which is vendor: 8086, device: 1 then you have more problems and the worst case is when you use both flavors in a single instance13:45
ijwSo, say I have the above two flavors, 'vague' and 'specific' for the sake of argument, and I want to start an instance with one device from each13:46
irenabijw: can we go over networking case taking into account phy_net connectivity?13:46
ijwOK, in a sec, I'll finish this case first13:46
irenabijw: afraid to be out of time13:46
ijwWhen I try and schedule, let's assume I have one product_id of each type13:46
*** amrith has quit IRC13:47
ijwThen there's a case that I can't use the device '1' for 'vague' because I would not be able to allocate anything for 'specific'.  The problem is hard, it's not insoluble, you just have to try multiple combinations until you succeed.13:47
ijwphysical networking cases:13:47
ijwImportant here is I have two network devices with different physical connections, so I need tobe able to distinguish and I can't do that by vendor/product13:48
irenabijw: yes13:48
irenabijw: assume neutron ML2 please13:48
irenabphysical netowrks/segments13:49
ijwRight, and here we get into the grey area13:49
ijwI'm not sure anything we've proposed to date solves the problem where a networking device can connect to some neutron networks but not to others.13:49
irenabijw: just assume provider_network is enough13:50
*** NikitaKonovalov has joined #openstack-meeting-alt13:50
irenaball neutron networks on certain provider_network can use same devices13:50
ijwirenab: the only solution to that problem that we have for provider networks at present is to ignore Neutron and label the devices on the provider networks with an extra_attr corresponding to the provider network.  Then you make a flavor per provider network and explicitly use the flavor.  But that doesn't work well with --nic arguments.13:51
ijwOr macvtap, for that matter.13:51
*** markwash has joined #openstack-meeting-alt13:51
baoliijw, we proposed to correspond a pci group to a provider network. that solved the issue elegantly.13:52
irenabijw: so going forward with the proposal you have, we still do not have a solution for networking?13:52
ijwbaoli: elegantly-ish.  If you do it that way then you would say --nic pci-flavor=provider_network_flavor,net-id=xxx and you can't check that the flavor and the network match easily so you can get yourself into trouble.13:52
ijwI think this is fixable by revisiting the code after we get the other cases working, it seems like we can do something in just the Neutron plugin to deal with the checks13:53
irenabijw: agree, but it will do the work ...13:53
*** colinmcnamara has joined #openstack-meeting-alt13:53
baoliijw, I dont' want to go back to those arguments13:53
*** jaypipes has joined #openstack-meeting-alt13:53
ijwbaoli: no, that's fine, just highlighting the outstanding issue.  I don't want to solve it now.13:53
ijwNetworking in general - where the network device is programmable13:53
baoliijw, we can also associate a PCI group with a network if that would cover all the use cases13:54
ijwbaoli: yes, that's about it, it's just the issue of making it usable from the bit of code in Neutron.13:54
ijwWe have a flavor containing SRIOV network devices, defined in pci_information as (presumably) something like { pf: ... device path ... }13:54
ijw* I don't think we have enough detail here so yes, this is vague.  Criticisms on the spec document please13:55
ijwHowever we set it up we end up with a PCI flavor that contains network devices we intend to use for neutron, which I shall call 'pcinet'13:56
irenabijw: I am confused, what is the approach with neutron programmable device?13:56
*** flwang has joined #openstack-meeting-alt13:56
ijwThat's what I'm covering now13:56
ijwSo we have a PCI flavor 'pcinet'13:56
irenabijw: how is it defined?13:57
ijwwhich 'it'?13:57
irenabproduct, vendor id + ?13:57
irenabit = PCI flavor13:57
*** safchain has joined #openstack-meeting-alt13:58
irenabwe have 2 mins....13:58
irenabCan we cover neutron requirements on Monday meeting?13:58
ijwIf it were me, I would probably tag it up on the backend - but wouldn't just vendor + product be enough if you wanted?13:58
ijwOn nova boot, we specify (my memory fails me here, correct the arguments as we go) nova boot --nic vnet-type=macvtap|passthrough,net-id=mynet,pci-flavor=pcinet ...13:58
ijwPCI device selection as usual (NIC device gets added to requirements before scheduling) but we need an extra bit of information to go to the compute node to point out the PCI device here has been allocated in response to --nic for interface 113:59
*** ruhe is now known as ruhe_away13:59
irenabijw: what do you mean by 'tag it up on the backend '?13:59
ijwextra_info13:59
baoliguys, times up14:00
ijwApologies, apparently I can't quite type fast enough14:00
ijwirenab: can we take this up on the list, I'm not sure I'm getting your concern.14:00
*** zhiyan has joined #openstack-meeting-alt14:00
baoliI can't imagine that we have a proposal that doesn't take care of the most of our concerns14:01
irenabbaoli: all: can we talk about neutron requirements next meeting?14:01
irenabijw: sure14:01
heyonglisure, irena14:01
baoliI believe it's solvable, but I just don't get it14:01
baoliIrena, sure14:01
baoli#endmeeting14:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:01
openstackMeeting ended Thu Jan 16 14:01:36 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-16-13.01.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-16-13.01.txt14:01
ijwI'm good with that, I think we have some details to work out about what info is needed where but that aside we're ok14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-16-13.01.log.html14:01
*** akuznetsov has quit IRC14:01
*** heyongli has quit IRC14:01
ijwSorry, I'd flip to openstack-neutron but I don't have time right this second - I'll be reading mail again later14:02
irenabijw: can we switch to openstack-dev?14:02
ijwirenab: will you be around in an hour?14:02
irenabijw: ok, lets follow later14:02
ijwI'm pleased we got that recorded, you know ;)14:02
irenabijw: probaly not ...14:03
irenab^probably14:03
ijwOK - then let's take half an hour now, that should be fine - need to catch something before 4 but half an hour will be enough for dealing with my errand14:03
ijw-> #openstack-dev14:03
markwashgood morning glance14:03
markwash#startmeeting glance14:04
openstackMeeting started Thu Jan 16 14:04:03 2014 UTC and is due to finish in 60 minutes.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.14:04
rosmaitagood morning!14:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:04
*** openstack changes topic to " (Meeting topic: glance)"14:04
openstackThe meeting name has been set to 'glance'14:04
zhiyangood morning14:04
*** nati_ueno has joined #openstack-meeting-alt14:04
*** sadasu has quit IRC14:05
markwash#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:05
markwashbit light today14:05
rosmaitait's ok if we end early14:06
markwashindeed14:06
rosmaitathough it would have been better to start later!14:06
markwashheh perhaps14:06
rosmaitadid you get a chance to think about exposing 'owner' in v2?14:07
markwash#topic expose 'owner' in v2 (rosmaita)14:07
*** openstack changes topic to "expose 'owner' in v2 (rosmaita) (Meeting topic: glance)"14:07
markwashwhen I thought about it explicitly I couldn't really think of a reason why we should hide it14:07
rosmaitaok14:07
markwashand just mulling on it didn't yield any other reasons for concern14:07
rosmaitame neither, plus i think it will be needed anyway when we kill off v114:08
markwashso it seems fine to move ahead with it14:08
rosmaitathis seems like a simple BP, "expose 'owner' in image response"14:08
markwashand probably simple code as well14:08
rosmaitabut i'm not sure if we were thinking about a new process?14:08
*** obondarev_ has joined #openstack-meeting-alt14:08
rosmaitai agree, i could possibly code it myself :)14:08
markwashI don't quite see how a new process would be necessary14:09
rosmaitame neither, thought I'd check though14:09
*** SushilKM has joined #openstack-meeting-alt14:09
markwashwell I think we're in good shape on this one, no one else objects?14:09
zhiyansounds good to me14:10
rosmaitacool14:11
zhiyanso we just need to change api controller ? or ned to change domain also?14:11
zhiyans/ned/need14:11
*** nermina has joined #openstack-meeting-alt14:11
markwashI think owner is already an attribute of the image object14:11
rosmaitayes, it's already in domain object14:12
markwash#topic deprecated options in glanceclient (rosmaita)14:12
*** openstack changes topic to "deprecated options in glanceclient (rosmaita) (Meeting topic: glance)"14:12
markwash(hope switch wasn't too soon)14:12
rosmaitathis is a minor thing14:12
*** akuznetsov has joined #openstack-meeting-alt14:12
rosmaitajust from a user perspective14:12
*** NikitaKonovalov has quit IRC14:12
rosmaitaever since i've been working on glance, theCLI help gives you a long list of stuff, mostly DEPRECATED14:13
zhiyanok got it (seems my network today has bigger delay, sorry)14:13
rosmaitawas wondering if we could clean that up a bit14:13
rosmaita(since it's a light week)14:13
*** yatin has joined #openstack-meeting-alt14:13
rosmaitabut, i'm not real clear on the client contract and versioning14:13
markwashrosmaita: I think its a good point, I was hoping we could do that in the major version bump14:14
rosmaitaso that would be with Icehouse?14:14
markwashbut it seemed like we never got anywhere with folks about how we can *do* the major version bump14:14
*** yatin has left #openstack-meeting-alt14:14
rosmaitayeah, that was my recollection, too14:14
rosmaitamaybe we can discuss at mini-summit?14:15
markwashyes14:15
rosmaitaiccha had mentioned that maybe we should have a "stability & cleanup" session14:15
rosmaitai think she's worried that with all the sexy new metadata catalog stuff, normal stability issues might get lost14:16
*** lblanchard has joined #openstack-meeting-alt14:16
markwashthat's a fine idea as well14:16
markwashI have added both of those ideas as potential topics on the mini summit agenda14:17
rosmaitai'll add to the agenda ... maybe sign up everyone as interested by default? :P14:17
rosmaitanetwork delay!14:18
markwashrosmaita: I'd like to work with some folks to move to the next level on the mini summit agenda, from ideas to more like plans14:18
markwashare there some folks on your end that could help me out? I imagine ashwini would be interested, but perhaps others as well?14:18
rosmaitai think everyone will be interested in helping out14:19
*** nati_ueno has quit IRC14:19
zhiyanmarkwash: interesting, which part ? :P14:20
rosmaitamaybe we can ask people to "adopt" a session and map it out with more details14:20
*** nati_ueno has joined #openstack-meeting-alt14:20
markwashyes, I think we need to announce a deadline for finalizing the topics perhaps, and if a topic doesn't have a leader/moderator by that time we figure we can hash it out on the ML or in informal time?14:21
flwangrosmaita: will you discuss the image marketplace on the mini summit?14:21
rosmaitayeah, i was thinking it would be cool if each session got a ML announcment so people who can't attend can reply to the thread and have their views represented14:21
markwashoh neat idea14:22
rosmaitaflwang: hi , yes i was thinking of doing that one14:22
markwashbefore or after the summit?14:22
*** banix has joined #openstack-meeting-alt14:22
rosmaitabefore, if we have time14:22
flwangmarkwash: before14:22
markwashsounds good14:22
flwangmarkwash: after confirm the topic list?14:22
rosmaitabut it is running out fast!14:22
*** julim has joined #openstack-meeting-alt14:22
markwashwe probably have about enough if we set up a timetable pretty immediately14:23
*** demorris has joined #openstack-meeting-alt14:23
flwangrosmaita: I love the image marketplace idea, since both AWS and Nebula have it14:23
markwashhow about if we get people to pick their topics by monday and send out email introductions by tuesday?14:23
rosmaitathat seems reasonable14:24
*** glucas has left #openstack-meeting-alt14:24
markwash*OpenNebula I think14:24
rosmaitai think you can ask anyone on the titan team to pick up an orphan topic14:24
markwashdoes 12 topics total seem okay? about 6/day?14:25
markwashwould 5/day be too few?14:25
markwash(I just counted and we have 14 suggestions on the list so far, not all of them adopted of course)14:25
flwangmarkwash: yep :) thanks for the correcting14:25
markwashrosmaita: okay thanks, we may need to do that14:26
rosmaitathat's a tough question14:26
*** SushilKM has quit IRC14:26
rosmaita6 topics would be 6 hours in-session + lunch + coffee == 8 hours14:26
*** obondarev__ has joined #openstack-meeting-alt14:26
rosmaitathat would leave time for disucssion after dinner14:26
rosmaitato follow up on that day's stuff14:27
rosmaitaexcept that wouldn't work on 2nd day14:27
markwashokay, so on that schedule 6 doesn't seem too skimpy, and even 5 might be okay14:27
markwashso perhaps if its an odd number or low, we should frontload the schedule14:27
rosmaitai think so14:27
rosmaita+1 to frontloading14:27
rosmaitai definitely don't think it's too light14:28
markwashyeah, i think our open discussion time will be better if its after the formal-ish sessions14:28
rosmaita+114:28
markwashokay cool, glad it doesn't seem too light14:29
markwashI'll be happy then if we do a solid 5/5 or 6/414:29
markwash#topic open discussion14:29
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:29
*** obondarev_ has quit IRC14:29
markwash(since we're on it anyway :-) )14:29
markwashanyone particularly concerned about their i-2 blueprints? I think we might end up deferring a lot14:30
markwashbut we have made good progress lately and have room in i-3 so I'm not very worried14:30
zhiyanmarkwash: do you think it's a good time to think about giving LocationRepo to glance v2 domain?14:31
markwashzhiyan: yes, I think its about time14:31
markwashzhiyan: with image location status, it will be nicer to have some domain code to handle the possible status values14:31
markwashand I realize from looking at the db code we really need to allow the clear distinction in the http api between add, replace, and remove to be expressed at the db api level14:32
zhiyanmarkwash: or do it in J?14:32
markwashzhiyan: I was trying to work on it last night but couldn't quite get my brain to thaw :-)14:32
markwashI'll revisit it today/tomorrow/this weekend14:32
markwashshouldn't take long once it seems a bit more clear, which usually only takes a few days of mulling14:33
rosmaitazhiyan: i have not been following closely, we are adding 'status' to locations, but not 'checksum' I hope?14:33
zhiyanmarkwash: ah, cool14:33
markwashrosmaita: just status, and its basically an internal field14:33
zhiyanrosmaita: yes, not yet14:34
flwangmarkwash: I think I may have to defer the image-recover14:34
zhiyanyes14:34
markwashrosmaita: the idea is that we can track deletion and "pending_deletion" on the locations themselves, which makes scrubber and other things cleaner14:34
*** sarob has joined #openstack-meeting-alt14:34
*** balajiiyer has joined #openstack-meeting-alt14:34
rosmaitacool14:34
markwashflwang: noted, thanks for the heads up14:34
*** jmcbride has joined #openstack-meeting-alt14:34
*** SergeyLukjanov is now known as SergeyLukjanov_a14:35
rosmaitamaybe this can be part of the "stability" session, but before we branch out too much with the metadata catalog stuff, i was wondering if we need to record a glance "philosophy" about what it's core principles are14:35
flwangmarkwash: since it's depending on zhiyan's locations status bp14:35
rosmaitaAFAIK, right now, it's just folklore14:35
zhiyanmarkwash: i believei location_repo will help more, when we try to add multi-hypervisor deployment support right? (like checksum, size, format ...)14:35
markwashyeah, that's a good thought, something I think iccha had mentioned was maybe a glossary14:36
*** alagalah has joined #openstack-meeting-alt14:36
markwashrosmaita: I sense you are a little concerned about the "metadata" repo stuff. . I somehow missed out on the december conversation that was had around that14:36
markwashzhiyan: yes I think there are a lot of avenues there14:36
rosmaitamarkwash: well, slightly concerned14:37
markwashthough we end up just having to figure out how we make it clear what those mean on a location vs on the image, but I think its do-able14:37
markwashrosmaita: I confess, I think I'm a bit against the idea of storing metadata generically14:37
rosmaitai think it's a great idea, and will enhance searching and allow relationships and stuff, but i'd still like glance to be glance14:37
rosmaitaso i am kind of mixed14:37
markwashit took a long while to get here, but I think we get a lot of benefit from knowing what our metadata means14:38
*** jmcbride has quit IRC14:39
*** sarob has quit IRC14:39
markwashokay, I think we're about tapped out (or I've netsplit :-) )14:39
markwashany other parting thoughts? I will email ashwini to set up a time for more mini summit planning discussion14:40
rosmaitanothing from me14:40
flwangi'm clear14:40
*** jmcbride has joined #openstack-meeting-alt14:41
markwashzhiyan, flwang, rosmaita thanks!14:41
markwashzhiyan, flwang keep up the great reviews!14:41
zhiyanmarkwash: nothing from me too. btw, you can ping me for anything around location_repo (actually i'm thinking if i can do that)14:41
flwangmarkwash: and coding !!!14:41
markwashheh yes and coding!14:41
zhiyan:P14:41
markwash:-)14:41
markwashzhiyan: sure thing14:42
rosmaitabye!14:42
markwash#endmeeting14:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:42
openstackMeeting ended Thu Jan 16 14:42:54 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-01-16-14.04.html14:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-01-16-14.04.txt14:42
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-01-16-14.04.log.html14:43
zhiyanmarkwash: btw, if you have time pls give some review on my patch :)14:43
markwashzhiyan: definitely14:43
zhiyanlater~14:43
zhiyanmarkwash: thanks!14:43
*** rraja has joined #openstack-meeting-alt14:46
*** eharney has quit IRC14:49
*** obondarev__ has quit IRC14:49
*** obondarev_ has joined #openstack-meeting-alt14:51
*** amrith has joined #openstack-meeting-alt14:53
*** bnemec has joined #openstack-meeting-alt14:55
*** bnemec has quit IRC14:55
*** bnemec has joined #openstack-meeting-alt14:56
*** amrith has quit IRC14:57
*** kevinconway has joined #openstack-meeting-alt14:59
*** aostapenko has joined #openstack-meeting-alt15:00
*** boris-42 has quit IRC15:00
*** julienvey_ has quit IRC15:00
*** achirko has joined #openstack-meeting-alt15:00
*** bswartz has joined #openstack-meeting-alt15:00
bswartz#startmeeting manila15:01
openstackMeeting started Thu Jan 16 15:01:08 2014 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: manila)"15:01
openstackThe meeting name has been set to 'manila'15:01
aostapenkohi15:01
rrajahi15:01
achirkohello15:01
bswartzhello everyone15:01
yportnovahi15:01
vponomaryovhello15:01
*** caitlin56 has joined #openstack-meeting-alt15:01
bswartzso I haven't updated the agenda, as usual15:02
bswartzmy previous meeting ran right into this one15:02
*** SergeyLukjanov_a is now known as SergeyLukjanov15:02
bswartzlet's jump right into development status -- I know a number of exciting things are getting close to completion15:03
bswartz#topic dev status15:03
*** openstack changes topic to "dev status (Meeting topic: manila)"15:03
*** shamail has joined #openstack-meeting-alt15:03
yportnovahttps://review.openstack.org/#/c/66001/15:03
yportnovahttps://review.openstack.org/#/c/62917/15:03
scottdahi15:03
yportnovasecurity services are merged15:03
bswartzyportnova/vponomaryov: please share the updates we discussed on monday15:03
bswartzyportnova: thx15:04
vponomaryovDev status:15:04
vponomaryov1) network-api15:04
vponomaryova) share-networks (approved name from previous meeting)15:04
vponomaryovshare-network on server side - https://review.openstack.org/#/c/66587/15:04
vponomaryovshare-network on client side - https://review.openstack.org/#/c/59466/15:04
vponomaryovb) security-services has already been merged - https://review.openstack.org/#/c/66001/15:04
vponomaryovc) api for linking 'a' and 'b' - TODO15:04
vponomaryov2) Multitenant Generic driver (draft / work in progress) - https://review.openstack.org/#/c/67182/15:04
vponomaryov3) Multitenant NetApp driver (work in progress) - https://review.openstack.org/#/c/59100/15:05
vponomaryov4) manila's tempest code has been merged into %manila_project%/contrib/tempest15:05
vponomaryovIt has all currently existing tests for manila15:05
vponomaryovChange to openstack-infra/config to enable tempest from that plugin for our 'devstack-job' - https://review.openstack.org/#/c/66846/15:05
bswartzand a reminder for those who don't know, the generic driver will use cinder+nova to create VMs and storage on the tenant network and export it using NFSD or Samba15:05
vponomaryovthat all for status15:06
bswartzvponomaryov: that was awesome, ty15:06
bswartzso this reminds me15:06
caitlin56bswartz: so partitions (as opposed to VMs) will be supported when nova supports them?15:07
bswartzthere is some overlap with the current generic driver approach and the so-called bridged networking approach15:07
bswartzbut first, any questions on the current status?15:07
bswartzcaitlin56: what do you mean by partitions?15:07
*** rwsu has joined #openstack-meeting-alt15:07
bswartzdo you mean disk partitions?15:07
caitlin56What Solaris calls zones: "lite" VMs.15:08
bswartzoh, you mean something like a LXC-based VM15:08
caitlin56bswartz: yes15:08
shamailvponomaryov and bswartz: Is the NetApp reference driver leveraging vFiler assisted Multi-tenancy and the generic driver is using hypervisor-assisted Multi-tenancy?  (Think the answer is yes but wanted to confirm) Is the delivery time-line the same or will one be complete before the other?15:09
bswartzyeah that's not something I've looked into -- I'm not sure of how well nova support LXC/OpenVZ -- but it doesn't matter so much for us15:09
bswartzUsing those hypervisors is signigicantly more efficient for the kinds of things manila needs to do, but it's just a performance optimization compared to full virtualization15:10
caitlin56So no specific issue was encourntered, just a determination that this is probably complex enough that nova should handle it.15:10
caitlin56?15:10
*** irenab has quit IRC15:10
bswartzor rather, a scalability optimization15:10
bswartzshamail: yes the netapp driver relies on vservers15:11
*** zhiyan has left #openstack-meeting-alt15:11
bswartzshamail: the netapp driver and the generic driver are being worked on in parallel15:11
shamailGreat, thanks.  We'd need to look at both.15:11
bswartzcaitlin56: in the interest of limiting complexity for ourselves, I want to ignore the hypervisor issue and just assume that "nova will handle it"15:12
caitlin56bswartz: that might be worth capturing as a design rationale.15:12
*** bill_az has joined #openstack-meeting-alt15:12
bswartzif someone wants to dig into what exactly nova can support I'd encourage them to do some experiments and share the results15:13
bswartzI could easily see some future enhancement in Juno where we add LXC/OpenVZ support15:13
*** dianefleming has quit IRC15:13
*** dianefleming has joined #openstack-meeting-alt15:14
*** nati_uen_ has joined #openstack-meeting-alt15:14
*** mestery_ is now known as mestery15:14
bswartzbut this discussion segues nicely into the other topic I brought up15:14
vponomaryovAFAIK, Nova supports LXC, but with limitations, why do we consider LXC at all as possible variant to use?15:14
aostapenkolxc doesn't support runtime volume attachment15:14
bswartzvponomaryov: mostly because you can run significantly more LXC instances on the same hardware than you can KVM instances15:14
*** NikitaKonovalov has joined #openstack-meeting-alt15:15
bswartzLXC/OpenVZ are dramatically more efficient virtualization technologies when you don't need the full feature set that KVM provides (i.e. full hardware virtualization)15:15
vponomaryovalso, OpenVZ requires patched linux core15:16
vponomaryovif I am not mistaken15:16
achirkobswartz: for generic driver networking we have 2 pollible implementations and no concensus15:17
bswartzanyways, I wanted to ignore these issues for now because they're a distraction from our core mission15:17
bswartzwhich is to deliver shared filesystems as a service15:17
*** nati_ueno has quit IRC15:17
achirkobswartz: here is doc which outlines two solutions https://docs.google.com/document/d/1kX7-S8aClxleydlbm6NmFEWirnyk7hsd4UhqxXcC0KA/edit?usp=sharing15:17
bswartzachirko: can you explain?15:17
bswartzoh yea15:18
bswartzthis deserves some time for discussion15:18
*** amytron has joined #openstack-meeting-alt15:18
bswartz#topic network communication between manila and service VMs15:18
*** openstack changes topic to "network communication between manila and service VMs (Meeting topic: manila)"15:18
bswartzokay so as we've discussed earlier, the generic driver will create nova instances (called "service VMs") to actually service the shared filesystems into the tenants' networks15:19
bswartzthese service VMs will have a network interface on the tenant network, and therefore there won't automatically be a network communication path between manila and these VMs15:20
bswartzobviously manila needs to be able to communicate with the VMs it creates, so there are a few options15:20
bswartzthx to achirko for providing a writeup of the situation15:20
bswartzthe 2 basic approaches break down like this:15:21
*** nati_uen_ has quit IRC15:21
*** betsy has joined #openstack-meeting-alt15:21
achirkofeel free to comment inside document or here15:21
bswartz1) manila creates virtual network intefaces connected to the tenant network on the manila node and uses those to talk to the VMs15:21
*** nati_ueno has joined #openstack-meeting-alt15:21
*** BradVandehey has joined #openstack-meeting-alt15:21
bswartz2) we add a second IP address to the VMs which is connected to somewhere that manila can reach through its default routes15:22
bswartzI don't have strong feelings about either approach, except that if we add secondary IP addresses to the service VMs, then those should be on a network that's protected from security threats15:22
bswartzthe "floating IP" approach implies that these VMs will have public IPs, which I don't like15:23
*** aignatov has quit IRC15:23
caitlin56A third option would be to have the "Base server" act as an application layer gateway, rather than as a router.15:23
bswartzwe would almost need to create a new type of floating IP which is for internal services rather than for use by end users15:24
bswartzcaitlin56: I don't follow15:24
yportnovabswartz: "floating IP" approach implies that these VMs will have public IPs - in theory we can create separate floating ip pool for Manila15:24
caitlin56Hey base server you need to tell your subsidiary server fornetwork x this.15:25
bswartzyportnova: does neutron explicitly support multiple pools of floating IPs?15:25
yportnovabswartz: http://docs.openstack.org/grizzly/openstack-network/admin/content/adv_cfg_l3_agent_multi_extnet.html15:25
*** xyang has joined #openstack-meeting-alt15:25
bswartzyportnova: how hard is that to setup, and will it be a hassle for users of manila?15:25
aostapenkonow we do not have an ability to use 2 floating ip pools15:25
bswartzcaitlin56: how would that be implemented15:26
yportnovabswartz: but there is bug https://bugs.launchpad.net/neutron/+bug/1212947. It is not confirmed but affects some people15:26
achirkobswartz: documentation says that we can have multiple floating ip pool, but on practice it doesn't work - I tried it15:26
caitlin56you would need to add a message relay daemon on the base server, i'm presuming each vendor knows how to talk to their own vservers within their box.15:27
bswartzachirko: hah!15:27
bswartzwho would have guessed that the openstack docs might be wrong?15:27
caitlin56achirko: the real trick is that you would want parallel allocation of floating ips. Basically, "matching" terminal numbers on each subnet. That's the way they would be assigned manually, and the only way a human could ever track what was going on.15:28
bswartzcaitlin56: we're not talking about drivers other than the generic driver -- it's presumed that vendor drivers have ways of solving the problem of talking to their vservers15:28
bswartzthe issue here is that the generic driver will be using nova to create its "vservers" (actually service VMs) and that nova doesn't provide a generic mechanism for talking to them across networks15:28
*** tanisdl has joined #openstack-meeting-alt15:29
bswartzso its up to us to create that mechanism15:29
bswartzachirko: I'm leaning towards approach 1, because it sounds simpler for the administrator15:30
bswartzachirko: what are the downsides to approach 115:30
*** ijw has quit IRC15:30
achirkobswartz: more work for us, developers15:30
*** IlyaE has joined #openstack-meeting-alt15:30
bswartzah15:31
*** balajiiyer has left #openstack-meeting-alt15:31
*** ijw has joined #openstack-meeting-alt15:31
bswartzso helpe me understand here why linux network namespaces are needed15:31
yportnovabswartz : using 1 approach we will have low-level dependency on Neutron internal implementation15:31
*** aignatov has joined #openstack-meeting-alt15:31
achirkobswartz: we need to have neutron agent set up and runnign on Manila node15:31
bswartzcan't we just create bridge interfaces and vnets?15:31
bswartzrequiring a neutron agent doesn't bother me too much -- I suspect there will be similar requirements for the gateway-based multitenancy -- which I want to get to in a minute15:32
caitlin56Could we do this with a firewalled router?15:33
*** ashaikh has joined #openstack-meeting-alt15:33
achirkobswartz: we need net-ns for virtual interfaces isolation - we can have 2 private subnets with the same cidr15:33
bswartzachirko: are you sure that's allowed? I was under the impression that openstack didn't allow re-use of IP addresses15:33
caitlin56That is we explicitly allow manila to have a message routed to the share-network via a router which enforces firewall rules (so general public cannot do this).15:33
achirkobswartz: as well as for security - to isolate manila node from tenant's private subnet15:34
bswartzcaitlin56: I think that secure firewalling is implied in any of these configurations -- it's not optional15:34
bswartzcaitlin56: the thornier issue is the basic routing and bridging15:34
caitlin56bswart:z: true. But by default there would be no routes between tenant networks.15:35
*** ashaikh_ has joined #openstack-meeting-alt15:35
*** Barker has joined #openstack-meeting-alt15:35
caitlin56Neutron might allow routing from the basenetwork to tenant networks however.15:35
*** BradVandehey has quit IRC15:36
bswartzachirko: have you actually prototyped approach 1 to show that it works?15:36
*** ashaikh has quit IRC15:36
*** ashaikh_ is now known as ashaikh15:36
bswartzor is it theoretical at this point?15:36
achirkobswartz: we can have 2 subnets with the same cidr as long as they resides in different neutron networks15:37
bswartzachirko: okay so it sounds like neutron has gotten smarter since I last checked15:37
caitlin56achirko: that would force those tenant networks to be fully isolated,correct?15:37
caitlin56you would not have a unique IP address while sitting in the common ntework to refer to a tenant endpoint.15:38
achirkobswartz: I pretty sure it will work because neutron uses similar approach for l3 and dhcp services15:38
*** tanisdl has quit IRC15:38
bswartzokay15:38
bswartznetapp has supported that kind of isolation for a long time -- we call it "ipspaces"15:38
bswartzit's hard to wrap your mind around though -- I worry about new users or even developers getting confused15:39
achirkocaitlin56: neutron network = l2 isolated domain using vlan, gre etc.15:39
*** jprovazn is now known as jprovazn_afk15:39
bswartzokay well I'm going to cast my vote for approach 1 at this point15:40
bswartzI'd like to at least try it and see if we can make it work15:40
caitlin56bswartz: many systems have a concept of a "common" or DMZ VLAN,. Anyt VLAN can route to it, it can route to any, but other VLANs cannot route to each other.15:40
bswartzthe floating IP approach can be a fallback plan15:40
bswartzcaitlin56: this is stronger separation than that15:40
*** jmcbride has quit IRC15:40
*** dprince has joined #openstack-meeting-alt15:41
*** julienvey_ has joined #openstack-meeting-alt15:41
bswartzan ipspace or netns is a whole separate set of routing tables15:41
bswartz2 networks in different namespaces don't even share the same routing universe15:41
bswartzas an aside, one of the reasons this is needed is because IPv4 doesn't offer a large enough address space15:42
*** tanisdl has joined #openstack-meeting-alt15:42
caitlin56Yes, common universal address almost requires IPV6 addressing.15:42
aostapenko+1 for first approach15:43
bswartzanyone disagree on the approach for communication between manila generic driver and is service VMs?15:43
achirkobswartz: I'm also for the first solution15:43
bswartzthat's 3 for the first solution15:43
shamailbswartz: First approach15:43
yportnovabswartz: I think 2 approach is better15:43
caitlin56How does the manila agent keep the clients distinct?15:43
bswartzyportnova: but approach 2 has some dependencies on stuf that doesn't work currently15:44
bswartzyportnova: can you explain why you think approach 1 is wrong?15:44
yportnovabswartz: I think the 1 approach is not good because Manila will depend on how networking is implemented in Neutron15:45
*** mattgriffin has joined #openstack-meeting-alt15:45
bswartzyportnova: only the generic driver will15:46
yportnovaGeneric driver will work only with Neutron (but currently we do not have alternatives)15:46
bswartzyportnova: and the generic driver already depends on several other key openstack projects, like nova and cinder15:46
yportnovabswartz: sorry, I meant the generic driver15:46
*** gokrokve has quit IRC15:46
*** gokrokve_ has joined #openstack-meeting-alt15:47
bswartzother drivers such as the NetApp driver won't need this because we can talk to the vservers through the cluster interface15:47
yportnovabswartz: yeah, but it does nor depend on how Nova spawns the VMs15:47
yportnovaand how Cinder provides volumes15:47
caitlin56Will the generic he  need to talk to a Vserverinstance from a child process associated with the network namespace?15:48
caitlin56generic driver need to talk...15:48
yportnovaAnd floating IP is one of important Openstack features, that provides access to VMs. And I hope the bug with multiple pools will be fixed15:48
aostapenkoyes, it's more low-level dependency, but it's dependency on core neutron architecture15:49
achirkobswartz: Yes, 1st approach introduces dependancy on Neutron architecture15:49
bswartzbut wait, doesn't the manila core also depend on neutron for basic things like provision IP addresses in tenant networks?15:49
bswartzhow is this different?15:49
caitlin56Will any vendor driver be able to implement its own solution on how to talk with its vservers?15:50
yportnovabswartz: yeah, but we just communicated with its API, and do not depend on implementation15:50
bswartzcaitlin56: not only will you be able to, you will have to15:50
bswartzcaitlin56: unless you reuse some code from the generic driver15:50
caitlin56bswartz: then I have no objection to either option.15:50
aostapenkothat is like dependency novas vif driver on neutron architecture, but not so complicated15:51
bswartzyportnova: can you explain how this introduces a deeper dependency?15:51
bswartzmaybe I'm thinking about approach 1 incorrectly15:51
*** nam_nguyen has joined #openstack-meeting-alt15:51
achirkobswartz: Manila will need to know ovs integration bridge name15:52
bswartzI had assumed that it would work the same, where we provision an IP from the tenants network to ourselves, and the generic driver takes care of creating a bridged network interface to the tenant network and binding the IP to that interface15:52
vponomaryovneutron api is interface for us, but in approach one we will depend on neutron architecture that is behind the API15:52
*** mattgriffin has quit IRC15:52
aostapenkothe most core architecture15:53
bswartzwell I don't see a deeper dependency on neutron as a large downside, for the generic driver15:53
bswartzwho would really use that driver outside of an openstack configuration which included nova, cinder, AND neutron?15:54
bswartzare there any credible alternatives to neutron that you could use with manila+nova+cinder?15:54
caitlin56bswartz: the fundamental issue is whether the IP address of the vserver for management purposes is global or not. If it is globally unique then you can set up routing rules about who can  talk with it.15:54
*** colinmcnamara has quit IRC15:54
bswartzcaitlin56: it sounds pretty clear that it's not unique15:54
caitlin56If it is not globally unique then you need to talk with it from a process that is scoped for the correct network namespace.15:54
bswartzoh wait15:55
bswartzno the tenant-facing address is not unique, but the manila-facing address could be15:55
bswartzwell I'd like to make a decision on this in the interest of forward progress15:56
caitlin56If the manila-facing address is unique then neutron can set up the required routes to allow *only* the desired access.15:56
bswartzyportnova: we may need to change the implementation later on if the dependency on neutron turns out to be a bad thing15:56
yportnovabswartz: sure15:57
bswartz#agreed manila generic driver will communicate with service VMs using neutron-provisioned virtual interfaces on the manila management node15:57
bswartzokay we used up almost all our time on that issue15:57
bswartzbut it was a good discussion to have15:57
bswartz#topic open discussion15:57
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:57
bswartzany last minute things?15:57
achirkobswartz: The main thing for generic driver is to make sure it will work with standard devstack inslalation, and approach 1 deliveres this15:58
bswartzachirko: agreed15:58
*** prasadv has joined #openstack-meeting-alt15:58
shamailAny anticipated dates for the new reference drivers yet?15:58
shamailDates being a loose term here, really time-frame15:58
bswartzshamail: just a couple of weeks tops15:59
*** kebray_ has joined #openstack-meeting-alt15:59
*** boris-42 has joined #openstack-meeting-alt15:59
bswartzshamail: probably by the end of the month?15:59
shamailAwesome15:59
shamailThanks.15:59
*** songole has joined #openstack-meeting-alt15:59
bswartzokay we need to vacate tthis channel -- grab me in #openstack-manila if you need anything else15:59
bswartzthanks all15:59
*** caitlin56 has quit IRC15:59
yportnovathanks15:59
bswartz#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Jan 16 16:00:00 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-01-16-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-01-16-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-01-16-15.01.log.html16:00
aostapenkothanks, bye16:00
mesteryHi16:00
*** s3wong has joined #openstack-meeting-alt16:00
*** Leonr has joined #openstack-meeting-alt16:00
mestery#startmeeting networking_policy16:00
*** achirko has quit IRC16:00
openstackMeeting started Thu Jan 16 16:00:44 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: networking_policy)"16:00
openstackThe meeting name has been set to 'networking_policy'16:00
mestery#link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy Agenda16:00
banixHi everybody16:01
s3wongHello16:01
mesteryWe'll wait a minute or two to gather everyone.16:01
mesterybanix s3wong: Howdy!16:01
ashaikhhi guys16:01
nam_nguyenHi all16:01
songoleHi all16:01
prasadvhello16:01
mesterySo, we have a short agenda for today.16:02
*** jmcbride has joined #openstack-meeting-alt16:02
*** xyang has left #openstack-meeting-alt16:02
mesteryThe main thing I wanted to discuss was the PoC, which we started talking about last week.16:02
mestery#topic Group Policy PoC16:02
*** openstack changes topic to "Group Policy PoC (Meeting topic: networking_policy)"16:02
mestery#link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy Neutron Group Policy PoC Document16:02
alagalahGood morning all16:03
*** dprince has quit IRC16:03
mesteryalagalah: Morning!16:03
*** eharney has joined #openstack-meeting-alt16:03
mesteryI don't think the document has changed much.16:03
mesteryBut the small subset of us who volunteered to work on the PoC have been discussing over email how to divide the work up.16:03
banixI just added the Heat work item; That's all.16:04
mesterybanix: Thanks!16:04
alagalahCount me in16:04
mesterySo really, we have a high level plan. I think we should put names by the tasks as we discussed.16:04
*** ruhe_away is now known as ruhe16:04
*** dprince has joined #openstack-meeting-alt16:04
mesteryalagalah: Awesome, glad to have you onboard!16:04
*** michsmit has joined #openstack-meeting-alt16:05
s3wongmestery: haven't seen your reply - have we finalized on who is doing what?16:05
alagalahmestery:  I live to serve :)16:05
*** thinrichs has joined #openstack-meeting-alt16:05
mesterys3wong: I think there are a few details left, for instance, I don't know if anyone signed up to implement the new extension APIs for GRoup Policy.16:05
mesterys3wong: Did you claim that item?16:05
* mestery forgets.16:05
s3wongmestery: sure16:05
mesteryCool! Can folks who have signed up put their names by the tasks?16:06
*** hemanthravi has joined #openstack-meeting-alt16:06
mesteryAlso, there was some discussion around coordinating this work.16:06
mesteryLogistically.16:06
*** kebray_ has quit IRC16:06
mesterys3wong and banix, you guys had some concerns here, right?16:06
s3wongI also believe banix volunteered for ML2 driver part16:06
s3wongmestery: yes16:06
banixMestery: Let's list the work items you had made16:06
*** jgriffith has joined #openstack-meeting-alt16:06
s3wongactually, rather, he volunteered for the ML2 plugin part16:07
songoleWe will do the heat plugin16:07
mesterysongole: Excellent! If you need edit access to the google doc, let me know, but I think I added you there.16:07
banixSo the main items were: The Ml2 plugin part (I volunteered) which includes the driver I would think16:07
songolemestery: Yes, I have access to it.16:07
s3wongthe extension APIs (which I volunteered)16:08
banixThe agent side that Mestery volunteered16:08
s3wongand the OVS agent (which mestery volunteered)16:08
* mestery nods in agreement.16:08
banixand yes the s3wong for Tom Mathews16:08
banixsorry ignore the last line16:08
hemanthravimestery: if you there are pieces on the agent side you want us to pick up, we can16:08
*** xuhanp has quit IRC16:09
mesteryhemanthravi: OK, cool! Will coordinate with you folks.16:09
*** colinmcnamara has joined #openstack-meeting-alt16:09
banixthe extension side that s3wong volunteered16:09
mesterySo, how much of this can we do in parallel?16:09
alagalahThe key will be not treading on each other's code16:10
*** betsy has quit IRC16:10
songoleheat is independent and can go in parallel.16:10
*** shamail has quit IRC16:11
s3wongMy part can be done rather independently - though Heat template would have the APIs as dependency16:11
banixSo may be we can nail down for the moment the API16:11
mesterybanix: Yes, good idea. That may be a first step.16:11
alagalahI'd like to work with banix on the ML2 driver16:11
*** NehaV has joined #openstack-meeting-alt16:11
mesteryI can start looking from the agent side right away as well.16:11
banixalagalah: Sounds good16:11
mesteryE.g. the flows we'll need to implement.16:11
mesteryCan someone refresh my memory on what we'll implement first? Was it security group like constructs?16:12
s3wongmestery: for action - just action_type 'security'16:12
mesterys3wong: Got it.16:12
s3wongbut endpoint, endpoint groups, policy, policy-rule will all be part of the PoC16:13
*** bswartz has left #openstack-meeting-alt16:13
banixs3wong: yes16:13
songoles3wong: can we work on API proposal this week?16:14
mesteryOK, this is all good.16:14
banixI will also implement the model (based on the model we have in the doc) so they are in code.16:14
s3wongsongole: of course16:14
mesterybanix: Awesome, thanks!16:14
songoles3wong: thanks.16:15
*** nati_uen_ has joined #openstack-meeting-alt16:15
mesteryOK, anything else to discuss at this meeting around the PoC?16:16
songoleI didn't see cli commands for classifier. I am hoping classifier is a neutron object and will have an API.16:16
banixsongole: yes, it's in the model I believe. What do you mean by cli?16:17
s3wongsongole: classifier is indeed a neutron object16:17
banixwe haven't defined the cli as such16:17
*** nati_uen_ has quit IRC16:17
songolebanix: I meant REST API examples16:18
*** nati_uen_ has joined #openstack-meeting-alt16:18
*** nati_ueno has quit IRC16:19
s3wongsongole: add/modify/delete classifier should be part of the APIs, we should finalize that this week as part of the API proposal16:19
banixyes they are Neutron objects16:19
songoles3wong banix: got it16:20
* mestery nods in agreement with s3wong and banix.16:20
alagalahbanix:  I have a pretty full dance card today, want to get together tomorrow to flesh out the details?16:21
alagalahbanix:  We could do over email if more convenient?16:21
banixalagalah: Sounds good.16:21
s3wongI will work with the rest of the PoC team to get the first draft of API proposal done over the next week16:21
banixs3wong: great16:22
s3wongotherwise I wouldn't be able to code them anyway :-)16:22
banixWe will eventually need a central repository but that can wait for now.16:23
mesterys3wong: :)16:23
s3wongbanix: Sure16:23
alagalahCould we use a branch ?16:23
mesterybanix: Yes, it may get tricky there, we want to strike a balance on this work for sure.16:23
*** jmontemayor has joined #openstack-meeting-alt16:23
mesteryWe could use a shared github for the work initially.16:23
* alagalah unsure of protocol 16:23
alagalahmestery:  ok16:24
banixmestery: I agree16:24
s3wongmestery: are you going to set one up?16:24
mesterys3wong: sure, I can take an action item to do that!16:24
* mestery makes note of some action items now.16:24
banixor github16:24
mestery#action s3wong to work with the rest of hte PoC team to get first draft of API proposal out.16:24
mestery#action mestery to setup shared github for PoC work16:24
*** SergeyLukjanov is now known as SergeyLukjanov_16:24
*** jmcbride has quit IRC16:25
mestery#topic Open Discussion16:27
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"16:27
mesteryAnything else for this week?16:27
banixNot here16:28
s3wongall good for me16:28
alagalahI think we have our marching orders16:28
mestery:)16:28
mesteryOK, thanks folks!16:28
s3wonganother week of short meeting!16:28
mesteryLets keep the momentum going!16:28
banixthanks16:28
hemanthravithanks16:28
alagalahthanks16:28
mesterys3wong: I like short meetings :)16:28
songolethanks16:28
s3wongThanks!16:28
mestery#endmeeting16:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:29
openstackMeeting ended Thu Jan 16 16:28:59 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-01-16-16.00.html16:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-01-16-16.00.txt16:29
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-01-16-16.00.log.html16:29
*** thinrichs has quit IRC16:29
*** prasadv has quit IRC16:29
*** songole has quit IRC16:29
*** hemanthravi has quit IRC16:29
*** julienvey_ has quit IRC16:29
*** michsmit has left #openstack-meeting-alt16:30
*** SergeyLukjanov_ is now known as SergeyLukjanov16:30
*** julienvey_ has joined #openstack-meeting-alt16:32
*** bdpayne has joined #openstack-meeting-alt16:32
*** ashaikh has quit IRC16:33
*** rossella_s has joined #openstack-meeting-alt16:34
*** rsblendido has joined #openstack-meeting-alt16:34
*** aignatov has quit IRC16:36
*** jprovazn_afk is now known as jprovazn16:36
*** s3wong has quit IRC16:36
*** bill_az has quit IRC16:36
*** alagalah has left #openstack-meeting-alt16:36
*** s3wong has joined #openstack-meeting-alt16:39
*** s3wong has quit IRC16:39
*** SushilKM has joined #openstack-meeting-alt16:41
*** lblanchard1 has joined #openstack-meeting-alt16:42
*** jmcbride has joined #openstack-meeting-alt16:42
*** lblanchard has quit IRC16:43
*** mattgriffin has joined #openstack-meeting-alt16:44
*** SushilKM has left #openstack-meeting-alt16:47
*** aostapenko has left #openstack-meeting-alt16:48
*** colinmcnamara has quit IRC16:48
*** baoli has quit IRC16:51
*** NehaV has quit IRC16:51
*** NehaV has joined #openstack-meeting-alt16:52
*** rraja has quit IRC16:54
*** nam_nguyen has quit IRC16:58
*** colinmcnamara has joined #openstack-meeting-alt17:00
*** ruhe is now known as ruhe_away17:00
*** ashaikh has joined #openstack-meeting-alt17:00
*** rnirmal has joined #openstack-meeting-alt17:01
*** sarob has joined #openstack-meeting-alt17:01
*** SergeyLukjanov is now known as SergeyLukjanov_17:01
*** sarob has quit IRC17:02
*** sarob has joined #openstack-meeting-alt17:02
*** sarob has quit IRC17:04
*** sarob has joined #openstack-meeting-alt17:04
*** colinmcnamara has quit IRC17:05
*** jmcbride has quit IRC17:05
*** jmcbride has joined #openstack-meeting-alt17:05
*** rajdeep has joined #openstack-meeting-alt17:06
*** nati_ueno has joined #openstack-meeting-alt17:06
*** nati_ueno has quit IRC17:06
*** jcoufal has quit IRC17:07
*** nati_ueno has joined #openstack-meeting-alt17:08
*** NikitaKonovalov has quit IRC17:08
*** gokrokve_ has quit IRC17:09
*** nati_uen_ has quit IRC17:09
*** ruhe_away is now known as _ruhe17:10
*** markwash has quit IRC17:10
*** rajdeep has quit IRC17:10
*** nati_ueno has quit IRC17:12
*** esker has joined #openstack-meeting-alt17:12
*** esp has left #openstack-meeting-alt17:12
*** sarob has quit IRC17:14
*** gokrokve has joined #openstack-meeting-alt17:14
*** gokrokve has quit IRC17:14
*** sarob has joined #openstack-meeting-alt17:14
*** gokrokve has joined #openstack-meeting-alt17:14
*** sarob has quit IRC17:18
*** sarob has joined #openstack-meeting-alt17:19
*** SergeyLukjanov_ is now known as SergeyLukjanov17:19
*** julienvey_ has quit IRC17:20
*** michael-yu has joined #openstack-meeting-alt17:21
*** markwash has joined #openstack-meeting-alt17:23
*** nati_ueno has joined #openstack-meeting-alt17:24
*** nermina has quit IRC17:26
*** sarob has quit IRC17:27
*** sarob has joined #openstack-meeting-alt17:28
*** sarob_ has joined #openstack-meeting-alt17:30
*** jmcbride has quit IRC17:32
*** sarob has quit IRC17:33
*** colinmcnamara has joined #openstack-meeting-alt17:33
*** kebray_ has joined #openstack-meeting-alt17:34
*** nati_ueno has quit IRC17:34
*** kebray_ has quit IRC17:34
*** rakhmerov has quit IRC17:36
*** nati_ueno has joined #openstack-meeting-alt17:36
*** safchain has quit IRC17:36
*** pballand has joined #openstack-meeting-alt17:38
*** jmcbride has joined #openstack-meeting-alt17:38
*** HenryG has joined #openstack-meeting-alt17:38
*** demorris has quit IRC17:40
*** chandankumar has quit IRC17:41
*** sarob_ has quit IRC17:42
* IgorYozhikov is now away: went away...17:42
*** IgorYozhikov is now known as IYozhikov_away17:42
*** nati_ueno has quit IRC17:43
*** jmcbride has quit IRC17:43
*** luqas has quit IRC17:43
*** nati_ueno has joined #openstack-meeting-alt17:43
*** luqas has joined #openstack-meeting-alt17:44
*** michael-yu has quit IRC17:44
*** beyounn has joined #openstack-meeting-alt17:44
*** SergeyLukjanov is now known as SergeyLukjanov_17:44
*** RajeshMohan has quit IRC17:45
*** luqas has quit IRC17:46
*** RajeshMohan has joined #openstack-meeting-alt17:46
*** derekh has quit IRC17:46
*** sarob has joined #openstack-meeting-alt17:46
*** dguitarbite has quit IRC17:46
*** NehaV has quit IRC17:49
*** sarob has quit IRC17:49
*** dprince has quit IRC17:51
*** michael-yu has joined #openstack-meeting-alt17:51
*** ErikB has joined #openstack-meeting-alt17:51
*** luqas has joined #openstack-meeting-alt17:52
*** michael-yu has left #openstack-meeting-alt17:54
*** luqas has quit IRC17:54
*** funzo has quit IRC17:54
*** michael-yu has joined #openstack-meeting-alt17:54
*** aignatov has joined #openstack-meeting-alt17:54
*** d0ugal has quit IRC17:55
*** luqas has joined #openstack-meeting-alt17:55
*** sbalukoff has quit IRC17:57
*** nati_uen_ has joined #openstack-meeting-alt17:57
*** michael-yu has quit IRC17:57
*** funzo has joined #openstack-meeting-alt17:58
*** paulmo has joined #openstack-meeting-alt17:59
*** derekh has joined #openstack-meeting-alt17:59
*** jmcbride has joined #openstack-meeting-alt18:00
*** luqas has quit IRC18:00
*** jspeidel has joined #openstack-meeting-alt18:00
*** nati_ueno has quit IRC18:00
*** mattoliverau has quit IRC18:01
*** crobertsrh has joined #openstack-meeting-alt18:01
*** d0ugal has joined #openstack-meeting-alt18:02
*** d0ugal has joined #openstack-meeting-alt18:02
*** d0ugal has quit IRC18:02
*** nati_uen_ has quit IRC18:02
*** rakhmerov has joined #openstack-meeting-alt18:03
*** d0ugal has joined #openstack-meeting-alt18:03
*** d0ugal has joined #openstack-meeting-alt18:03
*** harlowja_away is now known as harlowja_18:03
*** d0ugal has quit IRC18:03
*** harlowja_ has quit IRC18:04
aignatovsavanna folks around?18:04
jspeidelyep18:04
jmaronhere18:04
*** michael-yu has joined #openstack-meeting-alt18:04
*** paulmo has left #openstack-meeting-alt18:04
*** sarob has joined #openstack-meeting-alt18:05
*** nati_ueno has joined #openstack-meeting-alt18:05
*** nati_ueno has quit IRC18:05
*** alazarev has joined #openstack-meeting-alt18:05
ErikBHi Everyone18:05
*** dprince has joined #openstack-meeting-alt18:06
aignatovhi all18:06
aignatovok, let's start18:06
aignatov#startmeeting savanna18:06
openstackMeeting started Thu Jan 16 18:06:28 2014 UTC and is due to finish in 60 minutes.  The chair is aignatov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:06
*** openstack changes topic to " (Meeting topic: savanna)"18:06
openstackThe meeting name has been set to 'savanna'18:06
*** d0ugal has joined #openstack-meeting-alt18:06
*** d0ugal has joined #openstack-meeting-alt18:06
*** d0ugal has quit IRC18:06
aignatov#topic Agenda18:06
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:06
aignatov#link https://wiki.openstack.org/wiki/Meetings/SavannaAgenda18:07
*** d0ugal has joined #openstack-meeting-alt18:07
*** d0ugal has joined #openstack-meeting-alt18:07
*** d0ugal has quit IRC18:07
aignatov#topic Action items from the last meeting18:07
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"18:07
aignatovok, I see from the previous aid were on Sergey18:07
aignatovlets mov them as new AIs :)18:07
*** derekh has quit IRC18:08
*** mattf has joined #openstack-meeting-alt18:08
aignatovbtw, he was on PTLs webinar today and gave talk about savanna to the community18:08
aignatov#action SergeyLukjanov to check that all blueprints created and ping guys to make them if not18:08
aignatov#action SergeyLukjanov add links to the blueprints to roadmap18:08
aignatov#topic News / updates18:09
*** openstack changes topic to "News / updates (Meeting topic: savanna)"18:09
aignatovguys please18:09
*** d0ugal has joined #openstack-meeting-alt18:09
*** d0ugal has joined #openstack-meeting-alt18:09
*** vipul is now known as vipul-away18:09
*** vipul-away is now known as vipul18:09
mattfso the cli is coming along. i took a break to look at the rest api itself.18:09
*** shashank_ has joined #openstack-meeting-alt18:09
mattfi posed many comments to the wiki and mailing list.18:09
mattfthanks aignatov for feedback so far18:09
*** sarob has quit IRC18:10
jmaronmy EDP on neutron private networks patch update is hung up while we rebuild our in-house neutron env.  Apologies for the delay18:10
mattfi'd like feedback from jmaron jspeidel too before drafting the v2 api18:10
jmaronwill do18:10
jspeidelmattf - sure thing18:10
mattfjmaron, you too? i'm trying to do neutron atm too!18:10
ErikB On the hortonworks side, we're working a few things around providing HDP2 support and adding native support in Ambari for Blueprints which we will eventually leverage in Savanna HDP plugin18:10
*** luqas has joined #openstack-meeting-alt18:10
aignatovmattf, you did bread job and some useful ideas - move jobs and job_executions to jobs and job_templates is very good!18:10
aignatovbread -> great :)18:10
mattfthat rename is the least of it!18:11
aignatovErikB: nice to hear that!18:11
mattfit looks like the api doc will need to be updated too, it wasn't always consistent w/ the code18:11
aignatovbtw, who has not undated bps you are working on, please do this :)18:11
jspeidelmattf, if you know of specifics please file bugs18:11
mattfjspeidel, ack18:12
jmaronjust so I'm certain I'm reviewing the correct doc/wiki - what's the link?18:12
aignatovmattf, api should be updated, right! the last update was EDP section18:12
mattfaignatov, there was a topic for the meeting that i mentioned to sergey and have since forgotten. he send you any notes?18:12
aignatovmattf, sorry, but i didn't hear these notes18:13
*** d0ugal has joined #openstack-meeting-alt18:14
*** d0ugal has joined #openstack-meeting-alt18:14
*** d0ugal has quit IRC18:14
*** harlowja has joined #openstack-meeting-alt18:14
aignatovmaybe we can discuss it on the General discussion section18:14
mattfaignatov, fyi, there was an AI on me about oslo sync. i looked into it and decided to skip until after the release.18:14
*** gokrokve has quit IRC18:14
*** Duane has joined #openstack-meeting-alt18:14
*** d0ugal has joined #openstack-meeting-alt18:14
*** mattoliverau has joined #openstack-meeting-alt18:14
*** gokrokve has joined #openstack-meeting-alt18:14
aignatovmattf, agree, please make action tag and title in this meeting :)18:15
*** arnaud__ has joined #openstack-meeting-alt18:15
*** arnaud___ has joined #openstack-meeting-alt18:15
aignatovupdate from me: i'm finishing work on entegration savanna with heat provisioning feature, the latests bug fixes on the review18:16
alazarevfrom my side: IDH is partially merged, several parts are still on review18:16
aignatovaction on me18:16
* mattf found the general topic: if we should both w/ --name in the cli (we have --id and the api works primarily w/ ids)18:16
aignatov#action create doc about features included into savanna's heat engine18:16
*** shamail has joined #openstack-meeting-alt18:16
alazarevSergey Reshetnyak is working on adding IDH to CI18:17
*** d0ugal has joined #openstack-meeting-alt18:17
*** d0ugal has joined #openstack-meeting-alt18:17
aignatovmatte, +1, it should be added18:17
jspeidelmattf, I like being able to use the name in the cli18:17
*** arnaud___ has quit IRC18:17
*** arnaud__ has quit IRC18:17
mattflet's wait til general discussion18:17
jspeidelmattf, avoids unnecessary query to get the id using the name18:17
aignatovany other updates?18:18
*** arnaud__ has joined #openstack-meeting-alt18:18
alazarevmattf: +1 on names18:18
*** arnaud___ has joined #openstack-meeting-alt18:18
aignatovcrobertsrh, any updates? :)18:18
*** d0ugal has joined #openstack-meeting-alt18:18
crobertsrhGot the review up for Oozie Java Actions in the UI.18:18
crobertsrhNext up looks like HDFS data sources18:19
*** jmcbride has quit IRC18:19
aignatovcrobertsrh: great!18:19
aignatovlets move on18:19
*** d0ugal has quit IRC18:19
aignatov#topic Roadmap update/cleanup18:19
*** openstack changes topic to "Roadmap update/cleanup (Meeting topic: savanna)"18:19
*** yogesh has joined #openstack-meeting-alt18:19
aignatovaction above is still on the Sergey18:19
*** shamail has quit IRC18:19
*** gokrokve has quit IRC18:19
aignatov#topic General discussion18:19
*** openstack changes topic to "General discussion (Meeting topic: savanna)"18:19
*** Duane_ has joined #openstack-meeting-alt18:19
mattfshould have --name (in addition to --id) for cli commands, i.e. cluster-show --name cluster0 (instead of --id 28ee3cff-9f43-4c03-91e2-06467e15a6d7). if we should then we either have to implement in the client library or in the service api.18:20
alazarevsmall update from Intel side: their "dedicated" engineer is working on urgent project, going to start working on savanna in a week or two18:20
mattfbtw, that's should we have, just c&p from irc logs18:20
jmaronmattf, just so I'm certain I'm reviewing the correct doc/wiki - what's the link?18:20
aignatovmattf, afaik, openstack approach is to use both ids and names18:21
*** gokrokve has joined #openstack-meeting-alt18:21
*** d0ugal has joined #openstack-meeting-alt18:21
*** d0ugal has joined #openstack-meeting-alt18:21
mattfjmaron, https://blueprints.launchpad.net/savanna/+spec/v2-api and the email on openstack-dev18:21
jmaronthx18:21
*** d0ugal has joined #openstack-meeting-alt18:22
*** d0ugal has joined #openstack-meeting-alt18:22
*** d0ugal has quit IRC18:22
aignatov#link https://blueprints.launchpad.net/savanna/+spec/v2-api18:22
mattfi like names too. sounds like we have some consensus there.18:22
*** d0ugal has joined #openstack-meeting-alt18:22
aignatovmaybe let's vote?18:22
jspeidelmattf, +1 for names18:22
mattfthe issue is the rest api does not allow for lookup by name. so either we add that to the rest api, or we add the functionality to the python api. the python api would have to list + search + query.18:22
alazarevaignatov: who is against?18:22
mattfalazarev, lol, nice approach18:23
jspeidelmattf, rest api should also support18:23
*** sreshetnyak has joined #openstack-meeting-alt18:23
*** Duane has quit IRC18:23
jmaronjspeidel +118:23
mattfanyone know if it is common or not to have the name->id logic in the client or the api?18:24
alazarevmattf: +1 on having names in rest too18:24
aignatovit's just to be documented :) ok, we are all think the same about new rest18:24
*** d0ugal has joined #openstack-meeting-alt18:24
*** d0ugal has joined #openstack-meeting-alt18:24
*** d0ugal has joined #openstack-meeting-alt18:24
*** d0ugal has quit IRC18:24
*** vipul is now known as vipul-away18:25
aignatovErikB: will you continue working on edp over private networks and base support?18:25
*** _ruhe is now known as ruhe18:25
aignatov*hbase18:25
mattfsilence me no knows if it's more common to impl in api or in client?18:25
jspeidelmattf, rest api should only have a single primary id per resource but should allow queries by name also18:25
jspeidelmattf, I assume that id is the primary key for the resource18:26
*** d0ugal has joined #openstack-meeting-alt18:26
*** d0ugal has joined #openstack-meeting-alt18:26
*** d0ugal has quit IRC18:26
*** jasonb365 has joined #openstack-meeting-alt18:26
aignatovmattf, I think it should be in the api side18:26
ErikBaignatov, yes this work will continue, we still need to do some more functional testing18:26
*** gokrokve has quit IRC18:26
mattfi'll take an AI to look into adding names, and hopefully integrate it into the v2 api spec.18:27
*** gokrokve has joined #openstack-meeting-alt18:27
mattfso far the vocal folks say +1 name and +1 add to api (not just to client)18:27
*** d0ugal has joined #openstack-meeting-alt18:27
*** d0ugal has joined #openstack-meeting-alt18:27
*** d0ugal has quit IRC18:27
aignatovmattf, I think it's too much stuff in the single blueprint. Maybe we should divide it into some small bps?18:28
*** bdpayne_ has joined #openstack-meeting-alt18:28
mattfaignatov, i'd like to keep it all in one place for now18:28
*** nikhil has joined #openstack-meeting-alt18:28
mattfwe can break it up later when some impl starts18:28
aignatovok, sounds reasonable18:29
*** jasonb365 has quit IRC18:29
*** jasonb365 has joined #openstack-meeting-alt18:29
*** nikhil is now known as kin_18:29
*** bdpayne has quit IRC18:29
*** BrianB_ has quit IRC18:30
*** d0ugal has joined #openstack-meeting-alt18:30
*** pdmars has quit IRC18:30
*** d0ugal has joined #openstack-meeting-alt18:31
*** d0ugal has joined #openstack-meeting-alt18:31
*** d0ugal has quit IRC18:31
aignatovoh, one more update, Yaroslav updated bp to make HDP working over Heat, jspeidel and jmaron, please take a look on it ;)18:31
*** pdmars has joined #openstack-meeting-alt18:31
*** gokrokve has quit IRC18:31
*** bdpayne_ has quit IRC18:31
aignatov#link https://review.openstack.org/#/c/65911/18:32
*** colinmcnamara has quit IRC18:32
*** bdpayne has joined #openstack-meeting-alt18:32
*** d0ugal has joined #openstack-meeting-alt18:32
*** d0ugal has joined #openstack-meeting-alt18:32
*** d0ugal has joined #openstack-meeting-alt18:32
jmaronaignatov:  ok18:32
aignatovthan we will enable gate job for that as voting18:33
jspeidelaignatov, how is this related to #link https://review.openstack.org/#/c/65981/18:33
jspeidel?18:33
*** pdmars has quit IRC18:33
*** pdmars has joined #openstack-meeting-alt18:33
aignatovjspeidel: sorry, the proper, I mean the https://review.openstack.org/#/c/65981/18:33
jspeidelaignatov,ok.  I have already been involved in reviewing this18:34
*** pdmars_ has joined #openstack-meeting-alt18:34
aignatovand my first link is about enabling hdp integration tests working over heat18:34
jspeidelaignatov *nods*18:35
*** pdmars_ has quit IRC18:35
aignatov:)18:35
aignatovguys, do we have anything else to discuss?18:36
mattfnothing from me18:36
jspeidelnot me either18:36
alazarevnot from me18:36
jspeideloh18:36
*** d0ugal has joined #openstack-meeting-alt18:36
*** d0ugal has joined #openstack-meeting-alt18:36
*** d0ugal has quit IRC18:36
jspeidelwhere are we in regards to hbase discussions with community?18:37
mattfafaik that still lives w/ sergey18:37
mattfi missed the update webcast today, maybe it was covered there18:37
*** pdmars has quit IRC18:37
jspeidelwould be nice to get an updated status on this18:38
mattfactually, did anyone attend? can you give us a quick summary?18:38
*** pdmars has joined #openstack-meeting-alt18:38
aignatovjspeidel: I only know that you can continue working on your patch, please talk with Sergey directly about that :)18:38
jspeidelaignatov, ok.  Will ping Sergey18:39
aignatovmatff, as I know alazarev was there18:39
aignatovI was moving to home from work at that time :)18:39
*** pdmars_ has joined #openstack-meeting-alt18:39
alazarevjust updates from savanna and trove18:40
aignatovhow many people were there?18:40
*** pdmars_ has quit IRC18:40
*** jcoufal has joined #openstack-meeting-alt18:40
alazarevmattf: are you interested in something particular?18:40
mattfjust general summary. i'll just go get the recording. thanks.18:41
*** harlowja_ has joined #openstack-meeting-alt18:41
*** harlowja has quit IRC18:41
ErikBBTW - is there a page that describes the icehouse-3 milestone?18:41
*** nati_ueno has joined #openstack-meeting-alt18:42
aignatovErikB: there is no actual page in wiki18:42
aignatovbut this can help you18:42
aignatov#link https://launchpad.net/savanna/+milestone/icehouse-318:42
*** NikitaKonovalov has joined #openstack-meeting-alt18:42
*** pdmars has quit IRC18:42
ErikBaignatiov, thanks!18:43
aignatovall unfinished bugs and bp in icehouse-2 will be moved to icehouse-3 as well18:43
*** pdmars has joined #openstack-meeting-alt18:43
aignatovicehouse-2 release date is on Jan 2318:44
aignatovuseful link18:44
aignatov#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule18:44
*** markwash has quit IRC18:44
*** safchain has joined #openstack-meeting-alt18:44
*** pdmars has quit IRC18:44
*** harlowja has joined #openstack-meeting-alt18:45
*** ruhe is now known as ruhe_away18:45
aignatovok, I think we can finish this meeting18:45
*** tmckay has joined #openstack-meeting-alt18:45
aignatovthanks who's joined, have a nice day!18:45
aignatov#endmeeting18:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:45
openstackMeeting ended Thu Jan 16 18:45:44 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-01-16-18.06.html18:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-01-16-18.06.txt18:45
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-01-16-18.06.log.html18:45
*** jspeidel has left #openstack-meeting-alt18:45
*** jmaron has left #openstack-meeting-alt18:46
*** harlowja_ has quit IRC18:46
*** markwash has joined #openstack-meeting-alt18:46
*** IlyaE has quit IRC18:46
*** pdmars has joined #openstack-meeting-alt18:47
*** NikitaKonovalov has quit IRC18:47
*** ruhe_away is now known as ruhe18:48
*** nati_ueno has quit IRC18:48
*** pdmars has quit IRC18:48
*** pdmars has joined #openstack-meeting-alt18:49
*** nati_ueno has joined #openstack-meeting-alt18:49
*** pdmars has quit IRC18:49
*** NikitaKonovalov has joined #openstack-meeting-alt18:50
*** pdmars has joined #openstack-meeting-alt18:50
*** vipul-away is now known as vipul18:50
*** Duane has joined #openstack-meeting-alt18:51
*** pdmars has quit IRC18:51
*** pdmars has joined #openstack-meeting-alt18:51
*** pdmars has quit IRC18:52
*** pdmars has joined #openstack-meeting-alt18:53
*** pdmars has quit IRC18:54
*** crobertsrh has left #openstack-meeting-alt18:54
*** Duane_ has quit IRC18:54
*** coolsvap has quit IRC18:54
*** pdmars has joined #openstack-meeting-alt18:55
*** NikitaKonovalov has quit IRC18:56
*** pdmars has quit IRC18:56
*** markwash has quit IRC18:56
*** pdmars has joined #openstack-meeting-alt18:56
*** pdmars has quit IRC18:57
*** pdmars has joined #openstack-meeting-alt18:59
*** bdpayne has quit IRC19:00
*** pdmars has quit IRC19:00
*** markwash has joined #openstack-meeting-alt19:00
*** NikitaKonovalov has joined #openstack-meeting-alt19:00
*** mattf has left #openstack-meeting-alt19:00
*** sbalukoff has joined #openstack-meeting-alt19:00
*** pdmars has joined #openstack-meeting-alt19:00
*** luqas has quit IRC19:01
*** bdpayne has joined #openstack-meeting-alt19:01
*** pdmars has quit IRC19:01
*** luqas has joined #openstack-meeting-alt19:02
*** hartsocks has joined #openstack-meeting-alt19:02
*** jprovazn has quit IRC19:02
*** SergeyLukjanov_ is now known as SergeyLukjanov19:03
*** colinmcnamara has joined #openstack-meeting-alt19:03
*** derekh has joined #openstack-meeting-alt19:03
*** pdmars has joined #openstack-meeting-alt19:04
*** NikitaKonovalov has quit IRC19:05
*** ErikB has quit IRC19:05
*** pdmars has quit IRC19:05
*** vipul is now known as vipul-away19:05
*** pdmars has joined #openstack-meeting-alt19:05
*** pdmars has quit IRC19:07
*** NikitaKonovalov has joined #openstack-meeting-alt19:07
*** nermina has joined #openstack-meeting-alt19:08
*** pdmars has joined #openstack-meeting-alt19:08
*** jtomasek has quit IRC19:08
*** pdmars has quit IRC19:09
*** pdmars has joined #openstack-meeting-alt19:09
*** pdmars_ has joined #openstack-meeting-alt19:11
*** NikitaKonovalov has quit IRC19:11
*** pdmars_ has quit IRC19:11
*** jecarey has quit IRC19:12
*** pdmars_ has joined #openstack-meeting-alt19:12
*** alazarev has quit IRC19:12
*** NikitaKonovalov has joined #openstack-meeting-alt19:12
*** pdmars_ has quit IRC19:13
*** pdmars_ has joined #openstack-meeting-alt19:13
*** pdmars has quit IRC19:14
*** pdmars_ has quit IRC19:14
*** d0ugal has joined #openstack-meeting-alt19:14
*** d0ugal has joined #openstack-meeting-alt19:16
*** d0ugal has joined #openstack-meeting-alt19:16
*** d0ugal has quit IRC19:16
*** pdmars has joined #openstack-meeting-alt19:16
*** NikitaKonovalov has quit IRC19:16
*** d0ugal has joined #openstack-meeting-alt19:16
*** d0ugal has joined #openstack-meeting-alt19:16
*** luqas has quit IRC19:16
*** pdmars has quit IRC19:17
*** IlyaE has joined #openstack-meeting-alt19:17
*** d0ugal has joined #openstack-meeting-alt19:17
*** d0ugal has joined #openstack-meeting-alt19:17
*** d0ugal has quit IRC19:17
*** NikitaKonovalov has joined #openstack-meeting-alt19:18
*** d0ugal has joined #openstack-meeting-alt19:18
*** d0ugal has joined #openstack-meeting-alt19:18
*** d0ugal has quit IRC19:18
*** luqas has joined #openstack-meeting-alt19:18
*** d0ugal has joined #openstack-meeting-alt19:19
*** d0ugal has joined #openstack-meeting-alt19:19
*** d0ugal has quit IRC19:19
*** d0ugal has joined #openstack-meeting-alt19:20
*** d0ugal has joined #openstack-meeting-alt19:20
*** d0ugal has joined #openstack-meeting-alt19:20
*** d0ugal has joined #openstack-meeting-alt19:20
*** d0ugal has quit IRC19:20
*** d0ugal has joined #openstack-meeting-alt19:21
*** d0ugal has joined #openstack-meeting-alt19:21
*** pdmars has joined #openstack-meeting-alt19:21
*** NikitaKonovalov has quit IRC19:22
*** mattgriffin has quit IRC19:22
*** pdmars has quit IRC19:22
*** NikitaKonovalov has joined #openstack-meeting-alt19:23
*** luqas has quit IRC19:23
*** esker has quit IRC19:24
*** d0ugal has joined #openstack-meeting-alt19:24
*** d0ugal has quit IRC19:24
*** pdmars has joined #openstack-meeting-alt19:26
*** harlowja has quit IRC19:26
*** resker has joined #openstack-meeting-alt19:26
*** pdmars has quit IRC19:27
*** pdmars has joined #openstack-meeting-alt19:29
*** pdmars has quit IRC19:30
*** NikitaKonovalov has quit IRC19:30
*** harlowja has joined #openstack-meeting-alt19:31
*** pdmars has joined #openstack-meeting-alt19:31
*** pdmars has quit IRC19:32
*** pdmars has joined #openstack-meeting-alt19:32
*** ErikB has joined #openstack-meeting-alt19:32
*** derekh has quit IRC19:34
*** NikitaKonovalov has joined #openstack-meeting-alt19:35
*** jecarey has joined #openstack-meeting-alt19:35
*** nati_uen_ has joined #openstack-meeting-alt19:37
*** nati_uen_ has quit IRC19:38
*** kebray_ has joined #openstack-meeting-alt19:38
*** nati_uen_ has joined #openstack-meeting-alt19:39
*** jmcbride has joined #openstack-meeting-alt19:39
*** NikitaKonovalov has quit IRC19:39
*** NikitaKonovalov has joined #openstack-meeting-alt19:41
*** nati_ueno has quit IRC19:41
*** ErikB has quit IRC19:45
*** gokrokve has joined #openstack-meeting-alt19:48
*** NikitaKonovalov has quit IRC19:52
*** Duane has quit IRC19:54
*** vipul-away is now known as vipul19:54
*** Duane has joined #openstack-meeting-alt19:54
*** NikitaKonovalov has joined #openstack-meeting-alt19:57
*** alazarev has joined #openstack-meeting-alt19:58
*** kebray_ has quit IRC19:58
*** Duane has quit IRC19:58
*** resker has quit IRC20:01
*** NikitaKonovalov has quit IRC20:02
*** esker has joined #openstack-meeting-alt20:02
*** NikitaKonovalov has joined #openstack-meeting-alt20:02
*** mattgriffin has joined #openstack-meeting-alt20:06
*** mattgriffin has quit IRC20:06
*** mattgriffin has joined #openstack-meeting-alt20:06
*** esker has quit IRC20:06
*** luqas has joined #openstack-meeting-alt20:09
*** nati_ueno has joined #openstack-meeting-alt20:11
*** jmcbride has quit IRC20:13
*** krtaylor has quit IRC20:14
*** nati_uen_ has quit IRC20:15
*** nati_ueno has quit IRC20:15
*** colinmcnamara has quit IRC20:16
*** NikitaKonovalov has quit IRC20:19
*** NikitaKonovalov has joined #openstack-meeting-alt20:24
*** jmcbride has joined #openstack-meeting-alt20:26
*** Barker has quit IRC20:26
*** Barker has joined #openstack-meeting-alt20:27
*** alazarev has quit IRC20:31
*** colinmcnamara has joined #openstack-meeting-alt20:39
*** sarob has joined #openstack-meeting-alt20:42
*** michael-yu has quit IRC20:42
*** luqas has quit IRC20:49
*** luqas has joined #openstack-meeting-alt20:50
*** jmontemayor has quit IRC20:52
*** yamahata has quit IRC20:52
*** michael-yu has joined #openstack-meeting-alt20:53
*** luqas has quit IRC20:53
*** jmcbride has quit IRC20:55
*** denis_makogon_ has joined #openstack-meeting-alt20:56
*** michael-yu has quit IRC20:57
*** michael-yu has joined #openstack-meeting-alt20:58
*** denis_makogon has quit IRC21:04
*** denis_makogon_ is now known as denis_makogon21:04
*** dmakogon_ has joined #openstack-meeting-alt21:05
*** obondarev_ has quit IRC21:05
*** vipul is now known as vipul-away21:05
*** jmcbride has joined #openstack-meeting-alt21:06
*** krtaylor has joined #openstack-meeting-alt21:07
*** michael-yu has quit IRC21:07
*** michael-yu has joined #openstack-meeting-alt21:08
*** vipul-away is now known as vipul21:09
*** beyounn has quit IRC21:09
*** dprince has quit IRC21:09
*** yamahata has joined #openstack-meeting-alt21:13
*** jcoufal has quit IRC21:15
*** NikitaKonovalov has quit IRC21:16
*** Duane has joined #openstack-meeting-alt21:17
*** sarob has quit IRC21:21
*** pnavarro__ has quit IRC21:21
*** sarob has joined #openstack-meeting-alt21:22
*** sarob has quit IRC21:26
*** Duane_ has joined #openstack-meeting-alt21:26
*** Duane has quit IRC21:29
*** julim has quit IRC21:30
*** jcoufal has joined #openstack-meeting-alt21:31
*** obondarev_ has joined #openstack-meeting-alt21:31
*** michael-yu has quit IRC21:32
*** harlowja has quit IRC21:32
*** sarob has joined #openstack-meeting-alt21:35
*** michael-yu has joined #openstack-meeting-alt21:39
*** dianefleming has quit IRC21:40
*** Duane has joined #openstack-meeting-alt21:43
*** Duane has quit IRC21:45
*** Duane_ has quit IRC21:47
*** luqas has joined #openstack-meeting-alt21:57
*** alazarev has joined #openstack-meeting-alt21:58
*** harlowja has joined #openstack-meeting-alt21:59
*** harlowja has quit IRC21:59
*** harlowja has joined #openstack-meeting-alt21:59
*** aignatov has quit IRC21:59
*** aignatov has joined #openstack-meeting-alt22:00
*** aignatov has quit IRC22:01
*** aignatov has joined #openstack-meeting-alt22:01
*** jcoufal has quit IRC22:03
*** beyounn has joined #openstack-meeting-alt22:03
*** nati_ueno has joined #openstack-meeting-alt22:04
*** aignatov_ has quit IRC22:04
*** jdob has quit IRC22:05
*** ruhe is now known as _ruhe22:06
*** SergeyLukjanov is now known as SergeyLukjanov_a22:09
*** SergeyLukjanov_a is now known as SergeyLukjanov_22:10
*** MarkAtwood has joined #openstack-meeting-alt22:10
*** aignatov has quit IRC22:10
*** nati_ueno has quit IRC22:13
*** vipul is now known as vipul-away22:13
*** vipul-away is now known as vipul22:13
*** hartsocks has quit IRC22:13
*** sarob has quit IRC22:14
*** nati_ueno has joined #openstack-meeting-alt22:14
*** sarob has joined #openstack-meeting-alt22:14
*** luqas has quit IRC22:17
*** pdmars has quit IRC22:18
*** jaypipes has quit IRC22:21
*** lblanchard1 has quit IRC22:24
*** HenryG has quit IRC22:26
*** vipul is now known as vipul-away22:29
*** sreshetnyak has quit IRC22:31
*** tmckay has left #openstack-meeting-alt22:31
*** esker has joined #openstack-meeting-alt22:31
*** esker has quit IRC22:36
*** esker has joined #openstack-meeting-alt22:36
*** Barker has quit IRC22:37
*** sarob has quit IRC22:41
*** sarob has joined #openstack-meeting-alt22:42
*** nermina has quit IRC22:44
*** denis_makogon has quit IRC22:44
*** mattgriffin has quit IRC22:45
*** kevinconway has quit IRC22:45
*** sarob has quit IRC22:46
*** amytron has quit IRC22:48
*** banix has quit IRC22:48
*** vipul-away is now known as vipul22:48
*** obondarev_ has quit IRC22:56
*** simonmcc has quit IRC23:00
*** NehaV has joined #openstack-meeting-alt23:00
*** jmcbride has quit IRC23:00
*** safchain has quit IRC23:01
*** safchain has joined #openstack-meeting-alt23:01
*** safchain has quit IRC23:02
*** safchain has joined #openstack-meeting-alt23:02
*** nati_uen_ has joined #openstack-meeting-alt23:02
*** safchain has quit IRC23:02
*** safchain has joined #openstack-meeting-alt23:03
*** safchain has quit IRC23:03
*** safchain has joined #openstack-meeting-alt23:03
*** safchain has quit IRC23:04
*** safchain has joined #openstack-meeting-alt23:04
*** safchain has quit IRC23:04
*** safchain has joined #openstack-meeting-alt23:05
*** safchain has quit IRC23:05
*** safchain has joined #openstack-meeting-alt23:05
*** nati_ueno has quit IRC23:06
*** jecarey has quit IRC23:10
*** julienvey_ has joined #openstack-meeting-alt23:12
*** julienvey_ has quit IRC23:14
*** sarob has joined #openstack-meeting-alt23:16
*** flaper87 is now known as flaper87|afk23:19
*** rsblendido has quit IRC23:19
*** rossella_s has quit IRC23:19
*** ijw_ has joined #openstack-meeting-alt23:22
*** ijw has quit IRC23:22
*** eharney has quit IRC23:23
*** NehaV has quit IRC23:25
*** gokrokve has quit IRC23:26
*** sarob has quit IRC23:26
*** gokrokve has joined #openstack-meeting-alt23:26
*** gokrokve has quit IRC23:30
*** mattgriffin has joined #openstack-meeting-alt23:32
*** mattgriffin has quit IRC23:36
*** yogesh has quit IRC23:37
*** jasonb365 has quit IRC23:39
*** safchain has quit IRC23:41
*** NehaV has joined #openstack-meeting-alt23:44
*** michael-yu has quit IRC23:46
*** nati_ueno has joined #openstack-meeting-alt23:50
*** nati_ueno has quit IRC23:51
*** nati_ueno has joined #openstack-meeting-alt23:52
*** krtaylor has quit IRC23:52
*** nati_uen_ has quit IRC23:53
*** Leonr has quit IRC23:53
*** vipul is now known as vipul-away23:55
*** michael-yu has joined #openstack-meeting-alt23:58
*** michael-yu has quit IRC23:58

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