You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by John Skinner <jo...@appcore.com> on 2013/09/06 00:16:25 UTC
VMware DomainRouter
Hello list,
I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything seems to be working ok for the most part. However, I have noticed that my domain routers are getting created with a management IP address for the control network instead of a control network IP address (the link local IP addresses). Is this expected behavior?
Re: VMware DomainRouter
Posted by John Skinner <jo...@appcore.com>.
Awesome. Thank you.
----- Original Message -----
From: "Ilya Musayev" <im...@webmd.net>
To: users@cloudstack.apache.org
Sent: Monday, September 9, 2013 1:20:09 PM
Subject: RE: VMware DomainRouter
Yes only works for vmware and it worked for me in ACS 4.1
-----Original Message-----
From: John Skinner [mailto:john.skinner@appcore.com]
Sent: Monday, September 09, 2013 10:29 AM
To: users@cloudstack.apache.org
Subject: Re: VMware DomainRouter
So to put the management network on a VLAN on VMware would I just specify a management network label for example if I wanted VLAN 96: "vSwitch0,96" ?
----- Original Message -----
From: "John Skinner" <jo...@appcore.com>
To: users@cloudstack.apache.org
Cc: "Jayapal Reddy Uradi" <ja...@citrix.com>
Sent: Friday, September 6, 2013 1:27:12 PM
Subject: Re: VMware DomainRouter
Also, is it possible to put the management network on a tagged VLAN? It doesn't look like it is through the UI, but could I make some database changes to get cloud to create the nics on the host with a vlan similar to guest networks?
John Skinner
Senior Systems Administrator | Appcore - the business of cloud computing®
Office +1.800.735.7104
Direct +1.515.612.7783 | Mobile +1.515.745.0248 john.skinner@appcore.com | www.appcore.com
----------------------------------------------------------------------
The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you.
----- Original Message -----
From: "John Skinner" <jo...@appcore.com>
To: users@cloudstack.apache.org
Cc: "Jayapal Reddy Uradi" <ja...@citrix.com>
Sent: Friday, September 6, 2013 8:23:40 AM
Subject: Re: VMware DomainRouter
So it's expected that it uses an IP address from the management network on the domain router? I typically only set aside 10 or so IP addresses from the management network for CloudStack usage for things like SSVM and console proxy. Am I going to have to allocate a lot more of my management IP addresses now? Also, I believe I did use the 5.1 SDK. Thanks for the replies guys!
----- Original Message -----
From: "Kirk Kosinski" <ki...@gmail.com>
To: users@cloudstack.apache.org
Cc: "Jayapal Reddy Uradi" <ja...@citrix.com>
Sent: Friday, September 6, 2013 2:37:37 AM
Subject: Re: VMware DomainRouter
Right, since on KVM and XS hosts we can run scripts directly on the host to communicate with system VMs, whereas on ESXi this is discouraged and not even possible by default.
Best regards,
Kirk
On 09/05/2013 10:07 PM, Jayapal Reddy Uradi wrote:
> This is expected in vmware. In Xen and KVM we have link local IP address.
>
> Thanks,
> Jayapal
>
> On 06-Sep-2013, at 3:46 AM, John Skinner <jo...@appcore.com> wrote:
>
>> Hello list,
>>
>> I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything seems to be working ok for the most part. However, I have noticed that my domain routers are getting created with a management IP address for the control network instead of a control network IP address (the link local IP addresses). Is this expected behavior?
>>
>
RE: VMware DomainRouter
Posted by "Musayev, Ilya" <im...@webmd.net>.
Yes only works for vmware and it worked for me in ACS 4.1
-----Original Message-----
From: John Skinner [mailto:john.skinner@appcore.com]
Sent: Monday, September 09, 2013 10:29 AM
To: users@cloudstack.apache.org
Subject: Re: VMware DomainRouter
So to put the management network on a VLAN on VMware would I just specify a management network label for example if I wanted VLAN 96: "vSwitch0,96" ?
----- Original Message -----
From: "John Skinner" <jo...@appcore.com>
To: users@cloudstack.apache.org
Cc: "Jayapal Reddy Uradi" <ja...@citrix.com>
Sent: Friday, September 6, 2013 1:27:12 PM
Subject: Re: VMware DomainRouter
Also, is it possible to put the management network on a tagged VLAN? It doesn't look like it is through the UI, but could I make some database changes to get cloud to create the nics on the host with a vlan similar to guest networks?
John Skinner
Senior Systems Administrator | Appcore - the business of cloud computing®
Office +1.800.735.7104
Direct +1.515.612.7783 | Mobile +1.515.745.0248 john.skinner@appcore.com | www.appcore.com
----------------------------------------------------------------------
The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you.
----- Original Message -----
From: "John Skinner" <jo...@appcore.com>
To: users@cloudstack.apache.org
Cc: "Jayapal Reddy Uradi" <ja...@citrix.com>
Sent: Friday, September 6, 2013 8:23:40 AM
Subject: Re: VMware DomainRouter
So it's expected that it uses an IP address from the management network on the domain router? I typically only set aside 10 or so IP addresses from the management network for CloudStack usage for things like SSVM and console proxy. Am I going to have to allocate a lot more of my management IP addresses now? Also, I believe I did use the 5.1 SDK. Thanks for the replies guys!
----- Original Message -----
From: "Kirk Kosinski" <ki...@gmail.com>
To: users@cloudstack.apache.org
Cc: "Jayapal Reddy Uradi" <ja...@citrix.com>
Sent: Friday, September 6, 2013 2:37:37 AM
Subject: Re: VMware DomainRouter
Right, since on KVM and XS hosts we can run scripts directly on the host to communicate with system VMs, whereas on ESXi this is discouraged and not even possible by default.
Best regards,
Kirk
On 09/05/2013 10:07 PM, Jayapal Reddy Uradi wrote:
> This is expected in vmware. In Xen and KVM we have link local IP address.
>
> Thanks,
> Jayapal
>
> On 06-Sep-2013, at 3:46 AM, John Skinner <jo...@appcore.com> wrote:
>
>> Hello list,
>>
>> I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything seems to be working ok for the most part. However, I have noticed that my domain routers are getting created with a management IP address for the control network instead of a control network IP address (the link local IP addresses). Is this expected behavior?
>>
>
Re: VMware DomainRouter
Posted by John Skinner <jo...@appcore.com>.
So to put the management network on a VLAN on VMware would I just specify a management network label for example if I wanted VLAN 96: "vSwitch0,96" ?
----- Original Message -----
From: "John Skinner" <jo...@appcore.com>
To: users@cloudstack.apache.org
Cc: "Jayapal Reddy Uradi" <ja...@citrix.com>
Sent: Friday, September 6, 2013 1:27:12 PM
Subject: Re: VMware DomainRouter
Also, is it possible to put the management network on a tagged VLAN? It doesn't look like it is through the UI, but could I make some database changes to get cloud to create the nics on the host with a vlan similar to guest networks?
John Skinner
Senior Systems Administrator | Appcore - the business of cloud computing®
Office +1.800.735.7104
Direct +1.515.612.7783 | Mobile +1.515.745.0248
john.skinner@appcore.com | www.appcore.com
----------------------------------------------------------------------
The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you.
----- Original Message -----
From: "John Skinner" <jo...@appcore.com>
To: users@cloudstack.apache.org
Cc: "Jayapal Reddy Uradi" <ja...@citrix.com>
Sent: Friday, September 6, 2013 8:23:40 AM
Subject: Re: VMware DomainRouter
So it's expected that it uses an IP address from the management network on the domain router? I typically only set aside 10 or so IP addresses from the management network for CloudStack usage for things like SSVM and console proxy. Am I going to have to allocate a lot more of my management IP addresses now? Also, I believe I did use the 5.1 SDK. Thanks for the replies guys!
----- Original Message -----
From: "Kirk Kosinski" <ki...@gmail.com>
To: users@cloudstack.apache.org
Cc: "Jayapal Reddy Uradi" <ja...@citrix.com>
Sent: Friday, September 6, 2013 2:37:37 AM
Subject: Re: VMware DomainRouter
Right, since on KVM and XS hosts we can run scripts directly on the host
to communicate with system VMs, whereas on ESXi this is discouraged and
not even possible by default.
Best regards,
Kirk
On 09/05/2013 10:07 PM, Jayapal Reddy Uradi wrote:
> This is expected in vmware. In Xen and KVM we have link local IP address.
>
> Thanks,
> Jayapal
>
> On 06-Sep-2013, at 3:46 AM, John Skinner <jo...@appcore.com> wrote:
>
>> Hello list,
>>
>> I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything seems to be working ok for the most part. However, I have noticed that my domain routers are getting created with a management IP address for the control network instead of a control network IP address (the link local IP addresses). Is this expected behavior?
>>
>
Re: VMware DomainRouter
Posted by John Skinner <jo...@appcore.com>.
Also, is it possible to put the management network on a tagged VLAN? It doesn't look like it is through the UI, but could I make some database changes to get cloud to create the nics on the host with a vlan similar to guest networks?
John Skinner
Senior Systems Administrator | Appcore - the business of cloud computing®
Office +1.800.735.7104
Direct +1.515.612.7783 | Mobile +1.515.745.0248
john.skinner@appcore.com | www.appcore.com
----------------------------------------------------------------------
The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you.
----- Original Message -----
From: "John Skinner" <jo...@appcore.com>
To: users@cloudstack.apache.org
Cc: "Jayapal Reddy Uradi" <ja...@citrix.com>
Sent: Friday, September 6, 2013 8:23:40 AM
Subject: Re: VMware DomainRouter
So it's expected that it uses an IP address from the management network on the domain router? I typically only set aside 10 or so IP addresses from the management network for CloudStack usage for things like SSVM and console proxy. Am I going to have to allocate a lot more of my management IP addresses now? Also, I believe I did use the 5.1 SDK. Thanks for the replies guys!
----- Original Message -----
From: "Kirk Kosinski" <ki...@gmail.com>
To: users@cloudstack.apache.org
Cc: "Jayapal Reddy Uradi" <ja...@citrix.com>
Sent: Friday, September 6, 2013 2:37:37 AM
Subject: Re: VMware DomainRouter
Right, since on KVM and XS hosts we can run scripts directly on the host
to communicate with system VMs, whereas on ESXi this is discouraged and
not even possible by default.
Best regards,
Kirk
On 09/05/2013 10:07 PM, Jayapal Reddy Uradi wrote:
> This is expected in vmware. In Xen and KVM we have link local IP address.
>
> Thanks,
> Jayapal
>
> On 06-Sep-2013, at 3:46 AM, John Skinner <jo...@appcore.com> wrote:
>
>> Hello list,
>>
>> I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything seems to be working ok for the most part. However, I have noticed that my domain routers are getting created with a management IP address for the control network instead of a control network IP address (the link local IP addresses). Is this expected behavior?
>>
>
Re: VMware DomainRouter
Posted by John Skinner <jo...@appcore.com>.
So it's expected that it uses an IP address from the management network on the domain router? I typically only set aside 10 or so IP addresses from the management network for CloudStack usage for things like SSVM and console proxy. Am I going to have to allocate a lot more of my management IP addresses now? Also, I believe I did use the 5.1 SDK. Thanks for the replies guys!
----- Original Message -----
From: "Kirk Kosinski" <ki...@gmail.com>
To: users@cloudstack.apache.org
Cc: "Jayapal Reddy Uradi" <ja...@citrix.com>
Sent: Friday, September 6, 2013 2:37:37 AM
Subject: Re: VMware DomainRouter
Right, since on KVM and XS hosts we can run scripts directly on the host
to communicate with system VMs, whereas on ESXi this is discouraged and
not even possible by default.
Best regards,
Kirk
On 09/05/2013 10:07 PM, Jayapal Reddy Uradi wrote:
> This is expected in vmware. In Xen and KVM we have link local IP address.
>
> Thanks,
> Jayapal
>
> On 06-Sep-2013, at 3:46 AM, John Skinner <jo...@appcore.com> wrote:
>
>> Hello list,
>>
>> I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything seems to be working ok for the most part. However, I have noticed that my domain routers are getting created with a management IP address for the control network instead of a control network IP address (the link local IP addresses). Is this expected behavior?
>>
>
Re: VMware DomainRouter
Posted by Kirk Kosinski <ki...@gmail.com>.
Right, since on KVM and XS hosts we can run scripts directly on the host
to communicate with system VMs, whereas on ESXi this is discouraged and
not even possible by default.
Best regards,
Kirk
On 09/05/2013 10:07 PM, Jayapal Reddy Uradi wrote:
> This is expected in vmware. In Xen and KVM we have link local IP address.
>
> Thanks,
> Jayapal
>
> On 06-Sep-2013, at 3:46 AM, John Skinner <jo...@appcore.com> wrote:
>
>> Hello list,
>>
>> I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything seems to be working ok for the most part. However, I have noticed that my domain routers are getting created with a management IP address for the control network instead of a control network IP address (the link local IP addresses). Is this expected behavior?
>>
>
Re: VMware DomainRouter
Posted by Jayapal Reddy Uradi <ja...@citrix.com>.
This is expected in vmware. In Xen and KVM we have link local IP address.
Thanks,
Jayapal
On 06-Sep-2013, at 3:46 AM, John Skinner <jo...@appcore.com> wrote:
> Hello list,
>
> I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything seems to be working ok for the most part. However, I have noticed that my domain routers are getting created with a management IP address for the control network instead of a control network IP address (the link local IP addresses). Is this expected behavior?
>
RE: VMware DomainRouter
Posted by "Musayev, Ilya" <im...@webmd.net>.
Michael,
If I'm not mistaken, the convenience RPMs provided on apt-get.eu are containing nonoss as well, so no need to build from source :)
Regards
ilya
> -----Original Message-----
> From: Michael Phillips [mailto:mphilli7823@hotmail.com]
> Sent: Thursday, September 05, 2013 6:24 PM
> To: users@cloudstack.apache.org
> Subject: RE: VMware DomainRouter
>
> Hey QQ, since you are using vmware you obviously built from source. Did you
> use the vim25.jar from the 5.1SDK?
>
> > Date: Thu, 5 Sep 2013 17:16:25 -0500
> > From: john.skinner@appcore.com
> > To: users@cloudstack.apache.org
> > Subject: VMware DomainRouter
> >
> > Hello list,
> >
> > I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything
> seems to be working ok for the most part. However, I have noticed that my
> domain routers are getting created with a management IP address for the
> control network instead of a control network IP address (the link local IP
> addresses). Is this expected behavior?
> >
>
RE: VMware DomainRouter
Posted by Michael Phillips <mp...@hotmail.com>.
Hey QQ, since you are using vmware you obviously built from source. Did you use the vim25.jar from the 5.1SDK?
> Date: Thu, 5 Sep 2013 17:16:25 -0500
> From: john.skinner@appcore.com
> To: users@cloudstack.apache.org
> Subject: VMware DomainRouter
>
> Hello list,
>
> I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything seems to be working ok for the most part. However, I have noticed that my domain routers are getting created with a management IP address for the control network instead of a control network IP address (the link local IP addresses). Is this expected behavior?
>
RE: VMware DomainRouter
Posted by Michael Phillips <mp...@hotmail.com>.
I am curious as to which vim25.jar you included..the one from the 4.1 or 5.1 SDK?
> Date: Thu, 5 Sep 2013 18:31:02 -0500
> From: john.skinner@appcore.com
> To: users@cloudstack.apache.org
> Subject: Re: VMware DomainRouter
>
> I did build from source, and did include the vim25.jar. I have 2 interfaces that are bonded for all networks with 2 standard vSwitches. I have vSwitch0 for management and storage, and vSwitch2 for public and guest.
>
> John Skinner
> Senior Systems Administrator | Appcore - the business of cloud computing®
>
> Office +1.800.735.7104
> Direct +1.515.612.7783 | Mobile +1.515.745.0248
> john.skinner@appcore.com | www.appcore.com
> ----------------------------------------------------------------------
> The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you.
>
>
> ----- Original Message -----
>
> From: "Ilya Musayev" <im...@webmd.net>
> To: users@cloudstack.apache.org
> Sent: Thursday, September 5, 2013 5:22:30 PM
> Subject: RE: VMware DomainRouter
>
> Is your eth1 - guest network and eth2 - mgmt. network?
>
> > -----Original Message-----
> > From: John Skinner [mailto:john.skinner@appcore.com]
> > Sent: Thursday, September 05, 2013 6:16 PM
> > To: users@cloudstack.apache.org
> > Subject: VMware DomainRouter
> >
> > Hello list,
> >
> > I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything
> > seems to be working ok for the most part. However, I have noticed that my
> > domain routers are getting created with a management IP address for the
> > control network instead of a control network IP address (the link local IP
> > addresses). Is this expected behavior?
>
>
Re: VMware DomainRouter
Posted by John Skinner <jo...@appcore.com>.
I did build from source, and did include the vim25.jar. I have 2 interfaces that are bonded for all networks with 2 standard vSwitches. I have vSwitch0 for management and storage, and vSwitch2 for public and guest.
John Skinner
Senior Systems Administrator | Appcore - the business of cloud computing®
Office +1.800.735.7104
Direct +1.515.612.7783 | Mobile +1.515.745.0248
john.skinner@appcore.com | www.appcore.com
----------------------------------------------------------------------
The information in this message is intended for the named recipients only. It may contain information that is privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this e-mail in error, do not print it or disseminate it or its contents. In such event, please notify the sender by return e-mail and delete the e-mail file immediately thereafter. Thank you.
----- Original Message -----
From: "Ilya Musayev" <im...@webmd.net>
To: users@cloudstack.apache.org
Sent: Thursday, September 5, 2013 5:22:30 PM
Subject: RE: VMware DomainRouter
Is your eth1 - guest network and eth2 - mgmt. network?
> -----Original Message-----
> From: John Skinner [mailto:john.skinner@appcore.com]
> Sent: Thursday, September 05, 2013 6:16 PM
> To: users@cloudstack.apache.org
> Subject: VMware DomainRouter
>
> Hello list,
>
> I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything
> seems to be working ok for the most part. However, I have noticed that my
> domain routers are getting created with a management IP address for the
> control network instead of a control network IP address (the link local IP
> addresses). Is this expected behavior?
RE: VMware DomainRouter
Posted by "Musayev, Ilya" <im...@webmd.net>.
Is your eth1 - guest network and eth2 - mgmt. network?
> -----Original Message-----
> From: John Skinner [mailto:john.skinner@appcore.com]
> Sent: Thursday, September 05, 2013 6:16 PM
> To: users@cloudstack.apache.org
> Subject: VMware DomainRouter
>
> Hello list,
>
> I just setup a CloudStack 4.1 environment with vSphere 5.1. Everything
> seems to be working ok for the most part. However, I have noticed that my
> domain routers are getting created with a management IP address for the
> control network instead of a control network IP address (the link local IP
> addresses). Is this expected behavior?