You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Simon Murphy <si...@vifx.co.nz> on 2013/11/25 03:02:03 UTC

ACS 4.2.1 - Multi-Zone vSphere Architecture

Hi all,

Im after some guidance on setting up ACS 4.2.1 with vSphere in a multi zone environment. The only way I have been able to successfully build a zone to this point is by having vSphere, ESXi console ports, ACS and the reserved system range on a single VLAN. This is OK for a small, single site deployment but how does this translate for multiple zones? The docs suggest that configuring a single /20 range for management is desired, does that imply that that range should be stretched across sites?

Should it be possible to have a dedicated VLAN at each site for vCenter, ESXi console ports and the system VM's, and then have the ACS server sitting in a separate VLAN that can route between both networks? I have been unsuccessful in getting his working to date so hopefully someone out there has some experience setting up a multi-site ACS/vSphere envoronment.

Any guidance would be greatly appreciated!


Simon Murphy
Solutions Architect

ViFX | Cloud Infrastructure
Level 7, 57 Fort Street, Auckland, New Zealand 1010
PO Box 106700, Auckland, New Zealand 1143
M +64 21 285 4519 | S simon_a_murphy
www.vifx.co.nz<http://www.vifx.co.nz/> follow us on twitter<https://twitter.com/ViFX>
Auckland | Wellington | Christchurch

[cid:image003.jpg@01CDDF95.815BF160]

experience. expertise. execution.

This email and any files transmitted with it are confidential, without prejudice and may contain information that is subject to legal privilege. It is intended solely for the use of the individual/s to whom it is addressed in accordance with the provisions of the Privacy Act (1993). The content contained in this email does not, necessarily, reflect the official policy position of ViFX nor does ViFX have any responsibility for any alterations to the contents of this email that may occur following transmission. If you are not the addressee it may be unlawful for you to read, copy, distribute, disclose or otherwise use the information contained within this email. If you are not the intended recipient, please notify the sender prior to deleting this email message from your system. Please note ViFX reserves the right to monitor, from time to time, the communications sent to and from its email network.

RE: ACS 4.2.1 - Multi-Zone vSphere Architecture

Posted by Simon Murphy <si...@vifx.co.nz>.
thanks. i found the management.cidr global setting that needs to be set to make the setup work.

Sent from my Android phone using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: Sanjeev Neelarapu [sanjeev.neelarapu@citrix.com]
Received: Wednesday, 27 Nov 2013, 6:12pm
To: users@cloudstack.apache.org [users@cloudstack.apache.org]; dev@cloudstack.apache.org [dev@cloudstack.apache.org]
Subject: RE: ACS 4.2.1 - Multi-Zone vSphere Architecture

Hi,

It is not mandatory to use single dedicated vlan in a multi zone environment. It is possible to have a dedicated VLAN at each site for vCenter, ESXi console ports and the system VM's, and then have the ACS server sitting in a separate VLAN that can route between both networks.

Thanks,
Sanjeev

From: Simon Murphy [mailto:simon.Murphy@vifx.co.nz]
Sent: Monday, November 25, 2013 7:32 AM
To: users@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: ACS 4.2.1 - Multi-Zone vSphere Architecture

Hi all,

Im after some guidance on setting up ACS 4.2.1 with vSphere in a multi zone environment. The only way I have been able to successfully build a zone to this point is by having vSphere, ESXi console ports, ACS and the reserved system range on a single VLAN. This is OK for a small, single site deployment but how does this translate for multiple zones? The docs suggest that configuring a single /20 range for management is desired, does that imply that that range should be stretched across sites?

Should it be possible to have a dedicated VLAN at each site for vCenter, ESXi console ports and the system VM's, and then have the ACS server sitting in a separate VLAN that can route between both networks? I have been unsuccessful in getting his working to date so hopefully someone out there has some experience setting up a multi-site ACS/vSphere envoronment.

Any guidance would be greatly appreciated!


Simon Murphy
Solutions Architect

ViFX | Cloud Infrastructure
Level 7, 57 Fort Street, Auckland, New Zealand 1010
PO Box 106700, Auckland, New Zealand 1143
M +64 21 285 4519 | S simon_a_murphy
www.vifx.co.nz<http://www.vifx.co.nz/> follow us on twitter<https://twitter.com/ViFX>
Auckland | Wellington | Christchurch

[cid:image003.jpg@01CDDF95.815BF160]

