You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by ronald higgins <ro...@gmail.com> on 2013/04/17 09:53:46 UTC
Advice::Cloudstack Configuration for Seperate Storage interface
Heya friendlies.
I need some help wrapping my head around how to configure the storage
network on my deployment. It's the first time I'm trying to split the
traffic types. Previous was a flat network topology.
Below is the physical host configuration:
(RHEL6.4/KVM/CS4)
cloud-manager#>
eth0: 172.18.49.10 (management network) #tagged
eth1: 192.168.251.10 (storage network) #untagged
cloud-host1#>
eth0: 172.18.49.11 (management network) #tagged
eth1: 192.168.251.11 (storage network) #untagged
Both my primary and secondary NFS storage are sitting in the 192.168.251.0
network
pri-storage#> 192.168.251.1
sec-storage#> 192.168.251.2
In the Zone configuration wizard I left the defaults in the Advanced
Networking options.
My logic being that once it get's down to the actual routing the o.s kernel
would handle routing the storage through the correct interface (eth1). This
ended up working for the Primary Storage, but for the Secondary Storage not
so much. The SSVM looks to be trying to route traffic via the 172.18.49.1
gateway.
Is there any special configuration that I need to apply to the networking
on O.S Side to get this working correctly? I read some posts about having
to bridge the networks? Or am I going to have to configure a Storage
Network, VLAN, & Range in the Advanced Wizard? Or both :)
Appreciate any advice :)
Ro
RE: Advice::Cloudstack Configuration for Seperate Storage interface
Posted by Paul Angus <pa...@shapeblue.com>.
Sorry for the delay in replying!
In this case the bridges are being used to allow you to create a 'shared physical device'. Giving you multiple virtual network interface cards.
Regards,
Paul Angus
S: +44 20 3603 0540 | M: +447711418784
paul.angus@shapeblue.com
-----Original Message-----
From: ronald higgins [mailto:ronald.higgins@gmail.com]
Sent: 18 April 2013 20:11
To: users
Subject: Re: Advice::Cloudstack Configuration for Seperate Storage interface
Thanks for all the info Paul.
I must admit that the pieces are not fitting together yet for that "aha"
moment.
I'm not coming to grips with the use of the bridges on the Physical Host itself. In my limited use of bridges it's to connect 2 network segments but in this case I'm befuddled.
physical_host>
eth0: 172.18.49.11 (this is the management network) (untagged/native)
eth1.2000: 192.168.251.11 (this is the host interface in the storage
network) (tagged for VLAN 2000).
What is the function of creating a bridge eg. cloudbr1 which is made up of solely the interface eth1.2000?
Regards
Ronald
On Thu, Apr 18, 2013 at 6:12 PM, Paul Angus <pa...@shapeblue.com>wrote:
> Yes Ronald,
>
> That sounds like you've got it. Remember the CloudStack mgmt. server
> needs to be able to communicate with the secondary storage, so the
> secondary storage needs to be in the same subnet as the CloudStack
> mgmt. server and reachable through eth1 or you need routing in place
> to allow the communication between subnets.
>
> Regards,
>
> Paul Angus
> S: +44 20 3603 0540 | M: +447711418784 paul.angus@shapeblue.com
>
> -----Original Message-----
> From: ronald higgins [mailto:ronald.higgins@gmail.com]
> Sent: 18 April 2013 10:30
> To: users@cloudstack.apache.org
> Subject: Re: Advice::Cloudstack Configuration for Seperate Storage
> interface
>
> Thanks Paul.
>
> I does somewhat, although it feels like the rabbit hole got deeper :)
>
> What I've taken away from the above and is applicable to my setup is that:
>
> Before the CS Installation on the Physical Hosts i'll need to:
>
> A.) Create bridge Cloudbr0-mgmt-guest for the management and guest
> traffic on eth0
> B.) Create bridge Cloudbr1-storage for the storage traffic (primary
> and
> secondary) on eth1
>
> During CS Advanced Wizard:
>
> I'll have to assign MGMT & Guest Traffic to Physical Network 1 and
> label them accordingly.
> Assign Storage to the Physical Network 2 and label it accordingly
>
> In the Storage Network Assignment give CS a range of IP's that will be
> sitting on the same network as the storage (192.168.251.0)
>
> Does this sound vaguely correct and as if I'm on the correct path?
>
> Regards
>
> Ronald
> This email and any attachments to it may be confidential and are
> intended solely for the use of the individual to whom it is addressed.
> Any views or opinions expressed are solely those of the author and do
> not necessarily represent those of Shape Blue Ltd or related
> companies. If you are not the intended recipient of this email, you
> must neither take any action based upon its contents, nor copy or show
> it to anyone. Please contact the sender if you believe you have
> received this email in error. Shape Blue Ltd is a company incorporated
> in England & Wales. ShapeBlue Services India LLP is operated under
> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>
>
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
Re: Advice::Cloudstack Configuration for Seperate Storage interface
Posted by ronald higgins <ro...@gmail.com>.
Thanks for all the info Paul.
I must admit that the pieces are not fitting together yet for that "aha"
moment.
I'm not coming to grips with the use of the bridges on the Physical Host
itself. In my limited use of bridges it's to connect 2 network segments but
in this case I'm befuddled.
physical_host>
eth0: 172.18.49.11 (this is the management network) (untagged/native)
eth1.2000: 192.168.251.11 (this is the host interface in the storage
network) (tagged for VLAN 2000).
What is the function of creating a bridge eg. cloudbr1 which is made up of
solely the interface eth1.2000?
Regards
Ronald
On Thu, Apr 18, 2013 at 6:12 PM, Paul Angus <pa...@shapeblue.com>wrote:
> Yes Ronald,
>
> That sounds like you've got it. Remember the CloudStack mgmt. server needs
> to be able to communicate with the secondary storage, so the secondary
> storage needs to be in the same subnet as the CloudStack mgmt. server and
> reachable through eth1 or you need routing in place to allow the
> communication between subnets.
>
> Regards,
>
> Paul Angus
> S: +44 20 3603 0540 | M: +447711418784
> paul.angus@shapeblue.com
>
> -----Original Message-----
> From: ronald higgins [mailto:ronald.higgins@gmail.com]
> Sent: 18 April 2013 10:30
> To: users@cloudstack.apache.org
> Subject: Re: Advice::Cloudstack Configuration for Seperate Storage
> interface
>
> Thanks Paul.
>
> I does somewhat, although it feels like the rabbit hole got deeper :)
>
> What I've taken away from the above and is applicable to my setup is that:
>
> Before the CS Installation on the Physical Hosts i'll need to:
>
> A.) Create bridge Cloudbr0-mgmt-guest for the management and guest traffic
> on eth0
> B.) Create bridge Cloudbr1-storage for the storage traffic (primary and
> secondary) on eth1
>
> During CS Advanced Wizard:
>
> I'll have to assign MGMT & Guest Traffic to Physical Network 1 and label
> them accordingly.
> Assign Storage to the Physical Network 2 and label it accordingly
>
> In the Storage Network Assignment give CS a range of IP's that will be
> sitting on the same network as the storage (192.168.251.0)
>
> Does this sound vaguely correct and as if I'm on the correct path?
>
> Regards
>
> Ronald
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is
> operated under license from Shape Blue Ltd. ShapeBlue is a registered
> trademark.
>
>
RE: Advice::Cloudstack Configuration for Seperate Storage interface
Posted by Paul Angus <pa...@shapeblue.com>.
Yes Ronald,
That sounds like you've got it. Remember the CloudStack mgmt. server needs to be able to communicate with the secondary storage, so the secondary storage needs to be in the same subnet as the CloudStack mgmt. server and reachable through eth1 or you need routing in place to allow the communication between subnets.
Regards,
Paul Angus
S: +44 20 3603 0540 | M: +447711418784
paul.angus@shapeblue.com
-----Original Message-----
From: ronald higgins [mailto:ronald.higgins@gmail.com]
Sent: 18 April 2013 10:30
To: users@cloudstack.apache.org
Subject: Re: Advice::Cloudstack Configuration for Seperate Storage interface
Thanks Paul.
I does somewhat, although it feels like the rabbit hole got deeper :)
What I've taken away from the above and is applicable to my setup is that:
Before the CS Installation on the Physical Hosts i'll need to:
A.) Create bridge Cloudbr0-mgmt-guest for the management and guest traffic on eth0
B.) Create bridge Cloudbr1-storage for the storage traffic (primary and
secondary) on eth1
During CS Advanced Wizard:
I'll have to assign MGMT & Guest Traffic to Physical Network 1 and label them accordingly.
Assign Storage to the Physical Network 2 and label it accordingly
In the Storage Network Assignment give CS a range of IP's that will be sitting on the same network as the storage (192.168.251.0)
Does this sound vaguely correct and as if I'm on the correct path?
Regards
Ronald
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
Re: Advice::Cloudstack Configuration for Seperate Storage interface
Posted by ronald higgins <ro...@gmail.com>.
Thanks Paul.
I does somewhat, although it feels like the rabbit hole got deeper :)
What I've taken away from the above and is applicable to my setup is that:
Before the CS Installation on the Physical Hosts i'll need to:
A.) Create bridge Cloudbr0-mgmt-guest for the management and guest traffic
on eth0
B.) Create bridge Cloudbr1-storage for the storage traffic (primary and
secondary) on eth1
During CS Advanced Wizard:
I'll have to assign MGMT & Guest Traffic to Physical Network 1 and label
them accordingly.
Assign Storage to the Physical Network 2 and label it accordingly
In the Storage Network Assignment give CS a range of IP's that will be
sitting on the same network as the storage (192.168.251.0)
Does this sound vaguely correct and as if I'm on the correct path?
Regards
Ronald
RE: Advice::Cloudstack Configuration for Seperate Storage interface
Posted by Paul Angus <pa...@shapeblue.com>.
Hi Ronald,
This blog might help you for an overview.
http://www.shapeblue.com/2013/01/07/understanding-cloudstacks-physical-networking-architecture/
Regards,
Paul Angus
S: +44 20 3603 0540 | M: +447711418784
paul.angus@shapeblue.com
-----Original Message-----
From: ronald higgins [mailto:ronald.higgins@gmail.com]
Sent: 17 April 2013 08:54
To: cloudstack-users@incubator.apache.org
Subject: Advice::Cloudstack Configuration for Seperate Storage interface
Heya friendlies.
I need some help wrapping my head around how to configure the storage network on my deployment. It's the first time I'm trying to split the traffic types. Previous was a flat network topology.
Below is the physical host configuration:
(RHEL6.4/KVM/CS4)
cloud-manager#>
eth0: 172.18.49.10 (management network) #tagged
eth1: 192.168.251.10 (storage network) #untagged
cloud-host1#>
eth0: 172.18.49.11 (management network) #tagged
eth1: 192.168.251.11 (storage network) #untagged
Both my primary and secondary NFS storage are sitting in the 192.168.251.0 network
pri-storage#> 192.168.251.1
sec-storage#> 192.168.251.2
In the Zone configuration wizard I left the defaults in the Advanced Networking options.
My logic being that once it get's down to the actual routing the o.s kernel would handle routing the storage through the correct interface (eth1). This ended up working for the Primary Storage, but for the Secondary Storage not so much. The SSVM looks to be trying to route traffic via the 172.18.49.1 gateway.
Is there any special configuration that I need to apply to the networking on O.S Side to get this working correctly? I read some posts about having to bridge the networks? Or am I going to have to configure a Storage Network, VLAN, & Range in the Advanced Wizard? Or both :)
Appreciate any advice :)
Ro
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.