1 / 24

Accessing Cloud Systems from WS-PGRADE/gUSE

Accessing Cloud Systems from WS-PGRADE/gUSE. Zoltán Farkas MTA SZTAKI LPDS zoltan.farkas@sztaki.mta.hu. Outline. Aim of this presentation Generic portal administrator tasks Generic initial user tasks SaaS execution mode: Portal administrator tasks Workflow node configuration

wei
Télécharger la présentation

Accessing Cloud Systems from WS-PGRADE/gUSE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Accessing Cloud Systems from WS-PGRADE/gUSE Zoltán Farkas MTA SZTAKI LPDS zoltan.farkas@sztaki.mta.hu

  2. Outline • Aim of this presentation • Generic portal administrator tasks • Generic initial user tasks • SaaS execution mode: • Portal administrator tasks • Workflow node configuration • IaaS execution mode: • Portal administrator tasks • Workflow node configuration • Generic user tasks (workflow cost estimate, submission, cost display) • Security aspects, using robot certificates

  3. Aim To show what are the necessary setup tasks on the portal side to cloud-enable a portal To show how the extension can be used To introduce the security aspects of using clouds in the portal

  4. Covered portal user roles Portal administrator The one who is able to configure the portal services Workflow developer The one who is able to create and run workflows End user The one who is able to use existing workflows

  5. Generic portal admin tasks I. Through the DCI Bridge Admin interface: http://foo.bar:8080/dci_bridge_service/conf

  6. Generic portal admin tasks II. Settings: Enable plugin: set to „Enabled” Number of threads: the plugin will manage at most so many jobs in parallel Number of resubmissions: the plugin will resubmit a failed job at most so many times Leave other settings unchanged

  7. Generic portal admin tasks III. Add access to CloudBroker Platform service Name: users will see the resource using this name URL: URL of the CBP service Own executable: see IaaS execution mode later

  8. Status The portal administrator has enabled the CloudBroker plugin in the DCI Bridge, and all the CloudBroker services that users would like to use have been added These are set by default: CB plugin is enabled, Public and SCI-BUS CB services are added

  9. Generic initial user tasks If one would like to configure CBP jobs, proper CBP user credentials have to be set Make use of the Security / CloudBroker portlet

  10. Saas and IaaS execution modes

  11. SaaS execution – Overview Enables portal users to run applications registered in the selected CBP service (for example AutoDock 1.0 Software and ad_worker.sh Executable) Thus, no executable, only input files have to be provided by the portal user

  12. SaaS execution „architecutre”

  13. SaaS – Portal admin tasks Nothing special Only the generic portal admin tasks have to be performed (configure CBP service access in DCI Bridge)

  14. SaaS – Workflow node configuration Set „Type” to „cloudbroker”, and „Name” to the CBP service to be used Afterwards, select Software, Executable, Resource, Region and Instance type for your job A cost estimate is displayed as well

  15. SaaS – Data cost estimate Depending on the selected resource, the data fee is displayed as well

  16. IaaS execution - Overview Enables to run executables uploaded by the user A specially prepared wrapper application has to be registered in the target CBP service (see Wrapper 1.0) This wrapper application must be configured the DCI Bridge plugin instance The portal will upload the user-provided executable as an input called „execute.bin” to the CloudBroker job, which will be started by the wrapper application

  17. IaaS execution „architecture”

  18. IaaS – Portal admin tasks The Software and Executable in the CBP enabling IaaS execution should be defined in the DCI Bridge Following Day 2’s hands-on these are: Software: „Wrapper XY 1.0” Executable: „Wrapper XY 1.0 guse_wrapper.sh”

  19. IaaS – Workflow node configuration Set „Type” to „cloudbroker”, and „Name” to the CBP service to be used Click „Enable own executable” Afterwards, select Software, Executable, Resource, Region and Instance type for your job A cost estimate is displayed as well (note: no cost is assigned to using the Resource below)

  20. IaaS – Data cost estimate Depending on the selected resource, the data fee is displayed as well (note: no cost is assigned to using the Storage below)

  21. Generic user tasks – Workflow cost estimate Once the workflow is fully configured, estimated cost can be calculated on-demand Simply click „Refresh” below the WF graph

  22. Generic user tasks – Workflow submission Once the workflow is ready, click „Submit” to submit a workflow instance After the workflow has been submitted, you can check its progress as usual

  23. Generic user tasks – Workflow cost display Cost of individual jobs can be checked Overall workflow cost can be checked as well

  24. Security aspects CloudBroker entity (Resource, Software) visibility: Private: only the user who defined the entity + admins can use it Protected: users of the organization where the defining user belongs to + admins can use it Public: every user of the CloudBroker Platform service can use it Robot certificates: Can be assigned to CloudBroker jobs Take care (EGI VO Portal Policy): Enable only for the SaaS model, or Enable for IaaS model, but do not allow the users to upload their executables

More Related