-
Notifications
You must be signed in to change notification settings - Fork 10
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
Metro volume configure/end #131
Conversation
- refactoring MetroConfig and MetroSessionId type for compatibility with json decoder. - refactoring tests to match types. - fixing asser.Equal implementations to put correct variables in "expected" and "actual" arguments.
- updating configure-metro tests to end metro before deleting test vols.
- modifying tests to get new clients before testing in order to create a clean testing environments
- Suite setup will get all remote systems and iterate over them, trying to find one with Metro capabilities and in good connected state - Removed previous need for env GOPOWERSTORE_REMOTE_NAME
if err != nil { | ||
log.Printf("%s file not found.", envVarsFile) | ||
} | ||
client, err = gopowerstore.NewClient() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does NewClient use the session tokens if already logged into the array?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe, based on a quick review, the client will get a new token for each new client.
Description
Adding support for
volume
endpoint actions,configure_metro
andend_metro
to configure and end metro replication at a volume level.configure_metro
andend_metro
.ReplicationSession
struct to support the sessiontype
.RemoteSystem
struct to supportdata_connection_state
andcapabilities
.GitHub Issues
List the GitHub issues impacted by this PR:
Common PR Checklist:
Testing
Integration Tests
Main
compute_differences
test was failing due to reuse of API client between tests.This PR
Unit Tests
Main
Tests were failing due to a missed update to json field that was changed from
volume_group
tovolume_groups
.This PR