Re: [onap-discuss] onap-discuss Digest, Vol 3, Issue 7

2017-05-30 Thread Ali, Shaheen
Marco,

We are moving forward with a modified ONAP stack that suits us.  We are not 
tracking the currently released ONAP software.  We are picking up fixes 
appropriate for us as we go forward.

Shaheen


From: PLATANIA, MARCO  (MARCO) [plata...@research.att.com]
Sent: Monday, May 29, 2017 11:54 AM
To: Ali, Shaheen; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] onap-discuss Digest, Vol 3, Issue 7

Hello Shaheen,

Apologies for the late reply. Is this still causing issues to you?

As far as I see from the config file below, you modified some ONAP addresses, 
which is fine, but you need to check if the address assignment is coherent with 
the oam_network_cidr parameter in the heat environment file and the DNS VM 
config, which doesn’t seem to have the correct private address if it is 
resolving them incorrectly.

What template are you using?

resolv.conf seems correct to me. Also, make sure your OpenStack installation 
isn’t preventing you from resolving DNS queries (unfortunately I’m not an 
expert on this, so I can provide little help.)

Thanks,
Marco


On 5/5/17, 1:28 PM, "onap-discuss-boun...@lists.onap.org on behalf of Ali, 
Shaheen"  wrote:

Hello ONAP-discussers,

More information.  Might have a DNS problem.  The resolv.conf file on all 
the instances look like this:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.10.1.13
nameserver xxx.xxx.xxx.xxx
search openstacklocal


This is the correct instance named vm1-dns-server.  However, that domain is 
wrong: openstacklocal causes errors according to the messages in the DNS server.

May  5 17:04:42 vm1-dns-server named[1179]: client 10.10.1.17#43895 
(vm1-message-router.openstacklocal): query (cache) 
'vm1-message-router.openstacklocal/A/IN' denied
May  5 17:04:42 vm1-dns-server named[1179]: client 10.10.1.17#37936 
(vm1-message-router): query (cache) 'vm1-message-router/A/IN' denied

In fact, in this particular example, the portal (10.10.1.17) is trying to 
reach the host named vm1-message-router.  Problem is that the heat template set 
up a zone named simpledemo.openecomp.org in file 
/etc/bind/zones/db.simpledemo.openecomp.org which has an entry like so:
...
vm1.mr.simpledemo.openecomp.org.IN  A   10.10.1.15
...
;Message Router
;mr.api.simpledemo.openecomp.org.   IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
ueb.api.simpledemo.openecomp.org.   IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
mr.api.simpledemo.openecomp.org.IN  A   10.10.1
collector.api.simpledemo.openecomp.org. IN  A   10.10.1
;dbc.api.simpledemo.openecomp.org.  IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
;drprov.api.simpledemo.openecomp.org.   IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
...
So, the A records that point to 10.10.1 look wrong.  The A record for 
vm1.mr.simpledemo.openecomp.org looks correct except that the portal logs in 
the container are throwing exceptions because the web service is trying to 
reach a host named vm1-message-router...

Any clues?

Shaheen


--

Message: 1
Date: Fri, 5 May 2017 13:23:47 +
From: "Ali, Shaheen" 
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Problem with tutorial
Message-ID:
<21aad91308992140820380d7bf70793fa87...@podcwmbxex505.ctl.intranet>
Content-Type: text/plain; charset="iso-8859-1"

I have set up ONAP on our own Newton OpenStack instance.  I cannot add a 
License Key Group.  Where should I begin to debug?  I have poked around the 
logs of vm-vid, vm-sdc and vm-message-router, but nothing stands out.

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.


___
onap-discuss mailing list
onap-discuss@lists.onap.org

https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=4ApVTf-048h2sFMm8kA-ET1VUqm9vnfAQhSqv9gxi0g&s=O2C55Z1TwG8AuavqCnMgqww8R34H-t19kJiTE_oS8SM&e=


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 

Re: [onap-discuss] onap-discuss Digest, Vol 3, Issue 7

2017-05-29 Thread PLATANIA, MARCO (MARCO)
Hello Shaheen,

Apologies for the late reply. Is this still causing issues to you?

As far as I see from the config file below, you modified some ONAP addresses, 
which is fine, but you need to check if the address assignment is coherent with 
the oam_network_cidr parameter in the heat environment file and the DNS VM 
config, which doesn’t seem to have the correct private address if it is 
resolving them incorrectly.

What template are you using? 

resolv.conf seems correct to me. Also, make sure your OpenStack installation 
isn’t preventing you from resolving DNS queries (unfortunately I’m not an 
expert on this, so I can provide little help.)

Thanks,
Marco


On 5/5/17, 1:28 PM, "onap-discuss-boun...@lists.onap.org on behalf of Ali, 
Shaheen"  wrote:

Hello ONAP-discussers,

More information.  Might have a DNS problem.  The resolv.conf file on all 
the instances look like this:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.10.1.13
nameserver xxx.xxx.xxx.xxx
search openstacklocal


