Skip to content

Commit cdf4647

Browse files
committed
Update whats_new.rst
1 parent 90ae820 commit cdf4647

File tree

1 file changed

+11
-4
lines changed

1 file changed

+11
-4
lines changed

source/release_notes46/whats_new.rst

Lines changed: 11 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,10 @@
44
What's New in OpenNebula 4.6
55
============================
66

7+
OpenNebula 4.6 introduces the possibility of managing Virtual Data Centers natively, via Sunstone and the CLI. The new OpenNebula Zones component, which is tightly integrated with the rest of the OpenNebula components, makes it very easy to federate OpenNebula deployments. Federated environments share the same users, groups and acls, while maintaining the other resources locally.Virtual Data Centers, VDCs, have been also greatly improved, both in multi-tenant deployments and in stand-alone OpenNebula installations.
8+
9+
The Sunstone graphical interface has been completely redesigned, making a very strong emphasis on simplifying the interface and delivering a more intuitive experience. The dialogs have been reworked in order to help the user workflows. It also supports federated environments natively and allows users to switch to another OpenNebula Zone from within Sunstone. It has also been improved in order to natively support the new Marketplace version, which provides the possibility of creating multi-disk virtual machines.
10+
711
In the following list you can check the highlights of OpenNebula 4.6 Carina organised by component (`a detailed list of changes can be found here <http://dev.opennebula.org/projects/opennebula/issues?query_id=50>`__):
812

913
OpenNebula Core: End-user functionality
@@ -15,10 +19,12 @@ There has been several improvements for end-users:
1519
- **Network parameters can now be changed**, by updating the template. This includes ``VLAN_ID``, ``BRIDGE``, ``VLAN`` and ``PHYDEV``. See the :ref:`Managing Virtual Networks <vgg>` guide for more information.
1620
- **Templates for GROUP resources** TODO: documentation?
1721
- **Allow to change the base_path for existing Datastores** TODO: documentation?
18-
- **Support for an http proxy in the Ruby OCA client**, which can be passed as an option.
19-
See the `Ruby API Documentation <http://docs.opennebula.org/doc/4.6/oca/ruby/OpenNebula/Client.html>`__.
2022
- **Disable the XML-RPC log**, see the :ref:`ONED Configuration <oned_conf>` for more information.
2123
- **Support for limiting the Resources Exposed by a Host**, see :ref:`Scheduler <schg>` for more information.
24+
- **Support for an http proxy in the Ruby OCA client**, which can be passed as an option.
25+
See the `Ruby API Documentation <http://docs.opennebula.org/doc/4.6/oca/ruby/OpenNebula/Client.html>`
26+
27+
2228

2329
OpenNebula Core: Internals & Administration Interface
2430
-----------------------------------------------------
@@ -50,14 +56,15 @@ Virtualization Drivers
5056
Sunstone
5157
--------
5258

53-
The Sunstone graphical interface has been completely redesigned, making a very strong emphasis on simplifying the interface and delivering a more intuitive experience. The dialogs have been reworked in order to help the user workflows. It also supports federated environments natively and allows users to switch to another OpenNebula Zone from within Sunstone. It has also been improved in order to natively support the new Marketplace version, which provides the possibility of creating multi-disk virtual machines.
5459

5560
OneFlow
5661
-------
5762

5863
- **Configurable setting to render names assigned to VMs**, being able to use placeholders like ``SERVICE_ID`` and ``SERVICE_NAME``, see the :ref:`OneFlow Server Configuration <appflow_configure>` guide for more information.
5964

65+
OpenNebula vDCs
66+
----------------
67+
6068
OpenNebula Zones
6169
----------------
6270

63-
OpenNebula 4.6 introduces the possibility of managing Virtual Data Centers natively, via Sunstone and the CLI. The new OpenNebula Zones component, which is tightly integrated with the rest of the OpenNebula components, makes it very easy to federate OpenNebula deployments. Federated environments share the same users, groups and acls, while maintaining the other resources locally.Virtual Data Centers, VDCs, have been also greatly improved, both in multi-tenant deployments and in stand-alone OpenNebula installations.

0 commit comments

Comments
 (0)