• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Nice to have

    Scheduled Pinned Locked Moved
    Feature Request
    2
    3
    378
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • O
      oelked
      last edited by

      Hello, we currently have a fog network
      1 master
      and 4 storage nodes at different locations

      these are expected to increase by 19 over the next few years.

      The following things would simplify and improve the function.

      Snapin area

      Column with version number that is read from the .MSI, .EXE during upload or can be maintained manually

      Snapin update date column

      Dashboard area

      Synchronization status storage nodes
      or status in general

      Tom ElliottT 1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott @oelked
        last edited by Tom Elliott

        @oelked Snapins - reading what from the MSI or EXE?

        Fog runs on linux and wouldn’t have the ability to read the information, but even if it could/can (I’m just not aware of a method to do so)

        Snapins are not a softare management system. Sure, you can do one off “software” installs, custom configuration scripts, etc…, but it was not/is not, intended as a mechanism to manage software for your machines. This isn’t to say what you’re sasking couldn’t be implemented, but if your asking “can be maintained manually” why not just update the snapin with the version number for the Name?

        Syncing status, we have logs, that tell us the last time the syncronization occurred already. There is no “flag” as of yet to state, success/fail of it at all. That’s not to say there couldn’t be one, but there’s very few people around working on fog that feature requests are likely FAR down the the list of things to be done.

        I’m not trying to be rude, just trying ot set expectations here. That said, where on the “dashboard” would such a feature go? How would it be represented? How would it be stored? What constitutes failure? Should it be realtime check? Should it autorefresh on the dashboard?

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • O
          oelked
          last edited by

          Hello
          We primarily use Fog for software management on the clients
          This works relatively well, even if it wasn’t intended for that purpose.
          We would still like to keep this as this function is very convenient for us.

          You can certainly add the version number to the name.
          I actually wanted to avoid this because I can’t guarantee that there might be problems here in Fog if the name of an assigned packet changes all of a sudden.

          To the node status
          I currently know that you can read this in the logs

          One field in the dashboard for each storage node would be enough for me to operate it
          what the status is

          Example
          synchronization
          Ready
          Error

          If there are errors, you can read them in the log.

          Thank you for the great work on this project

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post

          151

          Online

          12.0k

          Users

          17.3k

          Topics

          155.2k

          Posts
          Copyright © 2012-2024 FOG Project