As per the current release tested runtime, we test
till python 3.11 so updating the same in python
classifier in setup.cfg
Change-Id: I462764b6ff8f8da0270daba82f2d6937070ba3c7
In Zed cycle, we have dropped the python 3.6/3.7[1] testing
and its support. Updating the python classifier also to reflect the same.
[1] https://governance.openstack.org/tc/reference/runtimes/zed.html
Change-Id: If7955df1073adadad2d306c3d9b74d1479cd334a
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I11660b10e55b3e6e0d7056d49a68f74eff61094c
Removes and/or replaces all mentions of py27.
Cleans up obsolete requirements and their lower-constraints.
Change-Id: Id43f1bbd6a454832ab8dbf003a058403f6b34b5d
2020 came, everyone should be using Python 3 now.
As per the official python support timeline set forth
by the OpenStack TC [1], OpenStack Train (in our case,
kolla 9.x) is the last release that will support python2.7.
[1] https://governance.openstack.org/tc/resolutions/20180529-python2-deprecation-timeline.html
Related bug: https://bugs.launchpad.net/tripleo/+bug/1856678
Merging depends on TripleO team - once they move CI job to CentOS 8 we
can merge.
Implements: blueprint drop-py2-support
Change-Id: Ic459561ab6ab8c62993c044c7a82d887839da289
contrib directory contains ovs-dpdk.j2 template override, but
exists only in git repository - not in the pip package contents.
Change-Id: Ic034331032810a2003a328b82492c6fd56ddd85f
Closes-Bug: #1808302
Fix warnings:
doc/image-building.rst:415:undefined label: deploy_a_registry
(if the link has no caption the label must precede a section header)
Change-Id: I8d921f3b05acf9304ccf41e172926887088b97d7
The gating on python 3.4 is restricted to <= Mitaka. This is due to
the change from Ubuntu Trusty to Xenial, where only python3.5 is
available. There is no need to continue to keep these settings.
Change-Id: I04cc81852392e659dca0002b33f037383fb814c3
* Remove duplicated info between the 'image-building' and 'multinode'
guides regarding deploying a local insecure registry.
* Add a helper script to easily start a local registry in a consistent
way.
* Remove warnings around bugs in older registries, 2.3+ is now the
default
* Remove references to running the local registry on port 4000, this
causes confusion as Docker expects port 5000 by default unless
specified, and registries are not required for all-in-one deployments
anyhow.
TrivialFix
Change-Id: I89f231df09102e3f1d5f21c8a8ca938ea60ae95b
The destroy playbook calls the cleanup-images script. All other
scripts related to destroy were in setup.cfg while cleanup-images
was missing.
TrivialFix
Change-Id: I3d5dc435d03aded9e8b415dda8435b5e1c5ec937
Now that there is a passing gate job, we can claim support for
Python 3.5 in the classifier. This patch also adds the convenience
py35 venv.
Change-Id: Ia7b1fb88ac108e1e8fd6ed963967e731ae3ca5a4
Closes-Bug: #1603006
For proper release note generation on the releases.openstack.org
website, this change will need to be backported into mitaka and
liberty as well. Then a special one-file reno file will have to
be added for mitaka describing the features and the same story
for liberty.
See log of the discussion here:
http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-release.2016-03-23.log.html#t2016-03-23T18:00:05
Change-Id: I3c298ae08ec4645f384ea5829cb0851fe82f4557
Partially-Implements: blueprint add-reno
As with all tools, this is a first pass at the generation. Perhaps we
even want to move this into kolla/kolla/cmd and be generated with tox
itself in the future.
This tool, when run, will only populate empty fields that have no
values meaning that it is safe to run repeatedly on the same file.
Of note, there is no way to preserve comments in the file after it has
been processed by the yaml parser in python. Comments and sections
will remain in the passwords.yml template for additional documentation
if the user wishes to populate the file themselves.
Use SystemRandom and clean up the docs a bit to not use pronouns.
Co-Authored-By: Steven Dake <stdake@cisco.com>
Closes-Bug: #1559266
Change-Id: I2932d592df8871f1b7811059206d0b4d0553a687
Master version was still set to 1.0.0. This became alot more obvious
in a recent patch when we started pulling that version number for the
tag...
TrivialFix
Change-Id: Ie9c95a4dc606d0527c44fcd624b4473e45f7f3cf
kolla-build requires setup.cfg to fetch its version and right now it's not
installed to pip data dir.
Change-Id: Id1df6aab72314710d436cd7584c89bcda5d2b1a0
Closes-Bug: 1525949
Our current version based upon conversations with TTX was
0.1.0. It appears now that the full API is nearly stable. It is
stable enough to call our first Liberty release 1.0.0.
The API consists of the following data:
The locations of config files passed to the container
The environment variables expected by the container
The JSON encoded file containing the copy and cmd operations
Each container in current master follows the same sytnax and
style for all of the implementations of every container that
atleast has been Ansibilized.
backport: liberty
Change-Id: I2064689ca6fd9f332ad26624e1b93f6aaa08e79b
Closes-Bug: #1503494
The source location definition previously in build.ini was merged in
etc/kolla/kolla-build.conf since it is really configuration for the
kolla-build tool.
Change-Id: I7531af0029bdfeabbaefb8a6aa97b70bb12c021a
Closes-Bug: #1496702
The pip installed kolla-build script was not able to build source images
due to missing build.ini file containing information where to download
sources.
Change-Id: Ibc347daff76b445f032d8366bea3a58549cda766
Closes-Bug: #1493728
The publishing docs expect the documentation to be present in the
/doc directory not the /docs directory. If the documentation is in
the /docs directory, according to fungi the docs won't be published
properly.
Change-Id: I718fec7e69d298a5cb2376ca4e2455e12169566e
Partially-Implements: blueprint kola-tox-doc
Updated build.py to reflect this change.
Deprecate --template option and make it a noop.
Change-Id: I7cd98d1ee684a4c64984a49597159868152683b2
Partially-Implements: blueprint remove-docker-dir
Install Ansible code, etc file examples, scripts, an open
rc example, a tool to initialize the OpenStack deployment,
and other various useful bits.
Start the versioning at 0.1.0 as recommended by ttx.
Change-Id: I35fa4042040957e7725c7fc3b146009e0135499a
Partially-Implements: blueprint python-package
Ghanshyam Mann