cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From linuxsupport <lin.supp...@gmail.com>
Subject Re: Cloudstack 4.0 networking
Date Thu, 27 Dec 2012 09:30:43 GMT
OK, I labeled the different network (mgmt, vm) in basic networking to
cloudbr0 and cloudbr1 and this worked well.

I am able to ping both public and private IP addresses.

But encountered another problem where it is creating another interface for
storage inside vm, I saw in secondary storage VM where it configured 4
interfaces.
eth0 -> local link
eth1 -> public IP
eth2 -> private ip
eth3 -> private ip

eth2 and eth3 both have an IP address from the private subnet,
192.168.64.103 and 192.168.64.104

I can access 192.168.64.103 but not to 192.168.64.104

It seems it is using eth3 (192.168.64.104) for storage and since managament
is not able to communicate with the storage vm on this IP, it keep saying
in log as below

Zone 1 is ready to launch secondary storage VM (keep repeating after
sometime)

while VM is up and I am able to access it.

Any thoughts on it?

Is it possible to make it use eth2 (192.168.64.103) for storage as well?

Thanks

On Thu, Dec 27, 2012 at 5:41 AM, Edison Su <Edison.su@citrix.com> wrote:

> You can try basic network with a little hack:
> 1. install cloudstack mgt server and kvm agent as normal, add the kvm host
> into cloudstack, without any extra configuration for network.
>     By default, cloudstack will create a bridge, called cloudbr0,  on your
> kvm host. The bridge is created on the gateway device(ip route|grep
> default|awk '{print $5}')
> 2. Then disable the zone, so no vm will be created.
> 3. manually create another bridge on the device which is not gateway
> device.
> 4. modify /etc/cloud/agent/agent.properties, set
> {guest,private,public}.network.device properly.
> For example, if cloudbr0 is created on eth0(which is your public network),
> and cloudbr1 is created on eth1(which is your private network), set
> guest.network.device=cloudbr1
> private.network.device=cloudbr1
> public.network.device=cloudbr0
> 5. restart cloud agent by "service cloud-agent restart"
> 6. enable the zone, everything should work as planned.
>
> > -----Original Message-----
> > From: linuxsupport [mailto:lin.support@gmail.com]
> > Sent: Wednesday, December 26, 2012 2:48 AM
> > To: cloudstack-users@incubator.apache.org
> > Subject: Cloudstack 4.0 networking
> >
> > Hi All,
> >
> > I am new to CloudStack, I have installed version 4 on CentOS 6.3
> >
> > Management node is a virtual machine, with 2 interfaces one for public
> and
> > other for private network
> >
> > eth0 => public
> > eth1 -> private
> >
> > Host machine in which management VM is running is a Xen host with 2
> > physical interfaces, eth0 and eth1, both eth0 and eth1 have a respective
> > bridge setup and this is working.
> >
> > I have another machine which is KVM host with cloud-agent (CentOS 6.3)
> >
> > KVM machine also have 2 physical interfaces eth0 and eth1, eth0 has a
> public
> > IP and eth1 has private IP (192.168.1.100)
> >
> > Now, I want that all the communication for management, storage and guest
> > to guest happen through eth1 and for internet use eth0
> >
> > Can someone guide me to configure networking correctly?
> >
> > If I use basic networking then it does not allow me to use eth1 and if I
> use
> > advance networking then it asks for VLANs, I tried to configure VLANs
> > interfaces on eth1 but it did not work, may be because I have no control
> on
> > switches provider has their own VLAN for public and private which I am
> not
> > aware about it.
> >
> > Please help me to find right way.
> >
> > Thanks
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message