Current Nova server volume support is broken. Nova also declared the
'os-volumes_boot' will be deprecated in the future. As creating volumes
by cinderclient has been supoorted for a long time, we could just drop
support of Nova server volume.
This patch also migrate to the new block_device_mapping_v2 parameter of
Nova servers creating API.
Closes-Bug: #1673408
Change-Id: I74d86241a5a0d0b1804b959313432168f68faf89
Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
add_options in trove.db is not used for a long time, and this is the
same situation fofr optparse in python 2.7, so we can safely remove
this part from trove.db.
Closes-Bug: #1553030
Change-Id: I17228eed5c122bce49ce80ec665fe73d6caa1e04
Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: Id890fde91a7e2b3ec9a6cf5ebe540d4fd65938bc
During the Vertica cluster growing/shrinking,
the "update_vertica" command tries to get AWS
metadata even if --ignore-aws-instance-type is
specified.
The only way to avoid the "_get_macs error" is to
define --ignore-install-config option.
This is very similar to this bug[1] but this time
this for the "trove cluster-grow" and "trove
cluster-shrink" commands.
[1] https://bugs.launchpad.net/trove/+bug/1745493
Change-Id: I35f2035039f72b3aa2d9beb665096d4fb57e1c4c
Closes-Bug: #1747050
During the DB2 installation, the db2_install
process asks a question about the license. Disk
Image Builder will hang until "yes" or "no" is
manually entered.
db2_install script provides the "-y" option to
accept automatically the license.
From db2_install help:
Specifies that you have read and agreed to the
license agreement file in the db2/license
directory on the CD. This parameter is mandatory
when -n is specified.
Change-Id: I8a8330adc41cbed60c8472f925b10cf816aed44e
Closes-Bug: #1747031
The DB2 path needs to be changed to something
basic and not using a version number because we
don't want to update the code every time than a
new DB2 version is released.
Updated DB2 version from 10.5 to 11.1, version
10.5 is no more available on IBM website.
Closes-Bug: #1746351
Change-Id: I4fd7c66c3cd5ff8d540e994ada979b59c7def35e
During the Vertica installation, the install script try to get AWS
metadata even if --ignore-aws-instance-type is specified.
The only way to avoid the _get_macs error is to define
--ignore-install-config option.
During the cluster creation, if the process is too long, Vertica
ask a question:
Do you want to continue waiting? (yes/no) [yes]
From the adminTools documentation there is no non-interactive or
timeout options. The only way to have this question answered is
to run "echo yes | " before the "adminTools -t create_db" command.
The only available version from Vertica website is 9.0.1.
Closes-Bug: #1745493
Change-Id: I94472082fac606f4ff14f26c2ca2b620ef0a3bbb
Add some configuration options on valuation rules file,
these options are availables from the release 9.5 and 9.6
New options from 9.5:
- gin_pending_list_limit
- idle_in_transaction_session_timeout
Changelog:
https://www.postgresql.org/docs/10/static/release-9-5.html
New options from 9.6:
- log_min_duration_statement
- backend_flush_after
- bgwriter_flush_after
- checkpoint_flush_after
- force_parallel_mode
- parallel_setup_cost
- parallel_tuple_cost
- replacement_sort_tuples
Changelog:
https://www.postgresql.org/docs/10/static/release-9-6.html
Closes-bug: #1745238
Change-Id: I89d793ccc7fa43deb3c1da7b23ce10cdf1e85c4d
models.DatastoreSchema() needs to be initialized
with a database name.
This change fix the backup on DB2 instance
Change-Id: I95a9c60cd2406d4aa3b6ee52c654b2590a8d7e03
Closes-Bug: #1746626
Looks like SQLAlchemy in version 1.2.x checks if the boolean value
is None, True, False, 1, or 0. We used a "1" in our test, which
does not seem to meet the requirements. In the meantime, if we
change it to 1 here, our function section needs to be changed
as well.
Change-Id: I8df2118fee12fd9dd02caf96a23bc59652efbed7
The element is configured to use version 3 of cassandra, unfortunatly
trove is actually not compatible with version 3.
Closes-Bug: #1745056
Change-Id: Ic22202eeae6f404433a84def8cf5da0e5dc28c7b
The pip command was not installed. Added a couple of
prerequisites (snappy, Cython) and db management package.
The cassandra-tools package provides commands for enabling
and disabling incremental backup, snapshots, and many other
features. It is provided by the cassandra community.
Change-Id: If0f807878d6f3da17e33bc9e40ecb9563de61a25
Doc style:
* use tildes for heading 2 (following the rst convention);
* break source lines exceeded 79 characters (rst convention);
* remove unneccessary blank lines:
* 4 blank lines between sections;
* 2 blank lines between sub-sections;
* 1 blank line between paragraphs in a section/subsection;
* no blank lines at the bottom of a source file.
* add a space after commas in the middle of a line;
Instances API:
* change the order to match the description at the begin;
* add "Update instance name";
* add "Upgrade datastore version".
Change-Id: I3520e42f6ad97cb30632cf05241cec316409c9be
Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
According to discussions on the ML, log messages should not be
translated any more. This patch also:
* removes all usage of _LI, _LW, _LE, _LC;
* updates log translation hacking rule.
ML discussions:
http://lists.openstack.org/pipermail/openstack-i18n/2016-November/002574.htmlhttp://lists.openstack.org/pipermail/openstack-dev/2017-March/113365.html
The original commit messages are kept as following to make a historic
note:
remove unwanted log translations
recent discussions on the ML have led to the decision to eliminate all
translations for messages that are destined for log files but retain
them for messages that are going to be returned as exceptions and
potentially shown to end users via an API. see [1], [2].
This change does that as follows.
1. If a string is being used to generate an exception, it will still
be translated. Still Trove used both _LE and _ for these translations,
there are some cases where _LE has been simply changed to _, and not
removed.
2. If a string is used for a logging message, remove the use of _,
_LE, _LW, _LI.
Also, I have long felt that we have had a creep of checks in the pep8
tests that apparently make the code easier to read. I strongly believe
that these kinds of "easier to read" things make sense if they are
followed across all projects and not just gratuitously added one
project at a time.
I've taken this opportunity to reduce the merge mess caused by this
change, to sync up our ignore flags with a long list of ignores from
Nova. When they made the change for removing log translation, they
could do it in an automated-way like I have because they didn't have
to deal with under and overindented lines for visual edit (E127). Same
for Cinder.
Changes 448443 [3] and 447839 [4] were inadequate because they only
addressed a little part of the problem, namely removing the use of
_LE, _LI, and _LW, and I think this is a change we don't need to
dribble in a few files at a time. The changes are straightforward and
should be taken in a single lump to make it easy to deal with the
merges coming.
[1] http://lists.openstack.org/pipermail/openstack-operators/2017-March/012887.html
[2] http://lists.openstack.org/pipermail/openstack-dev/2017-March/113365.html
[3] https://review.openstack.org/448443
[4] https://review.openstack.org/447839
Co-Authored-By: Amrith Kumar <amrith@amrith.org>
Co-Authored-By: Valencia Serrao <vserrao@us.ibm.com>
Change-Id: I5f86c982469e625997fc8bd15c6fae0fc77a8c64
TEMPEST_SERVICES global variable is not supported
by devstack since long back.
- I380dd20e5ed716a0bdf92aa02c3730359b8136e4
- I9c24705e494689f09a885eb0a640efd50db33fcf
Service availability of tempest known services will be
set by devstack with local check.
- I02be777bf93143d946ccbb8e9eff637bfd1928d4
This commit removes the unused TEMPEST_SERVICES setting
Related-Bug: #1743688
Change-Id: Iccbc833d821a2d7b2bc34860170ce1817fbecead
There are a lot request debug logging in Trove, when some values of
headers are encoded in utf8, UnicodeEncodeError will be raised by
webob.Request. Override how webob.Request is represented will fix.
Closes-Bug: #1720121
Change-Id: I91683b8dd24262b0f643e8d2bc7886a7c03be40a
Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>