We use proprietary and third party´s cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Ask Your Question

ffacca's profile - activity

2018-10-26 14:26:43 +0200 received badge  Editor (source)
2018-10-26 14:25:22 +0200 answered a question IDAS scalability

I doubt a single instance of an iot agent would scale to receive a million of requests per second or even minute. scalability it is not just about the software but the way you deploy it and the resources you dedicate to it. some ideas on how to deploy an ha instance of an iot agent are here: https://smartsdk-recipes.readthedocs....

2018-10-26 14:21:53 +0200 answered a question Can multiple fiware orion work with same mongodb backend?

see reply to: https://ask.fiware.org/question/1039/... let's avoid duplicating questions

2018-10-26 12:17:08 +0200 answered a question Multiple orion with single mongodb instance fails to process subscriptions

hi, can you better describe the scenario you are trying to achieve?

if what you are looking for is HA deployment (more replicas of the same orion service), then it should work easily. you find a guide here: https://github.com/telefonicaid/fiwar...

in the ha case, it is the expected behaviour that only one notification will be triggered, because once triggered the db is updated with such information.

if your purpose is to have different separate services (different data in the different orions) you need to be careful to configure different db for them.

2017-08-21 13:19:24 +0200 received badge  Notable Question (source)
2017-08-21 13:19:24 +0200 received badge  Famous Question (source)
2017-05-15 10:28:06 +0200 answered a question Is it possible to build FIWARE on my own OpenStack cluster?

You can install FIWARE services on your openstack, or any other hosting for what matters :) I recommend to start playing using dockerized services. You can see an example application here.

Details on how to use Docker on FIWARE are available here.

2017-03-02 09:46:35 +0200 received badge  Popular Question (source)
2017-02-16 15:10:26 +0200 asked a question Is there any information on how to deploy Kurento in HA for scalable deployments?

Suppose you have to support many streaming: one server will not be enough. Beyond that, to provide a service resilient to failure you would need multiple instances of the service. Before spending time in experiments on the scalability and how to achieve it, I would like to know if there is available any guideline. Is it enough to have multiple instances behind a load balancer? Somehow I doubt it, because even if you may be using pipelines that are stateless, the problem is that Kurento relies on the concept of session. Supposing than the kurento instance to which I am connected fails, and the load balancer redirect me to another instance, will it work? Or given that the session is not shared the user will experience a failure? Is there any way to share sessions among multiple instances?

2015-09-16 07:17:17 +0200 answered a question Please give us instruction how to restore expired fiware lab account so that the user connects to a company community account again?

dear tania, one community account is enough to allow your team to work, infact you can add as collaborator to your community account other basic accounts.

I would follow the following steps:

  1. ensure people that need to have access to your cloud resources have a fiware lab account (basic - that is not limited in number of users - is perfect). if for any reason the account was deleted they can re-register.
  2. log-in using your community account at https://account.lab.fiware.org
  3. click on "organizations"
  4. select the cloud organization of your community account (usually something like "account-name cloud"
  5. in the member panel click on "Manage"
  6. in the "All Users" panel search the name of your collaborators and add them to the members.

this should be enough to allow your team to access your cloud deployments!