Update the roadmap to reflect the current state

README.md

@@ -227,8 +227,8 @@ Other interesting resources include:
 
 - [The issue tracker](https://github.com/weaveworks/ignite/issues)
 - [The list of milestones](https://github.com/weaveworks/ignite/milestones)
+- [The Roadmap](docs/roadmap.md)
 - [CHANGELOG.md](CHANGELOG.md)
-- [ROADMAP.md](ROADMAP.md)
 
 ## Getting Help
 

docs/index.rst

@@ -25,6 +25,7 @@ In this folder you can read more about how to use Ignite, and how it works:
    awesome
    cloudprovider
    devel
+   roadmap
    FAQ
 
 .. toctree::

docs/roadmap.md

@@ -0,0 +1,22 @@
+# Roadmap
+
+This is a provisional roadmap for what we'd like to do in the coming releases.
+
+- `containerd` support as a backing container runtime
+  - We might switch this to be the default, once the implementation is stable
+- Split the `ignite` CLI into a client-server model
+  - The CLI should only be a thin wrapper that talks to `ignited`
+  - With this `ignite` can be run without root
+  - `ignited` will be run with `root` privileges, or in a container with capabilities specifically set
+- Add Virtual Kubelet support to `ignited`
+  - `ignited` will register as a Virtual Kubelet in the target Kubernetes cluster
+  - The `VM` API type will be register as a `CustomResourceDefinition`
+- Use device-mapper Thin Provisioning for layering image -> kernel -> resize -> writable overlay
+  - We might be able to utilize/vendor in containerd's devicemapper snapshotter
+- Parallelized internal architecture for better performance
+- Generate OpenAPI documentation and specifications
+- Add support for CSI volumes
+- Define what's in and out of scope for Ignite clearly, e.g.
+  - Supporting to restart VMs or not
+  - Supporting multiple network interfaces or not
+- Provide deb/rpm packages