Sorry reread – the -s option is to override the master server name/ip – on some environment (I don’t know yours) because of dns or routing – pass in the IP not the dns name of the server the -a option is to override the derived CATTLE_AGENT ip of the registering slave – again IP is safer for some environments – usually rancher detects the correct IP - but on occasion it will confuse multiple networks on the slave and send the wrong routable IP – if multiple private networks exist
Anyway, most times – aws, azure, VMware (but not openstack) – using the defaults is OK -s is required -a is not -b branch -s server-domain/ip -e onap If you do use -a you will need a -c true (the two go together, a -c false will ignore the client ip override) See the script -c false -a 104.209.168.116 should be -c true -a 104.209.168.116 https://git.onap.org/logging-analytics/tree/deploy/rancher/oom_rancher_setup.sh#n170 if [[ "$COMPUTEADDRESS" != false ]]; then echo "sudo docker run --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher $REGISTRATION_DOCKER $RANCHER_URL/v1/scripts/$REGISTRATION_TOKEN" sudo docker run --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher $REGISTRATION_DOCKER $RANCHER_URL/v1/scripts/$REGISTRATION_TOKEN else echo "sudo docker run -e CATTLE_AGENT_IP=\"$ADDRESS\" --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher rancher/agent:v$AGENT_VERSION http://$SERVER:$PORT/v1/scripts/$TOKEN"; sudo docker run -e CATTLE_AGENT_IP="$ADDRESS" --rm --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher rancher/agent:v$AGENT_VERSION http://$SERVER:$PORT/v1/scripts/$REGISTRATION_TOKEN fi Also note: kubectl/helm will work/fail together – both key off a working .kube/config Top/get nodes will take up to 2 min after host registration to see a server. /michael From: onap-discuss@lists.onap.org <onap-discuss@lists.onap.org> On Behalf Of Michael O'Brien Sent: Thursday, January 10, 2019 6:43 PM To: Samirkumar Ramcharitaprasad Singh <samirkumar_si...@infosys.com>; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] OOM issues after the Casablanca Release #oom Samir Hi the following error stood out – this likely means you are running the default 8080 port – my script sets up 8880 – to avoid any conflicts with (not supposed to be there – server software on 8080) The connection to the server was refused - did you specify the right host or port? Edit your ~/.kube/config and change 8880 to 8080 Kubectl should work then for your setup. However if you ran my script in its entiretly – then your rancher_server docker should be exposed on 8880 – if you cannot get either the k8s dashboard or kubectl to work – then host registration failed from either your co-located host or one/all of the slaves. In that case verify the IP back to the master – in windriver/openlab it should be your private ip 10.0.16.1 not the 10.12.0.0/16 EIP – on certain systems I also provided for CATTLE_AGENT override – the -a option you used. Worst case – delete all hosts in the gui – and re-add one from the docker paste emitted from the “add hosts” button – essentially what my script does. If that does not work then you have a communication problem to the host or from the slave – check that all your CIDRs are open – you can run with a security group of 0.0.0.0/0 ::1 – and only if your server is exposed to the internet directly (not in a VPC on AWS for example) – lock down 10249-10255 by using the oauth option on the rancher gui (get rid of the ! icon) – I use github oauth it works very well – after that crypto miners will not be able to provision pods. Thank you /michael From: Samirkumar Ramcharitaprasad Singh <samirkumar_si...@infosys.com<mailto:samirkumar_si...@infosys.com>> Sent: Thursday, January 10, 2019 5:11 AM To: Michael O'Brien <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: RE: [onap-discuss] OOM issues after the Casablanca Release #oom Hello Michael, Just noticed that the script below https://git.onap.org/logging-analytics/tree/deploy/rancher/oom_rancher_setup.sh<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.onap.org%2Flogging-analytics%2Ftree%2Fdeploy%2Francher%2Foom_rancher_setup.sh&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824895869&sdata=4yJQL2lbURSkng%2FkxcPnqf96KP%2FkAOMGzbkGfKzs4lY%3D&reserved=0> we are now passing additional parameters for sudo ./oom_rancher_setup.sh -b master -s cd.onap.cloud -e onap -c false -a 104.209.168.116 -v true As earlier I have been following your guidance on link below https://wiki.onap.org/display/DW/Cloud+Native+Deployment#CloudNativeDeployment-Scriptedundercloud(Helm/Kubernetes/Docker)andONAPinstall-SingleVM This had the advice to use just below ./oom_rancher_setup.sh -b master -s <your domain/ip> -e onap Please advise if --a [IP address] : client address ip - no FQDN Is needed because we are doing an ssh to the VM on which the Rancher is set up directly ? The reason I seek your help is today as today we simply couldn’t get kubectl top nodes after set up Nor could get the Helm version for the server with message of The connection to the server was refused - did you specify the right host or port? Br Samir K From: Michael O'Brien [mailto:frank.obr...@amdocs.com] Sent: Wednesday, January 09, 2019 11:20 PM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Samirkumar Ramcharitaprasad Singh <samirkumar_si...@infosys.com<mailto:samirkumar_si...@infosys.com>> Cc: Mike Elliott <mike.elli...@amdocs.com<mailto:mike.elli...@amdocs.com>> Subject: RE: [onap-discuss] OOM issues after the Casablanca Release #oom Samir, Hi, thanks for using the script, the cd.sh script assumes that your rancher cluster is fully setup or that you are using cd.sh to clone the oom repo - this includes installing Mike’s helm plugin deploy.sh script. This is done automatically in the cd.sh script if you use the -c true option (cd.sh clones the oom repo) – yes this is my script and I last added the helm plugin option after the clone so that we always get the latest version of plugin.sh from the oom repo – I may https://git.onap.org/logging-analytics/tree/deploy/cd.sh#n103<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.onap.org%2Flogging-analytics%2Ftree%2Fdeploy%2Fcd.sh%23n103&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824855840&sdata=7QVMDw3o6J8syW5A589FLH%2FDqyFGNVOUqc%2Bl2%2B2daBE%3D&reserved=0> sudo cp -R ~/oom/kubernetes/helm/plugins/ ~/.helm or follow the page https://wiki.onap.org/display/DW/OOM+Helm+%28un%29Deploy+plugins<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.onap.org%2Fdisplay%2FDW%2FOOM%2BHelm%2B%2528un%2529Deploy%2Bplugins&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824865849&sdata=2h2HCSxcRhiYxImHiZ2OUPwWu4h%2FnBjOu9VggRQTXxE%3D&reserved=0> https://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_quickstart_guide.html<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fonap.readthedocs.io%2Fen%2Flatest%2Fsubmodules%2Foom.git%2Fdocs%2Foom_quickstart_guide.html&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824865849&sdata=afxt2a3Bkj6UqioI5wilkF8cQWryal4LlXv8BJmr7Ew%3D&reserved=0> In a pending review for cd.sh to include intelligent sequencing of the pods – I have moved the helm plugin copy outside the loop – as it will cause issues for anyone with an existing oom repo - remember the cd.sh script is primariliy intended for CI/CD – where I throw out the oom repo on each run – I am making it dev friendly. Line 143 of https://gerrit.onap.org/r/#/c/75422/<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgerrit.onap.org%2Fr%2F%23%2Fc%2F75422%2F&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824875854&sdata=et7zxtgFdL5kq%2FyShHgbH%2FGJoYUebx2zQsQLASkpZF4%3D&reserved=0> for https://jira.onap.org/browse/LOG-898<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.onap.org%2Fbrowse%2FLOG-898&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824875854&sdata=28K01myCW3wbEaJArg4ousEWFZsE6DWI8OazOc3FvjM%3D&reserved=0> I may just put a secondary wget and chmod 777 on the 2 files in https://git.onap.org/oom/tree/kubernetes/helm/plugins/deploy<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.onap.org%2Foom%2Ftree%2Fkubernetes%2Fhelm%2Fplugins%2Fdeploy&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824885859&sdata=3naMViz7desvN03OFQWdR0ex4k9ITNjT9wP34hdaIvA%3D&reserved=0> for the first run where there is no oom repo yet. do either of those or just run the helm deploy cp and you will be OK Remember that these deployment scripts are an attempt to fill in the devops hole to allow the logging project and any other project to get onap up – the goal is one-click through the templates but it is still a WIP because the helm/kubernetes tools are in constant motion and reflected in the scripts below https://git.onap.org/logging-analytics/tree/deploy/cd.sh<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.onap.org%2Flogging-analytics%2Ftree%2Fdeploy%2Fcd.sh&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824885859&sdata=dlQ%2BGhgpKbr8TVmHdhhvO9aGemjlAxb6QbJBnIEV3yY%3D&reserved=0> https://git.onap.org/logging-analytics/tree/deploy/docker_prepull.sh<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.onap.org%2Flogging-analytics%2Ftree%2Fdeploy%2Fdocker_prepull.sh&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824895869&sdata=OYzadsEaQR1ajiUwOaUkh5Ddapu06Nu9gfJgVDoQgaI%3D&reserved=0> https://git.onap.org/logging-analytics/tree/deploy/rancher/oom_rancher_setup.sh<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.onap.org%2Flogging-analytics%2Ftree%2Fdeploy%2Francher%2Foom_rancher_setup.sh&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824895869&sdata=4yJQL2lbURSkng%2FkxcPnqf96KP%2FkAOMGzbkGfKzs4lY%3D&reserved=0> https://git.onap.org/logging-analytics/tree/deploy/aws/oom_cluster_host_install.sh<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.onap.org%2Flogging-analytics%2Ftree%2Fdeploy%2Faws%2Foom_cluster_host_install.sh&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824905878&sdata=GAcgeo8TlZT7y5%2B5waU4UJFMHrefoeBB2TJyal0zNpE%3D&reserved=0> https://git.onap.org/logging-analytics/tree/deploy/azure/oom_deployment.sh<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.onap.org%2Flogging-analytics%2Ftree%2Fdeploy%2Fazure%2Foom_deployment.sh&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824905878&sdata=P4XHR0z8DveTgW4%2Bgq5ofLk5bHI8PDQmZIHWP3M0cfQ%3D&reserved=0> https://git.onap.org/logging-analytics/tree/deploy/heat/logging_openstack_13_16g.yaml<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.onap.org%2Flogging-analytics%2Ftree%2Fdeploy%2Fheat%2Flogging_openstack_13_16g.yaml&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824915883&sdata=G%2FQk%2FeefSyxtI%2FnKJwkp4GtV0UqnWJBXkyFGABgqXB8%3D&reserved=0> thank you /michael From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> On Behalf Of samirkumar_si...@infosys.com<mailto:samirkumar_si...@infosys.com> Sent: Wednesday, January 9, 2019 1:31 AM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] OOM issues after the Casablanca Release #oom Dear Good Folks, Looking for some help on below .. this has happened only after Casablanca :( am using the script cd.sh to deploy https://gerrit.onap.org/r/gitweb?p=logging-analytics.git;a=blob;f=deploy/cd.sh;h=616ba81af4fa7977f9d2a737d6faa8d9c5cc0f39;hb=HEAD<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgerrit.onap.org%2Fr%2Fgitweb%3Fp%3Dlogging-analytics.git%3Ba%3Dblob%3Bf%3Ddeploy%2Fcd.sh%3Bh%3D616ba81af4fa7977f9d2a737d6faa8d9c5cc0f39%3Bhb%3DHEAD&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824915883&sdata=MOAMzvOPHNgTq3yns7stOqbEObi8bh%2Bt6Q2y9eU0SIM%3D&reserved=0> Life is wonderful until i hit the line -175<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgerrit.onap.org%2Fr%2Fgitweb%3Fp%3Dlogging-analytics.git%3Ba%3Dblob%3Bf%3Ddeploy%2Fcd.sh%3Bh%3D616ba81af4fa7977f9d2a737d6faa8d9c5cc0f39%3Bhb%3DHEAD%23l175&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824925888&sdata=pkQ7pproatLnT5mX7vZIHa%2FNrkAG2zH0Y4WyIy12dz8%3D&reserved=0> echo "report on non-running containers" and then this Happens -- 1 chart(s) linted, no failures Successfully packaged chart and saved it to: /home/ubuntu/logging-analytics/deploy/oom/kubernetes/dist/packages/onap-3.0.0.tgz make[1]: Leaving directory '/home/ubuntu/logging-analytics/deploy/oom/kubernetes' deploying empty onap deployment as base 1 of 3 Error: unknown command "deploy" for "helm" Run 'helm --help' for usage. deploying base onap pods as base 2 of 3 Error: unknown command "deploy" for "helm" Run 'helm --help' for usage. sleep 600 sec to allow base platform pods to complete - without a grep on 0/1|0/2| non-Complete jobs deploying rest of onap pods as base 3 of 3 Error: unknown command "deploy" for "helm" Run 'helm --help' for usage. wait for all pods up for 15-80 min report on non-running containers No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. No resources found. pending containers=0 check filebeat 2/2 count for ELK stack logging consumption sleep 5 min - to allow rest frameworks to finish Any Ideas/ thoughts .. the only thing is also common is below Error: unknown command "deploy" for "helm" Run 'helm --help' for usage. However this was also fixed in the script by Author --@Michael O'Brien 101<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgerrit.onap.org%2Fr%2Fgitweb%3Fp%3Dlogging-analytics.git%3Ba%3Dblob%3Bf%3Ddeploy%2Fcd.sh%3Bh%3D616ba81af4fa7977f9d2a737d6faa8d9c5cc0f39%3Bhb%3DHEAD%23l101&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824925888&sdata=eOM1N09ZgvyfdglJRVPmh2OX%2FAuFWth5QXRX0lTFHTc%3D&reserved=0> git clone -b $BRANCH http://gerrit.onap.org/r/oom<https://apac01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgerrit.onap.org%2Fr%2Foom&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824935897&sdata=K7Jbt5tXFZeMOKD9jj4xgghdhTM%2F7utFtXCQf4%2BUJNs%3D&reserved=0> 102<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgerrit.onap.org%2Fr%2Fgitweb%3Fp%3Dlogging-analytics.git%3Ba%3Dblob%3Bf%3Ddeploy%2Fcd.sh%3Bh%3D616ba81af4fa7977f9d2a737d6faa8d9c5cc0f39%3Bhb%3DHEAD%23l102&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824935897&sdata=%2Bate93idmjEEPWMJ0iCIwXFtCtgEkiANd4q27tXzR3M%3D&reserved=0> # https://wiki.onap.org/display/DW/OOM+Helm+%28un%29Deploy+plugins<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.onap.org%2Fdisplay%2FDW%2FOOM%2BHelm%2B%2528un%2529Deploy%2Bplugins&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824945902&sdata=IZgTReAb6kHEVUieiEzbb8IOIp%2BSSBpkDXCqcYFr4rI%3D&reserved=0> 103<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgerrit.onap.org%2Fr%2Fgitweb%3Fp%3Dlogging-analytics.git%3Ba%3Dblob%3Bf%3Ddeploy%2Fcd.sh%3Bh%3D616ba81af4fa7977f9d2a737d6faa8d9c5cc0f39%3Bhb%3DHEAD%23l103&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824945902&sdata=k5pMNg54Lif91Qw%2BOfUOnTM0Shpt8YPg3MAbmYzolm8%3D&reserved=0> sudo cp -R ~/oom/kubernetes/helm/plugins/ ~/.helm This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.amdocs.com%2Fabout%2Femail-terms-of-service&data=02%7C01%7CSamirkumar_Singh%40infosys.com%7Cc45af0fb2bae493e406508d6765b0f57%7C63ce7d592f3e42cda8ccbe764cff5eb6%7C1%7C0%7C636826530824985935&sdata=56IlcnytjVn5GxGUpuNSdkcT3QZyVPAq4mZDuGt8Soo%3D&reserved=0> This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service <https://www.amdocs.com/about/email-terms-of-service> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14937): https://lists.onap.org/g/onap-discuss/message/14937 Mute This Topic: https://lists.onap.org/mt/28986503/21656 Mute #oom: https://lists.onap.org/mk?hashtag=oom&subid=2740164 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
