[Openstack-operators] [Performance] No meeting today

Folks, sadly I have to cancel today's Performance Team meeting. The next one will be held next week on Tuesday (at usual time <https://wiki.openstack.org/wiki/Meetings/Performance#Agenda_for_next_meeting> ). Sorry for inconvenience. Cheers, Dina -- *Dina Belova* *Senior Software En

[openstack-dev] [Performance] No Performance Team meeting today

Folks, due to the internal training big part of Mirantis won't be able to attend the meeting. Let's skip this for today. Sorry for inconvenience. Cheers, Dina -- *Dina Belova* *Senior Software Engineer* Mirantis, Inc. 525 Almanor Avenue, 4th Floor Sunnyvale, CA 94085 *Phone: 650-772

[Openstack-operators] [Performance] No Performance Team meeting today

Folks, due to the internal training big part of Mirantis won't be able to attend the meeting. Let's skip this for today. Sorry for inconvenience. Cheers, Dina -- *Dina Belova* *Senior Software Engineer* Mirantis, Inc. 525 Almanor Avenue, 4th Floor Sunnyvale, CA 94085 *Phone: 650-772

Re: [Openstack-operators] [Performance][Meeting time] Possible meeting time change: feedback appreciated

OK, folks, new time chosen: 15:30 UTC (30 minutes earlier than usually, it looks like most of the people are ok with it). Starting with tomorrow (Tuesday, Aug 30th) we're running this time :) Cheers, Dina On Mon, Aug 22, 2016 at 12:09 PM, Dina Belova <dbel...@mirantis.com> wrote: >

Re: [openstack-dev] [Performance][Meeting time] Possible meeting time change: feedback appreciated

OK, folks, new time chosen: 15:30 UTC (30 minutes earlier than usually, it looks like most of the people are ok with it). Starting with tomorrow (Tuesday, Aug 30th) we're running this time :) Cheers, Dina On Mon, Aug 22, 2016 at 12:09 PM, Dina Belova <dbel...@mirantis.com> wrote: >

Re: [openstack-dev] [Openstack-operators] [Performance][Documentation] Please take a look on OpenStack perofmance-docs

tances. IMO, it'd be great if one could see >> instance flavor details (vCPUs, memory etc.) and, RAM and CPU over-commit >> ratios from host's perspective. >> >> >> Thanks, >> Kaustubh >> -- >> *From:* Dina Belova <dbel..

Re: [Openstack-operators] [Performance][Documentation] Please take a look on OpenStack perofmance-docs

tances. IMO, it'd be great if one could see >> instance flavor details (vCPUs, memory etc.) and, RAM and CPU over-commit >> ratios from host's perspective. >> >> >> Thanks, >> Kaustubh >> -- >> *From:* Dina Belova <dbel..

Re: [Openstack-operators] [Performance][Documentation] Please take a look on OpenStack perofmance-docs

e great if one could see > instance flavor details (vCPUs, memory etc.) and, RAM and CPU over-commit > ratios from host's perspective. > > > Thanks, > Kaustubh > ------ > *From:* Dina Belova <dbel...@mirantis.com> > *Sent:* Friday, August 19,

Re: [openstack-dev] [Openstack-operators] [Performance][Documentation] Please take a look on OpenStack perofmance-docs

e great if one could see > instance flavor details (vCPUs, memory etc.) and, RAM and CPU over-commit > ratios from host's perspective. > > > Thanks, > Kaustubh > ------ > *From:* Dina Belova <dbel...@mirantis.com> > *Sent:* Friday, August 19,

Re: [Openstack-operators] [Performance][Meeting time] Possible meeting time change: feedback appreciated

gt; 30-minute slot at 15:30 UTC or 18:00 UTC, but I realize it's hard to find > one to accommodate everyone. > > Thanks. > > Regards, > Augie > > > > > > From:Dina Belova <dbel...@mirantis.com> > To:lebre.adr...@free.fr, Joshua Harlow

Re: [openstack-dev] [Performance][Meeting time] Possible meeting time change: feedback appreciated

gt; 30-minute slot at 15:30 UTC or 18:00 UTC, but I realize it's hard to find > one to accommodate everyone. > > Thanks. > > Regards, > Augie > > > > > > From:Dina Belova <dbel...@mirantis.com> > To:lebre.adr...@free.fr, Joshua Harlow

