[openstack-dev] Fwd: [Openstack-stable-maint] Stable check of openstack/manila failed

[Matt Riedemann]

Manila jobs in stable/liberty are broken, and have been for awhile.

It looks like manila isn't using upper-constraints when running unit 
tests, not even on stable/mitaka or master. So in liberty it's pulling 
in uncapped oslo.utils 3.13 even though the upper constraint for 
oslo.utils in liberty is 3.2.


Who from the manila team is going to be working on fixing this, either 
via getting upper-constraints in place in the tox.ini for manila (on all 
supported branches) or performing some kind of workaround in the code?



 Forwarded Message 
Subject: [Openstack-stable-maint] Stable check of openstack/manila failed
Date: Sat, 25 Jun 2016 06:11:05 +
From: A mailing list for the OpenStack Stable Branch test reports. 


Reply-To: openstack-dev@lists.openstack.org
To: openstack-stable-ma...@lists.openstack.org

Build failed.

- periodic-manila-docs-liberty 
http://logs.openstack.org/periodic-stable/periodic-manila-docs-liberty/70e8bd8/ 
: SUCCESS in 4m 43s
- periodic-manila-python27-liberty 
http://logs.openstack.org/periodic-stable/periodic-manila-python27-liberty/7e1d14d/ 
: FAILURE in 3m 30s
- periodic-manila-docs-mitaka 
http://logs.openstack.org/periodic-stable/periodic-manila-docs-mitaka/0f1ab3f/ 
: SUCCESS in 4m 44s
- periodic-manila-python27-mitaka 
http://logs.openstack.org/periodic-stable/periodic-manila-python27-mitaka/d94d907/ 
: SUCCESS in 6m 04s


___
Openstack-stable-maint mailing list
openstack-stable-ma...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint


__
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

[openstack-dev] [tripleo] CI down - No connected Gearman servers

[Emilien Macchi]

Hi all,

CI is currently entirely  red:
https://bugs.launchpad.net/tripleo/+bug/1594732
http://logs.openstack.org/11/333511/5/check-tripleo/gate-tripleo-ci-centos-7-nonha/16f72e8/console.html#_2016-06-25_15_43_35_798040

gear.Client.unknown - ERROR - Connection  timed out waiting for a response to a
submit job request: 
gear.NoConnectedServersError: No connected Gearman servers

If someone who has secret access to tripleo CI could restart Gearman
that would be awesome,

Thanks and enjoy week-end.
-- 
Emilien Macchi

__
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

Re: [openstack-dev] [Fuel] Merge IRC channels

[Jonnalagadda, Venkata]

Yes. That’s a good move..

​
Thanks & Regards,

J. Venkata Mahesh


From: Roman Prykhodchenko [mailto:m...@romcheg.me]
Sent: Saturday, June 25, 2016 3:09 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [Fuel] Merge IRC channels

Since Fuel is a part of OpenStack now, should we rename #fuel to 
#openstack-fuel?

- romcheg
24 черв. 2016 р. о 18:49 Andrew Woodward 
> написав(ла):

There is also #fuel-devops

I never liked having all the channels, so +1

On Fri, Jun 24, 2016 at 4:25 AM Anastasia Urlapova 
> wrote:
Vova,
please don't forget merge #fuel-qa into a #fuel

On Fri, Jun 24, 2016 at 1:55 PM, Vladimir Kozhukalov 
> wrote:
Nice. #fuel-infra is to merged as well.

Vladimir Kozhukalov

On Fri, Jun 24, 2016 at 1:50 PM, Aleksandra Fedorova 
> wrote:
And +1 for #fuel-infra
As of now it will be more useful if infra issues related to project will be 
visible for project developers. We don't have much infra-related traffic on IRC 
for now, and we will be able to split again if we got it.

On Fri, Jun 24, 2016 at 1:26 PM, Vladimir Kozhukalov 
> wrote:
Dear colleagues,
We have a few IRC channels but the level of activity there is quite low.
#fuel
#fuel-dev
#fuel-python
#fuel-infra
My suggestion is to merge all these channels into a single IRC channel #fuel.
Other #fuel-* channels are to be deprecated.
What do you think of this?


Vladimir Kozhukalov

__
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



--
Aleksandra Fedorova
Fuel CI Engineer
bookwar

__
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


__
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

__
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
--
--
Andrew Woodward
Mirantis
Fuel Community Ambassador
Ceph Community
__
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

__
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

Re: [openstack-dev] [Openstack-operators] [gnocchi] profiling and benchmarking 2.1.x

[Curtis]

