Difference between revisions of "Fedcloud-tf:WorkGroups:Scenario8:AppDB-VA-Marketplace"

From EGIWiki
Jump to: navigation, search
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{TOC_right}}
+
#REDIRECT[[Federated_Cloud_Architecture#VM_Image_management]]
 
 
= The mission  =
 
 
 
Since the 4th quarter of 2013, the [http://appdb.egi.eu/ EGI Applications Database] (hereforth EGI&nbsp;AppDB) has been extended to include a community-driven service namely the Vistual Appliance marketplace, which:<br>
 
 
 
*stores and provides to the public, '''Virtual Appliances related metadata'''
 
*acts as '''distribution mechanism''' between the submitters, the community and the Resource Providers within the EGI FedCloud infrastructure<br>
 
 
 
<br>
 
 
 
= Prologue  =
 
 
 
The [https://appdb.egi.eu/ EGI AppDB] service has been extended to support Virtual Appliances in the form of the Virtual Appliance Marketplace. The Virtual Appliance Marketplace brings about a new category of software entries, called virtual appliances, which are, in all practical manners, clean-and mean virtual machine images designed to run on a virtualization platform, that provide a software solution out-of-the-box, ready to be used with minimal or no set-up needed weithing the EGI Federated Cloud infrastruture. AppDB's Virtual Appliance Marketplace will provide the ground for managing and publishing versioned repositories of virtual appliances, in a way that integrates with the existing HEPiX [https://github.com/hepix-virtualisation/vmcaster VMCaster] / [https://github.com/hepix-virtualisation/vmcatcher VMCatcher] framework, currently in use by the EGI. Besides basic features embedded in the AppDB portal itself, such as creating, publishing, enabling/disabling, and archiving or deleting VA versions, it will also use the HEPiX [https://github.com/hepix-virtualisation/vmcaster VMCaster] command line tool for uploading full VA versions, as well as a web-based dashboard for monitoring the individual uploads injected from the command line. <br><br>
 
 
 
= Context diagram  =
 
 
 
<br>
 
 
 
::'''AppDB Portal''': Using the AppDB portal:
 
::*a typical ''visitor'' is able to search, find and download, ready to be used virtual machine images that constitute the latest Virtual Appliance version
 
::*a ''VMI submitter/user'' is able to submit/upload VA version metadata (in the form of signed image lists)
 
 
 
::'''vmcaster@appdb module''': This module satisfies three functions:
 
::#acts as the AppDB interface for accepting individual uploads injected by a ''VMI submitter/user'' using the HEPiX [https://github.com/hepix-virtualisation/vmcaster VMCaster] command line tool.
 
::#offers a [https://vmcaster.appdb.egi.eu/ web-based dashboard] for monitoring the individual uploads injected via the aforementioned tool.
 
::#compiles the signed image lists per each published VA version and make them available for subscription by the ''Resource Providers'' (using the HEPiX [https://github.com/hepix-virtualisation/vmcatcher VMCatcher]tool)
 
 
 
::'''AppDB API''': By using the AppDB API, ''external services and/or applications'' are able to interact with our system.
 
 
 
[[Image:AppDB-VM-big-picture.png|center|800px|AppDB-VM-big-picture.png]] <br>
 
 
 
= Workflow  =
 
 
 
== Useful terms  ==
 
 
 
*'''Virtual Appliances''' (VAs) are ready-to-run virtual machines packaged with an operating system and software application(s)
 
*A '''Virtual Appliance''' '''version''' (VA&nbsp;version) provides a list of the versioned '''Virtual Machines Images '''(VMIs) that constitutes the said Virtual Appliance. '''Each VA version '''is further distributed and therefore mapped, to a single -- and unique within the EGI&nbsp;AppDB -- '''Virtual Machine Image list'''.<br>
 
*A '''Virtual Machine Image List '''is the SMIME X509 signed, JSON&nbsp;representation of a '''Virtual Appliance Version'''.
 
*A '''Virtual Machine Image''' (VMI) is the software implementation of a machine (i.e. a computer) that executes software application(s) just like a physical machine <br><br>
 
 
 
== The Virtual Appliance Version workflow  ==
 
 
 
Below you may find a graphical representation of the workflow defining the lifecycle of a Virtual Appliance Version.
 
 
 
[[Image:Appdb-vm-workflow.png|center|1000px|Appdb-vm-workflow.png]] <br>
 
 
 
= Prerequisites  =
 
 
 
In order to start using the EGI&nbsp;AppDB as a Virtual Appliance Marketplace you will need to:<br>
 
 
 
#Obtain a&nbsp; valid [https://www.egi.eu/sso EGI&nbsp;SSO]&nbsp;account<br>
 
#Login to the [http://appdb.egi.eu EGI&nbsp;AppDB] portal and claim your profile<br>
 
#Register your Virtual Appliance. The Virtual Appliance instance within the AppDB, provides the high level details of your work and will act as the placeholder for the released Virtual Appliance versions.<br>
 
#In case you would like to acquire write access to an '''already registered Virtual Appliance''', then please make submit a request to ''''Join as a contact'''' to the said VA; upon acceptance by the owner, you will have gained write permissions and therefore be able to modify VA&nbsp;metadata and manage its versions.
 
 
 
<br>
 
 
 
= Quick start guides &amp;&nbsp;HowTos  =
 
 
 
The Quick start guides and HowTos listed in this section, cover the usage of the EGI AppDB service as Virtual Appliance Marketplace, either through the '''AppDB portal''' (the graphical way) or by using the '''HEPiX [https://github.com/hepix-virtualisation/vmcaster VMCaster] command line tool'''. <br><br>
 
 
 
== Through the AppDB portal  ==
 
 
 
=== <div style="padding:2px;background: #e5e5e5;box-shadow: 5px 5px 5px #A0A0A0;padding: 8px;"><span style="color:#000"><span style="font-weight:normal">portal:</span> Register a Virtual Appliance (VA)</span></div>  ===
 
 
 
<br>
 
 
 
::'''1.''' Login to the [http://appdb.egi.eu EGI&nbsp;AppDB]&nbsp;.
 
 
 
::'''2.''' On the top left corner there is the option to Register a New Virtual Appliance
 
 
 
[[Image:Register new va.png|center|800px|Register new va.png]]
 
 
 
<br>
 
 
 
::'''3.''' Fill in the mandatory Virtual Appliance high level metadata.
 
 
 
::- The VA '''name''' - '''should be unique '''in the EGI AppDB, so that a unique canonical URL may be assigned
 
::- A '''short description''' (one sentence)
 
::- One or more '''discipline''''''s''' that best characterize/classify the newly registered VA. This will help us further promote your work within the specific scientific communities.
 
::- Full '''description''' and/or full '''abstract'''.
 
::- Optionally, we advise that you, to '''set the logo '''that will be displayed under the details dialog of the VA.
 
 
 
[[Image:Register new va dialog.png|center|800px|Register new va dialog.png]]
 
 
 
<br>
 
 
 
::'''4. '''Click on the '''save button '''and thats it!! Additional information, such as associated VOs, countries, middleware(s), tags, people etc, will be available for edit after saving.
 
 
 
----
 
 
 
<br>
 
 
 
=== <div style="padding:2px;background: #e5e5e5;box-shadow: 5px 5px 5px #A0A0A0;padding: 8px;"><span style="color:#000"><span style="font-weight:normal">portal:</span> Create a new VA version</span></div>  ===
 
 
 
<br>
 
 
 
::'''1.''' Click on the '''Manage VA versions''' option or alternatively, go directly to the '''Virtual Appliances Versions tab'''; both are available at the top of the VA&nbsp;dialog.
 
 
 
[[Image:Manage va version.png|center|800px|Manage va version.png]]
 
 
 
<br>
 
 
 
::'''2.''' From the VA Versions tab you should be able to either inspect your '''latest published version''', optionally going through '''previously released versions '''or to '''create a new one'''.
 
 
 
[[Image:Manage va version options.png|border|center|800px|Manage va version options.png]]
 
 
 
<br>
 
 
 
::'''3.''' Upon navigating to the '''Working/New Version''' nested tab and by clicking on the '''Create New Version''' button, you will be able to start a new VA version, a '''clone of the latest published one''' (if exists), and therefore:
 
 
 
<br>
 
 
 
::*'''add/remove '''virtual machine images
 
::*'''modify the metadata''' of the existed ones
 
::*'''reuse images '''from previous versions, '''either 'as is' or for updating them'''&nbsp;(see more details at the FAQ item [[#When_should_i_reuse_an_image.3F|When should i reuse an image]])
 
::*'''modify version wide metadata '''like version number, expiration date etc.<br>
 
 
 
[[Image:Manage va version create new.png|center|800px|Manage va version create new.png]]
 
 
 
<br>
 
 
 
::'''4.''' Add one -or more- '''new groups''' and add one or more '''new images''' per group.
 
 
 
[[Image:Manage va version create new group image.png|center|800px|Manage va version create new group image.png]]
 
 
 
<br>
 
 
 
::'''5.''' '''Fill in''' and/or '''Update''' the metadata.
 
 
 
::At the time of this writing, the needed metadata are:
 
 
 
::*'''Version level'''
 
::**Version number
 
::**Expiration date. (When the version will expire)
 
::**Description
 
 
 
::*'''Group level'''
 
::**A Group title [example: My Scientific Linux images]
 
::**Group notes (optional) [example: For Root password please contact me.]
 
 
 
::*'''Image level'''
 
::**Image version
 
::**Location, to a public URI (only http/https protocols are supoorted)
 
::**Automatic integrity check (ON / OFF[default])
 
::***if '''unchecked''' (OFF), then you will have to provide the SHA512 checksum and the filesize '''manually'''
 
::***if '''checked''' (ON), then the system will make an attempt to download the image and calculate the SHA512 checksum and filesize '''automatically'''.
 
::::'''For more details see tht FAQ entry [[#What_is_the_Autocheck_image_file_metadata_integrity|What is the Autocheck image file metadata integrity]]'''.
 
 
 
::**Title for the Image
 
::**Description (optional)
 
::**Comments (optional)
 
::**OS [example: Linux]
 
::**OS Version [example: Scientific Linux 6]  
 
::**Architecture [example: x86_64]
 
::**Format [example: raw]
 
::**Minimum cores (optional)
 
::**Recommended cores (optional)
 
::**Minimum ram (optional)
 
::**Recommended ram (optional)
 
::**Hypervisor
 
 
 
<br>
 
 
 
::'''7.''' Click '''Save'''.
 
 
 
[[Image:Manage va version create new save.png|center|800px|Manage va version create new save.png]]
 
 
 
----
 
 
 
<br>
 
 
 
=== <div style="padding:2px;background: #e5e5e5;box-shadow: 5px 5px 5px #A0A0A0;padding: 8px;"><span style="color:#000"><span style="font-weight:normal">portal:</span> Verify a VA version</span></div>  ===
 
 
 
<br>
 
 
 
::This option is available to the user if and '''only''' if at least one of the participating images has the [[#What_is_the_Autocheck_image_file_metadata_integrity|Autocheck image file metadata integrity]] '''checked'''.
 
 
 
::'''1.''' Click on the '''Verify''' button or on '''Verify &amp; Publish''' to perform verification and publishing in one step.
 
 
 
[[Image:Manage va version verify.png|center|800px|Manage va version verify.png]] <br>
 
 
 
::'''2a.''' If '''all the images''' having the [[#What_is_the_Autocheck_image_file_metadata_integrity|Autocheck image file metadata integrity]] checked, '''have been successfully verified''', then either the VA version is ready to be published or its being directly published in case the '''Verify &amp; Publish''' button was initially clicked.
 
 
 
[[Image:Manage va version verify status-success.png|center|800px|Manage va version verify status-success.png]] <br>
 
 
 
::'''2a.''' If '''at least one image''' having the [[#What_is_the_Autocheck_image_file_metadata_integrity|Autocheck image file metadata integrity]] checked, '''could not be verified''', then the associated VA version '''can not be published'''. For that image, the sha512 checksum and the filesize should be manually filled.
 
 
 
[[Image:Manage va version verify status failed.png|center|800px|Manage va version verify status failed.png]] <br>
 
 
 
::'''3.''' Upon '''successful verification''' the '''Publish''' option/button should be '''available'''.
 
 
 
[[Image:Manage va version verify status-publish.png|center|800px|Manage va version verify status-publish.png]] <br>
 
 
 
<br>
 
 
 
----
 
 
 
<br>
 
 
 
=== <div style="padding:2px;background: #e5e5e5;box-shadow: 5px 5px 5px #A0A0A0;padding: 8px;"><span style="color:#000"><span style="font-weight:normal">portal:</span> Publish a VA version</span></div>  ===
 
 
 
<br>
 
 
 
::*Upon clicking on the '''Publish button''':
 
::**The given VA version '''becomes the Latest one'''
 
::**An '''image list '''file is generated and becomes '''available for the Resource Providers'''
 
::**The '''previously published VA Version''' gets to the '''Previous/Archived versions tab''' and remains there for historical and auditing purposes.
 
 
 
<br>
 
 
 
[[Image:Manage va version publish.png|center|800px|Manage va version publish.png]]
 
 
 
----
 
 
 
<br>
 
 
 
=== <div style="padding:2px;background: #e5e5e5;box-shadow: 5px 5px 5px #A0A0A0;padding: 8px;"><span style="color:#000"><span style="font-weight:normal">portal:</span> Delete a VA version</span></div>  ===
 
 
 
<br>
 
 
 
::*As long as a VA version '''has not been published''' yet, it may be '''deleted'''.(Please note that this action can not be undone.)
 
 
 
[[Image:Manage va version delete.png|center|800px|Manage va version delete.png]]
 
 
 
----
 
 
 
<br>
 
 
 
=== <div style="padding:2px;background: #e5e5e5;box-shadow: 5px 5px 5px #A0A0A0;padding: 8px;"><span style="color:#000"><span style="font-weight:normal">portal:</span> Show/enable or Hide/disable a VA version</span></div>  ===
 
 
 
<br>
 
 
 
::*This operation is available '''only for published''' VA versions.
 
::*The result of using the Show/enable or Hide/disable functions is to:
 
::**Show/Hide the '''VA version metadata''' to/from the public
 
::**Enable/Disable the '''VA version image list''' for the Resource Providers (and from the public in general)
 
 
 
[[Image:Manage va version show-hide.png|center|800px|Manage va version show-hide.png]]
 
 
 
----
 
 
 
<br>
 
 
 
<br>
 
 
 
== Using the VMCaster command line tool (CLI)  ==
 
 
 
<br>
 
 
 
::The reader of this section should:
 
::*Be '''familiar''' with the HEPiX [https://github.com/hepix-virtualisation/vmcaster vmcaster] and [https://github.com/hepix-virtualisation/vmcatcher vmcatcher] toolset.
 
::*Have access to a machine with the aforementioned tools, '''correctly installed'''.
 
::*He/she should have [[#portal:_Register_a_Virtual_Appliance_.28VA.29|register a Virtual Appliance]] or to have write access to it.
 
 
 
<br>
 
 
 
=== <div style="padding:2px;background: #e5e5e5;box-shadow: 5px 5px 5px #A0A0A0;padding: 8px;"><span style="color:#000"><span style="font-weight:normal">vmcaster CLI:</span> Configure the egiappdb '''protocol'''</span></div>  ===
 
 
 
<br>
 
 
 
::*Edit or create the <code>.vmcaster.cfg</code> file in your home directory and append the following content.
 
<pre>[user@quido-x:~]$ cat ~/.vmcaster.cfg
 
 
 
[appdb]
 
server = "vmcaster.appdb.egi.eu"
 
protocol = "egiappdb"
 
uriMatch = ".*"
 
uriReplace = "egiappdb://_YOUR_EGI_SSO_USERNAME_@vmcaster.appdb.egi.eu"
 
 
 
</pre>
 
<br>
 
 
 
----
 
 
 
=== <div style="padding:2px;background: #e5e5e5;box-shadow: 5px 5px 5px #A0A0A0;padding: 8px;"><span style="color:#000"><span style="font-weight:normal">vmcaster CLI:</span> Create a new VA version</span></div>  ===
 
 
 
<br>
 
 
 
::'''1. '''Use the dedicated '''VMCaster image list identifier ''' produced automatically by the AppDB service (see [[#How_to_get_the_VMCaster_image_list_identifier_using_the_AppDB_portal|How to get the VMCaster image list identifier using the AppDB portal]]).
 
 
 
{{Template:Block-comment
 
| name=Notice
 
| text=Lets assume that the image list identifier is: <code>6b470d15-835a-42ec-b568-002393f4dc58</code>
 
}}
 
 
 
<br>
 
 
 
::'''2.''' Create a '''new image list''' as described in the [https://github.com/hepix-virtualisation/vmcaster VMCaster] documentation, using the aforementioned image list identifier.
 
 
 
<br>
 
 
 
::'''3.''' '''Add/remove/modify images''' as described in the [https://github.com/hepix-virtualisation/vmcaster VMCaster] documentation.
 
 
 
{{Template:Block-comment
 
| name=Notice
 
| text=Lets assume that the identifier of one of the included images is: <code>05535860-71b1-48cf-94e3-af05f169be7b</code>
 
}}
 
 
 
<br>
 
 
 
::'''4.''' '''Optionally''', perform some sort of '''grouping''' with the included '''images'''.
 
<pre>vmcaster  --select-image _IMAGE_IDENTIFIER_ --key-set-image  "ad:group" --key-value-image "_IMAGE_GROUP_"
 
</pre>
 
full example:
 
<pre>vmcaster  --select-image 05535860-71b1-48cf-94e3-af05f169be7b --key-set-image "ad:group" --key-value-image "My Scientific Linux Images"
 
</pre>
 
<br>
 
 
 
::'''5.''' '''Visually inspect the image list''', as a cross-check.
 
<pre>vmcaster  --select-imagelist _IMAGE_LIST_IDENTIFIER_ --show-imagelist
 
</pre>
 
full example:
 
<pre>vmcaster  --select-imagelist 6b470d15-835a-42ec-b568-002393f4dc58 --show-imagelist
 
</pre>
 
<br>
 
 
 
::'''6.''' '''Upload/Submit''' the image list to the [https://vmcaster.appdb.egi.eu/ vmcaster@appdb] end point.
 
::'''NOTE:''' vmcaster will prompt you for a passphrase and an 'Appdb password'. The first is for signing your submitted image list and the second is your personal EGI SSO account password.
 
<pre>vmcaster  --select-imagelist _IMAGE_LIST_IDENTIFIER_ --upload-imagelist
 
Enter passphrase:[_YOUR_x509_CERT_PASSPHRASE_]
 
Appdb password for 'user':[_YOUR_EGI_SSO_PASSWORD_]
 
</pre>
 
full example:
 
<pre>vmcaster  --select-imagelist 6b470d15-835a-42ec-b568-002393f4dc58 ---upload-imagelist
 
</pre>
 
<br>
 
 
 
::'''7.''' Upon completion, the vmcaster tool will prompt with an error message &amp; code in case of a failure or no message in case of success.
 
::In any case, a '''URL''' will be provided, directing the user to the [https://vmcaster.appdb.egi.eu/ vmcaster@appdb Dashboard], where he/she can see more details about the status of the submission.
 
<pre>vmcaster  --select-imagelist 6b470d15-835a-42ec-b568-002393f4dc58 --upload-imagelist
 
Enter passphrase:[_YOUR_x509_CERT_PASSPHRASE_]
 
Appdb password for 'user':[_YOUR_EGI_SSO_PASSWORD_]
 
details:https://vmcaster.appdb.egi.eu/vmlist/status/item/87
 
submission_id:87
 
</pre>
 
<br>
 
 
 
::'''8.''' If all's gone well, using your favorite web browser, navigate to the EGI AppDB portal and [[#portal:_Publish_a_VA_version|Publish the submitted VA version]]
 
 
 
<br>
 
 
 
----
 
 
 
=== <div style="padding:2px;background: #e5e5e5;box-shadow: 5px 5px 5px #A0A0A0;padding: 8px;"><span style="color:#000"><span style="font-weight:normal">vmcaster CLI:</span> Publish a VA version</span></div>  ===
 
 
 
<br>
 
 
 
::*In case you would like to upload and publish you image list in one move
 
::use the flag <code>--flag "egiappdb:publish=true"</code> while uploading.
 
<pre>vmcaster  --select-imagelist _IMAGE_LIST_IDENTIFIER_ --upload-imagelist --flag "egiappdb:publish=true"
 
</pre>
 
full example:
 
<pre>vmcaster  --select-imagelist 6b470d15-835a-42ec-b568-002393f4dc58 --upload-imagelist --flag "egiappdb:publish=true"
 
</pre>
 
<br>
 
 
 
----
 
 
 
= Information for the Resource Providers  =
 
 
 
<span style="color:#FFFFFF; background:#800000">To be defined.</span> <br><br><br>
 
 
 
= Frequently Asked Questions (FAQ)  =
 
 
 
== What is the Autocheck image file metadata integrity  ==
 
 
 
<br>
 
 
 
::'''Autocheck image file metadata integrity''' option is available on '''per image basis '''and '''if checked '''('''optional''') it will command our system (upon verification - not upon saving) to temporarily '''download the image '''from the ''Location'' given, to '''our/AppDB''' servers, and '''calculate the sha512 checksum '''and '''the filesize'''. By following this option the user does not have to fill in the respective metadata values manually.
 
 
 
::There are quite a few cases that this process '''could fail'''. For example:
 
::*The image is not accessible neither over http nor https protocol (at the time being '''only''' http(s) protocol is supported).
 
::*The http server requires authentication
 
::*The ''Location'' given was not found.
 
::*etc..
 
 
 
::One more thing that the user should be aware of, is '''the time needed for this process to be finalized'''. Downloading a couple of hundreds of data over http and calculate the sha512 checksum of the downloaded image file, could be considered as a '''time consuming process'''. Depending on the bandwidth of the network it could take from a few seconds up to a few tenths of minutes.
 
 
 
[[Image:Manage va version autocheck metadata integrity.png|center|800px|Manage va version autocheck metadata integrity.png]]
 
 
 
----
 
 
 
== When should i reuse an image?  ==
 
 
 
::You are strongly advised to '''reuse an image''' that was published in the past, in the following two cases:
 
::'''A''': reuse it ''''as is'''' in the new Virtual Appliance version (use-case: '''republishing an image''')<br>
 
::'''B''': use it as a '''starting point/template''' for describing an '''image update''' (use-case: '''image update''')<br>
 
 
 
[[Image:Manage reuse image.png|center|800px|manage_reuse_image.png]]
 
 
 
----
 
 
 
== How to get the VMCaster image list identifier using the AppDB portal  ==
 
 
 
::'''1.''' Using the AppDB portal, navigate to the registered Virtual Appliance
 
 
 
::'''2.''' On the right side of the title pane click on the <code>identifier</code> control.
 
 
 
[[Image:Cli va id.png|center|800px|Cli va id.png]] <br>
 
 
 
= VMCaster CLI Error Codes  =
 
 
 
This section lists the resulting errors that might occurred when using the VMCaster tool in order to upload VA versions in the form of signed image lists, to the EGI AppDB service. <br>
 
 
 
::*In any case, please do not hesitate to [http://appdb.egi.eu/pages/contact/feedback contact us].
 
 
 
{| width="1000" cellspacing="1" cellpadding="1" border="1" align="center"
 
|-
 
| style="width: 200px;text-align: center; background-color: gray;color: white;font-weight:bold;" | Error
 
| style="width: 50px;text-align: center; background-color: gray;color: white;font-weight:bold;" | Code
 
| style="width: 300px;text-align: center; background-color: gray;color: white;font-weight:bold;" | Description
 
| style="width: 300px;text-align: center; background-color: gray;color: white;font-weight:bold;" | Corrective actions
 
|-
 
|
 
====== ERROR_ADVMC_1001_UNAUTHORIZED<br>  ======
 
 
 
| style="text-align: center;" | 1001
 
| You are not authorized to perform this action.<br>
 
| Please follow steps 1 &amp; 2 as described in the [[#Prerequisites|Prerequisites]] section.
 
|-
 
|
 
====== ERROR_ADVMC_1002_NO_FILE_SUBMITTED  ======
 
 
 
| style="text-align: center;" | 1002<br>
 
| No image list file submitted.<br>
 
| Please read the section [[#.23Using_the_VMCaster_command_line_tool_.28CLI.29|Using the VMCaster command line tool]] and check out: <br>
 
*how the VMCaster should be configured,
 
*how it can be used to upload either new VA Versions or updates.
 
 
 
|-
 
|
 
====== ERROR_ADVMC_1003_NOT_VALID_JSON  ======
 
 
 
| style="text-align: center;" | 1003<br>
 
| The image file you have submitted, does not NOT follow a valid JSON format and can not being further processed.<br>
 
| Check the format of the produced image list.<br>
 
|-
 
|
 
====== ERROR_ADVMC_1004_XML_VALIDATOR  ======
 
 
 
| style="text-align: center;" | 1004<br>
 
| Internal error. Not correct or well formed, image list submitted.<br>
 
| It seams that the submitted image list is not valid. Please consider [http://appdb.egi.eu/pages/contact/feedback contacting us].<br>
 
Also please consider sending us either the vmcaster@appdb dashboard '''reference URL''' or the '''submission ID'''.<br>
 
 
 
|-
 
|
 
====== ERROR_ADVMC_1005_MISSING_APPDB_ID  ======
 
 
 
| style="text-align: center;" | 1005<br>
 
| Internal error: The application id (ad:appid) is missing. <br>
 
| It seams that the submitted image list is not valid. Please consider [http://appdb.egi.eu/pages/contact/feedback contacting us].
 
Also please consider to send us either the vmcaster@appdb dashboard '''reference URL '''or the '''submission ID'''. <br>
 
 
 
|-
 
|
 
====== ERROR_ADVMC_1006_INVALID_IMAGELIST_IDENTIFIER  ======
 
 
 
| style="text-align: center;" | 1006<br>
 
| The provided image list identifier (dc:identifier) is not valid.<br>
 
| You have provide a invalid image list identifier (dc:identifier). Please read&nbsp; section [[#Using_the_VMCaster_command_line_tool_.28CLI.29|Using the VMCaster command line tool]] and the FAQ item: [[#How_to_get_the_VMCaster_image_list_identifier_using_the_AppDB_portal|How to get the VMCaster image list identifier using the AppDB portal]].<br>
 
|-
 
|
 
====== ERROR_ADVMC_1007_NO_VA_APPDB_ID  ======
 
 
 
| style="text-align: center;" | 1007<br>
 
| Internal error. The application id (ad:appid) related with the provided image list identifier (dc:identifier), it is not correct.<br>
 
|
 
It seams that the submitted image list is not valid. Please consider [http://appdb.egi.eu/pages/contact/feedback contacting us].
 
 
 
Also please consider to send us either the vmcaster@appdb dashboard '''reference URL '''or the '''submission ID'''.
 
 
 
|-
 
|
 
====== ERROR_ADVMC_1008_NO_PERMISSION_TO_THE_VA  ======
 
 
 
| style="text-align: center;" | 1008<br>
 
| You DO NOT have access to submit versions for the given Virtual Appliance.<br>
 
| You are not authorized to perform this action on the given Virtual Appliance.<br>
 
Please follow the steps 1, 2 and 4 as described at the [[#Prerequisites|Prerequisites]] section.<br>
 
 
 
|-
 
|
 
====== ERROR_ADVMC_1009_INVALID_WRAPPER_XML  ======
 
 
 
| style="text-align: center;" | 1009<br>
 
| Internal error. Post data are not correct.<br>
 
| rowspan="3" | It seams that the submitted image list is not valid. Please consider [http://appdb.egi.eu/pages/contact/feedback contacting us].
 
Also please consider to send us either the vmcaster@appdb dashboard '''reference URL '''or the '''submission ID'''.<br>
 
 
 
|-
 
|
 
====== ERROR_ADVMC_1010_INVALID_WRAPPER_SCHEMA  ======
 
 
 
| style="text-align: center;" | 1010<br>
 
| Internal error. <br>
 
|-
 
|
 
====== ERROR_ADVMC_1011_UKNOWN_ACTION  ======
 
 
 
| style="text-align: center;" | 1011<br>
 
| Internal error. Uknown action submitted.<br>
 
|}
 

Latest revision as of 13:08, 8 June 2015