Commit 4021b274 authored by benoit manager's avatar benoit manager

Merge branch 'argonaut-1.2-fixes' into 'master'

Argonaut 1.2 fixes

See merge request argonaut/argonaut!88
parents 39a89073 b222924a
# Specify docker image
image: debian:stretch
# Define variable to disable SSL verification of GIT
variables:
GIT_SSL_NO_VERIFY: "true"
stages:
- test-perl
- test-manpages
- tarballs
# Generate perlcritic rapport
create_perlcritic_rapport:
stage: test-perl
only:
- branches
- tags
before_script:
- apt-get update -qq
- apt-get install -y -qq libperl-critic-perl
script:
- perlcritic .
# Perl lint
create_perl_lint_rapport:
stage: test-perl
only:
- branches
- tags
before_script:
- apt-get update -qq
- apt-get install -y -qq libapp-daemon-perl libconfig-inifiles-perl libdigest-sha-perl libfile-pid-perl libio-socket-ssl-perl
- apt-get install -y -qq libjson-perl libjson-rpc-perl liblog-handler-perl libmodule-pluggable-perl libnet-ldap-perl libpath-class-perl libxml-sax-expatxs-perl
- apt-get install -y -qq bind9utils libdns-zoneparse-perl
- apt-get install -y -qq libquota-perl
- apt-get install -y -qq libdatetime-perl libpoe-perl libpoe-component-pool-thread-perl libpoe-component-schedule-perl libpoe-component-server-jsonrpc-perl libpoe-component-server-simplehttp-perl libpoe-component-sslify-perl
- apt-get install -y -qq libhttp-daemon-ssl-perl
- apt-get install -y -qq fuse libfuse-perl
- apt-get install -y -qq debmirror libwww-perl
- apt-get install -y -qq libmail-sendmail-perl
- apt-get install -y -qq libfile-slurp-perl libdigest-perl-md5-perl
script:
- find . -type f -name '*.pm' -print0 | xargs -0 -n1 perl -cw -I argonaut-ldap2zone -I argonaut-common
# generate man pages to test validity
test_manpages:
stage: test-manpages
only:
- branches
- tags
before_script:
- apt-get update -qq
- apt-get install -y -qq perl man-db
script:
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-client/bin/argonaut-client argonaut-client/man/argonaut-client.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-common/man/argonaut.conf.pod argonaut-common/man/argonaut.conf.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fai-mirror/bin/argonaut-debconf-crawler argonaut-fai-mirror/man/argonaut-debconf-crawler.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fai-mirror/bin/argonaut-repository argonaut-fai-mirror/man/argonaut-repository.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fai-monitor/bin/argonaut-fai-monitor argonaut-fai-monitor/man/argonaut-fai-monitor.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fai-nfsroot/bin/argonaut-ldap2fai argonaut-fai-nfsroot/man/argonaut-ldap2fai.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fai-server/bin/fai2ldif argonaut-fai-server/man/fai2ldif.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fai-server/bin/yumgroup2yumi argonaut-fai-server/man/yumgroup2yumi.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fuse/bin/argonaut-fuse argonaut-fuse/man/argonaut-fuse.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fusiondirectory/bin/argonaut-clean-audit argonaut-fusiondirectory/man/argonaut-clean-audit.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-fusiondirectory/bin/argonaut-user-reminder argonaut-fusiondirectory/man/argonaut-user-reminder.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-ldap2zone/bin/argonaut-ldap2zone argonaut-ldap2zone/man/argonaut-ldap2zone.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-quota/bin/argonaut-quota argonaut-quota/man/argonaut-quota.1
- pod2man -c "Argonaut Documentation" -r "Argonaut 1.3" argonaut-server/bin/argonaut-server argonaut-server/man/argonaut-server.1
- lexgrog argonaut-client/man/argonaut-client.1
- lexgrog argonaut-common/man/argonaut.conf.1
- lexgrog argonaut-fai-mirror/man/argonaut-debconf-crawler.1
- lexgrog argonaut-fai-mirror/man/argonaut-repository.1
- lexgrog argonaut-fai-monitor/man/argonaut-fai-monitor.1
- lexgrog argonaut-fai-nfsroot/man/argonaut-ldap2fai.1
- lexgrog argonaut-fai-server/man/fai2ldif.1
- lexgrog argonaut-fai-server/man/yumgroup2yumi.1
- lexgrog argonaut-fuse/man/argonaut-fuse.1
- lexgrog argonaut-fusiondirectory/man/argonaut-clean-audit.1
- lexgrog argonaut-fusiondirectory/man/argonaut-user-reminder.1
- lexgrog argonaut-ldap2zone/man/argonaut-ldap2zone.1
- lexgrog argonaut-quota/man/argonaut-quota.1
- lexgrog argonaut-server/man/argonaut-server.1
build-tarballs:
stage: tarballs
script:
- tar -cvzf argonaut.tar.gz *
artifacts:
paths:
- argonaut.tar.gz
expire_in: 1h
build-release:
stage: tarballs
only:
- tags
script:
- tar -cvzf argonaut-$(grep '%' Changelog.md | head -n1 | cut -d ' ' -f3 | tr -d '"').tar.gz *
artifacts:
paths:
- argonaut-$(grep '%' Changelog.md | head -n1 | cut -d ' ' -f3 | tr -d '"').tar.gz
### Requirements
* Filling out the template is required. Any Enhancement request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
* All new code requires tests to ensure against regressions
## Descriptive title for this contribution
<!-- required -->
### Step by step description of this contribution
<!-- Required -->
1. [First Step]
2. [Second Step]
3. [and so on...]
### Does this contribution need a new FusionDirectory plugin
<!-- Name and ticket number of the FusionDirectory plugin associated -->
### Benefits
<!-- Required -->
<!-- What benefits will be realized with this contribution ? -->
### Possible Drawbacks
<!-- optional -->
<!-- What are the possible side-effects or negative impacts of this contribution ? -->
### Actual use cases
<!-- optional -->
<!-- Enter any applicable Issues here -->
### Requirements
* Filling out the template is required. Any Enhancement request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
* All new code requires tests to ensure against regressions
## Descriptive title for this enhancement
<!-- required -->
### Actual behavior
<!-- What actually happens -->
### Expected behavior
<!-- What you expect to happen-->
### Step by step description of new behaviour
<!-- Required -->
1. [First Step]
2. [Second Step]
3. [and so on...]
### Benefits
<!-- optional -->
<!-- What benefits will be realized by the code change? -->
### Possible Drawbacks
<!-- optional -->
<!-- What are the possible side-effects or negative impacts of the code change? -->
### Applicable Issues
<!-- optional -->
<!-- Enter any applicable Issues here -->
# Contributor Covenant Code of Conduct
## Our Pledge
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to making participation in our project and
our community a harassment-free experience for everyone, regardless of age, body
size, disability, ethnicity, gender identity and expression, level of experience,
nationality, personal appearance, race, religion, or sexual identity and
orientation.
## Our Standards
Examples of behavior that contributes to creating a positive environment
include:
* Using welcoming and inclusive language
* Being respectful of differing viewpoints and experiences
* Gracefully accepting constructive criticism
* Focusing on what is best for the community
* Showing empathy towards other community members
Examples of unacceptable behavior by participants include:
* The use of sexualized language or imagery and unwelcome sexual attention or
advances
* Trolling, insulting/derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or electronic
address, without explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting
## Our Responsibilities
Project maintainers are responsible for clarifying the standards of acceptable
behavior and are expected to take appropriate and fair corrective action in
response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned to this Code of Conduct, or to ban temporarily or
permanently any contributor for other behaviors that they deem inappropriate,
threatening, offensive, or harmful.
## Scope
This Code of Conduct applies both within project spaces and in public spaces
when an individual is representing the project or its community. Examples of
representing a project or community include using an official project e-mail
address, posting via an official social media account, or acting as an appointed
representative at an online or offline event. Representation of a project may be
further defined and clarified by project maintainers.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at <coc@fusiondirectory.org>. All
complaints will be reviewed and investigated and will result in a response that
is deemed necessary and appropriate to the circumstances. The project team is
obligated to maintain confidentiality with regard to the reporter of an incident.
Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good
faith may face temporary or permanent repercussions as determined by other
members of the project's leadership.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
available at [https://www.contributor-covenant.org/version/1/4][version]
[homepage]: https://www.contributor-covenant.org
[version]: https://www.contributor-covenant.org/version/1/4/
# Contributing to FusionDirectory projects
## Table Of Contents
1. [Welcome](#Welcome)
2. [Code of Conduct](#code-of-conduct)
3. [I just have a question!](#i-just-have-a-question)
4. [How Can I Contribute?](#how-can-i-contribute)
* [Finding Wonderful Bugs](#finding-wonderful-bugs)
* [Any Feedback To Enhance Our Apps](#any-feedback-to-enhance-our-apps)
* [Your Awesome And Mighty Codes Contributions](#your-awesome-and-mighty-codes-contributions)
5. [Coding with style](#coding-with-style)
* [Git Commit Messages](#git-commit-messages)
6. [Licensing](#licensing)
---
## Welcome
> «Here's a list of our guidelines, If you want to share a best practice, or think one of these guidelines should be removed, feel free to share it with us.»
:tada: First off, thanks for taking the time to contribute!
Now, sit comfortably at the fireplace, grab your glasses and immerse yourself in our documentation.
## Code Of Conduct
All projects and everyone participating in it is governed by [FusionDirectory Code Of Conduct](./CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please read this before.
## I just have a question!
> **Note:** Please don't file an issue to ask a question. You'll get faster results by using the resource below.
We have an various channel of communications
* [#fusiondirectory, the irc channel of FusionDirectory on freenode](https://webchat.freenode.net/), channel #fusiondirectory
* [FusionDirectory Users mailing list](https://lists.fusiondirectory.org/wws/info/users)
* [FusionDirectory dev mailing list](https://lists.fusiondirectory.org/wws/info/developpers)
## How Can I Contribute?
So, you've developed a new cool feature? Fixed an annoying bug? Found a mistake? We'd be happy to hear from you! :+1:
### Register for a FusionDirectory project account
To create a FusionDirectory project Account you must go to
* [FusionDirectory Sign UP](https://register.fusiondirectory.org)
### Put Argonaut in debug mode
* Stop the service if it is running
* Start in console with -v to get more log
* Start with -X if you want it to be in foreground and send logging to console
### Finding Wonderful Bugs
>This section guides you through submitting a bug report. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
When you are creating a bug report, please include as many details as possible. Fill out the **Bugs** template to create issues, the information it asks for helps us resolve issues faster.
Explain the problem and include additional details to help maintainers reproduce the problem:
* **Use a clear and descriptive title** for the issue to identify the problem.
* **Describe the exact steps which reproduce the problem** in as many details as possible.
* **Describe the behavior** you observed after following the steps and point out what exactly is the problem with that behavior.
* **Explain which behavior** you expected to see instead and why.
* **Include screenshots and animated GIFs** which show you following the described steps and clearly demonstrate the problem. You can use [this tool](http://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and this tool or [this tool](https://github.com/GNOME/byzanz) on Linux.
* **Include the Perl errors and trace** collected at the debug step above
* **If the problem is linked to a specific LDAP entry** attach its LDAP dump.
Fill in a report on :
* [Argonaut](https://gitlab.fusiondirectory.org/argonaut/argonaut/issues)
### Any Feedback To Enhance FusionDirectory
>This section guides you through submitting an enhancement suggestion, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion and find related suggestions.
When you are creating a enhancement report, please include as many details as possible. Fill out the **Enhancement** template to create thoses issues, the information it asks for helps us resolve issues faster.
* [Argonaut](https://gitlab.fusiondirectory.org/argonaut/argonaut/issues)
* **Use a clear and descriptive title** for the issue to identify the suggestion.
* **Provide a step-by-step description of the suggested enhancement** in as many details as possible.
* **Describe the current behavior** and **explain which behavior you expected to see instead** and why.
* **Include screenshots and animated GIFs** which help you demonstrate the steps which the suggestion is related to. You can use [this tool](http://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux.
* **Explain why this enhancement would be useful** to most Argonaut users.
### Your awesome And Mighty Codes Contributions
>This section guides you through submitting an enhancement suggestion, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion and find related suggestions.
When you are contributing a new fonctionnality or plugin, please include as many details as possible.
Fill out the **Contribution** template to create thoses issues, the information it asks for helps us resolve issues faster.
* [Argonaut](https://gitlab.fusiondirectory.org/argonaut/argonaut/issues)
* **Use a clear and descriptive title** for the issue to identify your contribution
* **Provide a step-by-step description of the contribution** in as many details as possible.
* **Include screenshots and animated GIFs** which help you demonstrate what this contribution is about. You can use [this tool](http://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux.
* **Explain why this contribution would be useful** to most Argonaut users.
* **Run** [Perl critic](https://metacpan.org/pod/Perl::Critic) on your code.
## Coding with style
### Git Commit Messages
>Having a good guideline for creating commits and sticking to it makes working with Git and collaborating with others a lot easier.
Here are some rules of thumb :
* Use the present tense ("Add feature" not "Added feature")
* If you have a body, separate the subject from the body with a newline
* Limit the subject line to 72 characters
* Do not end the subject line with a period
* Use imperative [mood](https://en.wikipedia.org/wiki/Imperative_mood#English) in the subject line
* If the subject is not clear enough, use the body to explain what and why as opposed to how
* Consider starting the commit message with an applicable emoji, when you feel it's an important commit :
* :tada: When first / initial commit
* :sparkles: When introducing new features
* :ambulance: When fixing a bug
* :handshake: When merging files
* :tractor: When you changing file structure or refactoring
* :books: When writing docs
* :gem: When new Release
* :lipstick: For cosmetics purposes
#### Commit Message Format
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes a **type**, a **scope** and a **subject**:
```
<emoji> <type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
```
The **header** is mandatory and the **scope** of the header is optional.
Where type can be :
* **feat**: A new feature
* **fix**: A bug fix
* **core**: Code for the Core
* **docs**: Documenting the code or writing new documentation
* **style**: Cosmetics purpose
* **test**: Adding missing or correcting tests
Examples:
```
:sparkles: feat(supann): Make supannRefId multivaluated
supannRefId on Structure object is too small and mono valued
close #5685
```
## Licensing
For all new projects and most of older one we use **GPL2+ License**. You can find it [here](../LICENSE.md).
Make sure to use resources that we have the rights to use. Copyrighted images and videos may cause legal problems.
---
This document is strongly inspired by the following resources: [ovh-ux-guidelines
](https://github.com/ovh-ux/ovh-ux-guidelines), [project-guidelines](https://github.com/wearehive/project-guidelines), [Atom Guidelines](https://github.com/atom/atom/blob/master/CONTRIBUTING.md#reporting-bugs), [Angularjs guidelines](https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md).
With love :heart:
## %"Argonaut 1.2.1" - 2018-04-20
### Added
#### argonaut
- argonaut#5695 No manpage is available for argonaut.conf
### Changed
#### argonaut
- argonaut#5690 Use ##no critic to desactive perlcritic on modules names not exactly the same as files names
- argonaut#5710 Support UTF-8 in user-reminder
- argonaut#5717 Change the url for the bug tracker into the argonaut manpages
### Removed
#### argonaut
- argonaut#5691 Remove the agent ldap backend for fusioninventory
### Fixed
#### argonaut
- argonaut#5679 Crash of argonaut-ldap2zone --slave when Ldap2zone slave list is empty on a DNS argonaut service
- argonaut#5681 argonaut-server is crashing on Debian Stretch
- argonaut#5693 add missing use if for json library selection
- argonaut#5696 argonaut-ldap2zone does not take the right SOA when refreshing a zone and its reverse
- argonaut#5700 argonaut-user-reminder has errors in ppolicy mode
- argonaut#5722 Error when we use argonaut-user-reminder
## %"Argonaut 1.2" - 2018-04-20
### Added
#### argonaut
- argonaut#5635 Document argonaut-client -X
### Changed
#### argonaut
- argonaut#5646 changing the library used to send mail in argonaut-user-reminder
### Fixed
#### argonaut
- argonaut#5402 documentation should explain limits of user-reminder with ppolicy
- argonaut#5513 netboot stayed in uninstall state
- argonaut#5523 Periodical schedule is not repeated
- argonaut#5541 Errors when trying to schedule actions
- argonaut#5544 Periodical jobs miss the first launch
- argonaut#5546 OPSI update software stay in deployement queue with "in progress" status
- argonaut#5558 Use some trim on argonaut.conf
- argonaut#5559 Argonaut client and server systemd service definition fails
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
Copyright (C) 1989, 1991 Free Software Foundation, Inc., <http://fsf.org/>
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
......@@ -15,7 +15,7 @@ software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
the GNU Lesser General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
......@@ -56,7 +56,6 @@ patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
......@@ -112,7 +111,6 @@ above, provided that you also meet all of these conditions:
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
......@@ -171,7 +169,6 @@ access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
......@@ -229,7 +226,6 @@ impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
......@@ -282,3 +278,62 @@ PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
fusiondirectory
Copyright (C) 2017 fusiondirectory
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License along
with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
{signature of Ty Coon}, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License.
......@@ -4,38 +4,55 @@
[Argonaut][Argonaut] is an effective tool for managing services, systems, task.
Integrate Argonaut with your own tools or with deployment tools like [FAI], [OPSI], Debconf.
Integrate Argonaut with [FusionDirectory], your own tools or with deployment tools like [FAI], [OPSI], Debconf.
## Features
Argonaut is a modular client/server system based on JSON-RPCprotocol. Both client and server sides can load modules at start. Argonaut has two primary functions.
Argonaut is a modular client/server system based on JSON-RPC protocol. Both client and server sides can load modules at start. Argonaut has many functions.
### Run a given operation on a system through a client
Two basic functions: restart service and switch on/off a system.
Modules can provide some more functionalities :
Argonaut server and argonaut client can booth load modules at startup
* argonaut-ldap2zone: update a dns zone, create view, create acls
* argonaut-quota: apply a quota
* argonaut-fai-mirror: create a synchronization script Mirror
* argonaut-fai-monitor: follow FAI installation and report states to FusionDirectory
* argonaut-dovecot: create the mailbox quota and applies it
* argonaut-user-reminder : to manage the accoun reminder plugin of FusionDirectory
* argonaut-clean-audit : to clean the audit branch of FusionDirectory
* argonaut-user-reminder : to send email reminder coordonated with the user-reminder plugin of FusionDirectory
### Integration with [FusionDirectory] and Services
### Allow integration with deployment tools [FAI], [OPSI], Debconf
* Services modules :
* argonaut-dovecot: Create the directory needed by dovecot to create the mailbox
* argonaut-ldap2zone: Create, update dns zones, create views, create acls
* argonaut-quota: Apply a file quota
* argonaut-samba : Create share from ldap information stored in FusionDirectory
### Integration with [FusionDirectory]
* argonaut-clean-audit : Clean the audit branch of FusionDirectory
* argonaut-user-reminder : Send an email reminder coordinated with the user-reminder plugin of FusionDirectory
### Integration with deployment tools [FAI], [OPSI], Debconf
* Deployment systems modules :
* argonaut-fai-mirror: Create a local mirror with the help of *argonaut-debconf-crawler* and *argonaut-repository*
* argonaut-fai-monitor : Monitor FAI installation and report states to FusionDirectory
* argonaut-fai-nfsroot : Integrate Argonaut into the FAI nfsroot
* argonaut-fai-server : Contains fai2ldif to create ldif from FAI text classes and yumgroup2yumi for creating in ldif the yum groups for centos/rhel deployment
* Intelligent PXE Management :
* argonaut-fuse : Get information and create pxelinux.cfg file that matches the type of machine to be deployed directly from LDAP, allowing automatic boot during an install by pxe
* argonaut-fuse-fai-module : Read Information from the fai tab of a system in FusionDirectory
* argonaut-fuse-opsi-module : Read Information from the opsi tab of a system in FusionDirectory an talk to the opsi webservice
* FAI integration (argonaut-server-module-fai and argonaut-common-fai) and the complement to integrate into the nfsroot and FAI server (argonaut-fai-nfsroot argonaut-fai-server, argonaut-fai-mirror)
* OPSI integration (argonaut-server-module-opsi)
* Manage the pxelinux.cfg directory using argonaut-fuse (argonaut-fuse-fai-module and argonaut-fuse-opsi-module): get information and create pxelinux.cfg file that matches the type of machine to be deployed, allowing automatic boot during an install by pxe
## Get help
There are a couple ways you can try [to get help][get help].You can also join the `#fusiondirectory` IRC channel at freenode.net.
You can [register on our system][register] and enter your bug [on the forge][issues-forge] or [here at github][issues-github] even if the forge is the prefered way of dealing with bugs
You can [register on our system][register] and enter issues [Argonaut][issues-core].
## IRC Etiquette
......@@ -60,13 +77,12 @@ If you like [Argonaut][Argonaut] and would like to [donate][donate-liberapay] ev
[OPSI]: http://opsi.org/en/
[FusionDirectory]: https://www.fusiondirectory.org/
[get help]: https://www.fusiondirectory.org/contact-us/
[register]: https://register.fusiondirectory.org
[issues-forge]: https://forge.fusiondirectory.org/projects/argonaut-agents/issues/new
[issues-github]: https://github.com/fusiondirectory/argonaut/issues
[issues-core]: https://gitlab.fusiondirectory.org/argonaut/argonaut/issues
[donate-liberapay]: https://liberapay.com/fusiondirectory/donate
......@@ -23,8 +23,12 @@
#
#######################################################################
## no critic
package Argonaut::ClientDaemon::Modules::Service;
## use critic
use strict;
use warnings;
......
......@@ -23,8 +23,12 @@
#
#######################################################################
## no critic
package Argonaut::ClientDaemon::Modules::System;
## use critic
use strict;
use warnings;
......
......@@ -23,8 +23,12 @@
#
#######################################################################
## no critic
package Argonaut::ClientDaemon::Modules::Service;
## use critic
use strict;
use warnings;
......
......@@ -23,8 +23,12 @@
#
#######################################################################
## no critic
package Argonaut::ClientDaemon::Modules::System;
## use critic
use strict;
use warnings;
......
......@@ -4,7 +4,7 @@
#
# argonaut-client-management - standalone binary
#
# Copyright (C) 2011-2016 FusionDirectory project
# Copyright (C) 2011-2018 FusionDirectory project
#
# Author: Côme BERNIGAUD
#
......@@ -141,7 +141,7 @@ and can load various modules at run time.
=head1 BUGS
Please report any bugs, or post any suggestions, to the fusiondirectory mailing list fusiondirectory-users or to
<https://forge.fusiondirectory.org/projects/argonaut-agents/issues/new>
<https://gitlab.fusiondirectory.org/argonaut/argonaut/issues/new>
=head1 LICENCE AND COPYRIGHT