In Python 3 __ne__ by default delegates to __eq__ and inverts the
result,but in Python 2 they urge you to define __ne__ when you define
__eq__ for it to work properly.There are no implied relationships
among the comparison operators. The truth of x==y does not imply that
x!=y is false.Accordingly, when defining __eq__(), one should also
define __ne__() so that the operators will behave as expected.
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:
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
When an exception was caught and rethrown, it should call 'raise'
without any arguments because it shows the place where an exception
occured initially instead of place where the exception re-raised.
Some tests used incorrect order assertEqual(observed, expected).
The correct order expected by testtools is
This patch will fix the issue.
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.
Signed-off-by: Kyle Mestery <email@example.com>
Instead of spawning our own threads and relying on the oslo.messaging
executor blocking, lets just use oslo.messaging's internal threading
capabilities. This converts rpc.Connection to rpc.MessagingService,
which is an oslo.service-based service and sets up messaging to managed
Subscribe to the correct floatingip event for events that broadcast
when a nova associate or disassociate floating IP takes place.
We currently pass the ssh key read from disk straight into
cloud-init. If it contains newlines before or after, it can
break the yaml formatting of the cloud-init causing the appliance
to fail to successfull boot.
In some deployments (OVS), port security must also be disabled
on the management port for communication from astara to the appliance
We currently do not allow operators to specify which endpoint type
needs to be used to reach nova and neutron via their clients. This
adds a new option that defaults to publicURL (as it is today) but
allows operators to specify internalURL or adminURL if they need.