Actions
User story #1205
closed
Techniques to implement
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
Ideas from Bruno Bonfils:
- sudo
- LDAP authentification for servers
- NFS server configuration
- User management
- Routing management
- SNMP server
- automount?
- Configure services to listen only on one interface (by IP address), ideally by choosing it in a drop down list that comes from the inventory
- add IP to network interface / configure networks
Updated by Jonathan CLARKE over 13 years ago
- Project changed from Rudder to 24
- Status changed from Discussion to New
Updated by François ARMAND about 13 years ago
- Target version changed from 10 to 18
Updated by François ARMAND about 13 years ago
- Target version changed from 18 to 24
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 24 to Ideas (not version specific)
Updated by François ARMAND almost 12 years ago
- Subject changed from Policy templates to implement to Techniques to implement
- Description updated (diff)
- Status changed from New to Discussion
- Assignee set to Jonathan CLARKE
Perhaps it would be easier to have one user story for each Technique ?
Updated by Jonathan CLARKE almost 12 years ago
- Assignee changed from Jonathan CLARKE to François ARMAND
François ARMAND wrote:
Perhaps it would be easier to have one user story for each Technique ?
Definitely! Feel free to break out my quick notes into real tickets :)
Updated by Dennis Cabooter over 11 years ago
- Execute a command based on output of another command
Updated by Benoît PECCATTE almost 10 years ago
- Project changed from 24 to Rudder
- Category set to Techniques
Updated by François ARMAND almost 7 years ago
- Status changed from Discussion to Rejected
Closing these ones. All these technique would be better handled with the technique editor, they don't match the generecity we want in the std user lib.
Actions