*** nati_ueno has quit IRC | 00:01 | |
*** yamahata_ has joined #openstack-meeting-alt | 00:02 | |
*** grapex has quit IRC | 00:08 | |
*** derekh has quit IRC | 00:09 | |
*** amotoki is now known as __amotoki__ | 00:14 | |
*** rongze has joined #openstack-meeting-alt | 00:16 | |
*** rongze has quit IRC | 00:20 | |
*** yamahata_ has quit IRC | 00:22 | |
*** yamahata_ has joined #openstack-meeting-alt | 00:22 | |
*** dosaboy has quit IRC | 00:23 | |
*** MarkAtwood has quit IRC | 00:24 | |
*** boris-42 has joined #openstack-meeting-alt | 00:32 | |
*** alazarev has joined #openstack-meeting-alt | 00:36 | |
*** julim has joined #openstack-meeting-alt | 00:37 | |
*** zane has joined #openstack-meeting-alt | 00:37 | |
*** julim has quit IRC | 00:46 | |
*** cody-somerville has quit IRC | 00:48 | |
*** devlaps has quit IRC | 00:56 | |
*** nati_ueno has joined #openstack-meeting-alt | 00:56 | |
*** nati_ueno has quit IRC | 00:57 | |
*** nati_ueno has joined #openstack-meeting-alt | 01:00 | |
*** nati_ueno has quit IRC | 01:00 | |
*** cody-somerville has joined #openstack-meeting-alt | 01:02 | |
*** nati_ueno has joined #openstack-meeting-alt | 01:05 | |
*** gduan has joined #openstack-meeting-alt | 01:05 | |
*** nati_ueno has quit IRC | 01:06 | |
*** nati_ueno has joined #openstack-meeting-alt | 01:06 | |
*** garyduan has quit IRC | 01:07 | |
*** alazarev has quit IRC | 01:07 | |
*** amytron has quit IRC | 01:11 | |
*** yogesh has joined #openstack-meeting-alt | 01:12 | |
*** boris-42 has quit IRC | 01:20 | |
*** alazarev has joined #openstack-meeting-alt | 01:23 | |
*** DennyZhang has joined #openstack-meeting-alt | 01:24 | |
*** nosnos has joined #openstack-meeting-alt | 01:30 | |
*** amcrn has quit IRC | 01:31 | |
*** yogesh has quit IRC | 01:36 | |
*** yogesh has joined #openstack-meeting-alt | 01:37 | |
*** sarob has joined #openstack-meeting-alt | 01:37 | |
*** gokrokve has joined #openstack-meeting-alt | 01:38 | |
*** yogesh has quit IRC | 01:41 | |
*** gokrokve has quit IRC | 01:43 | |
*** rongze has joined #openstack-meeting-alt | 01:47 | |
*** _ozstacker_ has joined #openstack-meeting-alt | 01:49 | |
*** ozstacker has quit IRC | 01:50 | |
*** rongze has quit IRC | 01:51 | |
*** alazarev has quit IRC | 01:56 | |
*** sarob has quit IRC | 01:58 | |
*** eankutse has joined #openstack-meeting-alt | 01:58 | |
*** alazarev has joined #openstack-meeting-alt | 01:59 | |
*** alazarev has quit IRC | 02:00 | |
*** nati_uen_ has joined #openstack-meeting-alt | 02:00 | |
*** zane has quit IRC | 02:03 | |
*** nati_ueno has quit IRC | 02:04 | |
*** DennyZhang has quit IRC | 02:05 | |
*** tanisdl has quit IRC | 02:06 | |
*** nati_uen_ has quit IRC | 02:15 | |
*** nati_ueno has joined #openstack-meeting-alt | 02:16 | |
*** sarob has joined #openstack-meeting-alt | 02:18 | |
*** demorris has joined #openstack-meeting-alt | 02:20 | |
*** rongze has joined #openstack-meeting-alt | 02:22 | |
*** boris-42 has joined #openstack-meeting-alt | 02:24 | |
*** Barker has joined #openstack-meeting-alt | 02:32 | |
*** bdpayne has quit IRC | 02:37 | |
*** flwang has quit IRC | 02:41 | |
*** yamahata_ has quit IRC | 02:42 | |
*** eankutse has quit IRC | 02:43 | |
*** alazarev has joined #openstack-meeting-alt | 02:48 | |
*** alazarev has quit IRC | 02:48 | |
*** ashaikh has quit IRC | 02:53 | |
*** sarob has quit IRC | 02:55 | |
*** sarob has joined #openstack-meeting-alt | 02:56 | |
*** nicole has joined #openstack-meeting-alt | 02:57 | |
*** nicole is now known as Guest10686 | 02:57 | |
*** demorris has quit IRC | 02:59 | |
*** sarob has quit IRC | 03:00 | |
*** zane has joined #openstack-meeting-alt | 03:03 | |
*** nati_uen_ has joined #openstack-meeting-alt | 03:10 | |
*** nati_ueno has quit IRC | 03:14 | |
*** twoputt has quit IRC | 03:16 | |
*** twoputt_ has quit IRC | 03:17 | |
*** DennyZhang has joined #openstack-meeting-alt | 03:25 | |
*** kraman has joined #openstack-meeting-alt | 03:33 | |
*** kraman1 has joined #openstack-meeting-alt | 03:35 | |
*** Barker has quit IRC | 03:38 | |
*** kraman has quit IRC | 03:38 | |
*** Barker has joined #openstack-meeting-alt | 03:38 | |
*** nati_uen_ has quit IRC | 03:39 | |
*** coolsvap has joined #openstack-meeting-alt | 03:40 | |
*** nati_ueno has joined #openstack-meeting-alt | 03:40 | |
*** gokrokve has joined #openstack-meeting-alt | 03:50 | |
*** Barker has quit IRC | 03:54 | |
*** flwang has joined #openstack-meeting-alt | 03:54 | |
*** boris-42 has quit IRC | 03:57 | |
*** nati_uen_ has joined #openstack-meeting-alt | 03:57 | |
*** boris-42 has joined #openstack-meeting-alt | 03:57 | |
*** gokrokve has quit IRC | 03:58 | |
*** nati_uen_ has quit IRC | 03:58 | |
*** gokrokve has joined #openstack-meeting-alt | 03:59 | |
*** nati_ueno has quit IRC | 04:01 | |
*** coolsvap has quit IRC | 04:19 | |
*** coolsvap has joined #openstack-meeting-alt | 04:21 | |
*** coolsvap has quit IRC | 04:27 | |
*** coolsvap_ has joined #openstack-meeting-alt | 04:27 | |
*** coolsvap_ has left #openstack-meeting-alt | 04:28 | |
*** coolsvap has joined #openstack-meeting-alt | 04:39 | |
*** coolsvap has quit IRC | 04:44 | |
*** coolsvap has joined #openstack-meeting-alt | 04:45 | |
*** coolsvap has quit IRC | 04:50 | |
*** coolsvap has joined #openstack-meeting-alt | 04:53 | |
*** nati_ueno has joined #openstack-meeting-alt | 04:57 | |
*** akuznetsov has joined #openstack-meeting-alt | 04:58 | |
*** DennyZhang has quit IRC | 04:59 | |
*** gokrokve has joined #openstack-meeting-alt | 05:01 | |
*** radix_ has quit IRC | 05:05 | |
*** gokrokve has quit IRC | 05:06 | |
*** Guest10686 has quit IRC | 05:11 | |
*** bdpayne has joined #openstack-meeting-alt | 05:12 | |
*** ashaikh has joined #openstack-meeting-alt | 05:15 | |
*** IlyaE has joined #openstack-meeting-alt | 05:20 | |
*** yogesh has joined #openstack-meeting-alt | 05:23 | |
*** yogesh has quit IRC | 05:28 | |
*** bdpayne has quit IRC | 05:31 | |
*** sarob has joined #openstack-meeting-alt | 05:39 | |
*** yogesh has joined #openstack-meeting-alt | 05:42 | |
*** sarob has quit IRC | 05:43 | |
*** SergeyLukjanov has joined #openstack-meeting-alt | 05:48 | |
*** yogesh has quit IRC | 05:49 | |
*** yogesh has joined #openstack-meeting-alt | 05:50 | |
*** yogesh has quit IRC | 05:51 | |
*** IlyaE has quit IRC | 05:58 | |
*** gokrokve has joined #openstack-meeting-alt | 06:02 | |
*** yogesh has joined #openstack-meeting-alt | 06:04 | |
*** gokrokve has quit IRC | 06:07 | |
*** akuznetsov has quit IRC | 06:08 | |
*** alazarev has joined #openstack-meeting-alt | 06:08 | |
*** akuznetsov has joined #openstack-meeting-alt | 06:11 | |
*** IlyaE has joined #openstack-meeting-alt | 06:11 | |
*** alazarev has quit IRC | 06:19 | |
*** IlyaE has quit IRC | 06:29 | |
*** yogesh has quit IRC | 06:31 | |
*** yogesh has joined #openstack-meeting-alt | 06:31 | |
*** yogesh has quit IRC | 06:32 | |
*** yogesh has joined #openstack-meeting-alt | 06:32 | |
*** IlyaE has joined #openstack-meeting-alt | 06:47 | |
*** nosnos has quit IRC | 06:48 | |
*** nosnos has joined #openstack-meeting-alt | 06:48 | |
*** IlyaE has quit IRC | 06:56 | |
*** kraman1 has quit IRC | 06:57 | |
*** zane has quit IRC | 06:59 | |
*** NikitaKonovalov has joined #openstack-meeting-alt | 06:59 | |
*** SergeyLukjanov has quit IRC | 06:59 | |
*** NikitaKonovalov has quit IRC | 07:00 | |
*** gokrokve has joined #openstack-meeting-alt | 07:00 | |
*** gokrokve has quit IRC | 07:05 | |
*** yogesh has quit IRC | 07:06 | |
*** yogesh has joined #openstack-meeting-alt | 07:07 | |
*** yogesh has quit IRC | 07:07 | |
*** yogesh has joined #openstack-meeting-alt | 07:08 | |
*** alazarev has joined #openstack-meeting-alt | 07:11 | |
*** jcoufal has joined #openstack-meeting-alt | 07:14 | |
*** akuznetsov has quit IRC | 07:15 | |
*** radix_ has joined #openstack-meeting-alt | 07:17 | |
*** nimi has left #openstack-meeting-alt | 07:26 | |
*** denis_makogon_ has joined #openstack-meeting-alt | 07:28 | |
*** akuznetsov has joined #openstack-meeting-alt | 07:32 | |
*** alazarev has quit IRC | 07:33 | |
*** akuznetsov has quit IRC | 07:34 | |
*** nati_ueno has quit IRC | 07:40 | |
*** nati_ueno has joined #openstack-meeting-alt | 07:43 | |
*** sacharya has quit IRC | 07:44 | |
*** sacharya has joined #openstack-meeting-alt | 07:44 | |
*** sacharya has quit IRC | 07:44 | |
*** kraman has joined #openstack-meeting-alt | 07:44 | |
*** sacharya has joined #openstack-meeting-alt | 07:45 | |
*** ashaikh has quit IRC | 07:45 | |
*** gokrokve has joined #openstack-meeting-alt | 08:00 | |
*** gokrokve_ has joined #openstack-meeting-alt | 08:02 | |
*** gokrokve has quit IRC | 08:05 | |
*** akuznetsov has joined #openstack-meeting-alt | 08:05 | |
*** jtomasek has joined #openstack-meeting-alt | 08:05 | |
*** gokrokve_ has quit IRC | 08:07 | |
*** kraman has quit IRC | 08:18 | |
*** SergeyLukjanov has joined #openstack-meeting-alt | 08:21 | |
*** flaper87|afk is now known as flaper87 | 08:21 | |
*** nosnos_ has joined #openstack-meeting-alt | 08:30 | |
*** sacharya has quit IRC | 08:32 | |
*** nosnos has quit IRC | 08:33 | |
*** boris-42 has quit IRC | 08:41 | |
*** kraman has joined #openstack-meeting-alt | 08:45 | |
*** jtomasek has quit IRC | 08:45 | |
*** ruhe has joined #openstack-meeting-alt | 08:47 | |
*** jtomasek has joined #openstack-meeting-alt | 08:47 | |
*** kraman has quit IRC | 08:49 | |
*** rossella_s has joined #openstack-meeting-alt | 08:55 | |
*** rsblendido has joined #openstack-meeting-alt | 08:55 | |
*** derekh has joined #openstack-meeting-alt | 08:58 | |
*** gokrokve has joined #openstack-meeting-alt | 09:00 | |
*** flwang has quit IRC | 09:01 | |
*** gokrokve has quit IRC | 09:05 | |
*** plomakin has joined #openstack-meeting-alt | 09:06 | |
*** yamahata_ has joined #openstack-meeting-alt | 09:14 | |
*** dosaboy has joined #openstack-meeting-alt | 09:17 | |
*** dosaboy has quit IRC | 09:19 | |
*** dosaboy has joined #openstack-meeting-alt | 09:19 | |
*** IlyaE has joined #openstack-meeting-alt | 09:21 | |
*** ruhe has quit IRC | 09:22 | |
*** coolsvap is now known as coolsvap[A] | 09:36 | |
*** coolsvap[A] is now known as coolsvap | 09:39 | |
*** yamahata_ has quit IRC | 09:40 | |
*** dosaboy has quit IRC | 09:43 | |
*** dosaboy has joined #openstack-meeting-alt | 09:43 | |
*** kraman has joined #openstack-meeting-alt | 09:45 | |
*** gokrokve has joined #openstack-meeting-alt | 09:45 | |
*** boris-42 has joined #openstack-meeting-alt | 09:48 | |
*** gokrokve has quit IRC | 09:50 | |
*** jtomasek has quit IRC | 09:51 | |
*** boris-42 has quit IRC | 09:52 | |
*** yogesh has quit IRC | 09:53 | |
*** yogesh has joined #openstack-meeting-alt | 09:53 | |
*** plomakin has quit IRC | 09:55 | |
*** nati_ueno has quit IRC | 09:55 | |
*** plomakin has joined #openstack-meeting-alt | 09:55 | |
*** jtomasek has joined #openstack-meeting-alt | 09:55 | |
*** yogesh has quit IRC | 09:58 | |
*** aignatov has joined #openstack-meeting-alt | 09:58 | |
*** ruhe has joined #openstack-meeting-alt | 09:58 | |
*** akuznetsov has quit IRC | 09:59 | |
*** SergeyLukjanov is now known as _SergeyLukjanov | 09:59 | |
*** gokrokve has joined #openstack-meeting-alt | 10:00 | |
*** gokrokve has quit IRC | 10:05 | |
*** jcoufal has quit IRC | 10:09 | |
*** coolsvap is now known as coolsvap[A] | 10:09 | |
*** kraman has quit IRC | 10:18 | |
*** yamahata_ has joined #openstack-meeting-alt | 10:21 | |
*** ruhe has quit IRC | 10:31 | |
*** yamahata_ has quit IRC | 10:33 | |
*** nati_ueno has joined #openstack-meeting-alt | 10:37 | |
*** akuznetsov has joined #openstack-meeting-alt | 10:38 | |
*** coolsvap[A] is now known as coolsvap | 10:38 | |
*** IlyaE has quit IRC | 10:39 | |
*** ruhe has joined #openstack-meeting-alt | 10:41 | |
*** IlyaE has joined #openstack-meeting-alt | 10:44 | |
*** IlyaE has quit IRC | 10:45 | |
*** kraman has joined #openstack-meeting-alt | 10:45 | |
*** IlyaE has joined #openstack-meeting-alt | 10:47 | |
*** aignatov has quit IRC | 10:47 | |
*** IlyaE has quit IRC | 10:48 | |
*** aignatov has joined #openstack-meeting-alt | 10:48 | |
*** kraman has quit IRC | 10:50 | |
*** rongze has quit IRC | 10:53 | |
*** NikitaKonovalov has joined #openstack-meeting-alt | 10:53 | |
*** rongze has joined #openstack-meeting-alt | 10:53 | |
*** rongze has quit IRC | 10:59 | |
*** SergeyLukjanov has joined #openstack-meeting-alt | 10:59 | |
*** gokrokve has joined #openstack-meeting-alt | 11:00 | |
*** gokrokve has quit IRC | 11:05 | |
*** coolsvap has quit IRC | 11:08 | |
*** sergmelikyan has joined #openstack-meeting-alt | 11:11 | |
*** coolsvap has joined #openstack-meeting-alt | 11:13 | |
*** nosnos_ has quit IRC | 11:20 | |
*** nosnos has joined #openstack-meeting-alt | 11:21 | |
*** nosnos has quit IRC | 11:25 | |
*** coolsvap has quit IRC | 11:37 | |
*** boris-42 has joined #openstack-meeting-alt | 11:45 | |
*** kraman has joined #openstack-meeting-alt | 11:45 | |
*** yamahata_ has joined #openstack-meeting-alt | 11:50 | |
*** gokrokve has joined #openstack-meeting-alt | 12:00 | |
*** NikitaKonovalov has quit IRC | 12:05 | |
*** gokrokve has quit IRC | 12:05 | |
*** NikitaKonovalov has joined #openstack-meeting-alt | 12:11 | |
*** ruhe has quit IRC | 12:15 | |
*** nati_ueno has quit IRC | 12:18 | |
*** kraman has quit IRC | 12:18 | |
*** ruhe has joined #openstack-meeting-alt | 12:26 | |
*** coolsvap has joined #openstack-meeting-alt | 12:30 | |
*** NikitaKonovalov has quit IRC | 12:32 | |
*** vkmc has joined #openstack-meeting-alt | 12:37 | |
*** jprovazn has joined #openstack-meeting-alt | 12:42 | |
*** NikitaKonovalov has joined #openstack-meeting-alt | 12:44 | |
*** kraman has joined #openstack-meeting-alt | 12:45 | |
*** pcm_ has joined #openstack-meeting-alt | 12:47 | |
*** kraman has quit IRC | 12:49 | |
*** flwang has joined #openstack-meeting-alt | 12:51 | |
*** rongze has joined #openstack-meeting-alt | 12:52 | |
*** rongze_ has joined #openstack-meeting-alt | 12:54 | |
*** pdmars has joined #openstack-meeting-alt | 12:55 | |
*** rongze has quit IRC | 12:58 | |
*** pdmars has quit IRC | 12:59 | |
*** coolsvap is now known as coolsvap_away | 12:59 | |
*** gokrokve has joined #openstack-meeting-alt | 13:00 | |
*** rongze_ has quit IRC | 13:02 | |
*** pdmars has joined #openstack-meeting-alt | 13:02 | |
*** rongze has joined #openstack-meeting-alt | 13:04 | |
*** gokrokve has quit IRC | 13:05 | |
*** demorris has joined #openstack-meeting-alt | 13:07 | |
*** kevinconway has joined #openstack-meeting-alt | 13:08 | |
*** ruhe has quit IRC | 13:12 | |
*** ruhe has joined #openstack-meeting-alt | 13:17 | |
*** demorris has quit IRC | 13:25 | |
*** marios has quit IRC | 13:41 | |
*** kraman has joined #openstack-meeting-alt | 13:45 | |
*** jergerber has joined #openstack-meeting-alt | 13:45 | |
*** demorris has joined #openstack-meeting-alt | 13:46 | |
*** noslzzp has joined #openstack-meeting-alt | 13:46 | |
*** lblanchard has joined #openstack-meeting-alt | 13:50 | |
*** jergerber has quit IRC | 13:52 | |
*** dprince has joined #openstack-meeting-alt | 13:53 | |
*** ilyashakhat has quit IRC | 13:55 | |
*** jergerber has joined #openstack-meeting-alt | 13:55 | |
*** yamahata_ has quit IRC | 13:57 | |
*** yamahata_ has joined #openstack-meeting-alt | 13:58 | |
*** zhiyan has joined #openstack-meeting-alt | 14:00 | |
*** gokrokve has joined #openstack-meeting-alt | 14:00 | |
markwash | good morning glance folks | 14:00 |
---|---|---|
rosmaita | o/ | 14:00 |
rosmaita | markwash: link to agenda etherpad? | 14:01 |
zhiyan | good morning/evening! | 14:01 |
zhiyan | https://etherpad.openstack.org/p/glance-team-meeting-agenda | 14:01 |
markwash | do we have any other folks here as well? | 14:01 |
*** demorris has quit IRC | 14:01 | |
markwash | iccha: nikhil__ flwang flaper87 ameade | 14:02 |
flaper87 | o/ | 14:02 |
flaper87 | gooood morning | 14:02 |
markwash | I suppose we should get started | 14:02 |
rosmaita | zhiyan: thanks and good evening | 14:02 |
markwash | #startmeeting glance | 14:02 |
openstack | Meeting started Thu Nov 21 14:02:56 2013 UTC and is due to finish in 60 minutes. The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:02 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:02 |
*** openstack changes topic to " (Meeting topic: glance)" | 14:02 | |
openstack | The meeting name has been set to 'glance' | 14:03 |
markwash | #link https://etherpad.openstack.org/p/glance-team-meeting-agenda | 14:03 |
zhiyan | rosmaita: :) | 14:03 |
markwash | First a couple of announcements | 14:03 |
markwash | #topic icehouse-1 | 14:03 |
*** openstack changes topic to "icehouse-1 (Meeting topic: glance)" | 14:04 | |
markwash | icehouse-1 is rapidly approaching | 14:04 |
markwash | I think its due to be cut on December 5th | 14:04 |
markwash | maybe a day earlier | 14:04 |
flaper87 | markwash: correct | 14:04 |
flaper87 | Dec 5th | 14:04 |
flaper87 | AFAIK | 14:04 |
zhiyan | ~2 weeks later | 14:04 |
flaper87 | #link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule | 14:04 |
*** gokrokve has quit IRC | 14:04 | |
markwash | #link https://launchpad.net/glance/+milestone/icehouse-1 | 14:04 |
* flaper87 just targeted https://blueprints.launchpad.net/glance/+spec/oslo-messaging for i-1 since the patch is already there | 14:05 | |
flaper87 | feel free to push it back | 14:05 |
*** aignatov has quit IRC | 14:05 | |
markwash | since I was triaging so close to the deadline, i mostly pushed stuff to icehouse-2 | 14:05 |
markwash | but that's just a projection, anything that we think we can land can go ahead | 14:05 |
markwash | flaper87: great! thanks | 14:05 |
markwash | if folks have other bps they want to land soon, go ahead and target them to i-1 so we can focus review efforts possibly | 14:06 |
zhiyan | markwash: before that ,can i ask you help check/approval bp first? | 14:06 |
markwash | yes | 14:06 |
markwash | wanna link them here now so I have a little todo list we can check back on? | 14:06 |
*** yamahata_ has quit IRC | 14:07 | |
*** yamahata_ has joined #openstack-meeting-alt | 14:08 | |
rosmaita | markwash: there are 2 more bugs along the lines of #1251518 that should be targeted for i-1 | 14:08 |
markwash | hmm, can I trouble you for the full links? when I click on the #<number> I get a lonely empty freenode room :-) | 14:09 |
* rosmaita is looking for them | 14:09 | |
rosmaita | https://bugs.launchpad.net/bugs/1251518 | 14:10 |
rosmaita | https://bugs.launchpad.net/glance/+bug/1252459 | 14:10 |
rosmaita | https://bugs.launchpad.net/glance/+bug/1252337 | 14:10 |
*** coolsvap_away is now known as coolsvap | 14:10 | |
markwash | great | 14:11 |
markwash | those look important! | 14:11 |
markwash | I'm inclined to make them I-1 critical | 14:11 |
rosmaita | i do what i can | 14:11 |
flaper87 | rosmaita: +1 | 14:12 |
rosmaita | i think Alex is already working on them, too | 14:12 |
markwash | just to hold our own feet to the fire | 14:12 |
flaper87 | I saw them yday, they are important | 14:12 |
flaper87 | markwash: +1 for critical | 14:12 |
markwash | zhiyan: if you can, please link the bps you are thinking about in here before meeting end, or just email them to me | 14:12 |
markwash | otherwise, are there any other i-1 pressing concerns? | 14:12 |
flaper87 | I saw ameade is already assigned, I guess he's working on them | 14:13 |
flaper87 | we should encourage him to ping core devs directly for review on those bugs | 14:13 |
*** eankutse has joined #openstack-meeting-alt | 14:13 | |
rosmaita | flaper87: +1 | 14:13 |
flaper87 | otherwise we'll get to the i-1 cut w/o even having looked at them | 14:13 |
flaper87 | :D | 14:13 |
markwash | yeah, especially since the review queue is still a bit long | 14:13 |
flaper87 | yeah | 14:13 |
*** eankutse has quit IRC | 14:14 | |
markwash | (segue!) | 14:14 |
*** eankutse has joined #openstack-meeting-alt | 14:14 | |
markwash | well, almost | 14:14 |
markwash | next topic! | 14:14 |
markwash | #topic glanceclient version 1.0.0 | 14:14 |
*** openstack changes topic to "glanceclient version 1.0.0 (Meeting topic: glance)" | 14:14 | |
markwash | I created a new development series in python-glanceclient on launchpad called v1 | 14:15 |
markwash | its my intention that bugfixes/bps that are technically breaking changes could be targeted to that | 14:15 |
flaper87 | markwash: can you quickly summarize what are the breaking changes introduced in the new release ? | 14:15 |
flaper87 | I think I lost track of some of those | 14:15 |
markwash | yeah, there are a few I know of | 14:16 |
markwash | but I want to make sure other folks can suggest and evaluate them | 14:16 |
markwash | 1) drop legacy cli | 14:16 |
*** NikitaKonovalov has quit IRC | 14:16 | |
markwash | 2) change default page size | 14:16 |
markwash | 3) maybe something with better version handling for endpoints | 14:16 |
markwash | 4) I'd actually like to switch to requests which means at least temporarily losing control over ssl compression | 14:17 |
markwash | 5) in the CLI, don't create an image if no arguments are passed to image-create | 14:17 |
markwash | I've also been trying to figure out how we will stage and manage all these changes | 14:17 |
flaper87 | 1) +1 2) Shouldn't we enforce this server side? 3) +1 4) +1 5) BIG +1 | 14:18 |
*** kraman has quit IRC | 14:18 | |
flaper87 | re 4) I did some work there | 14:18 |
flaper87 | I ended up abandoning the patch because of the ssl thing | 14:18 |
flaper87 | Actually | 14:18 |
markwash | flaper87: yeah, I think for #2 we really need the default on the client to be to send nothing, so the server can pick | 14:18 |
markwash | yeah, I was just looking at that patch | 14:18 |
flaper87 | I didn't abandoned it because of that. I workarounded the whole ssl thing | 14:18 |
markwash | bcwaldon was working on rebasing it a while back as well | 14:19 |
flaper87 | and kept the compression code Stuard worked on | 14:19 |
flaper87 | but it got lost somewhere | 14:19 |
flaper87 | cool | 14:19 |
flaper87 | I'm +1 for using requests | 14:19 |
markwash | I've been working on finding a place for staging all these changes | 14:19 |
markwash | and sent an email to the list | 14:19 |
markwash | #link http://lists.openstack.org/pipermail/openstack-dev/2013-November/019911.html | 14:20 |
*** NikitaKonovalov has joined #openstack-meeting-alt | 14:20 | |
*** ashwini has joined #openstack-meeting-alt | 14:20 | |
*** flwang has quit IRC | 14:20 | |
markwash | so that about sums that part up, any other thoughts on the glanceclient? | 14:20 |
markwash | cool | 14:21 |
flaper87 | we should consider to take some of the code that currently exists in nova and pull it in | 14:21 |
flaper87 | remember that patch that got blocked ? | 14:21 |
markwash | yes | 14:21 |
flaper87 | maybe find a better way to do that | 14:21 |
markwash | I strongly agree | 14:21 |
markwash | especially as location stuff gets a little more complicated and better presented | 14:22 |
flaper87 | +1 | 14:22 |
zhiyan | markwash: +1 | 14:22 |
markwash | I think the client would be a great place for us to standardize things like how to select 1 out of the available image locations | 14:22 |
*** coolsvap has left #openstack-meeting-alt | 14:22 | |
*** julim has joined #openstack-meeting-alt | 14:22 | |
markwash | next up, looking at the review queue | 14:22 |
zhiyan | markwash: so for this do you thinks we can reuse gho's patch? and rething about interface | 14:22 |
zhiyan | ? | 14:22 |
*** julim has quit IRC | 14:23 | |
markwash | I'm not sure | 14:23 |
* flaper87 neither | 14:23 | |
flaper87 | I think that patch needs a major rework | 14:23 |
flaper87 | although I +2'ed back then | 14:23 |
flaper87 | :D | 14:23 |
markwash | after being reminded how much work it is to deprecate and drop API stuff in the clients | 14:23 |
markwash | I'm glad we didn't land that one | 14:23 |
*** coolsvap has joined #openstack-meeting-alt | 14:23 | |
markwash | at least without more evaluation | 14:24 |
* markwash was at least nervous | 14:24 | |
zhiyan | tbh, i'm not very clear the goal | 14:24 |
markwash | the goal of? | 14:24 |
zhiyan | glance client lib | 14:24 |
*** rongze_ has joined #openstack-meeting-alt | 14:24 | |
zhiyan | i mean the details of the landing path | 14:25 |
markwash | I think we could benefit from actually trying to write down the goal | 14:25 |
markwash | I think there is good stuff there, but its not always clear what we're trying to accomplish, I agree | 14:25 |
*** aignatov has joined #openstack-meeting-alt | 14:25 | |
markwash | in particular, with the way the api libs are laid out | 14:25 |
markwash | but I think that might be enough for now | 14:26 |
markwash | #topic review backlog | 14:27 |
*** openstack changes topic to "review backlog (Meeting topic: glance)" | 14:27 | |
markwash | we are down to 61 open reviews | 14:27 |
markwash | that's actually a pretty big improvement over last week | 14:27 |
markwash | I think our average response time has also dropped by nearly a week | 14:27 |
*** rongze has quit IRC | 14:27 | |
markwash | or at least 4 days, something like that | 14:28 |
markwash | great work everybody! | 14:28 |
flaper87 | w000t | 14:28 |
*** demorris has joined #openstack-meeting-alt | 14:28 | |
zhiyan | markwash: if gate work well, the number will better :) | 14:28 |
markwash | zhiyan: that is true | 14:28 |
flaper87 | o/ I think there are some important, historical, patches that need some attention, though. | 14:28 |
flaper87 | for example: https://review.openstack.org/#/c/34801/ | 14:28 |
flaper87 | that was opened on June 27th | 14:29 |
markwash | "Remove user and key from location in Swift" | 14:29 |
markwash | yeah that review is definitely on my mind | 14:29 |
markwash | there has been some recent discussion which I guess has been unfortunately kind of hidden | 14:29 |
markwash | which has kept me from pursuing that | 14:29 |
flaper87 | oh | 14:30 |
*** rongze has joined #openstack-meeting-alt | 14:30 | |
markwash | rosmaita: would you say the conversations we've been having with smclaren about solving the credentials problem are relevant to that patch? | 14:30 |
markwash | and might change the direction we want to go? | 14:30 |
*** yamahata_ has quit IRC | 14:30 | |
rosmaita | yes, i would hold off on that patch | 14:31 |
rosmaita | i can post Stuart's doc link if others are interested | 14:31 |
flaper87 | rosmaita: yup, please. | 14:31 |
*** yamahata_ has joined #openstack-meeting-alt | 14:31 | |
markwash | I might -1 it with a note just to pull it out of the stats | 14:31 |
rosmaita | don't mean to work hidden, but don't want to broadcast our prob | 14:31 |
markwash | right | 14:32 |
* rosmaita looking for link | 14:32 | |
*** zhiyan1 has joined #openstack-meeting-alt | 14:32 | |
*** csaba has joined #openstack-meeting-alt | 14:32 | |
iccha | hey hey sorry forgot it hifted to 9 am | 14:32 |
rosmaita | https://region-a.geo-1.objects.hpcloudsvc.com:443/v1/61624292678963/public_referenced/logical-swift-store.pdf | 14:32 |
markwash | I did come up with one bookmark link I wanted to share with other reviewers since its helped me out a lot this week | 14:32 |
markwash | https://review.openstack.org/#/q/status:open+project:%255Eopenstack.*glance.*+branch:master+label:CodeReview%253D2+-label:CodeReview%253D-1+-+label:CodeReview%253D-2+-label:Approved%253D1,n,z | 14:33 |
*** venkatesh has joined #openstack-meeting-alt | 14:33 | |
markwash | ^^ will show you all the reviews that really just need one more +2 and an approval | 14:33 |
*** zhiyan has quit IRC | 14:33 | |
zhiyan1 | markwash: yes, it's true, also for me. | 14:33 |
*** rongze_ has quit IRC | 14:33 | |
markwash | its sometimes an area with "easy" reviews, but I think its also useful because it reduces the time a patch can sit around and catch rebase conflicts, assuming you're happy with it | 14:34 |
flaper87 | markwash: rosmaita so, is that something 'swift' store specific? | 14:34 |
rosmaita | flaper87: yes and no | 14:34 |
markwash | flaper87: not entirely swift-specific. . there are other stores that have credentials | 14:34 |
flaper87 | yeah, sorry, I meant to ask. Is that fix something we can replicate on other stores? | 14:34 |
rosmaita | i think the problem is more general, but we (hp, rackspace) use swift and are most concerned about it | 14:35 |
markwash | but its conceivable that solutions might be store-specific | 14:35 |
rosmaita | too early to say | 14:35 |
flaper87 | would it be better to have that on a wiki page ? | 14:36 |
flaper87 | StoreCredentialsManagement | 14:36 |
flaper87 | or something like that | 14:36 |
ameade | here now >.< | 14:36 |
markwash | I think a general fix for this problem would probably be a great thing to get done ASAP, as a prerequisite to some of the client work with locations we were talking about | 14:36 |
markwash | so anyway, in summary, great work on reviews this past week and lets keep it up! once the queue is small we can relax a bit | 14:37 |
iccha | flaper87: the s3 store | 14:37 |
iccha | flaper87: i was looking for other stores with sridevi and thats the other one we noticed | 14:38 |
markwash | #topic meta | 14:38 |
*** openstack changes topic to "meta (Meeting topic: glance)" | 14:38 | |
flaper87 | iccha: cool, thanks for the heads up | 14:38 |
markwash | so I was hoping we'd have some time here to brainstorm about ways to fix our sort of disasterous blueprint organization | 14:38 |
markwash | maybe its not so bad, but I personally can't make heads or tails of our blueprints from the general list | 14:38 |
*** bill_az has joined #openstack-meeting-alt | 14:39 | |
markwash | but that discussion is probably long, and there are two other topics that have been added to the agenda | 14:39 |
markwash | anybody prefer to talk about blueprint organization now? or maybe some other time? | 14:39 |
flaper87 | I think maybe other time | 14:40 |
flaper87 | since the next 2 topics are still related to blueprints | 14:40 |
iccha | i woud like time to go through the list | 14:40 |
flaper87 | and upcoming designs | 14:40 |
flaper87 | and what iccha said | 14:40 |
flaper87 | :D | 14:40 |
*** vponomaryov has joined #openstack-meeting-alt | 14:40 | |
markwash | okay cool | 14:40 |
iccha | sorry about not being better prepared | 14:40 |
*** julim has joined #openstack-meeting-alt | 14:40 | |
markwash | I should probably also jsut take a look at what some other projects are doing with theirs | 14:41 |
markwash | now, in hopefully fastest-first order | 14:41 |
markwash | #topic Doc update | 14:41 |
*** openstack changes topic to "Doc update (Meeting topic: glance)" | 14:41 | |
markwash | rosmaita? | 14:42 |
rosmaita | yo | 14:42 |
iccha | most imp topic :) we really need it! | 14:42 |
markwash | rosmaita: sorry, just trying to give you the floor | 14:42 |
rosmaita | sorry, ok | 14:42 |
*** AlanClark has joined #openstack-meeting-alt | 14:42 | |
rosmaita | so the patch i've got up handles defining the 2.1 version of openstack-json-patch | 14:42 |
*** yportnova has joined #openstack-meeting-alt | 14:43 | |
rosmaita | but, the missing part is the change to the "restricted json pointers" | 14:43 |
rosmaita | since now you can do multilevel references for hte location field | 14:43 |
markwash | ah yes | 14:43 |
rosmaita | i am a little unclear how we want to go on that | 14:43 |
rosmaita | whether a general multilevel deal | 14:43 |
rosmaita | or only allow /location/whatever | 14:44 |
rosmaita | so i was wondering if someone more in the know would like to write it | 14:44 |
markwash | it will probably take a bit of looking at the code again, as well | 14:44 |
markwash | rosmaita: is there a drop-dead date for this assignment? | 14:44 |
rosmaita | not really | 14:45 |
*** shusya has joined #openstack-meeting-alt | 14:45 | |
zhiyan1 | rosmaita: after first glance, do you have plan to involve location part in your doc change? seems there's not | 14:45 |
*** kraman has joined #openstack-meeting-alt | 14:45 | |
rosmaita | i can just split the bug and leave the multilevel pointers hanging, and get the new json patch stuff in | 14:45 |
markwash | rosmaita: I'd like to help, I'm just afraid I'll forget or get distracted | 14:45 |
markwash | like if there's something shiny or whatever | 14:45 |
rosmaita | zhiyan1: probably put an update in the GET images/{image_id} call | 14:45 |
rosmaita | and another example for PATCH /images/{image_id} | 14:46 |
rosmaita | well, if no one thinks it's pressing, it may take me a while to get around to it | 14:46 |
*** ashaikh has joined #openstack-meeting-alt | 14:46 | |
*** sergmelikyan has quit IRC | 14:46 | |
rosmaita | like after i get the import/export tasks written up | 14:46 |
markwash | rosmaita: how about split it and assign it to me | 14:47 |
markwash | and then if you remember to, bug me about it :-) | 14:47 |
rosmaita | markwash: +1 | 14:47 |
*** bill_az has quit IRC | 14:47 | |
markwash | moving on. . . | 14:47 |
*** bill_az has joined #openstack-meeting-alt | 14:47 | |
markwash | #topic Glance Image Handlers (zhiyan) | 14:47 |
*** openstack changes topic to "Glance Image Handlers (zhiyan) (Meeting topic: glance)" | 14:47 | |
flaper87 | that was me | 14:47 |
flaper87 | :D | 14:47 |
markwash | oh | 14:48 |
markwash | haha sorry! | 14:48 |
flaper87 | no worries | 14:48 |
flaper87 | :P | 14:48 |
markwash | #topic Glance Image Handlers (flaper87 ) | 14:48 |
zhiyan1 | rosmaita: i prefer add a location PATCH example for end user | 14:48 |
*** openstack changes topic to "Glance Image Handlers (flaper87 ) (Meeting topic: glance)" | 14:48 | |
flaper87 | so, we had this conversation during the summit about being able to group images and supporting image templates | 14:48 |
rosmaita | zhiyan1: +1, will note in bug | 14:48 |
zhiyan1 | also thinking are we talking the same point? flaper87 | 14:48 |
flaper87 | I wanted to get other folks feedback on that topic and perhaps start working on a blueprint for that | 14:48 |
zhiyan1 | rosmaita: thanks. | 14:48 |
flaper87 | The idea is to have a separate resource that knows about iamge tempaltes | 14:49 |
flaper87 | as images know about images' formats | 14:49 |
zhiyan1 | flaper87: actually i did some work around that, flaper87 https://review.openstack.org/#/c/33409/ | 14:49 |
*** kraman has quit IRC | 14:49 | |
markwash | zhiyan1: I think actually maybe that is different | 14:49 |
markwash | but we're just using the same word "Handler" | 14:50 |
flaper87 | indeed | 14:50 |
*** yamahata_ has quit IRC | 14:50 | |
zhiyan1 | oh? looking | 14:50 |
flaper87 | so, this images' tempaltes will also make what zhiyan1 did easier to implement | 14:50 |
iccha | i think some folks brought this up at the portland summit as well | 14:50 |
markwash | so, an image template would be something like, this image for /dev/sda, this image for /dev/sdb? or something else? | 14:50 |
iccha | is there a specfic format? what would template look like? | 14:51 |
flaper87 | Those templates are very hipervisor specific | 14:51 |
*** yamahata_ has joined #openstack-meeting-alt | 14:52 | |
markwash | oh, like vmware templates as images? | 14:52 |
flaper87 | markwash: yup | 14:52 |
iccha | i think there exists a bp for it? lemme dig | 14:52 |
flaper87 | oh, is there? | 14:53 |
flaper87 | mmmh | 14:53 |
markwash | you also mentioned grouping images | 14:53 |
flaper87 | so, I was thinking about not just creating a resource that people can upload templates too | 14:53 |
iccha | flaper87: https://blueprints.launchpad.net/glance/+spec/hypervisor-templates-as-glance-images | 14:53 |
flaper87 | but make it smart enough to link existing glance images to that template | 14:53 |
iccha | https://blueprints.launchpad.net/glance/+spec/rhev-m-ovirt-templates-as-glance-images | 14:54 |
flaper87 | so that when users download that template, it already holds the information of the images that belong to it | 14:54 |
flaper87 | etc | 14:54 |
iccha | flaper87: so maybe somehing which over arcs/ generalizes all these bps? | 14:54 |
zhiyan1 | flaper87: just like ova? | 14:54 |
flaper87 | iccha: awesome, thanks a lot! | 14:54 |
flaper87 | so, as for now, Glance just knows about images | 14:55 |
markwash | flaper87: ah okay. . so this proposal is like representing *some* of the complexity of ovf in glance | 14:55 |
zhiyan1 | sounds like ova to me still | 14:55 |
flaper87 | markwash: yes, but keeping it hypervisor / tempalte agnostic | 14:55 |
markwash | yeah | 14:55 |
flaper87 | zhiyan1: yeah, kindof | 14:56 |
markwash | which man, I wish ova/ovf were hypervisor agnostic, but it seems probably not | 14:56 |
*** jcorbin has joined #openstack-meeting-alt | 14:56 | |
flaper87 | markwash: indeed | 14:56 |
markwash | I think we're clearly building some mental momentum around this kind of idea | 14:56 |
flaper87 | and I don't think we want to pull the hypervisor knowledge into glance | 14:56 |
markwash | I think for it to get real traction I wanna figure out how we can make sure we have nova buy-in | 14:57 |
flaper87 | yeah, I haven't worked on a *real* proposal yet because I wanted to get folks thoughts about this | 14:57 |
*** rraja has joined #openstack-meeting-alt | 14:57 | |
markwash | I mean, for the "disks arrangement" part of ova, I'm pretty sure Nova will be mostly happy | 14:57 |
flaper87 | markwash: it'll require some work in the nova side | 14:57 |
*** Barker has joined #openstack-meeting-alt | 14:57 | |
*** venkatesh has quit IRC | 14:58 | |
markwash | even an initial proposal could be really useful for fleshing things out | 14:58 |
zhiyan1 | flaper87: under my plan, we can just allow user to put ova into glance as a common image file, and do that magic thing on nova/consumer side, under my image handler approach | 14:58 |
zhiyan1 | flaper87: so i'm interested in what you want to do on glance side | 14:58 |
markwash | zhiyan1: I think we might have to do that in the short term, but libvirt is never gonna support ova | 14:58 |
*** markmcclain has quit IRC | 14:58 | |
flaper87 | and I don't like 'tempaltes' being treated as images | 14:59 |
*** achirko has joined #openstack-meeting-alt | 14:59 | |
zhiyan1 | markwash: yes, but vmware folks can implement a particular ova handler for esxi/vc hypervisor | 14:59 |
*** venkatesh has joined #openstack-meeting-alt | 14:59 | |
flaper87 | I think is wrong and we can do better by having a real resource for it | 14:59 |
markwash | so it would be great if we could sort of make a simpler, more generic, implicitly remote concept of ova and represent it in glance | 14:59 |
markwash | yeah, ova's are not images honestly | 14:59 |
zhiyan1 | markwash: that's no limitation, it's a particular handler implementation | 14:59 |
markwash | not in the true sense of an image | 14:59 |
*** caitlin56 has joined #openstack-meeting-alt | 14:59 | |
*** gokrokve has joined #openstack-meeting-alt | 15:00 | |
*** aostapenko has joined #openstack-meeting-alt | 15:00 | |
markwash | zhiyan1: the problem is that "particular handler implementations" is a fairly divisive approach to doing stuff, and means that different hypervisors feel very differently and can't interoperate | 15:00 |
ameade | before the meeting is over | 15:00 |
ameade | WRT the new quotas stuff, do we care about backward compat or would sane defaults be better so deployers don't have to worry about it? | 15:00 |
ameade | https://review.openstack.org/#/c/56981/ | 15:00 |
markwash | ooh, great question! | 15:00 |
*** glenng has joined #openstack-meeting-alt | 15:00 | |
*** bswartz has joined #openstack-meeting-alt | 15:01 | |
*** akerr1 has joined #openstack-meeting-alt | 15:01 | |
*** mscohen02 has joined #openstack-meeting-alt | 15:01 | |
markwash | I think if the default is really bit its probably fine | 15:01 |
markwash | looks like we gotta run! | 15:01 |
flaper87 | so, that's it from me. I see some interest and I'll write something about this topic | 15:01 |
markwash | s/bit/big/ | 15:01 |
markwash | #endmeeting | 15:01 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:01 | |
openstack | Meeting ended Thu Nov 21 15:01:35 2013 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:01 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-11-21-14.02.html | 15:01 |
markwash | thanks everybody | 15:01 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-11-21-14.02.txt | 15:01 |
openstack | Log: http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-11-21-14.02.log.html | 15:01 |
ameade | see ya everyone | 15:01 |
markwash | thanks for patience lurkers! | 15:01 |
iccha | cya | 15:01 |
*** Dinesh_ has joined #openstack-meeting-alt | 15:01 | |
bswartz | #startmeeting manila | 15:01 |
openstack | Meeting started Thu Nov 21 15:01:54 2013 UTC and is due to finish in 60 minutes. The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
*** openstack changes topic to " (Meeting topic: manila)" | 15:01 | |
openstack | The meeting name has been set to 'manila' | 15:01 |
*** zhiyan1 has left #openstack-meeting-alt | 15:02 | |
bswartz | hello guys | 15:02 |
*** ashwini has left #openstack-meeting-alt | 15:02 | |
bswartz | (and gals) | 15:02 |
Dinesh_ | Hi Bswartz I am Dinesh here | 15:02 |
jcorbin | Hello | 15:02 |
achirko | Hi | 15:02 |
bill_az | hi everyone | 15:02 |
*** navneet has joined #openstack-meeting-alt | 15:02 | |
vponomaryov | hi | 15:02 |
akerr1 | hello | 15:02 |
yportnova | hi | 15:02 |
*** gregsfortytwo1 has joined #openstack-meeting-alt | 15:02 | |
bswartz | Dinesh_: hello! | 15:02 |
navneet | hi | 15:02 |
bswartz | #link https://wiki.openstack.org/wiki/ManilaMeetings | 15:02 |
caitlin56 | hi | 15:02 |
bswartz | #topic Incubation | 15:03 |
*** openstack changes topic to "Incubation (Meeting topic: manila)" | 15:03 | |
aostapenko | Hello | 15:03 |
*** venkatesh has quit IRC | 15:03 | |
csaba | hi | 15:03 |
bswartz | okay so the TC held a meeting on tuesday to decide on our incubation status | 15:03 |
rraja | Hi | 15:03 |
bswartz | they decided that we are NOT ready for incubation as of yet | 15:03 |
bswartz | the main concern was the maturity of the project | 15:04 |
*** gokrokve has quit IRC | 15:04 | |
bswartz | while it's not clearly stated anywhere, they claim that they expect projects to have a stable API and be used in production at least somewhere | 15:04 |
bswartz | basically the requirement, as they see it, is that the project has to be "done" and usable in some form | 15:05 |
caitlin56 | No eggs before we see some chickens. or perhaps vise versa. | 15:05 |
bswartz | I agree with them that we don't meet that definition | 15:05 |
gregsfortytwo1 | did they say "used in production"? I thought it was "ready to be used in production" | 15:05 |
*** amytron has joined #openstack-meeting-alt | 15:05 | |
*** bugsduggan has joined #openstack-meeting-alt | 15:05 | |
bswartz | whether that's the right defintion for incubation, or whether the defition has changed over time is something we could argue about | 15:05 |
bswartz | but I'm not interested in spending time on that | 15:05 |
caitlin56 | gregfortytwo: hard to show that something is ready for production without using it that way. | 15:06 |
*** vbellur has joined #openstack-meeting-alt | 15:06 | |
bswartz | gregsfortytwo1: yeah what caitlin56 said | 15:06 |
gregsfortytwo1 | heh, fair enough | 15:06 |
caitlin56 | might be a lab deployment,. | 15:06 |
bswartz | I think it has to be shown to be used in production at least 1 place | 15:06 |
bswartz | that's a pretty low bar, but not that we don't clear currently | 15:06 |
*** japplewhite has joined #openstack-meeting-alt | 15:06 | |
bill_az | used in production w/ multi-tenancy? | 15:07 |
bswartz | the bigger issue is that we're stilling churning on the method of supporting multi tenancy | 15:07 |
bswartz | I feel that we now have a clear design and we know how we want to do it | 15:07 |
*** rcallawa has joined #openstack-meeting-alt | 15:07 | |
bswartz | but until the code is complete and tested, we can't claim that we've solved those problems | 15:07 |
caitlin56 | multi-tenancy is key, you can set of NAS for a single tenant just using networking. | 15:08 |
bswartz | so the path ahead of us is clear: we need to finish the multitenancy support, get it tested, and get some people using it, then we can apply for incubation again | 15:08 |
*** bvandehey has joined #openstack-meeting-alt | 15:08 | |
vbellur | bswartz: we had both neutron mediated and hypervisor mediated multi-tenancy model proposals | 15:08 |
vbellur | do we need to get at least one of that working before applying for incubation? | 15:08 |
bswartz | vbellur: yes, either or both of those is probably enough | 15:08 |
vbellur | bswartz: ok | 15:08 |
bswartz | now it's not all bad news from the TC | 15:09 |
bswartz | they were very impressed with what we've done so far, and they feel we're on the right track | 15:09 |
bswartz | they WANT to see manila succeed as a project | 15:09 |
caitlin56 | Did you have a sense that this is *the* blocking issue? That is we can expect approval after this is solved? | 15:09 |
vbellur | bswartz: good to know! | 15:09 |
*** ruhe has quit IRC | 15:09 | |
bswartz | but they feel that the stamp of "incubation" should be reserved for stuff that's fully usable right now | 15:09 |
bswartz | and we're simply not there | 15:10 |
vbellur | right | 15:10 |
bswartz | of course we could make some digs about the usability of the neutron project -- but I'll refrain from that | 15:10 |
caitlin56 | Kind of makes it hard to have a definite track for developing an API. | 15:10 |
bill_az | bswartz: is neutron mediated mulit-tenancy the higher priority / first target? | 15:11 |
*** rushiagr has joined #openstack-meeting-alt | 15:11 | |
bswartz | bill_az: in my opinion, yes | 15:11 |
rushiagr | hi all! late :( | 15:11 |
vbellur | maybe all of us can collaborate to get it out first | 15:11 |
caitlin56 | I think we can work on both APIs, but clearly neutron-mediated should be implemented first. | 15:11 |
bswartz | if a bunch of people show up who are more interested in the hypervisor-mediated method I'll support their work | 15:11 |
bill_az | bswartz: I agree - we should put focus there | 15:11 |
bswartz | but I think we won't get around to it until later with current resources | 15:12 |
bswartz | okay so there are 2 important tangible effects of this decision | 15:12 |
bswartz | the main reason we wanted to be incubated is that we wanted to move forward with devstack and tempest integrations | 15:12 |
bswartz | beyond that, being incubated has little practical effect aside from the PR and the badge of honor | 15:13 |
*** bugsduggan has left #openstack-meeting-alt | 15:13 | |
vbellur | bswartz: agree | 15:14 |
bswartz | so I discovered that devstack had modularized their architecture enough so that we can integrate with it without even being incubated | 15:14 |
caitlin56 | bswartz: the incubation status is defintiely useful in getting resources committed. | 15:14 |
bswartz | s/had/has/ | 15:14 |
vbellur | caitlin56: that's right too, we will get more attention from decision makers and the larger community | 15:15 |
bswartz | #link http://paste.openstack.org/show/53618/ | 15:16 |
*** ruhe has joined #openstack-meeting-alt | 15:16 | |
bswartz | there's a fragment of the TC meeting that I captured on the topic of devstack integration | 15:16 |
bswartz | btw the whole TC meeting is here if you're interested: | 15:16 |
bswartz | #link http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-11-19-20.03.log.html | 15:16 |
bswartz | so we should be able to proceed with devstack integration and get out gate jobs working | 15:17 |
bswartz | in fact -- the TC indicated that that will be a prerequisite for incubation status going forward | 15:17 |
bswartz | they claim it doesn't take more than 1 hour of effort | 15:17 |
bswartz | integration with tempest however will still be very difficult | 15:18 |
vbellur | bswartz: ok, do we have anybody commited to the devstack effort? | 15:18 |
bswartz | they cannot accept our tests upstream until we're incubated, which means that we need to continue to maintain a side branch of tempest for our manila tests | 15:18 |
*** jtomasek has quit IRC | 15:19 | |
bswartz | and that means we'll be responsible for periodically pulling/rebasing that branch and dealing with any breakage that occurs from the unstable tempest libraries | 15:19 |
caitlin56 | bswartz: exactly how would each vendor set up their test infrastructure as you see it? | 15:19 |
*** nati_ueno has joined #openstack-meeting-alt | 15:20 | |
bswartz | vbellur: yeah I haven't talked to yportnova or vponomaryov about that yet, but we should get that done in the coming week | 15:20 |
bswartz | caitlin56: so this is what I expect... | 15:20 |
vbellur | bswartz: ok | 15:20 |
bswartz | after we're integrated with devstack, you should be able to install manila directly with devstack | 15:20 |
yportnova | bswartz: vponomaryov is working on integration with devstack | 15:20 |
bswartz | you'll need to configure your tempest to pull from a different git repo with a different branch | 15:21 |
*** yamahata_ has quit IRC | 15:21 | |
bswartz | our tempest branch will lag slightly behind tempest/master at all times | 15:21 |
*** banix has joined #openstack-meeting-alt | 15:22 | |
bswartz | but aside from the time lag, all of the same tests should be there, plus our manila ones | 15:22 |
vbellur | right | 15:22 |
caitlin56 | So we would check out this alternate-tempest branch which would have the default (LVM) version, and then add our own driver. Is that correct? | 15:22 |
bswartz | caitlin56: well the drivers will be in the manila tree not tempest | 15:23 |
vponomaryov | caitlin56, tempest works with service api, so it does not know anything about beckend | 15:23 |
bswartz | you shoudl be able to do manila development, including writing drivers and unit tests without touching tempest at all | 15:24 |
bswartz | tempest tests are about testing integration with the rest of openstack, and testing under a somewhat more realistic environment | 15:24 |
vponomaryov | until service api not changed tempest will still work | 15:24 |
*** markmcclain has joined #openstack-meeting-alt | 15:25 | |
bswartz | now we will have our gate tests setup to run tempest, so if you try to submit a driver to manila upstream, it will need to pass those tests | 15:25 |
vbellur | bswartz: ok | 15:25 |
bswartz | okay I feel we've gotten a bit offtopic | 15:26 |
bswartz | this is all good stuff though | 15:26 |
*** ajo has joined #openstack-meeting-alt | 15:26 | |
bswartz | any more questions about incubation before I move on? | 15:26 |
*** alazarev has joined #openstack-meeting-alt | 15:26 | |
vbellur | nothing from me | 15:26 |
bswartz | #topic dev status | 15:26 |
*** openstack changes topic to "dev status (Meeting topic: manila)" | 15:26 | |
bswartz | okay any questions about the stuff I mentioned about w.r.t. devstack, tempest, gate, etc? | 15:27 |
bswartz | s/about/above/ | 15:27 |
vbellur | bswartz: do we plan to add tests for flat network driver in tempest? | 15:27 |
bswartz | vbellur: yes | 15:28 |
vbellur | bswartz: ok | 15:28 |
bswartz | vbellur: and in fact until we have a generic driver that supports multitenancy, that's all we can test | 15:28 |
vbellur | bswartz: right | 15:29 |
bswartz | so that suggests that the generic-driver-with-multitenancy will also be a requirement for incubation because it's not possible to do proper gate testing without that | 15:29 |
vbellur | yeah | 15:29 |
bswartz | but I'm not certain about that, we'll need to evaluate when we know more | 15:29 |
vponomaryov | any multitenancy testing at all | 15:30 |
*** ashaikh has quit IRC | 15:30 | |
vponomaryov | not only gate | 15:30 |
bswartz | okay so icehouse-1 is coming in 2 weeks | 15:30 |
vbellur | bswartz: if we decide on the branch and communicate the status, I think we should be able to help in contributing tests to tempest | 15:31 |
bswartz | vponomaryov: actually it will be possible to do multitenancy testing with the NetApp driver if you have netapp hardware or the netapp simulator, once we complete that work | 15:31 |
*** bvandehey has quit IRC | 15:32 | |
vponomaryov | bswartz: yes, I was talking about common testing for everyone with devstack | 15:32 |
bswartz | yes | 15:32 |
bswartz | My feeling is that a NetApp (hardware-based) driver will serve as a better model for other hardware vendors than a pure-ly software-based generic driver however | 15:32 |
*** jtomasek has joined #openstack-meeting-alt | 15:33 | |
bswartz | which is why I'm pushing for that to be done first | 15:33 |
caitlin56 | bswartz: that's true. | 15:33 |
bswartz | my top goal is to make it possible for hardware vendors to start work on their backends | 15:33 |
bswartz | the main value of the generic driver will be for gate tests and for people who just want to tinker with manila | 15:34 |
bswartz | I don't expect the generic driver to provide compelling performance or even features for someone wanting to implement NAS in production | 15:34 |
bswartz | if it does, then that's great, but it seems unlikely given the underlying technologies | 15:35 |
*** ifarkas has left #openstack-meeting-alt | 15:35 | |
bswartz | laying the generic driver on top of cinder and nova puts it at a disadvantage compared to dedicated hardware solutions | 15:35 |
bswartz | layering* | 15:35 |
*** pballand has joined #openstack-meeting-alt | 15:36 | |
caitlin56 | bswartz: the ground rules for the generic driver doom it to be nothing but a certification tool. But that's all it needs to be. | 15:36 |
bswartz | caitlin56: I wouldn't go that far | 15:36 |
bswartz | the LVM driver for cinder has turned out to be far more than that, despite the intentions of the cinder team | 15:37 |
*** gokrokve has joined #openstack-meeting-alt | 15:37 | |
*** rongze_ has joined #openstack-meeting-alt | 15:37 | |
*** devkulkarni has joined #openstack-meeting-alt | 15:37 | |
vbellur | the LVM driver seems to be the one with most adoption in cinder as per the last user survey | 15:37 |
*** rongze has quit IRC | 15:37 | |
bswartz | Let me clearly state that I don't want to handicap the manila generic driver so it's not competitive | 15:38 |
bswartz | The generic driver should be as good as it can be given the limitted investment we're able to make in it given everything else we're trying to accomplish | 15:38 |
vbellur | bswartz: agree | 15:39 |
caitlin56 | there's no need to sabotage it. if you work with any hardware requirements it is handicapped. | 15:39 |
bswartz | okay so back to dev status | 15:39 |
bswartz | in the last week we've made a bit of progress on the multitenant stuff | 15:39 |
bswartz | I learned something I did not know, which might be of interest here | 15:40 |
bswartz | Evidently many users of OpenStack don't rely on neutron to configure the VLAN trunks for their switches -- it's common to statically configure the switches to pass a bunch of VLANs before setting up openstack | 15:40 |
bswartz | then they simply allow neutron to allocate the vlans they're already configured on the switches | 15:41 |
bswartz | In that mode of operation, the interaction between manila and neutron is actually quite simple | 15:41 |
vbellur | bswartz: interesting | 15:42 |
caitlin56 | kind of like a dhcp server where every address was assigned by hand. | 15:42 |
bswartz | yportnova: did the change for neutron integration go in already | 15:42 |
bswartz | ? | 15:42 |
*** __amotoki__ is now known as amotoki | 15:42 | |
bswartz | I think it did | 15:42 |
bswartz | caitlin56: hah! | 15:42 |
*** sacharya has joined #openstack-meeting-alt | 15:42 | |
yportnova | bswartz: it is not in upstream yet | 15:43 |
bswartz | yportnova: can you link the change? | 15:43 |
bswartz | https://review.openstack.org/#/c/55555/ | 15:43 |
bswartz | oh I found it | 15:43 |
jcorbin | bswartz: Why does Manila care how the VLANs are setup? Is it not that they are setup that matters? | 15:44 |
jcorbin | yportnova: I did a first pass code review and was going to add comments. Is it too late? | 15:44 |
bswartz | looks like jenkins is in a bad mood lately | 15:44 |
aostapenko | bswartz: it will be ready today or tomorrow | 15:44 |
*** colinmcnamara has joined #openstack-meeting-alt | 15:44 | |
caitlin56 | jcorbin: I agree, how VLANs are set up is something that neutron does. If neutron supports static configuratin then we don't care. | 15:45 |
bswartz | jcorbin: you're right, assuming that they're setup in advance | 15:45 |
yportnova | jcorbin: it is not late, feel free to add comments | 15:45 |
bswartz | jcorbin: however my understand is that neutron is moving in the direction of configuring the vlan trunks on your switchs for you | 15:45 |
bswartz | understanding* | 15:45 |
jcorbin | bswartz: The vendors can trigger that via their ML2 driver. | 15:46 |
*** coolsvap is now known as coolsvap_away | 15:46 | |
bswartz | jcorbin: in order for neutron to be able to add the right vlans to the right switch ports dynamically, we will need a way to discover what the right ports are, and that will require manila to obtain MAC addresses from the storage controllers | 15:46 |
caitlin56 | the point is that the user is able to launch compute nodes for a tenant and access virtual servers on tenant networks. | 15:46 |
bswartz | jcorbin: yes that's what we've discussed -- so the missing piece right now is a communication path to get the MAC addresses out of the manila backends to where they need to go | 15:47 |
bswartz | we'll get there soon | 15:47 |
*** boris-42 has quit IRC | 15:48 | |
bswartz | okay so for the coming week, we need to get past this jenkins nonsense, and get a working multitenant backend started | 15:48 |
*** markmcclain has quit IRC | 15:48 | |
jcorbin | bswartz: ok | 15:48 |
bswartz | we can do those 2 things in parallel | 15:48 |
Dinesh_ | Neutron is also moving in the direction of integrating opendaylight I guess | 15:49 |
bswartz | next week I hope to be talking about the details of the manila manager/manila backend interactions | 15:49 |
caitlin56 | bswartz: obviously you need to identify the storage serve that will add a VNIC on a tenant network. But why is it at a MAC address layer? | 15:49 |
bswartz | caitlin56: a MAC address is what the backend will return back to the manager -- it should be not be the backends job to know what switch port it's cabled to | 15:50 |
bswartz | the manila manager (or neutron) can figure that out as long as it has a MAC address from the backend | 15:50 |
bswartz | okay and since we're winding down on time... | 15:51 |
bswartz | #topic open discussion | 15:51 |
*** openstack changes topic to "open discussion (Meeting topic: manila)" | 15:51 | |
*** coolsvap_away is now known as coolsvap | 15:51 | |
bswartz | Dinesh_: what's opendaylight? | 15:51 |
jcorbin | Are we meeting next week? | 15:51 |
bswartz | OH! | 15:51 |
vbellur | bswartz: http://www.opendaylight.org/ | 15:51 |
bswartz | jcorbin: thanks for reminding me that it's a holiday in the USA next thursday | 15:51 |
Dinesh_ | adopting SDN | 15:51 |
Dinesh_ | it will be a plugin to the neutron | 15:52 |
bswartz | next week the meeting will be CANCELLED | 15:52 |
bswartz | hmmm | 15:52 |
bswartz | we could try to meet up some time on wednesday | 15:52 |
Dinesh_ | can someone share some info on the multi tenant backend topics you discussed I am bit lost in that.... | 15:52 |
bswartz | perhaps informally in the #manila channel | 15:52 |
vbellur | bswartz: yeah, having a meeting would be useful | 15:53 |
bswartz | Dinesh_: I can send you some links | 15:53 |
Dinesh_ | thank you bswartz :) | 15:53 |
*** ruhe has quit IRC | 15:53 | |
vbellur | bswartz: same time on wednesday in #manila? | 15:53 |
Dinesh_ | one question....has anyone thought about QoS over NFS for a effective multi-tenant solution? | 15:53 |
caitlin56 | I'll be on vacation next week. | 15:53 |
bswartz | okay here's what I propose: let's get together wednesday Nov 27 at 1500 UTC | 15:54 |
*** markmcclain has joined #openstack-meeting-alt | 15:54 | |
bswartz | in the #openstack-manila channel | 15:54 |
*** NikitaKonovalov has quit IRC | 15:54 | |
vbellur | bswartz: sounds good | 15:54 |
caitlin56 | Dinesh: you mean Qos=S expressed in NAS terms, rather than in Neutron terms? | 15:54 |
bswartz | qos? | 15:54 |
jcorbin | bswartz: meeting time sounds good | 15:54 |
bswartz | what does qos have to do w/ NAS? | 15:54 |
*** eharney has joined #openstack-meeting-alt | 15:55 | |
vbellur | i think S expressed in NAS terms | 15:55 |
*** SergeyLukjanov has quit IRC | 15:55 | |
Dinesh_ | I meant in performance issue....for better throughput and high IOPS something like that | 15:55 |
vbellur | bswartz: iops, throughput guarantees per tenant? | 15:55 |
bswartz | Dinesh_: that's a good topic for later | 15:55 |
bswartz | we don't even have multitenancy working at all right now -- baby steps | 15:56 |
*** sergmelikyan has joined #openstack-meeting-alt | 15:56 | |
*** s3wong has joined #openstack-meeting-alt | 15:56 | |
vbellur | yeah, one at a time | 15:56 |
Dinesh_ | bswartz: yeah I agree...I thought about this solution and working on it | 15:56 |
*** navneet has quit IRC | 15:57 | |
Dinesh_ | just shared my views :) | 15:57 |
bswartz | okay please keep us updated, and feel welcome to contribute to the project with the lower level issues we're working on right now | 15:57 |
*** kgriffs_afk is now known as kgriffs | 15:57 | |
bswartz | okay anything else? | 15:57 |
caitlin56 | Dinesh: any NAS QoS gets complex if you have any parallelism (such as pNFS) involved. | 15:57 |
Dinesh_ | bswartz : yes sure....please share me the links it will help me better to involve more | 15:57 |
vbellur | bswartz: nothing else from me | 15:58 |
bswartz | okay thanks everyone | 15:58 |
*** tanisdl has joined #openstack-meeting-alt | 15:58 | |
vbellur | thanks all | 15:58 |
bswartz | #endmeeting | 15:58 |
Dinesh_ | caitlin56: I am not sure need to check | 15:58 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:58 | |
openstack | Meeting ended Thu Nov 21 15:58:40 2013 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:58 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-11-21-15.01.html | 15:58 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-11-21-15.01.txt | 15:58 |
openstack | Log: http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-11-21-15.01.log.html | 15:58 |
*** rraja has quit IRC | 15:58 | |
*** jcorbin has quit IRC | 15:58 | |
*** achirko has left #openstack-meeting-alt | 15:58 | |
*** vbellur has left #openstack-meeting-alt | 15:58 | |
*** glenng has left #openstack-meeting-alt | 15:59 | |
*** bswartz has left #openstack-meeting-alt | 15:59 | |
*** akerr1 has left #openstack-meeting-alt | 15:59 | |
*** aostapenko has left #openstack-meeting-alt | 15:59 | |
*** gregsfortytwo1 has left #openstack-meeting-alt | 15:59 | |
mestery | Anyone here for the Neutron group policy subteam meeting? | 16:00 |
banix | Hi, Mohammad here | 16:00 |
mestery | banix: Hey! | 16:00 |
*** aignatov has quit IRC | 16:00 | |
*** s3wong has quit IRC | 16:00 | |
*** KDurazzo has joined #openstack-meeting-alt | 16:01 | |
mestery | #startmeeting networking_policy | 16:01 |
openstack | Meeting started Thu Nov 21 16:01:09 2013 UTC and is due to finish in 60 minutes. The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:01 |
*** openstack changes topic to " (Meeting topic: networking_policy)" | 16:01 | |
openstack | The meeting name has been set to 'networking_policy' | 16:01 |
mestery | #link https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy Agenda | 16:01 |
mestery | Anyone besides banix and myself? | 16:01 |
*** alagalah has joined #openstack-meeting-alt | 16:02 | |
mestery | alagalah: Welcome! | 16:02 |
*** michsmit has joined #openstack-meeting-alt | 16:02 | |
alagalah | mestery: Thank you sir | 16:02 |
mestery | michsmit: yo | 16:02 |
mestery | For those who missed it earlier: Agenda is here (https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy) | 16:03 |
*** nicole has joined #openstack-meeting-alt | 16:03 | |
*** uri__ has joined #openstack-meeting-alt | 16:03 | |
*** caitlin56 has quit IRC | 16:03 | |
*** nicole has left #openstack-meeting-alt | 16:03 | |
*** thinrichs2 has joined #openstack-meeting-alt | 16:04 | |
mestery | #link https://etherpad.openstack.org/p/NeutronIcehouseProjectPlan Neutron Icehouse Project Plan | 16:04 |
mestery | I wanted to mention the Project Plan for Neutron in Icehouse first. | 16:04 |
mestery | Per the Neutron IRC meeting on Monday, the policy work we're doing here is unlikely to make it into Icehouse. | 16:04 |
mestery | But we should continue exploring it and prototyping it to make sure it gets into "J" release. | 16:04 |
mestery | Any questions on that? | 16:05 |
banix | Yeah let's push the ball forward | 16:05 |
*** prasad_ has joined #openstack-meeting-alt | 16:05 | |
mestery | banix: Agreed. And we should certainly shoot to get some WIP type patches out for review at some point as well. | 16:05 |
mestery | #link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule Icehouse Release Schedule (for reference) | 16:06 |
mestery | Not the Icehouse dates there, for reference. | 16:06 |
mestery | #topic Group Based Policy Discussion | 16:06 |
*** openstack changes topic to "Group Based Policy Discussion (Meeting topic: networking_policy)" | 16:06 | |
mestery | So, what I'd like to start doing here is to make sure we all are in agreement around the high level constructs and terms. | 16:07 |
mestery | That will make it easier to move forward in discussions and implementation. | 16:07 |
*** rushiagr has quit IRC | 16:08 | |
mestery | #link https://docs.google.com/document/d/1ZbOFxAoibZbJmDWx1oOrOsDcov6Cuom5aaBIrupCD9E/edit?usp=sharing Group Policy Document | 16:08 |
*** s3wong has joined #openstack-meeting-alt | 16:08 | |
mestery | I encourage people to comment in the document as well as on the openstack-dev mailing list. | 16:08 |
mestery | Questions on that? | 16:08 |
*** rsblendido has quit IRC | 16:08 | |
*** rossella_s has quit IRC | 16:08 | |
thinrichs2 | I brought this up on the mailing list---I'd like to discuss whether there are plans to include a concrete policy language (or several). | 16:08 |
mestery | thinrichs2: There are currently no plans at the moment, partially because of how high level the proposal currently is. | 16:09 |
mestery | Perhaps it can evolve in this direction though. | 16:09 |
*** kgriffs is now known as kgriffs_afk | 16:10 | |
thinrichs2 | I ask mainly because I'm trying to figure out how another OS component would use this API. | 16:10 |
*** s3wong_ has joined #openstack-meeting-alt | 16:10 | |
thinrichs2 | For example, if I were writing Heat, if I don't know what policy language to use, I can't figure out which API calls to make. | 16:10 |
michsmit | I think getting the constructs into the current model would come first and then a policy language could potentially be layered on top later. | 16:11 |
thinrichs2 | I would know that I need to insert policy/group statements, but I wouldn't know which ones.--unless I knew which plugin we were using for Neutron. | 16:11 |
thinrichs2 | Or am I missing something? | 16:11 |
banix | thinrichs2: how is this done in Heat now for other resources? | 16:11 |
mestery | thinrichs2: I think the constructs would dictate what an API user could do, as michsmit is leading to. | 16:12 |
banix | Isn't the resource specified and the corresponding API called for it? | 16:12 |
thinrichs2 | Heat knows what routers/switches/etc are, and uses them appropriately. | 16:12 |
*** s3wong has quit IRC | 16:12 | |
*** songole_ has joined #openstack-meeting-alt | 16:12 | |
*** s3wong has joined #openstack-meeting-alt | 16:12 | |
thinrichs2 | Banix: But this is different in that the API basically allows us to pass arbitrary strings (policy statements), and we don't know what strings are even syntactically valid, let alone what they mean. | 16:13 |
*** japplewhite has quit IRC | 16:13 | |
*** japplewhite has joined #openstack-meeting-alt | 16:13 | |
thinrichs2 | The thought experiment I did was to assume I was trying to build a super-simple version of Heat where I only accepted app templates with a DB tier and a web tier. | 16:13 |
*** ErikB has joined #openstack-meeting-alt | 16:13 | |
*** colinmcnamara has quit IRC | 16:13 | |
thinrichs2 | So the template just said how many DB servers and how many Web servers we want. | 16:13 |
*** akuznetsov has quit IRC | 16:13 | |
*** jmontemayor has joined #openstack-meeting-alt | 16:14 | |
*** jmontemayor has quit IRC | 16:14 | |
thinrichs2 | I then need to write a function that takes as arguments number-of-db-servers and number-of-web-servers and outputs a sequence of neutron API policy calls that implements that app. | 16:14 |
michsmit | The policy should describe desired connectivity abstracted from topology i.e. group A can talk to group B using Web | 16:14 |
thinrichs2 | But I can't write that down *unless* I know the policy language. | 16:14 |
thinrichs2 | Does any of that make sense? | 16:15 |
banix | So to make it easier to begin with, let us assume someone will create the Heat template | 16:15 |
*** s3wong_ has quit IRC | 16:15 | |
michsmit | The "language" could be fairly simple at first. L4 protocol and ports | 16:16 |
michsmit | L4 port that is | 16:16 |
banix | Resources are defined based on what Neutron objects are | 16:16 |
*** shusya has quit IRC | 16:17 | |
*** rongze_ has quit IRC | 16:17 | |
*** eankutse has quit IRC | 16:17 | |
mestery | I think based on this discussion it's clear we should flesh out the objects and attributes we're talking about a bit more. | 16:18 |
michsmit | banix: Agree, I would expect the more topology specific constructs to not be described in the policy such as network but rendered by the extension. | 16:18 |
mestery | Any volunteers to do that in the Google doc? | 16:18 |
thinrichs2 | I agree we could invent a bunch of different languages to do this. Each plugin, for example, could have its own language. But therein lies the problem. We don't want Heat to have to know which plugin is being used in order to use the policy API. | 16:18 |
banix | mestery: I can get it started | 16:19 |
mestery | banix: Thanks! | 16:19 |
thinrichs2 | For the policy API to be useful, we should be able to write the following function today, and that function should work for every plugin. | 16:19 |
michsmit | mestery: I can help as well | 16:19 |
*** jmontemayor has joined #openstack-meeting-alt | 16:19 | |
mestery | #action banix and michsmit to flesh out the objects and attributes we want to expose in more detail in the design document | 16:20 |
thinrichs2 | void create_simple_app(int db-server-num, int web-server-num) { ... } | 16:20 |
thinrichs2 | I'm happy to help as well. But I'm sure I understand what constructs we're talking about. | 16:20 |
mestery | thinrichs2: I think the idea is to specify the desired connectivity, but let the plugins handle how that connectivity is achieved (michsmit correct me if I'm wrong here). | 16:20 |
banix | thinrich2: I think this where we want to get to but we are not there yet | 16:21 |
s3wong | thinrichs2: that abstraction seems to be more than what Neutron can handle, right? Nova has to be involved as well? | 16:21 |
mestery | thinrhcs2: Great! DM me your gmail and I can add you to the google doc. | 16:21 |
thinrichs2 | s3wong: Correct--but we *should* be able to write the Neutron API calls today. | 16:21 |
s3wong | mestery: I would like to be added to that Google Doc as well | 16:21 |
banix | What you are suggesting is perhaps done in an enhanced version of Heat engine or on something on top of it that produces appropriate Heat templates | 16:21 |
thinrichs2 | thinrichs@nicira.com | 16:21 |
mestery | s3wong: Sure, DM me your google ID so I can add you as well. | 16:22 |
s3wong | mestery: My email address is s3wong@midokura.com | 16:22 |
thinrichs2 | But I'm still a bit unsure what we're proposing to put into the google doc. | 16:22 |
thinrichs2 | Are we talking about a full language (grammar + semantics)? | 16:22 |
*** rongze has joined #openstack-meeting-alt | 16:23 | |
mestery | Not a full language, but the actual objects/resources we're talking about adding for the extension API, along with attributes. | 16:23 |
michsmit | I think the Google doc should focus on what needs to be described so that the extension plugin would have enough information to render the existing Neutron objects | 16:24 |
banix | thinrich2: no, we were talking about Neutron object model here. | 16:24 |
michsmit | but yet be independent of network topology | 16:24 |
*** s3wong has left #openstack-meeting-alt | 16:24 | |
*** s3wong has joined #openstack-meeting-alt | 16:24 | |
thinrichs2 | If we only talk about the objects, we still aren't giving enough information to actually use the API. | 16:24 |
*** s3wong has quit IRC | 16:25 | |
thinrichs2 | Suppose I want to add a policy statement. I don't know which strings are syntactically valid to pass into that API call. | 16:25 |
*** s3wong has joined #openstack-meeting-alt | 16:25 | |
banix | So if you look at the current doc, we are saying we will have these new objects, we want to specify them more precisely to begin with | 16:25 |
thinrichs2 | Anyway--hope my position is clear at this point. I think that before we start talking about implementing the proposal, we need to hammer out a concrete policy language (that could be extended, etc.) | 16:27 |
thinrichs2 | I'm happy to move onto other topics. | 16:27 |
mestery | Well, this is pretty much the only topic for today per the agenda. :) | 16:28 |
banix | I think we are looking at this from different angles which is perfectly fine; thinrichs2, could you say a bit more, may be later on the dev list …. | 16:28 |
*** kraman has joined #openstack-meeting-alt | 16:28 | |
s3wong | Policy implies rules - wouldn't defining better rules premitives for Neutron be a pre-requisite? | 16:28 |
thinrichs2 | I'm happy to write the example up and send to the dev list. | 16:29 |
thinrichs2 | s3wong: could you elaborate? | 16:29 |
*** kgriffs_afk is now known as kgriffs | 16:29 | |
banix | thinrichs2: thanks | 16:29 |
*** markmcclain has quit IRC | 16:29 | |
s3wong | Policy is a set of rules, rules would be {classifier/match -> set of actions} | 16:29 |
*** MarkAtwood has joined #openstack-meeting-alt | 16:30 | |
banix | s3wong: agree, that's what we need to define too. At least start with a set of possible rules, or types of rules | 16:30 |
s3wong | banix: absolutely | 16:31 |
*** ruhe has joined #openstack-meeting-alt | 16:31 | |
*** ruhe has quit IRC | 16:31 | |
thinrichs2 | banix: agreed. With the current proposal, it's impossible to write down 1 valid API call (and know it's valid for all plugins). | 16:31 |
mestery | banix s3wong: Are you volunteering to define the initial rules? | 16:32 |
alagalah | Excuse my naivety, but if the end game is to make this a part of core Neutron, with Step1 being a plugin, does it make sense to create any missing Neutron primitives in the plugin first since they'll be rolled in eventually anyway? | 16:32 |
mestery | alagalah: Not a plugin, an API extension at first, implemented in ML2 as the open source reference implementation. | 16:32 |
s3wong | mestery: certainly, I would love to | 16:32 |
mestery | s3wong: Cool, thanks! | 16:32 |
prasad_ | dont we have to define other APIs too such as connectivity group? What goes into the group? | 16:32 |
banix | mestery: yes sure | 16:33 |
alagalah | mestery: Sorry, I misread the paragraph in the doc on OpenSrouce Reference Implementation. | 16:33 |
mestery | alagalah: No worries. | 16:33 |
*** amotoki is now known as amotoki_zzz | 16:33 | |
*** csaba is now known as csaba|afk | 16:33 | |
michsmit | prasad_: yes, the group would contain the endpoints i.e. entities that source/sink traffic on the network | 16:34 |
banix | prasad_: yes, that is part of the extension. that's what we want to define more precisely. | 16:35 |
mestery | #action banix and s3wong to make first pass at defining initial rules. | 16:35 |
thinrichs2 | Could someone explain why we wouldn't want to define groups as part of the policy? Just curious. | 16:35 |
prasad_ | the question is how are end points defined? VMs, IP addresses? | 16:35 |
michsmit | Groups are a fundamental primitive that could be used in higher layer policy languages | 16:36 |
michsmit | prasad_: | 16:36 |
*** Barker has quit IRC | 16:36 | |
banix | prasad_: yes, may be ports, as a first step | 16:37 |
michsmit | prasad_: vnic, ip address as well for external subnets | 16:37 |
prasad_ | dont they have to be precise just like rule definition discussed above. Else it will again be pllugin dependent isnt it? | 16:37 |
*** s3wong has quit IRC | 16:37 | |
mestery | I think it's a safe assumption to assume that if we make any of this plugin dependent we've failed. | 16:38 |
thinrichs2 | I only ask b/c often we end up defining groups implicitly within the policy itself. | 16:38 |
thinrichs2 | mestery: agreed | 16:38 |
mestery | The entire goal of this is to abstract things at a higher level, by exposing plugin primitives this doesn't by us anything. | 16:38 |
*** s3wong has joined #openstack-meeting-alt | 16:38 | |
mestery | Look at the current state of Neutron extension APIs per-plugin to get an idea of why this is a bad idea. | 16:38 |
*** colinmcnamara has joined #openstack-meeting-alt | 16:38 | |
mestery | Cloud management vendors need to understand which plugin is running in Neutron before they can appropriately use Neutron, which is bad IMHO. | 16:39 |
mestery | So these new APIs need to abstract that away and simplify that state of affairs. | 16:39 |
uri__ | what happens whrn the Plugin can't support a given policy? | 16:39 |
KDurazzo | quit | 16:40 |
*** KDurazzo has quit IRC | 16:40 | |
*** alazarev has quit IRC | 16:40 | |
*** kgriffs is now known as kgriffs_afk | 16:40 | |
thinrichs2 | uri__: I would imagine we have a core policy language that *every* plugin must support, with extensions to the language that plugins can choose to support or not. | 16:40 |
thinrichs2 | Sort of like the API and its extensions. | 16:41 |
mestery | thinrichs2: I partially agree, although the extensions idea is a slippery slope. | 16:41 |
michsmit | The policy should express the intent of the connectivity independent of the low level networking details. This should allow the plugin some freedom in making it happen, but at some point if the intent cannot be realized, it would fail the call. | 16:41 |
uri__ | so the "bsic" set maybe a good starting point | 16:41 |
mestery | It all comes down to the API user an the choices they make. | 16:41 |
s3wong | michsmit: agree, if a policy is not supported by a particular plugin, logically it should return error | 16:42 |
thinrichs2 | mestery: I'm certainly happy to have a language w/o extensions. But extensions are something to keep in the back of our minds, if we find we need them. | 16:43 |
*** rcallawa has quit IRC | 16:43 | |
mestery | thinrichs2: Realistically, I agree. | 16:43 |
*** colinmcnamara has quit IRC | 16:44 | |
uri__ | and in the first version, we assume all policies implemented by ONE plugin? any way for few Plugin to implement each a share? Will ML2 for example divide it up among its mechanism drivers? | 16:44 |
*** colinmcn_ has joined #openstack-meeting-alt | 16:44 | |
mestery | uri__: These APIs will work similar to how the existing APIs work in ML2. | 16:45 |
banix | Well, I suppose if there are multiple segments in a network, the policy implementation may lead to different mechanism drivers. | 16:45 |
mestery | For example, if a single MechanismDriver fails a create call, ML2 will roll things back and clean up the ones which succeeded prior. | 16:46 |
*** flwang has joined #openstack-meeting-alt | 16:46 | |
uri__ | mestery: so i'm not sure how ML2 will guarantee to teh User all policy has been implemented. i hope in the opensource we see how this happens and how policies are handled by more than one Mech Driver | 16:47 |
*** jmontemayor has joined #openstack-meeting-alt | 16:47 | |
*** jmontemayor has quit IRC | 16:47 | |
mestery | uri__: It can guarantee success by the fact that each MechanismDriver returned success when it was called. | 16:47 |
s3wong | mestery: uri_: and I think that is necessary, otherwise if the policy is only applied partially, it would be a messy state | 16:48 |
*** japplewhite has quit IRC | 16:49 | |
mestery | Yes, agreed. | 16:49 |
mestery | OK, so we have about 10 minutes left, and I recored two action items so far. | 16:49 |
*** colinmcn_ has quit IRC | 16:49 | |
mestery | Is there anything else we should focus on this week? | 16:49 |
*** s3wong has quit IRC | 16:49 | |
mestery | With regards to action items for future meetings | 16:49 |
mestery | ? | 16:50 |
*** s3wong has joined #openstack-meeting-alt | 16:50 | |
banix | The next meeting will be in two weeks. Right? | 16:50 |
michsmit | do we have timelines for the actions ? | 16:50 |
prasad_ | are the api definition discussions going to take place on the mailing lists? | 16:51 |
s3wong | Thanksgiving next Thursday :-) | 16:51 |
mestery | banix: I was going to get to that, hold on. :) | 16:51 |
alagalah | mestery: I'm sure you and I will talk before then.... | 16:51 |
*** uri__ has quit IRC | 16:51 | |
mestery | #info No meeting next week (11-28-2013) due to Thanksgiving holiday in the US. | 16:51 |
mestery | michsmit: The action items will show up in the meeting logs, and I'll add them to the wiki page. | 16:51 |
mestery | We'll cover those first at our next meeting. | 16:52 |
mestery | prasad_: Mailing list and Google doc. If you want on that, please DM me your google ID so I can add you. | 16:52 |
*** uri__ has joined #openstack-meeting-alt | 16:53 | |
*** jmontemayor has joined #openstack-meeting-alt | 16:53 | |
prasad_ | mestery_: prasad.vellanki@oneconvergence.com | 16:53 |
mestery | Thanks prasad_ | 16:53 |
mestery | OK, thanks everyone for joining the first Neutron Group Policy meeting! | 16:54 |
alagalah | mestery: thank you | 16:54 |
mestery | Looking forward to continuing to make progress with everyone! | 16:54 |
mestery | #endmeeting | 16:54 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:54 | |
banix | Thank you! | 16:54 |
openstack | Meeting ended Thu Nov 21 16:54:17 2013 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:54 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/networking_policy/2013/networking_policy.2013-11-21-16.01.html | 16:54 |
s3wong | mestery: Thanks! | 16:54 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2013/networking_policy.2013-11-21-16.01.txt | 16:54 |
openstack | Log: http://eavesdrop.openstack.org/meetings/networking_policy/2013/networking_policy.2013-11-21-16.01.log.html | 16:54 |
*** uri__ has quit IRC | 16:54 | |
*** prasad_ has quit IRC | 16:54 | |
*** s3wong has quit IRC | 16:55 | |
*** thinrichs2 has quit IRC | 16:55 | |
*** jmontemayor has quit IRC | 16:55 | |
*** alazarev has joined #openstack-meeting-alt | 16:57 | |
*** mscohen02 has quit IRC | 16:58 | |
*** alagalah has quit IRC | 16:59 | |
*** jmontemayor has joined #openstack-meeting-alt | 16:59 | |
*** pdmars has quit IRC | 17:00 | |
*** aignatov has joined #openstack-meeting-alt | 17:00 | |
*** rushiagr has joined #openstack-meeting-alt | 17:01 | |
*** japplewhite has joined #openstack-meeting-alt | 17:02 | |
*** jmontemayor has quit IRC | 17:03 | |
*** rudrarugge has joined #openstack-meeting-alt | 17:05 | |
*** jmontemayor has joined #openstack-meeting-alt | 17:06 | |
*** Barker has joined #openstack-meeting-alt | 17:08 | |
*** devkulkarni has quit IRC | 17:10 | |
*** alazarev has quit IRC | 17:10 | |
*** markwash has quit IRC | 17:11 | |
*** rudrarugge has quit IRC | 17:12 | |
*** japplewhite has quit IRC | 17:13 | |
*** NikitaKonovalov has joined #openstack-meeting-alt | 17:14 | |
*** yogesh has joined #openstack-meeting-alt | 17:14 | |
*** boris-42 has joined #openstack-meeting-alt | 17:16 | |
*** Dinesh_ has quit IRC | 17:16 | |
*** michsmit has left #openstack-meeting-alt | 17:17 | |
*** japplewhite has joined #openstack-meeting-alt | 17:18 | |
*** eankutse has joined #openstack-meeting-alt | 17:19 | |
*** kgriffs_afk is now known as kgriffs | 17:21 | |
*** SergeyLukjanov has joined #openstack-meeting-alt | 17:22 | |
*** markmcclain has joined #openstack-meeting-alt | 17:24 | |
*** tanisdl has quit IRC | 17:26 | |
*** s3wong has joined #openstack-meeting-alt | 17:26 | |
*** s3wong has quit IRC | 17:26 | |
*** ekarlso has quit IRC | 17:30 | |
*** pballand has quit IRC | 17:31 | |
*** bdpayne has joined #openstack-meeting-alt | 17:36 | |
*** ekarlso has joined #openstack-meeting-alt | 17:37 | |
*** ruhe has joined #openstack-meeting-alt | 17:39 | |
*** ErikB has quit IRC | 17:41 | |
*** vkmc has quit IRC | 17:42 | |
*** NikitaKonovalov has quit IRC | 17:43 | |
*** NikitaKonovalov has joined #openstack-meeting-alt | 17:44 | |
*** markwash has joined #openstack-meeting-alt | 17:47 | |
*** NikitaKonovalov has quit IRC | 17:49 | |
*** coolsvap is now known as coolsvap_away | 17:50 | |
*** japplewhite has quit IRC | 17:51 | |
*** NikitaKonovalov has joined #openstack-meeting-alt | 17:51 | |
*** ashaikh has joined #openstack-meeting-alt | 17:52 | |
*** akuznetsov has joined #openstack-meeting-alt | 17:53 | |
*** julim has quit IRC | 17:53 | |
*** yogesh has quit IRC | 17:54 | |
*** alazarev has joined #openstack-meeting-alt | 17:55 | |
*** devlaps has joined #openstack-meeting-alt | 17:55 | |
*** songole_ has quit IRC | 17:56 | |
*** vponomaryov has left #openstack-meeting-alt | 17:57 | |
*** mattf has joined #openstack-meeting-alt | 17:58 | |
*** colinmcnamara has joined #openstack-meeting-alt | 17:58 | |
*** yogesh has joined #openstack-meeting-alt | 18:00 | |
*** sarob has joined #openstack-meeting-alt | 18:00 | |
*** jspeidel has joined #openstack-meeting-alt | 18:00 | |
*** pdmars has joined #openstack-meeting-alt | 18:02 | |
*** derekh has quit IRC | 18:02 | |
*** NikitaKonovalov has quit IRC | 18:02 | |
SergeyLukjanov | howdy savanna folks | 18:03 |
*** jmaron has joined #openstack-meeting-alt | 18:03 | |
ruhe | hey | 18:03 |
aignatov | o/ | 18:03 |
mattf | howdy | 18:04 |
jspeidel | hi | 18:04 |
SergeyLukjanov | ok, we have a quorum | 18:04 |
*** NikitaKonovalov has joined #openstack-meeting-alt | 18:04 | |
SergeyLukjanov | #startmeeting savanna | 18:04 |
openstack | Meeting started Thu Nov 21 18:04:52 2013 UTC and is due to finish in 60 minutes. The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:04 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:04 |
*** openstack changes topic to " (Meeting topic: savanna)" | 18:04 | |
openstack | The meeting name has been set to 'savanna' | 18:04 |
SergeyLukjanov | #topic Agenda | 18:05 |
*** openstack changes topic to "Agenda (Meeting topic: savanna)" | 18:05 | |
*** eankutse has quit IRC | 18:05 | |
SergeyLukjanov | #link https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_November.2C_21 | 18:05 |
SergeyLukjanov | #topic Action items from the last meeting | 18:05 |
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)" | 18:05 | |
SergeyLukjanov | #info there are no action items from the prev. meeting | 18:05 |
SergeyLukjanov | #topic News / updates | 18:05 |
*** openstack changes topic to "News / updates (Meeting topic: savanna)" | 18:05 | |
*** boris-42 has quit IRC | 18:05 | |
SergeyLukjanov | folks, please | 18:06 |
SergeyLukjanov | #info our next release will be icehouse-1 (Dec, 5) | 18:06 |
mattf | looks like the bug day went well, and rather fast. i had a couple morning calls and you guys were 95% done by 11ET! | 18:06 |
*** sarob has quit IRC | 18:07 | |
*** japplewhite has joined #openstack-meeting-alt | 18:07 | |
*** sarob has joined #openstack-meeting-alt | 18:07 | |
mattf | https://wiki.openstack.org/wiki/Icehouse_Release_Schedule | 18:07 |
SergeyLukjanov | #info we have an awesome bug day and almost all issues are now in actual state | 18:07 |
aignatov | this week I started to check dmitryme patch about preliminary heat integration and stucked in heat installation on my laptop | 18:07 |
*** twoputt has joined #openstack-meeting-alt | 18:08 | |
*** twoputt_ has joined #openstack-meeting-alt | 18:08 | |
*** japplewhite has left #openstack-meeting-alt | 18:08 | |
aignatov | it seems heat was installed successfully but patch seem to be not working properly :) | 18:08 |
SergeyLukjanov | btw at the last project meeting we decided that I'll release (tag) i1 and the ttx will take over and start doing it by icehouse-2 | 18:09 |
*** markmcclain has quit IRC | 18:09 | |
SergeyLukjanov | and then* | 18:09 |
*** nadya_ has joined #openstack-meeting-alt | 18:09 | |
jmaron | does dmitryme patch make provisioning pluggable? It's be nice to be able to accommodate any other provisioning techs we come across.. | 18:09 |
SergeyLukjanov | so, we'll be a part of centralized release, not integrate yet :) | 18:09 |
SergeyLukjanov | jmaron, not yet | 18:10 |
jmaron | :( | 18:10 |
aignatov | no, right now, his patch just replace main logic of provisioning | 18:10 |
SergeyLukjanov | it was done to check possibility of Heat integration | 18:10 |
SergeyLukjanov | it's a PoC | 18:10 |
jmaron | gotcha | 18:10 |
aignatov | and it works on his Laptop ;) | 18:11 |
SergeyLukjanov | we'll make a pluggable mechanism to transparently merge and polish Heat support | 18:11 |
jmaron | :) | 18:11 |
jspeidel | ship it ;) | 18:11 |
SergeyLukjanov | and then make it defailt | 18:11 |
jmaron | de-fail? ;) | 18:11 |
*** ErikB has joined #openstack-meeting-alt | 18:11 | |
aignatov | yeah, I like this approach, Sergey | 18:12 |
*** sarob has quit IRC | 18:12 | |
jmaron | +1 | 18:12 |
jmaron | we should probably maintain the current nova based scheme as another plugin | 18:13 |
ruhe | is there something which heat is missing, but current provisioning mechanism already provides? for instance anti-affinity | 18:13 |
jmaron | some of the /etc/hosts manipulation, I believe | 18:13 |
SergeyLukjanov | jmaron, I think it'll live at least before Heat-based provisioning will be completed | 18:14 |
jmaron | is missing | 18:14 |
SergeyLukjanov | jmaron, yep | 18:14 |
SergeyLukjanov | but we'll start from resources orchestration | 18:14 |
SergeyLukjanov | and I hope that we'll land some kind of agents till the end of I | 18:14 |
SergeyLukjanov | and so we'll avoid all the ssh/http from controller to vms | 18:15 |
nadya_ | will anybody start working on contribution to heat? | 18:15 |
aignatov | jmaron, as i remember and understood it correctly, heat guys told us that Neutron somehow can apply ip addresses before provisioning, so etc host manipulation could be done during cloud init script running | 18:15 |
SergeyLukjanov | aignatov, could you please make an update about our CI lab | 18:15 |
*** ErikB has quit IRC | 18:16 | |
aignatov | CI Lab is broken :( | 18:16 |
aignatov | so it will set -1 always from now | 18:16 |
*** ErikB has joined #openstack-meeting-alt | 18:16 | |
jmaron | any sense how long to fix? | 18:16 |
jspeidel | is this a temporary issue that is being resolved? | 18:16 |
SergeyLukjanov | aignatov, yep, AFAIK it's possible to acquire IP addresses from Neutron and then generate Heat template | 18:17 |
aignatov | it happened during moving ci from grizzly to havana | 18:17 |
alazarev | aignatov: will this work for floating IPs? | 18:17 |
aignatov | jspeidel: this temporary, our deployers do the best to make it work again | 18:17 |
*** boris-42 has joined #openstack-meeting-alt | 18:18 | |
aignatov | alazarev: don't know, need to dig it | 18:18 |
SergeyLukjanov | ok, let's move on | 18:18 |
nadya_ | i think ips assignment is the idea for the one more PoC | 18:18 |
ruhe | alazarev, we don't need floating ip for /etc/hosts | 18:18 |
jmaron | neutron client allows querying for floating IP pools, I believe, so it seems possible | 18:18 |
jmaron | ruhe: oh yeah…true | 18:19 |
*** gokrokve has quit IRC | 18:19 | |
*** boris-42 has quit IRC | 18:19 | |
SergeyLukjanov | only internal IPs needed to generate etc hosts | 18:19 |
SergeyLukjanov | #topic Icehouse-1 plans | 18:19 |
*** openstack changes topic to "Icehouse-1 plans (Meeting topic: savanna)" | 18:19 | |
*** yogesh has quit IRC | 18:19 | |
SergeyLukjanov | i1 will be in two weeks | 18:19 |
SergeyLukjanov | so, looks like it's too late to plan something big on it | 18:20 |
alazarev | ruhe: oh, true | 18:20 |
aignatov | jspeidel: we will retrigger ci jobs for all failed tests in each patch | 18:20 |
SergeyLukjanov | are there any thoughts about critical issues or bps that should be landed in i1? | 18:20 |
jspeidel | aignatov: thanks for the update | 18:20 |
jspeidel | for hdp, we are working on | 18:21 |
jspeidel | https://blueprints.launchpad.net/savanna/+spec/hdp-specify-local-repo | 18:21 |
jspeidel | and https://blueprints.launchpad.net/savanna/+spec/hdp-hdp2-support | 18:21 |
aignatov | SergeyLukjanov: may be we just need to fix all high priority bugs in i1. what do you think? | 18:21 |
aignatov | or at least all | 18:21 |
*** gokrokve has joined #openstack-meeting-alt | 18:21 | |
SergeyLukjanov | jspeidel, I prefer to not land huge patches more one week before the milestone | 18:22 |
mattf | fyi, next week is a standard vacation week in the US | 18:22 |
aignatov | at least -> almost | 18:22 |
ruhe | is it turkey week? | 18:22 |
SergeyLukjanov | US folks, how'll be on vacation next week? :) | 18:22 |
jspeidel | SergeyLukjanov: agreed that this work will not be complete for i1 | 18:22 |
ErikB | ruhe, yes | 18:23 |
jmaron | turkey/dreidel week, actually | 18:23 |
mattf | ruhe, it is | 18:23 |
SergeyLukjanov | jspeidel, I'm talking only about icehouse-1 now, don't worry about rest 4.5 months :) | 18:23 |
SergeyLukjanov | aignatov, it'll be great if we'll close high prio bugs | 18:24 |
SergeyLukjanov | in fact only one is https://bugs.launchpad.net/savanna/+bug/1243638 | 18:25 |
SergeyLukjanov | https://bugs.launchpad.net/savanna/+bug/1240511 is randomly reproducable | 18:25 |
SergeyLukjanov | and https://bugs.launchpad.net/savanna/+bug/1249063 | 18:25 |
SergeyLukjanov | I'll take it | 18:25 |
SergeyLukjanov | https://bugs.launchpad.net/savanna/+bug/1252684 I'm not sure that it's doable atm | 18:26 |
*** rcallawa has joined #openstack-meeting-alt | 18:26 | |
aignatov | https://bugs.launchpad.net/savanna/+bug/1240511 is wired, yeah | 18:26 |
SergeyLukjanov | any thoughts? | 18:26 |
SergeyLukjanov | ok, let's move on | 18:27 |
SergeyLukjanov | #topic Versioning and issues/bps management | 18:27 |
*** openstack changes topic to "Versioning and issues/bps management (Meeting topic: savanna)" | 18:27 | |
*** rnirmal has joined #openstack-meeting-alt | 18:27 | |
SergeyLukjanov | I've talked today with ttx about savanna subprojects versioning and releasing | 18:28 |
*** NikitaKonovalov has quit IRC | 18:28 | |
SergeyLukjanov | there are two mandatory changes needed | 18:28 |
*** rcallawa has left #openstack-meeting-alt | 18:28 | |
SergeyLukjanov | #info use a separate project and versions for the client | 18:28 |
aignatov | jfyi, ttx is release manager of openstack | 18:29 |
SergeyLukjanov | and release -extra separately too because it's not really connected to the main project | 18:29 |
*** markmcclain has joined #openstack-meeting-alt | 18:29 | |
SergeyLukjanov | and should moved to the Hadoop community | 18:29 |
SergeyLukjanov | ttx == Thierry Carrez | 18:29 |
aignatov | what you mean should moved to hadoop community? | 18:30 |
*** NikitaKonovalov has joined #openstack-meeting-alt | 18:30 | |
nadya_ | they dont want to have java code | 18:30 |
SergeyLukjanov | OpenStack community is not the best place for Hadoop FS and java code :) | 18:30 |
*** julim has joined #openstack-meeting-alt | 18:30 | |
SergeyLukjanov | and due to the fact that it was partially landed to the Hadoop, we should push it to the Hadoop eco I think | 18:31 |
mattf | -extra is currently swift plugin for hadoop and edp example | 18:31 |
SergeyLukjanov | yep | 18:31 |
mattf | +1 to that | 18:31 |
mattf | stevel has posted backports of the swift plugin to both the hadoop 1.x and 2.x branches | 18:31 |
SergeyLukjanov | as for the edp example - it's strongly wired with main code and could be moved to the savanna repo | 18:32 |
alazarev | mattf: it is in 2.x only for now | 18:32 |
ruhe | there is a problem with this plugin being a part of hadoop code | 18:32 |
mattf | i'm mildly concerned about the edp test jar files | 18:32 |
mattf | i was thinking about proposing they get moved to -extra | 18:32 |
ruhe | it'll be difficult to update it with changes in OpenStack api | 18:32 |
alazarev | mattf: do you have info about 1.x? | 18:32 |
SergeyLukjanov | all tests will be moved to the tempest eventually | 18:33 |
nadya_ | i think i should find sources of jars | 18:33 |
SergeyLukjanov | all integration tests* | 18:33 |
nadya_ | and publish | 18:33 |
mattf | alazarev, yeah, i can share the email w/ you after the meeting | 18:33 |
nadya_ | anybody hear me? | 18:33 |
mattf | nadya_, +1 at a minimum | 18:33 |
nadya_ | great :) | 18:33 |
SergeyLukjanov | nadya_, it'll be great to publish sources | 18:33 |
alazarev | mattf: thank you, please do it | 18:33 |
*** eankutse has joined #openstack-meeting-alt | 18:33 | |
*** eankutse has quit IRC | 18:34 | |
aignatov | udf.jar is piggybank, all rest code is self-written | 18:34 |
aignatov | that's all examples | 18:34 |
*** eankutse has joined #openstack-meeting-alt | 18:34 | |
SergeyLukjanov | so, for now, I think to keep -extra as is and release it with main savanna code | 18:34 |
SergeyLukjanov | to keep examples near to the project | 18:34 |
alazarev | mattf: because I'm doing back port to 1.x right now, it would be great if everything is already done | 18:34 |
mattf | alazarev, i would imagine! | 18:35 |
rnirmal | backport the swift plugin to 1.x ? | 18:35 |
mattf | yes | 18:35 |
alazarev | yes | 18:35 |
rnirmal | yeah it works with 1.x .. one or two minor tweaks | 18:35 |
SergeyLukjanov | we'll have separated launchpad projects for both client and dashboard plugin | 18:35 |
alazarev | the next step is to push data locality patch to both 1.x and 2.x | 18:35 |
mattf | SergeyLukjanov, btw, call me a purist, but committing a jar to git is wrong | 18:36 |
*** Barker has quit IRC | 18:36 | |
ruhe | mattf, that's wrong indeed | 18:36 |
aignatov | agree with mattf | 18:36 |
jmaron | purist | 18:36 |
alazarev | swift data locality | 18:36 |
jspeidel | mattf: +1 | 18:36 |
SergeyLukjanov | mattf, I'm absolutely agree, that's just temp solution | 18:36 |
mattf | git never forgets | 18:36 |
aignatov | we just need to describe instructions where to find needed jar file | 18:36 |
nadya_ | what jar do you mean? | 18:36 |
*** NikitaKonovalov has quit IRC | 18:36 | |
alazarev | mattf: +1 | 18:36 |
ruhe | can't we upload it to the same place where qcow2 images are hosted? | 18:37 |
aignatov | udf.jar in current examples is here https://cwiki.apache.org/confluence/display/PIG/PiggyBank | 18:37 |
SergeyLukjanov | nadya_, any jar | 18:37 |
nadya_ | udf.jar ? | 18:37 |
SergeyLukjanov | nadya_, any binary file | 18:37 |
jmaron | yes | 18:37 |
nadya_ | sergey, I mean our case | 18:37 |
mattf | nadya_, specifically these jars = https://review.openstack.org/#/c/56235/ | 18:37 |
SergeyLukjanov | yep | 18:37 |
SergeyLukjanov | we have 2 more subprojects - dashboard and elements and here we have several options | 18:38 |
nadya_ | we move swift plugins to Hadoop, udf i will publish. i thought we have no more jars | 18:38 |
aignatov | edp-lib.jar is udf.jar or piggybank, edp-job.jar is renamed oozie-examples | 18:38 |
jmaron | alazarev: data locality patch? | 18:38 |
aignatov | we don;tneed to keep it in any repo | 18:38 |
*** NikitaKonovalov has joined #openstack-meeting-alt | 18:39 | |
SergeyLukjanov | let's return back to the releasing/versions | 18:39 |
nadya_ | ah, libs...i see | 18:39 |
alazarev | jmaron: https://review.openstack.org/#/c/47824/ | 18:39 |
SergeyLukjanov | we'll release client much faster than savanna and so we can release dashboard too | 18:40 |
SergeyLukjanov | the question is - should we adjust our dashboard releases with savanna or not | 18:40 |
* mattf considers getting off his client soapbox | 18:40 | |
*** NikitaKonovalov has quit IRC | 18:40 | |
*** NikitaKonovalov has joined #openstack-meeting-alt | 18:40 | |
*** lblanchard has quit IRC | 18:40 | |
SergeyLukjanov | the same with elements | 18:40 |
mattf | adjust with savanna? | 18:40 |
*** rongze has quit IRC | 18:40 | |
nadya_ | anyway, looks like we may add lib to maven dependencies w.g. I think we may find a way to avoid jars | 18:41 |
SergeyLukjanov | I mean main code | 18:41 |
ruhe | SergeyLukjanov, definitely should | 18:41 |
mattf | adjust = align? | 18:41 |
SergeyLukjanov | yep | 18:41 |
*** yogesh has joined #openstack-meeting-alt | 18:41 | |
alazarev | SergeyLukjanov: we should somehow sync APIs they use/provide | 18:41 |
ruhe | SergeyLukjanov, otherwise it'll make a hell to those who bundle savanna into distro packages | 18:41 |
SergeyLukjanov | ruhe, sounds reasonable | 18:42 |
jspeidel | agreed, they should be aligned | 18:42 |
mattf | we have a handful of deliverables: savanna, dashboard, elements, client, extra. we're versioning and releasing them all together. what's the desired end state? | 18:42 |
aignatov | so, in such case, if savanna is in active development and savannaclient is not because it already has need functional, savannaclient amy become i2 from i1 without any patch, right? | 18:43 |
SergeyLukjanov | mattf, we'll have separated versioning for client starting from today | 18:43 |
mattf | sounds like extra -> /dev/null, client -> independent entity, savanna -> independent entity, dashboard -> horizon | 18:43 |
SergeyLukjanov | yep, we'll do it after graduating from the incubation | 18:43 |
alazarev | mattf: in this case after API change in any component it could be used only in next release | 18:44 |
SergeyLukjanov | (I mean horizon) | 18:44 |
mattf | alazarev, i'm not as firmly on my soapbox so long as the releases cycles are separated | 18:44 |
SergeyLukjanov | client should keep backward compatibility and support prev. APIs versions | 18:44 |
jmaron | is extra going away? I got impression some EDP code would remain | 18:45 |
mattf | alazarev, if we release client in i1 and have to wait 6 weeks to fix dashboard in i2, ugh | 18:45 |
SergeyLukjanov | client will be released separately anyway, it's not a question to discuss | 18:45 |
mattf | SergeyLukjanov, yeah, well done identifying the problem and defusing the argument | 18:46 |
SergeyLukjanov | the question is only about -dashboard and -image-elements | 18:46 |
mattf | what if we start pushing our elements up to dib? | 18:46 |
ruhe | i demand client releases on the same date with the main code. there might be additional releases for sure | 18:46 |
nadya_ | mattf, lol | 18:46 |
mattf | ruhe, is SergeyLukjanov close enough to throw something at you? | 18:47 |
ruhe | no :) | 18:47 |
mattf | darn | 18:47 |
SergeyLukjanov | ruhe, it's not a common approach in OpenStack | 18:48 |
mattf | ruhe, you're proposing a stronger alignment. not only is client released whenever we feel like it but it is also _always_ released w/ savanna main? | 18:48 |
SergeyLukjanov | clients have new releases after some important fixes or after some period of time | 18:48 |
mattf | to that i'd say sure, as long as i'm not doing the extra, potentially unnecessary, work to do that release | 18:48 |
SergeyLukjanov | minor releases | 18:48 |
SergeyLukjanov | and major for new release cycles and API versions | 18:48 |
ruhe | mattf, otherwise how can we align all the dependencies when packaging savanna, dashboard and client into disto packages | 18:49 |
mattf | i think we accept that version numbers no longer match | 18:49 |
SergeyLukjanov | ruhe, I don't think that it's a problem | 18:49 |
mattf | imho version numbers should not be aligned to identify compatibility. that's what deps are for. | 18:49 |
SergeyLukjanov | ruhe, the same story with all other OpenStack projects | 18:50 |
jmaron | mattf: +1 | 18:50 |
ruhe | SergeyLukjanov, i only want all the dependencies to be aligned. otherwise newer version of pythonclient might be api-compatible for denendency-incompatible | 18:50 |
*** NikitaKonovalov has quit IRC | 18:51 | |
ruhe | *but denendency-incompatible | 18:51 |
SergeyLukjanov | btw, the next releases will be 2014.1.b1 for savanna, 0.4 for python-savannaclient and if we decided to keep rest subprojects aligned with main savanna releases than they'll be 2013.1.b1 too | 18:51 |
mattf | how about the idea of elements -> dib ? | 18:52 |
SergeyLukjanov | mattf, only after incubation | 18:52 |
mattf | why's that? | 18:52 |
SergeyLukjanov | it's an integrated project | 18:52 |
*** NikitaKonovalov has joined #openstack-meeting-alt | 18:53 | |
jmaron | dib, that is? | 18:53 |
ruhe | https://github.com/openstack/diskimage-builder | 18:53 |
SergeyLukjanov | ttx suggests to move them to the savanna repo for the I release (like trove guys done) and then move them to dib or tripleo | 18:53 |
SergeyLukjanov | but it looks like that we should keep them separately and just release them with main code | 18:54 |
aignatov | mattf, who wanted to move elements to savanna repo originally? ;) | 18:54 |
SergeyLukjanov | aignatov, not me, I have concerns about gating them and just using | 18:54 |
SergeyLukjanov | the same story with -extra repo | 18:54 |
SergeyLukjanov | so, I think the main question is still about -dashboard | 18:55 |
SergeyLukjanov | is it better to be possible to push more versions for it? | 18:56 |
jmaron | how fluid do we think it's going to be, feature wise? | 18:56 |
alazarev | dashboard should indicate with which savanna version it works | 18:56 |
alazarev | is any way to do that without having releases synced? | 18:57 |
SergeyLukjanov | dashboard only depends on client :) | 18:57 |
SergeyLukjanov | that's released separately | 18:57 |
SergeyLukjanov | that's my concern | 18:57 |
SergeyLukjanov | [savanna, -image-elements, -extra] [client] [dashboard] | 18:58 |
SergeyLukjanov | ^^ my current opinion | 18:58 |
SergeyLukjanov | and then we move dashboard to horizon and we'll have only two separately releasing groups | 18:59 |
SergeyLukjanov | looks like we're out of time, let's move to the #savanna and continue discussion | 18:59 |
nadya_ | i dont understand what variants we have except the above | 18:59 |
SergeyLukjanov | it'll be better to complete it tpday | 18:59 |
alazarev | and how dashboard and savanna linked in this case? By docs? | 18:59 |
*** amcrn has joined #openstack-meeting-alt | 18:59 | |
*** jspeidel has left #openstack-meeting-alt | 18:59 | |
*** jmaron has left #openstack-meeting-alt | 19:00 | |
SergeyLukjanov | thank you all guys | 19:00 |
SergeyLukjanov | #endmeeting | 19:00 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 19:00 | |
openstack | Meeting ended Thu Nov 21 19:00:09 2013 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 19:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-11-21-18.04.html | 19:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-11-21-18.04.txt | 19:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-11-21-18.04.log.html | 19:00 |
*** _ozstacker_ has quit IRC | 19:00 | |
alazarev | mattf: please forward me email about swift in hadoop 1.x | 19:00 |
*** _ozstacker_ has joined #openstack-meeting-alt | 19:01 | |
*** nadya_ has quit IRC | 19:03 | |
*** gokrokve has quit IRC | 19:04 | |
*** gokrokve has joined #openstack-meeting-alt | 19:04 | |
*** sarob has joined #openstack-meeting-alt | 19:06 | |
*** gokrokve has quit IRC | 19:08 | |
*** colinmcnamara has quit IRC | 19:11 | |
*** rongze has joined #openstack-meeting-alt | 19:11 | |
*** akuznetsov has quit IRC | 19:11 | |
*** mattf has left #openstack-meeting-alt | 19:13 | |
*** NikitaKonovalov has quit IRC | 19:14 | |
*** akuznetsov has joined #openstack-meeting-alt | 19:17 | |
*** NikitaKonovalov has joined #openstack-meeting-alt | 19:17 | |
*** rongze has quit IRC | 19:18 | |
*** rushiagr has quit IRC | 19:19 | |
*** gokrokve has joined #openstack-meeting-alt | 19:20 | |
*** nadya has joined #openstack-meeting-alt | 19:21 | |
*** nadya is now known as Guest2893 | 19:21 | |
*** devkulkarni has joined #openstack-meeting-alt | 19:24 | |
*** jtomasek has quit IRC | 19:28 | |
*** ashaikh has quit IRC | 19:32 | |
*** alazarev has quit IRC | 19:37 | |
*** lblanchard has joined #openstack-meeting-alt | 19:37 | |
*** ErikB has quit IRC | 19:38 | |
*** Guest2893 has quit IRC | 19:43 | |
*** ThiagoCMC has joined #openstack-meeting-alt | 19:44 | |
*** amcrn is now known as [a]mcrn | 19:44 | |
*** rongze has joined #openstack-meeting-alt | 19:45 | |
*** ruhe has quit IRC | 19:45 | |
*** akuznetsov has quit IRC | 19:46 | |
*** alazarev has joined #openstack-meeting-alt | 19:49 | |
*** rongze has quit IRC | 19:50 | |
*** s3wong has joined #openstack-meeting-alt | 19:51 | |
*** sarob has quit IRC | 19:51 | |
*** sarob has joined #openstack-meeting-alt | 19:52 | |
*** ashaikh has joined #openstack-meeting-alt | 19:54 | |
*** jdbarry has quit IRC | 19:56 | |
*** sarob has quit IRC | 19:56 | |
*** jdbarry has joined #openstack-meeting-alt | 19:58 | |
*** sarob has joined #openstack-meeting-alt | 19:59 | |
*** sarob has quit IRC | 19:59 | |
*** bdpayne has quit IRC | 19:59 | |
*** sarob has joined #openstack-meeting-alt | 19:59 | |
*** bdpayne has joined #openstack-meeting-alt | 20:00 | |
*** yogesh has quit IRC | 20:01 | |
*** devkulkarni has quit IRC | 20:03 | |
*** s3wong has left #openstack-meeting-alt | 20:05 | |
*** yogesh_ has joined #openstack-meeting-alt | 20:05 | |
*** s3wong has joined #openstack-meeting-alt | 20:07 | |
*** rwsu has joined #openstack-meeting-alt | 20:08 | |
*** sc68cal has joined #openstack-meeting-alt | 20:08 | |
*** devkulkarni has joined #openstack-meeting-alt | 20:10 | |
*** radix_ has quit IRC | 20:12 | |
*** vipul is now known as vipul-away | 20:15 | |
*** vipul-away is now known as vipul | 20:15 | |
*** colinmcnamara has joined #openstack-meeting-alt | 20:18 | |
*** tedross has joined #openstack-meeting-alt | 20:20 | |
*** colinmcnamara has quit IRC | 20:22 | |
*** bdpayne has quit IRC | 20:23 | |
*** colinmcnamara has joined #openstack-meeting-alt | 20:27 | |
*** bdpayne has joined #openstack-meeting-alt | 20:30 | |
*** alazarev has quit IRC | 20:34 | |
*** yogesh has joined #openstack-meeting-alt | 20:35 | |
*** ashaikh has quit IRC | 20:37 | |
*** yogesh_ has quit IRC | 20:37 | |
*** vipul is now known as vipul-away | 20:38 | |
*** vipul-away is now known as vipul | 20:38 | |
*** colinmcnamara has quit IRC | 20:39 | |
*** ashaikh has joined #openstack-meeting-alt | 20:41 | |
*** rongze has joined #openstack-meeting-alt | 20:47 | |
*** markmcclain has quit IRC | 20:47 | |
*** ThiagoCMC has quit IRC | 20:49 | |
*** rongze has quit IRC | 20:51 | |
*** djoreilly has joined #openstack-meeting-alt | 20:53 | |
*** vipul is now known as vipul-away | 20:53 | |
*** kgriffs is now known as kgriffs_afk | 20:54 | |
*** vipul-away is now known as vipul | 20:54 | |
*** aveiga has joined #openstack-meeting-alt | 20:55 | |
*** markmcclain has joined #openstack-meeting-alt | 20:57 | |
*** shshang has joined #openstack-meeting-alt | 20:57 | |
shshang | Hello | 20:58 |
mestery | o/ | 20:59 |
aveiga | hello | 20:59 |
shshang | New to the meeting, sorry for any inconvenience in advance. :) | 20:59 |
mestery | shshang: No worries, lets wait until sc68cal starts things up. | 20:59 |
*** bdpayne has quit IRC | 21:00 | |
sc68cal | Hello | 21:01 |
sc68cal | #startmeeting neutron_ipv6 | 21:01 |
shshang | Hello, Sean | 21:01 |
openstack | Meeting started Thu Nov 21 21:01:11 2013 UTC and is due to finish in 60 minutes. The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot. | 21:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 21:01 |
*** bdpayne has joined #openstack-meeting-alt | 21:01 | |
*** openstack changes topic to " (Meeting topic: neutron_ipv6)" | 21:01 | |
openstack | The meeting name has been set to 'neutron_ipv6' | 21:01 |
*** kraman has quit IRC | 21:01 | |
*** kraman has joined #openstack-meeting-alt | 21:01 | |
sc68cal | OK - thank you everyone that has decided to attend | 21:02 |
*** BrianB_ has joined #openstack-meeting-alt | 21:02 | |
sc68cal | The agenda is pretty straight forward | 21:02 |
*** SergeyLukjanov has quit IRC | 21:02 | |
sc68cal | My name is Sean Collins, and I work for Comcast | 21:03 |
shshang | Great to "see" you, Sean | 21:03 |
sc68cal | please feel free to introduce yourselves | 21:03 |
*** dprince has quit IRC | 21:03 | |
*** kgriffs_afk is now known as kgriffs | 21:03 | |
aveiga | I'm Anthony Veiga, IPv6 SME at Comcast | 21:03 |
shshang | My name is Shixiong. I used to work for Cisco, but recently joined a startup working on OpenStack and IPv6 | 21:03 |
*** denis_makogon has quit IRC | 21:04 | |
*** denis_makogon_ is now known as denis_makogon | 21:04 | |
mestery | Howdy folks, Kyle from Cisco. | 21:04 |
shshang | Hi, Kyle | 21:04 |
*** dmakogon_ has joined #openstack-meeting-alt | 21:04 | |
sc68cal | I am mostly working with aveiga to get OpenStack Neutron to work with the networking environment we have set up at Comcast | 21:05 |
sc68cal | As such, we're busy creating bugs and blueprints to cover things that we need done right away, to make it work in our environment, as well as some blueprints that probably would be useful to the community as well | 21:05 |
sc68cal | #link https://bugs.launchpad.net/neutron/+bug/1252852 | 21:06 |
*** carlp has joined #openstack-meeting-alt | 21:06 | |
*** ijw has joined #openstack-meeting-alt | 21:06 | |
sc68cal | hmm, not sure if that worked or not | 21:06 |
sc68cal | #link https://bugs.launchpad.net/nova/+bug/1251235 | 21:06 |
sc68cal | #link https://bugs.launchpad.net/neutron/+bug/1242933 | 21:06 |
ijw | evening ladies and gents | 21:07 |
sc68cal | hi ijw - welcome | 21:07 |
shshang | interesting...the 2nd bug explained what we saw before.... | 21:07 |
carlp | o/ | 21:07 |
mestery | sc68cal: Try #link <link> <description> | 21:07 |
ijw | Seen that first one, it's bloody annoying | 21:07 |
*** ashaikh has quit IRC | 21:07 | |
mestery | It will show in hte logs. | 21:07 |
sc68cal | #link https://bugs.launchpad.net/nova/+bug/1251235 ip6tables rules isssues | 21:08 |
shshang | for the first one, I think ip6tables also drops ND packets, if I am not mistaken | 21:08 |
ijw | Didn't when I tried it | 21:08 |
ijw | The second's very risky - need to source-filter your RAs | 21:08 |
aveiga | shshang: It does | 21:08 |
sc68cal | Yeah, that's due to the hairpinning on the bridge device | 21:08 |
ijw | (speaking as a man of much experience and bitterness with some muppet in the lab sending them out) | 21:08 |
sc68cal | #link https://bugs.launchpad.net/nova/+bug/1251235 | 21:09 |
sc68cal | #link https://bugs.launchpad.net/nova/+bug/1251235 hairpinning issue for DAD | 21:09 |
sc68cal | sorry, still getting used to this :) | 21:09 |
shshang | is there any workaround for the 2nd bug? | 21:09 |
sc68cal | shshang: for the hairpin? | 21:09 |
shshang | yup | 21:10 |
aveiga | the workaround we're using currently is a very painful and manual process to disable hairpinning on the tap | 21:10 |
shshang | I had to manually disable DAD | 21:10 |
sc68cal | shshang: yeah, I have a patch to nova that's in review | 21:10 |
shshang | on guest VM before | 21:10 |
*** ashaikh has joined #openstack-meeting-alt | 21:10 | |
*** haleyb has joined #openstack-meeting-alt | 21:10 | |
sc68cal | should be linked in the bug report | 21:10 |
* haleyb never knew about the -alt channel until today | 21:10 | |
shshang | I see. Thanks for bringing it up | 21:11 |
sc68cal | Basically this stuff I've filed has been for our immediate goal, getting IPv6 networks that we have existing outside of openstack, to work with OpenStack the way provider networks does on the v4 side | 21:11 |
sc68cal | Obviously, IPv6 has some differences, since OpenStack wants to be the source of truth for things like subnets | 21:11 |
sc68cal | and that's where we're running up against issues, where OpenStack gets confused and creates ip6tables rules for ::/128 in the security group rules | 21:11 |
aveiga | we should consider a longer term roadmap of the parts of IPv6 that we need to get working | 21:11 |
sc68cal | aveiga: +1 | 21:12 |
shshang | agree | 21:12 |
sc68cal | #link https://blueprints.launchpad.net/neutron/+spec/ipv6-provider-nets-slaac | 21:12 |
shshang | #agreed | 21:12 |
*** Dane has joined #openstack-meeting-alt | 21:12 | |
sc68cal | That's a blueprint I'm trying to collect all my immediate work, to get IPv6 running inside OpenStack | 21:12 |
shshang | There is a hacking way to make dnsmasq to announce RA | 21:13 |
ijw | I don't think you'll be able to determine how routers should work in an hour long IRC meeting, to be honest... | 21:13 |
shshang | but it is quite a hassle | 21:13 |
aveiga | What I want to make sure we don't do is be blinded by individual goals. I realize there are many people who want IPv6 that aren't necessarily keen on it being done via l2-provier | 21:13 |
aveiga | so that said, we've already got IPv6 via l2-provider/slaac as one implementation | 21:13 |
aveiga | are there others that should be looked at for immediate needs? | 21:14 |
sc68cal | We also want to extend DNSmasq so that you can do things like DHCPv6, create subnets on the v6 side and get things on par with the v4 side | 21:14 |
sc68cal | #link https://blueprints.launchpad.net/neutron/+spec/dnsmasq-mode-keyword | 21:14 |
ijw | What are you doing about antispoof with SLAAC? | 21:14 |
sc68cal | more long term | 21:14 |
aveiga | ijw: right now, nothing | 21:14 |
aveiga | however, I think the goal should be that when you create a subnet in an IPv6 SLAAC network, we should configure the router | 21:15 |
aveiga | and then use the router's information to populate the source list for RA inpouts | 21:15 |
shshang | @sc68cal, I am a little bit confused about the #link https://blueprints.launchpad.net/neutron/+spec/dnsmasq-mode-keyword | 21:16 |
aveiga | but again, we're in the baby steps mode right now of just getting it to work at a low level before implementing | 21:16 |
ijw | What I said about how long it'll take to decide that definitely applies. Firstly, ipv4 routers don't advertise routes, but v6 ones do - so probably we should add a route-advertise flag on the network that both respect. | 21:16 |
sc68cal | shshang: what has you confused? | 21:17 |
*** aignatov has quit IRC | 21:17 | |
shshang | if we only talk about SLAAC here, then the way it is coding today has capability to detect subnet type. And if subnet is IPv6, then trigger RA. | 21:18 |
*** flaper87 is now known as flaper87|afk | 21:18 | |
shshang | However, if we talk about DHCPv6 and SLAAC, then yes, we need to provide options for user to define what they want | 21:18 |
ijw | I'm not sure you're allowed to assume that the link-local address is what the MAC suggests it is. | 21:18 |
aveiga | ijw: are you referring to privacy extensions? | 21:19 |
ijw | They don't apply to link local iirc | 21:19 |
aveiga | oops, missed that part | 21:19 |
shshang | agreed | 21:20 |
aveiga | what case would exist where the lla isn't EUI-64 derived? | 21:20 |
ijw | Trying to remember if link local is *required* to or *recommended* to be based on the link address. | 21:20 |
shshang | in my experiment, VM boots and it has linklocal address in any way. it doesn't need Openstack's help | 21:21 |
aveiga | I don't know that lla is relevant here | 21:22 |
shshang | the question here is, 1) How Openstack can send RA if we offer SLAAC 2) How OpenStack can store the SLAAC IPv6 address VM calculate | 21:22 |
aveiga | let's take a step back | 21:22 |
carlp | ijw: looks like it's required http://tools.ietf.org/html/rfc4291#section-2.5.6 | 21:22 |
aveiga | shshang: We don't necessarily want OpenStack to issue the RA in all cases | 21:23 |
aveiga | just in cases where an l3 agent is the gateway | 21:23 |
sc68cal | Oh, I nearly forgot, Dazhao yu is working on a patch to do the calculations for EUI-64 | 21:23 |
aveiga | most guests OSes ignore multiple RAs or ignore RA priority, and as such we'd blackhole them issueing RAs | 21:24 |
sc68cal | #link https://review.openstack.org/#/c/56184/ Calculate stateless IPv6 Addresses | 21:24 |
sc68cal | I think it just needs to be done against oslo, not neutron | 21:24 |
sc68cal | So, it's a bit of a info dump from what aveiga have been doing. | 21:26 |
sc68cal | There seems to be a lot of stuff where people have run into the same issues, but nothing seems to go back up into Neutron | 21:26 |
sc68cal | like hairpinning, etc. | 21:26 |
shshang | @aveiga, I can see your points in some setups.......is it a good approach to completely rely on external router? | 21:27 |
ijw | carlp - tehre's a few 'should' rather than 'must' in rfc2464 that leave it ambiguous | 21:27 |
carlp | ijw: true, but the diagram shows using the interface address which makes it seem like a must | 21:28 |
ijw | Yep, but how the interface address is calculated is where the 'should' comes in. That's a 64 bit value, there are options on what you use for it. | 21:28 |
aveiga | ijw, carlp: The instances where it wouldn't don't make sense, because you'd have a MAC collision anyway | 21:28 |
carlp | ijw: ah, missed that. Sorry | 21:28 |
ijw | To be fair, we get to tell people what they should do to an extent. Changing MACs in v4 gets you nowhere, too... | 21:29 |
*** jjmb has joined #openstack-meeting-alt | 21:29 | |
carlp | aveiga: MAC addresses should be unique in openstack, too much depends on that for them not to be. Especially on the same network segment. | 21:29 |
aveiga | carlp: agreed, hence lla shuld be EUI-64 derived in all cases | 21:30 |
ijw | In this instance, we're adding the additional requirement that no-one tries to be smart about assigning ipv6 LLs, but that's fine | 21:30 |
sc68cal | I'm a bit short on action items, at least for community work | 21:31 |
mestery | So, it's 30 minutes in, just checking if people have settle on either some bugs or BPs they'd like to focus on. | 21:31 |
mestery | Icehouse-1 is in 2 weeks. | 21:31 |
sc68cal | aveiga and myself are working mostly on the slaac + provider networking, since that's our setup internally | 21:32 |
aveiga | I'm also working to get some Third OParty Testing cycles spun up for this too | 21:32 |
aveiga | but I can only really test the l2-provider model right now | 21:32 |
mestery | Both of those are solid. I think it makes sense to track that work as action items for next week. | 21:33 |
mestery | Is anyone else willing to sign up for any of hte other bugs discussed here? | 21:33 |
shshang | @aveiga: Is your setup completely using external router to send RA, right? | 21:33 |
aveiga | shshang: Yes. | 21:33 |
*** pcm_ has quit IRC | 21:34 | |
ekarlso | yo gang | 21:34 |
ekarlso | quick question, what's the plan to introduce ipv6 in neutrpn ? | 21:34 |
haleyb | mestery: is there a list of bugs? i missed the first 10 minutes | 21:34 |
sc68cal | ekarlso: you'll have to read through the logs when we're done | 21:34 |
*** alazarev has joined #openstack-meeting-alt | 21:34 | |
mestery | sc68cal may have that list | 21:34 |
sc68cal | it should appear in the log when we're done, but if not I'll e-mail the mailing list for good measure | 21:35 |
haleyb | ok, i only know of the two he has | 21:35 |
aveiga | I actually have about 3 more to post. I'm a bit behind on my documentation | 21:35 |
*** NikitaKonovalov has quit IRC | 21:35 | |
ijw | sc68cal: so, just to confirm what your SLAAC stuff will leave us with - when you're done with your stuff, we're expecting VMs that assign themselves a global address appropriate to the subnet, right? | 21:35 |
jjmb | this is john brzozowski (jjmb), i run the ipv6 program at comcast - sean asked that introduce myself | 21:36 |
aveiga | ijw: We're expecting SLAAC to work normally as it would in any non-virtualized environment | 21:36 |
aveiga | again, this is for l2-provider models only | 21:36 |
sc68cal | ijw: Yes. Although the subnet is not inside openstack at this point | 21:36 |
aveiga | we should also get a blueprint to gether to bring DHCPv6 into the fold | 21:36 |
sc68cal | aveiga: I think the dnsmasq bp does cover that, though it could probably use better wording | 21:37 |
aveiga | then we should take that discussion in general to the mailing list and refine it | 21:37 |
sc68cal | ok | 21:38 |
aveiga | more needs to happen than just dnsmasq to get that bit working | 21:38 |
sc68cal | #action sc68cal discuss DHCPv6 support on the mailing list | 21:38 |
shshang | Can we discuss the big picture first, before we talk about bug fix? | 21:39 |
aveiga | please | 21:39 |
shshang | I am curious to see what approach we will take to tackle the IPv6 + Neutron issue | 21:40 |
shshang | something like the priority and dependancies | 21:40 |
aveiga | one of the key things required to get neutron to be ipv6-capable is for neutron to be able to derive, assign or retrieve the VM's IP address | 21:41 |
aveiga | that might be a good place to start | 21:41 |
shshang | agreed | 21:41 |
shshang | that is our goal | 21:41 |
shshang | or one of our goals | 21:41 |
sc68cal | aveiga: can I assign you a task of documenting our usecase? | 21:43 |
aveiga | sure, but let's link it to mailing list discussions | 21:43 |
aveiga | I don't claim to be omniscient | 21:44 |
sc68cal | ok | 21:44 |
*** yogesh has quit IRC | 21:44 | |
sc68cal | #action aveiga document our immediate needs from Neutron, and open discussion on the mailing list | 21:44 |
*** yogesh has joined #openstack-meeting-alt | 21:45 | |
shshang | How can we translate that to the blueprint? | 21:45 |
jjmb | do we want to include any phasing or future requirements? | 21:45 |
jjmb | ie a phased approach | 21:45 |
jjmb | or is this putting the cart before the horse? | 21:45 |
shshang | @jjmb, agreed | 21:45 |
aveiga | it might be better to gather them all and then prioritize them | 21:45 |
aveiga | perhaps based on the amount of responses from the mailing list | 21:45 |
sc68cal | #idea gather up requirements for immediate term, and log term | 21:46 |
jjmb | the immediate phase I would obviously need to be executed upon first... | 21:46 |
jjmb | however it might be useful for all to see and comment on what happens in future releases. aveiga/sc68cal? | 21:47 |
ijw | As a basic sequence of events, it seems it's basic firewalling and L2 stuff to start (so that SLAAC works at least on provider networks) then we'll move on to RAs and then DHCP, I would think. Longer term and more frightening is what routers actually *do* for v6, because it's not what they do for v4. And a problem for both v6 and v4 is how multiple subnets on a network are supposed to be treated, I think - mestery, unless you know mo | 21:47 |
aveiga | Is there anyone interested in doing a neutron-wide code review looking for instances of addressing that are either cast as ints or pulled from IPv4-only calls? | 21:47 |
*** rongze has joined #openstack-meeting-alt | 21:47 | |
sc68cal | ijw: well put | 21:47 |
shshang | @ijw. That sounds like a plan already | 21:48 |
sc68cal | aveiga: most of the calls i've seen is through netaddr | 21:48 |
aveiga | ijw: you bring up a good point, since multiple networks on the same subnet isn't a problem in IPv6... | 21:48 |
sc68cal | which handles ip stuff - most is stored internally in the DB I believe for addresses | 21:48 |
ijw | aveiga: 'interested' would be a strong statement, but I think it needs doing. We need to check the remaining bits of nova that neutron relies on too - and while we're at it can we please confirm that multiple subnets do work, and maybe even feed what we discover about operation to the docs people, because I don't think this is as well described as it should be | 21:48 |
sc68cal | *stored as strings | 21:49 |
*** yogesh has quit IRC | 21:49 | |
aveiga | ijw: Yes, and I plan on filing a bug soon about this. It turns out that if you even add an ipv6 subnet to a network with an IPv4 subnet, it disables the whole network | 21:49 |
shshang | aveiga, you are talking about the external network side? | 21:50 |
aveiga | Not sure about everyone else, but I don't want dual stack to require separate interfaces | 21:50 |
aveiga | shshang: yes | 21:50 |
*** jjmb has quit IRC | 21:50 | |
ijw | Yeah. Try not adding a subnet. Havana's slightly different in that you get an error, but in Grizzly you got no interfae | 21:50 |
shshang | I have solution for you | 21:50 |
ijw | aveiga: 4, 46 and 6 should all work | 21:50 |
shshang | aveiga, we already made dualstack working on external network side | 21:50 |
aveiga | shshang: We did too, by not putting in a subnet at all | 21:50 |
shshang | v4, v6 on the same interface | 21:50 |
aveiga | we can compare notes outside this meeting though, as I don't want to take up time | 21:51 |
ijw | shshang: where's the review? | 21:51 |
shshang | we didn't publish the code yet, but we wrote a white paper | 21:51 |
ijw | Right. Code review. Volunteer? | 21:51 |
ijw | o/ (reluctantly, cos someone has to) | 21:51 |
shshang | aveiga, ijw, if you are interested, we can have a call to review it together | 21:52 |
ijw | shshang: bung it in gerrit as a WIP and mail the link around, we can comment on it there | 21:52 |
aveiga | actually, I'd prefer documentation and an email thread on the list | 21:52 |
*** rongze has quit IRC | 21:52 | |
sc68cal | ijw: +1 | 21:52 |
sc68cal | shshang: can I put you down for an action on that item? | 21:52 |
shshang | ijw, that is a good idea, will do | 21:52 |
shshang | sc68cal, you mean, load code to github? | 21:53 |
sc68cal | #action shshang post code review & link on mailing list | 21:53 |
shshang | sure, I will do | 21:53 |
sc68cal | shshang: put it on gerrit and mark it as WIP | 21:53 |
shshang | aveiga, ijw, since this is my first time to post code, may need your help a little bit to make sure I did it right | 21:54 |
shshang | thanks in advance | 21:54 |
aveiga | I can help, but it will be my first time too shortly | 21:54 |
ijw | Might have more volunteers for the code review, if we can work out how best to file comments | 21:55 |
ijw | Also a checklist of issues to look for | 21:55 |
aveiga | I think I can finnagle jjmb into helping with that list | 21:55 |
aveiga | sc68cal: put me down for coming up with a list of gotchas that block IPv6 | 21:56 |
sc68cal | ok | 21:56 |
aveiga | I can work with soem folks internally that already did this on other projects | 21:56 |
shshang | sc68cal, please put me down for gap list too | 21:56 |
sc68cal | ok, not sure if I can link multiple people to it | 21:56 |
sc68cal | should probably be shshang aveiga and ijw | 21:57 |
ijw | sc68cal: can you start a thread on the ML about what to look for? And is there some way we can comment up the code on github or something similar? | 21:57 |
sc68cal | ijw: good question - probably the best thing to do is take notes then share on the mailing list | 21:57 |
aveiga | coming up on the end of the hour | 21:58 |
sc68cal | #action aveiga ijw shshang start code review looking for IPv4-isms | 21:58 |
sc68cal | Thanks everyone for coming, I'm going to get better at working with meetbot as we go along | 21:59 |
sc68cal | I promise :) | 21:59 |
*** eankutse has quit IRC | 21:59 | |
shshang | thanks! | 21:59 |
sc68cal | Next week is pretty close to a holiday in the US, so we may reconvene the week after | 21:59 |
sc68cal | #endmeeting | 21:59 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 22:00 | |
openstack | Meeting ended Thu Nov 21 21:59:58 2013 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 22:00 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-11-21-21.01.html | 22:00 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-11-21-21.01.txt | 22:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/neutron_ipv6/2013/neutron_ipv6.2013-11-21-21.01.log.html | 22:00 |
*** shshang has quit IRC | 22:00 | |
aveiga | thanks everyone | 22:00 |
ijw | sc68cal: only a holiday for some of us, so make sure you mail out if you cancel | 22:00 |
sc68cal | ijw: will do | 22:01 |
*** Dane has quit IRC | 22:01 | |
*** djoreilly has quit IRC | 22:01 | |
*** yogesh has joined #openstack-meeting-alt | 22:02 | |
*** julim has quit IRC | 22:03 | |
*** yamahata_ has joined #openstack-meeting-alt | 22:10 | |
*** radix_ has joined #openstack-meeting-alt | 22:10 | |
*** s3wong has quit IRC | 22:16 | |
*** pdmars has quit IRC | 22:17 | |
*** devkulkarni has quit IRC | 22:22 | |
*** kgriffs is now known as kgriffs_afk | 22:23 | |
*** BrianB_ has quit IRC | 22:26 | |
*** lblanchard has quit IRC | 22:29 | |
*** eankutse has joined #openstack-meeting-alt | 22:30 | |
*** aveiga has quit IRC | 22:31 | |
*** eggs-lunch is now known as eggmaster | 22:35 | |
*** markmcclain has quit IRC | 22:40 | |
*** radix_ has quit IRC | 22:42 | |
*** tedross has quit IRC | 22:44 | |
*** ashaikh has quit IRC | 22:45 | |
*** rongze has joined #openstack-meeting-alt | 22:48 | |
*** rongze has quit IRC | 22:54 | |
*** jprovazn has quit IRC | 22:57 | |
*** AlanClark has quit IRC | 22:58 | |
*** amytron has quit IRC | 23:02 | |
*** eharney has quit IRC | 23:02 | |
*** kevinconway has quit IRC | 23:02 | |
*** banix has quit IRC | 23:05 | |
*** venkatesh has joined #openstack-meeting-alt | 23:10 | |
*** alazarev has quit IRC | 23:13 | |
*** alazarev has joined #openstack-meeting-alt | 23:16 | |
*** devkulkarni has joined #openstack-meeting-alt | 23:17 | |
*** yogesh has quit IRC | 23:17 | |
*** yogesh has joined #openstack-meeting-alt | 23:18 | |
*** kgriffs_afk is now known as kgriffs | 23:19 | |
*** eankutse has quit IRC | 23:21 | |
*** yogesh has quit IRC | 23:22 | |
*** eankutse has joined #openstack-meeting-alt | 23:23 | |
*** yamahata_ has quit IRC | 23:25 | |
*** demorris has quit IRC | 23:25 | |
*** jmontemayor has quit IRC | 23:30 | |
*** venkatesh has quit IRC | 23:42 | |
*** [a]mcrn is now known as amcrn | 23:44 | |
*** sarob has quit IRC | 23:44 | |
*** sarob has joined #openstack-meeting-alt | 23:45 | |
*** sarob has quit IRC | 23:49 | |
*** rongze has joined #openstack-meeting-alt | 23:50 | |
*** rnirmal has quit IRC | 23:54 | |
*** rongze has quit IRC | 23:56 | |
*** amytron has joined #openstack-meeting-alt | 23:57 | |
*** yogesh has joined #openstack-meeting-alt | 23:57 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!