{"push_id":911514996,"size":1,"distinct_size":1,"ref":"refs/heads/feature-vdc2","head":"d1c5b765c3683bc58061885d003697f6c95b3a9c","before":"d946d08df632ba47144932f1084509a77afcc70d","commits":[{"sha":"d1c5b765c3683bc58061885d003697f6c95b3a9c","author":{"email":"4eedfe746d5134b8c81efae46df85118867a70a0@emc.com","name":"Jason Cwik"},"message":"Added -SkipVdcProvision for non-primary VDCs\n\n * For the first VDC, step2 will initialize a replication group, insert the first VDC, create a namespace, and create a user.  For subequent VDCs, you do not want to do this.  Use -SkipVdcProvision and after the storage pool is created and DTs initialize, login to the GUI on that VDC, get the key, and then add it to the cluster through the primary VDC's GUI.\n * Also fixed a couple bugs for insertVdc.","distinct":true,"url":"https://api.github.com/repos/EMCECS/ECS-CommunityEdition/commits/d1c5b765c3683bc58061885d003697f6c95b3a9c"}]}