Failures are stored in region_sync table in cloud DB. Sample entry:
mysql> select * from region_sync\G *************************** 1. row *************************** id: 3 region_id: 2 api: command=createUser&username=u6&password=u6&firstname=u6&lastname=u6&email=dsfd%40dsf.com&account=admin&domainid=53c7eafd-652b-11e2-821f-d4bed9117aff&userid=fb4bf544-f2f9-440a-9acc-8fe74ae5ed28®ionid=1 created: 2013-01-29 06:15:18 processed: 0 ********************************************************** Procedure to apply changes: 1. get all unprocessed sync items (where processed = 0) 2. Apply changes using the region end_point and api 3. Mark it as processed. Regards, Kishan > -----Original Message----- > From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] > Sent: Wednesday, 30 January 2013 5:12 AM > To: CloudStack DeveloperList > Subject: Re: Questions related to Regions Feature > > > I commented in the review as well. When you say that it "can be stored", is it > ACTUALLY stored? Who is maintaining this log file and what is the procedure > to apply these changes? > > > > > >On 1/25/13 3:29 AM, "Kishan Kavala" <kishan.kav...@citrix.com> wrote: > > > >>We use API calls to sync data and this is working fine when all the > >>Regions are up. When an API call to sync data fails (Region is down or > >>for any reason), it can be stored in a table or a log file. Cloud > >>operator can then apply these changes offline.