Jump to: navigation, search

Difference between revisions of "Auto-floating-ip"

 
Line 14: Line 14:
  
 
== User stories ==
 
== User stories ==
Eldar is going to create the best one SaaS app. He will deploy his app to AWS EC2. But he don't want to spent a lot of money on development stage. He is using [[OpenStack]] with AWS API and want to emulate AWS EC2 behavior, including public ip assignment for each instance.
+
Eldar is going to create the best one SaaS app. He will deploy his app to AWS EC2. But he doesn't want to spend a lot of money on development stage. He is using [[OpenStack]] with AWS API and wants to emulate AWS EC2 behavior, including public ip assignment for each instance.
  
Dmitry want to use [[OpenStack]] API for his SaaS app. He use vlan network and he need public ip for each his instance.
+
Dmitry wants to use [[OpenStack]] API for his SaaS app. He uses vlan network and he needs public ip for each his instance.
  
 
== Assumptions ==
 
== Assumptions ==

Revision as of 17:39, 18 April 2011

  • Launchpad Entry: NovaSpec:floating-ip-auto-assignment
  • Created: Ilya Alekseyev
  • Contributors: Ilya Alekseyev

Summary

Auto assigning floating ip address to instance when instance is starting.

Release Note

Provide option of auto assigning floating ip to each instance. Depend on auto_assign_floating_ip boolean flag value. False by default.

Rationale

User stories

Eldar is going to create the best one SaaS app. He will deploy his app to AWS EC2. But he doesn't want to spend a lot of money on development stage. He is using OpenStack with AWS API and wants to emulate AWS EC2 behavior, including public ip assignment for each instance.

Dmitry wants to use OpenStack API for his SaaS app. He uses vlan network and he needs public ip for each his instance.

Assumptions

Design

Implementation

UI Changes

Code Changes

Migration

Added column auto_assigned to floating_ips table.

Test/Demo Plan

Unresolved issues

BoF agenda and discussion