MenuExplore! Impressum Privacy Policy
☐
Solve sport lesson assignment
  • Issue number: #37

Task Description

Exemplary solve the sport lesson assignment problem from Martins Avots's master thesis, in order to extend the programs modelling and optimization capabilities.

Thereby make the project usable as a service by multiple users at once. A platform supporting many different optimization problems out of hand seems to be crippled, if the service can only be used by one user at once. Furthermore, in order to prepare the webserver for "Solve school course scheduling problem", basic support for authentication and authorization is to be added to the server. For testing purposes the authentication and authorization system is used, to only provide server CPU and RAM usage in real time to the administrator of the server. To make the administration GUI useful an update command of the webserver itself is to be implemented.

Tasks

  • [ ] Complete the issue "Create no-code gel editor" first.
  • [x] Improve user experience regarding the application's responsiveness, by supporting multiple web server users at once.
    • [x] Implement basic multi threading injection framework.
      • [x] Note, that multi threading is achieved while avoiding amount of thread safe code. Therefore, multiple instances of ProjectsRendererI are used, even though most of that code is probably thread safe. Code that is thread safe, because everything is read only is fine though.
    • [x] Make webserver thread safe, in order to support multiple users at once on public server.
    • [x] Document, that one of the goals of the threading injection framework, is to minimize the amount of code written specifically for multi-threading.
    • [x] Support multiple users at once via multi threading injection.
    • [o] Ensure, that logs are working in threads, too. Currently, it does not seem to be the case and therefore Throwable#printStackTrace() is used as a workaround. -> This cannot be replicated anymore.
    • [x] Use multiple threads for calculation of the ratings via the constraint nodes. -> The performance get worse with constraint multithreading.
    • [o] Use dedicated workers for lookup tables. -> This is not relevant to this issue.
    • [x] Continuously and automatically run test user in live distro, in order to test if server can endure many optimization runs.
      • [x] Determine web address via Dem config and not via a constant. -> This is already available via ServerConfig.
      • [x] Use dynamic web address determination at HtmlClientImpl, too.
      • [x] Create general live tester, where testers are registered in Dem. The tester should be disabled by default and is intended for stress testing the server.
      • [x] Create optimization test.
        • [x] Make playwright work on server.
        • [x] Execute optimization test via playwright.
          • [x] The browser cannot connect to server. This seems to be a firewall/network issue, as apt install netutils-ping && ping splitcells.net does not work as well in the container. This ping works outside the container and on the server. So, this is a podman issue.
            • [x] The problem is the same as https://github.com/containers/podman/discussions/22778
            • [x] The problem can be tested in the shell of the container via curl live.splitcells.net.
          • [x] Xml#parse has a race condition.
      • [x] Execute exactly 1 test at any given time. Provide option to execute exactly n tests at any given time. -> Now the number of simultaneously executed tests is half the CPU cores.
      • [x] Assign more RAM to container. -> Podman's container already get all available RAM.
      • [x] Move live test to optional system settings, in order to make live tests an optional standard functionality, that is easy to set up initially.
      • [x] Abort live server build with error, if Podman execution aborts with an error.
      • [x] Log all Service starts generically.
    • [x] Check CPU and RAM usage.
  • [x] Add first administrative GUI in webserver.
    • [x] Create blocked page.
    • [x] Authenticate
    • [x] Authorize
    • [x] Persist authentication info of the users.
    • [x] Authorize based on persisted authorization data of the users.
      • [x] Simplify config file structure and make more consistent.
        • [x] Place ACME files inside config folder. -> This was already the case. There were just some old files on the server, that created the impressions, that ACME files were stored inconsistently.
        • [x] Each user should have a password file. The user file should not contain the password, but be a folder, so that additional attributes can be placed there.
      • [x] Make file structure more consistent. Currently, some files are place in the top level. -> These were just some stray files on the live server.
      • [x] Read user from vertx.
        • [x] Ensure, that every handled user is created by the main Authentication. -> The solution calculators are ignored regarding this for now.
          • [x] Implement Vertx independent Authenticator.
          • [x] Test Vertx independent Authenticator.
          • [x] Use independent Authenticator in Vertx and the UserSession to the user attributes map of Vertx.
          • [x] Strongly limit allowed symbols username and password severely. -> Only the username was limited for now, as an urgent need for limiting the user's password is not know.
        • [x] Ensure, that every user object is created with proper user input. Do not look up user objects just by names. Ensure that proper authentication was provided by the user.
        • [x] Convert user object to user session object.
        • [x] Provide a RAII based cycle for user sessions. An access control object can ensure this, by providing a method, that takes a login and user session consumer, in order to execute a piece of code with login specified user session.
        • [x] use RAII based user session life cycle for server.
        • [x] Limit the amount of parallel user session, in order to detect life cycle problems of user sessions. -> Document this as a task, at the access control object source code.
      • [x] Read roles of user from config.
      • [x] Create base class for all currently present authenticators, in order to have standardized runtime checks for authenticators
    • [x] Do not render administrator documents on static rendering or render administrator pages with the lowest privilege.
      • [x] Renderers have to support a rights concept.
      • [o] View log files in website only for administrator. -> Viewing logs via web UI is not required for now.
    • [x] Create default user profile page, were the user sees links to user specific pages. May do this, by showing all paths, that only a specific user has access to?
    • [x] Provide access to CPU and RAM utilization, if the user session has the appropriate role for that.
    • [o] CPU utilization is not visible in the layout anymore. The reason for that is, that ProjectsRendererExtension do not support project paths listening via a user session. -> It is enough, that this page is visible in the users profile.
      • [o] Extend interface.
      • [o] Add implementation for CPU utilization extension.
    • [o] Fix styling for You do not have the rights to access this page. page. -> It is good enough for now.
    • [x] Document this in the web server's changelog.
    • [o] Create login page. -> The browser's default login page is enough for now.
    • [o] Link to login page from You do not have the rights to access this page. page. -> The browser's default login prompt is enough for now.
    • [x] The following extensions needed appropriate protection as well.
      • [x] net.splitcells.website.server.projects.extension.impls.TestExtension
      • [x] net.splitcells.website.server.projects.extension.status.HostMemoryUtilizationExtension
      • [x] Enable and secure net.splitcells.website.server.projects.extension.impls.DemConfigExtension, which is currently disabled.
    • [o] Create picture depicting an architectural overview of the security system. -> The authentication, authorization and access control API seems to be good enough.
    • [x] Deploy this feature to production.
  • [ ] Support complex problem definitions via editor, that are composed of multiple ones, so that the sport lesson assignment can be defined in the editor.
    • [ ] Extend Gel language, in order to model optimization problems consisting of multiple optimization problems.
      • [ ] Use domain object based parser as backend for editor and no-code editor, in order to simplify parsing.
        • [ ] Remove direct dependency to ANTLR4 at parser and any other code.
        • [ ] Consider moving parsing code to dedicated project, in order to isolate ANTLR4 and grammar dependencies.
        • [ ] Use Java sum type in order to simplify handling of domain object, if needed. This requires sum types to be added to the allowed Java grammar.
    • [ ] Add example of sport lesson assignment as an editor page to webserver.
  • [ ] Check sport lesson assignment model.
  • [ ] Check test data.
  • [ ] Solve sport lesson assignment.
  • [ ] Make it easier to understand the solution.
    • [ ] Store and show positive reason, why a certain supply was assigned as certain value.
    • [ ] Render ratings in formatted output as well via pop-ups. Consider using own table framework, for easier adaptability in this context.