yahoo-eng-team team mailing list archive

["Davanum Srinivas \(DIMS\)" <davanum@xxxxxxxxx>]

** Changed in: nova
       Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1371445

Title:
  Nova EC2 doesn't assign a floating IP to an instance being launched

Status in ec2-api:
  Confirmed
Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  In EC2 classic mode AWS automatically associates a public IP address
  to an instance being launched. See
  http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-
  addressing.html#differences

  Since Nova EC2 emulates EC2 classic mode of AWS (there is no VPC
  support in Nova EC2), it should associate a floating IP as well. But
  it doesn't do this.

  Though Nova has auto_assign_floating_ip parameter which does work
  similar AWS. But it isn't implemented for Neutron networks. And it
  affects both methods of running: EC2 and native Nova. Thus if we want
  a cloud to be AWS compatible, and we use this parameter, we change
  behavior of Nova in it's native part. This may be not desirable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ec2-api/+bug/1371445/+subscriptions