F OpenNebula/one#6430: Move Sunstone views to legacy section (#2971)

Signed-off-by: dcarracedo <[email protected]>

source/legacy_components/ruby_sunstone/index.rst

@@ -11,4 +11,5 @@ Ruby Sunstone
    Virtual Machine Charters <ruby_sunstone_vm_charter>
    Accessing VM Console and Desktop <ruby_sunstone_vm_console>
    Sunstone Labels <ruby_sunstone_labels>
+   Sunstone views <ruby_sunstone_views>
    Cloud view <ruby_sunstone_cloud_view>

source/management_and_operations/users_groups_management/sunstone_views.rst → source/legacy_components/ruby_sunstone/ruby_sunstone_views.rst

@@ -1,4 +1,4 @@
-.. _suns_views:
+.. _ruby_sunstone_views:
 
 ================================================================================
 Ruby Sunstone Views
@@ -419,7 +419,7 @@ The actions available for a given VM can be customized and extended by modifying
 .. |sunstone_dashboard| image:: /images/sunstone_dashboard.png
 .. |admin_view| image:: /images/admin_view.png
 .. |sunstone_user_dashboard| image:: /images/sunstone_user_dashboard.png
-.. |sunstone_cloud_dash| image:: /images/sunstone_cloud_dash.png
+.. |sunstone_cloud_dash| image:: /images/ruby_sunstone_cloud_dash.png
 .. |views_settings| image:: /images/views_settings.png
 .. |views_change| image:: /images/views_change.png
 .. |sunstone_group_defview| image:: /images/sunstone_group_defview.png

source/legacy_components/ruby_sunstone/sunstone.rst

@@ -325,7 +325,7 @@ The Service and Service Template tabs may complain about connection failures to
 
 |sunstone_oneflow_error|
 
-Ensure you have OneFlow server :ref:`configured and running <oneflow_conf>`, or disable Service and Service Templates tabs in :ref:`Sunstone View <suns_views>`.
+Ensure you have OneFlow server :ref:`configured and running <oneflow_conf>`, or disable Service and Service Templates tabs in :ref:`Sunstone View <ruby_sunstone_views>`.
 
 Tuning and Extending
 ====================
@@ -378,7 +378,7 @@ Branding Sunstone
 You can add your logo to the login and main screens by updating the ``logo:`` attribute as follows:
 
 - The login screen is defined in the ``/etc/one/sunstone-views.yaml``.
-- The logo of the main UI screen is defined for each view in :ref:`the view yaml file <suns_views>`.
+- The logo of the main UI screen is defined for each view in :ref:`the view yaml file <ruby_sunstone_views>`.
 
 The logo image must be copied to ``/usr/lib/one/sunstone/public/images/``.
 
@@ -393,7 +393,7 @@ Global User Settings of Sunstone Views
 
 OpenNebula Sunstone can be adapted to different user roles. For example, it will only show the
 resources the users have access to. Its behavior can be customized and extended via
-:ref:`Sunstone Views <suns_views>`.
+:ref:`Sunstone Views <ruby_sunstone_views>`.
 
 The preferred method to select which views are available to each group is to update the group
 configuration from Sunstone, as described in :ref:`Sunstone Views section <suns_views_configuring_access>`.
@@ -438,7 +438,7 @@ than one view is available for a given user, the first one is the default.
 Different Endpoint for Different View
 -------------------------------------
 
-OpenNebula :ref:`Sunstone Views <suns_views>` can be adapted to use a different endpoint for
+OpenNebula :ref:`Sunstone Views <ruby_sunstone_views>` can be adapted to use a different endpoint for
 each kind of user, such as if you want one endpoint for the admins and a different one for the
 cloud users. You just have to deploy a :ref:`new sunstone server <suns_advance>` and set a default
 view for each sunstone instance:

source/management_and_operations/users_groups_management/index.rst

@@ -9,7 +9,6 @@ Users and Groups
    Users <manage_users>
    Groups <manage_groups>
    VDCs <manage_vdcs>
-   Ruby Sunstone Views <sunstone_views>
    Sunstone Views <fireedge_sunstone_views>
    Permissions and ACLs <chmod>
    Accounting <accounting>

source/management_and_operations/vm_management/vm_templates.rst

@@ -185,9 +185,8 @@ Each VM Template can have a cost per hour. This cost is set by CPU unit and MEMO
 Enable End User Features
 --------------------------------------------------------------------------------
 
-There are a few features of the :ref:`Cloud View <suns_views>` that will work if you configure the Template to make use of them:
+There are a few features of the :ref:`Cloud View <cloud_view>` that will work if you configure the Template to make use of them:
 
-* Users will see the Template logo (``LOGO``) and description (``DESCRIPTION``), something that is not so visible in the normal admin view.
 * The Cloud View gives access to the VM's VNC, but only if it is configured in the Template.
 * End users can upload their public ssh key. This requires the VM guest to be :ref:`contextualized <context_overview>`, and the Template must have the ssh contextualization enabled.