Fullsync for vsphere CSI Driver

[lipingxue]

What this PR does / why we need it:
The goal for FullSync is to fetch data from CNS and comparing it with the local PV/PVC information in Kubernetes cluster to identify what volumes need to be created/updated/deleted in CNS. FullSync is designed to handle the case when Metadata Syncer cannot push down the data to vSphere as expected. Those cases includes, CNS goes down, csi driver goes down etc.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:
Integration, unit and e2e tests for FullSync will be added in the following PRs.

Release note:

FullSync for vSphere CSI Driver

[k8s-ci-robot]

Welcome @lipingxue!

It looks like this is your first PR to kubernetes-sigs/vsphere-csi-driver 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/vsphere-csi-driver has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-ci-robot]

Hi @lipingxue. Thanks for your PR.

I'm waiting for a kubernetes-sigs or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dvonthenen]

@lipingxue looks like you need to sign the CLA
https://git.k8s.io/community/CLA.md#the-contributor-license-agreement

[codenrhoden]

Just one small bit of feedback so far. Will ok-to-test once the CLA is in place.

[lipingxue]

@lipingxue looks like you need to sign the CLA
https://git.k8s.io/community/CLA.md#the-contributor-license-agreement

I just signed CLA.

[codenrhoden]

we'll see if the CLA bot picks it up!

[codenrhoden]

@lipingxue Your commit is under your personal address. We'll want it to be under your VMware address.

$ git show HEAD
commit dc400f1ade414ddb8c08db842d4f854d80423cd3 (HEAD, test/fullsync)
Author: Liping Xue <lipingxue@gmail.com>
Date:   Fri Sep 6 14:11:44 2019 -0700

Once you set your config correctly, you can change your single commit with:

git commit --amend --reset-author

[lipingxue]

@codenrhoden It seems that CLA bot does not pick up my CLA. I signed the CLA using my personal email and the email account I used for my github account is my personal email. Does it matter?

[lipingxue]

@codenrhoden Ignore my previous update. cncf-cla is marded as "Yes" now.

[codenrhoden]

@codenrhoden It seems that CLA bot does not pick up my CLA. I signed the CLA using my personal email and the email account I used for my github account is my personal email. Does it matter?

I know you said "ignore", but just for posterity -- yes it matters. The commits need to be with your VMware address for several reasons. I see that they are updated now, so thank you!

/ok-to-test

[dvonthenen]

Other than the comments @codenrhoden made, this seems pretty good to me! Awesome!

[codenrhoden]

@lipingxue It looks like there are just a couple fixes to make re: goimports. The verify-fmt test failed because some of the imports not being listed alphabetically.

You can test this locally by running either make fmt or hack/check-format.sh.

[codenrhoden]

This looks good to me! Please squash your commits and this is good to go.

[divyenpatel]

/lgtm

[codenrhoden]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: codenrhoden, lipingxue

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [codenrhoden]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment