Replace Snet Config with Endpoint Config¶
The snet option forces the deployer to name the desired endpoint after the public endpoint.
The snet option forces the deployer to name the desired endpoint after the public endpoint. In order to switch between multiple internal networks, names have to be changed.
Instead of constructing a URL with a prefix from what is returned by auth, specify the full URL via configuration (e.g. https://www.example.com/v1/not_a_container). The location of an object is obtained by appending the container and object to the configured URL.
Only use auth v2. Store and retrieve multiple internal endpoints from the catalog. This is the preferred approach and requires migrating code that is using v1 to v2 which is a much larger and completely separate effort. Furthermore, a configurable endpoint could still be useful for overriding catalog.
Data model impact¶
REST API impact¶
Other end user impact¶
Other deployer impact¶
Configuration options will change:
Removed config option: “swift_enable_snet”. The default value of “swift_enable_snet” was False . The comments indicated not to change this default value unless you are Rackspace .
Added config option “swift_store_endpoint”. The default value of “swift_store_endpoint” is None, in which case the storage url from the auth response will be used. If set, the configured endpoint will be used. Example values: “swift_store_endpoint” = “https://www.example.com/v1/not_a_container”
- Primary assignee:
- Core reviewer(s):
- Other reviewer(s):
Modify code to use endpoint config
Remove snet prefix code
Verify auth works
Verify configured endpoint is reached
Document new endpoint configuration option.
Remove documentation for snet configuration option.