Giter VIP home page Giter VIP logo

Comments (4)

Dautor avatar Dautor commented on September 22, 2024 1

That sounds like a good solution to the problem.
It seems much more powerful and simpler to maintain.

I would greatly appreciate if you put some efforts into researching / developing this.
Hopefully we can have this in future.

Thank you for putting thought into not over-complicating the feature!

from imunes.

denisSal avatar denisSal commented on September 22, 2024 1

Yeah, be my guest. We'll continue the discussion about it when I create this feature branch.

Denis

from imunes.

denisSal avatar denisSal commented on September 22, 2024

Hi Dautor,

As announced, I'm continuing the discussion initiated in #117... To begin with, there's already a similar request (see #98), but since there's renewed demand for this feature, I'll elaborate a bit and share my thoughts on it.

However appealing it may sound, I don't want to transform IMUNES into a hypervisor for all possible types of virtualization. It's a significant undertaking that would imply (over) substantial changes and continuous maintenance of multiple virtualization systems on various platforms.

On the other hand, it would be beneficial if virtual machines could somehow be integrated into IMUNES topologies without IMUNES needing to account for and be aware of all parameters during the machine's startup/configuration/shutdown. What I propose, and what would be entirely feasible, is to create a node (External node/host/machine?) that serves to define the parameters with which the IMUNES network would connect to that node. According to this article, it's possible to use netgraph (which IMUNES uses on FreeBSD) to connect a bhyve virtual machine to the host network. This means, for example, that in that node, only netgraph node and its hook could be defined, and IMUNES would connect it to nodes within the running topology.

Later, this node could be expanded with additional options (e.g., startup/terminate commands, a command to open the shell, etc.). The user would have complete responsibility for defining all aspects of these commands - IMUNES would only need to run them and not worry about any errors or misconfigurations.

If you find this idea appealing, I can try experimenting with it. Feel free to share your advice and opinions.

Best regards,
Denis

from imunes.

Dautor avatar Dautor commented on September 22, 2024

Does it make sense I close this issue and #117 as they make no sense if you decide to implement it in the way you described above?

from imunes.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.