Re: CloudStack VMware Network Question

[Andrija Panic]

As Vivek stated... your management server will talk to the Center - so
there needs to be proper connectivity.
Also your SSVM/CPVM/VRs will have a NIC that sits inside the PODs
Management network and needs to be able to talk to your management server -
for small deployments (and it could be in general as well), you would
probably have them all inside the same VLAN/subnet - some IPs are
(manually) assigned to management server, to vCenter, to ESXI hosts (i.e.
30-40 total), the rest from i.e. .41-.241 would be defined as "system
reserved IPs" when you deploy the zone - ACS will handle those IPs to the
vNIC of SSVM/CPVM (2 in total usually) and up to 198 VRs in your case
(241-41-2).


Cheers,

On Wed, 1 Jul 2020 at 21:29, Vivek Kumar 
wrote:

> Hello Mike,
>
> It works pretty well if we use separate network for Management and VMware
> hosts. If you can have a look on the logs you will get to know the reason
> of not getting deployed. Make sure that you have proper routing between you
> Management network and POD network (VMware hosts) .
>
> Vivek Kumar
> Manager - Cloud & DevOps
> IndiQus Technologies
> 24*7  O +91 11 4055 1411  |   M +91 7503460090
> www.indiqus.com 
>
> This message is intended only for the use of the individual or entity to
> which it is addressed and may contain information that is confidential
> and/or privileged. If you are not the intended recipient please delete the
> original message and any copy of it from your computer system. You are
> hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited unless proper authorization has been
> obtained for such action. If you have received this communication in error,
> please notify the sender immediately. Although IndiQus attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that both are
> virus-free and accepts no liability for any damage sustained as a result of
> viruses.
>
> > On 02-Jul-2020, at 12:13 AM, Corey, Mike  wrote:
> >
> > Hi,
> >
> > I’m running into trouble with deploying the SystemVMs.  I think it’s
> because the “Management Network” is different IP/VLAN than what my ESXi
> vmkernel port group is.
> >
> > I have re-read the installation doc and if this is in fact a requirement
> than it stinks…
> >
> > In the vSwitch properties dialog box, you may see a vCenter management
> network. This same network will also be used as the CloudStack management
> network. CloudStack requires the vCenter management network to be
> configured properly.
> >
> > Do the ESXi vmkernel and the network for the SystemVMs need to be the
> same VLAN/Network/Port Group?  As I stand right now, my ESXi hosts are on
> network 192.168.32.x and the management IP ranges are 192.168.4.x.
> >
> > If that is the case – can you explicitly call that out in the
> setup/installation?  Also, why is this the case as we’d typically have
> management and hypervisors on isolated/separate networks (ACLs).
> >
> >
> >
> >
> > Mike Corey <>
> >
> > Technology Senior Consultant, IT CS CTW Operation & Virtualization
> Service US <>
> >
> > SAP AMERICA, INC. <> 3999 West Chester Pike, Newtown Square, 19073
> United States <>
> >
> > T +1 610 661 0905, M +1 484 274 2658, E  <>mike.co...@sap.com  mike.co...@sap.com>
> >  <>  <>
> >
> >  <>
> >  <>
> >  <>
>


-- 

Andrija Panić

Re: CloudStack VMware Network Question

[Vivek Kumar]

Hello Mike, 

It works pretty well if we use separate network for Management and VMware 
hosts. If you can have a look on the logs you will get to know the reason of 
not getting deployed. Make sure that you have proper routing between you 
Management network and POD network (VMware hosts) . 

Vivek Kumar
Manager - Cloud & DevOps 
IndiQus Technologies
24*7  O +91 11 4055 1411  |   M +91 7503460090 
www.indiqus.com 

This message is intended only for the use of the individual or entity to which 
it is addressed and may contain information that is confidential and/or 
privileged. If you are not the intended recipient please delete the original 
message and any copy of it from your computer system. You are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited unless proper authorization has been obtained for such 
action. If you have received this communication in error, please notify the 
sender immediately. Although IndiQus attempts to sweep e-mail and attachments 
for viruses, it does not guarantee that both are virus-free and accepts no 
liability for any damage sustained as a result of viruses.

