Thanks for the heads up. I checked briefly for logos on Google just to see
what's around when I had the idea, but it seems I should've done a deeper/wider
search... :) :(
Cheers,
Ildikó
> -Original Message-
> From: Julien Danjou [mailto:jul...@danjou.info]
> Sent: July 25, 2016 14:30
>
Hi,
As we had a session about the Cinder-Nova API changes in progress last week
during the mid-cycles of these two modules we cancel the today's meeting.
You can find meeting logs on this etherpad starting from line 50:
https://etherpad.openstack.org/p/nova-newton-midcycle
Best Regards,
/Ildik
I had the Meerkat [1] in mind as Telemetry has a "family" of services and
meerkat lives in bigger groups too and a few of them stand sentry and listen to
any event or danger, etc. and "send alarms" to the others.
From the previous options I like Fennec too.
/Ildiko
[1] https://en.wikipedia.org
Hi,
The today's meeting is cancelled due to the holiday in the U.S. The next
meeting will be held next Monday (July 11th), 1700 UTC on #openstack-meeting-cp.
Thanks and Best Regards,
/Ildikó
__
OpenStack Development Mailing
Hi Andreas,
Thanks for the clarification on this. We will consider the options.
Best Regards,
Ildikó
> -Original Message-
> From: Andreas Jaeger [mailto:a...@suse.com]
> Sent: June 28, 2016 20:44
> To: Ildikó Váncsa; openstack-d...@lists.openstack.org
> Cc
ent: June 28, 2016 18:46
> To: Ildikó Váncsa; 'Spyros Trigazis'; OpenStack Development Mailing List (not
> for usage questions); openstack-
> d...@lists.openstack.org
> Subject: RE: [OpenStack-docs] [openstack-dev] [telemetry] Ceilometer and Aodh
> install guide(s)
>
&
, 'doc/install-guide', etc.?
Thanks and Best Regards,
/Ildikó
> -Original Message-
> From: Andreas Jaeger [mailto:a...@suse.com]
> Sent: June 28, 2016 15:12
> To: Ildikó Váncsa; openstack-d...@lists.openstack.org
> Cc: openstack-dev@lists.openstack.org
> Subject:
m: Ravi, Goutham [mailto:goutham.r...@netapp.com]
> Sent: June 28, 2016 15:32
> To: Ildikó Váncsa; openstack-d...@lists.openstack.org
> Cc: openstack-dev@lists.openstack.org
> Subject: Re: [OpenStack-docs] [telemetry] Ceilometer and Aodh install guide(s)
>
> Hi Ildikó,
>
> Pl
the files.
Do you have a good proposal for structuring things?
Thanks,
/Ildikó
> -Original Message-
> From: Spyros Trigazis [mailto:strig...@gmail.com]
> Sent: June 28, 2016 17:18
> To: OpenStack Development Mailing List (not for usage questions); Ildikó
> Váncsa; openstac
Hi,
I'm currently working on to move the Install Guide for Ceilometer [1] and Aodh
[2] under the project trees. I faced with a few difficulties so far about which
I would like to ask your opinion.
First of all these two projects are under the Telemetry umbrella, so they are
not completely sepa
Regards,
/Ildikó
> -Original Message-
> From: Ildikó Váncsa [mailto:ildiko.van...@ericsson.com]
> Sent: May 31, 2016 20:57
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly
> IRC meetings
>
> Hi
,
/Ildikó
> -Original Message-
> From: Ildikó Váncsa [mailto:ildiko.van...@ericsson.com]
> Sent: May 20, 2016 18:31
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly
> IRC meetings
>
> Hi All,
>
>
Hi All,
We have now the approved slot for the Cinder-Nova interaction changes meeting
series. The new slot is __Monday, 1700UTC__, it will be on channel
__#openstack-meeting-cp__.
Related etherpad: https://etherpad.openstack.org/p/cinder-nova-api-changes
Summary about ongoing items:
http://l
> -Original Message-
> From: Mike Perez [mailto:thin...@gmail.com]
> Sent: May 17, 2016 02:23
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly
> IRC meetings
>
>
Hi All,
We will have the Cinder-Nova interaction changes meetings in a new slot
starting from this week. The new slot is __Tuesday, 1700UTC__. We will also
move it to another channel, which is the __#openstack-meeting-alt__.
Related etherpad: https://etherpad.openstack.org/p/cinder-nova-api-cha
> -Original Message-
> From: Mike Perez [mailto:m...@openstack.org]
> Sent: May 11, 2016 23:52
> To: Ildikó Váncsa
> Cc: 'D'Angelo, Scott (scott.dang...@hpe.com)';
> 'Walter A. Boring IV'; 'John Griffith
> (john.griffi...@gmail
Hi All,
We will continue the meeting series about the Cinder-Nova interaction changes
mostly from multiattach perspective. We have a new meeting slot, which is
__Thursday, 1700UTC__ on the #openstack-meeting-cp channel.
Related etherpad: https://etherpad.openstack.org/p/cinder-nova-api-changes
> -Original Message-
> From: Andreas Jaeger [mailto:a...@suse.com]
> Sent: May 07, 2016 20:51
> To: Ildikó Váncsa; 'Matt Kassawara'
> Cc: OpenStack Development Mailing List; enstack.org
> Subject: Re: [OpenStack-docs] What's Up, Doc? 6 May 2016
>
>
lto:mkassaw...@gmail.com]
> Sent: May 07, 2016 00:55
> To: Ildikó Váncsa
> Cc: Lana Brindley; enstack.org; OpenStack Development Mailing List;
> openstack-i...@lists.openstack.org
> Subject: Re: [OpenStack-docs] What's Up, Doc? 6 May 2016
>
> One significant advantage of cen
Hi Lana,
Thanks for the summary, it's pretty good reading to catch up what happened
recently.
I have one question, I might missed a few entries, so please point me to the
right document in this case. We had a docco session with the Telemetry team and
we agreed on moving back the documentation
s during the session.
>
> At the end of the session, we (Nova) came away with the following next
> steps:
>
> 1. John Griffith (Cinder team) would work on a proof of concept for the
> abstracted volume idea.
>
> 2. Cinder would work on adding a volume migration test to Tem
Hi All,
We are having the last Cinder-Nova API interactions meeting before the Summit
this Wednesday __20th April 2100UTC__, on the #openstack-meeting-cp channel.
You can find the information about the recent discussions here:
https://etherpad.openstack.org/p/cinder-nova-api-changes
This week
Hi Julien,
First of all big +1. :)
The 16:10-16:50 slot looks better for me.
Thanks,
/Ildikó
> -Original Message-
> From: Julien Danjou [mailto:jul...@danjou.info]
> Sent: April 14, 2016 11:07
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [telemetry][vitrage] Joint
Hi All,
It's a friendly reminder we're having the next Cinder-Nova API interactions
meeting this Wednesday __13th April 2100UTC__, on the #openstack-meeting-cp
channel.
You can follow up the recent activities here:
https://etherpad.openstack.org/p/cinder-nova-api-changes Our current focus is
Best Regards,
/Ildikó
> -Original Message-
> From: Ildikó Váncsa
> Sent: March 24, 2016 10:01
> To: openstack-dev@lists.openstack.org
> Subject: [cinder][nova] Cinder-Nova API meeting
>
> Hi All,
>
> As it was discussed several times on this mailing list there
organise it better with priority and incentive.
I had the Roadmap page in mind as well partially, we could highlight the
plans/tasks from that page and also track progress.
Thanks,
/Ildikó
>
> On 31/03/2016 7:14 AM, Ildikó Váncsa wrote:
> > Hi All,
> >
> > +1 on the on d
Hi All,
+1 on the on demand meeting schedule. Maybe we can also have some news flash
mails week to summarize the progress in our sub-modules when we don't have the
meeting. Just to keep people up to date.
Will we already skip the today's meeting?
Thanks,
/Ildikó
> -Original Message-
Hi All,
I would like to throw my hat in the ring to be part of the OpenStack Technical
Committee.
I'm working at Ericsson, where I'm coordinating the OpenStack related activities
across the company. I started to contribute to OpenStack more than two years ago
by adding rich query functionality to
Hi All,
As it was discussed several times on this mailing list there is room for
improvements regarding the Cinder-Nova interaction. To fix these issues we
would like to create a cross-project spec to capture the problems and ways to
solve them. The current activity is captured on this etherpad
Hi Walt,
Thanks for describing the bigger picture.
In my opinion when we will have microversion support available in Cinder that
will give us a bit of a freedom and also possibility to handle these
difficulties.
Regarding terminate_connection we will have issues with live_migration as it is
t
Hi,
As far as I can see volume attachments are handled on attachment level today as
opposed to host level in Cinder. How the volume is exposed to a host
technically is another question, but conceptually Cinder is the ultimate source
of truth regarding how many attachments a volume has and what
ector.disconnect_volume
>
> On 02/09/2016 02:04 PM, Ildikó Váncsa wrote:
> > Hi Walt,
> >
> > Thanks for starting this thread. It is a good summary of the issue and the
> > proposal also looks feasible to me.
> >
> > I have a quick, hopefully not to
Hi Walt,
Thanks for starting this thread. It is a good summary of the issue and the
proposal also looks feasible to me.
I have a quick, hopefully not too wild idea based on the earlier discussions we
had. We were considering earlier to store the target identifier together with
the other items
Hi All,
I wonder whether we could provide an interface on the API where these kind of
capabilities can be retrieved? I know we have a support matrix in the
documentation that's good to have. I asked the question, because here we have a
base functionality, which is attaching a volume that Cinder
Hi All,
We will have a chat about the feature regarding design and next steps at the
contributors' meet-up on Friday at 10am.
https://etherpad.openstack.org/p/mitaka-neutron-unplugged-track
Best Regards,
Ildikó
(IRC: ildikov)
> -Original Message-
> From: Il
gt; On Oct 21, 2015, at 11:31 AM, Ildikó Váncsa
>> wrote:
>>
>> Hi Folks,
>>
>> The work has been ongoing for a while now to implement the feature to
>> support attaching a single volume to multiple VM instances.
>>
>> This work impacts both Nova and
Development Mailing List (not for usage questions)
> Cc: Bence Romsics; Petr Savelyev
> Subject: Re: [openstack-dev] [Neutron][Nova] Trunk port feature (VLAN aware
> VMs)
>
>
>
> On 21 October 2015 at 15:40, Ildikó Váncsa wrote:
>
>
> Hi Folks,
>
>
Hi,
The upcoming OpenStack Summit in Tokyo is a great opportunity to discuss open
questions, like resource management and resource reservation.
The Promise project in OPNFV is working on to identify the use cases and find a
solution to this missing piece. For further information about this proj
Hi Folks,
During Liberty we started the implementation of the VLAN aware VMs blueprint
(https://review.openstack.org/#/c/94612/). We had quite a good progress,
although we could use some extra hands on Neutron side and some thoughts on the
Nova-Neutron interaction aspect of the feature.
The st
Hi Folks,
The work has been ongoing for a while now to implement the feature to support
attaching a single volume to multiple VM instances.
This work impacts both Nova and Cinder. We are in quite good shape with the
implementation, but it is still far for completion and we temporarily ran out
Hi All,
I would like to inform you that we cancel the Ceilometer meeting for this week
in favor of Summit travels and preparation.
We finished to organize our sessions for next week, you can find the schedule
here: https://mitakadesignsummit.sched.org/overview/type/ceilometer
The etherpads for
On Fri, Aug 28, 2015 at 7:54 PM, Pierre
> Riteau
> mailto:prit...@uchicago.edu>> wrote:
> Hello,
>
> The NSF-funded Chameleon project
> (https://www.chameleoncloud.org) uses Blazar
Hi All,
The resource reservation topic pops up time to time on different forums to
cover use cases in terms of both IT and NFV. The Blazar project was intended to
address this need, but according to my knowledge due to earlier integration and
other difficulties the work has been stopped.
My qu
gt; Subject: Re: [openstack-dev] [Monasca] Minutes for Monasca mid-cycle meetup
>
> Ildikó, I think you are correct on the time. The meeting is at 3:00 PM UTC,
> which is 9:00 AM MDT. Sorry, the time I mentioned was
> incorrect.
> Regards --Roland
>
>
>
> On 8/16/15,
to IRC.
>
> If Tuesday's at 4:00 PM UTC are problematic, then we would consider setting
> up a separate time to cover this topic or move the
> Monasca meeting the following week.
>
> Regards --Roland
>
>
>
> On 8/14/15, 6:57 AM, "Ildikó Váncsa" wrot
Hi,
I will try to join if I can, I have an overlapping meeting on Tuesdays.
In general I think it would be really good to start a closer collaboration, the
componentization work in Ceilometer gives a really good opportunity as Chris
described.
Best Regards,
Ildikó
> -Original Message-
Hi Kyle,
First of all, sorry for the late response.
We are working on the design and implementation, the first patches are planned
to be up by the end of this week.
We could surely use more hands as it is quite a large amount of work that this
blueprint requires. If there are any Neutron exper
wanted to double check.
Ildikó
Sent from my iPad
> On 30 Jun 2015, at 14:18, Julien Danjou wrote:
>
>> On Tue, Jun 30 2015, Ildikó Váncsa wrote:
>>
>> Will this be accessible in the same way as currently or it needs
>> changes on client side?
>
> You may j
> -Original Message-
> From: Julien Danjou [mailto:jul...@danjou.info]
> Sent: June 30, 2015 10:10
> To: Ildikó Váncsa
> Cc: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [ceilometer] Aodh has been imported, next steps
&
Hi,
I think removing options from the API requires version bump. So if we plan to
do this, that should be introduced in v3 as opposed to v2, which should remain
the same and maintained for two cycles (assuming that we still have this policy
in OpenStack). It this is achievable by removing the o
ds,
Ildikó
> -Original Message-
> From: Kyle Mestery [mailto:mest...@mestery.com]
> Sent: June 15, 2015 15:52
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron] VLAN-aware VMs meeting
>
> On Mon, Jun 15, 2015 at 7
Hi Kyle,
> -Original Message-
> From: Kyle Mestery [mailto:mest...@mestery.com]
> Sent: June 15, 2015 04:26
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron] VLAN-aware VMs meeting
>
> On Fri, Jun 12, 20
Hi,
Since we reopened the review for this blueprint we've got a large number of
comments. It can be clearly seen that the original proposal has to be changed,
although it still requires some discussion to define a reasonable design that
provides the desired feature and is aligned with the archi
gt; Subject: Re: [openstack-dev] [Zaqar][all] Zaqar will stay... Lots of work
> ahead
>
> On 06/01/2015 04:34 AM, Flavio Percoco wrote:
> > On 31/05/15 18:12 +, Ildikó Váncsa wrote:
> >> Hi All,
> >>
> >> I would like to ask about the user-facing notificati
Hi All,
I would like to ask about the user-facing notifications part of the list. Do
you have a roadmap for this? Is this driven by the Zaqar team? What are the
next steps?
Thanks and Best Regards,
Ildikó
-Original Message-
From: Clint Byrum [mailto:cl...@fewbar.com]
Sent: May 27, 201
Hi All,
Thanks for showing interest in this feature proposal. Some additional info to
what Erik mentioned below:
The blueprint patch will soon be updated to target the Liberty release:
https://review.openstack.org/#/c/94612/
There will also be a design summit session about this topic on Wedne
Hi,
I like the base idea to trigger scaling based on other information than what we
have from the current Ceilometer alarms.
Although I think this functionality should live somewhere else than under the
responsibility of Ceilometer. This type of scaling is usually based on trend
analysis and o
Hi All,
Thanks for the heads up regarding to this inconsistency of terms in the docs. I
will open a bug for it and target both Ceilometer and OS Manuals to get it
corrected everywhere.
Best Regards,
Ildikó
-Original Message-
From: Julien Danjou [mailto:jul...@danjou.info]
Sent: Wednes
Hi,
+1 from me too, thanks for all the hard work so far.
Best Regards,
Ildikó
-Original Message-
From: Julien Danjou [mailto:jul...@danjou.info]
Sent: Thursday, September 11, 2014 3:25 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Ceilometer] Adding Dina Belova to c
Hi,
+1 from me, and thanks for the nice work so far.
Best Regards,
Ildikó
-Original Message-
From: Julien Danjou [mailto:jul...@danjou.info]
Sent: Wednesday, September 10, 2014 12:35 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Ceilometer] Adding Nejc Saje to ceilo
Hi,
I couldn’t reproduce this issue either. I’ve tried on precise and on a fresh
trusty too, everything worked fine…
Cheers,
Ildikó
From: Dina Belova [mailto:dbel...@mirantis.com]
Sent: Friday, August 22, 2014 11:40 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re
y of Ceilometer workability verification right now to
> continue work on its improvement.
>
> So any suggestions and comments are welcome here :)
>
> Thanks!
> Dina
>
>
> On Wed, Jul 16, 2014 at 7:06 PM, Ildikó Váncsa
>
> wrote:
>
> > Hi Folks,
&g
Hi Folks,
We've faced with some problems during running Ceilometer integration tests on
the gate. The main issue is that we cannot test the polling mechanism, as if we
use a small polling interval, like 1 min, then it puts a high pressure on Nova
API. If we use a longer interval, like 10 mins,
Hi Nadya,
You mentioned multiple DB backends in your mail. Which one did you use to
perform these tests or did you get the same/similar performance results in case
of both?
Best Regards,
Ildiko
From: Nadya Privalova [mailto:nprival...@mirantis.com]
Sent: Tuesday, March 11, 2014 6:05 PM
To: Ope
Hi Ceilometer guys,
We are implementing a complex query functionality for Ceilometer. We got a
comment to our implementation that using JSON in a string for representing the
query filter expression, is probably not the best solution.
The description of our current API design can be found here:
Hi,
In my opinion it would be better to let the user to define a ttl value for
his/her own samples. I do not see the use case, where it is needed to delete
samples, also if the user is able to randomly delete some data, then the
statistics functions will not generate a valid output for that dat
Hi Doug,
OK, so like I said, we did not design the system with the idea that a user of
the cloud (rather than the deployer of the cloud) would have any control over
what data was collected. They can ask questions about only some of the data,
but they can't tell ceilometer what to collect.
There
Hi,
> > My idea was just about providing the possibility to configure the data
> > collection in Ceilometer differently for the different tenants, I
> > didn't mean to link it to an API or at least not on the first place.
> > It could be done by the operator as well, for instance, if the pollin
Hi,
(You didn't Cc the list, not sure if it was on purpose. I'm not adding it back
to not break any confidentiality, but feel free to do so.)
Sorry that was just a mistake.
> > The point is to configure the data collection configuration for the
> > currently existing meters differently for ten
Hi Doug,
Answers inline again.
Best Regards,
Ildiko
On Wed, Jan 8, 2014 at 3:16 AM, Ildikó Váncsa
mailto:ildiko.van...@ericsson.com>> wrote:
Hi,
I've started to work on the idea of supporting a kind of tenant/project based
configuration for Ceilometer. Unfortunately I haven&#x
Wed, Jan 8, 2014 at 3:16 AM, Ildikó Váncsa
mailto:ildiko.van...@ericsson.com>> wrote:
Hi,
I've started to work on the idea of supporting a kind of tenant/project based
configuration for Ceilometer. Unfortunately I haven't reached the point of
having a blueprint that could be regi
Hi,
I've started to work on the idea of supporting a kind of tenant/project based
configuration for Ceilometer. Unfortunately I haven't reached the point of
having a blueprint that could be registered until now. I do not have a deep
knowledge about the collector and compute agent services, but
Hi,
Thank you all for the comments, see mines inline.
Best Regards and Merry Christmas,
Ildiko
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Tuesday, December 24, 2013 2:14 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Ceilometer] Complex
] Complex query BP implementation
On 12/16/2013 03:54 PM, Ildikó Váncsa wrote:
> Hi guys,
>
> The first working version of the Complex filter expressions in API
> queries blueprint [1] was pushed for review[2].
>
> We implemented a new query REST resource in order to pro
Hi guys,
The first working version of the Complex filter expressions in API queries
blueprint [1] was pushed for review[2].
We implemented a new query REST resource in order to provide rich query
functionality for samples, alarms and alarm history. The future plans (in
separated blueprints) wi
Hi All,
As a resumption of the Improving Ceilometer API query filtering session of the
HK Design Summit, I created a document about supporting complex query filters
in Ceilometer. The document contains a brief summary of the previously
suggested idea. The second part of the etherpad discuss the
76 matches
Mail list logo
