Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added content for "Programming Language", "Testing" sections

...

In the future, we could make improvements to migrate extractors, for example, if 4 extractors run on vm1, and only extractor 1 has work to do, and there is an open slot to run extractor 1 on vm2 (where extractor 1 is already running), we could migrate the extractor 1 instance from vm1 to vm2, and suspend vm1 – but this is considered lower priority.

  • Programming Language and Application Type
  • Testing

...

The team seems to be familiar, more comfortable with Java or Scala, so we consider using these. This module mainly operates on itself, instead of mainly serving client requests, so it does not seem to need to be a web app. A stand-alone app seems a better fit.

  • Testing
  • Input
    We plan to use scripts to generate high request rates. We can use different input files/configuration to generate high request rates for a certain set of extractors to test the scaling up part.  We can either reduce the request rate, or stop sending the requests to test the scaling down part.
  • Output
    We plan to use the OpenStack CLI tool (such as "nova") or Web UI, and RabbitMQ CLI or web UI to verify that the extractors are started, and VMs are started/resumed/suspended as expected.