-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for swap management #106
Comments
@gavenkoa The management of /etc/fstab is made by the mount module. I think this module should just manage activiation (swapon/off) and format (mkswap) |
* Declare functions swapon() & swapoff(), is_swap() & reswap(). * Apply swapon/swapoff for states mounted, unmounted, remounted and absent. * Move 'swap' related test cases into dedicated file (swap.yml) * Add new test cases about swap enabling/disabling * Update documentation
* Declare functions swapon() & swapoff(), is_swap() & reswap(). * Apply swapon/swapoff for states mounted, unmounted, remounted and absent. * Move 'swap' related test cases into dedicated file (swap.yml) * Add new test cases about swap enabling/disabling * Update documentation
* Declare functions swapon() & swapoff(), is_swap() & reswap(). * Apply swapon/swapoff for states mounted, unmounted, remounted and absent. * Move 'swap' related test cases into dedicated file (swap.yml) * Add new test cases about swap enabling/disabling * Update documentation
* Declare functions swapon() & swapoff(), is_swap() & reswap(). * Apply swapon/swapoff for states mounted, unmounted, remounted and absent. * Move 'swap' related test cases into dedicated file (swap.yml) * Add new test cases about swap enabling/disabling * Update documentation
* Declare functions swapon() & swapoff(), is_swap() & reswap(). * Apply swapon/swapoff for states mounted, unmounted, remounted and absent. * Move 'swap' related test cases into dedicated file (swap.yml) * Add new test cases about swap enabling/disabling * Update documentation
* Declare functions swapon() & swapoff(), is_swap() & reswap(). * Apply swapon/swapoff for states mounted, unmounted, remounted and absent. * Move 'swap' related test cases into dedicated file (swap.yml) * Add new test cases about swap enabling/disabling * Update documentation
* Declare functions swapon() & swapoff(), is_swap() & reswap(). * Apply swapon/swapoff for states mounted, unmounted, remounted and absent. * Move 'swap' related test cases into dedicated file (swap.yml) * Add new test cases about swap enabling/disabling * Update documentation
* Declare functions swapon() & swapoff(), is_swap() & reswap(). * Apply swapon/swapoff for states mounted, unmounted, remounted and absent. * Override default opts and boot when fstype=swap. * Do not honor 'fstab' when fstype=swap (fail instead). * Also fail when fstype=swap and 'path' is not 'none' ('-' for Solaris). * Update module documentation accordingly. + Replace all platform.system() calls by a variable. refactor integration tests * Improve readability/understanding of what is tested, and what OS is targeted. * Move 'swap' related test cases into dedicated file (swap.yml). * Add new test cases about swap enabling/disabling. * Extend tests to FreeBSD when possible.
This was implemented in the |
Hi, it would be nice to see swap management implemented from begin to end, that is not currently the case. Getting swap online or offline after swap filesystem creation (with I've implemented such swapon and swapoff commands in the The good news are that the draft, that comes with new integration tests to ensure it does the job (swapon when state=mounted; swapoff when state=unmounted), does the job. The bad news is that I'm not satisfied with it (that may be good news too). The changes introduce a lot of code, and overall, many branches (if/else) to take a special care of For short, I think it would be better to have a dedicated |
There were tasks:
closed due to migration to collections.
Docs:
don't mention swap support. I believe it is not implemented.
There are two things here:
/etc/fstab
swapon
/swapoff
.The text was updated successfully, but these errors were encountered: