kops/cloudmock/openstack
Pierre Prinetti 1005dda58e
Upgrade to Gophercloud v2
Essentially:

* Add a context argument to Gophercloud functions
* Refactor scheduler hints for server creation
2024-10-23 12:33:34 +02:00
..
mockblockstorage Upgrade to Gophercloud v2 2024-10-23 12:33:34 +02:00
mockcompute Upgrade to Gophercloud v2 2024-10-23 12:33:34 +02:00
mockdns Upgrade to Gophercloud v2 2024-10-23 12:33:34 +02:00
mockimage Upgrade to Gophercloud v2 2024-10-23 12:33:34 +02:00
mockloadbalancer Upgrade to Gophercloud v2 2024-10-23 12:33:34 +02:00
mocknetworking Upgrade to Gophercloud v2 2024-10-23 12:33:34 +02:00
README.md Add an initial structure for openstack cloudmock 2020-08-05 23:13:34 -05:00
mock.go Upgrade to Gophercloud v2 2024-10-23 12:33:34 +02: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.