search

gardener / gardener-extension-provider-azure

Gardener extension controller for the Azure cloud provider (https://azure.microsoft.com).
https://gardener.cloud
Apache License 2.0
10 stars 78 forks source link

Integrate vSMP MemeoryOne in Azure #788

Open sameach23 opened 7 months ago

sameach23 commented 7 months ago

How to categorize this issue?

/area usability /area os /kind enhancement

What would you like to be added: Gardener already supports multi-volume connection for machines used by MemeoryONE in AWS , to boot OS and MemeoryOne software on the same worker-node on separate dataVolumes. The same functionality needed in Azure for MemoryONE worker-nodes.

I would post here a link to an epic for the similar functionality requested in AWS in the past. https://github.com/gardener/gardener/issues/2354

Why is this needed:

YakovKugel commented 3 months ago

Dear Gardener Team, The absence of a multi-volume connection in Azure had led to 130 minutes of downtime for EU20, EU21 , Canary-AZ customers in total. This was triggered by the requirement to perform an extra reboot on the VM installed with MemoryONE to avoid a 50% decrease in machine memory size triggered by standard Azure's host OS update. This issue arose due to the availability of just one data volume for the VM in Azure. We kindly request you to elevate the priority level of this task to very high. https://jira.tools.sap/browse/HC01-210550

gardener-robot commented 3 months ago

@YakovKugel You have mentioned internal references in the public. Please check.

YakovKugel commented 3 months ago

What is the ETA of that feature in Gardener Live ?

kon-angelo commented 3 months ago

Hello @YakovKugel. We haven't started with the Azure implementation hence I can't really give a good ETA for this

YakovKugel commented 1 month ago

@kon-angelo Hello Konstantinos, We would like to begin our testing in Azure, and it appears that the feature is not merged yet. Is there any estimation when Gardener would merge this feature?

kon-angelo commented 1 month ago

@YakovKugel we wait for feedback by MCM colleagues in the referenced PR.