On Thu, Jul 7, 2016 at 7:11 PM, Osura Rathnayake <[email protected]> wrote:
> Hi Mentors, > > > In addition to refining the membership scheme code, I looked into > following features of Azure. > > Good findings Osura, please find few questions inline: > > > *Azure dynamic load balancing* > > > Azure has a native load balancer which is very easy to configure. It’s a > layer 4 (TCP, UDP) load balancer which helps to spread traffic among > healthy virtual machines. Following are some key terms you need to know. > > Can members be dynamically added and removed to/from a load balancer? To check this we may need to explore how autoscaling works. On AWS this is handled with autoscaling groups [3] > > *Capturing Virtual Machine Images as templates* > > > Azure provides the feature of generalizing and capturing virtual machines > so that they can be used as templates. This is very useful and time saving > when the production environment has many instances of the same kind of > virtual machine. When the virtual machine is being generalized all the data > in user directories are erased so better to have wso2 product directory not > in "/home/*". More about this can be found here [2]. > > Once the virtual machine is captured, it is stored in the storage account > that is associated with the virtual machine. You can either download this > or use directly by referring to the URI when you want to make other virtual > machines with this template. What would be awesome is if we can fully > configure the virtual machine with a given product and make it available to > users. > > > Yes, this is mandatory. Otherwise we would not be able to autoscale a server cluster. I'm sorry I may have missed, how did it go with centralized logging? [3] http://docs.aws.amazon.com/autoscaling/latest/userguide/AutoScalingGroup.html Thanks > [1] > https://azure.microsoft.com/en-us/documentation/articles/load-balancer-overview/ > > [2] > https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-capture-image/ > > > Thanks, > > On Wed, Jul 6, 2016 at 12:18 PM, Osura Rathnayake <[email protected]> > wrote: > >> Hi Akila, >> >> Please refer to the screenshots that I have attached. When I updated >> localMemberPort to 4200, I can see it being reflected in logs when members >> are joining. So should I still make modifications in the code? >> >> .gitignore was added. >> >> okay I will write test cases in testNG and update >> >> thanks, >> >> On Wed, Jul 6, 2016 at 9:06 AM, Akila Ravihansa Perera < >> [email protected]> wrote: >> >>> Hi, >>> >>> On Tue, Jul 5, 2016 at 11:38 AM, Osura Rathnayake <[email protected]> >>> wrote: >>> >>>> Hi Akila, >>>> >>>> Please check the modified code. It now takes the value which is >>>> specified as localMemberPort in axis2.xml. >>>> >>> >>> I still don't see any change to the logic of how member address is >>> calculated. Can you double check? >>> >>> Please make sure "target/**" directories are ignored from .gitignore. >>> These shouldn't be in the repo [1]. You might also need to ignore any IDE >>> specific files. Have a look at .gitignore in Kubernetes artifacts [2]. >>> >>> I see that you have committed some test cases based on JUnit. Please >>> note that as a platform we are moving to testng framework so better to use >>> that. >>> @Imesh, Isuru: Please correct me if I'm wrong. >>> >>> Shall we get a repo created under wso2-incubator for this? >>> >>> [1] https://github.com/osuran/azure-membership-scheme/tree/master/target >>> [2] https://github.com/wso2/kubernetes-artifacts/blob/master/.gitignore >>> >>> Thanks. >>> -- >>> Akila Ravihansa Perera >>> WSO2 Inc.; http://wso2.com/ >>> >>> Blog: http://ravihansa3000.blogspot.com >>> >> >> >> >> -- >> Regards, >> Osura Rathnayake >> > > > > -- > Regards, > Osura Rathnayake > -- *Imesh Gunaratne* Software Architect WSO2 Inc: http://wso2.com T: +94 11 214 5345 M: +94 77 374 2057 W: https://medium.com/@imesh TW: @imesh
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
