REMOVE rpm stuff

CHANGES_NEXT_RELEASE

@@ -12,3 +12,4 @@
 - Remove ngsiv1 support for updateAction (#714)
 - Fix: check timer string in lower case in TimedRule checker
 - Fix: dep of chai get-func-name to 2.0.0 to avoid installation errors
+- Remove: RPM stuff

docker/Dockerfile

@@ -87,7 +87,7 @@ RUN \
 	fi && \
 	RELEASE_CONCAT=$(echo "${RELEASE}" | tr / -); \
 	curl -s -L https://github.com/"${GITHUB_ACCOUNT}"/"${GITHUB_REPOSITORY}"/archive/"${RELEASE}".zip > source.zip && \
-	unzip source.zip -x "*/test/**" "*/rpm/**" "*/docker/**" "*/documentation/**" "*/.*" && \
+	unzip source.zip -x "*/test/**" "*/docker/**" "*/documentation/**" "*/.*" && \
 	rm source.zip && \
 	mv "${GITHUB_REPOSITORY}-${RELEASE_CONCAT}" /opt/perseo-fe && \
 	# Remove unzip and clean apt cache

docs/admin/deployment.md

@@ -119,52 +119,6 @@ docker logs perseo_fe
 docker exec perseo_core tail -f /var/log/perseo/perseo-core.log
 ```
 
-### Installation from RPM
-
-This project provides the specs to create the RPM Package for the project, that may (in the future) be installed in a
-package repository.
-
-To generate the RPM, checkout the project to a machine with the RPM Build Tools installed, and, from the `rpm/` folder,
-execute the following command:
-
-```bash
-./create-rpm.sh 0.1 1
-```
-
-The create-rpm.sh script uses the following parameters:
-
--   CEP version (0.1 in the example above), which is the base version of the software
--   CEP release (1 in the example above), tipically set with the commit number corresponding to the RPM.
-
-This command will generate some folders, including one called RPMS, holding the RPM created for every architecture
-(x86_64 is currently generated).
-
-In order to install the generated RPM from the local file, use the following command:
-
-```bash
-yum --nogpgcheck localinstall  perseo-cep-0.1-1.x86_64.rpm
-```
-
-It should automatically download all the dependencies provided they are available (Node.js and npm may require the EPEL
-repositories to be added).
-
-The RPM package can also be deployed in a artifact repository and the installed using:
-
-```bash
-yum install perseo-cep
-```
-
-NOTE: Perseo CEP Core is not installed as part of the dependencies in the RPM, so the URL of an existing Perseo Core
-must be provided and configured for Perseo to work properly.
-
-#### Activate service
-
-The perseo service is disabled once its installed. In order to enable it, use the following command:
-
-```bash
-service perseo start
-```
-
 ### Installation from Sources
 
 #### Installation
@@ -183,10 +137,9 @@ In order to undeploy the proxy just kill the process and remove the directory.
 
 ### Log Rotation
 
-Independently of how the service is installed, the log files will need an external rotation (e.g.: the `logrotate`
-command) to avoid disk full problems.
+Withing `etc` directory we can find some logrotate stuff (formerly used with RPM-based deployments, but probably not used at the present day), just in case they can be useful.
 
-`logrotate` is installed as RPM dependency along with perseo. The system is configured to rotate every day and whenever
+The configuration is set to rotate every day and whenever
 the log file size is greater than 100MB (checked very 30 minutes by default):
 
 -   For daily rotation: `/etc/logrotate.d/logrotate-perseo-daily` : which enables daily log rotation

docs/developer/contributing.md

@@ -157,7 +157,7 @@ The process of making a release consists of the following steps:
 
 1. Create a new task branch changing the development version number in the package.json (with a sufix `-next`), to the
    new target version (without any sufix), and PR into `master`. Also, in this task, the contents of the Change log are
-   copied to the RPM spec.
+   copied to the Changelog file.
 2. Create a tag from the last version of `master` named with the version number and push it to the repository.
 3. Create the release in Github, from the created tag. In the description, add the contents of the Change log.
 4. Create a release branch from the last version of `master` named with the version number.

scripts/build/release.sh

@@ -20,6 +20,10 @@
 # For those usages not covered by this license please contact with
 # iot_support at tid dot es
 
+# FIXME: this script is outdated. It is still using the rpm-based changelog.
+# Have a look to same script at fiware-orion repo (which was adapted to use the new Changelog file)
+# if we want to fix it
+
 # ------------------------------------------------------------------------------
 #
 # Example execution: