May I be the first :)? Big +1 from me. Thanks Dina!
On Thu, Sep 11, 2014 at 5:24 PM, Julien Danjou wrote:
> Hi,
>
> Dina has been doing a great work and has been very helpful during the
> Juno cycle and her help is very valuable. She's been doing a lot of
> reviews and has been very active in o
I'm in :)
+1
On Thu, Sep 11, 2014 at 4:58 PM, gordon chung wrote:
> > Nejc has been doing a great work and has been very helpful during the
>
> > Juno cycle and his help is very valuable.
>
> > I'd like to propose that we add Nejc Saje to the ceilometer-core group.
>
> can we minus because he ma
IMHO it's ok and even very natural to expect "escaped" query from users.
e.g, we store the following structure
{metadata:
{ Zoo:
{Foo.Boo: ''value"}}}
and query should be "metadata.Zoo.Foo\.Boo" .
In this case it's not necessary to know deep of t
Hello all,
As a Ceilometer's core, I'd like to add my 0.02$.
During previous discussions it was mentioned several projects which were
started or continue to be developed after Ceilometer became integrated. The
main question I'm thinking of is why it was impossible to contribute into
existing inte
Hi,
Yep, it would be great to have HBase installed on gating for Ceilometer.
Now we use self-written mocked HBase to test functionality. But HBase
backend is becoming more complex and it's really hard to add 'new features'
in mocked HBase. Hortonworks is the main and the largest contributor in
Hado
Sean,
The problem with 0.4 is a very new one. We had critical bug that was fixed
by ConnectionPool usage. This feature is available since 0.5. So we had two
options: 1. Go to rc1 with critical bug (not supported HBase in fact) 2.
Fix it but have incorrect dependency on 0.4. And we've chosen option
Sean, please see my comment in bug regarding 0.7. Unfortunately I have
nothing to suggest here. If distributive contains only 0.7 we cannot work
with HBase through happybase. And I don't see any solutions.
But anyway if you change requirements for happybase (I guess we need to get
0.7 back, no?) co
Today I've tested 0.6 and 0.8. They are acceptable for us. But 0.4 is not.
So I'd like to support Thomas's suggestion about freeze exception for
happybase.
Thanks, Nadya
On Fri, Mar 28, 2014 at 1:56 PM, Nadya Privalova wrote:
> Hi folks,
>
> Running rests against 0
Hi folks,
Running rests against 0.8. Will update you ASAP
Thanks,
Nadya
On Fri, Mar 28, 2014 at 1:39 PM, Thierry Carrez wrote:
> Thomas Goirand wrote:
> > I'd like to ask everyone's opinion here. Is it ok to do a freeze
> > exception in this case? If yes (please, everyone, agree! :) ), then
>
Tim, yep. If you use one db for Ceilometer and Nova then nova's performance
may be affected. I've seen this issue.
Will start profiling ASAP.
On Thu, Mar 20, 2014 at 3:59 PM, Tim Bell wrote:
>
> +1 for performance analysis to understand what needs to be optimised.
> Metering should be light-wei
Sean, thank for analysis.
JFYI, I did some initial profiling, it's described here
https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg19030.html.
On Thu, Mar 20, 2014 at 2:15 PM, Sean Dague wrote:
> On 03/20/2014 05:49 AM, Nadya Privalova wrote:
> > Hi all,
&g
Hi all,
First of all, thanks for your suggestions!
To summarize the discussions here:
1. We are not going to install Mongo (because "is's wrong" ?)
2. Idea about spawning several collectors is suspicious (btw there is a
patch that run several collectors: https://review.openstack.org/#/c/79962/.)
Ok, so we don't want to switch to UCA, let's consider this variant.
What options do we have to make possible to run Ceilometer jobs with Mongo
backend?
I see only https://review.openstack.org/#/c/81001/ or making Ceilometer
able to work with old Mongo. But the last variant looks inappropriate at
l
Hi folks,
I'd like to discuss Ceilometer's tempest situation with you.
Now we have several patch sets on review that test core functionality of
Ceilometer: notificaton and pollstering (topic
https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/add-basic-cei
of both?
>
>
>
> Best Regards,
>
> Ildiko
>
>
>
> *From:* Nadya Privalova [mailto:nprival...@mirantis.com]
> *Sent:* Tuesday, March 11, 2014 6:05 PM
> *To:* OpenStack Development Mailing List
> *Subject:* [openstack-dev] [Ceilometer]Collector's performan
Hi team!
Last week we were working on notification problem in ceilometer during
tempest tests creation. Tests for notification passed successfully on
Postgres but failed on MySQL. This made us start investigations and this
email contains some results.
As it turned out, tempest as it is is somethi
Hi guys,
I would ask in another way.
Ceilometer has a mechanism to add a sample through POST. So it looks not
consistent not to allow user to delete a sample.
IMHO, insertion and deletion through REST looks a little bit hacky: user
always has an ability to fake data collected from OpenStack servic
ink about it.
Thanks,
Nadya
On Mon, Jan 13, 2014 at 2:13 AM, Jay Pipes wrote:
> On Fri, 2014-01-10 at 17:10 +0400, Nadya Privalova wrote:
> > Idea:
> > The goal is to improve performance when user gets statistics for
> > meter. Now we have fixed list of statistics (min, max
Hi team,
I've decided to move discussion about aggregation in mailing list.
Here is a description about my idea and I really need your comments.
*Idea:*
The goal is to improve performance when user gets statistics for meter. Now
we have fixed list of statistics (min, max and so on). During reques
lien.
Thanks,
Nadya
On Mon, Dec 30, 2013 at 11:53 PM, David Kranz wrote:
> On 12/27/2013 05:27 AM, Nadya Privalova wrote:
>
> Hello guys!
>
> I hope all of you are enjoying the holidays! But I'd like to raise a
> Tempest question. Again. I hope this email will not be
Hello guys!
I hope all of you are enjoying the holidays! But I'd like to raise a
Tempest question. Again. I hope this email will not be lost after vacations
:)
After the summit we decided to track all tests that are being created for
Ceilometer in Tempest here:
https://blueprints.launchpad.net/tem
Thanks, Julien!
Will create blueprint on Monday and will start implementation.
On Fri, Dec 20, 2013 at 7:51 PM, Julien Danjou wrote:
> On Fri, Dec 20 2013, Nadya Privalova wrote:
>
> Hi Nadya,
>
> > For QA and Tempest guys brief description of Ceilometer's pollster
Hi guys!
For QA and Tempest guys brief description of Ceilometer's pollstering.
Ceilometer has several agents that once in 'interval' asks Nova, Glance and
other services about their metrics. We need to test this functionality,
'Interval' is defined in pipeline.yaml file and is 10 minutes by defau
Hi John,
As for me your ideas look very interesting. As I understood notification
messages will be kept in MQ for some time (during batch-basket is being
filled), right? I'm concerned about the additional load that will be on MQ
(Rabbit).
Thanks,
Nadya
On Fri, Dec 20, 2013 at 3:31 AM, Herndon,
Hi David,
I'm working on tempest tests for Ceilometer too.
I think this thread is a good place to make a reminder about our strategy
how to avoid duplications in change requests.
1. We have something like a test plan
https://etherpad.openstack.org/p/ceilometer-test-plan
2. Ceilometer team's decid
ec 10, 2013 at 9:47 AM, Nadya Privalova
> wrote:
>
>> Julien,
>>
>> Yes, I use the same SQL for Nova and Ceilometer. Thanks for pointing this
>> out. My bad, I didn't take it into account. So if we want to use Ceilometer
>> + MySQL in production (in theory :) )
Hello, guys!
We faced with Glance notifications issue during Tempest tests for
Ceilometer. We tried to send notification by ourselves (during
investigation we've found that Glance uses almost the same code):
from oslo.config import cfg
from oslo import messaging
CONF.rabbit_host = 'localhost'
C
to get it reviewed/merged.
>
>
> Thanks.
>
>
> Best regards,
> Boris Pavlovic
>
>
>
>
>
>
> On Tue, Dec 10, 2013 at 3:19 PM, Julien Danjou wrote:
>
>> On Tue, Dec 10 2013, Nadya Privalova wrote:
>>
>> Hi Nadya,
>>
>> >
Hi guys,
I decided to forward this message to dev list too. On the previous week I
was investigating Ceilometer performance. And this letter is a brief
description of my results.
Lab description:
3 controllers
187 computes
HA: Galera for MySQL
memcached is on, RabbitMQ in HA mode
Ceilometer proc
Hi guys,
I've faced with nova+memcache issue on the cluster in HA-mode.
Issue is related to nova in case of using REST (that includes Horizon):
it's impossible to use auth-token several times because it became
unauthorized in cache.
Logs:
Nov 13 06:58:49 controller-1461 nova keystoneclient.midd
Hello Sandy,
I'm very interested in performance results for Ceilometer. Now we have
successfully installed Ceilometer in the HA-lab with 200 computes and 3
controllers. Now it works pretty good with MySQL. Our next steps are:
1. Configure alarms
2. Try to use Rally for OpenStack performance with
Hi guys,
I've created the bp
https://blueprints.launchpad.net/python-ceilometerclient/+spec/proxy-support.
Will start working on this asap.
Thanks,
Nadya
On Fri, Nov 15, 2013 at 3:23 PM, Mike Scherbakov
wrote:
> Hi Ceilometer team,
> do you have any plans for http proxy support (see concerns b
or looking into crs. As I see 39237 made a good progress today
Thanks,
Nadya
On Wed, Nov 13, 2013 at 3:01 PM, Julien Danjou wrote:
> On Tue, Nov 12 2013, Nadya Privalova wrote:
>
> Hi Nadya,
>
> > Here is a list of ceilometer-regarding cr in tempest (just a reminder):
> >
Hello, guys!
I hope everybody has eventually got home after the summit and feeling ok :)
So it's time to proceed thinking about integration, unit and performance
testing in Ceilometer. First of all I'd like to appreciate your help in
composing etherpad
https://etherpad.openstack.org/p/icehouse-sum
Hi guys,
I can share my experience with devstack+ceilometer. There is certainly a
problem with MongoDB, because Ceilometer requires more fresh Mongo than
devstack provides. But I didn't experienced problems with SQL.
And just a quick question about testing: are there any plans to test
Ceilometer w
Hello folks,
Today I've showed a demo with EDP UI. Here a feedback from our
Mirantis-team. Items without NOTEs should be done, I believe. For some of
them bugs are already filed:
1. We need URL hints for DataSouce (as it done for JobBinary)
2. DataSource UI should depend on DataSource type (
http
Hi Jon,
The main reason why this button is on UI is to let user know that Savanna
supports swift.
If a cluster doesn't have swift at all user may disable swift explicitly,
but it's the truth that if he or she doesn't disable swift nothing will be
broken.
Regards,
Nadya
On Wed, Sep 11, 2013 at
Hi all,
I've created a temporary page for UIs mockups. Please take a look:
https://wiki.openstack.org/wiki/Savanna/UIMockups/JobCreationProposal
Chad, it's just pictures demonstrate how we see dependencies in UI. It's
not a final decision.
Guys, feel free to comment this. I think it's time to sta
38 matches
Mail list logo
