You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by "Boylan, James" <JA...@orbitz.com> on 2012/11/28 00:09:35 UTC
Question about Network Domains
Has anyone had any luck with having different Network Domain suffixes assigned for different Accounts or Domains?
Is there some special configuration that has to be assigned to make it work as expected. (People creating instances who are a member of a domain with a suffix get the suffix of that domain, etc?)
-- James
RE: Question about Network Domains
Posted by "Boylan, James" <JA...@orbitz.com>.
It was create before. Ok. That explains it. Thanks!
-- James
________________________________
From: Alena Prokharchyk [Alena.Prokharchyk@citrix.com]
Sent: Tuesday, November 27, 2012 9:03 PM
To: cloudstack-users@incubator.apache.org
Cc: Boylan, James
Subject: Re: Question about Network Domains
James,
"So if I assign a network domain on an account. It should override all other settings and a network assigned in a domain's network domain should override the network domain on the zone, correct?"
It will apply only for the new networks, created after you've assigned networkDomain to account/domain. All networks created prior to the change, will remain with the zone level network domain (even if you restart the router).
Were your networks created after you've set networkDomain for account/domain?
-Alena.
From: <Boylan>, James <JA...@orbitz.com>>
Reply-To: "'cloudstack-users@incubator. org'" <cl...@incubator.apache.org>>
To: "'cloudstack-users@incubator. org'" <cl...@incubator.apache.org>>
Subject: RE: Question about Network Domains
So if I assign a network domain on an account. It should override all other settings and a network assigned in a domain's network domain should override the network domain on the zone, correct?
Thats what I had thought to be the case. What might cause this behavior not to manifest? I'm having the network domain that I assigned when creating the zone applied to everything and nothing I do seems to change this behavior. (I have already restarted the Management, the Virtual Router and both System VMs)
-- James
________________________________
From: Alena Prokharchyk [Alena.Prokharchyk@citrix.com<ma...@citrix.com>]
Sent: Tuesday, November 27, 2012 6:41 PM
To: 'cloudstack-users@incubator. org'
Cc: Boylan, James
Subject: Re: Question about Network Domains
Hi James,
Hope the information below helps.
NetworkDomain can be defined
per account - "networkDomain" in createAccount Api
per domain - "networkDomain" in createDomain API
per zone - "domain" in createZone API
globally - "guest.domain.suffix" global config param
Here is how networkDomain is applied for diff types of networks:
1) For account specific network (Shared or Isolated) - take networkDomain from account object; if
not specified per account, take it from domain object; if not specified perdomain - take it from zone object; if not specified per zone - take it from the
global config.
2) For domain specific network - take networkDomain from domain object; if not
specified per domain - take it from zone object; if not specified per zone -
take it from the global config.
3) For zone specific network - take networkDomain from zone object; if not
specified per zone - take it from the global config.
All changes to networkDomain made for zone/account/domain will apply only to new
networks. If you want to change config for existing network, updateNetwork api
should be called. If network has running network elements, automatically
restart them.
Let me know if you have any questions,
-Alena.
From: <Boylan>, James <JA...@orbitz.com>>
Reply-To: "'cloudstack-users@incubator. org'" <cl...@incubator.apache.org>>
To: "'cloudstack-users@incubator. org'" <cl...@incubator.apache.org>>
Subject: Question about Network Domains
Has anyone had any luck with having different Network Domain suffixes assigned for different Accounts or Domains?
Is there some special configuration that has to be assigned to make it work as expected. (People creating instances who are a member of a domain with a suffix get the suffix of that domain, etc?)
-- James
Re: Question about Network Domains
Posted by Alena Prokharchyk <Al...@citrix.com>.
James,
"So if I assign a network domain on an account. It should override all other settings and a network assigned in a domain's network domain should override the network domain on the zone, correct?"
It will apply only for the new networks, created after you've assigned networkDomain to account/domain. All networks created prior to the change, will remain with the zone level network domain (even if you restart the router).
Were your networks created after you've set networkDomain for account/domain?
-Alena.
From: <Boylan>, James <JA...@orbitz.com>>
Reply-To: "'cloudstack-users@incubator. org'" <cl...@incubator.apache.org>>
To: "'cloudstack-users@incubator. org'" <cl...@incubator.apache.org>>
Subject: RE: Question about Network Domains
So if I assign a network domain on an account. It should override all other settings and a network assigned in a domain's network domain should override the network domain on the zone, correct?
Thats what I had thought to be the case. What might cause this behavior not to manifest? I'm having the network domain that I assigned when creating the zone applied to everything and nothing I do seems to change this behavior. (I have already restarted the Management, the Virtual Router and both System VMs)
-- James
________________________________
From: Alena Prokharchyk [Alena.Prokharchyk@citrix.com<ma...@citrix.com>]
Sent: Tuesday, November 27, 2012 6:41 PM
To: 'cloudstack-users@incubator. org'
Cc: Boylan, James
Subject: Re: Question about Network Domains
Hi James,
Hope the information below helps.
NetworkDomain can be defined
per account - "networkDomain" in createAccount Api
per domain - "networkDomain" in createDomain API
per zone - "domain" in createZone API
globally - "guest.domain.suffix" global config param
Here is how networkDomain is applied for diff types of networks:
1) For account specific network (Shared or Isolated) - take networkDomain from account object; if
not specified per account, take it from domain object; if not specified perdomain - take it from zone object; if not specified per zone - take it from the
global config.
2) For domain specific network - take networkDomain from domain object; if not
specified per domain - take it from zone object; if not specified per zone -
take it from the global config.
3) For zone specific network - take networkDomain from zone object; if not
specified per zone - take it from the global config.
All changes to networkDomain made for zone/account/domain will apply only to new
networks. If you want to change config for existing network, updateNetwork api
should be called. If network has running network elements, automatically
restart them.
Let me know if you have any questions,
-Alena.
From: <Boylan>, James <JA...@orbitz.com>>
Reply-To: "'cloudstack-users@incubator. org'" <cl...@incubator.apache.org>>
To: "'cloudstack-users@incubator. org'" <cl...@incubator.apache.org>>
Subject: Question about Network Domains
Has anyone had any luck with having different Network Domain suffixes assigned for different Accounts or Domains?
Is there some special configuration that has to be assigned to make it work as expected. (People creating instances who are a member of a domain with a suffix get the suffix of that domain, etc?)
-- James
RE: Question about Network Domains
Posted by "Boylan, James" <JA...@orbitz.com>.
So if I assign a network domain on an account. It should override all other settings and a network assigned in a domain's network domain should override the network domain on the zone, correct?
Thats what I had thought to be the case. What might cause this behavior not to manifest? I'm having the network domain that I assigned when creating the zone applied to everything and nothing I do seems to change this behavior. (I have already restarted the Management, the Virtual Router and both System VMs)
-- James
________________________________
From: Alena Prokharchyk [Alena.Prokharchyk@citrix.com]
Sent: Tuesday, November 27, 2012 6:41 PM
To: 'cloudstack-users@incubator. org'
Cc: Boylan, James
Subject: Re: Question about Network Domains
Hi James,
Hope the information below helps.
NetworkDomain can be defined
per account - "networkDomain" in createAccount Api
per domain - "networkDomain" in createDomain API
per zone - "domain" in createZone API
globally - "guest.domain.suffix" global config param
Here is how networkDomain is applied for diff types of networks:
1) For account specific network (Shared or Isolated) - take networkDomain from account object; if
not specified per account, take it from domain object; if not specified perdomain - take it from zone object; if not specified per zone - take it from the
global config.
2) For domain specific network - take networkDomain from domain object; if not
specified per domain - take it from zone object; if not specified per zone -
take it from the global config.
3) For zone specific network - take networkDomain from zone object; if not
specified per zone - take it from the global config.
All changes to networkDomain made for zone/account/domain will apply only to new
networks. If you want to change config for existing network, updateNetwork api
should be called. If network has running network elements, automatically
restart them.
Let me know if you have any questions,
-Alena.
From: <Boylan>, James <JA...@orbitz.com>>
Reply-To: "'cloudstack-users@incubator. org'" <cl...@incubator.apache.org>>
To: "'cloudstack-users@incubator. org'" <cl...@incubator.apache.org>>
Subject: Question about Network Domains
Has anyone had any luck with having different Network Domain suffixes assigned for different Accounts or Domains?
Is there some special configuration that has to be assigned to make it work as expected. (People creating instances who are a member of a domain with a suffix get the suffix of that domain, etc?)
-- James
Re: Question about Network Domains
Posted by Alena Prokharchyk <Al...@citrix.com>.
Hi James,
Hope the information below helps.
NetworkDomain can be defined
per account - "networkDomain" in createAccount Api
per domain - "networkDomain" in createDomain API
per zone - "domain" in createZone API
globally - "guest.domain.suffix" global config param
Here is how networkDomain is applied for diff types of networks:
1) For account specific network (Shared or Isolated) - take networkDomain from account object; if
not specified per account, take it from domain object; if not specified perdomain - take it from zone object; if not specified per zone - take it from the
global config.
2) For domain specific network - take networkDomain from domain object; if not
specified per domain - take it from zone object; if not specified per zone -
take it from the global config.
3) For zone specific network - take networkDomain from zone object; if not
specified per zone - take it from the global config.
All changes to networkDomain made for zone/account/domain will apply only to new
networks. If you want to change config for existing network, updateNetwork api
should be called. If network has running network elements, automatically
restart them.
Let me know if you have any questions,
-Alena.
From: <Boylan>, James <JA...@orbitz.com>>
Reply-To: "'cloudstack-users@incubator. org'" <cl...@incubator.apache.org>>
To: "'cloudstack-users@incubator. org'" <cl...@incubator.apache.org>>
Subject: Question about Network Domains
Has anyone had any luck with having different Network Domain suffixes assigned for different Accounts or Domains?
Is there some special configuration that has to be assigned to make it work as expected. (People creating instances who are a member of a domain with a suffix get the suffix of that domain, etc?)
-- James