You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Kishan Kavala <Ki...@citrix.com> on 2013/02/26 10:04:13 UTC
[CLOUDSTACK-241 ]Regions update
Removed API based account sync for Regions as discussed earlier [1] . Event framework will be used instead. I pushed the changes to master. commit: e37fdce125511535961c77a77d253ce232a954d0.
I'll be merging the same to 4.1 branch.
[1] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3CCD3462CF.64A2%25chiradeep.vittal@citrix.com%3E
RE: [CLOUDSTACK-241 ]Regions update
Posted by Sangeetha Hariharan <Sa...@citrix.com>.
Thanks Kishan. Will update the test cases accordingly.
-Thanks
Sangeetha
-----Original Message-----
From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
Sent: Friday, March 15, 2013 2:16 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: [CLOUDSTACK-241 ]Regions update
Sangeetha,
Test plan looks good to me. getUser is Admin only API.
Thanks,
Kishan
> -----Original Message-----
> From: Sangeetha Hariharan [mailto:Sangeetha.Hariharan@citrix.com]
> Sent: Friday, 15 March 2013 3:31 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> I have updated the Regions Test Plan to reflect the changes that have
> been made to the FS -
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Regions+T
> est+Plan.
>
> Please review and provide your feedback.
>
> -Thanks
> Sangeetha
>
> -----Original Message-----
> From: Sangeetha Hariharan
> Sent: Wednesday, March 13, 2013 6:29 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> Thanks Kishan for your input.
>
> Since we will now rely on Events Framework feature to publish events
> that could be used by admins to maintain data sync between regions , I
> have created test plan for this feature-
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Events+Framew
> ork+Test+plan .
> This test plan addresses only a part of Event Framework feature that
> is needed by AWS regions feature for achieving data sync of
> Account/Domain/User objects between regions.
> Please provide your feedback.
>
> -Thanks
> Sangeetha
>
> -----Original Message-----
> From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> Sent: Tuesday, March 12, 2013 5:53 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> Please find my response inline.
>
> > -----Original Message-----
> > From: Sangeetha Hariharan [mailto:Sangeetha.Hariharan@citrix.com]
> > Sent: Saturday, 9 March 2013 1:14 AM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: [CLOUDSTACK-241 ]Regions update
> >
> > I have updated the test cases according to the latest functional
> > Spec which is to make use of Event frameworks instead of api based
> > sync for domain/account/users.
> > Test cases can be found here -
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Regions+T
> > est+Plan . Please provide your feedback.
> >
> > I had the following questions:
> >
> > 1. In case of update/delete action from a region that is not the
> > owner , API call will succeed as long as it has been able to forward
> > the request to owner region and the owner region actually executed
> > the command . Even after receiving a success from the API call, the
> > changes will not be committed in this region. This seems like a
> > confusing experience . Can we expect any message indicating to the
> > user
> about the redirection of request?
> >
> [KK] Forwarding to owner region should be removed. Data sync is
> external to CloudStack.
>
> > 2. In case of deleting domains/accounts from a region that is not
> > the owner of this region , this will result in the domain/account
> > being actually deleted from the owner region which will also result
> > in all the resources like network and Vms being deleted. Is this acceptable?
> [KK] When account/domain is deleted all resources will also be deleted.
>
> >
> > 3. Consider the case of domains/accounts (owner Region 1) that have
> > users that are owned by 2 different regions , say user1 (owner
> > Region
> > 1) and user2 (owner Region2) . Which region is responsible for
> > deletion of domain/account , since this deletion will also involve
> > deletion of users which are now owned by 2 different regions?
> >
> [KK] Since data sync is external to CloudStack, we don't need the
> notion of owner region.
>
> > 4. Why is there a need for getUser API ? When will this get used ?
> [KK] getUser API is for components like object-store to authenticate
> and get account information
> >
> > 5. Can you include the response parameters for all the new API calls ?
> [KK] I've added the response parameters to the spec.
> >
> > -Thanks
> > Sangeetha
> >
> >
> > -----Original Message-----
> > From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> > Sent: Thursday, February 28, 2013 12:53 AM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: [CLOUDSTACK-241 ]Regions update
> >
> > > -----Original Message-----
> > > From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> > > Sent: Wednesday, 27 February 2013 12:07 PM
> > > To: cloudstack-dev@incubator.apache.org
> > > Subject: RE: [CLOUDSTACK-241 ]Regions update
> > >
> > > > -----Original Message-----
> > > > From: Chip Childers [mailto:chip.childers@sungard.com]
> > > > Sent: Tuesday, 26 February 2013 8:22 PM
> > > > To: cloudstack-dev@incubator.apache.org
> > > > Subject: Re: [CLOUDSTACK-241 ]Regions update
> > > >
> > > > On Tue, Feb 26, 2013 at 02:34:13PM +0530, Kishan Kavala wrote:
> > > > > Removed API based account sync for Regions as discussed earlier [1] .
> > > > Event framework will be used instead. I pushed the changes to master.
> > > > commit: e37fdce125511535961c77a77d253ce232a954d0.
> > > > > I'll be merging the same to 4.1 branch.
> > > > >
> > > > > [1]
> > > > > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-
> > > > dev/2013
> > > > > 02.mbox/%3CCD3462CF.64A2%25chiradeep.vittal@citrix.com%3E
> > > > >
> > > >
> > > > Is this something we really want to do now? Has the feature
> > > > been QA'ed
> > > yet?
> > > > This seems pretty late to make a change to the basic function of
> > > > the feature for 4.1.
> > > >
> > > > If my concern are overblown, then say so!
> > > >
> > > > -chip
> > >
> > > This commit only removes API based account data sync and it is
> > > fairly isolated part of the code.
> > > Events are already in place so no changes in that area.
> > >
> >
> > Changes were merged to 4.1 branch. I also changed tabs to spaces in
> > the related files, so the diff shows more changes than actual.
RE: [CLOUDSTACK-241 ]Regions update
Posted by Kishan Kavala <Ki...@citrix.com>.
Sangeetha,
Test plan looks good to me. getUser is Admin only API.
Thanks,
Kishan
> -----Original Message-----
> From: Sangeetha Hariharan [mailto:Sangeetha.Hariharan@citrix.com]
> Sent: Friday, 15 March 2013 3:31 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> I have updated the Regions Test Plan to reflect the changes that have been
> made to the FS -
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Regions+T
> est+Plan.
>
> Please review and provide your feedback.
>
> -Thanks
> Sangeetha
>
> -----Original Message-----
> From: Sangeetha Hariharan
> Sent: Wednesday, March 13, 2013 6:29 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> Thanks Kishan for your input.
>
> Since we will now rely on Events Framework feature to publish events that
> could be used by admins to maintain data sync between regions , I have
> created test plan for this feature-
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Events+Framew
> ork+Test+plan .
> This test plan addresses only a part of Event Framework feature that is
> needed by AWS regions feature for achieving data sync of
> Account/Domain/User objects between regions.
> Please provide your feedback.
>
> -Thanks
> Sangeetha
>
> -----Original Message-----
> From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> Sent: Tuesday, March 12, 2013 5:53 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> Please find my response inline.
>
> > -----Original Message-----
> > From: Sangeetha Hariharan [mailto:Sangeetha.Hariharan@citrix.com]
> > Sent: Saturday, 9 March 2013 1:14 AM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: [CLOUDSTACK-241 ]Regions update
> >
> > I have updated the test cases according to the latest functional Spec
> > which is to make use of Event frameworks instead of api based sync for
> > domain/account/users.
> > Test cases can be found here -
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Regions+T
> > est+Plan . Please provide your feedback.
> >
> > I had the following questions:
> >
> > 1. In case of update/delete action from a region that is not the owner
> > , API call will succeed as long as it has been able to forward the
> > request to owner region and the owner region actually executed the
> > command . Even after receiving a success from the API call, the
> > changes will not be committed in this region. This seems like a
> > confusing experience . Can we expect any message indicating to the user
> about the redirection of request?
> >
> [KK] Forwarding to owner region should be removed. Data sync is external
> to CloudStack.
>
> > 2. In case of deleting domains/accounts from a region that is not the
> > owner of this region , this will result in the domain/account being
> > actually deleted from the owner region which will also result in all
> > the resources like network and Vms being deleted. Is this acceptable?
> [KK] When account/domain is deleted all resources will also be deleted.
>
> >
> > 3. Consider the case of domains/accounts (owner Region 1) that have
> > users that are owned by 2 different regions , say user1 (owner Region
> > 1) and user2 (owner Region2) . Which region is responsible for
> > deletion of domain/account , since this deletion will also involve
> > deletion of users which are now owned by 2 different regions?
> >
> [KK] Since data sync is external to CloudStack, we don't need the notion of
> owner region.
>
> > 4. Why is there a need for getUser API ? When will this get used ?
> [KK] getUser API is for components like object-store to authenticate and get
> account information
> >
> > 5. Can you include the response parameters for all the new API calls ?
> [KK] I've added the response parameters to the spec.
> >
> > -Thanks
> > Sangeetha
> >
> >
> > -----Original Message-----
> > From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> > Sent: Thursday, February 28, 2013 12:53 AM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: [CLOUDSTACK-241 ]Regions update
> >
> > > -----Original Message-----
> > > From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> > > Sent: Wednesday, 27 February 2013 12:07 PM
> > > To: cloudstack-dev@incubator.apache.org
> > > Subject: RE: [CLOUDSTACK-241 ]Regions update
> > >
> > > > -----Original Message-----
> > > > From: Chip Childers [mailto:chip.childers@sungard.com]
> > > > Sent: Tuesday, 26 February 2013 8:22 PM
> > > > To: cloudstack-dev@incubator.apache.org
> > > > Subject: Re: [CLOUDSTACK-241 ]Regions update
> > > >
> > > > On Tue, Feb 26, 2013 at 02:34:13PM +0530, Kishan Kavala wrote:
> > > > > Removed API based account sync for Regions as discussed earlier [1] .
> > > > Event framework will be used instead. I pushed the changes to master.
> > > > commit: e37fdce125511535961c77a77d253ce232a954d0.
> > > > > I'll be merging the same to 4.1 branch.
> > > > >
> > > > > [1]
> > > > > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-
> > > > dev/2013
> > > > > 02.mbox/%3CCD3462CF.64A2%25chiradeep.vittal@citrix.com%3E
> > > > >
> > > >
> > > > Is this something we really want to do now? Has the feature been
> > > > QA'ed
> > > yet?
> > > > This seems pretty late to make a change to the basic function of
> > > > the feature for 4.1.
> > > >
> > > > If my concern are overblown, then say so!
> > > >
> > > > -chip
> > >
> > > This commit only removes API based account data sync and it is
> > > fairly isolated part of the code.
> > > Events are already in place so no changes in that area.
> > >
> >
> > Changes were merged to 4.1 branch. I also changed tabs to spaces in
> > the related files, so the diff shows more changes than actual.
RE: [CLOUDSTACK-241 ]Regions update
Posted by Sangeetha Hariharan <Sa...@citrix.com>.
I have updated the Regions Test Plan to reflect the changes that have been made to the FS - https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Regions+Test+Plan.
Please review and provide your feedback.
-Thanks
Sangeetha
-----Original Message-----
From: Sangeetha Hariharan
Sent: Wednesday, March 13, 2013 6:29 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: [CLOUDSTACK-241 ]Regions update
Thanks Kishan for your input.
Since we will now rely on Events Framework feature to publish events that could be used by admins to maintain data sync between regions , I have created test plan for this feature- https://cwiki.apache.org/confluence/display/CLOUDSTACK/Events+Framework+Test+plan .
This test plan addresses only a part of Event Framework feature that is needed by AWS regions feature for achieving data sync of Account/Domain/User objects between regions.
Please provide your feedback.
-Thanks
Sangeetha
-----Original Message-----
From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
Sent: Tuesday, March 12, 2013 5:53 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: [CLOUDSTACK-241 ]Regions update
Please find my response inline.
> -----Original Message-----
> From: Sangeetha Hariharan [mailto:Sangeetha.Hariharan@citrix.com]
> Sent: Saturday, 9 March 2013 1:14 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> I have updated the test cases according to the latest functional Spec
> which is to make use of Event frameworks instead of api based sync for
> domain/account/users.
> Test cases can be found here -
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Regions+T
> est+Plan . Please provide your feedback.
>
> I had the following questions:
>
> 1. In case of update/delete action from a region that is not the owner
> , API call will succeed as long as it has been able to forward the
> request to owner region and the owner region actually executed the
> command . Even after receiving a success from the API call, the
> changes will not be committed in this region. This seems like a
> confusing experience . Can we expect any message indicating to the user about the redirection of request?
>
[KK] Forwarding to owner region should be removed. Data sync is external to CloudStack.
> 2. In case of deleting domains/accounts from a region that is not the
> owner of this region , this will result in the domain/account being
> actually deleted from the owner region which will also result in all
> the resources like network and Vms being deleted. Is this acceptable?
[KK] When account/domain is deleted all resources will also be deleted.
>
> 3. Consider the case of domains/accounts (owner Region 1) that have
> users that are owned by 2 different regions , say user1 (owner Region
> 1) and user2 (owner Region2) . Which region is responsible for
> deletion of domain/account , since this deletion will also involve
> deletion of users which are now owned by 2 different regions?
>
[KK] Since data sync is external to CloudStack, we don't need the notion of owner region.
> 4. Why is there a need for getUser API ? When will this get used ?
[KK] getUser API is for components like object-store to authenticate and get account information
>
> 5. Can you include the response parameters for all the new API calls ?
[KK] I've added the response parameters to the spec.
>
> -Thanks
> Sangeetha
>
>
> -----Original Message-----
> From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> Sent: Thursday, February 28, 2013 12:53 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> > -----Original Message-----
> > From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> > Sent: Wednesday, 27 February 2013 12:07 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: [CLOUDSTACK-241 ]Regions update
> >
> > > -----Original Message-----
> > > From: Chip Childers [mailto:chip.childers@sungard.com]
> > > Sent: Tuesday, 26 February 2013 8:22 PM
> > > To: cloudstack-dev@incubator.apache.org
> > > Subject: Re: [CLOUDSTACK-241 ]Regions update
> > >
> > > On Tue, Feb 26, 2013 at 02:34:13PM +0530, Kishan Kavala wrote:
> > > > Removed API based account sync for Regions as discussed earlier [1] .
> > > Event framework will be used instead. I pushed the changes to master.
> > > commit: e37fdce125511535961c77a77d253ce232a954d0.
> > > > I'll be merging the same to 4.1 branch.
> > > >
> > > > [1]
> > > > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-
> > > dev/2013
> > > > 02.mbox/%3CCD3462CF.64A2%25chiradeep.vittal@citrix.com%3E
> > > >
> > >
> > > Is this something we really want to do now? Has the feature been
> > > QA'ed
> > yet?
> > > This seems pretty late to make a change to the basic function of
> > > the feature for 4.1.
> > >
> > > If my concern are overblown, then say so!
> > >
> > > -chip
> >
> > This commit only removes API based account data sync and it is
> > fairly isolated part of the code.
> > Events are already in place so no changes in that area.
> >
>
> Changes were merged to 4.1 branch. I also changed tabs to spaces in
> the related files, so the diff shows more changes than actual.
RE: [CLOUDSTACK-241 ]Regions update
Posted by Sangeetha Hariharan <Sa...@citrix.com>.
Thanks Kishan for your input.
Since we will now rely on Events Framework feature to publish events that could be used by admins to maintain data sync between regions , I have created test plan for this feature- https://cwiki.apache.org/confluence/display/CLOUDSTACK/Events+Framework+Test+plan .
This test plan addresses only a part of Event Framework feature that is needed by AWS regions feature for achieving data sync of Account/Domain/User objects between regions.
Please provide your feedback.
-Thanks
Sangeetha
-----Original Message-----
From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
Sent: Tuesday, March 12, 2013 5:53 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: [CLOUDSTACK-241 ]Regions update
Please find my response inline.
> -----Original Message-----
> From: Sangeetha Hariharan [mailto:Sangeetha.Hariharan@citrix.com]
> Sent: Saturday, 9 March 2013 1:14 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> I have updated the test cases according to the latest functional Spec
> which is to make use of Event frameworks instead of api based sync for
> domain/account/users.
> Test cases can be found here -
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Regions+T
> est+Plan . Please provide your feedback.
>
> I had the following questions:
>
> 1. In case of update/delete action from a region that is not the owner
> , API call will succeed as long as it has been able to forward the
> request to owner region and the owner region actually executed the
> command . Even after receiving a success from the API call, the
> changes will not be committed in this region. This seems like a
> confusing experience . Can we expect any message indicating to the user about the redirection of request?
>
[KK] Forwarding to owner region should be removed. Data sync is external to CloudStack.
> 2. In case of deleting domains/accounts from a region that is not the
> owner of this region , this will result in the domain/account being
> actually deleted from the owner region which will also result in all
> the resources like network and Vms being deleted. Is this acceptable?
[KK] When account/domain is deleted all resources will also be deleted.
>
> 3. Consider the case of domains/accounts (owner Region 1) that have
> users that are owned by 2 different regions , say user1 (owner Region
> 1) and user2 (owner Region2) . Which region is responsible for
> deletion of domain/account , since this deletion will also involve
> deletion of users which are now owned by 2 different regions?
>
[KK] Since data sync is external to CloudStack, we don't need the notion of owner region.
> 4. Why is there a need for getUser API ? When will this get used ?
[KK] getUser API is for components like object-store to authenticate and get account information
>
> 5. Can you include the response parameters for all the new API calls ?
[KK] I've added the response parameters to the spec.
>
> -Thanks
> Sangeetha
>
>
> -----Original Message-----
> From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> Sent: Thursday, February 28, 2013 12:53 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> > -----Original Message-----
> > From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> > Sent: Wednesday, 27 February 2013 12:07 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: [CLOUDSTACK-241 ]Regions update
> >
> > > -----Original Message-----
> > > From: Chip Childers [mailto:chip.childers@sungard.com]
> > > Sent: Tuesday, 26 February 2013 8:22 PM
> > > To: cloudstack-dev@incubator.apache.org
> > > Subject: Re: [CLOUDSTACK-241 ]Regions update
> > >
> > > On Tue, Feb 26, 2013 at 02:34:13PM +0530, Kishan Kavala wrote:
> > > > Removed API based account sync for Regions as discussed earlier [1] .
> > > Event framework will be used instead. I pushed the changes to master.
> > > commit: e37fdce125511535961c77a77d253ce232a954d0.
> > > > I'll be merging the same to 4.1 branch.
> > > >
> > > > [1]
> > > > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-
> > > dev/2013
> > > > 02.mbox/%3CCD3462CF.64A2%25chiradeep.vittal@citrix.com%3E
> > > >
> > >
> > > Is this something we really want to do now? Has the feature been
> > > QA'ed
> > yet?
> > > This seems pretty late to make a change to the basic function of
> > > the feature for 4.1.
> > >
> > > If my concern are overblown, then say so!
> > >
> > > -chip
> >
> > This commit only removes API based account data sync and it is
> > fairly isolated part of the code.
> > Events are already in place so no changes in that area.
> >
>
> Changes were merged to 4.1 branch. I also changed tabs to spaces in
> the related files, so the diff shows more changes than actual.
RE: [CLOUDSTACK-241 ]Regions update
Posted by Kishan Kavala <Ki...@citrix.com>.
Please find my response inline.
> -----Original Message-----
> From: Sangeetha Hariharan [mailto:Sangeetha.Hariharan@citrix.com]
> Sent: Saturday, 9 March 2013 1:14 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> I have updated the test cases according to the latest functional Spec which is
> to make use of Event frameworks instead of api based sync for
> domain/account/users.
> Test cases can be found here -
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Regions+T
> est+Plan . Please provide your feedback.
>
> I had the following questions:
>
> 1. In case of update/delete action from a region that is not the owner , API
> call will succeed as long as it has been able to forward the request to owner
> region and the owner region actually executed the command . Even after
> receiving a success from the API call, the changes will not be committed in
> this region. This seems like a confusing experience . Can we expect any
> message indicating to the user about the redirection of request?
>
[KK] Forwarding to owner region should be removed. Data sync is external to CloudStack.
> 2. In case of deleting domains/accounts from a region that is not the owner
> of this region , this will result in the domain/account being actually deleted
> from the owner region which will also result in all the resources like network
> and Vms being deleted. Is this acceptable?
[KK] When account/domain is deleted all resources will also be deleted.
>
> 3. Consider the case of domains/accounts (owner Region 1) that have users
> that are owned by 2 different regions , say user1 (owner Region 1) and user2
> (owner Region2) . Which region is responsible for deletion of
> domain/account , since this deletion will also involve deletion of users which
> are now owned by 2 different regions?
>
[KK] Since data sync is external to CloudStack, we don't need the notion of owner region.
> 4. Why is there a need for getUser API ? When will this get used ?
[KK] getUser API is for components like object-store to authenticate and get account information
>
> 5. Can you include the response parameters for all the new API calls ?
[KK] I've added the response parameters to the spec.
>
> -Thanks
> Sangeetha
>
>
> -----Original Message-----
> From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> Sent: Thursday, February 28, 2013 12:53 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> > -----Original Message-----
> > From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> > Sent: Wednesday, 27 February 2013 12:07 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: RE: [CLOUDSTACK-241 ]Regions update
> >
> > > -----Original Message-----
> > > From: Chip Childers [mailto:chip.childers@sungard.com]
> > > Sent: Tuesday, 26 February 2013 8:22 PM
> > > To: cloudstack-dev@incubator.apache.org
> > > Subject: Re: [CLOUDSTACK-241 ]Regions update
> > >
> > > On Tue, Feb 26, 2013 at 02:34:13PM +0530, Kishan Kavala wrote:
> > > > Removed API based account sync for Regions as discussed earlier [1] .
> > > Event framework will be used instead. I pushed the changes to master.
> > > commit: e37fdce125511535961c77a77d253ce232a954d0.
> > > > I'll be merging the same to 4.1 branch.
> > > >
> > > > [1]
> > > > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-
> > > dev/2013
> > > > 02.mbox/%3CCD3462CF.64A2%25chiradeep.vittal@citrix.com%3E
> > > >
> > >
> > > Is this something we really want to do now? Has the feature been
> > > QA'ed
> > yet?
> > > This seems pretty late to make a change to the basic function of the
> > > feature for 4.1.
> > >
> > > If my concern are overblown, then say so!
> > >
> > > -chip
> >
> > This commit only removes API based account data sync and it is fairly
> > isolated part of the code.
> > Events are already in place so no changes in that area.
> >
>
> Changes were merged to 4.1 branch. I also changed tabs to spaces in the
> related files, so the diff shows more changes than actual.
RE: [CLOUDSTACK-241 ]Regions update
Posted by Sangeetha Hariharan <Sa...@citrix.com>.
I have updated the test cases according to the latest functional Spec which is to make use of Event frameworks instead of api based sync for domain/account/users.
Test cases can be found here - https://cwiki.apache.org/confluence/display/CLOUDSTACK/AWS+Regions+Test+Plan . Please provide your feedback.
I had the following questions:
1. In case of update/delete action from a region that is not the owner , API call will succeed as long as it has been able to forward the request to owner region and the owner region actually executed the command . Even after receiving a success from the API call, the changes will not be committed in this region. This seems like a confusing experience . Can we expect any message indicating to the user about the redirection of request?
2. In case of deleting domains/accounts from a region that is not the owner of this region , this will result in the domain/account being actually deleted from the owner region which will also result in all the resources like network and Vms being deleted. Is this acceptable?
3. Consider the case of domains/accounts (owner Region 1) that have users that are owned by 2 different regions , say user1 (owner Region 1) and user2 (owner Region2) . Which region is responsible for deletion of domain/account , since this deletion will also involve deletion of users which are now owned by 2 different regions?
4. Why is there a need for getUser API ? When will this get used ?
5. Can you include the response parameters for all the new API calls ?
-Thanks
Sangeetha
-----Original Message-----
From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
Sent: Thursday, February 28, 2013 12:53 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: [CLOUDSTACK-241 ]Regions update
> -----Original Message-----
> From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> Sent: Wednesday, 27 February 2013 12:07 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> > -----Original Message-----
> > From: Chip Childers [mailto:chip.childers@sungard.com]
> > Sent: Tuesday, 26 February 2013 8:22 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Re: [CLOUDSTACK-241 ]Regions update
> >
> > On Tue, Feb 26, 2013 at 02:34:13PM +0530, Kishan Kavala wrote:
> > > Removed API based account sync for Regions as discussed earlier [1] .
> > Event framework will be used instead. I pushed the changes to master.
> > commit: e37fdce125511535961c77a77d253ce232a954d0.
> > > I'll be merging the same to 4.1 branch.
> > >
> > > [1]
> > > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-
> > dev/2013
> > > 02.mbox/%3CCD3462CF.64A2%25chiradeep.vittal@citrix.com%3E
> > >
> >
> > Is this something we really want to do now? Has the feature been
> > QA'ed
> yet?
> > This seems pretty late to make a change to the basic function of the
> > feature for 4.1.
> >
> > If my concern are overblown, then say so!
> >
> > -chip
>
> This commit only removes API based account data sync and it is fairly
> isolated part of the code.
> Events are already in place so no changes in that area.
>
Changes were merged to 4.1 branch. I also changed tabs to spaces in the related files, so the diff shows more changes than actual.
RE: [CLOUDSTACK-241 ]Regions update
Posted by Kishan Kavala <Ki...@citrix.com>.
> -----Original Message-----
> From: Kishan Kavala [mailto:Kishan.Kavala@citrix.com]
> Sent: Wednesday, 27 February 2013 12:07 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [CLOUDSTACK-241 ]Regions update
>
> > -----Original Message-----
> > From: Chip Childers [mailto:chip.childers@sungard.com]
> > Sent: Tuesday, 26 February 2013 8:22 PM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Re: [CLOUDSTACK-241 ]Regions update
> >
> > On Tue, Feb 26, 2013 at 02:34:13PM +0530, Kishan Kavala wrote:
> > > Removed API based account sync for Regions as discussed earlier [1] .
> > Event framework will be used instead. I pushed the changes to master.
> > commit: e37fdce125511535961c77a77d253ce232a954d0.
> > > I'll be merging the same to 4.1 branch.
> > >
> > > [1]
> > > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-
> > dev/2013
> > > 02.mbox/%3CCD3462CF.64A2%25chiradeep.vittal@citrix.com%3E
> > >
> >
> > Is this something we really want to do now? Has the feature been QA'ed
> yet?
> > This seems pretty late to make a change to the basic function of the
> > feature for 4.1.
> >
> > If my concern are overblown, then say so!
> >
> > -chip
>
> This commit only removes API based account data sync and it is fairly isolated
> part of the code.
> Events are already in place so no changes in that area.
>
Changes were merged to 4.1 branch. I also changed tabs to spaces in the related files, so the diff shows more changes than actual.
RE: [CLOUDSTACK-241 ]Regions update
Posted by Kishan Kavala <Ki...@citrix.com>.
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Tuesday, 26 February 2013 8:22 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [CLOUDSTACK-241 ]Regions update
>
> On Tue, Feb 26, 2013 at 02:34:13PM +0530, Kishan Kavala wrote:
> > Removed API based account sync for Regions as discussed earlier [1] .
> Event framework will be used instead. I pushed the changes to master.
> commit: e37fdce125511535961c77a77d253ce232a954d0.
> > I'll be merging the same to 4.1 branch.
> >
> > [1]
> > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-
> dev/2013
> > 02.mbox/%3CCD3462CF.64A2%25chiradeep.vittal@citrix.com%3E
> >
>
> Is this something we really want to do now? Has the feature been QA'ed yet?
> This seems pretty late to make a change to the basic function of the feature
> for 4.1.
>
> If my concern are overblown, then say so!
>
> -chip
This commit only removes API based account data sync and it is fairly isolated part of the code.
Events are already in place so no changes in that area.
RE: [CLOUDSTACK-241 ]Regions update
Posted by Sudha Ponnaganti <su...@citrix.com>.
Testing is planned but not sure what level of functionality exists in 4.1. My understanding is that it is not completely done to be QA'ed yet.
Kishan can confirm
-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]
Sent: Tuesday, February 26, 2013 6:52 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [CLOUDSTACK-241 ]Regions update
On Tue, Feb 26, 2013 at 02:34:13PM +0530, Kishan Kavala wrote:
> Removed API based account sync for Regions as discussed earlier [1] . Event framework will be used instead. I pushed the changes to master. commit: e37fdce125511535961c77a77d253ce232a954d0.
> I'll be merging the same to 4.1 branch.
>
> [1]
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/2013
> 02.mbox/%3CCD3462CF.64A2%25chiradeep.vittal@citrix.com%3E
>
Is this something we really want to do now? Has the feature been QA'ed yet? This seems pretty late to make a change to the basic function of the feature for 4.1.
If my concern are overblown, then say so!
-chip
Re: [CLOUDSTACK-241 ]Regions update
Posted by Chip Childers <ch...@sungard.com>.
On Tue, Feb 26, 2013 at 02:34:13PM +0530, Kishan Kavala wrote:
> Removed API based account sync for Regions as discussed earlier [1] . Event framework will be used instead. I pushed the changes to master. commit: e37fdce125511535961c77a77d253ce232a954d0.
> I'll be merging the same to 4.1 branch.
>
> [1] http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201302.mbox/%3CCD3462CF.64A2%25chiradeep.vittal@citrix.com%3E
>
Is this something we really want to do now? Has the feature been QA'ed
yet? This seems pretty late to make a change to the basic function of
the feature for 4.1.
If my concern are overblown, then say so!
-chip