> On 02-Jul-2020, at 12:13 AM, Corey, Mike  wrote:
> 
> Hi,
>  
> I’m running into trouble with deploying the SystemVMs.  I think it’s because 
> the “Management Network” is different IP/VLAN than what my ESXi vmkernel port 
> group is.
>  
> I have re-read the installation doc and if this is in fact a requirement than 
> it stinks…
>  
> In the vSwitch properties dialog box, you may see a vCenter management 
> network. This same network will also be used as the CloudStack management 
> network. CloudStack requires the vCenter management network to be configured 
> properly. 
>  
> Do the ESXi vmkernel and the network for the SystemVMs need to be the same 
> VLAN/Network/Port Group?  As I stand right now, my ESXi hosts are on network 
> 192.168.32.x and the management IP ranges are 192.168.4.x.
>  
> If that is the case – can you explicitly call that out in the 
> setup/installation?  Also, why is this the case as we’d typically have 
> management and hypervisors on isolated/separate networks (ACLs).
>  
>  
>  
>  
> Mike Corey <>
> 
> Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US 
> <>
> 
> SAP AMERICA, INC. <> 3999 West Chester Pike, Newtown Square, 19073 United 
> States <>
> 
> T +1 610 661 0905, M +1 484 274 2658, E  <>mike.co...@sap.com 
> 
>  <>  <>
> 
>  <>
>  <>
>  <>

Re: Cloudstack Vmware NSX Integration

[Rafael Weingärtner]

I found two PRs with something related to NSX-MH.
https://github.com/apache/cloudstack/pull/935
https://github.com/apache/cloudstack/pull/1094

The author is nvazquez.

On Mon, Mar 13, 2017 at 1:21 PM, Simon Weller  wrote:

> I'm pretty sure that a bunch of rework of NSX-MH was done for ACS 4.7.
> Remi would probably be the best person to confirm that, as I believe SBP
> did the work.
>
>
> - Si
>
>
> 
> From: Sergey Levitskiy 
> Sent: Monday, March 13, 2017 12:12 PM
> To: users@cloudstack.apache.org
> Subject: Re: Cloudstack Vmware NSX Integration
>
> NSX MH is supported up to version 4.2.X for both shared an isolated
> networking. The plugin only supports virtual networking, static and source
> NAT as well port forwarding over STT. No other services are supported and
> little new development is happening with NSX plugin. Also as per NSX 4.2
> only standard vSwitch can co-exist with NSX.
> Here it is some additional details on it:
> http://docs.cloudstack.apache.org/en/latest/networking/nicira-plugin.html
> The Nicira NVP Plugin — Apache CloudStack 4.8.0 documentation<http://docs.
> cloudstack.apache.org/en/latest/networking/nicira-plugin.html>
> docs.cloudstack.apache.org
> Introduction to the Nicira NVP Plugin¶ The Nicira NVP plugin adds Nicira
> NVP as one of the available SDN implementations in CloudStack. With the
> plugin an exisiting ...
>
>
>
>
>
> Thanks,
> Sergey
>
>
>
> On 3/13/17, 6:47 AM, "Özhan Rüzgar Karaman" 
> wrote:
>
> Hi;
> Do we have any build-in support for Vmware NSX Platform?
>
> We have currently integrated ACS 4.9.2 to customers Vmware environment
> and
> we also like to integrate with their NSX solution to supply firewall
> and
> qos support for deployed vm's.
>
> Thanks
> Özhan
>
>
>


-- 
Rafael Weingärtner

Re: Cloudstack Vmware NSX Integration

[Simon Weller]

I'm pretty sure that a bunch of rework of NSX-MH was done for ACS 4.7. Remi 
would probably be the best person to confirm that, as I believe SBP did the 
work.


- Si



From: Sergey Levitskiy 
Sent: Monday, March 13, 2017 12:12 PM
To: users@cloudstack.apache.org
Subject: Re: Cloudstack Vmware NSX Integration

