-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compute v2: Create aggregate #739
Conversation
Build failed.
|
recheck |
Build succeeded.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dstdfx Thank you for working on this :)
Two small changes.
Also, the UnmarshalJSON
stuff should be a separate PR. I'm OK with including it here, but in the future, please only one major change per PR.
|
||
type CreateOpts struct { | ||
// The name of the host aggregate. | ||
Name string `json:"name"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
name
is a required field, so this should be:
Name string `json:"name" required:"true"`
@@ -1,7 +1,21 @@ | |||
/* | |||
Package aggregates returns information about the host aggregates in the | |||
Package aggregates creates aggregates and returns information about the host aggregates in the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might as well rename this to:
Package aggregates manages information about the host aggregates in the
OpenStack cloud
@jtopjian Okay, will keep it in mind. |
Build succeeded.
|
@dstdfx Looks good to me. Thank you for working on this. :) |
…gophercloud#739) * vendor: adding customdiff support * Networking v2: Deprecate subnet allocation_pools for allocation_pool This commit deprecates the openstack_networking_subnet_v2 allocation_pools argument in favor of allocation_pool. allocation_pool is a singular word which makes more sense to use declaratively. In addition, allocation_pools was originally a TypeList, but the OpenStack API will not respect the ordering defined by the user for multiple pools, which triggered unneeded diffs. allocation_pool is now a TypeSet which accounts for an unordered response. * Networking v2: Check allocation_pool first during subnet creation * Networking v2: Refactor same allocation pool detection * Networking v2: Add ConflictsWith for allocation_pool(s)
For #738
Links to the line numbers/files in the OpenStack source code that support the
code in this PR:
API doc:
Source code: