You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Introduction

Purpose

Document History

References

Scope & Assumptions

Semantic differences from AWS EIP

Functional requirements & non-requirements

  • introduce notion of 'EIP' pool that will be associated with a region
  • Admin be able to add, delete, list the entries/range in to the EIP pool
  • Users be able to acquire, release, associate, disassociate, transfer and list EIP's
  • Users be able to associate EIP with any VM in either basic or advanced zone
  • Support for NetScaler as EIP service provider is P1, VR is P2, but the design should be generic so any NAT provider can be enhanced to act of EIP service provider
  • When EIP is transferred from VM in a zone to VM in another zone, CloudStack will not be responsible for the actual router advertisements but will provide a ways (alert, event etc) on which admin can act up on
  • no support for the VPC

Detailed Design

API

Schema changes

Action Events

Usage events

Upgrade

Risk/Open Issues 

  • No labels