Converted the api_server crate into a module inside firecracker

Moved the api_server crate into a module inside the firecracker crate
Updated the imports to code located in api_server to preserve behaviour

Signed-off-by: Matias Teragni <mteragni@amazon.com>

Author: MatiasT

Cargo.lock

@@ -92,7 +92,9 @@ Firecracker's overall architecture is described in
 
 Firecracker consists of a single micro Virtual Machine Manager process that
 exposes an API endpoint to the host once started. The API is
-[specified in OpenAPI format](src/api_server/swagger/firecracker.yaml). Read more
+[specified in OpenAPI format](
+  src/firecracker/src/api_server/swagger/firecracker.yaml
+  ). Read more
 about it in the [API docs](docs/api_requests).
 
 The **API endpoint** can be used to:

README.md

@@ -19,7 +19,9 @@ enough RAM, etc.), customers can rely on the following:
    they are logged<sup>2</sup> by the Firecracker process.
 1. **API Stability:** The API socket is always available and the API conforms
    to the in-tree
-   [Open API specification](src/api_server/swagger/firecracker.yaml). API failures
+   [Open API specification](
+    src/firecracker/src/api_server/swagger/firecracker.yaml
+    ). API failures
    are logged in the Firecracker log.
 1. **Overhead:** For a Firecracker virtual machine manager running a microVM
    with `1 CPUs and 128 MiB of RAM`, and a guest OS with the Firecracker-tuned

SPECIFICATION.md

@@ -4,7 +4,7 @@ Firecracker microVMs can execute actions that can be triggered via `PUT`
 requests on the `/actions` resource.
 
 Details about the required fields can be found in the
-[swagger definition](../../src/api_server/swagger/firecracker.yaml).
+[swagger definition](../../src/firecracker/src/api_server/swagger/firecracker.yaml).
 
 ## InstanceStart
 

docs/api_requests/actions.md

@@ -58,7 +58,7 @@ Accept: application/json
 ```
 
 The full specification of the data structures available for this call can be
-found in our [OpenAPI spec](../../src/api_server/swagger/firecracker.yaml).
+found in our [OpenAPI spec](../../src/firecracker/src/api_server/swagger/firecracker.yaml).
 
 **Note**: The data provided for the update is merged with the existing data.
 In the above example, the RX rate limit is updated, but the TX rate limit

docs/api_requests/patch-network-interface.md

@@ -34,7 +34,7 @@ a call to one of the [API Endpoints](#api-endpoints) will fail with a
 ## Input Schema
 
 All input schema fields can be found in the [Swagger](https://swagger.io)
-specification: [firecracker.yaml](./../src/api_server/swagger/firecracker.yaml).
+specification: [firecracker.yaml](./../src/firecracker/src/api_server/swagger/firecracker.yaml).
 
 | Schema                     | Property              | keyboard | serial console | virtio-block | vhost-user-block |  virtio-net   | virtio-vsock | virtio-rng |
 |----------------------------|-----------------------| :------: | :------------: | :----------: | :--------------: | :-----------: | :----------: | :--------: |
@@ -108,7 +108,7 @@ virtio-net, virtio-block and virtio-rng devices.
 ## Output Schema
 
 All output schema fields can be found in the [Swagger](https://swagger.io)
-specification: [firecracker.yaml](./../src/api_server/swagger/firecracker.yaml).
+specification: [firecracker.yaml](./../src/firecracker/src/api_server/swagger/firecracker.yaml).
 
 | Schema                 | Property          | keyboard | serial console | virtio-block | vhost-user-block | virtio-net | virtio-vsock |
 | ---------------------- | ----------------- | :------: | :------------: | :----------: | :--------------: | :--------: | :----------: |
@@ -126,7 +126,7 @@ specification: [firecracker.yaml](./../src/api_server/swagger/firecracker.yaml).
 ## Instance Actions
 
 All instance actions can be found in the [Swagger](https://swagger.io)
-specification: [firecracker.yaml](./../src/api_server/swagger/firecracker.yaml).
+specification: [firecracker.yaml](./../src/firecracker/src/api_server/swagger/firecracker.yaml).
 
 | Action           | keyboard | serial console | virtio-block | vhost-user-block | virtio-net | virtio-vsock |
 | ---------------- | :------: | :------------: | :----------: | :--------------: | :--------: | :----------: |

docs/device-api.md

@@ -276,7 +276,8 @@ configuration for the guest kernel and rootfs, all of the other resources are
 optional. This configuration method will also start the microVM, as such you
 need to specify all desired pre-boot configurable resources in the JSON. The
 names of the resources can be seen in
-[`firecracker.yaml`](../src/api_server/swagger/firecracker.yaml) and the
+[`firecracker.yaml`]
+(../src/firecracker/src/api_server/swagger/firecracker.yaml) and the
 names of their fields are the same that are used in the API requests.
 
 An example of configuration file is provided:

docs/getting-started.md

@@ -37,7 +37,7 @@ curl --unix-socket /tmp/firecracker.socket -i \
 ```
 
 Details about the required and optional fields can be found in the
-[swagger definition](../src/api_server/swagger/firecracker.yaml).
+[swagger definition](../src/firecracker/src/api_server/swagger/firecracker.yaml).
 
 ## Using command line parameters for configuration
 

docs/logger.md

@@ -43,7 +43,7 @@ curl --unix-socket /tmp/firecracker.socket -i \
 ```
 
 Details about this configuration can be found in the
-[swagger definition](../src/api_server/swagger/firecracker.yaml).
+[swagger definition](../src/firecracker/src/api_server/swagger/firecracker.yaml).
 
 The metrics are written to the `metrics_path` in JSON format.
 

docs/metrics.md

@@ -116,7 +116,7 @@ a reply.
 
 Somewhat confusingly, this is the name of the component which taps the device
 model. It has a user-configured IPv4 address (see
-[Firecracker MMDS configuration API](../../src/api_server/swagger/firecracker.yaml))
+[Firecracker MMDS configuration API](../../src/firecracker/src/api_server/swagger/firecracker.yaml))
 and MAC (`06:01:23:45:67:01`) addresses. The latter is also used to respond to
 ARP requests.
 For every frame coming from the guest, the following steps take place: