You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Guangning E <gu...@apache.org> on 2020/06/24 08:09:49 UTC
[Discuss] Apache pulsar-manager 0.2.0 release
Hello everyone:
It has been a long time since the release of the previous version's major
release (0.1.0). I am planning to start the 0.2.0 release soon (probably
this week).
You can find the whole change list of 0.2.0 release from:
https://github.com/apache/pulsar-manager/milestone/3?closed=1
If there are some other features that need to be merged to 0.2.0, please
let me know, thanks.
Thanks,
Guangning
Re: [Discuss] Apache pulsar-manager 0.2.0 release
Posted by Guangning E <eg...@gmail.com>.
Thank you very much @Enrico Olivelli.
About the first point, I can try to change the publishing process to make
it simpler and not rely on nginx.
Second, I think we can consider supporting bk management in a single
environment in this version, and we will support multiple environments in
the next version.
What do you think of this?
Thanks,
Guangning
Enrico Olivelli <eo...@gmail.com> 于2020年6月24日周三 下午5:06写道：
> Guangning
>
> Il giorno mer 24 giu 2020 alle ore 10:10 Guangning E <guangning@apache.org
> >
> ha scritto:
>
> > Hello everyone:
> >
> > It has been a long time since the release of the previous version's major
> > release (0.1.0). I am planning to start the 0.2.0 release soon (probably
> > this week).
> >
> > You can find the whole change list of 0.2.0 release from:
> > https://github.com/apache/pulsar-manager/milestone/3?closed=1
> >
> > If there are some other features that need to be merged to 0.2.0, please
> > let me know, thanks.
> >
>
>
> The new PM 0.2.0 will be great !
>
> I have only two points:
>
> 1) "Server frontend directly from Pulsar Manager backend"
> with https://github.com/apache/pulsar-manager/pull/288 we are now able
> to
> serve directly the front-end part from the Tomcat launched for the backend.
>
> Currently when you build the backend the front-end is not included in the
> pulsar-manager.tar package,
> if we are able to modify the release procedure in a way that the final
> artifact bundles the front-end running pulsar-manager will be only a matter
> of untarring the tar ball and run "pulsar-manager"
> without Nginx or other webserves.
> I am not able to change the release procedure, but I can try to modify
> Gradle configuration in a way that it bundles the front-end if you
> previously built it.
>
> 2) Package BKVM (BookKeeper Visual Manager)
> I have a draft Pull Request to embed BKVM with PulsarManager
> https://github.com/apache/pulsar-manager/pull/300
>
> My PR includes BKVM 1.1,but is does support only single-env deployments of
> BK/Pulsar, is it worth to finish this PR and release it with Pulsar Manager
> 0.2 ?
> We are working on multi-env support in BKVM 2.0 but I think it will take a
> couple of weeks before a release.
>
> Best regards
>
> Enrico
>
>
>
>
>
> >
> >
> > Thanks,
> > Guangning
> >
>
Re: [Discuss] Apache pulsar-manager 0.2.0 release
Posted by Enrico Olivelli <eo...@gmail.com>.
Guangning
Il giorno mer 24 giu 2020 alle ore 10:10 Guangning E <gu...@apache.org>
ha scritto:
> Hello everyone:
>
> It has been a long time since the release of the previous version's major
> release (0.1.0). I am planning to start the 0.2.0 release soon (probably
> this week).
>
> You can find the whole change list of 0.2.0 release from:
> https://github.com/apache/pulsar-manager/milestone/3?closed=1
>
> If there are some other features that need to be merged to 0.2.0, please
> let me know, thanks.
>
The new PM 0.2.0 will be great !
I have only two points:
1) "Server frontend directly from Pulsar Manager backend"
with https://github.com/apache/pulsar-manager/pull/288 we are now able to
serve directly the front-end part from the Tomcat launched for the backend.
Currently when you build the backend the front-end is not included in the
pulsar-manager.tar package,
if we are able to modify the release procedure in a way that the final
artifact bundles the front-end running pulsar-manager will be only a matter
of untarring the tar ball and run "pulsar-manager"
without Nginx or other webserves.
I am not able to change the release procedure, but I can try to modify
Gradle configuration in a way that it bundles the front-end if you
previously built it.
2) Package BKVM (BookKeeper Visual Manager)
I have a draft Pull Request to embed BKVM with PulsarManager
https://github.com/apache/pulsar-manager/pull/300
My PR includes BKVM 1.1,but is does support only single-env deployments of
BK/Pulsar, is it worth to finish this PR and release it with Pulsar Manager
0.2 ?
We are working on multi-env support in BKVM 2.0 but I think it will take a
couple of weeks before a release.
Best regards
Enrico
>
>
> Thanks,
> Guangning
>