| *** ivar-lazzaro has joined #openstack-meeting-3 | 00:01 | |
| *** MarkAtwood has quit IRC | 00:05 | |
| *** ivar-lazzaro has quit IRC | 00:05 | |
| *** mfer has joined #openstack-meeting-3 | 00:17 | |
| *** eghobo has quit IRC | 00:20 | |
| *** nkubota_ has quit IRC | 00:25 | |
| *** mfer has quit IRC | 00:26 | |
| *** briancurtin has joined #openstack-meeting-3 | 00:27 | |
| *** rudrarugge has quit IRC | 00:28 | |
| *** xuhanp has joined #openstack-meeting-3 | 00:30 | |
| *** yamahata has joined #openstack-meeting-3 | 00:37 | |
| *** hurgleburgler has quit IRC | 00:38 | |
| *** yamamoto has quit IRC | 00:47 | |
| *** banix has joined #openstack-meeting-3 | 00:50 | |
| *** jamielennox has quit IRC | 00:54 | |
| *** Sukhdev has quit IRC | 00:55 | |
| *** jamielennox_ has joined #openstack-meeting-3 | 00:55 | |
| *** jamielennox_ is now known as jamielennox | 00:56 | |
| *** xuhanp has quit IRC | 00:59 | |
| *** chuckC has quit IRC | 01:13 | |
| *** nkubota has joined #openstack-meeting-3 | 01:17 | |
| *** yamahata__ has joined #openstack-meeting-3 | 01:34 | |
| *** stanzgy has joined #openstack-meeting-3 | 01:37 | |
| *** baohua has joined #openstack-meeting-3 | 01:41 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 01:54 | |
| *** s3wong has quit IRC | 01:55 | |
| *** SumitNaiksatam has quit IRC | 01:57 | |
| *** amotoki has joined #openstack-meeting-3 | 01:57 | |
| *** sankarshan_away is now known as sankarshan | 01:58 | |
| *** sankarshan is now known as sankarshan_away | 01:58 | |
| *** beagles has quit IRC | 02:00 | |
| *** amotoki has quit IRC | 02:02 | |
| *** beagles has joined #openstack-meeting-3 | 02:05 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 02:13 | |
| *** carl_baldwin has quit IRC | 02:13 | |
| *** chuckC has joined #openstack-meeting-3 | 02:15 | |
| *** tomoe_ has joined #openstack-meeting-3 | 02:19 | |
| *** armax has quit IRC | 02:22 | |
| *** beagles has quit IRC | 02:25 | |
| *** armax has joined #openstack-meeting-3 | 02:30 | |
| *** beagles has joined #openstack-meeting-3 | 02:30 | |
| *** mfer has joined #openstack-meeting-3 | 02:33 | |
| *** armax has quit IRC | 02:33 | |
| *** mfer has quit IRC | 02:43 | |
| *** jamielennox is now known as jamielennox|away | 02:45 | |
| *** jamielennox|away is now known as jamielennox | 02:48 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 02:48 | |
| *** trinaths has quit IRC | 03:02 | |
| *** trinaths has joined #openstack-meeting-3 | 03:03 | |
| *** trinaths has quit IRC | 03:04 | |
| *** badveli has quit IRC | 03:06 | |
| *** nelsnelson has quit IRC | 03:08 | |
| *** nkubota has quit IRC | 03:20 | |
| *** nkubota_ has joined #openstack-meeting-3 | 03:21 | |
| *** yamamoto_ has joined #openstack-meeting-3 | 03:28 | |
| *** yamamot__ has joined #openstack-meeting-3 | 03:29 | |
| *** yamamoto_ has quit IRC | 03:33 | |
| *** yamahata has quit IRC | 03:33 | |
| *** yamahata__ has quit IRC | 03:34 | |
| *** carl_baldwin has quit IRC | 03:34 | |
| *** briancurtin has quit IRC | 03:34 | |
| *** yamahata has joined #openstack-meeting-3 | 03:35 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 03:38 | |
| *** jamielennox has left #openstack-meeting-3 | 03:42 | |
| *** carl_baldwin has quit IRC | 03:44 | |
| *** boris-42 has quit IRC | 03:57 | |
| *** amotoki has joined #openstack-meeting-3 | 03:58 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 03:58 | |
| *** amotoki has quit IRC | 04:02 | |
| *** HenryG is now known as HenryG_afk | 04:06 | |
| *** boris-42 has joined #openstack-meeting-3 | 04:07 | |
| *** briancurtin has joined #openstack-meeting-3 | 04:23 | |
| *** briancurtin has quit IRC | 04:27 | |
| *** banix has quit IRC | 04:29 | |
| *** sankarshan_away is now known as sankarshan | 04:51 | |
| *** sankarshan is now known as sankarshan_away | 04:51 | |
| *** amotoki has joined #openstack-meeting-3 | 04:51 | |
| *** yamamot__ has quit IRC | 05:01 | |
| *** amotoki has quit IRC | 05:06 | |
| *** MarkAtwood has joined #openstack-meeting-3 | 05:08 | |
| *** briancurtin has joined #openstack-meeting-3 | 05:17 | |
| *** yamamoto_ has joined #openstack-meeting-3 | 05:18 | |
| *** briancurtin has quit IRC | 05:21 | |
| *** carl_baldwin has quit IRC | 05:22 | |
| *** tomoe_ has quit IRC | 05:47 | |
| *** tomoe_ has joined #openstack-meeting-3 | 05:49 | |
| *** tmazur has joined #openstack-meeting-3 | 05:49 | |
| *** k4n0 has joined #openstack-meeting-3 | 05:51 | |
| *** jcoufal has joined #openstack-meeting-3 | 06:02 | |
| *** briancurtin has joined #openstack-meeting-3 | 06:07 | |
| *** briancurtin has quit IRC | 06:11 | |
| *** Longgeek has joined #openstack-meeting-3 | 06:18 | |
| *** Longgeek has quit IRC | 06:20 | |
| *** Longgeek has joined #openstack-meeting-3 | 06:22 | |
| *** mrunge has joined #openstack-meeting-3 | 06:31 | |
| *** MaxV has joined #openstack-meeting-3 | 06:45 | |
| *** iovadia has joined #openstack-meeting-3 | 06:46 | |
| *** tomoe_ has quit IRC | 06:47 | |
| *** briancurtin has joined #openstack-meeting-3 | 07:01 | |
| *** tomoe_ has joined #openstack-meeting-3 | 07:05 | |
| *** briancurtin has quit IRC | 07:05 | |
| *** MaxV has quit IRC | 07:09 | |
| *** MaxV has joined #openstack-meeting-3 | 07:09 | |
| *** MaxV has quit IRC | 07:14 | |
| *** iovadia1 has joined #openstack-meeting-3 | 07:27 | |
| *** iovadia2 has joined #openstack-meeting-3 | 07:28 | |
| *** iovadia has quit IRC | 07:28 | |
| *** iovadia1 has quit IRC | 07:31 | |
| *** pkoniszewski has joined #openstack-meeting-3 | 07:32 | |
| *** safchain has joined #openstack-meeting-3 | 07:34 | |
| *** MaxV has joined #openstack-meeting-3 | 07:48 | |
| *** yamahata has quit IRC | 07:51 | |
| *** MaxV has quit IRC | 07:53 | |
| *** briancurtin has joined #openstack-meeting-3 | 07:55 | |
| *** briancurtin has quit IRC | 07:59 | |
| *** Longgeek has quit IRC | 08:04 | |
| *** Longgeek has joined #openstack-meeting-3 | 08:05 | |
| *** tomoe__ has joined #openstack-meeting-3 | 08:08 | |
| *** MaxV has joined #openstack-meeting-3 | 08:10 | |
| *** tomoe_ has quit IRC | 08:12 | |
| *** nacim has joined #openstack-meeting-3 | 08:13 | |
| *** tomoe_ has joined #openstack-meeting-3 | 08:16 | |
| *** tomoe__ has quit IRC | 08:17 | |
| *** tomoe__ has joined #openstack-meeting-3 | 08:17 | |
| *** tomoe_ has quit IRC | 08:20 | |
| *** iovadia2 has quit IRC | 08:22 | |
| *** yamamoto_ has quit IRC | 08:36 | |
| *** iovadia has joined #openstack-meeting-3 | 08:46 | |
| *** MaxV has quit IRC | 08:48 | |
| *** scheuran has joined #openstack-meeting-3 | 08:49 | |
| *** MaxV has joined #openstack-meeting-3 | 08:49 | |
| *** briancurtin has joined #openstack-meeting-3 | 08:49 | |
| *** MaxV has quit IRC | 08:53 | |
| *** yamamoto has joined #openstack-meeting-3 | 08:53 | |
| *** briancurtin has quit IRC | 08:54 | |
| *** MaxV has joined #openstack-meeting-3 | 08:59 | |
| *** edleafe has quit IRC | 09:12 | |
| *** edleafe has joined #openstack-meeting-3 | 09:12 | |
| *** tmazur has quit IRC | 09:16 | |
| *** tomoe__ has quit IRC | 09:30 | |
| *** baohua has quit IRC | 09:30 | |
| *** tomoe_ has joined #openstack-meeting-3 | 09:31 | |
| *** tmazur has joined #openstack-meeting-3 | 09:38 | |
| *** briancurtin has joined #openstack-meeting-3 | 09:43 | |
| *** briancurtin has quit IRC | 09:48 | |
| *** MaxV has quit IRC | 10:31 | |
| *** MaxV has joined #openstack-meeting-3 | 10:32 | |
| *** MaxV has quit IRC | 10:37 | |
| *** briancurtin has joined #openstack-meeting-3 | 10:37 | |
| *** jcoufal_ has joined #openstack-meeting-3 | 10:37 | |
| *** jcoufal has quit IRC | 10:40 | |
| *** briancurtin has quit IRC | 10:42 | |
| *** nkubota_ is now known as zz_nkubota_ | 10:42 | |
| *** banix has joined #openstack-meeting-3 | 10:44 | |
| *** stanzgy has quit IRC | 10:49 | |
| *** beagles has quit IRC | 10:57 | |
| *** beagles has joined #openstack-meeting-3 | 11:03 | |
| *** beagles is now known as Guest95381 | 11:03 | |
| *** MaxV has joined #openstack-meeting-3 | 11:05 | |
| *** MaxV has quit IRC | 11:05 | |
| *** MaxV has joined #openstack-meeting-3 | 11:05 | |
| *** Guest95381 has quit IRC | 11:17 | |
| *** beagles_ has joined #openstack-meeting-3 | 11:21 | |
| *** tmazur has quit IRC | 11:22 | |
| *** beagles_ has quit IRC | 11:26 | |
| *** Longgeek_ has joined #openstack-meeting-3 | 11:28 | |
| *** beagles_ has joined #openstack-meeting-3 | 11:31 | |
| *** Longgeek has quit IRC | 11:31 | |
| *** tmazur has joined #openstack-meeting-3 | 11:35 | |
| *** flaviof_zzz is now known as flaviof | 11:36 | |
| *** banix has quit IRC | 11:42 | |
| *** beagles_ has quit IRC | 11:57 | |
| *** zz_nkubota_ is now known as nkubota | 11:58 | |
| *** Guest28074 has joined #openstack-meeting-3 | 12:02 | |
| *** alexpilotti has joined #openstack-meeting-3 | 12:10 | |
| *** baohua has joined #openstack-meeting-3 | 12:10 | |
| *** k4n0 has quit IRC | 12:14 | |
| *** briancurtin has joined #openstack-meeting-3 | 12:26 | |
| *** briancurtin has quit IRC | 12:30 | |
| *** Guest28074 is now known as beagles | 12:38 | |
| *** beagles is now known as Guest78450 | 12:38 | |
| *** Guest78450 is now known as b3nt_pin | 12:44 | |
| *** b3nt_pin is now known as Guest47913 | 12:44 | |
| *** flaviof is now known as flaviof_zzz | 12:46 | |
| *** HenryG_afk is now known as HenryG | 12:49 | |
| *** julim has joined #openstack-meeting-3 | 12:59 | |
| *** mwagner_lap has joined #openstack-meeting-3 | 12:59 | |
| *** julim has quit IRC | 13:00 | |
| *** nelsnelson has joined #openstack-meeting-3 | 13:00 | |
| *** HenryG has quit IRC | 13:02 | |
| *** nkubota is now known as zz_nkubota | 13:04 | |
| *** julim has joined #openstack-meeting-3 | 13:04 | |
| *** chuckC_ has joined #openstack-meeting-3 | 13:12 | |
| *** yamahata__ has joined #openstack-meeting-3 | 13:14 | |
| *** yamamoto_ has joined #openstack-meeting-3 | 13:14 | |
| *** yamahata_ has quit IRC | 13:15 | |
| *** sdague has quit IRC | 13:15 | |
| *** chuckC has quit IRC | 13:15 | |
| *** chuckC_ is now known as chuckC | 13:15 | |
| *** mwagner_lap has quit IRC | 13:15 | |
| *** yamamoto has quit IRC | 13:15 | |
| *** lsmola has quit IRC | 13:15 | |
| *** anteaya has quit IRC | 13:15 | |
| *** tmazur has quit IRC | 13:15 | |
| *** mwagner_lap has joined #openstack-meeting-3 | 13:15 | |
| *** tmazur has joined #openstack-meeting-3 | 13:15 | |
| *** sdague has joined #openstack-meeting-3 | 13:16 | |
| *** anteaya has joined #openstack-meeting-3 | 13:16 | |
| *** lsmola has joined #openstack-meeting-3 | 13:18 | |
| *** peristeri has joined #openstack-meeting-3 | 13:18 | |
| *** briancurtin has joined #openstack-meeting-3 | 13:20 | |
| *** briancurtin has quit IRC | 13:25 | |
| *** banix has joined #openstack-meeting-3 | 13:30 | |
| *** banix has quit IRC | 13:31 | |
| *** banix has joined #openstack-meeting-3 | 13:32 | |
| *** banix has quit IRC | 13:34 | |
| *** nelsnelson has quit IRC | 13:36 | |
| *** nelsnelson has joined #openstack-meeting-3 | 13:37 | |
| *** banix has joined #openstack-meeting-3 | 13:38 | |
| *** mfer has joined #openstack-meeting-3 | 13:42 | |
| *** nelsnelson has quit IRC | 13:42 | |
| *** Guest47913 has quit IRC | 13:47 | |
| *** briancurtin has joined #openstack-meeting-3 | 13:49 | |
| *** briancurtin has quit IRC | 13:49 | |
| *** needscoffee has joined #openstack-meeting-3 | 13:50 | |
| *** needscoffee has joined #openstack-meeting-3 | 13:50 | |
| *** briancurtin has joined #openstack-meeting-3 | 13:50 | |
| *** briancurtin has quit IRC | 13:50 | |
| *** briancurtin has joined #openstack-meeting-3 | 13:51 | |
| *** beagles has joined #openstack-meeting-3 | 13:53 | |
| *** TravT has joined #openstack-meeting-3 | 13:56 | |
| *** briancurtin has quit IRC | 13:57 | |
| *** briancurtin has joined #openstack-meeting-3 | 13:58 | |
| *** mfer has quit IRC | 13:59 | |
| *** briancurtin has quit IRC | 14:01 | |
| *** briancurtin2 has joined #openstack-meeting-3 | 14:01 | |
| *** thangp has joined #openstack-meeting-3 | 14:01 | |
| *** needscoffee has quit IRC | 14:04 | |
| *** briancurtin2 has quit IRC | 14:06 | |
| *** briancurtin has joined #openstack-meeting-3 | 14:06 | |
| *** briancurtin has joined #openstack-meeting-3 | 14:06 | |
| *** briancurtin has quit IRC | 14:08 | |
| *** otherwiseguy has joined #openstack-meeting-3 | 14:10 | |
| *** nelsnelson has joined #openstack-meeting-3 | 14:16 | |
| *** armax has joined #openstack-meeting-3 | 14:16 | |
| *** briancurtin has joined #openstack-meeting-3 | 14:22 | |
| *** briancurtin has joined #openstack-meeting-3 | 14:22 | |
| *** briancurtin has quit IRC | 14:23 | |
| *** yamahata__ has quit IRC | 14:31 | |
| *** mfer has joined #openstack-meeting-3 | 14:37 | |
| *** Longgeek has joined #openstack-meeting-3 | 14:38 | |
| *** Longgeek_ has quit IRC | 14:41 | |
| *** jcoufal_ has quit IRC | 14:41 | |
| *** mfer has quit IRC | 14:41 | |
| *** HenryG has joined #openstack-meeting-3 | 14:43 | |
| *** yyywu has joined #openstack-meeting-3 | 14:46 | |
| *** briancurtin has joined #openstack-meeting-3 | 14:46 | |
| *** briancurtin has joined #openstack-meeting-3 | 14:46 | |
| *** briancurtin has quit IRC | 14:48 | |
| *** mfer has joined #openstack-meeting-3 | 14:48 | |
| *** briancurtin has joined #openstack-meeting-3 | 14:49 | |
| *** briancurtin has quit IRC | 14:49 | |
| *** briancurtin has joined #openstack-meeting-3 | 14:49 | |
| *** Youcef has joined #openstack-meeting-3 | 14:50 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 14:50 | |
| *** devvesa_ has joined #openstack-meeting-3 | 14:51 | |
| *** briancurtin has quit IRC | 14:54 | |
| *** tomoe_ has joined #openstack-meeting-3 | 14:55 | |
| *** amuller has joined #openstack-meeting-3 | 14:55 | |
| *** baohua has quit IRC | 14:55 | |
| *** viveknarasimhan has joined #openstack-meeting-3 | 14:58 | |
| carl_baldwin | hi all | 14:59 |
|---|---|---|
| amuller | Hey Carl | 14:59 |
| armax | carl_baldwin: hi | 14:59 |
| *** seizadi has joined #openstack-meeting-3 | 14:59 | |
| yamamoto_ | hi | 14:59 |
| devvesa_ | hi | 14:59 |
| carl_baldwin | Swami, mrsmith, viveknarasimhan, safchain, pcm, nextone92: ping | 15:00 |
| *** xuhanp has joined #openstack-meeting-3 | 15:00 | |
| *** mrsmith has joined #openstack-meeting-3 | 15:00 | |
| carl_baldwin | #startmeeting neutron_l3 | 15:00 |
| openstack | Meeting started Thu Jul 31 15:00:23 2014 UTC and is due to finish in 60 minutes. The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| *** openstack changes topic to " (Meeting topic: neutron_l3)" | 15:00 | |
| openstack | The meeting name has been set to 'neutron_l3' | 15:00 |
| carl_baldwin | #topic Announcements | 15:00 |
| *** openstack changes topic to "Announcements (Meeting topic: neutron_l3)" | 15:00 | |
| kevinbenton | o/ | 15:00 |
| carl_baldwin | #link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam | 15:00 |
| *** briancurtin has joined #openstack-meeting-3 | 15:00 | |
| *** briancurtin has joined #openstack-meeting-3 | 15:00 | |
| mrsmith | howdy carl_baldwin | 15:00 |
| carl_baldwin | Already a week in to Juno-3. Things are moving fast. | 15:01 |
| safchain | hi | 15:01 |
| *** Swami has joined #openstack-meeting-3 | 15:01 | |
| carl_baldwin | juno-3 is targetted for September 4th. | 15:01 |
| carl_baldwin | #link https://wiki.openstack.org/wiki/Juno_Release_Schedule | 15:01 |
| *** briancurtin has quit IRC | 15:01 | |
| carl_baldwin | Also, the initial DVR implementation has been merged. This should enable broader testing. | 15:02 |
| carl_baldwin | The infra patches to enable experimental job have also merged I think. | 15:02 |
| armax | carl_baldwin: the first experimental job is running as we speak | 15:02 |
| armax | http://status.openstack.org/zuul/ | 15:03 |
| Swami | great. | 15:03 |
| carl_baldwin | armax: Great. I was just going to look this morning. | 15:03 |
| armax | https://jenkins06.openstack.org/job/check-tempest-dsvm-neutron-dvr/1/console | 15:03 |
| *** briancurtin has joined #openstack-meeting-3 | 15:03 | |
| armax | for review 108177,10 | 15:03 |
| carl_baldwin | Does this require an explicit “check experimental” to run? | 15:04 |
| armax | yes | 15:04 |
| armax | I did post comment ‘check experimental’ explictily | 15:05 |
| *** TravT has quit IRC | 15:05 | |
| carl_baldwin | #topic neutron-ovs-dvr | 15:05 |
| *** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)" | 15:05 | |
| carl_baldwin | all: Make use of this job on our DVR related patches. | 15:06 |
| * carl_baldwin goes to run ‘check experimental’ on his reviews | 15:06 | |
| carl_baldwin | Swami: Anything to report? | 15:07 |
| Swami | carl_baldwin: hi | 15:07 |
| Swami | we had a couple of issues that we wanted to discuss | 15:07 |
| Swami | This is related to migration | 15:07 |
| *** briancurtin has quit IRC | 15:08 | |
| carl_baldwin | You have the floor. | 15:08 |
| Swami | The first question that we have is for a "router-migration", can we make use of "admin_state_up/admin_state_down" first before issuing a router-update | 15:08 |
| carl_baldwin | Do you mean to require that a router be in admin_state_down before migration? | 15:09 |
| armax | Swami: I think it’s sensible | 15:09 |
| *** pballand has joined #openstack-meeting-3 | 15:09 | |
| Swami | The reason is, when admin issues these commands, the existing state of the routers are cleaned up and then we can move or migrate the routers to the new agent. | 15:09 |
| Swami | carl_baldwin: Yes | 15:10 |
| mrsmith | it comes down to the admin running 3 commands or one | 15:10 |
| carl_baldwin | Swami: I don’t see a problem with that. It should be documented. | 15:10 |
| armax | admin_state_down/up are there for a reason | 15:10 |
| *** briancurtin has joined #openstack-meeting-3 | 15:10 | |
| *** briancurtin has joined #openstack-meeting-3 | 15:10 | |
| Swami | We were initially debating that will the admin be ok, in issuing two commands for a migration. First would be to set the 'admin_state" and next would be to do an update. | 15:10 |
| *** briancurtin has quit IRC | 15:11 | |
| viveknarasimhan | could we do this internally | 15:11 |
| armax | we could flip the state automatically in the migration process, but I’d vote to be more explicit | 15:11 |
| viveknarasimhan | without the admin explicitly running 3 commands. | 15:11 |
| viveknarasimhan | does he need to know 3 commmands to be executed in a certain order? | 15:11 |
| yyywu | i vote for explicit, this is one time thing, right? | 15:11 |
| armax | the workflow usually goes like this: you warn your tenant of a maintenance | 15:11 |
| armax | you bring the router down | 15:12 |
| armax | you migrate | 15:12 |
| carl_baldwin | Can the admin run them one after the other with no delay? | 15:12 |
| armax | you bring it up (and hope that everything works) | 15:12 |
| armax | then go back to tenant and tell him that everything is okay :) | 15:12 |
| Swami | viveknarasimhan: I agree with you and that is the reason we wanted concensus from all of us before proceeding. | 15:12 |
| carl_baldwin | Or, does the admin need to wait on something before being allow to run the migration? | 15:12 |
| *** banix has quit IRC | 15:12 | |
| Swami | carl_baldwin: we need to check it out. | 15:13 |
| *** tmazur has quit IRC | 15:13 | |
| Swami | So if we all agree with armax: this is how it has to be done. | 15:13 |
| carl_baldwin | I ask because it could increase router downtime. But, it is a one time migration and can be planned downtime. | 15:13 |
| viveknarasimhan | if some command in teh 3 fails | 15:13 |
| viveknarasimhan | is there a way to rollback | 15:13 |
| mrsmith | I vote for explicit - it is more straight forward | 15:14 |
| viveknarasimhan | or he need to recreate the centralized router again? | 15:14 |
| Swami | We will document that "admin" need to first bring down the router, migrate the router and then tell the tenant to use it. | 15:14 |
| armax | carl_baldwin: i imagine that it’s better being explicit | 15:14 |
| Swami | any questions or concerns there. | 15:14 |
| armax | we might want to give us some room before the router going down and the migration | 15:15 |
| *** mfer has quit IRC | 15:15 | |
| armax | if we do everythin in one shot there’s a risk something gets scheduled on that router in between | 15:15 |
| yyywu | armax, agreed | 15:15 |
| Swami | armax: agreed | 15:15 |
| armax | scheduled as in something happens to that router | 15:16 |
| carl_baldwin | I don’t think I’m concerned. | 15:16 |
| armax | unlikely, but you never know | 15:16 |
| viveknarasimhan | if a problem happens, it could happen in 3 step process as well | 15:16 |
| yamamoto_ | explicit sounds less surprising in POV of admins | 15:16 |
| yyywu | and rollback is part of migration failure case, right? | 15:16 |
| Swami | yyywu: when do you think that rollback should happen | 15:17 |
| yyywu | Sawmi: I am thinking if migration failure happened, rollback should kick in. | 15:17 |
| Swami | right now we are not targeting 'rollback" but we can flag a "migration-error" if something odd happens. | 15:17 |
| armax | rollback can’t really happen if we don’t implement the distributed->centralized path | 15:18 |
| yyywu | Swami: i think we can live as it. | 15:18 |
| armax | a recovery procedure would be to destroy and recreate the router (with all the interfaces and gateway associated with it) | 15:18 |
| Swami | armax: you are right. | 15:18 |
| carl_baldwin | Anything else on migration / admin_state? | 15:19 |
| *** briancurtin has joined #openstack-meeting-3 | 15:19 | |
| Swami | carl_baldwin: admin_state is done. | 15:19 |
| *** briancurtin has quit IRC | 15:19 | |
| *** briancurtin has joined #openstack-meeting-3 | 15:19 | |
| Swami | Next question is on the VM migration. | 15:19 |
| *** briancurtin has quit IRC | 15:19 | |
| *** briancurtin has joined #openstack-meeting-3 | 15:20 | |
| Swami | How will vm migration be handled during router conversion. | 15:20 |
| Swami | There are two cases. | 15:20 |
| Swami | One admin would like to use the same compute node, so they will not disturb the VM, but restart the l3-agent with DVR mode enabled. | 15:21 |
| Swami | The other case is where, the admin wants to move all their VM to a greenfiled deployment for DVR enabled Nodes. So they bring up new Compute nodes with DVR enabled L3-agents. In this case the VM migration is out of scope for the dvr team. | 15:22 |
| carl_baldwin | The first is the only scenario I had in mind. | 15:22 |
| mrsmith | on the first l3-agent would need to be updated as well as ovs | 15:23 |
| carl_baldwin | Is this live migration in the second case? | 15:23 |
| *** nacim has quit IRC | 15:23 | |
| Swami | carl_baldwin: Ok, if we only target the first scenario, then we will go through the use cases. | 15:24 |
| yyywu | one question, during router conversion, could nova initiate vm migration? | 15:24 |
| Swami | carl_baldwin: yes it is a kind of live migration. | 15:24 |
| *** briancurtin has quit IRC | 15:24 | |
| Swami | yyywu: nova has no idea of router conversion, I don't nova will be aware about the router changes. | 15:25 |
| carl_baldwin | I think we should consider the second case out of scope. | 15:25 |
| armax | Swami: prior to doing the migration every compute host needs to run l2 (with dvr enalbed) and l3 agent | 15:25 |
| armax | correct? | 15:25 |
| viveknarasimhan | correct armax | 15:25 |
| Swami | armax: agreed. | 15:26 |
| Swami | So the admin issues a "router_admin_state_down". | 15:26 |
| armax | does it make sense to keep the compute host disabled well during the migrtion? | 15:26 |
| Swami | The the admin prepares the compute node for migration. | 15:26 |
| Swami | And the admin updates the router for migration. | 15:27 |
| armax | my understanding was that duing a planned upgrade the admin would deploy the right services with the right configs | 15:27 |
| Swami | This is for the "case 1" where we use the existing compute nodes. | 15:27 |
| armax | on the elements of the cloud | 15:27 |
| *** pballand has quit IRC | 15:27 | |
| armax | but router migration should probably be a step right after the upgrade is complete | 15:28 |
| armax | not 100% true in every case | 15:28 |
| armax | especially if the default router type is ‘centralized' | 15:29 |
| Swami | carl_baldwin: armax: viveknarasimhan: mrsmith: are we all in an agreement | 15:30 |
| *** scheuran has quit IRC | 15:30 | |
| mrsmith | Swami: on VM migration? | 15:30 |
| mrsmith | focus on case 1 ? | 15:30 |
| carl_baldwin | I think so. I’m not keen on adding the second case to our scope. | 15:30 |
| viveknarasimhan | i agree. we will try to get case 1 fully covered | 15:31 |
| carl_baldwin | Maybe in kilo if there is demand. | 15:31 |
| viveknarasimhan | case 2 looks bit complex | 15:31 |
| armax | makes sense | 15:31 |
| carl_baldwin | Swami: anything else? | 15:31 |
| armax | even though moving a vm to a new host | 15:31 |
| Swami | mrsmith: carl_baldwin's reply should have answered your question for VM migration. We should reduce our scope to the Case 1: that we discussed. | 15:31 |
| armax | does look like pretty much like a scheduling event | 15:31 |
| armax | so dvr should handle it just as well | 15:31 |
| *** briancurtin has joined #openstack-meeting-3 | 15:32 | |
| Swami | carl_baldwin: that's all from me. | 15:32 |
| *** briancurtin has quit IRC | 15:32 | |
| carl_baldwin | Swami: thanks. Let’s get pounding more on the DVR code and fixing bugs. We’ve already got some fixes done and a few more on the way. Great job! | 15:32 |
| *** briancurtin has joined #openstack-meeting-3 | 15:32 | |
| yamamoto_ | i have a small dvr question | 15:33 |
| carl_baldwin | yamamoto_: go ahead. | 15:33 |
| Swami | carl_baldwin: np | 15:33 |
| yamamoto_ | see https://review.openstack.org/#/c/110188/ | 15:33 |
| *** aleksandr_null has joined #openstack-meeting-3 | 15:33 | |
| *** pkoniszewski has quit IRC | 15:33 | |
| yamamoto_ | it's about ofagent but ovs-agent looks same | 15:33 |
| yamamoto_ | isn't it a problem for unbind_port_from_dvr? | 15:33 |
| carl_baldwin | yamamoto_: this will take a a bit to look into. Do you mind if we take the question to the neutron room? | 15:34 |
| yamamoto_ | np. i just wanted dvr folks know. | 15:35 |
| carl_baldwin | Now is a good time to grab them in the neutron room. | 15:35 |
| carl_baldwin | #topic l3-high-availability | 15:35 |
| *** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)" | 15:35 | |
| carl_baldwin | safchain: armax: Any update here? | 15:35 |
| safchain | hi | 15:35 |
| armax | carl_baldwin: going through the review bits | 15:35 |
| armax | armax: I need to allocate more time to this though | 15:36 |
| safchain | I addressed comments and reworked base classes | 15:36 |
| aleksandr_null | Hi guys, sorry I'm late, tried to find correct meeting room :) | 15:36 |
| amuller | Working on l3 agent functional testing: https://review.openstack.org/#/c/109860/ | 15:36 |
| carl_baldwin | I said I’d review last week and did not. But, now with the bulk of DVR merged, I have some review cycles. | 15:36 |
| amuller | Something basic for starters | 15:36 |
| safchain | currently rebasing the scheduler part | 15:37 |
| amuller | The l3 agent patch itself: https://review.openstack.org/#/c/70700/ - Adds HA routers to the functional tests | 15:37 |
| *** pballand has joined #openstack-meeting-3 | 15:37 | |
| amuller | Once that's working I'll be able to respond to reviewer comments and refactor the HA code in the l3 agent so that it isn't as obtrusive | 15:37 |
| carl_baldwin | amuller: do you have a timeline for getting that working? | 15:38 |
| amuller | the base patch that adds the functional tests is working | 15:39 |
| amuller | the ha additions in the l3 ha agent patch aren't... I figure I need 2-3 days working on that and I'll start pushing new patchsets that change the code itself and not the functional tests | 15:39 |
| carl_baldwin | amuller: Thanks. I need to catch up on the progress. I’ll review today. | 15:40 |
| carl_baldwin | Anything else? | 15:40 |
| safchain | ok for me | 15:40 |
| amuller | all good | 15:40 |
| carl_baldwin | Thanks | 15:40 |
| carl_baldwin | #topic bgp-dynamic-routing | 15:40 |
| *** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)" | 15:40 | |
| carl_baldwin | devvesa_: hi | 15:41 |
| devvesa_ | hi | 15:41 |
| devvesa_ | sorry, i was out last week | 15:41 |
| *** hurgleburgler has joined #openstack-meeting-3 | 15:41 | |
| carl_baldwin | Anything to report? | 15:41 |
| *** banix has joined #openstack-meeting-3 | 15:42 | |
| devvesa_ | keep working on it, i am close to push a WIP patch soon | 15:42 |
| devvesa_ | so you can start review it | 15:42 |
| carl_baldwin | devvesa_: That’d be great. | 15:43 |
| carl_baldwin | Be sure to ping me when you post it and I’ll have a look. | 15:43 |
| devvesa_ | ok, great | 15:43 |
| *** tomoe_ has quit IRC | 15:43 | |
| carl_baldwin | devvesa_: Anything else? | 15:44 |
| devvesa_ | no, anything else for the moment | 15:44 |
| carl_baldwin | devvesa_: thanks | 15:44 |
| devvesa_ | thanks carl | 15:44 |
| *** viveknarasimhan has quit IRC | 15:44 | |
| carl_baldwin | All of the other usual topics are deferred to Kilo. I’ll defer discussion for now. | 15:45 |
| carl_baldwin | #topic reschedule-routers-on-dead-agents | 15:45 |
| *** openstack changes topic to "reschedule-routers-on-dead-agents (Meeting topic: neutron_l3)" | 15:45 | |
| *** seizadi has quit IRC | 15:45 | |
| carl_baldwin | kevinbenton: hi, this one is yours. | 15:45 |
| *** Rajeev has joined #openstack-meeting-3 | 15:45 | |
| kevinbenton | topic title is pretty self-explanatory. i would like routers to be taken off of dead agents so they can be automatically rescheduled | 15:46 |
| kevinbenton | here is one approach https://review.openstack.org/#/c/110893/ | 15:46 |
| amuller | So, the L3 HA blueprint solves the same problem | 15:46 |
| kevinbenton | this needs to be in icehouse | 15:47 |
| kevinbenton | IMO | 15:47 |
| kevinbenton | so i was hoping for a bugfix | 15:47 |
| armax | kevinbenton, amuller I think the two overlap | 15:47 |
| armax | and I see kevinbenton’s approach also a a contingency plan | 15:47 |
| amuller | I was under the impression that people use pacemaker and other solutions currently | 15:47 |
| carl_baldwin | This might cross line from bug fix to feature. Might be hard to get in to Icehouse. | 15:47 |
| armax | that mitigates the need of relying on external elements to the fail-over process | 15:48 |
| carl_baldwin | amuller: We’ve toyed around with a pacemaker solution. A colleague gave a talk at the Atl. summit. | 15:48 |
| *** julim has quit IRC | 15:48 | |
| *** seizadi has joined #openstack-meeting-3 | 15:48 | |
| aleksandr_null | amuller: I could confirm it from Mirantis Fuel perspective | 15:49 |
| amuller | We use a Pacemaker based solution in RH OpenStack as well | 15:49 |
| amuller | to solve L3 HA issue | 15:49 |
| kevinbenton | it’s annoying to have to use an external process to do something as simple as rescheduling | 15:49 |
| *** briancurtin has quit IRC | 15:49 | |
| aleksandr_null | we using pm/crm to manage l3 agents and forcing rescheduling of routers. Of course with some downtime ;( | 15:49 |
| carl_baldwin | In our testing, we found it very easy to get in to situations where nodes start shooting themselves. It turned out to be somewhat difficult to get right. | 15:49 |
| amuller | kevinbenton: I agree, but I'm really conflicted if something like this should be merged... Since L3 HA is the concensus on how to do it, I'd be really careful with making the code any more complicated pre L3 HA | 15:50 |
| amuller | L3 HA == VRRP blueprint | 15:50 |
| kevinbenton | i don’t see how this is the same really | 15:51 |
| kevinbenton | it just does what can be done with the existing API | 15:51 |
| armax | I think kevinbenton’s proposal targets non HA deployments | 15:51 |
| armax | granted we want to minimize potential code conflicts | 15:51 |
| armax | so let’s see how the two develop and make a call later on when the code is more mature | 15:51 |
| kevinbenton | armax: right, and i don’t think there would be | 15:51 |
| aleksandr_null | From my point of view VRRP+cn_sync looks easier than rescheduling. In terms of used technologies. But it's not so easy to implement. | 15:51 |
| kevinbenton | aleksandr_null: what? | 15:52 |
| amuller | I know that Rackspace use something similar to your proposal Kevin | 15:52 |
| kevinbenton | aleksandr_null: did you see my patch? | 15:52 |
| armax | I’d see L3HA the canonical way of doing things | 15:52 |
| kevinbenton | it’s like 10 lines | 15:52 |
| amuller | they monitor the RPC bus and reschedule routers as needed | 15:52 |
| aleksandr_null | kevinbenton: Will take a look, of course. | 15:52 |
| *** jcoufal has joined #openstack-meeting-3 | 15:52 | |
| aleksandr_null | armax: +1 | 15:52 |
| *** nelsnelson has quit IRC | 15:52 | |
| armax | that said, there are situations where L3HA as a solution won’t be available | 15:53 |
| kevinbenton | armax: yes, l3ha is definitely the way to move forward, but I’m trying to address an issue in icehouse | 15:53 |
| kevinbenton | if possible | 15:53 |
| armax | now, people might have come up with their own solutions | 15:53 |
| armax | homegrown and painful | 15:53 |
| armax | I think kevinbenton is trying to see whether some of that pain can be taken away :) | 15:53 |
| kevinbenton | it’s embarrassing that a node goes down and we just throw our hands up | 15:53 |
| aleksandr_null | amuller: But what will happens if something will be wrong with communications inside of the cloud ? MQ fails from time to time, of course its out of scope but VRRP will do that autonomous | 15:53 |
| carl_baldwin | I’m concerned that simply rescheduling will not be enough. A pacemaker/corosync type solution would shoot the dead node. This solution would not. With the agent down, there is no one left around to clean up the old router. | 15:54 |
| *** briancurtin has joined #openstack-meeting-3 | 15:54 | |
| *** briancurtin has quit IRC | 15:54 | |
| *** briancurtin has joined #openstack-meeting-3 | 15:54 | |
| armax | I’d promote that effort, but I’d reserve me the judgment to see whether it’s icehouse/juno material once the code is complete | 15:54 |
| amuller | kevinbenton: If the code doesn't end up being more complicated after it's properly tested, and properly solved the problem, then it's safe enough to merge as it is, but I have a gut feeling that you'll find that it's gonna end up a lot more complicated | 15:54 |
| armax | kevinbenton: how far off are you? | 15:54 |
| *** nelsnelson has joined #openstack-meeting-3 | 15:55 | |
| *** pballand has quit IRC | 15:55 | |
| carl_baldwin | In many situations, the old routers could still be plumbed and moving traffic. | 15:55 |
| *** nelsnels_ has joined #openstack-meeting-3 | 15:55 | |
| kevinbenton | carl_baldwin: do your compute nodes frequently lose connectivity to the neutron server? | 15:55 |
| aleksandr_null | kevinbenton: it depends on architecture of cluster. We had an situation when customer just disabled mgmt/comm network. | 15:56 |
| carl_baldwin | kevinbenton: There are many reasons an agent can be considered dead. | 15:56 |
| aleksandr_null | For a while. | 15:56 |
| *** nelsnels_ has quit IRC | 15:56 | |
| kevinbenton | armax: i have the basic patch there, but it doesn’t address zombie nodes like carl_baldwin mentioned | 15:56 |
| kevinbenton | aleksandr_null, carl_baldwin: how does the openvswitch agent handle a broken management network? | 15:57 |
| kevinbenton | we have to assume that’s down too then, right? | 15:57 |
| aleksandr_null | yep. | 15:57 |
| carl_baldwin | kevinbenton: yes, the agent goes inactive. | 15:58 |
| kevinbenton | well then yes, i wasn’t aware we supported headless operational modes | 15:58 |
| *** nelsnelson has quit IRC | 15:59 | |
| kevinbenton | my patch is pointless and this isn’t a problem that can be solved from the neutron server | 15:59 |
| *** nelsnelson has joined #openstack-meeting-3 | 15:59 | |
| kevinbenton | because it doesn’t actually know if these routers are online or not | 16:00 |
| aleksandr_null | IMHO this could be solved only by using autonomous solutions like vrrp, I dont' have any other solutions related to RPC/MQ because they couldn't work autonomous =( | 16:00 |
| carl_baldwin | kevinbenton: It is still something that needs to be addressed. Our pacemaker / corosync solutions have not been as great as we’d hoped. | 16:01 |
| armax | kevinbenton’s solution obviously need cooperation between servers an agents | 16:01 |
| armax | kevinbenton: saying its’ pointless is a bit harsh | 16:02 |
| armax | :) | 16:02 |
| aleksandr_null | of course mgmt network outage is extraordinary case. Rescheduling that kevinbenton suggests maybe improved by trying to monitor neighborhood nodes and/or mgmt net and if something happens with mgmt net then don't do anything. Just suggestion. | 16:02 |
| armax | every solution has tradeoffs | 16:02 |
| *** mfer has joined #openstack-meeting-3 | 16:02 | |
| carl_baldwin | armax: +1 | 16:02 |
| aleksandr_null | +1 | 16:02 |
| armax | the larger question is: do we want to provide some degree of built-in functionality? | 16:02 |
| armax | with any of the cons that may have? | 16:03 |
| armax | external pcm/cm also has issues | 16:03 |
| aleksandr_null | carl_baldwin: Completely agree. pm/crm doing almost the same the Kevin suggested and also wouldn't work fine if mgmt network is down. | 16:03 |
| armax | so long as kevin’s proposal is not disruptive to the current effort for L3HA | 16:03 |
| aleksandr_null | corosync cluster will just split up. | 16:03 |
| amuller | kevinbenton: We'd appreciate any contributions to the L3HA efforts :) | 16:03 |
| armax | I’d like to have the option to decide whether to take it or not | 16:04 |
| aleksandr_null | I could test it in corosync environment and without it | 16:04 |
| armax | amuller: indeed, would kevin’s time best put to L3HA? | 16:04 |
| armax | kevinbenton: that’s a question for kevin :) | 16:04 |
| amuller | kevinbenton: testing/reviewing would be awesome, and there's loose ends also | 16:04 |
| armax | he might have an hidden customer requiremetn ;) | 16:04 |
| kevinbenton | armax: that’s not going to happen right now. I need a solution for icehouse | 16:04 |
| kevinbenton | armax: not hidden :-) | 16:04 |
| armax | kevinbenton: right, you know what I mean | 16:05 |
| armax | kevinbenton: I think it makes sense if you keep on working on this, let’s revise the progress in a week | 16:05 |
| carl_baldwin | I’m glad the discussion is opened. HA will be a hard nut to crack. Is this something we want to add to the permanent agenda? | 16:05 |
| carl_baldwin | I just noticed we’re over time. Anyone else waiting for the room? | 16:06 |
| armax | and see how far we got | 16:06 |
| armax | waaaay over time | 16:06 |
| * carl_baldwin is really sorry about going over time if someone is waiting for the room. | 16:06 | |
| aleksandr_null | looks like nobody :) | 16:06 |
| armax | carl_baldwin: they would have kicked us out | 16:06 |
| armax | :) | 16:06 |
| armax | bye everyone | 16:07 |
| yamamoto_ | bye | 16:07 |
| kevinbenton | bye | 16:07 |
| aleksandr_null | bye guys! | 16:07 |
| carl_baldwin | I’ve got to run. I’d like to discuss rescheduling routers more. I’ll keep it in the agenda near HA. | 16:07 |
| carl_baldwin | I’ll also get some of our guys with experience with our HA solution on kevinbenton’s review to provide insight. | 16:07 |
| carl_baldwin | Thanks all | 16:07 |
| carl_baldwin | #endmeeting | 16:08 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:08 | |
| openstack | Meeting ended Thu Jul 31 16:08:06 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:08 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-07-31-15.00.html | 16:08 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-07-31-15.00.txt | 16:08 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-07-31-15.00.log.html | 16:08 |
| *** yyywu has quit IRC | 16:08 | |
| *** rudrarugge has joined #openstack-meeting-3 | 16:08 | |
| *** MaxV has quit IRC | 16:09 | |
| *** MaxV has joined #openstack-meeting-3 | 16:09 | |
| *** tmazur has joined #openstack-meeting-3 | 16:09 | |
| *** MaxV has quit IRC | 16:14 | |
| *** Swami has quit IRC | 16:17 | |
| *** xuhanp has quit IRC | 16:17 | |
| *** julim has joined #openstack-meeting-3 | 16:18 | |
| *** ivar-lazzaro has joined #openstack-meeting-3 | 16:20 | |
| *** seizadi has left #openstack-meeting-3 | 16:20 | |
| *** nelsnelson has quit IRC | 16:23 | |
| *** mfer has quit IRC | 16:29 | |
| *** Rajeev has quit IRC | 16:30 | |
| *** mfer has joined #openstack-meeting-3 | 16:30 | |
| *** flaviof_zzz is now known as flaviof | 16:36 | |
| *** mfer has quit IRC | 16:37 | |
| *** rudrarug_ has joined #openstack-meeting-3 | 16:38 | |
| *** MaxV has joined #openstack-meeting-3 | 16:38 | |
| *** rudrarugge has quit IRC | 16:40 | |
| *** tmazur has quit IRC | 16:42 | |
| *** devvesa_ has quit IRC | 16:43 | |
| *** MaxV has quit IRC | 16:45 | |
| *** flaviof is now known as flaviof_zzz | 16:45 | |
| *** MaxV has joined #openstack-meeting-3 | 16:46 | |
| *** mfer has joined #openstack-meeting-3 | 16:48 | |
| *** Krishna_ has joined #openstack-meeting-3 | 16:49 | |
| *** MaxV has quit IRC | 16:50 | |
| *** Krishna_ has quit IRC | 16:51 | |
| *** KrishnaK_ has joined #openstack-meeting-3 | 16:51 | |
| *** mrsmith has quit IRC | 16:54 | |
| *** banix has quit IRC | 16:56 | |
| *** banix has joined #openstack-meeting-3 | 17:00 | |
| *** briancurtin has quit IRC | 17:00 | |
| *** amuller has quit IRC | 17:00 | |
| *** briancurtin has joined #openstack-meeting-3 | 17:00 | |
| *** SumitNaiksatam has quit IRC | 17:01 | |
| *** iovadia has quit IRC | 17:03 | |
| *** yisun has quit IRC | 17:03 | |
| *** otherwiseguy has quit IRC | 17:03 | |
| *** briancurtin has quit IRC | 17:05 | |
| *** otherwiseguy has joined #openstack-meeting-3 | 17:08 | |
| *** briancurtin has joined #openstack-meeting-3 | 17:09 | |
| *** briancurtin has quit IRC | 17:09 | |
| *** briancurtin has joined #openstack-meeting-3 | 17:09 | |
| *** briancurtin has quit IRC | 17:10 | |
| *** briancurtin has joined #openstack-meeting-3 | 17:11 | |
| *** briancurtin has joined #openstack-meeting-3 | 17:11 | |
| *** julim has quit IRC | 17:15 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 17:15 | |
| *** julim has joined #openstack-meeting-3 | 17:16 | |
| *** otherwiseguy has quit IRC | 17:16 | |
| *** julim has quit IRC | 17:17 | |
| *** otherwiseguy has joined #openstack-meeting-3 | 17:25 | |
| *** mestery has quit IRC | 17:31 | |
| *** mestery has joined #openstack-meeting-3 | 17:31 | |
| *** HenryG_ has joined #openstack-meeting-3 | 17:31 | |
| *** HenryG has quit IRC | 17:34 | |
| *** banix has quit IRC | 17:37 | |
| *** HenryG_ is now known as HenryG | 17:39 | |
| *** banix has joined #openstack-meeting-3 | 17:40 | |
| *** LouisF has joined #openstack-meeting-3 | 17:42 | |
| *** banix has quit IRC | 17:43 | |
| *** banix has joined #openstack-meeting-3 | 17:43 | |
| *** Sukhdev has joined #openstack-meeting-3 | 17:46 | |
| *** MaxV has joined #openstack-meeting-3 | 17:48 | |
| *** MaxV has quit IRC | 17:48 | |
| *** MaxV has joined #openstack-meeting-3 | 17:49 | |
| *** MaxV has quit IRC | 17:53 | |
| *** briancurtin has quit IRC | 17:53 | |
| *** rkukura has joined #openstack-meeting-3 | 17:55 | |
| *** briancurtin has joined #openstack-meeting-3 | 17:56 | |
| *** briancurtin has joined #openstack-meeting-3 | 17:56 | |
| *** Qijing has joined #openstack-meeting-3 | 17:58 | |
| SumitNaiksatam | hi | 17:58 |
| rkukura | hi SumitNaiksatam | 17:58 |
| banix | hallo | 17:58 |
| *** OSM has joined #openstack-meeting-3 | 17:58 | |
| *** OSM is now known as songole | 17:58 | |
| *** s3wong has joined #openstack-meeting-3 | 17:59 | |
| SumitNaiksatam | rkukura: banix: hi | 18:00 |
| SumitNaiksatam | lets get started | 18:00 |
| *** yyywu has joined #openstack-meeting-3 | 18:00 | |
| SumitNaiksatam | #startmeeting networking_policy | 18:00 |
| openstack | Meeting started Thu Jul 31 18:00:45 2014 UTC and is due to finish in 60 minutes. The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:00 |
| *** openstack changes topic to " (Meeting topic: networking_policy)" | 18:00 | |
| openstack | The meeting name has been set to 'networking_policy' | 18:00 |
| SumitNaiksatam | https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#July_31st.2C_2014 | 18:01 |
| *** mandeep has joined #openstack-meeting-3 | 18:01 | |
| SumitNaiksatam | #info agenda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy#July_31st.2C_2014 | 18:01 |
| SumitNaiksatam | #topic Patches in review | 18:01 |
| *** openstack changes topic to "Patches in review (Meeting topic: networking_policy)" | 18:01 | |
| SumitNaiksatam | #link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy/Patches | 18:01 |
| SumitNaiksatam | there is a long standing -2 on the first patch of the series from markmcclain | 18:02 |
| SumitNaiksatam | i have pointed this out in the -dev mailing list | 18:02 |
| SumitNaiksatam | we also requested markmcclain to attend this meeting | 18:03 |
| SumitNaiksatam | however, he does not seem to be online | 18:03 |
| mandeep | mestery: How should we proceed on this? | 18:03 |
| SumitNaiksatam | we have one +2 from rkukura on the patch | 18:03 |
| mestery | mandeep: It's hard to proceed unless markmcclain is here, I believe he's on a plane returning from the nova mid-cycle at the moment, but I'm not 100% sure. | 18:04 |
| SumitNaiksatam | mestery: okay | 18:04 |
| mandeep | mestery: Quoting salvatore from the mailing list: | 18:04 |
| mandeep | I try to avoid -2s as much as possible. I put a -2 only when I reckon your | 18:04 |
| mandeep | patch should never be merged because it'll make the software unstable or | 18:04 |
| mandeep | tries to solve a problem that does not exist. -2s stick across patches and | 18:04 |
| SumitNaiksatam | mestery: from a project process/policy perspective, is there any remediation to this? | 18:04 |
| mandeep | tend to put off other reviewers. | 18:04 |
| *** Youcef has quit IRC | 18:05 | |
| SumitNaiksatam | mestery: the issue has been raised in the mailing list as well | 18:05 |
| mandeep | mestery: Would you consider this appropriate use of -2 (assuming that definition)? | 18:05 |
| rkukura | I don’t think it would hurt to encourage other core reviewers to review the initial patches and place their votes. | 18:05 |
| mestery | SumitNaiksatam: As I've indicated before, I can't make people remove -2s. We need Mark to respond to this and remove the -2 or justify it at this point, and he hasn't done either. | 18:05 |
| mandeep | mestery: And also raised on 1-1 email and IRC chats | 18:05 |
| SumitNaiksatam | mestery: my suggestion, and as stated before as well, was never to ask you to ask markmcclain to remove his -2 | 18:06 |
| mandeep | mestery: Can you, as the PTL, take the action item to follow up on this? | 18:06 |
| SumitNaiksatam | mestery: the suggestion was to find out why the -2 still persists | 18:06 |
| mestery | mandeep: I have already spoken to Mark many times about this to no avail. | 18:06 |
| mestery | SumitNaiksatam: ++ | 18:06 |
| *** briancurtin2 has joined #openstack-meeting-3 | 18:06 | |
| mestery | SumitNaiksatam: That's really the crux, and I haven't had luck in getting that information out. | 18:06 |
| SumitNaiksatam | mestery: okay, we know you have tried | 18:07 |
| SumitNaiksatam | mestery: at this point, and in this forum, we are just trying to find out, from a process perspective, what needs to be done | 18:07 |
| *** regXboi has joined #openstack-meeting-3 | 18:07 | |
| regXboi | sorry all - ODL TSC call running late | 18:07 |
| regXboi | so I'm here - but not here | 18:08 |
| regXboi | so please move my agenda item to near the end | 18:08 |
| ivar-lazzaro | mestery: should there be a "no answer" time limit before the community takes action in these situations? (e.g. voting in the ML so that the PTL removes the -2?) | 18:08 |
| SumitNaiksatam | mestery: alternatively, if there is no process/policy in place for this, we probably need to formulate a reasonable one | 18:08 |
| SumitNaiksatam | ivar-lazzaro: +1 | 18:08 |
| SumitNaiksatam | i believe, as a core, i am accountable to the -2 i put | 18:08 |
| regXboi | ok... here now | 18:09 |
| SumitNaiksatam | so, if i put a -2, and a new patch set is posted, i review the -2 again | 18:09 |
| SumitNaiksatam | i believe that should be an explicit process that everyone should follow | 18:09 |
| regXboi | SumitNaiksatam: you can say that here | 18:09 |
| ivar-lazzaro | SumitNaiksatam: +1 | 18:10 |
| SumitNaiksatam | if a new patchset is posted, i think the onus is on the core who put the -2, to justify why it should persist | 18:10 |
| regXboi | but since there hasn't been any email on the ML archives, I can't point to any public record of asking for the -2 to be reviewed | 18:10 |
| regXboi | there is finally something in the patch set archives, but that's semi-ephermeal | 18:10 |
| *** briancurtin has quit IRC | 18:10 | |
| SumitNaiksatam | regXboi: there are explicit guidelines to not hound reviewers on the -dev mailing list for reviews | 18:10 |
| mandeep | mestery: Do you agree that the process is broken and needs to be addressed? It was also being discussed on the mailing list todayt morning | 18:10 |
| rkukura | regXboi: I explicitly asked Mark to either remove or justifiy his -2 in my review where I voted +2. | 18:11 |
| mandeep | mestery: http://lists.openstack.org/pipermail/openstack-dev/2014-July/041651.html | 18:11 |
| *** briancurtin2 has quit IRC | 18:11 | |
| regXboi | rkukura: yes, that's the comment I was referring to | 18:11 |
| regXboi | and mandeep: that's a reasonable email | 18:11 |
| mandeep | regXboi: We are forbidden to ask for reviews on the mailing list. | 18:11 |
| *** briancurtin has joined #openstack-meeting-3 | 18:11 | |
| mandeep | regXboi: And that is why we have been sending 1-1 emails to ask for re-review | 18:12 |
| SumitNaiksatam | regXboi: regardless, you cant reason that the -2 persists because there wasnt an email in the mailing list pointing to it, its the duty to of the core to remove the -2 if the circumstances under which he put the -2 have changed | 18:12 |
| * regXboi notes that rule is not in the interests of transparency | 18:12 | |
| mandeep | regXboi: I am asking mestery if the process should be updated if multiple teams are hitting similar issues? | 18:13 |
| regXboi | SumitNaiksatam: that is not my point at all | 18:13 |
| regXboi | my point is that a rule not asking for a re-review on the ML is not in the interests of transparency | 18:13 |
| SumitNaiksatam | okay, we dont intend this to be a meeting where we fix neutorn process/policy issues, i think this team deserves to know why the patch is not allowed to make progress | 18:14 |
| regXboi | because my first reaction would be (at this point) to say "d*mn the rules" :-) | 18:14 |
| regXboi | but that's me | 18:14 |
| SumitNaiksatam | hence this is being brought up in the agenda here | 18:14 |
| SumitNaiksatam | the hope was that markmcclain would have been able to attend so that he could explain to the team | 18:14 |
| mestery | regXboi: ++, there isn't any concern with sending these types of requests to the mailing list, in fact, in this case, that's where it should be discussed | 18:15 |
| SumitNaiksatam | unfortunately it seems that he is travel | 18:15 |
| mandeep | regXboi: And we are asking mestery (PTL) for direction | 18:15 |
| SumitNaiksatam | mestery: so how is asking for a request to review a -2 different from asking for a request to review a patch (the latter is explicitly prohibited) | 18:16 |
| mestery | My point here is that in this case, with a lingering -2, I fail to see how requesting on the list is out of bounds, in fact, it's like a last resort IMHO. | 18:16 |
| *** dkehnx has joined #openstack-meeting-3 | 18:16 | |
| SumitNaiksatam | mestery: okay, thanks for that guidance | 18:17 |
| SumitNaiksatam | mestery: that said, this has already been raised in the email that i sent out yesterday | 18:17 |
| ivar-lazzaro | mestery: well, technically they core could ignore the ML thread as well :D | 18:17 |
| *** julim has joined #openstack-meeting-3 | 18:17 | |
| ivar-lazzaro | they -> the | 18:18 |
| regXboi | ivar-lazzaro: true, but then the weight of public opinion shifts | 18:18 |
| ivar-lazzaro | I had the impression that -2s were a technical issue, not a political one | 18:18 |
| SumitNaiksatam | regXboi: why should we have to waste time in the first place having to build the weight of the public opinion in one way or the other// | 18:18 |
| mandeep | regXboi: I hope we are not becoming politicians and responding to public opinion as opposed to technical concerns | 18:19 |
| SumitNaiksatam | mandeep: exactly my point | 18:19 |
| regXboi | ok folks, let's be real here | 18:19 |
| regXboi | any time you have more than 2 people and money on the table, you have policics | 18:19 |
| regXboi | er politics | 18:19 |
| rkukura | we need some checks and balances, it seems | 18:19 |
| SumitNaiksatam | ok i will have to reign it here! | 18:19 |
| regXboi | even in the perceived optics of the situation there are politics | 18:19 |
| s3wong | In terms of policy change - one way to do so may be how contributors can vote for PTL, contributors can also vote for or against cores | 18:19 |
| *** jerryz has joined #openstack-meeting-3 | 18:20 | |
| regXboi | SumitNaiksatam: ++ :) | 18:20 |
| SumitNaiksatam | ok so moving on for the time being | 18:20 |
| SumitNaiksatam | all good suggestions | 18:20 |
| SumitNaiksatam | had to allow everyone (including myself) to vent a little! ;-P | 18:20 |
| mandeep | s3wong: That is a good idea | 18:20 |
| ivar-lazzaro | s3wong: +1 | 18:20 |
| mandeep | s3wong: If the public opinion is going to decide it, let the ATC decide it | 18:20 |
| SumitNaiksatam | the other update on the patch series is that all the three series are linear now | 18:21 |
| SumitNaiksatam | that means you can go to GP-PLG-3 and be able to pull everything before it | 18:21 |
| mandeep | SumitNaiksatam: Thanks. That helps a lot! | 18:21 |
| SumitNaiksatam | GP-PLG-3 did not pass jenkins because a db migration is dated | 18:21 |
| SumitNaiksatam | but it passes UTs, and should be functional | 18:22 |
| SumitNaiksatam | mestery: before i forget, thanks for stopping by and providing guidance | 18:22 |
| SumitNaiksatam | any questions on series 1, 2, and 3? | 18:23 |
| regXboi | other than I have to check that I've got +1s on all of them - no :) | 18:23 |
| SumitNaiksatam | regXboi: thanks ;-) | 18:23 |
| SumitNaiksatam | thanks for reviewing that is | 18:23 |
| *** yamamoto_ has quit IRC | 18:24 | |
| *** nelsnelson has joined #openstack-meeting-3 | 18:24 | |
| SumitNaiksatam | GP-*-1, and GPM-*-1 were rebased until yesterday | 18:24 |
| *** nelsnelson has quit IRC | 18:24 | |
| SumitNaiksatam | GP-*-2/3 need to rebased | 18:24 |
| SumitNaiksatam | #topic Mapping model/driver update | 18:24 |
| *** openstack changes topic to "Mapping model/driver update (Meeting topic: networking_policy)" | 18:25 | |
| SumitNaiksatam | rkukura: over to you, anything new to report here? | 18:25 |
| mandeep | with DB migrations in place we will have to rebase often, and that will keep wiping off all the +1s - perhaps gerrit should not wipe out +1s for dbmigration updates | 18:25 |
| regXboi | mandeep: that's actually a good point for reviewers - be prepared to do a lot of repeat +1s :/ | 18:25 |
| SumitNaiksatam | mandeep: ah, did not think of that, not sure how easy/difficult it is to achive that | 18:25 |
| rkukura | the DB migration for gpm-db-1 was a bit of a challenge, but thanks to HenryG and akamyshnikova, its all worked out | 18:25 |
| SumitNaiksatam | regXboi: thanks for accepting that responsibility! :-) | 18:26 |
| *** thangp has quit IRC | 18:26 | |
| SumitNaiksatam | rkukura: that was great that you were able to fix those issues | 18:26 |
| regXboi | SumitNaiksatam: I have been - I've got filters on all the re-review mails so I can hit them first thing in the morning :) | 18:26 |
| SumitNaiksatam | rkukura: any short pointers for the rest of the team here in terms what you did to get around the issue? | 18:26 |
| mandeep | regXboi: I agree :-( | 18:26 |
| rkukura | I’ll probably include some more validation checks in a gpm-rmd-1 update at some point | 18:26 |
| *** nelsnelson has joined #openstack-meeting-3 | 18:26 | |
| SumitNaiksatam | regXboi: sounds very organized, great! | 18:27 |
| rkukura | One issue was that alembic sometimes does not generate the foriegn key constraints that are in the model | 18:27 |
| rkukura | Also, when removing columns in a downgrade, some constraint types need to be removed first, and others don’t | 18:28 |
| SumitNaiksatam | rkukura: ah okay, so you had to manually add those? | 18:28 |
| rkukura | Its very easy to test the migrations if you’ve got a devstack environment | 18:28 |
| SumitNaiksatam | rkukura: i mean the foreign key | 18:28 |
| regXboi | rkukura: is *that* what that was all about | 18:28 |
| * regXboi mutters ugly things about code that sometimes does things and sometimes doesn't | 18:29 | |
| SumitNaiksatam | for reference, its the DB migration in this patch #link https://review.openstack.org/#/c/101795 | 18:29 |
| rkukura | I had to manually add the code add and remove foreign keys, and remove the generated code for removing unique constraints | 18:29 |
| SumitNaiksatam | rkukura: ok cool, i guess we can follow that example in the future | 18:30 |
| s3wong | rkukura: wouldn't the code be regenerated to remove your manual changes? | 18:30 |
| rkukura | akamyshnikova is very helpful on reviewing these, and tested the latest version with postgresql as well | 18:30 |
| SumitNaiksatam | rkukura: sweet | 18:30 |
| rkukura | we don’t usually regenerate the migration code | 18:30 |
| rkukura | its a generate once, then edit, process | 18:30 |
| SumitNaiksatam | akamyshnikova: much appreciated! | 18:30 |
| rkukura | the generated migrations always need some cleanup | 18:30 |
| *** mfer has quit IRC | 18:31 | |
| SumitNaiksatam | rkukura: also the issues that you ran into for generating the migration | 18:31 |
| SumitNaiksatam | rkukura: is the env module change merged upstream? | 18:31 |
| rkukura | SumitNaiksatam: Right, not sure if my workaround would still be needed. Hopefully its fixed. | 18:31 |
| SumitNaiksatam | rkukura: ah ok | 18:32 |
| SumitNaiksatam | any questions for rkukura on the mapping part? (since hopefully you are reviewing that right now ;-P ) | 18:32 |
| rkukura | So s3wong is making good progress on the next step of the mapping - creating SGs for enforcement of the policy rules. | 18:33 |
| SumitNaiksatam | rkukura: yeah thats next on the agenda item | 18:33 |
| SumitNaiksatam | #topic Security Groups mapping update | 18:33 |
| *** openstack changes topic to "Security Groups mapping update (Meeting topic: networking_policy)" | 18:33 | |
| SumitNaiksatam | s3wong: your turn :-) | 18:33 |
| s3wong | So I have been coding up the contract=>SG mapping | 18:34 |
| s3wong | so far I coded up the create/update/delete_contract part, and the create/update_EPG part (the latter almost done) | 18:35 |
| s3wong | still need to test, get them ready for gerrit | 18:35 |
| SumitNaiksatam | s3wong: okay nice | 18:35 |
| regXboi | s3wong: I see you want to defer the question of "which SG is matched" to the drivers, which is fair | 18:35 |
| s3wong | also adding unit test as I go along | 18:35 |
| SumitNaiksatam | regXboi: good point to bring up | 18:35 |
| regXboi | but that begs the question of how the driver in the patch set will handle that | 18:35 |
| SumitNaiksatam | so at this point, we think that the SG mapping is neutron resource mapping driver specific | 18:36 |
| regXboi | SumitNaiksatam: yes I think defering to the drivers is the right answer | 18:36 |
| regXboi | but if this includes a sample driver, that has to answer it :/ | 18:36 |
| s3wong | regXboi: yes, now it is rendered directly by the mapping driver | 18:36 |
| *** flaviof_zzz is now known as flaviof | 18:36 | |
| SumitNaiksatam | regXboi: in terms of patch logistics, this will be a new GPM-RMD-3 patch, right s3wong? | 18:37 |
| s3wong | SumitNaiksatam: that's correct | 18:37 |
| regXboi | works for me | 18:37 |
| regXboi | and I'll be reading when it arrives :) | 18:37 |
| SumitNaiksatam | okay any other questions for s3wong? | 18:38 |
| s3wong | so yeah, guys - stay tuned, patches will come soon | 18:38 |
| SumitNaiksatam | s3wong: any blockers for you at this point? | 18:38 |
| s3wong | SumitNaiksatam: no | 18:38 |
| s3wong | SumitNaiksatam: able to proceed well since you rebased | 18:39 |
| SumitNaiksatam | s3wong: ok good to hear | 18:39 |
| SumitNaiksatam | moving on | 18:39 |
| SumitNaiksatam | #topic CLI/Client | 18:39 |
| *** openstack changes topic to "CLI/Client (Meeting topic: networking_policy)" | 18:39 | |
| *** rudrarugge has joined #openstack-meeting-3 | 18:39 | |
| SumitNaiksatam | regXboi: we will get to your part in a bit | 18:39 |
| SumitNaiksatam | lets first get the update | 18:39 |
| SumitNaiksatam | songole: there? | 18:40 |
| songole | yes SumitNaiksatam | 18:40 |
| songole | Update: posted patches for all GBP resources | 18:40 |
| songole | tests are pending | 18:40 |
| songole | Need to handle mapping extension | 18:41 |
| LouisF | songole: what are patch numbers? | 18:41 |
| mandeep | songole: I have created a couple of public devstack VMs to do integration of the mapping driver, let me know if you need access to that. | 18:41 |
| songole | https://review.openstack.org/#/c/104013/ | 18:42 |
| songole | it has dependency links to others | 18:42 |
| regXboi | um | 18:42 |
| regXboi | that patch doesn't cover anything past -1 | 18:42 |
| regXboi | when are -2 and -3 going to be added? | 18:42 |
| songole | regXboi: they are all added | 18:43 |
| mandeep | regXboi: https://review.openstack.org/#/c/110798/ | 18:43 |
| *** rudrarug_ has quit IRC | 18:43 | |
| mandeep | regXboi: https://review.openstack.org/#/c/110806/ | 18:43 |
| SumitNaiksatam | songole: i am not sure i understood “Need to handle mapping extension” | 18:43 |
| songole | mandeep: thanks | 18:43 |
| mandeep | regXboi: (added links for the record) | 18:43 |
| regXboi | um... thos patches aren't listed in the wiki?!?! | 18:44 |
| regXboi | *those | 18:44 |
| songole | SumitNaiksatam: end point can take a port, l2 policy could take a network | 18:44 |
| songole | those options need to be added to CLI-1 | 18:44 |
| SumitNaiksatam | songole: oh okay, got it | 18:44 |
| SumitNaiksatam | regXboi: point noted | 18:45 |
| *** briancurtin has left #openstack-meeting-3 | 18:45 | |
| SumitNaiksatam | songole: can you please update the wiki page: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy/Patches | 18:45 |
| songole | mandeep: I will ping on reg those public devstack setups | 18:45 |
| songole | SumitNaiksatam: will do | 18:45 |
| regXboi | SumitNaiksatam, songole: thanks - I've been driving reviews based on that webpage | 18:45 |
| mandeep | songole: OK | 18:45 |
| SumitNaiksatam | btw, comment not directed just to songole, anyone if you see the wiki is outdated, please update with your patch link | 18:46 |
| SumitNaiksatam | *links | 18:46 |
| regXboi | ++ | 18:46 |
| SumitNaiksatam | regXboi: that was the reason we put the wiki, so you are right in going by that | 18:46 |
| mandeep | regXboi: agreed | 18:46 |
| SumitNaiksatam | songole: thats excellent progress, thanks much! | 18:46 |
| SumitNaiksatam | ok now to regXboi’s suggestion | 18:47 |
| SumitNaiksatam | #topic “Profiled” API | 18:47 |
| *** openstack changes topic to "“Profiled” API (Meeting topic: networking_policy)" | 18:47 | |
| SumitNaiksatam | regXboi: the floor is yours :-) | 18:47 |
| regXboi | folks have probably all seen the email, but let's link it in for the record | 18:47 |
| regXboi | the idea is to bring back support for the 2-group approach with minimal intrusiveness | 18:48 |
| regXboi | #link http://lists.openstack.org/pipermail/openstack-dev/2014-July/041467.html | 18:48 |
| SumitNaiksatam | regXboi: thanks was just about to post the link | 18:48 |
| regXboi | the suggestion is to do this as a patch on CLI-3 (call it CLI-4) because it is a departure from normal openstack convention | 18:49 |
| regXboi | and we can go that direction | 18:49 |
| SumitNaiksatam | regXboi: ah cool | 18:49 |
| regXboi | with the caveat that we may have to pry open the API to allow the CLI patch to make a single call to neutron | 18:49 |
| mandeep | regXboi: That also answer a few questions on what a "profiled API" is, | 18:50 |
| regXboi | IIRC the 2-group approach didn't discuss about reuse of policy information, so I have some freedom in trying to make that work | 18:50 |
| regXboi | mandeep: the idea of a profiled API come from IETF and other places | 18:50 |
| * regXboi goes and gets links | 18:50 | |
| mandeep | regXboi: The patch can also include diffs to other resources (as required), and we can review them as a single change | 18:51 |
| SumitNaiksatam | regXboi mandeep: i am still mystified by the term “profiled”, but i am just ignorant! | 18:51 |
| regXboi | examples of what I mean: | 18:51 |
| regXboi | OASIS (for SAMLv2): http://docs.oasis-open.org/security/saml/v2.0/saml-profiles-2.0-os.pdf | 18:51 |
| regXboi | Encryption and Checksum Specifications for Kerberos 5: http://tools.ietf.org/html/rfc3961 | 18:51 |
| regXboi | Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile: http://www.ietf.org/rfc/rfc3280.txt | 18:51 |
| SumitNaiksatam | regXboi: thanks | 18:51 |
| mandeep | regXboi: I am not familiar wit that, but it sounds like an interesting idea. | 18:51 |
| regXboi | Internet X.509 Public Key Infrastructure Qualified Certificates Profile: http://ftp.isi.edu/in-notes/rfc3039.txt | 18:51 |
| mandeep | regXboi: I will check the link. Thanks. | 18:52 |
| regXboi | the point being to define common sets of values for otherwise complex things | 18:52 |
| SumitNaiksatam | regXboi: can you explain what you mean by “we may have to pry open the API” | 18:52 |
| regXboi | SumiNaiksatam: sure | 18:52 |
| *** thomasem has joined #openstack-meeting-3 | 18:52 | |
| banix | SumitNaiksatam: looking at neutron client i do not see any command that leads to anything but a single crud call to neutron. don’t you think departure from that will be difficult? | 18:52 |
| regXboi | the issue that may arise is that the CLI is going to make multiple calls to neutron backend | 18:52 |
| regXboi | so if folks complain that is uncoventional, we may have to allow the CLI to make a single call and move the profile in to the API side of the patch | 18:53 |
| SumitNaiksatam | banix: yeah, this amounts to some orchestration on the client side | 18:53 |
| songole | regXboi: CLI is not an orchestrator today. Do you think heat might be a better place to put it? | 18:53 |
| regXboi | point folks: HEAT is already doing some orchestration on the client side | 18:53 |
| regXboi | songole: no... because that bypasses horizon | 18:54 |
| SumitNaiksatam | regXboi: i think we have some freedom to do the same orchestration in Horizon | 18:54 |
| regXboi | that's doing double the necessary work | 18:54 |
| mandeep | regXboi: If new orchestration is involved, do you think that we will need do a BP as well? | 18:54 |
| *** mfer has joined #openstack-meeting-3 | 18:54 | |
| *** thomasem has quit IRC | 18:54 | |
| regXboi | mandeep: I don't believe so but I don't *know* | 18:55 |
| SumitNaiksatam | i dont think we need a new BP if only client side changes are involved | 18:55 |
| regXboi | mestery might have some input here.... | 18:55 |
| mandeep | regXboi: Horizon equivalent of orchestration can be a wizard, but if needed it should be able to do the orchestration | 18:55 |
| SumitNaiksatam | mandeep: yeah, thats what i was thinking as well | 18:55 |
| mestery | regXboi: Lets discuss this and see, I don't know off the top of my head | 18:55 |
| mandeep | regXboi: But I will need to check if that is being done for now | 18:55 |
| regXboi | mandeep: that's not my point - somebody sharp might go "why are you doing this twice?" | 18:56 |
| SumitNaiksatam | mestery: any restrictions on doing some orchestration on the client side? | 18:56 |
| regXboi | and we won't have a good answer at that point | 18:56 |
| SumitNaiksatam | mestery: i am not aware that there are, but i dont think that there is a precedent either | 18:56 |
| mestery | SumitNaiksatam: ++, I'm not sure either | 18:56 |
| * regXboi is known for setting precedents :) | 18:56 | |
| SumitNaiksatam | regXboi: i think if its reasonable, there is always a first! | 18:57 |
| regXboi | anyway... that's the idea | 18:57 |
| regXboi | I was going to say I needed CLI-3 as a starting point | 18:57 |
| SumitNaiksatam | regXboi: okay thanks | 18:57 |
| regXboi | but now that is there :) | 18:57 |
| SumitNaiksatam | regXboi: yes we have to thank songole for getting it in expeditiously | 18:57 |
| mandeep | regXboi: A quick look at the example profile API links, I would have expected a BP for such a chnage. | 18:57 |
| LouisF | regXboi: should CLI be: neutron policy-apply [contract] [src group] [destination group] | 18:58 |
| regXboi | LouisF: I think policy-apply will need to change to be consistent with CLI-3 | 18:58 |
| rkukura | One thing to keep in mind is that the GP API in Juno will be considered experimental, so tweeks to make it more usable in Kilo are certainly possible, even breaking backward compatibility. This CLI approach could be thought of as a temporary workaround. | 18:58 |
| regXboi | rkukura: ++ | 18:58 |
| LouisF | rkukura: ++ | 18:59 |
| regXboi | mandeep: I'm not sure I agree with you, but that's just my opinion | 18:59 |
| *** mfer has quit IRC | 18:59 | |
| banix | mandeep: regXboi is not suggesting a generic profiled cli; just use of the concept; even that in my opinion it wont get through but i am a bit too cynic at this point | 18:59 |
| regXboi | banix: thanks for pointing that out | 18:59 |
| SumitNaiksatam | rkukura: agree | 18:59 |
| regXboi | I am *NOT* suggesting a general framework - that's a whole different kettle of fish | 18:59 |
| regXboi | I'm talking about a one off | 19:00 |
| mandeep | banix: Thanks for the clarification | 19:00 |
| mandeep | regXboi: But hopefully a one-off that sets a precedence for other similar updates ... ;-) | 19:00 |
| SumitNaiksatam | regXboi: it sounds perfectly reasonable to me suggest this approach in a patch | 19:00 |
| regXboi | anyway - we're at the top of the hour - any more questions? | 19:00 |
| mandeep | SumitNaiksatam: +1 | 19:00 |
| SumitNaiksatam | regXboi: thanks for that update and clarification | 19:00 |
| banix | I left a comment at #link https://review.openstack.org/#/c/103755/ a few days ago on Patch Set 3; i think regardless of what Ryan is suggesting this should be trivial to do; do you guys see any reason why it cannot be done? | 19:00 |
| SumitNaiksatam | banix: sorry i missed that | 19:01 |
| regXboi | and if I'm not here - reply to the thread on the ML | 19:01 |
| SumitNaiksatam | banix: until you pointed out in the email thread | 19:01 |
| SumitNaiksatam | banix: i will respond | 19:01 |
| SumitNaiksatam | #topic API Intercept | 19:01 |
| *** openstack changes topic to "API Intercept (Meeting topic: networking_policy)" | 19:01 | |
| * regXboi pads away | 19:01 | |
| SumitNaiksatam | just a quick plug for the work kevinbenton has been doing #link https://review.openstack.org/#/c/109901 | 19:01 |
| SumitNaiksatam | #topic Open Discussion | 19:02 |
| *** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)" | 19:02 | |
| SumitNaiksatam | we will need to wrap up quickly since we are over | 19:02 |
| SumitNaiksatam | we did not touch on the vendor drivers today | 19:02 |
| rkukura | I’ve started looking at the intercept patch, but need to spend more time to understand it. | 19:02 |
| SumitNaiksatam | but hopefully people are thinking about it and are not overly blocked | 19:02 |
| mandeep | Same here | 19:02 |
| SumitNaiksatam | rkukura mandeep: thanks | 19:03 |
| rms_13 | +1 | 19:03 |
| SumitNaiksatam | rms_13: any quick update on Horizon? | 19:03 |
| SumitNaiksatam | horizon integration that is | 19:03 |
| rms_13 | Not today. For sure next thursday as I am going to work full time on it tomorrow | 19:03 |
| SumitNaiksatam | rms_13: nice, looking forward to it | 19:03 |
| rms_13 | Abishek is going to do initial glance | 19:03 |
| SumitNaiksatam | rms_13: okay | 19:03 |
| SumitNaiksatam | rms_13: you might want to look at songole’s new patches | 19:04 |
| rms_13 | Yes. That is going to change my current patch | 19:04 |
| SumitNaiksatam | alright anything else, anyone? | 19:04 |
| SumitNaiksatam | alright, thanks all for joining | 19:05 |
| banix | bye | 19:05 |
| rms_13 | by | 19:05 |
| songole | bye | 19:05 |
| rkukura | bye | 19:05 |
| SumitNaiksatam | until next week, but please keep reviewing | 19:05 |
| LouisF | rms_13: has horizon ptach been updated? | 19:05 |
| SumitNaiksatam | bye | 19:05 |
| *** regXboi has left #openstack-meeting-3 | 19:05 | |
| *** banix has quit IRC | 19:05 | |
| mandeep | bye | 19:05 |
| SumitNaiksatam | #endmeeting | 19:05 |
| *** rkukura has left #openstack-meeting-3 | 19:05 | |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 19:05 | |
| openstack | Meeting ended Thu Jul 31 19:05:45 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:05 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-07-31-18.00.html | 19:05 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-07-31-18.00.txt | 19:05 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-07-31-18.00.log.html | 19:05 |
| rms_13 | LouisF: no | 19:05 |
| SumitNaiksatam | LouisF: i think rms_13 plans to do that tomorrow | 19:05 |
| *** songole has left #openstack-meeting-3 | 19:05 | |
| SumitNaiksatam | or starting tomorrow | 19:06 |
| LouisF | rms_13: thx | 19:06 |
| rms_13 | But its always good to take a look. | 19:06 |
| rms_13 | Whatever is there is going to stay with API changes only | 19:06 |
| rms_13 | So review comments will be appreciated | 19:06 |
| *** Qijing has quit IRC | 19:07 | |
| *** KrishnaK_ has quit IRC | 19:07 | |
| *** ivar-lazzaro has quit IRC | 19:12 | |
| *** mandeep has quit IRC | 19:13 | |
| *** pballand has joined #openstack-meeting-3 | 19:19 | |
| *** LouisF has quit IRC | 19:23 | |
| *** coolsvap has quit IRC | 19:24 | |
| *** banix has joined #openstack-meeting-3 | 19:27 | |
| *** yamamoto has joined #openstack-meeting-3 | 19:29 | |
| *** coolsvap has joined #openstack-meeting-3 | 19:29 | |
| *** yamamoto has quit IRC | 19:34 | |
| *** jcoufal has quit IRC | 19:39 | |
| *** jcoufal has joined #openstack-meeting-3 | 19:40 | |
| *** Sukhdev has quit IRC | 19:46 | |
| *** chuckC has quit IRC | 19:47 | |
| *** jaypipes has joined #openstack-meeting-3 | 19:55 | |
| *** thomasem has joined #openstack-meeting-3 | 20:05 | |
| *** peristeri has quit IRC | 20:05 | |
| *** chuckC has joined #openstack-meeting-3 | 20:08 | |
| *** thomasem has quit IRC | 20:09 | |
| *** peristeri has joined #openstack-meeting-3 | 20:10 | |
| *** eghobo has joined #openstack-meeting-3 | 20:17 | |
| *** peristeri has quit IRC | 20:23 | |
| *** thomasem has joined #openstack-meeting-3 | 20:26 | |
| *** SumitNaiksatam has quit IRC | 20:30 | |
| *** thomasem has quit IRC | 20:44 | |
| *** nelsnelson has quit IRC | 20:46 | |
| *** yamamoto has joined #openstack-meeting-3 | 20:48 | |
| *** thomasem has joined #openstack-meeting-3 | 20:51 | |
| *** yamamoto has quit IRC | 20:53 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 20:55 | |
| *** nelsnelson has joined #openstack-meeting-3 | 20:57 | |
| *** mfer has joined #openstack-meeting-3 | 20:57 | |
| *** thomasem_ has joined #openstack-meeting-3 | 21:02 | |
| *** sgordon has joined #openstack-meeting-3 | 21:02 | |
| *** thomasem has quit IRC | 21:05 | |
| *** thomasem has joined #openstack-meeting-3 | 21:07 | |
| *** openstack has joined #openstack-meeting-3 | 21:08 | |
| *** ChanServ sets mode: +o openstack | 21:08 | |
| *** flaviof is now known as flaviof_zzz | 21:08 | |
| *** armax has quit IRC | 21:08 | |
| *** yamamoto has joined #openstack-meeting-3 | 21:09 | |
| *** sgordon has left #openstack-meeting-3 | 21:10 | |
| *** thomasem_ has quit IRC | 21:10 | |
| *** thomasem has quit IRC | 21:11 | |
| *** mrunge has quit IRC | 21:11 | |
| *** yamamoto has quit IRC | 21:22 | |
| *** banix has quit IRC | 21:32 | |
| *** ivar-lazzaro has joined #openstack-meeting-3 | 21:40 | |
| *** mestery has quit IRC | 21:53 | |
| *** mestery has joined #openstack-meeting-3 | 21:54 | |
| *** nelsnelson has quit IRC | 21:57 | |
| *** yamamoto has joined #openstack-meeting-3 | 21:59 | |
| *** rfolco has quit IRC | 22:00 | |
| *** yamamoto has quit IRC | 22:03 | |
| *** otherwiseguy has quit IRC | 22:04 | |
| *** otherwiseguy has joined #openstack-meeting-3 | 22:09 | |
| *** mfer has quit IRC | 22:15 | |
| *** armax has joined #openstack-meeting-3 | 22:22 | |
| *** mestery has quit IRC | 22:22 | |
| *** mestery has joined #openstack-meeting-3 | 22:23 | |
| *** rms_13 has quit IRC | 22:27 | |
| *** igordcard has joined #openstack-meeting-3 | 22:27 | |
| *** mfer has joined #openstack-meeting-3 | 22:38 | |
| *** jcoufal has quit IRC | 22:39 | |
| *** jcoufal has joined #openstack-meeting-3 | 22:40 | |
| *** mikal_ is now known as mikal | 22:40 | |
| *** stanzgy has joined #openstack-meeting-3 | 22:42 | |
| *** HenryG has quit IRC | 22:45 | |
| *** safchain has quit IRC | 22:46 | |
| *** igordcard has quit IRC | 22:55 | |
| *** igordcard has joined #openstack-meeting-3 | 22:56 | |
| *** yamamoto has joined #openstack-meeting-3 | 22:59 | |
| *** carl_baldwin has quit IRC | 23:01 | |
| *** yamamoto has quit IRC | 23:03 | |
| *** tsufiev has quit IRC | 23:04 | |
| *** jcoufal has quit IRC | 23:05 | |
| *** tsufiev has joined #openstack-meeting-3 | 23:09 | |
| *** pballand has quit IRC | 23:18 | |
| *** jaypipes has quit IRC | 23:27 | |
| *** pballand has joined #openstack-meeting-3 | 23:40 | |
| *** s3wong has quit IRC | 23:43 | |
| *** pballand has quit IRC | 23:44 | |
| *** yamamoto has joined #openstack-meeting-3 | 23:48 | |
| *** yamamoto has quit IRC | 23:53 | |
| *** alexpilotti has quit IRC | 23:58 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!