Hi Shaheen, I just update the wiki page https://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack . Please see below:
Neutron may require that the dns_nameservers property of a OS::Neutron::Subnet resource be explicitly set, in order to allow VMs in the subnet to access the external network. dns_nameservers is a list of DNS IP addresses. However, some OpenStack installations do not support lists is the "user_data" section of a Heat template, which is used to build configuration files that are used during ONAP installation. As such, we define two different parameters: 1) dns_list is a list of DNS IP addresses that is provided to Neutron; 2) external_dns is a string that contains one of the DNS IP addresses in the list and can be used in the "user_data" section. In many cases, when only one DNS address is provided, these two parameters will be set to the same value. We try to be as generic as possible and accommodate possibly different OpenStack versions and deployments. The DNS list is used by Neutron, while the String is used by Heat. Thanks, Marco From: "Ali, Shaheen" <[email protected]> Date: Friday, May 12, 2017 at 11:44 AM To: "PLATANIA, MARCO (MARCO)" <[email protected]>, "ROSE, DANIEL V" <[email protected]>, "[email protected]" <[email protected]> Subject: RE: [onap-discuss] (no subject) So how is dns_list even used? Shaheen ________________________________ From: PLATANIA, MARCO (MARCO) [[email protected]] Sent: Friday, May 12, 2017 11:31 AM To: Ali, Shaheen; ROSE, DANIEL V; [email protected] Subject: Re: [onap-discuss] (no subject) Shaheen, I found that DNS issue too. In some OpenStack deployments, the heat engine complains and doesn’t even start. To get around it, I introduced another parameter in heat env, which is a simple string and is interpreted correctly by heat and docker engines. So, the heat template now has: dns_list: LIST OF DNS SERVERS external_dns: ONE OF THE DNS IP ADDRESSES IN THE PREVIOUS LIST In this way, both engines are happy. I will investigate later if there’s some different approach. Thanks, Marco From: "Ali, Shaheen" <[email protected]> Date: Friday, May 12, 2017 at 11:23 AM To: "PLATANIA, MARCO (MARCO)" <[email protected]>, "ROSE, DANIEL V" <[email protected]>, "[email protected]" <[email protected]> Subject: RE: [onap-discuss] (no subject) I found the problem. The docker opts for DNS were set thus: DOCKER_OPTS="--dns [123.123.123.1] --mtu=1450" The problem is the brackets. Turns out that the external_dns: element in onap_openstack.env file is a list and was thus passing in a python list. In my specific case, I hacked the heat template external_dns value with sed before saving it to /opt/config/external_dns.txt echo "__external_dns__" | sed 's/\(.*\)\[\(.*\)\]\(.*\)/\1\2\3/g' > /opt/config/external_dns.txt This is a hack but it got my servers up and working better. My next problem is that the portal tomcat is not able to communicate with the mysql container even though mysql is up and running. Restarting the containers and rebooting the portal VM do not help. Shaheen ________________________________ From: PLATANIA, MARCO (MARCO) [[email protected]] Sent: Friday, May 12, 2017 11:02 AM To: ROSE, DANIEL V; Ali, Shaheen; [email protected] Subject: Re: [onap-discuss] (no subject) Install scripts run as root, unless they are run manually, in which case you either grant root access or use sudo. Based on the message below, it seems to me that the docker engine didn’t install correctly. Shaheen, could you please verify if docker is actually installed? Try to run “sudo docker ps”. If that error message still appears, it means that the docker engine didn’t install correctly. Thanks, Marco From: <[email protected]> on behalf of "ROSE, DANIEL V" <[email protected]> Date: Friday, May 12, 2017 at 10:49 AM To: "Ali, Shaheen" <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [onap-discuss] (no subject) ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Marco seems to be a sudo issue? Are we running as root? Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: [email protected] [mailto:[email protected]] On Behalf Of Ali, Shaheen Sent: Thursday, May 11, 2017 6:33 PM To: [email protected] Cc: Ali, Shaheen <[email protected]> Subject: [onap-discuss] (no subject) I just started the latest ONAP heat template and all the servers that depend on docker failed on the same line in their install.sh: Setting up docker-engine (17.05.0~ce-0~ubuntu-trusty) ... docker start/running, process 25003 Setting up cgroup-lite (1.9) ... cgroup-lite start/running Processing triggers for libc-bin (2.19-0ubuntu6.11) ... Processing triggers for ureadahead (0.100.0-16) ... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 600 0 600 0 0 5839 0 --:--:-- --:--:-- --:--:-- 5882 100 7857k 100 7857k 0 0 3071k 0 0:00:02 0:00:02 --:--:-- 3722k docker stop/waiting start: Job failed to start Cloning into 'portal'... ... Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/<https://urldefense.proofpoint.com/v2/url?u=https-3A__index.docker.io_v1_&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=yTI42mOIyaw4Y6U8o2eHbYBU2IPRck0lo69aUxd4_Po&s=h_dZ5_X8_Qmk7IKrprXo_gTxKm5qgAvYikvDVIm9yJs&e=> Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Notice the message: 'start: Job failed to start'. Have other people seen this problem? Is there a known work around or is there a fix in flight? Thanks, Shaheen This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
