Commit Graph

13 Commits

Author SHA1 Message Date
Andreas Jaeger 7759e2fd82 Retire astara repo
Retire repository, following
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project

Change-Id: If5f7d284bd107a93edd9272ac0ed8e6d20ba5c51
2018-10-14 12:50:35 +02:00
Kyle Mestery e82baba8d0 vagrant: Add a Vagrant setup for Astara
Add a Vagrant configuration for Astara. This makes it easy for someone
to pull the openstack/astara repository and get up and running with an
Astara setup quickly.

Change-Id: I600328c2a53a8d4aff5bf39a96aaa5b79ef99464
Signed-off-by: Kyle Mestery <mestery@mestery.com>
2016-05-23 13:38:03 -05:00
Adam Gandelman cef007a772 Stop tracking test.conf.sample in git
This file changes anytime anyone generates configs, including devstack, and
can lead to unintended changes in patches if using a devstack env. as a
development environment.  This follows what we do with orchestrator.ini and
tracks the sample as test.conf and ignores the .sample.

Change-Id: I9151b1fa2161943cd9839927409b24f3c0430ffb
2016-02-04 11:16:17 -08:00
Adam Gandelman 84b0928c4d Enrich functional test suite
This beefs up the functional test suite to do some tests on a
tenant router.  The test can now creates one-off tenants to be used
in the tests.  The new tests act entirely on behalf of the test
router and attempt on only use admin-level things when required.

Partially-Implements: blueprint ci-updates-mitaka

Change-Id: I26fa70f877522f09075dc87583f2359cc0dcaf41
2016-01-21 23:17:15 -08:00
Adam Gandelman c598f366ec Drop orchestrator.ini.sample from git
This drops tracking of the generated sample from git, since the output
of generation is non-deterministic, we end up with big changes to this
file anytime someone proposes a change that requires a new sample.

Instead, lets track orchestrator.ini and update it at milestone/release
times.

Also, have the devstack plugin generate and use a sample, that way we
get some gate testing on proposed config changes.

Change-Id: Iaf5127733765e973dbf0e812f267a3304c575fd4
Closes-bug: #1535889
2016-01-19 13:55:14 -08:00
David Lenwell c8f14d6e9d Add driver framework
This abstracts all router-specific functionality into a router driver,
paving the way for the Rug managing other advanced services.

'rug-ctl router {debug, manage, update, rebuild}' commands have been
deprecated in favor of 'rug-ctl resource' equivalents, to be removed
in M.  The newer 'resource' commands are meant to address any
Rug-managed resource.  These requests are routed to the correct place
on the server-side, instead of a Neutron lookup on the client side.

Co-authored-by: Adam Gandelman <adamg@ubuntu.com>

Partially Implements: blueprint appliance-provisioning-driver
Change-Id: I1d2c68b81d28ebb0ca6ce4dcad237c4803bb96d6
2015-10-08 13:27:03 -07:00
Adam Gandelman 6a3261958b Adds a DB layer, use it for debug modes
In preparation for scale out RUG, this adds a database layer
(built on oslo.db) that will be used for managing debug modes.
Instead of tracking debug'd/ignored routers and tenants in-memory
or on disk as files, this uses a database. This means that putting
things into debug mode via rug-ctl are now persistent, and the file-based
approach is no longer available.  A sqlite database (the default) can be
used for single node installs, or the RUG can be pointed at mysql/pg to
handle this in larger environments.

This also adds a global debug mode that can be used to ignore all events
during maintanence periods.

A new optional 'reason' argument has been added to the debug modes, allowing
operators to add a note when entering a tenant/router/cluster into debug
mode.

Change-Id: I3f5129e11b11cf5aaed8889da3b204104e5ad203
Closes-bug: #1470619
Partially implements: blueprint rug-scaling
2015-08-12 15:09:33 -07:00
David Lenwell a227ab593b naming convention change vm to instance
vm_manager = instance_manager
VMManager = InstanceManager
vm = instance

Change-Id: I8ad2bc3f72888dfe43dd3a966cafee4ee2163131
2015-06-24 22:22:55 -07:00
Adam Gandelman 9942eb1433 Wait for a configured test router to become active
The router VM that is spawned during RUG startup may not be active until some
time after the test suite, causing tests to start before the thing is active.
This adds an assertion to the functional test setUp to wait for a configured
router to become active before continuing on with any tests.  The router to
wait on is now configured in test.conf.  run_functional.sh will attempt to find
the devstack created one, and error if there are multiples.  Users can specify
their own test router if running outside of the gate env.

Change-Id: I2b54ddfcce8dab446ac7418cca61320b370bc999
2015-06-08 14:19:28 -07:00
Adam Gandelman bd28d7fb65 Seed a functional test suite with a basic health check
This creates a base functional test suite with a minimal health check
of the service VM.  We can fill this in with richer tests as we go, but
in the meantime this will give us something to at least test that devstack
deployments and image builds produce a reachable VM via its management
port.

Change-Id: I304718e8d3cb270b1ff3b5ad46a027facb42f2af
2015-05-12 12:40:52 -07:00
Doug Hellmann 51e5a082bf convert packaging to pbr
Change-Id: Idc85f3ae84de79b6f2303e3b76368a16ce9867be
2014-03-10 11:56:17 -07:00
Doug Hellmann c3f76cd975 Start rebuilding rug main program
This commit includes a rudimentary main program and the
start of a scheduler for processing messages. It illustrates
the new architecture, but does not yet implement the dispatching
algorithm or actually listen to notifications.

Change-Id: Iedd467e9483a1ec0aea9a9133a6ede35825f2011
2013-07-18 17:25:08 -04:00
markmcclain 1cf04122cc Initial commit 2012-09-25 19:22:48 -07:00