Although there is an integrated release of OpenStack twice a year, that release
is the aggregate of different projects and different code repositories that are
managed by different subsets of the overall developer community. And there are
new projects added all the time. I don't think it's a tec
Well, please don't mistake my question as a personal resistance to how
things are currently done. I am however curious if standardizing things
across the ecosystem is possible so the perceived message is consistent.
Versioning of the programs themselves is different since folks seem to be
picking u
Adam, that sounds you're talking about the API versions. So a user is consuming
eg Keystone v2, Nova v3, and Swift v1 (not to mention all the other projects).
Are you asking for a singular "OpenStack API"? Or maybe a common API version
number across projects (similar to how the requirements are
This makes perfect sense to me John. But consistency across the project
would be a nice-to-have for those who design and communicate the platform
to decision makers who don't understand why they're signing off v1 of this,
v2 of that, v1 of this other one... It portrays a sense of program
incongruit
> Hope this helps clear things up.
This does. Thanks for the detailed explanation.
-Shri
>
> --John
>
>
>
>
>
>
> On Jul 22, 2014, at 10:05 AM, Shrinand Javadekar
> wrote:
>
>> This is confusing. So does this mean semantic versioning applies to
>> the API's and not the Swift product versions?
Semantic versioning is bigger than just API changes. In fact, since we
separately version the API, we can actually be quite explicit about what's in a
particular release. In general, we do semantic versioning in Swift for a few
reasons, but the main one is that it's been requested and confirmed
This is confusing. So does this mean semantic versioning applies to
the API's and not the Swift product versions? If so how are the
product versions decided? And given a product version, how does one
know about what API version is in use? The /info endpoint does not
mention the API version.
I had
Hi Shri,
The Object Storage API change is just to add a header called
'X-Storage-Policy: ' where name is set in the swift configuration
files by the cloud provider.
See http://docs.openstack.org/developer/swift/overview_policies.html
We'll add it to the API docs next, no version change needed for
