Age | Commit message (Collapse) | Author | Files | Lines |
|
-Small API changes as Fenix validates API schema
-Bug fixes in building Fenix service and container
-Need to wait container ready before testing
Related: https://review.opendev.org/#/c/706775/
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
Change-Id: I8b88865d6b8569c6660513974955f7cd65619a33
|
|
JIRA: DOCTOR-137
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
Change-Id: I6e632b24efb6728c171dd93979e3b1de5333251b
|
|
Support running Doctor testing is DevStack multi-node controller
JIRA: DOCTOR-136
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
Change-Id: I1569f3f77d889420b3b8f3c2724c10253e509c28
|
|
JIRA: DOCTOR-134
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
Change-Id: I51a93637f30b0eece2075a8277616fb97a1b230e
|
|
Change-Id: I719c46a8b5407b565cf0b6df4cd9b4c95a6a8ce5
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Congress as inspector, currently we can't get the vmdown time
and hostdown time unless we get the log of congress and extract the times.
Change-Id: Ie8b9dff6048040a1f834033c4873c168225e9d8c
Signed-off-by: dongwenjuan <dongwenjuan1122@gmail.com>
|
|
If ADMIN_TOOL_TYPE=fenix we run maintenance testing using Fenix
instead of sample implementation. Testing will build Fenix
Docker container from latest master and make configuration
according to controller host.
JIRA: DOCTOR-131
Change-Id: I84c566b7afc3c4e488aeed63b5cf5c75046d1427
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
Support yet another path to find config files.
Tune config changes to take effect properly for maintenance.
transport_url parcing enhanced.
Nova reset state to error takes well over 1 second these days
and at the end it then sends notification that we use.
Only reasonable thing is to send notification straight from
the Inspector as it should have been done in the first place.
Now we can do 200ms as total time, with just a few millisends
actuallly spent on sending the notification. Further one
could improve this by having node specific Inspector agent to
react even in more Telco grade speed.
Change-Id: I787f8e9dd6484842c6c568b15767018d11b36862
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
As Mcp already set the notifier for alarm in ceilometer configuration,
we remove the configuration workaround.
JIRA: DOCTOR-132
Change-Id: I30603d7f364fbbed143ebdb3dc6fdf71b10434a0
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
|
|
|
|
Fenix has now same capability as our sample implementation.
We can now support Fenix if manually installed on controllers.
Sample implementation should be closer to Fenix as Fenix is the
place to define the generic interfaces at the end.
JIRA: DOCTOR-131
Change-Id: Ied58b8f469dbcc4bb5caa787e62c1831a211ecd6
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
SSH connection might be reseted with long running session.
This may happen if run "testcase=all"
Change-Id: I232ae906628411dfbe0bbdbdc8d4fb43167760fd
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
Change-Id: I6ea9c031a8093d7ce94b49575cb6bfe348eb6c9a
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
|
|
Upstream apex now works in containers, so if used, it needs to be supported
JIRA: DOCTOR-130
Change-Id: I3d73a1699e4fee53b001f043f55d0eeefa7bfb7b
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
Change-Id: I6d5325166db642b3481a0327f518ec821a8ab378
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
|
|
Change-Id: Ide5ff5e1c894e3144ac07f14b76b7092539d39f6
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
If we delete doctor driver in congress configuration when cleanup,
the doctor datasource still existed, it will be raise an exeption
in congress server and the service can't be started.
Change-Id: Icefde9964229ef3d55af09cc2e81680cb8d19813
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Change-Id: I465fd6c59daf99dd543488a15819dab78e8cdd7b
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
-Add sample admin_tool
-Add sample app_manager
-Modify sample inspector
JIRA: DOCTOR-106
Change-Id: I52cffecaa88452ce5e7cc6487534c88fcfd378ad
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
JIRA: DOCTOR-106
Change-Id: Idb95e1391e8f9094f68e2c7bc79fd2d7e01af9de
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
|
|
|
|
Popen.terminate() will kill the child process, but if you set the
shell argument to True, this is the process ID of the spawned shell,
so the stunnels are still exit.It will cause the failure of stunnel
setup in the next test runtime.
see: https://stackoverflow.com/questions/4789837/how-to-terminate-a-python-subprocess-launched-with-shell-true/4791612#4791612
Change-Id: I578611510f5bd1eb0dbd9a08ab408ccf101594f7
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Change-Id: I063d7ba9b3eb8999cb2b08e7c6deca2644eb169e
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
The stunnel will be setup failed in the docker if we have the .log
at the end of file name.
Change-Id: I272a9fa3b668d49b0e26752403ad41a67dcfedc7
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Change-Id: I8809a24e75c0260f67d3e128b8bbd1becf924529
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Port number of consumer should be int instead of str.
Change-Id: I7f7c7b23ede094d1d3278ef4cd5f971fb57ca2e8
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
In Mcp baremetal env, doctor test is always failed because of
ssl certificate for https.
Change-Id: Ia443c6463fe177ff4e1ab5a86429750fbd23740c
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Get 'test_case' option form environment variable. If no
environment variable, use the default value so that we can
specify the test case in doctor verify job.
Change-Id: I1bc25d024ca56637d779006d685b57254af355a5
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
|
|
Change-Id: I47572b4515049c49f9aa04bf7984757779a605f3
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
1.support MCP installer
2.optimize the installer code
JIRA: DOCTOR-121
Change-Id: I8675c2652944575a8f73d0d1e2dafaad5a3e88e3
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Introducing root cause fix for sample inspector shutdown
JIRA: DOCTOR-123
Change-Id: Ibc95d482f476b60584c224d8e2757d071149d611
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
Change-Id: I4e3e510f51258e892b467f819951bd1a98625f90
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
This should be workaround before actual fix is done.
JIRA: DOCTOR-123
Change-Id: I70fd4ed9d2aa2cc3a6c46e2515062b7acd31ca0a
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
As doctor functest CI runs failed in Apex installer, it indicates
that flavor is None. See http://artifacts.opnfv.org/logs/functest/lf-pod1/2018-01-21_05-30-00/doctor-notification.log
Change-Id: Ia7a7111a7c6b94864f2e12f30969fe6e411058af
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
This patch changes the way to specify target test case to be run,
'test_fault_management' --> 'fault_management'.
Also, the default is set to 'fault_management'. The reason to this
is not to block any other on-going activities for Fraser release.
Change-Id: I92305477a84ffa0e703c36d309fbdf97435782aa
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
|
|
Change-Id: I91b8b6cd07d859a1d1abdc25f015a3c3b2756fab
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
JIRA: DOCTOR-119
Change-Id: I98e556fba30eb7ba244cb9d0d88a9e95c39193ff
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
|
|
|
|
Change-Id: I0b60e6f1e15cbe556c7555186352d28490b98acc
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Change-Id: I3c4358694c57d27a207ae60712c44f717c8895f7
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
JIRA: DOCTOR-118
Change-Id: Id4d586fd2b7ca043cfd8231b9c46bdc581f039ab
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Change-Id: Ia642279a99ad9bf014764337c8a5170e3c98e2f2
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
JIRA: DOCTOR-122
Change-Id: I771f778767a204e809d892c70603e479c1ed2f5c
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|