I wonder if there is any way to download a public image (e.g. orion-psb-image-R4.1) from Fiware Lab to install on a local VM?
How is the procedure performed?
Thank you very much in advance.
Please see the following link.
Locally run a FIWARE Lab Instance In another Hypervisors
(José Ignacio Carretero Guarde, FIWARE Cloud and Platform Expert)
Related
I would like to check the common vulnerabilities in some of FIWARE components that we are using in our platform, components list is given below.
Cepheus
Cygnus
Orion
STH-Comet
QuantumLeap
IoT Agent for JSON
IoT Agent Node Lib
If any source is available over some FIWARE website or some other source, where we can verify the vulnerabilities in FIWARE component. Please provide the information if such information is available.
For a given Docker baseline we are using Anchore and Clair checks. For a given usual running Docker Container based on a Docker Compose file a Docker Benchmark Security recommendation is executed. Additionally, we are running SAST code analysis over the corresponding repositories. Plus npm audit for the node.js ones plus.
We are defining corresponding GitHub Actions to use inside the repositories.
There is a working project to provide security analysis of the components, the first version is not released yet. You can take a look on it in this repository FIWARE Security Scan
I am new to Azure API Manager, I have used Apigee Edge before where you can store each api proxy code in either git or SVN. But in Azure I am not sure how each API that is exposed via the gateway is stored. I can see there is a repository for the whole API Manager instance. Does that mean all the APIs are bundled to the same Gateway Instance and stored there?
I am planning to build a CI/CD pipeline to create the APIs in the API Manager for that I need to understand how the APIs code will be stored.
Your help is appreciated. Thanks.
Besides the GIT repository for the apimanagement instance, you can fetch it in form of ARM templates. Refer this blog.
https://azure.microsoft.com/en-in/blog/build-a-ci-cd-pipeline-for-api-management/
I'm planning to use Promethus in ECS Cluster for monitoring but seems that Promethus does not support ECS service discovery in native, unlike EC2.
I'm searching but not enough information. I would really appreciate if any share any information. Thanks in advance.
I'm quite not sure, if i understood the problem correctly.
You can create private hosted zone in Route 53 and configure it to a particular VPC with DNSresolution and DNS Hostname enabled.
with this, you can create an ECS instances with the above set VPC, create a service with task having a name say promotheus.local or your application (app.local) to which you want to monitor from promotheus, with this kind of set up, you can use http://app.local:port to extract monitoring information by name instead of private IP.
Ref: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-considerations.html
Hope this helps.
Thanks,
Sridhar
I've correctly installed a Wirecloud instance in my own server. I've added a Marketplace available at this address http://130.206.81.113/FiwareMarketplace/v1.
I can retrieve the data from Marketplace correctly, and I can see all available widgets but I can't install anyone of them.
The only button present on each widget is Details, but I need Install to use them in my workspace.
Can I solve this issue in any way?
Thanks in advance.
Currently, WireCloud only allows you to install components from a marketplace/store if you are using the same IdM server in all the services: the marketplace, the store and WireCloud. As you want to use the global instance of the Marketplace, you should use the FIWARE Lab's KeyRock instance (https://account.lab.fiware.org) for authenticating users in your WireCloud instance to be able to install components from the FIWARE Lab's Marketplace.
NOTE: The Marketplace GE and the Store GE are currently in support mode. The Business API Ecosystem GE is going to replace it, but it won't be released until summer 2016.
I would like to know what is the common deployment pattern for IDAS and Orion in a production environment. Are they usually deployed as docker images or as a native service? If they are as a docker images then do they usually go together in one container or separate containers?
Thank you.
I can provide an answer from the point of view of Orion Context Broker (I hope that some of my colleagues from IDAS team can answer also that part).
Deployment options (look for slides "How to get Orion" in this presentation) are the following ones:
Image in FIWARE Lab cloud
Docker contaniner
VirtualBox image
RPM installation (from FIWARE repositories)
Compiling from sources
For IDAS it depends on the specific IoT-Agent you are using.
If you are using Ultralight2.0/HTTP or MQTT to connect devices, all the information for installation is available here:
https://github.com/telefonicaid/fiware-IoTAgent-Cplusplus/blob/release/1.3.0/README.md
On the other hand, if you will use OMA LWM2M/CoAP to connect devcies, this info is here:
https://github.com/telefonicaid/lightweightm2m-iotagent/blob/master/docs/administrationGuide.md
Also, docker files are available here:
http://catalogue.fiware.org/enablers/backend-device-management-idas/creating-instances
Hope this helps.
Cheers,