Cloud Pak for Data

 View Only

  • 1.  Trying to install icp4d to an existing icp enviroment

    Posted Wed May 15, 2019 03:15 PM

    Trying to install ICP4D to an existing ICP environment. But when I run the install it's looking for a cluster host https://mycluster.icp:8443/api/v1/config, but my cluster is host is https://app-rh-1.apptecinc.com:8443/api/v1/config. How do I tell the installer to use the existing host name?

    COMMAND LINE OUTPUT BELOW:

    Thank you for using IBM Cloud Private for Data

    Installer is preparing files for the initial setup, this will take several minutes........................Extracting package ibm-dde-0.13.4-x86_64.tar......Extracting package ibm-iisee-zen-1.0.0.tar.................................Please, inform the user and password for an admin account on the cluster. FAILED Get https://mycluster.icp:8443/api/v1/config: dial tcp 92.242.140.21:8443: connect: connection timed out

    FAILED The endpoint could not be accessed. Use cloudctl login command to set the api server endpoint. Authentication failed. Exiting... [root@app-rh-1 IBM]#



    ------------------------------
    John Longo
    ------------------------------

    #CloudPakforDataGroup


  • 2.  RE: Trying to install icp4d to an existing icp enviroment

    Posted Wed May 15, 2019 04:15 PM
    Edited by System Fri January 20, 2023 04:10 PM

    Hi John,

    It seems that your docker registry it not mycluster.icp . Do you know if this is correct url for docker registry ? what does `docker image ls ` gets you ? Once you know your docker registry,  see if you are able to login to it (docker login <registry url>) before restarting the installation.

    Thanks

    Sachin



    ------------------------------
    SACHIN PRASAD
    ------------------------------

    Original Message


  • 3.  RE: Trying to install icp4d to an existing icp enviroment

    Posted Thu May 16, 2019 03:55 AM
    That's how I setup the cluster

    Below is the console output when I log into docker, note the name under the docker info section

    app-rh-1.apptecinc.com. that's how I orginaly setup ICP

     

    root@app-rh-1 IBM]# cloudctl login -a https://app-rh-1.apptecinc.com:8443 --skip-ssl-validation

     

    Username> admin

     

    Password>

    Authenticating...

    OK

     

    Targeted account appicpclusterone Account (id-appicpclusterone-account)

     

    Select a namespace:

    1. cert-manager
    2. default
    3. ibmcom
    4. istio-system
    5. kube-public
    6. kube-system
    7. platform
    8. services
    9. zen

    Enter a number> 2

    Targeted namespace default

     

    Configuring kubectl ...

    Property "clusters.appicpclusterone" unset.

    Property "users.appicpclusterone-user" unset.

    Property "contexts.appicpclusterone-context" unset.

    Cluster "appicpclusterone" set.

    User "appicpclusterone-user" set.

    Context "appicpclusterone-context" created.

    Switched to context "appicpclusterone-context".

    OK

     

    Configuring helm: /root/.helm

    OK

    [root@app-rh-1 IBM]# docker login app-rh-1.apptecinc.com:8500

    Username (admin): admin

    Password:

    Login Succeeded

     

    [root@app-rh-1 IBM]# docker system info

    Containers: 185

    Running: 85

    Paused: 0

    Stopped: 100

    Images: 133

    Server Version: 18.03.1-ce

    Storage Driver: overlay2

    Backing Filesystem: xfs

    Supports d_type: true

    Native Overlay Diff: true

    Logging Driver: json-file

    Cgroup Driver: systemd

    Plugins:

    Volume: local

    Network: bridge host macvlan null overlay

    Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog

    Swarm: inactive

    Runtimes: runc

    Default Runtime: runc

    Init Binary: docker-init

    containerd version: 773c489c9c1b21a6d78b5c538cd395416ec50f88

    runc version: 4fc53a81fb7c994640722ac585fa9ca548971871

    init version: 949e6fa

    Security Options:

    seccomp

      Profile: default

    Kernel Version: 3.10.0-957.12.1.el7.x86_64

    Operating System: Red Hat Enterprise Linux

    OSType: linux

    Architecture: x86_64

    CPUs: 12

    Total Memory: 31.26GiB

    Name: app-rh-1.apptecinc.com

    ID: JJQB:EUF4:SI4X:VBFO:NXZB:WD77:SFLG:JPBY:RIKB:BTXW:YHPK:2RIW

    Docker Root Dir: /var/lib/docker

    Debug Mode (client): false

    Debug Mode (server): false

    Registry: https://index.docker.io/v1/

    Labels:

    Experimental: false

    Insecure Registries:

    127.0.0.0/8

    Live Restore Enabled: false



    ------------------------------
    John Longo
    ------------------------------

    Original Message


  • 4.  RE: Trying to install icp4d to an existing icp enviroment

    Posted Fri May 31, 2019 09:04 AM
    Hi John,

    just some words about my experiences with the package for installing into existing ICP. I tried this but then gave up, using the installation that comes with its own ICP instead. I found that the package got some hard wired settings at different places, which seem to correspond to the default IBM ICP installation that comes "with 4D" in the above mentioned complete installation. And sometimes the installation winds up with different installation path /ibm and /IBM.  Cannot imagine it's working in any customer ICP setup. 

    If you want to try further then you may try editing the unpacked installer script as follows:

    Line 21: ACCOUNT=$(find your appropriate account from:  cloudctl iam accounts)
    Line 27: MASTER_IP="$(set IP of your Master Node)"

    And set a symlink in root filesystem /ibm -> /IBM , you'll need it in a later step. Good luck!

    ------------------------------
    Best regards

    Bernd Künnen
    ------------------------------

    Original Message