I guess four times is better than one but if we need four times to kill
swift processes there is something pretty bad with it.
Change-Id: Id2ea2f4ca60feb9fddc7b3181063760d2044b421
The list of services that Tempest used to set its 'service_available'
config values was hard-coded. To be plugin-friendly have each
service (project) add its name to the TEMPEST_SERVICES variable
and use that for setting the 'service_avilable' values.
Change-Id: I208efd7fd0798b18ac2e6353ee70b773e84a2683
We need the new container-sync realms configuration or we will get a
nasty harmless error opening file at swift proxy startup.
Change-Id: If939da305dcb9403c418219032ac6b50b0099bd3
Closes-Bug: 1274295
stop_swift() was not killing all swift processes properly. Change to
manually clean up all screen services with pkill.
Closes-bug: 1268794
Change-Id: Ibb7a2e0dd10a313609f05963264087f82f6f00e2
We were running as auto so swift would spawn a lot of processes
consuming memory and CPU which are not really neeeded in a devstack env
(and bad for the jenkins vm).
Closes-Bug: 1259548
Change-Id: I6b5266186168fe99568dda5453b436c2f9cfedb3
Log only the first 12 characters of auth-token for the Swift
API, since PKI based auth-tokens from keystone can huge (>> 2K).
Also tidy up a comment.
Change-Id: Ib784e8ecdcb7e371fe03458c7fd82b4460fa82b9
Signed-off-by: Peter Portante <peter.portante@redhat.com>
Allow providing certificates through environment variables to be used
for keystone, and provide the basis for doing this for other services.
It cannot be used in conjunction with tls-proxy as the service provides
it's own encrypted endpoint.
Impletmenting: blueprint devstack-https
Change-Id: I8cf4c9c8c8a6911ae56ebcd14600a9d24cca99a0
Devstack is commonly run in a small slow environment, so bump the
timeouts up.
node_timeout is how long between read operations a node takes to
respond to the proxy server
conn_timeout is all about how long it takes a connect() system call to
return
Change-Id: Ib437466a3fc9274b8aa49b19e4fe7fa26f553419
Co-Authored-By: Peter Portante <peter.portante@redhat.com>
Related-Bug: #1252514
Quite easily one ends up calling ./stack.sh in an environment that,
albeit being user "stack" (for example), doesn't quite meet the
expectations of devstack. The errors that follow can be rather hard to
track down, as the dependency on `USER` is not mentioned.
To remedy this situation, this commit
- uses STACK_USER instead of USER and
- mentions that dependency in the script headers of lib/*
Change-Id: If4cdc39b922ea64b4c0893a0e695ec06349fccc5
Swift is returning 50x error codes because its disk is too small, set
size bigger then max_file_size in an attempt to fix the problem, or at
least reduce it.
"we create a 4GB device, but swift thinks it can write 5GB, hence fail"
--sdague
This patch based off of Iccd6368e4df71abb5ccfe7d361c64d86e1071d35
Change-Id: Ib56a98cd74e7edf1fa90facc25c72632d43180f1
Related-Bug: #1225664
This step is needed to enable its testing in Tempest. The patch adds a
variable SWIFT_EXTRAS_MIDDLEWARE_NO_AUTH that holds a list of
middlewares inserted in the pipeline before authentication middlewares
(tempauth, keystoneauth, ...).
Change-Id: I1927103feff997a354ccf82ccf12aa77db083ad3
Address miscellaneous issues with Markdown formatting in comments which
are consumed by shocco when generating the online documentation.
Change-Id: I953075cdbddbf1f119c6c7e35f039e2e54b79078
A few Markdown-oriented issues were causing Docutils errors to
leak into the end-user docs on http://devstack.org
Change-Id: I51fa9698afb1bfb48596478d83bd1fdcd84ac52e
- ${SWIFT_DATA_DIR}/drives/images/swift.img replaced by
${SWIFT_DISK_IMAGE}.
- using truncate -s command instead of dd over seeking
Change-Id: I0dd29af3247ba7819ef0c74775412074b6b62017
Commit 6650fda680310e71b5dda7764bf4033f670d90f0 is no longer needed:
https://review.openstack.org/#/c/46048 has been merged.
This reverts commit 6650fda680310e71b5dda7764bf4033f670d90f0.
Change-Id: I47d28a292667eb8ece2061c0ef19c7c925e5747c
Implements a fedora equivalent of ubuntu's sites-enabled and moves
enabling of mod_wsgi to the installation period so that it doesn't have
to be handled in a platform dependant way later.
Fixes: bug 1226363
Change-Id: I85325179f1792d985b0375572abfe8c8a82fecc3
Swift storage is used as glance image back-end. Tempest have cinder to
uploads 1 GiB image from cinder in twice.
In parallel execution in cause an issue, bacuse the current default size is
1_000_000 KiB.
Increasing the default swit storage size from 1_000_000 KiB 4_000_000
KiB when tempest is enabled.
Fixing bug 1225664
Change-Id: Iccd6368e4df71abb5ccfe7d361c64d86e1071d35
This function allowed you to change the process running user for all of
apache. This is better handled on a per-process basis.
Change-Id: I165adc0c49fc328f34835856b49983c4e189f143
Fixes: bug 1226346
Fixes: bug 1225853
This reverts commit f208aafa35996c98de40c1388bbebf326ab2ed20. This
commit broke swift functional tests because the ceilometer middleware
changes HTTP 404 responses into zero byte responses. This results in
BadStatusLine exceptions. Back out the use of ceilometer middleware
until it can be fixed.
Change-Id: Ie25269b58334c40dc1ecae985326af1cf29c3af4
This allows the storage.objects.{incoming,outgoing}.bytes measurements to be
easily used.
Closes-Bug: #1221097
Change-Id: If988a85930d7df1e043997763c3b5ebd720d6d86
Update keystone cli by changing parameter options (user_id, role_id and tenant_id)
to use '-' rather than '_' in the method user_role_add and consequently the method
user_role_remove without maintain backward compatibility because these are deprecated.
python-keystoneclient - Bug #1150434
Change-Id: Ia5113718eb050cf7dba443b8d0caf3bdaa1730f0
1.install apache and wsgi module
2.config apache2 vhost and wsgi files for proxy,
account, container and object server.
3.refactor apache functions from horizon and swift
into lib/apache
Change-Id: I3a5d1e511c5dca1e6d01a1adca8fda0a43d4f632
Implements: blueprint enable-apache-frontend-for-swift
- We used to set max_file_size to 10000 to get the functional tests
passing on devstack but this was the wrong way. We are now disabling
fallocate like done in saio to get the large objects test passing.
- Fixes bug 1201077.
Change-Id: I33058352f5abfb06f2a992890cbc7339cedc0ad3
