Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

M #-: Remove mention of OneGate Proxy #3016

Merged
merged 1 commit into from
Aug 7, 2024
Merged

M #-: Remove mention of OneGate Proxy #3016

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions source/overview/opennebula_concepts/opennebula_overview.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,8 +122,6 @@ The main components of an OpenNebula installation are listed below.

* **OneGate**: The OneGate server allows Virtual Machines to pull and push information from/to OpenNebula, enabling users and admins to gather metrics, detect problems in their applications, and trigger OneFlow elasticity rules from inside the VMs. It’s a dedicated daemon installed by default as part of the Single Front-end Installation, but can be deployed independently on a different machine.

* **OneGate/Proxy**: The OneGate/Proxy service is a simple TCP proxy solution that can be used to improve security for the OneGates endpoint, and which users can enable on hypervisor Nodes. Using this service avoids the need to expose the OneGate server on a public IP address in certain environments; furthermore, it greatly simplifies protecting the traffic to and from OneGate with a VPN solution.

These are OpenNebula’s system interfaces:

* **Sunstone**: OpenNebula’s next-generation Graphical User Interface (WebUI) intended for both end-users and administrators to easily manage all OpenNebula resources and perform typical operations. It’s a dedicated daemon installed by default as part of the Single Front-end Installation, but can be deployed independently on a different machine.
Expand Down
Loading