MRPHS-3897: Rebasing/Upgrading libretto#61
MRPHS-3897: Rebasing/Upgrading libretto#61avnish30jn wants to merge 23 commits intoapporbit:masterfrom
Conversation
pankajtandon12
left a comment
There was a problem hiding this comment.
Please update the testing section of PR template.
Recommended Testing:
- InfraVM and vsphere-c3-cluster creation for various config types
- single/multi-vm
- DRS enabled/disabled
- DHCP/static-ip
- VM template/visor workflows
- AWS/GCP cloud-support basic testing
| go: | ||
| - 1.6 | ||
| - 1.7 | ||
| - 1.9 |
There was a problem hiding this comment.
Is go1.9+ mandatory or recommended?
i.e. Ensure no build failure in go 1.7 enviornment
There was a problem hiding this comment.
go1.9+ is recommended and build is not failing with go 1.7.
6740740 to
02c3767
Compare
Delete unused code found by unused linter. Fix gofmt issue. Add gofmt check to .travis.yml. Update URL for gosimple. Fix gosimple issue.
Replace use of deprecated oauth2.NoContext with context.Background().
Fix not closing fd and missing err check. Delete leaking ticker from aws/vm.go. Add staticcheck to .travis.yml. Fix missing error check on runVMware.
This fixes a bug caught by staticcheck.
Update path from rackspace/gophercloud to gophercloud/gophercloud. Update gophercloud/floatingip -> floatingips. Update Associate/Dissociate to AssociateInstance and DissassociateInstance. Update rackspace/gophercloud to gophercloud/gophercloud. Update govmomi/object/VirtualDeviceList.CreateDiskMethod to add datastore reference (API change). Set InsecureIgnoreHostKey callback on SSH client.
Clean up logs by moving some work to the before_script section. Test go tip, but allow it to fail. Add/rewrite some comments for clarity.
This fixes a race condition reported by the Go race detector on the close channel field. I think the original intention was to clean up resources, but it's not necessary to nil out channels to clean them. The garbage collector will take care of this for us.
Fix code samples not using gofmt. Fix syntax error in Azure code sample. Fix old reference to using govend --prune instead of dep prune.
Remove unnecessary constraints from Gopkg.toml (latest master commit isn't a real constraint).
This commit ensures that we log out of the vCenter session we create for each request. Previously, we were not logging out and potentially leaving an unbounded number of active sessons hanging around.
Travis runs are really slow. We can speed them up by not testing on the 386 (32-bit) architecture. The world has moved on from 32-bit processors and we shouldn't waste time testing on them.
This prevents us from having to drain the reader, loading it entirely into memory, just to get the file size of the file to be uploaded. The scp protocol requires that we know the file size ahead of time.
We use Azure resource group templates, which are analagous to CloudFormation templates in AWS. The template has two values, "true", and "false" that are strings instead of booleans. The Azure API ignores the invalid keys.
Previously errors returned by deploy() were ignored.
Update code for breaking changes to Azure/go-autorest, Azure/azure-sdk-for-go pyr/egoscale vmware/govmomi
02c3767 to
3bf12f9
Compare
|
Testing done for the below: InfraVM Tried vsphere-c3-cluster creation for various with create_vms and cluster_configure manually as two separate steps as controller does not support c3-vmware cluster creation now(with the old ui as well). |
pankajtandon12
left a comment
There was a problem hiding this comment.
LGTM.
Assuming this is auto-rebase from apcera/libretto without any code-conflict.
Please open a jira ticket to do "session logout" before cancelling it for all newly added instances, as recommended by updated libretto.
|
Created jira ticket MRPHS-4436 to track this. |
Problem
Some new fixes have been added to apcera libretto, which need to be merged with apporbit/libretto.
Solution
Rebased apcera/libretto with apporbit/libretto.
Unit-Testing
Deployed vm apps on starling vcenter with various configurations. The app was deployed successfully. Tried various operations on the app. The operations were completed successfully. Logs are attached below:
c3ntry1.txt
visor.txt