Commit 6da0f9e0 authored by matze's avatar matze

__lxc_container: updated todo.txt about type splitting

Because it will get a mess when adding every option to __lxc_container
..
parent 2b97e08f
Pipeline #2750 passed with stage
in 1 minute and 5 seconds
# List of all featues that should be implemented
template:
template (common parameters):
- type: a.E. debian, ubuntu -> what on change?
- possible root_password?
- possible packages?
......@@ -7,10 +7,27 @@ template:
auto.. (lxc autostart):
- group
- start
handling networking?
- address
- bridge? (at default file?)
config:
- remove whole sections
- keep prettier config files?
- own type for config?
does it conflict with the current one?
own __lxc_default type?
`lxc-config lxc.default_config`
without lxcpath cause singleton?
Splitting up type? (all times the library question :-) )
__lxc_container (umbrella; creating,cloning,destroying??)
__lxc_container_config (single key-values)
__lxc_container_state (only running,freezed,stopped??)
__lxc_container_network
__lxc_container_mount
...
All common library files (except explorer things sadly) could be kept under __lxc_container.
if multi-valued object ids come to be a thing, following pattern is also used internal at lxc:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment