You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @SwiftOnSecurity , so what is the scope of deployment? Meaning on-premises, Azure, AWS, etc.? Are these images/systems going to be deployed to Hyper-V, VirtualBox, ESXi, Vagrant, or a Docker twist!
I’d love to help, if you want the help. :)
The text was updated successfully, but these errors were encountered:
This will not a server hydration tool for virtual environments, at least in my current vision. It will be semi-automated guided installation and direction.
The goal is to allow an IT admin of moderate skill to quickly rebuild a company after a complete network loss. So some of the fancy stuff will need to be left for others/the future.
May be worthwhile to construct two different deployments. One could be semi-autonomous as you described, and the other could be a Hyper-V/ESXi method as a demo environment for lab and demo use-cases.
Hey @SwiftOnSecurity , so what is the scope of deployment? Meaning on-premises, Azure, AWS, etc.? Are these images/systems going to be deployed to Hyper-V, VirtualBox, ESXi, Vagrant, or a Docker twist!
I’d love to help, if you want the help. :)
The text was updated successfully, but these errors were encountered: