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

    NVMe madness

    Scheduled Pinned Locked Moved
    General
    5
    40
    8.6k
    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.
    • S
      Sebastian Roth Moderator
      last edited by Sebastian Roth

      @Fog_Newb Finally found some time to work on this. At first I was hoping to come up with kind of a logic that would detect disk size and select the correct disk according to this. As I said we have this working for images set to multiple disk type.

      But half way into it I figured that my solution would only work for deployments where we have the size information from capturing beforehand. But this wouldn’t solve the issue of NVMe drives switching position on capturing in the first place.

      The only way we can solve this is by telling FOS to look for a disk of certain size when running a task. So far we only allowed the host setting Host Primary Disk to name a Linux device file to use - e.g. /dev/nvme0n1. But now I added the functionality for you to specify disk size (byte count) using this same field.

      So you just need to do is download the modified init.xz and put into /var/www/html/fog/service/ipxe/ directory (rename the original file beforehand) and set Host Primary Disk to an integer value matching exactly the byte count of the disk (value you get from blockdev --getsize64 /dev/...).

      Please give it a try and let me knwo what you think,

      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

      F 2 Replies Last reply Reply Quote 1
      • F
        Fog_Newb @Sebastian Roth
        last edited by

        @Sebastian-Roth

        Thanks. I will test as soon as I can. Probably middle of the night or early tomorrow.

        1 Reply Last reply Reply Quote 0
        • F
          Fog_Newb @Sebastian Roth
          last edited by Fog_Newb

          @Sebastian-Roth

          I copied over the updated init.xz to

          /var/www/html/fog/service/ipxe/

          Then set the host primary disk to 1000204886016 and attempted to capture

          It worked great

          Thank you very much

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by

            @Fog_Newb said in NVMe madness:

            Then set the host primary disk to 1000204886016 and attempted to capture

            So this was capturing the one tera byte disk, right?

            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

            F 2 Replies Last reply Reply Quote 0
            • F
              Fog_Newb @Sebastian Roth
              last edited by

              @Sebastian-Roth

              Yes.

              1 Reply Last reply Reply Quote 0
              • F
                Fog_Newb @Sebastian Roth
                last edited by Fog_Newb

                @Sebastian-Roth

                So yes, this is a perfect solution since Primary host disk can now be set by size. I have one image for the OS disk, and one for the “D” drive. I just switch the Primary Host disk setting depending on which image I want to capture or deploy.

                1 Reply Last reply Reply Quote 1
                • S
                  Sebastian Roth Moderator
                  last edited by

                  This is committed to the fos repo and will be available in the next release.

                  @Tom-Elliott Should we re-phrase the name of that field or just leave it like that and add this information to the documentation?

                  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

                  Tom ElliottT 2 Replies Last reply Reply Quote 0
                  • Tom ElliottT
                    Tom Elliott @Sebastian Roth
                    last edited by

                    @Sebastian-Roth I think leave as is but update documentation.

                    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
                    • S
                      Sebastian Roth Moderator
                      last edited by

                      @JJ-Fullmer @Jurgen-Goedbloed Would one of you take care of adding this new feature to the documentation?

                      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 1
                      • Tom ElliottT
                        Tom Elliott @Sebastian Roth
                        last edited by

                        @Sebastian-Roth hmmm what about a new field specifically designed for the size? If hard drive specified default to that, else if size specified match drive based on that?

                        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 1
                        • S
                          Sebastian Roth Moderator
                          last edited by

                          @Tom-Elliott But why have another file if they can’t be used in combination anyway? It’s either or!

                          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

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

                            @Sebastian-Roth that’s what I mean. If you have specified the hdd use that. If hdd not found but you have size defined, try to find matching size. If both or either defined but not exist error out.

                            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

                            Q 1 Reply Last reply Reply Quote 0
                            • Q
                              Quazz Moderator @Tom Elliott
                              last edited by Quazz

                              @Tom-Elliott I kind of like that idea of a fallback mechanism, but I fear that it would kind of nullify what it’s trying to solve in a way.

                              Few people would know about the NVME naming scheme being essentially random on each boot and thus may presumably fill in the name of the drive. This would then get used and the size (if filled in) would be ignored.

                              I think if it were to be implemented as such, then the GUI should inform to use size over name for NVME drives.

                              PS: What happens when you have 2 identical drives?

                              1 Reply Last reply Reply Quote 0
                              • S
                                Sebastian Roth Moderator
                                last edited by Sebastian Roth

                                @Quazz Right, using a second field will just allow for people to confuse things. While we try to give people more responsibility instead of trying to solve all things within the code I don’t think adding another field is valuable in this term. It’s a simple case of either or in one field and there is no situation where specifying both size and dev name at the same time makes sense.

                                PS: What happens when you have 2 identical drives?

                                I have thought about this while implementing the multi disk NVMe code and this new stuff as well but I don’t think there is any possible way we can help people with two identical sized disks. If we store disk identifiers (globally unique) it cannot be deployed to a different target machine. As far as I see size is the only parameter helping us to solve this dilemma.

                                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

                                F 1 Reply Last reply Reply Quote 0
                                • F
                                  Fog_Newb @Sebastian Roth
                                  last edited by

                                  @Sebastian-Roth

                                  Quick question. Does 1.5.9.36 dev build have these NVME related intits?

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    Sebastian Roth Moderator
                                    last edited by

                                    @Fog_Newb No, not yet.

                                    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

                                    F 1 Reply Last reply Reply Quote 0
                                    • F
                                      Fog_Newb @Sebastian Roth
                                      last edited by

                                      @Sebastian-Roth

                                      Thanks. I updated and instead of checking I got lazy and posted. Where can I find info on what’s changed in each dev build? Github didn’t seem to have anything listed.

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        Sebastian Roth Moderator
                                        last edited by

                                        @Fog_Newb Every dev version is just one single new commit to the dev-branch. So you know what changed looking at the commit history on github.

                                        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

                                        F 1 Reply Last reply Reply Quote 0
                                        • F
                                          Fog_Newb @Sebastian Roth
                                          last edited by

                                          @sebastian-roth

                                          Thanks.

                                          JJ FullmerJ 1 Reply Last reply Reply Quote 0
                                          • JJ FullmerJ
                                            JJ Fullmer Testers @Fog_Newb
                                            last edited by

                                            @fog_newb I suggest bookmarking https://github.com/FOGProject/fogproject/commits/dev-branch
                                            So you can do a quick check for updates on the dev-branch anytime 😃

                                            @Sebastian-Roth So, just so I’m documenting the right thing.
                                            Should I update the field’s documentation here https://docs.fogproject.org/en/latest/management/host-management.html#primary-disk
                                            With a note (and a link to this forum post) that you can put either the devname or the exact blocksize/sector count with the linux command to find said sector count. Is that command accessible in the fog debug console? It looks like in windows you can use the powershell command get-disk | select Number, "FriendlyName", Size to list available disks by number and friendly name and display the blocksize. So it can be found fairly easily in Windows and Linux.

                                            Is just adding a note by the field enough, or should there be a separate page explaining nvme selection?

                                            Have you tried the FogApi powershell module? It's pretty cool IMHO
                                            https://github.com/darksidemilk/FogApi
                                            https://fogapi.readthedocs.io/en/latest/
                                            https://www.powershellgallery.com/packages/FogApi
                                            https://forums.fogproject.org/topic/12026/powershell-api-module

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

                                            189

                                            Online

                                            12.1k

                                            Users

                                            17.3k

                                            Topics

                                            155.3k

                                            Posts
                                            Copyright © 2012-2024 FOG Project