Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
Sender Email:
-
HD-Chapter:Cloud
-
HD-Enabler:Pegasus
Description
Dear FiWare team,
In our application (HybridSuite, part of the Finodex accelerator) we want
to implement a workflow where VMs are instantiated and configured on demand
and depending on processing needs.
Ideally we would need an api offering PaaS management functionalities
(similar to
http://docs.aws.amazon.com/AWSEC2/latest/CommandLineReference/ApiReference-cmd-StartInstances.html
)
When specifying our solution, the PaaS manager GE (
http://catalogue.fiware.org/enablers/paas-manager-pegasus) seemed to be a
good fit for our scenario.
However now that we are in the process of integrating the GE we are having
difficulties in understanding whether 1) our scenario is supported and 2)
how to implement it.
The documentation states "This GE reference implementation product is only
of interest to potential FIWARE instance providers and therefore has been
used to build the basic FIWARE platform core infrastructure of the FIWARE
Lab".
Moreover the course at the eLearning platform (
http://edu.fiware.org/course/view.php?id=47) mentions only the Blueprint
templates.
So, our questions are:
1. Is it possible to implement our scenario using the PaaS manager API in
FILab? (start and stop instances or images with an API)
2. If not, we are considering the option of creating Blueprint templates
with the required configuration and manually open/ close template
instances. Will this be enough as far as our obligations to use PaaS are
concerned? (not that it's one of the GEs we describe in our technical
archtecture).
3. Can we create templates with custom software configuration (the software
catelogue in the template tier is too limited)?
A prompt reply would be appreciated.
Best regards,
Efthimios Bothos.
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-tech-help
[Created via e-mail received from: Efthimios Bothos <mpthimios@hybridstat.gr>]
Activity
- All
- Comments
- History
- Activity
- Transitions
Dear Henar,
Thank you for the prompt reply.
Let me explain the situation in more details.
Our idea is accepted for funding as part of the Finodex accelerator
programme.
We have specified a technical description of our proposed system where we
claim to use the PaaS manager.
Now we are in the process of implementing the idea which will be evaluated
by the end of September.
At the time of the specification writing we used the following information
on the PaaS manager:
"Self-Service provisioning and life cycle management of middleware
including the provisioning of the required virtual resources at IaaS and
configuration of the whole software stack on that virtual resources."
(see the PaaS description here: http://catalogue.fiware.org/enablers/)
Based on our technical description we have to (this is somehow an
"obligation") to use the PaaS GE.
I understand that PaaS Manager is some kind of extension to Openstack and
that we can only access it through the "Blueprint templates".
So if we create a Blueprint template will this be OK for the evaluation of
our idea in the next stage?
If you don't have this information, could point us to a colleague who could
inform us?
I checked the Openstack use in FIlab from here: https://forge.fiware.org/
plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSpecification.Cloud.
SelfServiceInterfaces
and I understand that Openstack APIs cannot be accessed by application
developers but these are integrated in the FIlab portal which we use anyway
for our prototype.
In terms of software additions in the catalogue of the templates, it would
be useful to have the R programming language (http://www.r-project.org/).
Thanks again!
-Thimios.
On Mon, Jul 13, 2015 at 9:48 AM, Help-Desk <jira-help-desk@fi-ware.org>