We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: I51f1d5da9248b139a59bd9fe59b284b368b61021
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Ic29b2d2b249353609779e27b8601152d98803716
Story: #2002586
Task: #24757
Describe an effort to extend existing clouds.yaml support to all
existing command line clients as well as support to horizon for
providing a downloadable config file snippet.
Change-Id: Ibc3f2e63deb8dbb1b96aec4000f8bbfef16bc7b0
The OpenStack Client has been the suggested way forward for CLI
applications now for a few cycles however we remain in a limbo where in
some cases we suggest using OpenStack Client and in others we suggest
the project CLI.
Ratify that the OpenStack client is the recommended CLI for OpenStack
projects so that there is a clear direction on this.
Change-Id: Icf517986bfc318eb621210383f81366779da5840
Distributed locks, the concept, the problem space, what
has been done, what could be done, what will be done,
what must be done, the journey begins now (weekdays at
7pm EST).
Updating due to summit session result, some more small
work and/or tweaks still needed.
Change-Id: Ibce47659c1108b94b4d538c63da69ce0371aed04
In this spec we are proposing to return 'request_id' along with various return
types such as list, dict, resource object etc. from python-clients to return
request id to the user.
blueprint: expose-get-x-openstack-request-id
Change-Id: Ia2e6789f24d0a7024b40230eb6fc866937a61b1f
These literal blocks show log snippets weren't being formatted
correctly due to a missing newline between the :: and the literal
block
This change just adds some whitespace to make the formatting come out
as intended; there's no change to the content of the guidelines.
Change-Id: Ic2f5fa9dcf281adbc95ce980b5409e993fead94e
Our current requirements management policy is causing signficant gate
downtime, developer issues and packaging headaches. We can do better.
Using pins rather than open ranges for testing avoids firedrills. Most
of the work involved is a consequence of that key change.
Change-Id: I1a53b418568b8304ad74a2b30bdf1bb86ccb5f7a
Changes requested in discussion on the original CORS specification, however
deferred in favor of landing that specification. Commentary here:
https://review.openstack.org/#/c/179866/5/specs/cors-support.rst
Change-Id: I9e8be30834e7020320a1cd37c8f18e59da4b360b
This specification details implementing the W3C's Cross Origin
Resource Sharing specification in openstack's API's. It is intended
to provide additional options to user interface projects, by
permitting the API's to selectively break the single-origin policy
for configurable domains. It makes use of a single, common
middleware implementation already available in oslo_middleware.
Change-Id: I2135043f49f64b096b6bd295966d2e73697c7764
To fail in case of any warnings or errors during the
doc build process the warnerrors pbr option has to be
set to true in the setup.cfg file.
Change-Id: I04c82cd4cc9a9ecced37da7acc0d4f602bc7d863
Attempt to document best practices for using eventlet, so things
learned by one project can be more easily applied to others.
Change-Id: I1d03f5a86970b59705ff7160db3e51a92d8776e6
This was added to work around bug 1091333. A new sphinx has been
released and so this is no longer necessary.
Change-Id: I6ea61a3cc441dd1ca2ced7e2fd837a55b917f76d
This proposes the cross-project spec to eliminate SQL Schema Downgrades
in OpenStack. This is based upon the conversations had on both the
dev and operator mailing lists. In short, SQL Schema Downgrades do not
have a clear use-case where a restore to known-good point would not both
be more appropriate and desired (due to data inconsistency, integrity,
etc).
Change-Id: I622f89fe63327d44f9b229d3bd9e76e15acbaa7a
We should consider actually using the TRACE keyword for logging as
something meaningful. Today TRACE is used as a prefix for stack traces
even though it has no logging level definition.
This would provide a deep debug level which many developers have
requested. TRACE is a standard level in other logging systems such as:
https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html
and means what we are proposing here.
This means that 3rd party tools are highly likely to understand this
meaning for TRACE (and actually be terribly confused by the current
OpenStack use of TRACE).
Co-Authored-By: Alexis Lee <alexisl@hp.com>
Change-Id: Iba69bb07e4c6fd5232efa20b984042a30c85e58b
This goal of this specification is to define the syntax for client
sorting arguments so that there is consistency across projects.
Note that an API working group guideline for sorting is closely
related:
https://review.openstack.org/#/c/145579/
Change-Id: Id99091cfcf0c8770babba5e6cbf9c9772b015960
Proposed final draft.
This attempts to integrate much of the existing feedback, including
clarity around the points that were confusing people regarding the
"unit of work" and when stacktraces are appropriate.
In addition the Security logging section was dropped, because
realistically it was a poor fit for this original document. The wiki
page on it remains. My expectation is that security for logging should
be proposed as a follow on patch by someone that wants to make that
info fit well with this document.
All the open questions are now removed. Hopefully this ends up very
close to an agreed point.
Note: This evolved originally in the nova-specs repo at:
I674966988ed501dee323a106b84b5b6602d846b1 but is now moved over to
cross project specs repo. Some deep history can be seen at the
original draft.
Part of bp:log-guidelines
Change-Id: I3a8d0ac570e05eb11ccc70ad4eb9da277aaac256
Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.
Change-Id: I3458bc41aa1d4f2425e2a0603d00560173921402
Set up sphinx to convert the specs to HTML and create an empty specs
directory to hold proposed specifications.
Change-Id: Ic49cfd646fd6782bc0e539de6390217767d3c4ff