TODO 1.6 KB
Newer Older
Daniel Walsh's avatar
Daniel Walsh committed
1 2
	 libvirt-sandbox TODO list
	 =================
3

Daniel Walsh's avatar
Daniel Walsh committed
4
systemd-tmpfiles --create needs to be run within the container, before any
5
apps are started, since it will populate /run (Completed)
6 7 8 9

CGROUPFS: integration so libvirt does it rather then systemd within the container
	 We need kernel labeling support for cgroupfs so we can allow systemd to write to its section of the cgroupfs.

Daniel Walsh's avatar
Daniel Walsh committed
10
SYSLOG:  Currently syslog messages are going no where within the container.
11
If we run a syslog within the container will it get messages from the outside?  Should we just use systemd-journal.  I think sysadmins will want to be able to look in /var/log/messages within the container. (systemd-journal is now running within a container)
12 13

EXECUTE:
14
	virt-sandbox-service execute --command "BLAH" does not work.  We need to have the ability to execute any random command within the container, and get stdin, stdout, stderror outside the container. (Partially Completed)
Alex Jia's avatar
Alex Jia committed
15
Still needs kernel to implement missing container namespace files under /proc/PID/ns, Also need a mechanism to get the PID of systemd from libvirt.
16 17

HOSTNAME:
Alex Jia's avatar
Alex Jia committed
18
	Currently if I execute hostname within the container it sees the name of the host not the name based on the container name or the IP Address associated with dhclient. (Completed)
19 20 21 22

virt-sandbox-service connect NAME hangs when you attempt to end the connection.
^d should bring you back to the host terminal.

Daniel Walsh's avatar
Daniel Walsh committed
23
Need a mechanism to allow admins to specify additional services to run within
24
the container.  For example you may want to run mysql and apache within the same container. (Completed) You can do this using systemctl enabel BLAH