Re: [openstack-dev] [Performance][Meeting time] Possible meeting time change: feedback appreciated

0/45 min, it would be great > if we could find a trade off a bit sooner. What's about 17:00 UTC ? > > Thanks, > Adrien > > ----- Mail original - > > De: "Dina Belova" <dbel...@mirantis.com> > > À: "OpenStack Development Mailing List" <opens

Re: [Openstack-operators] [Performance][Meeting time] Possible meeting time change: feedback appreciated

0/45 min, it would be great > if we could find a trade off a bit sooner. What's about 17:00 UTC ? > > Thanks, > Adrien > > ----- Mail original - > > De: "Dina Belova" <dbel...@mirantis.com> > > À: "OpenStack Development Mailing List" &l

[openstack-dev] [Performance][Documentation] Please take a look on OpenStack perofmance-docs

u here and share your opinion on what's going on regarding our performance researches. Thanks in advance! Cheers, Dina -- *Dina Belova* *Senior Software Engineer* Mirantis, Inc. 525 Almanor Avenue, 4th Floor Sunnyvale, CA 94085 *Phone: 650-772-8418Email: dbel...@mirantis.com <dbel...@mir

[openstack-dev] [Performance][Meeting time] Possible meeting time change: feedback appreciated

to internal daily meetings. The question is: can we move our weekly meeting to 17:30 UTC (10:30 PST)? It's late a bit for folks from Moscow (20:30), so I'd like to collect more feedback. Please leave your comments. Cheers, Dina -- *Dina Belova* *Senior Software Engineer* Mirantis, Inc. 525 Almanor

[Openstack-operators] [Performance][Meeting time] Possible meeting time change: feedback appreciated

to internal daily meetings. The question is: can we move our weekly meeting to 17:30 UTC (10:30 PST)? It's late a bit for folks from Moscow (20:30), so I'd like to collect more feedback. Please leave your comments. Cheers, Dina -- *Dina Belova* *Senior Software Engineer* Mirantis, Inc. 525 Almanor

[openstack-dev] [Performance] Team meeting canceled for today. Next meeting: July 19th

Folks, accidentally I have no opportunity to chair today meeting due to feeling sick, and as discussed on last Tuesday there is no chance I'll be available on July 12th. Let's assume our next meeting will be on Tuesday, July 19th at 16:00 UTC. Sorry for inconvenience! Cheers, Dina

[Openstack-operators] [Performance] No IRC meeting today

Folks, today we should have the Performance working group IRC meeting, but I have to announce that I won't be able to attend it today as well as several more folks. Therefore let's decline this event for today and make it happen next week due to the usual schedule. I'm really sorry for the

[openstack-dev] [Performance] No IRC meeting today

Folks, today we should have the Performance working group IRC meeting, but I have to announce that I won't be able to attend it today as well as several more folks. Therefore let's decline this event for today and make it happen next week due to the usual schedule. I'm really sorry for the

[Openstack-operators] [Performance] IRC meetings starting today after a break

Folks, just a reminder - today we'll start our periodical Performance Team meetings after a post-summit break we had. *#openstack-performance channel and 16:00 UTC* as usually :) See you! -- Dina ___ OpenStack-operators mailing list

[openstack-dev] [Performance] IRC meetings starting today after a break

Folks, just a reminder - today we'll start our periodical Performance Team meetings after a post-summit break we had. *#openstack-performance channel and 16:00 UTC* as usually :) See you! -- Dina __ OpenStack Development

Re: [openstack-dev] [Neutron] L3 HA testing on scale

t; Indeed it will be a terrific contribution. > > Edgar > > > On Apr 20, 2016, at 4:10 AM, Dina Belova <dbel...@mirantis.com> wrote: > > Folks, > > I think Ann's report is super cool and 100% worth publishing on OpenStack > performance-docs <http://docs.openstack.org/deve

[Openstack-operators] [Performance] Austin Performance Team working group session - please comment

Folks, we're going to have Performance Working Group session during the upcoming summit - here is the event description . Our team was kicked off during Mitaka Summit, so that was our first cycle :) Please attend the

[openstack-dev] [Performance] Austin Performance Team working group session - please comment

Folks, we're going to have Performance Working Group session during the upcoming summit - here is the event description . Our team was kicked off during Mitaka Summit, so that was our first cycle :) Please attend the

