You have to unsubscribe yourself,  check the link

http://cloudstack.apache.org/mailing-lists.html


> -----Original Message-----
> From: 김현일(Infra센터) [mailto:hyunil....@kt.com]
> Sent: Friday, March 22, 2013 2:19 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [PROPOSAL] EIP across zones
> 
> Hi
> 
> I don't want to recive this mail any more.
> 
> Thank you for your helpful tips and advices.
> 
> best regards.
> 
> -----Original Message-----
> From: Murali Reddy [mailto:murali.re...@citrix.com]
> Sent: Friday, March 22, 2013 5:34 PM
> To: Manan Shah; dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] EIP across zones
> 
> On 22/03/13 9:37 AM, "Manan Shah" <manan.s...@citrix.com> wrote:
> 
> >My assumption is that EIP for VPC should work exactly the same as EIP
> >for Isolated Networks since EIP is like another Public IP except that
> >it can be moved across zones. Also, we do support static NAT in VPC as
> >well as Isolated. So, my thinking is that it might just work with minimal
> effort.
> 
> It might not just work. I can think of questions like, can I move the EIP 
> across
> the tiers in VPC? Since cloudStack can not have tier's of VPC in multiple
> zones, question of moving across zones does not arise? Does EIP service
> provider and 'public gateway' need to be same? Does network ACL's has any
> impact? Etc.
> 
> It would take significant time to think through the scenarios, tweak the
> existing VPC functionality to adapt to EIP, write unit test, marvin test.
> Also QA effort for EIP in isolated network won't be same for VPC.
> 
> >
> >Regards,
> >Manan Shah
> 
> 
> 
> 
> 이 메일은 지정된 수취인만을 위해 작성되었으며, 중요한 정보나
> 저작권을 포함하고 있을 수 있습니다. 어떠한 권한 없이, 본 문서에
> 포함된 정보의 전부 또는 일부를 무단으로 제3자에게 공개, 배포, 복사
> 또는 사용하는 것을 엄격히 금지합니다. 만약, 본 메일이 잘못 전송된
> 경우, 발신인 또는 당사에 알려주시고, 본 메일을 즉시 삭제하여 주시기
> 바랍니다.
> This E-mail may contain confidential information and/or copyright material.
> This email is intended for the use of the addressee only. If you receive this
> email by mistake, please either delete it without reproducing, distributing or
> retaining copies thereof or notify the sender immediately.

Reply via email to