This changes the instance manager to use the InstanceGroupManager
to manage clusters of instances instead of individual instances,
including clusters of 1 node for non-HA resources.
This also adds some missing documenation on enabling clustering
of the astara-orchestartor service.
Change-Id: Ib679453aafe68e6653c8c5f9f412efa72c2b7cb1
This allow users to specify the driver and image associated with
a network function. This is dependent on the correct API extension
being loaded into neutron from the astara-neutron repo.
Depends-on: I6b6f98e8ae89c704f45b05f87f17ebed5a70fc1d
Partially-implements: blueprint astara-sfc
Co-authored by: Mark McClain <mark@mcclain.xyz>
Change-Id: I1c349e56fd23d1aa95c7f8c0da68d25246b0ceb2
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
This change add variable MTU support for each interface if the
underlying Neutron cloud supports it.
Change-Id: I52b2d95e892440afa7b941239abd44d37fc224a0
Depends-On: Ib4d4381f6977aabbeefd2f520bb5fc26ea54ffcd
Closes-Bug: #1539786
This cleans up the worker's handling of rebalance events a bit
and ensures we dont drop state machines in a way that prevents
them from later being recreated. It also avoids a bug where, upon
failing over resources to a new orchestartor, we create a state
machine per worker, instead of dispatching them to one single worker.
To do this, the scheduler is passed into workers as well as the
process name, allowing them to more intelligently figure out what
they need to manage after a cluster event.
Finally, this ensures a config update is issued to appliances after
they have moved to a new orchestrator after a cluster event.
Change-Id: I76bf702c33ac6ff831270e7185a6aa3fc4c464ca
Partial-bug: #1524068
Closes-bug: #1527396
This pushes a couple of flags into the appliance that are specific to the
individual orchestrator instance managing that appliance. Initially, we use
it to tell the appliance where the metadata proxy is listening. Previously,
this was hard-coded to a known address on the network. With multiple
orchestrators in a clustered env, this will allow each to run their own
metadata proxy and have only their managed appliances querying that.
Another patch will follow that will ensure this is up to date when rebalances
occur and orchestrators take over new appliances.
Change-Id: Ib502507b29f17146da81f61f34957cd96a1548f4
Partial-bug: #1524068
When a router name doesn't startswith 'ak-', set the default tenant_id to '*'.
Change-Id: I8f907cc191b9816972003e5a2c8dbb35ac2deec9
Closes-bug: 1537500
When a resource is deleted, its not currently removed from the tenant
resource cache. This causes a cache hit if the tenant attempts to re-create
the same type of resource, but the resource is then later ignored because
it has been deleted. This adds a callback used by the TRM to remove it
from the resource cache when its state machine is deleted.
Change-Id: I5dcbeda7de240a693fc7a4944dd34a37b10d174b
Closes-bug: #1531597
When configured to use zookeeper, tooz reports an additional member
named 'leader' in its membership list. This can mess with construction
of the hash table. This removes it from the list of members we use for
the DHT.
Closes-Bug: #1535857
Change-Id: I1d3d7c27984c99c46d6d26e0b9f21c3b5a511617
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
* Modified 'RouterSSH' class to parse neutron ports for ASTARA:MGT port
* Added Exception Handling in class for key or index error
* Fixed ssh username used for connection
* Generalized variable name for managment ip address usage
Change-Id: I2b06e5cb512612cd1b99a438568ddd17a1653c84
Closes-Bug: #1524592
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
We currently hard-code the address for management and external
ports to the first address on the subnet, which breaks clustering
astara-orchestrators when two nodes attempt to create neutron ports
with the same addresses. This updates usage to instead rely on
a Neutron-assigned address to bring up locally.
Note this is a partial fix: we'll need corresponding changes that
allow us to push in this address to appliances for metadata access,
which is hard-coded there as well to the same address.
Change-Id: I88fa97bae84ca245afa5ad0da4ac3c0bc1c441ff
Partial-bug: #1524068
Andreas Jaeger