| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As it was announced [1] global bindep-fallback.txt was removed and now
projects need to have a local bindep.txt to be able to install binary
dependencies for testing.
In test jobs the script tools/test-setup.sh is called which requires
mysql and postgres servers and clients to be installed.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007272.html
Change-Id: I76df1464d7bd7af76afa619766c1721afc1d169e
(cherry picked from commit 239f9c6e4fa7d7bb9bab396f79336725a149126c)
(cherry picked from commit bac67e878479c8edb34a952c850eb8b78d0f8e0c)
(cherry picked from commit 08027d0ff997c02cb8ee4cd2ececd43b2712857e)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Ibfd3689c52e87d7218bd1c8ba9966641235aba92
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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: Ie4708672fced79cf18407c683c0119a56c4264a8
Story: #2002586
Task: #24342
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a point that is easily hidden. In the case of not open
port 16379, redis cluster can still be deployed successfully,
but this success is a false success, there is no data communication
between the various nodes. This is because 16379 is the port for
data port[1]. We set the default value in cfg, but in the
case of conf,it is easy to be covered. Adding 16379 to conf.sample
helps the user to reduce some problem caused by the redis
configuration.
[1]:https://redis.io/topics/cluster-tutorial
Change-Id: If517072c1c875df68106af14dac1802bb959d17e
(cherry picked from commit dbeff81d5049131f0b9b129ae7c42fcec2ff746d)
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NOTE(mriedem/smatzek): This is a squash of two commits.
The first commit message is:
Jobs run as jenkins on Zuul v2 but run as user zuul on Zuul v3.
NOTE(mriedem): This is only taking one specific fix from the large
change on master (queens) since we don't need the other changes
for stable/pike to fix the gate.
(cherry picked from commit 9ec134996a1162de0d74ef915dc138bbacbcfdf1)
This is the 2nd commit message:
Increase the TROVE_AGENT_CALL_HIGH_TIMEOUT to
help the upgrade test pass. The upgrade test has an agent call
that takes longer than the current timeout when running in
the gate on Nova compute with virt_type set as qemu.
NOTE(smatzek): This is only taking one fix from this change as
the other is N/A in this case as it was enabling the disabled
integration tests.
(cherry picked from commit d7b773d2b07f0c95909ef73c4644a63f09fd82c3)
Change-Id: Ic55187b0d73d4c572d7f8332882b4f455a6177c8
(cherry picked from commit e6d4b4b3fe1768348c9df815940b97cecb5e7ee2)
|
| |
|
|
| |
Change-Id: I69f355b24cee311adddac43e00421982e69b5923
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In a recent patch some imports were added to the top of
cmd files, before the call to load the configuration
was issued. This caused anything initilized before the
configuration to fallback on default values.
Because of this, for example PROXY_AUTH_URL found in
trove/common/remote.py would always be set to the
default value: "http://0.0.0.0:5000/v2.0".
> PROXY_AUTH_URL = CONF.trove_auth_url
This patch changes the config values in the
trove/common/*remote.py files to be lazy loaded.
Co-Authored-By: Riccardo Pittau <rpittau@blizzard.com>
Change-Id: Ie3893680c406d92fe2b20e892c29fce675d7f224
Closes-Bug: #1671655
(cherry picked from commit db320b80a568f25f59da233853c530e647a0c496)
|
| |\ \ |
|
| | |/
| |
| |
| | |
Change-Id: I018e4db6411cca10732472a36fa12aaf9e5a7bae
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
dib is now going to have to be installed explicitly for us to actually
run the gate. the old method of just cloning the repo won't work with
dib v2.
There are other ways to accomplish this but I'm choosing this approach
knowing that it isn't ideal. First, what's the downside? This means
that dib gets installed wherever trove control plane is installed. Is
that necessary, NO. Is it the end of the world, NO.
What are the options?
- do what Octavia did and have a second requirements.txt in a folder
called diskimage-create. Would this work, yes but we don't have such
a mechanism right now and nothing would keep this requirements.txt
file in sync with g-r that I know of.
- hardcode the pip install command somewhere in the devstack
plugin. yes, this would work but this would also have no ability to
sync with g-r.
So, while the solution proposed here isn't ideal, it strikes me as not
bad, and much less risk than the other two options.
We also need to figure out where the elements are and fix the path for
disk-image-create.
Some pep8 failures appears to have crept in as well, those are
addressed.
Change-Id: Ic64d91e082102057417995a0f6851d03b9e0ca74
|
| |\ |
|
| | |
| |
| |
| | |
Change-Id: I10b8dfe4c7c3b90035b2785d1142d79e585a7a17
|
| |\ \
| |/ |
|
| | |
| |
| |
| | |
Change-Id: Ie9b82df8af61a8b5cd36bad86abbb89551f7ddc8
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When trove-integration was a thing, and was branchless, and not part
of the trove repository, we needed this kludge to get the guest
requirements. Now that trove-integration is no longer a thing, and the
image build is branched and part of the trove repository, we don't
need to keep requirements files which are version stamped.
The elements now just pick up either fedora-requirements.txt or
ubuntu-requirements.txt
This change will merge in master and get backported into stable/ocata.
Change-Id: I87b887befb2d12f607ffec919c79d462fbde42ca
(cherry picked from commit 5529c368e4788ab9a224970bae9076c015a3da12)
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add simple script to setup mysql and postgresql databases, this script
can be run by users during testing and will be run by CI systems for
specific setup before running unit tests.
This allows to change in project-config the python-db jobs to
python-jobs since python-jobs will call this script initially.
Update CONTRIBUTING for this.
See also
http://lists.openstack.org/pipermail/openstack-dev/2016-November/107784.html
Change-Id: I3463e75057d0d4544f6a0212da888759ab5e171b
Needed-By: I92e6e6502c2c516babf2bf66f3514875f77c460e
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The current implementation of poll_until will attempt the retriever
every second and given that the call itself may take some time, this
effectively ends up being a non-existant sleep. On the under-powered
CI systems, this has an unwanted bad effect with polls running
continuously.
Changing poll_until to use the BackOffLoopingCall instead.
Change-Id: I9487d753e65c4de7753d9db19626497217c71f63
Depends-On: Id5be526a0418db5d00cbf5cbceb4993274989e72
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Implement configuration attach and detach API for clusters.
Implement rolling strategy for applying configuration changes
(both attach and detach follow the same pattern).
1. Persist the changes on all nodes (leaving nodes in RESTART_REQUIRED state).
2. Update Trove records.
3. Apply changes dynamically via one or all node(s) if possible
(and remove RESTART_REQUIRED flag from all nodes).
Notes:
The single instance implementation has been restructured (similar to above)
such that it always leaves the instance in one of the three states:
a) Unchanged
b) Changes persisted but not applied
(Instance has configuration attached but requires restart.
It is safe restart manually or detach the group to avoid
any changes)
c) Changes persisted and applied (if possible)
This implemenation should always leave the cluster (and each instance)
in a consistent state.
Runtime configuration will not be changed until it is first persisted
on all nodes.
If there is a failure during step 1) the cluster is still running
the old configuration. Some instances may have new configuration
persisted, but not applied.
The cluster will not have configuration attached unless it can
be applied to all nodes.
The individual nodes will have configuration attached as soon as it is
persisted on the guest.
It is safe to retry, reapplying the same configuration on a node is
noop.
It is safe to detach. Removing configuration from nodes without one
is a noop.
It is safe to detach the configuration from individual nodes via
single-instance API.
It is safe to attach the configuration to remaining nodes via
single-instance API and rerun cluster attach to update Trove records.
If 3) fails for whatewer reason the instances are left
in RESTART_REQUIRED state.
It is safe to retry or detach configuration or restart the
instances manually.
Also fixed various minor cluster issues.
Implements: blueprint cluster-configuration-groups
Change-Id: I7c0a22c6a0287128d0c37e100589c78173fd9c1a
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Earlier code introduced in[1] aimed to handle the situation where a
context object serialized and sent over a message queue as a
dictionary is received by a version of code that doesn't necessarily
understand that context object.
That code relied on the fact that vars(TroveContext).keys() was a
dictionary that matched the full set of parameters that you can send
to the initializers for TroveContext() and RequestContext().
Recent changes in oslo.context [2] and [3] broke that
assumption. vars() on TroveContext provided a dictionary with the
internal representation(s) that are not the same as the kwargs in
RequestContext() and the params that TroveContext used to pop.
To get around this, new code introduced here uses
oslo_utils.reflection to determine all the possible kwargs that can be
sent to TroveContext, some of which are consumed by TroveContext and
the rest of which are sent along to RequestContext().
The construct in the earlier _remove_incompatible_context_args() also
modified kwargs.keys() by pop'ing values from it while iterating over
this. Python 3 takes a dim view of this and therefore some changes
have been made to accomodate this.
A unittest has been added to ensure that the from_dict() method
properly dumps stuff it doesn't know about. The test explicitly
verifies the warning generated when a bogus argument is eliminated.
[1] 24c5e8e244380e3e7e309f0b4aaffde32dbf0789
[2] 2394cff0631944a9259bfe04925e444d9f817758
[3] f25543fcc792ebf155728a91fde06e8dc4e96cea
Change-Id: I477dd29e034295e770925091c4ac6268c22ae59b
Related-Bug:#1661790
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is the first patch to enable the translation checks.
These translation checks were taken from neutron_lib/hacking
Translation checks include:
* validate_log_translation: Translate log messages
* no_translate_debug_logs: Don't transate debug level logs
* check_raised_localization_exception: Translate exception message
The pep8 tests will fail until all files meet the standards enforced
by these translaiton checks. So this patch is depenedent on the
following:
Depends-On: Ieb7e006de497c974756941608aea91f63e860dc5
Depends-On: I1d0649f240365b7f62b13af6edb1e8dbb5d06597
Depends-On: I48f95b3c090e9b6f91185c14113daae5bc621d0b
Depends-On: I5feafe8945960e34a8d0e038ad4617f39502f19b
Depends-On: If29f7b5df7f6958cec4b26f72babc47ca70f3706
Depends-On: Iddd738c2d9a7c9a57fcd445650d087123dbccfc4
Depends-On: Ifdf426684473fb05cae63877c334e6cf65aa5234
Depends-On: I94a341ba1fb4178e0c358c37ea31623d48938ec6
Depends-On: Ic8664bf105d601909c6efa5cf73db6c27adaf42e
Depends-On: I80f2ea6a20944cfbfdc79a8a71ad744f23aeaac1
Depends-On: If68b38ef5bdeba2fdc28f94d964ef8ce6d15c352
Depends-On: Ia54014fa8e44aacc7935bd73c1ee8d3139a19735
Depends-On: Iea58f4df337c79785dc7afe0e31bcfa7e231f374
Depends-On: I2b0313021fd9599bdaeb375358e8cf834581d493
Depends-On: I56972d16634654b8b71853d6aba10299cc9e2418
Depends-On: If632727fd29ec8d36c6890ebd156a46be70ba783
Depends-On: I1df8d4cba6a3a2ec23e8a1b2aa4ffc03c97b149e
Depends-On: I4070117b6335f4d85f35cc6473653c17d7c14bac
Depends-On: I83f2ccd623588af3fc5f94334b753cebcc3b6c18
Depends-On: I44ac13e9431018e18980e8ff7ff442c7fea68a13
Depends-On: I88284f61b5f37d78ad050a97c679f6bde23d832d
Depends-On: I6fb2bdcc4b83457e08b24599fb4a297ef6ec6c14
Change-Id: Ia2844799a2af8e020470d4c513ad55a51ec36ce1
|
| |\ \ \ \ \
| | |/ / /
| |/| | /
| |_|_|/
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Implement cluster rolling restart strategy.
Add support for Cassandra and PXC.
Add some missing cluster upgrade infrastructure.
Implements: blueprint cluster-restart
Co-Authored-By: Petr Malik <pmalik@tesora.com>
Co-Authored-By: Peter Stachowski <peter@tesora.com>
Change-Id: I21e654a8dd2dc6a74aa095604f78db4e96c70d64
|
| |\ \ \ \ |
|
| | | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is patch 1 of 5 that add i18n translation to the
guestagent/datastore directory
Custom hacking rules will be added later to enforce the style .
Change-Id: Ic8664bf105d601909c6efa5cf73db6c27adaf42e
Depends-On: I6fb2bdcc4b83457e08b24599fb4a297ef6ec6c14
|
| |\ \ \ \ |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is 2 of 5 commits to add i18n translation to the guestagent
datastore directory
Custom hacking rules will come later to enforce this style.
Change-Id: I80f2ea6a20944cfbfdc79a8a71ad744f23aeaac1
Depends-On: I6fb2bdcc4b83457e08b24599fb4a297ef6ec6c14
|
| |\ \ \ \ |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is 3 of 3 commits to add i18n translation to misc files.
Custom hacking rules will be added later to enforce this style.
Change-Id: I88284f61b5f37d78ad050a97c679f6bde23d832d
Depends-On: I6fb2bdcc4b83457e08b24599fb4a297ef6ec6c14
|
| |\ \ \ \ |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is patch 3 of 3 that aims to add i18n translation to the
extenstions directory and some other files.
Custom hacking rules will come later to enforce this style.
Change-Id: I94a341ba1fb4178e0c358c37ea31623d48938ec6
Depends-On: I6fb2bdcc4b83457e08b24599fb4a297ef6ec6c14
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit is a composite of two commits [1] and [2] to help unwedge
the gate. Both of them are required for the gate to possibly pass.
It introduces an unsafe change to unblock the gate temporarily. It
still needs to be debugged and addressed. The change in question is in
_remove_incompatible_context_args() in
trove/common/context.py. Without this check, initial tests indicate
that the system works as expected and testing locally is
successful. Why this is the case, I don't know yet but will
investigate in parallel.
[1] https://review.openstack.org/#/c/425857/
[2] https://review.openstack.org/#/c/423086/
[3] https://review.openstack.org/#/c/412497
From [1]
Fix a ``tox -eapi-ref`` warning
Currently, generating api-ref results in a warning that is treated as
an error.
See [1]. Since api-ref is now a jenkins voting gate, this needs to be
fixed.
[1] http://logs.openstack.org/56/401456/9/check/gate-trove-api-ref/e2e0d9d/console.html#_2017-01-26_17_23_10_952073
From [2]
SessionClient' object has no attribute 'user' Now gate py27 and py34
are being error:'SessionClient' object has no attribute 'user'" I
observed that this is because novaclient from 6.0.0 into 7.0.0 caused,
In novaclient 7.0.0,password and username is merge to auth[1],[2], I
tried to make a change, get password and username from auth[3].
[1]:https://github.com/openstack/python-novaclient/blob/6.0.0/novaclient/client.py#L164
[2]:https://github.com/openstack/python-novaclient/blob/7.0.0/novaclient/client.py#L147
[3]:https://github.com/openstack/keystoneauth/blob/master/keystoneauth1/identity/generic/password.py#L37
Change-Id: I6fb2bdcc4b83457e08b24599fb4a297ef6ec6c14
Closes-Bug: #1657968
Co-Authored-By: Andrey Kurilin <akurilin@mirantis.com>
Co-Authored-By: jiansong <jian.song@easystack.cn>
Co-Authored-By: Tin Lam <tinlam@gmail.com>
Related: I45a40d599b3a302726dc21e409a8da26c9f1f741
Related: I93c1942bb41bd77ea169f0e47d37132ce5d3637d
Related: I41f4144821e491da689c188e25bc2b916867bdca
|
| | | | |
| | | |
| | | |
| | | | |
Change-Id: I705dd4d0774dd373da725b7451de521a35a574f6
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
it isn't clear why flake8 needs to look here.
Change-Id: Iafd9df551e4ca0452dc9bdd793c183d144c72495
Depends-On: Id5be526a0418db5d00cbf5cbceb4993274989e72
|
| |\ \ \ \ \ |
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is patch 3 of 5 to use i18n translation.
Custom Hacking rule will be introduced when these merge.
Change-Id: I48f95b3c090e9b6f91185c14113daae5bc621d0b
|
| |\ \ \ \ \ |
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is patch 2 of 5 that adds i18n translation to the guestagent
directory
Custom hacking rules will be added later to enforce this style.
Change-Id: I56972d16634654b8b71853d6aba10299cc9e2418
|
| |\ \ \ \ \ |
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is patch 2 of 3 to add i18n translation to the extensions
directory and some other files.
Custom hacking rules will be added later to enforce this style.
Change-Id: Ifdf426684473fb05cae63877c334e6cf65aa5234
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Redis supports configuration groups but
the tests for it are not enabled.
Change-Id: I44ccb5371c83b0e1a176e2cad5c6c8b4fd7ac119
|
