Re: [openstack-dev] [vitrage] code organization for trace generator and

2017-01-15 Thread Yujun Zhang
)" > *Date: *Friday, 13 January 2017 at 09:43 > *To: *"OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > *Subject: *[openstack-dev] [vitrage] code organization for trace > generator and > > > >

Re: [openstack-dev] [vitrage] code organization for trace generator and

2017-01-15 Thread Afek, Ifat (Nokia - IL)
at. From: Yujun Zhang Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Friday, 13 January 2017 at 09:43 To: "OpenStack Development Mailing List (not for usage questions)" Subject: [openstack-dev] [vitrage] code organization for trace generator

[openstack-dev] [vitrage] code organization for trace generator and

2017-01-12 Thread Yujun Zhang
Hi, Root Causers In the implementation of static driver unit test, the most difficult part I've encountered is the mock driver and trace generator. Is there any particular reason to put all mock driver and transformer specs in the same file `trace_generator.py` and `mock_driver.py`? Would it be e