Michael,

Hard to follow everything you’re doing here, but I suggest we meet to discuss, 
if you want.

Alexis

> On Feb 4, 2018, at 6:15 PM, Michael O'Brien <frank.obr...@amdocs.com> wrote:
> 
> Update:
>    Running Alexis’s expanded onap-parameters.yaml for amsterdam with all the 
> DCAE and heat settings for the Kubernetes side DCAE controller
>    
> https://lists.onap.org/pipermail/onap-discuss/2018-February/007884.html 
> <https://lists.onap.org/pipermail/onap-discuss/2018-February/007884.html>
> https://jira.onap.org/browse/OOM-508 <https://jira.onap.org/browse/OOM-508> 
> https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher+in+OpenStack#ONAPonKubernetesonRancherinOpenStack-Deployingthedcaegen2pod
>  
> <https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher+in+OpenStack#ONAPonKubernetesonRancherinOpenStack-Deployingthedcaegen2pod>
> Writing up specific config expansion to
> https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-AmsterdamOOM+DCAEHeatinstallation
>  
> <https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-AmsterdamOOM+DCAEHeatinstallation>
>  
> triaging if there is a NodePort conflict – 
> https://jira.onap.org/browse/OOM-656 <https://jira.onap.org/browse/OOM-656>
> OOM-657 <https://jira.onap.org/browse/OOM-657>
> Verifying yaml
> Error: release onap-dcaegen2 failed: Service "dcaegen2" is invalid: 
> spec.ports[2]: Duplicate value: api.ServicePort{Name:"", Protocol:"TCP", 
> Port:8443, TargetPort:intstr.IntOrString{Type:0, IntVal:0, StrVal:""}, 
> NodePort:0}
>  
> /michael
>  
> From: Michael O'Brien 
> Sent: Sunday, February 4, 2018 00:00
> To: onap-discuss@lists.onap.org
> Subject: Help: HEAT DCAE controller dcae2_vm_init.sh blueprint tasks failing 
> - need a working DCAE config to compare to
>  
> Team,
>    Goal: to get DCAEGEN2 running in HEAT on openlab – so I can get closed 
> loop logs/DMaaP traffic via the hybrid DCAE/HEAT + Kubernetes deployment and 
> prep for when we add a Filebeat container for the ELK stack to DCAE 
> containers.
>    Issue: cannot get past dcae-bootstrap/opt/dcae2_vm_init.sh at the centos 
> blueprint tasks just before bringing up the consul VMs
>  
>    Need your help.  There are a couple working DCAE orchestrations in HEAT 
> right now and several working closed loop installs on this group -  so if I 
> could get a copy of the values for the following that would be of great 
> assistance.  It looks like everything should be good as long as I am patient 
> (aai starts after 40 min) – holding up DCAE and make sure my env file is 
> exact.
>  
>     I am following RTD and several wikis/jiras.  alexis.de_talho...@bell.ca 
> <mailto:alexis.de_talho...@bell.ca> has been providing a bridge between DCAE 
> and Kubernetes that I now need to dive more into since last being involved 
> with openstack late Nov. – starting on the heat side first.
> http://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/installation_heat.html#heat-template-parameters
>  
> <http://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/installation_heat.html#heat-template-parameters>
> These are good instructions but they have some ambiguities – I will try to 
> add a troubleshooting section once I get an exact set of variables.
>     
>     Right now I am just trying to get the HEAT stack up for Beijing and get 
> past cdap/consul orchestration.
>     Got past the AAI_vm1 container creation/dependency issues by rebooting 
> the VM and then in sequence the DCAE controller VM.
>     Initially had the double v2/v2.0 issue but a vi of the config in 
> /opt/config and /opt/config/app fixed this after an rm of the boot container 
> and a reboot of the DCAE vm.
>     Got past the authentication 404 – but I have an issue with the keypair – 
> but the dcae private/public keys are set ok in /opt/config.
>     This looks to be related to the generated key in 
> /opt/app/config/inputs.yaml:keypair
>     I am going to go through the boot code in demo repo more
>  
> The 4 tasks are created, sent but fail
> I used to get a 404 on network creation until I removed the extra v2.0 from 
> keystone_url.
>  
> >docker tail –f boot
> Initiated ./blueprints/centos_vm.yaml
> If you make changes to the blueprint, run `cfy local init -p 
> ./blueprints/centos_vm.yaml` again to apply them
> + cfy local execute -w install --task-retries=10
> 2018-02-04 04:22:20 CFY <local> Starting 'install' workflow execution
> 2018-02-04 04:22:20 CFY <local> [private_net_9a5e7] Creating node
> 2018-02-04 04:22:20 CFY <local> [security_group_1cbe1] Creating node
> 2018-02-04 04:22:20 CFY <local> [key_pair_0dbec] Creating node
> 2018-02-04 04:22:20 CFY <local> [floatingip_vm00_18e89] Creating node
> 2018-02-04 04:22:20 CFY <local> [key_pair_0dbec.create] Sending task 
> 'nova_plugin.keypair.create'
> 2018-02-04 04:22:20 CFY <local> [security_group_1cbe1.create] Sending task 
> 'neutron_plugin.security_group.create'
> 2018-02-04 04:22:20 CFY <local> [floatingip_vm00_18e89.create] Sending task 
> 'neutron_plugin.floatingip.create'
> 2018-02-04 04:22:20 CFY <local> [private_net_9a5e7.create] Sending task 
> 'neutron_plugin.network.create'
> 2018-02-04 04:22:20 CFY <local> [key_pair_0dbec.create] Task started 
> 'nova_plugin.keypair.create'
> 2018-02-04 04:22:21 CFY <local> [security_group_1cbe1.create] Task started 
> 'neutron_plugin.security_group.create'
> 2018-02-04 04:22:21 CFY <local> [floatingip_vm00_18e89.create] Task started 
> 'neutron_plugin.floatingip.create'
> 2018-02-04 04:22:21 CFY <local> [private_net_9a5e7.create] Task started 
> 'neutron_plugin.network.create'
> 2018-02-04 04:22:21 CFY <local> [key_pair_0dbec.create] Task failed 
> 'nova_plugin.keypair.create' -> The resource could not be found. 
> [status_code=404]
> 2018-02-04 04:22:21 CFY <local> 'install' workflow execution failed: Workflow 
> failed: Task failed 'nova_plugin.keypair.create' -> The resource could not be 
> found. [status_code=404]
> Workflow failed: Task failed 'nova_plugin.keypair.create' -> The resource 
> could not be found. [status_code=404]
> root@onap-dcae-bootstrap:~#
>  
> config 
>  
>   dcae_public_key: ssh-rsa AAAAB3N....gUHlRcVWV7lNo+418Tt 
> michaelobrien@obrienbiometrics
>   dcae_private_key: -----BEGIN RSA PRIVATE KEY-----MIIEow...Zl3t5s-----END 
> RSA PRIVATE KEY-----
>  
>   horizon_url: http://10.12.25.5:5000/v3 <http://10.12.25.5:5000/v3>
>   keystone_url: http://10.12.25.5:5000 <http://10.12.25.5:5000/>
>   dnsaas_keystone_url: http://10.12.25.5:5000/v3 <http://10.12.25.5:5000/v3>
>   dcae_keystone_url: http://10.12.25.5:5000 <http://10.12.25.5:5000/>
> not
> 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>
> defined in RTD
>  
> One of my issues is I do not see where we are getting the env substitution to 
> /opt/config for dcae_keystone_url
>  
> Some references
> https://jira.onap.org/browse/DCAEGEN2-300 
> <https://jira.onap.org/browse/DCAEGEN2-300>
> https://jira.onap.org/browse/LOG-167 <https://jira.onap.org/browse/LOG-167>
> https://jira.onap.org/browse/DOC-245 <https://jira.onap.org/browse/DOC-245>
> https://wiki.onap.org/display/DW/ONAP+on+Kubernetes?refresh=1517595416148&refresh=1517603522550&focusedCommentId=25431052&refresh=1517718504804#comment-25431052
>  
> <https://wiki.onap.org/display/DW/ONAP+on+Kubernetes?refresh=1517595416148&refresh=1517603522550&focusedCommentId=25431052&refresh=1517718504804#comment-25431052>
> https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher+in+OpenStack 
> <https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher+in+OpenStack>
>  
>  
> thank you
> /michael
>  
>     
>  
> Michael O’Brien
> Amdocs Technology
> 16135955268
> 55268
> <image001.jpg>
>  
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> you may review at https://www.amdocs.com/about/email-disclaimer 
> <https://www.amdocs.com/about/email-disclaimer>_______________________________________________
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss

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

Reply via email to