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

F OpenNebula/one#6430: Refactor appliances section #2961

Merged
merged 1 commit into from
Jul 5, 2024
+2 −10
Merged

F OpenNebula/one#6430: Refactor appliances section #2961

Show file tree
Hide file tree
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
Binary file modified source/images/show_marketplaceapp.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
12 changes: 2 additions & 10 deletions source/marketplace/appliances/marketapps.rst
View file
Open in desktop
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exporting Appliances into vCenter Datastoreexists in the legacy documentation section

Original file line number Diff line number Diff line change
Expand Up @@ -173,7 +173,7 @@ and for VM templates:

.. note:: NICs are marked as auto, so they can work when the Marketplace Application is exported to a OpenNebula cloud. If you have NIC_ALIAS in the template, NICs are **not** marked as auto, you need to select the network when you instantiate it.

.. warning:: To avoid clashing names, if no name is specified, a hash is added at the end of the main object name. Sub objects like disks or VM templates in case of Service Template, have always the hash.
.. warning:: To avoid clashing names, if no name is specified, a hash is added at the end of the main object name. Sub objects like disks or VM templates in case of Service Template, always have the hash.

Marketplace Appliance Attributes
--------------------------------------------------------------------------------
Expand Down Expand Up @@ -244,16 +244,8 @@ Please take a look at the CLI reference to see how to use these actions. These o

Using Sunstone to Manage Marketplace Appliances
================================================================================
You can also import and export Marketplace Appliances using :ref:`Sunstone <sunstone>`. Select the Storage > MarketApps tab, and there, you will be able see the available Appliances in a user friendly way.
You can also import and export Marketplace Appliances using :ref:`Sunstone <fireedge>`. Select the Storage > Apps tab, and there, you will be able see the available Appliances in a user friendly way.

.. image:: /images/show_marketplaceapp.png
:width: 90%
:align: center

Exporting Appliances into vCenter Datastore
================================================================================

When using a vCenter datastore there are two ways of export an app into the marketplace:

- You can import an existing VM template from your vCenter and then select it when exporting the app. This will create a clone from your template and replace the disks by the ones downloaded.
- If you don't select any existing VM template, OpenNebula will automatically create a new one in vCenter and use it. This template will be reused when you export a new app.
Loading