[
https://issues.apache.org/jira/browse/CLOUDSTACK-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chip Childers updated CLOUDSTACK-265:
-------------------------------------
Description:
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: http://markmail.org/message/b2h2cw62qnryk4qh
Functional Spec:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Optional+Public+IP+assignment+for+EIP+with+Basic+Zone?moved=true
Feature Branch: master
was:
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.
Issue Type: New Feature (was: Improvement)
Summary: Optional Public IP assignment for EIP with Basic Zone (was:
provide option to turn-off automatic public IP association for each VM when
using EIP service.)
> Optional Public IP assignment for EIP with Basic Zone
> -----------------------------------------------------
>
> Key: CLOUDSTACK-265
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-265
> 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.1.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: http://markmail.org/message/b2h2cw62qnryk4qh
> Functional Spec:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Optional+Public+IP+assignment+for+EIP+with+Basic+Zone?moved=true
> 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: http://www.atlassian.com/software/jira
