Policy Manager GEi of the FIWARE project, server to process facts from Orion Context Broker.
1.4K
There are several options to use fiware-facts very easily using docker. These are (in order of complexity):
You do not need to do all of them, just use the first one if you want to have a fully operational fiware-facts instance and maybe third one to check if your fiware-facts instance run properly.
You do need to have docker in your machine. See the documentation on how to do this. Additionally, you can use the proper FIWARE Lab docker functionality to deploy dockers image there. See the documentation
Docker allows you to deploy an fiware-facts container in a few minutes. This method requires that you have installed docker or can deploy container into the FIWARE Lab (see previous details about it).
Consider this method if you want to try fiware-facts and do not want to bother about losing data.
Follow these steps:
git clone https://github.com/telefonicaid/fiware-facts.git)cd fiware-facts/dockerdocker build -t fiware-facts -f Dockerfile ..After a few seconds you should have your fiware-facts image created. Just run the command docker images and you see the following response:
REPOSITORY TAG IMAGE ID CREATED SIZE
fiware-facts latest bd78d006c2ea About a minute ago 480.8 MB
...
fiware-facts image needs some dockers containers: mysql and rabbit already deployed. Thus, to deploy the container we need to execute the command docker run -p 8000:8000 -l rabbit -l mysql fiware-facts.
It will launch the fiware-facts service listening on port 8000, which is linked to mysql and rabbit dockers.
To check that the service is running correcly, just do
curl <IP address of a machine>:8000
You can obtain the IP address of the machine just executing docker-machine ip. What you have done with this method is the creation of the fiware-facts
image from the public repository of images called Docker Hub.
If you want to stop the scenario you have to execute docker ps and you see something like this:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b8e1de41deb5 fiware-facts "/bin/sh -c ./start.s" 6 minutes ago Up 6 minutes 0.0.0.0:8000->8000/tcp fervent_davinci
...
Take the Container ID and execute docker stop b8e1de41deb5 or docker kill b8e1de41deb5. Note that you will lose any data that was being used in fiware-facts using this method.
However, there is a simpler way to deploy the container. That is docker-compose and it avoids to deploy containers previously and specifies the port for fiware-facts. It involves just executing docker-compose up -d to launch the architecture, after exporting a set of environment variables.
export KEYSTONE_IP=<IP of the keystone instance for the Openstack environment previously deployed>
export ADM_TENANT_ID=<Tenant Id for the admin user in the OpenStack environment previously deployed>
export ADM_TENANT_NAME=<Tenant name for the admin user in the OpenStack environment previously deployed>
export ADM_USERNAME=<Username for the admin user in the OpenStack environment previously deployed>
export ADM_PASSWORD=<Password for the admin user in the OpenStack environment previously deployed>
export OS_USER_DOMAIN_NAME=<OpenStack user domain name for the Openstack environment previously deployed>
export OS_PROJECT_DOMAIN_NAME=<OpenStack project domain name for the Openstack environment previously deployed>
If you want to check the containers just execute docker-compose ps.
Name Command State Ports
----------------------------------------------------------------------------------------------------------------------------------------------------------------
docker_fiwarefacts_1 /bin/sh -c ./start.sh Up 0.0.0.0:8000->8000/tcp
mysql docker-entrypoint.sh mysqld Up 0.0.0.0:3306->3306/tcp
rabbit /docker-entrypoint.sh rabb ... Up 0.0.0.0:25672->25672/tcp, 0.0.0.0:4369->4369/tcp, 0.0.0.0:5671->5671/tcp, 0.0.0.0:5672->5672/tc
You can take a look to the log generated executing docker-compose logs.
Taking into account that you download the repository from GitHub (See Section 1. The Fastest Way), this method will launch a container running fiware-facts, and execute the unit tests associated to the component. You should move to the UnitTests folder ./UnitTests. Just create a new docker image executind docker build -t fiware-facts-unittests -f Dockerfile .. Please keep in mind that if you do not change the name of the image it will automatically create a new one for unit tests and change the previous one to tag none.
To see that the image is created run docker images and you see something like this:
REPOSITORY TAG IMAGE ID CREATED SIZE
fiware-facts-unittests latest 103464a8ede0 30 seconds ago 551.3 MB
...
To execute the unit tests of this component, just execute docker run --name fiware-facts-unittests fiware-facts-unittests. Finally you can extract the information of the executed tests
just executing docker cp fiware-facts-unittests:/opt/fiware-facts/report .
TIP: If you are trying these methods or run them more than once and come across an error saying that the container already exists you can delete it with
docker rm fiware-facts-unittests. If you have to stop it first dodocker stop fiware-facts-unittests.
Keep in mind that if you use these commands you get access to the tags and specific versions of fiware-facts. If you do not specify a version you are pulling from latest by default.
Taking into account that you download the repository from GitHub (See Section 1. The Fastest Way). This method will launch a container to run the E2E tests of the fiware-facts component, previously you should launch or configure a FIWARE Lab access. You have to define the following environment variables:
export KEYSTONE_IP=<IP of the keystone instance for the Openstack environment previously deployed>
export ADM_TENANT_ID=<Tenant Id for the admin user in the OpenStack environment previously deployed>
export ADM_TENANT_NAME=<Tenant name for the admin user in the OpenStack environment previously deployed>
export ADM_USERNAME=<Username for the admin user in the OpenStack environment previously deployed>
export ADM_PASSWORD=<Password for the admin user in the OpenStack environment previously deployed>
export OS_USER_DOMAIN_NAME=<OpenStack user domain name for the Openstack environment previously deployed>
export OS_PROJECT_DOMAIN_NAME=<OpenStack project domain name for the Openstack environment previously deployed>
Take it, You should move to the AcceptanceTests folder ./AcceptanceTests. Just create a new docker image executing docker build -t fiware-facts-acceptance .. To see that the image is created run docker images and you see something like this:
REPOSITORY TAG IMAGE ID CREATED SIZE
fiware-facts-acceptance latest eadbe0b2e186 About an hour ago 579.3 MB
fiware-facts latest a46ffad45e60 4 hours ago 480.8 MB
...
Now is time to execute the container. This time, we take advantage of the docker compose. Just execute docker-compose up
to launch the architecture. You can take a look to the log generated executing docker-compose logs. If you want to get
the result of the acceptance tests, just execute docker cp acceptancetests_fiwarefacts1:/opt/fiware-facts/tests/acceptance/testreport .
Please keep in mind that if you do not change the name of the image it will automatically create a new one for unit tests and change the previous one to tag none.
TIP: you can launch a FIWARE Lab testbed container to execute the fiware-facts E2E test. Just follow the indications in FIWARE Testbed Deploy. It will launch a virtual machine in which a reproduction of the FIWARE Lab is installed. Keep in mind that in that case Region1 have to be configured with the value qaregion.
Things to keep in mind while working with docker containers and fiware-facts.
Everything you do with fiware-facts when dockerized is non-persistent. You will lose all your data if you turn off the fiware-facts container. This will happen with either method presented in this README.
sudoIf you do not want to have to use sudo follow these instructions.
There are several options to use fiware-facts very easily using docker. These are (in order of complexity):
You do not need to do all of them, just use the first one if you want to have a fully operational fiware-facts instance and maybe third one to check if your fiware-facts instance run properly.
You do need to have docker in your machine. See the documentation on how to do this. Additionally, you can use the proper FIWARE Lab docker functionality to deploy dockers image there. See the documentation
Content type
Image
Digest
Size
239.1 MB
Last updated
almost 10 years ago
docker pull fiware/bosun-facts