Cloud Pak for Data

 View Only
Expand all | Collapse all

AWS Quickstart

  • 1.  AWS Quickstart

    Posted Fri May 31, 2019 04:36 PM
    Hi, has anybody been able to get the AWS Quickstart working?

    We have also been trying that one and no luck.

    Guillaume

    ------------------------------
    Guillaume Labelle
    ------------------------------

    #CloudPakforDataGroup


  • 2.  RE: AWS Quickstart

    Posted Wed June 05, 2019 12:43 PM

    Hi. I was able to get the AWS QuickStart to work back when it first came out at the end of March. There were some issues with filling out the template correctly since the mandatory fields weren't indicated as such. Plus, the resources were not what the minimum requirements are stated as. Thirdly, the QuickStart license doesn't cover many of the add-ons, so that's a challenge. I wound up doing a complete manual install for a POC with a client on AWS.

    What issues are you running in to with it?

    Dale.



    ------------------------------
    Dale Mumper
    ------------------------------



  • 3.  RE: AWS Quickstart

    Posted Wed June 05, 2019 01:59 PM
    Hi and thanks for your response. 

    I finally got the Quickstart to work but not the AWS Manual install.

    This one keeps failing even with the wdp config file.

    I also tried with the Portal console and it just doesn't like my ELB setup on a 3 nodes cluster. 

    Looked at the log files and it did not like the fact that it could not ping an NLB.

    I am going to try the same settings that I used for the AWS quickstart with the manual install and go from there.

    Did you use the conf file or the configuration through the portal console?

    Guillaume

    ------------------------------
    Guillaume Labelle
    ------------------------------



  • 4.  RE: AWS Quickstart

    Posted Tue September 01, 2020 04:49 PM
    Hi

    I'm trying to install via QuickStart on aws with custom subnets and the install hangs right after the boot instance is created

    So far, this client doesn't have any instance configured in this account, thus there is no EIP, IG, EOIG nor endpoints, nat gateways, nothing and security forbid (?) creating something (well, unless is absolutely needed and with some security groups associated clearly..)

    It looks to me that an internet gateway is needed and a routing on o.o.o.o/o added to the main VPC (are all these created if started from absolutely scratch ?)

    It's obvious that there is no way to connect to the instance unless some configuration on routing is performed


    ------------------------------
    Iosif Tanasescu
    ------------------------------



  • 5.  RE: AWS Quickstart

    Posted Wed September 02, 2020 02:34 AM
    Edited by System Fri January 20, 2023 04:50 PM
    Hi, 
         Can you please describe custom subnets used. Also possibly share the parameter list and install logs ( should be available in bootnode/S3 bucket for logs).

    Quickstart will create VPC and all other components required. But if you are deploying using existing VPC, then you need to have VPC and subnets created.

    ------------------------------
    SHARATH KUMAR AITHAL
    ------------------------------



  • 6.  RE: AWS Quickstart

    Posted Thu September 03, 2020 09:55 AM
      |   view attached

    Hi

     

    Thank you for your quick answer

     

    I was able meanwhile to update my custom subnets with a custom template I've stored in github, as described below

     

    https://github.com/iositan/IBMCloudPakForData

     

    Please note that the template is based on your original template in github, while updating to our environment and stripping out the subnets with ACL

     

    I might mention that the document :

    ibm-cloud-pak-for-data-on-the-aws-cloud.pdf,

    doesn't mention anything about what existing subnets means for the installer, nor what resources must be created already if one intend to use existing subnets

     

     

    This time the process went further and rollback after encountering the following error

     

    Attached are all the logs the installation created so far

     

    P.S.

    I did add our contacts from IBM which might also give me a help with the install, as this is a project we are working on

    One more mention: the bucket referenced as parameter while starting the stack is created if not exist.

    This is another thing not mentioned in the quick start document mentioned above

     

    On my side I will try to figure out what is wrong and try to push further the install, but any help from your part will me more than welcome

     

    Thank You

     

    Iosif Tanasescu

    , Digital Strategy

    Immigration, Refugees and Citizenship Canada / Government of Canada
    Iosif.Tanasescu@cic.gc.ca / Tel: 613-437-8379

    , Stratégie numérique

    Immigration, Réfugiés et Citoyenneté Canada / Gouvernement du Canada
    Iosif.Tanasescu@cic.gc.ca / Tél.: 613-437-8379




    Attachment(s)

    zip
    Logs.zip   92 KB 1 version


  • 7.  RE: AWS Quickstart

    Posted Thu September 03, 2020 10:26 AM
    From Logs, I see that VPC and subnets are not in the same CIDR range and hence openshift install has failed. 
    Please check them and try recreating stack.
    subnet's CIDR range start 10.163.96.0 is outside of the specified machine networks



    ------------------------------
    SHARATH KUMAR AITHAL
    ------------------------------



  • 8.  RE: AWS Quickstart

    Posted Thu September 03, 2020 01:54 PM

    Hi

     

    Indeed I was missing the main CIDR parameter to provide-it accurately while running the stack

    The subnets were OK

     

    Once done, now I'm at the DNS configuration

    Is failing (as expected) as the domain (ircc-edwh.ca) is not registered

     

    The error message is

     

    What are valid options here ?

    - buy a temporary domain and give aws the dns management via route53

    - use our existing domain ? this is gc.ca and we have no authority on it

    - use something from ibm.com ?

    - use AWS Directory Service for Microsoft Active Directory (AWS Managed Microsoft AD) and use forwarders..

    - other..

     

    Thank You

     

    Iosif Tanasescu

    , Digital Strategy

    Immigration, Refugees and Citizenship Canada / Government of Canada
    Iosif.Tanasescu@cic.gc.ca / Tel: 613-437-8379

    , Stratégie numérique

    Immigration, Réfugiés et Citoyenneté Canada / Gouvernement du Canada
    Iosif.Tanasescu@cic.gc.ca / Tél.: 613-437-8379






  • 9.  RE: AWS Quickstart

    Posted Mon September 07, 2020 02:10 AM
    buy a temporary domain and give aws the dns management via route53

    This would be the best option. IBM does not share ibm.com, so that does not hold good. If you can create hosted zones with gc.ca, then that could be an option too.


    ------------------------------
    SHARATH KUMAR AITHAL
    ------------------------------



  • 10.  RE: AWS Quickstart

    Posted Wed July 24, 2019 12:12 AM
    AWS Quick Starts help you to deploy popular solutions on AWS. Each Quick Start is designed by AWS solutions architects or partners, and makes use of AWS best practices for security and high availability. You can use them to spin up test or production environments that you can use right away. 




    ------------------------------
    madhu Dm
    ------------------------------