On Ubuntu 14.04, the site configuration file must have a .conf suffix for a2ensite and a2dissite to
recognise it. a2ensite and a2dissite ignore the .conf suffix used as parameter. The default sites'
files are 000-default.conf and default-ssl.conf.
On Ubuntu 12.04, the site configuration file may have any format, as long as it is in
/etc/apache2/sites-available/. a2ensite and a2dissite need the entire file name to work. The default
sites' files are default and default-ssl.
On Fedora, any file in /etc/httpd/conf.d/ whose name ends with .conf is enabled.
On RHEL and CentOS, things should hopefully work as in Fedora.
This change puts all distribution-related site configuration file name differences in lib/apache and
the other services gets the file name for its sites using the new exported function
apache_site_config_for <sitename>.
It also makes Fedora disabled sites use the .conf.disabled suffix instead of removing the .conf from
the file name.
The table below summarizes what should happen on each distribution:
+----------------------+--------------------+--------------------------+--------------------------+
| Distribution | File name | Site enabling command | Site disabling command |
+----------------------+--------------------+--------------------------+--------------------------+
| Ubuntu 12.04 | site | a2ensite site | a2dissite site |
| Ubuntu 14.04 | site.conf | a2ensite site | a2dissite site |
| Fedora, RHEL, CentOS | site.conf.disabled | mv site.conf{.disabled,} | mv site.conf{,.disabled} |
+----------------------+--------------------+--------------------------+--------------------------+
Change-Id: Ia2ba3cb7caccb6e9b65380f9d51d9d21180b894e
Closes-bug: #1313765
With the increasing number of entries in the service_catalog header,
some projects will have a header bigger than 8192 and Swift cannot
handle headers of this size. Solum is the first one to have this issue
As a temporary hack to fix Solum's gate, we are increasing
the value of the max_header_size parameter in our "lib" script.
This patch makes this settings global to all projects using devstack,
so that in a near future, if a project has a service_catalog header
bigger than 8192, it doesn't have the same problems we had.
Closes bug 1316585
Change-Id: I5c15f8f9531839353c3d99e46d920688058ec33c
Swift was missing an 'if [[ $SYSLOG != "False" ]]' statement which is used
by other services, and therefor failed with a 'No such file or directory'
error when 'SYSLOG=False' was set in localrc.
Closes-Bug: 1308461
Change-Id: I8655a955ebb322516d92bee418b93d4cc23bdc5c
Xfsprogs package has been installed. This is the cause of the error stack does not have
permission to perform mkfs.xfs command rather mkfs.xfs command in /sbin/
path, stack in order to perform mkfs.xfs must add the full path or use
the sudo command mode.
Fixed bug #1292466
Change-Id: I488133539331b4a0034a2afb4e75665904754245
it's not clear why swift start is the place where an rsyslogd start
is happening, we should really only make this change when we actually
change a file on disk.
Also, use rsyslogd's -HUP signal directly instead of the system init
scripts which are typically doing a stop and start, and apparently
racing under some circumstances.
Change-Id: I1b9891313d67b1da2ca2582e532b2536a81f9b25
Closes-Bug: #1262906
This middleware is spamming rsyslog with rabbitmq debug logs, making
this middleware practically unusable in combination with rsyslog. Because of
this, the rsyslog logs now account for 35% percent of the logs we store
in logstash. Until the underlying problem is solved disable the
offending code.
Change-Id: I50a73ae6beb1a11c41225340779fe8d7a1081e46
Related-Bug: #1294789
Swift commit 165dd44 added tempurl to the sample config, so now it
appears twice in the default devstack-installed configuration. This
commit removes tempurl from $SWIFT_EXTRAS_MIDDLEWARE so that it only
appears once in the generated proxy pipeline.
Change-Id: I4204b2a444312ab87c17f5fb296a43818a4528a6
stop_swift() wasn't calling screen_stop() so the pid files and screen
sessions were not being cleaned up. DevStack doesn't really care but
Grenade does for the 'base' copy of DevStack. This should be backported
to stable/havana for this reason.
Change-Id: Ib5afb321cef2b7ad74e69a3fd0d1dad469f78b11
Assuming if the system does not have the xinetd.d/rsync,
the dedicated service is the prefered way.
Change-Id: Ic42651c5c3fb5bf0099786ca81a7bd06ace896a8
Check that function calls look like ^function foo {$ in bash8, and fix
all existing failures of that check. Add a note to HACKING.rst
Change-Id: Ic19eecb39e0b20273d1bcd551a42fe400d54e938
migrated most keystoneclient commands from the following libs:
ceilometer
cinder
ironic
keystone
marconi
neutron
nova
savanna
swift
trove
Also need to set and unset openstackclient specific environment
variables from stack.sh
Change-Id: I725f30bc08e1df5a4c5770576c19ad1ddaeb843a
During the process, when create_userrc.sh tries to creates
certificates and sourcable rc, it assumes that all users have
the same password.
Change-Id: Ifb57a43aad439ffe041e98465719a8a8eceae544
Closes-Bug: #1260723
This converts the special cases in the is_service_enabled() function to call
individual functions declared by the projects. This allows projects that
are not in the DevStack repo and called via the extras.d plugin to handle
an equivalent service alias.
* Ceilometer
* Cinder
* Glance
* Neutron
* Nova
* Swift
TODO: remove the tests from is_service_enabled() after a transition period
Patch Set 2: Rebased
Change-Id: Ic78be433f93a9dd5f46be548bdbd4c984e0da6e7
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