Recent changes to AdministrationGuide

AdministrationGuide modified by Serge Lozovsky

Serge Lozovsky — Sun, 14 May 2017 06:09:24 -0000

--- v24
+++ v25
@@ -202,7 +202,7 @@

 Pic. 5

-After script is finished check the logs.
+Observe that status indicator in the upper right corner is red. That menas that there is VXEDI with violation logs. After script is finished check the logs.

 ### Checking logs

AdministrationGuide modified by Serge Lozovsky

Serge Lozovsky — Sun, 14 May 2017 06:06:23 -0000

--- v23
+++ v24
@@ -145,6 +145,10 @@

 This tab shows existing violations logs.

+
+
+Pic. 3
+
 *Live* section of the left pane lists violation logs of the running VXEIs. If a log index is selected in the left pane, the log contenets is shown in the right pane.

 *Complete* section of the left pane lists violation logs of the ended VXEIs. Logs are grouped by VXED names. Log indexes that can be applied to VXEDs (whose indixes match current index of particular VXED) are marked by bold font.

AdministrationGuide modified by Serge Lozovsky

Serge Lozovsky — Sun, 14 May 2017 06:05:06 -0000

--- v22
+++ v23
@@ -216,12 +216,24 @@

 ### Edit VXED

-In the *VXED Edit* tab all changed system call definitions and rules are marked as *changed*. It makes easier to locate changes made by the update. In our example all rules are new, so all of them are marked as changed.
+In the *VXED Edit* tab all changed system call definitions and rules are marked as *changed*. It makes easier to locate changes made by the update. In our example all rules are new, so all of them are marked as changed. VXED version is incremented.

 

 Pic. 7

-
-
-*To be continued*
+VXED should be generalized to become useful. Expand *open* syscall by clicking on it. We can see that there are many instances of accessing `/proc/...`. Let's allow our script read access to `/proc/...` with all subdirectories.
+
+Double-click on any rule with `/proc/...` and change `/proc/...` to `/proc/\*`. Set counter fileld to `\*` and press *Enter* or click outside of the rule. GUI will integarate all `/proc/...` rules into one. Flag 0 menas read access.
+
+Go through other system calls and do generalizations as you see fit.
+
+Click *Save* button to save results.
+
+### Run the script multiple times
+
+To get a complete VXED the script should be xecuted multiple times to reveal different exection paths and variances in using resources.
+
+If there is no need to be very specific about some system calls - select *Tools* - *Allow all*. For example, we probably don't care about *close* system call and it's hard to create meningful rules for it.
+
+Repeat previous steps multiple times until no violation logs are produced. At this point in time switch *Mode* to *deny* in VXED header above buttons.

AdministrationGuide modified by Serge Lozovsky

Serge Lozovsky — Sun, 14 May 2017 05:45:04 -0000

--- v21
+++ v22
@@ -208,6 +208,20 @@

 Pic. 6

+A number before system call name is conter. It indicates how many times this system call was executed with the given parameters.
+
+There are two way to update VXED with the violations from the log. The first is from *VXED Edit* tab, by clicking *Upadte* button. GUI will automatically mark all applicable logs. The second way is to mark logs manually. This is what we do in current example.
+
+Mark the checkbox before *1* log and click *Apply* button. This will bring us to the updated VXED.
+
+### Edit VXED
+
+In the *VXED Edit* tab all changed system call definitions and rules are marked as *changed*. It makes easier to locate changes made by the update. In our example all rules are new, so all of them are marked as changed.
+
+
+
+Pic. 7
+

 *To be continued*

AdministrationGuide modified by Serge Lozovsky

Serge Lozovsky — Sun, 14 May 2017 05:32:45 -0000

--- v20
+++ v21
@@ -186,10 +186,28 @@

 Enable VXED by marking the checkbox next to the VXED name *test*.

+No system calls are defined (allowed) in the new VXED, so they all will be logged in the subsequent run.
+
 ### Monitor execution

 From the command line run your test script.

 Monitor its execution through the *Dashboard* tab. 

+
+
+Pic. 5
+
+After script is finished check the logs.
+
+### Checking logs
+
+At the *Logs* tab expand *test* logs. There is just one log is present *1*. Select it. Contents of the log appears at the right pane.
+
+
+
+Pic. 6
+
+
+
 *To be continued*

AdministrationGuide modified by Serge Lozovsky

Serge Lozovsky — Sun, 14 May 2017 05:22:10 -0000

--- v19
+++ v20
@@ -170,7 +170,7 @@
 time.sleep(30)
 ~~~

-Path of the script is */home/slozovsky/vxetest.py*
+Path of the script is */home/slozovsky/vxe_test.py*

 You can create the similar script in your directiry for testing.

@@ -178,7 +178,7 @@

 Go to *VXED Edit* tab. Select *New*. Fill in *Name* and *Activation path*. Use path of your script.

-
+

 Pic. 4

@@ -186,6 +186,10 @@

 Enable VXED by marking the checkbox next to the VXED name *test*.

+### Monitor execution

+From the command line run your test script.
+
+Monitor its execution through the *Dashboard* tab. 

 *To be continued*

AdministrationGuide modified by Serge Lozovsky

Serge Lozovsky — Sun, 14 May 2017 04:55:26 -0000

--- v18
+++ v19
@@ -184,4 +184,8 @@

 Click *Save* button. Version number should become 1.

+Enable VXED by marking the checkbox next to the VXED name *test*.
+
+
+
 *To be continued*

AdministrationGuide modified by Serge Lozovsky

Serge Lozovsky — Sun, 14 May 2017 04:53:33 -0000

--- v17
+++ v18
@@ -174,4 +174,14 @@

 You can create the similar script in your directiry for testing.

+### Create a new VXED
+
+Go to *VXED Edit* tab. Select *New*. Fill in *Name* and *Activation path*. Use path of your script.
+
+
+
+Pic. 4
+
+Click *Save* button. Version number should become 1.
+
 *To be continued*

AdministrationGuide modified by Serge Lozovsky

Serge Lozovsky — Sun, 14 May 2017 04:15:38 -0000

--- v16
+++ v17
@@ -137,12 +137,23 @@

 Above the rules there is Tools menu with following options:

-* Allow all
-* Allow all with count
-* Delete all
+* Allow all - allow this system call with any parameters without limiting number of calls
+* Allow all with count - allow this system call with any parameters, but limit the number of calls by the sum of all calls in the table
+* Delete all - remove this syscall from VXED completely

+### Logs

+This tab shows existing violations logs.

+*Live* section of the left pane lists violation logs of the running VXEIs. If a log index is selected in the left pane, the log contenets is shown in the right pane.
+
+*Complete* section of the left pane lists violation logs of the ended VXEIs. Logs are grouped by VXED names. Log indexes that can be applied to VXEDs (whose indixes match current index of particular VXED) are marked by bold font.
+
+Buttons at the bottom left are applied to the logs with marked checkboxes. There are three such buttons:
+
+* Apply - apply logs with marked checkboxes to VXED; only one VXED can be updated in a time 
+* Clear - remove marks from all marked checkboxes
+* Delete - delete logs with marked checkboxes

 ## Example

AdministrationGuide modified by Serge Lozovsky

Serge Lozovsky — Fri, 12 May 2017 05:32:34 -0000

--- v15
+++ v16
@@ -132,8 +132,8 @@
 * n (number) - move at this number if changed, old row moves down
 * b - move to the begining of the table
 * e - move to the end of the table
-* - - delete this row
-* + - add a row after the current
+* \- - delete this row
+* \+ - add a row after the current

 Above the rules there is Tools menu with following options: