When the plugin is enabled, we should always enable the service, there's
no benefit in having an extra invocation - and it can only confuse users
when they forget setting it up.
For more info see:
http://docs.openstack.org/developer/devstack/plugins.html
Change-Id: Ifcabc0955cb54f66388cac0c74b70c70ba65a1f9
This change makes Astara compatible with Newton. This change adds support
for Neutron agent reporting and service providers to work with new L3
drivers. Included in this change is a temporary filed called newton_fix.py.
This file will be removed in follow-up change after changes are migrated to
astara-neutron.
Change-Id: I5843e84e36af2e46de5b8420ca5749033c26ee69
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>
This change enables ipsec VPN support when neutron_vpnass is enabled in
devstack.
Change-Id: Ia6fb1f9b23f0fbaf2531434c2cac1e317370046b
Closes-Bug:1566602
Bump alive timeout to 60s to deal with slow qemu instances.
Also, give astara more time to recover from a degraded cluster. This
can be slow to recover when a slow qemu node is waiting on a long-running
config update.
Change-Id: I491b96c43d898f7a961725e4f5720af7b9547038
- Dont cache management address of appliances
- Wait for nova instance status==active before asserting router status
- Wait a full config_timeout (600s) for rebuild
- Also look for ha router interfaces when cleaning up
Change-Id: I69341c6abee4e36b10f8e9b676587babe861f0c0
Table in horizon show neutron dhcp agent will cause an error
with astara plugin, override the panel by setting Horizon
customization_module option.
Change-Id: I01a323f44b0c99320d6437aebac1abbdf605974e
start_astara_horizon restarts apache to load the horizon plugin.
This also restarts keystone, which causes the initial boot loop
for the first router to fail when astara is started. This moves
updates it to restart apache before starting astara, eliminating
the race.
Change-Id: Ibec39488024497ed5fab2abd1e32f5d1f9e39a68
Previously the orchestrator could be configured to create access to the
external network. This combined with auto external gateway additions
would cause problems with automation tools and did not work reliably.
This change removes this functionality since it was often disabled in
production deployments. This change aslo slightly reduces devstack
runtime by removing the Neutron restart.
Change-Id: I556f1fc2729f1d62a60de24b6d5e9ed473749f9a
Astara floating IP hook was removed in another change[1]. We can remove
that support here.
[1] https://review.openstack.org/#/c/268286/
Change-Id: I4b99af1e8523da827c892ba67861d40dfb7fe980
Only change Nova policy settings with Nova is installed. Also make sure
to use configured value of NOVA_CONF instead of hardcoded path.
Change-Id: I8534c2631186b8937faaa6b82f67bae3a5a5fe7f
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
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
This switches keystone to use oslo-config-generator, where the contents
of our sample configuration file are configured using a configuration
file in etc/oslo-config-generator.
Also fix some config problems.
blueprint autogen-astara-conf-file
Change-Id: I394805b18eecc4fbc583f9d64d34b8e95b55a845
This allows users to configure a specific API listening address
for the astara administrative API. This also updates devstack
plugin to publish this into the keystone catalog, for easier
lookup by astara-horizon.
Partially-implements: blueprint astara-horizon-mitaka
Partial-bug: #1516787
Change-Id: I2b96137c05b832a68ad01a11ec0cfb2371111c3c
Squashes two commits needed to unblock the gate:
devstack: prevent auth params set in env. polluting client calls
The switch to keystone v3 has introduces issues when other devstack
components set tenant or project name in environment, as it overrides
those set by us in our plugin script. This ensures that doesnt happen.
It also updates usage of upload_image to avoid issuing a token (no longer
needed) and uses openstack client to create the nova flavor using clouds.yaml.
Fix E402 pep8 violation
Change-Id: Icfd0790e0f23bc9daaef6e006e39e3b94e42417e
Change plugin from "source" to mode "stack" and phase "pre-install" to generate the default ssh keypair.
Change-Id: Ie52095db3342cfa01114a2fd1c67220b9edf9626
Closes-Bug: #1531723
This deprecates usage of the old amqp_url in favor of using backend-specific
oslo.messaging configuration. Removes the old, pre-Liberty options and silences
a bunch of deprecation warnings to boot.
Change-Id: Ib666901c28f66a7616aa445ecc7120fe9d1e1364
Closes-bug: #1524595
Our published image is currently 1 commit behind trunk, so we need
to point this at the old console script until a newer image shows up
with the rename in place.
This can be reverted after mitaka-1.
Change-Id: Ieae165c98f23a1ff20ec75a09d79e495537cea2b
In this step all of the imports and usage of akanda.rug is updated to
use astara. Addtionally rename all internal references from Akanda to
Astara.
Change-Id: I0cb8596066d949bceaadc4718b210fc373b5f296
Depends-On: I87106ae63747291bb6424839b5155f53136c54f9
Implements: blueprint convert-to-astara
We're building astara.qcow2 but pointing glance to akanda.qcow2.
This fixes it and should fix the dsvm-src jobs.
Change-Id: I2e87e8bdcc3ad17d8689cd74e9697dc371849006
During devstack stack, Git cloning from Github regularly (not
always) fails using http.
Apparently, Github are moving away from http to https.
MarkMcClain correctly recommends using the devstack variable
GIT_BASE. This is actually a change from http to git protocol.
Track naming change from akanda to astara.
Change-Id: I753fe5edd16f83927993f75ddd29500b01555ea3