kops/cloudmock/openstack
Ole Markus With 9890839cec Add an integration test for openstack floating ip
* Integration test for floatingip cluster
* Implements mocking of floatingIP (only list for now)
* Expands various cloudmocks
* Fixes an NPR in openstack validation
* Fixes a bug where kops tries to use DNS even if the cluster is gossip
2020-08-12 12:59:30 +02:00
..
mockblockstorage Implement CRUD logic for cloudmock openstack 2020-08-10 15:22:49 -05:00
mockcompute Implement CRUD logic for cloudmock openstack 2020-08-10 15:22:49 -05:00
mockdns Implement CRUD logic for cloudmock openstack 2020-08-10 15:22:49 -05:00
mockloadbalancer Implement CRUD logic for cloudmock openstack 2020-08-10 15:22:49 -05:00
mocknetworking Add an integration test for openstack floating ip 2020-08-12 12:59:30 +02:00
BUILD.bazel Add an initial structure for openstack cloudmock 2020-08-05 23:13:34 -05:00
README.md Add an initial structure for openstack cloudmock 2020-08-05 23:13:34 -05:00
mock.go Add an initial structure for openstack cloudmock 2020-08-05 23:13:34 -05:00

README.md

Openstack Cloudmock

Design

Because the gophercloud library does not provide client interfaces whose client-side functions could be mocked like aws-sdk-go, this cloudmock uses a local HTTP server and updates state based on incoming requests from the gophercloud clients. This is how the gophercloud library tests themselves are implemented.

Each package represents one of the Openstack service clients and contains its own net/http/httptest server. Each package defines the endpoints for that client's resources.

Troubleshooting

One recommended way to troubleshoot requests and responses is with Wireshark or an equivalent, monitoring the loopback interface.