Re: [openstack-dev] [Neutron] L3 HA testing on scale

not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> >> >> -- >> Regards, >> Ann Kamyshnikova &

Re: [Openstack-operators] Allow to investigate instance actions after instance deletion

> | delete| req----- | - | > 2016-04-01T00:00:00.00 | > > +---+--+-++ > > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > htt

Re: [openstack-dev] [keystone][performance][profiling] Profiling Mitaka Keystone: some results and asking for a help

ixes have been proposed for both of these bugs. >> >> Cheers, >> --Morgan >> >> On Tue, Apr 12, 2016 at 12:38 AM, Dina Belova <dbel...@mirantis.com> >> wrote: >> >>> Matt, >>> >>> Thanks for sharing the information about your benchmark.

Re: [openstack-dev] [keystone][performance][profiling] Profiling Mitaka Keystone: some results and asking for a help

on my environment, and, due to the results, most probably it did not act as supposed during your benchmarking as well. Cheers, Dina On Mon, Apr 11, 2016 at 10:57 PM, Matt Fischer <m...@mattfischer.com> wrote: > On Mon, Apr 11, 2016 at 8:11 AM, Dina Belova <dbel...@mirantis.com>

[openstack-dev] [keystone][performance][profiling] Profiling Mitaka Keystone: some results and asking for a help

Hey, openstackers! Recently I was trying to profile Keystone (OpenStack Liberty vs Mitaka) using this set of changes (that's currently on review - some final steps are required there to finish the work) and

Re: [Openstack-operators] [Rally] Scale testing of openstack

{ > "name": "m1.tiny" > }, > "image": { > "name": "cirros-0.3.4-x86_64" > } > }, > > > Best regards, > Boris Pavlovic > &

Re: [Openstack-operators] [Rally] Scale testing of openstack

ind. > > Thanks, > > Edgar > > From: Akshay Kumar Sanghai <akshaykumarsang...@gmail.com> > Date: Thursday, March 10, 2016 at 9:43 AM > To: Dina Belova <dbel...@mirantis.com> > Cc: openstack-operators <openstack-operators@lists.openstack.org> > Subjec

Re: [Openstack-operators] [Rally] Scale testing of openstack

gt; load from those VMs > > > Thanks, > Akshay Sanghai > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [Performance] Let's have next meeting on March 15th

Just a reminder: we won't have a meeting today! Happy Women's Day! Cheers, Dina On Tue, Mar 1, 2016 at 7:54 PM, Dina Belova <dbel...@mirantis.com> wrote: > Folks, > > due to the schedule our next meeting > <https://wiki.openstack.org/wiki/Meetings/Performance> is going

[openstack-dev] [Performance] Let's have next meeting on March 15th

Folks, due to the schedule our next meeting is going to happen on March 8th, that's International Women's Day (non-working day in Russia, for instance). So let's have our next meeting scheduled for March 15th. Cheers, Dina

Re: [Openstack-operators] [Performance][Holidays] IRC meeting schedule

r team, but productive year! See you in 2016 :) Cheers, Dina On Wed, Dec 16, 2015 at 11:18 PM, Dina Belova <dbel...@mirantis.com> wrote: > Folks, > > we had an IRC meeting yesterday, and holidays schedule was one of the > topics covered. Although, the final decision was not m

Re: [openstack-dev] [Performance][Holidays] IRC meeting schedule

r team, but productive year! See you in 2016 :) Cheers, Dina On Wed, Dec 16, 2015 at 11:18 PM, Dina Belova <dbel...@mirantis.com> wrote: > Folks, > > we had an IRC meeting yesterday, and holidays schedule was one of the > topics covered. Although, the final decision was not m

[Openstack-operators] [Performance][Holidays] IRC meeting schedule

Folks, we had an IRC meeting yesterday, and holidays schedule was one of the topics covered. Although, the final decision was not made, so let's finalise everything here :) There are few options for 2015 and 2016 now: 1) Let's *do not have more meetings this year or let's meet last time on Dec

[openstack-dev] [Performance][Holidays] IRC meeting schedule

Folks, we had an IRC meeting yesterday, and holidays schedule was one of the topics covered. Although, the final decision was not made, so let's finalise everything here :) There are few options for 2015 and 2016 now: 1) Let's *do not have more meetings this year or let's meet last time on Dec