On Fri, Jun 24, 2016 at 2:09 PM, gordon chung  wrote:
> hi,
>
> i realised i didn't post this beyond IRC, so here are some initial
> numbers for some performance/benchmarking i did on Gnocchi.
>
> http://www.slideshare.net/GordonChung/gnocchi-profiling-21x
>
> as a headsup, the data above is using Ceph and with pretty much a
> default configuration. i'm currently doing more tests to see how it
> works if you actually start turning some knobs on Ceph (spoiler: it gets
> better).

Thanks Gordon. I will definitely take a look through your slides.
Looking forward to what test results you get when you start turning
some knobs.

Thanks,
Curtis.

>
> cheers,
>
> --
> gord
> ___
> OpenStack-operators mailing list
> openstack-operat...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



-- 
Blog: serverascode.com

__
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

[openstack-dev] [trove] OpenStack Trove Ocata Virtual Midcycle,

[Amrith Kumar]

After we discussed and announced this mid-cycle, there has been some feedback 
that (a) it would be better to hold the mid-cycle earlier, and (b) NYC was not 
the most convenient location for all attendees.

Thanks for the feedback. Given that we are coming up on a holiday week (in the 
US), and the N2 deadline in the week of July 18th, I propose that we conduct 
the Trove Ocata midcycle as a virtual midcycle in the week of July 25th.

In the interest of time, I'd like all those who are able and interested in 
attending to reply to this email so we can confirm this at the Trove meeting on 
Wednesday.

Trove Ocata Virtual Midcycle
Date and Time: 4 hours each day, July 26, 27 and 28; 1300-1700 EDT 
(1200 - 1600 CDT, 1000 to 1400 PDT, 1700 to 2100 UTC)
Location: Virtual midcycle, [likely] Google Hangouts with audio dial in 
(telephone)

Thanks,

-amrith



> -Original Message-
> From: Amrith Kumar
> Sent: Wednesday, June 22, 2016 9:54 AM
> To: openstack-dev 
> Subject: OpenStack Trove Ocata Midcycle, NYC, August 25 and 26.
> 
> The Trove midcycle will be held in midtown NYC, thanks to IBM for hosting
> the event, on August 25th and 26th.
> 
> If you are interested in attending, please join the Trove meeting today,
> 2pm Eastern Time (#openstack-meeting-alt) and register at
> http://www.eventbrite.com/e/openstack-trove-ocata-midcycle-tickets-
> 26197358003.
> 
> An etherpad for proposing sessions is at
> https://etherpad.openstack.org/p/ocata-trove-midcycle
> 
> This will be a two-day event (not three days as we have done in the past)
> so we will start early on 25th and go as late as we can on 26th
> recognizing that people who have to travel out of NYC may want to get late
> flights (9pm, 10pm) on Friday.
> 
> Thanks,
> 
> -amrith

__
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

Re: [openstack-dev] [Fuel] Merge IRC channels

[Roman Prykhodchenko]

Since Fuel is a part of OpenStack now, should we rename #fuel to 
#openstack-fuel?

- romcheg
> 24 черв. 2016 р. о 18:49 Andrew Woodward  написав(ла):
> 
> There is also #fuel-devops
> 
> I never liked having all the channels, so +1
> 
> On Fri, Jun 24, 2016 at 4:25 AM Anastasia Urlapova  > wrote:
> Vova,
> please don't forget merge #fuel-qa into a #fuel
> 
> On Fri, Jun 24, 2016 at 1:55 PM, Vladimir Kozhukalov 
> > wrote:
> Nice. #fuel-infra is to merged as well.
> 
> Vladimir Kozhukalov
> 
> On Fri, Jun 24, 2016 at 1:50 PM, Aleksandra Fedorova  > wrote:
> And +1 for #fuel-infra
> 
> As of now it will be more useful if infra issues related to project will be 
> visible for project developers. We don't have much infra-related traffic on 
> IRC for now, and we will be able to split again if we got it.
> 
> On Fri, Jun 24, 2016 at 1:26 PM, Vladimir Kozhukalov 
> > wrote:
> Dear colleagues,
> 
> We have a few IRC channels but the level of activity there is quite low.
> 
> #fuel
> #fuel-dev
> #fuel-python
> #fuel-infra
> 
> My suggestion is to merge all these channels into a single IRC channel #fuel.
> Other #fuel-* channels are to be deprecated.
> 
> What do you think of this?
> 
> 
> Vladimir Kozhukalov
> 
> __
> 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 
> 
> 
> 
> 
> 
> --
> Aleksandra Fedorova
> Fuel CI Engineer
> bookwar
> 
> __
> 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 
> 
> 
> 
> 
> __
> 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 
> 
> 
> 
> __
> 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 
> 
> --
> --
> 
> Andrew Woodward
> 
> Mirantis
> 
> Fuel Community Ambassador
> 
> Ceph Community
> 
> __
> 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



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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