http://www.slideshare.net/ShapeBlue/cloud-stack-networking-shapeblue-techni
cal-deep-dive
On 8/13/13 10:32 PM, "Mark van der Meulen" wrote:
>Does anyone have links to a more comprehensive design or implementation
>guide?
>
>Doco is vague at best, and that slideshow is hardly helpful when it co
Does anyone have links to a more comprehensive design or implementation guide?
Doco is vague at best, and that slideshow is hardly helpful when it comes to
implementation.
Mark
On 14/08/2013, at 10:23 AM, Ahmad Emneina wrote:
> True, you can have a shared network with public ips, that way vm'
2013/8/14 Chiradeep Vittal
> Actually this is not quite true. You can design a network offering with no
> NAT or firewall services and give a public range of ips for the network.
> Or you (the admin) can utilize the default 'shared network' offering to
> create a similar network on a specific VLA
True, you can have a shared network with public ips, that way vm's get
public ip's assigned to them directly on launch.
On Tue, Aug 13, 2013 at 3:47 PM, Chiradeep Vittal <
chiradeep.vit...@citrix.com> wrote:
> http://www.slideshare.net/cloudstack/cloudstack-networking (slides 17 and
> 18)
>
> On
http://www.slideshare.net/cloudstack/cloudstack-networking (slides 17 and
18)
On 8/13/13 3:44 PM, "Chiradeep Vittal" wrote:
>Actually this is not quite true. You can design a network offering with no
>NAT or firewall services and give a public range of ips for the network.
>Or you (the admin) ca
Actually this is not quite true. You can design a network offering with no
NAT or firewall services and give a public range of ips for the network.
Or you (the admin) can utilize the default 'shared network' offering to
create a similar network on a specific VLAN.
On 8/13/13 7:03 AM, "Nguyen Anh
2013/8/13 Mark van der Meulen
> Are you saying that the only way CloudStack supports public(read: networks
> outside immediate pod) access is via NAT? Can I not give the VM's publicly
> routable IP's(or equivalent for the network)?
Hi Mark,
At the moment Cloudstack only supports public access
ad Emneina [mailto:aemne...@gmail.com]
Sent: Tuesday, August 13, 2013 1:28 AM
To: Cloudstack users mailing list
Subject: Re: understanding cloudstack networking
>>Based on what I have read, I think I would like to setup a Public Cloud,
essentially some hypervisors on a private network(lets say 10
>>Based on what I have read, I think I would like to setup a Public Cloud,
essentially some hypervisors on a private network(lets say 10.1.254.0/24)
and storage on another network(let's say10.1.253.0/24) and then all the
VM's given public IP's(let's say 200.10.10.0/24). I don't understand how to
do
sounds great Ron,
I'm sure I am not the guy you need for this but I'll keep an eye on
it. The 'someone who actually knows what it s supposed to say' is
bound to be around on this list or dev.
regards,
Daan
On Mon, Aug 12, 2013 at 4:55 PM, Ron Wheeler
wrote:
> I have been reading and correcting
I have been reading and correcting the posted 4.2 documentation changes
that I understand or where the English errors are very clear.
I have filed JIRAs and some have been fixed.
I would be willing to participate in a workshop to walk through the
installation with someone who actually knows wh
you are right Ron, but even those companies/people can only spend
their time once. So please submit you improvements whenever you can.
regards,
Daan
On Mon, Aug 12, 2013 at 4:32 PM, Ron Wheeler
wrote:
> On 12/08/2013 10:08 AM, Travis Graham wrote:
>>
>> One of the most confusing things I've ran
On 12/08/2013 10:08 AM, Travis Graham wrote:
One of the most confusing things I've ran into, past the fact the documentation
is wrong about 80% of the time, is the mix of CentOS and Ubuntu instructions.
I think splitting things out into their own OS specific install guides would
reduce a lot o
One of the most confusing things I've ran into, past the fact the documentation
is wrong about 80% of the time, is the mix of CentOS and Ubuntu instructions.
I think splitting things out into their own OS specific install guides would
reduce a lot of confusion.
I was browsing the 4.2 docs in th
The documentation is wrong which is a big problem.
It is also confusing with extraneous stuff stuck in the middle and
missing introductory information to explain where the instructions are
leading.
There seems to be a big effort to get 4.2 out with accurate docs and I
hope more clarifying te
15 matches
Mail list logo