Re: [Openstack-operators] [openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

:19 PM, Sylvain Bauza <sba...@redhat.com> wrote: > > > Le 07/12/2015 11:27, Dina Belova a écrit : > > Ok, so due to the responses I propose to finalise this decision and move > the meeting to *16:00 UTC (Tuesdays)*. > So tomorrow please join me *on #openstack-perfor

Re: [openstack-dev] [Openstack-operators] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

:19 PM, Sylvain Bauza <sba...@redhat.com> wrote: > > > Le 07/12/2015 11:27, Dina Belova a écrit : > > Ok, so due to the responses I propose to finalise this decision and move > the meeting to *16:00 UTC (Tuesdays)*. > So tomorrow please join me *on #openstack-perfor

Re: [Openstack-operators] [openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

__ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Best re

Re: [openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

__ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/

[openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

Dear performance folks, There is a suggestion to move our meeting time from 15:00 UTC (Tuesdays ) to 16:00 UTC (also Tuesdays ) to make them more comfortable for

[Openstack-operators] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

Dear performance folks, There is a suggestion to move our meeting time from 15:00 UTC (Tuesdays ) to 16:00 UTC (also Tuesdays ) to make them more comfortable for

Re: [Openstack-operators] [openstack-tc] [Performance] Where to place OpenStack performance documentation?

the docs to the docs.openstack.org - like being now part of 'Rally' program. Cheers, Dina On Wed, Dec 2, 2015 at 11:53 AM, Thierry Carrez <thie...@openstack.org> wrote: > Dina Belova wrote: > > of course that's possible in future if there will be significant results > >

Re: [Openstack-operators] [openstack-tc] [Performance] Where to place OpenStack performance documentation?

t; > > Best regards, > Boris Pavlovic > > On Tue, Dec 1, 2015 at 4:57 AM, Dina Belova <dbel...@mirantis.com> wrote: > >> Thierry, >> >> this can work, of course, but in that case we won't have, for instance, >> ready reviewing mechanism for test plans.

[Openstack-operators] [Performance] Where to place OpenStack performance documentation?

Hi TC members, I'm writing to find out where to place information that Performance Team would like to share with community. We would like to share (and grab the feedback on) test plans (for OpenStack itself - we can use and develop Rally, for underlying layers like DB, MQ something else.),

Re: [openstack-dev] [Performance] Filling performance team working items list and taking part in their resolving

Matt, I guess it's good solution. Thanks for doing that! Cheers, Dina On Mon, Nov 30, 2015 at 6:30 PM, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > > > On 11/27/2015 3:54 AM, Dina Belova wrote: > >> Hey OpenStack devs and operators! >> >> Folks, I

[Openstack-operators] [Performance] Filling performance team working items list and taking part in their resolving

Hey OpenStack devs and operators! Folks, I would like to share list of working items Performance Team is currently having in the backlog - https://etherpad.openstack.org/p/perf-zoom-zoom [Work Items to grab] section. I'm really encouraging you to fill it with concrete pieces of work you think

[openstack-dev] [Performance] Filling performance team working items list and taking part in their resolving

Hey OpenStack devs and operators! Folks, I would like to share list of working items Performance Team is currently having in the backlog - https://etherpad.openstack.org/p/perf-zoom-zoom [Work Items to grab] section. I'm really encouraging you to fill it with concrete pieces of work you think

Re: [Openstack-operators] [Scale][Performance] / compute_nodes ratio experience

e doing > successfully, but keep in mind that it depends *a lot* on what sort of > workloads the cloud is supporting. > > --Dan > -- Best regards, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [Scale][Performance] / compute_nodes ratio experience

Dear operators, yesterday we (Performance Team) had weekly IRC meeting , one of the things on board to discuss was nova-conductor performance issue

Re: [openstack-dev] [Openstack-operators] Mirantis Fuel Multi-Region

aunchpad.net/fuel/+question/267127 >> >> http://lists.openstack.org/pipermail/openstack-dev/2015-October/076298.html >> >> >> -- >> Eren Türkay, System Administrator >> https://skyatlas.com/ | +90 850 885 0357 >> >> Yildiz Teknik Universitesi Davutpasa Kam

Re: [Openstack-operators] Mirantis Fuel Multi-Region

aunchpad.net/fuel/+question/267127 >> >> http://lists.openstack.org/pipermail/openstack-dev/2015-October/076298.html >> >> >> -- >> Eren Türkay, System Administrator >> https://skyatlas.com/ | +90 850 885 0357 >> >> Yildiz Teknik Universitesi Davutpasa Kam

Re: [Openstack-operators] [nova] FYI, local conductor mode is deprecated, pending removal in N

others are trying to >> achieve, given equal hardware types for each, and what are the barriers >> to this happening? >> >> >>> ___ >>> OpenStack-operators mailing list >>> OpenStack-operators@lists.o

[openstack-dev] [Performance] Please add your discussion items to the next meeting agenda

Folks, Last time we had Performance team meeting, we ha did a bit messy due to the lack of time spent by team members to fill the meeting agenda. Let's fix it this time! :) Please add your items to the agenda https://wiki.openstack.org/wiki/Meetings/Performance#Agenda_for_next_meeting (I

Re: [Openstack-operators] [openstack-dev] Performance Team summit session results

t; > > > I've created primary wiki pages for the team > > <https://wiki.openstack.org/wiki/Performance_Team> and its meetings > > <https://wiki.openstack.org/wiki/Meetings/Performance> - please feel > free > > to add more items to the agenda. > >

Re: [openstack-dev] [Openstack-operators] Performance Team summit session results

t; > > > I've created primary wiki pages for the team > > <https://wiki.openstack.org/wiki/Performance_Team> and its meetings > > <https://wiki.openstack.org/wiki/Meetings/Performance> - please feel > free > > to add more items to the agenda. > >

Re: [Openstack-operators] [openstack-dev] Performance Team summit session results

omorrow :) Cheers, Dina On Mon, Nov 9, 2015 at 5:38 PM, Dina Belova <dbel...@mirantis.com> wrote: > Matt, > > thank you so much for covering [1], [2] and [3] points - I'll ping folks > who've written these lines directly and will try to find out the answers. > > Cheers,

Re: [openstack-dev] [Openstack-operators] Performance Team summit session results

omorrow :) Cheers, Dina On Mon, Nov 9, 2015 at 5:38 PM, Dina Belova <dbel...@mirantis.com> wrote: > Matt, > > thank you so much for covering [1], [2] and [3] points - I'll ping folks > who've written these lines directly and will try to find out the answers. > > Cheers,

Re: [Openstack-operators] [openstack-dev] Performance Team summit session results

Matt Riedemann wrote: > >> >> >> On 10/29/2015 9:30 AM, Dina Belova wrote: >> >>> Hey folks! >>> >>> On Tuesday we had great summit session about performance team kick-off >>> and yesterday it was a great LDT session as well and I’m rea

Re: [openstack-dev] [tc][all][osprofiler] OSprofiler is dead, long live OSprofiler

enStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Best regards, Dina Belova Software Engineer Mirantis Inc.

Re: [Openstack-operators] [openstack-dev] [tc][all][osprofiler] OSprofiler is dead, long live OSprofiler

enStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Best regards, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Performance Team summit session results

Hey folks! On Tuesday we had great summit session about performance team kick-off and yesterday it was a great LDT session as well and I’m really glad to see how much does the OpenStack performance topic is important for all of us. 40 minutes session surely was not enough to analyse everyone’s

[openstack-dev] Performance Team summit session results

Hey folks! On Tuesday we had great summit session about performance team kick-off and yesterday it was a great LDT session as well and I’m really glad to see how much does the OpenStack performance topic is important for all of us. 40 minutes session surely was not enough to analyse everyone’s

Re: [Openstack-operators] Informal Ops Meetup?

t; > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org OpenStack-operators@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > __

Re: [Openstack-operators] Informal Ops Meetup?

penStack-operators mailing list >> >>>> OpenStack-operators@lists.openstack.org >> >>>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >>>> >> >>> >> >>> __

Re: [Openstack-operators] Keystone performance issue

atural behavior? or we can optimize keystone performance more? > > What are your suggestions? > > I'm pretty focused on doing exactly that right now, but we will need to > establish some baselines and try to make sure we have tools to maintain > the performance long-term. > > ___ > Open

Re: [openstack-dev] [Large Deployments Team][Performance Team] New informal working group suggestion

to set Doodle voting for the time people will be comfortable with to have periodic meetings :) Cheers, Dina On Fri, Sep 25, 2015 at 1:52 PM, Sandeep Raman <sandeep.ra...@gmail.com> wrote: > On Tue, Sep 22, 2015 at 6:27 PM, Dina Belova <dbel...@mirantis.com> wrote: > >> Hey,

Re: [openstack-dev] [Openstack-operators] [Large Deployments Team][Performance Team] New informal working group suggestion

ntry on the neutron side). > > ___ > Kris Lindgren > Senior Linux Systems Engineer > GoDaddy > > From: Matt Van Winkle > Date: Tuesday, September 22, 2015 at 7:46 AM > To: Dina Belova, OpenStack Development Mailing List, " > opensta

