| *** yogesh has quit IRC | 00:02 | |
| *** IlyaE has quit IRC | 00:15 | |
| *** michael-yu has quit IRC | 00:15 | |
| *** IlyaE has joined #openstack-meeting-alt | 00:16 | |
| *** matty_dubs is now known as matty_dubs|gone | 00:29 | |
| *** gokrokve has quit IRC | 00:33 | |
| *** gokrokve has joined #openstack-meeting-alt | 00:33 | |
| *** yamahata has quit IRC | 00:34 | |
| *** gokrokve has quit IRC | 00:37 | |
| *** jaypipes has quit IRC | 00:42 | |
| *** enikanorov has quit IRC | 00:47 | |
| *** enikanorov has joined #openstack-meeting-alt | 00:47 | |
| *** enikanorov has quit IRC | 00:49 | |
| *** enikanorov has joined #openstack-meeting-alt | 00:49 | |
| *** markwash has quit IRC | 00:58 | |
| *** banix has joined #openstack-meeting-alt | 01:01 | |
| *** IlyaE has quit IRC | 01:10 | |
| *** alazarev has quit IRC | 01:17 | |
| *** alazarev has joined #openstack-meeting-alt | 01:19 | |
| *** gokrokve has joined #openstack-meeting-alt | 01:20 | |
| *** flaper87 is now known as flaper87|afk | 01:24 | |
| *** sankarshan_away is now known as sankarshan | 01:26 | |
| *** safchain has quit IRC | 01:32 | |
| *** mozawa has joined #openstack-meeting-alt | 01:33 | |
| *** ccrouch has joined #openstack-meeting-alt | 01:35 | |
| *** markwash has joined #openstack-meeting-alt | 01:35 | |
| *** nosnos has joined #openstack-meeting-alt | 01:38 | |
| *** beyounn has quit IRC | 01:39 | |
| *** yamahata has joined #openstack-meeting-alt | 01:41 | |
| *** rakhmerov has quit IRC | 01:43 | |
| *** michael-yu has joined #openstack-meeting-alt | 01:48 | |
| *** beyounn has joined #openstack-meeting-alt | 01:51 | |
| *** yamahata has quit IRC | 01:52 | |
| *** xuhanp_ has joined #openstack-meeting-alt | 01:57 | |
| *** ijw has joined #openstack-meeting-alt | 01:57 | |
| *** harlowja is now known as harlowja_away | 01:58 | |
| *** xuhanp_ has quit IRC | 01:58 | |
| *** yamahata has joined #openstack-meeting-alt | 01:58 | |
| *** alazarev has quit IRC | 02:00 | |
| *** ijw has quit IRC | 02:02 | |
| *** xuhanp_ has joined #openstack-meeting-alt | 02:02 | |
| *** michael-yu has quit IRC | 02:03 | |
| *** xuhanp_ has quit IRC | 02:03 | |
| *** michael-yu has joined #openstack-meeting-alt | 02:04 | |
| *** sacharya has joined #openstack-meeting-alt | 02:07 | |
| *** mozawa has quit IRC | 02:14 | |
| *** sacharya has quit IRC | 02:14 | |
| *** michael-yu has quit IRC | 02:15 | |
| *** mozawa has joined #openstack-meeting-alt | 02:15 | |
| *** gokrokve has quit IRC | 02:17 | |
| *** gokrokve has joined #openstack-meeting-alt | 02:17 | |
| *** xuhanp_ has joined #openstack-meeting-alt | 02:20 | |
| *** amytron has quit IRC | 02:21 | |
| *** gokrokve has quit IRC | 02:21 | |
| *** gokrokve has joined #openstack-meeting-alt | 02:26 | |
| *** harlowja_away is now known as harlowja | 02:27 | |
| *** gokrokve has quit IRC | 02:29 | |
| *** alazarev has joined #openstack-meeting-alt | 02:32 | |
| *** alazarev has quit IRC | 02:36 | |
| *** nati_ueno has quit IRC | 02:40 | |
| *** nati_ueno has joined #openstack-meeting-alt | 02:40 | |
| *** nati_ueno has quit IRC | 02:45 | |
| *** gokrokve has joined #openstack-meeting-alt | 02:47 | |
| *** coolsvap has quit IRC | 02:48 | |
| *** yamahata has quit IRC | 02:50 | |
| *** yamahata has joined #openstack-meeting-alt | 02:51 | |
| *** ashaikh has joined #openstack-meeting-alt | 02:55 | |
| *** amcrn has quit IRC | 02:58 | |
| *** michael-yu has joined #openstack-meeting-alt | 03:01 | |
| *** gokrokve has quit IRC | 03:05 | |
| *** gokrokve has joined #openstack-meeting-alt | 03:05 | |
| *** HenryG has quit IRC | 03:09 | |
| *** gokrokve has quit IRC | 03:10 | |
| *** sbalukoff has quit IRC | 03:13 | |
| *** enikanorov has quit IRC | 03:17 | |
| *** enikanorov__ has joined #openstack-meeting-alt | 03:17 | |
| *** enikanorov has joined #openstack-meeting-alt | 03:17 | |
| *** gokrokve has joined #openstack-meeting-alt | 03:18 | |
| *** michael-yu has quit IRC | 03:19 | |
| *** enikanorov_ has quit IRC | 03:20 | |
| *** sbalukoff has joined #openstack-meeting-alt | 03:26 | |
| *** tomblank has joined #openstack-meeting-alt | 03:28 | |
| *** sbalukoff has quit IRC | 03:31 | |
| *** sacharya has joined #openstack-meeting-alt | 03:33 | |
| *** pballand has joined #openstack-meeting-alt | 03:36 | |
| *** doug_shelley66 has quit IRC | 03:38 | |
| *** dguitarbite has joined #openstack-meeting-alt | 03:40 | |
| *** dguitarbite_ has joined #openstack-meeting-alt | 03:41 | |
| *** coolsvap has joined #openstack-meeting-alt | 03:42 | |
| *** tomblank has quit IRC | 03:43 | |
| *** tomblank has joined #openstack-meeting-alt | 03:44 | |
| *** IlyaE has joined #openstack-meeting-alt | 03:45 | |
| *** sbalukoff has joined #openstack-meeting-alt | 03:48 | |
| *** dguitarbite__ has joined #openstack-meeting-alt | 03:49 | |
| *** dguitarbite has quit IRC | 03:49 | |
| *** dguitarbite_ has quit IRC | 03:49 | |
| *** coolsvap has quit IRC | 03:49 | |
| *** beyounn has quit IRC | 03:52 | |
| *** nati_ueno has joined #openstack-meeting-alt | 03:57 | |
| *** ijw has joined #openstack-meeting-alt | 03:58 | |
| *** harlowja is now known as harlowja_away | 03:59 | |
| *** pballand has quit IRC | 04:02 | |
| *** coolsvap has joined #openstack-meeting-alt | 04:02 | |
| *** coolsvap has quit IRC | 04:03 | |
| *** coolsvap has joined #openstack-meeting-alt | 04:03 | |
| *** ijw has quit IRC | 04:03 | |
| *** ccrouch has quit IRC | 04:07 | |
| *** ccrouch has joined #openstack-meeting-alt | 04:08 | |
| *** rwsu has quit IRC | 04:12 | |
| *** amytron has joined #openstack-meeting-alt | 04:19 | |
| *** pballand has joined #openstack-meeting-alt | 04:28 | |
| *** ccrouch has left #openstack-meeting-alt | 04:30 | |
| *** IlyaE has quit IRC | 04:35 | |
| *** pballand has quit IRC | 04:36 | |
| *** chandankumar has joined #openstack-meeting-alt | 04:40 | |
| *** akuznetsov has joined #openstack-meeting-alt | 04:47 | |
| *** coolsvap has quit IRC | 04:50 | |
| *** banix has quit IRC | 04:52 | |
| *** IlyaE has joined #openstack-meeting-alt | 04:53 | |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 04:56 | |
| *** sarob has joined #openstack-meeting-alt | 04:58 | |
| *** coolsvap has joined #openstack-meeting-alt | 05:08 | |
| *** michael-yu has joined #openstack-meeting-alt | 05:10 | |
| *** IlyaE has quit IRC | 05:13 | |
| *** IlyaE has joined #openstack-meeting-alt | 05:18 | |
| *** SergeyLukjanov has quit IRC | 05:36 | |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 05:44 | |
| *** alazarev has joined #openstack-meeting-alt | 05:47 | |
| *** SergeyLukjanov has quit IRC | 05:49 | |
| *** sarob has quit IRC | 05:50 | |
| *** nati_ueno has quit IRC | 05:50 | |
| *** nati_ueno has joined #openstack-meeting-alt | 05:51 | |
| *** RajeshMohan has quit IRC | 05:54 | |
| *** nati_ueno has quit IRC | 05:56 | |
| *** RajeshMohan has joined #openstack-meeting-alt | 05:56 | |
| *** alazarev has quit IRC | 05:57 | |
| *** IlyaE has quit IRC | 05:58 | |
| *** ijw has joined #openstack-meeting-alt | 05:59 | |
| *** colinmcnamara has joined #openstack-meeting-alt | 06:01 | |
| *** denis_makogon has joined #openstack-meeting-alt | 06:01 | |
| *** ijw has quit IRC | 06:04 | |
| *** alazarev has joined #openstack-meeting-alt | 06:08 | |
| *** sacharya has quit IRC | 06:10 | |
| *** coolsvap has quit IRC | 06:19 | |
| *** alazarev has quit IRC | 06:20 | |
| *** colinmcnamara has quit IRC | 06:24 | |
| *** nadya_ has joined #openstack-meeting-alt | 06:27 | |
| *** gokrokve has quit IRC | 06:27 | |
| *** IlyaE has joined #openstack-meeting-alt | 06:34 | |
| *** nadya_ has quit IRC | 06:37 | |
| *** NikitaKonovalov has joined #openstack-meeting-alt | 06:39 | |
| *** aignatov has joined #openstack-meeting-alt | 06:43 | |
| *** aignatov_ has quit IRC | 06:43 | |
| *** IlyaE has quit IRC | 06:46 | |
| *** aignatov_ has joined #openstack-meeting-alt | 06:50 | |
| *** sarob has joined #openstack-meeting-alt | 06:51 | |
| *** aignatov has quit IRC | 06:51 | |
| *** aignatov_ is now known as aignatov | 06:51 | |
| *** enikanorov__ has quit IRC | 06:52 | |
| *** enikanorov_ has joined #openstack-meeting-alt | 06:52 | |
| *** aignatov_ has joined #openstack-meeting-alt | 06:53 | |
| *** NikitaKonovalov has quit IRC | 06:53 | |
| *** enikanorov__ has joined #openstack-meeting-alt | 06:54 | |
| *** enikanorov_ has quit IRC | 06:54 | |
| *** RajeshMohan has quit IRC | 06:55 | |
| *** sarob has quit IRC | 06:55 | |
| *** RajeshMohan has joined #openstack-meeting-alt | 06:56 | |
| *** NikitaKonovalov has joined #openstack-meeting-alt | 06:57 | |
| *** flaper87|afk is now known as flaper87 | 06:57 | |
| *** alazarev has joined #openstack-meeting-alt | 06:57 | |
| *** boris-42 has quit IRC | 07:02 | |
| *** coolsvap has joined #openstack-meeting-alt | 07:13 | |
| *** arnaud__ has quit IRC | 07:15 | |
| *** arnaud has quit IRC | 07:15 | |
| *** nadya_ has joined #openstack-meeting-alt | 07:17 | |
| *** michael-yu has quit IRC | 07:17 | |
| *** nadya_ has quit IRC | 07:23 | |
| *** NikitaKonovalov has quit IRC | 07:27 | |
| *** ashaikh has quit IRC | 07:30 | |
| *** NikitaKonovalov has joined #openstack-meeting-alt | 07:32 | |
| *** alazarev has quit IRC | 07:35 | |
| *** aignatov has quit IRC | 07:37 | |
| *** ashaikh has joined #openstack-meeting-alt | 07:46 | |
| *** ashaikh has quit IRC | 07:48 | |
| *** denis_makogon has quit IRC | 07:52 | |
| *** sarob has joined #openstack-meeting-alt | 07:52 | |
| *** RajeshMohan has quit IRC | 07:55 | |
| *** sarob has quit IRC | 07:56 | |
| *** SushilKM has joined #openstack-meeting-alt | 07:57 | |
| *** SushilKM has left #openstack-meeting-alt | 07:57 | |
| *** RajeshMohan has joined #openstack-meeting-alt | 07:57 | |
| *** ijw has joined #openstack-meeting-alt | 08:00 | |
| *** aignatov has joined #openstack-meeting-alt | 08:01 | |
| *** ijw has quit IRC | 08:04 | |
| *** boris-42 has joined #openstack-meeting-alt | 08:04 | |
| *** NikitaKonovalov has quit IRC | 08:05 | |
| *** enikanorov has quit IRC | 08:06 | |
| *** NikitaKonovalov has joined #openstack-meeting-alt | 08:10 | |
| *** aignatov has quit IRC | 08:12 | |
| *** jtomasek has joined #openstack-meeting-alt | 08:13 | |
| *** pnavarro has joined #openstack-meeting-alt | 08:28 | |
| *** jtomasek has quit IRC | 08:33 | |
| *** enikanorov has joined #openstack-meeting-alt | 08:35 | |
| *** jtomasek has joined #openstack-meeting-alt | 08:36 | |
| *** chandankumar has quit IRC | 08:41 | |
| *** pnavarro has quit IRC | 08:42 | |
| *** NikitaKonovalov has quit IRC | 08:42 | |
| *** sarob has joined #openstack-meeting-alt | 08:51 | |
| *** pnavarro has joined #openstack-meeting-alt | 08:55 | |
| *** sarob has quit IRC | 08:55 | |
| *** coolsvap has quit IRC | 09:04 | |
| *** sankarshan is now known as sankarshan_away | 09:05 | |
| *** SushilKM has joined #openstack-meeting-alt | 09:06 | |
| *** chandankumar has joined #openstack-meeting-alt | 09:06 | |
| *** jcoufal has joined #openstack-meeting-alt | 09:08 | |
| *** coolsvap has joined #openstack-meeting-alt | 09:09 | |
| *** coolsvap has quit IRC | 09:10 | |
| *** ijw has joined #openstack-meeting-alt | 09:10 | |
| *** ijw has joined #openstack-meeting-alt | 09:10 | |
| *** derekh has joined #openstack-meeting-alt | 09:12 | |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 09:13 | |
| *** aignatov has joined #openstack-meeting-alt | 09:17 | |
| *** coolsvap has joined #openstack-meeting-alt | 09:20 | |
| *** jtomasek has quit IRC | 09:21 | |
| *** jtomasek has joined #openstack-meeting-alt | 09:25 | |
| *** jtomasek has quit IRC | 09:26 | |
| *** jtomasek has joined #openstack-meeting-alt | 09:28 | |
| *** SushilKM has quit IRC | 09:41 | |
| *** SushilKM has joined #openstack-meeting-alt | 09:41 | |
| *** _ruhe is now known as ruhe | 09:46 | |
| *** sarob has joined #openstack-meeting-alt | 09:51 | |
| *** sarob has quit IRC | 09:56 | |
| *** coolsvap has quit IRC | 10:00 | |
| *** coolsvap has joined #openstack-meeting-alt | 10:00 | |
| *** mozawa has quit IRC | 10:04 | |
| *** jtomasek has quit IRC | 10:05 | |
| *** jtomasek has joined #openstack-meeting-alt | 10:07 | |
| *** chandankumar has quit IRC | 10:09 | |
| *** xuhanp_ has quit IRC | 10:12 | |
| *** NikitaKonovalov has joined #openstack-meeting-alt | 10:18 | |
| *** chandankumar has joined #openstack-meeting-alt | 10:25 | |
| *** NikitaKonovalov has quit IRC | 10:35 | |
| *** jtomasek has quit IRC | 10:35 | |
| *** jtomasek has joined #openstack-meeting-alt | 10:36 | |
| *** aignatov has quit IRC | 10:36 | |
| *** ruhe is now known as ruhe_away | 10:37 | |
| *** NikitaKonovalov has joined #openstack-meeting-alt | 10:40 | |
| *** jtomasek has quit IRC | 10:46 | |
| *** jtomasek has joined #openstack-meeting-alt | 10:46 | |
| *** ruhe_away is now known as _ruhe | 10:46 | |
| *** ifarkas has joined #openstack-meeting-alt | 10:49 | |
| *** ifarkas has left #openstack-meeting-alt | 10:49 | |
| *** sarob has joined #openstack-meeting-alt | 10:51 | |
| *** sarob has quit IRC | 10:56 | |
| *** SushilKM has quit IRC | 11:13 | |
| *** jcoufal has quit IRC | 11:15 | |
| *** jtomasek has quit IRC | 11:16 | |
| *** katyafervent has quit IRC | 11:17 | |
| *** katyafervent has joined #openstack-meeting-alt | 11:17 | |
| *** sergmelikyan has quit IRC | 11:17 | |
| *** boris-42_ has joined #openstack-meeting-alt | 11:18 | |
| *** dteselkin has quit IRC | 11:18 | |
| *** dteselkin has joined #openstack-meeting-alt | 11:18 | |
| *** boris-42 has quit IRC | 11:19 | |
| *** boris-42_ is now known as boris-42 | 11:19 | |
| *** aignatov has joined #openstack-meeting-alt | 11:22 | |
| *** jtomasek has joined #openstack-meeting-alt | 11:24 | |
| *** sergmelikyan has joined #openstack-meeting-alt | 11:26 | |
| *** obondarev_ has joined #openstack-meeting-alt | 11:27 | |
| *** pnavarro has quit IRC | 11:50 | |
| *** sarob has joined #openstack-meeting-alt | 11:51 | |
| *** sarob_ has joined #openstack-meeting-alt | 11:53 | |
| *** sarob has quit IRC | 11:56 | |
| *** sarob_ has quit IRC | 11:58 | |
| *** mozawa has joined #openstack-meeting-alt | 11:58 | |
| *** coolsvap has quit IRC | 12:03 | |
| *** jcoufal has joined #openstack-meeting-alt | 12:03 | |
| *** yamahata has quit IRC | 12:06 | |
| *** pnavarro__ has joined #openstack-meeting-alt | 12:24 | |
| *** esker has joined #openstack-meeting-alt | 12:34 | |
| *** esker has quit IRC | 12:34 | |
| *** obondarev_ has quit IRC | 12:35 | |
| *** SushilKM has joined #openstack-meeting-alt | 12:36 | |
| *** obondarev_ has joined #openstack-meeting-alt | 12:39 | |
| *** SushilKM has quit IRC | 12:40 | |
| *** NikitaKonovalov has quit IRC | 12:44 | |
| ijw | Any PCI guys hanging out in advance, there's a document up - albeit very late - please read: https://docs.google.com/document/d/1vadqmurlnlvZ5bv3BlUbFeXRS_wh-dsgi5plSjimWjU | 12:49 |
|---|---|---|
| *** julim has joined #openstack-meeting-alt | 12:49 | |
| *** baoli has joined #openstack-meeting-alt | 12:49 | |
| *** sarob has joined #openstack-meeting-alt | 12:51 | |
| *** obondarev_ has quit IRC | 12:52 | |
| *** nati_ueno has joined #openstack-meeting-alt | 12:52 | |
| *** sarob has quit IRC | 12:56 | |
| *** nati_ueno has quit IRC | 12:57 | |
| *** irenab__ has joined #openstack-meeting-alt | 12:59 | |
| *** nosnos has quit IRC | 12:59 | |
| *** heyongli has joined #openstack-meeting-alt | 12:59 | |
| *** irenab__ is now known as irenab | 12:59 | |
| baoli | #startmeeting PCI Passthrough | 13:00 |
| openstack | Meeting started Wed Jan 15 13:00:01 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:00 |
| *** openstack changes topic to " (Meeting topic: PCI Passthrough)" | 13:00 | |
| openstack | The meeting name has been set to 'pci_passthrough' | 13:00 |
| baoli | Hi | 13:00 |
| ijw | o/ | 13:00 |
| heyongli | hi | 13:00 |
| irenab | hi | 13:00 |
| *** sadasu has joined #openstack-meeting-alt | 13:01 | |
| ijw | https://docs.google.com/document/d/1vadqmurlnlvZ5bv3BlUbFeXRS_wh-dsgi5plSjimWjU is the very late proposal from yesterday, plus a list of use cases at the bottom based on what we were talking about. I've not tried to justify the propsal against the use cases in there. | 13:01 |
| *** yjiang51 has joined #openstack-meeting-alt | 13:01 | |
| baoli | Let's continue with yesterday's use case, then. | 13:01 |
| baoli | a couple of minutes to look at your proposal | 13:02 |
| ijw | It's supposed to be what I was describing from yesterday, though it wouldn't kill me to add a diagram... | 13:03 |
| ijw | I think the questions to answer are: | 13:03 |
| ijw | - do we have more use cases than I've described (or are there some to go away) | 13:04 |
| ijw | - is the proposal going to satisfy them | 13:04 |
| *** pdmars has joined #openstack-meeting-alt | 13:04 | |
| ijw | - is there something else we could do that would be simpler / do better? | 13:04 |
| baoli | ijw, not much time to digest it. But I see it's very complicated. | 13:05 |
| baoli | First of all, about the attribute. | 13:05 |
| irenab | may I raise concern not related to the document? | 13:06 |
| ijw | Go ahead | 13:06 |
| irenab | We have about 2 month window to push something to icehouse and get accepted. What are we going to do? | 13:07 |
| *** BrianB_ has joined #openstack-meeting-alt | 13:07 | |
| irenab | Do we want full list of use cases with all apis or we can define basic cases and have e2e flow? | 13:07 |
| irenab | My feeling we discuss alot, but progress is very slow ... | 13:08 |
| ijw | The proposal on the table basically uses code we almost have ready - heyongli has a patch out there that's about 90% of the backend work. This can be implemented in stages, so if we can't write a flavor API in that time we would write a config item to do the same job temporarily. The question is whether we're going to accept it or argue about it again | 13:08 |
| heyongli | ijw, agree. | 13:08 |
| baoli | irena, I agree with you | 13:08 |
| ijw | baoli has the code for the --nic changes we need, you're on the PCI backend, the whole thing is pretty close if we'd just sit down and write it rather than debating | 13:09 |
| ijw | s/PCI/NIC/ | 13:09 |
| yjiang51 | irenab: in nova side, we have to wait for nova core to approve BPs and code, so on nova side, it's important to get john's ack. | 13:09 |
| baoli | ijw, what are the use cases that can't be taken care of by pci group but the pci flavor | 13:09 |
| *** banix has joined #openstack-meeting-alt | 13:09 | |
| irenab | so there is also baoli's code that require blueprint approval | 13:10 |
| yjiang51 | baoli: or, vice versa, any usage case can;t be taken care of pci flavor but pci group? | 13:10 |
| irenab | and neutron work that I need translate to blueprints | 13:10 |
| baoli | Can you answer my question first? | 13:11 |
| ijw | You can't easily do the online modifications - some of it is making things easier - 6-a-2 is a bugger in PCI group - some is because administrators might well have reasons to change the content of a flavor as in 6-b, 6-c | 13:11 |
| heyongli | irenab, i remember john said he like to review and approve if we done the work split | 13:11 |
| ijw | PCI group is mainly much simpler to implement. *Much* simpler. But a lot of flexibility goes away with it | 13:11 |
| baoli | How do you justify the flexibility | 13:12 |
| baoli | How do you define attributes | 13:12 |
| ijw | People asked for it. John and Alan K from Ericsson | 13:12 |
| ijw | Attribute definition is in there. | 13:12 |
| *** jtomasek has quit IRC | 13:12 | |
| ijw | In the backend aribtrary attributes are allowed for extra_info, there's no restriction. In the scheduler there's a list of available attrs. | 13:13 |
| baoli | ijw, I don't see any difference between the pci flaovr and the pci group | 13:13 |
| baoli | if you do that | 13:13 |
| irenab | heyongli: its good, need also neutron blueprints approved by Mark | 13:13 |
| ijw | baoli: if you do what? | 13:13 |
| baoli | If you define the extra attributes | 13:13 |
| baoli | Do we agree that PCI address and host can't be used in the pci flavor? | 13:14 |
| irenab | baoli: agree | 13:14 |
| ijw | The distinction is there's a mapping from combinations of attribute (which, absolutely, you can select to be 'pci_group' and you get the groups proposal, that's intentional) to flavor. That extra level of mapping gives you the requested API flexibility. | 13:14 |
| ijw | baoli: I'm happy to accept that | 13:15 |
| baoli | I think that we've talked about that you can add "meta-data" to a pci group down the road if needed | 13:15 |
| heyongli | baoli, pci flavor can contian you group as a extra attr, but not push the group to the domain factor of design | 13:15 |
| baoli | the meta-data is the attribute | 13:15 |
| ijw | baoli: The difference between this and group is tiny in that respect but still significant. | 13:15 |
| *** jtomasek has joined #openstack-meeting-alt | 13:16 | |
| baoli | Are you seeing that a pci group is a special attribute? | 13:16 |
| baoli | saying | 13:16 |
| ijw | In group, you put all devices into a group, presumably on the backend, and add attributes to the group. In this, you put attributes on the device and then group by the attribute (which conveniently can reuse the matching code we already have) | 13:16 |
| ijw | That gets you two things. Firstly, if you're of a mind like yjiang5 or heyongli, you can still define your flavors in terms of device and vendor ID and it will work | 13:16 |
| ijw | Second, you can put attributes on individual devices which don't apply to every device in the group, which we need | 13:17 |
| irenab | ijw: I think group is more compute specific definition (only name is global) and flavor is global, correct? | 13:18 |
| ijw | No extra_info attributes are special, I'm saying, but if you want to call one pci_group and use it to group your devices that is entirely your choice and you get pretty much the grouping behaviour you're looking for (while not denying other people the behaviour they'd like) | 13:18 |
| baoli | ijw, do you still need to add the attributes in the pci whitelist that is defined on the compute nodes? | 13:18 |
| ijw | yup | 13:18 |
| baoli | in that case, how could it be flexible? | 13:18 |
| ijw | baoli: yup. irenab: I think group was always driven from the compute node, it doesn't really work well done at the frontend | 13:18 |
| baoli | you can modify your flavor whatever way you want, but do you have to modify your compute node? | 13:19 |
| baoli | I see complexity, but not flexibitlity | 13:19 |
| ijw | It's inflexible in that you're configuring values there (though if you really want to change them you change them and restart, and as I said yesterday those values are largely dependent on the physical configuration and situation of the server so config's a good place for them) | 13:19 |
| baoli | And what benefits we get from it? | 13:19 |
| ijw | It's flexible in that you get to interpret those values in light of how you define the flavors, which means that you can change your mind with an API call later | 13:19 |
| baoli | Can you give an example on that? | 13:20 |
| ijw | You are defining the wiring of the host at the backend, where it belongs, and the features offered to the user in the front end. I would say that's why it works well | 13:20 |
| baoli | give an example | 13:20 |
| baoli | not something in general | 13:20 |
| ijw | So if I want to say 'this PCI device is attached to switch X port 4' then I would do that on the compute node, because that's very situational and nothing will apply globally to all compute nodes. | 13:21 |
| *** _ruhe is now known as ruhe | 13:21 | |
| ijw | If I want to say 'Cisco and Intel NICs are sold as the flavor 'fastnic'' then I do that at the front end, because that's a user facing decision and one I might want to re-evaluate in the future | 13:21 |
| irenab | ijw: if you need to specify compute node network interface, like neutron (eth2), not phy switch? | 13:22 |
| *** tomblank has quit IRC | 13:22 | |
| ijw | If I'm running a small cloud and the flavor functionality's too much bother then I can define a flavor as 'flavor X is all devices in group X' and label up my devices at the backend. If I don't like grouping at all, I can say 'flavor X is all Intel NICs (by device ID)' and that works too. ANd your specific case of 'all SRIOV NICs should be used for passthrough works as well, bonus | 13:23 |
| baoli | group? | 13:23 |
| ijw | irenab: if we want to do that we're going to have to add the network interface as a device property. | 13:23 |
| *** SushilKM has joined #openstack-meeting-alt | 13:23 | |
| ijw | You can't do it now, and that's basically why. That information's pretty easy to discover though so that wouldn't be a huge change. | 13:23 |
| baoli | group X | 13:23 |
| *** SushilKM has left #openstack-meeting-alt | 13:24 | |
| baoli | group X ? | 13:24 |
| irenab | ijw: not sure, this is the network interface of PF | 13:24 |
| baoli | ijw, you can do it with PCI group as well | 13:24 |
| ijw | irenab: I think it's the same - either we autodiscover it and it's a device property or we have to manually find it and it's extra_info | 13:24 |
| ijw | baoli: yes, indeed - my point is that this does precisely what groups do and a number of other things besides | 13:24 |
| baoli | a number of other things besides? | 13:25 |
| ijw | 'group' here would be an extra_info property that I just happened to call 'group' | 13:25 |
| irenab | ijw: you need it to choose the device that is child of this PF | 13:25 |
| ijw | irenab: we'll have to add that to the pci_device then. | 13:25 |
| ijw | Different problem but not too hard to solve | 13:25 |
| yjiang51 | irenab: for SR-IOV device, we record the corresponding PF even in current code already | 13:25 |
| ijw | Ah, ok | 13:25 |
| *** dprince has joined #openstack-meeting-alt | 13:25 | |
| *** rbrady has left #openstack-meeting-alt | 13:25 | |
| yjiang51 | irenab: as a PCI device property. | 13:25 |
| heyongli | irenab: define PF as a attr to the flavor in ijw's propsal you get you want | 13:26 |
| irenab | yjiang51: its fine, but I think we need some correlation with it in pci flavor | 13:26 |
| baoli | So you are saying that we need a special attribute, somethign called say sriov_group? | 13:26 |
| ijw | baoli: As I said before, and as the document says, groups can offer you backend configuration (if you set them up in config) or front-end flexibility (if you have an API to set them up) but they can't offer you both at the same time. | 13:26 |
| ijw | irenab: how'd you mean? | 13:26 |
| irenab | heyongly: cannot, since PF can differ between compute nodes | 13:26 |
| heyongli | irenab: then you can add attr 'connective' and define it diffrently in every host, and based it's pf | 13:27 |
| yjiang51 | irenab: so you mean you want to select SR-IOV device based on the attribute of the corresponding PF device's atrribute? | 13:27 |
| irenab | ijw: I want to specify flavor that suites connectivy case | 13:27 |
| ijw | irenab: that's where you'd use the backend tagging, I think: match PF = whatever, add an attr (not quite sure what you have in mind for there though) | 13:27 |
| ijw | match PF = whatever, add provider_network='outside' or something | 13:28 |
| baoli | guys, are we trying to define something so complicated when you have a simple solution to solve all the practical cases we have right now? | 13:28 |
| heyongli | ijw: +1 | 13:28 |
| *** jtomasek has quit IRC | 13:28 | |
| irenab | ijw:as an analogy, for neutron agent you specify where provider net is going outside (i.e. eth2) | 13:28 |
| heyongli | baoli: this is not complicated for me to implement it | 13:28 |
| ijw | baoli: because we don't. Whatever you think groups are they are either defined in backend config or via a frontend API | 13:28 |
| *** jtomasek has joined #openstack-meeting-alt | 13:29 | |
| baoli | you need all the APIs to support attributes, wouldn't you? | 13:29 |
| ijw | baoli: and yes, I don't think this *is* complicated, it's designed to build largely on what we have | 13:29 |
| ijw | baoli: no, you wouldn't - there's no API there that takes a bare attribute | 13:29 |
| ijw | Flavors take a matching expression, PCI flavors in flavors and NICs don't use attributes at all, only flavor names | 13:29 |
| baoli | how do you report stats? | 13:30 |
| *** jdob has joined #openstack-meeting-alt | 13:30 | |
| ijw | There's no use case for stats there - if you have one in mind we can add it and then I'll answer that question, because I can think of a number of stats that might be useful. | 13:30 |
| irenab | ijw: whre do you define the (match PF = whatever, add provider_network='outside' )? Flavor? | 13:31 |
| ijw | Also, I would question whether stats are a priority for Icehouse | 13:31 |
| baoli | ijw, how do you do scheduling? | 13:31 |
| yjiang51 | irenab: I remember even in neutron, you have to specifify provider net through config, right? then in nova , you have to specify the provider net by providing that attribute in compute node, and then create flavor for it. | 13:31 |
| ijw | irenab: I define that in the compute node config (because the compute node's physical connectivity determines the attribute value to use) then I make my flavor up by matching on e.provider_network | 13:32 |
| *** eharney has joined #openstack-meeting-alt | 13:32 | |
| irenab | yjiang51: so need to associate list of devices on compute node with this provider net | 13:32 |
| irenab | ijw: can you, amybe later write down how the configs will look like? | 13:32 |
| ijw | baoli: same as I described to you before - pci_stats buckets can be created by doing a SELECT COUNT(*) GROUP BY attr, attr, attr - giving you a limited number of buckets - then each PCI flavor corresponds to a number of buckets and you find a set of choices out of those buckets with availability that satisfies your demand | 13:33 |
| ijw | irenab: it's in there in the abstract, but there's no worked example - 'pci_information' | 13:33 |
| baoli | ok, a compute node can use whatever attributes in your mind to tag an entry? | 13:33 |
| *** julienvey_ has joined #openstack-meeting-alt | 13:33 | |
| ijw | yup | 13:33 |
| yjiang51 | irenab: just wonderinfgif nova have mechanism to get that network provider automatically? | 13:34 |
| irenab | ijw: I feel I need to take it a little bit more down to earth (example) | 13:34 |
| heyongli | as a implement, stats can be calculated based on flavor property | 13:34 |
| ijw | yjiang51: a provider network here is 'an external network attached to a compute node port' so it's not usually automatically discoverable - it's also a Neutron concept so Nova would find it hard to get hold of, I think | 13:35 |
| *** coolsvap has joined #openstack-meeting-alt | 13:35 | |
| irenab | yjiang51: not as far as I know, nova gets it by at allocate_network stage | 13:35 |
| ijw | heyongli: indeed, which is pretty much the same as 'group' that I was using in the worked examples above | 13:35 |
| *** dguitarbite__ has quit IRC | 13:35 | |
| ijw | irenab: the thing I don't like about that pci_information at the moment is it's ugly, but I think you'd end up with | 13:35 |
| *** xuhanp has joined #openstack-meeting-alt | 13:36 | |
| heyongli | ijw: yeah, anyway stats and scheduler is fine for this design | 13:36 |
| ijw | pci_information=[{pf => '0000:01:01.00'}, { provider_network => 'outside'}] | 13:36 |
| heyongli | ijw: +2 for this | 13:36 |
| BrianB_ | irenab: do you have a simple use case, seems it;s a good time to move on and see what and e2e solution will look like. | 13:36 |
| *** safchain has joined #openstack-meeting-alt | 13:37 | |
| irenab | BrianB: the use case is very simple. each compute node is connected to provider network via specific netowrk interface (SRIOV NIC) | 13:37 |
| ijw | I think that PCI information thing wants a DSL really but for the minute we'll stick with JSON or Python | 13:37 |
| *** boris-42_ has joined #openstack-meeting-alt | 13:38 | |
| baoli | ijw, we need to support live migration soon. | 13:38 |
| baoli | how do you take care of this? | 13:38 |
| *** enikanorov_ has joined #openstack-meeting-alt | 13:38 | |
| heyongli | baoli: live migration or migration ? | 13:39 |
| baoli | live migration | 13:39 |
| baoli | in the case of SRIOV | 13:39 |
| *** boris-42 has quit IRC | 13:39 | |
| *** boris-42_ is now known as boris-42 | 13:40 | |
| irenab | baoli: we need libvirt network then | 13:40 |
| baoli | yes | 13:40 |
| yjiang51 | irenab: how that provider network for each SRIOV NIC defined in neutron? In config file or automaticaly? If in config file, will it be ok to define same in nova also, as ijw suggested? (i.e. for all devices with PF=xxx, define provider_network as xxx) | 13:40 |
| *** enikanorov has quit IRC | 13:41 | |
| irenab | yjiang51: I think it will be sufficient | 13:41 |
| baoli | Also, does the compute node knows about flavor? | 13:41 |
| yjiang51 | irenab: great. | 13:42 |
| *** pdmars has quit IRC | 13:42 | |
| heyongli | irenab: cool | 13:42 |
| irenab | yjiang51: but it should be considered by scheduler too | 13:42 |
| *** sankarshan_away is now known as sankarshan | 13:42 | |
| ijw | baoli: live migration shouldn't be a problem from a scheduling perspective, but very very few devices support it and none that I know of with KVM support | 13:43 |
| ijw | baoli: irenab's macvtap connection will work though. | 13:43 |
| heyongli | irenab: sure and ijw and I give a rough description above | 13:43 |
| yjiang51 | irenab: yes, if we have attribute 'provider_network' defined as attributes supported for pci_stat/pci_flavor. | 13:43 |
| ijw | yjiang51: provider nets are in a config file | 13:44 |
| ijw | baoli: compute nodes don't know about flavors, only the results of flavor, I *think* | 13:44 |
| heyongli | ijw: i also think so | 13:45 |
| ijw | As in, by that point you have the allocations in terms of RAM, CPU and now PCI device, so you don't need the connection back to flavor | 13:45 |
| baoli | Again, we come back to the question on how pci stats are reported by the compute nodes? | 13:45 |
| heyongli | baoli: i think compute node report the stats by the avaliable pci flavor property | 13:45 |
| *** yamahata has joined #openstack-meeting-alt | 13:46 | |
| ijw | baoli: right now, they're reported individually by device. This allows you to report them grouped by the grouping attributes, but since we'd quite like something to work I was expecting to do what we do now - report all the PCI devices and group in the DB - and move to a different form later. Also, since the scheduler's being hacked to bits right now there's not much point in prejudging the results of that | 13:46 |
| *** nati_ueno has joined #openstack-meeting-alt | 13:46 | |
| heyongli | pci_flavor_attrs=attr,attr,attr on control node | 13:46 |
| baoli | ijw, no. they are not individually reported | 13:46 |
| ijw | OK, so why do we have a pci_devices table? | 13:47 |
| ijw | How does it get filled? | 13:47 |
| yjiang51 | irenab: so are you ok with ijw's suggestion ? | 13:47 |
| baoli | ijw, they maintain status information | 13:48 |
| irenab | yjiang51: seems Ok, need to go over the details to validate | 13:48 |
| heyongli | ijw: not so far, but can report by pci_flavor attrs, even directly from dB is so good( we try to push it in crrrent implementation at havana) | 13:48 |
| baoli | do you reporte by flavor? or do you report by individual attribute? | 13:49 |
| ijw | You'll notice I didn't say, because it's not terribly important | 13:49 |
| baoli | ijw, it's important | 13:49 |
| ijw | From a use case perspective it isn't - it doesn't matter which you're doing because it doesn't affect behaviour | 13:50 |
| ijw | As long as you get it right... | 13:50 |
| baoli | You can't conceptually bring up something without considering its complexity and pacticality | 13:50 |
| baoli | practicality | 13:50 |
| ijw | Actually, I considered it both ways | 13:51 |
| heyongli | baoli: not by flavor, can based on pci_flavor_attrs, it's practically , or just by DB | 13:51 |
| baoli | what do you mean by based on pci_flavor_attrs? | 13:51 |
| baoli | or just by DB? | 13:51 |
| *** nati_ueno has quit IRC | 13:51 | |
| *** sarob has joined #openstack-meeting-alt | 13:51 | |
| ijw | So, if you group on the control node, then that's a lot of network traffic, but otherwise fine. If you group on the compute node, the only thing you need to consider is that you need the grouping attributes available, so the one visible change would be whether you need that list of grouping attrs on the compute node (presumably in its configuration) | 13:51 |
| *** nati_ueno has joined #openstack-meeting-alt | 13:52 | |
| ijw | I would prefer that we group on the compute node, but I was also assuming that we could do it with control node grouping and fix the problem later, particularly since there's no user visible change there | 13:52 |
| *** coolsvap is now known as coolsvap_away | 13:52 | |
| baoli | ok, you define an API for PCI flaovr, you need to notify all the compute nodes about that, so that they can do grouping properly, is that what you say? | 13:52 |
| ijw | Personally I would choose - for now - the way that's closest to what we already have in the code to minimise work | 13:52 |
| ijw | No. | 13:53 |
| baoli | ok, then how | 13:53 |
| ijw | Not at all. | 13:53 |
| ijw | Flavors are defined in terms of a list of attributes that can be used in the flavor. | 13:53 |
| ijw | Which you define in config. | 13:53 |
| ijw | Setting aside for a moment where that config is. | 13:53 |
| *** banix has quit IRC | 13:53 | |
| *** pdmars has joined #openstack-meeting-alt | 13:53 | |
| ijw | So, your pci_stats table has a row for every value combination of those attributes. | 13:53 |
| ijw | Now, if you're grouping on compute nodes, you don't need to tell them about flavor. They do need to know what the grouping attributes are. Either they have the same attrs in their config and confirm early on that they have the right set or they have to ask the conrol node for the list. Either works. | 13:54 |
| baoli | you are saying the compute node will report every device? | 13:54 |
| ijw | No, I'm not. | 13:54 |
| yjiang51 | baoli: I'm not sure if anyone else have more questions. If you have more, possibly you can discuss with ijw after the meeting since you are on the same company and easy to discuss? | 13:56 |
| baoli | remember that pci flavors are defined on the controller node which has an arbitrary criteria | 13:56 |
| *** sarob has quit IRC | 13:56 | |
| irenab | ijw: baoli: do we want to set a plan/dates we want to progress? | 13:56 |
| baoli | yjang51, sure | 13:57 |
| irenab | baoli: any chance you can share git fork with you changes? | 13:57 |
| baoli | irena, I wish we can | 13:57 |
| *** safchain has joined #openstack-meeting-alt | 13:57 | |
| baoli | Irena, I can provide a full patch if you need one | 13:58 |
| ijw | baoli: flavors are defined on a controller node but the criteria are not arbitrary, they're validated against the list of grouping attributes. | 13:58 |
| *** rossella_s has joined #openstack-meeting-alt | 13:58 | |
| *** rsblendido has joined #openstack-meeting-alt | 13:58 | |
| ijw | And I think that that is what you're missing | 13:58 |
| baoli | ijw, let's discuss it offline then | 13:59 |
| baoli | #endmeeting | 13:59 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 13:59 | |
| irenab | baloi: thanks, will appritiate it. I am going to discuss with rkukura (ML2 neutron core) the neutron part and want to start coding next week. | 13:59 |
| openstack | Meeting ended Wed Jan 15 13:59:15 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:59 |
| *** lblanchard has joined #openstack-meeting-alt | 13:59 | |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-15-13.00.html | 13:59 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-15-13.00.txt | 13:59 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-15-13.00.log.html | 13:59 |
| *** Sam-I-Am has joined #openstack-meeting-alt | 13:59 | |
| irenab | baoli: tomorrow same time same place? | 13:59 |
| *** dianefleming has joined #openstack-meeting-alt | 13:59 | |
| * annegentle waves | 14:00 | |
| dianefleming | on the ocean | 14:00 |
| annegentle | hee | 14:00 |
| annegentle | ok let's get goin | 14:01 |
| annegentle | #startmeeting DocTeamMeeting | 14:01 |
| openstack | Meeting started Wed Jan 15 14:01:41 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:01 |
| *** openstack changes topic to " (Meeting topic: DocTeamMeeting)" | 14:01 | |
| openstack | The meeting name has been set to 'docteammeeting' | 14:01 |
| annegentle | boy I haven't done these in a while | 14:01 |
| annegentle | Ok, action items from last meeting | 14:01 |
| annegentle | #topic Action items from last meeting | 14:02 |
| EmilienM | good morning :) | 14:02 |
| *** openstack changes topic to "Action items from last meeting (Meeting topic: DocTeamMeeting)" | 14:02 | |
| annegentle | I have one where slong was going to add WIP info to the HowTo page | 14:02 |
| *** ruhe is now known as ruhe_away | 14:02 | |
| *** jjmb1 has quit IRC | 14:03 | |
| annegentle | Just did a search for "work in progress" and wip on that page but dont' see it | 14:03 |
| annegentle | But also chandankumar has it as an action item from the previous meeting | 14:03 |
| annegentle | I'd just do it but I'm not sure what people are seeking | 14:04 |
| annegentle | Leaving it as a continuing action item | 14:04 |
| annegentle | #action slong or chandankumar add WIP info to https://wiki.openstack.org/wiki/Documentation/HowTo#Reviewing_Documentation | 14:04 |
| annegentle | #topic Report from Doc Bug Day Dec 20 | 14:05 |
| *** openstack changes topic to "Report from Doc Bug Day Dec 20 (Meeting topic: DocTeamMeeting)" | 14:05 | |
| dianefleming | yeah, i'm not sure what that's about | 14:05 |
| annegentle | We definitely closed at least 80 bugs, that is FAN TAS TIC. | 14:05 |
| Sam-I-Am | it was euphoric :) | 14:05 |
| *** yamahata has quit IRC | 14:05 | |
| annegentle | hee | 14:05 |
| annegentle | I also had the API site repo added to http://status.openstack.org/bugday/ | 14:05 |
| dianefleming | api site doesn't look so good! | 14:06 |
| dianefleming | ha | 14:06 |
| annegentle | heh, well that shows 24 hours | 14:07 |
| annegentle | so it only looked good the day of :) | 14:07 |
| *** AJaeger has joined #openstack-meeting-alt | 14:07 | |
| dianefleming | i see | 14:07 |
| AJaeger | Hi, sorry being late ;( | 14:07 |
| Sam-I-Am | hi andreas | 14:08 |
| *** _tmckay has quit IRC | 14:08 | |
| annegentle | morning! | 14:08 |
| Sam-I-Am | AJaeger: dont worry, you got all the action items we already covered :) | 14:08 |
| AJaeger | Yeah! | 14:08 |
| annegentle | there was a nice graph in activity.openstack.org I was going to post but I can't seem to find it, sigh | 14:08 |
| * AJaeger plans to ignore them ;) | 14:08 | |
| annegentle | it was a great effort | 14:09 |
| AJaeger | it was indeed! | 14:09 |
| *** heyongli has quit IRC | 14:09 | |
| annegentle | the graph is like this one http://activity.openstack.org/data/display/OPNSTK2/All+Projects+Activity+Dashboard+-+Last+30+Days?src=contextnavchildmode but individual repos could be tracked. anywho. | 14:10 |
| *** ruhe_away is now known as ruhe | 14:10 | |
| annegentle | #topic Schedule January Monthly Google Hangout | 14:10 |
| *** openstack changes topic to "Schedule January Monthly Google Hangout (Meeting topic: DocTeamMeeting)" | 14:10 | |
| annegentle | Looking at next Monday evening my time, 1/20 | 14:10 |
| AJaeger | annegentle, http://activity.openstack.org/data/plugins/zfacts/renderpage.action?template=Project%20Activity&title=openstack-manuals%20-%20Activity%20Dashboard&repositoryID=SCM%2Crepository55dc94de-6597-4420-8e0b-09963819aade ? | 14:10 |
| annegentle | AJaeger: YES! Thank you! | 14:10 |
| annegentle | #link http://bit.ly/1b32JM0 | 14:11 |
| annegentle | Look at that spike! Woo. | 14:11 |
| Sam-I-Am | annegentle: that time works for me. who all can join this? | 14:11 |
| annegentle | Sam-I-Am: anyone can join, first 10 get mics | 14:12 |
| Sam-I-Am | will it go on youtube? | 14:12 |
| annegentle | I don't think there's another way with Google Hangouts, 10's the limit | 14:12 |
| annegentle | yeah we will do "On Air" again which will go on youtube | 14:12 |
| *** matty_dubs|gone is now known as matty_dubs | 14:12 | |
| AJaeger | I'm 6 (or 7) hours ahead of you - what time do you plan for the meeting? | 14:12 |
| *** matty_dubs has left #openstack-meeting-alt | 14:12 | |
| annegentle | There's also going to be a webinar the first week of Feb with QA, Docs, and Infra | 14:12 |
| annegentle | AJaeger: I'm thinking of evening but you had to miss the last one because of that, right? We can try another time | 14:13 |
| *** carlp has joined #openstack-meeting-alt | 14:13 | |
| *** nermina has joined #openstack-meeting-alt | 14:13 | |
| AJaeger | Whatever works for most... | 14:13 |
| annegentle | Let's play with http://www.timeanddate.com/worldclock/meeting.html | 14:13 |
| annegentle | AJaeger: I wouldn't mind playing with times a bit | 14:13 |
| dianefleming | what is the purpose of the google hangout? | 14:13 |
| nermina | sorry i'm late | 14:13 |
| *** NickChase has joined #openstack-meeting-alt | 14:13 | |
| Sam-I-Am | hi nermina | 14:14 |
| nermina | hi sam-i-am | 14:14 |
| NickChase | Hey, sorry I'm late, I was in the wrong room. :) | 14:14 |
| carlp | morning Sam-I-Am | 14:14 |
| annegentle | dianefleming: Lana likes them for getting to know each other and real-time chat | 14:14 |
| annegentle | heh sorry NickChase we lost that one | 14:14 |
| annegentle | though no one's in there, oh well | 14:14 |
| NickChase | that's life | 14:14 |
| annegentle | all, do you think there's still value in the video chat? | 14:14 |
| NickChase | as long as we know where to go. :) | 14:14 |
| dianefleming | okay - sounds good - | 14:15 |
| NickChase | I'm torn; it's nice to see face to face, but it's nice to have everything recorded, too. | 14:15 |
| annegentle | You know, looking at http://www.timeanddate.com/worldclock/meetingtime.html?iso=20140115&p1=24&p2=37&p3=57 it seems like your 9:00PM might work AJaeger | 14:15 |
| NickChase | or do you mean the sunday night thing in addition to this meeting? | 14:15 |
| AJaeger | annashen, my 9pm works for sure | 14:16 |
| Sam-I-Am | carlp: hi | 14:16 |
| annegentle | NickChase: two meetings: google hangout and a webinar | 14:16 |
| NickChase | right, sorry,it's early. :) | 14:16 |
| Sam-I-Am | i did my first hangout with tom the other day and it was really cool to see face to face | 14:16 |
| annegentle | NickChase: no worries :) | 14:16 |
| Sam-I-Am | so i think there's value in it | 14:16 |
| annegentle | Sam-I-Am: yeah I like it too | 14:16 |
| Sam-I-Am | plus it is recorded... | 14:16 |
| AJaeger | Yeah, there's value to it | 14:16 |
| annegentle | ok cool | 14:17 |
| NickChase | I do think it's good to see face to face, but let's keep it out of the weekends. :) | 14:17 |
| annegentle | I'll set it up, this time more geared towards EU | 14:17 |
| annegentle | NickChase: sure makes sense :) | 14:17 |
| annegentle | For next week, look for an invite like last time | 14:17 |
| annegentle | #topic Webinar in February (date tbd) to update Icehouse doc/qa/infra plans | 14:17 |
| *** openstack changes topic to "Webinar in February (date tbd) to update Icehouse doc/qa/infra plans (Meeting topic: DocTeamMeeting)" | 14:17 | |
| annegentle | Just letting you all know I'm prepping a 10-slide deck to share with anyone who comes to the webinar | 14:17 |
| NickChase | I don't mind working at 9 or 10 pm, but weekends are off limits unless I want a divorce. | 14:17 |
| annegentle | these are the same format as for all the PTLs | 14:18 |
| annegentle | NickChase: heh, no one wants that! | 14:18 |
| NickChase | which webinar? | 14:18 |
| *** yjiang51 has quit IRC | 14:18 | |
| dianefleming | not exactly true (divorce) | 14:18 |
| annegentle | NickChase: a to be scheduled one similar to the ones the other PTLs have done | 14:18 |
| NickChase | ah! | 14:18 |
| NickChase | great! | 14:18 |
| annegentle | this summit, HK, they stopped having the PTLs give an update for plans during the Summit itself | 14:18 |
| annegentle | so, they're doing webinars after | 14:18 |
| annegentle | this is docs turn | 14:18 |
| annegentle | should be first week of Feb. | 14:18 |
| annegentle | #topic Done with backports to stable/havana | 14:19 |
| *** openstack changes topic to "Done with backports to stable/havana (Meeting topic: DocTeamMeeting)" | 14:19 | |
| annegentle | ding, dong, done! | 14:19 |
| AJaeger | annegentle, is there anything you need help with for the webinar? | 14:19 |
| * Sam-I-Am faints | 14:19 | |
| annegentle | AJaeger: any comments there, are there more lurking? | 14:19 |
| annegentle | Really the cutoff was going to be last week but without a meeting we didn't finalize | 14:19 |
| AJaeger | I always thing we're done - and in comes another one... | 14:19 |
| AJaeger | ;( | 14:19 |
| Sam-I-Am | annegentle: i think we can kill major updates... but there might be serious things that come up | 14:19 |
| annegentle | AJaeger: If you could put your wanted bullets into an email for the slides that would be awesome, how much focus on tools, also? | 14:20 |
| chandankumar | hey here i came, i just woke up! | 14:20 |
| annegentle | chandankumar: welcome! | 14:20 |
| AJaeger | Yeah, there might be serious ones, let's backport those - but not anything minor or cosmetic | 14:20 |
| NickChase | good morning, chandankumar. :) | 14:20 |
| AJaeger | annegentle, ok, can provide a slide or two for the tools as input | 14:20 |
| annegentle | chandankumar: say, can you update the https://wiki.openstack.org/wiki/Documentation/HowTo page with WIP info? We weren't sure what needs to be added and it was an action item for you | 14:20 |
| annegentle | AJaeger: perfect, thanks | 14:20 |
| annegentle | AJaeger: any generic slide template (open office is fine too) would do | 14:21 |
| * Sam-I-Am needed to WIP something the other day :/ | 14:21 | |
| chandankumar | NickChase, good morning | 14:21 |
| chandankumar | annegentle, doing that right now ! | 14:21 |
| AJaeger | annegentle, ok | 14:21 |
| annegentle | Sam-I-Am: you can tell we are pretty easy to negotiate with | 14:21 |
| annegentle | but what I want to communicate is that we're done backporting | 14:21 |
| Sam-I-Am | yup | 14:21 |
| annegentle | cool | 14:22 |
| Sam-I-Am | the good news is we're leaving the havana install docs in a pretty good state | 14:22 |
| annegentle | Sam-I-Am: they are really well off, and commenters are helping each other every day, which is so awesome | 14:22 |
| annegentle | So let's get to it, | 14:22 |
| annegentle | #topic Discuss any installation guide changes for Icehouse | 14:22 |
| *** openstack changes topic to "Discuss any installation guide changes for Icehouse (Meeting topic: DocTeamMeeting)" | 14:22 | |
| annegentle | At the Summit, we said we would continue in Icehouse with the manual install. That seems to be all fine and good. | 14:23 |
| NickChase | Networking guide? | 14:23 |
| AJaeger | Just one wish: Rewrite Networking chapter ;) | 14:23 |
| Sam-I-Am | AJaeger: yeah, about that... | 14:23 |
| NickChase | :) | 14:23 |
| Sam-I-Am | but first | 14:23 |
| annegentle | One thing we are waiting for is a decision at i2 about whether we continue to doc nova-network with neutron | 14:23 |
| Sam-I-Am | i'm installing icehouse now using trunk and so far so good | 14:23 |
| NickChase | +1 on continuing manual install | 14:23 |
| chandankumar | +1 | 14:23 |
| Sam-I-Am | +1 | 14:23 |
| AJaeger | annegentle, nova-network will be in Icehouse AFAIU the discussion | 14:24 |
| annegentle | AJaeger: tha'ts my sense of it too | 14:24 |
| NickChase | From the development discussions around nova-network and making changes to it it looks like it will still be there | 14:24 |
| AJaeger | http://lists.openstack.org/pipermail/openstack-dev/2014-January/024175.html | 14:24 |
| annegentle | NickChase: agreed | 14:24 |
| NickChase | they are talking about using nova-conductor, etc. | 14:24 |
| NickChase | so I think it needs to stay | 14:24 |
| Sam-I-Am | yeah i dont think nova-net is going anywhere just yetr | 14:24 |
| annegentle | So, I like that we get to maintain the current guide as-is | 14:24 |
| Sam-I-Am | neutron still lacks a few important features | 14:25 |
| annegentle | I know Sam-I-Am has good ideas for neutron too | 14:25 |
| annegentle | and we'll ahve to add ml2 plugin explanations | 14:25 |
| Sam-I-Am | annegentle: well, sort of. i'm wondering about putting all the networking stuff together | 14:25 |
| carlp | Sam-I-Am: This is true, but the goal is to have all those features in place for Icehouse | 14:25 |
| annegentle | Sam-I-Am: tell me more, separate guide kinda stuff? | 14:25 |
| AJaeger | ML2 instead of current OVS I guess | 14:25 |
| Sam-I-Am | it seems to me that the installation guide is where a lot of people end up first | 14:25 |
| annegentle | I still like the choose your own adventure | 14:25 |
| carlp | The goal is to officially deprecate nova-network in Icehouse if possible | 14:25 |
| NickChase | choose-your-own-adventure is of course best -- for some things. | 14:26 |
| AJaeger | And change the neutron chapter so that there is no jumping around - and the Use-cases section follows the rest | 14:26 |
| annegentle | carlp: yes, and the sprint is still going on I think, so hence my lack of a final statement :) | 14:26 |
| Sam-I-Am | so i'm thinking about offering configurations for a couple of common configurations... one or two with neutron, and of course nova if it still exists | 14:26 |
| annegentle | Sam-I-Am: ok, that sounds ok (common configs for neutron) | 14:27 |
| Sam-I-Am | for more advanced stuff, maybe consult the book on networking? | 14:27 |
| Sam-I-Am | just dont want to overload people | 14:27 |
| NickChase | Let's talk about "the book on networking". Right now there's a book for the networking API, and a monster chapter on networking in the Cloud Admin Guide. | 14:27 |
| annegentle | Sam-I-Am: yeah that's what I'm thinking too, but we didn't really plan for a networking guide in icehouse and haven't found a real owner. Doesn't mean it's unpossible but we've got cleanup of cloud admin guide so I'm hesitant | 14:27 |
| NickChase | Even so, it doesn't provide a lot of the context and concepts it needs. | 14:28 |
| annegentle | NickChase: yeah talk more to it. | 14:28 |
| NickChase | I would very much like to see us do the following: | 14:28 |
| *** jecarey has joined #openstack-meeting-alt | 14:28 | |
| NickChase | 1) Take the networking chapter and break it out into a stand-alone book that is ALSO included (via includes) in the Cloud Admin Guide. | 14:28 |
| NickChase | 2) Add contextual/introductory material that gives people the background that they need on important concepts. | 14:29 |
| NickChase | 3) Reorganize if necessary. (Not sure how much re-org will be necessary. Maybe not that much.) | 14:29 |
| NickChase | I went through the structure in prep for this meeting | 14:29 |
| annegentle | NickChase: do you have a writer in mind for 2)? | 14:29 |
| Sam-I-Am | so... remove the networking chapter from the install guide? | 14:29 |
| dianefleming | is networking a post-installation (configuration) task? is that why you want it in the cloud admin guide? | 14:30 |
| annegentle | NickChase: yeah I think that's fine maybe woudl question the duplication though | 14:30 |
| annegentle | dianefleming: networking decisions do have to be made upfront, but people are not making good ones due to not having the background in networking | 14:30 |
| NickChase | anngentle: I think that me and nermina can handle #2. | 14:30 |
| NickChase | unless someone else wants it | 14:30 |
| NickChase | Lorin will probably also be willing to assist in some way | 14:30 |
| nermina | he definitely was offering | 14:31 |
| annegentle | NickChase: Yeah I don't think there's infighting for it :) Lorin started a new job and won't be working on OpenStack but might be swayed to help | 14:31 |
| NickChase | re: the duplication, I'm not sure that there IS duplication. we're just making it possible to get networking on its own if you want it | 14:31 |
| annegentle | Sam-I-Am: how interested are you in the networking guide? esp. the educational portions | 14:31 |
| NickChase | we can make that clear right in the book | 14:31 |
| carlp | I would dis-agree that networking is a post installation task. Choosing neutron vs nova-networking is definitely an installation task. Having a very basic neutron config also makes sense as an install task, and then go into more advanced stuff later | 14:31 |
| Sam-I-Am | NickChase: i was also hoping we would offer 2 arch options in the install guide... one for nova-net, one for neutron... then make sure we create detailed diagrams and background into for them... and follow the theme throughout the guide | 14:31 |
| Sam-I-Am | carlp: particularly because your arch changes (e.g, addition of network node) | 14:32 |
| annegentle | Thing is, I would prefer we point to other places to learn the complexities of networking rather than write our own... is there a way to keep the context in OpenStack or is the topic not like that? | 14:32 |
| NickChase | carlp: I agree with you. But you can't put all of that in the install guide. :) | 14:32 |
| annegentle | Sam-I-Am: now you're talkin' == sold! | 14:32 |
| nermina | i bet you that training guides have a lot of conceptual stuff | 14:32 |
| NickChase | Sam-I-Am: Agreed, though I wouldn't kill ourselves on nova-net | 14:32 |
| Sam-I-Am | NickChase: it seems to me that most people using the install guide just want it Just Work when they're done... THEN go figure out why it works :) | 14:32 |
| annegentle | carlp: yeah the install guide needs to do one happy path then get people to really think about their deployment | 14:32 |
| NickChase | annegentle: I agree to a certain extent, but it's difficult to find resources that really provide the context that we need. I'm all for linking out for topics where it exists, though. | 14:33 |
| carlp | annegentle: agreed, when I said "more advanced stuff later" that doesn't need to be in the install guide | 14:33 |
| Sam-I-Am | thats why i was thinking about covering a couple of options well... provide a little background, but make them work. then provide the details and advanced config in a book somewhere... or some existing place | 14:33 |
| Sam-I-Am | annegentle: yeah i can help with any networking stuff we put elsewhere | 14:33 |
| nermina | sam-i-am, have you seen the cloud admin guide's networking chapter? | 14:34 |
| NickChase | Sam-I-Am: I agree that they want to just make it work. But usually, it won't, and there's no simple answer as to why. | 14:34 |
| Sam-I-Am | nermina: briefly | 14:34 |
| annegentle | NickChase: +1 | 14:34 |
| *** SergeyLukjanov_ has joined #openstack-meeting-alt | 14:34 | |
| nermina | i just recently moved quite a few config scenarios to it | 14:34 |
| NickChase | The reality is that networking in OpenStack is just really, really complicated, and there's no getting around it. | 14:34 |
| Sam-I-Am | NickChase: i think if we document the prereqs first, its not bad. i'm seeing plenty of people have success with neutron using the guide now. | 14:34 |
| NickChase | Sam-I-Am: that's great, and I agree. | 14:35 |
| carlp | NickChase: using the ML2 driver with OVS and GRE "just works" in most cases these days. It's much simpler to debug over the older OVS code and is the forward path for the Neutron team anyway | 14:35 |
| annegentle | NickChase: Sam-I-Am: can you also engage the neutron team after this week? They have a doc lead, Edgar Magana | 14:35 |
| Sam-I-Am | annegentle: sure | 14:35 |
| annegentle | I mentioned it at their team meeting week before last and they are interested | 14:35 |
| NickChase | carlp: that's great. I'd love your feedback on this. | 14:35 |
| annegentle | carlp: that is GREAT to hear | 14:35 |
| chandankumar | annegentle, while writing networking book, these two videos might be helpful http://www.youtube.com/watch?v=afImoFeuDnY and http://www.youtube.com/watch?v=wEa_8ESxPAY | 14:36 |
| annegentle | carlp: makes the doc job that much easier | 14:36 |
| NickChase | that's fantastic, Anne. I'd LOVE to get with Edgar. | 14:36 |
| NickChase | Contact info? | 14:36 |
| Sam-I-Am | one thing i think we can all agree on... lets break up the huge xml file covering neutron into per-node files like we do everywhere else :) | 14:36 |
| annegentle | carlp: how much interest do you have in the networking vs install guide? | 14:36 |
| annegentle | carlp: cuz you can probably tell we want to write this with a few people | 14:36 |
| NickChase | Sam-I-Am: +` | 14:36 |
| Sam-I-Am | that thing is a pain in the butt to edit | 14:36 |
| NickChase | +1, even .:) | 14:36 |
| annegentle | Sam-I-Am: oh good thinking | 14:36 |
| Sam-I-Am | more like +100000 :) | 14:36 |
| NickChase | very much so. | 14:36 |
| annegentle | Sam-I-Am: make it so! | 14:36 |
| Sam-I-Am | then we need to figure out if we keep the format supporting multiple plug-ins | 14:37 |
| annegentle | I really appreciate how much thought people are putting into thise | 14:37 |
| annegentle | these | 14:37 |
| Sam-I-Am | or just go with ML2 and make the guide less jumpy | 14:37 |
| NickChase | Sam-I-Am: Maybe we can get together later to discuss details? | 14:37 |
| annegentle | Sam-I-Am: yeah, might play with it some and see what reviewers say, but I think ML2's the way | 14:37 |
| Sam-I-Am | NickChase: yes! ... and carlp | 14:37 |
| carlp | annegentle: I have a lot of interest in making the documentation for networking better everywhere. Most of the customers I deal with are using blogs because the docs are not up-to-date enough or simply don't cover enough and it gets complicated because the blogs people find are not clear on what versions of OpenStack or the code, etc | 14:38 |
| *** tomblank has joined #openstack-meeting-alt | 14:38 | |
| Sam-I-Am | annegentle: i might need some help breaking the big file up | 14:38 |
| nermina | i can help, sam-i-am | 14:38 |
| NickChase | Sam-I-Am: I will help you with that | 14:38 |
| NickChase | :) | 14:38 |
| nermina | high five | 14:38 |
| NickChase | Opening a side channel to set a time... | 14:38 |
| Sam-I-Am | carlp: we do see a lot of third-party guides... and i think those will go away if we make this guide work | 14:38 |
| carlp | Sam-I-Am: agreed | 14:38 |
| Sam-I-Am | nermina/nick thanks... i'm not a docbook guru yet | 14:39 |
| nermina | you'll be one by the time you're done with this guide, sam-i-am :) | 14:39 |
| Sam-I-Am | ha | 14:39 |
| annegentle | Sam-I-Am: you're certainly doing a great job | 14:39 |
| carlp | Sam-I-Am: at least for the OpenSource stuff (OVS, LinuxBridge, etc). There will always be third-party guides for the proprietary plug-ins but that's unavoidable | 14:39 |
| annegentle | carlp: are there already? | 14:39 |
| Sam-I-Am | oh, sure... | 14:39 |
| *** SergeyLukjanov has quit IRC | 14:39 | |
| *** SergeyLukjanov_ is now known as SergeyLukjanov | 14:39 | |
| *** BrianB_ has quit IRC | 14:39 | |
| carlp | annegentle: yes. Most of the third-party plugins from commercial vendors ship their own documentation to customers (nicira, etc) | 14:40 |
| annegentle | carlp: ah ok, that's not stuff we see. Wonder if we can just make a list to links to their sites then? | 14:40 |
| annegentle | carlp: that'd be a huge debt load off docs | 14:40 |
| NickChase | +1 | 14:40 |
| Sam-I-Am | so far, i havent seen many people using the install guide with special plug-ins | 14:41 |
| Sam-I-Am | its always been a very basic architecture | 14:41 |
| NickChase | At the very least, WE can go there to get information. :) | 14:41 |
| annegentle | funny thing is, block storage tends to write theirs upstream | 14:41 |
| carlp | annegentle: Maybe. Not all of them are publicly available. It's a mixed bag. | 14:41 |
| annegentle | carlp: got it. good to know | 14:41 |
| annegentle | woo mixed bag. not :) | 14:42 |
| annegentle | ok, I'm definitely going to talk about install guide for that webinar | 14:42 |
| annegentle | note to self | 14:42 |
| Sam-I-Am | cool | 14:42 |
| annegentle | anything else on install guide? networking guide? | 14:42 |
| NickChase | nope. | 14:42 |
| Sam-I-Am | i think we have a plan | 14:43 |
| annegentle | I'm going to put up some actions then. cool. | 14:43 |
| NickChase | except carlp, let me know when you can meet | 14:43 |
| annegentle | #action NickChase and carlp and Sam-I-Am to meet | 14:43 |
| Sam-I-Am | i'm installing icehouse where i can... should know soon how that's turning out | 14:43 |
| annegentle | NickChase: can you share on the Mailing list about the networking guide pull out | 14:43 |
| carlp | NickChase: I'm flexible :) | 14:43 |
| annegentle | NickChase: and contact Edgar? | 14:43 |
| NickChase | Need his info. | 14:43 |
| nermina | annegentle, what is still left to do on the install guide? | 14:43 |
| NickChase | and yes, I will. | 14:44 |
| annegentle | #action NickChase to contact Edgar Magana on the neutron team to let him know the networking guide plan | 14:44 |
| annegentle | #action annegentle to email Nick and Edgar | 14:44 |
| *** ruhe is now known as ruhe_away | 14:44 | |
| Sam-I-Am | nermina: there's plenty of phrasing/formatting cleanup | 14:44 |
| annegentle | #action NickChase to email openstack-docs mailing list with plan for networking guide | 14:44 |
| annegentle | anything I missed? | 14:44 |
| Sam-I-Am | nermina: lots of inconsistency between sections | 14:44 |
| *** SergeyLukjanov has quit IRC | 14:44 | |
| *** ruhe_away is now known as ruhe | 14:44 | |
| annegentle | #topic Doc tools update | 14:44 |
| *** openstack changes topic to "Doc tools update (Meeting topic: DocTeamMeeting)" | 14:44 | |
| nermina | sam-i-am, could you send me a msg with details? | 14:45 |
| *** ruhe is now known as ruhe_away | 14:45 | |
| annegentle | The openstack-doc-tools release 0.3 went out Monday and release notes are now available | 14:45 |
| *** SergeyLukjanov_ has joined #openstack-meeting-alt | 14:45 | |
| annegentle | #link https://github.com/openstack/openstack-doc-tools | 14:45 |
| *** SergeyLukjanov_ is now known as SergeyLukjanov | 14:45 | |
| annegentle | AJaeger: great story, I had an email from a cloud architect at Rackspace who found that missing div and your patch was already in the review queue! Winning. | 14:46 |
| *** nati_uen_ has joined #openstack-meeting-alt | 14:46 | |
| AJaeger | ;) | 14:46 |
| *** ruhe_away is now known as ruhe | 14:46 | |
| Sam-I-Am | nermina: e-mail? | 14:46 |
| AJaeger | There were many bugs in the api project sites where some never build - e.g. database-api was unbuildable | 14:47 |
| nermina | nmiller@mirantis.com | 14:47 |
| Sam-I-Am | nermina: k | 14:47 |
| nermina | thanks, sam-i-am | 14:47 |
| annegentle | AJaeger: wow that's blarg. Makes me want to go yell at people. Sigh. | 14:47 |
| annegentle | AJaeger: good work here. | 14:47 |
| AJaeger | annegentle, there's wasn't a patch for 6 months at least for the repo - and the bug was using clouddocs-plugin 1.7-SNAPSHOT... | 14:48 |
| AJaeger | We really need those gates everywhere - I'm working on that | 14:48 |
| AJaeger | And dianefleming helped a lot debugging | 14:48 |
| annegentle | AJaeger: yeah I know the peeps working on it (or not working currently) and it's a problem, thanks for the help | 14:48 |
| annegentle | AJaeger: and, getting Japanese translation automated will be very exciting | 14:49 |
| AJaeger | YEah - but something I cannot handle right now - others have to help on that... | 14:49 |
| *** nati_ueno has quit IRC | 14:49 | |
| annegentle | AJaeger: yeah I dont' think that's yours at all other than having the tool on pypi | 14:49 |
| dianefleming | i could help with database-api - let me know | 14:50 |
| dianefleming | or any other api that's not building | 14:50 |
| annegentle | Let's see, nothing on the horizon for clouddocs maven plugin, though if you haven't pulled up api.openstack.org/api-ref.html you should! | 14:50 |
| annegentle | #link api.openstack.org/api-ref.html | 14:50 |
| annegentle | full refresh so that it works on mobile | 14:50 |
| annegentle | A guy on me and Diane's team did it in like 4 hours on a Friday afternoon. He's that good. | 14:50 |
| NickChase | annegentle: that's great! | 14:51 |
| annegentle | dianefleming: cool thanks | 14:51 |
| *** balajiiyer has joined #openstack-meeting-alt | 14:51 | |
| annegentle | #info openstack-doc-tools 0.3 released this week | 14:51 |
| *** demorris has joined #openstack-meeting-alt | 14:51 | |
| annegentle | #info clouddocs-maven-plugin released 1.12.2 refreshing http://api.openstack.org/api-ref.html | 14:51 |
| annegentle | Anything else on tools? | 14:51 |
| *** sarob has joined #openstack-meeting-alt | 14:51 | |
| annegentle | # Open discussion | 14:51 |
| annegentle | #topic Open discussion | 14:52 |
| *** openstack changes topic to "Open discussion (Meeting topic: DocTeamMeeting)" | 14:52 | |
| annegentle | sorry didn't mean to rush anyone but we've got 9 mins left | 14:52 |
| *** jecarey has quit IRC | 14:53 | |
| *** nati_uen_ has quit IRC | 14:53 | |
| AJaeger | annegentle, nothing else on tools - hope to have the gates working quickly - but waiting for infra | 14:53 |
| *** irenab has quit IRC | 14:53 | |
| annegentle | AJaeger: fine work you're doing | 14:53 |
| AJaeger | What about glossary: Did you read my email? Is that something we should try for one guide - like Install Guide | 14:53 |
| *** jayahn has joined #openstack-meeting-alt | 14:53 | |
| annegentle | AJaeger: I seriously was so happy about that caught div :) | 14:53 |
| *** nati_ueno has joined #openstack-meeting-alt | 14:53 | |
| *** SergeyLukjanov is now known as SergeyLukjanov_ | 14:53 | |
| annegentle | AJaeger: oh yeah! GLossary | 14:54 |
| annegentle | so during the book sprint the Ops guide peeps said the large glossary was tooooo big | 14:54 |
| annegentle | dianefleming: didn't you try to do conditional output for it or some such? What was the story there? My memory fails me | 14:54 |
| *** boris-42_ has joined #openstack-meeting-alt | 14:54 | |
| *** SergeyLukjanov_ is now known as SergeyLukjanov | 14:54 | |
| AJaeger | You can either add the whole glossary - or just the entries used in the guide. I would go for the later for now.... | 14:54 |
| *** sarob has quit IRC | 14:55 | |
| AJaeger | The security guide already has that glossary with just the entries used in it - have a look at my email for the link | 14:56 |
| annegentle | AJaeger: dianefleming: okay maybe that's what I was thinking of,that there's an automated way to have a smaller glossary? | 14:56 |
| annegentle | AJaeger: and the security guide does this already somehow? | 14:56 |
| AJaeger | http://docs.openstack.org/security-guide/content/go01.html | 14:56 |
| *** boris-42_ has quit IRC | 14:56 | |
| annegentle | AJaeger: also is Tom accurate in his assessment that the glossary is not specially treated in translation? Not even sure how to research taht myself. | 14:56 |
| AJaeger | Yeah, it does it - really short one | 14:56 |
| *** jjmb has joined #openstack-meeting-alt | 14:57 | |
| AJaeger | The translators can just remove the few lines to include the glossary ;) | 14:57 |
| *** boris-42 has quit IRC | 14:57 | |
| annegentle | AJaeger: there's a bug already, it says See access control list. but access control list isn't an entry | 14:57 |
| AJaeger | It's easy to add the glossary in a way similar to the install guide. | 14:57 |
| annegentle | AJaeger: ok | 14:57 |
| *** colinmcnamara has joined #openstack-meeting-alt | 14:57 | |
| annegentle | colinmcnamara: or sean roberts, any report for training? I saw your notes from the last meeting | 14:58 |
| AJaeger | annegentle, yeah - that one needs extra handling | 14:58 |
| annegentle | AJaeger: ok, I'll file a doc bug | 14:59 |
| AJaeger | annegentle, assign it to me, I'll take care of it | 14:59 |
| annegentle | AJaeger: thanks! | 14:59 |
| *** coolsvap_away is now known as coolsvap | 14:59 | |
| AJaeger | the hard part is adding all the <glossterm> entries to the guide.... | 14:59 |
| *** safchain has quit IRC | 14:59 | |
| AJaeger | but not much... | 14:59 |
| *** safchain has joined #openstack-meeting-alt | 15:00 | |
| annegentle | AJaeger: yeah I see it as better than index entries but still work like that | 15:00 |
| *** Swami has joined #openstack-meeting-alt | 15:01 | |
| annegentle | Ok, outta time, not sure who has this room next. | 15:01 |
| annegentle | Thanks everyone!! Great work, I mean that. | 15:01 |
| Sam-I-Am | good meeting | 15:01 |
| annegentle | #endmeeting | 15:01 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:01 | |
| AJaeger | I'll evaluate it a bit more... | 15:01 |
| openstack | Meeting ended Wed Jan 15 15:01:34 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:01 |
| AJaeger | bye | 15:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/docteammeeting/2014/docteammeeting.2014-01-15-14.01.html | 15:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/docteammeeting/2014/docteammeeting.2014-01-15-14.01.txt | 15:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/docteammeeting/2014/docteammeeting.2014-01-15-14.01.log.html | 15:01 |
| *** dianefleming has left #openstack-meeting-alt | 15:01 | |
| *** Sam-I-Am has left #openstack-meeting-alt | 15:01 | |
| *** jjmb has quit IRC | 15:01 | |
| *** sankarshan is now known as sankarshan_away | 15:01 | |
| Swami | hi | 15:01 |
| Swami | safchain ping | 15:02 |
| Swami | james ping | 15:02 |
| safchain | Swami, pong, Hi | 15:02 |
| Swami | robin wong ping | 15:02 |
| Swami | safchain: hi | 15:03 |
| NickChase | Bye, all! | 15:03 |
| *** NickChase has quit IRC | 15:03 | |
| Swami | #startmeeting Distributed_virtual_router | 15:03 |
| openstack | Meeting started Wed Jan 15 15:03:30 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:03 |
| *** openstack changes topic to " (Meeting topic: Distributed_virtual_router)" | 15:03 | |
| openstack | The meeting name has been set to 'distributed_virtual_router' | 15:03 |
| Swami | #topic agenda | 15:04 |
| *** openstack changes topic to "agenda (Meeting topic: Distributed_virtual_router)" | 15:04 | |
| Swami | Go over safchain's proposal. | 15:04 |
| Swami | Discuss about the API | 15:04 |
| Swami | Next steps | 15:04 |
| Swami | safchain: Thanks for your email response and the picture that helped me to understand some of your design considerations. | 15:05 |
| Swami | safchain: I have a question on your east-west router? Do you have a minute to discuss about it. | 15:07 |
| *** amytron has quit IRC | 15:07 | |
| *** hemanthravi has joined #openstack-meeting-alt | 15:07 | |
| safchain | Swami, yes | 15:07 |
| *** gokrokve has joined #openstack-meeting-alt | 15:07 | |
| Swami | safchain: In your east-west router, you have mentoned it is still generated by the VRRP. So my understanding is the East-West router will reside within the Network Node or will it be distributed across the compute nodes. | 15:09 |
| Swami | hemanthravi:hi | 15:09 |
| hemanthravi | swami: hi | 15:09 |
| *** SergeyLukjanov has quit IRC | 15:09 | |
| safchain | Swami, could be on network nodes, but could be one specific network nodes for the east-west | 15:09 |
| *** SergeyLukjanov_ has joined #openstack-meeting-alt | 15:10 | |
| safchain | s/one/on/ | 15:10 |
| *** SergeyLukjanov_ is now known as SergeyLukjanov | 15:10 | |
| safchain | Swami, since no need to be connected to an external network | 15:10 |
| *** yamahata has joined #openstack-meeting-alt | 15:11 | |
| Swami | safchain: Yes in this case your east-west routers are normal regular routers that we have today without external connectivity | 15:11 |
| *** colinmcnamara has quit IRC | 15:11 | |
| safchain | Swami, with vrrp added | 15:11 |
| safchain | Swami, but yes | 15:11 |
| hemanthravi | shouldn't east-west be done without the network node always for DVR | 15:12 |
| Swami | safchain: Why should the east west routers know about the vrrp, is it for failover. | 15:12 |
| safchain | Swami, yes | 15:12 |
| Swami | hemanthravi: sorry for the confussion, I am currently discussing safchain's proposal where he supports only the North-South | 15:12 |
| hemanthravi | ok | 15:13 |
| Swami | hemanthravi: his proposal should be a link in our google doc at the end of the document. | 15:13 |
| safchain | I'm going to update the link not sure the link at the bottom is the good one | 15:14 |
| Swami | safchain; yes go ahead and update with your latest picture and the additional information that you added. | 15:14 |
| *** jjmb has joined #openstack-meeting-alt | 15:14 | |
| *** Barker has joined #openstack-meeting-alt | 15:15 | |
| *** jjmb has quit IRC | 15:15 | |
| Swami | safchain: How many network nodes will be required in your design, is it just one or we can have as many network nodes as possible. | 15:15 |
| safchain | Swami, many as possible | 15:16 |
| Swami | safchain: Will you be providing HA for all the nodes | 15:16 |
| *** betsy has joined #openstack-meeting-alt | 15:17 | |
| safchain | Swami, for north-south without floating ip yes, but for north-south when a vm has a floating ip, no | 15:17 |
| Swami | safchain: In other words, will each network node have a HA pair or there will be only one HA pair and it will substitute for the failed one in the pool. | 15:17 |
| safchain | Swami, virtual routers are distributed on networks nodes, each network node could host master or slave vrouter | 15:18 |
| safchain | Swami, https://docs.google.com/document/d/1Ps8Oc-mNcJXdOwAcor3hzoMBS_5zeTQUBbvX9QWx50g/edit | 15:19 |
| Swami | safchain: But you mentioned for north-south when a vm has a floating ip there will not be "HA" . Is that right. | 15:19 |
| *** SergeyLukjanov has quit IRC | 15:19 | |
| safchain | and https://docs.google.com/drawings/d/1iLWlHbUfWNaXpitXU-5xnk4kUi6_V6aS94YZWgYFxX8/edit | 15:19 |
| Swami | safchain: Can you also add the other picture you sent to me yesterday in to the same document. | 15:20 |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 15:20 | |
| *** IlyaE has joined #openstack-meeting-alt | 15:21 | |
| safchain | Swami, yes no need HA in that case (floating ip), since if the compute node fails, the VM fails too | 15:21 |
| safchain | Swami, yes I'll add the picture | 15:21 |
| Swami | safchain: Ok got it. | 15:21 |
| Swami | safchain: Thanks for the update. | 15:22 |
| *** SergeyLukjanov has quit IRC | 15:22 | |
| safchain | Swami, just added the picture at the end of the doc | 15:22 |
| Swami | safchain: Thanks | 15:22 |
| Swami | #topic API | 15:22 |
| *** openstack changes topic to "API (Meeting topic: Distributed_virtual_router)" | 15:22 | |
| *** SergeyLukjanov has joined #openstack-meeting-alt | 15:23 | |
| *** xuhanp has quit IRC | 15:23 | |
| Swami | safchain: For the vrrp are you proposing any new api for the router. | 15:23 |
| safchain | Swami, no new api, just a new parameter in the config file of neutron | 15:23 |
| safchain | Swami, in the l3 config file too | 15:24 |
| Swami | safchain: In the summit you had mentioned that the router will have a type=vrrp, is that still true. | 15:24 |
| *** ruhe is now known as ruhe_away | 15:25 | |
| safchain | Swami, that was discussed during the last summit, yes we have changed this point to use only a parameter in the config | 15:25 |
| *** alazarev has joined #openstack-meeting-alt | 15:25 | |
| Swami | safchain: yes thanks for the clarification. | 15:25 |
| safchain | Swami, The goal is to hide HA stuff for the user | 15:25 |
| Swami | safchain: Yes you are right. | 15:25 |
| safchain | Swami, propably network optimisation too, east-west/north-south ? | 15:26 |
| *** demorris has quit IRC | 15:27 | |
| Swami | safchain: The problem that we are facing in our proposal is the "API" change. Since we do support DVR for east-west and for north-south, there is no way to distinguish between the two types of routers. | 15:27 |
| *** sadasu has quit IRC | 15:27 | |
| *** demorris has joined #openstack-meeting-alt | 15:27 | |
| Swami | The only way that we can distinguish is by providing the "--distributed" flag in the router command. | 15:28 |
| safchain | Swami, one is connected to an external network, and the other one is only connected to private networks | 15:28 |
| *** akuznetsov has quit IRC | 15:28 | |
| Swami | safchain: Yes that would work in your proposal, if we split the SNAT from the floating ip. In our design proposal we have external network supported on all routers if required. | 15:29 |
| safchain | Swami, the scheduler could distinguish the agent, and schedule/reschedule routers on the right agent | 15:29 |
| *** aignatov has quit IRC | 15:29 | |
| *** dguitarbite has joined #openstack-meeting-alt | 15:30 | |
| Swami | safchain: Yes I thought through the process, it would work in your design because you would associate a float router to a float agent through the schedular. | 15:31 |
| Swami | safchain: In our case the schedular first schedules the router as DVR and then when we associate an external network, its property will now change from East-West DVR to north south. | 15:33 |
| *** amytron has joined #openstack-meeting-alt | 15:34 | |
| *** ruhe_away is now known as _ruhe | 15:34 | |
| Swami | Folks I might have a hard stop for this meeting at 7.45, since I have another meeting. | 15:35 |
| *** chandankumar has quit IRC | 15:35 | |
| Swami | safchain: When do we want to target our work for Icehouse. | 15:35 |
| Swami | safchain:Did you look at the "Provider router" blueprint, will that have any impact on our design. | 15:37 |
| safchain | Swami, I currently working on HA, already submitting WIP patches I hope we will have it on Icehouse, no didn't look at it | 15:37 |
| safchain | Swami, I will | 15:38 |
| *** betsy has quit IRC | 15:38 | |
| Swami | safchain: So your HA will go through Icehouse 3. | 15:38 |
| safchain | Swami, yes I hope | 15:38 |
| Swami | #topic Open Discussion | 15:38 |
| *** openstack changes topic to "Open Discussion (Meeting topic: Distributed_virtual_router)" | 15:38 | |
| *** betsy has joined #openstack-meeting-alt | 15:39 | |
| *** IlyaE has quit IRC | 15:39 | |
| *** chandankumar has joined #openstack-meeting-alt | 15:39 | |
| Swami | If anyone have not gone through the Provider router blueprint please go through it. | 15:39 |
| *** akuznetsov has joined #openstack-meeting-alt | 15:39 | |
| *** SergeyLukjanov is now known as SergeyLukjanov_a | 15:39 | |
| Swami | hemanthravi: Do you have any questions? | 15:40 |
| *** SergeyLukjanov_a is now known as SergeyLukjanov_ | 15:40 | |
| Swami | If you folks have any other questions please feel free to send me an email. | 15:41 |
| *** nati_uen_ has joined #openstack-meeting-alt | 15:41 | |
| *** nati_uen_ has quit IRC | 15:41 | |
| *** nati_uen_ has joined #openstack-meeting-alt | 15:42 | |
| hemanthravi | swami: need to go through the docs again, will send an email | 15:42 |
| Swami | safchain: Next week I am planning to have a broader proposal review from the OpenStack community, so if you can add any details to your doc, make sure you add that and we can go over. | 15:42 |
| Swami | Thanks everyone for joining the meeting. | 15:43 |
| Swami | see you next week. | 15:43 |
| *** SergeyLukjanov_ is now known as SergeyLukjanov | 15:43 | |
| hemanthravi | swami: do you still have the mon meeting. | 15:43 |
| Swami | bye | 15:43 |
| *** betsy has quit IRC | 15:43 | |
| Swami | hemanthravi: no I temporarily suspended the monday meeting since the attendance was very low. | 15:43 |
| *** SergeyLukjanov is now known as SergeyLukjanov_ | 15:44 | |
| Swami | If you need to chat with me on monday I am available on IRC and you can catch me on private chat. | 15:44 |
| Swami | #endmeeting | 15:44 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:44 | |
| openstack | Meeting ended Wed Jan 15 15:44:42 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:44 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-01-15-15.03.html | 15:44 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-01-15-15.03.txt | 15:44 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/distributed_virtual_router/2014/distributed_virtual_router.2014-01-15-15.03.log.html | 15:44 |
| *** nati_ueno has quit IRC | 15:45 | |
| *** alazarev has quit IRC | 15:45 | |
| safchain | Swami, bye | 15:46 |
| Swami | safchain: bye | 15:46 |
| Swami | hemanthravi: bye | 15:46 |
| *** jmontemayor has joined #openstack-meeting-alt | 15:47 | |
| *** Swami has quit IRC | 15:48 | |
| hemanthravi | bye | 15:48 |
| *** jayahn has quit IRC | 15:49 | |
| *** jayahn has joined #openstack-meeting-alt | 15:49 | |
| *** AlanClark has joined #openstack-meeting-alt | 15:50 | |
| *** colinmcnamara has joined #openstack-meeting-alt | 15:51 | |
| *** sarob has joined #openstack-meeting-alt | 15:51 | |
| *** rkukura has joined #openstack-meeting-alt | 15:54 | |
| *** rcurran has joined #openstack-meeting-alt | 15:56 | |
| *** sarob has quit IRC | 15:56 | |
| *** AJaeger has left #openstack-meeting-alt | 15:56 | |
| mestery | Greetings fellow ML2 developers! | 16:00 |
| asadoughi | hi | 16:00 |
| rcurran | hi | 16:00 |
| hemanthravi | hi | 16:00 |
| *** BrianB_ has joined #openstack-meeting-alt | 16:00 | |
| rkukura | hi | 16:00 |
| mestery | #startmeeting networking_ml2 | 16:00 |
| openstack | Meeting started Wed Jan 15 16:00:37 2014 UTC and is due to finish in 60 minutes. The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| *** openstack changes topic to " (Meeting topic: networking_ml2)" | 16:00 | |
| openstack | The meeting name has been set to 'networking_ml2' | 16:00 |
| mestery | #link https://wiki.openstack.org/wiki/Meetings/ML2 Agenda | 16:00 |
| mestery | We've got an agenda which will either go at least an hour, or we'll be done in 20 minutes. Lets see what happens. :) | 16:01 |
| mestery | #topic Action Items | 16:01 |
| *** openstack changes topic to "Action Items (Meeting topic: networking_ml2)" | 16:01 | |
| mestery | The first action item to cover is for rcurran. | 16:01 |
| *** bill_az has joined #openstack-meeting-alt | 16:01 | |
| mestery | rcurran: Did you verify if a bug is needed for Cisco UT coverage in ML2? | 16:01 |
| rcurran | yes, do you want the link | 16:01 |
| rcurran | bug# | 16:02 |
| mestery | rcurran: Yes please, I'll add it in the meeting minutes. | 16:02 |
| rcurran | https://bugs.launchpad.net/neutron/+bug/1267481 | 16:02 |
| *** jecarey has joined #openstack-meeting-alt | 16:02 | |
| mestery | rcurran: thanks! | 16:02 |
| *** banix has joined #openstack-meeting-alt | 16:02 | |
| mestery | #link https://bugs.launchpad.net/neutron/+bug/1267481 Bug for Cisco ML2 UT coverage | 16:02 |
| mestery | asadoughi: Thank you for filing bugs for the ML2 UT coverage gaps! | 16:03 |
| mestery | #info ML2 UT coverage bugs filed and tagged: https://bugs.launchpad.net/neutron/+bugs?field.tag=ml2-unit-test-coverage | 16:03 |
| asadoughi | mestery: np | 16:03 |
| *** tomblank1 has joined #openstack-meeting-alt | 16:03 | |
| *** tomblank has quit IRC | 16:03 | |
| mestery | Now that these bugs are filed, if you are planning to work on one, please assign it to yourself. Anyone can grab one of these. | 16:03 |
| mestery | Would be good to get this coverage added during Icehouse if we can spread the load. | 16:04 |
| mestery | So, jumping around a little (we'll come back to you rkukura): | 16:04 |
| mestery | I pinged asomya this morning around his RPC google document | 16:04 |
| mestery | #link https://docs.google.com/document/d/1ZHb2zzPmkSOpM6PR8M9sx2SJOJPHblaP5eVXHr5zOFg/edit RPC Google Document | 16:04 |
| mestery | I have not heard back from asomya yet, but once I do, we'll send email to the mailing list. | 16:04 |
| mestery | #topic Port Binding | 16:05 |
| *** openstack changes topic to "Port Binding (Meeting topic: networking_ml2)" | 16:05 | |
| mestery | So now, the meat of the meeting: port binding :) | 16:05 |
| *** asomya has joined #openstack-meeting-alt | 16:05 | |
| mestery | #undo | 16:05 |
| openstack | Removing item from minutes: <ircmeeting.items.Topic object at 0x39171d0> | 16:05 |
| mestery | Wait, asomya joined! | 16:05 |
| mestery | asomya, welcome! | 16:05 |
| asomya | Hello | 16:05 |
| mestery | I just mentioned your RPC document (https://docs.google.com/document/d/1ZHb2zzPmkSOpM6PR8M9sx2SJOJPHblaP5eVXHr5zOFg/edit) | 16:05 |
| matrohon | hi | 16:06 |
| mestery | Last week, there was a question on if you were still targeting this for Icehouse or not. | 16:06 |
| mestery | I wasn't sure, thus needed your input :) | 16:06 |
| asomya | That's not being worked on actively at the moment, It needs the other patch that i proposed in the summit to make type drivers more self sufficient | 16:06 |
| asomya | I was waiting for Zan'g ptch to go in before i posted mine but now I see that one is abandoned | 16:06 |
| mestery | asomya: Thanks. Could we expand Zhang's typedriver patch to make that work with this RPC work? | 16:06 |
| mestery | asomya: :) | 16:06 |
| asomya | Yes I'll post a patch for that work and then work on this | 16:07 |
| rkukura | Phasing smaller patches is better | 16:07 |
| rkukura | Lets get the type driver refactor active again, whether the original patch or a new one | 16:07 |
| mestery | Agreed. So asomya, do you want to reach out to Zhang and cooridnate thigns there? | 16:07 |
| mestery | rkukura: Agreed. | 16:07 |
| asomya | rkukura: agreed | 16:07 |
| mestery | asomya: You ok reaching out for this or do you want me to to take an action? | 16:07 |
| asomya | I'll reach out to Zhang if i need his counsel on the patch | 16:08 |
| mestery | asomya: Thanks! | 16:08 |
| mestery | #action asomya to work on new typedriver refactoring patch with zhang | 16:08 |
| mestery | OK, anything else on RPC or TypeDriver here before we move on to port binding discussions? | 16:08 |
| matrohon | asomya: let's keep in touch we may need your functionnality | 16:09 |
| asomya | matrohon: sure | 16:09 |
| *** jayahn has quit IRC | 16:09 | |
| mestery | #topic Port Binding | 16:09 |
| *** yamahata has quit IRC | 16:09 | |
| *** openstack changes topic to "Port Binding (Meeting topic: networking_ml2)" | 16:09 | |
| mestery | rkukura: You're up! | 16:09 |
| rkukura | OK, I have not yet emailed a concrete proposal on port binding improvments | 16:10 |
| *** yamahata has joined #openstack-meeting-alt | 16:10 | |
| rkukura | but can discuss the ideas/conclusions here | 16:10 |
| rkukura | 1st, because MDs may need to make remote calls to controllers/devices, we need ml2 to call bind_port() on them outside of any transaction rather than inside, as is currently done | 16:11 |
| *** mozawa has quit IRC | 16:11 | |
| rkukura | So I was looking into whether we could do the port binding before starting the transaction. But if binding:host_id is supplied in port_create, this would mean trying to bind before we've stored anything about the port in the DB | 16:12 |
| *** esker has joined #openstack-meeting-alt | 16:12 | |
| rkukura | It seems some MDs might need to maintain their own table mapping neutron's port ID to a controller's port ID | 16:13 |
| *** dguitarbite has quit IRC | 16:13 | |
| *** SergeyLukjanov_ is now known as SergeyLukjanov | 16:13 | |
| rkukura | But the MD's could not reference the neutron port as a foriegn key with cascading delete and all that if the transaction creating this hasn't even started. | 16:14 |
| rkukura | So that leads to a two transaction approach. | 16:14 |
| *** _ruhe is now known as ruhe | 16:14 | |
| rkukura | The port_create or port_update that sets the binding:host_id would 1st be processed normally without trying to bind the port, and the MDs' precommit and postcommit calls would be made | 16:15 |
| rkukura | Then port binding would occur outside any tranaction | 16:15 |
| mestery | rkukura: Per our discussion last night, this all makes sense to me. I'm curious what others think. | 16:15 |
| rkukura | in bind_port, MDs could do their own transactions if needed and/or could talk to controllers/devices | 16:16 |
| rkukura | Then a 2nd transaction would update the ml2_port_binding table with the result | 16:16 |
| *** ozstacker has quit IRC | 16:16 | |
| matrohon | make sens to me too | 16:16 |
| rkukura | And I think the MDs would see this as a port_update | 16:16 |
| rkukura | with its own precommit and postcommit calls | 16:17 |
| mestery | Yes. rkukura, I think this also makes the interactions with nova pretty concise as well, since nova would first create the port, then update the port. | 16:17 |
| rkukura | mestery: Actually, nova could still just create the port, and expect the returned port dict to have the binding result | 16:17 |
| matrohon | mestery : why nova should update the port? | 16:18 |
| *** ozstacker has joined #openstack-meeting-alt | 16:18 | |
| mestery | rkukura matrohon: Nevermind, I was confusing this with some other nova thing. Carry on. :) | 16:18 |
| rkukura | when the user passes in a port-id, then nova updates to set binding:host_id, otherwise it can just create it with binding:host_id | 16:18 |
| *** Barker has quit IRC | 16:18 | |
| rkukura | either way, nova needs the binding result (vif_type, capabilities/vif_security, etc.) | 16:19 |
| rkukura | So from the API, its a single operation, but internally its two transactions | 16:19 |
| *** Barker has joined #openstack-meeting-alt | 16:20 | |
| rkukura | Which then brings up the question of concurrency, since all kinds of things can happen between those two transactions | 16:20 |
| *** Barker has quit IRC | 16:20 | |
| mestery | rkukura: :) | 16:21 |
| matrohon | maybe out of scope but don't you think that this is a scheduler issue, the scheduler should ask for a host capable to bind the port first | 16:21 |
| rkukura | I was thinking a state machine would be needed, where the thread doing the binding sets a state showing that a binding is in progress in the 1st transaction, and then changes to complete/failed after | 16:21 |
| *** asadoughi has quit IRC | 16:21 | |
| rkukura | matrohon: Agreed, but we still need to eventually do the binding | 16:21 |
| rkukura | matrohon: We could have the scheduler set binding:host_id and nova just to port_get, but that's later | 16:22 |
| matrohon | rkukura : ok | 16:22 |
| rkukura | Anyway, the state machine gets complex when you consider the thread/process doing the binding dying, or other threads needing the result of the binding | 16:22 |
| *** aignatov has joined #openstack-meeting-alt | 16:23 | |
| rkukura | So was chatting with mestery and describing this, and we started thinking maybe we can just allow different threads/proccess to attempt to bind concurrently, and not need a state machine | 16:23 |
| rkukura | This would work as follows: | 16:24 |
| rkukura | Any thread executing port_create, port_update, or port_get may see that it is possible to bind (binding:host_id is set) but the port is not yet bound. | 16:25 |
| rkukura | It will then attempt to bind the port (after committing the 1st transaction in the case of port_create or port_update) | 16:25 |
| *** akuznetsov has quit IRC | 16:25 | |
| rkukura | When its binding attempt is complete, it will start a new transaction | 16:26 |
| rkukura | In that new transaction, it will look to see if the port has already been bound concurrently by some other thread/process | 16:26 |
| rkukura | if so, it will use the stored binding to return the right port dict info from the operation, and if not it will its own binding result and return it | 16:27 |
| rkukura | does this make any sense, and seem workable? | 16:27 |
| matrohon | looks great to me :) | 16:28 |
| mestery | +1 | 16:28 |
| rcurran | looks good but waiting for the unbind/delete logic :-) | 16:28 |
| rkukura | rcurran: good point - haven't worked out details on that yet | 16:29 |
| *** guestuser9490 has joined #openstack-meeting-alt | 16:31 | |
| *** dguitarbite has joined #openstack-meeting-alt | 16:31 | |
| matrohon | the port delet should ask the MD in charge of the binding first, to unbind the port | 16:31 |
| rkukura | So if the basic idea/approach discussed here seems workable, I'll flesh out the remaining details, including unbind/delete and send an email to openstack-dev for discussion | 16:31 |
| *** kevinconway has joined #openstack-meeting-alt | 16:31 | |
| *** Barker has joined #openstack-meeting-alt | 16:31 | |
| mestery | rkukura: Go for it! Thanks for all your work on this! | 16:32 |
| mestery | #action rkukura to flesh out details of bind/unbind and send email to openstack-dev ML | 16:32 |
| matrohon | rkukura : thanks | 16:32 |
| rcurran | yes, thanks | 16:32 |
| rkukura | matrohon: I think you are right - want to make sure the bound MD knows it has been unbound, but also that all MDs know the port itself has been unbound | 16:32 |
| rkukura | And in both cases, should know the details of that previous binding | 16:33 |
| matrohon | other MD will be aware of that with port_update_pre/post commit | 16:33 |
| rkukura | matrohon: right | 16:33 |
| rcurran | and the (now) unbound information is available to md's (bob beat me to it) | 16:33 |
| *** IlyaE has joined #openstack-meeting-alt | 16:33 | |
| rkukura | one other port binding change comes from nati_uen_'s vif_security patch | 16:34 |
| *** IlyaE has quit IRC | 16:35 | |
| rkukura | that basically replaces storing the capabilities supplied by the bound MD with calling into the bound MD to get the vif_security attribute | 16:35 |
| rkukura | I'd like to apply that same pattern to the vif_type, and allow it to be extended for things like attributes needed for sr-iov | 16:36 |
| *** nati_ueno has joined #openstack-meeting-alt | 16:36 | |
| *** hemanth__ has joined #openstack-meeting-alt | 16:36 | |
| mestery | Makes sense to me rkukura. | 16:36 |
| rkukura | nati_ueno: did you see last couple lines? | 16:37 |
| *** hemanthravi has quit IRC | 16:37 | |
| matrohon | make sense to me too | 16:37 |
| nati_ueno | rkukura: yes | 16:37 |
| nati_ueno | rkukura: Ah may be I'm missing few lines.. It looks like I've disconnected | 16:38 |
| rkukura | I'm willing to take this subset of nati_uen's patch, generalize it a bit, make sure it works for vif_type, and propose it for review separately from the capabilities->vif_security change | 16:38 |
| rkukura | nati_ueno: one other port binding change comes from nati_uen_'s vif_security patch | 16:38 |
| rkukura | nati_ueno: that basically replaces storing the capabilities supplied by the bound MD with calling into the bound MD to get the vif_security attribute | 16:39 |
| *** SushilKM has joined #openstack-meeting-alt | 16:39 | |
| nati_ueno | rkukura: OK I saw the line. Thanks | 16:39 |
| *** Barker has quit IRC | 16:39 | |
| rkukura | nati_ueno: I'd like to apply that same pattern to the vif_type, and allow it to be extended for things like attributes needed for sr-iov | 16:39 |
| *** nati_uen_ has quit IRC | 16:39 | |
| matrohon | vif_security and vif_type are returned back to agent through get_device_details? | 16:40 |
| nati_ueno | matrohon: vif_security won't got to the agent | 16:40 |
| nati_ueno | s/got/go/ | 16:40 |
| nati_ueno | it is needed by nova | 16:40 |
| rkukura | matrohon: These are REST API extensions to port, not RPC | 16:40 |
| *** SushilKM has left #openstack-meeting-alt | 16:40 | |
| *** jcoufal has quit IRC | 16:41 | |
| rkukura | nati_ueno's patch updates the portbinding extension, replacing capabilities with vif_security | 16:41 |
| nati_ueno | rkukura: so you wanna have the generalized version before the my patch? | 16:41 |
| *** Barker has joined #openstack-meeting-alt | 16:42 | |
| rkukura | nati_ueno: If that helps get things moving, sure | 16:42 |
| nati_ueno | rkukura: if it is faster, ok please | 16:42 |
| rkukura | I think that patch would be a small change completely localized to ml2 | 16:42 |
| *** dmakogon_ is now known as denis_makogon | 16:43 | |
| rkukura | Separate issue with vif_security is how ml2 gets right info for the firewall_driver in the L2 agent on the node where the port gets bound | 16:43 |
| nati_ueno | yes. but we need some workaround fix for this since security group is broken | 16:44 |
| rkukura | I've suggested that the L2 agent could get the vif_security info from its firewall_driver, and include this in its agents_db info | 16:44 |
| rkukura | then the bound MD would return this as the vif_security for the port | 16:44 |
| rkukura | existing agents_db RPC would send it from agent to server and store it in the agents_db table | 16:45 |
| *** IlyaE has joined #openstack-meeting-alt | 16:46 | |
| mestery | makes sense to me rkukura. | 16:46 |
| rkukura | Maybe this should be on agenda for next week's ml2 meeting if not wrapped up by then? | 16:46 |
| mestery | rkukura: I agree. | 16:47 |
| nati_ueno | rkukura: so you wanna do this from first step? | 16:47 |
| rkukura | nati_ueno: Sound reasonable? | 16:47 |
| nati_ueno | rkukura: hmm I need to time to think about the architecture.. depending agent's configuration sounds like wrong direction | 16:48 |
| *** tomblank1 has quit IRC | 16:48 | |
| rkukura | nati_ueno: I should be able to post initial patch for calling extend_port_dict() on the bound MD instread of storing vif_type and capabliities in ml2_port_binding table today | 16:48 |
| *** coolsvap is now known as coolsvap_away | 16:49 | |
| *** IlyaE has quit IRC | 16:49 | |
| *** mugsie has joined #openstack-meeting-alt | 16:49 | |
| nati_ueno | rkukura: Ok how about remove ml2 from https://review.openstack.org/#/c/21946/ | 16:49 |
| rkukura | nati_ueno: Is that concern around getting the vif_security from the firewall driver in the agent? | 16:49 |
| nati_ueno | rkukura: yes | 16:49 |
| *** ativelkov has left #openstack-meeting-alt | 16:49 | |
| *** boris-42 has joined #openstack-meeting-alt | 16:49 | |
| *** jecarey has quit IRC | 16:49 | |
| nati_ueno | rkukura: then you will have a patch on ml2 localized | 16:49 |
| rkukura | nati_ueno: As I recall, your patch has the firewall_driver supply the vif_security value, right? | 16:50 |
| nati_ueno | rkukura: yes | 16:50 |
| rkukura | If that's the case, then I think the issue is whether this call on the firewall_driver gets made in the L2 agent or in the server | 16:51 |
| *** IlyaE has joined #openstack-meeting-alt | 16:51 | |
| rkukura | Right now, ml2 users need to supply a dummy value for firewall_driver so that the SG API extension is enabled | 16:51 |
| rkukura | in havanan | 16:51 |
| rkukura | havana | 16:51 |
| *** sarob has joined #openstack-meeting-alt | 16:51 | |
| nati_ueno | so my opinion is the current firewall driver model is broken | 16:52 |
| nati_ueno | some functionaries are mixed | 16:52 |
| nati_ueno | enable sec group or not | 16:52 |
| nati_ueno | select driver for each agent implementation | 16:52 |
| rkukura | Agreed enabling the API should be a separate config in the server | 16:52 |
| rkukura | But with ml2, different L2 agents might use different firewall drivers | 16:53 |
| nati_ueno | select driver for agent who support more than one implemenation | 16:53 |
| rkukura | Or a MD for a controller might not use any L2 agent, and instead do SG's some other way | 16:53 |
| nati_ueno | Most of plugin (or MD) supports only one driver | 16:53 |
| nati_ueno | so it should be defined automatically | 16:53 |
| rkukura | ml2 works concurrently with openvswitch-agent, linuxbridge-agent, hyperv-agent, and soon with controllers like ODL | 16:54 |
| nati_ueno | currently there is no plugin or (MD) support multiple drivers | 16:54 |
| rkukura | each of these may have different ways to enforce SGs | 16:54 |
| matrohon | so MD should be in charge of defining the firewall_driver? | 16:54 |
| nati_ueno | rkukura: I agree. so ML2 can support multiple MD | 16:54 |
| nati_ueno | and driver will be decided by MD | 16:54 |
| rkukura | So your approach of having the bound MD return vif_security is correct | 16:55 |
| nati_ueno | because there is no MD which support more than one firewall driver | 16:55 |
| nati_ueno | except Noop | 16:55 |
| rkukura | but we need to resolve how the different MDs in the server get the correct vif_security to return | 16:55 |
| nati_ueno | so we should able to decide vif_security value based on vif_type | 16:55 |
| rkukura | when these MDs are supporting an L2 agent, the agents_db seems like a good solution to me | 16:56 |
| *** sballe has joined #openstack-meeting-alt | 16:56 | |
| nati_ueno | rkukura: OK so we should remove NoopDriver. | 16:56 |
| nati_ueno | so let's say we could remove Noop | 16:56 |
| *** sarob has quit IRC | 16:56 | |
| nati_ueno | we should able to decide vif_security value based on vif_type | 16:57 |
| rkukura | right now, the bound MD supplies the vif_type and the capabilities - just want it to be able to supply the vif_security from the firewall_driver in the agent | 16:57 |
| *** IlyaE has quit IRC | 16:57 | |
| *** jecarey has joined #openstack-meeting-alt | 16:57 | |
| *** sballe has quit IRC | 16:57 | |
| *** jmcbride has joined #openstack-meeting-alt | 16:57 | |
| rkukura | the agent-based MDs already use agents_db to see what network segment they can bind to, based on bridge_mappings info | 16:57 |
| nati_ueno | rkukura: yes, but it is not needed because we can map vif_type to vif_security value | 16:57 |
| mestery | Just a note: We have 3 minutes left here folks. | 16:57 |
| *** sballe has joined #openstack-meeting-alt | 16:57 | |
| mestery | Best to continue this on ML discussion perhaps? | 16:57 |
| rkukura | sure | 16:58 |
| nati_ueno | gotcha | 16:58 |
| mestery | I just know there is another meeting right after this one. :) | 16:58 |
| rkukura | I'm glad we got a chance to get this conversation with nati_ueno going | 16:58 |
| nati_ueno | rkukura: I'll start thread in the openstack-dev | 16:58 |
| * mestery nods in agreement | 16:58 | |
| mestery | nati_ueno: Thanks! | 16:58 |
| nati_ueno | mestery: sure! | 16:58 |
| *** tsimmons has joined #openstack-meeting-alt | 16:58 | |
| *** ashaikh has joined #openstack-meeting-alt | 16:59 | |
| mestery | OK, I think that's it for this week folks! | 16:59 |
| mestery | Lets continue with these threads on the ML. | 16:59 |
| matrohon | very inetresting discussion | 16:59 |
| mestery | Thanks for joining the discussions this week everyone! | 16:59 |
| mestery | #endmeeting | 16:59 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:59 | |
| openstack | Meeting ended Wed Jan 15 16:59:22 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:59 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-01-15-16.00.html | 16:59 |
| nati_ueno | I wanna agree on one point now | 16:59 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-01-15-16.00.txt | 16:59 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-01-15-16.00.log.html | 16:59 |
| nati_ueno | let me remove ml2 from https://review.openstack.org/#/c/21946/ | 16:59 |
| nati_ueno | Then we can focus ml2 fix | 16:59 |
| *** IlyaE has joined #openstack-meeting-alt | 16:59 | |
| nati_ueno | rkukura: any thought? | 17:00 |
| rkukura | nati_ueno: can we discuss that on private irc or #openstack-neutron? | 17:00 |
| nati_ueno | rkukura: sure | 17:00 |
| *** coolsvap_away is now known as coolsvap | 17:00 | |
| *** rjrjr_ has joined #openstack-meeting-alt | 17:00 | |
| *** artom has joined #openstack-meeting-alt | 17:00 | |
| mugsie | hey | 17:00 |
| mugsie | whos here? | 17:00 |
| tsimmons | I am | 17:00 |
| artom | o/ | 17:00 |
| kiall | o/ | 17:01 |
| jmcbride | howdy | 17:01 |
| *** chandankumar has quit IRC | 17:01 | |
| mugsie | #startmeeting | 17:01 |
| openstack | mugsie: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee' | 17:01 |
| jmcbride | Most of the Rackspace crew will not be in the meeting today | 17:01 |
| mugsie | #startmeeting Designate | 17:01 |
| openstack | Meeting started Wed Jan 15 17:01:41 2014 UTC and is due to finish in 60 minutes. The chair is mugsie. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:01 |
| *** openstack changes topic to " (Meeting topic: Designate)" | 17:01 | |
| openstack | The meeting name has been set to 'designate' | 17:01 |
| *** hemanth__ has quit IRC | 17:01 | |
| *** Barker has quit IRC | 17:01 | |
| mugsie | so, lets have a look at the agenda | 17:01 |
| mugsie | #topic Review proposed Austin workshop details (a.k.a. 'mini-summit') | 17:02 |
| *** openstack changes topic to "Review proposed Austin workshop details (a.k.a. 'mini-summit') (Meeting topic: Designate)" | 17:02 | |
| jmcbride | Hi guys, I assembled some rough details and a registration page. | 17:02 |
| *** rcurran has quit IRC | 17:02 | |
| mugsie | #link https://etherpad.openstack.org/p/DesignateAustinWorkshop2014-01 | 17:02 |
| jmcbride | Details about the agenda can be found at https://etherpad.openstack.org/p/DesignateAustinWorkshop2014-01 | 17:02 |
| jmcbride | To register, you sign up at https://www.eventbrite.com/e/designate-development-workshop-january-2014-tickets-10180041779 | 17:03 |
| jmcbride | #link https://www.eventbrite.com/e/designate-development-workshop-january-2014-tickets-10180041779 | 17:03 |
| jmcbride | I'll get a detailed agenda together next week. | 17:03 |
| mugsie | cool, thanks jmcbride | 17:03 |
| jmcbride | So, I'd like to make sure: everyone is aware of the details | 17:04 |
| *** obondarev_ has joined #openstack-meeting-alt | 17:04 | |
| jmcbride | and if there are no objections, I'd like to send it out to the Openstack Dev mailing list | 17:04 |
| mugsie | anyone questions / comments etc? | 17:04 |
| *** akuznetsov has joined #openstack-meeting-alt | 17:04 | |
| mugsie | i think that is a good idea (mailing list) | 17:04 |
| *** Barker has joined #openstack-meeting-alt | 17:04 | |
| kiall | (Just wrapping up a call ATM ..) | 17:04 |
| mugsie | anyone have any major issue with the mailing list? | 17:05 |
| tsimmons | It'll be a good thing. | 17:05 |
| mugsie | cool, we will say that is happening then | 17:05 |
| mugsie | ok to move on? | 17:06 |
| kiall | jmcbride: no objections at all :) | 17:06 |
| jmcbride | #action send email to Openstack mailing list | 17:06 |
| mugsie | #topic Gating reviews on DevStack with MySQL and PostgreSQL (kiall) | 17:06 |
| *** openstack changes topic to "Gating reviews on DevStack with MySQL and PostgreSQL (kiall) (Meeting topic: Designate)" | 17:06 | |
| mugsie | kiall - you have the floor | 17:06 |
| kiall | Heya :) So - I wanted to give you guys a heads up about some additionall testing we're doing | 17:07 |
| kiall | We had some "complaints" on the mailing list about our PostgreSQL support being broken etc | 17:07 |
| kiall | So - I took our devstack forked, turned it into a new devstack plugin, and setup a Jenkins instance to run against mysql and postgres for every commit | 17:07 |
| kiall | #link http://15.126.220.179:8080/ | 17:08 |
| kiall | It currently lives there ^ .. It'll get a name soon | 17:08 |
| *** guestuser9490 has quit IRC | 17:08 | |
| kiall | The extracted plugin for devstack is in https://github.com/designate-dns/devstack-designate | 17:08 |
| kiall | Anyway, I think this gives us a good opportunity for better functional testing - e.g. real testing with powerdns, bind etc | 17:09 |
| *** pballand has joined #openstack-meeting-alt | 17:09 | |
| *** rakhmerov has joined #openstack-meeting-alt | 17:09 | |
| *** asomya has left #openstack-meeting-alt | 17:09 | |
| tsimmons | That'd be cool. | 17:10 |
| kiall | But - I'm wondering who's up for helping to maintain the devstack plugin, add support for bind to it, updated it to always would with the latest upstream devstack etc etc | 17:10 |
| artom | Could we start thinking about testing with Tempest? | 17:10 |
| kiall | updating* | 17:10 |
| kiall | artom: I looked at at, and I don't believe there's an easy way to "plugin" to it.. Which sucks, and makes the maintenance burden shoot up | 17:11 |
| kiall | If it's doable - great! | 17:11 |
| *** colinmcnamara has quit IRC | 17:12 | |
| *** alazarev has joined #openstack-meeting-alt | 17:12 | |
| kiall | We can do poor-mans functional testing with simple devstack exercise scirpts - https://github.com/designate-dns/devstack-designate/blob/master/exercises/designate.sh | 17:12 |
| *** IlyaE has quit IRC | 17:12 | |
| kiall | Anyway - Anyone who has submitted a review in the last few days will have noticed "me" commenting on the reviews with -1/+1 .. I have a ticke filed to get a dedicated account for that .. | 17:13 |
| kiall | ticket* | 17:13 |
| mugsie | cool. thanks kiall. Any comments / queries? | 17:14 |
| tsimmons | Good stuff, you've been crazy busy lately :P | 17:14 |
| kiall | So - Back to - who's willing to help get more functional tests (exercises, or tempest), bind support, etc written? | 17:14 |
| kiall | tsimmons: yea - we've had a lot of patches land over the last few days :) | 17:15 |
| tsimmons | I wouldn't want to speak for people, but I'd think that bind support would be something that we could help with soon. | 17:15 |
| *** colinmcnamara has joined #openstack-meeting-alt | 17:16 | |
| kiall | Cool :) I was planning on spending a few hours later this week getting it to properly standup powerdns, and some really basic functional tests | 17:17 |
| *** IlyaE has joined #openstack-meeting-alt | 17:17 | |
| tsimmons | I'd imagine we could use that as a sort of template to get something stood up. | 17:17 |
| kiall | Great :) I'll ping you guys when I have that up .. | 17:18 |
| *** IlyaE has quit IRC | 17:18 | |
| artom | "Standup" powerdns? | 17:18 |
| tsimmons | Cool. Most of my team isn't here. Well…all of them probably. I'm sure they'll have more comments. | 17:18 |
| kiall | artom: install, configure it to point at the right databases etc .. e.g. after running `./stack.sh` you should be able to issue DNS queries to 127.0.0.1 and get results | 17:18 |
| kiall | tsimmons: day off for RackSpace? :D | 17:19 |
| tsimmons | Hah, they're in some training :) I'm at school so I can't be there atm. | 17:19 |
| artom | Ah, devstack to "standup" powerdns | 17:19 |
| artom | Gotcha. | 17:19 |
| mugsie | cool | 17:19 |
| mugsie | #topic grahamhayes/dt211-SI | 17:19 |
| *** openstack changes topic to "grahamhayes/dt211-SI (Meeting topic: Designate)" | 17:19 | |
| kiall | lol | 17:20 |
| mugsie | #topic Open Disscusion | 17:20 |
| *** openstack changes topic to "Open Disscusion (Meeting topic: Designate)" | 17:20 | |
| mugsie | there we go | 17:20 |
| mugsie | anyone have anything else? | 17:20 |
| kiall | This has defiantly been one of our shortest meetings since we're real light on people here today :) | 17:21 |
| mugsie | yup | 17:21 |
| tsimmons | kiall: if you have a minute | 17:21 |
| mugsie | we call it done? | 17:21 |
| mugsie | tsimmons: go for it | 17:21 |
| tsimmons | I have some questions that aren't really relevant to the group at large about changing the storage db interactions to transactions that rollback automatically. | 17:22 |
| kiall | Ok - Sure, we could take them to the #openstack-dns room rather than having them in the meeting logs forever? ;) | 17:23 |
| tsimmons | That'd be good :) | 17:23 |
| mugsie | #endmeeting | 17:23 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 17:23 | |
| mugsie | cool | 17:23 |
| openstack | Meeting ended Wed Jan 15 17:23:20 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:23 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-01-15-17.01.html | 17:23 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-01-15-17.01.txt | 17:23 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/designate/2014/designate.2014-01-15-17.01.log.html | 17:23 |
| *** markwash has quit IRC | 17:23 | |
| mugsie | thanks everyone! | 17:23 |
| *** tsimmons has left #openstack-meeting-alt | 17:24 | |
| *** artom has left #openstack-meeting-alt | 17:24 | |
| *** nermina has quit IRC | 17:25 | |
| *** mugsie has left #openstack-meeting-alt | 17:26 | |
| *** IlyaE has joined #openstack-meeting-alt | 17:27 | |
| *** IlyaE has quit IRC | 17:30 | |
| *** IlyaE has joined #openstack-meeting-alt | 17:31 | |
| *** markwash has joined #openstack-meeting-alt | 17:32 | |
| *** rjrjr_ has quit IRC | 17:34 | |
| *** k-pom has joined #openstack-meeting-alt | 17:39 | |
| *** jmcbride has quit IRC | 17:41 | |
| *** aignatov has quit IRC | 17:42 | |
| *** jasonb365 has joined #openstack-meeting-alt | 17:43 | |
| *** nati_ueno has quit IRC | 17:45 | |
| *** cp16net has joined #openstack-meeting-alt | 17:45 | |
| *** jimbobhickville has joined #openstack-meeting-alt | 17:46 | |
| *** nati_ueno has joined #openstack-meeting-alt | 17:46 | |
| *** cweid_ has joined #openstack-meeting-alt | 17:47 | |
| *** ruhe is now known as ruhe_away | 17:49 | |
| *** rsblendido has quit IRC | 17:49 | |
| *** rsblendido has joined #openstack-meeting-alt | 17:49 | |
| *** datsun180b has joined #openstack-meeting-alt | 17:50 | |
| *** nermina has joined #openstack-meeting-alt | 17:50 | |
| *** colinmcnamara has quit IRC | 17:50 | |
| *** glucas has joined #openstack-meeting-alt | 17:51 | |
| *** jmcbride has joined #openstack-meeting-alt | 17:52 | |
| *** safchain has quit IRC | 17:53 | |
| *** safchain has joined #openstack-meeting-alt | 17:53 | |
| *** beyounn has joined #openstack-meeting-alt | 17:54 | |
| *** robertmyers has joined #openstack-meeting-alt | 17:55 | |
| *** amrith has joined #openstack-meeting-alt | 17:55 | |
| *** rsblendido has quit IRC | 17:55 | |
| *** imsplitbit has joined #openstack-meeting-alt | 17:55 | |
| *** saurabhs has joined #openstack-meeting-alt | 17:55 | |
| *** rsblendido has joined #openstack-meeting-alt | 17:55 | |
| *** RajeshMohan has quit IRC | 17:56 | |
| *** RajeshMohan has joined #openstack-meeting-alt | 17:56 | |
| *** jmcbride has quit IRC | 17:57 | |
| *** ruhe_away is now known as _ruhe | 17:58 | |
| *** rossella_s has quit IRC | 17:59 | |
| *** rsblendido has quit IRC | 17:59 | |
| *** jcru has joined #openstack-meeting-alt | 18:00 | |
| *** esp has joined #openstack-meeting-alt | 18:00 | |
| *** derekh has quit IRC | 18:00 | |
| *** amcrn has joined #openstack-meeting-alt | 18:00 | |
| hub_cap | hello folks | 18:00 |
| datsun180b | hello | 18:01 |
| imsplitbit | o/ | 18:01 |
| vipul | hello | 18:01 |
| *** NehaV has joined #openstack-meeting-alt | 18:01 | |
| robertmyers | o/ | 18:01 |
| hub_cap | #startmeeting trove | 18:01 |
| openstack | Meeting started Wed Jan 15 18:01:44 2014 UTC and is due to finish in 60 minutes. The chair is hub_cap. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:01 |
| *** openstack changes topic to " (Meeting topic: trove)" | 18:01 | |
| cweid_ | o/ | 18:01 |
| openstack | The meeting name has been set to 'trove' | 18:01 |
| robertmyers | o/ | 18:01 |
| hub_cap | so um | 18:01 |
| amcrn | o/ | 18:01 |
| pdmars | o/ | 18:02 |
| datsun180b | we had one item on the agenda but | 18:02 |
| esp | o/ | 18:02 |
| kevinconway | #help | 18:02 |
| *** cweid_ has quit IRC | 18:02 | |
| kevinconway | awe... | 18:02 |
| hub_cap | our meeting agenda is nil | 18:02 |
| kevinconway | o/ | 18:02 |
| *** SlickNik has joined #openstack-meeting-alt | 18:02 | |
| *** cweid has joined #openstack-meeting-alt | 18:02 | |
| datsun180b | since grapex isn't here to talk to it it's not fair to debate and decide without him | 18:02 |
| cweid | o/ | 18:02 |
| SlickNik | o/ | 18:02 |
| *** bdpayne has joined #openstack-meeting-alt | 18:03 | |
| cp16net | o/ | 18:03 |
| *** balajiiyer has left #openstack-meeting-alt | 18:03 | |
| vipul | hello | 18:03 |
| hub_cap | so what shall we talk about! | 18:03 |
| juice | o/ | 18:04 |
| jimbobhickville | I had one thing I was about to bring up on the email list but maybe we can discuss it here first? | 18:04 |
| robertmyers | Incremental backups? | 18:04 |
| datsun180b | did you see that ludicrous display last night? | 18:04 |
| denis_makogon | o/ | 18:04 |
| hub_cap | jimbobhickville: lets do | 18:04 |
| jimbobhickville | https://wiki.openstack.org/wiki/Trove/scheduled-tasks | 18:04 |
| SlickNik | go for it jimbobhickville | 18:04 |
| jimbobhickville | there's part of the spec about sending success/failure notifications to customers in relation to scheduled tasks like backups | 18:05 |
| hub_cap | #topic task notifications | 18:05 |
| *** openstack changes topic to "task notifications (Meeting topic: trove)" | 18:05 | |
| jimbobhickville | I think really trove should just emit a message indicating the information and let an external program like ceilometer consume the message and handle the notification part | 18:05 |
| kevinconway | datsun180b: the thing about arsenal is they always try to walk it in | 18:05 |
| *** dguitarbite has quit IRC | 18:05 | |
| kevinconway | jimbobhickville: +1 | 18:06 |
| *** michael-yu has joined #openstack-meeting-alt | 18:06 | |
| robertmyers | jimbobhickville: notifications sound great | 18:06 |
| denis_makogon | mqaas has BP for notifications | 18:06 |
| datsun180b | yes let's do | 18:06 |
| kevinconway | #link https://github.com/openstack/trove/blob/f18e0936264b6dd96ddacc7594b661b50de1729f/trove/taskmanager/models.py#L66 | 18:07 |
| kevinconway | we have a mixing for sending events | 18:07 |
| jimbobhickville | that's basically it, just wanted to run it by the group before I ripped out all the logic for storing the notification data in the database in my branch | 18:07 |
| hub_cap | jimbobhickville: ++ to just emitting a msg | 18:07 |
| robertmyers | kevinconway: for usage correct | 18:07 |
| *** doug_shelley66 has joined #openstack-meeting-alt | 18:08 | |
| hub_cap | jimbobhickville: heh | 18:09 |
| hub_cap | rip that shiz out | 18:09 |
| jimbobhickville | alrighty, I'll update the blueprint later today to reflect the desired functionality | 18:09 |
| vipul | yep agreed, notifications should just be emittted, no need to store them | 18:09 |
| hub_cap | trove dont care about storing it | 18:09 |
| cp16net | i think adding a new message makes sense | 18:09 |
| hub_cap | cp16net: too late for input its been decided (i kid) | 18:09 |
| denis_makogon | guys, gate is broken ... | 18:09 |
| SlickNik | +1 to not storing notifications. | 18:09 |
| denis_makogon | i just find out it | 18:09 |
| cp16net | ahhh | 18:09 |
| hub_cap | denis_makogon: is that worth a topic? | 18:09 |
| SlickNik | denis_makogon: What do you mean, do you have a link? | 18:09 |
| hub_cap | denis_makogon: maybe put that in the #openstack-trove channel guys | 18:10 |
| hub_cap | so we can do meeting here | 18:10 |
| denis_makogon | sorry for off-topic | 18:10 |
| hub_cap | np | 18:10 |
| hub_cap | so jimbobhickville you good to go? | 18:10 |
| jimbobhickville | yep, I'm good | 18:11 |
| hub_cap | ok awesome. | 18:11 |
| hub_cap | #topic open discussion | 18:11 |
| *** openstack changes topic to "open discussion (Meeting topic: trove)" | 18:11 | |
| SlickNik | Will look into the gate as soon as the meeting is done. | 18:11 |
| *** michael-yu has left #openstack-meeting-alt | 18:11 | |
| *** nadya_ has joined #openstack-meeting-alt | 18:11 | |
| *** michael-yu has joined #openstack-meeting-alt | 18:12 | |
| SlickNik | I didn't get a chance to schedule the tempest meeting as yet. | 18:12 |
| SlickNik | Will do it this week. | 18:12 |
| vipul | wrt replication / cluster api.. we seemed to have agreement that replicaiton would be two separate calls, first to create the master, another to create a slave that points to the master | 18:12 |
| vipul | imsplitbit: is that the approach you were taking | 18:12 |
| SlickNik | So please keep an eye out on the mailing list for that. | 18:12 |
| vipul | and is Heat a requirement for implemention master/slave | 18:13 |
| *** sarob has joined #openstack-meeting-alt | 18:13 | |
| imsplitbit | vipul: yes | 18:14 |
| vipul | or were you going to just add that logic to Taskmanager | 18:14 |
| imsplitbit | this is what we discussed | 18:14 |
| *** nati_ueno has quit IRC | 18:14 | |
| imsplitbit | and is the assumption I am operating on | 18:14 |
| *** nati_ueno has joined #openstack-meeting-alt | 18:14 | |
| hub_cap | vipul: imsplitbit i hate to say it | 18:14 |
| *** colinmcnamara has joined #openstack-meeting-alt | 18:14 | |
| hub_cap | but im on the fence still in some sort (if we can consolidate it) | 18:14 |
| hub_cap | i think itll be easier once one of the apis is created | 18:14 |
| *** arnaud__ has joined #openstack-meeting-alt | 18:15 | |
| *** arnaud___ has joined #openstack-meeting-alt | 18:15 | |
| *** michael-yu has left #openstack-meeting-alt | 18:15 | |
| hub_cap | but imsplitbits assumption is valid for now | 18:15 |
| hub_cap | :) | 18:15 |
| vipul | hmm ok.. we might pick up the implementation soon so maybe we'll need to adjust it during review | 18:15 |
| amcrn | vipul imsplitbit can we get a rundown of the assumptions and talking points made this past week wrt clusters/topologies? | 18:15 |
| vipul | what about Heat? | 18:15 |
| amcrn | (over mailing list preferably) | 18:16 |
| vipul | Sure we can do that | 18:16 |
| imsplitbit | one quick note here is I am *not* writing a datastore impl | 18:16 |
| imsplitbit | I am hooking in metadata into the instance object | 18:16 |
| vipul | Ok, so purely an API change -- no code to actually look into the metadata and act on it | 18:17 |
| imsplitbit | correct | 18:18 |
| imsplitbit | then I'll hook in the validation for the replication contract descriptive language | 18:18 |
| *** rsblendido has joined #openstack-meeting-alt | 18:18 | |
| *** rossella_s has joined #openstack-meeting-alt | 18:18 | |
| imsplitbit | at that point someone can write a datastore impl | 18:18 |
| denis_makogon | imsplitbit, of course | 18:19 |
| denis_makogon | it IH release we could have mongo and mysql replicas | 18:19 |
| vipul | so is there a stance on Heat for provisioning? should all new provisioning code go through Heat, and only support a single code path | 18:20 |
| hub_cap | denis_makogon: that might be a stretch :) | 18:21 |
| imsplitbit | I would say that for better or worse heat is intended to do all that stuff | 18:21 |
| imsplitbit | I've had a few convos with heat devs | 18:21 |
| amcrn | vipul to be clear, when you say provisioning you're only referring to creation/launching, not the modification of, correct? | 18:21 |
| hub_cap | heat should be doing the provisioning work | 18:21 |
| imsplitbit | all so far have asked "now wait... *why* are you using heat for that?" | 18:21 |
| denis_makogon | vipul, i assume that we would use only heat | 18:21 |
| vipul | amcrn: I would assume modification of the stack as well, not necessarily of an instance | 18:21 |
| hub_cap | imsplitbit: we dont have a choice | 18:22 |
| imsplitbit | but that's not within the realm of things I care enough to even investigate to formulate an informed desicion | 18:22 |
| hub_cap | vipul: amcrn yes to grow/shrink a stack | 18:22 |
| vipul | amcrn: so stack-create may create 1 master node.. if we go with the 2 api call approach | 18:22 |
| denis_makogon | i'm working on heat and search for missing funcs for trove | 18:22 |
| imsplitbit | hence my previous statement hub_cap :) | 18:22 |
| vipul | then we'd do stack update to add slave | 18:22 |
| hub_cap | but first we need to solve resize + heat + trove it hink | 18:22 |
| imsplitbit | hub_cap: yep | 18:22 |
| demorris | how will slave promotion work? | 18:22 |
| denis_makogon | stack create could handle instance group provisioning | 18:22 |
| amcrn | vipul thanks for the clarification | 18:22 |
| demorris | both manually, and automated, in the event of a failed master | 18:23 |
| vipul | demorris: I believe there shoudl be an API for that | 18:23 |
| vipul | removal of the metadata "replicates_from" on a slave instance would promote it | 18:23 |
| vipul | automated... | 18:23 |
| demorris | vipul: cool | 18:23 |
| demorris | but that is a bit obscure ihmo | 18:23 |
| *** IlyaE has quit IRC | 18:24 | |
| *** michael-yu has joined #openstack-meeting-alt | 18:24 | |
| imsplitbit | vipul: correct | 18:24 |
| *** nadya_ has quit IRC | 18:24 | |
| demorris | vs a call that says promote or promotToMaster and removes the replicates_from | 18:24 |
| vipul | we would likely need another component 'observer' or something that watches the states reported (or not reported) by guest agents | 18:24 |
| *** mpolanco has joined #openstack-meeting-alt | 18:24 | |
| *** NehaV has quit IRC | 18:24 | |
| vipul | there are better ways to do this.. by introducing 3rd party things that would watch a master/slave pair | 18:25 |
| vipul | but in the context of Trove, we probably would have to rely on the status of the guests themselves | 18:25 |
| imsplitbit | vipul: yes | 18:25 |
| vipul | it would be more polling, but don't knkow of a better way | 18:25 |
| imsplitbit | the health or replication, wrt mysql, is something that *must* be queried actively from the replicants | 18:26 |
| SlickNik | vipul: is this so that we can watch the status to ensure that replication is healthy? | 18:26 |
| vipul | right | 18:26 |
| imsplitbit | therefore it is data that would have to bubble up from the guest agent | 18:26 |
| imsplitbit | or a client connection | 18:26 |
| jimbobhickville | I agree with demorris that we should have a convenience API to make the process easier to grok | 18:26 |
| hub_cap | yea lets get a clustering api working before we solve this guys :) | 18:26 |
| kevinconway | could you not add replication/cluster health to the heartbeat? | 18:26 |
| imsplitbit | I don't disagree with making it easier | 18:26 |
| vipul | so it's likely that most of the time when there is a failure, there won't be a status from the guest heartbeat.. absense of a heartbeat | 18:27 |
| jimbobhickville | no, we must solve everything and do nothing | 18:27 |
| jimbobhickville | :P | 18:27 |
| imsplitbit | but before we build the lego castle we first need the lego no? | 18:27 |
| *** bdpayne has quit IRC | 18:27 | |
| vipul | which will be difficult to determine why a heartbeat was missing, was it cuz gueatagent died... was it cuz instance died.. | 18:27 |
| demorris | i am fine with get manual promotion working first | 18:27 |
| kevinconway | vipul: wouldn't both indicate a problem with the node though? | 18:27 |
| SlickNik | kevinconway: You could, but I think the observer needs to be actively observing it to automate any slave-promotion scenarios (on an unhealthy master, for instance). | 18:28 |
| vipul | kevinconway: sure, but guestagent being down doesn't mean mysql is down | 18:28 |
| imsplitbit | kevinconway: yes but not necessarily a problem with replication | 18:28 |
| kevinconway | but if the guest is down then we have no control over the db or the instance anymore | 18:28 |
| vipul | kevinconway: it could lead to premature slave promotions | 18:28 |
| kevinconway | shouldn't it be pruned from the set for that reason? | 18:28 |
| imsplitbit | vipul: +100000000 | 18:28 |
| vipul | kevinconway: yea that's one way to look at it.. we can't actively manage it.. so maybe a promotion is justified.. but not a good experience for the user | 18:29 |
| kevinconway | can we call it a rogue master. is that an oxymoron? | 18:29 |
| hub_cap | so a shutdown message that came to conductor 2s ago, which has been shutdown for the last few msgs, indicates mysql is failed, act upon it, via the guest | 18:29 |
| hub_cap | no communciation to conductor means the guest is down, there is nothing we can do | 18:30 |
| hub_cap | so i dont think we need to program to #2 yet | 18:30 |
| denis_makogon | agreed | 18:30 |
| hub_cap | lets focus on #1 when we go down this route | 18:30 |
| jimbobhickville | agreed | 18:30 |
| imsplitbit | I can't wait until we're circularly promoting slaves infinitely | 18:30 |
| imsplitbit | :) | 18:30 |
| SlickNik | +1 to focusing on the API first. | 18:30 |
| hub_cap | imsplitbit: hehehe yes, yes it will | 18:30 |
| denis_makogon | since we have heartbeat timeout we could totally say that guest is down | 18:30 |
| vipul | i was hoping heat would be able to to act on this kind of stuff... but i don't think it's possible to feed in our states | 18:31 |
| hub_cap | imsplitbit: if we promote them at different intervals we can eventually detect a cycle, right ;) | 18:31 |
| vipul | w/o sending those through ceilometer or something | 18:31 |
| vipul | anywya, since heat is something we'll need, there is a bunch of stuff missing in the current heat integration | 18:32 |
| vipul | like keeping track of the 'stack id' | 18:32 |
| imsplitbit | there are definitely valid rules that need to be wrapped around this yet. I just want to make sure that we first have the ability to accurately describe that one instances data is being replicated to another before we try to solve how you stop a rogue master and circular replication slave promotion :) | 18:32 |
| denis_makogon | vipul, i'm working on that (traking stack id) | 18:33 |
| vipul | imsplitbit: agree, good to know we're all on the same track | 18:33 |
| imsplitbit | definitely | 18:33 |
| vipul | denis_makogon: cool | 18:33 |
| denis_makogon | there is a plan to keep trove simple and make heat quite smart | 18:33 |
| *** nati_ueno has quit IRC | 18:34 | |
| denis_makogon | there are already bunch of BPs for that | 18:34 |
| vipul | denis_makogon: sure, i think there are integrations with a lot of different things required to get to that point (i.e. Ceilometer) | 18:34 |
| *** nati_ueno has joined #openstack-meeting-alt | 18:34 | |
| demorris | so what of the API discussion with replication and slave promotion..are Greg and I the only ones who think that an explicit API call is needed for these, rather than just setting or modifying metadata? | 18:34 |
| denis_makogon | #link https://blueprints.launchpad.net/heat/+spec/search-stack-by-resource-id | 18:34 |
| denis_makogon | #link https://blueprints.launchpad.net/heat/+spec/search-resource-by-physical-resource-id | 18:35 |
| *** NehaV has joined #openstack-meeting-alt | 18:35 | |
| vipul | demorris: i don't think a separate call should be introduced.. it really is an update to an existing resource | 18:35 |
| *** harlowja has joined #openstack-meeting-alt | 18:36 | |
| jimbobhickville | it would just be a convenience method to make it simpler for users | 18:36 |
| vipul | we may want to add to the metadata.. and explicitly introduce a 'type' = slave or something | 18:36 |
| amcrn | to be honest, without a specification or quick walkthrough via bp/wiki, it's hard to objectively say one approach is better than the other; the devil is in the details. | 18:36 |
| imsplitbit | I get skittish about "convenience" methods | 18:36 |
| demorris | in the current design, how does it work if I have a single master and I want to add a slave? | 18:37 |
| vipul | amcrn: https://wiki.openstack.org/wiki/Trove-Replication-And-Clustering-API | 18:37 |
| jimbobhickville | ok, I don't. I think making the API easy to use is the primary concern | 18:37 |
| imsplitbit | but we should first examine how the existing proposal is hard and see if we can simplify that | 18:37 |
| vipul | amcrn: at the very bottom | 18:37 |
| kevinconway | jimbobhickville: i think "convenience method" could also be called "application" | 18:37 |
| amcrn | vipul: isn't this outdated? | 18:37 |
| *** jmcbride has joined #openstack-meeting-alt | 18:37 | |
| demorris | I have a single instance and its my master and I want to create a slave of it, but no other instances exist | 18:37 |
| imsplitbit | demorris: the current proposal is to change the metadata of the resource | 18:37 |
| imsplitbit | that triggers the needful | 18:37 |
| vipul | imsplitbit, amcrn: this is the only one i know of https://wiki.openstack.org/wiki/Trove-Replication-And-Clustering-API -- is this what you're working off of? | 18:38 |
| imsplitbit | vipul: yep | 18:38 |
| *** IlyaE has joined #openstack-meeting-alt | 18:38 | |
| demorris | can I create a new instance and have it be a slave of the master in a single operation? | 18:38 |
| imsplitbit | if there is anything that is missing then lets iron it out | 18:38 |
| demorris | or do I have to do multiple operations | 18:38 |
| imsplitbit | cause if this changes again I may commit seppuku | 18:38 |
| vipul | demorris: it's a single operation to create a slave instance and have it start replicating | 18:38 |
| demorris | i think it should be an atomic operation for the user | 18:38 |
| hub_cap | lol imsplitbit | 18:39 |
| *** harlowja_away has quit IRC | 18:39 | |
| demorris | vipul: okay cool | 18:39 |
| vipul | demorris: it's 2 operations to create a master+ slave | 18:39 |
| amcrn | vipul: maybe i've just had these conversations in my head (quite possible), but i swear i remember talking about things like replicates_from being non-sensical from a NoSQL perspective, and a couple of other things | 18:39 |
| amcrn | i mean the examples still have service_type vs. datastore, it's very mysql-centric | 18:40 |
| imsplitbit | amcrn: it may for some datastores yes? | 18:40 |
| imsplitbit | how does that not apply to say redis? | 18:40 |
| jimbobhickville | sorry, I thought we were talking about promoting a slave, and it sounded like it was two separate operations to promote the slave and demote the master, and I thought a single atomic convenience method made sense for that operation | 18:40 |
| imsplitbit | or postgres? | 18:40 |
| kevinconway | does mongo only do master-master replication? | 18:40 |
| imsplitbit | perhaps redundant | 18:40 |
| amcrn | right, but the api schema should not wildly change depending upon the datastore; it's possible to construct terms/structures that are fairly agnostic | 18:41 |
| demorris | kevinconway: mongodb does replica sets | 18:41 |
| imsplitbit | I don't think the verbiage was ever accepted | 18:41 |
| imsplitbit | I was gonna hook in metadata and then ML the replicaton contract verbiage | 18:41 |
| vipul | what was the suggested alternative? i don't remember the details of that | 18:41 |
| imsplitbit | I don't know that there were vipul | 18:42 |
| *** jmcbride has quit IRC | 18:42 | |
| imsplitbit | I remember hearing that replicates_from didn't make sense | 18:42 |
| *** yogesh has joined #openstack-meeting-alt | 18:42 | |
| imsplitbit | but there needs to be a way to describe a bidirectional replication contract imo | 18:42 |
| amcrn | imsplitbit: just to make sure: so i can take that wiki as the source of truth for the current state of the proposal, and iterate on it (by sending thoughts to ML, etc.)? | 18:42 |
| imsplitbit | that is the basis on which I am operating amcrn | 18:43 |
| kevinconway | amcrn: the bigger the changes the better | 18:43 |
| SlickNik | IIRC, the master-master replication scenarios for other datastore types were going to be handled by the clustering API (using a master-master cluster type) | 18:43 |
| *** jmcbride has joined #openstack-meeting-alt | 18:43 | |
| *** jmcbride has quit IRC | 18:43 | |
| imsplitbit | SlickNik: I don't know that that is a great idea but I'm not prepared to argue it right now :D | 18:44 |
| vipul | also it is metadata, we need to figure out how much flexibility we want to add to that | 18:44 |
| imsplitbit | vipul: +1 | 18:44 |
| vipul | because i don't think there will be a verb that makes sense for all use cases | 18:44 |
| SlickNik | imsplitbit: I'm not arguing for it either. It was just something that was brought up in a different conversation earlier. | 18:44 |
| imsplitbit | so *no* work has been put into the replication contract language. the proposal I believe includes some jumping off points | 18:44 |
| amcrn | vipul imsplitbit i remember bringing up handling metadata like glance (w/ its pros and cons) | 18:45 |
| imsplitbit | SlickNik: possibly I don't really recall | 18:45 |
| hub_cap | amcrn: imsplitbit any changes to the wiki should be ok'd by the group at this point | 18:45 |
| imsplitbit | yeah for sure | 18:45 |
| hub_cap | amrith: u following this? :) | 18:45 |
| kevinconway | imsplitbit: is that a DSL for replication? i feel like i missed that bit. | 18:46 |
| amcrn | alright, cool, glad to see this is gaining some mindshare/traction again, let me reacquaint mysql with the wiki and start collecting my thoughts. | 18:46 |
| amcrn | lol, mysql = myself* | 18:46 |
| vipul | amcrn: i will dig out the email thread you had started, must have missed some of this stuff | 18:46 |
| doug_shelley66 | we are following along | 18:46 |
| imsplitbit | kevinconway: we have said we lack sufficient discussion on the dsl | 18:46 |
| imsplitbit | so that is forthcoming | 18:46 |
| SlickNik | imsplitbit: I'm perfectly fine with not handling that until we have a working replication API for the mysql datastore. | 18:46 |
| hub_cap | amcrn: lol at that slip | 18:46 |
| SlickNik | lol amcrn | 18:46 |
| hub_cap | imsplitbit: likes to say dsl cuz it sounds like dsal | 18:46 |
| kevinconway | imsplitbit: I hear HEAT has a great DSL for describing configurations of things. | 18:46 |
| hub_cap | hahaha kevinconway | 18:47 |
| imsplitbit | I don't know why we're doing anything, just tell heat to do it! | 18:47 |
| imsplitbit | :) | 18:47 |
| denis_makogon | kevinconway, somehow yes | 18:47 |
| hub_cap | ok so.. do we all have a understanding of whats going on w/ clustering currently? | 18:47 |
| imsplitbit | replication yes | 18:47 |
| amrith | hub_cap: yes ... | 18:47 |
| denis_makogon | until heat guys will say DIY | 18:47 |
| imsplitbit | clustering we haven't even talked about | 18:47 |
| kevinconway | it sounds like we need to totally redo the wiki | 18:47 |
| hub_cap | imsplitbit: :O | 18:47 |
| hub_cap | semantics ;) | 18:48 |
| imsplitbit | but I believe we've sync'd back up now on metadata and replication | 18:48 |
| vipul | we should try to nail this stuff down soon.. so folks can get some of the cooler things added to trove | 18:48 |
| *** nadya_ has joined #openstack-meeting-alt | 18:49 | |
| imsplitbit | vipul: +1 | 18:49 |
| imsplitbit | I should be done with metadata soon | 18:49 |
| *** dprince has quit IRC | 18:49 | |
| imsplitbit | hooking it into SimpleInstance now | 18:49 |
| hub_cap | s/hook/hack | 18:49 |
| imsplitbit | for sure | 18:49 |
| imsplitbit | :) | 18:49 |
| hub_cap | :P | 18:49 |
| imsplitbit | then we can tear that apart and make it right | 18:50 |
| imsplitbit | and then work on replication | 18:50 |
| hub_cap | ok so anything not related to clustering/replication? | 18:50 |
| *** lsmola has joined #openstack-meeting-alt | 18:50 | |
| hub_cap | SlickNik: did u mention a testing update? | 18:50 |
| imsplitbit | man and I wasn't even *on* the agenda | 18:50 |
| amrith | vipul: looking at the document (https://wiki.openstack.org/wiki/Trove-Replication-And-Clustering-API) referenced above, I think there's a serious set of issue around the fact that fundamentally Trove wishes to support both RDBMS and NoSQL DBMS. And each one has a different interpretation of "which way is up" | 18:50 |
| *** julienvey_ has quit IRC | 18:50 | |
| vipul | amrith: Yea we do want to create an API that supports both types of datastores, which is why this is much harder to do than it seemed | 18:51 |
| kevinconway | we should probably drop mongo support… denis_makogon | 18:51 |
| SlickNik | hub_cap: I'm still waiting for a couple of patches to merge into infra. | 18:51 |
| hub_cap | amcrn: heh | 18:51 |
| denis_makogon | amrith, it's funny but NoSQL Cassandra perfectly fits to replication design)))) | 18:51 |
| amrith | kevinconway: :) | 18:51 |
| *** Duane has joined #openstack-meeting-alt | 18:51 | |
| *** IlyaE has quit IRC | 18:52 | |
| SlickNik | hub_cap: I've gotten started on writing basic services for trove in tempest. | 18:52 |
| denis_makogon | kevinconway, yes, sounds like, oh way, it sounds like bad idea, lol | 18:52 |
| demorris | there are lots of similarities in describing clusters of NoSQL and SQL data stores, I don't see that as the big issue on the surface from an API perspective | 18:52 |
| SlickNik | #action: SlickNik to schedule some time to talk about tempest testing in openstack-trove and send an update out on the ML | 18:52 |
| denis_makogon | good idea | 18:53 |
| SlickNik | That's all I have for now. | 18:53 |
| amcrn | i've got a few things on making devstack/redstack easier for new contributors, plus getting a management-cli out in the public and consumable; but that's for next week. | 18:54 |
| hub_cap | amrith: i think we have to address your concerns outside this meeting | 18:54 |
| amrith | denis_makogon: I don't understand the proposal for repl fully yet so will get back to you later. | 18:54 |
| amrith | hub_cap: I have a lot to understand of the proposal | 18:54 |
| amrith | will do as you recommend; outside mth | 18:55 |
| amrith | s/mth/mtg/ | 18:55 |
| hub_cap | amrith: i think we all have a lot to discover about the proposal | 18:55 |
| hub_cap | and at best its a proposal currently hehe | 18:55 |
| denis_makogon | are we done for the meeting ? | 18:56 |
| *** bdpayne has joined #openstack-meeting-alt | 18:57 | |
| kevinconway | maybe we should talk about the specifics of clustering api with our remaining 2.5 minutes | 18:57 |
| imsplitbit | kevinconway: I will find you | 18:58 |
| imsplitbit | :) | 18:58 |
| hub_cap | LOL kevinconway | 18:58 |
| *** sarob has quit IRC | 18:58 | |
| hub_cap | #topic make kevinconway our official master of ceremonies | 18:58 |
| *** openstack changes topic to "make kevinconway our official master of ceremonies (Meeting topic: trove)" | 18:58 | |
| jimbobhickville | concur! | 18:58 |
| denis_makogon | lol | 18:58 |
| *** sarob has joined #openstack-meeting-alt | 18:58 | |
| hub_cap | whoops that was supposed to be an action | 18:58 |
| *** colinmcnamara has quit IRC | 18:58 | |
| hub_cap | not a topic change | 18:59 |
| hub_cap | HAHAHAAH | 18:59 |
| *** eharney has quit IRC | 18:59 | |
| hub_cap | ok were done | 18:59 |
| hub_cap | #endmeeting | 18:59 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 18:59 | |
| openstack | Meeting ended Wed Jan 15 18:59:22 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:59 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-01-15-18.01.html | 18:59 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-01-15-18.01.txt | 18:59 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/trove/2014/trove.2014-01-15-18.01.log.html | 18:59 |
| amrith | toodles | 18:59 |
| cp16net | peace | 18:59 |
| *** robertmyers has left #openstack-meeting-alt | 18:59 | |
| *** datsun180b has left #openstack-meeting-alt | 18:59 | |
| *** jimbobhickville has left #openstack-meeting-alt | 19:00 | |
| *** amcrn is now known as [a]mcrn | 19:00 | |
| *** imsplitbit has left #openstack-meeting-alt | 19:00 | |
| *** pcm_ has joined #openstack-meeting-alt | 19:00 | |
| *** IlyaE has joined #openstack-meeting-alt | 19:00 | |
| *** jasonb365_ has joined #openstack-meeting-alt | 19:02 | |
| *** sarob has quit IRC | 19:03 | |
| *** jasonb365 has quit IRC | 19:04 | |
| *** jasonb365_ is now known as jasonb365 | 19:04 | |
| *** jcoufal has joined #openstack-meeting-alt | 19:06 | |
| *** harlowja_ has joined #openstack-meeting-alt | 19:07 | |
| *** sarob has joined #openstack-meeting-alt | 19:07 | |
| *** dprince has joined #openstack-meeting-alt | 19:09 | |
| *** pballand has quit IRC | 19:10 | |
| *** harlowja has quit IRC | 19:10 | |
| *** colinmcnamara has joined #openstack-meeting-alt | 19:10 | |
| *** [a]mcrn is now known as amcrn | 19:12 | |
| *** roshanagr has joined #openstack-meeting-alt | 19:16 | |
| *** pcm_ has left #openstack-meeting-alt | 19:17 | |
| *** pballand has joined #openstack-meeting-alt | 19:17 | |
| *** gokrokve has quit IRC | 19:18 | |
| *** nadya_ has quit IRC | 19:18 | |
| *** gokrokve has joined #openstack-meeting-alt | 19:19 | |
| *** roshanagr has left #openstack-meeting-alt | 19:19 | |
| *** gokrokve has quit IRC | 19:23 | |
| *** nadya_ has joined #openstack-meeting-alt | 19:23 | |
| *** _ruhe is now known as ruhe | 19:24 | |
| *** cp16net has left #openstack-meeting-alt | 19:24 | |
| *** sarob has quit IRC | 19:25 | |
| *** sarob has joined #openstack-meeting-alt | 19:25 | |
| *** jmcbride has joined #openstack-meeting-alt | 19:26 | |
| *** jtomasek has quit IRC | 19:27 | |
| *** songole has joined #openstack-meeting-alt | 19:28 | |
| *** songole has left #openstack-meeting-alt | 19:28 | |
| *** nati_uen_ has joined #openstack-meeting-alt | 19:28 | |
| *** sarob has quit IRC | 19:30 | |
| *** jmcbride has quit IRC | 19:30 | |
| *** gokrokve has joined #openstack-meeting-alt | 19:31 | |
| *** nati_uen_ has quit IRC | 19:31 | |
| *** nati_ueno has quit IRC | 19:31 | |
| *** nati_ueno has joined #openstack-meeting-alt | 19:32 | |
| *** jmcbride has joined #openstack-meeting-alt | 19:33 | |
| *** gokrokve has quit IRC | 19:34 | |
| *** gokrokve has joined #openstack-meeting-alt | 19:34 | |
| *** tanisdl has joined #openstack-meeting-alt | 19:37 | |
| *** sarob has joined #openstack-meeting-alt | 19:38 | |
| *** amcrn has joined #openstack-meeting-alt | 19:38 | |
| *** IlyaE has quit IRC | 19:38 | |
| *** eharney has joined #openstack-meeting-alt | 19:39 | |
| *** gokrokve has quit IRC | 19:39 | |
| *** coolsvap is now known as coolsvap_away | 19:40 | |
| *** jmcbride has quit IRC | 19:40 | |
| *** mpolanco1 has joined #openstack-meeting-alt | 19:41 | |
| *** jaypipes has joined #openstack-meeting-alt | 19:41 | |
| *** colinmcnamara has quit IRC | 19:41 | |
| *** mpolanco1 has quit IRC | 19:41 | |
| *** mpolanco2 has joined #openstack-meeting-alt | 19:41 | |
| *** mpolanco has quit IRC | 19:44 | |
| *** RajeshMohan has quit IRC | 19:44 | |
| *** RajeshMohan has joined #openstack-meeting-alt | 19:44 | |
| *** michael-yu has quit IRC | 19:45 | |
| *** sballe_ has joined #openstack-meeting-alt | 19:47 | |
| *** sarob has quit IRC | 19:48 | |
| *** sballe has quit IRC | 19:48 | |
| *** sarob has joined #openstack-meeting-alt | 19:48 | |
| *** mpolanco has joined #openstack-meeting-alt | 19:52 | |
| *** mpolanco2 has quit IRC | 19:52 | |
| *** sarob has quit IRC | 19:52 | |
| *** vipul is now known as vipul-away | 19:57 | |
| *** vipul-away is now known as vipul | 19:57 | |
| *** Barker has quit IRC | 19:59 | |
| *** alazarev has quit IRC | 20:00 | |
| *** jasonb365 has quit IRC | 20:00 | |
| *** IlyaE has joined #openstack-meeting-alt | 20:02 | |
| *** sarob has joined #openstack-meeting-alt | 20:03 | |
| *** Barker has joined #openstack-meeting-alt | 20:04 | |
| *** gokrokve has joined #openstack-meeting-alt | 20:05 | |
| *** baoli has quit IRC | 20:06 | |
| *** alazarev has joined #openstack-meeting-alt | 20:06 | |
| *** NehaV1 has joined #openstack-meeting-alt | 20:07 | |
| *** NehaV has quit IRC | 20:08 | |
| *** IlyaE has quit IRC | 20:09 | |
| *** julienvey_ has joined #openstack-meeting-alt | 20:10 | |
| *** mpolanco has quit IRC | 20:11 | |
| *** vipul is now known as vipul-away | 20:13 | |
| *** denis_makogon_ has joined #openstack-meeting-alt | 20:13 | |
| *** denis_makogon has quit IRC | 20:14 | |
| *** denis_makogon_ is now known as denis_makogon | 20:14 | |
| *** dmakogon_ has joined #openstack-meeting-alt | 20:14 | |
| *** jmcbride has joined #openstack-meeting-alt | 20:15 | |
| *** IlyaE has joined #openstack-meeting-alt | 20:16 | |
| *** IlyaE has quit IRC | 20:17 | |
| *** NehaV1 has quit IRC | 20:19 | |
| *** derekh has joined #openstack-meeting-alt | 20:19 | |
| *** mpolanco has joined #openstack-meeting-alt | 20:20 | |
| *** doug_shelley66 has quit IRC | 20:21 | |
| *** nati_uen_ has joined #openstack-meeting-alt | 20:26 | |
| *** nati_uen_ has quit IRC | 20:26 | |
| *** nati_uen_ has joined #openstack-meeting-alt | 20:27 | |
| *** glucas has left #openstack-meeting-alt | 20:27 | |
| *** ruhe is now known as _ruhe | 20:28 | |
| *** nati_ueno has quit IRC | 20:29 | |
| *** aignatov has joined #openstack-meeting-alt | 20:30 | |
| *** NehaV has joined #openstack-meeting-alt | 20:31 | |
| *** sarob_ has joined #openstack-meeting-alt | 20:32 | |
| *** sarob_ has quit IRC | 20:32 | |
| *** Barker has quit IRC | 20:32 | |
| *** sarob_ has joined #openstack-meeting-alt | 20:33 | |
| *** amrith has quit IRC | 20:33 | |
| *** rkukura has left #openstack-meeting-alt | 20:33 | |
| *** amrith has joined #openstack-meeting-alt | 20:34 | |
| *** Barker has joined #openstack-meeting-alt | 20:34 | |
| *** nermina has quit IRC | 20:35 | |
| *** sarob has quit IRC | 20:35 | |
| *** sarob_ has quit IRC | 20:35 | |
| *** nermina has joined #openstack-meeting-alt | 20:35 | |
| *** sarob has joined #openstack-meeting-alt | 20:35 | |
| *** jmcbride has quit IRC | 20:35 | |
| *** coolsvap_away has quit IRC | 20:39 | |
| *** sarob has quit IRC | 20:40 | |
| *** jmcbride has joined #openstack-meeting-alt | 20:43 | |
| *** IlyaE has joined #openstack-meeting-alt | 20:44 | |
| *** lsmola has left #openstack-meeting-alt | 20:46 | |
| *** lsmola has joined #openstack-meeting-alt | 20:46 | |
| *** vipul-away is now known as vipul | 20:49 | |
| *** HenryG has joined #openstack-meeting-alt | 20:52 | |
| *** harlowja_ is now known as harlowja_away | 20:59 | |
| *** julienvey_ has quit IRC | 21:01 | |
| *** bdpayne has quit IRC | 21:04 | |
| *** mrda has joined #openstack-meeting-alt | 21:06 | |
| *** mattgriffin has joined #openstack-meeting-alt | 21:06 | |
| *** mrda has left #openstack-meeting-alt | 21:07 | |
| *** SergeyLukjanov is now known as SergeyLukjanov_ | 21:08 | |
| *** dprince has quit IRC | 21:10 | |
| *** nati_ueno has joined #openstack-meeting-alt | 21:15 | |
| *** nati_ueno has quit IRC | 21:16 | |
| *** nati_ueno has joined #openstack-meeting-alt | 21:16 | |
| *** derekh has quit IRC | 21:18 | |
| *** nati_uen_ has quit IRC | 21:19 | |
| *** mpolanco has quit IRC | 21:21 | |
| *** saurabhs has left #openstack-meeting-alt | 21:28 | |
| *** amrith has quit IRC | 21:31 | |
| *** richm has joined #openstack-meeting-alt | 21:31 | |
| *** michael-yu has joined #openstack-meeting-alt | 21:32 | |
| *** colinmcnamara has joined #openstack-meeting-alt | 21:35 | |
| *** boris-42 has quit IRC | 21:36 | |
| *** denis_makogon has quit IRC | 21:37 | |
| *** Duane has quit IRC | 21:38 | |
| *** Duane has joined #openstack-meeting-alt | 21:39 | |
| *** shashank_ has joined #openstack-meeting-alt | 21:39 | |
| *** amrith has joined #openstack-meeting-alt | 21:39 | |
| *** jmcbride has quit IRC | 21:40 | |
| *** boris-42 has joined #openstack-meeting-alt | 21:40 | |
| *** Duane has quit IRC | 21:43 | |
| *** lsmola has quit IRC | 21:43 | |
| *** nati_ueno has quit IRC | 21:46 | |
| *** sarob has joined #openstack-meeting-alt | 21:46 | |
| *** roeyc has joined #openstack-meeting-alt | 21:47 | |
| *** lyxys has joined #openstack-meeting-alt | 21:49 | |
| *** BrianB_ has quit IRC | 21:50 | |
| *** nati_ueno has joined #openstack-meeting-alt | 21:50 | |
| *** lyxys is now known as lyxus | 21:50 | |
| *** sarob has quit IRC | 21:50 | |
| *** doug_shelley66 has joined #openstack-meeting-alt | 21:52 | |
| *** BrianB_ has joined #openstack-meeting-alt | 21:53 | |
| *** luqas has joined #openstack-meeting-alt | 21:54 | |
| *** jmcbride has joined #openstack-meeting-alt | 21:54 | |
| *** nati_ueno has quit IRC | 21:55 | |
| *** nadya_ has quit IRC | 21:55 | |
| *** hemanthravi has joined #openstack-meeting-alt | 21:55 | |
| *** jdob has quit IRC | 21:55 | |
| *** nati_ueno has joined #openstack-meeting-alt | 21:56 | |
| *** kebray_ has joined #openstack-meeting-alt | 21:58 | |
| mestery | Hi, anyone here for the Neutron 3rd party testing meeting? | 22:00 |
| banix | mestery: Hi | 22:00 |
| mestery | banix: howdy! :) | 22:00 |
| roeyc | Hi | 22:00 |
| *** mpolanco has joined #openstack-meeting-alt | 22:00 | |
| luqas | hi | 22:00 |
| hemanthravi | hi | 22:00 |
| BrianB_ | hi | 22:00 |
| banix | :) | 22:00 |
| * mestery takes note of the rather large crowd and proceeds to begin the meeting. | 22:00 | |
| mestery | #startmeeting networking_third_party_testing | 22:00 |
| openstack | Meeting started Wed Jan 15 22:00:59 2014 UTC and is due to finish in 60 minutes. The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot. | 22:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 22:01 |
| lyxus | Hello, yes I am | 22:01 |
| *** openstack changes topic to " (Meeting topic: networking_third_party_testing)" | 22:01 | |
| openstack | The meeting name has been set to 'networking_third_party_testing' | 22:01 |
| mestery | #link https://etherpad.openstack.org/p/multi-node-neutron-tempest Neutron 3rd Party and Muilti-Node Testing Etherpad | 22:01 |
| mestery | We'll use the etherpad for notes today and to update progress, so please sign in with your name there if you can. | 22:01 |
| krtaylor | o/ | 22:02 |
| *** colinmcnamara has quit IRC | 22:02 | |
| mestery | So, first off, has anyone succesfully completed the entire 3rd party testing requirement? :) | 22:02 |
| *** nati_uen_ has joined #openstack-meeting-alt | 22:03 | |
| *** kebray_ has quit IRC | 22:03 | |
| luqas | not yet :-( | 22:03 |
| luqas | still working on it | 22:03 |
| mestery | luqas: I suspect most are still in various stages here, you're not alone. | 22:03 |
| hemanthravi | partially, not sure if we are on the right track | 22:03 |
| hemanthravi | adding what we did to the etherpad | 22:04 |
| hemanthravi | for comments | 22:04 |
| mestery | hemanthravi: Thanks! | 22:04 |
| mestery | So, banix, you had some questions you posed to the list, should we start with those for discussion now? | 22:04 |
| *** amrith has quit IRC | 22:04 | |
| banix | Is the instructions mentioned towards the end of http://ci.openstack.org/third_party.html a good place to start? | 22:04 |
| banix | mestery: sure | 22:04 |
| *** k-pom has left #openstack-meeting-alt | 22:05 | |
| banix | I have followed the instructions there: So have a Jenkins running with Gerrit plugin | 22:05 |
| mestery | banix: Yes, I believe those are the instructions folks have been and should be following as a starting point. | 22:06 |
| *** colinmcnamara has joined #openstack-meeting-alt | 22:06 | |
| *** shivh has joined #openstack-meeting-alt | 22:06 | |
| banix | The instructions for configuring Jenkins are reasonable. The part I am not sure about is the reporting back to Gerrit | 22:06 |
| mestery | banix: OK, what's got you hung up there? | 22:06 |
| *** nati_ueno has quit IRC | 22:07 | |
| banix | last line of the instructions on the web page above says: "This job will now automatically trigger when a new patchset is uploaded and will report the results to Gerrit automatically." | 22:07 |
| *** michael-yu has quit IRC | 22:08 | |
| mestery | So, I've seen a few other testing rigs reporting back, can anyone comment on banix's question here that has that part working already? | 22:08 |
| banix | So I am assuming if all the steps in the Build phase return without error a +1 is reported? | 22:08 |
| *** shashank_ has quit IRC | 22:08 | |
| *** shashank_ has joined #openstack-meeting-alt | 22:08 | |
| *** michael-yu has joined #openstack-meeting-alt | 22:09 | |
| hemanthravi | banix: do the jenkins steps I added to the etherpad seem right? | 22:09 |
| banix | hemanthravi: let me have a look please | 22:09 |
| *** EmilienM has quit IRC | 22:10 | |
| banix | I believe you can do the step 5 items in different way; what hemanthravi has outlines is one way of doing it | 22:10 |
| banix | Alternatively, you could have a multi-node setup, and all that but I believe for the first try those steps sound reasonable | 22:11 |
| *** amcrn has quit IRC | 22:11 | |
| mestery | I agree, steps 5 could differ slightly, but the general approach looks reasonable to me as well. | 22:11 |
| hemanthravi | for 5.5, do we specify the list of tests to be run or is there a standard set of test | 22:11 |
| banix | I am not sure about how to do step 6. Being cautious to avoid reporting/voting incorrectly | 22:12 |
| *** EmilienM has joined #openstack-meeting-alt | 22:12 | |
| mestery | hemanthravi: I think you can run the standard tempest tests. | 22:12 |
| banix | hemanthravi: I would think the tests could be limited to say your plugin only | 22:13 |
| *** michael-yu has quit IRC | 22:13 | |
| hemanthravi | remember some disc about filters for the tests to be run, is this a config outside jenkins? | 22:13 |
| *** lblanchard has quit IRC | 22:13 | |
| *** amcrn has joined #openstack-meeting-alt | 22:14 | |
| banix | lugas: are you setup the system that posts reviews for Midokura? | 22:14 |
| shivh | Currently there is push to consolidate all network tests in one directory, one could specify that to nosetests to run networking tests (suggestions?) | 22:14 |
| banix | hemanthravi: no you can specify the directories | 22:14 |
| luqas | yes, but currently I fake the answer to post +1 votes always | 22:14 |
| mestery | You can decide which subset of Tempest tests to run to work your plugin out | 22:14 |
| hemanthravi | got it, thanks | 22:15 |
| luqas | you can configure that in the gerrit trigger plugin | 22:15 |
| banix | luqas: how do you do that? where do you specify that? | 22:15 |
| banix | in the gerrit plugin and not the Jenkins job configuration? | 22:15 |
| shashank_ | So we've noticed that devstack is a bit flaky. So I was wondering is it ok to vote -1 if devstack fails? | 22:16 |
| *** colinmcnamara has quit IRC | 22:16 | |
| mestery | shashank_: What do you mean devstack is flakey? devstack itself fails? | 22:16 |
| shashank_ | yep | 22:16 |
| mestery | shashank_: That shouldn't happen, I think you need to figure out why devstack is failing, maybe it's in your local.conf file or something. | 22:17 |
| shashank_ | We were actually hitting a db migration bug | 22:17 |
| *** pdmars has quit IRC | 22:17 | |
| shashank_ | We worked around it by enabling lbaas | 22:17 |
| *** colinmcnamara has joined #openstack-meeting-alt | 22:17 | |
| mestery | shashank_: Cool! So maybe that was your problem, and not a devstack issue itself? | 22:18 |
| *** jbrendel has joined #openstack-meeting-alt | 22:18 | |
| banix | shashank_: yes that is not a devstack issue | 22:18 |
| shivh | mestery: devstack to use should be stable version, not master? | 22:18 |
| banix | shashank_: I think the fix is submitted but not merged or may be got merged recently | 22:18 |
| mestery | shivh: I would suggest the latest, e.g. track upstream. But maybe I'm missing a nuance somewhere. :) | 22:19 |
| shashank_ | My concern was what if such bugs creep into devstack and cause stack to fail | 22:19 |
| luqas | banix: in manage jenkins -> gerrit trigger | 22:19 |
| *** jmcbride has quit IRC | 22:19 | |
| shivh | mestery: top of the master (head) may be unstable, somewhere there should be a good known version (stable) | 22:20 |
| luqas | you set the reporting values | 22:20 |
| mestery | shivh: True, but you also run the risk of an older version of devstack not being able to support deploying the latest code, right? | 22:20 |
| shashank_ | So I was a bit concerned about stacking before testing each patch | 22:20 |
| shivh | mestery: I see your point. maybe head is fine to use. | 22:21 |
| banix | luqas: I see that; so you set the value for successful, etc; but how is it decided that the test was successful is I guess what I am missing | 22:21 |
| roeyc | shashank_: You can vote 0 and just report with a message. | 22:21 |
| mestery | shivh: I think there's a balance, and if you look at what -qa and -infra do, they have to strike that balance all the time. | 22:21 |
| shashank_ | cool… | 22:21 |
| mestery | shivh: But I think this is something we need to all be aware of. | 22:21 |
| shashank_ | @banix, it depends on the exit value of the script that you run | 22:22 |
| * mestery nods in agreement with shashank_. | 22:22 | |
| *** colinmcnamara has quit IRC | 22:22 | |
| banix | I see. Thanks shashank and luqas | 22:22 |
| *** colinmcnamara has joined #openstack-meeting-alt | 22:23 | |
| banix | So I think just to be safe, one could set the values for reporting to 0 or +1 for all cases | 22:23 |
| banix | Just don't want to incorrectly vote -1 on patches and block their review | 22:23 |
| *** jcru has left #openstack-meeting-alt | 22:24 | |
| mestery | banix: Yes, we've seen that happen already. But I think -infra is limiting the voting ability of the testing setups until they can prove themselves, which will alleviate that problem as well. | 22:24 |
| banix | mestery: That's good to know! | 22:25 |
| mestery | banix: :) | 22:25 |
| luqas | regarding the tempest test, network related is enough? | 22:25 |
| *** jaypipes has quit IRC | 22:25 | |
| banix | With respect to testing a plugin, I would thing any change to neutron directory could lead to failure and therefore should trigger a test but I am thinking that to begin with I will limit the trigger to the plugin I am concerned with. | 22:26 |
| shashank_ | Yeah… Even I am curious as to which tests need to be run | 22:27 |
| mestery | So, those are differences: Waht tests to run, and what changes trigger the running of the tests. | 22:27 |
| shivh | so voting with 0 is allowed? | 22:27 |
| mestery | The latter was suggested as changes to your plugin/MechanismDriver along with all Jenkins changes. | 22:27 |
| mestery | The former woudl be the Tempest tests, or a subset of those. | 22:27 |
| mestery | Makes sense? | 22:28 |
| banix | That would be another way of limiting the impact of my voting…. | 22:28 |
| banix | mestery: where/what are Jenkins changes? | 22:28 |
| mestery | I don't think the testing rigs voting "0" would have much value, unless it was only temporary. | 22:28 |
| mestery | banix: I mean, changes submitted by the Jenkins user (e.g. translation changes as an example). | 22:29 |
| banix | mestery: thanks; | 22:29 |
| *** kebray_ has joined #openstack-meeting-alt | 22:29 | |
| mestery | banix: Cool. | 22:29 |
| banix | so that means we can trigger by who submitted the patch set? | 22:30 |
| mestery | banix: I believe so, yes. | 22:30 |
| *** jcoufal has quit IRC | 22:31 | |
| *** Barker has quit IRC | 22:32 | |
| mestery | OK, so is there anything else people want to discuss here? | 22:33 |
| *** nati_uen_ has quit IRC | 22:33 | |
| *** obondarev_ has quit IRC | 22:33 | |
| hemanthravi | is there a criteria to decide, when the test setup can start voting? | 22:33 |
| *** nati_ueno has joined #openstack-meeting-alt | 22:34 | |
| mestery | hemanthravi: That's a very good question actually. I think the idea is that the test rig has to be running ok for a while, a contact from that company/project has to be particiapting upstream in meetings. | 22:34 |
| mestery | Thsoe are the two things which I remember from an email to the list a while back. | 22:34 |
| *** nati_ueno has quit IRC | 22:35 | |
| *** nati_ueno has joined #openstack-meeting-alt | 22:36 | |
| banix | So, multi-node testing would come later on? Anybody working on that? | 22:36 |
| mestery | banix: That's ... complicated. | 22:37 |
| banix | :) | 22:37 |
| mestery | As anita indicated in email, that doesn't exist yet upstream. | 22:38 |
| mestery | All gate testing is done on a single node if you can believe it! | 22:38 |
| mestery | Now, I see no reason why this shouldn't work, after all, Tempest runs against an OpenStack cloud. | 22:38 |
| mestery | There may be issues with deploying this for testing, etc. But that's all things we can work through together perhaps. | 22:38 |
| banix | I see | 22:38 |
| banix | sounds good | 22:39 |
| mestery | OK, good. :) | 22:40 |
| mestery | banix: There could be problems, but if there are, lets all work through them together. | 22:40 |
| banix | mestery: Yes of course. | 22:40 |
| banix | So I think from what I have heard so far, Jenkins with Gerrit plugin seems the way to go. | 22:40 |
| *** pnavarro__ has quit IRC | 22:41 | |
| * mestery nods. | 22:41 | |
| mestery | I think so. | 22:41 |
| *** colinmcnamara has quit IRC | 22:41 | |
| luqas | a last question regarding the stability of devstack | 22:41 |
| *** HenryG has quit IRC | 22:42 | |
| luqas | sometimes when stacking, at the end, it gives some errors, when setting up the default config | 22:42 |
| shivh | mestery: thanks for the clarifications - much needed. | 22:42 |
| *** colinmcnamara has joined #openstack-meeting-alt | 22:42 | |
| *** Duane has joined #openstack-meeting-alt | 22:42 | |
| luqas | can it be because of some race condition? | 22:42 |
| *** glucas has joined #openstack-meeting-alt | 22:42 | |
| *** jmcbride has joined #openstack-meeting-alt | 22:43 | |
| mestery | luqas: I would verify it's not related to your plugin, try ensuring you can get consistent devstack runs outside of the test harness. | 22:43 |
| mestery | OR are you saying you've already done that? | 22:43 |
| *** derekh has joined #openstack-meeting-alt | 22:43 | |
| shivh | if there are race conditions others may have experienced it. Maybe ask the question on ML. | 22:44 |
| luqas | it happens sometimes with our pluggin that I have to unstack a couple of times before everything is setup correctly | 22:44 |
| mestery | Good point shivh. | 22:45 |
| luqas | I have to be sure that this has never happen of plain devstack without our plugin | 22:45 |
| *** jmcbride has quit IRC | 22:45 | |
| mestery | luqas: That would be a good datapoint to have. | 22:45 |
| mestery | FYI: I am consisently stacking with the latest master and Neutron and I've never seen it fail with a race condition. | 22:45 |
| luqas | mestery: ok, i?ll check that | 22:45 |
| mestery | luqas: Cool. | 22:45 |
| *** aignatov has quit IRC | 22:46 | |
| mestery | OK, anything else before we wrap this meeting up? | 22:47 |
| *** jmcbride has joined #openstack-meeting-alt | 22:47 | |
| *** jmcbride has quit IRC | 22:48 | |
| mestery | OK, lets keep communicating in channel (#openstack-neutron and #openstack-qa) and on the ML. | 22:48 |
| mestery | Thanks everyone, and good luck as we move to the 3rd party testing deadline next week! | 22:48 |
| mestery | #endmeeting | 22:48 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 22:48 | |
| openstack | Meeting ended Wed Jan 15 22:48:52 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 22:48 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2014/networking_third_party_testing.2014-01-15-22.00.html | 22:48 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2014/networking_third_party_testing.2014-01-15-22.00.txt | 22:48 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2014/networking_third_party_testing.2014-01-15-22.00.log.html | 22:48 |
| shivh | bye all | 22:48 |
| banix | thank you. | 22:48 |
| luqas | bye! | 22:49 |
| hemanthravi | bye | 22:49 |
| roeyc | bye | 22:49 |
| *** luqas has quit IRC | 22:49 | |
| *** roeyc has left #openstack-meeting-alt | 22:50 | |
| *** lyxus has left #openstack-meeting-alt | 22:50 | |
| *** shivh has quit IRC | 22:51 | |
| *** shashank_ has left #openstack-meeting-alt | 22:54 | |
| *** richm has left #openstack-meeting-alt | 22:54 | |
| *** hemanthravi has quit IRC | 22:55 | |
| *** jbrendel has quit IRC | 22:55 | |
| *** nati_ueno has quit IRC | 22:56 | |
| *** yamahata has quit IRC | 22:57 | |
| *** roshanagr1 has joined #openstack-meeting-alt | 22:58 | |
| *** flaper87 is now known as flaper87|afk | 22:59 | |
| *** mpolanco has quit IRC | 22:59 | |
| *** roeyc has joined #openstack-meeting-alt | 23:00 | |
| *** roeyc has left #openstack-meeting-alt | 23:00 | |
| *** rossella_s has quit IRC | 23:01 | |
| *** rsblendido has quit IRC | 23:01 | |
| *** harlowja_away is now known as harlowja_ | 23:02 | |
| *** nati_ueno has joined #openstack-meeting-alt | 23:05 | |
| *** nati_ueno has quit IRC | 23:06 | |
| *** safchain has quit IRC | 23:07 | |
| *** katyafervent_ has joined #openstack-meeting-alt | 23:12 | |
| *** mtaylor has joined #openstack-meeting-alt | 23:12 | |
| *** carlp_ has joined #openstack-meeting-alt | 23:12 | |
| *** dteselkin_ has joined #openstack-meeting-alt | 23:13 | |
| *** colinmcnamara has quit IRC | 23:14 | |
| *** dosaboy_ has joined #openstack-meeting-alt | 23:15 | |
| *** amcrn_ has joined #openstack-meeting-alt | 23:15 | |
| *** amcrn has quit IRC | 23:16 | |
| *** pballand has quit IRC | 23:16 | |
| *** amcrn_ is now known as amcrn | 23:16 | |
| *** SlickN1k has joined #openstack-meeting-alt | 23:16 | |
| *** banix has quit IRC | 23:16 | |
| *** yjiang5_1 has joined #openstack-meeting-alt | 23:16 | |
| *** stannie has quit IRC | 23:17 | |
| *** mordred has quit IRC | 23:17 | |
| *** carlp has quit IRC | 23:17 | |
| *** katyafervent has quit IRC | 23:17 | |
| *** doug_shelley66 has quit IRC | 23:17 | |
| *** dteselkin has quit IRC | 23:17 | |
| *** dosaboy has quit IRC | 23:17 | |
| *** alazarev has quit IRC | 23:17 | |
| *** SlickNik has quit IRC | 23:17 | |
| *** kebray has quit IRC | 23:17 | |
| *** yjiang5 has quit IRC | 23:17 | |
| *** SlickN1k is now known as SlickNik | 23:17 | |
| *** kebray has joined #openstack-meeting-alt | 23:17 | |
| *** doug_shelley66 has joined #openstack-meeting-alt | 23:18 | |
| *** stannie has joined #openstack-meeting-alt | 23:18 | |
| *** NehaV has quit IRC | 23:19 | |
| *** ijw_ has joined #openstack-meeting-alt | 23:20 | |
| *** michael-yu has joined #openstack-meeting-alt | 23:20 | |
| *** BrianB_ has quit IRC | 23:21 | |
| *** obondarev_ has joined #openstack-meeting-alt | 23:22 | |
| *** derekh has quit IRC | 23:24 | |
| *** sballe_ has quit IRC | 23:24 | |
| *** ijw has quit IRC | 23:25 | |
| *** yogesh has quit IRC | 23:27 | |
| *** jjmb has joined #openstack-meeting-alt | 23:29 | |
| *** jmontemayor has quit IRC | 23:33 | |
| *** obondarev_ has quit IRC | 23:34 | |
| *** obondarev_ has joined #openstack-meeting-alt | 23:35 | |
| *** obondarev_ has quit IRC | 23:39 | |
| *** kevinconway has quit IRC | 23:41 | |
| *** amytron has quit IRC | 23:42 | |
| *** sarob has joined #openstack-meeting-alt | 23:42 | |
| *** xuhanp has joined #openstack-meeting-alt | 23:42 | |
| *** ijw_ has quit IRC | 23:44 | |
| *** Duane_ has joined #openstack-meeting-alt | 23:44 | |
| *** demorris has quit IRC | 23:44 | |
| *** jjmb has quit IRC | 23:45 | |
| *** ijw has joined #openstack-meeting-alt | 23:45 | |
| *** AlanClark has quit IRC | 23:45 | |
| *** sarob has quit IRC | 23:47 | |
| *** Duane has quit IRC | 23:47 | |
| *** sarob has joined #openstack-meeting-alt | 23:48 | |
| *** sarob has quit IRC | 23:49 | |
| *** roshanagr1 has quit IRC | 23:49 | |
| *** sarob has joined #openstack-meeting-alt | 23:50 | |
| *** yamahata has joined #openstack-meeting-alt | 23:53 | |
| *** Duane_ has quit IRC | 23:53 | |
| *** ashaikh has quit IRC | 23:55 | |
| *** nermina has quit IRC | 23:56 | |
| *** jcoufal has joined #openstack-meeting-alt | 23:57 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!