Contributing to LXD

[stgraber (Stéphane Graber)]

Opportunistic issues (no deadline currently set):

• nftables support for firewalling rules
  • Assigned: yes
  • Size: medium
  • Knowledge: firewall (iptables, ebtables, nft), networking (ipv4, ipv6), Go packages
• Implement background process manager
  • Assigned: yes
  • Size: large
  • Knowledge: Linux processes, Go packages
• Uevent based hotplug support for unix-char/unix-block
  • Assigned: yes
  • Size: large
  • Knowledge: Linux device events, LXD container configuration
• Allow for striped LVM storage volumes
  • Assigned: yes
  • Size: small
  • Knowledge: LVM storage, LXD storage configuration
• Passwordless PKI mode (with CRL to revocation)
  • Assigned: yes
  • Size: medium
  • Knowledge: Certificate Authority, TLS, LXD server configuration
• Multi-architecture clustering
  • Assigned: yes
  • Size: small
  • Knowledge: LXD clustering, database, API
• Automatic snapshot and expiry for custom storage volumes
  • Assigned: no
  • Size: medium
  • Knowledge: LXD storage, database, API

Issue on our current roadmap (deadline for those is end of October):

• Rework event distribution
  • Assigned: yes
  • Size: medium
  • Knowledge: LXD clustering, event logic and API
• Storage volumes in projects
  • Assigned: no
  • Size: large
  • Knowledge: LXD projects, storage volumes, container configuration and API

Issue early on next roadmap (deadline for those is end of January)

• Restrictions for projects
  • Assigned: yes
  • Size: large
  • Knowledge: LXD projects, database, containers and API
• Limits (quotas) for projects
  • Assigned: yes
  • Size: large
  • Knowledge: Linux Cgroups, LXD projects, database, containers and API

I’ve sorted those lists in what would be our (upstream) order of preference for those based on how useful we feel each of those would be to our users. I’ve also indicated which have been assigned to UT Austin students already. The Knowledge field attempts to quickly describe the areas affected by the issue and knowledge that would be acquired by working on it.

Once you decide to work on one of those issues, have every one of your team members comment in the associated Github issue so we can assign the issue to your group. That will also signal us that we should provide as many details as we can think of in the issue to try and make your life a bit easier

Feel free to directly reach out to me with any question you may have: stgraber at ubuntu dot com