Commit graph

11 commits

Author SHA1 Message Date
Greg DeKoenigsberg
9180538277 Adding author's github id 2015-05-13 14:15:37 -04:00
Brian Coca
56f466c70d Merge pull request #328 from cloudnull/lxc-overlayfs-feature
Added overlayfs backend type to the lxc_container module
2015-05-13 14:01:23 -04:00
Brian Coca
bfb8868d8b Merge pull request #469 from sigmavirus24/lxc-bug-fix
Interpolate container name into error message
2015-05-13 14:00:37 -04:00
Toshio Kuratomi
a589a66710 Update module documentation if modules have a dep on python2.6+ 2015-05-11 10:09:56 -07:00
Ian Cordasco
deb11be684 Interpolate container name into error message
In the event failed to start, the container name was not being properly
interpolated into the error message.
2015-05-08 21:18:59 -05:00
Brian Coca
c5f787e6df Merge pull request #357 from bcoca/lxc_container_home_fix
Lxc container home fix
2015-03-30 22:12:11 -04:00
Brian Coca
ee7fbcf418 minor fix to method of finding home as previous could 'overmatch' 2015-03-30 22:11:17 -04:00
Kevin Carter
2f188600a8 Added overlayfs backend type to the lxc_container module
This commit adds the overlayfs type to the lxc_container module. In
Adding the overlayfs type the commit adds the ability to clone a
container. While cloning is not locked down to only the overlayfs
container backend it is of particular interest when using the overlayfs
backend as it provides for amazingly fast snapshots.

Changes to the resource types and documentation have been added on how
the new backend type can be used along with the clone operation.

This PR addresses a question asked on the original merged pull request
for overlayfs support which came from @fghaas on PR
"https://github.com/ansible/ansible-modules-extras/pull/123".

The overlayfs archive function is a first class function and will
allow for the containers to be backed-up using all methods which
brings support up to that of all other storage backends.
2015-03-23 19:31:03 -05:00
Kevin Carter
24cfcd2497 Updated lxc_container module to fix option parsing
The option parsing object within the module was performing a split
on an '=' sign and assuming that there would only ever be one '='
in a user provided option. Sadly, the assumption is incorrect and
the list comprehension that is building the options list needs to
be set to split on the first occurrence of an '=' sign in a given
option string. This commit adds the required change to make it
possible for options to contain additional '=' signs and be handled
correctly.
2015-03-18 23:33:33 -05:00
Brian Coca
bb886a595d updated lxc-containter docs to reflect new name 2015-02-27 09:19:51 -05:00
Maciej Delmanowski
528e1a644c Rename 'lxc-container' module to 'lxc_container'
This is done to keep the convention of naming modules with underscores
instead of hypens.
2015-02-27 13:00:49 +01:00
Renamed from cloud/lxc/lxc-container.py (Browse further)