experience. expertise. execution.

This email and any files transmitted with it are confidential, without prejudice and may contain information that is subject to legal privilege. It is intended solely for the use of the individual/s to whom it is addressed in accordance with the provisions of the Privacy Act (1993). The content contained in this email does not, necessarily, reflect the official policy position of ViFX nor does ViFX have any responsibility for any alterations to the contents of this email that may occur following transmission. If you are not the addressee it may be unlawful for you to read, copy, distribute, disclose or otherwise use the information contained within this email. If you are not the intended recipient, please notify the sender prior to deleting this email message from your system. Please note ViFX reserves the right to monitor, from time to time, the communications sent to and from its email network.

RE: ACS 4.2.1 - Multi-Zone vSphere Architecture

Posted by Simon Murphy <si...@vifx.co.nz>.
thanks. i found the management.cidr global setting that needs to be set to make the setup work.

Sent from my Android phone using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: Sanjeev Neelarapu [sanjeev.neelarapu@citrix.com]
Received: Wednesday, 27 Nov 2013, 6:12pm
To: users@cloudstack.apache.org [users@cloudstack.apache.org]; dev@cloudstack.apache.org [dev@cloudstack.apache.org]
Subject: RE: ACS 4.2.1 - Multi-Zone vSphere Architecture

Hi,

It is not mandatory to use single dedicated vlan in a multi zone environment. It is possible to have a dedicated VLAN at each site for vCenter, ESXi console ports and the system VM's, and then have the ACS server sitting in a separate VLAN that can route between both networks.

Thanks,
Sanjeev

From: Simon Murphy [mailto:simon.Murphy@vifx.co.nz]
Sent: Monday, November 25, 2013 7:32 AM
To: users@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: ACS 4.2.1 - Multi-Zone vSphere Architecture

Hi all,

Im after some guidance on setting up ACS 4.2.1 with vSphere in a multi zone environment. The only way I have been able to successfully build a zone to this point is by having vSphere, ESXi console ports, ACS and the reserved system range on a single VLAN. This is OK for a small, single site deployment but how does this translate for multiple zones? The docs suggest that configuring a single /20 range for management is desired, does that imply that that range should be stretched across sites?

Should it be possible to have a dedicated VLAN at each site for vCenter, ESXi console ports and the system VM's, and then have the ACS server sitting in a separate VLAN that can route between both networks? I have been unsuccessful in getting his working to date so hopefully someone out there has some experience setting up a multi-site ACS/vSphere envoronment.

Any guidance would be greatly appreciated!


Simon Murphy
Solutions Architect

ViFX | Cloud Infrastructure
Level 7, 57 Fort Street, Auckland, New Zealand 1010
PO Box 106700, Auckland, New Zealand 1143
M +64 21 285 4519 | S simon_a_murphy
www.vifx.co.nz<http://www.vifx.co.nz/> follow us on twitter<https://twitter.com/ViFX>
Auckland | Wellington | Christchurch

[cid:image003.jpg@01CDDF95.815BF160]

experience. expertise. execution.

This email and any files transmitted with it are confidential, without prejudice and may contain information that is subject to legal privilege. It is intended solely for the use of the individual/s to whom it is addressed in accordance with the provisions of the Privacy Act (1993). The content contained in this email does not, necessarily, reflect the official policy position of ViFX nor does ViFX have any responsibility for any alterations to the contents of this email that may occur following transmission. If you are not the addressee it may be unlawful for you to read, copy, distribute, disclose or otherwise use the information contained within this email. If you are not the intended recipient, please notify the sender prior to deleting this email message from your system. Please note ViFX reserves the right to monitor, from time to time, the communications sent to and from its email network.

RE: ACS 4.2.1 - Multi-Zone vSphere Architecture

Posted by Sanjeev Neelarapu <sa...@citrix.com>.
Hi,

It is not mandatory to use single dedicated vlan in a multi zone environment. It is possible to have a dedicated VLAN at each site for vCenter, ESXi console ports and the system VM's, and then have the ACS server sitting in a separate VLAN that can route between both networks.

Thanks,
Sanjeev

From: Simon Murphy [mailto:simon.Murphy@vifx.co.nz]
Sent: Monday, November 25, 2013 7:32 AM
To: users@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: ACS 4.2.1 - Multi-Zone vSphere Architecture

Hi all,