NSX MH is supported up to version 4.2.X for both shared an isolated networking. 
The plugin only supports virtual networking, static and source NAT as well port 
forwarding over STT. No other services are supported and little new development 
is happening with NSX plugin. Also as per NSX 4.2 only standard vSwitch can 
co-exist with NSX.
Here it is some additional details on it:
http://docs.cloudstack.apache.org/en/latest/networking/nicira-plugin.html
The Nicira NVP Plugin — Apache CloudStack 4.8.0 
documentation<http://docs.cloudstack.apache.org/en/latest/networking/nicira-plugin.html>
docs.cloudstack.apache.org
Introduction to the Nicira NVP Plugin¶ The Nicira NVP plugin adds Nicira NVP as 
one of the available SDN implementations in CloudStack. With the plugin an 
exisiting ...





Thanks,
Sergey



On 3/13/17, 6:47 AM, "Özhan Rüzgar Karaman"  wrote:

Hi;
Do we have any build-in support for Vmware NSX Platform?

We have currently integrated ACS 4.9.2 to customers Vmware environment and
we also like to integrate with their NSX solution to supply firewall and
qos support for deployed vm's.

Thanks
Özhan

Re: Cloudstack Vmware NSX Integration

[Sergey Levitskiy]

NSX MH is supported up to version 4.2.X for both shared an isolated networking. 
The plugin only supports virtual networking, static and source NAT as well port 
forwarding over STT. No other services are supported and little new development 
is happening with NSX plugin. Also as per NSX 4.2 only standard vSwitch can 
co-exist with NSX.
Here it is some additional details on it:
http://docs.cloudstack.apache.org/en/latest/networking/nicira-plugin.html


Thanks,
Sergey



On 3/13/17, 6:47 AM, "Özhan Rüzgar Karaman"  wrote:

Hi;
Do we have any build-in support for Vmware NSX Platform?

We have currently integrated ACS 4.9.2 to customers Vmware environment and
we also like to integrate with their NSX solution to supply firewall and
qos support for deployed vm's.

Thanks
Özhan

Re: CloudStack VMware templates

[Erik Weber]

Check out http://dl.openvm.eu I believe it should have vmware templates AS
well

Den søndag 7. februar 2016 skrev Cristian Ciobanu 
følgende:

> Hello,
>
> Can i get some linux OS templates for CloudStack VMware ? no matter if
> i need to pay for..
>
>
> Cristian
> Thanks.

Re: cloudstack + vmware

[Daan Hoogland]

I would like this, but it is not there and no one is working on it.
You might find some problems there with respect to networking
especially.

regards,
Daan

On Tue, Dec 10, 2013 at 5:47 AM, Simon Murphy  wrote:
> that functionality does not exist, and it is a big problem for us too. 
> hopefully someone is working on it.
>
> Sent from my Android phone using TouchDown (www.nitrodesk.com)
>
> -Original Message-
> From: Daniel Wittenberg [dwittenberg2...@gmail.com]
> Received: Tuesday, 10 Dec 2013, 11:28am
> To: users@cloudstack.apache.org [users@cloudstack.apache.org]
> Subject: cloudstack + vmware
>
> I was reading through the docs now that I have a basic setup going and it 
> appears that you can’t really have CS manage a current VMware environment, if 
> I read this right:
> “Make sure the hypervisor hosts do not have any VMs already running before 
> you add them to CloudStack”
>
> So if there now way to just bring CS into an existing environment to take 
> over management or do you really have to build a new environment with it?
>
> Thanks!
> Dan

RE: cloudstack + vmware

[Simon Murphy]

that functionality does not exist, and it is a big problem for us too. 
hopefully someone is working on it.

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

-Original Message-
From: Daniel Wittenberg [dwittenberg2...@gmail.com]
Received: Tuesday, 10 Dec 2013, 11:28am
To: users@cloudstack.apache.org [users@cloudstack.apache.org]
Subject: cloudstack + vmware

I was reading through the docs now that I have a basic setup going and it 
appears that you can’t really have CS manage a current VMware environment, if I 
read this right:
“Make sure the hypervisor hosts do not have any VMs already running before you 
add them to CloudStack”

So if there now way to just bring CS into an existing environment to take over 
management or do you really have to build a new environment with it?

Thanks!
Dan