IC SunsetThe developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this community and its apps will no longer be available. More details available on our FAQ.
Topic
  • 2 replies
  • Latest Post - ‏2016-05-23T11:24:02Z by amanabe
amanabe
amanabe
68 Posts

Pinned topic TSA MP on AWS environment

‏2016-05-20T10:44:42Z |

Hello,

Is it possible to install TSA MP on the AWS (amazon web service) environment?
If it is OK, the network segment of the active node and the standby node on AWS will be different.

While this configuration is not described in the manual, how can be set for the Service IP is?

 

Best Regards.

Atsushi Manabe(amanabe@jp.ibm.com)

  • Enrico_Joedecke
    Enrico_Joedecke
    121 Posts

    Re: TSA MP on AWS environment

    ‏2016-05-23T08:57:35Z  

    Hello Manabe-san,

    the support (and test) matrix for TSA MP is found in the documentation - AWS is not included.

    Besides the operating system support, there are additional requirements to fulfill, e.g.:
    - StorageRM support depends on the attached disks / drivers
    - TieBreaker support - network and disk TB might not work

    If all those environment issues are solved, the different network segments you mentioned come up, which is out of control of TSA MP:
    -> from TSA MP's perspective, you can simply define an IBM.ServiceIP resource with different IP addresses for the individual nodes
    -> either the AWS, or the (client) application has to be able to 'find/connect to' the TSA MP nodes, that are potentially to host the application

        - AWS might provide some 'gateway', or separate logical network, or

        - your client application has to be able to find/connect to the nodes using different IP addresses

    Hope that answered your question.

    Regards,

    Enrico Joedecke

  • amanabe
    amanabe
    68 Posts

    Re: TSA MP on AWS environment

    ‏2016-05-23T11:24:02Z  

    Hello Manabe-san,

    the support (and test) matrix for TSA MP is found in the documentation - AWS is not included.

    Besides the operating system support, there are additional requirements to fulfill, e.g.:
    - StorageRM support depends on the attached disks / drivers
    - TieBreaker support - network and disk TB might not work

    If all those environment issues are solved, the different network segments you mentioned come up, which is out of control of TSA MP:
    -> from TSA MP's perspective, you can simply define an IBM.ServiceIP resource with different IP addresses for the individual nodes
    -> either the AWS, or the (client) application has to be able to 'find/connect to' the TSA MP nodes, that are potentially to host the application

        - AWS might provide some 'gateway', or separate logical network, or

        - your client application has to be able to find/connect to the nodes using different IP addresses

    Hope that answered your question.

    Regards,

    Enrico Joedecke

    Enrico-san,

    Thank you for your answer.

     

    I agree that AWS is not formally supported.

    By the way, Do you have something limit for SoftLayer (with IA Linux), which have increased in recent days?

    Atsushi Manabe(amanabe@jp.ibm.com)