Im after some guidance on setting up ACS 4.2.1 with vSphere in a multi zone environment. The only way I have been able to successfully build a zone to this point is by having vSphere, ESXi console ports, ACS and the reserved system range on a single VLAN. This is OK for a small, single site deployment but how does this translate for multiple zones? The docs suggest that configuring a single /20 range for management is desired, does that imply that that range should be stretched across sites?

Should it be possible to have a dedicated VLAN at each site for vCenter, ESXi console ports and the system VM's, and then have the ACS server sitting in a separate VLAN that can route between both networks? I have been unsuccessful in getting his working to date so hopefully someone out there has some experience setting up a multi-site ACS/vSphere envoronment.

Any guidance would be greatly appreciated!


Simon Murphy
Solutions Architect

ViFX | Cloud Infrastructure
Level 7, 57 Fort Street, Auckland, New Zealand 1010
PO Box 106700, Auckland, New Zealand 1143
M +64 21 285 4519 | S simon_a_murphy
www.vifx.co.nz<http://www.vifx.co.nz/> follow us on twitter<https://twitter.com/ViFX>
Auckland | Wellington | Christchurch

[cid:image003.jpg@01CDDF95.815BF160]

experience. expertise. execution.

This email and any files transmitted with it are confidential, without prejudice and may contain information that is subject to legal privilege. It is intended solely for the use of the individual/s to whom it is addressed in accordance with the provisions of the Privacy Act (1993). The content contained in this email does not, necessarily, reflect the official policy position of ViFX nor does ViFX have any responsibility for any alterations to the contents of this email that may occur following transmission. If you are not the addressee it may be unlawful for you to read, copy, distribute, disclose or otherwise use the information contained within this email. If you are not the intended recipient, please notify the sender prior to deleting this email message from your system. Please note ViFX reserves the right to monitor, from time to time, the communications sent to and from its email network.

RE: ACS 4.2.1 - Multi-Zone vSphere Architecture

Posted by Sanjeev Neelarapu <sa...@citrix.com>.
Hi,

It is not mandatory to use single dedicated vlan in a multi zone environment. It is possible to have a dedicated VLAN at each site for vCenter, ESXi console ports and the system VM's, and then have the ACS server sitting in a separate VLAN that can route between both networks.

Thanks,
Sanjeev

From: Simon Murphy [mailto:simon.Murphy@vifx.co.nz]
Sent: Monday, November 25, 2013 7:32 AM
To: users@cloudstack.apache.org; dev@cloudstack.apache.org
Subject: ACS 4.2.1 - Multi-Zone vSphere Architecture

Hi all,

Im after some guidance on setting up ACS 4.2.1 with vSphere in a multi zone environment. The only way I have been able to successfully build a zone to this point is by having vSphere, ESXi console ports, ACS and the reserved system range on a single VLAN. This is OK for a small, single site deployment but how does this translate for multiple zones? The docs suggest that configuring a single /20 range for management is desired, does that imply that that range should be stretched across sites?

Should it be possible to have a dedicated VLAN at each site for vCenter, ESXi console ports and the system VM's, and then have the ACS server sitting in a separate VLAN that can route between both networks? I have been unsuccessful in getting his working to date so hopefully someone out there has some experience setting up a multi-site ACS/vSphere envoronment.

Any guidance would be greatly appreciated!


Simon Murphy
Solutions Architect

ViFX | Cloud Infrastructure
Level 7, 57 Fort Street, Auckland, New Zealand 1010
PO Box 106700, Auckland, New Zealand 1143
M +64 21 285 4519 | S simon_a_murphy
www.vifx.co.nz<http://www.vifx.co.nz/> follow us on twitter<https://twitter.com/ViFX>
Auckland | Wellington | Christchurch

[cid:image003.jpg@01CDDF95.815BF160]

experience. expertise. execution.

This email and any files transmitted with it are confidential, without prejudice and may contain information that is subject to legal privilege. It is intended solely for the use of the individual/s to whom it is addressed in accordance with the provisions of the Privacy Act (1993). The content contained in this email does not, necessarily, reflect the official policy position of ViFX nor does ViFX have any responsibility for any alterations to the contents of this email that may occur following transmission. If you are not the addressee it may be unlawful for you to read, copy, distribute, disclose or otherwise use the information contained within this email. If you are not the intended recipient, please notify the sender prior to deleting this email message from your system. Please note ViFX reserves the right to monitor, from time to time, the communications sent to and from its email network.