Thursday, 2016-06-02

*** Qiming has quit IRC00:00
*** lhcheng has quit IRC00:01
*** zeih has joined #tacker00:11
*** amotoki has joined #tacker00:12
*** arturt_ has quit IRC00:13
*** zeih has quit IRC00:15
*** arturt_ has joined #tacker00:18
openstackgerritMerged openstack/tacker: Fix the typo for 'VimNotFoundException'  https://review.openstack.org/32229600:20
*** arturt_ has quit IRC00:24
*** amotoki has quit IRC00:32
*** arturt_ has joined #tacker00:33
*** sripriya has quit IRC00:41
*** Qiming has joined #tacker01:12
*** amotoki has joined #tacker01:15
*** amotoki_ has joined #tacker01:24
*** amotoki has quit IRC01:26
*** arturt_ has quit IRC01:38
*** zeih has joined #tacker01:39
*** zeih has quit IRC01:43
*** arturt_ has joined #tacker01:50
*** s3wong has quit IRC01:54
*** vishwanathj has joined #tacker02:03
*** zeih has joined #tacker02:06
*** zeih has quit IRC02:11
*** dkushwaha has quit IRC02:19
*** prashantD has quit IRC02:29
*** arturt_ has quit IRC02:33
*** dkushwaha has joined #tacker02:36
*** vishwanathj has quit IRC03:01
*** dkushwaha has quit IRC03:06
*** KanagarajM has joined #tacker03:10
*** sripriya has joined #tacker03:24
*** sripriya has quit IRC03:33
*** sripriya has joined #tacker03:34
*** zeih has joined #tacker03:35
*** dkushwaha has joined #tacker03:36
*** zeih has quit IRC03:39
KanagarajMsripriya, ping03:40
sripriyaKanagarajM: pong03:40
KanagarajMsripriya, for the db optimization, for making some the entry not null, would like to get your opinion03:41
KanagarajMsripriya, https://etherpad.openstack.org/p/tacker-db03:42
KanagarajMsripriya, from line 5203:42
* sripriya looking03:43
*** arturt_ has joined #tacker03:48
sripriyaKanagarajM: the list of changes look fine for me03:50
sripriyaKanagarajM: my concern is for mgmt_driver being not NULL may throw error if mgmt_driver is not specified03:50
KanagarajMsripriya, ok in that case, should we keep mgmt_driver keeps NULL as exist now?03:52
*** arturt_ has quit IRC03:53
*** arturt_ has joined #tacker03:53
sripriyaKanagarajM: or ensure we set it to 'noop' as default in api layer before pushing it to db03:53
sripriyaKanagarajM: https://github.com/openstack/tacker/blob/master/tacker/vm/tosca/utils.py#L24403:53
KanagarajMsripriya, only make vims.tenant_id CAN NOT NULL03:53
KanagarajMdevicetemplates.tenant_id CAN NOT NULL03:53
KanagarajMservicetypes.tenant_id CAN NOT NULL03:53
sripriyaKanagarajM: yup03:54
KanagarajMsripriya, ok i think its good idea, how about the infra_driver?03:54
KanagarajMit should be not null right03:54
sripriyaKanagarajM: which one?03:55
KanagarajMdevicetemplates.infra_driver CAN  NOT NULL03:56
KanagarajMsripriya, ^^03:56
sripriyaKanagarajM: yes, that should be NOT NULL03:57
KanagarajMsripriya, thanks, i will try to put one more patch for this ones.03:59
sripriyaKanagarajM: in fact there is inconsistency in API layer for infra_driver, we set infra_driver as ATTR_NOT_SPECIFIED (which set to default), but then raise an exception if infra driver is not specified at plugin level03:59
KanagarajMsripriya, its evident that infra_driver can't be null ! thanks for pointing out it.04:01
KanagarajMsripriya, do you think setting noop as default value for mgmt_driver would be nice option?04:01
KanagarajMsripriya, in the db schema itself04:01
*** zeih has joined #tacker04:02
*** prashantD has joined #tacker04:02
sripriyaKanagarajM: suppose at any point in future, i want to change the default mgmt_driver, i will have to migrate my db scripts just to update this04:05
*** prashantD_ has joined #tacker04:06
*** zeih has quit IRC04:06
KanagarajMsripriya, we can always override from code i believe, and i assume that noop would be the default one for mgmt_driver , may be for ever :)04:08
*** arturt_ has quit IRC04:09
*** prashantD has quit IRC04:10
sripriyaKanagarajM: may be some providers do not want to have 'noop' at all as default and have their custom driver as default :-)04:12
sripriyaKanagarajM: i think having in db as 'noop04:12
sripriyaKanagarajM: is fine and we can overrride in code at any time04:12
KanagarajMsripriya, yes. that flexibility always we have04:12
sripriyaKanagarajM: cool.04:13
KanagarajMsripriya, i feel, we could do the same for the vims.type SET TO openstack04:13
sripriyaKanagarajM: i don't know if it is a value add to have 'openstack' as default as some providers may not necessarily want 'openstack' vim as default and we force them to override it as default in code. also vim type in api layer is mandatory04:16
*** arturt_ has joined #tacker04:16
KanagarajMsripriya, got your point, that is right. thanks :)04:17
*** arturt_ has quit IRC04:24
*** arturt_ has joined #tacker04:24
*** arturt_ has quit IRC04:27
*** arturt_ has joined #tacker04:27
openstackgerritSripriya Seetharam proposed openstack/tacker: Fix keystone error handling in openstack driver  https://review.openstack.org/32180604:35
*** prashantD_ has quit IRC04:38
*** arturt_ has quit IRC04:44
openstackgerritbharaththiruveedula proposed openstack/tacker: Add monitor feature to the VIM  https://review.openstack.org/31547504:47
*** arturt_ has joined #tacker04:52
*** arturt_ has quit IRC05:04
*** arturt_ has joined #tacker05:05
*** arturt_ has quit IRC05:05
*** arturt_ has joined #tacker05:07
*** arturt_ has quit IRC05:07
*** arturt_ has joined #tacker05:10
*** arturt_ has quit IRC05:15
sridhar_ramsripriya: ping05:17
*** amotoki_ is now known as amotoki05:19
*** zeih has joined #tacker05:30
*** zeih has quit IRC05:35
openstackgerritKanagaraj Manickam proposed openstack/tacker: db schema improvements: openstack entity id set to 64 length  https://review.openstack.org/32369405:55
openstackgerritKanagaraj Manickam proposed openstack/tacker: db schema improvements: set mandatory column not null  https://review.openstack.org/32421905:55
*** zeih has joined #tacker05:57
*** zeih has quit IRC06:02
*** dkushwaha has quit IRC06:04
*** vishnoianil has quit IRC06:10
*** dkushwaha has joined #tacker06:17
sripriyasridhar_ram: pong06:22
*** vishwanathj has joined #tacker07:15
*** vishwana_ has joined #tacker07:15
*** vishwanathj has quit IRC07:19
openstackgerritgongysh proposed openstack/tacker: Change default port into 9898  https://review.openstack.org/32426107:19
*** vishwana_ is now known as vishwanathj07:26
*** vishwanathj has quit IRC07:34
*** zeih has joined #tacker07:35
openstackgerritSantosh Kodicherla proposed openstack/tacker: Adding vnf testcase with monitoring with new tosca template  https://review.openstack.org/30024807:47
*** zeih has quit IRC08:01
*** dkushwaha has quit IRC08:06
*** mbound has joined #tacker08:08
*** vishwanathj has joined #tacker08:14
*** dkushwaha has joined #tacker08:28
*** zeih has joined #tacker08:40
*** mbound has quit IRC08:49
*** zeih has quit IRC08:52
*** dkushwaha has quit IRC08:59
openstackgerritKanagaraj Manickam proposed openstack/tacker: nova infra driver failed to load  https://review.openstack.org/32431909:15
openstackgerritgongysh proposed openstack/tacker: Use oslo log and oslo concurrency  https://review.openstack.org/32432909:41
openstackgerritgongysh proposed openstack/tacker: Use oslo log and oslo concurrency  https://review.openstack.org/32432909:44
openstackgerritgongysh proposed openstack/tacker: Use oslo log and oslo concurrency  https://review.openstack.org/32432909:46
*** zeih has joined #tacker09:51
*** zeih has quit IRC09:56
*** KanagarajM has quit IRC09:57
*** vishwanathj has quit IRC09:57
*** Qiming has quit IRC09:59
*** amotoki has quit IRC10:01
*** amotoki has joined #tacker10:04
*** vishwanathj has joined #tacker10:07
*** vishwanathj has quit IRC10:21
*** amotoki has quit IRC10:37
*** amotoki has joined #tacker10:39
*** fxpester has quit IRC10:46
*** fxpester has joined #tacker10:46
*** Qiming has joined #tacker10:56
*** zeih has joined #tacker10:59
*** amotoki has quit IRC11:07
*** amotoki has joined #tacker11:15
*** amotoki has quit IRC12:11
*** amotoki has joined #tacker12:18
*** amotoki has quit IRC12:18
*** aasmith has joined #tacker12:25
*** tbh has joined #tacker12:34
*** bobh has joined #tacker12:36
*** amotoki has joined #tacker12:36
*** bobh has quit IRC12:41
*** amotoki has quit IRC12:53
*** KanagarajM has joined #tacker13:03
*** mbound has joined #tacker13:11
*** mbound has quit IRC13:13
*** mbound has joined #tacker13:13
*** tbh has quit IRC13:16
*** zeih has quit IRC13:22
*** zeih has joined #tacker13:34
*** twm2016 has joined #tacker14:05
*** bobh has joined #tacker14:13
*** aasmith has quit IRC14:30
*** amotoki has joined #tacker14:35
*** aasmith has joined #tacker14:46
*** zeih has quit IRC14:58
*** aasmith has quit IRC15:00
*** zeih has joined #tacker15:07
*** aasmith has joined #tacker15:08
*** zeih has quit IRC15:11
*** aasmith is now known as tsa-la-gi15:23
*** zeih has joined #tacker15:30
*** zeih has quit IRC15:35
*** prashantD has joined #tacker15:37
*** KanagarajM has quit IRC15:41
*** vishnoianil has joined #tacker15:48
*** tsa-la-gi has quit IRC15:50
*** zeih has joined #tacker15:58
*** uck has joined #tacker16:02
*** zeih has quit IRC16:03
*** tsa-la-gi has joined #tacker16:05
*** KanagarajM has joined #tacker16:07
*** tbh has joined #tacker16:08
*** aasmith has joined #tacker16:09
*** Qiming has quit IRC16:11
*** tsa-la-gi has quit IRC16:11
*** lhcheng has joined #tacker16:13
*** amotoki has quit IRC16:20
*** amotoki has joined #tacker16:22
*** amotoki has quit IRC16:32
*** tbh has quit IRC16:37
*** tbh has joined #tacker16:39
*** s3wong has joined #tacker17:09
*** tbh has quit IRC17:24
*** tbh has joined #tacker17:27
*** sripriya has quit IRC17:28
*** amotoki has joined #tacker17:32
*** amotoki has quit IRC17:38
sridhar_ramtbh: ping17:57
tbhsridhar_ram, Hi17:57
sridhar_ramquick follow up on https://review.openstack.org/#/c/315475/17:58
sridhar_ramtbh: new patchset looks reasonable, only concern is when we have lots of unreachable VIM how does tacker server would perform17:59
sridhar_ramtbh: particularly when a new vim-register happen to arrive in this "window" it will "hang" for a while17:59
tbhsridhar_ram, yes I agree, in the worst case, all the CRUD operations will hold18:00
sridhar_ramtbh: can you characterize the impact by adding few "bad" VIMs and see how long it takes for monitor to come out of the critical section ?18:01
*** sripriya has joined #tacker18:01
sridhar_ramtbh: say, adding 10 invalid VIMs and see the impact18:01
sridhar_ramsripriya: ^^^18:01
tbhsridhar_ram, so I was thinking, I am just reading the values of created_vims and not writing anything18:02
* sripriya catching up18:02
tbhsridhar_ram, sure I will check that18:02
sridhar_ramtbh: bottom line, i'm looking to characterize the situation, so that we can leave a TODO in the code to revisit / enhance this piece18:03
sridhar_ramtbh: .. in a follow on18:03
sridhar_ramtbh: thanks!18:03
sripriyatbh: sridhar_ram: will take a look at the updated patchset18:08
sripriyatbh: i see in code that you are still creating an url connection request to server18:09
sripriyatbh: do you plan to change that?18:09
tbhsripriya, yes18:10
sripriyatbh: ok, just wanted to confirm. thanks.18:10
sridhar_ramtbh: sripriya: fyi, left just more comment as well18:11
sripriyasridhar_ram: ack18:11
tbhsripriya, sure18:12
*** uck has quit IRC18:16
tbhsridhar_ram, actually as in the current version we are taking values from tacker.conf18:16
tbhsripriya suggested to take monitor details from the client18:16
tbhsridhar_ram, so I am trying to have another monitor_drivers folder in nfvo/18:17
sridhar_ramtbh: sorry, which value are we grabbing from tacker.conf ?18:18
tbhand take monitor_type and monitor_action value from the tacker client18:18
tbhsridhar_ram, retry and timeout currently18:19
tbhand we are not taking any monitoring_type value( I mean no modularity)18:19
sridhar_ramtbh: sripriya: why ? I don't think VIM health mon needs to be such a customizable feature .. at least at this point. I'd suggest something simple, as i mentioned earlier a lightweight, lazy health check18:19
tbhsridhar_ram, yeah that's true, but most of the comments raised on this concern,18:21
sridhar_ramtbh: sripriya: we have a TOSCA template policies to describe complicated, customizable monitoring for VNFs & VDUs18:21
tbhi.e, not to just check check network reachability18:21
sripriyasridhar_ram: this won't allow to bring in external agents for vim monitoring18:21
sridhar_ramsripriya: this is something we can delegate to individual VIM type to take inputs from tacker.conf...18:22
sridhar_ramsripriya: we shouldn't push that complexity into vim-register API... we will have only a handful of VIM types..18:22
sridhar_ramsripriya: custom VIM monitoring for a given VIM can still be configured using [vim_foo_monitor_type] in tacker.conf18:23
sripriyasridhar_ram: but this will require us to restart tacker sever in case we want to change the monitor_type for a given VIM18:24
sridhar_ramsripriya: or rather have a [vim_foo] section in the tacker.conf and have monitor_type and monitor_action as settings18:24
sridhar_ramsripriya: yes, the assumption here is introducing new VIMs is usually a s/w upgrade and needs a tacker-server restart18:25
sripriyasridhar_ram: that also implies we will have the same monitoring type for all VIMs18:26
sridhar_ramsripriya: introducing new VIM type is a major event in to a tacker runtime system.. opposed to introducing new VNF moniroting types18:26
sripriyasridhar_ram: i saw 'vim' and 'vnf' as resources that can be configured run time dynamically18:27
sridhar_ramsripriya: no necessarily, openstack VIM might not do more than a simple auth_url ping .. and if it does offer few flavors of it, we can still have this selected using tacker.conf18:27
sripriyasridhar_ram: and that would apply to all VIMs right? the same auth_url ping.18:28
sridhar_ramsripriya: we can let that actual vim driver to implement the "monitor_vim" call .. and they can do what ever they want..18:29
sridhar_ramsripriya: if a particular VIM type has multuple VIM monitoring types.. lets them read that from tacker.conf18:29
sridhar_ramagain, we will *not* have tons of VIM types at any moment in tacker...18:30
sridhar_ramsince this is the first time we are introducing this health mon for VIM, lets do the basic first and see if we get some operator inputs18:31
*** amotoki has joined #tacker18:34
sripriyasridhar_ram: ok, so we need the implementation of reading from tacker.conf and having a custom monitor_vim call which can either call default monitor type or write their own which can listen to some external agent specific for that VIM18:35
sridhar_ramsripriya: exactly !18:36
*** vishnoianil has quit IRC18:38
*** amotoki has quit IRC18:39
sridhar_ramsripriya: monitor_vim call is already VIM specific, correct?18:39
sridhar_ramtbh: ^^18:39
sridhar_ramtbh: sripriya : openstack-driver will have an implementation and another VIM type can have its own ?18:40
tbhsridhar_ram, yup, following the conversation18:43
sridhar_rambobh: can you please review https://review.openstack.org/321806 ? This is the last one holding a point release off stable/mitaka18:43
sripriyasridhar_ram: yes18:45
sridhar_ramsripriya: tbh: okay, we can defer this flexibility to the actual VIM driver implementation..18:46
sridhar_ramsripriya: tbh: do we need to support different monitor_type for openstack VIM driver ?18:47
tbhsridhar_ram, I think we can continue with checking network reachability for now18:51
sridhar_ramtbh: okay.. i'll let you and sripriya make the right call on that. however, IMO, we should keep this initial vim health implementation simple and let it evolve in iterations in the future.18:53
sripriyasridhar_ram: tbh: agree. we can enhance it in follow ons19:02
*** KanagarajM has quit IRC19:20
*** amotoki has joined #tacker19:34
*** zeih has joined #tacker19:35
*** amotoki has quit IRC19:39
*** openstack has joined #tacker19:43
*** uck has joined #tacker19:48
*** mbound has quit IRC19:53
*** uck has quit IRC19:53
*** uck_ has joined #tacker19:53
*** zeih has joined #tacker20:03
openstackgerritMerged openstack/tacker: Fix keystone error handling in openstack driver  https://review.openstack.org/32180620:04
*** zeih has quit IRC20:07
*** tbh has quit IRC20:13
*** uck has joined #tacker20:32
*** uck_ has quit IRC20:32
*** amotoki has joined #tacker20:35
*** vishnoianil has joined #tacker20:36
*** amotoki has quit IRC20:40
*** santoshk has joined #tacker20:43
*** mbound has joined #tacker20:53
*** mbound has quit IRC20:58
*** aasmith has quit IRC21:04
*** prashantD_ has joined #tacker21:13
*** prashantD has quit IRC21:16
*** prashantD has joined #tacker21:17
*** prashantD_ has quit IRC21:19
*** amotoki has joined #tacker21:36
*** amotoki has quit IRC21:42
*** prashantD_ has joined #tacker21:56
*** prashantD has quit IRC21:59
*** twm2016 has quit IRC22:06
*** openstackgerrit has quit IRC22:19
*** openstackgerrit has joined #tacker22:20
*** bobh has quit IRC22:22
*** arturt_ has joined #tacker22:36
*** arturt_ has quit IRC22:37
*** arturt_ has joined #tacker22:50
*** vishnoianil has quit IRC23:07
*** Qiming has joined #tacker23:09
*** lhcheng has quit IRC23:22
*** sripriya_ has joined #tacker23:23
*** sripriya has quit IRC23:26
*** aasmith has joined #tacker23:30
*** amotoki has joined #tacker23:39
*** Qiming has quit IRC23:40
*** amotoki has quit IRC23:44
*** vishwanathj has joined #tacker23:49

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