You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by b-long <br...@gmail.com> on 2017/09/29 03:09:44 UTC
Issue running Brooklyn in Vagrant
Hi all,
I must admit, IRC and mailing lists aren't very familiar to me. In any case, I messaged the group recently on Twitter and IRC, expressing my excitement about Brooklyn v0.12 : https://twitter.com/blong___/status/912788485412655104
I'm happy to report, I've managed to get it working. But, I ran into a couple issues along the way (including with the base Vagrant box and with a broken symlink causing the service to fail).
I've written up my findings in the following gist, with formatting: https://gist.github.com/b-long/ab096f45a7867574b74f01adff9f6c22
I'd really like to help promote Brooklyn, and as I said, I'm particularly interested in using Brooklyn for an Ambari deployment. For instance, following this example: https://github.com/brooklyncentral/brooklyn-ambari
If anyone can address my findings, I would greatly appreciate it.
- b-long
Re: Issue running Brooklyn in Vagrant
Posted by Thomas Bouron <th...@cloudsoftcorp.com>.
Hi.
Just pushed a PR[1] that should solve your issue b-long.
Best.
[1] https://github.com/apache/brooklyn-dist/pull/111
On Fri, 29 Sep 2017 at 17:55 Thomas Bouron <th...@cloudsoftcorp.com>
wrote:
> Hi b-long.
>
> I think I found a solution for the symlink, will push a PR for it as soon
> as possible. Will update once it's done.
>
> Best.
>
> On Fri, 29 Sep 2017 at 13:21 Thomas Bouron <
> thomas.bouron@cloudsoftcorp.com> wrote:
>
>> Hi b-long.
>>
>> Thanks for the detailed report, it's very interesting. I tested the PR
>> that updated Brooklyn Vagrant [1] before the release of 0.12.0 and it went
>> fine. Although, I suspect it was because I used a locally built artifact
>> rather than the released distribution (which didn't exist at the time)
>>
>> I can reproduce your second error, i.e. the symlink pointing to the wrong
>> folder. I'll try to fix this ASAP. This hopefully should be resolved soon
>> anyway as the goal is for vagrant to use the RPM distribution [2]
>>
>> Regarding for first issue, I couldn't reproduce what you saw with the
>> bento images. But based on the logs you provided, looks like it was
>> something to do with local installation rather than `brooklyn-vagrant`:
>>
>> Could not find the X.Org or XFree86 Window System, skipping.An error occurred during installation of VirtualBox Guest Additions 5.1.28. Some functionality may not work as intended.
>>
>>
>> Best.
>>
>> [1] https://github.com/apache/brooklyn-dist/pull/106
>> [2] https://github.com/apache/brooklyn-dist/pull/105
>>
>> On Fri, 29 Sep 2017 at 12:36 b-long <br...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I must admit, IRC and mailing lists aren't very familiar to me. In any
>>> case, I messaged the group recently on Twitter and IRC, expressing my
>>> excitement about Brooklyn v0.12 :
>>> https://twitter.com/blong___/status/912788485412655104
>>>
>>> I'm happy to report, I've managed to get it working. But, I ran into a
>>> couple issues along the way (including with the base Vagrant box and with a
>>> broken symlink causing the service to fail).
>>>
>>> I've written up my findings in the following gist, with formatting:
>>> https://gist.github.com/b-long/ab096f45a7867574b74f01adff9f6c22
>>>
>>> I'd really like to help promote Brooklyn, and as I said, I'm
>>> particularly interested in using Brooklyn for an Ambari deployment. For
>>> instance, following this example:
>>> https://github.com/brooklyncentral/brooklyn-ambari
>>>
>>> If anyone can address my findings, I would greatly appreciate it.
>>>
>>> - b-long
>>>
>> --
>>
>> Thomas Bouron • Senior Software Engineer @ Cloudsoft Corporation •
>> https://cloudsoft.io/
>> Github: https://github.com/tbouron
>> Twitter: https://twitter.com/eltibouron
>>
> --
>
> Thomas Bouron • Senior Software Engineer @ Cloudsoft Corporation •
> https://cloudsoft.io/
> Github: https://github.com/tbouron
> Twitter: https://twitter.com/eltibouron
>
--
Thomas Bouron • Senior Software Engineer @ Cloudsoft Corporation •
https://cloudsoft.io/
Github: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
Re: Issue running Brooklyn in Vagrant
Posted by Thomas Bouron <th...@cloudsoftcorp.com>.
Hi b-long.
I think I found a solution for the symlink, will push a PR for it as soon
as possible. Will update once it's done.
Best.
On Fri, 29 Sep 2017 at 13:21 Thomas Bouron <th...@cloudsoftcorp.com>
wrote:
> Hi b-long.
>
> Thanks for the detailed report, it's very interesting. I tested the PR
> that updated Brooklyn Vagrant [1] before the release of 0.12.0 and it went
> fine. Although, I suspect it was because I used a locally built artifact
> rather than the released distribution (which didn't exist at the time)
>
> I can reproduce your second error, i.e. the symlink pointing to the wrong
> folder. I'll try to fix this ASAP. This hopefully should be resolved soon
> anyway as the goal is for vagrant to use the RPM distribution [2]
>
> Regarding for first issue, I couldn't reproduce what you saw with the
> bento images. But based on the logs you provided, looks like it was
> something to do with local installation rather than `brooklyn-vagrant`:
>
> Could not find the X.Org or XFree86 Window System, skipping.An error occurred during installation of VirtualBox Guest Additions 5.1.28. Some functionality may not work as intended.
>
>
> Best.
>
> [1] https://github.com/apache/brooklyn-dist/pull/106
> [2] https://github.com/apache/brooklyn-dist/pull/105
>
> On Fri, 29 Sep 2017 at 12:36 b-long <br...@gmail.com> wrote:
>
>> Hi all,
>>
>> I must admit, IRC and mailing lists aren't very familiar to me. In any
>> case, I messaged the group recently on Twitter and IRC, expressing my
>> excitement about Brooklyn v0.12 :
>> https://twitter.com/blong___/status/912788485412655104
>>
>> I'm happy to report, I've managed to get it working. But, I ran into a
>> couple issues along the way (including with the base Vagrant box and with a
>> broken symlink causing the service to fail).
>>
>> I've written up my findings in the following gist, with formatting:
>> https://gist.github.com/b-long/ab096f45a7867574b74f01adff9f6c22
>>
>> I'd really like to help promote Brooklyn, and as I said, I'm particularly
>> interested in using Brooklyn for an Ambari deployment. For instance,
>> following this example:
>> https://github.com/brooklyncentral/brooklyn-ambari
>>
>> If anyone can address my findings, I would greatly appreciate it.
>>
>> - b-long
>>
> --
>
> Thomas Bouron • Senior Software Engineer @ Cloudsoft Corporation •
> https://cloudsoft.io/
> Github: https://github.com/tbouron
> Twitter: https://twitter.com/eltibouron
>
--
Thomas Bouron • Senior Software Engineer @ Cloudsoft Corporation •
https://cloudsoft.io/
Github: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
Re: Issue running Brooklyn in Vagrant
Posted by Thomas Bouron <th...@cloudsoftcorp.com>.
Hi b-long.
Thanks for the detailed report, it's very interesting. I tested the PR that
updated Brooklyn Vagrant [1] before the release of 0.12.0 and it went fine.
Although, I suspect it was because I used a locally built artifact rather
than the released distribution (which didn't exist at the time)
I can reproduce your second error, i.e. the symlink pointing to the wrong
folder. I'll try to fix this ASAP. This hopefully should be resolved soon
anyway as the goal is for vagrant to use the RPM distribution [2]
Regarding for first issue, I couldn't reproduce what you saw with the bento
images. But based on the logs you provided, looks like it was something to
do with local installation rather than `brooklyn-vagrant`:
Could not find the X.Org or XFree86 Window System, skipping.An error
occurred during installation of VirtualBox Guest Additions 5.1.28.
Some functionality may not work as intended.
Best.
[1] https://github.com/apache/brooklyn-dist/pull/106
[2] https://github.com/apache/brooklyn-dist/pull/105
On Fri, 29 Sep 2017 at 12:36 b-long <br...@gmail.com> wrote:
> Hi all,
>
> I must admit, IRC and mailing lists aren't very familiar to me. In any
> case, I messaged the group recently on Twitter and IRC, expressing my
> excitement about Brooklyn v0.12 :
> https://twitter.com/blong___/status/912788485412655104
>
> I'm happy to report, I've managed to get it working. But, I ran into a
> couple issues along the way (including with the base Vagrant box and with a
> broken symlink causing the service to fail).
>
> I've written up my findings in the following gist, with formatting:
> https://gist.github.com/b-long/ab096f45a7867574b74f01adff9f6c22
>
> I'd really like to help promote Brooklyn, and as I said, I'm particularly
> interested in using Brooklyn for an Ambari deployment. For instance,
> following this example: https://github.com/brooklyncentral/brooklyn-ambari
>
> If anyone can address my findings, I would greatly appreciate it.
>
> - b-long
>
--
Thomas Bouron • Senior Software Engineer @ Cloudsoft Corporation •
https://cloudsoft.io/
Github: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron