Migrate from vHive utils to vSwarm ones

Signed-off-by: Leonid Kondrashov <[email protected]>

README.md

@@ -24,7 +24,7 @@ The standalone functions can therefore be used as microbenchmarks to first pin-p
 - `benchmarks` contains all of the available benchmark source code and manifests.
 - `utils` contains utilities for use within serverless functions, e.g. the tracing module.
 - `tools` is for command-line tools and services useful outside of serverless functions, such as
-   deployment or invokation.
+   deployment or invocation.
 - `runner` is for setting up self-hosted GitHub Actions runners.
 - `docs` contains additional documentation on a number of relevant topics.
 

docs/methodology.md

@@ -38,7 +38,7 @@ In gRPC requests, vHive Metadata is passed as field
 vHive metadata is stored in `vhivemetadata` extension attribute of type
 byte array---this is also what TimeseriesDB looks for.
 
-Developers can use `utils/benchmarking/eventing/vhivemetadata` to read
+Developers can use `tools/benchmarking_eventing/vhivemetadata` to read
 and create vHive metadata objects.
 
 ## Benchmarking

tools/benchmarking_eventing/proto/timeseries.proto

@@ -25,7 +25,7 @@ import "google/protobuf/duration.proto";
 import "google/protobuf/empty.proto";
 import "google/protobuf/timestamp.proto";
 
-option go_package = "github.com/ease-lab/vhive/utils/benchmarking/eventing/proto";
+option go_package = "github.com/ease-lab/vSwarm/tools/benchmarking_eventing/proto";
 
 /*
     EXAMPLE USAGE: