Remove site-manager from common-modules

Patch 1: The site-manager is specific to the AT&T environment and is
not functional in ONAP.  This change removes the site-manager module
from the policy common-modules.

Patch 2: Removed the site-manager from the pom.xml file.

Issue-ID: POLICY-1001
Change-Id: Ibd8dd95915739205b0c5463c8b28706b615d9faf
Signed-off-by: Kevin McKiou <km097d@att.com>

1 files changed, 0 insertions, 30 deletions

diff --git a/site-manager/src/main/files/README b/site-manager/src/main/files/README
deleted file mode 100644
index d5d2df6e..00000000
--- a/site-manager/src/main/files/README
+++ /dev/null
@@ -1,30 +0,0 @@
-Copyright 2018 AT&T Intellectual Property. All rights reserved.
-This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE
-Full license text at https://creativecommons.org/licenses/by/4.0/legalcode
-
-Before using 'siteManager', the file 'siteManager.properties' needs to be
-edited to configure the parameters used to access the database:
-
-    javax.persistence.jdbc.driver - typically 'org.mariadb.jdbc.Driver'
-    javax.persistence.jdbc.url - URL referring to the database,
-        which typically has the form: 'jdbc:mariadb://<host>:<port>/<db>'
-		('<db>' is probably 'xacml' in this case)
-    javax.persistence.jdbc.user - the user id for accessing the database
-    javax.persistence.jdbc.password - password for accessing the database
-
-Once the properties file has been updated, the 'siteManager' script can be
-invoked as follows:
-
-    siteManager show [ -s <site> | -r <resourceName> ] :
-        display node information
-    siteManager setAdminState { -s <site> | -r <resourceName> } <new-state> :
-        update admin state on selected nodes
-    siteManager lock { -s <site> | -r <resourceName> } :
-        lock selected nodes
-    siteManager unlock { -s <site> | -r <resourceName> } :
-        unlock selected nodes
-
-Note that the 'siteManager' script assumes that the script,
-'site-manager-${project.version}.jar' file and 'siteManager.properties' file
-are all in the same directory. If the files are separated, the 'siteManager'
-script will need to be modified so it can locate the jar and properties files.