Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
Sender Email:
-
External Participants:
-
HD-Chapter:Cloud
-
HD-Enabler:Object Storage
Description
Comment by toffoli@linkroma.it :
Dear Sandor,
during the past months we had performed simple tests on the Object
Storage by creating containers and uploading objects from the web
interface of the FI-Lab portal.
In order to test some application functions using the Object Storage
API, we started with the execution of the sample code in the Object
Storage wiki
(https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Object_Storage_-_User_and_Programmers_Guide#Programmer_Guide_-_Accessing_Object_Storage_via_the_native_API).
But we met a few problems, due to our lack of experience and possibly to
uncomplete documentation.
1. Some swift endpoints listed as available don't respond
We repeatedly executed the sample code without success. Then, since it
seems that there are some 10 swift endpoints in the list, while the
sample code in the wiki always picks always the same endpoint
(http://api3.ficore.imaginlab.fr:8080/v1 in our case), we iterated on
the list until we found one service provider working
(http://api2.xifi.imaginlab.fr:8080/v1).
2. Cannot find complete documentation on the OS service provided by the
FI-Lab
By executing the modified sample code, eventually we are able to create
a test container and to put a test object inside it.
At the start we were confused: not finding specific information on the
endpoints of the swift service, we tried to use the first one that
allowed us to execute the test procedure (modified sample code) with
success.
We thought that the different endpoints were working as a federation
managing a shared namespace. Only by trying we became aware that we
should pick from the list the Budapest2 endpoint in order to get a
synchronized view of our containers from both the Fi-lab dashboard and
the API interface.
By the way: we noticed that, adding an object to a container through the
REST API, the count of objects in the web view is refreshed with
considerable delay, possibly due to some caching.
Could you tell us where we could find some more documentation, besides
the general one concerning the Object Storage specifications and the
Object Storage API?
Thank you in advance.
Best regards, Giovanni
–
Giovanni Toffoli, CEO
LINK srl - Via Udine 30, 00161 Roma
+39 06 44231115, +39 340 0727780
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-fiadopt-coaching@lists.fiware.org) instead of the old one.
Issue Links
Activity
The escalation level is not going directly to the general coordination. In fact, this case should be managed by the cloud coordination, in IBM. In any case, I replied in private giving the procedure to use the forge and the wiki. This is now awaiting the feedback from Eran to see if it is resolved.
I have access to edit the wiki. I am now working with Kalman and Kenneth to succeed in actually accessing the object store using the ficore auth endpoint. It currently appears that my user does not have any services defined:
curl -d '{"auth": {"passwordCredentials":
{"username":"eranr@il.ibm.com", "password":"********"}}}' -H 'Content-type: application/json' http://cloud.lab.fiware.org:4730/v2.0/tokens -vvv
{"access": {"token":
{"issued_at": "2016-05-02T13:56:26.133340", "expires": "2016-05-03T13:56:26Z", "id": "6c59777d23d14ce59f98b25c2860e1d6", "audit_ids": ["c4EO1qqpQG-RN0PetZExlQ"]}, "serviceCatalog": [], "user":
{"username": "eranr@il.ibm.com", "roles_links": [], "id": "eranr", "roles": [], "name": "eranr@il.ibm.com"}, "metadata":
{"is_admin": 0, "roles": []}}}
Apologies for the long time this took (mainly due to passover vacation, but not only...).
I have updated the documentation here:
https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Object_Storage_-_User_and_Programmers_Guide#3._Authenticate_tenant_to_get_token_for_Object_Storage
the changes include:
1. specifying the the way of Accessing Object Storage via the Cloud Portal is obsolete.
2. Added an example for retrieving the token using tenant name (and how to retrieve it)
3. Added an explanation on the token structure and the fact that not all regions are operational.
Hope this helps!
Eran
I have updated the documentation here:
https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Object_Storage_-_User_and_Programmers_Guide#3._Authenticate_tenant_to_get_token_for_Object_Storage
the changes include:
1. specifying the the way of Accessing Object Storage via the Cloud Portal is obsolete.
2. Added an example for retrieving the token using tenant name (and how to retrieve it)
3. Added an explanation on the token structure and the fact that not all regions are operational.
Dear Fiware Lab team,
The inquiry has been handled in https://jira.fiware.org/browse/HELC-1213 by the Budapets team. But this ticket is just to raise awareness about the feedback that an SME gave us about the difficulty of finding the SWIFT endpoints on each node:
"Thank you Sandor, thank you Ilknur,
in fact, by issuing the equivalent request inside our Python test
procedure, we got a big Json data structure including, for each type of
service, the list of the endpoints that we should be able to access.
With my email, I wished mainly to give a feedback, useful for other
people and for improving the documentation, on the difficulty that we
met at finding and interpreting that information.
Best regards"
so perhaps we have to provide better documentation somewhere to let SMEs find this information more easily.