deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sang-Min Park <sang-min.p...@eucalyptus.com>
Subject Re: firewall support for ec2 instances
Date Sat, 25 Jun 2011 12:49:39 GMT
FYI, I looked at the firewall implementation and found that there's an issue
with Eucalyptus driver.
Eucalyptus supports the old parameter convention in
'AuthorizeSecurityGroupIngress' action. I'll try if I can patch AWS to
generate the old parameters as well as the new one.

Sang-min



On Fri, Jun 17, 2011 at 8:06 AM, <marios@redhat.com> wrote:

>
> This patch uses the new 'Firewalls' collection (I pushed that to trunk
> today).
> The create_instance operation for the ec2 driver takes an array of firewall
> names
> for the instance to be 'launched into'. Patch includes:
>
> * necessary modifications to server.rb
> * addition of 'firewalls' to the Instance model
> * modification of the haml views: html for the create operation, html/xml
> for showing
>  firewalls when inspecting a given instance.
>
> If you aren't using the html interface to create an instance, you can
> specify
> firewalls using form input : 'firewall#=name' where '#' is any digit.  For
> example:
>
> curl -F 'image_id=ami-48aa4921' -F 'firewalls1=default' -F
> 'firewalls2=test'
>  --user 'ec2_key:ec2_password'
> http://localhost:3001/api/instances?format=xml
>
> will create an instance from ami-48aa4921 and place it into firewalls
> 'default'
> and 'test'. EC2 does not support 'moving' an instance between firewalls
> once it's
> launched so this functionality was not implemented
> (http://aws.amazon.com/articles/1145?_encoding=UTF8&jiveRedirect=1#13)
>
> marios
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message