| | 7 | Tigran: pools, NFS |
| | 8 | |
| | 9 | Antje: looked at old tickets several tickets needing an answer. Coming around with a big stick. |
| | 10 | |
| | 11 | Tanja: tickets, reading about NFS spec. Want our NFS server to work in a federated NFS deployment. |
| | 12 | |
| | 13 | Gerd: visited DESY, tried to learn about NFS 4, wrote replacement for gPlazma cell + small stuff. |
| | 14 | |
| | 15 | Dmitry: mostly looked at ticket. |
| | 16 | |
| | 17 | Timur: wrote configuration parser for PAM style ... factories. Started working on implementaiton of strategy |
| | 18 | |
| | 19 | Jan: fought on username/pw plugin, web-admin work. PNFS migration to Chimera. |
| | 20 | |
| | 21 | Paul: |
| | 22 | |
| | 23 | Owen: parser for layout.conf. Applies diffs to layout.conf. Can parse site-info.def now. About 80% done now. Should be submitting some code at end of the week. Other task is EMI certification. Unfortunately had another 3 test suites dumped that doesn't work at DESY. Other task is migration of our gLite hosts onto a new virtualisation service. |
| | 38 | = Adapters in FTP = |
| | 39 | |
| | 40 | CDF system: security scanners would cause |
| | 41 | |
| | 42 | detect that the connection isn't from a pool and close the connection. |
| | 43 | |
| | 44 | For the pool, this is something you can do, but one cannot |
| | 45 | |
| | 46 | Clients connect directly but pools queue, so this would fix |
| | 47 | |
| | 48 | Luckily there is already MoverProtocolv2 send a message mover back to the door. We can extend this to also report source ip of the pool. |
| | 49 | |
| | 50 | You can have a race-condition between pool connect and pool's message arriving: if the message is too slow then |
| | 51 | |
| | 52 | We could have a token between pool and door, so that door sends token to the pool and will only accept a connection with this token sent as first n-bytes. |
| | 53 | |
| | 54 | We could share the same server socket on the door for all pools. |
| | 55 | |
| | 74 | Jan: moved the kpwd to commons directory to use it. There are legacies classes that are dependencies of kpwd parser. |
| | 75 | |
| | 76 | We don't have doors depending on kpwd. The KpwdLoginStrategy is the only dependency. |
| | 77 | |
| | 78 | Yes, we do need kpwd parser as some sites |
| | 79 | |
| | 80 | If we just want to use kpwd ... |
| | 81 | |
| | 82 | Do we use what's already in dCache or do we write a new. |
| | 83 | |
| | 84 | Plugins should go in gPlazma module. |
| | 85 | |
| | 86 | Can you update kpwd parser to remove |
| | 87 | |
| | 88 | Commons is probably not the right location. |
| | 89 | |
| | 90 | To show the true independence of gPlazma, separate module for plugins and package as separate JARs. |
| | 91 | |
| | 92 | Tigran and Jan to look into it tomorrow. |
| | 93 | |
