That's what I figured.  We were hoping to be able to set up
site-to-site VPN on the existing network.  If a VPC is just a supernet
to multiple virtual routers it seems like it would be feasible to
seamlessly add an existing network/VR to a VPC.

Since this isn't possible now I guess opening a feature request for it
would be good, in case we run into a similar issue next year.  Before
I do, does anyone know if this is technically possible, just not yet
coded?  In other words, could I theoretically add an existing isolated
network/VR to a VPC seamlessly via updating the database or manually
changing something on the VR?  If so I would think adding the code to
handle that task would be relatively easy.

Thank You,

Logan Barfield
Tranquil Hosting


On Wed, Apr 1, 2015 at 3:20 AM, Sanjeev N <sanj...@apache.org> wrote:
> As Erik mentioned, we can add nic from VPC network to existing vms so the
> vms will be in both isolated(non-vpc) and vpc networks.
>
> On Wed, Apr 1, 2015 at 11:56 AM, Erik Weber <terbol...@gmail.com> wrote:
>
>> Haven't tried it myself, but i think you should be able to create the vpc
>> and change nic on VMs.
>>
>> If you want to keep the ip addresses you might have to use the api
>>
>> Erik
>>
>> Den onsdag 1. april 2015 skrev Logan Barfield <lbarfi...@tqhosting.com>
>> følgende:
>>
>> > We have a customer that is currently set up in an isolated network in
>> > an advanced zone.  They recently mentioned that they have a need for
>> > site-to-site VPN connectivity for their application.
>> >
>> > Is it possible to move an existing isolated network into a VPC for
>> > site-to-site VPN functionality?  Or is there another way to set up a
>> > site-to-site VPN using the existing network?
>> >
>> >
>> > Thank You,
>> >
>> > Logan Barfield
>> > Tranquil Hosting
>> >
>>

Reply via email to