Hi Asanka, Thanks for the update.
Yeah.It is better to have a hangout for this.I think we can schedule that in early next week. Thanks, Gayan On Thu, Jun 18, 2015 at 6:18 PM, Asanka Sanjaya Herath <angal...@gmail.com> wrote: > Hi Isuru and Gayan, > > I'm implementing the logic for listening to topology events for > configuring the GCE LB. I have added my logic to configure method in > GCELoadBalancer class [1]. > > I have attached a flow chart for logic of configure method. As topology > changes, it analyses the topology and configure target pools, forwarding > rules and health checks in GCE according to the given topology. > > Currently I'm testing the logic using sample applications. > > I would like to have the hangout too. Please let me know a comfortable > time slot for you. > > [1]. > https://github.com/asankasanjaya/stratos/blob/master/extensions/load-balancer/gce-extension/src/main/java/org/apache/stratos/gce/extension/GCELoadBalancer.java > > On Tue, Jun 16, 2015 at 6:43 PM, Asanka Sanjaya Herath <angal...@gmail.com > > wrote: > >> Hi Gayan, >> >> >>> Can you please describe how do you achieve this? >> >> >> I think you are asking that how I implemented a way to wait for API call >> completion. There are three types of operations in GCE. >> 1. Global operations [1] >> 2. Region operations [2] >> 3. Zone operations [3] >> >> Therefore every time we do a API call, one of these operation objects >> will be created in IaaS side. That operation has an attribute called >> status. If status is DONE, operation is completed. So I periodically polled >> that operation object from IaaS in order to check whether the operation has >> been completed or not. >> >> I implemented three methods for this in GCEOperations.java class. >> >> a. waitForGlobalOperationCompletion(String operationName) >> b. waitForRegionOperationCompletion(String operationName) >> c. waitForZoneOperationCompletion(String operationName) >> >> >>> Once you implement the listening to topology events for configuring the >>> GCE LB, shall we have a Google hangout for this? >> >> >> I'm happy to have a hangout for this. I think I'll be able to complete >> that task within this week. I'll let you know once I'm done. >> >> [1]. >> https://cloud.google.com/compute/docs/reference/latest/globalOperations >> [2]. >> https://cloud.google.com/compute/docs/reference/latest/regionOperations >> [3]. >> https://cloud.google.com/compute/docs/reference/latest/zoneOperations >> >> On Tue, Jun 16, 2015 at 11:36 AM, Gayan Gunarathne <gay...@wso2.com> >> wrote: >> >>> >>> Hi Asanka, >>> >>> On Tue, Jun 16, 2015 at 4:27 AM, Asanka Sanjaya Herath < >>> angal...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> In last week I was working on following tasks. >>>> >>>> 1. Implementing a way to wait for API call completion >>>> >>> >>> Can you please describe how do you achieve this? >>> >>> >>>> 2. Getting the instance ID(The member ID in IaaS side) and adding the >>>> instance to target pool >>>> >>>> Now I think the basic functionality of the extension is completed. I >>>> tested it with a sample PHP application which is deployed using Stratos and >>>> I was able to access the application through the GCE load balancer >>>> IP(Corresponding forwarding rule IP). >>>> >>> >>> Great.Nice to hear that. >>> >>> >>>> Here I'm listing TO DOs according to my opinion. >>>> >>>> 1. Implement the reload() method >>>> 2. Implement the stop() method >>>> 3. Adding a firewall rule >>>> 4. Add validation checks >>>> 5. Statistics publishing to CEP >>>> 6. Exception handling >>>> 7. Testing >>>> 8. Discuss and implementing a better way to start the load >>>> balancer(Stand alone mode or in application sign up process). >>>> 9. Standardize the code >>>> >>>> Any comment is highly appreciated. >>>> >>>> Github repo: >>>> >>>> https://github.com/asankasanjaya/stratos/tree/master/extensions/load-balancer/gce-extension >>>> >>>> Good progress so far. Once you implement the listening to topology >>> events for configuring the GCE LB, shall we have a Google hangout for this? >>> >>> >>> -- >>>> Thanks, >>>> Regards, >>>> ASH >>>> >>> >>> >>> >>> -- >>> >>> Gayan Gunarathne >>> Technical Lead, WSO2 Inc. (http://wso2.com) >>> Committer & PMC Member, Apache Stratos >>> email : gay...@wso2.com | mobile : +94 766819985 >>> >>> >>> >>> >>> >>> >> >> >> >> -- >> Thanks, >> Regards, >> ASH >> > > > > -- > Thanks, > Regards, > ASH > -- Gayan Gunarathne Technical Lead, WSO2 Inc. (http://wso2.com) Committer & PMC Member, Apache Stratos email : gay...@wso2.com | mobile : +94 766819985
