sonata-nfv / son-install Goto Github PK

We have configured the following url:

--gkApiUrl=http://{{ public_ip }}:32001

Should be:

--gkApiUrl=https://{{ public_ip }}/api/v2

We need to change the way to link the containers.

1. Create the network sonata in the VM
2. Start the containers in the network sonata
3. Create the network alias to the container in order to insert the record in the local network DNS.

son-gtkpkg have a volume created to write the logs but is not configured in the right folder

    volumes:
      - /var/log/sonata:/var/log/son-gtkpkg

[WARNING]: While constructing a mapping from /var/lib/jenkins/jobs/son-
install/workspace/destroy/ntp.yml, line 18, column 5, found a duplicate dict
key (when). Using last defined value only.
[WARNING]: While constructing a mapping from /var/lib/jenkins/jobs/son-
install/workspace/destroy/ntp.yml, line 24, column 5, found a duplicate dict
key (when). Using last defined value only.

Is configured dbPath: "/var/lib/mongo",

Should be dbPath: "/var/lib/mongodb",

This is the configuration:
GK_URL: "{{ public_ip }}:32001"

Should be like this:
GK_URL: "{{ public_ip }}:32001/api/v2"

We need to publish the port 25002:1338

We got the following error:

D, [2017-04-16 21:45:08#14] DEBUG -- : PG::UndefinedTable: ERROR: relation "requests" does not exist
LINE 5: WHERE a.attrelid = '"requests"'::regclass
^
: SELECT a.attname, format_type(a.atttypid, a.atttypmod),
pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod
FROM pg_attribute a LEFT JOIN pg_attrdef d
ON a.attrelid = d.adrelid AND a.attnum = d.adnum
WHERE a.attrelid = '"requests"'::regclass
AND a.attnum > 0 AND NOT a.attisdropped
ORDER BY a.attnum

Solution:
bundle exec rake db:migrate that has to be run

Allow to generate a ramdom password for postgres database and insert as variable.

son-postgres have a volume created to write the logs but is not configured in the right folder

    volumes:
      - /var/log/sonata:/var/log/son-postgres

Hi,
When I installed the sonata platform (v 3,0) (previously i had edited the Sonata SP user in roles/sp/defaults/main.yml). Initially, I could login and exit normally, but after installing the son-cli and son-emu in the PC. I couldn't login again to SONATA SP.

What can I do?

Best regards

We have this configuration:

CATALOGUES_URL: http://{{ public_ip }}:4002/catalogues

We need to change it for this:

CATALOGUES_URL: http://{{ public_ip }}:4002/catalogues/api/v2

The GUI have a volume created to write the logs but is not configured in the right folder

    volumes:
      - /var/log/sonata:/var/log/son-gui

Received Access forbidden message while deploying network service OpenStack.
Though I could able to establish the connection between Sonata and OpenStack.
Attaching some log of son-sp-infrabstract.

I just tried to install our SP on a fresh Ubuntu 16.04 server and noticed two small glitches where the installation aborts:

• Folder /etc/ansible/group_vars missing
  • Workaround: sudo mkdir /etc/ansible/group_vars
• Group docker missing
  • Workaround: sudo groupadd docker

I used the installation description provided on our webpage: http://sonata-nfv.eu/content/installation

Add the following parameters to the command to start the docker container:

--userManagementEnabled=false --licenseManagementEnabled=false

The port 80 of container son-gui seems not be exposed

Catalogues and Repositories have a volume created to write the logs but is not configured in the right folder

    volumes:
      - /var/log/sonata:/var/log/son-catalogue-repos

Error message:
TASK [GATEKEEPER API - running Docker containers] ******************************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Error starting container e767c39d03498f3defb61d1ee311a862bff71cbfbbf29562e0f8986775747f5a: 500 Server Error: Internal Server Error ("Cannot link to a non running container: /son-gtksrv AS /son-gtkapi/son-gtksrv")"}

NO MORE HOSTS LEFT *************************************************************
[WARNING]: Could not create retry file 'son-cmud.retry'. [Errno 2] No
such file or directory: ''

PLAY RECAP *********************************************************************
localhost : ok=47 changed=15 unreachable=0 failed=1

Hi,

I am trying to instlal on a fresh Ubuntu 16.04, the following steps:
https://sonata-nfv.github.io/component_installation.

The process to install SP is the same as for version 3.0 ?
If yes, I installed first the packages mentioned at the beginning:

Create tango user

sudo adduser tango
sudo usermod -a -G sudo tango

Packages installation

sudo apt-get install -y software-properties-common
sudo apt-add-repository -y ppa:ansible/ansible
sudo apt-get update
sudo apt-get install -y ansible
sudo apt-get install -y git
sudo apt-get install python3
sudo apt install python3-pip
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3 10
sudo pip3 install docker

Docker-ce

sudo apt-get update
sudo apt-get install
apt-transport-https
ca-certificates
curl
software-properties-common
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo apt-key fingerprint 0EBFCD88
sudo add-apt-repository
"deb [arch=amd64] https://download.docker.com/linux/ubuntu
$(lsb_release -cs)
stable"
sudo apt-get update
sudo apt-get install docker-ce

Create docker network

sudo docker network create tango

Repository cloning

git clone https://github.com/sonata-nfv/tng-devops.git
cd tng-devops

After that, I encounter the following error:

root@sonata-tango:/home/sonata/son-install# ansible-playbook utils/deploy/sp.yml -e "target=localhost public_ip=10.0.2.15"
Traceback (most recent call last):
File "/usr/bin/ansible-playbook", line 40, in
from ansible.errors import AnsibleError, AnsibleOptionsError, AnsibleParserError
ImportError: No module named 'ansible'

Could you pleas help ?
Thanks !

son-bss have a volume created to write the logs but is not configured in the right folder

    volumes:
      - /var/log/sonata:/var/log/son-bss

This url should be configured in case you have a graylog system conected to SONATA.

The IP address should be different to public_ip. Something like graylog_ip if this exists.

Here the list of new services:

• son-validate
• son-gtkrtl
• son-gtklic
• son-redis
• functionlifecyclemanagement

Aditional Tasks:

• Check the configuration of all SP components.

Path prefix lookup('env', 'PWD') == '', thus ansible tries to find files from root instead of repository directory.

roles/docker/tasks/main.yaml, line 10
roles/sp/tasks/main.yaml, line 10, 12, 57

Currently this is the status:

IMAGE PORTS
sonatanfv/servicelifecyclemanagement
sonatanfv/pluginmanager
sonatanfv/son-gtkapi 5000/tcp
sonatanfv/son-gtksrv 5300/tcp
sonatanfv/son-yo-gen-bss 1337-1338/tcp, 9000/tcp
sonatanfv/son-monitor-manager 9000/tcp, 9090/tcp, 0.0.0.0:32775->8000/tcp
sonatanfv/son-monitor-prometheus 0.0.0.0:32774->9089/tcp, 0.0.0.0:32773->9090/tcp
sonatanfv/son-monitor-pushgateway 0.0.0.0:32772->9091/tcp
sonatanfv/son-monitor-mysql 0.0.0.0:32771->3306/tcp
sonatanfv/son-monitor-influxdb 8083/tcp, 0.0.0.0:32770->8086/tcp
sonatanfv/son-sp-infrabstract
sonatanfv/son-catalogue-repos 0.0.0.0:32769->4002/tcp
sonatanfv/son-gtkpkg 0.0.0.0:32768->5100/tcp
sonatanfv/son-gui
rabbitmq 4369/tcp, 5671/tcp, 25672/tcp, 0.0.0.0:5672->5672/tcp

Hi Sonatas,

I'm trying to setup a working sonata platform with these install script and as I understand there is a "secret" public_ip variable that one should change to the public IP of the host. It would be great if you can include this in the README.md.

Some info:
Master branch, commit a97ad93
Files:
install/group_vars/all, install/roles/docker/files/group_vars.all
Ansible command:
ansible-playbook son-cmud.yml -e "target=localhost env=demo operation=install service=all"

Regards,
Janos

2016-07-27T14:24:17.606+0200 I CONTROL [main] ERROR: Cannot write pid file to /var/run/mongodb/mongod.pid: No such file or directory

The catalogues can't reach to mongodb

We have this configuration:

CATALOGUES_URL: http://{{ public_ip }}:4002/catalogues

We need to change it for this:

CATALOGUES_URL: http://{{ public_ip }}:4002/catalogues/api/v2

Good day!
Would you like to help us..
We installed full sonata-package (// INSTALL full SP) and have got access to the web interface(dashboard). But when we сhanged some settings in sonata dashboard and tried to to apply this settings, we pushed "Save" button, but changes weren't applied.
We tried several times - the same result.We used Github-login and password.
May be ..the problem is that all dependences weren't established? And how to learn the list of all dependences (the version of packages)?
Thanks a lot
Best regards,
Alex

We have this configuration:

CATALOGUES_URL: http://{{ public_ip }}:4002/catalogues

We need to change it for this:

CATALOGUES_URL: http://{{ public_ip }}:4002/catalogues/api/v2

Here are the list of files:
./deploy-terraform.yml
./deploy-pgsql.yml
./deploy-jenkins.yml
./destroy-pgsql.yml

[DEPRECATION WARNING]: Instead of sudo/sudo_user, use become/become_user and
make sure become_method is 'sudo' (default).
This feature will be removed in a
future release. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.

To support https in the bss module we should add this options in the command to start the container:

--hostname=<dns_name>
--protocol=https

For the dns_url we should create a global variable with this entry.

Also we need to create the following volume:

/etc/ssl/private/sonata/:/usr/local/yeoman/SonataBSS/app/certs/

And verify if the certs for SONATA are available in the folder /etc/ssl/private/sonata/

Mongo have a volume created to write the logs but is not configured in the right folder

    volumes:
      - /var/log/sonata:/var/log/mongo

We have the following link:
´´´
etc_hosts:
mongo: "{{ ansible_default_ipv4.address }}"
´´´

Try to reconfigure the son-catalogue repos to not use mongo IP like this.

It is mounting this volume but the application is not writting the logs there.

    volumes:
      - /var/log/sonata/son-broker:/var/log/son-broker

The restart policy for the son-postgres container is missing forcing you to start the container manually after a system reboot.

son-gtksrv have a volume created to write the logs but is not configured in the right folder

    volumes:
      - /home/{{ vm_user }}/son-gkeeper/son-gtksrv/:/opt/sonata/son-gktsrv
      - /var/log/sonata:/var/log/son-gtksrv

Also/home/{{ vm_user }}/son-gkeeper/son-gtksrv/:/opt/sonata/son-gktsrv is not needed

We need to add in the deployment SP script, a new playbook that start the son-keycloak just after databases deployment

hiya

I have a very general question, I hope this is an OK place to ask

we're looking for a solution that would allow to orchestrate several k8s-based clusters; there is no VM-based cluster in the landscape, and so I was curious to know if it's possible to use sonata in such a use case - given that the docs that I have seen suggest otherwise (that openstack is mandatory)

I am referring specifically to this quote that I found in https://sonata-nfv.github.io/quickguide

Setup
To setup SONATA you must install the three major components of SONATA and OpenStack in the order shown is the following bulleted list and as highlighted in the following diagram.

thanks in advance for your insights

Shared catalogue between a hierarchy of SPs should be configurated during the installation.

We should use the following command:

docker run -i --net=sonata -e DATABASE_HOST={{ public_ip }} -e MQSERVER=amqp://guest:guest@{{ public_ip }}:5672 -e RACK_ENV=integration -e CATALOGUES_URL=http://{{ public_ip }}:4002/catalogues/api/v2  -e DATABASE_PORT=5432 -e POSTGRES_PASSWORD=sonata -e POSTGRES_USER=sonatatest --rm=true  sonatanfv/son-gtksrv bundle exec rake db:migrate