Uploaded image for project: 'Logging analytics'
  1. Logging analytics
  2. LOG-323

CD: Oneclick Amazon AWS Cloudformation template for Kubernetes VM install and OOM deployment

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Medium Medium
    • Beijing Release
    • None

      https://wiki.onap.org/display/DW/Cloud+Native+Deployment#CloudNativeDeployment-AWSEFSshareforsharedNFS
      20180502:
      cluster up, tiller pods up, EFS share up, kubectl up, but hanging on helm 2.8.2
      https://github.com/kubernetes/helm/issues/3133
      root@ip-10-0-0-19:~# helm version
      Client: &version.Version

      {SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}

      Error: cannot connect to Tiller
      root@ip-10-0-0-19:~# helm reset
      Error: forwarding ports: error upgrading connection: error dialing backend: dial tcp 18.222.4.161:10250: getsockopt: connection timed out

      my 10250 workaround likely
      root@ip-10-0-0-19:~# helm version
      Client: &version.Version

      {SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}

      Server: &version.Version

      {SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}

      my inbound 10249-10255 was the issue - still need to allow only for VPC traffic

      IE: appc across 3 AWS VMs
      http://jenkins.onap.info/job/oom-cd-master/2832/console
      onap dev-appc-0 0/2 Init:0/1 0 3m <none> ip-10-0-0-8.us-east-2.compute.internal
      onap dev-appc-1 0/2 Init:0/1 0 3m <none> ip-10-0-0-210.us-east-2.compute.internal
      onap dev-appc-2 0/2 Init:0/1 0 3m <none> ip-10-0-0-66.us-east-2.compute.internal

            michaelobrien michaelobrien
            michaelobrien michaelobrien
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: