Add support for a LXD backend to Libertine

Bug #1580612 reported by Christopher Townsend
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Libertine
Status tracked in Devel
Devel
Fix Released
Medium
Larry Price
Trunk
Fix Released
Medium
Larry Price
libertine (Ubuntu)
Fix Released
Medium
Larry Price

Bug Description

Need to investigate the feasibility of using an LXD backend in Libertine.

1. Need to see if it's possible to have all of the bind-mounts we need.
2. LXD seems to have much better reporting of various statuses [0]
3. LXD uses a basic REST API for interacting with the LXD daemon [0]
4. ???

[0] https://www.stgraber.org/2016/04/18/lxd-api-direct-interaction/

Related branches

Changed in libertine:
importance: Undecided → Low
assignee: nobody → Christopher Townsend (townsend)
status: New → Triaged
Revision history for this message
Christopher Townsend (townsend) wrote :

After quite a bit of investigation, I found that there is already a python3-pylxd API in development by the maintainers of LXD. Instead of rolling our own API and duplicate work, we should use that instead.

However, one of the most important pieces is missing form pylxd- the actual executing of commands inside the LXD container. There is a very minimal exec function, but offers no process control nor any access to stdin, stdout, and stderr. There is a comment in that part of the pylxd code that says it needs to be expanded in the future.

I think we should wait on pylxd to mature some more before moving forward with this.

Changed in libertine:
milestone: none → 1.2
Changed in libertine:
milestone: 1.2 → 1.3
Changed in libertine:
milestone: 1.3 → 1.4
Changed in libertine:
milestone: 1.4 → 1.5
Changed in libertine (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Libertine CI Bot (libertine-ci-bot) wrote :

Fix committed into lp:libertine at revision None, scheduled for release in libertine, milestone Unknown

Changed in libertine:
status: In Progress → Fix Committed
Changed in libertine (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Larry Price (larryprice)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libertine - 1.5+17.04.20170105.1-0ubuntu1

---------------
libertine (1.5+17.04.20170105.1-0ubuntu1) zesty; urgency=medium

  [ Chris Townsend ]
  * Drop support for the Puritine click package as that is Vivid only
    and a Vivid Libertine branch exists for any future fixes.
  * Only set the lxc log when a container is defined during class init.
    (LP: #1653973)
  * Bump version to 1.5 for new upstream release.

  [ Larry Price ]
  * Logic for bundling libertine as a snap built from source.
  * Catch exceptions raised during container creation.
  * Initial implementation of lxd backend. (LP: #1580612)
  * Use the libertine logger and LIBERTINE_DEBUG variable everywhere.
  * Update configure bind-mount logic given new lxd backend.
  * Use dpkg to find package name when installing local deb.
  * Create d-bus service for lxd container management.

 -- Christopher Townsend <email address hidden> Thu, 05 Jan 2017 20:20:33 +0000

Changed in libertine (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.