 |
I think I would like to make things a bit broader e.g. combine the ideas with the feature request of allowing a client initiated backup. You can probably re-use the socket that gets opened from the client to the director after doing the normal challenge response mostly in the same way as we do for passive backups in Bareos e.g. nothing prevents you from using the opened socket as return socket mostly like it normally gets initiated by the director. I don't like the idea of using an extra listener and socket port. We could use the same approach that the filed and stored already use in Bareos and that is dispatch based on the hello message send. Given you have very old code I wonder how much of it will still apply to a code base that has drifted for almost 8 years. Bareos also is very different from a config engine aspect etc. If you can show the current code we can easily decide if it makes any sense to reuse that code or to redesign things from scratch. If we want to do a proper design first it probably makes sense to do that via the devel mailinglist as this is a somewhat larger change we don't want to end up with something thats unsupportable. As long as things are configurable I see no problems in adding some changes that potential may be of use for some people. At least people coming from TSM etc like the idea of client initiated backups and even if it may not be for everyone I can see a use case there. We probably first need to set the expectations right as we need to do proper design first and then potentially reuse some already existing code. |
|
|
I added to the master branch some refactoring to allow the DIR to determine if its a normal console connection or a client connecting to the director. We could take the design further from here. I would be interested in reviewing some code even when its not working. |
- Anonymous