Re: [Openstack-operators] [Large Deployments Team][Performance Team] New informal working group suggestion

ntry on the neutron side). > > ___ > Kris Lindgren > Senior Linux Systems Engineer > GoDaddy > > From: Matt Van Winkle > Date: Tuesday, September 22, 2015 at 7:46 AM > To: Dina Belova, OpenStack Development Mailing List, " > opensta

[Openstack-operators] Fwd: [Large Deployments Team][Performance Team] New informal working group suggestion

cfp/details/5> to meet in Tokyo and hold a kick-off meeting. I would like to apologise I'm writing to two mailing lists at the same time, but I want to make sure that all possibly interested people will notice the email. Thanks and see you in Tokyo :) Cheers, Dina -- Best regards, Dina

[openstack-dev] [Large Deployments Team][Performance Team] New informal working group suggestion

cfp/details/5> to meet in Tokyo and hold a kick-off meeting. I would like to apologise I'm writing to two mailing lists at the same time, but I want to make sure that all possibly interested people will notice the email. Thanks and see you in Tokyo :) Cheers, Dina -- Best regards, Dina

Re: [openstack-dev] [Fuel] Rabbitmq 3.4.0 upgrade for the 6.1 release, is it worth it?

-- Best regards, Dina Belova Software Engineer Mirantis Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org

