rico.lin.guanyu at gmail.com
Thu Dec 19 02:15:13 UTC 2019
Just another ML earlier people need to also aware of ->
On Thu, Dec 19, 2019 at 10:07 AM Rico Lin <rico.lin.guanyu at gmail.com> wrote:
> On Wed, Dec 18, 2019 at 1:43 PM Lingxian Kong <anlin.kong at gmail.com>
> > Hi all,
> > 1. Maybe Gnocchi is good, but it's not part of OpenStack, currently
> > there is no one in the Telemetry team shows any interest in maintaining
> > it, I'd be very happy to see if there is someone raises hand and say: I
> > commit to spend some time on this project, fixing bugs, maintaining
> > document and answering questions either on IRC or via email. If yes, We
> > will see how it goes in this dev cycle.
> If Gnocchi can't provide documents and CI, also can't close the issue
> said `Project is unmaintained`,
> we should ask if anyone here volunteer to resolved that part. Anyone?:)
> If you really care about Gnocchi+Telemetry, join the team please.
> > 3. The Telemetry team did have discussed to bring the Ceilometer API and
> > MongoDB support back, given neither Gnocchi nor Monasca is able to store
> > the original samples. However, nothing is happening, so don't be panic.
> From my perspective, to bring back Ceilometer API and MongoDB as another
> driver for Telemetry isn't a bad idea at all as long as other driver can
> keep their tasks forward.
> No one (at least I didn't see any one) mentioned about if some people in
> Telemetry team
> start the effort on Ceilometer API and MongoDB, no others can keep their
> effort on Gnocchi.
> The one thing I'm interested on is how to tune the MongoDB performance
> with Ceilometer.
> How can you make Ceilometer API+MongoDB more robust?
> So if any chances that's happening, will be create to provide related
> documents too.
> Also the CI need to be there when we bring back Ceilometer API and MongoDB
> Despite the detail is not yet develop here, I'm agree if that's a
> short-term plan.
>  https://github.com/gnocchixyz/gnocchi/issues/1049
> > the current project core members are also the Telemetry service cloud
> > providers, we know how important it is to not break anything, to not
> > bring any more overhead than before. we are so glad to see this
> I believe that's really important for you guys too:)
> > discussion, at least there are still so many people using
> > Ceilometer/Gnocchi and have concerns about the current upstream
> > situation. It would be much better that people involved in this
> > discussion could participate in the design and implementation of the
> > future tasks.
> Yes, the only way is to join the team, stand your ground, and involve in
> the design.
> In long term, IMO we need to have a ultimate solution for all. A standard
> way so whatever
> other tools or service is developing, on the other can use it too.
> An tool/sdk/interface (and no need to build another service) to support
> both project.
> Or if there's better solution for it.
> And what need to done if we would like that.
> Will Telemetry and Monasca team interested on this?
> I would like to propose we move that discussion somewhere else, like
> in Monasca or Telemetry's team meeting?
> Will ask if any TC can help to coordinate.
> May The Force of OpenStack Be With You,
> Rico Lin
> irc: ricolin
May The Force of OpenStack Be With You,
*Rico Lin*irc: ricolin
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss