yash-kudesia / ic2 Goto Github PK

Please search for the required tools to us MongoDB locally, not the hosted one

• Read the status from output.txt, not from console
• Use the command received to run the received file
• Sen the IP of the client corresponding to PhysicalID to NSM_DB on start

Create function in S3 to update the route in Proxy related to current Service Request.
Trigger : Service Created and Successfully spawned in client(C2).

Proxy Control Server(Connection Handler ) will notify W1 of any changes to the services spawned.

1. Service Spawned and route defined.
2. Service Closed.
3. Service Breakdown.

Creating the main server for all type of Clients C1 and C2

Use Prometheus

• Can analyze real-time data

For the INDEX, you can either put that in the discussion tab in Github or create a google docs
For the backlog, it is recommended for you to create issues, that will make it clear for all to see the progress

The servers should not crash for any type of coding errors and are immune to at least common operation errors

All the file transfers currently do not have any security check, so we have to create one

• Create a table in doctorDB for the file transfers
• Generate a hash from the content of the file
• Put the has in doctorDB new table along with the SRC and DEST
• Put the hash on the top of the file, which is t be read by the receiver
• Then the receiver will verify that using the doctorDB

Either use a third party or an open-source tool or create one.
Check for authorization also, (LDAP)

Finalize the request to be sent to C2 from S3 for spawning the container with respect to the command which is to be executed.