Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Component/s: Finish
-
Labels:None
Description
Dear Robin,
Yes, currently all granted SMEs are asked to fill-in the FIWARE assessment survey in order to help us identify the FIWARE success stories but also to get some feedback about the platform.
I tried to find some answers for your questions from the FIWARE technical team. And here is what they have replied:
“The question about which PEP to use depends on what other components are you going to use. Steelskin was created to be used in Telefonica's IoT FIWARE-based Platform, that makes use of some of the official FIWARE GEs, but uses Telefonica's own implementation for other components (PEP is an example, and the Access Control GE, Keypass is another). Most of the components of Telefonica's IoT Platform are Open Source and, in theory, fully compatible with other FIWARE software, but you should take into account that none of them have been tested with other FIWARE Ges, so compatibility can't be guaranteed (although, if there are compatibility issues they should be easy to solve and contribute). There is plenty of documentation in the Steelskin PEP Github page about how it works, and you can also find a guide on how to install the proper users and permissions in Openstack Keyston for the PEP proxy to work as it should.
On the other hand, Wilma is the reference implementation for the PEP Proxy GE, and, as such, it is supposed to integrate seamlessly with any other official FIWARE GE, so if you are going to use other official GEs, it would be your best option. Wilma is also the PEP Proxy used in the global instances in FIWARE Lab, so the behavior should be the same in both your local installations and the global ones.
Concerning Openstack Keystone and Keyrock, the later is a fork of the official Keystone repository, adding some functionalities that are not present in the official version. This functionalities are going to be encapsulated in a plugin in the future, so they can be contributed to the official branch or installed as a separate RPM, but this work is still pending today. So, once the plugin has been contributed, they will be basically the same thing.“
Based on their reply, my recommendation would be to use Wilma Pep Proxy and the KeyRock to be more in line with the standard FIWARE platform.
Regarding the installation Object Storage and IDM, in theory you do not need to install these GEs (but of course you can if you really want to).
It may be much easier to use the global instances of these GEs on FIWARE Lab instead.
Hope this helps a bit.
Kind regards,
ilknur
From: Robin Puthli r.puthli@itude.com
Sent: Tuesday, August 11, 2015 3:47 PM
To: Chulani, Ilknur
Subject: Questions regarding FIWARE
Hello Ilknur,
We have been accepted into the FInish accelerate program, which is probably why i received an email regarding FIWARE usage assessment.
Regarding a number of FIWARE components we have a number of questions which the FIWARE GE website and GE sites do not answer for us.
1. We intended to use KeyRock iDM, but with the Object Store GE the installer added Openstack Keystone. Now we are confused what the difference is between Keystone and Keyrock. There does not seem to be much difference between the products. What does Keyrock add over Keystone?
2. We intended to use the Wilma PEP proxy but see there is also an Orion PEP proxy which connects to Openstack Keystone. What reasons are there to choose one over the other if we opt for Keystone?
3. The Object Store GE seems to be identical to Openstack Swift. Are we missing something here?
Best regards,
Robin Puthli
Met vriendelijke groet,
Robin Puthli
Directeur
[cid:image001.png@01D0D6AB.8A691AC0]
Lageweg 2
3703 CA Zeist
■ mob +31(0) 6 21 88 22 86
■ tel direct +31(0)30 692 60 04
■ tel receptie +31(0)30 699 70 20
■ mail r.puthli@itude.com<r.puthli@itude.com>
■ google.com/+RobinPuthli<http://google.com/+RobinPuthli>
■ skype: robin.puthli
■ linkedIn:nl.linkedin.com/in/puthli/<http://nl.linkedin.com/in/puthli/>
www.itude.com<http://www.itude.com/> ■ K.v.K. 30146090
_____________________________________________________________________________
**Op deze mail is een disclaimer van toepassing. De inhoud daarvan is te lezen op onze website**
Bu mesaj ve ekleri gönderilen kişiye özeldir ve gizli bilgiler içerebilir. Eğer mesajın gönderilmek istendiği kişi değilseniz lütfen kopyalamayınız, başkalarına göndermeyiniz ve göndericiyi bilgilendiriniz. Internet üzerinden gönderilen mesajların güvenli ve hatasız olduğunun garantisi olmadığından Atos grubu mesajın içeriğinden sorumlu tutulamaz. Göndericinin bilgisayarı anti-virüs sistemleri tarafından taranmaktadır, ancak yine de mesajın virüs içermediği garanti edilemez ve gönderici, meydana gelebilecek zararlardan sorumlu tutulamaz.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
_______________________________________________
Fiware-finish-coaching mailing list
Fiware-finish-coaching@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-finish-coaching
Hi Robin,
Actually best thing to do is to use the official support mailing lists:
There are also lots of Fiware related questions and answers in Stackoverflow (you can search with tag fiware) .
Other than this, a new support platform will also be launched very soon :
https://ask.fiware.org/questions/
This last one will probably be the best place to get support once it’s fully active.
Kind regards,
ilknur
From: Robin Puthli r.puthli@itude.com
Sent: Friday, August 14, 2015 5:01 PM
To: Chulani, Ilknur
Subject: Re: Questions regarding FIWARE
Thanks Ilknur!
If i have further technical questions regarding the FIWARE GE’s. Who should i ask my guys to contact? Is there a single Fiware support forum somewhere? At the moment each GE’s seems to have its own way of providing support, which is a little confusing when we try to integrate them.
Regards,
Robin
Met vriendelijke groet,
Robin Puthli
Directeur
[cid:image001.png@01D0D6B2.E07D86B0]
Lageweg 2
3703 CA Zeist
■ mob +31(0) 6 21 88 22 86
■ tel direct +31(0)30 692 60 04
■ tel receptie +31(0)30 699 70 20
■ mail r.puthli@itude.com<r.puthli@itude.com>
■ google.com/+RobinPuthli<http://google.com/+RobinPuthli>
■ skype: robin.puthli
■ linkedIn:nl.linkedin.com/in/puthli/<http://nl.linkedin.com/in/puthli/>
www.itude.com<http://www.itude.com/> ■ K.v.K. 30146090
_____________________________________________________________________________
**Op deze mail is een disclaimer van toepassing. De inhoud daarvan is te lezen op onze website**
Op 14 aug. 2015, om 15:09 heeft Chulani, Ilknur <ilknur.chulani@atos.net<ilknur.chulani@atos.net>> het volgende geschreven:
Dear Robin,
Yes, currently all granted SMEs are asked to fill-in the FIWARE assessment survey in order to help us identify the FIWARE success stories but also to get some feedback about the platform.
I tried to find some answers for your questions from the FIWARE technical team. And here is what they have replied:
“The question about which PEP to use depends on what other components are you going to use. Steelskin was created to be used in Telefonica's IoT FIWARE-based Platform, that makes use of some of the official FIWARE GEs, but uses Telefonica's own implementation for other components (PEP is an example, and the Access Control GE, Keypass is another). Most of the components of Telefonica's IoT Platform are Open Source and, in theory, fully compatible with other FIWARE software, but you should take into account that none of them have been tested with other FIWARE Ges, so compatibility can't be guaranteed (although, if there are compatibility issues they should be easy to solve and contribute). There is plenty of documentation in the Steelskin PEP Github page about how it works, and you can also find a guide on how to install the proper users and permissions in Openstack Keyston for the PEP proxy to work as it should.
On the other hand, Wilma is the reference implementation for the PEP Proxy GE, and, as such, it is supposed to integrate seamlessly with any other official FIWARE GE, so if you are going to use other official GEs, it would be your best option. Wilma is also the PEP Proxy used in the global instances in FIWARE Lab, so the behavior should be the same in both your local installations and the global ones.
Concerning Openstack Keystone and Keyrock, the later is a fork of the official Keystone repository, adding some functionalities that are not present in the official version. This functionalities are going to be encapsulated in a plugin in the future, so they can be contributed to the official branch or installed as a separate RPM, but this work is still pending today. So, once the plugin has been contributed, they will be basically the same thing.“
Based on their reply, my recommendation would be to use Wilma Pep Proxy and the KeyRock to be more in line with the standard FIWARE platform.
Regarding the installation Object Storage and IDM, in theory you do not need to install these GEs (but of course you can if you really want to).
It may be much easier to use the global instances of these GEs on FIWARE Lab instead.
Hope this helps a bit.
Kind regards,
ilknur
From: Robin Puthli r.puthli@itude.com
Sent: Tuesday, August 11, 2015 3:47 PM
To: Chulani, Ilknur
Subject: Questions regarding FIWARE
Hello Ilknur,
We have been accepted into the FInish accelerate program, which is probably why i received an email regarding FIWARE usage assessment.
Regarding a number of FIWARE components we have a number of questions which the FIWARE GE website and GE sites do not answer for us.
1. We intended to use KeyRock iDM, but with the Object Store GE the installer added Openstack Keystone. Now we are confused what the difference is between Keystone and Keyrock. There does not seem to be much difference between the products. What does Keyrock add over Keystone?
2. We intended to use the Wilma PEP proxy but see there is also an Orion PEP proxy which connects to Openstack Keystone. What reasons are there to choose one over the other if we opt for Keystone?
3. The Object Store GE seems to be identical to Openstack Swift. Are we missing something here?
Best regards,
Robin Puthli
Met vriendelijke groet,
Robin Puthli
Directeur
<image001.png>
Lageweg 2
3703 CA Zeist
■ mob +31(0) 6 21 88 22 86
■ tel direct +31(0)30 692 60 04
■ tel receptie +31(0)30 699 70 20
■ mail r.puthli@itude.com<r.puthli@itude.com>
■ google.com/+RobinPuthli<http://google.com/+RobinPuthli>
■ skype: robin.puthli
■ linkedIn:nl.linkedin.com/in/puthli/<http://nl.linkedin.com/in/puthli/>
www.itude.com<http://www.itude.com/> ■ K.v.K. 30146090
_____________________________________________________________________________
**Op deze mail is een disclaimer van toepassing. De inhoud daarvan is te lezen op onze website**
Bu mesaj ve ekleri gönderilen kişiye özeldir ve gizli bilgiler içerebilir. Eğer mesajın gönderilmek istendiği kişi değilseniz lütfen kopyalamayınız, başkalarına göndermeyiniz ve göndericiyi bilgilendiriniz. Internet üzerinden gönderilen mesajların güvenli ve hatasız olduğunun garantisi olmadığından Atos grubu mesajın içeriğinden sorumlu tutulamaz. Göndericinin bilgisayarı anti-virüs sistemleri tarafından taranmaktadır, ancak yine de mesajın virüs içermediği garanti edilemez ve gönderici, meydana gelebilecek zararlardan sorumlu tutulamaz.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Bu mesaj ve ekleri gönderilen kişiye özeldir ve gizli bilgiler içerebilir. Eğer mesajın gönderilmek istendiği kişi değilseniz lütfen kopyalamayınız, başkalarına göndermeyiniz ve göndericiyi bilgilendiriniz. Internet üzerinden gönderilen mesajların güvenli ve hatasız olduğunun garantisi olmadığından Atos grubu mesajın içeriğinden sorumlu tutulamaz. Göndericinin bilgisayarı anti-virüs sistemleri tarafından taranmaktadır, ancak yine de mesajın virüs içermediği garanti edilemez ve gönderici, meydana gelebilecek zararlardan sorumlu tutulamaz.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
_______________________________________________
Fiware-finish-coaching mailing list
Fiware-finish-coaching@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-finish-coaching