Merge pull request containers#2 from flouthoc/main

cli: Integrate clap and bootstrap initial command structure.

.gitignore

@@ -0,0 +1 @@
+bin

Cargo.toml

@@ -0,0 +1,11 @@
+[package]
+name = "netavark"
+version = "0.0.1"
+edition = "2018"
+authors = ["github.com/containers"]
+description = "A container network stack"
+
+# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
+
+[dependencies]
+clap = "3.0.0-beta.4"

Makefile

@@ -0,0 +1,28 @@
+# TODO: Make this more configurable
+#prog :=xnixperms
+
+debug ?=
+
+$(info debug is $(debug))
+
+ifdef debug
+  release :=
+  target :=debug
+  extension :=debug
+else
+  release :=--release
+  target :=release
+  extension :=
+endif
+
+build:
+	cargo build $(release) --target-dir bin
+	cp bin/$(target)/netavark bin/netavark
+
+clean:
+	rm -rf bin
+
+all: build
+
+help:
+	@echo "usage: make $(prog) [debug=1]"

README.md

@@ -14,6 +14,18 @@ Netavark is capable of the following given the proper JSON input:
 As this project is in very early development, we will add more capabilities in
 the near future.
 
+## Requires
+
+- [Rust](https://www.rust-lang.org/tools/install)
+
+## Build
+
+```console
+$ make
+```
+## Latest release
+Not applicable yet (TBD)
+
 ## Latest release
 Not applicable yet (TBD)
 
@@ -24,4 +36,4 @@ IRC `#podman` channel on `irc.libera.chat`.
 
 For discussions around issues/bugs and features, you can use the GitHub
 [issues](https://github.com/containers/netavark/issues)
-and [PRs](https://github.com/containers/netavark/pulls) tracking system.
+and [PRs](https://github.com/containers/netavark/pulls) tracking system.

src/commands/mod.rs

@@ -0,0 +1,2 @@
+pub mod setup;
+pub mod teardown;

src/commands/setup.rs

@@ -0,0 +1,23 @@
+//! Configures the given network namespace with provided specs
+use std::path::PathBuf;
+use clap::{self, Clap};
+
+#[derive(Clap, Debug)]
+pub struct Setup {
+    /// Network namespace path
+    #[clap(forbid_empty_values = true, required = true)]
+    network_namespace_path: String,
+}
+
+impl Setup {
+    /// The setup command configures the given network namespace with the given configuration, creating any interfaces and firewall rules necessary.
+    pub fn new(network_namespace_path: String) -> Self {
+        Self {
+            network_namespace_path,
+        }
+    }
+
+    pub fn exec(&self, input_file: PathBuf) {
+        ()
+    }
+}

src/commands/teardown.rs

@@ -0,0 +1,22 @@
+use std::path::PathBuf;
+use clap::{self, Clap};
+
+#[derive(Clap, Debug)]
+pub struct Teardown {
+    /// Network namespace path
+    #[clap(forbid_empty_values = true, required = true)]
+    network_namespace_path: String,
+}
+
+impl Teardown {
+    /// The teardown command is the inverse of the setup command, undoing any configuration applied. Some interfaces may not be deleted (bridge interfaces, for example, will not be removed).
+    pub fn new(network_namespace_path: String) -> Self {
+        Self {
+            network_namespace_path,
+        }
+    }
+
+    pub fn exec(&self, input_file: PathBuf) {
+        ()
+    }
+}

src/lib.rs

@@ -0,0 +1 @@
+pub mod commands;