On Tue, Jan 26, 2021 at 8:43 PM Bekir Fajkovic < bekir.fajkovic@citynetwork.eu> wrote:
Hi!
Thanks a lot for the kind answers and explanations, now the picture of the concept and the current development situation overall is much clearer to me.
Regarding the question about different types of Guest Agents acquired, depending on the database type, that i asked, it is mainly based on the information i read about in the latest edition of the book "*Openstack Trove Essentials*" by Alok Shrivastwa and Sunil Sarat that i purchased recently.
For example, as mentioned in the book:
*- Let's also look at the different types of guest agents that are required depending on the database engine that needs to be supported. The different guest agents (for example, the MySQL and PostgreSQL guest agents) may even have different capabilities depending on what is supported on the particular database.* (page 6) *- The Guest Agent code is different for every datastore that needs to be supported and the Guest Agent for that particular datastore is installed on the corresponding image of the datastore version. *(page 10) *- As we have already seen in the previous chapters, the guest agent is different for different database engines, and hence the correct version of the guest agent needs to be installed on the system. *(page 58)
Some of those have been changed and not the case any more. After database containerization, there is no database related stuff installed in the guest image. However, it's correct that different datastores are implemented as different drivers, so you can say "The Guest Agent code is different".
When it comes to guest image creation, i found now the places in the code that are used, as well as the acquired elements. A call to the function *build_guest_image() *is performed, involving those needed elements as minimal requirements:
- *ubuntu-minimal *(which also invokes *ubuntu-common* i think) - *cloud-init-datasources* - *pip-and-virtualenv* - *pip-cache* - *guest-agent* - ${guest_os}-*docker* - *root-passwd*
ref:
https://github.com/openstack/trove/blob/master/integration/scripts/functions...
So, when it comes to my question regarding the disabling of the automatic updates, it should be doable in a couple of ways. Either by executing a script placed in UserData during guest VM creation and initialisation or by manipulating elements (for example, such as we have a script placed in *ubuntu-common* element that disables privacy extensions for IPv6 (RFC4941):
/usr/local/lib/python3.6/dist-packages/diskimage_builder/elements/ubuntu-common/install.d/80-disable-rfc3041
You are right, but the recommended way is either those changes could be contributed back to the upstream if they are common feature requests and could benefit the others, or they are implemented in a separate element so there is little chance that conflict may happen when upgrading trove.
I am really looking forward to our soon deployment of the Trove project, i see huge potential there!
Good luck and please let me know if you have any other questions. --- Lingxian Kong Senior Cloud Engineer (Catalyst Cloud) Trove PTL (OpenStack) OpenStack Cloud Provider Co-Lead (Kubernetes) <http://www.catalystcloud.nz>