Dear Leonid,
Have you set the security groups correctly? By default all the TCP and
UDP ports are closed, so you have to add the proper ports to the
security group used by your instance.
Basically, you can deploy a Kurento instance in two ways: 1. by using
blueprint templates (adding kurento to the tier is enough), 2. by
launching the pre-prepared kurento image available in all the regions.
The 2. option is faster and should work in most of the regions, with
blueprint templates we have experienced some issues that are currently
under investigation.
The Spain region is overloaded and they have run out of public IP
addresses. This will be solved soon, but currently you should try
another region. If you experience some problems e.g. you cannot ssh to
the VM or kurento is not available, or provides bad performance, please
send the issue with the name of the used REGION to this mailing list, so
that the operators of the region could solve the problem.
My answers to your further questions:
1. Do I understood right, that all additional software (kurent, MySQL,
apache etc.) I have to install through Blueprint Instance creation
interface. Or It is possible to install just Ubuntu for example and then
all services I need?
In blueprint templates you can put together a software stack you need
for your app. If you choose kurento, all the dependencies will be
installed automatically. An empty blueprint contains the base OS
basically. After deployment, you cannot modify the instance. (you can of
course remove it and redeploy the modified blueprint...)
2. Keypairs are the only way to connect to the server?
Basically, yes, they are. However, after loging in to the server, you
will have root access, so you can reconfigure the os as you need.
Important, that each region manages the keypairs separately... To access
the vm via ssh, you should add port 22 to the security group assigned to
your vm.
3. Is it possible to get future technical support from FIWARE-Lab?
Yes, you can write to this mailing list or to directly the GE owners
available in the FIWARE catalogue.
Please let me know if the problem is still there and you cannot access
your instance in Spain2 and Stockholm.
Best,
Sandor
– on behalf of level-1 support team of FIWARE Lab
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
extRequest
Dear Leonid,
Have you set the security groups correctly? By default all the TCP and
UDP ports are closed, so you have to add the proper ports to the
security group used by your instance.
Basically, you can deploy a Kurento instance in two ways: 1. by using
blueprint templates (adding kurento to the tier is enough), 2. by
launching the pre-prepared kurento image available in all the regions.
The 2. option is faster and should work in most of the regions, with
blueprint templates we have experienced some issues that are currently
under investigation.
The Spain region is overloaded and they have run out of public IP
addresses. This will be solved soon, but currently you should try
another region. If you experience some problems e.g. you cannot ssh to
the VM or kurento is not available, or provides bad performance, please
send the issue with the name of the used REGION to this mailing list, so
that the operators of the region could solve the problem.
My answers to your further questions:
1. Do I understood right, that all additional software (kurent, MySQL,
apache etc.) I have to install through Blueprint Instance creation
interface. Or It is possible to install just Ubuntu for example and then
all services I need?
In blueprint templates you can put together a software stack you need
for your app. If you choose kurento, all the dependencies will be
installed automatically. An empty blueprint contains the base OS
basically. After deployment, you cannot modify the instance. (you can of
course remove it and redeploy the modified blueprint...)
2. Keypairs are the only way to connect to the server?
Basically, yes, they are. However, after loging in to the server, you
will have root access, so you can reconfigure the os as you need.
Important, that each region manages the keypairs separately... To access
the vm via ssh, you should add port 22 to the security group assigned to
your vm.
3. Is it possible to get future technical support from FIWARE-Lab?
Yes, you can write to this mailing list or to directly the GE owners
available in the FIWARE catalogue.
Please let me know if the problem is still there and you cannot access
your instance in Spain2 and Stockholm.
Best,
Sandor
– on behalf of level-1 support team of FIWARE Lab
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help