Client Consumer Focused Workload Consolidation

Forums Personal Topics Unbidden Thoughts Client Consumer Focused Workload Consolidation

This topic contains 2 replies, has 1 voice, and was last updated by  josh July 7, 2021 at 11:01 am.

  • Author
    Posts
  • #96675

    josh

    So, for example, I’ll make up some non-expert nonsense which may be not quite right, but will give an idea for a true form:

    Say there “WHATITIS_II_7000” system runs on X platform for which there is a strong hardware emulator and we can also read & write the file system in embedded and new format. This allows the ability to not mess with old installation media & system port the ready to boot system to the new platform (peripherals…). We call this “Rigid Virtualization CLoning”. Say it really works. Now, studying a few months of real workload & recording it all, we can get confidence in out ability to interface with the system in new ways, with new functionality, based on the testable observation that the existing workload continues to function in the prescribed way on simulated playback, even while interacting with the added software functionality.

  • #96714

    josh

    The work & concepts here don’t start out sounding sexy as biz or intellectual endeavor, but objectively there are some meta angles for extra plugging as broader context goals.

    Point 1: You’ve got diverse hardware legacies – get all of your VM & software support from a single, super competent source. That points is true for direct & indirect support arrangements.

    Point 2: There is a project, sexy to some metal tech fans, to make behavior tests of emulation environments achieve the same level of coverage as unit testing of source code trees. Emulation makes it possible to look inside, smart documentation makes it possible to name what we see, & dev ops makes it possible to industrialize an entry level tech force in pursuit of this.

    Point 3: GT looks for profitable ways to employ more “typical” career growers.

    Point 4: Sale opportunities can be a wishbone arbitrage of many sorts. Buying their old gear may be interesting & profitable in cases where the softare update doesn’t appeal. Friend or foe, whatever, by cases.

    Point 5: Mfg. continues to innovate. Who says it will stick with a few compute platforms in the future for the entire range of ops?

    Point 6: Fixing the problem nobody else would touch or make right can be a good entry point for more biz.

    Point 7: The older an installed piece of factory gear is, the harder it is to update, & the more likely it is to benefit from making a bridge to networked apps. Why was it not replaced a long time ago? Whatever the reason was, it was a reason it’s still there.

You must be logged in to reply to this topic.