cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yiting Wu <yting...@gmail.com>
Subject Re: Cloudstack 4.0.1 with VCenter 5.1
Date Fri, 18 Jan 2013 11:14:09 GMT
I've success configure Cloudstack 4.0.1 with vCenter 5.1 finally!!!

I use basic network mode with only one physical network.
I configured Guest VMware traffic label as vSwitch0,83;
and management/storage VMware traffic label as vSwitch0,55;

This is very tricky, cloudstack automatically generate the real network
group name based on what you provided.
eg: vSwitch0,83 will created a portgroup
name: cloud.guest.83.200.1-vSwitch0 with vlan 83 configured in vcenter.

I haven't try whether it may work or not to directly provide the portgroup
name as traffic label.
VMware traffic labelvSwitch0,83
But there are still some tricky issues:
1. if you stop a vm(not reboot), and restart it, cloudstack will
automatically re-configure the vm with network port group:
cloud.guest.untagged.200.1-vSwitch0,
even this group doesn't exist, it will create it..
2. the virtual router has the same behavior, if you have system vms use
wrong port group, simply delete it, and cloudstack will recreate them, that
fix my problem
3. after setup, my management node could not ssh into virtual router, in
this case, you may have to update your system iso to the system vm, you may
have the wrong public key there.

I will spend more time to write a detail wiki for vmware setup. hope that
would help someone like me, strungle a longtime with vCenter configuration.
The only thing that would benefit is you become more familiar with
cloudstack when you finally resolve it.

Thanks,
Yiting


On Thu, Jan 17, 2013 at 4:26 PM, Paul Angus <paul.angus@shapeblue.com>wrote:

> Hi Jerry,
>
> Guest and management networks can (and should) be connected to different
> interfaces in a basic zone and by extension they then can be on different
> VLANs within your network.  However basic networks don't do tagged VLANs so
> your VLANs would need to be created as access ports on your switch.
>
> Have a look at a recent blog on physical networking in CloudStack
>
> 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: Jerry Jiang [mailto:jerry.jiang@tyxtech.com]
> Sent: 17 January 2013 01:22
> To: cloudstack-users@incubator.apache.org
> Subject: 答复: Cloudstack 4.0.1 with VCenter 5.1
>
> I met same issue regarding deployment of CS with vlan.
>
> Jerry jiang
>
> -----邮件原件-----
> 发件人: Yiting Wu [mailto:yting.wu@gmail.com]
> 发送时间: 2013年1月16日 星期三 11:34
> 收件人: cloudstack-users@incubator.apache.org
> 主题: Cloudstack 4.0.1 with VCenter 5.1
>
> I got some trouble install cloudStack 4.0.1 with VCenter 5.1.
>
> But could not find detail documentation about it yet.
>
> Problems as below:
> Our esxi are in vlan 55(Management Network), and Guest network in vlan 83.
>
>  I've tried Basic network Zone, 2 system vms can be setuped with console
> available, but can't deploy vm. Later I found there is statement in doc
> "Guest and host should in the same vlan for basic zone".
>
> so I try to deploy with Advance Network Zone, this time, it's even tricky.
> system vm could not setup...
>
> If there anyone can provide a detail tutorial about how to setup VCenter
> with CloudStack with vlan?
>
>
> --
>
> Thanks,
>
> Yiting, Wu
>
>
> ShapeBlue provides a range of strategic and technical consulting and
> implementation services to help IT Service Providers and Enterprises to
> build a true IaaS compute cloud. ShapeBlue’s expertise, combined with
> CloudStack technology, allows IT Service Providers and Enterprises to
> deliver true, utility based, IaaS to the customer or end-user.
>
> ________________________________
>
> 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. 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.
>



-- 

Thanks,

Yiting, Wu

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