Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

initial checks for VMware vSphere (jsc#TRNT-1682) #259

Merged
merged 28 commits into from
Jul 6, 2023

Conversation

yeoldegrove
Copy link
Contributor

@yeoldegrove yeoldegrove commented Jun 27, 2023

initial checks for VMware vSphere (jsc#TRNT-1682)

(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
(jsc#TRNT-1682)
Copy link
Member

@nelsonkopliku nelsonkopliku left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @yeoldegrove!

@nelsonkopliku nelsonkopliku added the documentation Improvements or additions to documentation label Jul 4, 2023
@coveralls
Copy link
Collaborator

Coverage Status

coverage: 96.122%. remained the same when pulling 54d3aa3 on yeoldegrove:jsc#TRNT-1682 into 81a62c7 on trento-project:main.

Copy link
Contributor

@arbulu89 arbulu89 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @yeoldegrove ,
Glad to see you back 💪
Just a question. I just see documentation changes without any change in the values.
Does this mean that the default values are the correct ones?
In the other hand, we never used the vSphere term at least internally. Is this the correct term? Asking to @abravosuse as well

PD: You didn't need to add each change in one commit hehe one commit would be good enough

@yeoldegrove
Copy link
Contributor Author

@arbulu89 I doubled checked the term VMware vSphere with @gereonvey ... If someone comes up with another term, we can change it, sure. I found it e.g. here: https://wiki.scn.sap.com/wiki/display/VIRTUALIZATION/SAP+HANA+on+VMware+vSphere

There is no publicly available documentation from VMware nor SUSE for the HA side of things on SAP systems. So we went for the default values for now.

@gereonvey
Copy link
Member

VMware vSphere is the correct/official product name (https://www.vmware.com/products/vsphere.html) for the platform that SAP systems would be running on, so we should use that.

@abravosuse
Copy link

@arbulu89 when you talk about SAP on VMware vSphere you normally just say "VMware". So we stick to that name.

@yeoldegrove
Copy link
Contributor Author

@gereonvey @abravosuse So shall I name it VMware or VMware vSphere as (referenced by SAP and VMware)?

@abravosuse
Copy link

VMware is good for me. And I believe that other vendors/providers/platforms are all spelt out in lowercase.

@yeoldegrove
Copy link
Contributor Author

@abravosuse env.provider is spelled in lowercase. The other vendors in the remediation section have very different spelling like Azure, Nutanix, SUSE / KVM, so VMware would look good there in my opinion.
I added 5312e01 which changes this in this way.

@arbulu89
Copy link
Contributor

arbulu89 commented Jul 5, 2023

@yeoldegrove All good from my side. Just thumbs up here if it is ready to be merged!

@arbulu89 arbulu89 merged commit ddd9838 into trento-project:main Jul 6, 2023
@arbulu89 arbulu89 added the enhancement New feature or request label Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
check documentation Improvements or additions to documentation enhancement New feature or request
Development

Successfully merging this pull request may close these issues.

6 participants