This is the correct instance named vm1-dns-server.  However, that domain is 
wrong: openstacklocal causes errors according to the messages in the DNS server.

May  5 17:04:42 vm1-dns-server named[1179]: client 10.10.1.17#43895 
(vm1-message-router.openstacklocal): query (cache) 
'vm1-message-router.openstacklocal/A/IN' denied
May  5 17:04:42 vm1-dns-server named[1179]: client 10.10.1.17#37936 
(vm1-message-router): query (cache) 'vm1-message-router/A/IN' denied

In fact, in this particular example, the portal (10.10.1.17) is trying to 
reach the host named vm1-message-router.  Problem is that the heat template set 
up a zone named simpledemo.openecomp.org in file 
/etc/bind/zones/db.simpledemo.openecomp.org which has an entry like so:
...
vm1.mr.simpledemo.openecomp.org.IN  A   10.10.1.15
...
;Message Router
;mr.api.simpledemo.openecomp.org.   IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
ueb.api.simpledemo.openecomp.org.   IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
mr.api.simpledemo.openecomp.org.IN  A   10.10.1
collector.api.simpledemo.openecomp.org. IN  A   10.10.1
;dbc.api.simpledemo.openecomp.org.  IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
;drprov.api.simpledemo.openecomp.org.   IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
...
So, the A records that point to 10.10.1 look wrong.  The A record for 
vm1.mr.simpledemo.openecomp.org looks correct except that the portal logs in 
the container are throwing exceptions because the web service is trying to 
reach a host named vm1-message-router...

Any clues?

Shaheen


--

Message: 1
Date: Fri, 5 May 2017 13:23:47 +
From: "Ali, Shaheen" 
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Problem with tutorial
Message-ID:
<21aad91308992140820380d7bf70793fa87...@podcwmbxex505.ctl.intranet>
Content-Type: text/plain; charset="iso-8859-1"

I have set up ONAP on our own Newton OpenStack instance.  I cannot add a 
License Key Group.  Where should I begin to debug?  I have poked around the 
logs of vm-vid, vm-sdc and vm-message-router, but nothing stands out.

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.


___
onap-discuss mailing list
onap-discuss@lists.onap.org

https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=4ApVTf-048h2sFMm8kA-ET1VUqm9vnfAQhSqv9gxi0g&s=O2C55Z1TwG8AuavqCnMgqww8R34H-t19kJiTE_oS8SM&e=
 


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] onap-discuss Digest, Vol 3, Issue 7

2017-05-05 Thread Ali, Shaheen
Hello ONAP-discussers,

More information.  Might have a DNS problem.  The resolv.conf file on all the 
instances look like this:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.10.1.13
nameserver xxx.xxx.xxx.xxx
search openstacklocal


This is the correct instance named vm1-dns-server.  However, that domain is 
wrong: openstacklocal causes errors according to the messages in the DNS server.

May  5 17:04:42 vm1-dns-server named[1179]: client 10.10.1.17#43895 
(vm1-message-router.openstacklocal): query (cache) 
'vm1-message-router.openstacklocal/A/IN' denied
May  5 17:04:42 vm1-dns-server named[1179]: client 10.10.1.17#37936 
(vm1-message-router): query (cache) 'vm1-message-router/A/IN' denied

In fact, in this particular example, the portal (10.10.1.17) is trying to reach 
the host named vm1-message-router.  Problem is that the heat template set up a 
zone named simpledemo.openecomp.org in file 
/etc/bind/zones/db.simpledemo.openecomp.org which has an entry like so:
...
vm1.mr.simpledemo.openecomp.org.IN  A   10.10.1.15
...
;Message Router
;mr.api.simpledemo.openecomp.org.   IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
ueb.api.simpledemo.openecomp.org.   IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
mr.api.simpledemo.openecomp.org.IN  A   10.10.1
collector.api.simpledemo.openecomp.org. IN  A   10.10.1
;dbc.api.simpledemo.openecomp.org.  IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
;drprov.api.simpledemo.openecomp.org.   IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
...
So, the A records that point to 10.10.1 look wrong.  The A record for 
vm1.mr.simpledemo.openecomp.org looks correct except that the portal logs in 
the container are throwing exceptions because the web service is trying to 
reach a host named vm1-message-router...

Any clues?

Shaheen


--

Message: 1
Date: Fri, 5 May 2017 13:23:47 +
From: "Ali, Shaheen" 
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Problem with tutorial
Message-ID:
<21aad91308992140820380d7bf70793fa87...@podcwmbxex505.ctl.intranet>
Content-Type: text/plain; charset="iso-8859-1"

I have set up ONAP on our own Newton OpenStack instance.  I cannot add a 
License Key Group.  Where should I begin to debug?  I have poked around the 
logs of vm-vid, vm-sdc and vm-message-router, but nothing stands out.

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.


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss