Add a new repo searchlight-specs to contain specification documents for
searchlight. Requires a new group searchlight-specs-core; initial
member should be the PTL, Travis Tripp.
Change-Id: I7560b937bef076b9afa3900626b0a1082d8d1b73
This job only runs in stable/juno and was meant to test the
transition from nova baremetal to ironic, which people should have
done by now.
Also, the job appears to be busted in stable/juno and it's blocking
things from getting into the final 2014.2.4 release before we EOL
the branch, so let's delete it now.
Change-Id: I7128f4c6bbcf2250d4e57d214d04086ea4db542e
This patch adds new pipeline for magnum swarm COE functional testing.
Partially implements: blueprint split-gate-functional-dsvm-magnum
Change-Id: Ifa028f6f30b7c2bb7b1dd32b22669379e162c7c5
This is our first voting gate job. We already have a patchset in place
to make this gate pass correctly.
Change-Id: Ia0d691baca3d9ef7386b2748bc6042a546e6d5f6
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Due to the length of the job name and the tox target we run into an
uncommon limitation; the virtualenv that tox launches is nested in a
path that is too long. This leads to an error on our longest named
job which prevents tox from running properly.
This limitation is the limit for the line length of the first line
in a shell script. In this case <virtualenv>/bin/pip has a path that
exceeds that limit by a few characters. This results in a very
confusing "OSError: [Errno 2] No such file or directory" error.
See `man execve` for more info. A quote from that manpage:
'A maximum line length of 127 characters is allowed for the first line
in a #! executable shell script.'
To reproduce this locally you can just create a very long path and
then run tox in it. Example: http://paste.openstack.org/show/478559/
Change-Id: I51f8f67d9ab139f1d539fce05ce3cc4766aeedff
Depends-On: I43fba2a5ff1890d699045496c9eaee5e849f3e75
This is a trivial change to keep things inline with system-config.
Additionally, this will allow a follow up patch to update pep8 to only
run when .py files changes.
Change-Id: I7981c118b2483147a145617a14a583fe80a20df7
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
os-vif is a project to define an object model and plugin system
to integrate OpenStack network providers (eg Neutron) and
OpenStack compute providers (eg Nova)
Change-Id: Ifc2c1a3198075aafc3fd97f0c5355eb27ba8bc19
This was put in place before prior to releasing Astara Liberty. All
our projects now have a stable/liberty and this can be unpinned.
Change-Id: I45bccff119d84bb27a6fb589119165c7cbf54dc1
Shade needs a job to test the new Ansible 2.0 OpenStack
modules against the latest shade so we can catch breakages.
Change-Id: I0b8d2ccc0344d2213834380d17fdbf665395c5f1
This patch is adding a non-voting job to test Ironic booting iPXE. iPXE
setting up iPXE is already supported in DevStack.
Change-Id: I41d31588f0c1bd6c1154bb9c7e56391ed614d67e
clarkb suggested dsvm be in the job names for Kolla to follow the
job naming convention. In the case of the experimental job we have
recently merged, that it as a requirement for the name of the job.
To keep consistency within the project and within the OpenStack
community we are renaming all of the gates that use the dsvm's to the
convention that all other jobnames follow.
Since the tox paramaters do not change in the jobs/kolla.yaml, this
requires no change on the Kolla side.
Change-Id: I9a22434d99b4deb7936ecaf7b714d0dc41666367
This patch splits one functional testing pipeline to api(common) and
k8s.
We should merge this patch first, then
Ic33ea42f6108c7444c152706458cf1a686ed1756 would works well.
Partially implements: blueprint split-gate-functional-dsvm-magnum
Change-Id: I10e09b2deea7a0643a9516701994cc47813e1aaa
The networking-bagpipe-l2 project needs to be renamed
to reflect the fact that its scope encompasses more than just
a driver for Neutron L2 networks. The scope includes agent
extensions for BGPVPN interconnection, and will extend to Neutron
L3 and service-chaining.
The renaming consists in simply removing "-l2" from the name.
The group statement in gerrit/projects.yaml is not needed anymore,
because the LP project has been removed to drop "-l2" and
add 'networking-" so that LP and Openstack project are now identical.
This change also updates the gerrit ACLs for networking-bagpipe
to match the access list of a neutron stadium project.
Change-Id: I7774b9e9eb830c9320b361b78ebb0dbde3f97205
This commit renames the module to be 'puppet-openstack_health'.
As Spencer Krum (nibalizer) pointed out at https://review.openstack.org/#/c/227849/
this project is not following the naming conventions for puppet modules.
This has a major impact on install_modules.sh, which will not be able to clone and
install this module appropriately.
As part of this, we will need to schedule a maintenance window to take down
gerrit, zuul, etc. and follow the steps enumerated at:
http://docs.openstack.org/infra/system-config/gerrit.html#renaming-a-project
Change-Id: I10c0b61268179088496fe3c381ebd17935cc9e69
Co-Authored-By: Caio Carrara <ccarrara@thoughtworks.com>
The project-formely-known as Akanda has moved to openstack/ and is to be
renamed Astara. This is the final phase of the project move+rename.
This patch renames:
- openstack/akanda-rug -> openstack/astara
- openstack/akanda-appliance -> openstack/astara-appliance
- openstack/akanda-horizon -> openstack/astara-horizon
- openstatck/akanda-neutron -> openstack/astara-neutron
It also renames gerrit groups:
- akanda-core -> astara-core
- akanda-release -> astara-release
As part of the rename, it also retires two unused repos to openstack-attic:
- akanda
- akanda-appliance-builder
Jenkins jobs and zuul layouts updated accordingly.
Change-Id: I3d64946d00cf7fd9c8dce725c56b83e256a6fd11
This adds an experimental job for Kolla to take advantage of n-node
gating.
Change-Id: I9e326fcf0efbf530099bb6a58c59fa0151a0e2e4
Depends-On: I3e05e2d5c739794ae6ff0cc375dc6226f81bb542