- Add a new element 'guest-agent' for image building. This element is
used when dev_mode=false, so that the trove code is downloaded into
the image during the building phase rather than during the guest
agent initialization.
- Improve trovestack sub-command 'build-image'.
./trovestack build-image ${datastore_type} \
${guest_os} \
${guest_release} \
${dev_mode}
- Improve documentation.
Story: #2005387
Task: #30375
Change-Id: I9d7acbd6a97f8c01b48b0f2cf94398d549d89124
New entry added as an RST file with examples showing how to
create and manage users and databases on Trove instances
using Trove API.
Change-Id: I565f3b4d7c215c9508de127f1781638531d6fb45
Signed-off-by: Dariusz Krol <dkrol3@gmail.com>
Signed-off-by: Dariusz Krol <d.krol@samsung.com>
This check detects Trove instances in state other than Active
(identified by assigned None tasks), as such instances have some
kind of activity running, which requires communication between
the instance and Trove control plane.
Change-Id: I64901fd27dc97de8ee5e3bc693ec966d4f1a3346
Signed-off-by: Dariusz Krol <d.krol@samsung.com>
This adds basic framework for trove-status upgrade
check commands. For now it has only "check_placeholder"
check implemented.
Real checks can be added to this tool in the future.
Change-Id: Idfeab4c06cba6f841c17ab6e255a29e8707bfa55
Story: 2003657
Task: 26162
Support for the [oslo_messaging_rabbit] section has been removed in
oslo.messaging==9.0.0 package [1].
That's why integration tests failures on build devstack step.
This is the moment where we need to use the transport_url directive
in the [DEFAULT] section instead.
Moreover rpc_backend property (which was used in trove to enable fake
RPC backend) has been removed from DEFAULT section and API tests
fails on TIME_OUT as they starts on rabbit RPC backend.
Fake RPC can be now configured as described here [2]:
transport_url = 'fake:/'
[1] https://docs.openstack.org/releasenotes/oslo.messaging/unreleased.html
[2] https://docs.openstack.org/oslo.messaging/latest/configuration/conffixture.html
Change-Id: Id6c5a9198d5a213cb085407a1d8b534e7c755f69
Signed-off-by: Marcin Piwowarczyk <m.piwowarczy@samsung.com>
It seems that the current guestagent only needs to communicate
through amqp, and does not need to interact with nova, so the
related nova configuration can be removed from the guestagent,
which can reduce some invalid configuration.
Similarly, we removed the related configuration of condutor
and guestagent in devstack plugin.
Change-Id: I3f0b3b445c053351c1f3e966d77ea228df0e94a7
The neutron client commands will be deprecated,
and 'nova net-list' has already been deprecated, so use
openstack client commands to replace neutron client.
Change-Id: Idb7d9782bb3af28cba7e318b0ed664641b5d731f
Option auth_uri from group keystone_authtoken is deprecated[1].
Use option www_authenticate_uri from group keystone_authtoken.
[1]https://review.openstack.org/#/c/508522/
Change-Id: I46bb0acaf1dec9bb4b91d4a2180b3e7ed66741c2
Ubuntu Trusty continues to get MySQL 5.6.
The selection of the MySQL version is based on the version
of Ubuntu that is installed. If the script trovestack is
invoked on Xenial, the version that is chosen is 5.7. If
it is invoked on Trusty, then version 5.6 is chosen.
The only thing that is eliminated is the dubious combination
of MySQL 5.6 on Ubuntu Xenial. This combination is probably
not supported by Ubuntu as it is down level from their
standard offering is probably not tested anywhere.
Note Xenial does not provide the 5.6 version of mysql. This
was accomplished by initializing the Apt repo with the
Trusty software repository.
The size of the root file system is increased from 3 to 4 GBs
as the Mysql Xenial image does not fit in 3 GBs. This has an
impact on the flavors that are used by Trove for testing as the
name of the flavor includes the size of the root file system.
This is turn caused a change to each of the db specific test
config files as the trove falvors are referenced in them.
Change-Id: I4f4e497208b8f4728580e48239a8ae208e0a96dd
The link of Ubuntu Cloud Archive is broken and was referring to daily
buildings. Using official released images instead.
Change-Id: I78352c72c667cae93c0865f79ded0ed5caff7560
Signed-off-by: Zhao Chao <zhaochao1984@gmail.com>
1. since the Nova-network has been deprecated, the install docs should
update too.
2. optimise the description
Change-Id: I651789b5f50a3c7ef5d68e4b720881d5b245b911
bin/disk-image-create was moved in a patch last year, this moves
disk-image-create to a regular python entry-point[1].Resulting in
our current document will be some problems. It seems that an
effective solution is to install DIB. Updated the relevant
information.
[1]:https://review.openstack.org/#/c/367157/
Change-Id: Idf1c15491ca77f4bd06a7b13aec676c84d15a800
Remove references to Mitaka.
Remove reference to bug.
Remove tag referenced in the document.
Some small fixes.
Change-Id: Ia0b8f6e465b4417178dbbcd5e186610e65255a08
Closes-Bug: #1725191
Closes-Bug: #1725192
Remove notifier_queue_* because the options are no longer needed and
should be removed.
Closes-bug: #1706528
Change-Id: Idfd205473f1756a69d0d9607e9f8c1dd9780553c
Currently the link in our developer documentation to our api-ref
is old. This updates it to the new one.
Change-Id: I68a36d4136422b823f2a71f3ea579896c7813c81
For the longest time I've had a hard time understanding why my instances
were in ERROR or stuck in BUILD state. This guide fills in the
missing details that are necessary for setting up a trove instance.
I hope this guide will expand into other debugging steps/tips but
this is a good start.
I often found myself reserving too many resources that weren't
available. I didn't realize the virtual machine hogs so much of
the resources, or at least on my machine that is.
This guide will help those who are new to the world of cloud
computing and give them an understanding of how a trove instance
relates to your system's hardware.
Change-Id: I2dcfadb77b2a66f7e4ba3363aa54c8ad89605a88
This change enables behind mod-wsgi as part of the community pike goal
goal-deploy-api-in-wsgi.
The change includes:
- the wsgi script files to run trove api under apache
- updates to the devstack plugin
- a basic deploy doc which explains this change
Change-Id: Icdd39b47a1be426e87a5d09f9e9d567af1974a9c
Depends-On: I3d6f6649430ee40879de15fee0b215dc32e8b666
Closes-Bug: #1681478
I don't know why we even needed heat-cfntools but we appear to have
depended on it. In commit c653eaee1c4091701e8da0f2c6f193e7126d8c49,
this was yanked unceremoniously. So I'm making us no longer reference
it other than the help string in dib's usage (which I won't bother to
fix).
Change-Id: I3cde6b7ba43fdd757a3994d0f3ac6ebec554538c
Caused-By: I221c5a3f82a2500c90646fc69439a210cf64e5e1
Related: I221c5a3f82a2500c90646fc69439a210cf64e5e1
Add warning-is-error to setup.cfg to treat sphinx warnings as errors.
Fix all existing warnings so that docs build with this change.
Also fix some display problems in secure_oslo_messaging.
Change-Id: I7b2fe76cfc388c49f6be4c2d62e983b19bd7e927
This is an interim commit of the changes for secure
oslo-messaging.rpc. In this commit we introduce the code for
serializers that will encrypt all traffic being sent on
oslo_messaging.rpc.
Each guest communicates with the control plane with traffic encrypted
using a per-instance key. This includes both traffic from the
taskmanager to the guest as well as the guest and the conductor.
Per-instance keys are stored in the infrastructure database. These
keys are further encrypted in the database.
Tests that got annoyed have been placated.
Upgrade related changes have been proposed. If an instance has no key,
no encryption is performed. If the guest gets no key, it won't
encrypt, just pass through. When an instance is upgraded, keys are
added.
The output of the trove show command (and the show API) have been
augmented to show which instances are using secure RPC communication
** if the requestor is an administrator **.
A simple caching mechanism for encryption keys has been proposed; this
will avoid the frequent database access to get the encryption
keys. For Ocata, to handle the upgrade case, None as an encryption_key
is a valid one, and is therefore not cached. This is why we can't use
something like lrucache.
A brief writeup has been included in dev docs
(dev/secure_oslo_messaging.rst) which shows how the feature can be
used and would help the documentation team write up the documentation
for this capability.
Change-Id: Iad03f190c99039fd34cbfb0e6aade23de8654b28
DocImpact: see dev/secure_oslo_messaging.rst
Blueprint: secure-oslo-messaging-messages
Related: If0146f08b3c5ad49a277963fcc685f5192d92edb
Related: I04cb76793cbb8b7e404841e9bb864fda93d06504
Our readmes and rst files had references to trove-integration and
redstack. This commit cleans up those references.
Jian Song had also been trying to make some of these kinds of changes
to the documentation and to reduce conflicts and merges, I'd requested
him to hold off. As a result, I think it is only fair that I list him
as a co-author.
Change-Id: I685659391fd04eefd250e72d789da5a0d7b7aace
Co-Authored-By: jiansong <jian.song@easystack.cn>
Add additional information with links to the Trove installation guides
found in the OpenStack documentation.
Co-Authored-By:jiansong <jian.song@easystack.cn>
Change-Id: Ic46b84a48faf77e1a609d2abf94fffb002e92112
