Wednesday, 2014-02-12

*** noslzzp has joined #openstack-meeting-alt00:00
*** tanisdl has quit IRC00:00
*** ijw_ has quit IRC00:04
*** atiwari has quit IRC00:04
*** ijw_ has joined #openstack-meeting-alt00:08
*** michael-yu has quit IRC00:12
*** ijw_ has quit IRC00:13
*** ijw has joined #openstack-meeting-alt00:17
*** eankutse has joined #openstack-meeting-alt00:17
*** morazi has quit IRC00:21
*** flaper87 is now known as flaper87|afk00:21
*** noslzzp has quit IRC00:21
*** noslzzp has joined #openstack-meeting-alt00:27
*** jcru has joined #openstack-meeting-alt00:28
*** kevinconway has quit IRC00:29
*** demorris has joined #openstack-meeting-alt00:31
*** noslzzp has quit IRC00:34
*** demorris has quit IRC00:36
*** noslzzp has joined #openstack-meeting-alt00:37
*** Ranjitha has quit IRC00:39
*** michael-yu has joined #openstack-meeting-alt00:39
*** noslzzp has quit IRC00:42
*** balajiiyer has joined #openstack-meeting-alt00:43
*** Haiying has joined #openstack-meeting-alt00:43
*** balajiiyer has quit IRC00:47
*** balajiiyer1 has joined #openstack-meeting-alt00:49
*** michael-yu has quit IRC00:51
*** jcru has quit IRC00:53
*** balajiiyer1 has quit IRC00:54
*** bdpayne has joined #openstack-meeting-alt00:54
*** jmaron has quit IRC00:55
*** bdpayne_ has quit IRC00:56
*** nosnos has joined #openstack-meeting-alt01:01
*** MarkAtwood has joined #openstack-meeting-alt01:05
*** sarob has joined #openstack-meeting-alt01:05
*** david-lyle has quit IRC01:05
*** devlaps has quit IRC01:07
*** noslzzp has joined #openstack-meeting-alt01:11
*** sarob has quit IRC01:12
*** eankutse has quit IRC01:13
*** noslzzp has quit IRC01:15
*** eankutse has joined #openstack-meeting-alt01:19
*** MarkAtwood has quit IRC01:20
*** Barker has quit IRC01:23
*** RajeshMohan has quit IRC01:25
*** MarkAtwood has joined #openstack-meeting-alt01:26
*** RajeshMohan has joined #openstack-meeting-alt01:26
*** krtaylor has joined #openstack-meeting-alt01:28
*** Haiying has quit IRC01:30
*** mozawa has joined #openstack-meeting-alt01:34
*** ErikB has quit IRC01:39
*** banix has joined #openstack-meeting-alt01:49
*** balajiiyer1 has joined #openstack-meeting-alt01:50
*** balajiiyer1 has quit IRC01:54
*** ErikB has joined #openstack-meeting-alt01:58
*** xuhanp has joined #openstack-meeting-alt02:02
*** amcrn has quit IRC02:03
*** akuznets_ has joined #openstack-meeting-alt02:08
*** akuznetsov has quit IRC02:09
*** sarob has joined #openstack-meeting-alt02:09
*** MarkAtwood has quit IRC02:10
*** ErikB has quit IRC02:10
*** IlyaE has quit IRC02:12
*** sarob has quit IRC02:13
*** eankutse has quit IRC02:24
*** MarkAtwood has joined #openstack-meeting-alt02:24
*** richm has quit IRC02:26
*** mattgriffin has quit IRC02:26
*** michael-yu has joined #openstack-meeting-alt02:31
*** igormarnat_ has quit IRC02:32
*** eankutse has joined #openstack-meeting-alt02:37
*** ErikB has joined #openstack-meeting-alt02:41
*** banix has quit IRC02:42
*** mattgriffin has joined #openstack-meeting-alt02:43
*** mwagner_lap has joined #openstack-meeting-alt02:45
*** ErikB has quit IRC02:45
*** Haiying has joined #openstack-meeting-alt02:50
*** balajiiyer1 has joined #openstack-meeting-alt02:51
*** balajiiyer2 has joined #openstack-meeting-alt02:53
*** balajiiyer1 has quit IRC02:55
*** balajiiyer2 has quit IRC02:57
*** ijw_ has joined #openstack-meeting-alt02:57
*** ijw has quit IRC02:59
*** flwang has quit IRC03:00
*** arnaud__ has quit IRC03:00
*** banix has joined #openstack-meeting-alt03:01
*** flwang has joined #openstack-meeting-alt03:04
*** arnaud__ has joined #openstack-meeting-alt03:05
*** michael-yu has quit IRC03:08
*** sarob has joined #openstack-meeting-alt03:09
*** igormarnat_ has joined #openstack-meeting-alt03:14
*** gokrokve has joined #openstack-meeting-alt03:14
*** sarob has quit IRC03:16
*** sarob has joined #openstack-meeting-alt03:19
*** esker has joined #openstack-meeting-alt03:21
*** esker has quit IRC03:23
*** sarob has quit IRC03:24
*** esker has joined #openstack-meeting-alt03:24
*** jmontemayor has joined #openstack-meeting-alt03:31
*** arnaud__ has quit IRC03:31
*** arnaud has quit IRC03:31
*** ErikB has joined #openstack-meeting-alt03:37
*** igormarnat_ has quit IRC03:37
*** ErikB has quit IRC03:41
*** eankutse has quit IRC03:50
*** chandan_kumar has joined #openstack-meeting-alt03:51
*** baoli has joined #openstack-meeting-alt03:53
*** balajiiyer1 has joined #openstack-meeting-alt03:53
*** doug_shelley66 has quit IRC03:54
*** balajiiyer1 has quit IRC03:57
*** yamahata has quit IRC03:59
*** dkehn__ has joined #openstack-meeting-alt04:00
*** baoli has quit IRC04:01
*** dkehn has quit IRC04:03
*** dkehn_ has quit IRC04:03
*** arborism has joined #openstack-meeting-alt04:04
*** ken1ohmichi has joined #openstack-meeting-alt04:04
*** dkehn has joined #openstack-meeting-alt04:05
*** yamahata has joined #openstack-meeting-alt04:05
*** amcrn_ has joined #openstack-meeting-alt04:05
*** amcrn_ is now known as amcrn04:08
*** tanisdl has joined #openstack-meeting-alt04:08
*** arborism has quit IRC04:09
*** dkehn__ is now known as dkehn_04:12
*** ErikB has joined #openstack-meeting-alt04:36
*** jmontemayor has quit IRC04:37
*** ErikB has quit IRC04:41
*** AlanClark has quit IRC04:42
*** harlowja is now known as harlowja_away04:44
*** tanisdl has quit IRC04:48
*** nacim has joined #openstack-meeting-alt04:50
*** balajiiyer1 has joined #openstack-meeting-alt04:54
*** markwash has joined #openstack-meeting-alt04:55
*** balajiiyer1 has quit IRC04:58
*** nacim has quit IRC04:59
*** SushilKM has joined #openstack-meeting-alt05:01
*** gokrokve has quit IRC05:09
*** Haiying has quit IRC05:11
*** cadenzajon has joined #openstack-meeting-alt05:13
*** sarob has joined #openstack-meeting-alt05:13
*** banix has quit IRC05:15
*** gokrokve has joined #openstack-meeting-alt05:17
*** cadenzajon has quit IRC05:18
*** sarob has quit IRC05:19
*** sarob has joined #openstack-meeting-alt05:23
*** cody-somerville has quit IRC05:24
*** sarob has quit IRC05:28
*** aignatov_ is now known as aignatov05:36
*** ErikB has joined #openstack-meeting-alt05:37
*** ErikB has quit IRC05:41
*** garyk has quit IRC05:41
*** nosnos_ has joined #openstack-meeting-alt05:43
*** nosnos_ has quit IRC05:44
*** nosnos_ has joined #openstack-meeting-alt05:44
*** DinaBelova_ is now known as DinaBelova05:45
*** nosnos has quit IRC05:46
*** doug_shelley66 has joined #openstack-meeting-alt05:49
*** doug_shelley66 has quit IRC05:53
*** balajiiyer1 has joined #openstack-meeting-alt05:55
*** balajiiyer1 has quit IRC05:59
*** _nadya_ has joined #openstack-meeting-alt06:01
*** saju_m has joined #openstack-meeting-alt06:03
*** nosnos_ has quit IRC06:04
*** nosnos has joined #openstack-meeting-alt06:04
*** gokrokve has quit IRC06:04
*** sarob has joined #openstack-meeting-alt06:07
*** jaypipes has quit IRC06:12
*** MarkAtwood has quit IRC06:13
*** dkehn__ has joined #openstack-meeting-alt06:14
*** jaypipes has joined #openstack-meeting-alt06:15
*** michael-yu has joined #openstack-meeting-alt06:15
*** dkehn__ has quit IRC06:16
*** dkehn__ has joined #openstack-meeting-alt06:17
*** dkehn has quit IRC06:17
*** dkehn_ has quit IRC06:17
*** dkehn has joined #openstack-meeting-alt06:19
*** _nadya_ has quit IRC06:24
*** adrian_otto has left #openstack-meeting-alt06:26
*** lifeless has quit IRC06:34
*** gokrokve has joined #openstack-meeting-alt06:35
*** denis_makogon has joined #openstack-meeting-alt06:35
*** dkehn_ has joined #openstack-meeting-alt06:36
*** ErikB has joined #openstack-meeting-alt06:37
*** gokrokve_ has joined #openstack-meeting-alt06:37
*** dkehn has quit IRC06:38
*** dkehn__ has quit IRC06:39
*** gokrokve has quit IRC06:40
*** dkehn has joined #openstack-meeting-alt06:40
*** MarkAtwood has joined #openstack-meeting-alt06:41
*** ErikB has quit IRC06:41
*** gokrokve_ has quit IRC06:42
*** markwash has quit IRC06:42
*** dmakogon_ has quit IRC06:44
*** aostapenko has quit IRC06:44
*** dmakogon_ has joined #openstack-meeting-alt06:44
*** esker has quit IRC06:45
*** mozawa has quit IRC06:45
*** garyk has joined #openstack-meeting-alt06:46
*** sarob has quit IRC06:47
*** sarob has joined #openstack-meeting-alt06:48
*** michael-yu has quit IRC06:50
*** sarob has quit IRC06:53
*** esker has joined #openstack-meeting-alt06:54
*** balajiiyer1 has joined #openstack-meeting-alt06:56
*** aignatov is now known as aignatov_07:00
*** balajiiyer1 has quit IRC07:00
*** gokrokve has joined #openstack-meeting-alt07:00
*** dkehn__ has joined #openstack-meeting-alt07:01
*** aignatov_ is now known as aignatov07:02
*** dkehn has quit IRC07:04
*** dkehn_ has quit IRC07:04
*** gokrokve has quit IRC07:05
*** dkehn has joined #openstack-meeting-alt07:06
*** jtomasek has joined #openstack-meeting-alt07:07
*** MarkAtwood has quit IRC07:17
*** sarob has joined #openstack-meeting-alt07:18
*** garyk has quit IRC07:18
*** aignatov is now known as aignatov_07:19
*** coolsvap has joined #openstack-meeting-alt07:21
*** mozawa has joined #openstack-meeting-alt07:21
*** sarob has quit IRC07:24
*** coolsvap1 has joined #openstack-meeting-alt07:26
*** coolsvap has quit IRC07:28
*** MarkAtwood has joined #openstack-meeting-alt07:31
*** coolsvap1 has quit IRC07:36
*** coolsvap has joined #openstack-meeting-alt07:36
*** ErikB has joined #openstack-meeting-alt07:37
*** ErikB has quit IRC07:41
*** flaper87|afk is now known as flaper8707:47
*** balajiiyer1 has joined #openstack-meeting-alt07:56
*** gokrokve has joined #openstack-meeting-alt08:00
*** balajiiyer1 has quit IRC08:01
*** IlyaE has joined #openstack-meeting-alt08:04
*** gokrokve has quit IRC08:05
*** amotoki has joined #openstack-meeting-alt08:06
*** jcoufal has joined #openstack-meeting-alt08:13
*** julienvey_ has joined #openstack-meeting-alt08:17
*** MarkAtwood has quit IRC08:18
*** sarob has joined #openstack-meeting-alt08:19
*** dkehn_ has joined #openstack-meeting-alt08:24
*** sarob has quit IRC08:24
*** dkehn_ has quit IRC08:26
*** dkehn_ has joined #openstack-meeting-alt08:26
*** dkehn has quit IRC08:26
*** dkehn__ has quit IRC08:27
*** michael-yu has joined #openstack-meeting-alt08:27
*** dkehn has joined #openstack-meeting-alt08:28
*** PeterSchwaller has quit IRC08:29
*** boris-42_ has joined #openstack-meeting-alt08:30
*** ErikB has joined #openstack-meeting-alt08:37
*** IlyaE has quit IRC08:41
*** ErikB has quit IRC08:41
*** ijw_ has quit IRC08:41
*** PeterSchwaller has joined #openstack-meeting-alt08:44
*** nacim has joined #openstack-meeting-alt08:50
*** nacim has quit IRC08:51
*** michael-yu has quit IRC08:51
*** nacim has joined #openstack-meeting-alt08:53
*** balajiiyer1 has joined #openstack-meeting-alt08:57
*** coolsvap1 has joined #openstack-meeting-alt08:59
*** gokrokve has joined #openstack-meeting-alt09:00
*** coolsvap has quit IRC09:01
*** balajiiyer1 has quit IRC09:01
*** aignatov_ is now known as aignatov09:02
*** SushilKM has quit IRC09:04
*** gokrokve has quit IRC09:05
*** ijw has joined #openstack-meeting-alt09:06
*** sarob has joined #openstack-meeting-alt09:08
*** sarob has quit IRC09:13
*** sarob has joined #openstack-meeting-alt09:19
*** sarob has quit IRC09:24
*** rsblendido has joined #openstack-meeting-alt09:25
*** safchain has joined #openstack-meeting-alt09:25
*** jcoufal has quit IRC09:30
*** jcoufal has joined #openstack-meeting-alt09:30
*** ErikB has joined #openstack-meeting-alt09:36
*** dukhlov has joined #openstack-meeting-alt09:38
*** DinaBelova is now known as DinaBelova_09:40
*** ErikB has quit IRC09:41
*** flwang has quit IRC09:42
*** ken1ohmichi has quit IRC09:43
*** resker has joined #openstack-meeting-alt09:46
*** esker has quit IRC09:50
*** denis_makogon has quit IRC09:57
*** balajiiyer1 has joined #openstack-meeting-alt09:58
*** gokrokve has joined #openstack-meeting-alt10:00
*** balajiiyer1 has quit IRC10:02
*** gokrokve has quit IRC10:05
*** ijw has quit IRC10:06
*** rsblendido has left #openstack-meeting-alt10:12
*** rsblendido has joined #openstack-meeting-alt10:12
*** rossella_s has joined #openstack-meeting-alt10:12
*** sarob has joined #openstack-meeting-alt10:19
*** sarob has quit IRC10:24
*** xuhanp has quit IRC10:28
*** schwicke has joined #openstack-meeting-alt10:32
*** schwicke has quit IRC10:32
*** schwicke has joined #openstack-meeting-alt10:33
*** schwicke has quit IRC10:33
*** ErikB has joined #openstack-meeting-alt10:37
*** flwang has joined #openstack-meeting-alt10:37
*** ErikB has quit IRC10:41
*** aignatov is now known as aignatov_10:41
*** VINOD has joined #openstack-meeting-alt10:45
*** VINOD has quit IRC10:50
*** saju_m has quit IRC10:57
*** balajiiyer1 has joined #openstack-meeting-alt10:59
*** gokrokve has joined #openstack-meeting-alt11:00
*** balajiiyer1 has quit IRC11:03
*** gokrokve has quit IRC11:05
*** lifeless has joined #openstack-meeting-alt11:07
*** mozawa has quit IRC11:08
*** amcrn has quit IRC11:08
*** dkehn__ has joined #openstack-meeting-alt11:18
*** sarob has joined #openstack-meeting-alt11:19
*** dkehn__ has quit IRC11:20
*** dkehn__ has joined #openstack-meeting-alt11:20
*** dkehn has quit IRC11:20
*** aignatov_ is now known as aignatov11:21
*** dkehn_ has quit IRC11:21
*** dkehn has joined #openstack-meeting-alt11:22
*** sarob has quit IRC11:24
*** aignatov is now known as aignatov_11:37
*** ErikB has joined #openstack-meeting-alt11:37
*** saju_m has joined #openstack-meeting-alt11:40
*** ErikB has quit IRC11:41
*** saju_m has quit IRC11:49
*** julienvey_ has quit IRC11:58
*** balajiiyer1 has joined #openstack-meeting-alt11:59
*** gokrokve has joined #openstack-meeting-alt12:00
*** doug_shelley66 has joined #openstack-meeting-alt12:00
*** balajiiyer1 has quit IRC12:04
*** DinaBelova_ is now known as DinaBelova12:04
*** julienvey_ has joined #openstack-meeting-alt12:04
*** gokrokve has quit IRC12:05
*** julienvey_ has quit IRC12:09
*** coolsvap_ has joined #openstack-meeting-alt12:14
*** coolsvap1 has quit IRC12:17
*** dkehn_ has joined #openstack-meeting-alt12:18
*** julienvey_ has joined #openstack-meeting-alt12:18
*** sarob has joined #openstack-meeting-alt12:19
*** dkehn has quit IRC12:20
*** dkehn__ has quit IRC12:21
*** dkehn has joined #openstack-meeting-alt12:22
*** baoli has joined #openstack-meeting-alt12:23
*** baoli has quit IRC12:23
*** sarob has quit IRC12:24
*** baoli has joined #openstack-meeting-alt12:25
*** aignatov_ is now known as aignatov12:26
*** ErikB has joined #openstack-meeting-alt12:36
*** sgordon has joined #openstack-meeting-alt12:37
*** ErikB has quit IRC12:41
*** irenab has joined #openstack-meeting-alt12:44
*** aignatov is now known as aignatov_12:45
*** doug_shelley66 has quit IRC12:45
*** aignatov_ is now known as aignatov12:48
*** beagles has joined #openstack-meeting-alt12:57
*** nacim has quit IRC12:57
*** rkukura has joined #openstack-meeting-alt13:00
baoli#startmeeting PCI Passthrough13:00
openstackMeeting started Wed Feb 12 13:00:21 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
*** gokrokve has joined #openstack-meeting-alt13:00
rkukurahi everyone!13:00
*** balajiiyer1 has joined #openstack-meeting-alt13:00
baoliHi rkukura13:00
irenabhi13:00
baoliwait for a couple of more minutes and see if more will join13:01
beagleshi13:01
*** sadasu has joined #openstack-meeting-alt13:01
sadasuhello13:02
*** noslzzp has joined #openstack-meeting-alt13:03
*** tzumainn has left #openstack-meeting-alt13:03
*** BrianB_ has joined #openstack-meeting-alt13:04
*** gokrokve has quit IRC13:05
*** balajiiyer1 has quit IRC13:05
*** saju_m has joined #openstack-meeting-alt13:05
*** saju_m has quit IRC13:06
irenabCan we start?13:06
*** saju_m has joined #openstack-meeting-alt13:07
baoliI was hoping that Yongli He would join. But let's get started13:07
baoliLet's discuss binding:profile13:07
*** markvoelker1 has joined #openstack-meeting-alt13:07
baoliIrenab, saw your email.13:07
irenabbaoli: what is your opinion?13:08
baoliSo you'd like to have "vendor_id:product_id", and "domain:bus:slot.fu"13:08
sadasuIrena: missed replying yesterday13:08
sadasuI sent reply now13:08
irenabbaoli: I think SRIOV MD will need to filter if to handle the port binding based on vendor:product13:09
sadasuI am OK with separation for  'vendor_id:product_id', 'domain:bus:slot.func'13:09
baoliirenab, I'm fine with it.13:10
sadasuirenab: correct about filtering13:10
*** jecarey has quit IRC13:10
*** igormarnat_ has joined #openstack-meeting-alt13:10
sadasuare they going to be 2 seperate strings?13:10
baoliSo we name the field something like: pci_vidpid, pci_slot.13:10
rkukuraI've read the emails too. I'll forward them to beagles, who is here from Red Hat and is much more familiar with the nova code than I am.13:10
baolisadasu, yes, it's going to be strings13:10
baoliHI beagles13:11
irenabbaoli: this makes sense to me13:11
beagleshi, baoli (and thanks rkukura)13:11
sadasuHi rkukura!13:11
irenabbeagles: wellcome to the club :-)13:11
*** mwagner_lap has quit IRC13:11
sadasuwelcome beagles13:11
beaglesthanks!13:12
*** nacim has joined #openstack-meeting-alt13:12
baoliSo binding:profile:pci_vidpid = "vendor_id:product_id", binding:profile:pci_slot = "domain:bus:slot.func"13:12
sadasu+113:12
irenabbaoli: generally agree13:13
irenabmaybe need more friendly name for vidpid13:13
baoliirenab, what do you suggest?13:13
*** pdmars has joined #openstack-meeting-alt13:13
rkukuraI'm OK with these formats, but am not familiar enough with the nova scheduling and PCI code to know if there are any implications13:13
irenabbaoli: no good ideas, maybe something like pci_vendor_spec13:14
baolirkukura, this is input from nova to neutron while creating/updating a port. We'll get to the physical net name in a bit13:14
rkukurabaoli: Understood13:15
irenablet's start with your suggestion and see if better name comes up13:15
sadasupci_vender_info ?13:15
sadasujust throwing it out there13:15
irenabsadasu: sounds good13:16
baoliirenab, vidpid is vendor_id_product_id but vendor_spec is kind of big.13:16
baoliok, pci_vendor_info is better13:16
sadasupci_vidpid, pci_vendor_spec, pci_vendor_info, 3 choices so far...lets move this discussion to the thread13:17
irenabI am fine with pci_vendor_info13:17
baoliok, let's call it pci_vendor_info13:17
sadasuok....phy_net discussion now?13:17
baoliLet's move on to the phy net name13:17
*** heyongli has joined #openstack-meeting-alt13:18
sadasurkukura: we need phy-net to be part of binding_profile bcuz of multiprovidernet extension?13:18
baoliHi Heyongli13:18
heyonglisorry, later, baoli,13:18
baoliWe are just discussing the fields in binding:profile13:18
irenabrkukura: Is it also required for non SRIOV case?13:18
rkukurasadasu: The ML2 model for networks is that they can have multiple segments13:19
rkukuraThe multiprovidernet API extension lets admins create these, and see the details.13:19
*** sarob has joined #openstack-meeting-alt13:19
*** yamahata has quit IRC13:19
sadasurkukura: ok13:20
*** resker has quit IRC13:20
rkukuraEven if we don't end up having the nova code in icehouse use multiprovidernet, I believe we should define the interaction between nova and neutron so that nova tells neutron which phyiscal_network its SR-IOV device is connected to13:20
sadasurkukura: I agree13:21
rkukuraThe code in the mechanism driver will just need one additional line to compare this to the segment's physical_network as it iterates through the segments (see the AgentMechanismDriverBase)13:21
sadasuI am fuzzy about how the diff segments would be considered for scheduling decision in nova13:21
irenabrkukura: I am not sure why nova will send physical network name to neutron on create port, we currently plan to get physicla network name from neutron13:21
sadasurkukura: agree13:22
rkukurairenab: If nuetron networks never had multiple segments, this info would be redundant, but multiple segments are possible13:22
rkukurasadasu: I also am fuzzy about how nova's scheduling would handle multiple segment networks13:23
*** jecarey has joined #openstack-meeting-alt13:23
*** sarob has quit IRC13:24
rkukuraThe filter would need to allow compute nodes that have an SR-IOV device connected to any of the physical_networks.13:24
irenabrkukura: so nova code that baoli plan, should support multisegment networks for scheduling decision?13:25
*** yamahata has joined #openstack-meeting-alt13:25
rkukuraBut if the instance has multiple SR-IOV ports, then the filter needs to only allow compute nodes with the correct number of available devices, each connected to one of the physical_networks for a specific port's network13:25
rkukuraIf baoli knows how to make the scheduling work, that would be great.13:26
sadasu:-)13:26
irenabrkukura: by filter you mean the MD validate_port_binding sequence?13:26
baolirkukura, as exchanged in the email, each compute node would tag their devices with the phsical network it supports13:26
baoliThen it becomes a matter of finding a compute node that satisfy: net-group = phy-net1 OR net-group = phy-net2 OR ....13:27
rkukuraBut even if we start initially with the nova code only using the old providernet extension, I think the binding:profile:physical_network should be sent to neutron and neutron should ensure that the port binds to a segment with that physical_network13:27
irenabrkukura: agree13:27
*** balajiiyer1 has joined #openstack-meeting-alt13:27
rkukurabaoli: That works fine for a single port.13:28
baolirkukura, what do you mean by single port?13:28
rkukuraIt gets fuzzy for me when their are multiple ports, each with its own list of physical_networks13:28
*** jdob has joined #openstack-meeting-alt13:28
baolirkukura, it works the same way13:28
rkukurabaoli: The instance only connects to one SR-IOV network.13:28
baolirkukura, can you be more specific by "connect to one SR-IOV network"13:29
rkukuraI guess I wasn't sure that we'd be writing logic for the scheduling filter, or trying to setup tags so that some existing filter logic would do what we need13:29
rkukuraIf the former, I don't think handling multiple SR-IOV ports per instance should be difficult.13:29
irenabrkukura: for virtio ports, the multi segment network case will be worked by neutron only?13:30
baolirkukura, we can come up with a new filter.13:30
rkukurairenab: correct13:30
baolirkukura, can you describe the non-sriov case?13:30
irenabrkukura: so SRIOV  MD will need to update some segment related DB table?13:31
rkukurabaoli: By "connect to one SR-IOV network", I mean that the user has done something like "nova boot --nic [1st SR-IOV port info] --nic [2nd SR-IOV port info] ...13:32
*** dprince has joined #openstack-meeting-alt13:32
irenabrkukura, baoli:  I think this case should work13:32
*** kevinconway has joined #openstack-meeting-alt13:33
irenabit should work also for mixing sriov and non-sriov ports for same VM13:33
rkukuraIn the non-SR-IOV case with the agent-based MDs, the ML2 plugin's port binding code iterates over the registered MDs to try to bind, calling bind_port() on each13:33
rkukuraWithin the AgentMechanismDriverBase.bind_port() implementation, it iterates over the network segments, calling check_segment_for_agent() on the derived class for each segment.13:33
*** doug_shelley66 has joined #openstack-meeting-alt13:34
rkukuraThe 1st segment that is tried for which the agent on the node identified by binding:host_id has a mapping for the segment's physical_network is used13:35
heyonglibaoli, i try to catch up the multi segment network what it will impact the device extra info?13:35
rkukuraThe agents_db has these mappings via RPCs from the agents13:35
baolirkukura, so you'd check the vnic_type to decide to use the phy net name or iterate throught the MDs13:35
irenabbaoli: you still need to iterate through the MDs13:36
baolis/to use the phy net name/ to use the phy net name in binding:profile/13:36
*** ErikB has joined #openstack-meeting-alt13:36
rkukuraWe'll need to add a line of code in the existing agent-based MDs check_segment_for_agent() to make sure vnic_type == 'virtio', so it won't bind when SR-IOV is required13:37
baoliheyongli, I don't think so13:37
irenabrkukura: it should be covered by vnic_type support in patch I pushed13:37
irenabI'll check this case13:37
heyonglibaoli, seems all  network side's work13:38
rkukuraI think the SR-IOV MDs will need to iterate over the segments looking for the 1st one that has network_type of 'flat' or 'vlan' and that has the physical_network specified in binding:profile:physical_network13:38
baoliheyongli, it may require enhancement to the pci filter in the scheduler13:38
rkukuraThen, for VLAN, the SR-IOV MDs can include the segment's segmentation_id within the binding:vif_details so that VIF driver can put that into the libvirt XML13:39
heyonglibaoli, does the requirement of the filter clear now?13:39
irenabrkukura: makes sense13:39
irenabsadsu: I think its the place you put the profileid for the port13:40
sadasurkukura: I think I am ok with what you said so far, will try to code it up today and ping if I have questions13:40
rkukurasadasu: ok13:40
baoliHeyongli, we still need to nail it down.13:40
baoliok, so we decide to add this in binding:profile13:40
*** ErikB has quit IRC13:41
baolinow, comes to the name of the field13:41
sadasuirenab: yes, i package segmentation id into my profileid and put that into vif_details13:41
irenabso we have 3 strings on binding:profile13:41
baoliwe have pci_vendor_info, pci_slot13:42
irenabbinding:profile:physical_network, binding:profile:pci_vendor_info, binding:profile:pci_slot13:42
rkukurairenab: +113:42
sadasu+1 from me13:42
baoliagreed13:42
baoliok, move on to binding:vif_details13:43
baoliwe would have either binding:vif_details:profileid or binding:vif_details:vlan_id for the time being?13:43
sadasuI think we need to have both?13:44
irenabsadasu: +113:44
sadasubecause the these will fill diff fields in the libvirt xml file13:44
irenabit will be actually for different VIF Types13:44
baolisadasu, by "or", I mean that which field(s) is available depends on the vif types as Irenab indicated13:45
*** julienvey_ has quit IRC13:45
*** balajiiyer1 has left #openstack-meeting-alt13:45
irenabanother question on VIF types, do we have 2 or 4 vif types?13:45
sadasubaoli, irenab: agree for the dependency on vif type13:46
baoliwe have 802_1qbh and hw_veb to be implemented initially13:46
sadasudirect, macvtap, virtio, hw_veb?13:46
irenabI mean do we have vnic_type impact on VIF_TYPE or use it as additional field to decide how to create libvirt net interface XML13:46
*** julienvey_ has joined #openstack-meeting-alt13:47
irenab802_1qbh_direct, 802_1qbh_macvtap,...?13:47
baoliirenab, vnic_type is available in the port object. I think that we'd use both vnic_type and vif_type to make that decision13:48
irenabbaoli: you will need to propogate the vnic_type to VIFDriver13:49
baoliIrenab, yes13:49
irenabbaoli: OK13:50
baoliI also want to add that the network xml will be a separate BP13:50
sadasufor icehouse or juno?13:51
irenabbaoli: Fine with me.13:51
sadasugoing back, vnic_type would be part of vif_details?13:51
baolisadasu, Hopefully for icehouse, but we are too late13:51
irenabsadasu: +113:52
baolisadasu, vnic_type is part of the port object13:52
baoliwe have 10 minutes left. I want to discuss a little bit on our IRC meeting time13:52
irenabbaoli: I think it make sense to add it to VIF Details13:52
sadasuhow will nova access it ?13:52
sadasuyes, in port object, but has to be part of vif_details too13:53
irenabbaoli: go ahead13:53
rkukuraIf vnic_type is a top-level port attribute, can the nova code just put it into the VIF object for the driver to use?13:53
baolirkukura, that's what I thought13:53
baoliok, do we still need daily meeting?13:53
irenabrkukura: nova will need to manage cases that vnic_type is not present in port (backward compatibility)13:54
baoliand heyongli, I'd like to continue the nova side of things from tomorrow.13:54
heyonglisure13:54
baoliheyongli, cool, thanks13:54
*** dianefleming has joined #openstack-meeting-alt13:55
heyonglibut i can not attend this on Friday13:55
baoliirenab, the default value, if not present, is virtio, right?13:55
baoliheyongli, we dont' have meeting on Friday13:55
heyonglioh,,,13:55
irenabbaoli: It maybe old neutron13:55
baoliirenab, are you suggesting that a NEW nova works with an OLD neutron?13:56
rkukurabaoli, irenab: I think it would be fine the nova VIF driver to default to virtio when the vnic_type is not present13:56
*** krtaylor has quit IRC13:56
*** ErikB has joined #openstack-meeting-alt13:56
*** loquacities has joined #openstack-meeting-alt13:56
rkukuraSomeone may need to think about what all this means for baremetal though;-)13:56
*** krtaylor has joined #openstack-meeting-alt13:57
*** nickchase has joined #openstack-meeting-alt13:57
baoliHeyongli, would Yunghong join tomorrow?13:57
irenabrkukura: any chance you can take a look on the vnic_type patch?13:57
heyonglibaoli , i don't thinks so13:58
irenabbaoli: there can be plugins that not support vnic_type13:58
rkukurairenab: yes13:58
baoliHeyongli, shall we schedule a different time for nova side of things?13:58
irenabagree with rkukura on setting default on nova side if vnic_type not present13:58
heyonglihe is on trip13:58
heyonglibaoli, also fine for me13:59
heyonglifor nova , bp is the big problem13:59
rkukurairenab: I started looking, saw Eugene's comment about DB migrations, then went off an solved that for my vif-details patch!13:59
irenabbaoli: I would like to be in the loop for nova side as well13:59
baoliirenab, I understand13:59
irenabrkukura: I'll look how you solved it!14:00
beaglesbaoli, I would also like to be in the loop on the nova side14:00
*** lblanchard has joined #openstack-meeting-alt14:00
* annegentle waves14:00
*** gokrokve has joined #openstack-meeting-alt14:00
*** jmaron has joined #openstack-meeting-alt14:00
irenabso  see,s we currenlty continue with daily meetings?14:00
baoliSo let's continue tomorrow same time, start with nova stuff.14:00
baoli#endmeeting14:00
sadasubaoli: +114:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Feb 12 14:00:49 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-12-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-12-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-02-12-13.00.log.html14:00
beaglesbaoli, cool14:00
rkukuraI'll continue to track the nova side, but probably won't have as much to say;-)14:00
*** Sam-I-Am has joined #openstack-meeting-alt14:00
*** heyongli has quit IRC14:00
annegentlethanks baoli :)14:00
annegentlewho's here for the doc team meeting?14:01
*** krtaylor has quit IRC14:01
* Sam-I-Am raises hand14:01
annegentle#startmeeting DocTeam14:01
openstackMeeting started Wed Feb 12 14:01:20 2014 UTC and is due to finish in 60 minutes.  The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
*** rkukura has left #openstack-meeting-alt14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: DocTeam)"14:01
openstackThe meeting name has been set to 'docteam'14:01
EmilienMo/14:01
annegentleI think I use a different meeting name and that's bad because then eavesdrop has different folder names. Ah well.14:01
nickchaseI'm here. :)14:01
nickchasegood morning, all.14:01
*** krtaylor has joined #openstack-meeting-alt14:02
annegentleAgenda is here:14:02
annegentle#link https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting14:02
loquacitiesi'm here too, visiting from the future14:02
annegentlehey nickchase14:02
annegentleloquacities: how's tomorrow?14:02
annegentle#topic Action items from the last meeting14:02
*** openstack changes topic to "Action items from the last meeting (Meeting topic: DocTeam)"14:02
loquacitiesonly started a minute and a half ago14:02
loquacitiesso it's a bit early to tell14:02
*** coolsvap_ has quit IRC14:02
*** gpocentek has joined #openstack-meeting-alt14:03
annegentleAll we had was slong to update the howto with the new tools update14:03
annegentleI think that was about test.py changing14:03
loquacitiesthat's correct14:03
loquacitiesi'm not sure if that's done or not, though, i haven't gone looking14:03
annegentlethe one before that was annegentle to email Sam-I-Am for networking details on a slide for webinar14:03
annegentleUh, I don't think I did that, but I don't think the webinar is going to happen, so that's just fine14:03
annegentleAJaeger to create a separate CLI Reference to get input from reviewers14:04
annegentleThat's done, woo!14:04
annegentlelastly, annegentle to find out if Oxygen XML is interested in continuing to support OpenStack with donated licenses14:04
Sam-I-Ambooo14:04
annegentlethat's done as well14:04
loquacitiesaww, no webinar :(14:04
nickchaseare they?14:04
annegentleSam-I-Am: oh believe me I'm fine with no webinar there's enough going on :)14:04
annegentlenickchase: yeah I sent an email to the ML - we got 10 more, one I've given away.14:04
annegentleProbably I'll save another for slong14:04
annegentlebut other wise they're up for grabs14:05
Sam-I-Amannegentle: true14:05
*** gokrokve has quit IRC14:05
loquacitiesi'll mention that next week for apac14:05
*** yamahata has quit IRC14:05
annegentleloquacities: yes please do14:05
annegentleOk next topic if that's all the action items to follow up on14:05
annegentle#topic Doc tools update - 0.6 release of openstack-doc-tools14:06
*** openstack changes topic to "Doc tools update - 0.6 release of openstack-doc-tools (Meeting topic: DocTeam)"14:06
*** sadasu has quit IRC14:06
annegentleheh Looks like I'm behind already14:06
annegentle0.6 release fixed the python packaging14:06
annegentleand there's an upcoming 0.7 it looks like14:06
annegentle#link https://github.com/openstack/openstack-doc-tools14:06
*** zzelle has joined #openstack-meeting-alt14:07
annegentleLots of great progress on translated documents. Much appreciation.14:07
annegentleI'll check with Andreas on 0.714:07
*** yamamoto2 has joined #openstack-meeting-alt14:07
chandan_kumarhello14:07
annegentleAny doc tools questions?14:07
*** AJaeger has joined #openstack-meeting-alt14:08
annegentlehey chandan_kumar!14:08
AJaegerHI14:08
Sam-I-Amhello14:08
annegentleHi AJaeger :)14:08
annegentleDo you need a 0.7 AJaeger? I see it on the release notes section14:09
AJaegerannegentle, not yet - first need to merge all the changes in.14:09
AJaegerAnd I would prefer if people that request features, also review them at least a bit...14:09
annegentleAJaeger: yes good thinking14:09
* AJaeger doesn't want to self-approve without any +1s at all.14:10
annegentleAJaeger: agreed14:10
*** yamahata has joined #openstack-meeting-alt14:10
AJaegerStill, doing it far too often for minor things - if somebody likes to review, I happily wait for you!14:10
annegentleAJaeger: I'll look today, I was definitely offline a lot yesterday14:10
annegentleI don't think David Cramer's here to ask him anything.14:11
annegentledianefleming: can you think of any report for the maven plugin?14:11
AJaegerThanks, annegentle. Shall I add you to features for review?14:11
*** julim has joined #openstack-meeting-alt14:11
annegentleAJaeger: I think I'm subscribed to changes on the repo14:11
AJaegerannegentle, great!14:11
annegentledianefleming has been working on automating the table of contents / sidebar nav for the API reference page14:12
annegentlethat's the only feature that's new for us for clouddocs-maven-plugin14:12
dianeflemingyes!14:12
AJaegerThere're two more that interest me:14:12
AJaegerLinking to ask.openstack.org14:12
chandan_kumari will be reviewing all the doc-tool reviews14:12
annegentleAJaeger: oh yes! Thank you.14:12
dianeflemingsorry, stepped away to get coffee14:12
annegentledianefleming: man I need to get coffee :)14:12
*** vkmc has joined #openstack-meeting-alt14:12
Sam-I-Amannegentle: it helps14:13
Sam-I-Amslurrrrp14:13
annegentleAJaeger: is there a review in place for the link to ask?14:13
dianeflemingi have another one coming to clouddocs-maven-plugin - adding PDF links to the API ref pages14:13
AJaegerBetter way of handling targetdir, this will allow to copy only needed files to the server and remove the delete jobs we have in a few cases14:13
annegentleAJaeger: and how do we time that to prevent it changing stable/havana output?14:13
AJaegerIt's merged already14:13
annegentleAJaeger: ok cool14:13
AJaegerfor ask.o.o: Will only change havana if we update the pom14:14
annegentleAJaeger: oh nevermind my question about preventing changes, it's a version in the pom.xml. Forgive my brain pause.14:14
annegentleAJaeger: :)14:14
AJaegerThe deltion: Only when we switch to new plugin for havana14:14
AJaegerannegentle, exactly ;)14:14
annegentleAJaeger: shall I ask David for a release this week or next?14:14
AJaegerif dianefleming's change for the API site is in: Yeah, ready to release anytime IMHO.14:15
annegentleAJaeger: ok sounds good14:15
annegentleOk anything else on tools?14:15
dianeflemingdavid cramer needs to approve my change on api-site14:15
dianeflemingi'll ping him14:16
annegentledianefleming: ok good14:16
annegentle#topic Style Guide for config strings14:16
*** openstack changes topic to "Style Guide for config strings (Meeting topic: DocTeam)"14:16
annegentledianefleming put together a style guide similiar to the config strings one14:16
annegentle#link https://review.openstack.org/#/c/70778/514:16
annegentleWe can keep reviewing -- just wanted to mention it.14:16
annegentledianefleming: are you also adding to HACKING.rst?14:16
annegentledianefleming: I'll clarify the "admin only" comment14:16
dianeflemingyes, and someone asked that I move it to HACKING.rst in python-novaclient14:17
AJaegerI'm still struggling where this belongs - whether it can be an enhancement to oslo.config or should go to the hacking repository14:17
AJaegerdianefleming, don't move it to HACKING.rst in novaclient. It should apply everywhere!14:17
dianeflemingwell, who is the audience? and where would they be most likely to look for this information?14:17
AJaegerMy suggestion would be hacking repository14:17
dianeflemingok - wasn't aware of hacking repo -14:17
dianeflemingwill put it there14:17
AJaegerThat contains our coding guidelines14:17
dianeflemingok14:18
annegentledianefleming: yeah I wasn't sure either, so good to ask14:18
AJaegerand if nobody likes it, we'll take it in openstack-doc-tools ;)14:18
annegentleAJaeger: good!14:18
dianeflemingokay - sounds like a plan14:18
annegentleOkie14:18
dianeflemingi'll take care of that this morning14:18
annegentledianefleming: sounds good14:18
*** eankutse has joined #openstack-meeting-alt14:18
annegentleOk moving along14:18
annegentle#topic Next APAC docs meeting f2f in Brisbane14:18
*** openstack changes topic to "Next APAC docs meeting f2f in Brisbane (Meeting topic: DocTeam)"14:18
annegentleloquacities: that's cool!14:18
*** yamahata has quit IRC14:19
loquacitieshaha14:19
loquacitiesyep, so there's a fairly large concentration of openstack writers in brisbane14:19
loquacitiesand we've been talking about having a get together for a little while14:19
*** sarob has joined #openstack-meeting-alt14:19
loquacitiesso it made some sense to tie it into the apac meeting14:19
* Sam-I-Am moves to brisbane14:19
AJaegerloquacities, make a group photo to share!14:19
loquacitiesred hat have kindly offered to host it in their new meeting space14:20
annegentleloquacities: that is super cool14:20
loquacitiesfor sure!14:20
annegentleOkay go to loquacities for any more details :)14:20
loquacitiesso we'll still be on irc for anyone who wants to join in14:20
Sam-I-Amah, cool. i was just going to ask that.14:20
annegentleloquacities: ok I'll try to hang out on IRC then too14:21
*** eankutse has quit IRC14:21
loquacitiesbut all the brisbanites will be in a room together :)14:21
loquacitiesthat'd be awesome14:21
loquacitiesthanks for the support14:21
annegentle#topic Operations Guide edits from O'Reilly, master and feature/edits branches14:21
AJaegermight be at some "crazy" hour ;)14:21
*** openstack changes topic to "Operations Guide edits from O'Reilly, master and feature/edits branches (Meeting topic: DocTeam)"14:21
annegentleSo we have a new branch of the openstack/operations-guide repo14:21
annegentleit's called feature/edits14:21
AJaegeris it pushed to github?14:21
annegentleWe can move anything from master to feature/edits and vice versa14:21
annegentleAJaeger: yep14:21
*** saju_m has quit IRC14:21
*** rsblendido has quit IRC14:22
*** rossella_s has quit IRC14:22
annegentleO'Reilly sent an annotated PDF of edits for ch 1-7 last night, so we'll be updating master with those, and then I'll port to feature/edits14:22
AJaegerAh, found it!14:22
annegentleMostly it's for consistency - like getting the two architectures more parallel, tables, etc14:22
annegentleAJaeger: yeah I need to find the instructions for porting back and forth so I'm ready to try some!14:23
*** eankutse has joined #openstack-meeting-alt14:23
Sam-I-Amannegentle: that was quick14:23
Sam-I-Amannegentle: i could use some instructions too14:23
annegentleSam-I-Am: yeah they're minor really, it's not a technical edit but a consistency edit14:23
Sam-I-Amme and git... little rocky.14:23
AJaegerannegentle, it'S in the wiki - but I can sent you my scripts for backports as well...14:23
annegentleSam-I-Am: AJaeger: tell me if this makes sense, but I think just one person should do the back and forth?14:23
gpocentekannegentle: how does it work, O'reilly makes edits on feature/edits themselves, or should the doc team do the modifications?14:23
annegentleSam-I-Am: heh me too14:23
*** yamahata has joined #openstack-meeting-alt14:23
annegentlegpocentek: we wanted O'Reilly to make edits on feature/edits themselves, but he apologetically sent an annotated PDF :)14:24
gpocentekok :)14:24
*** eankutse has quit IRC14:24
Sam-I-Amannegentle: if one person handles the back-and-forth, can multiple hand the edits?14:24
AJaegerYeah, best if one person does it.14:24
annegentlegpocentek: and I might go ahead with your abandoned edits since it seems like we still have time to get stuff over14:24
gpocentekannegentle: does it makes sense to merge the beginning of a patch I made then?14:24
annegentleAJaeger: ok14:24
*** eankutse has joined #openstack-meeting-alt14:24
*** sarob has quit IRC14:24
annegentlegpocentek: yeah, just what I was thinking! mind reader :)14:24
*** eankutse has quit IRC14:24
gpocentek:)14:25
*** eankutse has joined #openstack-meeting-alt14:25
annegentleI know the goal is to release in March so it's aggressive and I'd rather distract just me, though, rather than a lot of people... there's enough release doc work to go around.14:25
*** aignatov is now known as aignatov_14:25
annegentlegpocentek: so that was my thinking ^^ was avoiding distractions14:26
* annegentle deflects distractions!14:26
annegentleAny questions on that?14:26
annegentle#topic Proposals for OpenStack Summit due 2/14, Design Summit tracks will be set in April14:26
*** openstack changes topic to "Proposals for OpenStack Summit due 2/14, Design Summit tracks will be set in April (Meeting topic: DocTeam)"14:26
gpocentekannegentle: if you need help to apply O'Reilly suggestion I can find some time14:26
annegentlegpocentek: thanks much.14:26
annegentlegpocentek: I just might need to take you up on that :)14:27
annegentlegpocentek: so far so good14:27
annegentleSo, the Summit proposals are due this Friday14:27
*** rohit404 has joined #openstack-meeting-alt14:27
annegentlelast Summit there were 600 proposals14:27
gpocentekannegentle: ok, feel free to ping me any time14:27
annegentleThese proposals are not for the Design Summit where we decided what to work on next release14:27
annegentleThose I'll be asking for about a month ahead of the Summit.14:28
annegentleThe Summit is May 12-16 in Atlanta, GA14:28
*** gokrokve has joined #openstack-meeting-alt14:28
annegentle(Yes I realize the US Mother's Day is the Sunday before)14:28
nickchaseI feel like I'm juggling 600 proposals right now just from Mirantis.  (JK)14:28
*** aignatov_ is now known as aignatov14:28
annegentlenickchase: heh I believe it14:28
annegentledianefleming and I are proposing one in the Community Building section about the Documentation community and how we operate14:28
annegentleSeems like each Summit I get asked if I proposed one about docs so there it is!14:29
loquacities\o/14:29
nickchase:)14:29
annegentleMany thanks to dianefleming for the outline. Really she does all the work around here.14:29
AJaegerannegentle, dianefleming: Great!14:29
Sam-I-Amdo we just talk about how cool this team is?14:29
annegentleSam-I-Am: heeh yes14:29
AJaegerSam-I-Am, a group hug ;)14:29
dianeflemingha ha -14:29
dianeflemingyeah right!!!! :)14:29
*** esker has joined #openstack-meeting-alt14:30
annegentletalks about our meetings, book sprints, what works well, what's difficult14:30
chandan_kumarhappy hug day to all the team mates :)14:30
annegentleAll of it!14:30
annegentlechandan_kumar: :)14:31
annegentleOk that's all I've got on the Summit.14:31
*** irenab has quit IRC14:31
annegentleWell other than to strongly encourage docs team to apply for the Travel Program14:32
annegentle#link https://wiki.openstack.org/wiki/Travel_Support_Program14:32
dianefleming@annegentle we should definitely get short bios and pictures of everyone on this team to include in our presentation!14:32
annegentledianefleming: that's a great idea!14:32
annegentledianefleming: let's see if it gets accepted :)14:33
annegentledianefleming: before doing a ton of work.14:33
dianeflemingyeah!14:34
AJaegerWE should all vote for it once voting is up ;)14:34
annegentleAlthough, this preso can be reused a bunch for Write the Docs and Open Help14:34
annegentleAJaeger: :)14:34
annegentle#topic API Docs blueprint updated14:34
*** openstack changes topic to "API Docs blueprint updated (Meeting topic: DocTeam)"14:34
annegentle#link  https://wiki.openstack.org/wiki/Blueprint-os-api-docs14:34
*** Haiying has joined #openstack-meeting-alt14:34
annegentleso remember how we were gonna move all the <project>-api docs into the <project>/doc location?14:35
annegentlewe've updated the blueprint to not do the move this release14:35
annegentledianefleming: any other details you want to be sure people know?14:35
dianeflemingnothing i can think of - just that it's a work in progress, with some of the work happening now and the completion happening in juno14:35
dianeflemingbut the effort is serving to clean up the API docs in general - it's having a good effect overall (i think)14:36
annegentledianefleming: yeah sounds right. And YES on the cleanup.14:37
annegentledianefleming: lots of improvement this release. A LOT.14:37
annegentleOkay any API docs Qs?14:37
dianeflemingthanks, and big thanks to AJaeger for all the gating work he did for APIs14:37
annegentleyes14:37
annegentleabsolutely AJaeger!14:38
Sam-I-Amyes... lots of work14:38
AJaegerThe gating work showed a lot of problems that dianefleming had to fix ;)14:38
AJaegerSo, we kept each other busy - thank!14:38
annegentlealways that tension between quality testers and the people making stuff!!14:38
dianeflemingha ha - yes true - but i wouldn't have known about that without the gates14:38
*** ajo has joined #openstack-meeting-alt14:38
AJaegerand now I don't see it coming in again...14:38
*** saju_m has joined #openstack-meeting-alt14:38
annegentle#topic Giveaways: Oxygen licenses are available, Travel Program for Summit, and Write the Docs in Budapest14:39
*** openstack changes topic to "Giveaways: Oxygen licenses are available, Travel Program for Summit, and Write the Docs in Budapest (Meeting topic: DocTeam)"14:39
annegentleOkay, just want to be sure people know about the stuff you can get!14:39
annegentleI mentioned the Oxygen licenses earlier14:39
annegentleand the Travel Program14:39
annegentleSo also wanted to say we have a free registration for Write the Docs.14:40
annegentle#link http://conf.writethedocs.org/eu/2014/index.html14:40
annegentleAJaeger: is that anywhere near you?14:40
loquacitiesit looks like a great conf14:40
annegentleI sat and watched nearly ALL the videos from the last Write the Docs14:40
annegentleloquacities: yes! Rackspace is a sponsor14:40
loquacitiesi saw :)14:40
*** betsy has quit IRC14:41
*** rsblendido has joined #openstack-meeting-alt14:41
*** rossella_s has joined #openstack-meeting-alt14:41
AJaegerannegentle, depends on your definition of near - for me its too far ;)14:41
annegentleAJaeger: yeah I have those same definitions :)14:41
Sam-I-Amclose than we are14:41
Sam-I-Amcloser14:41
annegentleIdeally we'll get some passes for the Portland one too14:41
annegentleJamie Hannaford, a PHP dev on the same team as Diane and I, will be in Hungary14:42
annegentleOk, want to leave time for install doc talk!14:43
annegentle#topic Installation guide updates for Icehouse14:43
*** openstack changes topic to "Installation guide updates for Icehouse (Meeting topic: DocTeam)"14:43
annegentleSam-I-Am: sounds like you've had some good progress!14:43
Sam-I-Amwoooo14:43
Sam-I-Amyeah, had some meetings with nick and phil14:43
Sam-I-Amprimarily trying to work out the networking stuff14:43
*** MarkAtwood has joined #openstack-meeting-alt14:43
Sam-I-Amin order to make networking fit best, some other parts of the doc could use some rearrangement14:44
Sam-I-Ami finally have a working installation of icehouse on havana with nova-net14:44
nickchaseYes, Sam-I-Am has doen a great job14:44
Sam-I-Amso far the steps arent too different from havana. however, i would really like to find someone who can explain what really needs to be in the [keystone_authtoken] section of each service config file14:45
nickchaseWe have a blueprint of the changes we want to make.14:45
AJaegerapplause for Sam-I-Am14:45
Sam-I-Amseems to be magical undocumented goodness14:45
loquacitiesnice work Sam-I-Am14:45
*** jamiec_ has joined #openstack-meeting-alt14:45
Sam-I-Amalso a few questions about the v3 identity api because keystone now claims v2 is deprecated, but v3 doesnt seem to work.14:45
*** MarkAtwood has quit IRC14:46
Sam-I-Ammy next step is trying to get neutron/ml2 working on icehouse/ubuntu14:46
annegentleSam-I-Am: I've been bugging dolphm about it14:46
Sam-I-Amannegentle: thx14:46
annegentleSam-I-Am: there's no support for v3 in their client as I understand it14:46
Sam-I-Amin addition to fixing networking, i'm trying to un-cruft the install guide14:46
annegentleSam-I-Am: I think they can't deprecate v2 yet14:46
Sam-I-Amthe good news is i havent needed to edit a single .ini file yet :)14:46
*** ccrouch has left #openstack-meeting-alt14:47
annegentleSam-I-Am: whoohoo14:47
annegentleSam-I-Am: oh I had another thought about swift/keystone14:47
Sam-I-Amthe networking party also decided we'd get the install guide done first, then work on the cloud guide and book14:48
annegentleSam-I-Am: I think that people will want that arch in, but it shouldn't need much more than testing for icehouse14:48
annegentleSam-I-Am: so that hopefully isn't much14:48
annegentleSam-I-Am: sounds good14:48
Sam-I-Amannegentle: so swift without any other components?14:48
AJaegernickchase, do you have a link handy for the blueprint?14:48
nickchase#link https://wiki.openstack.org/wiki/Documentation/InstallGuideChanges14:49
annegentleSam-I-Am: swift and keystone only... thing is, you don't get a dashboard without horizon/nova I think14:49
Sam-I-Amannegentle: how many people do that?14:49
nickchaseI want to get the existing structure in there and then will be sending it over the to ML in case people have feedback before we start moving things.14:49
annegentleSam-I-Am: right now we "add swift" with our install guide14:49
annegentleSam-I-Am: lots of people, storage is that entry point14:49
annegentleSam-I-Am: adding swift means that the dash works14:50
Sam-I-Amannegentle: hmm, i'll have to see where we can fit a "lite" swift chapter14:50
annegentleSam-I-Am: it's also fine to leave it how it is, as additive14:50
annegentleSam-I-Am: just don't want it to get lost is all14:50
Sam-I-Amwe'll find a place for it... and an arch... somehow.14:51
annegentleany questions about install, networking, storage, anything?14:51
Sam-I-Amlooks pretty quiet :P14:52
* AJaeger just read the wiki page - I like where this is going!14:53
annegentle#topic Docs core, docs team14:53
*** openstack changes topic to "Docs core, docs team (Meeting topic: DocTeam)"14:53
annegentleI wanted to follow up on the email I sent to the list about docs core14:53
nickchaseGreat, thanks AJaeger!14:53
Sam-I-Amthanks a14:53
annegentlewanted to emphasize that we don't have to have a super large core, and core is about reviews more than anything14:54
* AJaeger looks forward to more reviewers ;)14:54
annegentleAJaeger: yes :)14:54
* loquacities has been putting more effort into reviews this week14:54
loquacitiesi slacked off last month ;)14:54
* Sam-I-Am tries to review more... but doesnt necessarily understand everything14:54
annegentleI also realize I should trim out docs core for those who aren't really reviewers any more14:54
annegentleloquacities: you've been doing great reviews!14:54
loquacitiesaww, thanks :)14:55
loquacitieshopefully they're helpful14:55
loquacitiesand dianefleming i've been meaning to say sorry for being so nitpicky!14:55
annegentleI still don't really want to go to a ML vote -- I like how infra runs theirs with small growth rate, but that can change for sure!14:55
annegentleAnd I do appreciate all the input...14:55
annegentleand I probably will change my mind about votes eventually...14:55
Sam-I-Amheh @ diane reviews14:55
AJaegerloquacities, sure!14:55
*** yamahata has quit IRC14:55
dianeflemingnit-picky? ha! you're talking to the queen of the nit-pickers!14:55
loquacitieshehe, at least we're on the same page ;)14:56
annegentleLOL14:56
loquacitiesso to speak :P14:56
dianeflemingon the same page with the same red pencil!14:56
loquacities\o/14:56
*** IlyaE has joined #openstack-meeting-alt14:56
Sam-I-Am'drive-by-diane-ing' - when you have a few +1s and out of nowhere comes a -1 for a period or comma somewhere :P14:56
annegentlehee hee hee so true14:56
loquacitiesLOL14:56
nickchaseHA!14:56
AJaegerI agree, we need active reviewers - and those that are in core and don't want to review anymore, should be asked to either step up or leave...14:56
dianeflemingha ha ha - i'm a little slow to the game, and then i like to crash into things!14:57
annegentleAJaeger: yeah14:57
Sam-I-Ami always fear the -114:57
AJaegerSam-I-Am, especially in a paragraph taht you didn't touch at all ;)14:57
Sam-I-AmAJaeger: lol yeah14:57
loquacitiesohh, i'm good at those14:57
annegentlealso, I took from the 90-day list of reviewers, looking for longer-term knowledge of the docs state14:57
loquacities"I know you didn't edit this bit, but i just noticed this crime against English grammar ..."14:57
Sam-I-Amwe lost our other drive-byer... nermina14:57
annegentleso sad to lose nermina!14:58
Sam-I-Amshe still lurks14:58
loquacities:'(14:58
nickchaseBelieve me, nobody misses her more than I do.14:58
nickchaseWe did hire a new writer14:58
annegentlenickchase: hope you're hiring!14:58
*** amuller has joined #openstack-meeting-alt14:58
*** Haiying has quit IRC14:58
loquacitiesfresh blood!14:58
annegentlenickchase: great, let us know if you want any help onboarding/training14:58
Sam-I-Amnickchase: when is the hazing?14:58
nickchaseI'm shanghia -- I mean introducing her to docs tomorrow14:58
loquacitieslol14:58
nickchase:)14:59
annegentleheehee14:59
AJaegernickchase, great!14:59
annegentleOkay onward!14:59
Sam-I-Am"we shall -1 your patches for tiny things for a month"14:59
annegentle#topic Open discussion14:59
*** openstack changes topic to "Open discussion (Meeting topic: DocTeam)"14:59
annegentlewell for one minute :)14:59
loquacitiesbetter make it quick ...14:59
annegentlehee14:59
Sam-I-Amstill having a blast working with y'all14:59
loquacities+114:59
Sam-I-Amkeeps me sane14:59
annegentleWe are working towards developer.openstack.org, where SDKs will live14:59
*** Swami has joined #openstack-meeting-alt14:59
annegentleso stay tuned for more user-dev oriented work15:00
annegentleSam-I-Am: awesome!15:00
annegentleSam-I-Am: your energy has been great!15:00
loquacitiesyes, indeed :)15:00
nickchasewe just have to forbid him from working weekends. :)15:00
annegentleok better give up the meeting room, thanks all!15:00
annegentle#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
nickchasebye15:00
openstackMeeting ended Wed Feb 12 15:00:49 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-02-12-14.01.html15:00
Sam-I-Amnickchase: i managed last weekend!15:00
loquacitiesthanks annegentle15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-02-12-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/docteam/2014/docteam.2014-02-12-14.01.log.html15:00
* loquacities wanders off to bed15:01
Swamihi15:01
*** banix has joined #openstack-meeting-alt15:01
nickchaseSam-I-Am; good!15:01
*** cody-somerville has joined #openstack-meeting-alt15:01
*** yamahata has joined #openstack-meeting-alt15:01
Sam-I-Amnickchase: i was bored, but did not openstack :P15:01
annegentlegnite loquacities!15:01
*** nickchase has quit IRC15:01
Sam-I-Amnight loq15:01
loquacitieso/15:01
* Sam-I-Am gets more coffee15:01
*** Sam-I-Am has left #openstack-meeting-alt15:01
Swamiping carl15:01
*** mozawa has joined #openstack-meeting-alt15:01
Swamiping safchain15:01
Swamiping jamie15:01
ajohi :)15:02
Swamiping carl15:02
ajoDVR meeting?15:02
jamiec_hi15:02
SwamiYes this is the DVR meeting15:02
Swamijamiec_: Nice to see you after a long time15:02
*** mozawa has quit IRC15:02
Swami#startmeeting distributed_virtual_router15:02
openstackMeeting started Wed Feb 12 15:02:59 2014 UTC and is due to finish in 60 minutes.  The chair is Swami. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: distributed_virtual_router)"15:03
openstackThe meeting name has been set to 'distributed_virtual_router'15:03
jamiec_yes, sorry couldn't get on earlier15:03
Swamijamiec_: its ok, if you joined the meeting at the right time.15:03
Swamiping safchain15:03
Swamiping Robin wong15:03
ajoping amuller15:04
amullerSwami: I wasn't able to write up my VRRP A/A idea in time, but I was hoping to present it concisely just so people are aware of it when considering DVR15:04
Swamiamuller: Hi15:04
Swamiamuller: are you going to present today in this meeting.15:04
amulleryes15:04
Swamiis it different than the safchain vrrp idea15:05
amullerIt's an extension / a second blueprint depending on safchain's blueprint15:05
amullerit relies on his bp15:05
Swamiwhat I am asking is, for the DVR is it different than the safchain blueprint that uses the vrrp15:06
amullerIt's different but the ideas are related15:06
amullerAnd they can solve the same issues15:06
amullerSo it's worth considering I think15:06
Swamiok, let me tell you one thing. We have a meeting tomorrow and this would be the dry run to discuss what we are going to present in that meeting to the global audience15:07
amullerRight15:07
amullerI understand I'm coming in late15:07
*** hemanthravi has joined #openstack-meeting-alt15:07
SwamiYes you are too late.15:07
hemanthravihi15:07
*** richm has joined #openstack-meeting-alt15:07
SwamiBut what I would suggest is, send us a copy of your blueprint and we can take a look at it. Next week we can have a discussion and see what are the pros and cons and then evaluate.15:08
Swamihemanthravi: hi.15:08
*** sgordon has left #openstack-meeting-alt15:08
Swami#agenda F2f dry run and update on the blueprint changes.15:08
amullerSwami: I'll do that15:09
Swami#link https://docs.google.com/document/d/1iXMAyVMf42FTahExmGdYNGOBFyeA4e74sAO3pvr_RjA/edit15:09
SwamiHi folks I would like to go over the blueprint changes with you folks, the link to the document is pasted above.15:09
hemanthraviswami: added some comments to the doc last night, some of them might be due lack of info on my par15:10
hemanthravit15:10
Swamiamuller: yes thanks, that would help. I don't want to de-rail our efforts at this time.15:10
*** lazzzy_ has joined #openstack-meeting-alt15:12
Swamihemanthravi: I will take a look at your comments and then probably answer your comments.15:12
SwamiOk let me discuss the high level changes that had happend in our blueprint.15:12
*** Barker has joined #openstack-meeting-alt15:12
Swami#info Blueprint change15:12
SwamiWe have split the routing, floating and SNAT.15:13
SwamiThe routing functionality will be distributed across the compute Nodes and each router will run in its own namespace in the compute node.15:13
SwamiThe SNAT functionality for external connectivity will be centralized and be part of the Service Node or the Legacy Network Node.15:14
jamiec_Swami: just the SNAT?  floating still on the compute?15:15
*** BrianB_ has quit IRC15:16
SwamiThe reason we wanted to split the SNAT functionality and make it centralized is to get rid of the "IP Address consumption" in each and every node for the SNAT and also to provision the singleton services such as "VPN router" in the Service node or Legacy Network node.15:16
Swamijamiec_: Is I am coming there, let me finish the SNAT part.15:16
jamiec_ok15:16
SwamiFor FloatingIP we are providing Floating IP at the Compute Node Level, but the FloatingIP will be allocated and provisioned in its own namespace. Each compute node will have "a" flaotingIP namespace that will be shared by all tenants.15:17
SwamiSo by splitting the "SNAT", floatingiP and routers we are now able to provide "East-West routing" and "North-South" routing without affecting any of our services.15:19
Swamiping safchain15:19
*** sarob has joined #openstack-meeting-alt15:19
safchainSwami, Hi, sorry to be late15:19
Swamisafchain: it is ok.15:19
SwamiI was just briefing the change that we did to our blueprint to logically merge with your ideas on splitting the Floatingip and SNAT from the router.15:20
Swamisafchain: I am not sure if you had a chance to look at the changes that I did to the doc.15:21
*** jjmb has joined #openstack-meeting-alt15:21
safchainSwami, yes I did15:21
hemanthraviswami: in the current network-node impl, don't snat and floating-ip use the same addr?15:21
hemanthraviin the non dvr case15:21
*** shivharis has joined #openstack-meeting-alt15:22
Swamihemanthravi: Yes, but in our model, the SNAT will consume one IP Address and the Floating IP, where ever it is enabled will be consuming an IP address from the external pool.15:22
*** betsy has joined #openstack-meeting-alt15:23
SwamiIn the doc that I updated, you can see there are couple of "Admin" level API changes that we have proposed, and that is purely for legacy L3 migration.15:23
*** sarob has quit IRC15:24
Swamijamiec_: did I answer your question.15:24
safchainSwami, yes only small changes, which is a good thing15:24
jamiec_Swami: yes, thank you - clear now15:24
jamiec_makes sense15:24
Swamisafchain: We might have to sync up on the "Arp" proxy implementation.15:25
*** dianefleming has quit IRC15:25
*** demorris has joined #openstack-meeting-alt15:26
SwamiCurrently we are not dependent on the OVS arp proxy implementation, but we are preventing arp, and populating arp table from our agent. But if we all wanted to use the "ovs" arp proxy with the ml2-pop we can use it.15:26
safchainSwami, edouard did lot of work around that, arp responder on ovs and work on an ebtables wrapper15:27
safchainSwami, https://review.openstack.org/#/c/49227/ ARP responder on OVS for l2 pop15:28
Swamisafchain: Thanks I might have to sync up the edouard on the timeline and delivery for the arp responder on ovs,15:28
*** eankutse has quit IRC15:29
*** eankutse has joined #openstack-meeting-alt15:29
*** jmaron has quit IRC15:29
Swamisafchain: For tomorrow's meeting I would like to have the agenda as a follow up from the "Hong Kong" summit.15:29
safchainSwami, not sure to be able to attend tomorrow, i'll try15:30
SwamiI would like to present it, saying that we presented a DVR blueprint for the Icehouse summit with just "East-West", community wanted to address "North-South" as well and aslo don't like the kernel module solution.15:31
*** igormarnat_ has quit IRC15:31
SwamiSo we went back and safchain: had a norht-south solution and we had a east-west solution and we came up with this solution that addresses both north-south and east-west.15:31
*** akuznets_ has quit IRC15:32
*** rohit404 has quit IRC15:32
Swamisafchain: If you could not make it, I will make sure that I will also bring up your doc for discussion with the audience.15:32
safchainSwami, ok thx15:33
*** aignatov is now known as aignatov_15:33
*** rohit404 has joined #openstack-meeting-alt15:33
*** sballe has joined #openstack-meeting-alt15:33
Swami#info Tomorrow for the F2F there will be a change in the Conference Room, since more people are attending I booked a bigger room. This room will be "Building 20" Palo Alto HP Office. I will send out the details and directions.15:34
*** jamiec_ has quit IRC15:34
*** jamiec_ has joined #openstack-meeting-alt15:34
*** colinmcnamara has joined #openstack-meeting-alt15:35
*** sergmelikyan has quit IRC15:36
SwamiAlso the other information about the doc update, we would be using just a single agent which will be a superset and based on the config option the agent will behave either distributed router agent, floatingip agent or the default SNAT agent aka legacy L3 agent.15:36
*** akuznetsov has joined #openstack-meeting-alt15:36
*** akuznetsov has quit IRC15:36
*** dkehn__ has joined #openstack-meeting-alt15:37
*** coolsvap has joined #openstack-meeting-alt15:37
SwamiIn the model that has been proposed, services such as "LBaaS" will not have any issue. FWaaS should be implemented in all compute Node routers, since we are doing East-West. This will not be a problem since we are using the same L3 agent and if required we can make changes to fix any issues.15:37
*** dkehn has quit IRC15:38
*** dkehn_ has quit IRC15:38
*** akuznetsov has joined #openstack-meeting-alt15:39
*** atiwari has joined #openstack-meeting-alt15:39
SwamiI might have a question for the community to address the "VPN service". There should be a way to identify that specific router so that we can deploy that router in the "Service node/legacy network node".15:39
*** chandan_kumar has quit IRC15:39
*** akuznetsov has quit IRC15:40
*** dkehn has joined #openstack-meeting-alt15:40
Swami#action After this meeting if you have any questions please feel free to add your comments to the google doc and I will try to answer the questions.15:40
*** chandan_kumar has joined #openstack-meeting-alt15:40
*** jmaron has joined #openstack-meeting-alt15:40
Swami#acton amuller: Please share your doc with us next week so that we can have a discussion on your suggestion.15:41
Swami#action amuller: Please share your doc with us next week so that we can have a discussion on your suggestion.15:41
amullerAbsolutely :)15:41
SwamiI have a hard stop at 7.45, so if you have any other questions please let me know.15:41
*** trinaths has joined #openstack-meeting-alt15:42
ajoI have a question15:42
ajoshould I ask here, or in the doc itself?15:42
SwamiI have very little time here, but go ahead and ask the queston if I cannot answer here I will address it in the document.15:43
*** dkehn_ has joined #openstack-meeting-alt15:43
ajook15:43
ajoI'll write it on the document itself15:44
Swamiok15:44
ajoI actually need time to make the question :)15:44
ajothanks Swami15:44
Swamithanks guys for taking your time.15:44
jamiec_thank you Swami15:44
Swamisee you all next week.15:44
*** dkehn has quit IRC15:45
safchainthanks Swami15:45
Swamibye all15:45
amullerBuhbye15:45
*** phil_h has joined #openstack-meeting-alt15:45
*** jamiec_ has quit IRC15:45
Swami#endmeeting15:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:45
openstackMeeting ended Wed Feb 12 15:45:27 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-02-12-15.02.html15:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-02-12-15.02.txt15:45
openstackLog:            http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-02-12-15.02.log.html15:45
*** dkehn__ has quit IRC15:47
*** dkehn__ has joined #openstack-meeting-alt15:47
*** Swami has quit IRC15:47
*** pdmars_ has joined #openstack-meeting-alt15:47
*** mattgriffin1 has joined #openstack-meeting-alt15:47
*** aignatov_ is now known as aignatov15:47
*** lblanchard has quit IRC15:48
*** dkehn has joined #openstack-meeting-alt15:48
*** sarob has joined #openstack-meeting-alt15:48
*** dukhlov_ has joined #openstack-meeting-alt15:49
*** davidlenwell_ has joined #openstack-meeting-alt15:49
*** lblanchard has joined #openstack-meeting-alt15:50
*** SpamapS_ has joined #openstack-meeting-alt15:51
*** ZangMing1ie has joined #openstack-meeting-alt15:52
*** jmontemayor has joined #openstack-meeting-alt15:52
trinathsHello stackers.. ! Good Morning15:53
*** atiwari_ has joined #openstack-meeting-alt15:53
*** sarob has quit IRC15:53
*** igormarnat_ has joined #openstack-meeting-alt15:54
*** AlanClark has joined #openstack-meeting-alt15:54
*** rcurran has joined #openstack-meeting-alt15:55
*** Barker has quit IRC15:56
*** jgallard has joined #openstack-meeting-alt15:56
*** dkehn_ has quit IRC15:56
*** atiwari has quit IRC15:56
*** pdmars has quit IRC15:56
*** dukhlov has quit IRC15:56
*** jaypipes has quit IRC15:56
*** mattgriffin has quit IRC15:56
*** d0ugal has quit IRC15:56
*** ZangMingJie has quit IRC15:56
*** haleyb has quit IRC15:56
*** SpamapS has quit IRC15:56
*** ogelbukh has quit IRC15:56
*** davidlenwell has quit IRC15:56
*** mordred has quit IRC15:56
*** markwash has joined #openstack-meeting-alt15:57
*** sadasu has joined #openstack-meeting-alt15:58
*** d0ugal has joined #openstack-meeting-alt15:58
*** chandankumar_ has joined #openstack-meeting-alt15:58
*** chandan_kumar has quit IRC15:59
*** BrianB_ has joined #openstack-meeting-alt15:59
*** irenab has joined #openstack-meeting-alt15:59
*** atiwari_ has quit IRC16:00
mesteryHi fellow ML2 coders!16:00
asadoughihi16:00
zzelleHi !16:00
trinathsHi Mestery16:00
*** atiwari has joined #openstack-meeting-alt16:00
banixHi16:00
matrohonhi16:00
rcurranhi16:00
jgallardhi16:00
irenabhi16:00
*** markwash_ has joined #openstack-meeting-alt16:00
mesteryrkukura: here?16:00
*** rkukura has joined #openstack-meeting-alt16:00
mesteryhey rkukura16:01
rkukurahi16:01
yamamoto2hi16:01
mestery#startmeeting networking_ml216:01
trinathshi rkukura16:01
openstackMeeting started Wed Feb 12 16:01:14 2014 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
*** AJaeger has left #openstack-meeting-alt16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: networking_ml2)"16:01
openstackThe meeting name has been set to 'networking_ml2'16:01
shivharishi all16:01
mestery#link https://wiki.openstack.org/wiki/Meetings/ML2 Agenda16:01
*** coolsvap1 has joined #openstack-meeting-alt16:01
*** pcm_ has joined #openstack-meeting-alt16:01
mesteryWe have a very packed agenda today, lets see how far we can make it in an hour. :)16:01
*** markwash has quit IRC16:01
*** markwash_ is now known as markwash16:01
mestery#topic Action Item Review16:01
*** openstack changes topic to "Action Item Review (Meeting topic: networking_ml2)"16:01
rkukuraI just updated agenda with my AI details, so please refresh if you've got it open16:02
mesteryThanks to rkukura for sending email the binding changes.16:02
*** amotoki_ has joined #openstack-meeting-alt16:02
yamamoto2can anyone fix ical feed?  it told me this meeting was 2h earlier.16:02
*** jaypipes has joined #openstack-meeting-alt16:02
*** ogelbukh has joined #openstack-meeting-alt16:02
mesteryyamamoto2: I don't know how that works, maybe asking on #openstack-infra would be a good idea.16:02
mesteryrkukura: Thanks for driving the discussion around the binding changes, that was pretty awesome!16:02
rkukuraI think there is at least one email on the thread that I haven't replied to yet16:03
mesteryYes16:03
*** Sukhdev has joined #openstack-meeting-alt16:03
mesteryBut overall, I think folks are all on the same page now it apepars.16:03
*** sarob has joined #openstack-meeting-alt16:03
rkukuraAre there any reservations regarding moving forward on this in the next couple days?16:03
*** haleyb has joined #openstack-meeting-alt16:03
yamamoto2mestery: ok, thanks16:03
*** coolsvap has quit IRC16:03
rkukuraI've been focusing on my two BPs plus the SR-IOV work, but should start implementing the binding changes this week16:04
mesteryrkukura: I'll give you an AI to move the discussion into a Google Doc, is that ok?16:04
*** mordred has joined #openstack-meeting-alt16:04
mesteryOr is that not necessary?16:04
rkukuramestery: Fine, same as this week's AI16:04
rkukuraI think a doc makes sense for this.16:05
mestery#action rkukura to move port binding discussion into Google Doc16:05
* mestery nods in agreement.16:05
mesteryAny questions on the port binding discussions>?16:05
matrohonno, rkukura, did you talk about my post that you didn't respond?16:05
matrohonyet?16:06
rkukuramatrohon: I mentioned that I still need to respond. Sorry for the delay.16:06
matrohonrkukura : fine, np :)16:06
*** asomya has joined #openstack-meeting-alt16:07
rkukuramatrohon: Will think about that race condition and respond16:07
*** isviridov has left #openstack-meeting-alt16:07
mesteryNext AI review: prioritizing ML2 MechanismDriver BPs.16:07
mesterySo, the feature freeze is this coming Teusday I believe.16:08
*** sarob has quit IRC16:08
mesteryPeople need to propose their MDs by then to have a shot of getting them into Icehouse.16:08
mesteryAnd the 3rd party testing requirement must be met as well.16:08
rkukuraI haven't changed any priorities, but I summarize status of the 12 MD BPs in the agenda.16:08
mesteryThanks rkukura.16:08
rkukuraI'd like to discuss the ones that have question marks at this meeting if we can.16:08
rkukuraNow or later in the agenda?16:09
mesteryPlease do!16:09
mesteryLets do it now.16:09
asadoughimestery: 2/18 is a code deadline, not a bp deadline, right?16:09
*** xuhanp has joined #openstack-meeting-alt16:09
*** jjmb has quit IRC16:09
rkukuraFirst, there are two from bigswitch16:09
amotoki_asadoughi: right. precisely speaking the feature freeze is I-3. Next tuesday is the deadline to propose the code of blueprints.16:09
mesteryI think 2/18 is feature freeze: https://wiki.openstack.org/wiki/Icehouse_Release_Schedule16:09
rkukurahttps://blueprints.launchpad.net/neutron/+spec/bsn-ml2-mechanism-driver - medium, approved, no review, no jenkins?16:09
trinathsregarding FSL-SDN Mechanism Driver BP, I'm working on 3rd party test setup. sent a mail to opestack-infra on gerrit account.. waiting for reply. Done with code improvements. need to commit the code for review.16:09
Sukhdevmestry - we are working on making some enhancements to Arista MD. next week's deadline does not apply to that, right?16:10
rkukurahttps://blueprints.launchpad.net/neutron/+spec/bigswitch-ml2-driver - low, approved, in review, no jenkins?, relationship to bsn-ml2-mechanism-driver?16:10
asadoughimestery: no i think it's what amotoki_ said16:10
trinathsiIs netwt week dead line applicable for our MD.. FSL-SDN16:10
trinaths??16:10
mesteryasadoughi: You are correct, it's feature proposal freeze. If you haven't pushed code for your BP by 2-18, it won't be considered for Icehouse.16:10
rkukuraBoth of these are approved and have reviews linked. Are these two different drivers? And is a jenkins job in the works?16:11
mesterytrinaths: Yes16:11
mesterytrinaths: You need to have pushed code by next Tuesday, it doesn't have to be complete.16:11
*** jjmb has joined #openstack-meeting-alt16:11
trinathsmestery: I have the code in place for review16:11
mesterytrinaths: OK, if it's pushed out, you are ok for FPP on 2-18.16:12
trinathsall the CI's give +1, but jenkins gives -116:12
trinathsso woking on code improvements and 3rd party test setup16:12
*** nosnos has quit IRC16:12
rkukuraSounds like we've covered: https://blueprints.launchpad.net/neutron/+spec/fsl-sdn-os-mech-driver - low, approved, in review, no jenkins?16:12
mesteryOK, thanks trinaths.16:13
rkukuraIts at low, so should be bumped to medium as soon as the jenkins job is in place16:13
trinathsyes rkukura.. I have submitted the code for review and improving the same'16:13
*** xuhanp has quit IRC16:13
rkukuraAnyone from BigSwitch here?16:13
trinathsdoes Jenkins job mean our 3rd party test setup16:13
rkukuratrinaths: yes16:14
*** xuhanp has joined #openstack-meeting-alt16:14
Sukhdevmestery: can you answer my question, please?16:14
mesterySukhdev: Sorry, missed your question due to mispelling my name :P16:14
mesterySo, any code which has a shot at Icehouse needs to be proposed by 2-18.16:14
mesteryIn some form.16:14
mesteryEven WIP.16:14
shivharissukhdev: it is new code, so the deadline does not apply to you16:14
mesteryIf it's not proposed by 2-18, it won't make Icehouse is my understanding.16:14
trinathssince I have jenkins job in pending state, can my driver cross the 218 deadline??16:14
mesteryBug fixes are ok I guess poast that right?16:15
rcurraneven code being pushed up labeled as bugs16:15
mesterybugs are ok past that, sorry for the confusion :)16:15
rkukurabug fixes are OK past this deadline16:15
mesteryI meant BP code.16:15
*** david-lyle has joined #openstack-meeting-alt16:15
* mestery drinks some more coffee.16:15
trinathssince I have jenkins job in pending state, can my driver cross the 2-18 deadline??16:16
shivharismestery: well put. it is BP code.16:16
mesteryThanks shivharis.16:17
rkukuratrinaths: I think you are OK with 2/18 since you have code in review. Just need the jenkins job.16:17
trinathsokay rkukura.. thank you16:17
Sukhdevmestery: so, to be clear - since we are making enhancements to older code, this dead line is not applicable to us. We can submit a bug and code at a later date, right?16:17
*** dhellmann_ is now known as dhellmann16:17
mesterySukhdev: If it's a bug, it's ok past 2-18.16:18
mesteryrkukura: Regarding https://blueprints.launchpad.net/neutron/+spec/ml2-opendaylight-mechanism-driver16:18
mesteryCode is proposed, waiting on Linux Foundation for 3rdp arty testing.16:18
rkukuraSukhdev: The challenge will be to get core reviewers to pay attention later in the cycle16:18
mesteryHopefully next week we get that up and running.16:18
Sukhdevmestery: thanks for clarification16:18
*** gyee has joined #openstack-meeting-alt16:19
mesteryAny other updates for the remaining MDs with question marks?16:19
rkukuraDo all the cisco MDs get tested by the current cisco jenkins job?16:19
HenryGrkukura: that will be the case soon16:20
rkukuraHenryG: OK, thanks16:20
rkukuraAnyone know if there are BigSwitch and/or Huawei jenkins jobs in the works?16:20
trinathsI have seen Bigswitch CI16:21
amotoki_as far as I looked so far, it seems big switch CI works16:21
trinathstesting my code16:21
sadasuregarding https://blueprints.launchpad.net/neutron/+spec/ml2-ucs-manager-mechanism-driver - medium, approved, no review, have jenkins?16:22
sadasuwill have code shortly..before 2/18...jenkins before march 6th16:22
sadasuhave dependency on 3 other BPs16:22
rkukuraI see it on some reviews, so I guess its OK. Seems to be missing from https://review.openstack.org/#/c/72452/16:22
rkukuraok16:23
rkukuraI think we've covered everything we can16:23
rkukurathanks!16:23
mesterythanks rkukura!16:23
mestery#topic ML2 Exceptions to UserSpace16:24
*** openstack changes topic to "ML2 Exceptions to UserSpace (Meeting topic: networking_ml2)"16:24
mesteryThis is in reference to this bug: https://bugs.launchpad.net/neutron/+bug/127373016:24
mesteryThere was some pushback in the review, I think it's worth discussing this here, right rkukura?16:24
rkukurasure16:25
*** ftcjeff has joined #openstack-meeting-alt16:25
*** tanisdl has joined #openstack-meeting-alt16:25
*** tanisdl has quit IRC16:25
*** Leonr has joined #openstack-meeting-alt16:25
*** beagles is now known as beagles_brb16:25
rkukuraOK, hadn't seen latest comments16:26
*** tanisdl has joined #openstack-meeting-alt16:26
*** jjmb has quit IRC16:26
mesterySo, it appears armax was recommending pushing this to Juno, the author of the patch appears to have agreed.16:26
rkukuraI kind of like the idea of storing exceptions in port attributes16:26
shivharisthe push back seem cosmetic at this stage.16:26
shivharisformat of the error message (of course collecting all messages was taken care of by paul ward)16:27
mesteryshivharis: I think comments from armax appear to indicate this should be refactored, right?16:27
rkukuraI think it can be argued that normal users should not see details that expose the internal implementation choices of the cloud16:27
rcurranshivharis, armando's comment was interesting and ... what mestery said16:28
mesteryYes, I agree with what rkukura and armax say there.16:28
*** jjmb has joined #openstack-meeting-alt16:28
rkukuraAre we currently logging the detailed exception?16:28
rkukuraIf so, the admin can track it down if necessary.16:28
rcurranyou'd need to look at all md's to get that answer16:28
amotoki_rkukura: the detail is logged. https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/managers.py#L15916:29
rkukuraShouldn't the MechanismManager be logging the caught exception, then raising the generic one?16:29
shivharismestery: i just read that comment.16:29
*** chadlung has joined #openstack-meeting-alt16:30
rkukuraamotoki_: thanks16:30
banixSomewhat related; not essential but something we need to have at some point: Deals with fails in update-*-postcommit ops  https://review.openstack.org/#/c/69792/16:30
rcurrannote that the managers.py LOG doesn't give you any real depth of what the md exception was16:30
rkukurarcurran: Doesn't LOG.exception(16:31
rkukura                    _("Mechanism driver '%(name)s' failed in %(method)s"),16:31
rkukura                    {'name': driver.name, 'method': method_name}16:31
rkukura                ) give enough depth?16:31
rcurrandoesn't that just give you the method name that caught the excep16:32
rcurranwhat if there are multi exception types on one method16:32
rkukuraI thought LOG.exception logged the actual exception, but could be wrong16:32
shivhariswe seem to all agree that err messaging needs to be enhanced, but it should not hold other things up.16:32
*** trinaths has quit IRC16:32
rkukuraI do like the proposal to but the detailed error info in an admin-only port attribute16:33
amotoki_hopefully adding the arguments of the method to log messages will help admin to debug.16:33
rkukuraamotoki_: Do you mean like everything in the PortContext?16:34
*** colinmcnamara has quit IRC16:34
amotoki_what i mean is adding these infomration to the log message for MD exception.16:34
amotoki_At now i cannot say it applies to all PortContext.16:35
*** vinod has joined #openstack-meeting-alt16:36
rkukuraShould we move this discussion back to the jenkins review, and try to agree on what's needed for icehouse vs. longer term?16:36
mesteryI think so.16:36
* HenryG agrees16:37
amotoki_agree16:37
mesteryOK, moving on in the agenda.16:37
rcurranyeah, i think most engs are leaning towards the longer term approach16:37
* mestery agrees with rcurran.16:37
mestery#topic BPs16:37
*** openstack changes topic to "BPs (Meeting topic: networking_ml2)"16:37
mesteryFirst up: Provider network partial specs: https://wiki.openstack.org/wiki/Provider-network-partial-specs16:37
mesteryAddressed by review https://wiki.openstack.org/wiki/Provider-network-partial-specs16:37
mesteryIs zzelle here?16:38
zzelleyes, here i am !16:38
mesteryzzelle: Hey, howdy!16:38
zzellefine16:38
mesterySo, can you walk us through the high level thinking here?16:38
zzellecurrently, you have tenant network, neutron is in charge of network attributes choice16:39
rkukuramestery: Do you have the link to the actual review?16:39
mesteryrkukura: Sorry, yes: https://review.openstack.org/#/c/71904/16:39
zzelleyou have provider netowkr, neutron admins are in charge of attributes choice16:40
zzellethe aim is to allow to delegate some provider network attributes choice to neutron (when possible)16:40
zzelletypically, you need a vlan network, you do neutron net-create myvlannet --provider:network_type=vlan16:41
zzelleand neutron tries to find in a pool a valid network16:41
*** nacim has quit IRC16:42
zzelleIMHO, the feature could used when deploying networks for baremetal/appliances16:42
matrohonyou want to add a provider pool?16:43
mesterySo, the idea is to not require provider:physical_network and provider:segmentation_id when creating provider networks?16:43
mesteryAnd use the normal tenant pool or some new pool as matrohon says?16:43
zzellematrohon, currently in the review i reuse tenant pools16:43
*** aignatov is now known as aignatov_16:44
zzellebut salv proposes to use a specific one, but it implies to change the datamodel16:44
rkukuraThis kind of touches on an area from the original ML2 proposal that has not (yet) been implemented. The tenant_network_types config is a list, with the intention that TypeDrivers are tried until one can allocate the network. We eventually wanted some generic QoS requirements that users could specify that would influence which TypeDriver was chosen. Basically TypeDrivers would ignore the request if they couldn't16:44
rkukuraprovide the QoS.16:44
*** coolsvap1 has quit IRC16:44
*** amuller has quit IRC16:45
zzelleso my proposal was first to reuse tenant pools, and after allow to specify a provider (only) one16:45
shivharisIdea has definite merit, beginning to think this should be post I3.16:46
zzellerkukura, good to know, the aim of this feature is more pragmatic16:46
zzellei only provide the support for vlan networks because i don't see usecase for other network types16:47
*** colinmcnamara has joined #openstack-meeting-alt16:47
zzellebut supporting other network types is quite simple16:47
rkukuraIs this still admin-only, or would the policy.json have to allow normal users to specify the providernet attrbutes?16:47
*** amytron has joined #openstack-meeting-alt16:48
matrohon+1 for post-I3 with independent pool, to have something clearer in the conf files16:48
zzellestill admin-only because it concerns provider networks16:48
zzellein practice, the feature is implemented through an alternative vlan type driver implementation16:49
mesterySo, is the consensus for this we need the separate pool, which would push this to Juno then?16:50
rkukuraI'm kind of favoring using the existing TypeDrivers and pools, but just making provider network allocation able to use the pool to fill in the unspecified details (vlan)16:50
rkukuraTo me, this is a relaxation of the current provider network restriction, not a new tenant network16:51
amotoki_I think so.16:51
rkukuraPlus, the reservation of the VLAN tag on  a physical_network for this has to make that tag unavailable for normal tenant network allocation16:51
amotoki_i think reusing tenant pools is still useful. For example admin can create a net only with network_type (and phys_net).16:51
mesteryOK, so maybe we approve this one for Icehouse then as-is? Is that what I'm hearing?16:52
mesteryThe use case is compelling I think.16:52
zzellefine :)16:53
rkukuraMaybe a config option for VlanTypeDriver is all that's needed - it would just use the pool when provider:network_type is specified but the other data isn't specified.16:53
zzelledo i provide the support only for vlans ?16:53
mesteryzzelle: That makes sense to me.16:53
mesteryOK, we only have 7 minutes left now.16:54
zzelleor does it makes sense to provide for others network types ? for testing ?16:54
matrohonvxlan ang gre would be nice toot16:54
mesteryLets continue this discussion on the review and ML.16:54
zzelles/provide/porivde it/16:54
rkukuraI don't see a lot of use for provider tunnels as long as the neutron server is doing the endpoint management16:54
shivharisrkukura: are you still suggesting using the existing type driver and folding this functionality in it?16:54
mesteryI wanted to give matrohon 5 minutes or so for his agenda item (we'll have to skip a few other items).16:54
*** nacim has joined #openstack-meeting-alt16:54
matrohonfine16:54
rkukurarkukura: That's what I'd prefer. I'll comment in the review.16:55
mestery#topic Multi-Node Testing16:55
*** openstack changes topic to "Multi-Node Testing (Meeting topic: networking_ml2)"16:55
mesteryWith 5 minutes left, I give the floor to matrohon.16:55
rkukuras/rkukura/shivharis/16:55
*** artom has joined #openstack-meeting-alt16:55
*** msisk has joined #openstack-meeting-alt16:55
matrohonso we would like to enable mutli-node in the gate16:55
matrohonto improve test on ovs/lb/l2-pop MD16:56
*** mugsie has joined #openstack-meeting-alt16:56
mesteryMakes sense to me matrohon16:56
rkukuramatrohon: +116:56
matrohonjgallard, doude and I are working on a gate to manage multi-node with lxc16:57
mesterymatrohon: Sounds very interesting!16:57
amotoki_nice16:57
*** julim has quit IRC16:57
matrohonbut we should first write a BP in openstack-infra16:57
matrohonwe need your help to have infra team focusing on this issue16:58
matrohonthis would be needed for live-migration test too16:58
*** vinod has quit IRC16:59
mesterymatrohon: Agreed.16:59
mesterySo, I would suggest filing the BP and bringing it up at the infra meeting this week (or next if it's already happened this week).16:59
mesteryBut this is a good thing to have, so thanks for taking this on!16:59
matrohonok I tak ethe AI16:59
HenryGmatrohon: the nodes themselves are lxc? Or the instances in the nodes?17:00
amotoki_I am not sure which is better infra or QA.17:00
mestery#action matrohon to file BP for multi-node testing and bring this up in the infra meeting17:00
mesteryAnd with that, we're out of time folks.17:00
asadoughiquick ovs-firewall-driver update: moving bp to juno since dependent ovs release won't be released until march https://blueprints.launchpad.net/neutron/+spec/ovs-firewall-driver17:00
ekarlsomestery: indeed :p17:00
*** coolsvap has joined #openstack-meeting-alt17:00
mesteryThanks for all your efforts on ML2 everyone!17:00
mesteryThanks asadoughi, apologies we ran out of time. :)17:00
mestery#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Feb 12 17:00:38 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-02-12-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-02-12-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-02-12-16.01.log.html17:00
*** xuhanp has quit IRC17:00
*** asomya has quit IRC17:01
shivharisbye17:01
kiall#startmeeting Designate17:01
openstackMeeting started Wed Feb 12 17:01:21 2014 UTC and is due to finish in 60 minutes.  The chair is kiall. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
Sukhdevbye17:01
*** openstack changes topic to " (Meeting topic: Designate)"17:01
openstackThe meeting name has been set to 'designate'17:01
ekarlsoey dns folks17:01
kiallAgenda: https://wiki.openstack.org/wiki/Meetings/Designate17:01
*** sadasu has quit IRC17:01
*** rjrjr_ has joined #openstack-meeting-alt17:01
*** yogesh has joined #openstack-meeting-alt17:01
*** yamamoto2 has quit IRC17:01
kiallWow - IRC lagged like 30 seconds :/17:01
eankutseeankutse17:02
kiallWho's about today?17:02
mugsieo/17:02
kiallbrb - reconnecting!17:02
eankutsek17:02
betsyo/17:02
richmhello17:02
*** jmcbride has joined #openstack-meeting-alt17:02
*** rcurran has quit IRC17:02
* artom is half around.17:02
*** hemanthravi has quit IRC17:03
msiskhere17:03
jmcbridereporting for duty17:03
rjrjr_here17:03
*** rkukura has left #openstack-meeting-alt17:03
kiallOkay - back :)17:03
kiall#topic Review action items from last week17:03
*** openstack changes topic to "Review action items from last week (Meeting topic: Designate)"17:03
kiallFirst up is: vinod update the Getting Involved Section in the documentation for suggested lines of code / commit17:03
eankutsevinod stepped away for 1 sec17:04
kiallI saw from the meeting logs last week that 350 was discussed, seems sane and along the times of what we discussed at the mini-summit..17:04
*** shivharis has quit IRC17:04
kiallAh.. Well, No worries.. Moving on17:04
kiallNext: (all) review/add new blueprints as needed to track smaller work items17:04
kiallI've personally not had a chance to break up any of the blueprints, has anyone else?17:05
eankutsei have not added any blueprints ;-)17:05
mugsienot yet, i have a dreakdown in my head though17:05
kiallI know ekarlso has filed a sub-BP for the pagination stuffs (to be discussed in a few mins)17:05
kiallOkay - Well, Let leave that for next week again17:05
*** yogesh has quit IRC17:05
kiall#action (all) review/add new blueprints as needed to track smaller work items17:06
mugsieproably should be a standing item for a while17:06
kiallmugsie: agreed17:06
eankutseyep17:06
kiallNext: Betsy and Rich to followup on incubation status wrt v2 and mini-dns17:06
betsyI talked with Anne Gentle yesterday17:06
kiall(agenda is pretty full today, hence working fast.. Tell me to slow down if needed ;))17:06
*** vinod has joined #openstack-meeting-alt17:06
betsyI'm in the process of writing up an email about it now17:07
betsyShould go out later today17:07
mugsiecool17:07
kiallI talked with Monty, He's of the opinion that we reapply.. That V2 being in progress won't hurt us, and that MiniDNS is "The only sane way to do it" (or something along those lines)17:07
richmI spoke to Mark (RH TC) - he says that minidns and v2 should not have an impact on incubation, and that in general designate looks good17:07
kiallQuick aside - Alex Barclay from HP, our dev manager, has been asked to start looking into designate incubation.17:08
kiallOkay.. Moving on again real quick :)\17:08
kiallNext: Rich to document the minidns concerns on the wiki spec17:08
betsyAnne pretty much felt the same way17:08
*** dkehn__ is now known as dkehn_17:08
betsyShe did mention that there are already 4 projects ahead of us that have applied for incubation17:09
kiallI'm not sure if ^ got worked out in the post-meeting discussions or not, richm?17:09
*** jgallard has quit IRC17:09
richmkiall: yeah, I still need to do some more homework before I can make intelligent comments about minidns with respect to ipa integration17:09
kiallbetsy: humm - I know theres a "limit" per-cycle .. Let's leave that for next week though, I think we have too full an agenda to get into it today :)17:09
betsyok17:09
richmbut that should not hold up minidns design/progress17:10
kiall#action kiall to review current incubation applications and new "limits" on # per cycle17:10
*** SushilKM has joined #openstack-meeting-alt17:10
kiallrichm: K - Thanks :)17:10
kiall#topic API v2 Pagination17:10
*** lazzzy_ has quit IRC17:10
*** openstack changes topic to "API v2 Pagination (Meeting topic: Designate)"17:10
ekarlsolink: https://blueprints.launchpad.net/designate/+spec/api-v2-pagination17:10
ekarlsoor how to do that ;)17:10
kiallOkay - So, we discussed this to death before, but ekarlso is about to start work on it.. I just wanted to confirm everyone is happy with the proposed method of making this happen (marker/limit vs page/per_page)17:11
mugsieyup17:11
kiall#link https://blueprints.launchpad.net/designate/+spec/storage-pagination-support17:11
ekarlsothere ya go17:11
kiall^ the first "Sub Blueprint" for the storage part, it's not a full spec - since it's already defined in the APIv2 spec17:11
eankutselooks like marker/limit is the practice so far in Openstack17:12
richmI'm all for code sharing/reuse17:12
kiallYea - I asked ekarlso to review all the current APIs, the patterns they use are in the parent / main BP17:12
kiallAnyway - Has anyone got any concerns over following this pattern? Otherwise, we can press on with getting the Storage layer updated with this.17:13
vinodnone from me17:13
richm+117:13
betsyagree17:13
*** jmcbride has quit IRC17:14
kiallOkay - I'll mark the sub-BP as approved, and we'll get it started :17:14
ekarlsook!17:14
kiall#topic Review abstract proposals for Openstack Summit in Atlanta17:14
*** openstack changes topic to "Review abstract proposals for Openstack Summit in Atlanta (Meeting topic: Designate)"17:14
ekarlsosee ya folks for today ;)17:14
*** beagles_brb is now known as beagles17:15
kiallekarlso: hope your not late to pick her up ;) Enjoy!17:15
kiallSo - I've not written an abstract for the talk I was supposed to (sorry!) a mix of time constraints, and I'm not confident there's enough content to have a whole talk on it.17:16
*** jimbobhickville has joined #openstack-meeting-alt17:16
kiallI know Tim and Graham have both written abstracts, do you guys have links handy?17:16
kiallI believe this is tims: https://docs.google.com/a/managedit.ie/document/d/1xIprT3xEzujFPWJhVGnIKRdsB7gkmpgTgo0DfG3Ml4s/edit17:16
*** jjmb has quit IRC17:17
vinodAbstract for the workshop17:17
vinod#link https://wiki.openstack.org/wiki/Designate/Atlanta/Workshop_117:17
kiall#link https://docs.google.com/document/d/1xIprT3xEzujFPWJhVGnIKRdsB7gkmpgTgo0DfG3Ml4s/edit?usp=sharing17:17
kiallmugsie: do you have your link handy?17:17
mugsie#link https://docs.google.com/document/d/1D6FcXMiWMvFTIggWiRu3VajVTnerCFDErTdafcSyxl0/edit?usp=sharing17:17
mugsieWe start at Tims and work our way donw?17:18
mugsiedown*17:18
richmTim's looks good to me - does it overlap with kiall's or mugsie's?17:18
*** jmcbride has joined #openstack-meeting-alt17:18
kiallrichm: mine is non-existant, there's not enough unique content IMHO, and I failed to find enough time to write it.17:18
mugsiea little with mine, but n ot too much17:18
vinodOne overlap is about the Nuetron floating IPs17:19
mugsieyeap. i think it is from 2 different view points though17:19
kiall#link https://etherpad.openstack.org/p/DesignateAustinWorkshop2014-0117:19
kiall^ the original outlines17:19
mugsiekiall: they are on https://wiki.openstack.org/wiki/Designate/Atlanta17:20
mugsie#link https://wiki.openstack.org/wiki/Designate/Atlanta17:20
kiallAh - I missed that page17:20
mugsieso, any changes to tims?17:21
kiallI personally think Both Tim's and Grahams abstracts are good, and that "Talk 3", then one I was supposed to write (sorry :() should have the Mini-DNS / NSUpdate  detail piece merged into Grahams17:21
richmSounds good to me17:22
eankutseMaybe Tim's can be a little more focused17:22
betsyYeah. I think that works17:22
jmcbrideOne question about the abstracts, should we put all of our "wood behind one arrow", e.g. pick one talk?17:22
eankutseit looks pretty broad17:22
mugsiei think seen as there is only 2 being submitted, we should be ok17:23
betsymugsie: agree17:23
jmcbrideWhat about the proposed workshop?17:23
jmcbride2 talks + workshop = 317:23
*** amrith has joined #openstack-meeting-alt17:23
mugsiei think that stands on its own merits17:23
kiallWorkshop proposal looks perfect :)17:23
betsyI think we should still propose that, as it's in a separate bucket, so to speak17:23
kiallYea - I absolutely think the WS is a great idea.17:24
mugsiei see tims abstract as an updated version of what kiall gave in Hong Kong17:24
*** colinmcnamara has quit IRC17:24
eankutsemugsie: so you think the breath of it is fine17:24
eankutse?17:24
eankutses/breath/breadth17:24
mugsiemine is aimed at operators, and your workshop is aimed at anyone who is interested17:24
eankutseok17:25
mugsiei think so...17:25
eankutsek17:25
mugsiebut I am open to correction17:25
eankutsethat sounds good17:25
betsymugsie: I think you're correct17:25
kialleankutse: I think so, 1 general "What we do, general arch, general direction" is useful for giving a good overview.. WIth another being aimed more at people already sold on the concept of designate17:25
eankutsekiall: yes17:26
richmyeah, I think Graham's is more in depth in a few topics which would be of primary interest to operators and developers with an interest in DNS17:26
*** SushilKM has quit IRC17:26
*** NehaV has joined #openstack-meeting-alt17:26
kiallThese are due Friday from memory.. I think we should sync up again tomorrow at 17:00 UTC (same as this meet) for an hour to do any final cleanups, and walk through the submission.17:26
mugsieany changes to the workshop? i think is looks good -  what we are trying to get across17:27
*** akuznetsov has joined #openstack-meeting-alt17:27
kiall(Not intending to stop the discussion now with ^, just getting it out there)17:27
mugsiewell, see if there is any changes people want17:27
kiall1 other point we discussed was giving the talks jointly between the various companies... Who's still up for that?17:27
mugsie+117:28
jmcbride+117:28
richmI am - looks like I am going17:28
kiall(We need presenter names for the submissions)17:28
vinod#agree17:28
jmcbrideWe should try to appoint at least 2 people (one from each organization) to run the talks17:28
eankutseJoint presentations will help incubation, I agree17:28
eankutse+117:29
jmcbrideI would like to participate on talk 1.17:29
betsy+117:29
kiallOkay .. So HP/RAX/RH all up for that? Why don't we let Tim and Graham decide on who they want for their talks? And the WS would be a free-for-all, since hands on deck will be useful17:29
betsykiall: sounds good17:29
richm+1 - I would be happy to do either one17:30
*** demorris has quit IRC17:30
jmcbrideFrom RAX perspective, we don't have approval yet on who all is attending.  So lets plan to put my name on things for now (might change).17:31
jmcbride^ for all the Rackspace participation that is.17:31
*** gokrokve has quit IRC17:32
jmcbrideHow about this: RedHat + RAX for talk 1 (with a cameo from Kiall)17:32
kialljmcbride: any idea when you'll find out?17:32
jmcbridekiall: nope17:32
*** gokrokve has joined #openstack-meeting-alt17:32
kiallOk17:32
jmcbridefor talk two, it would be cool to see Mugsie lead it, with backup from ??17:32
*** BrianB_ has quit IRC17:33
mugsiei am open to suggestions17:33
mugsieI think you could probably get 3 on talk 1 - its more topics, that can be broken down17:33
mugsiemine splits into 2 i think17:33
kialljmcbride: Sounds good for Talk 1.. I'd actually like to take a back-seat and let you guys give the meat of the presentations :)17:33
*** questionmask_ has joined #openstack-meeting-alt17:34
*** igormarnat_ has quit IRC17:34
jmcbridekiall: I think your contributions thus far speak for them selves… Designate is your legacy :)17:34
kiallOne of the reasons I'd like all you guys to be main faces of these ;)17:34
eankutseKiall should do a "live" from-scratch demo :-)17:35
mugsiecould I suggest RAX + richm + (short bit of) kiall for Talk 1?17:35
jmcbrideIt is noble for you to back-seat for a little - I still expect we would reference your prior talks and point accolades where they belong.17:35
kialleankutse: lol .. happy to. I'll get it right this time :P17:35
eankutse:-)17:35
*** pballand has joined #openstack-meeting-alt17:35
jmcbride+1 mugsie on could I suggest RAX + richm + (short bit of) kiall for Talk 1?17:35
richmworks for me17:35
jmcbride+1 on live demo!17:36
kiallSO .. That'd be tim (assuming approval) / richm with a teeny bit from me on T1? I'm happy with that..17:36
*** michael-yu has joined #openstack-meeting-alt17:36
mugsieand then me + 1 RAX  for talk 2?17:36
kiallNames came be changed later for these BTW.. But better to get a general idea before they are submissted17:37
kiallsubmitted*17:37
jmcbridemugsie: yes17:37
*** gokrokve has quit IRC17:37
jmcbrideIs Artom going?17:37
kiallI think he said he wasn't going to be able to.. Not 100% sure.17:37
artomHaha.17:37
artomNo.17:37
jmcbrideWhat about Ron?17:37
*** isviridov1 has joined #openstack-meeting-alt17:37
rjrjr_i'm going to try and be there.17:37
artomUnless I pay for my own stuff, I suppose.17:37
jmcbriderjrjrj_: would you like to work with mugsie on talk 2?17:38
rjrjr_that sounds okay.  let me get an okay to go in the next couple of days.17:38
*** amytron has quit IRC17:38
mugsiecool17:39
kiallOkay .. So lets say, mugsie + rjrjr_ will give T2, failing approval for rjrjr_, mugsie + someone else to be decided later?17:39
mugsiebingo17:39
jmcbrideCool.17:39
kiallartom: too bad :(17:39
*** bdpayne has quit IRC17:39
richmSounds good17:39
*** rossella_s has quit IRC17:39
*** rsblendido has quit IRC17:39
jmcbrideartom: :(17:40
*** beagles has quit IRC17:40
kiallOkay - Let's move on for the moment, and come back tomorrow with the 2 talk proposals tweaked and names on them.. We'll regroup 17:00 UTC tomorrow for an hour to get the final things tweaked and submitted?17:40
*** isviridov1 has quit IRC17:40
kiallThat time work for people/17:40
kiall?*17:40
rjrjr_yes17:41
mugsieyup17:41
*** b3nt_pin has joined #openstack-meeting-alt17:41
*** b3nt_pin is now known as beagles17:41
*** isviridov1 has joined #openstack-meeting-alt17:41
jmcbrideyes17:41
kiall(The WS propose looks good as is, and will probably just have a whole pile of names on it..)17:41
betsyperfect17:41
kiall#action Regroup on Talks+WS at 17:00 UTC tomorrow (Thursday)17:41
kiall#topic import-tlds - right place to put it17:42
*** openstack changes topic to "import-tlds - right place to put it (Meeting topic: Designate)"17:42
*** datsun180b has joined #openstack-meeting-alt17:42
vinodLike we talked yesterday 2 of the issues with the current import-tlds in designate is that (1) you need ssh access to the box where central and designate run (2) The user running import-tlds is not logged17:42
vinodwe talked about having a bulk api for import-tlds to overcome these 2 issues17:42
vinodJoe mentioned that apart from the bulk api, he wanted the current tool as is for (1) initial population of the tlds when a new Designate system is up. (2) an easy way to import TLDs for people trying out Designate.17:42
vinodJoe do you have any other comments to add on this?17:43
kiallI think we discussed this in #openstack-dns yesterday, where we talked about how designate-manage might be the wrong place (for accountability). And came to the conclusion that we leave it there for now, and replace it once we have bulk API actions (which can be applied to the TLD apis too..)17:43
kiallor .. ^ what he said ;)17:43
*** hub_cap has joined #openstack-meeting-alt17:44
kiallI'm thinking everyone is in agreement on those points already?17:44
*** isviridov1 has quit IRC17:44
hub_capkiall: i agree17:44
kiallhub_cap: good for you.17:44
kiall:P17:44
hub_cap:)17:44
mugsiesounds good17:44
*** NehaV1 has joined #openstack-meeting-alt17:44
kiallYou know you just agreed to being our b*tch for the next cycle?17:45
kiall;)17:45
kiallvinod / jmcbride ?17:45
*** jtomasek has quit IRC17:45
*** cweid has joined #openstack-meeting-alt17:45
cweido/17:45
vinodnothing else from me17:45
vinodchecking with Joe17:45
*** jcru has joined #openstack-meeting-alt17:46
*** grapex has joined #openstack-meeting-alt17:46
*** robertmyers has joined #openstack-meeting-alt17:46
*** cp16net has joined #openstack-meeting-alt17:46
*** kalebpomeroy has joined #openstack-meeting-alt17:46
*** zane has joined #openstack-meeting-alt17:46
kiallOkay - Let's assuming it's a "Yes" and come back at the end if it's not :)17:46
vinodJoe agrees too17:46
kiallGetting close on time ;)17:46
kiall#topic API v2 Structured Record Format17:46
*** openstack changes topic to "API v2 Structured Record Format (Meeting topic: Designate)"17:46
jmcbridehub_cap, Betsy is about to get medieval on yah!17:46
kiall#link https://wiki.openstack.org/wiki/Designate/Blueprints/APIv2StructuredData17:47
hub_capjmcbride: :)17:47
kiall#link https://blueprints.launchpad.net/designate/+spec/api-v2-structured-data-format17:47
kiall#link https://review.openstack.org/#/c/71944/ (<-- Very much WIP, started as an experiment)17:47
*** NehaV has quit IRC17:47
betsyI have to admit I haven't had time to review them17:48
eankutseI've been following the WIP. I need to look at the latest updates17:48
kiallThis starts getting the APIv2 structured format in place, and as part of it, happens to make the RRType's into plugins.17:48
*** _nadya_ has joined #openstack-meeting-alt17:48
kialleankutse: there's not too much new, other than the very experimental wire protocol stuff was killed.17:49
eankutsek17:49
kiallI'm just bringing it up as it looks like the pattern I started with will work, so, we should review and see if anyone has concerns.17:49
eankutseso the intent is to make it possible for a given installation to pick and define what RR types they support?17:49
kiall(Not expecting people to have read it yet - just finished writing the BP wiki a hour or wo ago)17:49
*** dprince has quit IRC17:50
*** saju_m has quit IRC17:50
kialleankutse: It's a mix of that, and allowing for both the string and dict representations of each RRType in the API17:50
*** ViswaV has joined #openstack-meeting-alt17:50
kiallImplementing them together was really the "only way", as both really depend on each other.17:50
eankutsethx17:51
*** saju_m has joined #openstack-meeting-alt17:51
kiallAnyway - Just wanted people to know that was there ^, and that it'll be in a decent shape to discuss properly next week.. Please have a look :)17:51
betsykiall: sounds good17:52
richmIs the string type needed for some sort of legacy application?17:52
kiallrichm: the string type is often simpler to copy and paste from various docs etc, and is what some people are familiar with..17:52
richmOk17:52
kiallTake someone setting up Google Apps - The number of SRV recrods to get Google Talk going is huge (about 10)17:53
kiallmost people will have no clue which of the example records map to the actual fields17:53
*** ftcjeff has quit IRC17:53
kiall6 mins left.. Rushing, We'll come back to that next week..17:54
kiall#topic Mini-DNS, what next?17:54
*** openstack changes topic to "Mini-DNS, what next? (Meeting topic: Designate)"17:54
kiallSo - The big-one with like 6 mins to go.. Perfect ;)17:54
betsy:)17:55
artomOverflow into #openstack-dns afterwards?17:55
mugsieI think this falls under the 'big pcture bp' idea17:55
mugsiewhere one person drives it, and has side meeting17:55
kiallI think, the next steps are to take all the discussions we had at the mini-summit, and get the mini-dns BP updated with some implementation details..17:55
*** pdmars_ is now known as pdmars17:55
eankutseyes17:56
mugsie+117:56
*** bdpayne has joined #openstack-meeting-alt17:56
eankutseAnd also with perceived issues17:56
kiall#action kiall to condense mini-summit dicussions into MiniDNS spec17:56
eankutsefor further consideration17:56
mugsie(multiple specs ;))17:56
kiallWe also need to decide on DIY or dnspython .. I'm of the opinion that DIY is going to give us the best results with the least pain ..17:57
kiallmugsie: overall vision spec ;) Implementation will be small pieces :D17:57
artomkiall, why ditch dnspython?17:57
richmcan we salvage it at all?17:57
artomNot to shoehorn it everywhere, but if it can be useful in places...17:57
*** saju_m has quit IRC17:58
eankutseso dnspython + some glue code?17:58
artomeankutse, I think it needs more than glue ;)17:58
kiallNot ditch it per-se, just not necessarily use it for this piece. It's API is quite.. clunky.. and we're going to end up doing mappings all over the place between DNS Python objects, and ours.17:58
eankutseagree17:58
betsyI thought there was some concern about the reliability of dnspython17:58
artomBut it can handle some of the to/from wire stuff.17:58
*** michael-yu has quit IRC17:59
rjrjr_dnspython seems like the correct direction.17:59
betsy1 minute left17:59
*** dmakogon_ is now known as denis_makogon17:59
kiallbetsy: I'm personally pretty sure dnspython will be reliable.. I think it's the awkwardness of the API, combined with it having much more than we need in there, and the conversions between DNS Python objects and our own.. Performance wise, I think we're going to do better DIY18:00
*** mat-lowery has joined #openstack-meeting-alt18:00
kiallLets move to #openstack-dns18:00
kiall#endmeeting18:00
*** saju_m has joined #openstack-meeting-alt18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Wed Feb 12 18:00:16 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
*** glucas has joined #openstack-meeting-alt18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-02-12-17.01.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-02-12-17.01.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-02-12-17.01.log.html18:00
*** rjrjr_ has quit IRC18:00
*** mugsie has left #openstack-meeting-alt18:00
*** SlickNik has joined #openstack-meeting-alt18:01
datsun180boh it's time isn't it18:02
SlickNikyup18:02
*** pleia2 has quit IRC18:02
*** vinod has left #openstack-meeting-alt18:02
denis_makogonyup18:02
denis_makogonhub_cap, ping)18:02
*** imsplitbit has joined #openstack-meeting-alt18:03
*** pcm_ has left #openstack-meeting-alt18:03
imsplitbito/18:03
grapexo/18:03
hub_capheyo sry18:03
denis_makogonlets start, i suppose18:03
SlickNikI suggest we give people a couple of minutes to show up.18:03
kalebpomeroyo/18:03
hub_cap#startmeeting trove18:03
openstackMeeting started Wed Feb 12 18:03:31 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:03
*** chandankumar_ has quit IRC18:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:03
datsun180bhello18:03
*** openstack changes topic to " (Meeting topic: trove)"18:03
openstackThe meeting name has been set to 'trove'18:03
cweido/18:03
robertmyerso/18:03
denis_makogono/18:03
glucaso/18:03
ViswaVo/18:03
hub_caphi all18:03
denis_makogonwhaazzzzaap18:03
hub_cap#topic i3 status18:04
*** openstack changes topic to "i3 status (Meeting topic: trove)"18:04
*** pleia2 has joined #openstack-meeting-alt18:04
kevinconwayo/18:04
mat-loweryo/18:04
abramleyo/18:04
pdmarso/18:04
hub_capso weve had a few more blueprints merge, and weve definitely packed in more items18:04
*** zane has left #openstack-meeting-alt18:04
hub_capso i think we will have to slip our deadline to the end of feb18:04
hub_capits fine for this cycle :)18:04
*** esp has joined #openstack-meeting-alt18:05
hub_capi know rackers will be out of pocket for a good section of the last wk in feb as well18:05
imsplitbit\o/18:05
*** igormarnat_ has joined #openstack-meeting-alt18:05
*** msisk has left #openstack-meeting-alt18:05
imsplitbit /o\18:05
cp16neto_O18:06
imsplitbit))))))18:06
hub_capok my internet is freaking out..18:06
hub_capim back :)18:06
grapex>>:((18:06
hub_capso core needs to step it up and finish reviews18:06
* grapex looks down bashfully18:06
hub_capwe need to focus on the critical gate fixing bug first tho18:06
hub_capand we need to test out the datastore impls18:06
esmuteo/18:07
hub_capthere is only one unassigned bp in i318:07
hub_capand the rest are mostly in code review18:07
hub_capohh link sryy18:07
hub_cap#link launchpad.net/trove/+milestone/icehouse-318:07
hub_capwhoopsies18:07
*** saurabhs has joined #openstack-meeting-alt18:07
vipulo/18:07
juiceo/18:07
hub_capplz update your blueprints today18:07
hub_capif its in 'needs code review', then we know to look at it18:08
hub_capif its in started or not started, then we wont look for it in gerrit18:08
hub_capwe are focusing on this page for i318:08
hub_capthat goes for bugs as well18:08
juiceUpdate? How?18:08
cp16netsounds good18:08
*** artom has left #openstack-meeting-alt18:09
SlickNikjuice: make sure that any patchsets that you have in gerrit are linked with the BP.18:09
SlickNik(in the commit message)18:09
juiceGot it18:09
SlickNikThat way the state of the bp will automatically be changed to "Code Review"18:09
hub_capjuice: make sure the "Delivery" status is set to "Needs Code review"18:09
hub_capSlickNik: that doesnt hapen w bps18:09
hub_capits manual18:09
hub_capunless thats changed18:09
hub_capive manually set mine and many others :)18:10
cp16netnope its manual last i saw18:10
hub_capso go edit your bps!!18:10
*** michael-yu has joined #openstack-meeting-alt18:10
*** jdbarry_ has joined #openstack-meeting-alt18:10
juiceAhhh18:10
juiceThanks hub_cap for clarification18:11
SlickNikhub_cap: interesting; it used to work I think (maybe a bug in CI?). I guess do it manually for now.18:11
juiceI know you guys are swamped - can we talk about process perhaps triage perhaps using priority to help filter out "noise"18:11
hub_capSlickNik: ive never seen it work18:12
hub_capjuice: in gerrit?18:12
juiceIt's like looking at the matrix sometimes watching patches going into irc18:12
hub_capor on this i3 page18:12
juiceIn general18:12
hub_capyea ive told core we need to focus on the i3 page, not the gerrit system for now18:12
hub_capthis should give us _some_ filter to the noise18:13
hub_capat least till we get to the mid cycle sprint18:13
juiceSo if it has been tagged as i3 then it's top priority18:13
vipulis there a similar status for bugs?18:13
hub_capthere we have a session on blueprints and bugs and how we can better our approach18:13
vipulthat we should be focusing on reviewing18:13
hub_capvipul: yes its just below the bps18:13
hub_capon that same page18:13
vipuljust review any marked as in progess?18:13
hub_capbut w bugs18:13
hub_capit just goes to in porgress18:13
hub_cap*progress18:14
imsplitbitlol18:14
SlickNikBugs can still go in after the i3 FF, right?18:14
hub_capyes, after i3 is cut18:14
hub_capthen only backported features that had a FFE (pretty much all of thse in i3 have to be in)18:14
hub_capand yes they have to all be backported :)18:15
hub_capand backported critical bugs18:15
hub_capand then after that we can only merge bugs till its cut18:15
vipulso when after March 6th, we open it up for Juno?18:15
hub_caponce rc1 is cut (usually a wk after or whatever)18:15
hub_capthen juno is open18:15
vipulOk18:15
*** vgnbkr has joined #openstack-meeting-alt18:15
*** cadenzajon has joined #openstack-meeting-alt18:16
hub_capok so any questions about this?18:16
*** michael-yu has quit IRC18:16
*** pballand has quit IRC18:16
hub_capalso, just so everyone knows, blueprints/bugs will eventually go away18:17
hub_capthe storyboard project team had a sprint (ttx i think ran it)18:17
SlickNikwith storyboard?18:17
*** jmcbride has left #openstack-meeting-alt18:17
hub_capand they are working, i think, toward a solution18:17
vipulhooray18:17
hub_capim not sure how active it is18:17
*** julim has joined #openstack-meeting-alt18:17
vipulone of the developers on that sits on this floor18:18
vipulso i think it's on18:18
SlickNikYup, it's definitely on from what I heard last.18:18
hub_cap#link https://github.com/openstack-infra/storyboard18:18
*** gokrokve has joined #openstack-meeting-alt18:19
kevinconwayhub_cap: where are the screenshots?18:20
hub_caplol kevinconway18:20
vipulsomewhat live here http://storyboard.openstack.org/#!/page/about18:20
*** jcru has quit IRC18:20
hub_capoh nice18:20
hub_capya if yall want, we can get in early18:20
*** jcru has joined #openstack-meeting-alt18:21
hub_capbut like right now it has no login18:21
denis_makogonlol18:21
denis_makogonimage-boards18:21
hub_capbut we can help their team w/ filing bugs and such18:22
hub_capand help shape the project18:22
denis_makogontotally anonymous18:22
hub_capor we can keep using blueprints/bugs for now18:22
hub_capno we will wait for auth denis_makogon :)18:22
hub_capok so any more Qs18:23
denis_makogoni like jira18:23
hub_capdenis_makogon: ya they are choosing to build one18:23
hub_capok so moving on18:24
hub_cap#topic Meetup!!18:24
*** openstack changes topic to "Meetup!! (Meeting topic: trove)"18:24
hub_capso i think ill be able to post a link to a hangout for a few days18:24
kevinconwaytinder vs… ?18:24
hub_capim almost odne testing it18:24
hub_cap*done18:24
SlickNiktinder?18:24
hub_capso we will have remote participation18:24
vipulas long as its < 9 remote participants :)18:25
hub_capvipul: im sure it will be :)18:25
hub_capif not we can um.. open 2x laptops18:25
vipulyep, probably not that many that won't be there18:25
vipulso the most important question.. are the parties booked? :)18:26
datsun180bi'm going to introduce myself to all of you as michael basnight18:26
vipulyou should put them on the agenda page18:26
hub_capbut we will do our best to accommodate18:26
hub_capi will vipul , once im sure its working18:26
hub_capill keep it to the channel tho18:26
*** dprince has joined #openstack-meeting-alt18:26
kevinconwayno, i am michael basnight!18:27
hub_capso that we can have active participants instead of any random joe :)18:27
vipuloh no, i meant the party schedule hub_cap18:27
hub_caplies18:27
hub_capvipul: ohhh that schedule18:27
hub_capyea i can do that18:27
*** aignatov_ is now known as aignatov18:27
*** colinmcnamara has joined #openstack-meeting-alt18:27
hub_capwe are going to be PACKED18:27
hub_capits like a 20~25 person room18:27
*** safchain has quit IRC18:27
hub_capwith 30 people in it18:27
hub_capbut i imagine there will be some mingling / side convos18:27
cp16nethopefully there are enough chairs18:28
hub_capso that can happen outside18:28
vipuloh SkySQL came into the office.. they _may_ be coming18:28
hub_capcp16net: u sit too much ;)18:28
grapexI wonder if it will be like twelve angry men. I'll be sure to bring my nice sweating shirt.18:28
vipulthey will confirm today they said18:28
*** harlowja_away is now known as harlowja18:28
hub_capto the meetup? yeesh thatll be painful!18:28
vipulyea.. kinda late to the game18:28
hub_capits already closed / full :D18:28
hub_capill chat w em too if they really need to particiapte18:28
hub_capwow i cant speel18:28
vipuli'll forward them to you.. you can tell them politely18:29
hub_cap:)18:29
SlickNik:)18:29
SlickNikOh, speaking of the sprint. I set up a page for the key-signing party.18:29
SlickNik#link https://wiki.openstack.org/wiki/OpenPGP_Web_of_Trust/Trove_Icehouse_Sprint18:29
hub_capSlickNik: NICE18:30
hub_capwe should put some more verbiage here18:30
hub_capill add to it today18:30
kevinconwayso am i limited to a certain number of keys i can bring?18:30
SlickNikThere's a lot more verbiage regarding it if you click on the linked parent article18:31
SlickNik#link https://wiki.openstack.org/wiki/OpenPGP_Web_of_Trust#Key_Signing_Process18:31
hub_capkevinconway: not really, but only use ones that u actively use18:31
hub_cap*only bring*18:31
hub_capoh icic18:32
hub_capsweet SlickNik18:32
hub_capso lets ad our fingerprints18:32
*** dkehn__ has joined #openstack-meeting-alt18:32
*** davidlenwell_ is now known as davidlenwell18:32
SlickNikYeah, if you guys add them, I'll make sure I have enough sheets printed out for us all with the info on it. Should make life a little easier.18:32
hub_capSlickNik: awesome, i was gonna do that the afternoon of the first day18:33
hub_capif u need help SlickNik and I are avail18:33
juiceI have a script that will speed up this process slightly18:33
SlickNikhub_cap: Sounds good. Let me add that info to the sprint wiki.18:33
juiceWe can verify a master list of keys so that everyone doesn't have to type them in18:33
*** nacim has quit IRC18:34
kevinconwayjuice: i just give it my private key and it does it all right?18:34
hub_capjuice: u will still have to do typing when u get home :)18:34
hub_capso that should be exciting :)18:34
hub_capand we are going to do intros in the beginning too, and id like to make sure we have remote participants for that as well18:35
juiceWell we can put the key id in a file to identify your peers18:35
*** dkehn_ has quit IRC18:35
kevinconwaywe could put all our PKs in a shared drop-box18:35
kevinconwaythat would make it easy18:35
*** dkehn has quit IRC18:35
*** rsblendido has joined #openstack-meeting-alt18:35
*** rossella_s has joined #openstack-meeting-alt18:35
hub_capsounds great kevinconway18:35
*** kmak has quit IRC18:35
SlickNikjuice: you can get the key from the GPG server, you wouldn't have to type it in.18:36
*** aignatov is now known as aignatov_18:36
juiceYou still need to identify the person you are signing18:36
SlickNikjuice: You'd just have to ensure that the signature matches the one that you verified in person18:36
juiceThere are about 20 of us18:36
juiceWe each put out key id in a file and we verify that file18:36
*** Ranjitha has joined #openstack-meeting-alt18:36
juiceThat file is then used by each person to identify their peers keys and sign it18:37
*** dkehn has joined #openstack-meeting-alt18:37
*** dkehn__ is now known as dkehn_18:37
*** _nadya_ has quit IRC18:37
SlickNikjuice: Let's take this offline after the meeting. :)18:37
hub_capoh ok cool :)18:38
kevinconwayso i sign my key and bring it?18:38
kevinconwayi'm so confused18:38
hub_capkevinconway: sign your key with uour key18:38
vipulkevinconway: just bring your laptop :D18:38
hub_capand bring the signature of the fingerprint and sing that with your retina18:38
vipulwe'll figure it out.. you're not the only one confused18:38
hub_capits a lot easier than it seems18:38
hub_caplets bring it back to trove channel and dicuss18:38
hub_capso yes we will havesome cool events sponsored by http://www.tesora.com/, HP and Rax18:39
hub_capin the evenings on wed and thr18:39
*** Sukhdev has quit IRC18:39
hub_capi assume everyone will be going to those :)18:39
hub_capso does anyoen ahve Qs about the meetup at present?18:40
*** jjmb has joined #openstack-meeting-alt18:41
vipulhub_cap: do you have certain goals that should come out of this meetup..18:41
jimbobhickvillefix all the things!18:42
vipuli.e. work items.. clarity.. what should be accomplished18:42
*** arnaud has joined #openstack-meeting-alt18:42
*** arnaud__ has joined #openstack-meeting-alt18:42
hub_capi think that each session woudl have differnt goals18:42
SlickNikkevinconway: (and others who want more info about the keysigning party) Here's some more info you might find useful:  http://www.cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html18:42
hub_capbut id like to, at least, have some concrete design for each thing/feature we are discussing18:42
*** chadlung has quit IRC18:42
*** rsblendido has quit IRC18:42
*** rossella_s has quit IRC18:42
datsun180bkind of looking forward to an event similar to pycon's TiP BoF at our midcycle18:43
hub_capdatsun180b: is that the drunkfest heckle event?18:44
*** ijw has joined #openstack-meeting-alt18:44
datsun180bhub_cap: of course18:44
hub_capand if possibel some hacking done vipul18:44
hub_capif nothign else a really well formed blueprint w/ design, caveats of the feature, etc.. future thoughts18:44
imsplitbitjesus your speeling is horibble18:44
hub_capso that people can hit the road runnin for juno18:44
hub_capit really is18:44
vipulhub_cap: ok cool18:44
hub_capmy fingers dont work at the proper speed18:44
hub_capbut my emacs fu is getting better so i can correct easier18:45
denis_makogoni would try to present my vision of capabilities for meetup, if its possible18:45
hub_capdenis_makogon:18:46
hub_capoopsies18:46
hub_capi think it might make more sense to discuss capabilities over pecan/wsme18:46
hub_capwhat do yall think?18:46
denis_makogonhm, difficalt to say18:46
denis_makogonif that so, we need to migrate to pecan first18:47
*** yogesh has joined #openstack-meeting-alt18:47
denis_makogonit's not the easiest task18:47
vipulis there any discussion on v2 api? because that seems like the logical place to discuss pecan18:47
grapexOne thing I'd like to talk about18:47
grapexis maybe moving files about to make the MVC pattern a bit more defined18:47
grapexas I think it could help us migrate to pecan18:47
denis_makogoni'd left pecan/API v2 for the Summit18:47
*** jprovazn has joined #openstack-meeting-alt18:48
hub_capyea i think thats a fair18:48
kevinconwaywe should discuss the summit at the meetup18:48
juiceOh no not patterns18:49
SlickNikI think we should go with capabilities unless we know there's an imminent effort to move to Pecan / WSME.18:49
juiceHiss18:49
hub_caplol kevinconway juice18:49
hub_capi agree SlickNik18:49
SlickNikI feel like that discussion might be a bit more concrete.18:49
juiceIs pecan a done deal?18:49
hub_capand i do think we should take some time to discuss that grapex , lets do it during a lunch time thing18:49
grapexhub_cap: Cool18:49
hub_capjuice: i believe everyone is moving to it evntually.. maybe im rong18:50
hub_cap*wrong18:50
grapexAlso... let's talk about moving the Reference Guest18:50
hub_capbut i do agree w vipul that itll be a dicussion for when we need v218:50
grapexAnd also my idea to nickname it "Reffy the Reference Guest" and give it a cartoon dog for a mascot18:50
hub_capwe can discuss that a bit during clutsreint too18:50
hub_cap*clustering18:50
*** zzelle has quit IRC18:51
vipulreference guest makes it sound taboo to actually us :p18:51
*** saju_m has quit IRC18:51
vipuluse18:51
*** _nadya_ has joined #openstack-meeting-alt18:52
grapexvipul: But Reffy makes it sound adorable!18:52
grapexvipul: Good point though18:52
kevinconwayi'm going to upload my competing guest called bashy18:52
hub_capok so it seems like we should discuss the sessions a bit18:52
*** chadlung has joined #openstack-meeting-alt18:52
hub_capwe can still move stuff around18:52
kevinconway100% shell commands18:52
hub_capso lets take it offline too18:52
hub_cap /mute kevinconway18:53
hub_cap;)18:53
datsun180bkevinconway: | bc "+1"18:53
hub_capok so this has digressed18:53
hub_cap#topic open dicussion18:53
*** openstack changes topic to "open dicussion (Meeting topic: trove)"18:53
datsun180booh ooh18:53
datsun180bhttps://wiki.openstack.org/wiki/UnifiedSDK18:53
datsun180bdo we have a hat in that ring18:54
hub_capi have not talked w/ anyone from that yet18:54
vipuldatsun180b: is there non-python implementatons in this18:54
datsun180bdon't know about that so much18:55
hub_capis it safe to assume they'll call us?18:55
datsun180bask our ptl18:55
vipulthere is already a python-openstackclient i wonder how this is different18:56
vipulunless they do plan to offer non-python bindings as well18:57
datsun180bseriously though if we don't try to help them i bet they'll try to build one without us and that could be a lot more difficult that it needs to be18:57
hub_capya ill buy in to this when the rest of the "Community" does18:57
SlickNikvipul: I think they're actually talking about the API here (not the consumer)18:57
SlickNikSo you don't have to hit the endpoints directly.18:57
datsun180bright, https://etherpad.openstack.org/p/unified-sdk-notes defines four layers18:58
denis_makogonvipul, there are already non-pythonic binding (java, C#, etc)18:58
kevinconwaydatsun180b: not enough for a good dip though18:58
datsun180bkevinconway: seven or don't bother, right18:58
datsun180bvipul: i think layer four is where the bindings would go18:58
hub_capok so core, REVIEW18:58
hub_capother people, REVIEW18:59
cp16netlol18:59
cp16netok18:59
hub_capuse the i3 page as a guide18:59
cp16netand with that its ova18:59
hub_cap#endmeeting18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:59
openstackMeeting ended Wed Feb 12 18:59:41 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-02-12-18.03.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-02-12-18.03.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-02-12-18.03.log.html18:59
*** asomya has joined #openstack-meeting-alt18:59
*** eankutse has quit IRC18:59
*** glucas has left #openstack-meeting-alt19:00
*** imsplitbit has left #openstack-meeting-alt19:00
*** pcm_ has joined #openstack-meeting-alt19:00
*** SushilKM has joined #openstack-meeting-alt19:00
*** datsun180b has left #openstack-meeting-alt19:00
*** mat-lowery has left #openstack-meeting-alt19:00
*** saju_m has joined #openstack-meeting-alt19:01
*** jimbobhickville has left #openstack-meeting-alt19:01
*** s3wong has joined #openstack-meeting-alt19:02
*** s3wong has quit IRC19:02
*** julienvey_ has quit IRC19:03
*** robertmyers has left #openstack-meeting-alt19:03
*** cp16net has left #openstack-meeting-alt19:04
*** ViswaV has left #openstack-meeting-alt19:05
*** colinmcnamara has quit IRC19:06
*** sarob has joined #openstack-meeting-alt19:07
*** ErikB has quit IRC19:08
*** igormarnat_ has quit IRC19:09
*** pcm_ has left #openstack-meeting-alt19:10
*** balajiiyer has joined #openstack-meeting-alt19:10
*** jcru has left #openstack-meeting-alt19:12
*** sarob has quit IRC19:13
*** asomya has quit IRC19:14
*** balajiiyer1 has joined #openstack-meeting-alt19:16
*** balajiiyer has quit IRC19:16
*** ErikB has joined #openstack-meeting-alt19:18
*** esp has left #openstack-meeting-alt19:19
*** demorris has joined #openstack-meeting-alt19:19
*** IlyaE has quit IRC19:21
*** Barker has joined #openstack-meeting-alt19:23
*** SlickNik has left #openstack-meeting-alt19:28
*** NehaV has joined #openstack-meeting-alt19:30
*** igormarnat_ has joined #openstack-meeting-alt19:30
*** eankutse has joined #openstack-meeting-alt19:30
*** colinmcnamara has joined #openstack-meeting-alt19:32
*** igormarnat_ has quit IRC19:33
*** NehaV1 has quit IRC19:33
*** igormarnat_ has joined #openstack-meeting-alt19:33
*** eankutse has quit IRC19:39
*** krtaylor has quit IRC19:39
*** eankutse has joined #openstack-meeting-alt19:40
*** baoli has quit IRC19:43
*** melodous has left #openstack-meeting-alt19:43
*** aignatov_ is now known as aignatov19:43
*** Ranjitha has quit IRC19:45
*** _nadya_ has quit IRC19:45
*** ErikB has quit IRC19:46
*** ErikB has joined #openstack-meeting-alt19:46
*** saju_m has quit IRC19:48
*** julienvey_ has joined #openstack-meeting-alt19:51
*** julienvey_ has quit IRC19:53
*** balajiiyer1 has left #openstack-meeting-alt19:53
*** colinmcnamara has quit IRC19:53
*** Ranjitha has joined #openstack-meeting-alt19:58
*** ErikB has quit IRC19:59
*** julim has quit IRC19:59
*** Barker has quit IRC20:00
*** Barker has joined #openstack-meeting-alt20:01
*** ijw_ has joined #openstack-meeting-alt20:04
*** ijw has quit IRC20:07
*** ErikB has joined #openstack-meeting-alt20:11
*** igormarnat_ has quit IRC20:12
*** zzelle has joined #openstack-meeting-alt20:22
*** grapex has quit IRC20:25
*** ajo has quit IRC20:32
*** SumitNaiksatam has joined #openstack-meeting-alt20:33
*** IlyaE has joined #openstack-meeting-alt20:34
*** Ranjitha has quit IRC20:39
*** krtaylor has joined #openstack-meeting-alt20:43
*** DinaBelova is now known as DinaBelova_20:47
*** harlowja is now known as harlowja_away20:48
*** ajo has joined #openstack-meeting-alt20:48
*** julim has joined #openstack-meeting-alt20:52
*** ErikB has quit IRC20:53
*** Barker has quit IRC20:53
*** arborism has joined #openstack-meeting-alt20:54
*** boris-42_ has quit IRC20:55
*** dripton has quit IRC20:55
*** arborism is now known as amcnr20:57
*** amcnr is now known as amcrn20:57
*** jdob has quit IRC20:58
*** d0ugal has quit IRC20:58
*** jdob has joined #openstack-meeting-alt20:58
*** dripton has joined #openstack-meeting-alt20:58
*** SpamapS_ is now known as SpamapS20:58
*** SpamapS has quit IRC20:58
*** SpamapS has joined #openstack-meeting-alt20:58
*** hub_cap has left #openstack-meeting-alt20:59
*** boris-42_ has joined #openstack-meeting-alt20:59
*** Barker has joined #openstack-meeting-alt20:59
*** zzelle has left #openstack-meeting-alt21:05
*** betsy has quit IRC21:07
*** jdob has quit IRC21:08
*** jdob has joined #openstack-meeting-alt21:08
*** denis_makogon_ has joined #openstack-meeting-alt21:09
*** baoli has joined #openstack-meeting-alt21:09
*** rohit404 has quit IRC21:12
*** baoli has quit IRC21:12
*** baoli has joined #openstack-meeting-alt21:13
*** derekh has joined #openstack-meeting-alt21:13
*** svetlanad has joined #openstack-meeting-alt21:14
*** sacharya has joined #openstack-meeting-alt21:14
*** sacharya has quit IRC21:14
*** demorris has quit IRC21:15
*** jprovazn has quit IRC21:15
*** ftcjeff has joined #openstack-meeting-alt21:16
*** ErikB has joined #openstack-meeting-alt21:17
*** amrith has quit IRC21:18
*** lblanchard has quit IRC21:22
*** denis_makogon has quit IRC21:22
*** denis_makogon_ is now known as denis_makogon21:22
*** dmakogon_ has joined #openstack-meeting-alt21:22
*** markwash has quit IRC21:25
*** dprince has quit IRC21:26
*** lblanchard has joined #openstack-meeting-alt21:29
*** ajo has quit IRC21:32
*** colinmcnamara has joined #openstack-meeting-alt21:33
*** Ranjitha has joined #openstack-meeting-alt21:34
*** ccrouch has joined #openstack-meeting-alt21:34
*** ccrouch has left #openstack-meeting-alt21:38
*** cweid has quit IRC21:40
*** pballand has joined #openstack-meeting-alt21:41
*** dkehn__ has joined #openstack-meeting-alt21:46
*** lblanchard has quit IRC21:48
*** dkehn__ has quit IRC21:48
*** dkehn__ has joined #openstack-meeting-alt21:48
*** dkehn has quit IRC21:48
*** dkehn_ has quit IRC21:49
*** lblanchard has joined #openstack-meeting-alt21:49
*** dkehn has joined #openstack-meeting-alt21:50
*** bdpayne has quit IRC21:52
*** bdpayne has joined #openstack-meeting-alt21:53
*** ftcjeff has quit IRC21:53
*** ijw_ has quit IRC21:57
*** ijw has joined #openstack-meeting-alt21:57
*** jecarey has quit IRC21:58
*** kevinconway has quit IRC21:59
*** pleia2 has quit IRC22:01
*** ijw has quit IRC22:02
*** pballand has quit IRC22:03
*** ijw has joined #openstack-meeting-alt22:03
*** pdmars has quit IRC22:04
*** pballand has joined #openstack-meeting-alt22:06
*** pleia2 has joined #openstack-meeting-alt22:07
*** gokrokve has quit IRC22:07
*** pballand has quit IRC22:08
*** gokrokve has joined #openstack-meeting-alt22:08
*** kebray_ has joined #openstack-meeting-alt22:08
*** gokrokve_ has joined #openstack-meeting-alt22:08
*** jdbarry_ has quit IRC22:09
*** doug_shelley66 has quit IRC22:09
*** ErikB has quit IRC22:10
*** jjmb has quit IRC22:11
*** jecarey has joined #openstack-meeting-alt22:12
*** gokrokve has quit IRC22:12
*** lblanchard has quit IRC22:20
*** igormarnat_ has joined #openstack-meeting-alt22:25
*** kebray_ has quit IRC22:33
*** Barker has quit IRC22:33
*** Barker has joined #openstack-meeting-alt22:37
*** jdob has quit IRC22:37
*** Barker has quit IRC22:41
*** betsy has joined #openstack-meeting-alt22:43
*** banix has quit IRC22:53
*** harlowja_away is now known as harlowja22:54
*** doug_shelley66 has joined #openstack-meeting-alt22:54
*** baoli has quit IRC22:58
*** SumitNaiksatam has quit IRC23:02
*** aignatov is now known as aignatov_23:03
*** AlanClark has quit IRC23:05
*** rwsu has quit IRC23:06
*** rwsu has joined #openstack-meeting-alt23:08
*** pballand has joined #openstack-meeting-alt23:10
*** yamahata has quit IRC23:11
*** pballand has quit IRC23:11
*** yamahata has joined #openstack-meeting-alt23:15
*** flaper87 is now known as flaper87|afk23:16
*** pballand has joined #openstack-meeting-alt23:16
*** krtaylor has quit IRC23:19
*** tedross has joined #openstack-meeting-alt23:19
*** tedross has left #openstack-meeting-alt23:20
*** pballand has quit IRC23:20
*** NehaV has quit IRC23:21
*** eankutse has quit IRC23:22
*** hdd is now known as hdd_23:28
*** igormarnat_ has quit IRC23:30
*** pballand has joined #openstack-meeting-alt23:35
*** pballand has quit IRC23:37
*** Leonr has quit IRC23:37
*** pballand has joined #openstack-meeting-alt23:40
*** sarob has joined #openstack-meeting-alt23:41
*** yamahata has quit IRC23:42
*** david-lyle has quit IRC23:43
*** derekh has quit IRC23:44
*** jmontemayor has quit IRC23:44
*** jmontemayor has joined #openstack-meeting-alt23:45
*** jcoufal has quit IRC23:46
*** baoli has joined #openstack-meeting-alt23:46
*** pballand has quit IRC23:46
*** jmontemayor has quit IRC23:49
*** esker has quit IRC23:49
*** esker has joined #openstack-meeting-alt23:50
*** drray has joined #openstack-meeting-alt23:50
*** baoli has quit IRC23:51
*** pballand has joined #openstack-meeting-alt23:51
*** drray has left #openstack-meeting-alt23:51
*** RaymondWong has joined #openstack-meeting-alt23:52
*** yogesh has quit IRC23:53
*** esker has quit IRC23:55
*** jmaron has quit IRC23:55
*** denis_makogon has quit IRC23:59

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