Hi mentors, As you might already know, Azure has two deployment models , azure classic (old portal) and azure resource manager (ARM)(new portal). Unfortunately some functionalities of classic is not available in ARM vice versa[1] but microsoft is rapidly developing all the functionalities across both models. Also certain API references [2] are not available for both the models, for an example, for network both classic and ARM API references are available but for network security groups only classic is available, while network security groups is a supported feature in ARM. shall we have a hangout to discuss this matter?
[1] https://blog.kloud.com.au/2016/04/05/azure-classic-vs-azure-resource-manager/ [2] https://msdn.microsoft.com/en-us/library/azure/mt420159.aspx On Fri, May 20, 2016 at 11:05 AM, Isuru Haththotuwa <isu...@wso2.com> wrote: > Hi Osura, > > Are you joining the hangout now? > > On Thu, May 19, 2016 at 7:37 PM, Osura Rathnayake <osura...@gmail.com> > wrote: > >> Hi Isuru, >> >> It's no problem. Okay let's have a hangout at 11 o'clock tomorrow. >> >> On Thursday, May 19, 2016, Isuru Haththotuwa <isu...@wso2.com> wrote: >> >>> Hi Osura, >>> >>> Sorry for the delayed response. >>> >>> Shall we have a hangout at 11 AM on 20th May (Friday)? >>> >>> On Tue, May 17, 2016 at 9:09 PM, Osura Rathnayake <osura...@gmail.com> >>> wrote: >>> >>>> Hi Imesh, >>>> >>>> Shall we have a hangout on Thursday or so? >>>> >>>> >>>> On Thu, May 12, 2016 at 8:26 PM, Imesh Gunaratne <im...@wso2.com> >>>> wrote: >>>> >>>>> Hi Osura, >>>>> >>>>> On Thu, May 12, 2016 at 8:09 PM, Osura Rathnayake <osura...@gmail.com> >>>>> wrote: >>>>> >>>>>> Hi Mentors, >>>>>> >>>>>> I created a github repository so that all the work related to this >>>>>> project can be accumulated with ease. >>>>>> here is the link https://github.com/osuran/azure-membership-scheme. >>>>>> >>>>> >>>>> Great! Will you be able to arrange a Hangout and demonstrate what you >>>>> did so far? >>>>> >>>>> Thanks >>>>> >>>>> On Thu, May 12, 2016 at 8:09 PM, Osura Rathnayake <osura...@gmail.com> >>>>> wrote: >>>>> >>>>>> Hi Mentors, >>>>>> >>>>>> I created a github repository so that all the work related to this >>>>>> project can be accumulated with ease. >>>>>> here is the link https://github.com/osuran/azure-membership-scheme. >>>>>> >>>>>> On Wed, May 11, 2016 at 11:22 AM, Osura Rathnayake < >>>>>> osura...@gmail.com> wrote: >>>>>> >>>>>>> Hi Mentors, >>>>>>> >>>>>>> I sorted out all the errors and the cluster is up and running. Now I >>>>>>> can see the log messages of members joining and leaving. >>>>>>> >>>>>>> >>>>>>> On Wed, May 11, 2016 at 11:04 AM, Isuru Haththotuwa <isu...@wso2.com >>>>>>> > wrote: >>>>>>> >>>>>>>> Hi Osura, >>>>>>>> >>>>>>>> Please refer [1] for configuring deployment synchronizer. >>>>>>>> >>>>>>>> Initially, its ok even if you disable the deployment synchronizer >>>>>>>> and test the clustering. >>>>>>>> >>>>>>>> [1]. >>>>>>>> https://docs.wso2.com/display/CLUSTER44x/Configuring+SVN-Based+Deployment+Synchronizer >>>>>>>> >>>>>>>> On Wed, May 11, 2016 at 10:55 AM, Osura Rathnayake < >>>>>>>> osura...@gmail.com> wrote: >>>>>>>> >>>>>>>>> Hi All, >>>>>>>>> >>>>>>>>> Thank you very much. I got it sorted out. I created a new user and >>>>>>>>> granted permission on it. >>>>>>>>> Can you please tell me the format of svn url and access protocol >>>>>>>>> when configuring <DeploymentSynchronizer> , my repository is >>>>>>>>> /home/as/svnrepo. I have attached the error I got as well. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> On Wed, May 11, 2016 at 7:13 AM, Imesh Gunaratne <im...@wso2.com> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Tue, May 10, 2016 at 11:12 PM, Osura Rathnayake < >>>>>>>>>> osura...@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Hi Imesh, >>>>>>>>>>> >>>>>>>>>>> Now i'm getting this error. I can't connect to the DB from the >>>>>>>>>>> client either. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Credentials might be correct, I think the issue is with the >>>>>>>>>> permission. You might need to grant permission to the relevant >>>>>>>>>> databases to >>>>>>>>>> your user for the given IP address. Please refer [1]. >>>>>>>>>> >>>>>>>>>> [1] http://dev.mysql.com/doc/refman/5.5/en/grant.html >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Thanks >>>>>>>>>>> >>>>>>>>>>> On Tue, May 10, 2016 at 9:46 PM, Imesh Gunaratne <im...@wso2.com >>>>>>>>>>> > wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Tue, May 10, 2016 at 9:43 PM, Osura Rathnayake < >>>>>>>>>>>> osura...@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi Mentors, >>>>>>>>>>>>> >>>>>>>>>>>>> when i was trying to up the manager node, i kept getting an >>>>>>>>>>>>> error and a screenshot of it is attached herewith. There is no >>>>>>>>>>>>> problem with >>>>>>>>>>>>> network connectivity and dns resolution. Also a diagram of my >>>>>>>>>>>>> setup is >>>>>>>>>>>>> attached. please have a look. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> This looks like a database connectivity issue. >>>>>>>>>>>> >>>>>>>>>>>> Can you please try to install a mysql client in one of the >>>>>>>>>>>> hosts that AS is installed and check whether it can connect to the >>>>>>>>>>>> database >>>>>>>>>>>> server? >>>>>>>>>>>> >>>>>>>>>>>> Thanks >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> thanks and regards, >>>>>>>>>>>>> Osura >>>>>>>>>>>>> >>>>>>>>>>>>> On Tue, May 10, 2016 at 6:40 AM, Isuru Haththotuwa < >>>>>>>>>>>>> isu...@wso2.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi Osura, >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, May 9, 2016 at 11:22 PM, Osura Rathnayake < >>>>>>>>>>>>>> osura...@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi mentors, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> When setting up the DB according to [1], should shared >>>>>>>>>>>>>>> REGISTRY_DB and shared WSO2_USER_DB be resided on a separate >>>>>>>>>>>>>>> server other >>>>>>>>>>>>>>> than the manager/worker node? if so can I use the same server i >>>>>>>>>>>>>>> used for >>>>>>>>>>>>>>> load balancer for this purpose? >>>>>>>>>>>>>>> >>>>>>>>>>>>>> Yes, you can. >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> [1] >>>>>>>>>>>>>>> https://docs.wso2.com/display/CLUSTER44x/Setting+up+the+Database >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Thanks and Regards >>>>>>>>>>>>>>> Osura >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Sun, May 1, 2016 at 9:53 AM, Imesh Gunaratne < >>>>>>>>>>>>>>> im...@wso2.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Sat, Apr 30, 2016 at 9:20 PM, Osura Rathnayake < >>>>>>>>>>>>>>>> osura...@gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi Imesh, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Thank you very much for the guidelines. I will do as you >>>>>>>>>>>>>>>>> have instructed and let you know the progress. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Great! Let us know if you find any problems. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>>> Osura >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Saturday, April 30, 2016, Imesh Gunaratne < >>>>>>>>>>>>>>>>> im...@wso2.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi Osura, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> It's nice to hear from you. I think it would be better if >>>>>>>>>>>>>>>>>> you can follow below steps: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 1. Implementing WSO2 Azure membership scheme: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> - First understand how WSO2 Carbon works by setting >>>>>>>>>>>>>>>>>> up a WSO2 Application Server worker/manager deployment on >>>>>>>>>>>>>>>>>> Azure. >>>>>>>>>>>>>>>>>> - Use WKA membership scheme for this and see how >>>>>>>>>>>>>>>>>> clustering works. >>>>>>>>>>>>>>>>>> - Then go through the WSO2 Kubernetes membership >>>>>>>>>>>>>>>>>> scheme source code. >>>>>>>>>>>>>>>>>> - Afterwards implement a new WSO2 membership scheme >>>>>>>>>>>>>>>>>> for Azure. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 2. Next see how each of the following can be setup on >>>>>>>>>>>>>>>>>> Azure using native features: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> - Auto healing >>>>>>>>>>>>>>>>>> - Autoscaling >>>>>>>>>>>>>>>>>> - Dynamic load balancing >>>>>>>>>>>>>>>>>> - Centralized logging >>>>>>>>>>>>>>>>>> - Monitoring >>>>>>>>>>>>>>>>>> - Metering >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Fri, Apr 29, 2016 at 8:07 PM, Osura Rathnayake < >>>>>>>>>>>>>>>>>> osura...@gmail.com> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi All, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Thank you very much for accepting my proposal. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Yes these days i am working on understanding how >>>>>>>>>>>>>>>>>>> hazelcast behaves. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I have already come across some of Azure API references >>>>>>>>>>>>>>>>>>> that can be used to identify a group of VMs. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Network Security Group (NSG) is the equivalent AWS >>>>>>>>>>>>>>>>>>> Security group that we could find in azure. And this [1] is >>>>>>>>>>>>>>>>>>> the API >>>>>>>>>>>>>>>>>>> reference that can be used to get information about a >>>>>>>>>>>>>>>>>>> particular NSG. There >>>>>>>>>>>>>>>>>>> under networkInterfaces.id element, we can get a collection >>>>>>>>>>>>>>>>>>> of references to Network Interface Cards that reference >>>>>>>>>>>>>>>>>>> this NSG. And then >>>>>>>>>>>>>>>>>>> using that we can get information about NICs [2]. There >>>>>>>>>>>>>>>>>>> under virtualMachine >>>>>>>>>>>>>>>>>>> element, we can get the VM associated with that NIC. I >>>>>>>>>>>>>>>>>>> think we can use >>>>>>>>>>>>>>>>>>> method to identify a group of VMs. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> [1] >>>>>>>>>>>>>>>>>>> https://msdn.microsoft.com/en-us/library/azure/mt163654.aspx >>>>>>>>>>>>>>>>>>> [2] >>>>>>>>>>>>>>>>>>> https://msdn.microsoft.com/en-us/library/azure/mt163611.aspx >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>>>>> Osura >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Fri, Apr 29, 2016 at 4:16 PM, Isuru Haththotuwa < >>>>>>>>>>>>>>>>>>> isu...@wso2.com> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Hi Osura, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> First of all, great work with the proposal and >>>>>>>>>>>>>>>>>>>> congratulations on getting selected! >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> As you know, this is the community bonding period which >>>>>>>>>>>>>>>>>>>> you can use to enhance your community relationship and of >>>>>>>>>>>>>>>>>>>> course to gain >>>>>>>>>>>>>>>>>>>> knowledge in the related areas. Hope you are right on it! >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Can you please send a brief update about the any >>>>>>>>>>>>>>>>>>>> project related work that you are doing now? Please copy >>>>>>>>>>>>>>>>>>>> the wso2 dev list ( >>>>>>>>>>>>>>>>>>>> dev@wso2.org) as well. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>> Thanks and Regards, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Isuru H. >>>>>>>>>>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>* >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> *Imesh Gunaratne* >>>>>>>>>>>>>>>>>> Senior Technical Lead >>>>>>>>>>>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>>>>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>>>>>>>>>>> W: http://imesh.io TW: @imesh >>>>>>>>>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> *Imesh Gunaratne* >>>>>>>>>>>>>>>> Senior Technical Lead >>>>>>>>>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>>>>>>>>> W: http://imesh.io TW: @imesh >>>>>>>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Thanks and Regards, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Isuru H. >>>>>>>>>>>>>> +94 716 358 048* <http://wso2.com/>* >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> *Imesh Gunaratne* >>>>>>>>>>>> Senior Technical Lead >>>>>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>>>>> W: http://imesh.io TW: @imesh >>>>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *Imesh Gunaratne* >>>>>>>>>> Senior Technical Lead >>>>>>>>>> WSO2 Inc: http://wso2.com >>>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>>>>>>> W: http://imesh.io TW: @imesh >>>>>>>>>> Lean . Enterprise . Middleware >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Thanks and Regards, >>>>>>>> >>>>>>>> Isuru H. >>>>>>>> +94 716 358 048* <http://wso2.com/>* >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Thanks and Regards, >>>>>>> Osura Rathnayake >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Thanks and Regards, >>>>>> Osura Rathnayake >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Imesh Gunaratne* >>>>> Senior Technical Lead >>>>> WSO2 Inc: http://wso2.com >>>>> T: +94 11 214 5345 M: +94 77 374 2057 >>>>> W: http://imesh.io TW: @imesh >>>>> Lean . Enterprise . Middleware >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thanks and Regards, >>>> Osura Rathnayake >>>> >>> >>> >>> >>> -- >>> Thanks and Regards, >>> >>> Isuru H. >>> +94 716 358 048* <http://wso2.com/>* >>> >>> >>> >> >> -- >> Thanks and Regards, >> Osura Rathnayake >> >> > > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* <http://wso2.com/>* > > > -- Thanks and Regards, Osura Rathnayake
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
