Age | Commit message (Collapse) | Author | Files | Lines |
|
The ovs_logger library was too tightly connected
to the Fuel installer.
This patch make the aforementioned library
installer independent
Change-Id: I39115067393b8d4baf66c23baf2d9c130e4668bd
Signed-off-by: Dimitrios Markou <mardim@intracom-telecom.com>
|
|
Although it makes no sense that the lists of controller/compute nodes
are empty, the function should not crash.
This check ensures that the directory where the logs are written to is
always created before dumping anything.
Change-Id: I3a1fd8ac8ab983decb0bc227a2a22286ff5e34ce
Signed-off-by: Juan Vidal <juan.vidal.allende@ericsson.com>
|
|
Change-Id: I7c72a75324897231a583f38d424dedea42b20f3d
Signed-off-by: George Paraskevopoulos <geopar@intracom-telecom.com>
|
|
Change-Id: I45769ff9c9db2de9fbba69117a92de414dd7f651
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
JIRA: SFC-61
In SFC we have created a module to gather "ovs-vsctl show" and
"ovs-ofctl dump-flows" information automatically.
Releng is a more appropriate place for it, as it can be utilized by
other projects to create artifacts with ovs logs when a testcase fails
Change-Id: If6cf6a937532f7776f9b300ffdb2ab6c4fde82c8
Signed-off-by: George Paraskevopoulos <geopar@intracom-telecom.com>
|