Wednesday, 2014-02-05

*** roshanagr has joined #openstack-meeting-alt00:01
*** ftcjeff has quit IRC00:03
*** RajeshMohan has quit IRC00:04
*** amcrn has quit IRC00:04
*** RajeshMohan has joined #openstack-meeting-alt00:05
*** RajeshMohan has quit IRC00:06
*** RajeshMohan has joined #openstack-meeting-alt00:07
*** julienvey_ has quit IRC00:08
*** RajeshMohan has quit IRC00:11
*** tanisdl has quit IRC00:11
*** RajeshMohan has joined #openstack-meeting-alt00:12
*** ijw has quit IRC00:13
*** david-lyle has joined #openstack-meeting-alt00:13
*** RajeshMohan has quit IRC00:16
*** RajeshMohan has joined #openstack-meeting-alt00:16
*** sarob has joined #openstack-meeting-alt00:18
*** sarob_ has quit IRC00:19
*** roshanagr2 has joined #openstack-meeting-alt00:29
*** roshanagr has quit IRC00:31
*** atiwari has quit IRC00:33
*** sacharya has joined #openstack-meeting-alt00:35
*** Ranjitha has quit IRC00:35
*** ijw has joined #openstack-meeting-alt00:37
*** sarob has quit IRC00:39
*** michael-yu has quit IRC00:41
*** jcoufal has quit IRC00:42
*** ccrouch has joined #openstack-meeting-alt00:42
*** jcoufal has joined #openstack-meeting-alt00:42
*** ccrouch1 has quit IRC00:43
*** ccrouch has quit IRC00:46
*** gokrokve_ has joined #openstack-meeting-alt00:50
*** sarob has joined #openstack-meeting-alt00:52
*** yamahata has joined #openstack-meeting-alt00:53
*** gokrokve has quit IRC00:53
*** sarob has quit IRC00:56
*** nosnos has joined #openstack-meeting-alt00:57
*** gokrokve_ has quit IRC00:57
*** banix has joined #openstack-meeting-alt00:59
*** nosnos has quit IRC01:01
*** nosnos has joined #openstack-meeting-alt01:01
*** Ranjitha has joined #openstack-meeting-alt01:04
*** Ranjitha has quit IRC01:09
*** ccrouch has joined #openstack-meeting-alt01:15
*** mestery has quit IRC01:15
*** cody-somerville has quit IRC01:17
*** jjmb has quit IRC01:27
*** sbalukoff has quit IRC01:37
*** morazi has quit IRC01:41
*** roshanagr2 has quit IRC01:43
*** bill_az_ has quit IRC01:48
*** amcrn has joined #openstack-meeting-alt01:48
*** michael-yu has joined #openstack-meeting-alt01:55
*** sarob has joined #openstack-meeting-alt01:57
*** sacharya has quit IRC02:00
*** sarob has quit IRC02:03
*** tanisdl has joined #openstack-meeting-alt02:05
*** sarob has joined #openstack-meeting-alt02:08
*** sarob has quit IRC02:12
*** nati_ueno has quit IRC02:14
*** amotoki has joined #openstack-meeting-alt02:14
*** ccrouch has quit IRC02:16
*** coolsvap_away has quit IRC02:34
*** gokrokve has joined #openstack-meeting-alt02:41
*** jcoufal has quit IRC02:42
*** sarob has joined #openstack-meeting-alt02:43
*** jcoufal has joined #openstack-meeting-alt02:43
*** sarob has quit IRC02:45
*** sarob has joined #openstack-meeting-alt02:45
*** sarob_ has joined #openstack-meeting-alt02:47
*** ijw has quit IRC02:47
*** arnaud___ has quit IRC02:48
*** arnaud__ has quit IRC02:48
*** sarob has quit IRC02:50
*** sarob_ has quit IRC02:57
*** doug_shelley66 has quit IRC02:57
*** sarob has joined #openstack-meeting-alt02:58
*** doug_shelley66 has joined #openstack-meeting-alt02:58
*** jcoufal has quit IRC02:59
*** sarob has quit IRC03:02
*** Haiying has joined #openstack-meeting-alt03:07
*** gokrokve has quit IRC03:10
*** gokrokve has joined #openstack-meeting-alt03:13
*** michael-yu has quit IRC03:21
*** amcrn has quit IRC03:25
*** sarob has joined #openstack-meeting-alt03:33
*** mozawa has joined #openstack-meeting-alt03:38
*** tchaypo has joined #openstack-meeting-alt03:41
*** doug_shelley66 has quit IRC03:54
*** ijw has joined #openstack-meeting-alt03:58
*** tanisdl has quit IRC04:01
*** ijw has quit IRC04:02
*** harlowja is now known as harlowja_away04:03
*** bdpayne has quit IRC04:05
*** bdpayne has joined #openstack-meeting-alt04:06
*** bdpayne has quit IRC04:06
*** sarob has quit IRC04:07
*** sarob has joined #openstack-meeting-alt04:08
*** baoli has joined #openstack-meeting-alt04:09
*** sarob has quit IRC04:12
*** baoli has quit IRC04:13
*** roshanagr has joined #openstack-meeting-alt04:14
*** ccrouch has joined #openstack-meeting-alt04:15
*** IlyaE has joined #openstack-meeting-alt04:28
*** roshanagr has quit IRC04:30
*** gokrokve has quit IRC04:36
*** gokrokve has joined #openstack-meeting-alt04:40
*** SushilKM has joined #openstack-meeting-alt04:44
*** ijw has joined #openstack-meeting-alt04:50
*** michael-yu has joined #openstack-meeting-alt04:52
*** IlyaE has quit IRC04:52
*** ijw has quit IRC04:54
*** akuznetsov has joined #openstack-meeting-alt04:56
*** SushilKM has quit IRC04:57
*** dguitarbite has joined #openstack-meeting-alt04:57
*** ijw has joined #openstack-meeting-alt04:58
*** marun has quit IRC05:02
*** marun has joined #openstack-meeting-alt05:03
*** sarob has joined #openstack-meeting-alt05:09
*** Haiying has quit IRC05:11
*** sarob has quit IRC05:15
*** jcooley_ has quit IRC05:19
*** Ranjitha has joined #openstack-meeting-alt05:22
*** IlyaE has joined #openstack-meeting-alt05:23
*** gokrokve has quit IRC05:24
*** SushilKM has joined #openstack-meeting-alt05:25
*** Ranjitha_ has joined #openstack-meeting-alt05:28
*** Ranjitha has quit IRC05:28
*** Ranjitha_ is now known as Ranjitha05:28
*** banix has quit IRC05:29
*** gokrokve has joined #openstack-meeting-alt05:31
*** michael-yu has quit IRC05:32
*** ijw_ has joined #openstack-meeting-alt05:36
*** ijw has quit IRC05:36
*** igor__ has joined #openstack-meeting-alt05:37
*** banix has joined #openstack-meeting-alt05:37
*** igor has quit IRC05:37
*** mestery has joined #openstack-meeting-alt05:38
*** mestery has quit IRC05:38
*** mestery has joined #openstack-meeting-alt05:39
*** SushilKM has quit IRC05:40
*** sbalukoff has joined #openstack-meeting-alt05:42
*** mestery_ has joined #openstack-meeting-alt05:44
*** sbalukoff has quit IRC05:46
*** mestery has quit IRC05:46
*** gokrokve has quit IRC05:46
*** gokrokve has joined #openstack-meeting-alt05:47
*** sbalukoff has joined #openstack-meeting-alt05:47
*** jcooley_ has joined #openstack-meeting-alt05:48
*** nati_ueno has joined #openstack-meeting-alt05:51
*** gokrokve has quit IRC05:51
*** mestery_ has quit IRC06:00
*** banix has quit IRC06:03
*** ijw_ has quit IRC06:07
*** ijw has joined #openstack-meeting-alt06:08
*** sarob has joined #openstack-meeting-alt06:12
*** sarob has quit IRC06:17
*** SushilKM has joined #openstack-meeting-alt06:19
*** igor__ has quit IRC06:21
*** doug_shelley66 has joined #openstack-meeting-alt06:49
*** SushilKM has quit IRC07:02
*** boris-42_ has quit IRC07:05
*** nati_ueno has quit IRC07:05
*** nati_ueno has joined #openstack-meeting-alt07:06
*** coolsvap has joined #openstack-meeting-alt07:09
*** jcooley_ has quit IRC07:12
*** jcooley_ has joined #openstack-meeting-alt07:12
*** nati_ueno has quit IRC07:14
*** nati_ueno has joined #openstack-meeting-alt07:14
*** nati_ueno has quit IRC07:15
*** sarob has joined #openstack-meeting-alt07:15
*** nati_ueno has joined #openstack-meeting-alt07:15
*** nati_ueno has quit IRC07:16
*** ijw has quit IRC07:16
*** nati_ueno has joined #openstack-meeting-alt07:17
*** jcooley_ has quit IRC07:17
*** DinaBelova_ is now known as DinaBelova07:19
*** sarob has quit IRC07:19
*** nati_ueno has quit IRC07:25
*** nati_ueno has joined #openstack-meeting-alt07:26
*** IlyaE has quit IRC07:27
*** nati_ueno has quit IRC07:28
*** nati_ueno has joined #openstack-meeting-alt07:29
*** yamahata has quit IRC07:36
*** nati_ueno has quit IRC07:37
*** nati_ueno has joined #openstack-meeting-alt07:37
*** nati_ueno has quit IRC07:40
*** igormarnat_ has joined #openstack-meeting-alt07:45
*** ijw has joined #openstack-meeting-alt07:47
*** dguitarbite has quit IRC07:49
*** dguitarbite has joined #openstack-meeting-alt07:49
*** igormarnat_ has quit IRC07:55
*** julienvey_ has joined #openstack-meeting-alt08:04
*** flaper87|afk is now known as flaper8708:05
*** yamahata has joined #openstack-meeting-alt08:07
*** yamahata has quit IRC08:11
*** jtomasek has joined #openstack-meeting-alt08:18
*** jtomasek has quit IRC08:20
*** julienvey_ has quit IRC08:21
*** jtomasek has joined #openstack-meeting-alt08:22
*** bauzas has joined #openstack-meeting-alt08:26
*** akuznetsov has quit IRC08:28
*** akuznetsov has joined #openstack-meeting-alt08:31
*** lsmola has quit IRC08:46
*** krtaylor has quit IRC08:47
*** krtaylor has joined #openstack-meeting-alt08:49
*** krtaylor has quit IRC08:55
*** jcoufal has joined #openstack-meeting-alt08:55
*** nacim has joined #openstack-meeting-alt08:55
*** krtaylor has joined #openstack-meeting-alt08:56
*** aignatov_ is now known as aignatov08:59
*** lsmola has joined #openstack-meeting-alt08:59
*** aignatov is now known as aignatov_09:02
*** derekh has joined #openstack-meeting-alt09:05
*** aignatov_ is now known as aignatov09:10
*** fungi has quit IRC09:12
*** fungi has joined #openstack-meeting-alt09:16
*** sarob has joined #openstack-meeting-alt09:17
*** lsmola has quit IRC09:19
*** sarob has quit IRC09:23
*** boris-42_ has joined #openstack-meeting-alt09:23
*** igormarnat_ has joined #openstack-meeting-alt09:26
*** d0ugal has quit IRC09:29
*** d0ugal has joined #openstack-meeting-alt09:29
*** lsmola has joined #openstack-meeting-alt09:32
*** melodous has quit IRC09:34
*** safchain has joined #openstack-meeting-alt09:36
*** julim has joined #openstack-meeting-alt09:42
*** baoli has joined #openstack-meeting-alt09:49
*** baoli has quit IRC09:50
*** jcoufal has quit IRC09:54
*** cody-somerville has joined #openstack-meeting-alt10:05
*** baoli has joined #openstack-meeting-alt10:06
*** baoli has quit IRC10:08
*** johnthetubaguy has joined #openstack-meeting-alt10:09
*** sarob has joined #openstack-meeting-alt10:20
*** jcoufal has joined #openstack-meeting-alt10:23
*** aignatov is now known as aignatov_10:25
*** sarob has quit IRC10:27
*** boris-42_ has quit IRC10:28
*** mozawa has quit IRC10:39
*** boris-42_ has joined #openstack-meeting-alt10:40
*** nosnos has quit IRC10:53
*** johnthetubaguy has quit IRC10:59
*** johnthetubaguy has joined #openstack-meeting-alt11:03
*** jtomasek has quit IRC11:05
*** jtomasek has joined #openstack-meeting-alt11:05
*** aignatov_ is now known as aignatov11:14
*** dguitarbite has quit IRC11:17
*** sarob has joined #openstack-meeting-alt11:24
*** sarob has quit IRC11:29
*** vkmc has joined #openstack-meeting-alt11:43
*** vkmc has joined #openstack-meeting-alt11:43
*** lsmola has quit IRC11:46
*** irenab has joined #openstack-meeting-alt11:50
*** igor_ has joined #openstack-meeting-alt11:57
*** Ranjitha has quit IRC11:58
*** ruhe has joined #openstack-meeting-alt11:59
*** lsmola has joined #openstack-meeting-alt12:01
*** igormarnat_ has quit IRC12:01
*** ruhe is now known as ruhe_12:06
*** ruhe_ is now known as ruhe12:06
*** yamahata has joined #openstack-meeting-alt12:19
*** coolsvap has quit IRC12:33
*** cody-somerville has quit IRC12:39
*** sgordon has joined #openstack-meeting-alt12:42
*** ruhe is now known as ruhe_12:44
*** ruhe_ has quit IRC12:48
*** lsmola has quit IRC12:53
*** baoli has joined #openstack-meeting-alt12:54
*** amotoki has quit IRC12:55
*** lsmola has joined #openstack-meeting-alt12:56
*** mozawa has joined #openstack-meeting-alt12:57
*** baoli has quit IRC12:59
*** lblanchard has joined #openstack-meeting-alt13:00
*** baoli has joined #openstack-meeting-alt13:00
baoli#startmeeting PCI Passthrough13:00
openstackMeeting started Wed Feb  5 13:00: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:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: PCI Passthrough)"13:00
openstackThe meeting name has been set to 'pci_passthrough'13:00
irenabhi13:00
baoliHi13:01
irenabshort update with current status?13:02
baoliIrenab, Shall we wait for others13:02
irenabsure13:03
*** rkukura has joined #openstack-meeting-alt13:05
*** BrianB_ has joined #openstack-meeting-alt13:05
rkukurahi13:05
irenabrkukura:hi13:06
rkukurasnow day here - had to shovel a path to take the trash out13:06
baoliHi rkukura13:06
irenabrkukura: we are more than month without rain...13:07
baoliwe'll have 8-12 inches snow today13:08
irenabbaoli: shall we wait for Sandhya?13:08
rkukuraexpecting 10-12" of snow today - looks like about 8" so far13:08
rkukurabaoli: Where are you located?13:08
baoliirenab, yes. a couple of more minutes13:08
baolirkukura, westford/boston13:08
baolirkukura, is your office in westford?13:09
rkukurabaoli: I'm in Sudbury, office is in Westford13:09
*** pdmars has joined #openstack-meeting-alt13:09
irenabguys, till we wait for Sandhya, how we make progress with vnic_type?13:09
baolirkukura, we are neighbors13:09
rkukuraAt least the couple days a week I work from the office13:10
baoliyep13:10
*** dprince has joined #openstack-meeting-alt13:11
baoliirenab, regarding vnic_type, I'd like to see normal users can choose to go with sriov or virtio.13:13
irenabrkukura: did you have any chance to discuss it with other core team members? Shall I send an email to the mailing list?13:13
irenabbaoli: I think I'll be able to push the code for it as draft either later today or tomorrow13:15
rkukurairenab: I think you should send an email to openstack-dev.13:15
rkukurairenab: That's probably best - makes it concrete.13:15
baoliirenab, that sounds great13:15
irenabrkukura: Ok, thanks13:15
irenabrkukura: It will be a hard to present without having nova api defined..13:16
baoliNot sure if you guys are aware of the change proposed for ipv6. Two new keywords for ipv6 subnet: ipv6_ra_mode and ipv6_address_mode. You'd expect a normal user to fully understand ipv6 before using it13:17
baoliintuitively, a normal user should just say "I want ipv6" for my network13:17
rkukurabaoli: I'm no IPv6 expert, but don't those effect what happens inside the VM?13:18
irenabbaoli: it has permissions as regular user in  policy.py ?13:18
*** cody-somerville has joined #openstack-meeting-alt13:18
*** cody-somerville has joined #openstack-meeting-alt13:18
baolirkukura, it just provides ipv6 connectivity13:18
baoliirenab, no restrictions imposed in policy.py13:19
baolion subnet13:19
rkukuraWith IPv4, the VM needs to know whether DHCP is being used. Aren't these similar?13:19
irenabbaoli: only admin or network owner can create subnet13:19
baolirkukura, in addition to that, a user needs to say dhcp stateless or dhcp statefull, or slacc, etc13:19
irenabbaoli: can you please send the link to review?13:20
rkukurabaoli: Someone should be looking out for the usability of this for normal tenants!13:21
irenabbaoli: I am not sure it supposed to be managed by regular user, should be admin or network owner13:21
baoliirenab, you mean the ipv6 change?13:21
irenabbaii: yes13:21
irenabbaoli:yes13:22
baoliirenab, if it's ok for network owner, then it's ok for a network owner to say that I need a sriov port13:22
rkukuraIf this precedent helps with the case that exposing vnic_type to nomral users is the way to go, fine.13:22
*** ruhe has joined #openstack-meeting-alt13:22
rkukuraDon't forget that tenants can use networks owned by someone else, as long as the shared attribute is set.13:23
irenabso normal_user =network_owner for the vnic_type case?13:23
rkukuraThere are also proposals being discussed for hierarchies of tenants13:23
irenabI need to state it in the neutron policy.py13:24
rkukuraI do not think we should restrinct SR-IOV to the case where the tenant is the owner of the network.13:24
irenabits either admin or owner13:24
irenabrkukura: would it be ok?13:24
rkukuraNetworks (and their subnets) are often shared, especially provider networks.13:24
rkukuraI don't think admin or owner is correct for attaching to a network13:25
baolirkukura, in the current proposal, sriov ports are shared among tenants!13:25
rkukuraWhy not just let normal users request SR-IOV via vnic_type?13:26
irenabaccording to policy.py  "create_port:mac_learning_enabled": "rule:admin_or_network_owner"13:27
*** igor_ has quit IRC13:27
irenabI think we should have same for vnic_type13:27
*** sarob has joined #openstack-meeting-alt13:27
*** igor_ has joined #openstack-meeting-alt13:28
rkukuraThis whole API is getting way too complicated!13:28
rkukuramac_learning_enabled is a nicira-specific extension, it looks like.13:29
baoliirenab, I think that --binding:vnic_type should have at least have the same restriction as the command port-create.13:29
baoliSo I think it should be admin_or_network_owner13:30
*** jdob has joined #openstack-meeting-alt13:30
rkukuraI have no idea what the use case is for mac_learning_enabled, so maybe it is something normal users would never use unless they own the network13:30
rkukurabaoli: Wouldn't using admin_or_network_owner would prevent normal tenants from requesting SR-IOV on a port attached to a shared network? Maybe I'm wrong and this poilicy rule takes --shared into account?13:31
irenabrkukura: do not see any other examle that fits... MAC and IP seems indeed something the only admin_or_network_owner should manage13:31
irenabrkukura: there is also rule "shared", not sure how it works13:32
irenabrkukura: so we can mix13:32
rkukuraInteresting - I do see now that specifying mac_address or fixed_ips is admin_or_network_owner. I'm getting convinced that that rule must take sharing into account.13:33
*** igor_ has quit IRC13:33
baolirkukura, good point. I think that i need to study the policy.py  a bit more13:33
*** sarob has quit IRC13:34
irenabanyway seems that  the current discussion proves that there is a good chance vnic_type may have different policy rules that other items that may land into binding:profile13:34
rkukuraI apologize if my misinformation on this has been leading the team astray!13:34
rkukurairenab: Agreed.13:35
*** jecarey has joined #openstack-meeting-alt13:35
irenabrkukura: I think your questions are in place and cause us provide good answers13:35
irenabso seems that no reason to block the vnic_type bp, what do you think?13:36
rkukurairenab: I'm fine with going forward with it.13:38
baolirkukura, a shared network can be used by any tenant, is that right?13:38
irenabbaoli: there was a question sadasu sent to the mailing list on neutron SRIOV ports and MD. After vnic_type I wanted to start with SRIOVPortMDBase. Do know if sadasu started some work on this?13:41
*** jecarey has quit IRC13:41
rkukurabaoli: That is my understanding. The mailing list discussion regarding hierarchies of tenants/projects may eventually make that more useful.13:41
baoliirenab, not sure if she would do something.13:42
irenabbaoli: ok..13:42
baoliso for vnic_type, we'd go with binding:vnic_type, and set the rule as admin_or_network_owner? is that agreed?13:43
irenabbaoli: I agree13:43
baolicool13:44
baolilet's move on to SRIOVPortMDBase13:44
irenabrkukura: do you agree?13:44
rkukurairenab: I agree as long as admin_or_network_owner really does work for shared networks13:45
irenabrkukura: I'll do some test on some existing attribute to verify13:46
baolirkukura, that's the catch we have to experiment with. But I think that should be same for someone to create a port on a shared network regardless the vnic_type. I maybe wrong, though13:46
*** ruhe is now known as ruhe_13:46
rkukurairenab: Great. Very interested in what you find out.13:46
irenabthe rule can be also the rule like "rule:admin_or_owner or rule:shared",13:47
baoliIrenab, let us know once you find out13:47
irenabbaoli: sure13:47
irenabbaoli: can you please give short update for nova side?13:47
*** sadasu has joined #openstack-meeting-alt13:48
baoliirenab, sure13:48
baolibasically, yunhong would like to go with a simpler version for Icehouse13:48
baoliThe major enhancement would be: a) add attr supports in the whitelist b) support multiple aliases13:49
baoliand c) support stats based on aliases13:49
baolihe is asking for approval13:50
irenabbaoli: this will work without need to create VM flavor with PCI alias, right?13:50
baoliIf that can be done, then we should be ok. I also asked for the API to support correlation between the allocated device with the requested networks.13:51
baoliirenab, no vm flavor for network.13:51
irenabbaoli: and for your bp, is it on the way?13:51
*** nickchase has joined #openstack-meeting-alt13:52
baoliirenab, I put John's name as approver. I need to send an email as well13:52
rkukuraIs requesting the physical network still implicit in requesting the PCI device? I saw some mention in baoli's wiki of nova asking neutron for the physical_network, but don't think that is possible.13:52
irenabbaoli: thanks13:53
irenabbaoli: so we need to well define nova-neutron API for setting PCI details and returning VIF details/VIF_TYPE13:54
baolirkukura, what is not possible? Can you clarify it?13:54
*** ruhe_ is now known as ruhe13:54
*** ruhe has quit IRC13:54
*** tedross has joined #openstack-meeting-alt13:54
sadasurkukura: yes, the wiki says that, why not possible?13:55
sadasuI thought phy_net can be part of the vif_details13:55
rkukurabaoli: With ML2, a virtual network can be made up of multiple segments, which may have different values for provider:phyiscal_network. I don't think either nova or neutron could know which segment's physical_network to  use.13:55
rkukurasadasu: Once port binding occurs, a segment has been picked, and the MD can put that segment's physical_network into binding:vif_details.13:56
baolirkukura, do you have an example on how that's used and provisioned?13:56
baolirkukura, I mean multi-segments13:57
rkukuraIt seemed to me that the physical_network was needed in nova before the VM is scheduled. Port binding can't be done until after the VM is scheduled.13:57
sadasurkukura: yes. didn't know of his sequencing problem13:57
baolirkukura, I assumes that a nuetron net is associated with a physical net13:57
*** igor_ has joined #openstack-meeting-alt13:58
baolirkukura, and a port is created from a neutron net13:58
irenabrkukura: it  should possible to support single segment network, right?13:58
baolitime is up. can we switch to a different channel?13:59
rkukuraSingle segment networks are certainly possible, and most common right now, but the ML2 model allows multi-segment networks.13:59
irenabI can for ~10 mins more13:59
baoliOk, rkukura, could you please send me an email on that? I'd like to know more details14:00
irenabme too14:00
*** igor__ has joined #openstack-meeting-alt14:00
*** sadasu has quit IRC14:00
rkukuraWhat happened to the plan for the admin to create flavors or host aggregates with SR-IOV connectivity to specific physical networks?14:00
irenabrkukura: Host aggregates can be done today14:01
*** sadasu has joined #openstack-meeting-alt14:01
*** nickchase has quit IRC14:01
rkukuraWe should #endmeeting14:02
baoliif no one is using it, we can continue a bit more14:02
*** Guest29565 is now known as leifz14:02
rkukuraOK, but if someone else is scheduled and ready they should speak up14:03
*** nickchase has joined #openstack-meeting-alt14:03
*** igor_ has quit IRC14:03
baolichecked, it's open14:04
irenabrkukura: with multi-segment + provider netowrk, should the network be created as with regular plugin?14:04
baoliI think that we only care about the first segment, which is the one that the compute node immediately connects with.14:05
*** sadasu has quit IRC14:06
rkukurairenab: I'm not sure what you mean. The ML2 plugin supports both the providernet and multiprovidernet extensions. Either API extension can be used to create single-segment provider networks. Only the multiprovidernet extension can be used to create multi-segment provider networks. Creating normal tenant networks doesn't use either extension.14:06
rkukurabaoli: Port binding can pick any of the segments. First is not special. In fact there is a bug right now that the order of the segments isn't even deterministic.14:06
baolirkukura, is the multi-segments support documented anywhere?14:07
irenabso now I don't understand how vnic_type helps us ...14:08
rkukurabaoli: I'm not sure, but multiprovidernet should be covered in the API guide.14:08
rkukuraHere's what I thought was supposed to happen:14:09
irenabbaoli: I think that provider net is documented in neutron admin guide14:09
irenabbut not with ML2, if its differ14:09
baolirkukura, please go ahead to describe it. I'll take a look at it offline as well.14:10
rkukura1) The admin creates a flavor or host aggregate with SR-IOV connectivity to a specific physical network14:10
rkukura2) Probably the admin, or someone else, creates a virtual VLAN network on that physical network, and gives the tenant access (as owner or shared)14:11
rkukuraactually I guess 2) needs to be the admin14:11
baolirkukura, in 2), a neutron net is associated with a physical net, right?14:12
rkukura3) The tenant creates a neutron port on that network specifying --binding:vnic_type <something other than virtio>14:12
*** ftcjeff has joined #openstack-meeting-alt14:12
*** eankutse has joined #openstack-meeting-alt14:12
rkukura4) The tenant boots a VM specifying the flavor or host aggregate with SR-IOV connectivity to that same network14:13
*** eankutse has quit IRC14:13
rkukuraIn 4) the user specifying --nic with the port ID from 314:14
*** eankutse has joined #openstack-meeting-alt14:14
irenabrkukura: I don't see a problem here. neutron net is associated with physicla network and nova had admin access, right?14:14
rkukura5) Nova takes care of reserving the PCI slot and PF when scheduling the VM, and stores these details in the binding:profile attrbiute of the port created in 314:14
baolirkukura, also in 1), we need to tag the pci devices with a specific physical network on each compute nodes.14:14
rkukura6) Either in 5 or after, nova sets binding:host_id to specify, which triggers ML2 port biinding14:15
baolirkukura, if by port binding, you mean to bind a port to a host, then we don't have a problem here. The association of a port with a physical net is determined when the port is created14:17
*** bill_az has joined #openstack-meeting-alt14:17
rkukura7) ML2 port binding tries the registered mechanism drivers. Ones that don't support the binding:vnic_type refuse to binding. The SR-IOV mechanism drivers do try to bind, and look for a segment for which the PCI device has connectivity to the segment's physical network14:17
baolithat information is then used for scheduling a host. We don't want to do a trail-and-error approach in selecting a host to 'bind'14:18
baolisorry, trial-and-error14:19
rkukurabaoli: Port binding is what determines which network segment is being used, what the binding:vif_type is, and (soon) what is in binding:vif_details.14:19
baolibut in 2), you said that a vlan net(a nuetron net) is associated with a physical net, right?14:19
irenabrkukura: its first time in the flow you mentioned network segment. when it was created?14:19
rkukurabaoli: My understanding was that nova's scheduler would schedule on a host from the aggregate or flavor with the needed connectivtiy, so as long as the user gets this right, its not trial and errror.14:20
baolirkukura, no. that's not the plan for now14:20
rkukurairenab: The network segment(s) is/are created in 214:21
*** PeterS has quit IRC14:21
*** sarob has joined #openstack-meeting-alt14:22
baolirkukura, regardless sriov, can you provide a work flow for multi-segment?14:22
irenabrkukura: 2) says, network is created14:22
rkukurabaoli: What is the current plan for making nova schedule on a host with an available SR-IOV VF with connectivity to the needed physical network then?14:22
baolirkukura, it's described in my wiki14:22
irenabI have to go, please do end meeting by the end to make logs available.14:23
baoli1) you tag each pci device with the attached physical net14:23
baoli2) compute node reports pci stats as "host:net-group:phynet1:count" to the controller/scheduler14:23
*** PeterS has joined #openstack-meeting-alt14:23
rkukurabaoli: Right now multi-segment networks can only be created by passing in a list of maps describing each segment to create network or update network, using the multiprovider extension.14:23
baolirkukura, can you provide how it's done in terms of neutron config and work flow (cli commands, etc)?14:24
baoli3) create a neutron net that is associated with a physical net14:25
*** bill_az_ has joined #openstack-meeting-alt14:25
baoli4) create a neutron port on this net with --vnic-type=direct14:25
*** bill_az has quit IRC14:25
baoli5) nova boot --nic port-id=<port-uuid-in-abovr>14:25
rkukurabaoli: I can track down the exact syntax. They aren't too commonly used right now, but the capability is there. The bridging between the segments in not managed by neutron and must be setup administratively right now.14:26
baolirkukura, are all the segements bridged together?14:26
baoliadministratively?14:26
*** amytron has quit IRC14:27
rkukurabaoli: Yes, that's what makes them the same virtual L2 network, right?14:27
baolirkukura, so on each compute node, the starting segement may be different?14:27
rkukuraLonger term plans are for some of this to be automated - maybe creating a vlan segment shared within a specific rack, but a vxlan segment connecting the various top of rack switches14:28
rkukurabaoli: Not sure what you mean by "starting segment"?14:29
baolirkukura, I think that we need to do some study on that. Thanks for bringing that up.14:29
rkukurabaoli: In your steps above, what forces nova to schedule the VM on a node with an available VF for an SR-IOV device with connectivity to the needed physical network?14:29
baoliwe have a pci filter scheudler that has to be loaded into the nova scheduler14:30
*** itzikb has joined #openstack-meeting-alt14:30
baolithat pci filter scheduler works off the stats: host:net-group:phynet:count14:31
sgordonspeaking of nova...which bps are still active on the nova side for icehouse?14:31
sgordondo we need to seek core reviewers?14:31
baoli#endmeeting14:31
rkukuraAnd how does the pci filter scheduler know what net-group is needed?14:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:31
openstackMeeting ended Wed Feb  5 14:31:17 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-05-13.00.html14:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-05-13.00.txt14:31
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-05-13.00.log.html14:31
sgordon(rbryant just pushed out bps that hadn't been approved yet)14:31
*** boris-42_ has quit IRC14:31
rkukurasgordon: We've gone way past our scheduled slot on this channel. Not sure about the nova side BPs.14:32
baolisgordon, are you asking for nova BPs on PCI passthrough?14:34
sgordonbaoli, yes14:34
sgordonbaoli, and any required for sr-iov too14:34
russellbi think we should be able to do the initial pci API, at least, but would love to get in whatever we can14:35
russellbneed reviewer sponsors at this point on anything that wasn't already approved though14:35
*** irenab has quit IRC14:35
*** ruhe has joined #openstack-meeting-alt14:35
baolihttps://blueprints.launchpad.net/nova/+spec/pci-extra-info-icehouse14:36
sgordonso that one in particular was one i was looking at14:36
sgordonit's no longer targeted as it has no code submissions, and no core reviewers signed up14:36
baoliand https://blueprints.launchpad.net/nova/+spec/pci-passthrough-sriov14:37
sgordonso we will need to find reviewrs to sponsor14:37
baolithose are the two BPs on the nova side14:37
sgordonack14:38
*** amrith has joined #openstack-meeting-alt14:40
*** itzikb has quit IRC14:41
*** lisaclark1 has joined #openstack-meeting-alt14:42
*** balajiiyer has joined #openstack-meeting-alt14:44
*** balajiiyer has left #openstack-meeting-alt14:45
*** sarob has quit IRC14:46
*** ruhe is now known as ruhe_14:46
*** jecarey has joined #openstack-meeting-alt14:47
BrianB_sgordon, we need the nova pci in icehouse, how do we get sponsor, do they need to be nova core?14:49
*** ruhe_ is now known as ruhe14:49
*** ccrouch has left #openstack-meeting-alt14:49
*** aignatov is now known as aignatov_14:49
*** mestery has joined #openstack-meeting-alt14:52
*** mestery has quit IRC14:53
*** aignatov_ is now known as aignatov14:53
*** ruhe is now known as ruhe_14:53
*** ruhe_ is now known as ruhe14:53
*** mestery has joined #openstack-meeting-alt14:53
*** jprovazn has joined #openstack-meeting-alt14:54
*** carl_baldwin has joined #openstack-meeting-alt14:55
*** carl_baldwin has quit IRC14:56
*** amytron has joined #openstack-meeting-alt14:57
*** Barker has joined #openstack-meeting-alt15:00
*** carl_baldwin has joined #openstack-meeting-alt15:00
*** NikitaKonovalov is now known as NikitaKonovalov_15:01
*** ruhe is now known as ruhe_15:01
*** Swami has joined #openstack-meeting-alt15:01
Swamihi15:02
carl_baldwinHi15:02
Swamicarl: hi15:02
Swamisafchain: ping15:02
safchainSwami, hi15:03
Swamisafchain:hi15:03
Swamijamie: ping15:03
Swamirobin wong: ping15:03
Swami#startmeeting distributed_virtual_router15:04
openstackMeeting started Wed Feb  5 15:04:02 2014 UTC and is due to finish in 60 minutes.  The chair is Swami. Information about MeetBot at http://wiki.debian.org/MeetBot.15:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:04
*** openstack changes topic to " (Meeting topic: distributed_virtual_router)"15:04
openstackThe meeting name has been set to 'distributed_virtual_router'15:04
Swami#topic F2F Meeting15:04
*** rsblendido has joined #openstack-meeting-alt15:04
*** rossella_s has joined #openstack-meeting-alt15:04
*** openstack changes topic to "F2F Meeting (Meeting topic: distributed_virtual_router)"15:04
*** ruhe_ is now known as ruhe15:05
carl_baldwinI'll need to join the f2f virtually.15:05
Swamihi folks, as I have mentioned in my previous meeting I am planning to have a face to face meeting on Feb 13th at Palo Alto to get the community feedback on the DVR proposal. The meeting will be from 11.a.m to 1.00p.m15:05
safchainI hope I will be able too15:06
SwamiCarl: Yes I will send out a virtual invite to everyone today.15:06
SwamiI will also send out a conf. bridge for people to dial in.15:06
Swamisafchain: Have anything changed on your end for the DVR proposal, have you updated your document or else should I proceed with what you have in the document.15:07
*** ruhe is now known as ruhe_15:07
safchainSwami, I'm currently doing it, I'll finish to update it by this end of the day15:07
safchainso I will send you an email15:08
Swamisafchain: thanks15:08
*** shivh has joined #openstack-meeting-alt15:08
SwamiI will also update my document with some minor changes.15:08
* carl_baldwin will now switch to my other client15:09
Swamisafchain: As I have mentioned earlier I would like both of our blueprints to be merged to a single blueprint with support for both North-South and East-West without affecting any of the existing services.15:09
*** carl_baldwin has quit IRC15:09
*** jergerber has joined #openstack-meeting-alt15:09
*** ruhe_ is now known as ruhe15:09
safchainSwami, sounds good15:10
*** carl_baldwin has joined #openstack-meeting-alt15:10
Swamisafchain: Currently we are also trying to move the SNAT functionality to a specific node, that can be a Network Node.15:10
Swamibut retain the floating ip and other routing functionality with the compute node.15:10
*** mestery has quit IRC15:10
safchainSwami, great so the two proposals go to same way15:11
carl_baldwinsafchain: Swami: are you speaking of updating the HA routers document?15:11
*** rossella_s has quit IRC15:11
safchainyes I pointed the blueprint15:11
SwamiSorry for not updating the document, I will update it in a couple of days. By thursday I should have updated the document.15:11
SwamiOnce I update I will send a message to everyone.15:11
Swamicarl: Not the HA routers doc, but the DVR doc.15:11
safchaincarl_baldwin, Will be used for north-south when VM will not have floating ip15:12
*** gokrokve has joined #openstack-meeting-alt15:12
*** jergerber has quit IRC15:12
carl_baldwinOkay.  Sorry, trying to catch up.15:12
safchaincarl_baldwin, I will send you the email with the document updated15:13
Swamicarl: no worries, since the doc is changing constantly15:13
carl_baldwinsafchain: great15:13
safchainto everyone15:13
*** nacim_ has joined #openstack-meeting-alt15:13
*** jmontemayor has joined #openstack-meeting-alt15:14
SwamiSo i think that's all I want to say about the F2F meeting.15:14
*** jmontemayor has quit IRC15:14
Swamicarl_baldwin: Do you have any update on the L3_agent consolidation, what is the status and who is working on it.15:14
*** nacim has quit IRC15:14
Swamitopic# L3 cosolidation15:14
*** jmontemayor has joined #openstack-meeting-alt15:14
carl_baldwinI haven't seen much about it lately.  Let me take a look.15:15
Swami#topic l3 consolidation15:15
*** openstack changes topic to "l3 consolidation (Meeting topic: distributed_virtual_router)"15:15
carl_baldwinIsaku was working on it.15:15
Swamicarl: do you tink it is targeted for Icehouse15:16
carl_baldwinLooks like the patch has not seen an update since early december.15:16
carl_baldwinI will ping Isaku on it.15:17
Swamicarl: Thanks15:17
*** kevinconway has joined #openstack-meeting-alt15:18
Swamitopic; L3 service framework15:18
*** dprince has quit IRC15:18
*** jmontemayor has quit IRC15:18
Swami#topic L3 service framework15:18
*** openstack changes topic to "L3 service framework (Meeting topic: distributed_virtual_router)"15:18
Swamicarl: Is there any L3 drivers today that drives a hardware router.15:19
*** dprince has joined #openstack-meeting-alt15:19
carl_baldwinI'm not sure what they are.15:20
*** amotoki has joined #openstack-meeting-alt15:20
yamahatacarl_baldwin, yes?15:21
Swamicarl: The reason I am asking is, there are service framework for other services such as LBaaS and there are vendor drivers to drive a physical or virtual device.15:21
Swamisimilarly is there any driver for L3 to drive the hardware15:21
*** esker has quit IRC15:21
Swamiyamahata: hi15:22
*** esker has joined #openstack-meeting-alt15:22
*** esker has quit IRC15:23
SwamiDoes anyone know how we should handle the DVR situation when there is a L3 hardware router or VM based router appliance that does the L3 service15:23
*** esker has joined #openstack-meeting-alt15:23
*** IlyaE has joined #openstack-meeting-alt15:24
*** rossella_s has joined #openstack-meeting-alt15:24
carl_baldwinSwami: If there is a hardware router doing L3, I think that DVR would not be possible.  Or, not easy.15:25
*** esker has quit IRC15:27
*** ruhe is now known as ruhe_15:27
*** aignatov is now known as aignatov_15:28
*** tedross has left #openstack-meeting-alt15:28
carl_baldwinIf I recall, Mark's former company used a VM to do L3.  It might be a good question to ask him.15:28
*** coolsvap has joined #openstack-meeting-alt15:29
*** amuller has joined #openstack-meeting-alt15:29
*** Swami has quit IRC15:29
*** AlanClark has joined #openstack-meeting-alt15:30
*** Swami has joined #openstack-meeting-alt15:31
SwamiSorry folks i got dropped15:31
Swamidid I miss anything15:31
safchainSwami, no15:31
carl_baldwinAre we still having problems with free node like the other day?  I don't think you miss anything.  The meeting went idle when you dropped.15:31
SwamiYes sometimes it drops our session15:31
*** ruhe_ has quit IRC15:32
Swamicarl:yes same symptom15:32
*** boris-42_ has joined #openstack-meeting-alt15:32
Swamisafchain: How is your L3 HA going?15:32
safchainI almost sent all the patches related to this feature15:32
*** BrianB_ has quit IRC15:33
safchainamuller, is working on the conntrackd patch15:33
Swamisafchain:Ok thanks15:33
Swamisafchain: With respect to the L3 HA, all the services that are owned or tied to the L3 agent will it be saved.15:34
safchainSwami, like metadata ?15:34
Swamitoday FWaaS is tied to L3 agent15:34
*** rkukura has quit IRC15:34
Swamisafchain: Yes also metadata.15:35
*** rkukura has joined #openstack-meeting-alt15:35
safchainSwami, I have to check for the FWAAS, but if the policies/rules are inserted to each l3, I think it is ok15:35
safchainSwami, for the metadata it is ok15:36
Swamisafchain:Thanks15:36
carl_baldwinsafchain: Are all of the patches on the bp/l3-high-availability topic?15:37
safchaincarl_baldwin, yes15:38
safchainbp/l3-high-availability-api15:38
safchainbp/l3-high-availability-keepalived15:38
safchainbp/l3-high-availability-scheduler15:38
*** trinaths has joined #openstack-meeting-alt15:38
*** richm has joined #openstack-meeting-alt15:38
Swami#topic General discussion15:39
*** openstack changes topic to "General discussion (Meeting topic: distributed_virtual_router)"15:39
carl_baldwinsafchain: I see, so there are a few topics.15:39
safchaincarl_baldwin, yes15:39
carl_baldwin... but they are all named similarly.15:39
safchaincarl_baldwin, yes same prefix15:39
trinathshi, any topic for discussion on 3rd party test setup..15:41
SwamiFolks I do have a hard stop at 7.45PST, if you don't have any other items I would like to summarize the action items and will end the session15:41
carl_baldwinSorry I missed the meeting last week, had a conflict.  There was talk about combining presentations or something.  I didn't know what was being combined from the context in the meeting.15:41
trinathswanted to know the requirements and procedure and working of a 3rd party setup15:41
Swami#action safchain: Will update the document15:41
Swami#action Swami: will update the document and will try to get it into a single doc for the F2F review.15:42
carl_baldwinWhich blueprints were to be combined?15:42
SwamiCarl: Right now we have two different blueprints for DVR, one from safchain and one from me.15:43
Swamicarl: So it would be great if we could come up with a single blueprint to combine the best of both worlds.15:44
amullerSwami: There's also https://blueprints.launchpad.net/neutron/+spec/ovs-distributed-router15:44
carl_baldwinWhat is the link to safchain 's blueprint?15:44
Swamiamuller: Yes Robin wong is already part of our subteam and we are taking into the consideration the East-West.15:44
*** markwash has quit IRC15:45
amullerAnd there will also be a new idea by me soon. I'll make a draft for the next meeting, hopefully we'll be able to discuss/consider it15:45
safchaincarl_baldwin, no blueprint just a gdoc for now15:45
amullerBasically VRRP A/A, which depends on Sylvain's blueprint15:45
carl_baldwinsafchain: Thanks, I did see the gdoc.15:45
carl_baldwinThat clears that up for me.  Thanks.15:46
Swamiamuller: It would be great if you have any idea pitch it to us as early as possible, because it would be usefull to discuss in the F2F15:46
amullerok15:46
safchaincarl_baldwin, I will update it by the end of the day15:46
*** RajeshMohan has quit IRC15:46
carl_baldwinsafchain: great15:46
Swamiamuller: The current sub-team that we are working in is based on the Icehouse summit proposals that was done for East-West and North-South, feel free to join the meeting and communicate with the sub team and we can converge.15:47
carl_baldwinSwami: I know you have a hard stop.  That is all from me for now.  Thanks.15:47
SwamiFolks I need to stop.15:47
SwamiThanks for all your input and participation15:47
SwamiHave a nice day.15:47
SwamiSee you all next week.15:48
Swami#endmeeting15:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:48
*** RajeshMohan has joined #openstack-meeting-alt15:48
openstackMeeting ended Wed Feb  5 15:48:08 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-02-05-15.04.html15:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-02-05-15.04.txt15:48
openstackLog:            http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-02-05-15.04.log.html15:48
safchainSwami, thx for the meeting15:48
safchainbye all15:48
amullerbuhbye15:48
carl_baldwinbye15:48
*** Swami has quit IRC15:48
*** chadlung has joined #openstack-meeting-alt15:49
*** dhellmann is now known as dhellmann_15:52
*** haleyb has quit IRC15:52
*** DinaBelova is now known as DinaBelova_15:53
*** nickchase has quit IRC15:53
trinaths     hi, any topic for discussion on 3rd party test setup..     wanted to know the requirements and procedure and working of a 3rd party setup, any topic for discussion on 3rd party test setup.. any views on how to setup a 3rd party test setup15:53
*** vkmc has quit IRC15:54
*** igor__ has quit IRC15:57
*** sarob has joined #openstack-meeting-alt15:57
*** trinath has joined #openstack-meeting-alt15:57
*** trinaths has quit IRC15:57
*** trinath has quit IRC15:58
*** rcurran has joined #openstack-meeting-alt15:58
*** shivh has left #openstack-meeting-alt15:59
*** pcm_ has joined #openstack-meeting-alt15:59
*** jasonb365 has joined #openstack-meeting-alt15:59
*** shivharis has joined #openstack-meeting-alt15:59
*** trinaths has joined #openstack-meeting-alt16:00
*** lukego has joined #openstack-meeting-alt16:01
*** sarob has quit IRC16:01
asadoughihi16:01
rkukurahi ML2'ers!16:01
lukegoHowdy16:01
*** NikitaKonovalov_ is now known as NikitaKonovalov16:01
trinathsHi16:01
shivharisHi ML216:02
matrohonhi16:02
trinathsHi rkukura16:02
HenryGo/16:02
rcurranhello all16:02
amotokihi16:02
*** sadasu has joined #openstack-meeting-alt16:02
*** banix has joined #openstack-meeting-alt16:02
rkukuramestery is presenting at a conference, so will miss today's meeting and I'll chair16:02
banixHi16:03
trinathsokay..16:03
rkukura#startmeeting networking_ml216:03
openstackMeeting started Wed Feb  5 16:03:32 2014 UTC and is due to finish in 60 minutes.  The chair is rkukura. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
*** openstack changes topic to " (Meeting topic: networking_ml2)"16:03
openstackThe meeting name has been set to 'networking_ml2'16:03
* pcm_ lurking16:03
rkukura#link https://wiki.openstack.org/wiki/Meetings/ML2 Agenda16:03
*** igor_ has joined #openstack-meeting-alt16:03
rkukura#topic Announcements16:04
*** openstack changes topic to "Announcements (Meeting topic: networking_ml2)"16:04
trinathshi rkukura, please add a topic for 3rd part testing too..16:05
rkukuraLooks like neutron patches are merging again finally - anyone know more details on whether the general merges are now being approved?16:05
rkukuratrinaths: OK16:05
lukego(I'd like to briefly review status of the Tail-f md if that's possible. I'm not sure if I should have added that on the agenda already?)16:05
trinathsthank you rkukura16:05
rkukuralukego: OK, I think that would be under the Blueprints topic16:06
lukegoThanks16:06
*** tanisdl has joined #openstack-meeting-alt16:06
rkukuraFeature proposal deadline is February 18th16:06
rkukuraAll BP implementations for icehouse must be in review by then16:06
rkukuraUnder the Blueprint topic, we can discuss prioritization, etc of the huge list16:07
rkukura#topic Action Item Review16:07
*** openstack changes topic to "Action Item Review (Meeting topic: networking_ml2)"16:07
*** BrianB_ has joined #openstack-meeting-alt16:08
rkukuraThe only formal action item was mine, which I've finally completed!16:08
*** igor_ has quit IRC16:08
rkukuraLooks like good discussion on the proposed port binding changes is under way on openstack-dev, so we don't need to spend too much time on it here16:09
rkukuraAre there any quick questions or issues regarding that action item?16:09
trinathsi'm currently doing the improvement to the code base of fsl-sdn-os-mech-driver. this weekend will push to the git..16:09
matrohonrkukura : did you already start coding your proposal?16:10
rkukuratrinaths and everyone else implemening mechanism drivers, please take a careful look at the planned binding changes!16:10
rkukuramatrohon: About to start16:10
matrohonrkukura : great!16:10
rkukuraAnything else on action items?16:11
amotokiregarding havana db migration fix on ML2, there is a post on dev ML, but there seems to be no good solution so far.16:11
shivharisthanks for the summary email. will have to read it at least 2 more times.16:11
trinathsfor pushing the code to upstream, 'mark and kyle' said to go for 3rd party test setup.. I was struck there..16:11
rkukura#action rkukura to put result of binding changes email discussion into a wiki or google doc16:13
*** Sukhdev has joined #openstack-meeting-alt16:13
*** haleyb has joined #openstack-meeting-alt16:13
*** irenab has joined #openstack-meeting-alt16:13
rkukuraamotoki: That is the backport issue - lets talk about that under the bugs topic16:13
amotokirkukura: ok.16:14
rkukura#topic Blueprints16:14
*** openstack changes topic to "Blueprints (Meeting topic: networking_ml2)"16:14
*** dhellmann_ is now known as dhellmann16:15
rkukuraSince many of the BPs are for new drivers, lets start with trinaths's 3rd party testing question16:15
trinathsthank you rkukura...16:15
trinathsWas att the basic to 3rd party testing..16:15
rkukuratrinaths: Can you summarize?16:15
trinathshow do to setup the 3rd party testing16:16
trinathswhat r the requirements16:16
trinathsthese are the doubts I have..16:16
banixhttp://ci.openstack.org/third_party.html16:16
Sukhdevtrinaths: it has been discussed a lot on the ML16:17
HenryGtrinaths: search the ML archives16:17
trinathsokay..16:17
*** NikitaKonovalov is now known as NikitaKonovalov_16:18
trinathshow to get the service account..16:18
*** jmontemayor has joined #openstack-meeting-alt16:18
HenryGtrinaths: also, here is a good read to understand the underlying system: #link http://www.joinfu.com/2014/01/understanding-the-openstack-ci-system/16:18
shivharistrinaths: also there is an etherpad for it (i will add the link to it on the wiki)16:18
*** mestery has joined #openstack-meeting-alt16:18
irenabhere is a link #https://etherpad.openstack.org/p/multi-node-neutron-tempest16:18
trinathsokay.. let me understand the same .. this takes some time.. :)16:18
banixtrinaths: how to get an account: at http://ci.openstack.org/third_party.html16:18
amotokitrinaths: about service account, please send a mail to openstack-infra with information described in http://ci.openstack.org/third_party.html16:19
Sukhdevtrinaths: I am trying to put together wiki on third partry testing - have not had much time to finish it - will publish next week16:19
amotokiSukhdev: could you share a link? I can contribute.16:19
rkukuratrinaths: Will this get you started?16:20
Sukhdevamotoki: will do - as soon as I am done16:20
trinathsbanix the email is a list email16:20
banixJay Pipes has a wiki as well: http://www.joinfu.com16:20
trinathsis there any specific email to get the service account16:20
trinathsyes rkukura... this give a lot of info..16:21
trinathswell i will start tomorrow..16:21
rkukuraThanks everyione for the links! I'd like to look at these too.16:21
banixtrinaths: yes send an email with the info requested to that list16:21
*** jcooley_ has joined #openstack-meeting-alt16:21
amotokitrinaths: we have many malis on servcie account at http://lists.openstack.org/pipermail/openstack-infra/2014-February/thread.html16:21
trinathsI have already sent, anix.. they send me the URL for thirdparty.html16:21
amotokilet's share our knowledge on Wiki page. etherpad is hard to search.16:22
trinathsokay.. thank you.. amotoki.. for the link.. will look into the pages..16:22
trinathstrue said amotoki..16:22
shivharisamotoki: +116:22
rkukuraMoving on to BPs in general...16:22
trinathsthanks for topic rkukura...16:23
trinathsit helped me a lot..16:23
rkukuraThere are 31 ML2 BPs returned by https://blueprints.launchpad.net/neutron?searchtext=ml216:23
rkukuraI'd like to clean this up a bit, and make sure priorities and series are correct.16:24
rkukuraSeems only fair to me that all 3rd party MD BPs should be at the same priority, probably either medium. Does that make sense?16:24
matrohon+116:25
irenabagree16:25
trinaths1  [from my side, 'fsl-sdn-os-mech-driver' BP, with LOW priority, completed the code and waiting for 3rd party test setup... ]16:25
trinaths116:25
Sukhdev+116:25
sadasu+1 about 3rd party MD BP priority16:26
amotokiAgree with the same priority.16:26
*** DinaBelova_ is now known as DinaBelova16:26
shivharis+116:26
amotokiAll have "low" is another idea. too many medium BPs make it diffictult to track.16:26
rkukuraSee we need to get the ones that we think can make icehouse approved.16:26
*** amuller has quit IRC16:26
rkukuraI'm fine with either medium or low for these, but don't want them to fall below the radar for reviewers.16:27
*** esker has joined #openstack-meeting-alt16:27
SukhdevI like amotoki's idea - start with low priority for all and as they meet the third part requirement- bump up the priority to medium16:27
trinathssukhdev +116:28
*** jcooley_ has quit IRC16:28
irenaband whicj already has 3rd party testing, start with medium16:28
irenab^which16:29
rkukuraSukhdev: +116:29
matrohon+116:29
HenryGsounds good16:29
shivharisrkukura: there is a chicken egg prblem in that16:30
rkukurashivharis: I was trying to articulate the same thing16:30
shivharisif the code is not in the master, you cannot run third party anywasys16:30
shivharissukhdev: -116:30
rkukuraIs setting up the jenkins job before the code is merged possible?16:30
Sukhdevshivharis: why not?16:31
*** PeterSchwaller has joined #openstack-meeting-alt16:31
banixrkukura: yes16:31
shivharisyou need to pull in the branch of a new checkin which should already have your ml2 code in it16:31
shivharishence u cannot test, ifyour ml2 is not in the master to begin with16:31
Sukhdevwhen you run third party testing, you are applying patches anyways why can you apply your own patch before kicking the testing?16:31
banixno you can bring in a patch set under review16:31
amotokiwe can run tests for proposed commits, so third party testing works.16:32
banixno need for it to be merged before testing16:32
HenryGIn fact, that is how your 3rd party testing should be set up16:32
*** PeterS has quit IRC16:32
rkukuraSo the tests would not actually test the new MD until it gets merged, right?16:32
shivharisrkukura: correct16:33
banixand the merge should happen after third part tests pass16:33
banixrkukura: not really16:33
*** sacharya has joined #openstack-meeting-alt16:33
banixthe test should test the new MD16:33
rkukuraBut should the jenkins job test the patch set(s) proposed to implement the new MD?16:33
*** jcooley_ has joined #openstack-meeting-alt16:33
banixrkukura: yes16:34
HenryGexactly16:34
Sukhdevrkukura: not really - that is not true16:34
rkukuraSeems the job would need to run the test only iff the branch contains the MD16:34
trinathssukhdev: jenkins surely tests the code.16:34
banixyou setup your test so it can get triggered as you submit a patch to your new MD or plugin16:35
HenryG^^^ what banix says16:35
HenryGplus, you should trigger on all core code patches too16:35
amotokiwe setup third party testing for proposed patches. but it really helps us to debug our own plugins/drivers against the master branch.16:36
Sukhdevbanix, HenryG: correct16:36
*** eankutse1 has joined #openstack-meeting-alt16:36
*** gokrokve has quit IRC16:36
*** eankutse1 has quit IRC16:36
*** vkmc has joined #openstack-meeting-alt16:37
Sukhdevamotoki: +116:37
*** gokrokve has joined #openstack-meeting-alt16:37
shivharisrkukura: your call16:37
SukhdevSo, I do not see chicken and egg problem :-)16:37
rkukuraSo are we agreeing that BPs for new MDs should be low priority until they have the jenkins job in place that will test the patch sets submitted to implement the MD, then they should get bumped to medium?16:37
*** eankutse has quit IRC16:38
Sukhdevrkukura: +116:38
amotoki+116:38
banixsounds reasonable16:38
rkukuraAny objections?16:39
rcurran+116:39
trinaths+116:39
shivharisSo we only test the patchset that has the MD. not CI.16:39
banixand all submissions by Jenkins16:39
lukegoWe are struggling with the 3rd party testing, don't know if now is the time to broach that topic...16:39
jaypipeshi all, sorry I missed above...16:39
banixthat is the stated requirement; not sure if it is being enforced16:39
matrohonwhat about opensource MD (l2-pop, ovs, lb). like 3rd party, They need multi-node setup which is not available in openstack-infra by now16:40
banixjaypipes: I referred to your blog wrt testing16:40
jaypipeswas wondering what the percentage of you all that are using Jenkins Gerrit plugin as your triggering agent vs. Zuul is. Can I get a show of hands of how many use the Jenkins Gerrit plugin please?16:40
*** mestery has quit IRC16:40
*** bauzas has quit IRC16:40
banixGerrit Plugin for us16:40
irenabalso for us16:41
rkukura#action: rkukura to change priorities of all new 3rd party MD BPs to low if they do not already have jenkins job in place.16:41
HenryGgerrit, not zuul16:41
jaypipestrinaths, Sukhdev? Gerrit Jenkins plugin?16:41
*** gokrokve has quit IRC16:41
Sukhdevjaypipes: I am using jenkins with Gerrit Plugin - you saw my setup in Montreal :-)16:41
amotokiat now i am using Gerrit plugin and now testing zuul. It seems easy to migrate from gerrit plugin to zuul.16:41
jaypipesSukhdev: k, I thought so... just wanted to check you had not changed :)16:41
shivharisjaypipes: wrote our own from scratch16:42
jaypipesamotoki: k, thx.16:42
jaypipesshivharis: yikes :)16:42
trinathsjaypipes: me need to start the setup..16:42
shivharisjaypipes: very flexible16:42
jaypipesshivharis: did you use Zuul as a model?16:42
Sukhdevjaypipes: using our own setup gives us flexibility of being light weight :-):-)16:43
shivharisno, pure python code16:43
jaypipesshivharis: so, like Zuul then :)16:43
shivharisyup.16:43
rkukuramatrohon: Good point about multi-node testing of the non-3rd-party drivers.16:43
jaypipeskk, thx all. I should have the puppet modules in http://github.com/jaypipes/os-ext-testing setting up Zuul sometime today (replacing the use of the Gerrit Jenkins plugin)16:44
*** Leonr has joined #openstack-meeting-alt16:44
jaypipessorry for interrupting, rkukura16:44
*** jasonb365 has quit IRC16:44
rkukuraLets put multi-node testing of the non-3rd-party drivers on the agenda for next week16:45
matrohonrkukura : ok16:45
rkukuraproposals/ideas/implementations are welcome16:45
matrohonrkukura : we are working on it16:45
*** jasonb365 has joined #openstack-meeting-alt16:46
Sukhdevjaypipes: The real issue I am faced with (I am sure others are hitting or will hit) is the kind of tests to run and what services to enable - as opposed to the framework itself16:46
rkukuraSo we have many BPs that are not introducing new MDs16:46
matrohonwith multi-node setup with lxc16:46
*** nacim_ has quit IRC16:46
rkukurawondering if there is a need for separate neutron 3rd party testing meeting(s)?16:47
*** jcoufal has quit IRC16:47
lukegoI'd like a neutron 3rdty party testing therapy session :)16:47
banixrkukura: there have been already a couple of such meetings16:47
rkukurabanix: Right, wondering if more are needed?16:47
jaypipesrkukura: actually, I think there's a need for a cross-project 3rd party testing meeting...16:47
amotokiAFAIK it is not scheduled now, but many folks are more interested in it than a month ago.16:47
Sukhdevrkukura: it may be a good idea - but, agenda should not focus on CI - but, on what to test, what servvices should be enabled when running devstack16:47
trinathsjaypipes: can you share your wiki link about the procedure to setup and 3rd party test setup16:48
jaypipesrkukura: since many vendors in cinder, nova, and neutron are struggling with setups.16:48
jaypipestrinaths: I will share it when I'm done (hopefully today!)16:48
banixI think we need a clear detailed wiki describing how to do this16:48
amotokijaypipes: great16:49
rkukuraMaybe two different discussions, general 3rd party testing vs. neutron-specific, such as which tempest tests16:49
lukego3rd party testing doesn't bring us much benefit, because our driver is so simple and we're happy with the unit tests, but it has got us into a fight with #openstack-infra, and we feel the threat of "deprecation". #sadface16:49
*** vinod has joined #openstack-meeting-alt16:49
banixjaypipes has a good post about using zuul and I think he is going to have another with Gerrit plugin16:49
trinathsjaypipes: okay16:49
*** PeterSchwaller has quit IRC16:49
trinathsbanix +116:49
rkukuralukego: You might appreciate it more when my merge breaks your driver;-)16:49
shivharisrkukura: thanks for that!16:50
matrohoni'd like to see this BP at a higer level :16:50
matrohonhttps://blueprints.launchpad.net/neutron/+spec/ml2-typedriver-extra-port-info16:50
Sukhdevrkukura: yes, we need to understand what to test from Neutron point of view - I spoke with Mark when in Montreal - he wants full gate testing, which requires many services to be enabled16:50
lukegorkukura: breaks integration tests without breaking unit tests?16:50
rkukurasorry, snow plow was stuck in our driveway16:50
banixBeautiful Northeast. Digging out in NYC as well :)16:51
lukegorkukura: all the OpenStack ever sees from our 3rd party system is "200 OK".. the logic is so basic that nothing more is needed16:51
Sukhdevrkukura: Can I bring up an issue that I am seeing with devstack while doing 3rd party testing with ML2 Plugin?16:53
rkukuramatrohon: That's the one that lets type drivers put info the get_device_details response. Seems mechanism drivers need to do this as well. How about kicking off an email discussion on this?16:53
rkukuraSukhdev: sure16:53
*** PeterS has joined #openstack-meeting-alt16:53
amotokiApart from third party testing, another concern towards  I-3 is how to coordinate changes in ML2 main code (such as binding issues) and MD patches. The change in main code requires to rebase and refactor all MD patches.16:54
Sukhdevwhen we run devstack, neutron invokes neutron-debug probe-create (which makes create_port_pre/post call) The port context/port structure fields are not set correctly, and causes the ML2 drivers to fail16:55
rkukuraWe've got 5 minutes left.16:55
matrohonrkukura : this is not this one, but asomya told us that he was waiting for this BP to merge besore proposing its patch to allow MD to add info in get_device_details16:55
rkukuraSukhdev: Is there a bug for that?16:55
Sukhdevrkukura: do not know16:56
*** gyee has joined #openstack-meeting-alt16:56
shivharissukhdev: file a bug16:56
rkukuramatrohon my question is whether MD should control the RPC response, and get the info fro the TD if needed16:57
rkukuraI'll try to ping owners of all the BPs in the next couple days and get priorities and approvals sorted out.16:57
rkukuraNext week we can check status based on priority and make sure we are on track for feature proposal freeze16:58
trinathsokay16:58
matrohonrkukura : ok, that could be a way of implementing this!16:58
Sukhdevrkukura: sounds good16:59
*** nati_ueno has joined #openstack-meeting-alt16:59
*** RajeshMohan has quit IRC16:59
HenryGmatrohon: can you keep me and asomya in the loop on that?17:00
rkukuraWe didn't cover bugs today, but the VIF security issue needs resolution. See http://lists.openstack.org/pipermail/openstack-dev/2014-January/026060.html17:00
rkukura#topic open discussion17:00
*** openstack changes topic to "open discussion (Meeting topic: networking_ml2)"17:00
asadoughiovs-firewall-driver update: should be pushing out code for a firewall driver review before the next meeting, making minor adjustments to existing assign vlans review as well to accomodate that17:00
*** RajeshMohan has joined #openstack-meeting-alt17:00
rkukuraasadoughi: Great! Thanks for the update!17:01
rkukuraanything else?17:01
rkukura#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
openstackMeeting ended Wed Feb  5 17:01:29 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-02-05-16.03.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-02-05-16.03.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-02-05-16.03.log.html17:01
*** rcurran has quit IRC17:01
*** jmcbride has joined #openstack-meeting-alt17:02
vinod#startmeeting designate17:03
openstackMeeting started Wed Feb  5 17:03:03 2014 UTC and is due to finish in 60 minutes.  The chair is vinod. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: designate)"17:03
openstackThe meeting name has been set to 'designate'17:03
vinodWho's here today?17:03
richmRich17:03
*** lukego has quit IRC17:03
*** trinaths has quit IRC17:03
vinodJoe and Betsy will be joining the meeting shortly17:03
jmcbrideI'm here17:03
vinod#topic Review action items from last week17:04
*** openstack changes topic to "Review action items from last week (Meeting topic: designate)"17:04
*** igor_ has joined #openstack-meeting-alt17:04
*** betsy has joined #openstack-meeting-alt17:04
vinodkiall had an action item to write a mini-dns spec ahead of the summit17:05
*** rudrarugge has joined #openstack-meeting-alt17:05
vinodI would consider that done17:05
*** gokrokve has joined #openstack-meeting-alt17:05
*** eankutse has joined #openstack-meeting-alt17:05
jmcbridereally? do you have a link to the spec?17:05
betsyhere17:05
eankutseeankutse17:05
vinodThe action item here was creating the spec just for the summit17:06
vinodand not a detailed mini-dns spec17:06
*** irenab has quit IRC17:06
jmcbrideI see, so you are referring to the doc he prepared for last week's workshop.17:06
vinod#link https://wiki.openstack.org/wiki/Designate/Blueprints/MiniDNS17:07
*** gokrokve_ has joined #openstack-meeting-alt17:07
vinodMoving onto the next topic17:07
vinod#topic Recap on Designate Mini-Summit in Austin17:07
*** openstack changes topic to "Recap on Designate Mini-Summit in Austin (Meeting topic: designate)"17:07
*** stannie has quit IRC17:08
jmcbrideIf memory serves me right, vinod and richm were going to get something together for the dev list.17:08
vinodAnybody have things to share from the summit17:08
*** bdpayne has joined #openstack-meeting-alt17:08
vinodI think Rich posted some notes internally in RedHat17:09
richmI sent email to openstack-dev with summit summary17:09
richmand sent to our internal rhos list17:09
*** igor_ has quit IRC17:09
jmcbridecool (I missed it)17:09
richmI put [designate] in the Subject17:09
richmThat seems to be the convention17:09
*** gokrokve has quit IRC17:10
betsyYes. I saw it last week. Thanks richm17:10
*** gokrokve has joined #openstack-meeting-alt17:10
*** msisk_ has joined #openstack-meeting-alt17:10
jmcbride#link http://lists.openstack.org/pipermail/openstack-dev/2014-January/026023.html17:10
vinodThanks Joe for the link - I was trying to search for it17:11
jmcbridemy google foo is high today ;)17:11
vinodAnybody have anything else to add17:12
*** amotoki is now known as amotoki_17:12
*** artom has joined #openstack-meeting-alt17:12
vinod#topic Action items from the summit17:12
*** openstack changes topic to "Action items from the summit (Meeting topic: designate)"17:12
vinodTim had one action item - What is current average commit size?17:12
*** amrith has quit IRC17:13
*** gokrokve_ has quit IRC17:13
vinodHe Wrote a script that sort of works (counts merge commits twice)17:13
*** amrith has joined #openstack-meeting-alt17:13
vinodIf memory serves right, based on that the average commit size has ~ 194 adds and ~134 deletes17:13
vinodTim is not around now to verify17:14
vinodBut the average commit size for the last year for use seems to be ~ 350 lines17:14
vinod#link  https://github.com/Squab/commit-stats17:14
vinodBy comparision Solum seemed to average ~ 100 lines per commit17:15
jmcbrideSeems like we need to ratify the original intent of that action item: agree to limit commit sizes to less than 350 lines.17:15
*** julim has quit IRC17:15
*** jasonb365 has quit IRC17:15
jmcbridebut without kiall and mugsie, I don't think we can establish that just yet.17:16
betsyDo we actually need a hard upper limit?17:16
betsyOr a goal to shoot for?17:16
richmI think that seems reasonable for now - once we start having a few other committers and reviewers, we can adjust17:16
jmcbrideI'd call it a guideline or goal17:16
betsyOkay17:16
richmyeah, I don't think we want to have gerrit outright reject large patches17:17
vinodI would vote for it to be a guideline rather than a hard upper limit17:17
*** haleyb has quit IRC17:17
betsyvinod: agree17:17
eankutseguideline is good17:17
richmThe reviewer can say "hey, can you split this commit?"17:17
vinodWe could add it to the documentation in the Getting Involved section17:17
eankutsethat's what solum does too17:17
jmcbrideOn second thought, I think kiall and mugsie were cool with 350.17:17
betsyIn that note, we probably need to make the blueprints smaller -- maybe subdivide them17:17
jmcbridevinod: that sounds like an action item to me!17:18
betsyjmcbride: that's my memory, too17:18
jmcbridebetsy: good point17:18
jmcbrideI think the action is: notify designate devs via the email list about this proposed change.  Then update the documentation.17:19
vinod#action vinod update the Getting Involved Section in the documentation for suggested lines of code / commit17:19
jmcbridevinod: cool, make sure you update the openstack dev list too.17:20
vinodbetsy: regarding splitting the blueprints - yes that would be ideal17:20
*** shivharis has quit IRC17:20
betsyvinod: Might add that to the documentation, too17:20
vinodThe blueprint owners should probably spend some time and split their existing blueprints into smaller ones17:21
betsyvinod: I agree17:21
vinodor rather add new blueprints for smaller work items and track it to the main blueprint17:21
jmcbridevinod: lets address this as we review/start on new blueprints17:21
*** demorris has joined #openstack-meeting-alt17:22
*** jcooley_ has quit IRC17:22
vinod#action (all) review/add new blueprints as needed to track smaller work items17:22
*** jcooley_ has joined #openstack-meeting-alt17:23
vinodThe next action item from the summit was "Atlanta summit abstracts on talks/workshop."17:23
*** lisaclark1 has quit IRC17:23
*** jmontemayor has quit IRC17:23
vinodI updated the abstract for workshop17:24
*** Barker has quit IRC17:24
vinod#link https://wiki.openstack.org/wiki/Designate/Atlanta#Workshop17:24
vinodFeel free to update the wiki page with your comments/suggestions or send them to me and I will update the page17:24
vinodTim wrote an abstract for the talk about new features17:25
vinod#link https://docs.google.com/document/d/1xIprT3xEzujFPWJhVGnIKRdsB7gkmpgTgo0DfG3Ml4s/edit?pli=117:25
*** amotoki_ has quit IRC17:26
*** ijw has quit IRC17:26
vinodI don't have any updates from mugsie and kiall on the abstract for the other 2 talks17:26
*** pcm_ has left #openstack-meeting-alt17:26
*** ijw has joined #openstack-meeting-alt17:27
*** BBG_Stephen has joined #openstack-meeting-alt17:27
*** lisaclark1 has joined #openstack-meeting-alt17:27
vinodNext action item from the summit - "Get feedback from TC on major architectural reworks and Designates chances of incubation."17:27
richmI think they are still on vacation - probably nothing until next week, I'm guessing17:27
vinodrichm: That is right17:27
vinodWe still have time until next Fri to submit the abstracts17:27
*** david-lyle has quit IRC17:28
*** jmontemayor has joined #openstack-meeting-alt17:28
vinodrich I think you mentioned that Designate's chances for incubation are bright.  Do you have any other feedback to share?17:28
richmI emailed Mark McLoughlin - he said designate looks very good for incubation status - the only real problem last time was too few committers17:28
*** Barker has joined #openstack-meeting-alt17:29
richmAlso, about the term "Registered Program" -17:29
richmMark says: "I haven't heard the term "registered program", but programs are essentially OpenStack's sub-projects except we use the term "program" to recognize that sub-projects can consist of multiple repos (even projects like Nova have nova and python-novaclient) and that not all sub-projects are like the "service" projects we typically think of (e.g. infra, docs, oslo, release management).  However, only "service" sub-pro17:29
*** sbalukoff has quit IRC17:30
eankutseWe also agreed that it would be best to finish the miniDNS architecture changes in preparation for incubation17:30
jmcbriderichm: so is a "program" about the service and related tools (e.g. testing, deploy and cli repos)?17:30
richmThat's what it seems to me, yes17:31
jmcbrideOr is a "program" a group of related services (Nuetron, other networking services)?17:31
richmLooks like there could be some judgement by the TC involved with that17:32
vinodbetsy: do you have any more information on the incubation status?17:32
betsyvinod: Haven't gotten a chance to follow up with Anne Gentle yet17:32
betsyWill give feedback next week17:32
*** funzo has joined #openstack-meeting-alt17:33
richmIt seems to me that, if designate is incubated, that would include python-designateclient too17:33
*** 64MAAAAC4 is now known as kpomeroy17:33
*** kpomeroy is now known as kalebpomeroy17:33
*** NehaV1 has joined #openstack-meeting-alt17:33
jmcbriderichm: yep17:33
betsyrichm: I would hope so17:33
jmcbrideRegarding incubation, I would like to know from the TC folks what impact having v2 and mini-dns looming over the project will have on incubation.17:33
* artom always considered the client part of designate...17:33
richmNot sure if there are currently any other "sub-projects" of designate17:33
jmcbriderichm and betsy: can you guys inquire about those items?17:34
*** funzo_ has quit IRC17:34
*** jcooley_ has quit IRC17:34
betsyjmcbride: Will do17:34
*** jcooley_ has joined #openstack-meeting-alt17:34
richmjmcbride: Ok, will ask17:34
vinod#action Betsy and Rich to followup on incubation status wrt v2 and mini-dns17:34
jmcbridethanks17:35
vinodThere were a bunch of other action items from the summit relating to adding/updating blueprints17:35
vinodI did not specifically add them to the agenda17:36
vinodAnybody have anything to share here - I noticed that some of the items are marked as done in etherpad17:36
jmcbrideyes, there was quite a bit there. I finished mine and simply added a bolded "DONE" next to them.17:37
*** SushilKM has joined #openstack-meeting-alt17:37
vinod#topic Open Discussion17:37
*** openstack changes topic to "Open Discussion (Meeting topic: designate)"17:37
vinodAnything on people's mind at this point - here is your chance17:38
*** vgnbkr_1 has joined #openstack-meeting-alt17:38
jmcbriderichm, out of curiosity, what do you think your team will focus on for development?17:38
*** atiwari has joined #openstack-meeting-alt17:39
richmFirst thing will be to do an ipa (bind+ldap) backend17:39
richmI have some concerns about minidns17:39
jmcbrideyep, seems like that could be a bit of a blocker for you getting started.17:39
richmOne is that we have customers that will refuse to allow any other service to "master" the dns data17:40
richmincluding minidns17:40
eankutserichm: regarding your concerns about miniDNS17:40
richmAnother is latency - writing an update over LDAP to bind+ldap is very, very fast17:40
eankutsewould you like to document them under the propoal?17:40
richmeankutse: Yes17:40
eankutse#link https://wiki.openstack.org/wiki/Designate/Blueprints/MiniDNS17:41
richmFrom the perspective of Rackspace and the other folks here, are either of those issues a concern?17:41
eankutseI have a few things that I think will guide implementation17:41
*** jcooley_ has quit IRC17:41
eankutseI should add them to the wiki as well17:41
jmcbriderichm: what use case do those customers have?  Are they tracking their user's desktops or do they track servers in app (for example)?17:41
*** jimbobhickville has joined #openstack-meeting-alt17:41
*** jcooley_ has joined #openstack-meeting-alt17:42
jmcbriderichm: at the moment, no)17:42
jmcbridebut understanding your use case may make us realize it is a problem.17:43
richmWhen a new machine is created in openstack (e.g. nova), you may need to immediately issue ssl certs and/or kerberos keytabs17:43
richme.g. keystone17:43
richmin order to do that, you need a fqdn for the machine17:43
*** yogesh has joined #openstack-meeting-alt17:43
richmif a client wants to connect to that machine, the client will need that fqdn to resolve forward and reverse in DNS17:44
jmcbrideso how does ldap fit into nova?17:44
artomrichm, not necessarily reverse, but go on ;)17:44
richmby reverse, I mean that the client and server may only know the ip address of its peer17:45
*** cp16net has joined #openstack-meeting-alt17:45
richmthe client or server will also have the ssl cert or kerberos credentials from the peer17:46
richmthe cert or credentials will usually have the fqdn of the peer17:46
*** denis_makogon has quit IRC17:46
*** dmakogon_ is now known as denis_makogon17:46
richmfor security, the client or server will want to verify that the ip address resolves to that fqdn17:46
*** denis_makogon_ has joined #openstack-meeting-alt17:46
artomAh!17:47
*** datsun180b has joined #openstack-meeting-alt17:47
richmbasically, ssl and kerberos depend on having fqdn and dns working17:48
jmcbridewhat system issues and manages the certificates?17:49
*** jasonb365 has joined #openstack-meeting-alt17:49
richmkeystone will, at some point17:50
richmnot sure what the current status is17:51
jmcbriderichm: why don't we add an action item for you to document these points so that we can address them at the next IRC (that will give people an opportunity to research a bit too).17:51
*** gokrokve has quit IRC17:51
*** lisaclark1 has quit IRC17:51
richmWe have customers that use Windows Active Directory Domain Controller as their authoritative DNS for their enterprise17:51
*** gokrokve has joined #openstack-meeting-alt17:52
richmThey will _not_ want to migrate their data to minidns17:52
jmcbrideseems to me that minidns is an internal implementation of desigante17:52
artomWon't they *have* to migrate to Designate^17:52
artom?17:52
*** PeterS is now known as PeterSchwaller17:52
richmWhy?17:52
*** markwash has joined #openstack-meeting-alt17:52
artomIf they want to use the REST API to manage their DNS...17:53
*** haleyb has joined #openstack-meeting-alt17:53
richmSo designate _is_ the DNS, not just a _frontend_ to the DNS?17:54
kiallHeya - Just realize the time! Apologies :)17:54
jmcbrideFundamentally, Designate is the REST API + backend DNS + a databased for all zones/records17:54
artomNow, it could be that they would be more comfortable using the current backend model and getting a backend for AD...17:54
eankutse:-)17:54
betsykiall: heya17:54
jmcbridekiall: shouldn't you be on vacation?17:54
artomBut if they use Designate, storage comes with it ;)17:54
kiallWaiting around in the hotel room to head to the airport ;)17:54
richmartom: Yes - that is what some of our customers will want - they will just want to use designate as a restful + mq aware frontend to their DNS17:54
*** SlickNik has joined #openstack-meeting-alt17:55
artomHrmm, yeah, I can see how minidns would not work in that case...17:55
richmand use a backend provided by designate, or provide a backend of their own to tie designate to their master DNS17:55
*** ViswaV has joined #openstack-meeting-alt17:55
*** dhellmann is now known as dhellmann_17:56
artomEssentially by using minidns we're forcing all users to give up any DNS servers that can't operate in slave move.17:56
artom*mode17:56
kiallrichm: (only read half the logs..) I think we'll always have users who want to have something like MS AD as their auth nameservers. I'm skeptical of the value of that other than making the politics easier...17:56
*** gokrokve has quit IRC17:56
richmkiall: It is almost always politics17:56
kiallThe Q is, is that in scope for designate? I'd argue that it's not, but others may have different opinions.\17:57
betsykiall: agree17:57
kiallDesignate has always had a "Designate owns the nameserver, all of it" policy .. MS AD DNS doesn't fit that model17:57
*** aignatov_ is now known as aignatov17:57
richmkiall: I don't understand - was the purpose of designate always to be the authoritative DNS?17:57
richmThen designate will shut out a lot of our customers17:57
*** akuznetsov has quit IRC17:58
kiallrichm: yes, it's intended to be authoritative and the single point of control over the nameservers it manages.. Long term, things like integrating with MS AD are doable with inbound AXFR17:58
*** hub_cap has joined #openstack-meeting-alt17:58
*** grapex has joined #openstack-meeting-alt17:58
*** jcru has joined #openstack-meeting-alt17:58
kiallSo - MS AD controls the various AD specific (sub-)zones, and designate would AXFR those from the AD DNS's into the queryable DNS servers17:58
richmIs this written down somewhere?17:58
*** imsplitbit has joined #openstack-meeting-alt17:58
*** eankutse has quit IRC17:59
kiallrichm: no, and I'm still working on half context here.. Missed a lot of the start of this conversation!17:59
*** arnaud__ has joined #openstack-meeting-alt17:59
*** arnaud has joined #openstack-meeting-alt17:59
*** beyounn has joined #openstack-meeting-alt18:00
vinod#action Rich to document the minidns concerns on the wiki spec18:00
richmTo me, looking at the current state of the designate design, was that designate was basically a rest + mq frontend to whatever backend DNS you wanted to use18:00
vinodWe could talk about this again in the irc and follow up in the next meeting18:00
betsyAs we are out of time18:00
*** derekh has quit IRC18:00
vinodGiven that it is 12:00 and trove will have a meeting here now18:00
richmOk - moving over to #designate18:00
betsyAnother team starts now18:00
*** nadya has joined #openstack-meeting-alt18:00
*** jmcbride has left #openstack-meeting-alt18:00
vinodbye folks18:00
kiallrichm: yes, technically is is.. And it still will be, just the mechanics are changing a bit18:00
kiallAnyway - hub_cap is about to rage if whoever started this meeting doesn't #endmeeting soon :)18:00
vinod#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Wed Feb  5 18:01:03 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-02-05-17.03.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-02-05-17.03.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-02-05-17.03.log.html18:01
SlickNikthanks kiall!18:01
*** nadya is now known as Guest8386318:01
*** glucas has joined #openstack-meeting-alt18:01
*** artom has left #openstack-meeting-alt18:01
*** funzo_ has joined #openstack-meeting-alt18:01
cp16netwoor18:01
SlickNikhello18:01
imsplitbito/18:01
glucasHi18:01
*** msisk_ has left #openstack-meeting-alt18:01
hub_cap#startmeeting trove18:01
*** vinod has left #openstack-meeting-alt18:01
openstackMeeting started Wed Feb  5 18:01:55 2014 UTC and is due to finish in 60 minutes.  The chair is hub_cap. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: trove)"18:01
hub_caphiall18:01
openstackThe meeting name has been set to 'trove'18:01
denis_makogono/18:02
abramleyhi18:02
datsun180boh boy18:02
grapexo/18:02
hub_cap#link https://wiki.openstack.org/wiki/Meetings/TroveMeeting18:02
cp16nethi all18:02
kevinconwayo/18:02
pdmarso/18:02
SlickNikhello18:02
*** funzo has quit IRC18:02
denis_makogonmaybe we should start with updates from last meeting ?18:03
vgnbkr_1o/18:03
doug_shelley66o/18:03
hub_capdenis_makogon: ?18:03
denis_makogontempest stuff18:03
esmuteo/18:03
hub_capdenis_makogon: if u want to talk about something18:03
hub_capput it on the agenda18:03
denis_makogonok18:04
hub_cap#topic tempest18:04
*** openstack changes topic to "tempest (Meeting topic: trove)"18:04
hub_capSlickNik: denis_makogon would like to know whats up w/ this18:04
*** Sackmann has joined #openstack-meeting-alt18:04
denis_makogonSlickNik, any news about image elements ?18:04
*** gyee has quit IRC18:05
SlickNikdenis_makogon: nope, still WIP.18:05
juiceo/18:05
denis_makogonoh, ok18:05
*** igor__ has joined #openstack-meeting-alt18:05
SlickNikI'm waiting for reviews on this https://review.openstack.org/#/c/69501/18:05
hub_capawesome SlickNik18:06
hub_capim glad u didnt add /xml/ tests :)18:06
SlickNikdenis_makogon: have you started writing other tempest tests that are not dependent on image-elements?18:06
SlickNikhub_cap: I'm not going to :)18:06
denis_makogonSlickNik, i'm still learing tempest18:06
jimbobhickvilleI'm sure glad i spent that week figuring out how to make XML work with scheduled tasks :P18:06
cp16netlol18:07
denis_makogonlets talk about it later18:07
SlickNikIf so, please update: https://etherpad.openstack.org/p/trove-tempest-items18:07
*** cody-somerville has quit IRC18:07
hub_capjimbobhickville: :)18:07
hub_capso moving on?18:07
datsun180bi'm glad i spent that time working on the file suffix fix18:07
denis_makogonyes18:07
SlickNikI'm gonna ask around #openstack-qa this week to get that patch reviewed.18:07
hub_caplol datsun180b18:07
*** khyati has joined #openstack-meeting-alt18:07
hub_cap#topic i3 status18:07
*** openstack changes topic to "i3 status (Meeting topic: trove)"18:07
SlickNikYup, not much else to report on that.18:08
hub_cap#link https://launchpad.net/trove/+milestone/icehouse-318:08
hub_capso we have a few not started and a few unknown states18:08
hub_capif u own one of these plz fix teh state of it, if its being worked on18:08
datsun180bundefined eh18:08
hub_capif its not being worked on yet, talk to me, even if youve talked to me already18:08
datsun180bwell the one i own is in review presently18:09
hub_capdatsun180b: privately :)18:09
hub_capi wont change it right now cuz ill stop payin attn18:09
*** david-lyle has joined #openstack-meeting-alt18:09
hub_capok so, if is not in i3, its not going to be reviewed or merged till after the mid cycle sprint18:10
*** igor__ has quit IRC18:10
hub_capif i -2 you (or another core member fdoes) plz talk to us about it18:10
hub_capif u feel it needs to be in i318:10
*** jdbarry_ has joined #openstack-meeting-alt18:11
hub_capotehrwise we will remove -2's after i3 is cut18:11
kevinconwayhub_cap: any way to keep reviews alive until then?18:11
hub_capkevinconway: yup, click the button every 2 wks :/18:11
kevinconway-_-18:11
hub_capyea it sux18:11
*** nati_ueno has quit IRC18:11
*** rsblendido has quit IRC18:12
*** rossella_s has quit IRC18:12
SlickNikyeah, I know. :/18:12
hub_capok any q's about it?18:12
cp16netsounds good18:12
cp16netgot some work ahead18:12
hub_capok movin on18:13
hub_cap#topic mid cycle sprint18:13
*** openstack changes topic to "mid cycle sprint (Meeting topic: trove)"18:13
hub_capso weve got some great progress on this18:13
denis_makogonyes18:13
*** safchain has quit IRC18:13
hub_cap#link https://wiki.openstack.org/wiki/Trove/IcehouseCycleMeetup18:13
amytrondone18:13
datsun180bapparently it's impossible to get a flight from ABIA to ABIA18:13
hub_capif u look under event details, ther eis a schedule now18:13
hub_capamy has finished the meetup18:13
datsun180ball you get are weird looks from the ticket agents18:13
amytronhaha my bad18:13
amytronwrong window18:14
SlickNiklol @ datsun180b18:14
SlickNikYou need 2 round trip tickets :P18:14
vgnbkr_1datsun180b: slip a redcap $2[18:14
hub_capand we have some events that are being put on too, sponsored by parelastic, hp and rackspace18:15
vgnbkr_1datsun180b: slip a redcap $20 - I'm sure he'd be happy to cart you around the airport.18:15
datsun180b"Where you goin?" "Here"18:15
amytronhey all - if you're a registered trove meetup participant, pls respond to hub_cap with your size by 21:00 UTC18:15
amytront-shirt size18:15
*** gokrokve has joined #openstack-meeting-alt18:15
hub_cap^ ^ ^18:15
hub_capill be coming for u if i dont have your info18:15
hub_capso for our remoters, we need to come up w a solution18:15
amytronotherwise, you're getting a large by default18:15
jimbobhickvillehow many peeps we expectin?18:16
hub_capi think maybe a google hangout w/ someone monitoring irc could ork18:16
hub_capjimbobhickville: its close to 30 now18:16
jimbobhickvillenice18:16
hub_capin a room that fits 20~25 "comfortably"18:16
hub_capso, be prepared to stand18:16
denis_makogonhub_cap, hangout would be perfect18:16
mattgriffin1+118:16
*** mattgriffin1 is now known as mattgriffin18:16
hub_capdenis_makogon: k. ill be sure to set it up18:16
hub_capmattgriffin: ^ ^18:17
denis_makogonthanks, a lot18:17
hub_capill send the info to the ML18:17
*** gokrokve has quit IRC18:17
mattgriffinhub_cap: thanks!18:17
hub_cap#action hub_cap to set up hangouts for the trove meetup18:17
jmontemayorhttp://static2.businessinsider.com/image/5034f4cf69beddb425000017/a-robotics-startup-is-putting-an-ipad-on-a-segway-like-roller-and-selling-it-for-2499.jpg18:17
*** gokrokve has joined #openstack-meeting-alt18:17
grapexjmontemayor: Good idea18:17
hub_capid also like to put together a keysigning party18:18
hub_capwhich ive never done before18:18
hub_capso it might be a bit shaky18:18
*** gokrokve_ has joined #openstack-meeting-alt18:19
*** esp has joined #openstack-meeting-alt18:19
cp16netyeah that sounds fun18:19
*** IlyaE has quit IRC18:19
SlickNikhub_cap: I can help put that together.18:19
vipulo/18:19
*** jcooley_ has quit IRC18:19
hub_capSlickNik: ok perfect18:19
SlickNikLet me get a wiki page going for it.18:20
hub_capSlickNik: k, i already have a good bit of info18:20
juiceI know all about gpg keysigning18:20
juice:)18:20
vipuli know all about parties18:20
SlickNiklol vipul18:21
juiceit's rather trivial process assuming everyone can identify their key and you trust them18:21
juiceI think we can skip the part of the process where you show them your state/gov ID :)18:21
SlickNikyou don't really do the keysigning at the party.18:21
*** jcooley_ has joined #openstack-meeting-alt18:21
SlickNikAll you do is verify their identity, and ensure that you have the right key for them.18:21
SlickNikOnce that's done, you can sign it at your leisure.18:21
hub_capNO SIGNING AT THE PARTY!18:21
hub_capNO LAPTOPS!18:21
juiceawwwww18:22
*** gokrokve has quit IRC18:22
juiceboo18:22
hub_capSlickNik: and i will put together some info18:22
juicewhat if it is to setup a LAN party to play league of legends :)18:22
hub_capand send everyone emails aobut what to do for prep18:22
kevinconwayi've got six or seven keys i need signed at the meet up.18:22
hub_capkevinconway: then u suck at pgp18:22
cp16netno laptops at the meetup?18:22
kevinconwayi'll be in the back18:22
*** saurabhs has joined #openstack-meeting-alt18:22
hub_capcp16net: fail...18:22
cp16netlol18:22
jimbobhickvillejust at the key party cp16net18:22
hub_capok lets move on :)18:22
grapexkevinconway: I get this sinking feeling we'll later have to testify against you for some form of tax evasion...18:23
hub_cap#topic extensions management18:23
*** openstack changes topic to "extensions management (Meeting topic: trove)"18:23
*** jcooley_ has quit IRC18:23
denis_makogon#link https://docs.google.com/document/d/1vsrndOmtCwO2Cb7_6JCE6XZd1kyjWVGCBsjXeT0WOuM/edit?usp=sharing18:23
hub_capdenis_makogon: do u not remember that we had a HUGE discussion on this already?18:23
denis_makogoni've sent the ML18:23
hub_capand came to conclusions?18:23
*** jcooley_ has joined #openstack-meeting-alt18:23
hub_capyou participated18:23
hub_capcweid was the owner and we talked abou twhat we would do18:23
*** lisaclark1 has joined #openstack-meeting-alt18:24
denis_makogoni remember, we came into capabilities18:24
hub_capdid u encorporate that discussion into your thoughts?18:24
*** aignatov is now known as aignatov_18:24
jimbobhickvilleman, hub_cap, expecting people to remember things?  what's up with that?18:24
hub_capright and now kaleb is working on capabilities18:24
hub_capjimbobhickville: lol18:24
grapexI have a comment about item #3- "each method should raise NotImplemented exception"18:24
hub_capkalebpomeroy: thas kaleb18:24
grapexI think we shouldn't bother raising that. If the method isn't there, it won't be callable and will fail either way18:24
denis_makogonyes, i researched over capabilities and found out that trove hasn't got enough flexibility to allows such things18:24
jimbobhickvilleI concur with grapex, the lack of the method existing should be enough of an exception18:25
hub_capdenis_makogon: did u talk to kalebpomeroy who is working on it?18:25
hub_capbecause capabilities doesnt exist yet really denis_makogon18:25
hub_capand its just a blueprint18:25
hub_capthis seems to duplicate that in a way18:25
hub_capusers is a capability of trove, so is volumes18:26
hub_capso is root.. etc...18:26
denis_makogonno, because i didn't knew that he's on that, and there were no ML's about trove and its capabilities18:26
*** bdpayne_ has joined #openstack-meeting-alt18:26
*** bdpayne has quit IRC18:26
hub_capya we have been discussing it at rax, hes brought it up in the channel18:27
kalebpomeroyhttps://wiki.openstack.org/wiki/Trove/trove-capabilities18:27
hub_capso lets see how those can work together, can u work w/ kalebpomeroy denis_makogon ?18:27
hub_capmaybe there is overlap between these18:27
denis_makogoni suppose, channel discussions is not enough, thought18:27
hub_capkalebpomeroy: is there a blueprint too?18:27
hub_capdenis_makogon: definitely18:27
denis_makogonhub_cap, yes, i will18:27
kalebpomeroyhttps://blueprints.launchpad.net/trove/+spec/capabilities18:27
hub_capthis was a mistake on my end, i told him to hold off cuz we were going to discuss in the trove mid cycle sprint denis_makogon18:28
denis_makogonkalebpomeroy, lets talk about that after meeting18:28
hub_capkalebpomeroy: was going to send a ML18:28
kalebpomeroydenis_makogon: K18:28
*** Sukhdev has quit IRC18:28
denis_makogonhub_cap, i raised this question because amcrn wrote me several times at mongo and cassandra reviews18:29
*** beyounn has quit IRC18:29
denis_makogonso i decided to go it asap18:29
hub_capdenis_makogon: its fine18:29
hub_capwe can solve it together18:29
denis_makogonsince redis passed through, i decided to do that asap18:29
*** lisaclark1 has quit IRC18:29
*** aignatov_ is now known as aignatov18:30
hub_capok so anythign else to add to this?18:30
denis_makogonno18:30
hub_capyall gonna chat about it after, cool18:30
denis_makogonmaybe we need ML about capabilities before meet-up18:30
hub_cap#topic security groups18:31
*** openstack changes topic to "security groups (Meeting topic: trove)"18:31
denis_makogon#link https://docs.google.com/document/d/12zy7KYzB3e8fHjHlflU-JevN_rbkOgei4ZjGusgq1bQ/edit?usp=sharing18:31
denis_makogonif there are no objections about oslo groups per datastore and about single ports and port ranges18:31
denis_makogonare there any suggestions for this topic ?18:32
hub_capdenis_makogon: did u and I and amcrn talk about this a while ago?18:32
hub_capand agree on this?18:32
denis_makogonyes18:32
hub_capim pretty sure we wantd to do nested groups, but we couldnt18:32
hub_capthat still doenst exist in oslo rigth?18:32
hub_cap*right?18:32
denis_makogonyes18:32
denis_makogononly stand alone groups18:32
hub_capperfect18:33
hub_capthen i re-approve this denis_makogon  :)18:33
hub_cap#topic backup-restore encryption18:33
denis_makogonso, after some research over oslo and other possible ways, i found out that given implementation is more than enough18:33
*** openstack changes topic to "backup-restore encryption (Meeting topic: trove)"18:33
SlickNikThis looks more reasonable, with the ranges.18:33
hub_capyea18:33
hub_capits great work18:34
denis_makogon#link https://docs.google.com/document/d/1cp-S_KiJjEEo_ZIgWA8lK1pLd5aWITOnnwUGEQU3yME/edit?usp=sharing18:34
denis_makogoni'd not suggest to perform integration with BBQ, until it's not integrated into DevStack fully18:34
denis_makogonsolum followed that way and they stacked18:35
hub_capdenis_makogon: BBQ?18:35
cp16netlol bbq18:35
grapexThat sounds delicious18:35
denis_makogonhub_cap, Barbican18:35
hub_capis that barbican?18:35
hub_caphahahhah18:35
cp16neti made some this past weekend18:35
SlickNikBarbican18:35
grapexIs Barbican's nickname really BBQ? Because if so that is awesome.18:35
denis_makogonBarbican is long enough to write its name fully18:36
denis_makogonBBQ is enough18:36
hub_capbarbican is requesting incubation18:36
denis_makogonor Barby cannon18:36
hub_capbarbie ;)18:36
espI'm getting hungry18:36
denis_makogonlol18:36
SlickNikWhere did the Q come from? Shouldn't it be BBC? :P18:36
jimbobhickvilleBarbie is a registered trademark, it will never get incubated18:37
kevinconwayBBC, code name Dr. Who?18:37
denis_makogoni suggest to make driver driven strategy18:37
hub_caphehe lets get off the name18:37
hub_capdenis_makogon: sure, just like dns18:37
denis_makogonyes18:37
denis_makogonso, what do you think about KDF ?18:37
hub_capbut im not sure i see a need to do it locally18:37
denis_makogoni researched about that almost month18:38
hub_capdenis_makogon: sure i mean thats good for encryption18:38
SlickNikdenis_makogon: KDF sounds good, what's the actual value you plan to use for derivation, though?18:38
hub_capfwiw18:38
hub_cap#link http://en.wikipedia.org/wiki/Key_derivation_function18:38
hub_capbut id rather u impl barbican first18:38
hub_capi dont know if i want that encrytion _in_ our codebase18:38
hub_capif we can use bbq18:38
*** IlyaE has joined #openstack-meeting-alt18:38
SlickNikhub_cap: I definitely don't. I'd rather it be in barbican / oslo18:39
denis_makogonhub_cap, since all up for driver-driven stuff than we can do that in parallel18:39
hub_capno18:39
hub_capnot if we never need it locally18:39
hub_capwe will remove the rsdns driver once we use designate here18:39
denis_makogonBBQ is only requested, RFC already released and implemented18:39
hub_capdenis_makogon: we dont need that extra code here18:39
hub_capif the ONLY reason is that its not incubated18:40
denis_makogoncontrib18:40
hub_capthen thats not a good enough reason to write our own code18:40
hub_capu can put it in another repo if u want but i dont see a need for it in trove if we have a whole key mgmt system being built18:40
*** IlyaE has quit IRC18:40
hub_capanyone agree from core?18:40
hub_capSlickNik: vipul grapex ?18:40
denis_makogonOS cryptography implemented in oslo.crypt18:40
hub_capif u want to push it there, feel free denis_makogon18:40
denis_makogonBBQ is far away from production ready PKI18:40
SlickNik+1 I'd rather not have to deal with a whole crypto codebase in trove.18:40
grapexhub_cap: I agree18:41
*** balajiiyer has joined #openstack-meeting-alt18:41
hub_capand the code we write will be production ready?18:41
imsplitbit+1 hub_cap18:41
denis_makogonSlickNik, oslo ?18:41
*** nati_ueno has joined #openstack-meeting-alt18:41
denis_makogonwhat about pushing it in oslo ?18:41
hub_capu can guarantee that the code u write will be better than a whole proejct devoted to pki encryption?18:41
denis_makogonand we can reuse it from there18:41
juicethat sounds like a smart approach18:41
*** Guest83863 is now known as _nadya_18:41
denis_makogonPKI allows to do more than i proposed18:42
denis_makogonbut i'm guarantee that BBQ will give us what we really need18:42
SlickNikI can be convinced to use PKI from oslo if Barbican's not making much traction.18:42
datsun180b^^18:42
denis_makogonlets start with oslo18:43
hub_capdenis_makogon: feel free to write code in oslo18:43
hub_capand make a barbican driver for us18:43
denis_makogoni'm sure what oslo-inc will release oslo.crypto18:43
SlickNikBut frankly we should align with what OpenStack is doing with PKI as a whole.18:43
hub_capSlickNik: ++18:43
*** akuznetsov has joined #openstack-meeting-alt18:43
hub_capid much rather make it only bbq18:43
hub_caprather than support a legacy thing for the next year or more18:43
grapexOr maybe BYOB18:43
kevinconwayi want lunch suddenly18:43
hub_capthat _isint_ what the rest of openstack is now using18:43
hub_capkevinconway: can u type and eat at the same time?18:44
denis_makogonplugging system18:44
jimbobhickvilledon't you have 3 arms kevinconway?18:44
denis_makogonwe now have contrib dir18:44
cp16neti'd rather not clutter contrib18:44
hub_capdenis_makogon: we can chat about it once u get your code into oslo18:45
hub_capbut it wont go into trove first18:45
hub_capfor now, if u want, u can integrate bbq into trove18:45
hub_capand thats going to be in juno too18:45
hub_capso its likely itll be incubated in juno too18:45
hub_capdenis_makogon: not in contrib18:45
hub_capin oslo18:45
hub_caplike u said18:45
denis_makogonok, i'll do that18:45
denis_makogonbut still i'm not the fun of half-integrated projects18:46
hub_capthat is the point of openstack18:46
hub_capintegration w/ other projects18:46
*** aignatov is now known as aignatov_18:46
hub_capwe are on the bleeding edge of these projects18:46
hub_capand can help them18:46
hub_caplike other porjects helped us18:46
hub_capits our responsibilty to do this18:46
denis_makogonif someone read BBQ's docs - it has lots of security issues in design18:46
hub_capperiod18:46
hub_capthen make it better denis_makogon18:46
hub_capdont rewrite it18:47
hub_capin trove18:47
hub_capperiod18:47
SlickNikdenis_makogon: Then we should bring it up and help fix them.18:47
hub_capthis is the community of together not silos18:47
denis_makogon#action implement KDF to oslo18:47
hub_caplets move on18:47
juicegood speech hub_cap18:47
hub_capthx juice :)18:47
denis_makogonwhat's next ?18:48
hub_cap#topic open discssion18:48
*** openstack changes topic to "open discssion (Meeting topic: trove)"18:48
*** IlyaE has joined #openstack-meeting-alt18:48
hub_capso lets realize we have stuff in i318:48
datsun180byou got to add a handle to #actions, ie #action barney steal fred's pebbles18:48
hub_capand everything we hav ein i3 shoul be merged18:48
hub_caplol datsun180b18:48
*** bauzas has joined #openstack-meeting-alt18:48
*** _nadya_ has quit IRC18:49
denis_makogonguys patches about DB logs audit hanging almost 2 month without reviewers18:49
*** balajiiyer has quit IRC18:49
*** arnaud__ has quit IRC18:49
*** arnaud has quit IRC18:49
*** balajiiyer has joined #openstack-meeting-alt18:49
*** arnaud has joined #openstack-meeting-alt18:50
grapexhub_cap is lagging18:50
cp16nethub_cap: is lagging18:50
kevinconwayis hub_cap lagging?18:50
*** jprovazn has quit IRC18:50
cp16netla18:50
juicewhat's that one about denis_makogon?18:50
cp16netg18:50
juicebriefly..18:50
denis_makogonjuice, pulling database logs18:50
denis_makogonfrom image18:50
juicefrom guest?18:50
denis_makogonyes18:50
denis_makogonfor audit18:50
*** arnaud___ has joined #openstack-meeting-alt18:51
*** hgedikli has quit IRC18:51
hub_capeven if we havent looked at the review yet its low on the prio (or newer than the older ones)18:51
hub_capso i apoligise for not seeing all reviews yet, as does the rest of core18:51
*** hub_cap has left #openstack-meeting-alt18:51
*** hub_cap has joined #openstack-meeting-alt18:51
hub_capwow18:51
hub_capi lagged out so bad18:51
denis_makogoni've sent ML about that18:51
hub_capwowow18:51
*** hgedikli has joined #openstack-meeting-alt18:51
hub_capdenis_makogon: we will look at your code18:51
hub_capits in i318:51
hub_capit will be merged in i318:51
denis_makogonok, thanks18:51
hub_capeverything in i3 will be merged before i318:51
hub_capor backported into i318:51
hub_capperiod18:51
cp16nethub_cap: you like period?18:52
hub_capyup18:52
hub_captoday i do18:52
demorrisso absolute18:52
cp16netbam18:52
SlickNikAlso, it looks like it's been failing unit tests, which makes me de-prioritize it as still WIP.18:52
*** rudrarug_ has joined #openstack-meeting-alt18:52
hub_cap++ SlickNik18:52
hub_capbut the problem is that sometimes we have dependent reviews18:53
hub_capon projects18:53
SlickNikYeah, we need to figure that one out.18:53
cp16netyeah maybe some og my magic i've worked on will help with that18:54
hub_capyup i end up runing them manually18:54
SlickNikMaybe for now leave a note in the review saying that it is dependent on another review?18:54
hub_capcp16net: huuuuuuh?18:54
*** rudrarugge has quit IRC18:54
hub_capyes everyone does that SlickNik18:54
hub_capif its not in the review, then i assume it shoudl work18:54
cp16nethub_cap: i've made some tricks18:54
hub_capbut i do have to look at all the comments from the review-ee18:54
cp16netneed to test it out some more18:54
*** balajiiyer has left #openstack-meeting-alt18:55
hub_capso we have 5 min left18:55
SlickNikcp16net: Let me know if you find some magic to deal with it. Let's try and automate it.18:56
hub_capanything else to chat about?18:56
denis_makogonT-shirts topic ?))18:56
juicestrings of statuses was something mentioned yesterday18:56
cp16netSlickNik: yeah we can talk about it at the meetup more18:56
hub_capdenis_makogon: amy mentioned it18:56
hub_capalready18:56
denis_makogonthen nothing else18:56
juicepushing the status management into respective classes rather than strung throughout the code18:56
hub_capdenis_makogon: someone can say something still18:57
hub_capopen discussion doesnt need to be listed for someone to bring it up :)18:57
denis_makogonyes18:57
hub_capbut if no one else has anything18:57
juiceI don't think there is much to say about it other than there are opportunities to make improvements there18:57
SlickNikI'm good.18:57
juiceand we can do so incrementtally18:57
juiceok I am off to the rally18:58
hub_cap#endmeeting18:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:58
openstackMeeting ended Wed Feb  5 18:58:10 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:58
juiceGo Hawks!!!  And Peace to Ukraine18:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-02-05-18.01.html18:58
grapexjuice: Sounds good18:58
hub_capthx all18:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-02-05-18.01.txt18:58
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-02-05-18.01.log.html18:58
cp16netthx18:58
*** lisaclark1 has joined #openstack-meeting-alt18:58
*** jimbobhickville has left #openstack-meeting-alt18:58
SlickNikjuice: something came up and I won't be able to make it.. :(18:58
SlickNikYou guys have fun.18:58
SlickNiklater all18:58
grapexSee you18:58
*** datsun180b has left #openstack-meeting-alt18:59
*** SlickNik has left #openstack-meeting-alt18:59
*** imsplitbit has left #openstack-meeting-alt18:59
*** lisaclark1 has quit IRC19:00
*** pcm_ has joined #openstack-meeting-alt19:00
*** jdbarry_ has quit IRC19:01
*** glucas has left #openstack-meeting-alt19:02
*** hub_cap has left #openstack-meeting-alt19:02
*** pcm_ has left #openstack-meeting-alt19:04
*** harlowja_away is now known as harlowja19:05
*** ViswaV has left #openstack-meeting-alt19:05
*** igor__ has joined #openstack-meeting-alt19:06
*** jcooley_ has quit IRC19:07
*** jcooley_ has joined #openstack-meeting-alt19:08
*** lisaclark1 has joined #openstack-meeting-alt19:09
*** Sackmann has left #openstack-meeting-alt19:09
*** esp has left #openstack-meeting-alt19:10
*** igor__ has quit IRC19:10
*** beyounn has joined #openstack-meeting-alt19:11
*** Duane_ has joined #openstack-meeting-alt19:14
*** coolsvap is now known as coolsvap_away19:15
*** bdpayne_ has quit IRC19:17
*** bdpayne has joined #openstack-meeting-alt19:18
*** sadasu has quit IRC19:19
*** haleyb has quit IRC19:22
*** eankutse has joined #openstack-meeting-alt19:27
*** ftcjeff has quit IRC19:28
*** haleyb has joined #openstack-meeting-alt19:30
*** irenab has joined #openstack-meeting-alt19:31
*** igor___ has joined #openstack-meeting-alt19:32
*** jasonb365 has quit IRC19:33
*** johnthetubaguy has quit IRC19:34
*** arnaud___ has quit IRC19:34
*** arnaud has quit IRC19:35
*** igor___ has quit IRC19:37
*** akuznetsov has quit IRC19:43
*** arnaud__ has joined #openstack-meeting-alt19:44
*** arnaud has joined #openstack-meeting-alt19:44
*** Duane_ has quit IRC19:45
*** eankutse has quit IRC19:45
*** eankutse has joined #openstack-meeting-alt19:45
*** Duane_ has joined #openstack-meeting-alt19:46
*** baoli has quit IRC19:49
*** denis_makogon has quit IRC19:49
*** Duane_ has quit IRC19:50
*** shakayumi has joined #openstack-meeting-alt20:00
*** mspreitz has joined #openstack-meeting-alt20:01
*** shakayum_ has joined #openstack-meeting-alt20:02
*** igor___ has joined #openstack-meeting-alt20:03
*** Duane_ has joined #openstack-meeting-alt20:03
*** shakayumi has quit IRC20:05
*** igor____ has joined #openstack-meeting-alt20:05
*** igor___ has quit IRC20:07
*** amytron has quit IRC20:09
*** khyati has quit IRC20:09
*** mspreitz has quit IRC20:10
*** julim has joined #openstack-meeting-alt20:11
*** jtomasek has quit IRC20:14
*** michael-yu has joined #openstack-meeting-alt20:14
*** kanabuchi_ has joined #openstack-meeting-alt20:19
*** IlyaE has quit IRC20:20
*** kanabuchi_ has quit IRC20:21
*** gokrokve_ has quit IRC20:21
*** gokrokve has joined #openstack-meeting-alt20:21
*** ycombinator has joined #openstack-meeting-alt20:24
*** rudrarug_ has quit IRC20:25
*** gokrokve has quit IRC20:26
*** ycombinator has quit IRC20:26
*** Barker has quit IRC20:28
*** yogesh has quit IRC20:30
*** Duane_ has quit IRC20:35
*** Barker has joined #openstack-meeting-alt20:37
*** vkmc has quit IRC20:46
*** itzikb has joined #openstack-meeting-alt20:49
*** itzikb has left #openstack-meeting-alt20:52
*** sarob has joined #openstack-meeting-alt20:57
*** sarob has quit IRC20:57
*** Barker has quit IRC20:57
*** sarob has joined #openstack-meeting-alt20:57
*** amcrn has joined #openstack-meeting-alt21:00
*** Barker has joined #openstack-meeting-alt21:00
*** nati_ueno has quit IRC21:02
*** nati_ueno has joined #openstack-meeting-alt21:04
*** irenab has quit IRC21:04
*** dprince has quit IRC21:05
*** RajeshMohan has quit IRC21:07
*** RajeshMohan has joined #openstack-meeting-alt21:08
*** DinaBelova is now known as DinaBelova_21:09
*** baoli has joined #openstack-meeting-alt21:11
*** cp16net has left #openstack-meeting-alt21:11
*** funzo_ is now known as funzo21:12
*** dripton has quit IRC21:17
*** RajeshMohan has quit IRC21:21
*** RajeshMohan has joined #openstack-meeting-alt21:22
*** dripton has joined #openstack-meeting-alt21:22
*** IlyaE has joined #openstack-meeting-alt21:27
*** lisaclark1 has quit IRC21:33
*** nati_ueno has quit IRC21:35
*** lisaclark1 has joined #openstack-meeting-alt21:37
*** yogesh has joined #openstack-meeting-alt21:41
*** sparkycollier has joined #openstack-meeting-alt21:42
*** yogesh has quit IRC21:45
*** amytron has joined #openstack-meeting-alt21:46
*** mestery has joined #openstack-meeting-alt21:54
*** BBG_Stephen is now known as sbalukoff22:00
*** gokrokve has joined #openstack-meeting-alt22:01
*** nati_ueno has joined #openstack-meeting-alt22:02
*** nacim has joined #openstack-meeting-alt22:03
*** jdob has quit IRC22:07
*** nacim has quit IRC22:07
*** david-lyle has quit IRC22:08
*** nacim has joined #openstack-meeting-alt22:08
*** pdmars has quit IRC22:09
*** cody-somerville has joined #openstack-meeting-alt22:10
*** jecarey has quit IRC22:11
*** nacim has quit IRC22:12
*** michael-yu has quit IRC22:12
*** betsy has quit IRC22:13
*** lisaclark1 has quit IRC22:14
*** bauzas has quit IRC22:17
*** jergerber has joined #openstack-meeting-alt22:25
*** lisaclark1 has joined #openstack-meeting-alt22:25
*** mestery has quit IRC22:26
*** denis_makogon_ is now known as denis_makogon22:30
*** gokrokve has quit IRC22:30
*** lisaclark1 has quit IRC22:38
*** lisaclark1 has joined #openstack-meeting-alt22:39
*** michael-yu has joined #openstack-meeting-alt22:42
*** lblanchard has quit IRC22:43
*** ijw has quit IRC22:43
*** RajeshMohan has quit IRC22:43
*** lisaclark1 has quit IRC22:44
*** RajeshMohan has joined #openstack-meeting-alt22:44
*** demorris has quit IRC22:47
*** baoli has quit IRC22:51
*** RajeshMohan has quit IRC22:52
*** RajeshMohan has joined #openstack-meeting-alt22:53
*** gokrokve has joined #openstack-meeting-alt22:53
*** kevinconway has quit IRC22:54
*** shakayum_ has quit IRC22:54
*** Sukhdev has joined #openstack-meeting-alt22:54
*** hemanth has joined #openstack-meeting-alt22:55
*** carl_baldwin has quit IRC22:57
*** ijw has joined #openstack-meeting-alt23:02
*** NehaV1 has quit IRC23:05
*** amytron_ has joined #openstack-meeting-alt23:05
*** amytron has quit IRC23:07
*** amytron_ is now known as amytron23:07
*** lblanchard has joined #openstack-meeting-alt23:17
*** lblanchard has quit IRC23:19
*** david-lyle has joined #openstack-meeting-alt23:21
*** doug_shelley66 has quit IRC23:23
*** amytron has quit IRC23:25
*** doug_shelley66 has joined #openstack-meeting-alt23:26
*** sacharya has quit IRC23:26
*** esker has quit IRC23:29
*** esker has joined #openstack-meeting-alt23:29
*** amytron has joined #openstack-meeting-alt23:30
*** flaper87 is now known as flaper87|afk23:30
*** denis_makogon has quit IRC23:32
*** ijw has quit IRC23:32
*** Barker has quit IRC23:33
*** yamahata has quit IRC23:33
*** esker has quit IRC23:34
*** ijw has joined #openstack-meeting-alt23:34
*** AlanClark has quit IRC23:35
*** mozawa has quit IRC23:38
*** Leonr has quit IRC23:38
*** amytron has quit IRC23:39
*** amytron has joined #openstack-meeting-alt23:40
*** HenryG has quit IRC23:41
*** julim has quit IRC23:42
*** amytron has quit IRC23:43
*** tchaypo has left #openstack-meeting-alt23:45
*** BrianB_ has quit IRC23:51
*** sparkycollier has quit IRC23:53
*** kin_ is now known as nikhil23:56
*** nikhil is now known as nikhil__23:56

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