Wednesday, 2017-04-19

*** uck has joined #tacker00:17
*** Aqsa has quit IRC00:19
*** uck has quit IRC00:21
*** amotoki has quit IRC00:45
*** amotoki has joined #tacker00:50
*** amotoki has quit IRC00:59
*** amotoki has joined #tacker01:14
*** s3wong has quit IRC01:17
*** gongysh has joined #tacker01:54
*** openstackgerrit has joined #tacker02:31
openstackgerritgongysh proposed openstack/tacker master: Refactor mistral workflow to lay foundation for monitor to use it  https://review.openstack.org/45784302:31
openstackgerritgongysh proposed openstack/tacker master: Refactor mistral workflow to lay foundation for monitor to use it  https://review.openstack.org/45784302:32
*** amotoki has quit IRC02:35
*** tung_doan has joined #tacker02:37
*** amotoki has joined #tacker02:50
*** amotoki has quit IRC03:15
openstackgerritgongysh proposed openstack/tacker master: VIM reachable monitoring via mistral workflow  https://review.openstack.org/45714003:18
*** links has joined #tacker03:19
openstackgerritYan Xing an proposed openstack/tacker-specs master: encrypt vim credentials with barbican  https://review.openstack.org/44554303:24
*** amotoki has joined #tacker03:35
openstackgerritgongysh proposed openstack/tacker master: Refactor mistral workflow to lay foundation for monitor to use it  https://review.openstack.org/45784303:37
openstackgerritgongysh proposed openstack/tacker master: Make vim test config file aware of devstack keystone setting  https://review.openstack.org/45785203:46
*** KanagarajM has joined #tacker03:54
*** gongysh has quit IRC03:56
*** amotoki_ has joined #tacker03:58
*** amotoki has quit IRC04:00
*** amotoki_ has quit IRC04:06
*** amotoki has joined #tacker04:19
*** trinaths has joined #tacker04:20
*** tbh has joined #tacker04:33
*** diga has joined #tacker04:34
*** links has quit IRC04:36
*** links has joined #tacker04:52
*** gongysh has joined #tacker05:01
*** janki has joined #tacker05:22
*** thebling has joined #tacker05:22
*** amotoki_ has joined #tacker05:23
*** links has quit IRC05:25
*** amotoki has quit IRC05:26
*** YanXing_an has joined #tacker05:31
*** nmathew has joined #tacker05:36
*** links has joined #tacker05:37
theblingjoin openstack-telemetry06:28
*** sanjay_ has joined #tacker06:29
*** janki has quit IRC06:30
sridhar_ramthebling: may i ask why? :)06:35
gongyshtrinaths, hi06:37
gongyshsridhar_ram, http://lists.openstack.org/pipermail/openstack-dev/2017-April/115568.html06:37
gongyshwhat do you mean by: http://lists.openstack.org/pipermail/openstack-dev/2017-April/115568.html?06:37
sridhar_ramgongysh: i was just pointing out the ML discussion06:38
sridhar_ram.. with latest suggestions06:38
gongyshsorry, I mean the text in this email: I agree 'nfv' is an umbrella term and it has significance for other06:38
gongyshprojects as well (like nova).06:38
gongyshsignificance for other projects as well ( like nova)?06:39
gongyshI just quite understand it.06:39
*** mohankumar has joined #tacker06:41
sanjay_Hi Sridhar and Team, I am new to to tacker and want to contribute. Please suggest me how to start06:42
sridhar_ram you might know this, lots of nfv related features were worked on by different projects like nova (sr-iov, EPA, ..)  .. i was just referring that06:42
gongyshsridhar_ram, ?06:42
sridhar_ramgongysh: still unclear ?06:43
sridhar_ramsanjay_: welcome to the tacker project! gongysh is the current PTL ... he has lined up tons of interesting items to work on06:44
gongyshthat is what NFV is demanding on these projects.06:45
sridhar_ramsanjay_: i'd suggest you start picking up some simple bugs .. https://bugs.launchpad.net/tacker/06:45
sanjay_Thanks. Ok. I will start looking intoit06:45
trinathsgongysh: hi06:46
gongyshthe NFV output on openstack community should be tacker.06:46
sridhar_ramgongysh: i guess the general concern is .. tacker is just an orchestration project and it can't take up the whole 'nfv' namespace .. as this first level namespace belongs to the whole openstack project family.06:46
sridhar_ramNo.. tacker is just the orchestration component of openstack's NFV offering .. atleast that is the argument06:47
trinathssanjay_: Hi, Welcome to Tacker project. Start your contribution by fixing something here, at https://bugs.launchpad.net/python-tackerclient06:47
*** nmathew- has joined #tacker06:47
gongyshsridhar_ram, in fact no one is objecting to use nfv from other projects.06:47
gongyshsince there is no organization to arrange the first level namespace,  we can use it anyway.06:48
trinathsgongysh: but NFV is a very broad umberella. where NFVI, VNFs, NFVO, VNFM and OSS/BSS fit into it.06:49
sanjay_Sure trinaths06:49
*** janki has joined #tacker06:49
gongyshyes, right. so take the broader one if narrow one cannot contain it.06:50
sridhar_rami'm not sure about the full review process for OSC .. ML email is the general good first step.. we need to reach out to atleast anne gentle to get more eyes on this06:50
*** YanXingan has joined #tacker06:51
*** nmathew has quit IRC06:51
gongyshsridhar_ram, we can do first one our side. if there is big objection, we can change.06:51
sridhar_ramone reason 'vnf' keyword grew on me is it make the CLI concise ..06:51
gongyshanne gentle is not the one to review the namespace.06:52
*** Aqsa has joined #tacker06:52
sridhar_ram'openstack vnf create' vs 'openstack nfv vnf create'06:52
sridhar_rami like the first more .. more concise and easy to understand06:52
*** YanXing_an has quit IRC06:52
sridhar_ramthe problem comes only for "network-service"06:52
sridhar_ramthere is no easy choice .. imo06:53
sridhar_ramof the choices .. i prefer 'vnf' as it keeps the CLI family consistent06:53
openstackgerritdharmendra kushwaha proposed openstack/tacker master: Adds unique constraint on deleted_at  https://review.openstack.org/45542106:53
trinathsgongysh: Choosing broader one is a good choice, But we dont do NFVI directly. We rely on Openstack projects for that.06:53
gongyshtrinaths, there is no one will have nfvi command.06:54
trinathsgongysh: perfectly agree06:54
gongyshthere is no nfvi command.06:54
trinathsgongysh: agree. my comment above is w.r.t broader view.06:55
gongyshKanagarajM, dkushwaha ,  could you please give your comments?06:56
gongyshtbh,  please.06:56
tbhgongysh, I haven't gone through complete ML discussion, but imo though nfv is broader term tacker can fit into some of the functionalities06:58
tbhand for nfv orchestration I don't think there is no other project is doing that06:58
gongyshtrinaths, it is not a P1 job.06:59
tbhmany other projects like nova though facilitating "nfv" features but is there any API they are exposing?06:59
gongyshwe can hold it for a while.06:59
trinathsgongysh: +1 , agree.06:59
sridhar_ramgongysh: can you reply to the ML w/ your views ?06:59
gongyshsridhar_ram, sometimes, we can decide it on our own.06:59
gongyshsince you have sent out email, and get some ideas on it.  we can do some decision.07:01
tbhgongysh, sridhar_ram very basic question, is there any limitation for openstack x y(like openstack user list), does x also refer to single openstack project?07:02
tbhs/also/always07:03
gongyshtbh,  I don't think so.07:03
sridhar_ramhere are some data points .. for all your thoughts .. there are commands like 'openstack router create', 'openstack port create' and 'openstack network create'  .. all these are coming from one Neutron project. They are all *not* hiding under one top-level keyword like 'openstack network port create' , 'openstack network router create' ...  this is were we07:03
sridhar_ramneed to switch out of Tacker project and think at openstack "product" level and decide things that make sense for OpenStack ..07:03
tbhsridhar_ram, yes, makes sense07:05
* sridhar_ram is going to doze off soon ...07:05
gongyshthere is one point with network-service named vnf service. but I cannot come up with better way to do it.07:07
trinathsgongysh: else, we can have $> openstack nfv|vfn network service create|delete07:09
gongyshtrinaths, also vnf event list,  here the 'vnf' is becoming a prefix.07:10
gongyshvnf create, here, vnf is a nfv term: vnf.07:10
sridhar_ram'network-service' is the main hurdle ..07:10
trinathsotherwise, can we split this way, VNFM and NFVO commands07:10
gongyshsridhar_ram,  a confustion. sometimes 'vnf' is a prefix, sometimes, it is a term.07:11
trinaths$> openstack vnfm vnf create07:11
trinaths$> openstack nfvo network service create07:11
sridhar_ramfor osc is always a term .. given no hyphens are allowed07:11
sridhar_ramtrinaths: no.. bad, bad idea to expose s/w components in CLIs / APIs07:12
trinathssridhar_ram: sorry. my mistake.07:12
trinathssridhar_ram: I thought we are exposing capabilites from tacker.07:13
sridhar_ramtrinaths: no problem.. these are good suggestions.. ideate as much as possible07:13
trinathssridhar_ram: ok07:13
trinathsokay. now how we go with OSC commands ?07:14
sridhar_ramgongysh: think about it .. as you said we have some time but i'm trinaths would rather like this wrapped up soon... given we are already in the thick of it..07:15
sridhar_ramfolks - sorry, got to sign off now07:16
gongyshsridhar_ram, good night07:16
sridhar_ramgongysh: thanks..07:16
dkushwahasridhar_ram, gongysh, tbh sorry I missed discussion. Can we use some other term for network-service? I07:17
trinathssridhar_ram: good night07:17
gongyshdkushwaha, tbh https://review.openstack.org/#/c/455188/15/specs/pike/python-openstackclient.rst07:18
gongyshyou can put comments on this patch07:18
tbhsure07:19
dkushwahagongysh, sure07:19
trinathsgongysh: thanks for this valuable discussion. it was more informative moving forward to adopt osc.07:23
*** trinaths is now known as trinaths_at_lunc07:26
*** trinaths_at_lunc is now known as trinaths_lunch07:26
gongyshdkushwaha, https://review.openstack.org/#/c/448466/07:26
gongyshcould you please have a look at this patch?07:27
*** trinaths_lunch is now known as trinaths07:50
trinathsgongysh:07:50
trinathsgongysh: ping07:50
trinathsgongysh: https://review.openstack.org/#/c/455188/15/specs/pike/python-openstackclient.rst , its okay to have  $> openstack nfv service create                   compared to              $>openstack nfv network service create ??07:51
openstackgerritTrinath Somanchi proposed openstack/tacker-specs master: Tacker support in python-openstackclient  https://review.openstack.org/45518807:53
dkushwahagongysh, sure07:55
*** amotoki_ has quit IRC08:22
openstackgerritRajat Sharma proposed openstack/tacker master: Fix doc generation for Python3  https://review.openstack.org/45792108:25
*** thebling has quit IRC08:26
*** YanXing_an has joined #tacker08:35
*** YanXingan has quit IRC08:38
*** janki has quit IRC08:41
*** janki has joined #tacker08:49
*** janki has quit IRC08:56
*** janki has joined #tacker08:57
*** Aqsa has quit IRC09:05
*** Aqsa has joined #tacker09:07
*** amotoki has joined #tacker09:29
openstackgerritStephen Finucane proposed openstack/python-tackerclient master: Explicitly set 'builders' option  https://review.openstack.org/45796409:31
*** amotoki has quit IRC09:45
openstackgerritStephen Finucane proposed openstack/python-tackerclient master: Use Sphinx 1.5 warning-is-error  https://review.openstack.org/45797809:46
*** YanXing_an has quit IRC09:57
*** amotoki has joined #tacker09:58
*** janki has quit IRC10:05
*** janki has joined #tacker10:16
gongyshdkushwaha, hi10:19
gongyshKanagarajM hi10:21
gongyshtbh hi10:21
*** janki has quit IRC10:37
*** janki has joined #tacker10:37
dkushwahagongysh, hi10:40
gongyshdkushwaha, https://review.openstack.org/#/c/448466/10:41
gongyshalthough this patch does not fix all problem, but it definetely improve the robustness.10:41
*** janki has quit IRC10:41
gongyshalso at line 130 of https://review.openstack.org/#/c/448466/5/tacker/vnfm/infra_drivers/openstack/openstack.py10:42
gongyshwe already have a heatclient.get(vnf_id)10:42
gongyshso the exceptions should be temp connection exception most of time.10:43
dkushwahagongysh, Actually my point is, with this fix we un-necessary needs to wait, even if we have actual failure. Otherwise rest looks fine10:43
dkushwahatbh, KanagarajM any thought on this?10:44
gongyshI know that. you see at line 130, most of non connection error will be happen there.10:44
dkushwahagongysh, make sense. I Think we can merge this patch, and rest improvements can be done later stage.10:48
gongyshthanks10:49
*** janki has joined #tacker10:50
*** janki has quit IRC10:53
*** Vijayendra has quit IRC10:56
openstackgerritMerged openstack/tacker master: Continue waiting to avoid temporary connection error with target VIM  https://review.openstack.org/44846610:59
*** dmk0202 has joined #tacker11:02
openstackgerritdharmendra kushwaha proposed openstack/tacker master: Adds unique constraint on deleted_at  https://review.openstack.org/45542111:13
*** janki has joined #tacker11:17
*** dmk0202 has quit IRC11:21
*** dmk0202 has joined #tacker11:21
*** dkushwaha has left #tacker11:21
*** gongysh has quit IRC11:35
*** trinaths has left #tacker11:45
*** sanjay_ has quit IRC11:45
*** nmathew- has quit IRC11:48
*** amotoki has quit IRC11:50
*** amotoki has joined #tacker11:57
*** amotoki has quit IRC12:02
*** diga has quit IRC12:11
*** trinaths has joined #tacker12:35
*** gongysh has joined #tacker12:41
*** mohankumar has quit IRC12:52
*** trinaths has left #tacker12:54
*** nmathew- has joined #tacker12:57
*** nmathew- has quit IRC12:57
*** Aqsam has joined #tacker13:05
*** trinaths has joined #tacker13:07
*** Aqsa has quit IRC13:08
*** jamesdenton has joined #tacker13:11
*** jamesdenton has quit IRC13:24
*** jamesdenton has joined #tacker13:25
*** mohankumar has joined #tacker13:47
openstackgerritgongysh proposed openstack/tacker master: Make vim test config file aware of devstack keystone setting  https://review.openstack.org/45785213:54
openstackgerritMerged openstack/tacker-specs master: encrypt vim credentials with barbican  https://review.openstack.org/44554313:54
openstackgerritgongysh proposed openstack/tacker master: Make vim test config file aware of devstack keystone setting  https://review.openstack.org/45785214:00
*** links has quit IRC14:02
*** janki has quit IRC14:06
*** tung_doan_ has joined #tacker14:12
*** haiwei has quit IRC14:13
*** tung_doan has quit IRC14:13
*** amotoki has joined #tacker14:14
*** amotoki has quit IRC14:15
*** KanagarajM has quit IRC14:29
*** tbh has quit IRC14:34
*** amotoki has joined #tacker14:40
*** trinaths has left #tacker14:41
*** mohankumar has quit IRC15:05
openstackgerritOpenStack Proposal Bot proposed openstack/tacker master: Updated from global requirements  https://review.openstack.org/45602415:18
*** amotoki has quit IRC15:19
*** jamesdenton has quit IRC15:19
*** bobh has joined #tacker15:31
*** bobh has quit IRC15:36
*** bobh has joined #tacker15:38
*** uck has joined #tacker15:52
*** dmk0202 has quit IRC16:09
*** Aqsam has quit IRC16:11
*** gongysh has quit IRC16:22
*** amotoki has joined #tacker16:54
*** uck has quit IRC17:05
*** vishnoianil has quit IRC17:11
*** 17WAAQLLM has joined #tacker17:40
*** jamesden_ has joined #tacker17:59
*** vishnoianil has joined #tacker18:04
*** 17WAAQLLM has quit IRC18:07
*** uck has joined #tacker18:07
*** bobh has quit IRC18:13
*** amotoki has quit IRC18:30
*** Aqsam has joined #tacker19:04
*** bobh has joined #tacker19:14
*** bobh has quit IRC19:19
*** uck_ has joined #tacker19:34
*** uck has quit IRC19:34
*** Aqsam has quit IRC19:47
*** dmk0202 has joined #tacker19:47
*** bobh has joined #tacker20:15
*** bobh has quit IRC20:20
*** uck_ has quit IRC20:40
*** s3wong has joined #tacker20:59
*** bobh has joined #tacker21:16
*** bobh has quit IRC21:21
*** uck has joined #tacker21:40
*** uck has quit IRC21:45
*** jamesden_ has quit IRC22:03
*** bobh has joined #tacker22:17
*** dmk0202 has quit IRC22:17
*** bobh has quit IRC22:24
*** gongysh has joined #tacker22:38
*** gongysh has quit IRC22:40
openstackgerritgongysh proposed openstack/tacker master: Make vim test config file aware of devstack keystone setting  https://review.openstack.org/45785222:43
*** jamesden_ has joined #tacker22:59
*** jamesden_ has quit IRC23:33
*** uck has joined #tacker23:42
*** uck has quit IRC23:47

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