[jira] [Assigned] (MYRIAD-261) Vagrant-libvirt for Apache Mesos Testbed

[Javi Roman (JIRA)]

 [ 
https://issues.apache.org/jira/browse/MYRIAD-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javi Roman reassigned MYRIAD-261:
-

Assignee: Javi Roman

> Vagrant-libvirt for Apache Mesos Testbed 
> -
>
> Key: MYRIAD-261
> URL: https://issues.apache.org/jira/browse/MYRIAD-261
> Project: Myriad
>  Issue Type: Sub-task
>Reporter: Javi Roman
>Assignee: Javi Roman
>Priority: Minor
>
> Vagrant libvirt environment for deploying Apache Mesos cluster. This 
> environment will be ready for Apache Myriad developing with a plain Apache 
> Mesos. We can test in this environment deployments on top of Apache Aurora 
> for example.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [DISCUSS] Apache Myriad Roadmap

[Juan P]

Thanks Javi Roman, this is an important step

On 3 April 2018 at 07:43, Javi Roman  wrote:

> Hi all!
>
> I've created a proposal (draft) of Project Roadmap [1]. The idea is to
> have a simple guide for re-activating the project. Please feel to
> comment your feedback, and any other modifications you consider.
>
> We have a lot of work to do!
>
> [1] https://goo.gl/xtD5oT
>
> --
> Javi Roman
>
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
>

Re: Regarding local environment based on Vagrant

[Juan P]

+1

On 4 April 2018 at 09:10, Javi Roman  wrote:

> I going to merge the PR [1] related with the Vagrant environment reworking.
>
> Please feel free to comment whatever enhance or inconvenient you think
> about the commit. I will merge he PR if there are no negative
> comments/votes.
>
>
> [1] https://github.com/apache/incubator-myriad/pull/107
> --
> Javi Roman
>
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
>
>
> On Mon, Feb 5, 2018 at 2:36 PM, Javi Roman 
> wrote:
> > For sure, this is something to include in the vagrant testbed. Good
> point.
> > --
> > Javi Roman
> >
> > Twitter: @javiromanrh
> > GitHub: github.com/javiroman
> > Linkedin: es.linkedin.com/in/javiroman
> > Big Data Blog: dataintensive.info
> >
> >
> > On Mon, Feb 5, 2018 at 10:01 AM, Juan P  wrote:
> >> Hello Javi, I think it's a great idea.
> >>
> >> Is it possible to prepare the automatic environment to perform automatic
> >> end-to-end tests (acceptance) or with a minimum of configuration?
> >>
> >> In later versions, would it be possible to include all the known Yarn
> >> frameworks and prepare some automatic use cases that serve as an example
> >> for the community and regression / integration test?
> >>
> >> Thank you
> >>
> >> On 4 February 2018 at 10:09, Javi Roman 
> wrote:
> >>
> >>> I would like share with you the strategy that I'm following for a
> >>> powerful local development environment for Myriad.
> >>>
> >>> The idea is to create an easy-to-use environment for new contributors,
> >>> setting up a Mesos cluster, or DCOS cluster (with hadoop running which
> >>> is a tedious task). I guess automate this task is a key point for
> >>> accelerating the development and focusing in the Myriad hacking.
> >>>
> >>> In this first task [1] I am working on Vagrant libvirt support for a
> >>> plain Mesos cluster. However the roadmap for this environment would
> >>> be:
> >>>
> >>> 1. vagrant-libvirt based cluster for Mesos, provisioned with Ansible
> >>> (already working in my environment).
> >>> 2. vagrant-libvirt based cluster for DC/OS provisioned with Ansible:
> >>> Easier environment for testing Myriad with Marathon, Mesos-DNS, VIPS,
> >>>  and so on.
> >>> 3. vagrant-virtualbox based cluster (maintain the original environment
> >>> used right now).
> >>>
> >>> The layout would be something like this:
> >>>
> >>> vagrant/
> >>> ├── libvirt
> >>> │   ├── dcos
> >>> │   │   └── Vagrantfile
> >>> │   └── mesos
> >>> │   └── Vagrantfile
> >>> └── virtualbox
> >>> └── Vagrantfile
> >>>
> >>>
> >>> In a second stage, the final scenario would be, only one folder with
> >>> one "smart" Vagrantfile for supporting Mesos and DC/OS for Linux and
> >>> OSX, the tool will be able of selecting the suitable virtualization
> >>> technology by user configuration.
> >>>
> >>> This is the idea.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/MYRIAD-257
> >>>
> >>> --
> >>> Javi Roman
> >>>
> >>> Twitter: @javiromanrh
> >>> GitHub: github.com/javiroman
> >>> Linkedin: es.linkedin.com/in/javiroman
> >>> Big Data Blog: dataintensive.info
> >>>
>

Re: Regarding local environment based on Vagrant

[Javi Roman]

I going to merge the PR [1] related with the Vagrant environment reworking.

Please feel free to comment whatever enhance or inconvenient you think
about the commit. I will merge he PR if there are no negative
comments/votes.


[1] https://github.com/apache/incubator-myriad/pull/107
--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info


On Mon, Feb 5, 2018 at 2:36 PM, Javi Roman  wrote:
> For sure, this is something to include in the vagrant testbed. Good point.
> --
> Javi Roman
>
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
>
>
> On Mon, Feb 5, 2018 at 10:01 AM, Juan P  wrote:
>> Hello Javi, I think it's a great idea.
>>
>> Is it possible to prepare the automatic environment to perform automatic
>> end-to-end tests (acceptance) or with a minimum of configuration?
>>
>> In later versions, would it be possible to include all the known Yarn
>> frameworks and prepare some automatic use cases that serve as an example
>> for the community and regression / integration test?
>>
>> Thank you
>>
>> On 4 February 2018 at 10:09, Javi Roman  wrote:
>>
>>> I would like share with you the strategy that I'm following for a
>>> powerful local development environment for Myriad.
>>>
>>> The idea is to create an easy-to-use environment for new contributors,
>>> setting up a Mesos cluster, or DCOS cluster (with hadoop running which
>>> is a tedious task). I guess automate this task is a key point for
>>> accelerating the development and focusing in the Myriad hacking.
>>>
>>> In this first task [1] I am working on Vagrant libvirt support for a
>>> plain Mesos cluster. However the roadmap for this environment would
>>> be:
>>>
>>> 1. vagrant-libvirt based cluster for Mesos, provisioned with Ansible
>>> (already working in my environment).
>>> 2. vagrant-libvirt based cluster for DC/OS provisioned with Ansible:
>>> Easier environment for testing Myriad with Marathon, Mesos-DNS, VIPS,
>>>  and so on.
>>> 3. vagrant-virtualbox based cluster (maintain the original environment
>>> used right now).
>>>
>>> The layout would be something like this:
>>>
>>> vagrant/
>>> ├── libvirt
>>> │   ├── dcos
>>> │   │   └── Vagrantfile
>>> │   └── mesos
>>> │   └── Vagrantfile
>>> └── virtualbox
>>> └── Vagrantfile
>>>
>>>
>>> In a second stage, the final scenario would be, only one folder with
>>> one "smart" Vagrantfile for supporting Mesos and DC/OS for Linux and
>>> OSX, the tool will be able of selecting the suitable virtualization
>>> technology by user configuration.
>>>
>>> This is the idea.
>>>
>>> [1] https://issues.apache.org/jira/browse/MYRIAD-257
>>>
>>> --
>>> Javi Roman
>>>
>>> Twitter: @javiromanrh
>>> GitHub: github.com/javiroman
>>> Linkedin: es.linkedin.com/in/javiroman
>>> Big Data Blog: dataintensive.info
>>>

Re: [Github] PR review

[Javi Roman]

Juan P.

The PR was already merged here [1]


[1] 
https://github.com/apache/incubator-myriad/commit/2f4ad0d6bf277548cc0f5bbdde0d18881b8a857b
--
Javi Roman

Twitter: @javiromanrh
GitHub: github.com/javiroman
Linkedin: es.linkedin.com/in/javiroman
Big Data Blog: dataintensive.info


On Sat, Feb 10, 2018 at 1:41 PM, John D. Ament  wrote:
> Hi,
>
> I just want to point out, Mohit is a committer on the project.  I'm not sure 
> what your workflow is, but considering the lack of developers on the project 
> maybe it makes sense to recommend people to commit directly to the repository?
>
> John
>
> On 2018/02/07 09:07:18, Juan P  wrote:
>> Please, can anyone merge this PR?
>>
>> https://github.com/apache/incubator-myriad/pull/104
>>
>> It is very important/necessary for the proper functioning of Travis.
>>
>>
>> Thanks
>>

Re: [Github] PR review

[Juan P]

Thanks Javi Roman

On 4 April 2018 at 09:53, Javi Roman  wrote:

> Juan P.
>
> The PR was already merged here [1]
>
>
> [1] https://github.com/apache/incubator-myriad/commit/
> 2f4ad0d6bf277548cc0f5bbdde0d18881b8a857b
> --
> Javi Roman
>
> Twitter: @javiromanrh
> GitHub: github.com/javiroman
> Linkedin: es.linkedin.com/in/javiroman
> Big Data Blog: dataintensive.info
>
>
> On Sat, Feb 10, 2018 at 1:41 PM, John D. Ament 
> wrote:
> > Hi,
> >
> > I just want to point out, Mohit is a committer on the project.  I'm not
> sure what your workflow is, but considering the lack of developers on the
> project maybe it makes sense to recommend people to commit directly to the
> repository?
> >
> > John
> >
> > On 2018/02/07 09:07:18, Juan P  wrote:
> >> Please, can anyone merge this PR?
> >>
> >> https://github.com/apache/incubator-myriad/pull/104
> >>
> >> It is very important/necessary for the proper functioning of Travis.
> >>
> >>
> >> Thanks
> >>
>