Re: [openstack-dev] [Ceilometer]Unit test failed on branch stable/icehouse

- ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dina Belova Software Engineer Mirantis Inc

Re: [openstack-dev] [Ceilometer] Adding pylint checking of new ceilometer patches

/openstack-dev -- Best regards, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Ceilometer] MySQL performance and Mongodb backend maturity question

___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev

Re: [openstack-dev] [Ceilometer] Adding Dina Belova to ceilometer-core

valuable. She's been doing a lot of reviews and has been very active in our community. I'd like to propose that we add Dina Belova to the ceilometer-core group, as I'm convinced it'll help the project. Please, dear ceilometer-core members, reply with your votes! With seven yeas and zero

Re: [openstack-dev] [ceilometer]How to collect the real-time data

? whether plan to implement it or not Thanks! Jian Li ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dina Belova Software Engineer

Re: [openstack-dev] [Ceilometer][WSME] Sphinx failing sporadically because of wsme autodoc extension

-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org

Re: [openstack-dev] [ceilometer] gate-ceilometer-python33 failed because of wrong setup.py in happybase

for it. I'm happy to have clear understanding your thought. On Wednesday, August 13, 2014 7:54 PM, Dina Belova wrote: Here it is: https://review.openstack.org/#/c/113842/ Thank you for providing the fix. I surprised the speed for it. it's really fast... Thanks again! Hisashi Osanai -- Best

Re: [openstack-dev] [ceilometer] gate-ceilometer-python33 failed because of wrong setup.py in happybase

for the direct cause, right? Thanks in advance, Hisashi Osanai ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dina Belova Software Engineer

Re: [openstack-dev] [ceilometer] gate-ceilometer-python33 failed because of wrong setup.py in happybase

___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev

Re: [openstack-dev] [ceilometer] gate-ceilometer-python33 failed because of wrong setup.py in happybase

Here it is: https://review.openstack.org/#/c/113842/ Thanks, Dina On Wed, Aug 13, 2014 at 2:40 PM, Dina Belova dbel...@mirantis.com wrote: Julien, will do right now. Thanks Dina On Wed, Aug 13, 2014 at 2:35 PM, Julien Danjou jul...@danjou.info wrote: On Wed, Aug 13 2014, Osanai

