ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Where to find "best practice" for any given IT scenario

    Water Closet
    11
    58
    4.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.
    • C
      Carnival Boy
      last edited by

      It's an easy one for anyone who hangs around the same forums you do 🙂

      1 Reply Last reply Reply Quote 2
      • scottalanmillerS
        scottalanmiller
        last edited by

        Another best practice: virtualize every workload (unless it is impossible to do so)

        dafyreD 1 Reply Last reply Reply Quote 0
        • dafyreD
          dafyre @scottalanmiller
          last edited by

          @scottalanmiller said:

          Another best practice: virtualize every workload (unless it is impossible to do so)

          What are some workloads it would be impossible to virtualize? With the exception of real-time, ulta-low latency requirements, I cannot think of anything.

          scottalanmillerS 1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller @dafyre
            last edited by

            @dafyre said:

            What are some workloads it would be impossible to virtualize? With the exception of real-time, ulta-low latency requirements, I cannot think of anything.

            Those and ones with very specific hardware requirements either technically or politically. That's about it. It is rare enough that it is effective to just say "never".

            1 Reply Last reply Reply Quote 0
            • C
              Carnival Boy
              last edited by

              Workloads that you can't get working virtualised for whatever reason. I couldn't get Hamachi to work virtualised. Googling suggested a common problem with Hamachi not liking the VMware network drivers or something.

              I've virtualised our firewall. I wonder if there's an argument that says I shouldn't because it means I have a hypervisor on a public facing host. Maybe? I dunno, could that be a security risk? It's not something I'm going to lose any sleep over.

              scottalanmillerS dafyreD 2 Replies Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller @Carnival Boy
                last edited by

                @Carnival-Boy said:

                I've virtualised our firewall. I wonder if there's an argument that says I shouldn't because it means I have a hypervisor on a public facing host. Maybe? I dunno, could that be a security risk? It's not something I'm going to lose any sleep over.

                You can virtualize that without exposing the hypervisor in any way.

                1 Reply Last reply Reply Quote 0
                • C
                  Carnival Boy
                  last edited by

                  That's what I figured. I suppose I was wondering about accidentally exposing the hypervisor through human error.

                  scottalanmillerS 1 Reply Last reply Reply Quote 1
                  • scottalanmillerS
                    scottalanmiller @Carnival Boy
                    last edited by

                    @Carnival-Boy said:

                    That's what I figured. I suppose I was wondering about accidentally exposing the hypervisor through human error.

                    Always a risk, but pretty easily addresses as long as people are aware.

                    1 Reply Last reply Reply Quote 0
                    • dafyreD
                      dafyre @Carnival Boy
                      last edited by

                      @Carnival-Boy said:

                      Workloads that you can't get working virtualised for whatever reason. I couldn't get Hamachi to work virtualised. Googling suggested a common problem with Hamachi not liking the VMware network drivers or something.

                      I've virtualised our firewall. I wonder if there's an argument that says I shouldn't because it means I have a hypervisor on a public facing host. Maybe? I dunno, could that be a security risk? It's not something I'm going to lose any sleep over.

                      How do you virtualize the Firewall without exposing the underlying hypervisor? By making sure that there is not an IP address assigned to the actual host on the interface that connects to the WAN?

                      scottalanmillerS 1 Reply Last reply Reply Quote 0
                      • scottalanmillerS
                        scottalanmiller @dafyre
                        last edited by

                        @dafyre said:

                        @Carnival-Boy said:

                        Workloads that you can't get working virtualised for whatever reason. I couldn't get Hamachi to work virtualised. Googling suggested a common problem with Hamachi not liking the VMware network drivers or something.

                        I've virtualised our firewall. I wonder if there's an argument that says I shouldn't because it means I have a hypervisor on a public facing host. Maybe? I dunno, could that be a security risk? It's not something I'm going to lose any sleep over.

                        How do you virtualize the Firewall without exposing the underlying hypervisor? By making sure that there is not an IP address assigned to the actual host on the interface that connects to the WAN?

                        Have the hypervisor exposed on a different physical adapter that is not on the WAN network side.

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