Thursday, 2014-01-23

*** sarob has quit IRC00:00
*** sarob has joined #openstack-meeting-alt00:00
*** flaper87 is now known as flaper87|afk00:01
*** tanisdl has quit IRC00:04
*** sarob has quit IRC00:05
*** Barker has quit IRC00:08
*** banix has quit IRC00:21
*** pdmars has quit IRC00:23
*** rnirmal has quit IRC00:24
*** Duane_ has joined #openstack-meeting-alt00:32
*** Duane_ has quit IRC00:37
*** Duane_ has joined #openstack-meeting-alt00:44
*** michael-yu has quit IRC00:52
*** Ranjitha has quit IRC00:52
*** saurabhs has left #openstack-meeting-alt00:57
*** banix has joined #openstack-meeting-alt00:59
*** julim has quit IRC01:04
*** Duane_ has quit IRC01:04
*** Duane_ has joined #openstack-meeting-alt01:05
*** julim has joined #openstack-meeting-alt01:07
*** Duane_ has quit IRC01:09
*** yogesh has joined #openstack-meeting-alt01:10
*** vipul is now known as vipul-away01:14
*** yogesh has quit IRC01:27
*** vipul-away is now known as vipul01:29
*** amcrn has quit IRC01:33
*** nosnos has joined #openstack-meeting-alt01:34
*** michael-yu has joined #openstack-meeting-alt01:40
*** ViswaV has quit IRC01:44
*** michael-yu has quit IRC01:46
*** grapex has quit IRC01:48
*** gokrokve has quit IRC02:07
*** gokrokve has joined #openstack-meeting-alt02:07
*** gokrokve has quit IRC02:12
*** coolsvap has quit IRC02:21
*** coolsvap has joined #openstack-meeting-alt02:24
*** rakhmerov has quit IRC02:30
*** demorris has joined #openstack-meeting-alt02:31
*** julim has quit IRC02:35
*** Duane_ has joined #openstack-meeting-alt02:35
*** coolsvap has quit IRC02:37
*** Duane_ has quit IRC02:39
*** demorris has quit IRC02:40
*** Barker has joined #openstack-meeting-alt02:45
*** richm has quit IRC02:48
*** eankutse has joined #openstack-meeting-alt02:48
*** gokrokve has joined #openstack-meeting-alt02:51
*** michael-yu has joined #openstack-meeting-alt02:53
*** eankutse has quit IRC02:56
*** Duane_ has joined #openstack-meeting-alt02:57
*** sballe_ has quit IRC02:59
*** dguitarbite has joined #openstack-meeting-alt02:59
*** sballe_ has joined #openstack-meeting-alt03:00
*** Duane_ has quit IRC03:04
*** Duane_ has joined #openstack-meeting-alt03:05
*** sballe_ has quit IRC03:08
*** dguitarbite has quit IRC03:09
*** Duane_ has quit IRC03:10
*** nati_ueno has quit IRC03:10
*** michael-yu has quit IRC03:13
*** gokrokve has quit IRC03:17
*** sacharya has joined #openstack-meeting-alt03:20
*** doug_shelley66 has quit IRC03:29
*** cody-somerville has quit IRC03:35
*** dguitarbite has joined #openstack-meeting-alt03:41
*** eankutse has joined #openstack-meeting-alt03:44
*** arnaud__ has quit IRC03:44
*** arnaud has quit IRC03:45
*** eankutse has quit IRC03:47
*** gokrokve has joined #openstack-meeting-alt03:49
*** cody-somerville has joined #openstack-meeting-alt03:51
*** yamahata has joined #openstack-meeting-alt04:08
*** harlowja is now known as harlowja_away04:23
*** balajiiyer has joined #openstack-meeting-alt04:24
*** balajiiyer has left #openstack-meeting-alt04:25
*** chadlung has quit IRC04:28
*** aignatov_ is now known as aignatov04:29
*** michael-yu has joined #openstack-meeting-alt04:42
*** markwash_ has joined #openstack-meeting-alt04:43
*** markwash has quit IRC04:43
*** markwash_ is now known as markwash04:43
*** colinmcnamara has joined #openstack-meeting-alt04:45
*** Duane_ has joined #openstack-meeting-alt04:46
*** Duane_ has quit IRC04:51
*** colinmcnamara has quit IRC04:52
*** akuznetsov has joined #openstack-meeting-alt04:56
*** aignatov is now known as aignatov_04:56
*** yamahata has quit IRC04:57
*** nati_ueno has joined #openstack-meeting-alt05:03
*** nati_uen_ has joined #openstack-meeting-alt05:05
*** sbalukoff has quit IRC05:06
*** nati_ueno has quit IRC05:08
*** rakhmerov has joined #openstack-meeting-alt05:09
*** sbalukoff has joined #openstack-meeting-alt05:10
*** harlowja_away is now known as harlowja05:10
*** gokrokve has quit IRC05:14
*** yamahata has joined #openstack-meeting-alt05:20
*** pballand has quit IRC05:34
*** pballand has joined #openstack-meeting-alt05:36
*** pballand has quit IRC05:39
*** nadya__ has joined #openstack-meeting-alt05:40
*** coolsvap has joined #openstack-meeting-alt05:41
*** nadya__ has quit IRC05:44
*** gokrokve has joined #openstack-meeting-alt05:45
*** SergeyLukjanov_ is now known as SergeyLukjanov05:46
*** yogesh has joined #openstack-meeting-alt05:46
*** Barker has quit IRC05:46
*** SergeyLukjanov is now known as SergeyLukjanov_05:49
*** nati_ueno has joined #openstack-meeting-alt05:53
*** nati_ueno has quit IRC05:53
*** nati_ueno has joined #openstack-meeting-alt05:54
*** nati_uen_ has quit IRC05:56
*** banix has quit IRC06:03
*** mattgriffin has quit IRC06:18
*** nadya__ has joined #openstack-meeting-alt06:18
*** mattgriffin has joined #openstack-meeting-alt06:19
*** Ranjitha has joined #openstack-meeting-alt06:24
*** sacharya has quit IRC06:25
*** akuznetsov has quit IRC06:27
*** nadya__ has quit IRC06:27
*** yogesh has quit IRC06:27
*** RobinWang has joined #openstack-meeting-alt06:28
*** yogesh has joined #openstack-meeting-alt06:29
*** akuznetsov has joined #openstack-meeting-alt06:31
*** arborism has joined #openstack-meeting-alt06:31
*** yogesh has quit IRC06:33
*** Ranjitha_ has joined #openstack-meeting-alt06:33
*** Ranjitha has quit IRC06:34
*** Ranjitha_ is now known as Ranjitha06:34
*** Duane_ has joined #openstack-meeting-alt06:35
*** yogesh has joined #openstack-meeting-alt06:39
*** Duane_ has quit IRC06:40
*** yogesh_ has joined #openstack-meeting-alt06:42
*** arborism is now known as amcrn06:44
*** harlowja is now known as harlowja_away06:45
*** yogesh__ has joined #openstack-meeting-alt06:45
*** yogesh has quit IRC06:46
*** yogesh_ has quit IRC06:48
*** nati_uen_ has joined #openstack-meeting-alt06:48
*** nati_ueno has quit IRC06:51
*** nadya__ has joined #openstack-meeting-alt06:57
*** michael-yu has quit IRC06:58
*** michael-yu has joined #openstack-meeting-alt07:02
*** nadya__ has quit IRC07:03
*** gokrokve has quit IRC07:11
*** rakhmerov has quit IRC07:12
*** amcrn has quit IRC07:15
*** gokrokve has joined #openstack-meeting-alt07:18
*** gokrokve has quit IRC07:22
*** amotoki has joined #openstack-meeting-alt07:30
*** nadya__ has joined #openstack-meeting-alt07:30
*** nwidell has joined #openstack-meeting-alt07:31
*** nwidell has quit IRC07:34
*** nadya__ has quit IRC07:35
*** mattgriffin has quit IRC07:36
*** amcrn has joined #openstack-meeting-alt07:37
*** boris-42 has quit IRC07:41
*** gokrokve has joined #openstack-meeting-alt07:41
*** nati_ueno has joined #openstack-meeting-alt07:42
*** nati_uen_ has quit IRC07:46
*** yamahata has quit IRC07:46
*** gokrokve has quit IRC07:46
*** gokrokve has joined #openstack-meeting-alt07:47
*** RobinWang has quit IRC08:00
*** yamahata has joined #openstack-meeting-alt08:02
*** jcoufal has joined #openstack-meeting-alt08:08
*** julienvey_ has joined #openstack-meeting-alt08:10
*** flaper87|afk is now known as flaper8708:12
*** luqas has joined #openstack-meeting-alt08:15
*** ozstacker has quit IRC08:19
*** ozstacker has joined #openstack-meeting-alt08:20
*** Duane_ has joined #openstack-meeting-alt08:23
*** michael-yu has quit IRC08:25
*** Duane_ has quit IRC08:28
*** markwash has quit IRC08:29
*** markwash has joined #openstack-meeting-alt08:30
*** markwash has quit IRC08:31
*** ozstacker has quit IRC08:32
*** sergmelikyan has joined #openstack-meeting-alt08:33
*** jcoufal has quit IRC08:34
*** jcoufal has joined #openstack-meeting-alt08:35
*** SushilKM has joined #openstack-meeting-alt08:47
*** yamahata has quit IRC08:53
*** aignatov_ is now known as aignatov08:54
*** aignatov is now known as aignatov_09:00
*** konetzed has quit IRC09:06
*** d0ugal has quit IRC09:10
*** d0ugal has joined #openstack-meeting-alt09:10
*** yogesh__ has quit IRC09:10
*** yamahata has joined #openstack-meeting-alt09:11
*** konetzed has joined #openstack-meeting-alt09:11
*** NikitaKonovalov_ is now known as NikitaKonovalov09:12
*** konetzed has quit IRC09:13
*** derekh has joined #openstack-meeting-alt09:14
*** safchain has joined #openstack-meeting-alt09:14
*** johnthetubaguy has joined #openstack-meeting-alt09:22
*** aignatov_ is now known as aignatov09:30
*** Ranjitha has quit IRC09:31
*** Ranjitha has joined #openstack-meeting-alt09:32
*** jtomasek has joined #openstack-meeting-alt09:36
*** luqas has quit IRC09:38
*** konetzed has joined #openstack-meeting-alt09:41
*** Ranjitha has quit IRC09:42
*** aignatov is now known as aignatov_09:42
*** coolsvap has quit IRC09:43
*** coolsvap has joined #openstack-meeting-alt09:45
*** johnthetubaguy1 has joined #openstack-meeting-alt09:45
*** aignatov_ is now known as aignatov09:46
*** boris-42 has joined #openstack-meeting-alt09:46
*** johnthetubaguy has quit IRC09:47
*** DinaBelova_ is now known as DinaBelova09:49
*** SergeyLukjanov_ is now known as SergeyLukjanov09:51
*** amcrn has quit IRC10:01
*** dosaboy has quit IRC10:07
*** luqas has joined #openstack-meeting-alt10:09
*** Duane_ has joined #openstack-meeting-alt10:11
*** Duane_ has quit IRC10:16
*** yogesh has joined #openstack-meeting-alt10:21
*** yogesh has quit IRC10:26
*** SushilKM has quit IRC10:30
*** SushilKM has joined #openstack-meeting-alt10:34
*** DinaBelova is now known as DinaBelova_10:36
*** SushilKM has quit IRC10:38
*** DinaBelova_ is now known as DinaBelova10:45
*** d0ugal has quit IRC10:58
*** d0ugal has joined #openstack-meeting-alt10:58
*** d0ugal has quit IRC10:59
*** d0ugal has joined #openstack-meeting-alt10:59
*** d0ugal has quit IRC10:59
*** d0ugal has joined #openstack-meeting-alt10:59
*** colinmcnamara has joined #openstack-meeting-alt11:02
*** colinmcnamara has quit IRC11:06
*** doug_shelley66 has joined #openstack-meeting-alt11:16
*** jprovazn_ has joined #openstack-meeting-alt11:20
*** rsblendido has joined #openstack-meeting-alt11:28
*** rossella_s has joined #openstack-meeting-alt11:28
*** d0ugal has quit IRC11:32
*** ylobankov has joined #openstack-meeting-alt11:52
*** Duane_ has joined #openstack-meeting-alt11:59
*** Duane_ has quit IRC12:04
*** irenab has joined #openstack-meeting-alt12:06
*** jjmb has joined #openstack-meeting-alt12:08
*** sgordon has quit IRC12:10
*** ylobankov has quit IRC12:17
*** Barker has joined #openstack-meeting-alt12:18
*** Duane_ has joined #openstack-meeting-alt12:18
*** Duane__ has joined #openstack-meeting-alt12:21
*** luqas has quit IRC12:23
*** akuznetsov has quit IRC12:24
*** Duane_ has quit IRC12:25
*** akuznetsov has joined #openstack-meeting-alt12:25
*** luqas has joined #openstack-meeting-alt12:33
*** nosnos has quit IRC12:36
*** pdmars has joined #openstack-meeting-alt12:42
*** doug_shelley66 has quit IRC12:42
*** Leonr has joined #openstack-meeting-alt12:47
*** dguitarbite has quit IRC12:48
*** luqas has quit IRC12:49
*** coolsvap has quit IRC12:58
*** BrianB_ has joined #openstack-meeting-alt12:59
*** jdob has joined #openstack-meeting-alt13:00
*** _ruhe is now known as ruhe13:01
*** sadasu has joined #openstack-meeting-alt13:01
*** baoli has joined #openstack-meeting-alt13:02
baoli#startmeeting PCI passthrough13:02
openstackMeeting started Thu Jan 23 13:02:28 2014 UTC and is due to finish in 60 minutes.  The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
*** openstack changes topic to " (Meeting topic: PCI passthrough)"13:02
openstackThe meeting name has been set to 'pci_passthrough'13:02
baoliHi13:03
irenabhi13:03
*** heyongli has joined #openstack-meeting-alt13:03
sadasuHello! should we set the topic to SR-IOV?13:04
baoliirenab, rkukura is going to join?13:04
baoli#topic SRIOV13:05
*** openstack changes topic to "SRIOV (Meeting topic: PCI passthrough)"13:05
irenabbaoli: I hope so. Will ping to check13:05
heyonglihi,13:05
sadasuhe mentioned in the ML2 meeting yesterday that he would13:05
rkukurahi13:06
sadasuWelcome!13:06
baoliHi13:06
baoliLet's get started13:06
irenabrkukura: I have updated the vnic_type neutron plueprint according to our discussion13:06
irenab^blueprint13:07
rkukurairenab: Great! I'll review it today.13:07
baoliIrenab, pointer to the bp?13:07
irenabjust to share with all, the idea is to use port binding:profile for vnic_type and pci details13:08
baoliso binding:profile is another dictionary?13:08
irenab#link https://blueprints.launchpad.net/neutron/+spec/ml2-request-vnic-type13:08
rkukurabaoli: Its an existing attribute that is a dictionary13:08
irenabbaoli: this is already supported via neutron CLI, so just to add persistency13:08
baoliunderstood.13:09
rkukuraIts part of the portbinding extension, but needs to be implemented in ml213:09
baolirkukura, that sounds good13:09
irenabrkukura: I think to add it as part of supporting this BP13:09
rkukuraright13:10
sadasuwhat changes do we need in ML2 to support vnic_type "pcipassthrough" ?13:10
irenabso, by adding this we add the common layer to propagate and persist attributes to neutron13:10
irenabsadasu: it will be managed by Mech Driver not by plugin13:11
irenabMech Driver will need to look at binding:profile , check if wnic_type is supported13:12
sadasuok...just making sure it does not need any special handling at ML2 layer...it will just be passed along to the respective mech driver13:12
rkukurathe plugin will persist it and handle the CRUD operations, but it will be interpreted by MechanismDrivers as they attempt to bind the port13:12
sadasugot it13:12
irenabsadasu: and here I guess we will need some general util to parse it with regards to PCI device record details13:12
baoliare you suggesting that only ML2 supports the vmic_type and PCI stuff? I guess that's fine since regular plugins will be deprecated?13:13
*** SergeyLukjanov is now known as SergeyLukjanov_13:13
irenabseens it will be needed by both our Drivers13:13
irenabbaoli: not sure why to limit it to ML2 only13:14
irenabif there is plugin that wants to support this extension, can add the support13:14
sadasuirenab: both means ML2 mech driver and regular (non-ML2) plugin?13:14
irenaband then will check the vnic_type on plugin layer13:14
baoliirenab, ok, that sounds right13:14
rkukurabaoli: The openvswitch and linuxbridge plugins are deprecated. Some other plugins already implement binding:profile, so they should probably be updated to handle the vnic_type key if it makes sense for them.13:15
irenabsadasu: regular do not need to handle PCI device fields13:15
baolirkukura, sounds good13:15
baoli#topic specify SRIOV13:16
*** openstack changes topic to "specify SRIOV (Meeting topic: PCI passthrough)"13:16
baoliCan we talk about how to specify SRIOV requests from API/CLI?13:16
irenabbaoli: API/CLI of nova or neutron?13:16
baoliirenab, both. Let's start from nova13:16
rkukuraOne other key point on binding:profile - this is being used purely as an input param to neutron/ml2, so a different attribute will be used for output from neutron to the VIF driver.13:17
heyonglinic request for pci should translate to request before scheduler, in API , i  think13:18
heyongliand store it in to instance meta data.13:18
*** aignatov is now known as aignatov_13:18
sadasubefore the API/CLI, I also wanted to talk about passing the pci_flavor info given in --nic option to neutron13:19
irenabheyongli: right, but then it comes to compute node and allocates specific device13:19
*** aignatov_ is now known as aignatov13:20
heyongliirenab: sure, only if conver  to request and store in the meta data, all works.13:20
heyonglii had proposed interface to do this in my pathset.13:20
baoliI think that the question is what should be part of the --nic parameters13:21
*** jcoufal has quit IRC13:21
heyonglibaoli, sure.13:21
*** ruhe is now known as _ruhe13:22
irenaband we need to define what is passed  from nova to neutron and vise versa13:22
heyongli#link https://review.openstack.org/#/q/status:abandoned+project:openstack/nova+branch:master+topic:bp/pci-extra-info,n,z13:22
*** jcoufal has joined #openstack-meeting-alt13:22
*** SergeyLukjanov_ is now known as SergeyLukjanov13:22
irenabheyongli: which one do you refer?13:23
baolivnic-type=“vnic” | “direct” | “macvtap” pci-group=pci-group-name port-profile=port-profile-name. Except that we can change the pci group to pci flavor, I guess.13:24
heyonglibaoli, agree.13:24
*** dosaboy has joined #openstack-meeting-alt13:24
irenabbaoli: all these --nic options will be possible to defined with binding:profile on port-create13:25
baoliirenab, yes, that's what we have been talking about in all of our docs13:25
baoliBut let's start with nova boot13:25
irenabbaoli: I missing the question :-)13:26
baoliirenab, what question? The input will be put into the binding:profile. In addition, neutron port-create can use the same parameters13:27
irenabsure, so what do you want to discuss?13:28
baoliwell, just to make sure we are on agreement with that, and then we can submit the BP for approval13:28
rkukuraOne point - if existing port UUID is passed into nova via --nic, nova needs to merge its binding:profile keys with any that already exist when doing the port_update.13:29
baolirkukura, agreed13:29
irenabagree13:29
*** aignatov is now known as aignatov_13:29
baoliSo neutron port-create will have similar parameters. And --nic port-id=sriov-port will populate the binding:profile after geting the infor from neutron13:30
irenabI do not think the pci_flavor should be pushed to port profile, it should be pci slot details, right?13:30
baoliirenab, if a pci-flavor name can correspond to a provider net or physical net, certainly it's useful information in the neutron13:31
*** SushilKM has joined #openstack-meeting-alt13:32
*** SushilKM has left #openstack-meeting-alt13:32
irenabbaoli: I mean it can pass, but its not enough, we need the pci device BDF too13:32
baoliirenab, agreed.13:32
rkukurabaoli: What do you mean above by " after geting the infor from neutron"?13:33
baolirkukura, if --nic port-id=srivo-port-uuid is specified, nova will query neutron for port info. So the binding:profile will be returned as part of the query13:34
*** hartsocks has joined #openstack-meeting-alt13:34
*** aignatov_ is now known as aignatov13:35
baoliirenab, I also think that vendor_id and product_id are useful information for the mech driver.13:35
*** doug_shelley66 has joined #openstack-meeting-alt13:35
rkukurabaoli: OK, you just mean getting the existing binding:profile, adding stuff, and then doing a port_update. You said "port-create" above, in which case the port doesn't already exist.13:35
irenabbaoli:agree, this can help to filter between diff.v vendor Mech Drivers for SR-IOV13:35
baolirkukura, with --nic port-id=sriov-port-uuid, the port has to be created before hand13:36
*** mattgriffin has joined #openstack-meeting-alt13:37
rkukurabaoli: agreed - I was just confusing this with the case where nova creates the port.13:37
baoliso it would be like, neutron port-create --vnic-type=direct --pci-flavor=f1 net, and then nova boot --nic port-id=port-uuid. It's not exact the cli syntax, but that's the idea13:37
irenabbaoli: agree13:38
baolicool13:38
baoliNow let's talk about the neutron net-create command13:38
heyongli--pci-flavor=f1:number13:38
*** rahmu has left #openstack-meeting-alt13:38
baoliheyongli, we don't need :number, since it's only one nic a time13:39
heyonglibaoli: to keep it all the same , i suggest it should have one13:39
irenabheyongli: can it be assumed 1 if not specified?13:40
baoliheyongli, I suggest that if it's one, it can be omitted in the extra spec as well13:40
baoliin our case, it's always one13:40
heyonglibaoli: let's accept this , maybe convinet to you guy.13:40
*** dosaboy has quit IRC13:41
baolidisagree13:41
heyongliwhat ?13:41
*** rahmu has joined #openstack-meeting-alt13:41
*** mattgriffin has quit IRC13:41
heyonglii mean ommit is ok for me, disagree?13:41
*** dosaboy has joined #openstack-meeting-alt13:42
*** doug_shelley66 has quit IRC13:42
baoliheyongli, sorry, I misunderstood because the sequence of messages. So that's cool13:42
*** doug_shelley66 has joined #openstack-meeting-alt13:42
baoliSo we agree that if it's one, it can be omitted13:42
irenabbaoli: can you present the net-create13:43
baoliirenab, I was thinking to add --pci-flavor and --port-profile to the command.13:43
irenabbaoli: so you need extension for this?13:44
baoliThe idea behind adding pci-flavor is that a pci flavor can be associated with a physical net by admin, and a neutron network is associated with a physical net.13:45
baoliirenab, possibly if we agree to add them13:45
irenabbaoli: another question, how the pci flavor will be taken into account by scheduler?13:45
*** joel-coffman has joined #openstack-meeting-alt13:45
baoliirenab, when you specify --nic net-id=net-uuid, nova query neutron for the network information, so that's when that information will be passed back to nova13:46
baolithe rest will be the same13:46
irenabnaoli: not sure, but is it before the scheduler decision?13:46
*** lblanchard has joined #openstack-meeting-alt13:46
*** sgordon has joined #openstack-meeting-alt13:46
*** vponomaryov has joined #openstack-meeting-alt13:46
baoliirenab, yes.13:46
irenabso from the point it gets it from network details, it will be the flow heyongi already supports/plan to support?13:47
baoliSo the sequence of api requests would be: neutron net-create --pci-falvor f1 net1, nova boot --nic net-id=net1-uuid.13:48
baoliirenab, it will be the same flow as the patch I have posted13:48
irenabbaoli: So you just do not need to specify it explicitly on nova boot?13:48
baoliirenab, yes.13:49
irenabI think the correct constract to associate the pci_flavor with is provider_network and not virtual netowrk, so probably can come from config file13:49
baoliThis gives the admin a simplified view/tool of the sriov network13:49
*** SergeyLukjanov is now known as SergeyLukjanov_a13:50
baoliirenab, that's a good idea too. we can think about it more13:50
irenaband if needed can be overriden on virtual network/port level13:50
baoliAssuming that we use sriov for provider net only13:50
*** SergeyLukjanov_a is now known as SergeyLukjanov_13:51
irenabbaoli: I like your idea to simplfy the management view13:51
baolirkukura, any thoughts on this?13:51
rkukurairenab: Do you mean physical_network rather than "provider network"?13:51
irenabrkukura: same13:52
rkukuraOnce they are created, provider networks are no different than tenant networks. In fact, there is no way to know which way it was created.13:52
irenabI mean physical network you specify via provider extension13:52
rkukuraok, that's what I thought13:52
rkukuraat least for flat and vlan networks, this makes sense13:53
*** dgenin has joined #openstack-meeting-alt13:53
*** sahid has joined #openstack-meeting-alt13:53
rkukuraAre any other network_types, which might not involve a physical_network, in scope for this discussion?13:53
irenabrkukura: at least for now, not for Mellanox case13:54
*** llu-laptop has joined #openstack-meeting-alt13:54
*** rushiagr has joined #openstack-meeting-alt13:55
rkukuraSo who where in the process does the physical_network come into play? Does the user need to see this?13:55
baolirkukura, by user, you mean?13:55
rkukuraOnly admin users would ever know anything about any physical_network13:56
*** ndipanov has joined #openstack-meeting-alt13:56
baolirkukura, when we create a neutron network, the provider net needs to be specified with provider network, right?13:57
irenabthe matching pci_flavor to physical_net should be done by admin only13:57
baoliagreed13:57
*** d0ugal has joined #openstack-meeting-alt13:57
irenabbaoli: there can be default, then no need to specify13:57
*** luqas has joined #openstack-meeting-alt13:57
rkukuraok, so a non-admin user needs to pick the right flavor for the network he is using?13:57
*** jecarey has quit IRC13:57
heyonglirkukura: for current, it is.13:58
rkukuraThat's fine for now.13:58
irenabrkukura: not is it was associated previously by admin13:58
baoliirenab, so you mean to say that it should be configured13:58
irenabbaoli: what should be configured?13:58
*** yamahata has quit IRC13:58
heyonglirkukura, we had plan B, discuss in the meeting, i recall.13:58
baoliirenab, I mean to say that the pci flavor and physical net association can be configured13:58
rkukuraSo when it comes to the ml2 port binding by the PCI-passthru MechanismDriver, it will make sure the network has a segment who's physical_network matches that of the PCI device?13:59
irenabits an option, like you have vlan_ranges configured via config13:59
*** johnthetubaguy1 is now known as johnthetubaguy13:59
*** codekobe has left #openstack-meeting-alt13:59
irenabrkukura: it should be so13:59
baoliOk, time is running out. Let's continue on Monday, in the same time let's also talk about work division.14:00
baoli#endmeeting14:00
*** n0ano has joined #openstack-meeting-alt14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Thu Jan 23 14:00:09 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-23-13.02.html14:00
rkukurairenab: agreed14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-23-13.02.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-23-13.02.log.html14:00
baolithanks everyone14:00
*** matel has joined #openstack-meeting-alt14:00
irenabthanks all14:00
heyonglithanks ,boli14:00
heyonglisorry, baoli14:00
russellb#startmeeting nova14:00
openstackMeeting started Thu Jan 23 14:00:52 2014 UTC and is due to finish in 60 minutes.  The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova)"14:00
openstackThe meeting name has been set to 'nova'14:00
russellbHello, everyone!14:00
russellbThis is our second bi-weekly meeting at 1400 UTC14:01
llu-laptophi14:01
matelhi14:01
* n0ano is it morning yet14:01
*** tianst has joined #openstack-meeting-alt14:01
hartsocks\o14:01
johnthetubaguyhi14:01
sahidhi14:01
russellbseemed to be attended just as well as the other time 2 weeks ago14:01
russellb#topic general14:01
*** openstack changes topic to "general (Meeting topic: nova)"14:01
russellbso let's check in on the icehouse schedule14:02
russellb#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule14:02
russellbicehouse-2 is today14:02
russellbwhich means we're now in icehouse-3 development14:02
russellbsome critical dates to keep in mind for icehouse-3 ...14:02
russellbfeature freeze --> March 414:02
russellbhowever, we need to pick a date for our feature proposal freeze14:02
russellblast cycle we had a deadline for code to be posted 2 weeks before feature freeze14:03
russellbi think it would be wise to do the same thing again, but hadn't really picked a specific date yet14:03
llu-laptopfeature proposal == bp approval?14:03
russellbi should say, blueprint code proposal freeze14:03
russellbnot sure what to call it :-)14:04
johnthetubaguy+1 sounds good14:04
hartsocksproposal deadline?14:04
russellbbasically ... we want code to be up in advance of the merge deadline14:04
russellbyeah.14:04
matelpatch proposal14:04
*** rkukura has left #openstack-meeting-alt14:04
russellbwe're looking at mid-february sometime14:04
russellbi'll start a thread on openstack-dev to finalize the date14:05
russellbbecause i suspect other projects may want to coordinate on that14:05
rushiagrhi14:05
*** BrianB_ has quit IRC14:05
russellbbut basically ... less than 4 weeks to have code up for review for icehouse (for blueprints)14:05
russellbany schedule questions?14:05
johnthetubaguysounds good, cross project meeting agenda item?14:06
russellbjohnthetubaguy: that's a good idea14:06
russellb#action russellb to bring code proposal freeze date selection to cross project meeting14:06
*** sballe has joined #openstack-meeting-alt14:06
johnthetubaguy:)14:06
russellb#topic sub-teams14:07
*** openstack changes topic to "sub-teams (Meeting topic: nova)"14:07
* hartsocks waves14:07
* n0ano gantt14:07
* johnthetubaguy raises hand14:07
russellbhartsocks: go for it14:07
hartsockssure.14:07
hartsocksWe're set for Minesweeper to do voting ...14:07
hartsocks… it's set for a "0" vote right now instead of a −1 vote.14:07
*** aignatov is now known as aignatov_14:08
hartsocksMostly we're bummed because none of our blueprints were reviewed.14:08
hartsocksThat's all I'd bring to the group.14:08
russellbsorry about that14:08
hartsocksI'll hit the mailing list later with my detailed update.14:08
russellba very low number of blueprints made it in14:08
* hartsocks bows out14:08
hartsocksyeah I figured.14:08
russellbwe can revisit that in a bit more detail in the blueprints section in a bit14:08
hartsocksThis was a rocky milestone.14:09
russellbk, will look for your detailed update on list14:09
russellbn0ano: hi14:09
n0anocouple of things...14:09
n0anodecision was made to get the gantt tree working first and then re-sync (potentially recreate the tree) to the nova tree...14:10
*** heyongli has quit IRC14:10
russellbyes, i think that's a good plan of attack14:10
n0anoto that, I've submitted a couple of patches for review that get almost all of the 254 unit tests working (17 related to affinity still fail)...14:10
russellblinks?14:10
russellbhttps://review.openstack.org/#/q/project:openstack/gantt+branch:master,n,z14:11
n0ano#link https://review.openstack.org/#/c/68521/14:11
n0anoreviews would be nice :-)14:11
russellbhttps://review.openstack.org/#/q/project:openstack/gantt+branch:master+status:open,n,z14:11
russellbok, will keep a tab open on them to look today14:12
johnthetubaguyn0ano: I keep meaning to, will bump up the list a bit14:12
russellbon the add/remove files thing ... probably something to note for regenerating the repo14:12
n0anoNP, they're there waiting for you :-)14:12
russellbif that gets done14:12
*** aignatov_ is now known as aignatov14:12
*** SergeyLukjanov_ is now known as SergeyLukjanov14:12
*** baoli has quit IRC14:13
n0anoI did it that way so that the gantt changes would be separate from adding/deleting files, makes the re-sync easier14:13
russellbso i think for icehouse we should aim to have the thing running so that we could do a nova-scheduler freeze early juno14:13
n0anorussellb, +1 (that would be the goal)14:13
russellbi think a full dev cycle is ideal to let things shake out with splitting14:13
johnthetubaguyrunning by end of icehouse then?14:14
russellbyeah14:14
johnthetubaguysounds good14:14
russellband if we meet that, we can then have the conversation with release management about the deprecation plan and release of gantt14:14
*** boris-42_ has joined #openstack-meeting-alt14:14
n0anowe're close (getting most of the unit tests going is big) so I think that's doable14:14
*** yamahata has joined #openstack-meeting-alt14:14
russellbsounds good14:15
russellbthanks for your work on it!14:15
russellbanything else in scheduler land?14:15
n0anoBTW, I haven't gotten anyone to look at my devstack changes for gantt14:15
*** katyafervent has quit IRC14:15
n0ano#link https://review.openstack.org/#/c/67666/14:15
*** boris-42 has quit IRC14:15
*** katyafervent has joined #openstack-meeting-alt14:15
*** dteselkin_ has quit IRC14:15
n0anogetting reviews for that would be nice also14:15
russellbooh i didn't know that existed yet14:15
*** rushiagr has left #openstack-meeting-alt14:15
russellbwill look at that too14:15
n0anoyes, one more item, johnthetubaguy brought up his BP for caching scheduler14:15
*** dteselkin_ has joined #openstack-meeting-alt14:16
johnthetubaguyI am writing a new caching scheduler driver: https://review.openstack.org/#/c/67855/14:16
n0ano#link https://blueprints.launchpad.net/nova/+spec/caching-scheduler14:16
*** rushiagr has joined #openstack-meeting-alt14:16
*** bugsduggan has joined #openstack-meeting-alt14:16
*** bugsduggan has left #openstack-meeting-alt14:16
n0anosome discussion around that, looks interesting but need more info14:16
johnthetubaguyits going to be experimental at the moment14:16
*** mclarenst has joined #openstack-meeting-alt14:16
johnthetubaguyI don't have stats only feelings14:16
*** esker has joined #openstack-meeting-alt14:17
johnthetubaguywould like to encourage innovation there, over perfection14:17
russellbhmm, maybe a design wiki page to go with it?14:17
russellbrun through some examples14:17
johnthetubaguyit re-uses all filters and weights at the moment14:17
n0anorussellb, that was suggested at the meeting14:17
*** _ruhe is now known as ruhe14:17
*** NehaV has joined #openstack-meeting-alt14:17
russellbjohnthetubaguy: cool, just trying to understand how the cache part works14:18
russellbwhich i guess is kinda the point :)14:18
johnthetubaguyyeah, I should write that, proved to myself it works14:18
johnthetubaguyish14:18
*** alaski has joined #openstack-meeting-alt14:18
russellbbut yeah, i'm all for alternative approaches14:18
n0anothat's pretty much all from me14:18
*** coolsvap has joined #openstack-meeting-alt14:18
johnthetubaguyI will write it up, now it works (with one host anyway)14:19
russellbjohnthetubaguy: ok great14:19
*** dhellmann_ is now known as dhellmann14:19
russellbping me when you have that so we can push the bp review along14:19
* n0ano one host - my favorite cloud14:19
russellbwe all do dev on one host clouds, right?  heh14:19
russellbworks on devstack, ship it14:19
johnthetubaguyI didn't approve the BP since I didn't feel I wrote it up well enough yet :)14:19
*** sahid has quit IRC14:19
johnthetubaguyhehe14:19
n0anosometimes I go wild and bring up 214:20
*** eankutse has joined #openstack-meeting-alt14:20
*** mriedem has joined #openstack-meeting-alt14:20
russellbjohnthetubaguy: yeah, that's all i want to see (a bit of a write-up)14:20
johnthetubaguy+114:20
russellbalright, thanks guys!14:20
russellbjohnthetubaguy: you!14:20
johnthetubaguycool14:20
russellbin another context i suspect14:20
johnthetubaguymatel: is doing great work on the test stuff, maybe he can summarise that?14:21
*** rraja has joined #openstack-meeting-alt14:21
matelyes, we have pending changes in nodepool & infra, but tempest still fails.14:21
matelSo the plan is to get a stable tempest run first, and then trigger the infra team.14:21
johnthetubaguybut on a physical node BobBall has full tempest passing right?14:22
russellbinfra team is pretty slammed at the moment anyway14:22
matelyes, physical works.14:22
mriedemfull tempest?14:22
mriedemand is that scoped to only xenapi patches? or all?14:22
russellbwhat about the other env makes it fail?14:22
matelrusselb: Still looking into that14:22
russellbk just curious14:22
russellbappreciate your hard work on this14:23
matelIt's a bit slow, but we'are getting closer.14:23
russellbhow do you feel about the timeline right now14:23
matelmriedem: full passed on 17th last.14:23
mriedemmatel: how long is a full run taking on your physical node?14:24
*** julim has joined #openstack-meeting-alt14:24
matelrussellb: Not sure, related to our changes, it's around 2-4 weeks.14:24
*** kashyap has joined #openstack-meeting-alt14:24
*** NehaV has quit IRC14:25
russellbOK, was wondering how realistic having it running by icehouse-3 was14:25
russellbi guess getting tempest passing is in your control ... infra integration slightly out of your control14:25
matelmriedem: 4118.578s on a rather old machine14:25
russellbnot bad14:25
russellbthat's how long current jobs are taking14:26
johnthetubaguyyeah, there are some perf fixes done by Bob to help that, so we are getting close14:26
johnthetubaguyso far...14:26
russellbcurrent jobs were faster before, but we cut concurrency back to 2 from 414:26
russellbbecause 4 overloaded the test nodes14:26
mriedemmatel: and is this on all nova patches, or a subset?14:26
johnthetubaguyah, makes sense14:26
matelmriedem: This job, that I was looking at, was a nova master + under review citrix patches.14:27
johnthetubaguyyeah, final thing with run in Rax cloud using zuul14:27
johnthetubaguyanyway, that was main news14:28
russellbgreat, happy to hear about progress on that front14:28
matelmriedem: last master pass was on 8-jan14:28
russellbregarding other drivers ... no real word from hyperv lately, and docker folks just starting to work on it14:29
russellbhyperv at the biggest risk, then docker14:29
mriedemi was going to read the latest hyperv meeting minutes14:29
russellbi feel good about vmware and xenapi14:29
johnthetubaguyLXC are thinking about stuff too I think14:29
mriedemis there any news in there?14:29
russellbjohnthetubaguy: LXC?  as in libvirt/lxc or?14:29
russellbmriedem: good idea14:29
russellbmriedem: wish they would show up here ... :(14:29
mriedemyeah, me too14:30
mriedemi'll read their minutes14:30
johnthetubaguyrussellb: libvirt + LXC I think14:30
russellbmriedem: k let me know14:30
russellbjohnthetubaguy: ah OK14:30
russellbwe also do libvirt/xen14:30
russellbi doubt there will be CI for that14:30
johnthetubaguyyeah, suse guys mentioned it, or someone did at the summit14:31
russellbbut also not sure it's worth ripping out that pieces of it14:31
johnthetubaguybut not seen anything14:31
*** Barker has quit IRC14:31
russellbit being libvirt driver14:31
johnthetubaguywell, I think we agreed to add a log saying "untested" or something14:31
russellbmaybe put a big warning in the logs ... yeah14:31
mriedemfor xenapi?14:31
johnthetubaguyxenapi is not in libvirt14:31
johnthetubaguylibvirt xen is a different thingy14:31
mriedemok, xenapi is what we were just talking about before right?14:31
mriedemok, yeah14:31
mriedemi joined late :)14:32
johnthetubaguyyeah, sorry, for confusion, why just have one tool stack, when you can have seven?14:32
russellbxenapi is in good shape14:32
russellbok onward14:32
*** d0ugal has quit IRC14:32
johnthetubaguyits promising at least, hoping to add cloudcafe after we have tempest working14:32
russellb#topic bugs14:32
*** openstack changes topic to "bugs (Meeting topic: nova)"14:32
*** demorris has joined #openstack-meeting-alt14:32
russellb#link https://bugs.launchpad.net/nova14:33
russellb226 new bugs14:33
*** pcarver has joined #openstack-meeting-alt14:33
russellbit's probably worth a bug triage day soon14:33
*** jecarey has joined #openstack-meeting-alt14:33
russellbto make sure we catch anything really important in there for icehouse14:33
russellbanyone interested in organizing that?14:33
johnthetubaguyfirst friday of icehouse-3 and icehouse-4?14:34
mriedem101 untagged, wow14:34
russellbwhat's icehouse-4  :)14:34
johnthetubaguyI am tempted by might need some guidance, I can reach out to mr still I guess14:34
johnthetubaguydoh14:34
russellbjohnthetubaguy: happy to provide guidance, and michael would be great too14:34
johnthetubaguycool, I can give it a try then14:34
russellbbasically ... pick a day, write up an encouraging call to arms email14:35
russellbinvite everyone to join #openstack-nova to work together14:35
johnthetubaguyoh, yeah, and ready the stats14:35
russellbprovide a set of links to the bug lists, and process notes14:35
russellband yeah, metrics are good so that we can celebrate progress made14:35
johnthetubaguycool, I can dig out the old emails14:35
johnthetubaguywhen do we want it, next week or two?14:35
russellbi think any time in icehouse-3 would be OK14:36
kashyapI can volunteer for the bug triage day to participate if it's before 30th of this month.14:36
russellbbefore we start our big bug fix push in the RC cycle14:36
russellbkashyap: great thanks14:36
johnthetubaguyrussellb: right, and after the gate bug day, I guess14:36
russellbtrue14:36
mriedemgate bug day is every day right?14:36
russellbwhich is this coming monday14:36
russellbheh14:36
kashyapAlthough, my areas limited to KVM/QEMU/Libvirt aspects.14:36
russellbgate bug day has been every day for me lately  yes :)14:37
russellbkashyap: plenty of those in there to look at i think14:37
russellbkashyap: and you can always expand your knowledge by studying some others :)14:37
kashyaprushiagr, Yeah, I'm already on two of them14:37
rushiagrI'll do some bugtriage wrt ec2 api bugs14:37
kashyaprussellb, Yeah, for now I'm focusing on KVM internals/nested virt in my spare time14:37
johnthetubaguyOK, so I will try sort something out, maybe aim for the Monday after the gate day?14:38
russellbif nothing else, for status we have http://webnumbr.com/untouched-nova-bugs14:38
* rushiagr smiles at kashyap thanking him for waking /me up at the right time14:38
mriedemjohnthetubaguy: week after next sounds good14:38
russellbjohnthetubaguy: sure ... or i think fridays are good for this kinda thing too ... any day is good with me though14:38
mriedemb/c the week after that is the mid cycle meetup14:38
kashyap(Oops, didn't mean to prompt, damn auto-completion)14:38
rushiagrkashyap: no worries14:38
russellbcould be a mid-cycle meetup activity, too14:38
mriedemyeah14:39
russellbfor some of the time anyway14:39
mriedemmight work out that way14:39
johnthetubaguywell, do we want it after the mid-cycle meetup14:39
mriedemis that too late?14:39
russellbwe also have http://status.openstack.org/bugday/14:39
*** irenab has quit IRC14:39
johnthetubaguymriedem: yeah, I guess, so week before it will be14:40
kashyap(/me is trying to reproduce this nasty one on his setup, I wonder why more more people aren't hitting it - https://bugs.launchpad.net/nova/+bug/1267191)14:40
russellbsounds good to me14:40
russellbthanks a bunch johnthetubaguy :)14:40
*** matel is now known as matel_brb14:40
russellbjohnthetubaguy: catch my two stats links?14:40
johnthetubaguyyeah, looks good, thanks14:40
russellbcool14:40
russellbmikal may have another too14:40
johnthetubaguyyeah, will drop him a mail, given he sleeps while I code14:41
*** ikhudoshyn has quit IRC14:41
russellbok last bug note real quick ...14:41
russellb#link http://status.openstack.org/elastic-recheck/14:41
russellbi've been focusing on gate bugs the last couple weeks14:41
russellbcould still use more help14:41
kashyapIs there a URL for gate bugs?14:42
russellbthe elastic-recheck page sorts the known ones by frequency14:42
*** matel_brb is now known as matel14:42
russellbkashyap: there's a libvirt one on there14:42
kashyapI'd like to keep an eye, as most of my testing is on Fedora + latest bits (mostly RDO; sometimes devstack)14:42
russellb#topic blueprints14:42
*** openstack changes topic to "blueprints (Meeting topic: nova)"14:42
russellbso blueprints ...14:43
russellbour velocity is down a good bit this cycle, and i think other projects too14:43
russellb#link https://launchpad.net/nova/+milestone/icehouse-214:43
russellbwe completed 9 in icehouse-214:43
russellband 13 in icehouse-114:43
russellband now icehouse-3 is kind of insane looking14:43
russellbbut on the velocity issue14:43
russellbi think there are a few major contributing factors worth noting14:44
johnthetubaguybeen thinking about the process, if there are more higher priority blueprints, its easier to review them above all the other low? Maybe we should just bump a few up and leave sponsors as extra input not only input?14:44
russellb1) summit in the middle of icehouse-114:44
russellb2) holidays in the middle of icehouse-214:44
russellb3) major gate troubles in the last couple weeks14:44
russellbjohnthetubaguy: yes the process, thanks for bringing that up14:44
russellbso i sent out a message last week asking for people to please sponsor stuff14:45
russellbi'm not sure that really helped14:45
russellbso i agree, i think for icehouse at this point, we should just bump things up that we just feel are more important14:45
russellbwe should only bump up the ones we really want to get in, and think can (sponsors aside)14:45
kashyaprussellb, Yes, that Gate bug (1254872) - I looked at it a couple of days ago. danpb posted some investigation for the reporter. I'll try it tomorrow14:45
johnthetubaguyyeah, we kinda need to, we can leave sponsoring as a handy way to get _other_ blueprints to medium14:46
russellbjohnthetubaguy: sure, i'm good with that14:46
russellband we'll have to re-discuss the process for juno14:46
russellbi'm loving the help, that part is good14:46
russellbthe prioritization part is a flop14:46
johnthetubaguy+114:46
johnthetubaguythe review seems to work better, spread around, but yeah, priorities suck right now14:47
russellbso johnthetubaguy (and other nova-drivers) feel free to start selectively increasing priority14:47
*** dgenin has quit IRC14:47
johnthetubaguyrussellb: worth a mail to nova-drivers again?14:47
russellbyes14:47
johnthetubaguysweet14:47
russellbso we should do that very soon14:48
russellbaim to pick out the ones we really want to land14:48
alaskiI almost missed this meeting, and I'm guessing others aren't here.  So email is good14:48
russellbalaski: all good14:48
*** xyang1 has joined #openstack-meeting-alt14:48
russellbwe have a list of 147 right now14:48
russellbwhich is far from realistic14:48
*** eankutse1 has joined #openstack-meeting-alt14:49
johnthetubaguyvs 13 and 9…14:49
russellbright.14:49
johnthetubaguyeek14:49
russellbso ... prioritize to pick the ones we want to focus on14:49
*** balajiiyer has joined #openstack-meeting-alt14:49
russellbset a blueprint approval deadline to be soon14:49
russellba good number of these haven't been approved14:49
russellband then i suspect proposal deadline will kick out another big chunk14:49
russellbsounds like i need to write another email about icehouse-3 blueprint timeline14:50
johnthetubaguyyeah, would be good14:50
*** eankutse has quit IRC14:50
russellbthe points in time where we'll be kicking stuff out14:50
russellbhow much time should we reserve to get the last bit approved14:50
russellbnot like we need more approved, but should do another pass14:50
russellbnext Friday reasonable?14:50
johnthetubaguyso, blueprint approved by, all patches ready and passing tests by?14:50
russellbyeah14:51
russellband then of course, feature freeze (merged)14:51
*** balajiiyer has quit IRC14:51
johnthetubaguygood point14:51
johnthetubaguya week seems a bit short, but longer seems too long14:51
*** balajiiyer has joined #openstack-meeting-alt14:51
russellbanother week and a day seem reasonable to do our last blueprint approvals?14:51
russellbheh14:51
johnthetubaguyI think I aggree with a week14:51
*** balajiiyer has left #openstack-meeting-alt14:51
russellbwe can always grant exceptions :)14:51
alaskisounds good to me14:51
johnthetubaguytrue14:51
russellbso at least we'll hear the complaints sooner and have more time to respond to them, heh14:52
johnthetubaguytrue true14:52
*** bswartz has joined #openstack-meeting-alt14:52
russellband if anyone has an icehouse-3 blueprint you know won't make it, save us some work and update it to defer :)14:53
johnthetubaguystuff that is up for review now, all patches ready, should we make them medium now? since they got them there first?14:53
driptonthat sounds totally fair14:53
russellbi wouldn't update all of them to medium14:53
russellbshould be more selective14:53
*** esker has quit IRC14:54
johnthetubaguywell, if we make the other stuff we _really_ want high?14:54
russellbthe ones we feel are most important out of them, yes14:54
* mriedem gets out my defer pen14:54
russellbwell ... release management treates medium and above special ... as in, those are the things we expect to merge14:54
russellblow is all "nice to have"14:54
*** esker has joined #openstack-meeting-alt14:54
*** bill_az has joined #openstack-meeting-alt14:54
johnthetubaguytrue, we should stick with that14:54
russellbthat's the only reason i'm picky about it14:54
russellbbut we can certainly afford more medium/high than we have right now14:55
*** eharney has joined #openstack-meeting-alt14:55
*** d0ugal has joined #openstack-meeting-alt14:55
*** d0ugal has quit IRC14:55
*** d0ugal has joined #openstack-meeting-alt14:55
driptonbut if the work's already done then we expect it to merge, unless we just don't like the blueprint idea, in which case it should have been rejected14:55
johnthetubaguyjust wondering about fairness to those with code already out there, and others who come late to the party, but no easy solution there I guess14:55
russellbjohnthetubaguy: yeah i think it's worth picking the mediums and such out of the ones in that state14:56
russellbjust not wanting to agree to a blanket upgrade of all of them14:56
*** sacharya has joined #openstack-meeting-alt14:56
johnthetubaguyyeah, thats a good way of putting it14:56
russellbbecause there are some things that are just a ton of work with seemingly low backing14:57
russellblike gce for example14:57
*** banix has joined #openstack-meeting-alt14:57
russellb#topic open discussion14:57
*** openstack changes topic to "open discussion (Meeting topic: nova)"14:57
hartsockscaching?14:57
russellbhartsocks: caching of what14:57
hartsocksmethod outputs14:57
russellbno idea what you're talking about, heh14:57
*** banix has quit IRC14:57
johnthetubaguyerm...14:57
hartsocksI've seen a number of patches that implement their own caches….14:57
russellbdon't we have an oslo thingy for that?14:58
hartsocksI thought so...14:58
sdaguerussellb: nova v3 xml remove? ;)14:58
*** vbellur has joined #openstack-meeting-alt14:58
russellbsdague: AH YES14:58
russellbso xml in v3.14:58
russellbanyone want to keep it?14:58
johnthetubaguynope14:58
alaskinope14:58
mriedemi still need to read that thread14:58
russellbmriedem: i'll take that as a no14:58
mriedem:)14:58
*** achirko has joined #openstack-meeting-alt14:58
mriedemnot me personally14:58
russellbFWIW, i'm happy to remove it14:58
sdagueI'm getting a tempest patch ready so we could do the nova delete14:58
russellbi feel like we put some threads out there, no real support for keeping it14:59
sdagueI think it would take a lot of cruft out of the code, and let us focus on real issues14:59
johnthetubaguy…its a great sub team project, if someone wants to fund it in the future, not something we have resources for now14:59
russellbi also feel like i should send (yet another) email on it making it clear that we're making that call14:59
russellbsdague: do we have a blueprint?14:59
*** gregsfortytwo1 has joined #openstack-meeting-alt14:59
sdaguerussellb: no, I'll create one14:59
russellbk15:00
mriedemthe xml stuff is also a PITA for handling datetimes in responses, i found that out the hard way with converting an api to objects15:00
*** caitlin56 has joined #openstack-meeting-alt15:00
russellbs/PITA.*/PITA/15:00
russellbheh15:00
russellbalright, time is up15:00
russellbthank you all for coming15:00
russellbi appreciate your time, and your work on nova!15:00
rushiagrI have submitted some code w.r.t. additions to ec2 api related to block storage. I'd appreciate any help w.r.t getting some eyes on my code..15:01
alaskirussellb: we appreciate you15:01
johnthetubaguy+115:01
russellblet's jump to #openstack-nova rushiagr15:01
russellbalaski: johnthetubaguy <315:01
rushiagrrussellb: done15:01
*** akerr has joined #openstack-meeting-alt15:01
russellbbye :)15:01
russellb#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
openstackMeeting ended Thu Jan 23 15:01:42 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-01-23-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-01-23-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/nova/2014/nova.2014-01-23-14.00.log.html15:01
*** llu-laptop has left #openstack-meeting-alt15:01
*** mriedem has left #openstack-meeting-alt15:01
bswartz#startmeeting manila15:02
openstackMeeting started Thu Jan 23 15:02:07 2014 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: manila)"15:02
*** joel-coffman has quit IRC15:02
openstackThe meeting name has been set to 'manila'15:02
*** demorris_ has joined #openstack-meeting-alt15:02
*** hartsocks has left #openstack-meeting-alt15:02
bswartzhello folks15:02
bswartzwho do we have?15:02
vponomaryovhi15:02
xyang1hi15:02
gregsfortytwo1hi15:02
bill_azHi15:02
vbellurhello15:02
achirkohello15:02
rrajahi15:02
caitlin56hi15:02
*** demorris has quit IRC15:03
*** demorris_ is now known as demorris15:03
*** tianst has quit IRC15:03
*** amytron has joined #openstack-meeting-alt15:03
bswartzwow we've got everyone it looks like15:03
*** julim has quit IRC15:03
bswartzonce again I don't have anything special for todays agenda15:03
bswartzI know some drivers are getting close to being done15:04
*** banix has joined #openstack-meeting-alt15:04
bswartzso let's do the status update first15:04
bswartz#topic dev status15:04
*** openstack changes topic to "dev status (Meeting topic: manila)"15:04
vponomaryovI will update about it15:04
*** csaba|afk is now known as csaba15:04
vponomaryovDev status:15:04
bswartzvponomaryov: ty15:04
*** aostapenko has joined #openstack-meeting-alt15:04
vponomaryov1) network-api15:05
vponomaryovSuccessfully merged, it includes: security-services entities, share-networks and its linking.15:05
vponomaryovNot documented, for now,15:05
vponomaryovit is expected to be added here: https://wiki.openstack.org/wiki/Manila/API15:05
vponomaryov2) Multitenant Generic driver (work in progress) - https://review.openstack.org/#/c/67182/15:05
vponomaryovFor now, it:15:05
vponomaryova) creates service vm for manila in service tenant (vm of nova + volumes of cinder)15:05
vponomaryovb) uses ssh connection via namespaces for making connection between service vm and user vm (neutron approach, no floating ip).15:05
vponomaryovc) allows to create shares and snapshots15:05
vponomaryovwork left for generic driver:15:06
vponomaryovd) Implement handling of rules (NFS and CIFS)15:06
vponomaryove) Implement proper handling of service VM, after restart of manila for each VM state15:06
*** yportnova_ has joined #openstack-meeting-alt15:06
vponomaryov3) NetApp Cmode multitenant driver - https://review.openstack.org/#/c/59100/15:06
vponomaryovMain work is done, left:15:06
vponomaryova) implement proper removing of errored shares15:06
vponomaryovb) test setting of all provided security services data (depends on environment)15:06
*** luqas has quit IRC15:07
vponomaryovNetApp Cmode driver and generic driver are multi-tenant and they are dependent on share-network entity, that has only neutron plugin, and can not work without neutron.15:07
*** julim has joined #openstack-meeting-alt15:07
vponomaryovOther already existing merged drivers are single-tenant and don't depend on share-network entity:15:07
vponomaryov - LVM driver (supports nfs and cifs, but sid rules not implemented)15:07
vponomaryov - glusterfs driver (supports only nfs)15:07
vponomaryov - netapp 7mode driver15:07
bswartzand the "generic" driver can not work without nova or cinder either15:07
vponomaryovbswartz: right15:08
bswartzso manila will start out being heavily dependent on the rest of openstack15:08
vponomaryovthat all for status15:08
bswartzwe might want to think about whether that's a good thing or a bad thing15:08
vponomaryovgeneric driver isn't production-oriented15:08
bswartzI personally thing that modularity is important, and dependencies are generally bad15:09
*** sacharya has quit IRC15:09
bswartzthink*15:09
vbellurbswartz: +115:09
bswartzhowever if removing dependencies creates a bunch of complexity then that's not good either15:09
bswartzthat can be a future topic15:09
bswartzmaybe something to discuss in atlanta15:09
bswartzfor now I'm more interested in getting something production ready15:09
bswartzthanks for the comprehensive update vponomaryov!15:10
caitlin56For any given site the set of manila drivers would be very static, so some setup cmplexitywould be quite tolerable.15:10
bswartzjust to jump back to the generic driver and the SSH communication -- where is that code?15:10
bswartzcaitlin56: complexity and tolerable should not appear in the same sentence!15:11
vbellurvponomaryov: what are the reasons behind generic driver not being production ready?15:11
bswartzcaitlin56: that way of thinking is a slippery slope15:11
xyang1vponomaryov: are you using a custom image for the generic driver when you launch a VM from nova?15:11
*** luqas has joined #openstack-meeting-alt15:11
vponomaryovbswartz: that code in gerrit topic https://review.openstack.org/#/c/67182/15:11
achirkobswartz: https://review.openstack.org/#/q/status:open+project:stackforge/manila+branch:master+topic:bp/generic-driver,n,z15:12
bswartzvbellur: I think the point is that the top priority for the generic driver is to function as a software only implementation for the purpose of POCs and automated testing15:12
vponomaryovvbellur: for now, it is pretty slow, and it will work much faster will manila backend driver15:12
bswartzI would like to see the generic driver become production quality15:12
*** jomara_ has quit IRC15:13
vponomaryovxyang1: for, yes, we are using ubuntu cloud image with installed nfs and samba servers15:13
vbellurbswartz, vponomaryov: got it, thanks.15:13
xyang1vponomaryov: thanks.  so this image has to be checked in, right15:13
bswartzvponomaryov, xyang1: We need to make sure that administrators can run an image of their choosing in the service VM for the generic driver15:14
bswartzxyang1: no!15:14
xyang1bswartz: admin has to create their own custom image to use the generic driver?15:14
bswartzWhat we need is to document the requirements for the service VM, so that it's possible to build an ubuntu-based service VM or a redhat-based service VM, or a SLES-based service VM15:15
vponomaryovxyang1: image dependency should be left for administrator or devstack15:15
*** Barker has joined #openstack-meeting-alt15:15
bswartzas long as the image contains a linux image with SSHD, NFSD, and Samba it should be okay15:15
*** jergerber has joined #openstack-meeting-alt15:15
xyang1vponomaryov: is this image you are using downloadable already, or did you install the nfs and samba servers and then create a image yourself?15:16
vbellurvponomaryov: +115:16
bswartzmaybe someone will take up the task of building a minimal service VM image for manila -- something like Cirros but with file share capabilities15:16
*** sgordon has left #openstack-meeting-alt15:17
vponomaryovxyang1: we have downloaded ubuntu cloud image, installed nfs and samba, and enabled passwords for ssh, thats all15:17
bswartzI think the task for the manila team is to simply document the requirements that the generic driver will rely on and leave it to the administrator to find or build something suitable15:17
xyang1vponomaryov: ok, thanks15:17
csababswartz: we have a PoC Cirros hack, that is as much as possible to use an  nfsv3 client, it could be enhanced along said requirements15:17
bswartzxyang1: I don't think so15:17
bswartzxyang1: oops nm15:18
bswartzcsaba: that sounds exciting15:18
bswartzjumping back up though15:19
vponomaryovyeah, cirros with nfs and samba is pretty interesting thing, but we need both protocols15:19
bswartzvponomaryov: do you have an estimate for when the generic driver will be complete?15:19
vponomaryovwe hope, next week15:19
bswartzokay that's what I expected15:20
bswartzand the NetApp driver too?15:20
bswartzany issues with NetApp cmode other than LDAP support?15:20
vponomaryovwe need to test it with all variants of environment15:21
vponomaryovactive directory, ldap, kerberos15:21
*** kevinconway has joined #openstack-meeting-alt15:21
bswartzokay15:21
vponomaryovif we are successfull, next week too15:21
bswartzokay let's hope for no problems15:22
* bswartz crosses his fingers15:22
bswartz#topic generic driver15:22
*** openstack changes topic to "generic driver (Meeting topic: manila)"15:22
bswartzokay what's preventing the generic driver from being production ready?15:23
bswartzis it mostly performance limitations?15:23
aostapenkoyes15:23
*** pballand has joined #openstack-meeting-alt15:23
bswartzis running NFSD in a VM inherently slower than running it on bare metal?15:24
caitlin56poor performance even with a single vserver?15:24
bswartzis it a question of the backend performance w/ Cinder?15:24
vponomaryovalso, if we restart manila, it should validate service vm15:24
vponomaryoveach share one by one15:25
vponomaryovand it is take a while15:25
bswartzI realize that a whitebox file server running open source software will not really compete with custom hardware/software, but I'd like the generic driver to be at least as good as other pure OSS approaches on comparable hardware15:25
vponomaryovif we try create something during this period, we get fail15:25
vbellurhow bad is the performance with the generic driver at the moment?15:25
*** mattgriffin has joined #openstack-meeting-alt15:25
aostapenkoif we find good light image for service vm it will be much better15:26
achirkoBecause of using cinder to provide volumes and nova for vservers we introducing additional layer (abstraction and resources utilization) compare to some cool back-end15:26
bswartzMaybe during Juno we can undertake a manila-generic-performance-enhancement project15:27
*** caitlin56 has quit IRC15:27
csabahow far is it down on the road that container-based service vm becomes feasible?15:27
vponomaryovvbellur: after using manila-compute for this, it is endless waiting =)15:27
*** caitlin56 has joined #openstack-meeting-alt15:27
vbellurvponomaryov: ok, I feel the performance impact now :)15:27
bswartzachirko there are cinder backends that can serve local storage though -- those should dramatically reduce bottlenecks related to remote backends15:27
vbellurcsaba: that is a good point., might help address the restart case15:28
*** jmontemayor has joined #openstack-meeting-alt15:28
achirkocsaba: as far as I know containers do not support run-time volumes attachment, so it can be a blocker15:28
vponomaryovachirko: also no NFS for containers, in repositories15:29
bswartzwell there's no kernel NFS but userspace NFS is not looking so bad15:29
aostapenkono nfs kernel server for containers15:30
vponomaryovwill be right, nfs kernel server won't work with containers15:30
bswartzIn fact I'd like to talk about userspace NFS and gateways15:30
vbelluryeah, we could try with Ganesha or Gluster NFS within a container15:30
bswartz#topic gateways15:30
*** openstack changes topic to "gateways (Meeting topic: manila)"15:30
bswartzokay so there are a number of backends which can't natively support multitenancy with segmented VLANs15:31
vponomaryovvbellur: if we have cirros with userspace nfs and samba, so it will be breakthrough15:31
xyang1vbellur: has anyone tried Ganesha?  Seems very buggy to me.15:31
bswartzxyang1: it's under active development -- are you sure you're running the latest stable branch?15:32
vbellurxyang1: we have been playing around with it (both v1.5 and v2)15:32
xyang1bswartz: I think so.15:32
vponomaryovxyang1: +1, itworks on CentOS and similar to it, not on debian, as for me15:32
xyang1vponomaryov: I tried on debian15:33
bswartzmy current idea for gateways looks very similar to the generic driver15:33
vbellurxyang1: and we have been able to run reasonable tests15:33
xyang1vbellur: ok, good to know.15:33
bswartzthe server that will be visible to the tenant will be something like ganesha-nfs, either running in a VM or somewhere that has a network interface on the tenant's VLAN15:34
bswartzganesha-nfs will in turn be a client of the real backend15:34
vbellurbswartz: sounds feasible to me15:35
bswartzso if you have a giant clustered filesystem, ganesha will re-export some subtree of the namespace15:35
*** krtaylor has quit IRC15:35
*** DennyZhang has joined #openstack-meeting-alt15:35
vbellurbswartz: right..15:35
xyang1vbellur: are you running ganesha-nfs in a container or VM?15:36
bswartzthe gateway could in principle be a full HVM, or a container-based VM, or just a process running on a hypervisor node -- the key would be that it would need dual network connectivity -- to the tenant VLAN on one side and to the backend storage network on the other side15:36
vbellurxyang1: VM and bare metal too15:36
xyang1vbellur: I tried in a container, maybe that's why I had problems.15:37
bswartzthere's potential for resuing a bunch of the code that's been written for the generic driver15:37
vbellurxyang1: worth a try in a VM15:37
xyang1vbellur: sure15:37
bswartzas we get some of the drivers wrapped up I'd like ot move onto prototyping the gateway-based multitenancy15:38
bswartzprobably a few weeks from now15:38
bswartzso anyone who is interested get ready to participate15:38
vbellurbswartz: we are exploring Ganesha on similar lines15:38
bswartzor go ahead and start whipping up some prototypes so we'll have something to look at in a few weeks15:38
vbellurcsaba did open a blueprint but I guess it is titled hypervisor mediated ...15:38
bswartzvbellur: oh I need to review the current BPs15:39
*** boris-42_ has quit IRC15:39
vbelluron nomenclature - what should we call this scheme? gateway or hypervisor? gateway seems more generic to me.15:39
bswartzI like gateway, since it doesn't preclude any approach that I can think of15:39
caitlin56+1 to gateway. It is more general, and the hypervisor is a gateway.15:39
bswartz+115:40
vbellurok, we will rename the blue print.15:40
bswartzvbellur: ty15:40
bswartz#topic incubation15:40
*** openstack changes topic to "incubation (Meeting topic: manila)"15:40
bswartzokay so many of you will remember that the TC felt manila was not ready for incubation last november15:41
*** jdob has quit IRC15:41
bswartzGiven how much work we've needed to do on multitenancy I think they were correct15:41
vbellurbswartz: agree15:41
bswartzbut I'm now hopeful that we'll have working multitenancy by Icehouse15:41
bswartzand there is another hurdle that the TC threw in front of us15:42
bswartzthey want to see that Manila is production-ready -- which implies that someone somewhere is actually running it in production15:42
bswartzso I wanted to ask the community if there are any organizations interested in being early deployers15:42
*** doug_shelley66 has quit IRC15:43
bswartzNetApp definitely is interested, but hardware and people are needed and I'm not sure that NetApp is best equipped to do this quickly15:43
vbellurbswartz: there was some interest expressed in the openstack ML, we can try reaching out to those folks too.15:44
bswartzyeah I don't think group is the right group to ask -- but I wanted to put the word out that we're looking for a "beta" site so to speak15:44
vponomaryovvbellur: which mailing list group are you talking about?15:44
bswartzwe need someone who wants the services that Manila offers and is willing to deal with the pain of deploying brand new code15:45
vbellurvponomaryov: openstack@lists.openstack.org - the user ML15:45
*** doug_shelley66 has joined #openstack-meeting-alt15:46
bswartzafter real drivers are available this will matter more15:46
vbellurbswartz: yeah, we can possibly seek out testing help from the community. that would be a natural way of converting those test deployments to real ones.15:46
bswartzit's not urgent, but I wanted everyone to be aware that the TC considers this a condition for incubation15:46
vbellurnot sure how many noticed the barbican incubation request on openstack-dev ML15:46
bswartzI did not15:46
bswartzanything interesting?15:47
vbellurquite a bit, let me try to post a link to that thread15:47
vbellurhere it is - http://lists.openstack.org/pipermail/openstack-dev/2013-December/020924.html15:47
bswartzvbellur: ty15:47
vbellurdoes give a good idea on the factors that TC considers for incubation15:48
*** codekobe has joined #openstack-meeting-alt15:48
bswartz#topic open discussion15:48
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:48
bswartzalright we have some time for anything else15:48
*** ViswaV has joined #openstack-meeting-alt15:49
csabalet me ask a silly question15:49
csabahow do we exaclty define multi-tenancy in this context?15:49
bswartzcsaba: that's not a silly question! that's a good question15:49
vponomaryovcsaba: separated resources for each tenant15:50
csabaie. in what way is gluster , lvm ,etc considered single-tennant capalbe15:50
csabawhen they can serve multiple tenants as subnets15:50
bswartzwhen we talk about multitenancy, we're referring to an environment where different tenants have compute resources in segmented networks so they're securely isolated from eachother15:51
*** rakhmerov has joined #openstack-meeting-alt15:51
bswartzmultitenancy is about making sure that different users cannot perceive eachother's existence and cannot interfere with eachother intentionally or unintentionally15:51
vponomaryovalso isolated ip rules for NFS15:52
bswartzVLANs are the typical approach for isolating the network, but there are other perfectly valid approaches15:52
bswartzsuch as GRE tunnels or VXLANs15:52
*** MarkAtwood has joined #openstack-meeting-alt15:53
*** esker has quit IRC15:53
*** dhellmann is now known as dhellmann_15:53
bill_azbswartz:  do you consider vlan isoloation sufficient isolation for multi-tenancy?15:53
*** esker has joined #openstack-meeting-alt15:53
bill_az(isolation)15:53
bswartzthe main limitation with some shared filesystems (GlusterFS, CephFS, GPFS, and Isilon NFS are the ones I know about) is that they only support a single security domain15:53
csabaoh so simply IP ranges (in the same network) with fw/export rules to control access to resources is too poor separation to call it multi-tenancy?15:53
*** ViswaV has quit IRC15:54
caitlin56The latter are becoming omore common, you run out of VLANs way too quickly.15:54
*** DennyZha` has joined #openstack-meeting-alt15:54
bswartzcsaba: yes access rules aren't sufficient because they assume a single IP routing domain and a common set of usernames/passwords15:55
*** jcoufal has quit IRC15:55
*** DennyZhang has quit IRC15:55
caitlin56csaba: the real question is do you have mount control, and prevention of stealing mount handles. IF you could do that without network separation that *would* work.15:55
bswartzit's possible for tenant A to have a VM on 10.10.10.10 and for tenant B to also have a tenant VM on 10.10.10.10 and for those IP addresses to be completely different15:55
caitlin56separate logical networks is a lot simpler.15:55
*** jdob has joined #openstack-meeting-alt15:55
bswartzit's also possible for tenant A to have a user called "bswartz" and tenant B to have a user called "bswartz" who is totally different15:55
*** gokrokve has quit IRC15:56
*** jcooley_ has joined #openstack-meeting-alt15:57
*** banix has quit IRC15:57
csabais there an advantage of ip collisions?15:58
bswartznote that there are cases when less-secure tenant isolation would be acceptable15:58
*** thinrichs has joined #openstack-meeting-alt15:58
*** esker has quit IRC15:58
bswartzcsaba: there's no advantage -- it's just unavoidable at scale due to the small space of IPv4 addresses15:58
caitlin56csaba: you cannot tell Tenant A that they cannot ue IP addressX because tenant B is using it.15:58
*** Duane_ has joined #openstack-meeting-alt15:58
*** glucas has left #openstack-meeting-alt15:58
vbellurcsaba: a tenant would be unaware of resource utilization by other tenants15:59
csabaah I get it15:59
*** DennyZha` has quit IRC15:59
bswartzokay our time is up15:59
bswartzthat was a good question csaba16:00
vbellurquick qn - should we do a 0.1 release of manila after generic driver is in?16:00
csabathx the answers16:00
*** jmontemayor has quit IRC16:00
*** s3wong has joined #openstack-meeting-alt16:00
bswartzsee you all next week when we hope to have the drivers merged!16:00
vbellurthanks16:00
bswartz#endmeeting16:00
*** caitlin56 has quit IRC16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Jan 23 16:00:32 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
aostapenkothanks, bye. Viva La Revolucion16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-01-23-15.02.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-01-23-15.02.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-01-23-15.02.log.html16:00
*** gregsfortytwo1 has left #openstack-meeting-alt16:00
*** vbellur has left #openstack-meeting-alt16:00
mesteryhi16:00
*** achirko has quit IRC16:00
*** michsmit has joined #openstack-meeting-alt16:01
mestery#startmeeting networking_policy16:01
openstackMeeting started Thu Jan 23 16:01:06 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: networking_policy)"16:01
openstackThe meeting name has been set to 'networking_policy'16:01
*** aostapenko has left #openstack-meeting-alt16:01
thinrichsHi16:01
*** banix has joined #openstack-meeting-alt16:01
mesterythinrichs: Hows it going?16:01
*** jmontemayor has joined #openstack-meeting-alt16:01
mesteryhi banix!16:01
thinrichsGood--busy as always.  How about you?16:01
*** akerr has left #openstack-meeting-alt16:01
mesterymichsmit: yo!16:01
*** michael-yu has joined #openstack-meeting-alt16:01
mesterythinrichs: Busy but happy :)16:01
banixmestery: hi16:02
michsmithi16:02
banixhi everybody16:02
*** jmontemayor has quit IRC16:02
mestery#link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy Agenda16:02
s3wonghello16:02
*** songole_ has joined #openstack-meeting-alt16:02
mesterys3wong: Greetings!16:02
songole_Hi all16:02
mesteryLooks like we have most of the team here.16:02
mesterysongole_: howdy!16:02
*** jmontemayor has joined #openstack-meeting-alt16:02
*** Duane__ has quit IRC16:02
*** Duane___ has joined #openstack-meeting-alt16:02
mestery#topic Action Item Review16:03
*** openstack changes topic to "Action Item Review (Meeting topic: networking_policy)"16:03
*** prasadv has joined #openstack-meeting-alt16:03
mesterySo, I setup a shared github for the PoC work for now.16:04
mesteryI was thinking we could just use a github and merge code there, and then formulate patches for upstream later.16:04
mesteryThoughts?16:04
mestery#link https://github.com/mestery/neutron/tree/group_policy Shared github repository16:04
s3wongmestery: sounds good16:04
banixmestery: Thanks. Sounds good.16:04
mesteryCool!16:04
prasadvmestery: that sounds good16:04
mesterySo, it's just a clone of upstream Neutron for now, next step is to get the APIs in there I think. :)16:04
mesteryOne more action item to review16:05
mesteryThanks to s3wong for setting up the API document16:05
mestery#link https://docs.google.com/a/mestery.com/document/d/1b_ywmSTKYW4PBjhkXREPePRgVmz-Uwv_Bb-i7Jaqsu4/edit API Document16:05
*** rraja has quit IRC16:05
*** Duane_ has quit IRC16:05
mesterySo, review comments on that document appreciated by folks.16:06
s3wongyes, please16:06
s3wongand if anyone else wants editing right, please let me know as well (just send request via document)16:07
mesteryThanks s3wong.16:07
mestery#topic PoC16:07
*** openstack changes topic to "PoC (Meeting topic: networking_policy)"16:07
*** csaba is now known as csaba|afk16:07
mesterys3wong: Do you have enough info to start coding up the APIs now?16:07
s3wongmestery: yes, so I will be doing that over the next week or so16:08
mesterys3wong: Great! I'll start looking at the agent side as well for actually implementing things in OVS as well.16:08
banixI have *just* started coding the model (the db tables).16:08
s3wong(hopefully, other than songole, everyone else can do their part without waiting on me to finish)16:08
*** marun has joined #openstack-meeting-alt16:08
songole_s3wong: any access restrictions on APIs. admin vs tenant I suppose none.16:08
s3wongsongole: for now, I don't see any16:09
mesterybanix: Great! I'll start the agent stuff as well then.16:09
banixlooks like for now the policy is defined within a tenant16:09
banixIs that right? Anything we need to do to have policies defined across tenants? Are we assuming the admin could do that16:10
prasadvi think if keystone scoping allows then apis should be allowed right?16:10
songole_A tenant could only specify an endpoint in his domain?16:11
s3wongbanix: I don't think there is anything we defined so far that is cross-tenant. Did I miss something?16:11
mesteryprasadv: I think that makes sense, in which case admin would be able to work across tenants through keystone16:11
banixs3wong: you are correct16:11
banixMay be not right now but something to think about / discuss.16:11
thinrichsWould there ever be a need for an admin to impose network-wide policies, i.e. that apply to every tenant?16:11
banixprasadv, mestery: agree16:12
*** rnirmal has joined #openstack-meeting-alt16:12
s3wongI guess just "external network", if we put that into an endpoint group... (and expecting the group-policy implementation to say create a port on provider router)16:12
*** tanisdl has joined #openstack-meeting-alt16:12
banixyeah admin will be able to say see endpoints / groups defined by different tenants16:12
mesterys3wong: Makes sense16:12
*** ashaikh has joined #openstack-meeting-alt16:13
*** SushilKM has joined #openstack-meeting-alt16:13
prasadvi guess there could be an issue when there is a conflict between what admin configures and say another role restericted to tenant configures16:13
*** aignatov is now known as aignatov_16:13
*** SushilKM has left #openstack-meeting-alt16:14
prasadvwhich one takes precedence?16:14
mesteryprasadv: That gets into the conflict resolution stuff we talked about a few weeks back I think.16:14
banixprasadv: So we had a simple conflict resolution mechanism16:15
banixthat should apply regardless of admin/tenant. Right?16:15
thinrichsBut I think prasadv brings up an interesting case.16:15
prasadvok. I am thinking this is more of authorization policy right?16:15
*** marun has quit IRC16:15
s3wongprasadv: that is an interesting case - so admin has some security group setup, and tenant's policy conflict with it?16:15
thinrichsWe wouldn't want our admin to say 'drop', and the tenant to say 'allow', and for the tenant to win out.16:15
s3wongI would guess in that case, admin will win?16:15
mesteryI think in this particular case, keystone policy would have to win out.16:16
thinrichss3wong: that's what we'd want, but right now there's no mechanism for that.16:16
prasadvmaybe this should be resolved by keystone and not by individual Openstack components16:16
mesterye.g. the admin user's group policy configuration supercedes the tenants16:16
mesteryprasadv: Yes, that exactly.16:16
banixmestery: but keystone won't be involved ...16:16
banixmestery: ok16:16
s3wongmestery: that makes the most sense16:17
banixprasadv: I am not sure I see how this works16:17
thinrichsI'm confused: so Keystone is now accepting these policy rules we're creating here?16:17
banixkeystone is not really involved. Is it?16:17
prasadvwhat I mean is whether a user has higher precence in terms of authorization is done by keystone16:17
prasadvsay admin supercedes tenant role16:18
banixprasadv: You are saying keystone is consulted for conflict resolution?16:18
mesteryWhen policies are created, won't they will have keystone auth attached to them, right?16:18
prasadvnot sure now where this role based conflict resolution takes place16:19
prasadvi am sure this is not just a problem for neutron alone. This is a common problem across all of openstack right?16:19
banixmestery: Ok, carry on16:19
thinrichsprasadv: I'm guessing the implementation has to ensure that the policy it eventually enforces takes all these conflict resolution schemes into account.16:19
thinrichsIs it possible for 2 different tenant policies to conflict?  Both tenants having VMs on the same machine or something?16:20
thinrichsIf so, the keystone-based conflict resolution won't work.16:20
*** marun has joined #openstack-meeting-alt16:20
mesteryAPI calls into Neutron have tenant information attached banix, so we may need to take that into account when doing policy resolution is what I was thinking.16:20
mesterythinrichs: I think tenant roles need to be factored into the conflict resolution, but it's not the final resolution story for sure.16:21
s3wongmestery: so conflict resolution is done at the API layer here?16:21
*** michael-yu has quit IRC16:21
mesteryAt least for tenant resolution, maybe it has to be s3wong?16:21
s3wongmestery: it appears so, actually16:22
banixmestery: so at the creation of policy conflicts are detected?16:22
mesterybanix: For tenant conflicts, maybe it has to be done then, yes.16:22
banixI see what you are saying16:22
thinrichsWhy do we need to resolve conflicts within the API?  Can we have the API just create a bunch of policies with IDs attached, and the implementation compiles that down into the real policy it is implementing?16:23
*** jtomasek has quit IRC16:23
s3wongbanix: more interestingly, if tenant has an 'allow', then later on admin adds an 'deny', we would have to find a way to inform tenant his policy fails?16:23
mesterythinrichs: That is the other approach I was thinking yes, not sure which approach has advantages.16:23
songole_thinrichs: agree16:23
banixso if assume admin creates a policy after a tenant has already created a policy and there is conflict, something we need to figure out what to do then.16:23
banixs3wong: that's what i was think about16:24
thinrichsWe might need that more dynamic version anyway because users can change roles, which would require eliminating conflicts again.  We wouldn't want to lose the policy rules they sent in initially.16:24
prasadvthinrichs: shouldnt we just limit it during creation? instead of doing it dynamically?16:25
thinrichsWhat would happen if a user changes roles *after* they finished inserting their policies but they didn't login again?  Would Neutron even know their roles changed and that conflict resolution should be revisited?16:25
banixSo just to narrow down the problem, our simple resolution method would be fine within a tenant. with checks done at policy creation time. Agree?16:25
thinrichsprasadv: Not sure--trying to understand the tradeoffs.16:25
thinrichsbanix: not sure we'd do it at policy creation time.16:26
songole_There could be pert issues with dynamic conflict resolution.16:26
mesterythinrichs: Is there a workflow in Horizon/CLI to change a users role? I'm asking because I don't know off-hand.16:26
thinrichsbanix: Suppose two classifiers overlap--do we reject the policy?16:26
*** marun has quit IRC16:26
thinrichsmestery: I don't know--I assumed user roles could change.16:26
prasadvi think keystone provides user to be put into different roles16:27
mesterythinrichs: I'm asking because we may be boiling the ocean here without knowing hte workflow in existing OpenStack use cases. :)16:27
mesterythinrichs: Want to take an action item to figure that out?16:27
banixthinrichs: yes16:27
mesterythinrichs: It would help us with resolution I think. :)16:27
*** marun has joined #openstack-meeting-alt16:27
thinrichsbanix: Is it always easy to determine if classifiers overlap?16:28
*** tanisdl has quit IRC16:28
banixthat would be a good idea.16:28
thinrichsmestery: I'll figure out if roles can be changed in Keystone.16:28
*** nati_ueno has quit IRC16:28
banixto look into this more closely16:28
mestery#action thinrichs to determine if roles can be changed in keystone16:28
mesterythanks thinrichs!16:28
thinrichsNP16:28
mesteryOK, lets move on from that discussion until we figure out the underlying keystone stuff for next week.16:28
banixmestery: agree16:29
s3wongmestery: yes16:29
s3wongconflict resolution is an ongoing topic16:29
mesteryOK, what else to discuss with regards to PoC this week?16:29
mesteryAnything else?16:29
banixIt is really cold around here :)16:29
mesterybanix: So cold school was canceled again today :)16:30
s3wongbanix: New York?16:30
mesteryMinnesota here16:30
banixs3wong: yes16:30
* s3wong enjoying sunny California16:30
*** marun has quit IRC16:30
banixDidn't hear the last sentence :)16:30
thinrichsBTW here's the info on Keystone.16:30
mesterys3wong: :P16:30
thinrichsuser-project roles can be changed on the fly: http://docs.openstack.org/user-guide-admin/content/admin_cli_manage_projects_users.html16:30
mesterythinrichs: that was fast!16:30
thinrichsHad some help.16:31
mesterythinrichs: :)16:31
s3wongthinrichs: seems like we need a mechanism to inform tenants that their policies may be invalidated16:31
mesterys3wong: My thoughts exactly16:32
banixLet us think more about conflict resolution and perhaps discuss on ML?16:32
banixs3wong: Getting complicated16:32
prasadvs3wong, mestery: Isnt this a Openstack infrastrcuture issue and not just networking?16:32
mesterybanix: Agreed!16:32
mesteryprasadv: Yes16:33
mesterybanix: Want to start the thread for the group on the ML?16:33
s3wongand to avoid confusion, in an event of invalidation, I would say all policies need to be invalidated16:33
*** rakhmerov1 has joined #openstack-meeting-alt16:33
s3wongfor that tenant16:33
*** rakhmerov has quit IRC16:33
thinrichsAgreed to take it to the ML.16:33
*** coolsvap is now known as coolsvap_away16:33
s3wongML it is!16:33
mestery#action banix to start discussion around role changes on the ML16:33
mesteryAnything else for this week with regards to PoC?16:34
banixWill do16:34
s3wongHappy coding, guys :-)16:34
mesterys3wong! Ha!16:34
mestery#topic Open Discussion16:34
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"16:34
mesteryAnything else or should we call it early this week?16:34
banixThinrichs: Needless to say, please feel free to post to the ML regarding this.16:35
s3wonganother quick meeting, three in a row!16:35
mesteryYes!16:35
mesteryOK, lets see what we can get done with regards to PoC code for next week then.16:35
banixSounds good16:35
mesteryThanks everyone!16:35
mestery#endmeeting16:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:35
openstackMeeting ended Thu Jan 23 16:35:30 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-01-23-16.01.html16:35
s3wongThanks16:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-01-23-16.01.txt16:35
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-01-23-16.01.log.html16:35
songole_thanks16:35
*** songole_ has quit IRC16:35
*** prasadv has quit IRC16:35
*** coolsvap_away is now known as coolsvap16:35
*** michsmit has left #openstack-meeting-alt16:36
*** coolsvap is now known as coolsvap_away16:37
*** rushiagr has left #openstack-meeting-alt16:38
*** thinrichs has quit IRC16:38
*** glucas has joined #openstack-meeting-alt16:40
*** codekobe has left #openstack-meeting-alt16:40
*** amotoki is now known as amotoki_zzz16:46
*** vponomaryov has left #openstack-meeting-alt16:47
*** jmontemayor has quit IRC16:47
*** Barker has quit IRC16:47
*** jmontemayor has joined #openstack-meeting-alt16:49
*** safchain has quit IRC16:50
*** pballand has quit IRC16:52
*** Barker has joined #openstack-meeting-alt16:53
*** s3wong has quit IRC16:54
*** ashaikh has quit IRC16:57
*** mclarenst has quit IRC16:57
*** NikitaKonovalov is now known as NikitaKonovalov_16:58
*** coolsvap_away is now known as coolsvap16:59
*** kevinconway_ has joined #openstack-meeting-alt17:00
*** kevinconway has quit IRC17:00
*** kevinconway_ is now known as kevinconway17:00
*** boris-42 has joined #openstack-meeting-alt17:02
*** pdmars_ has joined #openstack-meeting-alt17:02
*** pdmars has quit IRC17:02
*** Duane_ has joined #openstack-meeting-alt17:03
*** SergeyLukjanov is now known as SergeyLukjanov_17:03
*** Duane___ has quit IRC17:06
*** yamahata has quit IRC17:07
*** marios is now known as marios|gone17:07
*** DinaBelova is now known as DinaBelova_17:08
*** markwash has joined #openstack-meeting-alt17:11
*** lsmola_ has quit IRC17:13
*** dprince has joined #openstack-meeting-alt17:13
*** yportnova_ has quit IRC17:15
*** colinmcnamara has joined #openstack-meeting-alt17:15
*** glucas has left #openstack-meeting-alt17:16
*** pballand has joined #openstack-meeting-alt17:17
*** krtaylor has joined #openstack-meeting-alt17:18
*** sbalukoff has quit IRC17:24
*** bdpayne has joined #openstack-meeting-alt17:27
*** pdmars_ has quit IRC17:29
*** pdmars has joined #openstack-meeting-alt17:29
*** demorris has quit IRC17:30
*** pdmars has quit IRC17:34
*** tanisdl has joined #openstack-meeting-alt17:44
*** ashaikh has joined #openstack-meeting-alt17:44
*** johnthetubaguy has quit IRC17:49
*** amcrn has joined #openstack-meeting-alt17:50
*** pcarver has quit IRC17:51
*** yamahata has joined #openstack-meeting-alt17:53
*** ndipanov is now known as ndipanov_gone17:53
*** crobertsrh has joined #openstack-meeting-alt17:56
*** ErikB has joined #openstack-meeting-alt17:56
*** dmitryme has joined #openstack-meeting-alt17:58
*** ViswaV has joined #openstack-meeting-alt17:59
*** rakhmerov1 has quit IRC18:00
*** derekh has quit IRC18:00
*** nati_ueno has joined #openstack-meeting-alt18:00
*** alazarev has joined #openstack-meeting-alt18:01
*** mattf has joined #openstack-meeting-alt18:01
*** bob_nettleton has joined #openstack-meeting-alt18:01
*** aignatov_ is now known as aignatov18:02
*** MarkAtwood has quit IRC18:03
*** MarkAtwood has joined #openstack-meeting-alt18:03
*** SergeyLukjanov_ is now known as SergeyLukjanov18:06
SergeyLukjanovsavanna folks around?18:06
dmitrymeyup18:06
ErikBHere18:06
crobertsrhyup18:07
SergeyLukjanovok, looks like we have a quorum18:07
SergeyLukjanov#startmeeting savanna18:07
openstackMeeting started Thu Jan 23 18:07:28 2014 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:07
*** openstack changes topic to " (Meeting topic: savanna)"18:07
openstackThe meeting name has been set to 'savanna'18:07
*** DinaBelova_ is now known as DinaBelova18:07
SergeyLukjanov#topic Agenda18:08
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:08
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_January.2C_2318:08
*** MarkAtwood has quit IRC18:08
SergeyLukjanovaction items are partially resolved18:08
SergeyLukjanovwill make an update next time18:08
SergeyLukjanov#topic Icehouse-2 dev milestone18:08
*** openstack changes topic to "Icehouse-2 dev milestone (Meeting topic: savanna)"18:08
*** tmckay has joined #openstack-meeting-alt18:08
*** MarkAtwood has joined #openstack-meeting-alt18:09
SergeyLukjanov#link http://lists.openstack.org/pipermail/openstack-dev/2014-January/025250.html18:09
SergeyLukjanovyou can find links and details in this email18:09
SergeyLukjanovwe've successfully delivered icehouse-2 with mostly all planned features and bugs fixed18:09
SergeyLukjanovso, my congratulations!18:10
*** harlowja_away is now known as harlowja18:10
mattfcongrats all!18:10
*** jmontemayor has quit IRC18:10
*** jmaron has joined #openstack-meeting-alt18:10
ErikBGreat job everyone!18:10
*** jmontemayor has joined #openstack-meeting-alt18:10
SergeyLukjanovit's our second dev milestone18:10
mattfit's terrific to see all the progress on heat integration18:11
aignatovhurrrah!18:11
alazarevcongrats!18:11
SergeyLukjanovit was handled by ttx18:11
SergeyLukjanovfor the main savanna project18:11
SergeyLukjanovok, let's move on18:11
SergeyLukjanov#topic News / updates18:12
*** openstack changes topic to "News / updates (Meeting topic: savanna)"18:12
SergeyLukjanovfolks, please18:12
SergeyLukjanovshare news18:12
*** luqas has quit IRC18:12
SergeyLukjanovpreferably good news, because I have some bad ones18:12
*** MarkAtwood has quit IRC18:12
crobertsrhUI part of java actions and HDFS are up for review, seem positive so far.18:12
mattfjust a few -create cli commands short of having full coverage of the v1.1 api18:12
ErikBOn the HDP side, we are moving forward with EDP change, Blueprints, DiskBuilder and docs18:12
tmckayI'm looking at more Oozie actions now, streaming mapreduce first18:12
*** codekobe has joined #openstack-meeting-alt18:13
dmitrymeI'am replacing SSH configuring with the guest agent18:13
aignatovcontinue working on Heat integration polishing, fixing some bugs, also yesterday I've realised that savanna heat engine does;t working with heat in master18:13
SergeyLukjanovErikB, that's awesome to hear about dib elements for HDP18:14
aignatovbecause of https://bugs.launchpad.net/heat/+bug/127159718:14
alazarevI'm working on blogpost about data locality support, hopefully will be published soon18:14
ErikBSergeyLukjanov, will be a good change and Bob should me merging shortly.18:14
*** nadya__ has joined #openstack-meeting-alt18:14
aignatovbut seems the bug will be fixed in the heat side soon18:15
bob_nettletonI hope to submit a patch for the HDP DIB elements sometime over the next few days.18:15
aignatovbob_nettleton: awesome!!18:15
SergeyLukjanovbob_nettleton, awesome, ping me or mattf if any questions18:15
bob_nettletongreat. thanks!18:15
* mattf gets his meat grinder ready18:16
ErikBSergeyLukjanov, what is the bad news…18:16
SergeyLukjanovthe bad news are about Savanna project naming18:16
mattfforcing us to add a trailing h?18:16
ErikB;-)18:16
dmitrymemattf, lol18:16
SergeyLukjanovI've contacted OpenStack Foundation marketing team to ensure that we're using consumable names18:16
* mattf hands out Gs Ns and Us18:17
* SergeyLukjanov looking for the bad link18:17
SergeyLukjanovaaaaand18:17
SergeyLukjanov#link http://www.thetus.com/savanna18:17
*** sbalukoff has joined #openstack-meeting-alt18:17
mattfother than savannah, we're almost past out painful name collision with "havana"18:17
SergeyLukjanovmattf, yep, but it's not so bad18:18
aignatov:-( so we should rename our wonderful project Savanna, right?18:18
SergeyLukjanovaignatov, yep18:18
* mattf groans18:18
SergeyLukjanovand we should at least find the new name in next 2-4 weeks18:18
*** yogesh has joined #openstack-meeting-alt18:19
SergeyLukjanovto be able to rename the world before the graduation review18:19
mattfSergeyLukjanov, have a pointer to the trademark registration?18:19
aignatovproposing new name - Saratov :)18:19
SergeyLukjanovmattf, their project was released first time Feb 201018:19
SergeyLukjanovand so it's at least bad to use the same name18:19
SergeyLukjanovbecause it's a project in the same area - cloud, hadoop18:20
DinaBelovaSergeyLukjanov you may combine the fact you need new name with the fact you are not only Hadoop now - you are "Data processing" OS program18:20
DinaBelovaSergeyLukjanov, and elephants topic (Savanna) seems to be not right now, really :)18:20
SergeyLukjanovthat's the only pros I see...18:20
DinaBelovaso maybe renaming is a good idea anyway18:20
SergeyLukjanovnope, I really love the Savanna naming!18:21
DinaBelova:D18:21
aignatovit could be an elephant topic still, why not?18:21
alazarevwe can use 'Savannah' :D18:21
SergeyLukjanovI dislike h18:21
mattfSergeyLukjanov, do they have a trademark on the name Savanna, is the os foundation going to acquire a trademark on our name?18:21
SergeyLukjanovmattf, I'll clarify that18:21
tmckayHow about "Grassland" ? :)18:21
SergeyLukjanov:)18:22
tmckayStackVanna?18:22
aignatovlol!18:22
SergeyLukjanovI'll start a ML thread when ensure all details18:22
SergeyLukjanovand we'll try to find the better name18:23
SergeyLukjanovthan npthing ;)18:23
SergeyLukjanovI hope that will find the great naming that'll be ok for all ofus18:23
alazarevwe should at least 1. check is Savanna is really registered 2. contact thetus and try to buy name18:23
mattfis there an existing trademark on Savanna? is the openstack foundation going to trademark our eventual name?18:23
*** coolsvap has quit IRC18:23
SergeyLukjanovmattf, I'll ask foundation about that18:24
SergeyLukjanovdon't worry :)18:24
mattfthis is going to be especially rough on ErikB, who still uses quantum18:24
*** coolsvap has joined #openstack-meeting-alt18:24
mattfErikB, we're here to help18:24
*** Ranjitha has joined #openstack-meeting-alt18:25
DinaBelovaEven Google don't know about these Thetus Savanna :) Try "cloud hadoop savanna" - you'll see only your Savanna18:25
DinaBelovadon't -> doesn't18:26
mattfthis stuff is best left to the lawyers, but we definitely should jump ship on the name unless we have a solid reason18:26
SergeyLukjanovDinaBelova, that's right, but it looks like it'll not help us :(18:26
SergeyLukjanovheh, so, to summarize18:27
SergeyLukjanovI'll talk again with foundation folks to clarify stuff18:27
SergeyLukjanovand than start a mailing thread (if needed) to find the name18:28
SergeyLukjanovlet's move on18:28
SergeyLukjanov#topic Meeting re-org18:28
*** openstack changes topic to "Meeting re-org (Meeting topic: savanna)"18:28
*** michael-yu has joined #openstack-meeting-alt18:28
SergeyLukjanovI was thinking about how our meeting working now and have some ideas18:28
SergeyLukjanovI'd like to share them and receive some feedback18:28
*** nadya__ has quit IRC18:29
SergeyLukjanov#1 add topics with topic chairs how will be responsible for them18:29
SergeyLukjanovlike Heat integration update or CI status18:29
aignatovhow->who?18:29
*** nadya__ has joined #openstack-meeting-alt18:29
SergeyLukjanovyep18:29
SergeyLukjanovit could contain about 1-2 sentences with short clearly defined status news18:30
SergeyLukjanovstatus/news18:30
SergeyLukjanovidea #2:18:30
SergeyLukjanovheh, I completely forgot the second idea18:30
SergeyLukjanovany thoughts on the first one?18:30
mattfi guess we can settle #2 then18:30
*** michael-yu has quit IRC18:31
SergeyLukjanov:)18:31
*** jcooley_ has quit IRC18:31
mattf#1 could just be a rundown of active bps, each has an assignee18:31
*** colinmcnamara has quit IRC18:31
aignatovwhat is the difference between idea1 and what is happening right now when we just say news/updates?18:31
mattfi think we get the information into the minutes anyway. if there's value in structuring it more, i'm ok witht hat18:31
*** rakhmerov has joined #openstack-meeting-alt18:32
*** michael-yu has joined #openstack-meeting-alt18:32
aignatovChad works on the UI, he updates us about it, Trevor owirks on EDP, he updates us, I work on Heat, I update you18:32
aignatovowirks -> works :)18:33
SergeyLukjanovaignatov, that's correct18:33
*** NikitaKonovalov_ is now known as NikitaKonovalov18:33
SergeyLukjanovthe idea was to ensure that all parts are covered18:33
alazarevI also don't see difference with what we have right now18:33
*** DinaBelova is now known as DinaBelova_18:33
SergeyLukjanovfor example I'd like to see CI status updates18:33
mattfafaict #1 is some added structure, seems low overhead, but the added value hasn't been articulated yet18:34
SergeyLukjanovprobably structuring is overcomplexity18:34
alazarevSergeyLukjanov: if you like CI updates - you can always ask about it18:34
SergeyLukjanovalazarev, I'd like to avoid pings, just short updates18:34
SergeyLukjanovbecause we already have enough stuff that could be shared weekly18:35
SergeyLukjanovso, currently it looks for me that we could distribute interesting topics between folks and everyone will now what should he/she cover18:35
SergeyLukjanovand will be able to prepare18:36
SergeyLukjanovfor ex.18:36
SergeyLukjanovif you really  dislike such idea18:36
SergeyLukjanovwrite about it :)18:36
SergeyLukjanovany thoughts?18:37
mattfi'm ambivalent18:38
ErikBsame here18:38
alazarevsounds reasonable, the only thing needed is a list of topics with assignments, don't think that we need some kind of ball passing18:38
jmaronI'm ambi-normal18:38
crobertsrhSeems like it's worth a shot.  Maybe it will help someone with something.  If not, we can always change back.18:38
aignatovwell, I still do not see the much difference, but we can try, maybe I didn't get your idea18:39
SergeyLukjanovalazarev, sure, w/o ball passing, just updates18:39
*** cweid has quit IRC18:39
SergeyLukjanovaignatov, I'd like to ensure that we have an aggregated weekly updates18:39
SergeyLukjanovpersonally I think that it's awesome to have a weekly updates in meeting logs18:40
SergeyLukjanovany thoughts on topics that should be covered?18:40
alazarevas I understand the difference, there will be update on CI even if there are no much changes in CI18:40
alazarevSergeyLukjanov: is my understanding right?18:40
aignatovalazarev: exactly18:41
ErikBit would be good to get update on 'active' blueprints18:41
SergeyLukjanovalazarev, I'd like to see some stats for CI for example18:41
SergeyLukjanovfrom CI guys18:41
mattfErikB, nice idea18:41
*** NikitaKonovalov is now known as NikitaKonovalov_18:41
SergeyLukjanovErikB, agreed18:41
aignatovErikB: good point18:41
jmarondependency updates.  I stumbled (painfully) across the new need for mysql and postgres installs on my dev obx18:41
jmaronbox18:41
*** nadya__ has quit IRC18:41
alazarevso, we just need to document list of topics somewhere18:42
alazarevnot much changes to existing structure18:42
mattfi painfully stumbled on use_namespaces requiring savanna-api be run as root, oof18:42
jmaronthat wasn't that painful… ;)18:42
SergeyLukjanovI'll try to list topics to the next meeting18:43
mattfmaybe not for you!18:43
SergeyLukjanovlet's move on to the open discussion18:43
jmaron(btw, any luck corralling neutron experts)18:43
SergeyLukjanov#topic General discussion18:43
*** openstack changes topic to "General discussion (Meeting topic: savanna)"18:43
mattfsome18:43
mattfgeneral topic from last week - everyone wants the cli to support IDs and NAMEs18:43
jmaronI would hope there's a way to configure the nature of the namespace creation18:44
*** arnaud has joined #openstack-meeting-alt18:44
mattfeveryone also wants the savanna api (rest) to support them so the client can be thin18:44
*** arnaud__ has joined #openstack-meeting-alt18:44
SergeyLukjanovmattf, btw, how is your cli work? do you have estimates to name it beta cli?18:44
mattfi did some digging and it looks like we may be unique in having that functionality in our rest api18:44
jmarontrail blazers!18:44
SergeyLukjanovmattf, all projects support it on the client side18:44
mattfsooooo... how strongly do people want the client to be thin?18:44
*** jcooley_ has joined #openstack-meeting-alt18:45
mattfSergeyLukjanov, yeah, where were you last week to tell us that!?18:45
SergeyLukjanovbecause mostly all other project have no constraint on resource name18:45
* mattf has since learned this18:45
SergeyLukjanovI was on the PTL's webinar :)18:45
mattfexcuses excuses18:45
mattfso, unless someone who hasn't been hitting the hwx bar pressures me really hard, the name support is going to be client side - at least for the first pass i write18:46
SergeyLukjanovat least for the v1.1 api18:46
mattfyeah, i dunno what magical support will be unlocked with the new v2 impl that may use an entirely different framework18:46
*** NikitaKonovalov_ is now known as NikitaKonovalov18:46
*** Duane__ has joined #openstack-meeting-alt18:46
SergeyLukjanovmattf, I'd like to not harry with v2 api and include all nice features to it18:47
SergeyLukjanovthat all of us dreaming about ;)18:47
mattfthat's nice, we can have a dv2 (dream v2) too18:47
SergeyLukjanovlike /v2/beer/one-more-please18:48
mattfin the meantime, i'll be busy on v218:48
SergeyLukjanovmattf, are you planning to complete your 'run_tests.sh'?18:48
mattfsounds like no objections to name search on the client side, thank!18:48
SergeyLukjanovmattf, not from my side18:48
mattfSergeyLukjanov, i'll take a look again this week, but it was still busted for savanna18:49
alazarevmattf: name search on client side looks fine18:49
*** SushilKM has joined #openstack-meeting-alt18:49
mattfas for v1 and v1.1 - i'm a little disturbed that we store swift creds and pass them around18:49
*** SushilKM has left #openstack-meeting-alt18:49
mattfi'm curious about how we happen to call them credentials in one call and extra in another though18:49
SergeyLukjanovwe need to add the corresponding properties to the filter18:49
SergeyLukjanovto not return back them from the rest api18:50
aignatovtmckay: I had a quick look at the savanna channel and observed that you plan to start working on the streaming api for edp18:50
*** Duane_ has quit IRC18:50
mattfdata-sources uses credentials, job-binaries uses extra18:50
mattfif no one speaks up, i'll probably propose them both as "credentials" for v218:51
*** bob_nettleton has quit IRC18:51
tmckayaignatov, yes18:51
ErikB+118:51
* mattf might even if folks speak up18:51
tmckayI have a question about that, but I have to run to the doctor18:51
aignatovtmckay: ok, we can talk later about it18:52
tmckayaignatov, essentially, should streaming map-reduce be a new job type, or extra options for current map-reduce job type?18:52
tmckayit effects crobertsrh, we should consider ease of use in the UI18:52
mattfanother oddity i found - clusters have a status property that provides you info about what you'd expect, cluster status18:52
mattfjob-executions have an info property that has a status property that tells you about the job-execution18:52
aignatovtmckay: as I remember streaming is the subset of common MapReduce, right?18:52
*** pballand has quit IRC18:52
alazarevmattf: +1 on minimizing extra18:52
tmckayyes18:52
*** akuznetsov has quit IRC18:52
mattfanyone know why cluster.status and job-executino.info.status or know why they should be the same?18:53
mattfalazarev, thx18:53
mattfErikB, thx18:53
mattfs/why they should/why they should not/18:53
aignatovtmckay: maybe in the UI side it should be as a separate job type but in the core EDP...18:53
SergeyLukjanovmattf, I'd like to have j_e.status18:53
aignatovhow simple to implement :)18:53
tmckayaignatov, could be, I had that thought to.  talk to you soon18:54
SergeyLukjanovwe have 6 mins18:54
* mattf can be done18:54
aignatovtmckay: not today, ok? tomorrow, ping me18:54
*** bob_nettleton has joined #openstack-meeting-alt18:54
tmckayack18:54
alazarevmattf: does job-executino.info contain something other than status?18:55
mattfalazarev, afaik, no18:55
*** pballand has joined #openstack-meeting-alt18:55
jmaron'info': {'status': 'Pending'},18:55
alazarevmattf: may be something was supposed...18:56
mattfok, keep an eye out. i'll probably propose it gets collapsed for v218:57
SergeyLukjanovmattf, ok18:58
SergeyLukjanovlooks like we're out of time18:59
SergeyLukjanovthank you all!18:59
SergeyLukjanovhave a good night/day18:59
SergeyLukjanov#endmeeting18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:59
openstackMeeting ended Thu Jan 23 18:59:16 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
*** ErikB has quit IRC18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-01-23-18.07.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-01-23-18.07.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-01-23-18.07.log.html18:59
*** mattf has left #openstack-meeting-alt19:00
*** dmitryme has left #openstack-meeting-alt19:00
*** bob_nettleton has quit IRC19:00
*** jcooley_ has quit IRC19:01
*** tmckay has quit IRC19:03
*** jprovazn_ has quit IRC19:03
*** ViswaV has left #openstack-meeting-alt19:03
*** nadya__ has joined #openstack-meeting-alt19:05
*** DinaBelova_ is now known as DinaBelova19:07
*** amytron has quit IRC19:08
*** amytron has joined #openstack-meeting-alt19:10
*** eankutse1 has quit IRC19:11
*** eankutse has joined #openstack-meeting-alt19:11
*** colinmcnamara has joined #openstack-meeting-alt19:13
*** SushilKM has joined #openstack-meeting-alt19:16
*** ruhe is now known as _ruhe19:19
*** aignatov is now known as aignatov_19:20
*** pballand has quit IRC19:23
*** markwash_ has joined #openstack-meeting-alt19:30
*** harlowja is now known as harlowja_away19:31
*** SushilKM has left #openstack-meeting-alt19:31
*** markwash has quit IRC19:32
*** markwash_ is now known as markwash19:32
*** crobertsrh has left #openstack-meeting-alt19:33
*** pballand has joined #openstack-meeting-alt19:35
*** pdmars has joined #openstack-meeting-alt19:37
*** jtomasek has joined #openstack-meeting-alt19:38
*** NikitaKonovalov is now known as NikitaKonovalov_19:39
*** colinmcnamara has quit IRC19:40
*** sarob has joined #openstack-meeting-alt19:42
*** nadya__ has quit IRC19:43
*** NikitaKonovalov_ is now known as NikitaKonovalov19:44
*** sarob has quit IRC19:49
*** NikitaKonovalov is now known as NikitaKonovalov_19:49
*** jtomasek has quit IRC19:49
*** sarob has joined #openstack-meeting-alt19:50
*** sharwell_ has joined #openstack-meeting-alt19:51
*** gokrokve has joined #openstack-meeting-alt19:52
*** mattgriffin has quit IRC19:53
*** zhiyan has joined #openstack-meeting-alt19:54
*** sarob has quit IRC19:54
*** bdpayne has quit IRC19:54
*** NikitaKonovalov_ is now known as NikitaKonovalov19:54
*** sarob has joined #openstack-meeting-alt19:56
*** bdpayne has joined #openstack-meeting-alt19:56
*** mspreitz has joined #openstack-meeting-alt19:57
*** sarob has quit IRC19:58
*** gokrokve has quit IRC19:58
*** sarob has joined #openstack-meeting-alt19:58
*** harlowja_away is now known as harlowja19:59
*** NikitaKonovalov is now known as NikitaKonovalov_19:59
markwash#startmeeting glance20:00
openstackMeeting started Thu Jan 23 20:00:00 2014 UTC and is due to finish in 60 minutes.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: glance)"20:00
openstackThe meeting name has been set to 'glance'20:00
markwashhi glance folks20:00
arnaudhi20:00
markwasharnaud: o/ :-)20:00
*** xyang1 has quit IRC20:01
markwashrosmaita iccha ameade nikhil__ esheffield flwang flaper87 zhiyan hemanth_20:01
markwashhighlight time!20:01
markwash#topic agenda20:01
*** openstack changes topic to "agenda (Meeting topic: glance)"20:01
sharwell_hi everyone :)20:01
markwashwe're a bit light today20:01
zhiyanhi!20:02
*** sadasu has quit IRC20:02
markwashI myself am just in "get ready for the mini summit" mode20:02
markwashso I thought we could just talk about that a bit, if anyone has questions20:02
rosmaitai don't know, will hi mark20:02
rosmaitai mean "hello"20:02
*** ashwini_ has joined #openstack-meeting-alt20:02
markwashso anyone have any other topics they want to discuss today other than the mini summit?20:03
sharwell_i'm up for talking about schemas if you want to, but definitely don't have to if it's not the right time20:03
*** sarob has quit IRC20:04
*** nadya__ has joined #openstack-meeting-alt20:04
markwashsharwell_: looks like we'll have time20:04
*** NikitaKonovalov_ is now known as NikitaKonovalov20:04
markwashlast call for suggestions. . .20:04
*** jcoufal has joined #openstack-meeting-alt20:04
*** dhellmann_ is now known as dhellmann20:04
*** rnirmal has quit IRC20:05
markwashall right20:05
markwash#topic mini summit this monday20:05
*** openstack changes topic to "mini summit this monday (Meeting topic: glance)"20:05
markwashI'm working on the broadcasting angle at the moment20:05
markwashI'm trying to pick a solution that can be picked up internationally20:05
markwashthe plan is for remote participants to be able to watch, but I think we'll just have to have some local participants in IRC who can relay questions and thoughts20:06
markwashwatch and listen, I mean, of course20:07
*** rnirmal has joined #openstack-meeting-alt20:07
markwashI'd also love it if anyone who has etherpads for their sessions could provide links20:07
markwashnot quite sure how to fit that into the wiki page20:08
markwash#link https://wiki.openstack.org/wiki/Glance/IcehouseCycleMeetup20:08
*** alazarev has quit IRC20:08
markwashthat's it for updates for me, anyone have questions?20:08
markwash#topic open discussion20:10
*** openstack changes topic to "open discussion (Meeting topic: glance)"20:10
ameadewe are lurking btw lol20:10
markwashsorry not much content today folks, but we can always just have our time back :-)20:10
rosmaitai think sam has some comments about schemas :)20:10
markwashsharwell_: wanna talk about schemas here? or if20:10
sharwell_or if?20:11
markwashsorry20:11
sharwell_here is fine for me20:11
markwashokay sounds good20:11
markwashsharwell_: care to introduce the topic?20:11
sharwell_So as rosmaita knows, I've taken particular interest in the introduction of json schemas to this api, along with some of the others20:11
*** pballand has quit IRC20:12
*** rnirmal has quit IRC20:12
markwashsharwell_: I take it you've been trying to use them while writing some client-side tooling? or am I mistaken. .20:13
sharwell_what i'd like to accomplish is working towards creating a combination of a schema development strategy and an associated breaking changes policy that meets the requirements of both developers using openstack APIs and the requirement of openstack projects to incorporate extensions, new functionality, and/or customizable portions of the software installation process of individual users20:13
sharwell_that ended with "individual users" did the message come through?20:14
markwashyes I think so20:14
sharwell_thanks20:14
*** gokrokve has joined #openstack-meeting-alt20:14
sharwell_i believe everyone agrees about the benefits json schema brings to the table regarding communicating the behavior of our apis20:15
markwashwell20:15
markwashmaybe :-)20:15
markwashI think if we were using them a bit better, we'd get the benefit we were aiming at20:15
sharwell_meaning it's ok for me to focus on addressing problems that have been observed without explaining why we're trying to keep it around20:16
markwashheh sure20:16
markwashI'm curious if you hae some examples of the types of problems20:17
sharwell_I believe our target should be including "a valid reference schema" for items found in requests and responses in our API reference.20:17
rosmaitai wonder whether the schema fix should be targeted for v3 ?20:17
rosmaitabecause i think we're going to have to have different request/response schemas20:18
rosmaitaand that's a big change20:18
sharwell_The primary challenges are 1) ensuring that the schema is update and 2) ensuring that the schema does not box the project in to the point that it can't be extended to meet customer/company requirements20:18
markwashrosmaita: we haven't talked a lot about what v3 might look like, I'm curious if we even want schemas for it in the way we have them today20:20
markwashI'm a bit skeptical these days about schemas hosted on the api server20:20
markwashpublishing static schemas per api minor revision seems quite good still20:20
sharwell_schemas hosted on the api server are able to communicate certain infromation that we will never be able to include in the api reference20:20
rosmaitai think we need a kind of "vision statement" for what we want the schemas to do20:21
rosmaitai've always thought of them as guidelines, not contracts20:21
rosmaitabut that's just me20:21
markwashsharwell_: true.. what kind of killer usecase can you think of for that feature, though?20:21
sharwell_for example, the name of an image has a maximum length that is likely configurable as part of the software installation. the api reference wouldn't include a maxLength for this field, but the API could return a schema that does include this property with the current value in effect for that installation20:21
markwashokay sure20:22
sharwell_in addition, json schema does not prevent you from using properties that lie outside the schema (i.e. objects can include properties that are not validated)20:22
markwashanother use case that is nice is communicating which properties are allowed on a POST or PATCH, but it is sometimes hard as I don't know a good way to communicate "negative" patterns20:23
markwashi.e., a property can be anything except "billing_foo"20:23
markwashbut I might just be a bit rusty on my jsonschema20:23
*** NikitaKonovalov is now known as NikitaKonovalov_20:23
sharwell_the api reference could omit custom properties, while the api call itself might return information about custom properties20:23
*** vipul is now known as vipul-away20:24
sharwell_this fact is the primary reason why i believe you can include authoritative schemas in the api reference without fear of them getting "out of date"20:24
sharwell_you would just need to include a message that the server may support properties for objects which are not described by the schema, and the service provider will define the meaning of any such custom properties20:26
*** amrith has joined #openstack-meeting-alt20:27
markwashwhat exactly does a client do with that kind of schema information though?20:27
sharwell_markwash: are you referring to a schema in the api reference, or a schema returned by an api call20:27
markwashit can do local validation, but its not clear to me that its a huge win over remote validation. .20:28
markwashapi call20:28
*** SergeyLukjanov is now known as SergeyLukjanov_20:28
*** NikitaKonovalov_ is now known as NikitaKonovalov20:28
*** aignatov_ is now known as aignatov20:29
markwashsorry I don't mean to be overly skeptical. . I'm just struggling atm for the vision that rosmaita was talking about20:29
sharwell_i'm more concerned today with communicating the meaning of schemas in the api reference. i.e. what long-term guarantees does a client developer have in relation to the schema they read about in the api reference.20:30
*** nadya__ has quit IRC20:30
*** NikitaKonovalov is now known as NikitaKonovalov_20:31
*** mspreitz has quit IRC20:31
rosmaitaso would it be better to have no shcemas at all?20:31
rosmaitarahter than inaccurate ones?20:31
sharwell_i believe that by documenting only a required subset of the total set of resource properties, we can ensure that "inaccurate" never happens, while at the same time providing more concrete guarantees than has ever been seen before in OS documentation20:32
markwashsharwell_: we aim for 100% backwards compatibility but I wouldn't be surprised if we missed a bit20:32
markwashand we don't necessarily do so exclusively in terms of the schema20:32
sharwell_or any web api documentation for that matter20:33
markwashi.e. if the behavior differs from the schema we might be stuck keeping both for backwards compatibility :-(20:33
*** kevinconway_ has joined #openstack-meeting-alt20:33
*** kevinconway has quit IRC20:34
*** kevinconway_ is now known as kevinconway20:34
markwashsharwell_: but in any case, what kind of changes do you have in mind?20:36
*** vipul-away is now known as vipul20:36
sharwell_markwash: i'd like to help prepare schemas for the api reference that we can treat as authoritative, and used as a guide for any glance updates made through the icehouse release20:37
markwashooh, with some validation we can try out to prevent regressions?20:37
sharwell_i'm not 100% confident, but i believe it is possible to automate a "compatibility analysis" of two schemas to highlight if and where new properties could cause bugs to appear in code that follows the old schema20:38
sharwell_this type of analysis falls square within my research interests :)20:39
markwashit may also work to run the api schema against the api to verify they match up20:39
*** vipul is now known as vipul-away20:40
*** rnirmal has joined #openstack-meeting-alt20:41
markwashbut in any case, valid schemas for long term supported behavior sounds great20:41
markwashI think we can probably sign up for that without any concerns20:41
markwashsharwell_: there are sort of two steps in this process, 1) this discussion, 2) writing up a blueprint (which can be brief)20:42
markwashdo you want to look into #2 and then we can meet up again in 2 weeks to review?20:42
markwashor is there already a blueprint?20:42
markwash(also if the blueprint is ready faster you can just ping for review in #openstack-glance)20:43
sharwell_sure. i'll look into writing a blueprint describing a breaking changes policy for json schemas used by various APIs20:43
sharwell_if we define the breaking changes policy, then it becomes easy to ask if a particular schema is likely to cause problems in that context20:44
markwasheys20:44
markwashyes20:44
*** coolsvap is now known as coolsvap_away20:44
rosmaita+120:44
markwashI think defining "breaking changes" in a crunchy way we can evaluate more rigorously would be a huge benefit20:45
markwashright now, avoiding them is mostly based on gut-feeling20:45
markwashwhich is obviously not a good long term policy20:45
*** colinmcnamara has joined #openstack-meeting-alt20:45
markwashif we controlled clients, we could do this quite simply -- we could test all of them20:46
sharwell_markwash: that often works, I just think we have some cool tools at our disposal that allows us to do even better20:46
markwashsharwell_: +120:46
rosmaitasharwell_: this sounds good, thanks for taking this on20:47
markwashyes indeed, thank you20:47
sharwell_no problem, i think about these things in my free time anyway20:47
sharwell_"free time"20:47
markwash:-)20:49
markwashall right, seems we're exhausted for today20:49
*** Duane_ has joined #openstack-meeting-alt20:50
markwashunless anyone has another item, I'll close it out and look forward to seeing many of you next week20:50
rosmaitasee you next week!20:51
markwash#endmeeting20:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:52
openstackMeeting ended Thu Jan 23 20:52:00 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-01-23-20.00.html20:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-01-23-20.00.txt20:52
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-01-23-20.00.log.html20:52
*** marun has joined #openstack-meeting-alt20:52
*** zhiyan has left #openstack-meeting-alt20:52
*** pballand has joined #openstack-meeting-alt20:53
*** Duane__ has quit IRC20:54
*** ashwini_ has left #openstack-meeting-alt20:55
*** coolsvap_away has quit IRC20:56
*** jmontemayor has quit IRC21:00
*** jecarey has quit IRC21:00
*** jmontemayor has joined #openstack-meeting-alt21:02
*** jmontemayor has quit IRC21:03
*** jmontemayor has joined #openstack-meeting-alt21:03
*** Duane_ has quit IRC21:05
*** amytron has quit IRC21:06
*** alazarev has joined #openstack-meeting-alt21:06
*** Duane_ has joined #openstack-meeting-alt21:06
*** DinaBelova is now known as DinaBelova_21:09
*** kebray_ has joined #openstack-meeting-alt21:09
*** Duane_ has quit IRC21:10
*** lblanchard has quit IRC21:13
*** pballand has quit IRC21:14
*** vipul-away is now known as vipul21:18
*** marun has quit IRC21:24
*** sarob has joined #openstack-meeting-alt21:25
*** julim has quit IRC21:26
*** marun has joined #openstack-meeting-alt21:27
*** MarkAtwood has joined #openstack-meeting-alt21:32
*** bswartz has quit IRC21:38
*** dprince has quit IRC21:43
*** sarob has quit IRC21:47
*** sarob has joined #openstack-meeting-alt21:47
*** sarob_ has joined #openstack-meeting-alt21:48
*** michael-yu has quit IRC21:49
*** sarob has quit IRC21:51
*** pballand has joined #openstack-meeting-alt21:53
*** jdob has quit IRC21:56
*** sarob_ has quit IRC21:57
*** doug_shelley66 has quit IRC22:02
*** sarob has joined #openstack-meeting-alt22:03
*** krtaylor has quit IRC22:09
*** jecarey has joined #openstack-meeting-alt22:10
*** amytron has joined #openstack-meeting-alt22:12
*** jmontemayor has quit IRC22:15
*** Barker has quit IRC22:16
*** Barker has joined #openstack-meeting-alt22:16
*** marun has quit IRC22:20
*** DennyZhang has joined #openstack-meeting-alt22:21
*** nati_ueno has quit IRC22:21
*** kevinconway has quit IRC22:28
*** doug_shelley66 has joined #openstack-meeting-alt22:35
*** amcrn has quit IRC22:35
*** Duane_ has joined #openstack-meeting-alt22:36
*** Duane__ has joined #openstack-meeting-alt22:37
*** colinmcnamara has quit IRC22:38
*** Duane_ has quit IRC22:40
*** colinmcnamara has joined #openstack-meeting-alt22:41
*** esker has joined #openstack-meeting-alt22:43
*** eankutse has quit IRC22:43
*** michael-yu has joined #openstack-meeting-alt22:46
*** banix has quit IRC22:47
*** DennyZhang has quit IRC22:50
*** Leonr has quit IRC22:54
*** sarob has quit IRC22:55
*** ivar-lazzaro has joined #openstack-meeting-alt22:58
*** esker has quit IRC22:59
*** sarob has joined #openstack-meeting-alt23:02
*** sarob has quit IRC23:03
*** julienvey_ has quit IRC23:05
*** aignatov is now known as aignatov_23:12
*** sarob has joined #openstack-meeting-alt23:12
*** amrith has quit IRC23:14
*** sarob has quit IRC23:17
*** yogesh has quit IRC23:18
*** sacharya has joined #openstack-meeting-alt23:18
*** jcoufal has quit IRC23:19
*** DennyZhang has joined #openstack-meeting-alt23:20
*** amytron has quit IRC23:21
*** Duane__ has quit IRC23:25
*** DennyZhang has quit IRC23:26
*** DennyZhang has joined #openstack-meeting-alt23:29
*** garyduan has quit IRC23:35
*** garyduan has joined #openstack-meeting-alt23:35
*** krtaylor has joined #openstack-meeting-alt23:36
*** pballand has quit IRC23:37
*** tanisdl has quit IRC23:38
*** sacharya1 has joined #openstack-meeting-alt23:45
*** sacharya1 has quit IRC23:45
*** amcrn has joined #openstack-meeting-alt23:46
*** sacharya has quit IRC23:48
*** eankutse has joined #openstack-meeting-alt23:59

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