Re: [openstack-dev] [ceilometer] tox -epy26 failed because of insufficient test environment

, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ceilometer] tox -epy26 failed because of insufficient test environment

like it should be ok for now. Thanks, Dina On Tue, Aug 12, 2014 at 2:23 PM, Osanai, Hisashi osanai.hisa...@jp.fujitsu.com wrote: On Tuesday, August 12, 2014 7:05 PM, Dina Belova wrote: that is blocking the Ceilometer gate at all for now. Thank you for your quick response. I understand

Re: [openstack-dev] [qa] Test Ceilometer polling in tempest

and Best Regards, Ildiko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dina Belova Software Engineer Mirantis Inc

[openstack-dev] [oslo][messaging] Further improvements and refactoring

/status:open+owner:akornienko+project:openstack/oslo.messaging,n,z Best regards, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo][messaging] Further improvements and refactoring

, Alexey, Do you mind filing some spec(s) please? http://markmail.org/message/yqhndsr3zrqcfwq4 http://markmail.org/message/kpk35uikcnodq3jb thanks, dims On Tue, Jun 10, 2014 at 7:03 AM, Dina Belova dbel...@mirantis.com wrote: Hello, stackers! Oslo.messaging is future of how different

Re: [openstack-dev] New setuptools release seems to break some of the OS projects

progress. Doug On Mon, Jun 2, 2014 at 8:07 AM, Dina Belova dbel...@mirantis.com wrote: Folks, o/ I did not find the appropriate discussion in the ML, so decided to start it myself - I see that new setuptools release seems to break at least some of the OpenStack gates and even more

Re: [openstack-dev] New setuptools release seems to break some of the OS projects

the lines of a version-cap that we'd apply in the global requirements.txt, for dependencies pulled in that way). Cheers, Eoghan Doug On Mon, Jun 2, 2014 at 8:07 AM, Dina Belova dbel...@mirantis.com wrote: Folks, o/ I did not find the appropriate discussion in the ML, so decided

Re: [openstack-dev] New setuptools release seems to break some of the OS projects

Folks, setuptools 4.0.1 and 3.7.1 have been released - these should fix the issue. -- Dina On Mon, Jun 2, 2014 at 4:45 PM, Dina Belova dbel...@mirantis.com wrote: The newest setuptools has been removed from the gate mirror - the latest there now is 3.6 - that *might* in the gate. We'll see

Re: [openstack-dev] [Blazar] Weekly meeting Blazar (previously Climate) [Climate]

, I want to make sure we run the weekly meeting today at 3pm UTC. Thanks, -Sylvain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dina

Re: [openstack-dev] [Keystone] [Blazar] [Ironic] Py26/27 gates failing because of keystoneclient-0.9.0

-requirements.txt to only accept keystoneclient 0.9.0 ? Thanks, -Sylvain ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dina Belova Software Engineer

[openstack-dev] [climate] Friday Meeting

Folks, o/ I finally got my dates for the US trip, and I have to say, that I won't be able to attend our closest Friday meeting as I'll be flying at this moment) Sylvain, will you be able to hold the meeting? Best regards, Dina Belova Software Engineer Mirantis Inc

Re: [openstack-dev] [climate] Friday Meeting

topics in mailing-list if needed. -Sylvain 2014-04-30 19:17 GMT+02:00 Dina Belova dbel...@mirantis.com: Folks, o/ I finally got my dates for the US trip, and I have to say, that I won't be able to attend our closest Friday meeting as I'll be flying at this moment) Sylvain, will you

Re: [openstack-dev] [Climate] Meeting minutes

client, but as V1 and V2 are quite identical, I can take this blueprint. -Sylvain 2014-04-27 17:44 GMT+02:00 Dina Belova dbel...@mirantis.com: Christian, variant #2 looks good to me) On Fri, Apr 25, 2014 at 9:59 PM, Martinez, Christian christian.marti...@intel.com wrote: Hello

Re: [openstack-dev] [ceilometer] cancelling team meeting for May 1st

@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin

Re: [openstack-dev] [Climate] Meeting minutes

___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best regards, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev

[openstack-dev] [Climate] nominating Pablo Andres Fuente for the Climate core reviewers team

and background I suppose it'll be great to add him to the team. Best regards, Dina Belova Software Engineer Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

  1   2   >