Hi , As per the code in "dnsdesig/dns_plugin.py" in boot container, it expects the "dns" service in endpoints with the same region name as DCAE_REGION. So the region name and tenant name of both the openstack should be same. It worked for me.
Best Regards Bharath T On Wed, Jan 31, 2018 at 5:33 PM, Thiruveedula, Bharath < bharath.thiruveed...@verizon.com> wrote: > Hi Alexis, > > (Sorry Ramu for hijacking the mail) > > I am also facing the same error. > > The parameter you are referring "dcae_keystone_url" is the value in* > /opt/config/keystone_url.txt*? > > First of all, let me clear you that I am trying t install DCAEGEN2 using > heat way not the OOM approach. Though the approach for installing DCAE in > heat or OOM is the same, but the parameter is sligtly different it seems. > > In the heat way of installation, we have three files pointing to keystone: > 1) */opt/config/keystone_url.txt* -> > "*http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0 > <http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0>* > " > 2) */opt/config/**openstack_keystone_url.txt* -> > "*http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0 > <http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0>* > " > 3) */opt/config/dnsaas_keystone_url.txt* -> "*http://10.0.0.8/identity > <http://10.0.0.8/identity>*" > > And below is the contents of /tmp/local_inputs.yaml > > ubuntu1604image_id: 'ubuntu-16.04-x86_64-v1-core' > centos7image_id: 'centos-7-x86_64-v4-core' > flavor_id: 'm1.xlarge' > security_group: 'onap_sg_MYGL' > public_net: 'provider-core-cmn-v4' > private_net: 'oam_onap_MYGL' > openstack: > username: 'admin' > password: 'admin_pw' > tenant_name: 'ONAP_Manual_Installation' > auth_url: 'http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_ > regionOne/identity/v2.0' > region: 'regionOne' > keypair: 'onap_key_MYGL' > key_filename: ./key600 > location_prefix: 'dcae' > location_domain: 'MYGL.USWIN' > codesource_url: 'https://nexus.onap.org/service/local/repositories/raw/ > content' > codesource_version: 'org.onap.dcaegen2.deployments/releases' > > I tried to see the request logs from multicloud > > [31/Jan/2018 11:31:22] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v3/auth/tokens HTTP/1.1" 201 5135 > [31/Jan/2018 11:31:24] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/dns-delegate/v2/zones?name=MYGL.USWIN. HTTP/1.1" > 200 635 [31/Jan/2018 11:31:24] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/dns-delegate/v2/zones HTTP/1.1" 200 618 > [31/Jan/2018 11:31:35] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/dns-delegate/v2/zones?name=MYGL.USWIN. HTTP/1.1" > 200 635 [31/Jan/2018 11:32:30] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 > [31/Jan/2018 11:32:31] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=oam_onap_MYGL > HTTP/1.1" 200 631 [31/Jan/2018 11:32:31] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0 HTTP/1.1" 200 185 [31/Jan/2018 > 11:32:31] "POST > /api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens > HTTP/1.1" 200 4481 [31/Jan/2018 11:32:32] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/compute/v2.1/os-keypairs HTTP/1.1" 200 5152 > [31/Jan/2018 11:32:32] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 > [31/Jan/2018 11:32:33] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=provider-core-cmn-v4 > HTTP/1.1" 200 654 [31/Jan/2018 11:32:33] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/network/v2.0/floatingips.json HTTP/1.1" 201 434 > [31/Jan/2018 11:32:34] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 > [31/Jan/2018 11:32:34] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/network/v2.0/security-groups.json?name=onap_sg_MYGL > HTTP/1.1" 200 2628 [31/Jan/2018 11:32:36] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 > [31/Jan/2018 11:32:37] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/network/v2.0/ports.json HTTP/1.1" 201 760 > [31/Jan/2018 11:32:38] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 > [31/Jan/2018 11:32:38] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 > [31/Jan/2018 11:35:55] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 > [31/Jan/2018 11:35:55] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=oam_onap_MYGL > HTTP/1.1" 200 631 [31/Jan/2018 11:35:56] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 > [31/Jan/2018 11:35:56] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/network/v2.0/security-groups.json?name=onap_sg_MYGL > HTTP/1.1" 200 2628 [31/Jan/2018 11:35:57] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 > [31/Jan/2018 11:35:57] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=provider-core-cmn-v4 > HTTP/1.1" 200 654 [31/Jan/2018 11:35:58] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/network/v2.0/floatingips.json HTTP/1.1" 201 434 > [31/Jan/2018 11:35:58] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0 HTTP/1.1" 200 185 [31/Jan/2018 > 11:35:58] "POST > /api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens > HTTP/1.1" 200 4481 [31/Jan/2018 11:35:59] "GET /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/compute/v2.1/os-keypairs HTTP/1.1" 200 5152 > [31/Jan/2018 11:36:01] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 > [31/Jan/2018 11:36:02] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/network/v2.0/ports.json HTTP/1.1" 201 759 > [31/Jan/2018 11:36:02] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 > [31/Jan/2018 11:36:03] "POST /api/multicloud-titanium_ > cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 > > > > from dcae2_vm_init.sh, it can access designate where as in boot container > it didn't send any request to designate. > > Am I missing something here? > > > > > On Wed, Jan 31, 2018 at 2:25 AM, Alexis de Talhouët < > adetalhoue...@gmail.com> wrote: > >> Have you tried *dcae_keystone_url* = http://10.0.14.1/api/multicloud-ti >> tanium_cloud/v0/pod25_regionOne/identity/v2.0 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.0.14.1_api_multicloud-2Dtitanium-5Fcloud_v0_pod25-5FregionOne_identity_v2.0&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=0nYDovBOw68SXyeIgWKuj70Mi0tfqJHZdlp18cvw9SM&e=> >> ? >> >> >> On Jan 30, 2018, at 3:20 PM, Akula, Ramanjaneyul Reddy (Nokia - >> US/Irving) <ramanjaneyul_reddy.ak...@nokia.com> wrote: >> >> Alex, >> Thanks a lot for quick response. >> >> Apologies. There is a typo due to copy paste error. >> >> I meant the dcae_keystone is pointing to the openstack keystone endpoint >> url >> dcae_keystone_url: http://<openstack >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__-253Copenstack_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=fxbsQBz0OUNw1rx7itZZrsB0zEmCSEPQMc2NSvx3UBI&e=> >> public keystone ip>:5000 >> >> Here is the content from bootstrat config files >> >> ==================== >> root@dcae-dcae-bootstrap:/opt# cat /opt/config/dnsaas_keystone_url.txt >> http://<designateip>/identity >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__-253Cdesignateip-253E_identity&d=DwQFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=cLv1G4L3BaAGcx2p8ZIaZLDnbZcbwyP1OCuAS4znzkI&e=> >> root@dcae-dcae-bootstrap:/opt# >> >> ==================== >> >> dcae2_vm_init.sh: DNSAAS_SERVICE_URL="$(cat >> /opt/config/dnsaas_keystone_url.txt)" >> ==================== >> >> ==================== >> cat keystone_url.txt >> http://<keystone >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__-253Ckeystone_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=C4oy3_INqHSLIPKqSoiA8-rVFLQa3Yis_k5ntHTJ_fY&e=> >> endpoint IP>:5000/v2.0 >> ==================== >> ==================== >> >> root@dcae-dcae-bootstrap:/opt/config# cat openstack_keystone_url.txt >> http://<keystone >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__-253Ckeystone_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=C4oy3_INqHSLIPKqSoiA8-rVFLQa3Yis_k5ntHTJ_fY&e=> >> endpoint IP>:5000 >> ==================== >> >> From your statement è >> When creating a VM using a proxied DNS Designate, the *dcae_keystone_url* >> _must_ leverage the multicloud-titanium cloud driver, e.g. in your case >> *dcae_keystone_url* = http://10.0.14.1/api/multicloud-tit >> anium_cloud/v0/pod25_regionOne/identity/v2.0 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.0.14.1_api_multicloud-2Dtitanium-5Fcloud_v0_pod25-5FregionOne_identity_v2.0&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=0nYDovBOw68SXyeIgWKuj70Mi0tfqJHZdlp18cvw9SM&e=> >> . >> >> I believe you meant to do this registration in AAI so that it will >> leverage the titanium drivier. >> And the init script already has the logic to register the multicloud pod >> with aai using above said url. >> >> ============= >> CLOUD_IDENTITY_URL="http://${MCIP}/api/multicloud-titanium_c >> loud/v0/${CLOUD_OWNER}_${CLOUD_REGION}/identity/v2.0 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__-24-257Bmcip-257D_api_multicloud-2Dtitanium-5Fcloud_v0_-24-257BCLOUD-5FOWNER-257D-5F-24-257BCLOUD-5FREGION-257D_identity_v2.0&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=NfnHmo23ycgYfKIskqnPR-yroxPA7u3ajHcpuX9BKfY&e=> >> " >> ============= >> >> Or am I interpreting you wrongly? >> >> *best regards,* >> *Ramu* >> >> >> *From:* Alexis de Talhouët [mailto:adetalhoue...@gmail.com >> <adetalhoue...@gmail.com>] >> *Sent:* Tuesday, January 30, 2018 1:23 PM >> *To:* Akula, Ramanjaneyul Reddy (Nokia - US/Irving) < >> ramanjaneyul_reddy.ak...@nokia.com> >> *Cc:* Yang, Bin <bin.y...@windriver.com>; onap-discuss < >> onap-discuss@lists.onap.org>; Bisht, Suraj (Nokia - US/Irving) < >> suraj.bi...@nokia.com>; Talari Nehemiah Vara, Vara (Nokia - US/Irving) < >> vara.talari_nehemiah_v...@nokia.com> >> *Subject:* Re: [onap-discuss] [DCAGEN2] Proxied DNS Designate only with >> Multicloud Titanium >> >> Ramu, >> >> You’re confusing things. >> >> *dcae_keystone_url* is the keystone of the openstack where you will >> deploy DCAE >> *dnsaas_keystone_url* is the keystone of the openstack providing DNS >> Designate support >> >> When creating a VM using a proxied DNS Designate, the *dcae_keystone_url* >> _must_ leverage the multicloud-titanium cloud driver, e.g. in your case >> *dcae_keystone_url* = http://10.0.14.1/api/multicloud-tit >> anium_cloud/v0/pod25_regionOne/identity/v2.0 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.0.14.1_api_multicloud-2Dtitanium-5Fcloud_v0_pod25-5FregionOne_identity_v2.0&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=0nYDovBOw68SXyeIgWKuj70Mi0tfqJHZdlp18cvw9SM&e=> >> . >> This is because cloudify will create the resources for the VM to be >> created using the *dcae_keystone_url*. Among other things, this will >> create the record in the DNS zone. This is possible because >> the multicloud-titanium leverage AAI ESR information to know that for a >> particular cloud-site (identified by the *dcae_keystone_url*) it should >> be using another site that provides Designate support (dns-delegate) >> >> See* cloud-extra-info,* e.g. >> { >> "epa-caps": { >> "huge_page": "true", >> "cpu_pinning": "true", >> "cpu_thread_policy": "true", >> "numa_aware": "true", >> "sriov": "true", >> "dpdk_vswitch": "true", >> "rdt": "false", >> "numa_locality_pci": "true" >> }, >> "dns-delegate": { >> "cloud-owner": "pod25dns", >> "cloud-region-id": "RegionOne" >> } >> } >> >> >> Alexis >> >> >> On Jan 30, 2018, at 2:07 PM, Akula, Ramanjaneyul Reddy (Nokia - >> US/Irving) <ramanjaneyul_reddy.ak...@nokia.com> wrote: >> >> Hi Alexis, >> Thanks for the response. >> >> I’m using below params in my env file while creating the heat stack. >> >> =================== >> dnsaas_config_enabled: true >> dnsaas_region: regionOne >> dnsaas_keystone_url: http://<designate >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__-253Cdesignate_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=kAnMrv976nwqlscuw71hwWezjAHeWchLzFNa8n1EDQA&e=> >> ip>/identity >> dnsaas_tenant_name: admin >> dnsaas_username: admin >> dnsaas_password: password >> dcae_keystone_url: http://<designate >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__-253Cdesignate_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=kAnMrv976nwqlscuw71hwWezjAHeWchLzFNa8n1EDQA&e=> >> ip>:5000 >> =================== >> >> To try it out, I changed the dnsaas_keystone_url.txt file on bootstrap >> and tried to kick start the vm init script. >> >> Changed file content ============ >> >> root@dcae-dcae-bootstrap:~# cat /opt/config/dnsaas_keystone_url.txt >> http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_ >> regionOne/identity/v2.0 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.0.14.1_api_multicloud-2Dtitanium-5Fcloud_v0_pod25-5FregionOne_identity_v2.0&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=0nYDovBOw68SXyeIgWKuj70Mi0tfqJHZdlp18cvw9SM&e=> >> root@dcae-dcae-bootstrap:~# >> ============ >> >> I’m getting the same error as earlier. >> >> By the way with/without this change, on the designate instance I see the >> dns zone getting created + recordset is being added. It means I believe >> it’s able to talk to Designate successfully. >> >> ubuntu@designate:~/devstack$ openstack recordset list >> 122ffabf-0268-41b1-a3d7-fed5ca4e2366 >> +--------------------------------------+-------------------- >> -+------+--------------------------------------------------- >> ---------------------+--------+--------+ >> | id | name | type | >> records | >> status | action | >> +--------------------------------------+-------------------- >> -+------+--------------------------------------------------- >> ---------------------+--------+--------+ >> | 14b0c34e-c88e-4ead-81b0-fe7f1c8d6679 | wJOo.dcae.onap.org >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__wJOo.dcae.onap.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=rR8siFlvg5WjlQPoYDEOwqoHFZmVouWz16EH9fh0fYA&e=>. >> | NS | ns1.devstack.org >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__ns1.devstack.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=TZPtATlJDI4wOf-czhbYyU-HdsE66xtD6NGkCs9syys&e=>. >> | ACTIVE | NONE | >> | f95281a1-f97c-4beb-a7cc-77bbbb7d860c | wJOo.dcae.onap.org >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__wJOo.dcae.onap.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=rR8siFlvg5WjlQPoYDEOwqoHFZmVouWz16EH9fh0fYA&e=>. >> | SOA | ns1.devstack.org >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__ns1.devstack.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=TZPtATlJDI4wOf-czhbYyU-HdsE66xtD6NGkCs9syys&e=> >> . lji.research.att.com >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__lji.research.att.com&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=aHanHyaTe2rxtZnEa7YlydAuD0SZsk4AjB5lCa7KYXA&e=>. >> 1517329561 <0151%20732%209561> 3565 600 86400 3600 | ACTIVE | NONE | >> +--------------------------------------+-------------------- >> -+------+--------------------------------------------------- >> ---------------------+--------+--------+ >> >> >> best regards, >> Ramu >> >> >> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com >> <adetalhoue...@gmail.com>] >> Sent: Tuesday, January 30, 2018 10:47 AM >> To: Akula, Ramanjaneyul Reddy (Nokia - US/Irving) < >> ramanjaneyul_reddy.ak...@nokia.com> >> Cc: Yang, Bin <bin.y...@windriver.com>; onap-discuss < >> onap-discuss@lists.onap.org>; Bisht, Suraj (Nokia - US/Irving) < >> suraj.bi...@nokia.com>; Talari Nehemiah Vara, Vara (Nokia - US/Irving) < >> vara.talari_nehemiah_v...@nokia.com> >> Subject: Re: [onap-discuss] [DCAGEN2] Proxied DNS Designate only with >> Multicloud Titanium >> >> Ramu, >> >> What did you use for DCAE_PROXIED_KEYSTONE_URL parameter? It must be the >> proxied url. See https://github.com/onap/oom/blob/amsterdam/kubernetes/co >> nfig/onap-parameters-sample.yaml#L143-L144 >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_onap_oom_blob_amsterdam_kubernetes_config_onap-2Dparameters-2Dsample.yaml-23L143-2DL144&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=pnotPr6dpisM6foBpYgO5J1s1c6o7L1WyW-3aVPVdUY&e=> >> >> Hope this helps, >> Alexis >> >> >> On Jan 30, 2018, at 11:27 AM, Akula, Ramanjaneyul Reddy (Nokia - >> US/Irving) <ramanjaneyul_reddy.ak...@nokia.com> wrote: >> >> Hi Alex/Bin, >> I’m also witnessing the same problem in my cloud. >> My cloud is built using RedHat OSP10 (Newton). >> >> Bottstrap log has below info. >> >> 2018-01-30 16:00:51 CFY <local> [security_group_38d63] Configuring node >> 2018-01-30 16:00:51 CFY <local> [private_net_85fe3] Configuring node >> 2018-01-30 16:00:51 CFY <local> [key_pair_31e7f] Configuring node >> 2018-01-30 16:00:51 CFY <local> [floatingip_vm00_474ed] Configuring node >> 2018-01-30 16:00:51 CFY <local> [key_pair_31e7f] Starting node >> 2018-01-30 16:00:51 CFY <local> [private_net_85fe3] Starting node >> 2018-01-30 16:00:51 CFY <local> [security_group_38d63] Starting node >> 2018-01-30 16:00:51 CFY <local> [floatingip_vm00_474ed] Starting node >> 2018-01-30 16:00:52 CFY <local> [fixedip_vm00_b112a] Creating node >> 2018-01-30 16:00:52 CFY <local> [dns_cm_3211b] Creating node >> 2018-01-30 16:00:52 CFY <local> [dns_vm00_3cba2] Creating node >> 2018-01-30 16:00:52 CFY <local> [dns_cm_3211b.create] Sending task >> 'dnsdesig.dns_plugin.aneeded' >> 2018-01-30 16:00:52 CFY <local> [dns_vm00_3cba2.create] Sending task >> 'dnsdesig.dns_plugin.aneeded' >> 2018-01-30 16:00:52 CFY <local> [fixedip_vm00_b112a.create] Sending task >> 'neutron_plugin.port.create' >> 2018-01-30 16:00:52 CFY <local> [dns_cm_3211b.create] Task started >> 'dnsdesig.dns_plugin.aneeded' >> 2018-01-30 16:00:52 CFY <local> [dns_vm00_3cba2.create] Task started >> 'dnsdesig.dns_plugin.aneeded' >> 2018-01-30 16:00:52 CFY <local> [dns_cm_3211b.create] Task failed >> 'dnsdesig.dns_plugin.aneeded' -> 'dns' >> 2018-01-30 16:00:52 CFY <local> 'install' workflow execution failed: >> Workflow failed: Task failed 'dnsdesig.dns_plugin.aneeded' -> 'dns' >> >> My AAI is already populated with both the pods info as shown below >> >> =================== >> { >> "cloud-region": [ >> { >> "cloud-owner": "pod25", >> "cloud-region-id": "regionOne", >> "cloud-type": "openstack", >> "owner-defined-type": "owner-defined-type", >> "cloud-region-version": "titanium_cloud", >> "identity-url": "http://10.0.14.1/api/multiclo >> ud-titanium_cloud/v0/pod25_regionOne/identity/v2.0 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.0.14.1_api_multicloud-2Dtitanium-5Fcloud_v0_pod25-5FregionOne_identity_v2.0&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=0nYDovBOw68SXyeIgWKuj70Mi0tfqJHZdlp18cvw9SM&e=> >> ", >> "cloud-zone": "cloud zone", >> "complex-name": "complex name", >> "resource-version": "1517257340971" >> }, >> { >> "cloud-owner": "pod25dns", >> "cloud-region-id": "regionOne", >> "cloud-type": "openstack", >> "owner-defined-type": "owner-defined-type", >> "cloud-region-version": "titanium_cloud", >> "identity-url": "http://10.0.14.1/api/multiclo >> ud-titanium_cloud/v0/pod25dns_regionOne/identity/v2.0 >> <https://urldefense.proofpoint.com/v2/url?u=http-3A__10.0.14.1_api_multicloud-2Dtitanium-5Fcloud_v0_pod25dns-5FregionOne_identity_v2.0&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=D4UM1YyFLMtVDdml6hccl-JRsozCM1q1kyzq2C47xq0&e=> >> ", >> "cloud-zone": "cloud zone", >> "complex-name": "complex name2", >> "resource-version": "1517257341850" >> } >> ] >> } >> =================== >> >> >> And on designate I see the new zone getting created. >> >> Appreciate any hints/clues on how to overcome this problem. >> >> >> >> best regards, >> Ramu >> >> >> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discu >> ss-boun...@lists.onap.org <onap-discuss-boun...@lists.onap.org>] On >> Behalf Of Alexis de Talhouët >> Sent: Friday, January 19, 2018 1:08 PM >> To: Yang, Bin <bin.y...@windriver.com> >> Cc: onap-discuss <onap-discuss@lists.onap.org> >> Subject: Re: [onap-discuss] [DCAGEN2] Proxied DNS Designate only with >> Multicloud Titanium >> >> Ah, I missed the fact that when it’s proxied, dcae_keystone_url needs to >> be the one from multivim. All good now. >> >> Alexis >> >> >> >> >> On Jan 19, 2018, at 11:05 AM, Alexis de Talhouët <adetalhoue...@gmail.com> >> wrote: >> >> Hum, actually, the DNS zone registration works. But now, the boot >> container is failing with the following: >> >> 2018-01-19 15:52:53 CFY <local> [dns_cm_4834b.create] Sending task >> 'dnsdesig.dns_plugin.aneeded' >> 2018-01-19 15:52:53 CFY <local> [dns_vm00_73f5a.create] Sending task >> 'dnsdesig.dns_plugin.aneeded' >> 2018-01-19 15:52:53 CFY <local> [fixedip_vm00_91a2f] Creating node >> 2018-01-19 15:52:53 CFY <local> [dns_cm_4834b.create] Task started >> 'dnsdesig.dns_plugin.aneeded' >> 2018-01-19 15:52:53 CFY <local> [dns_vm00_73f5a.create] Task started >> 'dnsdesig.dns_plugin.aneeded' >> 2018-01-19 15:52:53 CFY <local> [dns_cm_4834b.create] Task failed >> 'dnsdesig.dns_plugin.aneeded' -> 'dns' >> 2018-01-19 15:52:53 CFY <local> 'install' workflow execution failed: >> Workflow failed: Task failed 'dnsdesig.dns_plugin.aneeded' -> 'dns' >> Workflow failed: Task failed 'dnsdesig.dns_plugin.aneeded' -> ‘dns' >> >> Of course, the OpenStack on which I deploy DCAE doesn’t support DNS >> Designate, I’m wondering what I could have missed? >> >> Alexis >> >> >> >> On Jan 19, 2018, at 10:46 AM, Alexis de Talhouët <adetalhoue...@gmail.com> >> wrote: >> >> Bin, >> >> Awesome, I got it to work with my OpenStack Pike instance. >> >> One issue though, the register_multicloud_pod25dns_with_aai() is using >> hardcoded username/password https://gerrit.onap.org/r/gitweb?p=demo. >> git;a=blob;f=boot/dcae2_vm_init.sh;h=b071dffd53f0a431bbdf >> f1c1228edce8ecddef2d;hb=refs/heads/amsterdam >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dboot_dcae2-5Fvm-5Finit.sh-3Bh-3Db071dffd53f0a431bbdff1c1228edce8ecddef2d-3Bhb-3Drefs_heads_amsterdam&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=fitNlPOFcshGlq3WAQcIOCVMFd3ZzASgbfkiOJI07n4&e=> >> >> I opened DCAEGEN2-270 and submitted the fix https://gerrit.onap.org/r/ >> #/c/28673/ >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_28673_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=HIIGoKowEylNwpgLDiLnwoVGHpt_UARpxOuPAky74uQ&e=> >> >> Current workaround is to push the data in AAI prior to having the script >> running. So the put request will fail, but the validation will pass. >> >> Alexis >> >> >> >> On Jan 19, 2018, at 12:10 AM, Yang, Bin <bin.y...@windriver.com> wrote: >> >> Hi Alexis, >> >> Please refer to answers embedded below >> >> Best Regards, >> Bin Yang, Solution Readiness Team, Wind River >> Direct +86,10,84777126 Mobile +86,13811391682 Fax +86,10,64398189 >> Skype: yangbincs993 >> >> -----Original Message----- >> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com >> <adetalhoue...@gmail.com>] >> Sent: Friday, January 19, 2018 10:30 AM >> To: Yang, Bin >> Cc: onap-discuss >> Subject: Re: [onap-discuss] [DCAGEN2] Proxied DNS Designate only with >> Multicloud Titanium >> >> Hi Bin, >> >> So if I understand correctly, I should register the VIM in multi cloud >> (do you have an example or a link on how to ) and DCAE will be able to use >> it to proxy DNS request (DNSaaS) to this instance. I was under the >> impression it was hard coded to pod25 in the DCAE boostrap script, I’ll >> look again. >> >> >> [Bin] Yes, pod25 was hard coded in DCAE bootstrap script, but it is just >> the cloud owner name, most related information that DCAE bootstrap uses to >> register a VIM instance are passed by HEAT template ( I believe OOM could >> support that parameter injection , correct?) >> >> I’m glad this is already there then, I guess I got confused while reading >> the script. I’ll try this tomorrow. >> [Bin] I think it is the hardcoded 'titanium_cloud' in that script to >> confuse you. This could be changed to be a parameter passing by HEAT/OOM. >> But right now MultiCloud plugin for titanium_cloud support vanilla >> OpenStack version like ocata, mitaka, newton as well. I didn't try the >> pike, but there is big chance that pike can be supported without any >> modification. >> >> So you confirm I can already use the proxy setup provided by DCAE to use >> a proxy for DNS Desginate other than the OpenLab one? >> >> I have OpenStack Pike, would that work? >> [Bin] I didn't test with pike yet, you can give it a try . >> >> >> OOM does already provide the support for this in Amsterdam. I guess what >> I was looking for is a proxy setup using plain OpenStack APIs. and not >> using Multicloud. But I’m all in for using Multicloud if available and >> working already. >> >> [Bin]: I do think it will be valuable that OOM provide such kind of >> support and I can share what I learned and hope you get more comprehensive >> understanding of the requirement/solutions. >> >> Thanks, >> Alexis >> >> >> >> On Jan 18, 2018, at 8:58 PM, Yang, Bin <bin.y...@windriver.com> wrote: >> >> Hi Alexis, >> >> I think it would be better to clarify that: proxy the DNS Designate >> requests is the enhanced feature by MultiCloud to federate services from >> different underlying VIM instances. In ONAP Amsterdam release it has been >> implemented to support both vanilla OpenStack Ocata (and Newton as well, >> not tested yet) and Titanium Cloud, and more to come in future releases. I >> had tested with vanilla OpenStack Ocata and it works well. >> >> To utilize it , the consumer presuppose that the MultiCloud services >> are ready and the VIM instances are registered. So for DCAEgen2 which has >> been the actually consumer in ONAP Amsterdam release, the bootstrap VM did >> this part , the VIM instance information (both underlying OpenStack and the >> proxied one which exposes Designate services) are passed in by HEAT >> template/environment file. I believe OOM can support this in similar way. >> >> This federation can be designed/implemented in various way but why it >> was designed/implemented is that MultiCloud do the federation and the >> consumers will be transparent with regards who provides DNSaaS services. >> >> BTW, I do think it will be valuable that OOM can offer the similar >> proxy to DNS designate, I would like to share our experiences. >> >> Best Regards, >> Bin Yang, Solution Readiness Team, Wind River >> Direct +86,10,84777126 Mobile +86,13811391682 Fax +86,10,64398189 >> Skype: yangbincs993 >> >> -----Original Message----- >> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discu >> ss-boun...@lists.onap.org <onap-discuss-boun...@lists.onap.org>] On >> Behalf Of Alexis de Talhouët >> Sent: Friday, January 19, 2018 6:34 AM >> To: onap-discuss >> Subject: [onap-discuss] [DCAGEN2] Proxied DNS Designate only with >> Multicloud Titanium >> >> Hi experts, >> >> In the dcae_vm_init.sh script, we have the possibility to proxy the DNS >> Designate requests to an OpenStack other than the one on which we spawn >> DCAE. >> But this feature only allow to proxy to Multicloud Titanium cloud, it >> doesn’t allow to proxy to an other plain OpenStack instance. >> I was wondering whether a contribution to address this is Amsterdam would >> be accepted, if yes, I can do it. >> >> Basically, I’d like to leverage the dnaas_* config bits to establish a >> connection to an OpenStack directly, instead of using Multi-cloud. >> I would have a add a param to let the user choose whether the use >> Multicloud Titanium or plain OpenStack. >> >> Please, let me know what you think of this? >> >> FYI, I tend to think we should be able to have DNS Designate running >> where ever we want in the infra, as long as it’s provided. Moreover, we’re >> working on providing it in OOM, so it’s not required in ppl infra. >> >> Thanks, >> Alexis >> >> >> _______________________________________________ >> onap-discuss mailing list >> onap-discuss@lists.onap.org >> https://lists.onap.org/mailman/listinfo/onap-discuss >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkElFfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCDrCAx36YI_USDA&s=WxS_I3hc1S-AKQ4tt9pkJJZWEGzyQaa7nVizSVgEHYs&e=> >> >> >> >> _______________________________________________ >> onap-discuss mailing list >> onap-discuss@lists.onap.org >> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.o >> nap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=udBTRvFvX >> C5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=UTP8N06L2trD3jawJkEl >> FfA6CQYtkCWzTnn4GsHkmJw&m=yVUttGTl-Q6McKAsdtJZ3a2xYL5eCD >> rCAx36YI_USDA&s=WxS_I3hc1S-AKQ4tt9pkJJZWEGzyQaa7nVizSVgEHYs&e= >> >> >
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
