[nova][metadata] EC2 compatible metadata deprecation

Matt Riedemann mriedemos at gmail.com
Tue Dec 17 15:58:15 UTC 2019

On 12/17/2019 9:10 AM, Artom Lifshitz wrote:
>> Currently, we use EC2 metadata in our product to obtain public and private IP addresses, as well as the instance-type (flavor). Therefore, I would like to ask you a couple of questions.
>> 1. Do you plan to ensure compatibility before removing EC2 metadata from the system, i.e. to add these fields to the OpenStack metadata, which is not yet available?

I would think adding flavor info to meta_data.json should be trivial. 
It's an API change so it requires a spec though [1].

As for the network addresses, those aren't in network_data.json? Are you 
using neutron?

>> 2. When is it expected that EC2 metadata will be removed from the system?

I wouldn't expect it anytime soon. The documentation that mentions this 
is a warning to not use something that is no longer maintained in nova 
(anything related to ec2), like a deprecation warning of sorts.

If you have identified feature compatibility gaps to close in the 
openstack metadata API, please open a spec for Ussuri detailing what you 
need. Flavor should be pretty easy and the network addresses I would 
expect are already available in network_data.json but if something is 
missing there let's get it documented in the spec.

> Nova's in-tree ec2-api has already been removed [2] (though I can't
> find the commit that did it). That being said, the out-of-tree ec2-api
> project [3] is still around and kicking (just barely, looking at the
> commit history, but it's not inactive).

Mikhail isn't talking about the user-facing EC2 API shim, he's talking 
about the metadata API code [2].

[1] https://specs.openstack.org/openstack/nova-specs/readme.html




More information about the openstack-discuss mailing list