cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-265) Optional Public IP assignment for EIP with Basic Zone
Date Tue, 16 Apr 2013 18:05:15 GMT


ASF subversion and git services commented on CLOUDSTACK-265:

Commit 90e8158db577e4978323510e1faa9ae01a0e7b11 in branch refs/heads/ui-new-project-switcher
from [~murali.reddy]
[;h=90e8158 ]

re-merge optional public IP for EIP service feature

Squashed commit of the following:

commit 2dae394a42a364cd93a11b2c2f74b274b7c43315
Author: Murali Reddy <>
Date:   Tue Apr 16 17:35:28 2013 +0530

    CLOUDSTACK-265: provide option to turn-off automatic public IP association
    for each VM when using EIP service.

      - introduces Capability in the network offering, which decides when EIP
        service is used, by defualt public IP should be assigned to the VM or not

      - default network offering with EIP/ELB service will still work with old
        EIP semantics, i.e) assign a public IP to each VM on start

> Optional Public IP assignment for EIP with Basic Zone
> -----------------------------------------------------
>                 Key: CLOUDSTACK-265
>                 URL:
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.0.0, 4.1.0
>            Reporter: Murali Reddy
>            Assignee: Murali Reddy
>             Fix For: 4.2.0
> Current EIP in CloudStack has below semantics.
>    - When a user VM is deployed, a public ip is automatically acquired. This IP is owned
by the vm's        account and is marked as 'system' in the db.
>    - When the user VM starts, static NAT is provisioned on the static NAT provider between
the public ip and the guest ip of the vm.
> Since public IP's can be scarce resource is some deployments, its not desirable to allocate
a public IP by default. This bug is to provide the flexibility for cloud providers to enable/disable
the ability to automatically allocate public IP. 
> Release Planning:
> Dev List Discussion:
> Functional Spec:
> Feature Branch: master

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message