Is it possible to organize such a virtual network?

Question

linux

Hello!
I need help building a virtual network.
There is a server with 2 static ip and one dedicated ipv6/64 subnet. but with only one network interface eth0. Openvswitch and kvm are also present. and two domains, one of which also has startSSL.
The server will have either debian wheezy + proxmox or ubuntu 14.10 with opennebula It is
necessary that:
1) the first ipv4 be assigned to the server and used for administrative purposes.
2) the ipv6 network was distributed between the server and the virtual machines
3) the second ipv4 should be assigned to the virtual machine that proxies all requests from this ip to a specific virtual machine in the 10.0.0.0 virtual grid depending on the domain. Including ssh.
If at all possible, please advise how. Also, if there is info on the topic in Russian or English - skinte links please.

Answer 1

Throw eth0 into a separate bridge, hang the first address on the internal port of the host.
Then, in the virtual machine, make a second network card, attach it to this new bridge and assign a second address to it. Let the first network look into the gray subnet of another bridge.
If you want to dig, but more beautifully - use one openvswitch bridge broken down into vlans. Then you will have a vlan for a gray network, other guests get just an accessport of this vlan, a guest with a white address gets a trunk with two vlans. For the host, you make an internal vlan access port with external ares, include eth0 in the same vlan as an access port. PS: " will be
on the server ". Time will be why not debian jessie? Release in a week and then do not bathe with the update.

Answer 2

If I understood everything correctly, then
1) The simplest, an IP address is assigned to the external interface, as is always done.
2) You need a second interface (at least real, at least virtual, but separate), to which you assign an address from the IPv6 subnet. It will be GW for all other hosts on this subnet.
3) Why do we need a proxying virtual machine? It is necessary to assign a second white address to a "specific" machine. Here's a nuance, I'm not sure what will work, you need to check.
About SSL, you need to understand that each domain (certificate) needs a separate IP, provided that both work on port 443.