Thanks Marty, I just needed confirmation of my work, I deployed CS 4.0.0. (from not knowing what it is, till fully operational and used in kind of production) in less than 15 days...so lot of stuff was done in kind of rush, but got 99% of networkng understood then. Now, 9 months later, I got that 1% I missed :)
Thanks On 22 October 2013 21:04, Marty Sweet <msweet....@gmail.com> wrote: > Hi Andrija, > > Your setup seems fine to me, I am not sure why you would want to get rid of > VLANs as it provides the flexibility you require when it comes to isolated > public/private networking all on the same infrastructure. > I run a shared network for our 'Public' addresses, on a set VLAN and also > have other vlans for certain servers for private networks, just like yours. > I hope that answers your question. > > Marty > > > On Tue, Oct 22, 2013 at 7:20 PM, Andrija Panic <andrija.pa...@gmail.com > >wrote: > > > Or to post question other way: > > > > The only way to make public IP addresses available to VMs directly (call > it > > VPS style) (without VR), is using "guest network (bind it to ethX/bridgeX > > that has direct internet access) and create shared network offer... as I > > already done ? > > > > > > > > > > On 22 October 2013 18:09, Andrija Panic <andrija.pa...@gmail.com> wrote: > > > > > Hi, > > > > > > I have one question on "public network", used in Advance networking > > > scenario. > > > > > > As I understood from documentation, "Public network" is only used by > > > system VMs, and assigned to the public interface on VR(s). > > > What is recommended way if I want public IP address to be assigned to > > some > > > user VMs? I'm not deploying VR for customer VMs, just kind of "VPS" > VM... > > > > > > I have done the folowing, and wonder if this is good/correct method - > it > > > is working fine for now. > > > > > > In order to have public IPs assigned to single VM - I had to use > another > > > guest network with vlan tagged packets (so, I have one guest network, > > with > > > vlans 40-50 on eth0 for private IP range communication between VMs > (each > > > account get it's own vlan ID from range 40-60), and I HAD to have vlan > > 500 > > > on eth1, on HOST. > > > > > > Then I deployed new Shared Network inside CS UI, with vlan 500 (that > can > > > be assigned to all acount VMs, in order to have public IP and direct > > > internet access), and CS created bridge cloudVrBb500, and joing > eth1.500 > > to > > > that network... > > > > > > So, any other solution to have normal VMs get public IP address from > > > public IP range without using vlans for that guest network ??? > > > > > > Thanks, > > > -- > > > > > > Andrija Panić > > > > > > > > > > > > -- > > > > Andrija Panić > > -------------------------------------- > > http://admintweets.com > > -------------------------------------- > > > -- Andrija Panić -------------------------------------- http://admintweets.com --------------------------------------
