Release v2.0

This release has update to the mongoose package from v.5.13.30 to 8.9.5.
Read more details about mongoose release @ https://github.com/Automattic/mongoose/releases

What's Changed

• Query update towards working on latest OS and mongodb version > 2.6.x by @octaviansoldea in #79
• Fix: microservices Bad URL Error by @Jonathan-Alexander in #81
• V1.2.0 by @octaviansoldea in #82
• Fix: #83 - MongoDB initialization in cluster mode by @octaviansoldea in #84
• Fix: #85 - Exiting execution if MongoDB cannot run at predefined port. by @octaviansoldea in #86
• Using scp and ssh instead of rcp and rsh respectively by @octaviansoldea in #90
• Configurable files for cluster mode. by @octaviansoldea in #89
• CPU_COUNT in cluster mode is not correctly settable. by @octaviansoldea in #93
• Changing mongoose from 4.4.12 to 5.7.7 due to security issues. by @octaviansoldea in #99
• Changing express from 4.13.3 to 4.17.1 due to security issues. by @octaviansoldea in #103
• Changing body-parser from 1.15.0 to 1.19.0 due to security issues. by @octaviansoldea in #105
• Changing pug from 2.0.0-rc.1 to 2.0.4 due to security issues. by @octaviansoldea in #107
• Bump pug from 2.0.4 to 3.0.2 in /Node-DC-EIS-cluster by @dependabot in #117
• Bump mongoose from 5.7.7 to 5.13.20 in /Node-DC-EIS-microservices/comp_service by @dependabot in #116
• Bump mongoose from 5.7.7 to 5.13.20 in /Node-DC-EIS-microservices/employee_service by @dependabot in #115
• Upgrading Node-DC-EIS to Python version 3. by @octaviansoldea in #101
• Bump mongoose from 5.7.7 to 5.13.20 in /Node-DC-EIS-microservices/photo_service by @dependabot in #109
• Bump mongoose from 5.7.7 to 5.13.20 in /Node-DC-EIS-microservices/health_service by @dependabot in #110
• Bump mongoose from 5.7.7 to 5.13.20 in /Node-DC-EIS-microservices/family_service by @dependabot in #111
• Bump mongoose from 5.7.7 to 5.13.20 in /Node-DC-EIS-microservices/address_service by @dependabot in #112
• Bump mongoose from 5.7.7 to 5.13.20 in /Node-DC-EIS-microservices/db_loader_service by @dependabot in #113
• Bump mongoose from 5.7.7 to 5.13.20 in /Node-DC-EIS-cluster by @dependabot in #114
• Bump express from 4.17.1 to 4.20.0 in /Node-DC-EIS-cluster by @dependabot in #118
• Bump body-parser from 1.19.0 to 1.20.3 in /Node-DC-EIS-cluster by @dependabot in #119
• Bump pug from 3.0.2 to 3.0.3 in /Node-DC-EIS-cluster by @dependabot in #120
• Bump async from 2.0.1 to 2.6.4 in /Node-DC-EIS-cluster by @dependabot in #121
• doc: clarify microservice launch by @Jonathan-Alexander in #80
• Fix security issues by upgrade by @uttampawar in #126
• Security fix issue 127 by @uttampawar in #128

New Contributors

• @octaviansoldea made their first contribution in #79
• @Jonathan-Alexander made their first contribution in #81
• @dependabot made their first contribution in #117

Full Changelog: v1.1.2...v2.0

Enhancement patch release

This is a incremental release with data reporting enhancement. Now runspec.py reports data transfer size in terms of 'total bytes received", during the run.

Patch Release

This is a quick bug fix release.

Release v1.1.0

This release has few changes containing support for --nograph and refactoring of related code.

Node-DC-EIS workload v1.0

This is a first major release of this workload with lot of effort to make it stable, supporting multiple use cases. Following are the major features.

**A node.js server application** ,
  - Embedded database objects as per NoSQL (mongodb) guide.
  - Uses Node.js core features such as 'Cluster'
  - Runs in a monolithic (single process), multiple processes using Cluster where server scaling is important and micro-services mode
  - Runs on a bare metal and in a Docker container
  - It can be deployed as a single application or multiple instances where density is important.
  - In a multiple instance execution mode, it can be deployed on a single host and across a network of machines.
  - It can be configured to use single, all or specific number of CPU cores using environment variable.
  - When launched in multiple instance mode, the measuring time is synchronized across all instances to get maximum CPU and System utilization.
  - It can be configured to use single or multiple mongodb server instance(s)
  - Supports default JSON or HTML data response using PUG engine.
  - Supports GET, POST and DELETE operations
  - Currently support following end-points:
    * '/'        : Application root
    * '/loaddb'  : Instantiates database
    * '/checkdb' : Verifies DB for consistency
    * '/employees' : GET request to retrieve all employee records
    * '/employees' : POST request to insert new employee record
    * '/employees/id' : GET request to retrieve all employee IDs only
    * '/employees/id/:id' : GET request to retrieve employee record by ID
    * '/employees/name' : GET request to retrieve employee record(s) by name
    * '/employees/zipcode' : GET request to retrieve employee record(s) by zip code
    * '/employees/id/:id' : DELETE request to delete employee specified by ID
    * '/employees/id/:id/photo.jpg' : GET request to retrieve employee photo by ID

    * '/getmeminfo' : GET request to get memory snapshot  details. This get called every 1 second by the client and used for live graph.
    * '/getcpuinfo' : GET request to get system information. This includes hardware and software details
    * '/stopserver' : GET request to stop the server application.

- A Python based multi-threaded client
  - It support various phases like ramp-up, measurement and ramp-down
  - Creates a set of URLs with mix of GET, POST and DELETE types with randomly selected query parameters (id, name or zip code).
  - Collects 'server memory usage' at specified interval
  - Tracks response time for each request and errors.
  - Aggregates Throughput for specified interval
  - Shows live graphs during the run
  - Validates the runs
  - Post-processes the transactions log producing final metrics and graphs.