[MCOL-1846] AMI support for Instances with ENA drivers Created: 2018-11-01  Updated: 2018-11-14  Resolved: 2018-11-14

Status: Closed
Project: MariaDB ColumnStore
Component/s: installation
Affects Version/s: 1.1.6
Fix Version/s: 1.2.1

Type: Task Priority: Major
Reporter: David Thompson (Inactive) Assignee: David Hill (Inactive)
Resolution: Fixed Votes: 0
Labels: beta


 Description   

Because we use centos 7 as a base os for the AMI, we currently can't support newer instances types that use the ENA network drivers. We should add support for this, with centos7 we need to do some custom steps to add the drivers in (suspect we are better doing this rather than switching to amazon linux or ubuntu):
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking-ena.html



 Comments   
Comment by David Hill (Inactive) [ 2018-11-01 ]

Tested in our current AMI by added package with the "sudo yum update"
Then created a new AMI to start with. But the new AMI, just like the current base version doesn't allow selecting instance types like c4, c5, r5, z1. Some of these are recommended for use with ENA.
So our current based Instance is limited.

I did find other based Centos 7 that has Elastic Network Adapter (ENA) already enabled and it does support all types of Instances.

So for 1.2.1 AMI CentOS 7, we should start with this as a base instance which contains ENA. I tested one and the interface does startup as configured a ENA. And it will support the other instance types that our based on doesnt. c4, c5, r5, z1.

So for CentOS based AMI, this is the way I think we need to go... I can create a new AMI with this instance setup, do an instance and retest all the functionality and regression test of MCS to make sure it works..

We have had 1 user asked why we dont support the other instance types, so this will address that issue also...

Also I would stay with centos based since previous version was centos base. But if a user request a ubuntu base AMI, we could do that separately.

Comment by David Hill (Inactive) [ 2018-11-02 ]

regression test run was successful on the new ENA AMI..
Will do some multi-node installs and testing next

Comment by David Hill (Inactive) [ 2018-11-05 ]

1. will require 1 code change related to the MCSInstance.sh script, which makes calls to the aws-cli api interface.

2. here is the command to run to see that the interface is configured for ENA

  1. ethtool -i eth0
    driver: ena
Comment by David Hill (Inactive) [ 2018-11-06 ]

please review - 1 line changed on how to get the region of the instance

https://github.com/mariadb-corporation/mariadb-columnstore-engine/pull/613

Comment by David Hill (Inactive) [ 2018-11-06 ]

how to test, once the 1.2.1 AMI is created

1. launch AMI as pm1
2. log into pm1 instance
3. run the following command and see if set to 'ena'
ethtool -i eth0
4. run postConfigure and setup a 1um and 2 pm system using the AMI CLI to launch the instances

Comment by David Hill (Inactive) [ 2018-11-14 ]

Also a change of note for the 1.2.1 AMI, the working user account has been changed from 'mariadb-user' to 'mysql' user

So now log into the AMI with mysql as the user

Generated at Thu Feb 08 02:31:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.