Lustre Kerberos: Difference between revisions
Jump to navigation
Jump to search
| Line 24: | Line 24: | ||
=Comments on the Code= | =Comments on the Code= | ||
architectural plan, codemap, how to add flavors, ... | architectural plan, codemap, how to add flavors, ... | ||
=Errata= | |||
These are things to watch out for, don't work, etc. | |||
Revision as of 17:02, 30 September 2013
Resources
Documentation
- 1.8 Manual entry
- lustre.org wiki Flavors and setup
Mailing List
- iudev list we share the iudev mailing list currently (low traffic)
Related Topics
- Contract_SFS-DEV-002 Shared Key and UID Mapping project using Lustre's GSS
Jira
Background
(someone please fix this up)
Lustre Kerberos implements the Kerberos-5 security protocol to protect the privacy, integrity, and authenticity of Lustre-protocol messages. Basically the way this works is that the *sptlrpc* layer wraps each Lustre RPC inside an sptlrpc envelope, protecting all the data (including the header and other metadata) of the original message.
How to Get Started Using Kerberos
Kerberos setup requires the following components/packages to be installed before Lustre can be compiled with Kerberos support.
...
How to set up those packages
How to compile Kerberized Lustre
How to enable/use Kerberized Lustre
Kerberos FAQ
Comments on the Code
architectural plan, codemap, how to add flavors, ...
Errata
These are things to watch out for, don't work, etc.