LXC - test the Go bindings
Test the Go bindings for LXC, especially for suitability for use by juju.
[GOAL]
Determine whether the existing lxc api Go bindings suffice for use by juju.
[RATIONALE]
The lxc api and its bindings have been written so that the same core lxc code could be used by many projects (libvirt, juju, arkose, etc). At a previous UDS there had been concerns that threading in lxc would prevent the API from being used by juju. It woudl be good to test this and, if there are problems, look into solutions. This would be far preferable to having reimplementation of lxc features.
Blueprint information
- Status:
- Not started
- Approver:
- Antonio Rosales
- Priority:
- Undefined
- Drafter:
- Serge Hallyn
- Direction:
- Needs approval
- Assignee:
- Serge Hallyn
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Informational
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
[USER STORIES]
Joe is writing a Go program to snapshot and start containers. Rather than re-implement containers functionality or calling out to the lxc-* programs, he'd like to use the native Go API bindings for liblxc.
[ASSUMPTIONS]
The existing Go bindings work (or mostly work).
[RISKS]
The Go implementation may cause problems with calling out to C code which then clones a container. That is precisely a part of what we need to test.
