Monday, 2014-01-20

*** ijw has joined #openstack-meeting-alt00:13
*** sergmelikyan has quit IRC00:38
*** DennyZhang has joined #openstack-meeting-alt00:39
*** sergmelikyan has joined #openstack-meeting-alt00:43
*** sarob has joined #openstack-meeting-alt00:43
*** doug_shelley66 has quit IRC00:56
*** sarob has quit IRC01:17
*** DennyZhang has quit IRC01:17
*** sarob has joined #openstack-meeting-alt01:20
*** mozawa has joined #openstack-meeting-alt01:23
*** nosnos has joined #openstack-meeting-alt01:24
*** sarob has quit IRC01:35
*** ijw has quit IRC01:39
*** ijw has joined #openstack-meeting-alt01:40
*** ijw has quit IRC01:51
*** ijw has joined #openstack-meeting-alt01:56
*** sarob has joined #openstack-meeting-alt02:13
*** sarob has quit IRC02:18
*** nati_uen_ has quit IRC02:27
*** beyounn has joined #openstack-meeting-alt02:45
*** IlyaE has joined #openstack-meeting-alt02:47
*** flwang has quit IRC02:48
*** gokrokve has quit IRC02:48
*** gokrokve has joined #openstack-meeting-alt02:57
*** gokrokve has quit IRC03:02
*** sarob has joined #openstack-meeting-alt03:09
*** sarob_ has joined #openstack-meeting-alt03:13
*** sarob has quit IRC03:14
*** sarob_ has quit IRC03:18
*** gokrokve has joined #openstack-meeting-alt03:19
*** gokrokve has quit IRC03:24
*** flwang has joined #openstack-meeting-alt03:29
*** nati_ueno has joined #openstack-meeting-alt03:41
*** nati_ueno has quit IRC03:43
*** nati_ueno has joined #openstack-meeting-alt03:44
*** banix has quit IRC03:46
*** beyounn has quit IRC03:52
*** sarob has joined #openstack-meeting-alt04:13
*** akuznetsov has joined #openstack-meeting-alt04:16
*** sarob has quit IRC04:18
*** coolsvap has joined #openstack-meeting-alt04:19
*** gokrokve has joined #openstack-meeting-alt04:20
*** gokrokve has quit IRC04:25
*** nati_uen_ has joined #openstack-meeting-alt04:32
*** ozstacker has joined #openstack-meeting-alt04:33
*** nati_uen_ has quit IRC04:33
*** nati_uen_ has joined #openstack-meeting-alt04:33
*** nati_ueno has quit IRC04:36
*** rraja has joined #openstack-meeting-alt04:40
*** tnurlygayanov has quit IRC04:51
*** IlyaE has quit IRC04:52
*** amotoki has joined #openstack-meeting-alt04:55
*** gokrokve has joined #openstack-meeting-alt04:57
*** katyafervent has quit IRC05:11
*** katyafervent has joined #openstack-meeting-alt05:11
*** aignatov has joined #openstack-meeting-alt05:12
*** sergmelikyan has quit IRC05:12
*** dteselkin_ has quit IRC05:13
*** dteselkin_ has joined #openstack-meeting-alt05:13
*** sarob has joined #openstack-meeting-alt05:13
*** aignatov has quit IRC05:17
*** IlyaE has joined #openstack-meeting-alt05:17
*** sarob has quit IRC05:18
*** nati_ueno has joined #openstack-meeting-alt05:21
*** nati_ueno has quit IRC05:21
*** nati_ueno has joined #openstack-meeting-alt05:22
*** jecarey has quit IRC05:24
*** krtaylor has joined #openstack-meeting-alt05:25
*** nati_uen_ has quit IRC05:25
*** chandankumar_ has joined #openstack-meeting-alt05:26
*** ashaikh_ has joined #openstack-meeting-alt05:26
*** ashaikh has quit IRC05:27
*** ashaikh_ is now known as ashaikh05:27
*** noslzzp has quit IRC05:34
*** DinaBelova_ is now known as DinaBelova05:40
*** SergeyLukjanov_ is now known as SergeyLukjanov05:40
*** akuznetsov has quit IRC05:46
*** nosnos has quit IRC05:52
*** nosnos_ has joined #openstack-meeting-alt05:52
*** nati_uen_ has joined #openstack-meeting-alt06:10
*** akuznetsov has joined #openstack-meeting-alt06:13
*** akuznetsov has quit IRC06:13
*** sarob has joined #openstack-meeting-alt06:13
*** akuznetsov has joined #openstack-meeting-alt06:13
*** nati_ueno has quit IRC06:14
*** gokrokve has quit IRC06:16
*** sarob has quit IRC06:18
*** antigluk has quit IRC06:23
*** rraja has quit IRC06:23
*** ijw_ has joined #openstack-meeting-alt06:25
*** ijw has quit IRC06:27
*** rahmu has quit IRC06:27
*** antigluk has joined #openstack-meeting-alt06:28
*** DinaBelova has quit IRC06:28
*** marios has quit IRC06:28
*** rahmu has joined #openstack-meeting-alt06:29
*** marios has joined #openstack-meeting-alt06:29
*** DinaBelova has joined #openstack-meeting-alt06:31
*** rraja has joined #openstack-meeting-alt06:40
*** gokrokve has joined #openstack-meeting-alt06:47
*** gokrokve_ has joined #openstack-meeting-alt06:49
*** yamahata has joined #openstack-meeting-alt06:52
*** gokrokve has quit IRC06:52
*** nosnos_ has quit IRC06:52
*** nosnos has joined #openstack-meeting-alt06:53
*** gokrokve_ has quit IRC06:54
*** gokrokve has joined #openstack-meeting-alt06:58
*** nati_ueno has joined #openstack-meeting-alt06:59
*** SergeyLukjanov is now known as SergeyLukjanov_a06:59
*** SergeyLukjanov_a is now known as SergeyLukjanov_07:00
*** nati_uen_ has quit IRC07:01
*** gokrokve has quit IRC07:03
*** nati_ueno has quit IRC07:04
*** nati_ueno has joined #openstack-meeting-alt07:04
*** SergeyLukjanov_ is now known as SergeyLukjanov07:08
*** sarob has joined #openstack-meeting-alt07:13
*** sarob has quit IRC07:17
*** SergeyLukjanov is now known as SergeyLukjanov_07:18
*** rraja has quit IRC07:23
*** ashaikh has quit IRC07:24
*** SushilKM has joined #openstack-meeting-alt07:25
*** jcoufal has joined #openstack-meeting-alt07:29
*** SushilKM has left #openstack-meeting-alt07:35
*** d0ugal has joined #openstack-meeting-alt07:37
*** d0ugal has quit IRC07:37
*** d0ugal has joined #openstack-meeting-alt07:37
*** IlyaE has quit IRC07:42
*** NikitaKonovalov_ is now known as NikitaKonovalov07:43
*** dguitarbite has quit IRC07:47
*** safchain has joined #openstack-meeting-alt07:51
*** dguitarbite has joined #openstack-meeting-alt07:52
*** SergeyLukjanov_ is now known as SergeyLukjanov07:53
*** nati_uen_ has joined #openstack-meeting-alt07:53
*** nati_ueno has quit IRC07:56
*** gokrokve has joined #openstack-meeting-alt07:59
*** gokrokve has quit IRC08:04
*** sarob has joined #openstack-meeting-alt08:13
*** jtomasek has joined #openstack-meeting-alt08:16
*** sarob has quit IRC08:18
*** flaper87|afk is now known as flaper8708:18
*** luqas has joined #openstack-meeting-alt08:26
*** matrohon has joined #openstack-meeting-alt08:36
*** luqas has quit IRC08:36
*** shashank_ has quit IRC08:37
*** nati_ueno has joined #openstack-meeting-alt08:41
*** nati_ueno has quit IRC08:41
*** nati_ueno has joined #openstack-meeting-alt08:42
*** nati_uen_ has quit IRC08:44
*** SergeyLukjanov is now known as SergeyLukjanov_08:47
*** DinaBelova is now known as DinaBelova_08:48
*** jcoufal has quit IRC08:49
*** gokrokve has joined #openstack-meeting-alt09:00
*** rraja has joined #openstack-meeting-alt09:02
*** gokrokve has quit IRC09:05
*** nati_ueno has quit IRC09:07
*** nati_ueno has joined #openstack-meeting-alt09:07
*** luqas has joined #openstack-meeting-alt09:12
*** nati_ueno has quit IRC09:12
*** jcoufal has joined #openstack-meeting-alt09:12
*** sarob has joined #openstack-meeting-alt09:13
*** derekh has joined #openstack-meeting-alt09:15
*** sarob has quit IRC09:18
*** aignatov_ has joined #openstack-meeting-alt09:24
*** lsmola_ has joined #openstack-meeting-alt09:38
*** SergeyLukjanov_ is now known as SergeyLukjanov09:43
*** SergeyLukjanov is now known as SergeyLukjanov_09:48
*** IYozhikov_away is now known as IgorYozhikov09:50
*** sergmelikyan has joined #openstack-meeting-alt09:50
*** ijw_ has quit IRC09:52
*** ijw has joined #openstack-meeting-alt09:53
*** derekh is now known as derekh_afk09:59
*** gokrokve has joined #openstack-meeting-alt10:01
*** rwsu has joined #openstack-meeting-alt10:03
*** gokrokve has quit IRC10:06
*** johnthetubaguy has joined #openstack-meeting-alt10:08
*** amotoki has quit IRC10:08
*** flwang has quit IRC10:09
*** sarob has joined #openstack-meeting-alt10:13
*** mozawa has quit IRC10:14
*** sarob has quit IRC10:18
*** dmakogon_ is now known as denis_makogon10:36
*** _ruhe is now known as ruhe10:42
*** ogelbukh has quit IRC10:47
*** ogelbukh has joined #openstack-meeting-alt10:47
*** nmarchenko has joined #openstack-meeting-alt11:00
*** gokrokve has joined #openstack-meeting-alt11:01
*** markvoelker has quit IRC11:04
*** gokrokve has quit IRC11:06
*** svetlanad has joined #openstack-meeting-alt11:09
*** sarob has joined #openstack-meeting-alt11:13
*** sarob has quit IRC11:18
*** rraja has quit IRC11:25
*** dguitarbite has quit IRC11:27
*** antigluk has quit IRC11:28
*** antigluk has joined #openstack-meeting-alt11:30
*** dguitarbite has joined #openstack-meeting-alt11:31
*** boris-42 has quit IRC11:31
*** tnurlygayanov has joined #openstack-meeting-alt11:31
*** safchain has quit IRC11:37
*** derekh_afk is now known as derekh11:38
*** safchain has joined #openstack-meeting-alt11:38
*** boris-42 has joined #openstack-meeting-alt11:41
*** antigluk has quit IRC11:41
*** smemon92 has joined #openstack-meeting-alt11:47
*** antigluk has joined #openstack-meeting-alt11:50
*** flwang has joined #openstack-meeting-alt11:52
*** gokrokve has joined #openstack-meeting-alt12:02
*** gokrokve has quit IRC12:07
*** coolsvap has quit IRC12:07
*** ruhe is now known as _ruhe12:09
*** dguitarbite_ has joined #openstack-meeting-alt12:10
*** smemon92 has quit IRC12:13
*** sarob has joined #openstack-meeting-alt12:13
*** dguitarbite_ has quit IRC12:13
*** sarob has quit IRC12:18
*** irenab has joined #openstack-meeting-alt12:27
*** _ruhe is now known as ruhe12:30
*** julienvey_ has joined #openstack-meeting-alt12:35
*** julienvey_ has quit IRC12:38
*** xuhanp has joined #openstack-meeting-alt12:57
*** SergeyLukjanov_ is now known as SergeyLukjanov12:58
*** DinaBelova_ is now known as DinaBelova12:58
*** shadower has quit IRC12:59
*** shadower has joined #openstack-meeting-alt12:59
ijw#startmeeting pci_passthrough13:02
openstackMeeting started Mon Jan 20 13:02:10 2014 UTC and is due to finish in 60 minutes.  The chair is ijw. 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
ijwHope that name is right...13:02
ijwWho's about?  I know Robert's skiving and I imagine yongli is too13:02
irenabhi13:03
*** gokrokve has joined #openstack-meeting-alt13:03
ijwWell then, this will be a short meeting13:03
ijw#topic Provider networks13:04
*** openstack changes topic to "Provider networks (Meeting topic: pci_passthrough)"13:04
ijwSo the issue we've been discussing is that provider networks in particular are usually on separate trunk networks to internal networks.  I think that in ML2 the issue might potentially be more general than that.13:04
ijwSo you have to pick a card attached to the right trunk in order to be able to connect to the network.13:05
irenabijw:  yes. What do you mean by trunk?13:05
*** markvoelker has joined #openstack-meeting-alt13:05
ijwWell, in the VLAN case it's the physical network you're attached to, without VLANs13:05
*** heyongli has joined #openstack-meeting-alt13:06
ijwSo you could have two provider networks that are completely isolated from each other, and a number of Neutron networks set up on those networks with different segmentation IDs13:06
irenabijw: so in neutron languafe is a phy network label13:06
ijwYup13:06
ijwIn ML2 I think it's a segment (because it can use separate segments internally)13:07
ijwBut I shall defer to Bob on that because I am not a master of ML213:07
irenabijw: fine, its exactly my case. So just need a way to group PCI device s on compute node according to labels13:07
ijwIf I wanted to connect to a Neutron network on one of those provider networks I would have to choose a port with the right physical connection or I just can't do it13:07
*** rkukura has joined #openstack-meeting-alt13:08
*** gokrokve has quit IRC13:08
ijwAnd since that's a problem of scheduling then Neutron can't solve it by itself - you have to choose the right device13:08
irenabI think rkukura is here13:08
ijwWhat I propose is that - initially - we just pick a device from the flavor, and if it can't be attached to the network because it's physically the wrong connection we abort the machine start.  That would practically mean you would want to set up two flavors and choose the right flavor for the network.13:09
ijwThat's obviously crap as a solution, but it means that we can implement the Neutron part and solve the other problem independently13:09
ijwThe other half of the problem is then making sure Nova picks the right device based on the Neutron network.13:09
*** mozawa has joined #openstack-meeting-alt13:09
irenabijw: I am OK with this approach for a start13:10
rkukuraI missed the proposal here - sorry I'm late13:10
ijwHey bob13:10
rkukurahi13:10
irenabhi13:10
irenabijw: want to recup?13:10
ijwWe were just discussing how you make PCI work when you need to choose a device that's connected to the right bit of network to suit the Neutron network you want to attach to13:10
*** BrianB_ has joined #openstack-meeting-alt13:11
ijwStep one: ignore the problem and hope someone else makes it go away.  If you get an unsuitable port you refuse to start the VM13:11
irenabassuming ML2 and segments,..13:11
*** ruhe is now known as _ruhe13:11
ijwOr anything else and provider networks - it's a problem with the OVS plugin too, in fact (not that I see us implementing PCI passthrough in the OVS plugin)13:11
irenabijw: not sure how you know if the port is unsuitable13:11
heyongliijw, i miss a little,  if the device label by phy connection, why we can not attach to VM ?13:12
ijwWell, provider-network-wise you can find the provider network that the Neutron network is on.  ML2-wise, dunno13:12
*** xuhanp has quit IRC13:12
ijwheyongli: if I pick Neutron network X and some network device flavor, there's no guarantee I can connect the device I get to X13:12
ijwAs a user, I don't know (in theory) which devices are suitable - even if I have multiple flavors13:13
irenabijw: if we label the device flavor with provider network label, it should be solved?13:13
ijwThe best solution would be where I don't have to know and I just go grab a 10Gbit flavor and leave Neutron to solve the problem.13:13
*** sarob has joined #openstack-meeting-alt13:13
ijwirenab: that works better, but you can still come up with a Neutron network and a flavor in a single --nic argument that won't work together13:13
irenabijw: why?13:14
rkukuraijw: We eventually need some way for nova scheduling to take neutron connectivity into account13:14
heyongliijw, for example, if device connect to phy  network X, labeled X, and flavor , we request phy-network: X, why this can not reslove this problem?13:14
ijwrkukura: I have a cunning plan, we'll get there in a mo ;)13:14
ijwI think the best solution is that (regardless of connection) you put all your 10G NICs in a single flavor and Neutron and Nova work out which specific device from that flavor to use13:14
ijwheyongli: that works, but you have to know that if you choose a neutron network 'thing' on phy network X - which you can't see as a user, I think, anyway - then you need to choose flavor tagged with phy-network X to make it work13:15
irenabijw: I think it should be thus way, but to be realistic and have something work for current release, we can have separate flavor for each net connectivity. I think it should work13:15
ijwBetter is if you have a set of devices connected to multiple networks (X and Y say) all in the one flavor, and the scheduler finds you a suitable device without having to do anything special13:16
ijwirenab: yep, that's plan A, basically, what we do to start with13:16
ijwPlan B would involve changing Neutron so that, at the point at the moment in nova-api where Nova checks all the networks exist, you also say 'and I need a device labelled as on segment X'13:16
ijwNeutron tells nova-api that and nova-api passes the information on to the scheduler.13:17
*** pdmars has joined #openstack-meeting-alt13:17
*** sarob has quit IRC13:17
ijwPlus point: without the user knowing anything special about the setup of the cloud, they will get a PCI device attached to the network13:17
irenabijw: so for plan B, you suggest neutron to manage PCI devices network connectivity awarness?13:17
ijwMinus point: if I have a flavor with 10 devices left in it but they're all attached to network Y, I may be unable to schedule the machine13:17
heyongliijw,  given a example about your B plan , that's interesting13:18
ijwirenab: I think Neutron needs to tell Nova which segment (provider network, whatever) it needs and Nova has to check the extra-info on the devices to work out which one suits13:18
irenabijw: understood13:19
ijwSo basically Nova says 'does this network exist?' and neutron now replies 'it exists and it's on segment X'.  Nova tells the scheduler 'I want a PCI device from flavor '10G' and on segment 'X'13:19
rkukuraport binding is where ml2 figures out which segment is going to be used13:19
ijwrkukura: you can see from above where that wouldn't work here, we'd need the information a bit earlier13:19
rkukuraijw: I think you are using "segment" slightly differently than in ml213:19
ijwAnd segment might be the wrong term, to be honest - this is the underlying trunk13:20
ijwindeed13:20
rkukuratrunk == physical_network13:20
ijwOK, physical_network it is13:20
heyongliijw, you mean we label the device with network, but flavor does not need to set up for that.13:20
ijwheyongli: that's what I think we want, yes13:20
rkukuraA virtual network (tenant or provider) can have multiple segments, on different physical_networks, but somehow bridged13:20
heyongliso when we tell the nova scheduler and how13:20
ijwheyongli: I think to be properly generic Neutron should be supplying its own list of scheduling requirements as {attr: value}13:21
heyongliijw, where to inject this information?13:22
ijwAnd (and I think from the way he's spoken about it baoli doesn't like this much) we will be setting aside specific named extra-info attributes for special purposes, so we would reserve 'physical_network' say and use that consistently for this purpose in both the extra-info and in Neutron13:22
heyonglito nova scheduler,13:22
ijwnova-api would pass it on to the scheduler, and the scheduler would find matching information in extra-info, done like this13:22
ijwWe'd use a consistent attribute name in both Neutron and in the configuration we added to nova-compute (the pci_information)13:23
irenabijw: the only problem I have is that we put networking info into nova configuration, but I think its not a tragedy13:23
ijwIn any case, plan B is up for discussion but plan A, I think, is what we should do for now - if Neutron can't attach the device it just kills the machine start13:24
ijwirenab: yeah - we discussed that before and it's annoying but it's not the end of the world13:24
rkukuraijw: Is "if Neutron can't attach the device it just kills the machine start" enforced in ml2's port binding?13:24
ijwI think that's best fixed by rethinking the way the pci_information is gathered at some point in the future.  If you could pull it from several files or sources this would work better13:24
ijwrkukura: yup13:25
heyongliijw, this information should be inject to VM's instance type before the scheduler does it's work, i wondering nova should do something in API stage, it's unclear to me ...13:25
irenabijw: for the plan A, I do not like that it may end without resources, so probably should use PCI flavor per phy_net13:25
ijwheyongli: yes, that's exactly what I'm trying to describe - there's a call to neutron in the API code and we can just get the information and push it on to the instance just there13:25
*** dguitarbite_ has joined #openstack-meeting-alt13:25
*** SergeyLukjanov is now known as SergeyLukjanov_13:26
heyongliijw: thank undstood.13:26
ijwirenab: We're agreeing, I think - we're saying that the administrator has to configure things consistently and, if the admin or the user does something that's not consistent we have a fallback plan (don't boot the VM)13:26
heyongliijw: this sound a configration problem13:27
irenabijw: fine with me13:27
ijwheyongli: for plan A, it is, absolutely - we need everything to be set up just right or things won't work.13:27
irenabsince we have Bob here, can we discuss the --nic vnic_type?13:27
rkukuraEven without PCI passthru, as soon as we have heterogeneous connectivity, we really need to make nova scheduling take account of connnectivity - so  I do not think this is a PCI-specific issue, and the solution shouldn't be PCI-specific13:27
ijwFor plan B then we basically solve the configuration problem for people by doing better scheduling13:27
ijwrkukura: indeed, and that should work - it's the same call in the same place and I think we need to work out how we can get Neutron to return information to be passed to the scheduler that isn't too Neutron-specific13:28
heyonglirkukura: sounds great.13:28
ijwAs in a requirement 'I want a machine that looks like this' and not 'I want a neutron-specific thing from nova'13:28
irenabsoud like task for next summit, if don't make it before13:28
ijwrkukura: how far down the line is heterogeneous network connectivity?13:29
*** _ruhe is now known as ruhe13:29
ijwNot soon, I'm thinking13:29
rkukuraijw: Its been a long time since I looked at the nova scheduler in detail - can it be made to call into nova to test whether connectivity is possible, or to prune a list of candidates or anything like that?13:29
ijwAnd in fact if someone doesn't configure a provider network on one compute node presumably we get the same failure right now...13:29
ijwIt prunes candidates and it's really best if it's operating on static-ish information, so sources of information about the compute nodes and a requirement from the API13:30
ijwI think callouts would be wrong - it tries to build and use a data model and the compute nodes generally try and keep that model current.  In your case I think the neutron agents would be supplying more information to its model.13:30
irenabijw: there is probably the assumption on homogenous environment, but with ML2 it is changing ..13:30
ijwAnd it's also allowed to be wrong - in the case the information is slightly out of date it reschedules13:31
rkukuraijw: OK, so static-ish but not static?13:31
ijwYeah - periodic updates are favoured.  You don't call to discover the info, you have it to hand and the backend keeps it current13:31
ijwI'm not in the current scheduler rewrite discussions but I don't think anyone was planning on changing that aspect of it13:32
rkukurathe assumption has been that connectivity is homogeneous, but we've basically been saying that right now, if you need heterogeneous connectivity, you are on your own to configure some nova feature such as flavors/cells/... to match13:32
ijwAlso you can add plugins (filters, really) so adding one that reads more information and excludes machines is exactly the right model13:32
*** jdob has joined #openstack-meeting-alt13:33
ijwrkukura: yes, so that model and this one are exactly the same - the 'make the flavors right' plan A here is exactly what you're recommending right now, too13:33
rkukuraijw: Filters calling into neutron was what I was originally thinking might work13:33
ijwrkukura: I think 'neutron updates a table of machine information in all the schedulers with a cast, then a filter acts on that information' is the model you'll end up with13:34
irenabijw: I think filter calliing into neutron will take more efforts to implement13:34
ijw'table' != DB table here13:34
ijwIt's nto really the right model anyway, there can be multiple schedulers which is why the information broadcast is favoured13:34
*** lblanchard has joined #openstack-meeting-alt13:34
ijwSo, are we good with the A/B approach?13:35
heyongliijw: for plan A, we label the device with phy connectivity and put it to flavor, and for neutron network configuration, use irenab's rename approach?13:35
rkukuraijw: I think we could get the info to the filters, but what about have the scheduler reserve an actual resource?13:35
heyongliijw: i'm ok with it.13:35
irenabijw: what you suggest is that neutron agent will be required to gather local machine PCI devices connectivity info, propagate to neutron server and server will update the scheduler?13:35
ijwrkukura: it already has stuff for that - you have a resource type and counts, it prereserves till the next update13:35
ijwirenab: no, for Bob's case where he's talking about provider network bridges I think the neutron agent would be reporting - for our case I think we would report it from nova-compute at least for now13:36
irenabijw: I meant for plan B13:37
rkukuraijw: Right now, neutron L2 agents report their connectivity to neutron-server via the agents_db RPC13:37
ijwFor plan B too, I would just use an attribute13:37
rkukuraAny ml2 port binding uses this info13:37
*** flaper87 is now known as flaper87|afk13:37
ijwrkukura: ok - then maybe neutron-server should cast it13:37
ijwOr maybe you should just call out.  Either works.13:37
irenabijw: I just think that not any vendor solution will require neutron agent13:38
irenabI am not sure, but think that baoli's case can manage without the agent13:38
rkukuraMaybe the RPC should be replaced with a notification that both the neutron-server and nova-schedulers could subscribe to13:38
ijwirenab: yeah - this is more Bob's problem we're solving.  PCI passthrough, we'll use the nova-compute config13:38
rkukurairenab: good point about not always having an L2 agent13:38
irenabrkukura: cool, I like it13:39
rkukuraHas the creating of PCI-passthru-capable neutron networks been addressed?13:39
ijwSo - plan A: 'we get the right device for the network we're trying to attach or we just abort'; plan B: 'we add code so that Neutron can add stuff to the scheduling request'.  A now, B later - possibly in Juno13:40
ijwrkukura: as in tagging them as capable?13:40
irenabijw: agree. We need good examples how to setup the nova  and neutron conf13:40
ijwAt the moment we're assuming they're all capable, practically speaking.13:40
irenabrkukura: we are talking on PCI pass-through capable ports13:41
rkukuraAs in a normal tenant specifying that they need (and are willing to pay for) this capability without having to know anything about the provider's physical topology13:41
ijwI can see how you might want to mark them so that Neutron provisions them accordingly, but we haven't gone there at present13:41
ijwrkukura: seems like a thing we could implement independently13:41
* ijw really needs to write that capability stuff.13:41
rkukuraRight, so neutron picks a physical_network that is attached to PCI-passthru-capable NICs13:41
ijwrkukura: not discussed.  Want to enter a BP?13:42
heyongliijw: in plan A if we scheduler the VM to a host, it should match the requirements, so there is may not be always failed, except a competition condition happens.13:42
irenabrkukura: not following your case, can elaborate please?13:42
rkukuraInitially, it might make sense to require these to be provider networks, where the administrator knows which physical_network to pick13:42
ijwheyongli: indeed - you pick a network on provider network X and a flavor on Y and it will go wrong, and it will all be your fault13:43
irenabrkukura: makes sence13:43
ijwOK, I don't see any disagreement here, just clarifications and refinements at the moment13:43
ijwSo, since Bob's here13:43
ijw#topic ML2 plugin13:44
*** openstack changes topic to "ML2 plugin (Meeting topic: pci_passthrough)"13:44
heyongliijw: lets do A, and B is more user friendly.13:44
irenabrkukura: I registered a blueprint for vnic_type request13:44
rkukuraIf PCI-passthru NICs are a very limited resource, it might make most sense to connect all of them to one physical network, and only allocate that physical_network to virtual networks that will need passthru13:44
ijwirenab: link?13:44
heyongliirenab: cool13:45
irenabijw: https://blueprints.launchpad.net/neutron/+spec/ml2-request-vnic-type13:45
ijwrkukura: totally true and also reasonable; I think we'll do as you say, we'll just implement it later13:45
ijw#link https://blueprints.launchpad.net/neutron/+spec/ml2-request-vnic-type13:45
ijw#link https://blueprints.launchpad.net/neutron/+spec/ml2-request-vnic-type Irena's blueprint13:45
rkukuraThe terms "plan A" and "plan B" imply either/or - I think you want something more like "phase 1" and "phase 2"13:45
ijwScrew you, meetingbot13:45
ijwFair.  The mailing list email is 1/213:46
irenabfor ML2 mech drivers, we going with cisco and mellanox as separate Mech. Drivers13:46
rkukuraSo who sets vnic_type on a port?13:46
ijwIt's set via the nova boot api13:47
ijw(and therefore cli)13:47
ijw--nic net-id=xxx,pci-flavor=yyy,vnic-type=macvtap13:47
irenabon nova  bott command as part of --nic option (we should extend) on on neutron port-create13:47
irenabvnic-type can be macvtap/pci direct/virtio13:47
irenabname can be more logical13:48
irenabFast/Slow/...13:48
rkukuraSo does nova interpret this --nic and pass the vnic_type to the port_create or port_update along with host_id?13:48
irenabrkukura: yes13:48
irenabwill do so13:48
ijwI would just go with macvtap (needs a PCI flavor, pci passthrough (ditto) and absent for a vnic, right now13:48
irenabijw: default = vnic13:48
irenabrkukura: can you please take a look and approve this blueprint?13:49
rkukuraIs it considered desirable for the user to pick between these vnic_types explicitly?13:49
*** BobBall has joined #openstack-meeting-alt13:49
rkukuravs. just saying they need low-latency high-bandwidth option13:50
ijwyes- firstly the device drivers change dramatically for passthrough and second you can't migrate with macvtap (which some people may care about)13:50
irenabon nova boot api it makes sense to go with later, but I think for neutron it can be explicit13:50
rkukuraMight also not get security groups, right?13:51
irenabrkukura: yes, with PCI passthrugh its not that easy13:51
rkukuraBut I get the point that the VM has to be prepared for the vnic_type chosen, so it needs to be explicit13:51
irenabfor pci passthrough VM image must have vendor drivers13:52
rkukuraOK, so having nova interpret --nic option and set binding:vnic_type seems reasonable13:52
ijwrkukura: I'm sure secgroups and antispoof will be a nightmare at some point, yes...13:53
irenabsorry, I have to leave now. I'll try to chat in few hours on IRC13:53
irenabbye13:53
rkukuraOK, so ml2 MechanismDrivers can then look at the binding:vnic_type, but what would they do with it?13:54
*** eankutse has joined #openstack-meeting-alt13:56
heyongliso for nova part we are get some agreement, so i going to update my bp, and i hope ijw can review it.13:56
heyongliseem time is up soon.13:56
ijwPlease, yes - mail me at my Cisco address if you want me to spot it ;)13:56
ijwOne othe thing13:56
ijw#topic Xen13:56
*** openstack changes topic to "Xen (Meeting topic: pci_passthrough)"13:56
ijwApparently the Xen guys (I've just been talking on another chat) have been implementing the PCI passthrough as it stands13:57
BobBall*cough* Sorry 'bout that! Not quite ready for external review - but we have patches up and are doing internal reviews with a few guys :)13:57
ijwSo, what I suggest is we try and get heyongli's compute changes agreed and coded sharpish (obviously we're going to miss I-2 but we get quiet time afterward) so that we can show them and get them to change their implmenentation in step13:57
ijwBad Bob.13:58
BobBallwe were aiming for I-2 but figured it'll slip a little so now were aiming for early I-313:58
BobBallyeah, we're very happy to update the impl as needed13:58
*** irenab has quit IRC13:58
ijwBobBall: the changes are that we don't (just) group by device and vendor any more, we can provide extra parameters in the config and group by them as well (per an externally defined list of 'significant' attributes)13:58
ijwThe discovery ought to be pretty similar, I think13:59
ijwheyongli is your guy13:59
BobBallAh, great.13:59
ijwTop of the hour.  Any more for any more?13:59
ijw#action heyongli to update BP, ijw to review13:59
ijw#action Annoy BobBall with superfluous changes to Xen13:59
heyonglibob, talk me any time.13:59
ijw#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Mon Jan 20 14:00:03 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-20-13.02.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-20-13.02.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-20-13.02.log.html14:00
*** rkukura has left #openstack-meeting-alt14:00
BobBallthanks heyongli14:00
heyonglibobball, i had to sleep, see you later. bye14:01
*** heyongli has quit IRC14:02
BobBallnight!14:02
*** gokrokve has joined #openstack-meeting-alt14:04
*** SergeyLukjanov_ is now known as SergeyLukjanov14:04
*** gokrokve has quit IRC14:09
*** sarob has joined #openstack-meeting-alt14:13
*** sarob has quit IRC14:18
*** glucas has joined #openstack-meeting-alt14:21
*** dprince has joined #openstack-meeting-alt14:27
*** BobBall has left #openstack-meeting-alt14:30
*** eharney has joined #openstack-meeting-alt14:34
*** coolsvap has joined #openstack-meeting-alt14:41
*** banix has joined #openstack-meeting-alt14:41
*** SergeyLukjanov is now known as SergeyLukjanov_a14:51
*** SergeyLukjanov_a is now known as SergeyLukjanov_14:52
*** BrianB_ has quit IRC14:54
*** banix has quit IRC14:57
*** gokrokve has joined #openstack-meeting-alt15:04
*** nosnos has quit IRC15:06
*** amytron has joined #openstack-meeting-alt15:06
*** banix has joined #openstack-meeting-alt15:08
*** gokrokve has quit IRC15:09
*** bcrochet has quit IRC15:11
*** bcrochet has joined #openstack-meeting-alt15:13
*** sarob has joined #openstack-meeting-alt15:13
*** DinaBelova is now known as DinaBelova_15:16
*** betsy has joined #openstack-meeting-alt15:17
*** sarob has quit IRC15:18
*** balajiiyer has joined #openstack-meeting-alt15:19
*** SergeyLukjanov_ is now known as SergeyLukjanov15:19
*** balajiiyer has left #openstack-meeting-alt15:19
*** DinaBelova_ is now known as DinaBelova15:20
*** rakhmerov has quit IRC15:22
*** rakhmerov has joined #openstack-meeting-alt15:22
*** Barker has joined #openstack-meeting-alt15:26
*** AlanClark has joined #openstack-meeting-alt15:28
*** jecarey has joined #openstack-meeting-alt15:33
*** banix has quit IRC15:34
*** gokrokve has joined #openstack-meeting-alt15:37
*** gokrokve has quit IRC15:37
*** gokrokve has joined #openstack-meeting-alt15:37
*** banix has joined #openstack-meeting-alt15:38
*** munlight has joined #openstack-meeting-alt15:40
*** kevinconway has joined #openstack-meeting-alt15:40
*** johnthetubaguy has quit IRC15:40
*** DennyZhang has joined #openstack-meeting-alt15:40
*** johnthetubaguy has joined #openstack-meeting-alt15:41
*** tanisdl has joined #openstack-meeting-alt15:41
*** mattgriffin has joined #openstack-meeting-alt15:42
*** mozawa has quit IRC15:44
*** IlyaE has joined #openstack-meeting-alt15:46
*** NikitaKonovalov is now known as NikitaKonovalov_15:47
*** munlight has quit IRC15:51
*** vkmc has joined #openstack-meeting-alt15:53
*** banix has quit IRC15:55
*** stanlagun has joined #openstack-meeting-alt15:58
*** banix has joined #openstack-meeting-alt16:02
*** johnthetubaguy has quit IRC16:02
*** johnthetubaguy has joined #openstack-meeting-alt16:05
*** jmontemayor has joined #openstack-meeting-alt16:05
*** antigluk has quit IRC16:07
*** SergeyLukjanov is now known as SergeyLukjanov_16:09
*** SushilKM has joined #openstack-meeting-alt16:10
*** antigluk has joined #openstack-meeting-alt16:11
*** eankutse has quit IRC16:11
*** sarob has joined #openstack-meeting-alt16:13
*** jcoufal has quit IRC16:15
*** DinaBelova is now known as DinaBelova_16:17
*** sarob has quit IRC16:18
*** nati_ueno has joined #openstack-meeting-alt16:19
*** johnthetubaguy has quit IRC16:22
*** johnthetubaguy has joined #openstack-meeting-alt16:22
*** SushilKM has left #openstack-meeting-alt16:30
*** NikitaKonovalov_ is now known as NikitaKonovalov16:32
*** SushilKM has joined #openstack-meeting-alt16:36
*** yamahata has quit IRC16:39
*** DinaBelova_ is now known as DinaBelova16:39
*** SushilKM has left #openstack-meeting-alt16:40
*** smemon92 has joined #openstack-meeting-alt16:44
*** eankutse has joined #openstack-meeting-alt16:47
*** colinmcnamara has joined #openstack-meeting-alt16:47
*** eankutse has quit IRC16:47
*** eankutse has joined #openstack-meeting-alt16:48
*** aignatov_ has quit IRC16:50
*** balajiiyer has joined #openstack-meeting-alt16:51
*** balajiiyer has left #openstack-meeting-alt16:51
*** colinmcnamara has quit IRC16:53
*** MarkAtwood has joined #openstack-meeting-alt16:54
*** SushilKM has joined #openstack-meeting-alt16:55
*** jmontemayor has quit IRC16:56
*** sarob has joined #openstack-meeting-alt16:59
*** doug_shelley66 has joined #openstack-meeting-alt16:59
*** ruhe is now known as _ruhe16:59
*** ashaikh has joined #openstack-meeting-alt17:00
sarob#startmeeting training-manuals17:00
openstackMeeting started Mon Jan 20 17:00:46 2014 UTC and is due to finish in 60 minutes.  The chair is sarob. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: training-manuals)"17:00
openstackThe meeting name has been set to 'training_manuals'17:00
sarob#help17:01
*** dguitarbite__ has joined #openstack-meeting-alt17:01
*** SushilKM has left #openstack-meeting-alt17:01
*** medlux has joined #openstack-meeting-alt17:01
*** AlanClark has quit IRC17:02
*** Barker has quit IRC17:02
*** nati_ueno has quit IRC17:02
sarob#topic moodle17:02
*** openstack changes topic to "moodle (Meeting topic: training-manuals)"17:02
*** dguitarbite_ has quit IRC17:02
*** dguitarbite has quit IRC17:02
sarobmorning/evening dude17:02
*** stanlagun has left #openstack-meeting-alt17:02
sarobdguitarbite: ping17:02
* sarob drumming fingers17:03
* sarob drumming head17:04
smemon92sarob,hello17:04
sarobdguitarbite__17:04
smemon92morning17:04
sarobhello17:04
dguitarbite__hello17:04
sarobhello17:05
saroblets talk moodle17:05
dguitarbite__we have hosted few sample questions for your reference17:05
*** shashank_ has joined #openstack-meeting-alt17:05
sarobsweeeet17:05
sarobwheres it at17:06
dguitarbite__salman is working on making it very easy to for people to contribute17:06
dguitarbite__http://os-trainingquiz.aptira.com17:06
saroblooking17:06
dguitarbite__its a bit slow as its testing server17:06
* sarob thinking17:06
*** jmontemayor has joined #openstack-meeting-alt17:08
*** tanisdl has quit IRC17:08
dguitarbite__sarob: smemon92 is working with me on Moodle App17:09
sarobcool17:09
dguitarbite__he is intern at Aptira17:09
*** medlux has quit IRC17:10
sarobso the buildout instructions17:10
sarobyou have notes?17:10
*** Barker has joined #openstack-meeting-alt17:11
*** colinmcnamara has joined #openstack-meeting-alt17:12
dguitarbite__sarob: did you login?17:12
dguitarbite__I have sent login credentials via email17:13
dguitarbite__last monday17:13
sarobtrying, i waiting on the new account email17:13
saroboh17:13
*** gokrokve has quit IRC17:13
colinmcnamarasorry guys. brainfart17:13
dguitarbite__for some reason the email goes into spam17:13
dguitarbite__I guess this domain is not recognized for now17:13
*** gokrokve has joined #openstack-meeting-alt17:13
dguitarbite__but for admin access I suggest you to use the one I sent, so that you get to experience how to host quiz17:14
*** AlanClark has joined #openstack-meeting-alt17:14
sarobill have to look further, but this looks exactly like what we need17:15
*** shashank_ has quit IRC17:15
sarobim thinking beyond17:15
sarobour testing needs17:16
sarobthis is good17:16
dguitarbite__we could add a few more modules17:16
sarobso the build instructions17:16
dguitarbite__re-design the UI, change theme17:16
sarobeasy?17:16
dguitarbite__yep, easy17:16
sarobcan you write that up in https://docs.google.com/a/yahoo-inc.com/document/d/1w7XhcJzdZi_DMT4eenA9rBY7n3uPieCzIfllaQZkXag/edit?usp=sharing17:17
dguitarbite__but I run Arch Linux and Gentoo (so I dont know if you like my easy!)17:17
sarobso we can prep to discuss with oss infra17:17
dguitarbite__yep, looking forward to porting this to Infra17:18
sarobi want to have lots of info on what they will have to do17:18
*** gokrokve has quit IRC17:18
*** jaypipes has joined #openstack-meeting-alt17:19
dguitarbite__ok, can we have a list of expected features? because for installing new modules (for features) we will have to tweak infra every time17:19
sarobinstall, restarting process, where does data get stored, who to contact when is goes grey17:19
sarobwe are going to be partnering with infra17:19
sarobso we need to explain as much as possible17:20
saroband be ready to answer as many questions as possible17:20
dguitarbite__how much expected time? I guess we decided before 10th Feb17:20
sarobthis could become the official testing thingy17:20
sarobso lets do our homework17:21
dguitarbite__ok17:21
sarobyup 08 feb17:21
sarobweek of17:21
sarobwe should start thinking about the summit next17:21
dguitarbite__yes, but I want to finish this by next week, so that I can focus better on Install Gudie17:22
dguitarbite__is that possible?17:22
sarobany ideas on using launchpad auth?17:22
sarobinstall guide?17:22
*** IlyaE has quit IRC17:23
saroboperations guide you mean?17:23
dguitarbite__Havana Install Guide for Operator Training17:23
dguitarbite__*operations sorry17:23
sarobyup, im eager to dig into that as well17:23
sarob#topic commercial training17:24
*** openstack changes topic to "commercial training (Meeting topic: training-manuals)"17:24
sarobso have you talked to sina?17:24
dguitarbite__sarob: need to look into Launchpad Auth for once. But I'm not sure.17:24
dguitarbite__sarob: yes, I forwarded your request to him, I guess he is quite busy ... we have a busy start to this year at Aptira.17:25
sarobwe can figure some on auth17:25
sarobsina, busy, understood17:25
sarobme too17:25
sarobfrenetic energy17:25
dguitarbite__yeah, same here17:26
sarob#topic clean up training guides17:26
*** openstack changes topic to "clean up training guides (Meeting topic: training-manuals)"17:26
*** DennyZhang has quit IRC17:26
sarobafter we get moodle prepped,17:26
sarobyou ready to finish the clean up?17:27
sarobwe should have only 5 books in the set17:27
sarobstart here, associate, operator, developer, architect17:27
dguitarbite__I am going for commercial training next month, we need to do it before hand17:27
dguitarbite__is that possible?17:28
sarobim ready17:28
dguitarbite__colin ?17:28
saroblets schedule a few hours and work on it together17:28
sarobbang it out17:28
sarobwhats your schedule look like this week?17:28
dguitarbite__I am quite free this week17:29
dguitarbite__infact it overlapps with cleaning training manuals as I need to prepare and update existing manuals for Commercial Training17:30
sarobso aptira is going to pull from training guide repo17:31
sarobto build commerical version?17:31
dguitarbite__just the extra part which is not yet ready in training repo17:31
sarobor do maven build17:31
sarobeh?17:31
sarobmeaning one of the books thats not finished?17:32
dguitarbite__just the Havana Installation Guide will be added which is not there in training repo17:32
dguitarbite__rest all is Associate Guide17:32
sarobah, well lets make it17:32
sarobso you can use it17:32
sarobthen you dont need to do anything special17:33
dguitarbite__I'm in, sure thing ... also it can replace basic-install. Thanks17:33
sarobyup17:33
sarobokay17:33
*** Barker has quit IRC17:33
saroblate your time tomorrow17:33
sarobor something else17:34
dguitarbite__works for me, give me a second I will get precise time17:34
sarobim available 9-11am PST, 1-3pm PST tomorrow17:36
sarobid rather the early slot17:36
dguitarbite__16:30 (4.30pm) to 20:30 8.30pm) IST17:37
dguitarbite__UTC17:38
dguitarbite__16:30 pm to 20:30 pm UTC17:38
dguitarbite__I guess its about the 10:30~11 am to 2pm PST17:38
smemon92ya, i will also join at 16:30 pm to 20:30 pm UTC17:38
sarob5-7pm utc tuesday is good then?17:40
dguitarbite__yes17:40
sarobcool, ill book it and invite colin17:40
*** pballand has joined #openstack-meeting-alt17:40
sarobinvite anyone else that is interested17:41
*** aignatov_ has joined #openstack-meeting-alt17:41
dguitarbite__ok, sounds good, yes I will try to invite more contributors17:42
sarob#action operations guide work session 5-7pm UTC tuesday 21 jan 201417:42
*** chandankumar_ has quit IRC17:42
sarob#topic any other business17:42
*** openstack changes topic to "any other business (Meeting topic: training-manuals)"17:42
*** svetlanad has quit IRC17:42
*** luqas has quit IRC17:43
*** svetlanad has joined #openstack-meeting-alt17:43
sarobokay, then17:43
saroblets break early17:43
dguitarbite__ok, need to get some zzz's ;)17:43
sarobcool, thx dude17:44
sarob#endmeeting17:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:44
openstackMeeting ended Mon Jan 20 17:44:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/training_manuals/2014/training_manuals.2014-01-20-17.00.html17:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/training_manuals/2014/training_manuals.2014-01-20-17.00.txt17:44
openstackLog:            http://eavesdrop.openstack.org/meetings/training_manuals/2014/training_manuals.2014-01-20-17.00.log.html17:44
dguitarbite__have a nice day, see ya guys tomm. By colinmcnamara,sean,smemon9217:44
colinmcnamaral8ters17:44
sarobah, didnt see you there17:45
smemon92bye17:45
colinmcnamarayup, I'm here17:45
*** _ruhe is now known as ruhe17:45
colinmcnamaraI had a brain fart, and drove in a 917:45
colinmcnamarawell, 8:3217:45
colinmcnamara8:5217:45
sarobah17:45
sarobi gots to run, check out eavesdrop for meet notes17:46
*** nati_ueno has joined #openstack-meeting-alt17:47
*** aignatov_ has quit IRC17:47
*** smemon92 has quit IRC17:47
*** IlyaE has joined #openstack-meeting-alt17:47
*** dguitarbite__ has quit IRC17:48
*** nati_ueno has quit IRC17:48
*** rakhmerov has quit IRC17:51
*** SergeyLukjanov_ is now known as SergeyLukjanov17:52
*** sarob has quit IRC17:53
*** sarob has joined #openstack-meeting-alt17:54
*** bnemec_ is now known as bnemec17:54
*** ruhe is now known as _ruhe17:57
*** Barker has joined #openstack-meeting-alt17:58
*** MarkAtwood has quit IRC18:00
*** boris-42 has quit IRC18:00
*** derekh has quit IRC18:03
*** chandankumar_ has joined #openstack-meeting-alt18:03
*** boris-42 has joined #openstack-meeting-alt18:04
*** nati_ueno has joined #openstack-meeting-alt18:04
*** NikitaKonovalov is now known as NikitaKonovalov_18:05
*** Barker has quit IRC18:05
*** gokrokve has joined #openstack-meeting-alt18:09
*** sarob has quit IRC18:09
*** shashank_ has joined #openstack-meeting-alt18:11
*** dguitarbite has joined #openstack-meeting-alt18:11
*** dguitarbite is now known as dguitarbyte18:11
*** rakhmerov has joined #openstack-meeting-alt18:11
*** rakhmerov has quit IRC18:11
*** rakhmerov has joined #openstack-meeting-alt18:12
*** johnthetubaguy has quit IRC18:13
*** Barker has joined #openstack-meeting-alt18:14
*** nadya__ has joined #openstack-meeting-alt18:16
*** jaypipes has quit IRC18:16
*** nadya__ has quit IRC18:17
*** yamahata has joined #openstack-meeting-alt18:21
*** pballand has quit IRC18:23
*** Leonr has joined #openstack-meeting-alt18:24
*** SergeyLukjanov is now known as SergeyLukjanov_a18:24
*** SergeyLukjanov_a is now known as SergeyLukjanov_18:25
*** dguitarbyte has quit IRC18:31
*** svetlanad has quit IRC18:33
*** svetlanad has joined #openstack-meeting-alt18:34
*** Barker has quit IRC18:35
*** Barker has joined #openstack-meeting-alt18:36
*** IlyaE has quit IRC18:37
*** jaypipes has joined #openstack-meeting-alt18:37
*** chandankumar_ has quit IRC18:44
*** venkatesh has joined #openstack-meeting-alt18:48
*** yamahata has quit IRC18:48
*** k4n0 has joined #openstack-meeting-alt18:51
*** nati_uen_ has joined #openstack-meeting-alt18:53
*** IlyaE has joined #openstack-meeting-alt18:55
*** nati_ueno has quit IRC18:56
*** sbalukoff has joined #openstack-meeting-alt19:00
*** SergeyLukjanov_ is now known as SergeyLukjanov19:02
*** venkatesh has quit IRC19:02
*** amotoki has joined #openstack-meeting-alt19:03
*** aignatov_ has joined #openstack-meeting-alt19:03
*** IlyaE has quit IRC19:03
*** amotoki has quit IRC19:03
*** balajiiyer has joined #openstack-meeting-alt19:05
*** yamahata has joined #openstack-meeting-alt19:13
*** jtomasek has quit IRC19:17
*** nati_uen_ has quit IRC19:22
*** IlyaE has joined #openstack-meeting-alt19:23
*** yogesh has joined #openstack-meeting-alt19:27
*** SergeyLukjanov is now known as SergeyLukjanov_a19:31
*** SergeyLukjanov_a is now known as SergeyLukjanov_19:32
*** svetlanad has quit IRC19:33
*** svetlanad has joined #openstack-meeting-alt19:34
*** SergeyLukjanov_ is now known as SergeyLukjanov19:35
*** k4n01 has joined #openstack-meeting-alt19:35
*** k4n0 has quit IRC19:37
*** nadya__ has joined #openstack-meeting-alt19:37
*** HenryG has quit IRC19:39
*** julienvey_ has joined #openstack-meeting-alt19:42
*** kevinconway_ has joined #openstack-meeting-alt19:48
*** kevinconway has quit IRC19:49
*** kevinconway_ is now known as kevinconway19:49
*** nadya__ has quit IRC19:50
*** banix has quit IRC19:51
*** gokrokve has quit IRC19:53
*** gokrokve has joined #openstack-meeting-alt19:53
*** dstufft has joined #openstack-meeting-alt19:54
*** rnirmal has joined #openstack-meeting-alt19:55
*** westmau5 is now known as westmaas19:55
*** hockeynut has joined #openstack-meeting-alt19:55
*** reaperhulk has joined #openstack-meeting-alt19:56
*** HenryG has joined #openstack-meeting-alt19:57
*** jjmb1 has quit IRC19:58
*** gokrokve has quit IRC19:58
*** _ruhe is now known as ruhe19:59
*** SheenaG has joined #openstack-meeting-alt20:00
*** redrobot has joined #openstack-meeting-alt20:00
*** banix has joined #openstack-meeting-alt20:00
*** k4n01 has left #openstack-meeting-alt20:02
*** aelkikhia has joined #openstack-meeting-alt20:03
jraimAlright, who is here for the Barbican meeting?20:03
reaperhulko/20:03
codekobepresent20:03
SheenaGpresent20:04
hockeynut(raises hand)20:04
*** zvital has joined #openstack-meeting-alt20:04
jraimokay, let's get started20:04
dstufft<-20:04
redroboto/20:04
jraim#startmeeting Barbican status meeting20:04
openstackMeeting started Mon Jan 20 20:04:34 2014 UTC and is due to finish in 60 minutes.  The chair is jraim. Information about MeetBot at http://wiki.debian.org/MeetBot.20:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:04
*** openstack changes topic to " (Meeting topic: Barbican status meeting)"20:04
openstackThe meeting name has been set to 'barbican_status_meeting'20:04
jraim#topic Incubation work20:04
*** openstack changes topic to "Incubation work (Meeting topic: Barbican status meeting)"20:04
jraimHokey dokey. It mostly looks like Rackspace folks, so let's just run through the incubation tasks20:05
jraimand we'll see if anyone else shows up20:05
*** nadya__ has joined #openstack-meeting-alt20:05
jraimSo, dstufft - did you get a chance to upload the new client to pypi?20:05
*** woodster1 has joined #openstack-meeting-alt20:05
dstufftjraim: waiting on 2 CR's to merge (which looks like they are now) to make the pypi page have rnedered output20:06
*** warlord_ has joined #openstack-meeting-alt20:06
jraimahh okay, the switch from md to rst?20:06
dstufftI don't think there was a decision on if it should be version 2.0 or 1.1 either20:06
warlord_yo20:06
dstufftjraim: ya20:06
dstufftand fixing it so the summary wasn't overwriting the file20:06
dstufftwhich wa sa mistake in the switch to pbr20:06
jraim#info so we can expect the new client version to be up today then20:07
redrobotdstufft, I think we agreed on 2.020:07
dstufftredrobot: ok!20:07
jraimcool20:07
jraimalright, the only other thing i have left is the devstack work20:07
dstufftI'm looking at pbr to see if i'm supposed to make it version = 2.0 or just tag it20:07
*** chadlung has joined #openstack-meeting-alt20:07
*** hmuren has joined #openstack-meeting-alt20:07
jraimafter a lot of discussion, it looks like using mod_wsgi instaed of uwsgi will be easier20:08
jraimso chad and I are working on getting that done20:08
jraimafter that, we can rebase and submit the patches20:08
aelkikhiacool20:08
jraimso, is everyone okay with me asking for us to be on the TC agenda for a week from tomorrow?20:08
reaperhulkI don't see a problem with that on my end20:08
jraim#action jraim to ask TC for our incubation to be on the agenda for next week20:09
woodster1sounds good to me20:09
jraimthat's all I have on my list. Anyone have anything else that we need for incubation?20:09
*** gokrokve has joined #openstack-meeting-alt20:09
hockeynutanything needed from test perspective?20:10
jraimI don't think so. We need to start moving some tests into Tempest, but I think that can happen after incubation20:10
*** nadya__ has quit IRC20:10
hockeynutok cool - wasn't sure of the timeframe20:10
jraimalright. anyone have anything else to talk about?20:11
jraimk. easy meeting. I'll hang out here in case anyone else shows up, but other than that, I think we are done until next week20:11
jraim#endmeeting20:11
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:11
openstackMeeting ended Mon Jan 20 20:11:42 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican_status_meeting/2014/barbican_status_meeting.2014-01-20-20.04.html20:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican_status_meeting/2014/barbican_status_meeting.2014-01-20-20.04.txt20:11
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican_status_meeting/2014/barbican_status_meeting.2014-01-20-20.04.log.html20:11
*** chadlung has left #openstack-meeting-alt20:13
*** hmuren has quit IRC20:15
*** balajiiyer has left #openstack-meeting-alt20:15
*** aignatov_ has quit IRC20:16
*** jcoufal has joined #openstack-meeting-alt20:18
*** aignatov_ has joined #openstack-meeting-alt20:19
*** SergeyLukjanov is now known as SergeyLukjanov_20:22
*** colinmcnamara has quit IRC20:26
*** svetlanad has quit IRC20:33
*** svetlanad has joined #openstack-meeting-alt20:34
*** gokrokve has quit IRC20:34
*** dstufft has left #openstack-meeting-alt20:34
*** gokrokve has joined #openstack-meeting-alt20:34
*** gokrokve_ has joined #openstack-meeting-alt20:35
*** markwash has joined #openstack-meeting-alt20:36
*** gokrokve has quit IRC20:39
*** Leon has joined #openstack-meeting-alt20:41
*** Leonr has quit IRC20:41
*** Leon is now known as Guest8881320:41
*** warlord_ has quit IRC20:44
*** NikitaKonovalov_ is now known as NikitaKonovalov20:45
*** Guest88813 has quit IRC20:46
*** Leonr has joined #openstack-meeting-alt20:47
*** derekh has joined #openstack-meeting-alt20:48
*** Barker has quit IRC20:49
*** funzo has quit IRC20:54
*** IlyaE has quit IRC20:54
*** funzo has joined #openstack-meeting-alt20:54
*** IlyaE has joined #openstack-meeting-alt20:55
*** rnirmal has quit IRC20:56
*** zvital has quit IRC20:57
*** DinaBelova is now known as DinaBelova_21:00
*** quarck has joined #openstack-meeting-alt21:00
*** dprince has quit IRC21:10
*** jaypipes has quit IRC21:12
*** colinmcnamara has joined #openstack-meeting-alt21:14
*** betsy has quit IRC21:14
*** quarck has quit IRC21:17
*** aelkikhia has quit IRC21:26
*** aelkikhia has joined #openstack-meeting-alt21:27
*** jjmb has joined #openstack-meeting-alt21:31
*** jjmb has quit IRC21:32
*** IlyaE has quit IRC21:32
*** svetlanad has quit IRC21:33
*** svetlanad has joined #openstack-meeting-alt21:34
*** aignatov_ has quit IRC21:34
*** ruhe is now known as _ruhe21:34
*** yamahata has quit IRC21:36
*** nati_ueno has joined #openstack-meeting-alt21:37
*** IlyaE has joined #openstack-meeting-alt21:37
*** yamahata has joined #openstack-meeting-alt21:38
*** NikitaKonovalov is now known as NikitaKonovalov_21:52
*** jaypipes has joined #openstack-meeting-alt21:52
*** mattgriffin has quit IRC21:52
*** rnirmal has joined #openstack-meeting-alt22:00
*** banix has quit IRC22:01
*** vkmc has quit IRC22:02
*** lblanchard has quit IRC22:02
*** doug_shelley66 has quit IRC22:03
*** nati_ueno has quit IRC22:04
*** jdob has quit IRC22:10
*** nati_ueno has joined #openstack-meeting-alt22:14
*** nati_ueno has quit IRC22:14
*** nati_ueno has joined #openstack-meeting-alt22:16
*** pdmars has quit IRC22:16
*** mattgriffin has joined #openstack-meeting-alt22:21
*** nati_ueno has quit IRC22:23
*** colinmcnamara has quit IRC22:24
*** colinmcnamara has joined #openstack-meeting-alt22:25
*** doug_shelley66 has joined #openstack-meeting-alt22:28
*** yamahata has quit IRC22:29
*** bdpayne has joined #openstack-meeting-alt22:29
*** woodster1 has quit IRC22:31
*** svetlanad has quit IRC22:33
*** svetlanad has joined #openstack-meeting-alt22:34
*** doug_shelley66 has quit IRC22:35
*** nati_ueno has joined #openstack-meeting-alt22:35
*** doug_shelley66 has joined #openstack-meeting-alt22:36
*** jcoufal has quit IRC22:36
*** yamahata has joined #openstack-meeting-alt22:38
*** jmontemayor has quit IRC22:40
*** colinmcnamara has quit IRC22:46
*** colinmcnamara has joined #openstack-meeting-alt22:47
*** nati_ueno has quit IRC22:52
*** jmontemayor has joined #openstack-meeting-alt22:52
*** shashank_ has quit IRC22:52
*** kevinconway has quit IRC22:54
*** nati_ueno has joined #openstack-meeting-alt22:54
*** nati_ueno has quit IRC23:03
*** nati_ueno has joined #openstack-meeting-alt23:04
*** sarob has joined #openstack-meeting-alt23:13
*** jecarey has quit IRC23:21
*** sarob has quit IRC23:22
*** eankutse1 has joined #openstack-meeting-alt23:28
*** eharney has quit IRC23:28
*** derekh has quit IRC23:30
*** eankutse has quit IRC23:32
*** svetlanad has quit IRC23:33
*** gokrokve_ has quit IRC23:33
*** gokrokve has joined #openstack-meeting-alt23:34
*** svetlanad has joined #openstack-meeting-alt23:34
*** gokrokve has quit IRC23:38
*** banix has joined #openstack-meeting-alt23:39
*** rraja has joined #openstack-meeting-alt23:41
*** Leonr has quit IRC23:44
*** banix has quit IRC23:44
*** jmontemayor has quit IRC23:58
*** hockeynut has quit IRC23:59

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