- bump version from 2 to 3 for cinderclient
- update aws ec2 interface for create_colume and
create_network_interface. add cilent_token param
- fix describe network interface - something was
changed in neutron ports output
- set metadata port for OVN conf file also
Change-Id: Ie3e5a5930d5a8159050ecc0900239935558dddd7
when two clients come for functions where check_default_vpc
is present then one goes to create default vpc and other fails.
it fails because vpc with is_default flag is already in DB
but children objects (like subnets) are not yet created.
For we will lock check_default_vpc function.
Another way is to rework _create_vpc. It can create VPC
without is_default flag. And at the end it can set the flag.
First thread will pass this. And second thread will fail at flag set
operation and will revert all created object. Then second thread
can check presence of default VPC again.
This way is better cause it can work across several controllers.
Change-Id: I5586fa234257b72721e328a9fa2375a56d1553c2
current version of migration API doesn't allow to
pass several commands to one execute
Depends-On: I9f1f39b30d43dc16a474febcf6549cf1901732ec
Change-Id: I0a74c87c4c782a7a26aa0e67fada994cb3e31434
replacement of functions performed earlier with nova-cert service
function decrypt_text copied from novaclient to image api
certificates in devstack for uploading image to s3 are created by openssl
Change-Id: Ibf7b90ea29085656005317c4aa0fd96f3313da0c
if configured adds the resulting metadata tree to the cache and
upon next request retrieves the data from the cache
reduces the time of the second and subsequent sequential requests
to the metadata approximately from 2.5 seconds to 0.1
Change-Id: Ia1408f6ef407eb97db1789b5b60d6b36b162ba4d
removed NovaEngine in addresses, availability_zones, instances, security_groups
removed unit tests for NovaEngine
disabled some unit tests using NovaEngine for further reworking
Closes-bug: #1691484
Change-Id: I662d5b57b9e46be80c1d2093038ada83897565eb
do not use keystone_url in keystone_ec2_tokens_url definition.
configure these two urls independently.
Change-Id: I78c54c26820dfd7b52bf7cec81fa4ca0174a9eb6
The README mentions that install.sh allows setting
custom port(other than 8788 default) to start ec2api
on but upon looking, there wasnt any option. This patch
adds the option to allow user to set a different port
prior to installation using install.sh script.
also the options defined in devstack plugin but
it isnt being set in ec2api.conf.
Change-Id: I440b69fafb5555a7a9f4d1e27b1f811d2a3ecc29
Specify auth version for delete endpoint and service operations.
Also remove v2.0 from keystone url to allow discovery of auth method in Nova CLI.
Change-Id: Ibfab462b89bc45f9acf9337be54d92d9be48e846
plugin used 'openstack' to recreate ec2 endpoint
now devstack uses keystone v3 and 'endpoint list' shows
three lines. but script accepted only one.
Change-Id: I6819069a7bb0559dd34c923824695866a7edf956
DevStack has API_WORKERS variable which mean a count of worker threads
for services. This variable allows to be set in local.conf. Otherwise it
is evaluated in stackrc script. DevStack's nova script uses it to set
workers count for ec2 and metadata services. Thus ec2-api have to do the
same.
Change-Id: I67a991be239588beb8086b7c462e559cd08da055
fix register_image function -
code can access outer variable but "set operation" will create
a new name in the current scope, which cover the outer one.
Change-Id: Ica2750fbf05e0d3c68ed199996afd8c6e7662229
Copy S3 server implmenetation and unit tests from Nova.
Add fileutils from oslo-incubator and refresh incubation modules.
Upgrade script doesn't copy buckets content because Nova S3 server
is not intended to be permanent full functionality object storage, but
has to be used temporary to CreateImage operation only.
Change-Id: I7d38b0a8e014dfff8238e7134d837d1074e4dd95
Important features:
- Nova client with microversion support is required.
- Nova API server may not support microversion 2.3 (not tested).
- Attaching volumes are not displayed in an instance bdm. Because Cinder
volume doesn't yet contain attachment info (which contains a device
name), and Nova instance volumes_attached doesn't contain a device name
(mountpoint). But a bdm must contain it.
Other features:
- v2.3 is requested always
- RunInstance result is formatted w/o extra v2.3 info, so it doesn't
contain rootDeviceName and other such info
- if rootDeviceName property is empty it's omitted instead of
to report fake /dev/sda1 as Nova EC2 does it. This leads to omit
rootDeviceType property in this case as well.
Also the same is done for corresponding image's properties.
- deleteOnTermination volume property is omitted for volume at all, and
for instance bdm if Nova doesn't report it. Previously this volume
property contained 'False' only.
- DescribeVolumes isn't used in DescribeInstances (as opposed to
DescribeNetworkInterfaces), because both methods require actual state
of corresponding OS objects, so we prevent duplication of OS requests.
- Not merged Nova client is used
https://review.openstack.org/#/c/152569/
Also:
- fix multi-run instances for EC2 Classic mode
- safe getting of OS instance security groups
- ec2context module alias is renamed to ec2_context, as it is in other
code
- fakes.CinderVolume is renamed to local standard OSVolume
- fakes.OSInstance it transformed to be initialized from a dictionary,
as it is for other fakes.OSXxx objects
- fix code style
Depends-On: Icf2b9739aaf87b4c9af13ad64a310081a68f776e
Change-Id: Id65ea0f56ffd889286d5ca082e1daf2643205c52
A preparation step to get rid of Nova DB usage.
Move a function of OS admin context initialization to context module to
use it in all of API.
We're going to use this function to initialize Nova client to get
instance object with an admin account (which is the only option to get
neccessary extended instance attributes).
Change-Id: I195d899ed245ea3489c7e97b56ee6aaff9a08be2
Andrey Pavlov