Hello Kern, pt., 25 sty 2019 o 16:47 Kern Sibbald <k...@sibbald.com> napisał(a):
> Hello guys, > > Interesting conversation. I thought I would throw in some general > comments of my own. > > - I really like seeing another GUI for Bacula, because it is something we > really need. > Thank you Kern, I really appreciate your support. You are the only one who sees it as an opportunity and not a threat. > - The BWeb GUI created by Bacula Systems, is very essential to corporate > users. > - The Baculum GUI created by Bacula Community (Marcin Haba -- note he also > works > on the Enterprise BWeb) will be very essential to large community > users. > - I don't like the idea that a GUI read/write directly into the Bacula > catalog. If I am not mistaken > both BWeb and Baculum do this, but we are developing API calls and > trying to make sure all > accesses go through the Bacula core code. However, it will take more > time to get those > products switched over. > Thank you Kern for your opinion. As I wrote before, IBAdmin should support databases split without a problem. So I prepared a patch which support a full databases split. The patch is available in IBAdmin/split branch for anyone who wants to test it. IBAdmin was not designed as an another Bacula GUI but it was designed as a complete solution where Bacula is the main engine. Not all the design goals are reached yet and requires a lot of work. But now it can be used as a general purpose Bacula GUI. The project started in 2015 and was opened to public at Jun 29, 2017 with opensource license - AGPL-3, basically the same as Bacula Community. Now the IBAdmin reached the next big goal - advanced users and permissions management with multitenant support which was a great opportunity to introduce it to all Bacula users at bacula-users and bacula-devel mailing list. The introduction failed. Community rejected the project. > - GUI programs designed and coded by Bacula Systems and/or Bacula > Community will remain > compatible with the Bacula Catalog -- this is a given. However > non-Bacula GUI until we finish > the APIs and those programs use them, 3-rd party GUIs are almost certain > to have problems > with Bacula catalog changes (the exception is IBAdmin, because Radek > works directly with both > Bacula Enterprise and Bacula Community so he knows what is changing > before the release). > Thank you Kern. > - Around April of 2019 (or whenever I finish the work) there will be a > major Bacula Community > Catalog change -- anyone who reads the catalog directly will very likely > need to adapt their > SQL. > - For Bacula itself (enterprise or community), I am not in favor of > storing Bacula configuration files in the catalog, > because doing so makes it more difficult to change the configuration > files, and requires the SD and FD and > any tool to know how to access the database. Even more importantly, in > a disaster recovery situation, > you may not be able to reconstruct the same catalog database, while > restoring ASCII configuration > files is relatively simple. > Every solution has pros and cons. I'm very happy when I can discuss what is a best solution in certain requirements and assumptions. The main requirements for IBAdmin in this area are: encrypted passwords storage and a single Catalog and Configuration replication. To meet the requirements we decided to store configuration data in a database where as a bonus we've got a transaction configuration change, so the application error does not invalidate the current configuration. We see it as a real value. DR in IBAdmin will be based on replication. Someone in other projects can have a different assumptions or requirements and I respect it. best regards -- Radosław Korzeniewski rados...@korzeniewski.net
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
