Friday, 2016-09-09

*** sripriya has quit IRC00:01
openstackgerritvishwanath jayaraman proposed openstack/tacker: Move functional tests from commonservices directory  https://review.openstack.org/36769700:06
*** sripriya has joined #tacker00:07
*** diga has joined #tacker00:07
*** vishwanathj is now known as vishwanathj_zzz00:08
*** vishwanathj_zzz is now known as vishwanathj_00:08
*** KanagarajM_ has joined #tacker00:10
*** KanagarajM has quit IRC00:10
digatrozet:00:12
digatrozet: Hi00:13
*** uck has quit IRC00:15
bryan_attsridhar_ram: any way to inject an SSH key into a VM via the template? I tried using the "key_name" property but the mitaka/stable version appears not to support that.00:18
sridhar_rambryan_att: unfortunately that went in Newton as well :(00:18
bryan_attsridhar_ram: how were you able to do anything with VMs if you couldn't SSH to them? (at least with normal cloud images which have password SSH disabled)00:19
bryan_attI guess you were creating custom images for testing?00:20
sridhar_ramsripriya: qq, would a newton tacker + mitaka keystone work from vim-register point of view ?00:20
sridhar_rambryan_att: many vnfs we tried support restapi, CLI and netconf00:21
bryan_attsridhar_ram: OK, let me see what I can find in the meantime, or I can customize an ubuntu server so I can log into it. I need SSH so that I can push setup scripts.00:22
sripriyasridhar_ram: d you mean registerting an openstack mitaka vim?00:23
sripriyasridhar_ram: or to run tacker tacker service itself?00:24
*** uck has joined #tacker00:24
*** uck has quit IRC00:29
sridhar_rambryan_att: Ok... we also want to cover blank vm + vnfc s/w option (like ur vIMS).. hence we started adding ssh key, secgroup, etc in the newer release00:41
bryan_attsridhar_ram: OK, I'll get there soon enough. Next OPNFV release will be Newton based. In the meantime I'll figure it out.00:41
sridhar_ramsripriya: is later feasible?00:42
sripriyasridhar_ram: i dont think so, with common packages (oslo, middleware, etc.) used across multiple services, version incompatibility will cause problems for tacker newton to be installed with mitaka services00:45
*** gongysh has quit IRC00:45
*** sripriya has quit IRC00:46
openstackgerritdharmendra kushwaha proposed openstack/python-tackerclient: Add support for multi delete  https://review.openstack.org/34980600:46
sridhar_ramsripriya: thought so, was trying to be greedy :)00:47
sridhar_ramsripriya: however newton tacker connecting to mitaka OpenStack would be supported...we shd point check this00:47
*** gongysh has joined #tacker01:11
*** KanagarajM_ has quit IRC01:13
*** KanagarajM has joined #tacker01:13
*** gongysh has quit IRC01:41
*** dkushwaha__ has joined #tacker01:41
*** s3wong has quit IRC01:48
*** gongysh has joined #tacker02:01
*** diga has quit IRC02:32
*** dkushwaha__ has quit IRC02:38
*** amotoki has quit IRC02:49
*** vishnoianil has quit IRC02:52
*** amotoki has joined #tacker03:49
*** achatterjee has joined #tacker03:55
*** amotoki has quit IRC04:16
*** Vijayendra has joined #tacker04:21
*** tbh has joined #tacker05:05
*** neel has joined #tacker05:13
openstackgerritMerged openstack/tacker-horizon: Adds audit support for VNF, VIM and VNFD resources  https://review.openstack.org/34975505:17
*** janki has joined #tacker05:21
*** lulei has quit IRC05:22
*** sripriya has joined #tacker05:23
openstackgerritdharmendra kushwaha proposed openstack/python-tackerclient: Add support for multi delete  https://review.openstack.org/34980605:27
*** vishwanathj_ is now known as vishwanathj_zzz05:28
dkushwahagongysh, ping05:36
dkushwahagongysh, please check my response on https://review.openstack.org/#/c/346557/05:36
*** kvmahesh has joined #tacker05:38
*** Ravikiran_K has joined #tacker05:41
*** amotoki has joined #tacker05:43
*** kvmahesh has quit IRC05:49
*** santoshk has joined #tacker05:56
santoshkKanagarajM, Hi05:56
*** vishnoianil has joined #tacker06:06
*** amotoki has quit IRC06:19
*** veena_ has joined #tacker06:20
openstackgerritMerged openstack/python-tackerclient: Add support for multi delete  https://review.openstack.org/34980606:28
*** amotoki has joined #tacker06:28
*** sripriya has quit IRC06:46
*** amotoki has quit IRC06:48
jankitung_doan, ping06:48
*** KanagarajM has quit IRC06:49
*** KanagarajM has joined #tacker06:49
*** amotoki has joined #tacker06:52
*** santoshk has quit IRC06:56
*** amotoki has quit IRC07:02
*** amotoki has joined #tacker07:14
*** veena_ has quit IRC07:22
*** tung_doan has quit IRC07:32
*** vishwana_ has joined #tacker07:42
*** vishwana_ has quit IRC07:42
*** vishwana_ has joined #tacker07:43
*** neel has quit IRC07:43
*** vishwanathj_zzz has quit IRC07:44
*** KanagarajM_ has joined #tacker07:53
*** KanagarajM has quit IRC07:53
*** mbound has joined #tacker07:54
*** mbound has quit IRC07:59
openstackgerritJiWei proposed openstack/tacker: Fix order of arguments in assertIs  https://review.openstack.org/36781208:14
*** tung_doan has joined #tacker08:15
tung_doanjanki: pong08:16
jankitung_doan, hey, I tried to solve that password issue08:20
tung_doanjanki: oh.. nice.. i already had a way to fix.. but it's great to hear from you08:21
jankitung_doan, ohh cool :)08:21
tung_doanjanki: really want to know your solution.. appreciate it08:24
jankitung_doan, I did it os module.08:24
jankitung_doan, how about you?08:24
*** vishwana_ has quit IRC08:25
*** vishwanathj_zzz has joined #tacker08:25
tung_doanjanki: i still used username-password method.. but we dont need to hard-code them08:26
jankitung_doan, I did like this http://pastebin.com/LqYuXb73. Yours?08:27
tung_doanI just save username and pass in tacker.conf. but didnot try it.. did it work ok?08:30
tung_doanjanki: with your changes08:31
*** lulei has joined #tacker08:39
jankitung_doan, yes, my changes work okay08:40
jankitung_doan, share your changes. I will try08:41
*** neel has joined #tacker08:46
*** KanagarajM has joined #tacker08:47
*** KanagarajM_ has quit IRC08:49
*** KanagarajM_ has joined #tacker08:51
*** KanagarajM has quit IRC08:54
*** amotoki has quit IRC09:04
*** mfedosin has joined #tacker09:06
*** mbound has joined #tacker09:14
*** tbh has quit IRC09:22
*** KanagarajM__ has joined #tacker09:29
*** KanagarajM_ has quit IRC09:33
*** neel has quit IRC09:41
*** Vijayendra has quit IRC09:48
*** Vijayendra has joined #tacker09:48
openstackgerritTung Doan proposed openstack/tacker: Alarm monitor: All in one  https://review.openstack.org/36543510:27
*** neel has joined #tacker10:30
*** tung_doan is now known as tung_doan_afk10:32
*** mfedosin has quit IRC10:34
*** mfedosin has joined #tacker10:36
*** neel has quit IRC10:56
*** tbh has joined #tacker10:59
*** lulei has quit IRC11:00
*** mfedosin has quit IRC11:05
*** tung_doan_afk is now known as tung_doan11:21
*** KanagarajM__ has quit IRC11:23
openstackgerritdharmendra kushwaha proposed openstack/tacker: Cleanup unused file hooks.py  https://review.openstack.org/36795311:31
*** dkushwaha has quit IRC11:33
*** Vijayendra has quit IRC11:48
*** gongysh has quit IRC12:00
*** mfedosin has joined #tacker12:12
*** bobh has joined #tacker12:19
*** bobh has quit IRC12:30
*** mfedosin has quit IRC12:36
*** mfedosin has joined #tacker12:44
*** tung_doan is now known as tung_doan_afk12:58
*** gongysh has joined #tacker13:11
trozetsridhar_ram: ping?13:48
trozetgongysh: ping?13:51
openstackgerritJanki Chhatbar proposed openstack/tacker: Alarm monitor: All in one  https://review.openstack.org/36543513:56
openstackgerritJanki Chhatbar proposed openstack/tacker: Alarm monitor: All in one  https://review.openstack.org/36543513:57
*** bobh has joined #tacker14:01
*** mfedosin has quit IRC14:02
*** mfedosin has joined #tacker14:04
openstackgerritJanki Chhatbar proposed openstack/tacker: Alarm monitor: All in one  https://review.openstack.org/36543514:06
*** bobh has quit IRC14:06
*** janki has quit IRC14:07
*** bobh has joined #tacker14:14
*** tamilhce has joined #tacker14:58
*** tamilhce has quit IRC15:02
*** tung_doan_afk is now known as tung_doan15:09
*** tbh_ has joined #tacker15:09
tung_doangonggysh: ping15:09
*** tbh_ has quit IRC15:09
*** gongysh has quit IRC15:13
openstackgerritbharaththiruveedula proposed openstack/tacker-specs: Tacker VNFC support  https://review.openstack.org/33979815:14
*** mbound has quit IRC15:22
*** vishwanathj_zzz is now known as vishwanath15:27
*** vishwanath is now known as vishwanathj15:27
*** amotoki has joined #tacker15:27
*** gongysh has joined #tacker15:30
*** uck has joined #tacker15:44
*** yifei has quit IRC15:48
*** openstackgerrit has quit IRC15:49
*** openstackgerrit has joined #tacker15:50
-openstackstatus- NOTICE: New setuptools release appears to have a circular import which is breaking many jobs - check for ImportError: cannot import name monkey.15:55
*** ChanServ changes topic to "New setuptools release appears to have a circular import which is breaking many jobs - check for ImportError: cannot import name monkey."15:55
*** amotoki_ has joined #tacker16:02
*** gongysh has quit IRC16:03
*** amotoki_ has quit IRC16:03
*** amotoki has quit IRC16:05
*** mbound has joined #tacker16:22
*** mbound has quit IRC16:28
*** janki has joined #tacker16:42
*** yifei has joined #tacker16:46
*** ChanServ changes topic to "Discussion on OpenStack NFV Orchestration | Docs @ http://docs.openstack.org/developer/tacker/ | Wiki @ https://wiki.openstack.org/wiki/Tacker | Logged @ http://eavesdrop.openstack.org/irclogs/%23tacker/"16:59
-openstackstatus- NOTICE: setuptools 27.1.2 addresses the circular import16:59
*** uck has quit IRC17:09
*** yifei has quit IRC17:10
*** vishnoianil has quit IRC17:22
*** janki has quit IRC17:30
*** sripriya has joined #tacker17:30
sridhar_ramtrozet: pong17:39
*** tbh has quit IRC17:47
openstackgerritMerged openstack/python-tackerclient: Removing test cases for already removed methods  https://review.openstack.org/36102717:47
*** uck has joined #tacker17:49
*** mfedosin has quit IRC17:51
*** prashantD has joined #tacker17:55
trozetsridhar_ram: i'm trying to test everything together on my setup17:59
trozetsridhar_ram: but the register vim part is new to me17:59
trozetmight have questions17:59
*** s3wong has joined #tacker18:01
trozetsripriya: ping?18:03
sridhar_ramtrozet: sure Tim. I'm point checking the feature as well..18:10
trozetsridhar_ram: ok i was just able to create the VIM, i guess it's working...it says "REACHABLE"18:11
sridhar_ramtrozet: perfect, that's good18:11
trozetsridhar_ram: i wasnt sure what domain name was in the vim.conf...i just put the region for keystone18:11
sridhar_ramtrozet: btw, left few minor comments in the patchset18:12
trozetsridhar_ram: yeah saw that, thanks18:12
*** vishnoianil has joined #tacker18:15
*** sripriya has quit IRC18:16
trozetsridhar_ram: ok able to try to create VNFFG now, hit a bug already :)18:17
sridhar_ramtrozet: finding bugs at this stage is absolute goodness :)18:19
trozetsridhar_ram: haha yeah looks like i forgot to do a try/exception18:20
sridhar_ramtrozet: I see18:21
trozetsridhar_ram: actually there is some kind of bug in my filter18:29
trozetsridhar_ram: vnfm_plugin.get_vnfds(context, {'name': vnfd}, fields=['id'])18:30
trozetsridhar_ram: for filters (2nd arg) is that the correct way to write it?18:30
trozetsridhar_ram: oh crap, the vnfd needs to be in a list18:45
*** uck_ has joined #tacker18:49
*** uck has quit IRC18:49
tung_doansridhar_ram: ping19:26
*** sripriya has joined #tacker19:28
sripriyatrozet: pong19:28
trozethey sripriya19:28
trozetsripriya: was asking earlier about registering a VIM, but figured it out with an example from unit test19:29
sripriyatrozet: cool, continuing to review your patch19:29
trozetsripriya: good19:31
trozetsripriya: i'm testing the whole thing now in a full openstack setup19:31
trozetsripriya: already hit a few bugs19:31
sripriyatrozet: nice, on which distro?19:31
trozetsripriya: stable/mitaka19:31
sripriyatrozet: mitaka?19:32
trozetsripriya: i remember sridhar_ram emailing about refactoring vnfm and some changes there.  Do you know off hand if the VNF DB was changed from template_id to vnfd_id?19:32
sripriyatrzoet: yes it was refactored19:32
sridhar_ramtung_doan: pong19:33
trozetsripriya: ok, my code is trying to filter for template_id19:33
trozetsripriya: so thats probably why things are breaking19:33
sripriyatrozet: ^19:33
sripriyatrozet: i saw that yest. and wondered how it was working19:33
trozetsripriya: well in unit tests i mock the VNFM19:33
trozetsripriya: so tahts why those pass19:34
tung_doansridhar_ram: Hi sridhar, actually next week is mid-autumn festival in Korea. Therefore, my work should be finished until 14th Sept.19:34
sripriyatrozet: hmm that needs to be fixed too then19:34
tung_doanCurrently, gonggysh and Janki are helping me to review my patch... Hope we can wrap this patch soon...19:34
trozetsripriya: yeah need to change that to vnfd_Id19:34
sripriyatrozet: cool19:34
sripriyatrozet: on my earlier question, why mitaka?19:34
trozetsripriya: thats what my OPNFV installer uses19:35
trozetsripriya: not using devstack19:35
sripriyatrozet: the networking-sfc doesnt work on newton?19:35
trozetsripriya: no i just know this setup, and its dependable so I can be sure the rest of the stuff works19:35
sripriyatrozet: sorry need some context, so you integrated your code to work with tacker mitaka then?19:36
trozetsripriya: no , i just installed tacker off my patch in master19:37
trozetsripriya: the rest of openstack is stable/mitaka19:37
sripriyatrozet: are all installed on the same system?19:38
trozetsripriya: well its 3 nodes, 1 controller, and 2 computes19:38
trozetbut yeah19:38
sripriyatrozet: and you register the openstack instance as a vim and deploy vnffg19:39
trozetsripriya: yeah, after i created 2 VNFs19:39
sripriyatrozet: i’m surprized you did not run into issues with common packages versions between  tacker master and mitaka openstack services19:40
trozetsripriya: yeah it seems ok19:40
sripriyatrozet: ah ok good to know,19:41
sripriyasridhar_ram: your ask yest. of tacker newton with openstack mitaka keystone works as per trozet.19:41
sripriyatrozet: one last question which linux distro are you using?19:42
trozetsripriya: centos ftw!19:47
trozetsridhar_ram, sripriya: btw the vnf resource list stuff works, even with client-> server :)19:47
sripriyatrozet: nice!19:48
*** uck_ has quit IRC19:55
trozetsripriya: VimInUseException: VIM e62b2468-6377-4a87-8d68-4cfcf39e1bdb is still in use by VNF20:01
sripriyatrozet: are you trying to delete a VIM?20:02
trozetsripriya: that is returned when i do get_vim()?20:02
sripriyatrozet: no20:02
trozetsripriya: https://paste.fedoraproject.org/425000/raw/20:03
trozet    def _get_vim(self, context, vim_id):20:03
trozet        if not self.is_vim_still_in_use(context, vim_id):20:03
trozet            return self.get_vim(context, vim_id)20:03
trozetsripriya: is that intentional? or a bug?20:06
sripriyatrozet: that is used internally by update_vim for updating vim only when vnf is not deployed on it20:07
trozetsripriya: ah i should use get_vim not _get_vim20:07
sripriyatrzoet: in your code you need to be using the get_vim call instead of _get_vim20:07
trozetok easy fix20:07
sripriyatrozet: may be that method name should be different insted of _get_vim20:08
trozetsripriya: yeah20:08
sridhar_ramtung_doan: act, let's wrap up bef Sept 14th20:09
sridhar_ramtung_doan: *ack20:09
tung_doanI will spend the rest of this week and several days next week to fix and enhance code... so if possible, please help me to review20:09
trozetsridhar_ram, sripriya: huzzah! https://paste.fedoraproject.org/425007/20:09
trozet(note this is without the networking-sfc driver, im just generating UUID for driver call)20:10
sridhar_ramtung_doan: will help w/ reviews20:10
sripriyatrozet: super awesome20:10
sridhar_ramtrozet: woot!20:10
sridhar_ramtrozet: the uuids in vnf_mapping maps to existing active VNFs ?20:11
trozet| a8d3f96f-d34a-404c-a552-f0ec13ee41ea | testVNF2 |20:12
trozet| e0d23783-27bd-43ee-9f16-ae4d4506ba23 | testVNF1 |20:12
trozetsridhar_ram^ yeah i this vnffg i created with abstract types, so the plugin picked which ones to use20:12
sridhar_ramtrozet: cool.. i believe you now ;-)20:12
trozetsridhar_ram, sripriya: more goodness https://paste.fedoraproject.org/425008/20:13
sridhar_ramtrozet: if you create the same vnffg those VNFs won't be used again ?20:13
sridhar_ram*those two VNFs20:13
trozetsridhar_ram: haha stop poking holes in it!20:13
trozetnot a use case :)20:13
trozetsridhar_ram: no but seriously, the same VNFs can be used again in a chain20:13
sridhar_ramtrozet: lol... couldn't hold my enthusiam20:13
sridhar_ramtrozet: yes, with specific mapping .. but how abt w/ abstract types ?20:14
trozetsridhar_ram: it will reuse them20:14
trozetsridhar_ram: i actually dont know though if networking-sfc handles that, or if the driver handles that correctly20:15
trozetsridhar_ram: but from plugin perspective, you should be able to use VNFs in more than one chain20:15
sripriyatrozet: only if there are more than one VNF for vnfd and  random func. picked the same VNF again20:15
trozetsripriya: yeah that is a bug for sure20:15
trozetsripriya: so if you said VNF1, VNF1 (as vnfds) in your forwarding path and it picked the same one twice, that would be a bug I think20:16
trozetsripriya: and i think that bug exists in my code20:16
sridhar_ramtrozet: :)20:16
trozetsridhar_ram, sripriya: right now the code would just use the first VNF instance for both, but if a user specifies 2 VNFDs explicitly in the path i think we should do 220:16
trozetsridhar_ram, sripriya: agree?20:17
sripriyatrzoet: if you needed to deploy a new VNFFG with the same VNFD and it picked up the same VNF again that should work20:17
sripriyatrozet: ^20:17
trozetsripriya: yeah that part should work now.  The issue I am talking about is in a single VNFFG, your forwarding path is 2 VNFs, both of the same VNFD type, and you create with abstract types20:18
trozetsripriya: that means the plugin goes and decides which VNFs to use, and right nwo with the logic, it will pick the same VNF twice20:18
sripriyatrozet: i see20:18
trozetsripriya: it should pick 2 different ones, right?20:18
sripriyatrozet: suppose there are 2 VNFS, for the same VNFD it could pick both of them20:19
trozetsripriya: what if there was only 1 VNF, and 2 were specified of the same VNFD type in the forwarding path, we should throw exception?20:19
sripriyatrozet: yeah it should pick 2 diff ones20:19
trozetsripriya: ok let me try to fix that20:19
*** mbound has joined #tacker20:20
sripriyatrozet: but is that doable?20:20
trozetsripriya: doable code wise?20:20
sripriyatrozet: where one VNF is used twice?20:20
sripriyatrozet: on the driver side?20:21
sripriyatrozet: not code20:21
trozetsripriya: well speaking not on networking-sfc driver, but on IETF SFC, yeah it is possible20:21
sripriyatrozet: then shouldn’t we allow it?20:22
trozetsripriya: i don't think it is currently allowed in networking-sfc (they dont use IETF SFC just yet)20:22
trozetsripriya: but something I can follow up on20:22
sripriyatrozet: okay20:22
trozetsripriya: for now I'll throw an exception if htere are not enough VNFs, and then I will look into that20:23
sripriyatrozet: can we defer this decision to the driver or should this be handled in plugin itself20:23
sripriyatrozet: okay20:23
trozetsripriya: that is another good point20:24
trozetsripriya: but i think if more than 1 is available, we should try to use a different one20:24
trozetsripriya: so let me at least add that20:24
trozetsripriya: and maybe not thrown any exception or do anythign right now for hte other case20:25
sridhar_ramtrozet: just caught up.. at the outset, it seems using two VNFs of the same type in a FFG seems a bad idea20:25
trozetsridhar_ram: you think we should just ignore that case for now?20:25
sridhar_ramtrozet: hmm... i think we shd error out20:25
trozetsridhar_ram: ok so if the same VNFD is listed in the path twice in the VNFFGD, we should throw exception on VNFFGD create, right?20:26
sridhar_ramtrozet: yes, i can think of some convoluted cases where we might end up w/ such an ask.. but as a mainstream case we are better have erroring out20:27
sridhar_ram*better off20:27
trozetsridhar_ram: ok i will add that now then20:27
trozetsridhar_ram: so i guess where I am at now, let me fix that along with the comments in the review.  The next step will be refactoring s3wong patch to be in openstack driver20:27
sridhar_ramtrozet: let some ffg user explicitly hit this "restriction" and come to us with correct reasoning20:27
trozetsridhar_ram: but it looks like the plugin is working20:28
sridhar_ramtrozet: super cool.. once the n-sfc refactoring into openstack driver happens.. we shd land all these patches and continue w/ test <-> fix cycle20:29
sridhar_ramsripriya: what do you think ?20:29
* trozet exudes giant sigh of relief20:30
trozetsridhar_ram: also i just tried creating VNFFG with vnf_mapping provided, works20:31
*** sripriya has quit IRC20:40
*** tung_doan is now known as tung_doan_afk20:43
*** sripriya has joined #tacker20:49
sripriyasridhar_ram: good to land these patches asap else there will be another few cycles spent on resolving merge conflicts20:52
*** uck has joined #tacker20:56
*** openstackstatus has quit IRC20:57
*** openstackstatus has joined #tacker21:00
*** ChanServ sets mode: +v openstackstatus21:00
*** uck has quit IRC21:00
trozetsridhar_ram: lol so i added the thing to detect the same forwarder twice...and my unit test fail because it caught that my unit test example file has VNF1 listed twice:21:05
trozet        path:21:05
trozet          - forwarder: VNF121:05
trozet            capability: CP1121:05
trozet          - forwarder: VNF121:05
trozet            capability: CP1221:05
trozetsridhar_ram, sripriya: actually now I realize listing the same VNF in the path is fine, as long as the CP is different21:07
trozetsridhar_ram, sripriya: if the same VNF is listed twice, I assume the first port is the ingress port and the 2nd port is egress21:08
trozetsridhar_ram, sripriya: so i guess really what we should look for is it listed more than twice, and not in order21:08
*** uck has joined #tacker21:15
*** sripriya has quit IRC21:18
*** mbound has quit IRC21:19
*** sripriya has joined #tacker21:20
sripriyatrozet: yeah makes sense21:25
sripriyatrozet: also, is it possible to create port pair out of ingress port of one vnf with egress port of another vnf21:26
trozetsripriya: no, i don't think that is possible21:26
sripriyatrozet: i mean two different forwarders21:27
sripriyatrozet: then in that case ingress and egres sport will be the same21:27
sripriyaegress port*21:27
trozetsripriya: if you have a single VNF, and only one port listed, it is assumed that is both ingress and egress21:27
sripriyatrozet: got it21:27
sripriyatrozet: and if we have multiple VNFs with one port listed, it will be the same behavior again21:28
trozetsripriya: yeah21:28
trozetsripriya: i added a check for duplicate ports as well, for hte same VNF21:29
trozetsripriya: so if you have VNF1 CP1, VNF1 CP1, it will throw error21:29
*** prashantD has quit IRC21:29
*** prashantD has joined #tacker21:30
sripriyatrozet: ok21:30
sripriyatrozet: we have a good no. of combinations here that can happen, it is good to document these behaviors21:31
*** bobh has quit IRC21:40
openstackgerritTim Rozet proposed openstack/tacker: Implements VNFFG into NFVO  https://review.openstack.org/34452222:07
*** prashantD has quit IRC22:17
*** prashantD has joined #tacker22:17
*** uck has quit IRC22:23
*** sripriya has quit IRC22:25
*** sripriya has joined #tacker22:25
*** sripriya has quit IRC22:41
*** bobh has joined #tacker22:54
*** bobh has quit IRC22:57
*** uck has joined #tacker23:12
*** uck has quit IRC23:17
*** vishwanathj has quit IRC23:52

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