EC2 API supports deprecated authorize and revoke methods, and not recommended methods

I think it matches what Boto 1.9 uses, which is apparently not the latest.

Though it apparently still matches what Amazon recommends to do:
http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/index.html?using-network-security.html

I love how that method is deprecated, but they still recommend its use.

I guess I'll keep this low priority in my attempts to add support.

boto-2.0b4 no more works with nova-api since
boto commit e94096d7aeb803ea69947fd722ce4ca2aa969cff
Author: Mitch Garnaat <email address hidden>
Date: Tue Nov 16 08:39:47 2010 -0500

nova/api.log has
(nova.api): TRACE: File "/usr/lib64/python2.6/site-packages/nova/api/ec2/cloud.py", line 473, in authorize_security_group_ingress
(nova.api): TRACE: values = self._revoke_rule_args_to_dict(context, **kwargs)
(nova.api): TRACE: TypeError: _revoke_rule_args_to_dict() got an unexpected keyword argument 'ip_permissions'

euca-authorize -P tcp -p 22 default
just writes
UnknownError: An unknown error has occurred. Please try your request again.

Raising importance

euca2ools also depends on boto , so if you upgrade boto to any variant of 2.0x, that changes the authorize and revoke methods to use the IpPermissions data structure upon submission.

Bernhard, therefore your euca2ools will work if you revert back to boto1.9x.

Thierry, I'm playing w/ the nova api code so that it supports the IpPermissions, however, should I keep in consideration for the methods to be backwards compatible w/ the deprecated data structure? If I make the method only support the IpPermission structure, that means anyone w/ boto1.9 will have problems.

I've submitted a blueprint to propose upgrading to boto2.0x. https://blueprints.launchpad.net/nova/+spec/upgrade-to-boto2.0

I thought about this again , and considered that since the eucatools I was testing against nova was on the same box, I made the wrong assumption that boto needed to be upgraded on the nova side but I understand now that the boto upgrade only affects the client. I've created a branch that modifies the authorize & revoke ingress methods to accomodate either the deprecated method of params or the new aws spec'd method.

@John, It surely does need to be upgraded on the nova side for the test suite to pass?

Thanks.

Dave, it shouldn't need to upgrade boto on the nova side.