The previous patch deleted the entry for the third-party-request
mailing list since -request is a reserved word on the mailing
list server. This patch adds the list entry back with the name
third-party-requests, which should avoid a word usage clash with
the mail server.
Change-Id: I91cc67ba87c1deb1f21fa102f4051934cf9d890d
Using the word -request in a mailing list name is a bad idea.
The mail server uses -request internally as a reserved word. This
patch removes the definition for the list with the name
third-party-request.
Change-Id: Id549f982c74407e3ea57ba5bfe1bf950774f14e3
Add bashate to test-requirements.txt, add a tox env for bashate, and start
running it on config. Also convert devstack to run bashate via tox rather than
via run_tests.sh (the needed tox.ini changes to devstack have already merged).
Change-Id: I205d675ff231c0403dd135eacc8d57b45317859f
Installing only neutron results in errors during provisioning
due to Keystone being required. More testing is required before
service installation can be minimized via config, and maybe it
would be better to skip right to ensuring devstack can install
only dependencies.
Change-Id: I95f7468e53c942091e1f5fe4afd76994da2d386f
Release status page generation is broken since we renamed 'oslo' to
'oslo-incubator' in Launchpad. This fixes it.
This also removes oslo.messaging which is no longer tracked as part
of the Juno release (it has its separate release schedule).
Change-Id: I5cca639a7de2e05dd291ac93da4d67651575b065
The Neutron functional job is running properly again after the hooks script fixes merged to master and stable/icehouse:
https://review.openstack.org/#/c/117280/https://review.openstack.org/#/c/117281/
Enabling this job will ensure that breaking hook script changes will not be able to merge in the future.
This reverts commit 70d909536116a14f670f44ee7411552bd6e0cf2a.
Change-Id: I1f39f182d7807fcbc80ba20684ea9f0f3e935116
* modules/openstack_project/manifests/review.pp: The foundation
member API backend now has a separate direct hostname which can be
used to connect to it without going through a CDN. Using it will
work around proxy-related throttle problems we've seen in the past
where the CDN decides it's being attacked by our Gerrit when failing
arbitrary contact store updates.
Change-Id: I5387eb0d28e8e990ddfa04af9ce8f07468c0f0d6
This allows us to bring up the puppet3 master in an automated way,
then flip on puppetdb later. Most importantly this allows for a step
in the middle where an infra core applies the puppetmaster3 cert
and key from the original puppetmaster.
Change-Id: I77a815591649d55b8c17fb9431add0edd68ce0d2
When change I74e0bda10e85fbe430238f9b53d53b3671309a6a was merged
into master via merge commit
889190486928acf663b1ac616b442d56fcb7f110 it was applied incorrectly.
Its context should have conflicted with an earlier change two lines
away, now corrected here.
Change-Id: I111895676b4376430c1730631f3eb96866991cd4
Berkshelf 3.x requires GeCode 3.x. Default is to install
wrapper gem dep-selector-libgecode which will compile the 3.x
GeCode libraries. This is a very large project to compile and
will fail at times when memory or cpus are limited.
To work around this, there is a dep-selector-libgecode flag,
USE_SYSTEM_GECODE that will allow the gem to just use the GeCode
system libraries. The 3.x version of the GeCode libraries are default
on precise. The 4.x version of GeCode on trusty is not compatible
with Berkshelf 3.x.
* Use precise for cookbook gates until Berkshelf/Chef DK support trusty
* Install the precise GeCode 3.x system libraries when using
Berkshelf 3.x.
Change-Id: I19d16e06e72aff090771c46c15b2b8de164988c8
Closes-Bug: #1357439
This patch creates a stackforge repo for a new project called
radar. This code is currently in Michael Still's github repo
and provides a dashboard to view ci output. An example:
http://www.rcbops.com/gerrit/reports/neutron-cireport.html
Having this repository in stackforge will allow more contributions
on the code base.
Change-Id: I38fe6b3e1d6a7a12b47bf769e65c1b251eef8896
