Hi Imesh,

I just shared the proposal in gsoc site. but it still needs changes and i'm
working on those changes.

thanks

On Fri, Mar 25, 2016 at 9:41 AM, Imesh Gunaratne <im...@wso2.com> wrote:

> Hi Osura,
>
> It looks like you have not uploaded the project proposal to GSoC website
> yet. Please do it immediately and do the changes afterwards. Today is the
> last day.
>
> Thanks
>
> On Wed, Mar 23, 2016 at 1:18 PM, Osura Rathnayake <osura...@gmail.com>
> wrote:
>
>> okay sir 3 pm would be fine.
>>
>> thanks and regards,
>> Osura
>>
>> On Wed, Mar 23, 2016 at 1:16 PM, Imesh Gunaratne <im...@wso2.com> wrote:
>>
>>>
>>>
>>> On Wed, Mar 23, 2016 at 1:09 PM, Osura Rathnayake <osura...@gmail.com>
>>> wrote:
>>>
>>>> Hi Sir,
>>>>
>>>> Okay i will prepare a proposal and send to you. what time would be
>>>> convenient for you to have a hangout?
>>>>
>>>
>>> How about at 3 pm today?
>>>
>>> Thanks
>>>
>>>>
>>>> thanks and regards,
>>>> Osura
>>>>
>>>> On Wed, Mar 23, 2016 at 10:47 AM, Imesh Gunaratne <im...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Osura,
>>>>>
>>>>> On Wed, Mar 23, 2016 at 12:38 AM, Osura Rathnayake <osura...@gmail.com
>>>>> > wrote:
>>>>>
>>>>>> Hi sir,
>>>>>>
>>>>>> This is what we found when we were going through the API.
>>>>>>
>>>>>> 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. Can we use this method to identify a group 
>>>>>> of
>>>>>> VMs?  or can't we simply assign a tag to set of VM and identify them 
>>>>>> using
>>>>>> that tag?
>>>>>>
>>>>>> Yes I think this is good. Can you please prepare a project proposal
>>>>> and share it privately? Will review it and give you feedback. If you need
>>>>> more information will have a Hangout today afternoon.
>>>>>
>>>>> Thanks
>>>>>
>>>>>>
>>>>>>
>>>>>> [1] https://msdn.microsoft.com/en-us/library/azure/mt163654.aspx
>>>>>> [2] https://msdn.microsoft.com/en-us/library/azure/mt163611.aspx
>>>>>>
>>>>>> Thanks and regards,
>>>>>> Osura
>>>>>>
>>>>>> On Mon, Mar 21, 2016 at 11:22 PM, Imesh Gunaratne <im...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Osura/Sahan,
>>>>>>>
>>>>>>> Please try to do the following first:
>>>>>>>
>>>>>>>    1. Create a free Azure account
>>>>>>>    2. Evaluate virtual machine and container features in Azure. As
>>>>>>>    I saw container support is very primitive at the moment. We can use 
>>>>>>> K8S on
>>>>>>>    Azure for container based deployments. In this project will focus on 
>>>>>>> VM
>>>>>>>    based deployment.
>>>>>>>    3. Go through the Azure API and see how we can identify a group
>>>>>>>    of VMs. On AWS we do this by using security groups. We call this 
>>>>>>> group a
>>>>>>>    cluster.
>>>>>>>    4. Next try to start a WSO2 product in a VM.
>>>>>>>    5. Afterwards will try to implement a Carbon Membership Scheme
>>>>>>>    for Azure using the Azure API and the above grouping feature.
>>>>>>>    6. Next we need to identify how to use native Azure features for
>>>>>>>    implementing following:
>>>>>>>
>>>>>>>
>>>>>>>    - Auto healing
>>>>>>>       - Autoscaling
>>>>>>>       - Dynamic load balancing
>>>>>>>       - Multi-tenancy
>>>>>>>       - Configuration orchestration
>>>>>>>       - Artifact distribution
>>>>>>>       - Software update distribution
>>>>>>>       - Multi-region/cloud deployments
>>>>>>>       - Centralized logging
>>>>>>>       - Monitoring
>>>>>>>       - Metering
>>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> On Mon, Mar 21, 2016 at 2:25 PM, Osura Rathnayake <
>>>>>>> osura...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi Sir,
>>>>>>>>
>>>>>>>> Can you please direct us on how we should get started ? As in what
>>>>>>>> would be the first step and so on.
>>>>>>>>
>>>>>>>> regards,
>>>>>>>> Osura
>>>>>>>>
>>>>>>>> On Mon, Mar 14, 2016 at 5:18 PM, Imesh Gunaratne <im...@wso2.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi Osura,
>>>>>>>>>
>>>>>>>>> Please note that we changed this project description to the
>>>>>>>>> following:
>>>>>>>>>
>>>>>>>>> https://docs.wso2.com/display/GSoC/Project+Proposals+for+2016#ProjectProposalsfor2016-Proposal29:[Cloud]NativeCloudSupportforRunningWSO2MiddlewareonMicrosoftAzure
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>> On Sat, Mar 5, 2016 at 3:25 PM, Osura Rathnayake <
>>>>>>>>> osura...@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi sir,
>>>>>>>>>>
>>>>>>>>>> I followed the steps in [1].
>>>>>>>>>>
>>>>>>>>>> [1] http://mesos.apache.org/gettingstarted/
>>>>>>>>>>
>>>>>>>>>> thanks and regards
>>>>>>>>>>
>>>>>>>>>> On Sat, Mar 5, 2016 at 3:17 PM, Imesh Gunaratne <im...@wso2.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Can you please explain how you installed Mesos on a Ubuntu
>>>>>>>>>>> machine?
>>>>>>>>>>>
>>>>>>>>>>> Thanks
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Saturday, March 5, 2016, Osura Rathnayake <osura...@gmail.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Sir,
>>>>>>>>>>>>
>>>>>>>>>>>> We were able to install mesos, docker and WSO2 carbon on a
>>>>>>>>>>>> Ubuntu machine. Furthermore we installed wso2 ESB and AS through 
>>>>>>>>>>>> docker.
>>>>>>>>>>>> Currently we are working on understanding how K8S works in this 
>>>>>>>>>>>> scenario.
>>>>>>>>>>>> After that what would be the next step?
>>>>>>>>>>>>
>>>>>>>>>>>> thanks and regards,
>>>>>>>>>>>> Osura Rathnayake, Sahan Wickramaarachchi, Vishwa Jayaratne,
>>>>>>>>>>>> Allan Barthelot
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Feb 29, 2016 at 12:38 PM, Imesh Gunaratne <
>>>>>>>>>>>> im...@wso2.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Osura,
>>>>>>>>>>>>>
>>>>>>>>>>>>> It's nice to hear your interest on this project. The starting
>>>>>>>>>>>>> point would be to install Mesos and see how it works. Then try to 
>>>>>>>>>>>>> deploy a
>>>>>>>>>>>>> WSO2 product on Mesos using Docker. Then understand how Carbon 
>>>>>>>>>>>>> clustering
>>>>>>>>>>>>> works including K8S membership scheme [1] we have implemented for 
>>>>>>>>>>>>> the same
>>>>>>>>>>>>> purpose on K8S. Later on move to other native PaaS features 
>>>>>>>>>>>>> needed.
>>>>>>>>>>>>>
>>>>>>>>>>>>> [1]
>>>>>>>>>>>>> https://github.com/wso2/kubernetes-artifacts/tree/master/common/kubernetes-membership-scheme
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Feb 29, 2016 at 12:29 PM, Osura Rathnayake <
>>>>>>>>>>>>> osura...@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Dear Sir,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We are a group of 4th year students following the Computer
>>>>>>>>>>>>>> Systems and Networking degree program at SLIIT. We are 
>>>>>>>>>>>>>> interested in
>>>>>>>>>>>>>> undertaking above mentioned project as our 4th year research 
>>>>>>>>>>>>>> project.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> As 4th year CSN students we have a fairly good understanding
>>>>>>>>>>>>>> in PaaS concepts and Java language. We have a basic 
>>>>>>>>>>>>>> understanding of basic
>>>>>>>>>>>>>> features of WSO2 Carbon.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> We were asked to contact you by Senior Lecturer Mr. Lakmal
>>>>>>>>>>>>>> Rupasinghe.
>>>>>>>>>>>>>> Please get back to us soon.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>> Osura Rathnayake, Sahan Wickramaarachchi, Vishwa Jayaratne,
>>>>>>>>>>>>>> Allan Barthelot
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> *Imesh Gunaratne*
>>>>>>>>>>>>> Senior Technical Lead
>>>>>>>>>>>>> WSO2 Inc: http://wso2.com
>>>>>>>>>>>>> T: +94 11 214 5345 M: +94 77 374 2057
>>>>>>>>>>>>> W: http://imesh.io
>>>>>>>>>>>>> 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
>>>>>>>>>>> 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
>>>>>>>>> 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
>>>>>>> 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
>>>>> 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
>>> 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
> Lean . Enterprise . Middleware
>
>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to