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

Stub out API tests for vCenter Reports #94

Closed
kdelee opened this issue Dec 7, 2017 · 1 comment
Closed

Stub out API tests for vCenter Reports #94

kdelee opened this issue Dec 7, 2017 · 1 comment
Assignees
Milestone

Comments

@kdelee
Copy link
Contributor

kdelee commented Dec 7, 2017

In the 1.0 release, we want quipucords server to be able to "make use of the technical facts gathered by the vCenter host manager".

"Making use of" should constitute, at a minimum, the following:

  • The following facts can be collected from supported versions of vCenter: {5.x, 6.x}:
    • cluster name
    • number of vmware hosts in cluster
    • virtual sockets
    • UUID (must be BIOS UUID for Ansible to capture it)
    • MAC address of interfaces (would only help with duplicates between sources not with duplicates within data source e.g. Rho could scan a single system multiple times if it has multiple interfaces and the MAC addresses would all be unique).
    • Hostname - very weak and appears differently in different data sources. would likely need to be a secondary or tertiary check
    • IP address - systems can have multiple IPs and could potentially have the same IP as another system (NAT environments)

In addition, we need to confirm the following:

  • Test that Sonar can make a connection to vCenter versions {5.x, 6.x}
  • Test that Sonar closes connection to vCenter versions {5.x, 6.x}
    • security issue, don't wan to leave open session
  • Validate that Sonar makes a secure connection if it is available (possibly not automated, but we may want this test stub in Polarion)
@kdelee kdelee added this to the Sonar 1.0 Test Stubs milestone Dec 7, 2017
@kdelee kdelee changed the title Stub out API tests for vCenter features Stub out API tests for vCenter Reports Jan 8, 2018
@kdelee kdelee modified the milestones: Sprint 13, Sprint 14 Jan 8, 2018
@kdelee
Copy link
Contributor Author

kdelee commented Jan 8, 2018

Moved to sprint 14 because no report is available yet for testing

kdelee added a commit that referenced this issue Jan 25, 2018
Outline test cases for reports. Reports are still very much in flux and
we need some more details about what facts will be present, with what
priority they are chosen between sources when different information is
merged, and what queries to the reports endpoint will be acceptable.
That being said, this is a good start and gets the test cases in a
format so we can view them from our read the docs website.

Closes #95
Closes #94
Closes #98
@kdelee kdelee self-assigned this Jan 25, 2018
kdelee added a commit that referenced this issue Jan 25, 2018
Outline test cases for reports. Reports are still very much in flux and
we need some more details about what facts will be present, with what
priority they are chosen between sources when different information is
merged, and what queries to the reports endpoint will be acceptable.
That being said, this is a good start and gets the test cases in a
format so we can view them from our read the docs website.

Closes #95
Closes #94
Closes #98
kdelee added a commit that referenced this issue Jan 26, 2018
Outline test cases for reports. Reports are still very much in flux and
we need some more details about what facts will be present, with what
priority they are chosen between sources when different information is
merged, and what queries to the reports endpoint will be acceptable.
That being said, this is a good start and gets the test cases in a
format so we can view them from our read the docs website.

Closes #95
Closes #94
Closes #98
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant