Re: [openstack-dev] Avoiding regression in project governance

2015-03-10 Thread Devananda van der Veen
On Tue, Mar 10, 2015 at 12:12 PM Lauren Sell wrote: > Dissolving the integrated release without having a solid plan and > replacement is difficult to communicate to people who depend on OpenStack. > We’re struggling on that front. > > That said, I’m still optimistic about project structure reform

Re: [openstack-dev] Avoiding regression in project governance

2015-03-10 Thread Devananda van der Veen
On Tue, Mar 10, 2015 at 12:00 PM Jeremy Stanley wrote: > On 2015-03-10 14:42:18 -0400 (-0400), Russell Bryant wrote: > [...] > > As to specific tags, I refer back to this: > > > > http://governance.openstack.org/reference/incubation- > integration-requirements.html > > > > We worked pretty hard t

[openstack-dev] [murano] PTL elections

2015-03-10 Thread Sergey Lukjanov
Hi folks, due to the requirement to have officially elected PTL, we're running elections for the Murano PTL for Kilo and Liberty cycles. Schedule and policies are fully aligned with official OpenStack PTLs elections. You can find more info in official elections wiki page [0] and the same page for

Re: [openstack-dev] [heat] Unknown resource OS::Heat::ScaledResource

2015-03-10 Thread Angus Salkeld
On Wed, Mar 11, 2015 at 3:04 AM, Zane Bitter wrote: > On 10/03/15 12:26, Manickam, Kanagaraj wrote: > >> Hi, >> >> I observed in one of the patch mentioned below, OS::Heat::ScaledResource >> is reported as unknown, could anyone help here to resolve the issue. >> Thanks. >> >> http://logs.openstac

Re: [openstack-dev] [Fuel] Recent issues with our review workflow

2015-03-10 Thread Ryan Moe
Here are some examples of proposing changes prior to being merged in master [0][1][2][3][4]. [0] is a perfect example of why this isn't a good process. A change was proposed to stable/6.0 before master was merged, and now the change to master needs to be reworked based on review feedback. Premature

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

2015-03-10 Thread Alan Pevec
> The wheel has been removed from PyPI and anyone installing testtools > 1.7.0 now will install from source which works fine. On stable/icehouse devstack fails[*] with pkg_resources.VersionConflict: (unittest2 0.5.1 (/usr/lib/python2.7/dist-packages), Requirement.parse('unittest2>=1.0.0')) when in

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

2015-03-10 Thread Joe Gordon
On Tue, Mar 10, 2015 at 5:09 PM, Alan Pevec wrote: > > The wheel has been removed from PyPI and anyone installing testtools > > 1.7.0 now will install from source which works fine. > > On stable/icehouse devstack fails[*] with > pkg_resources.VersionConflict: (unittest2 0.5.1 > (/usr/lib/python2.

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

2015-03-10 Thread Robert Collins
On 11 March 2015 at 10:27, Dolph Mathews wrote: > Great to hear that this has been addressed, as this impacted a few tests in > keystone. > > (but why was the fix not released as 1.7.1?) There will be a new release indeed later today to fix a small UI issue on pypy3 which affects testtools CI, bu

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

2015-03-10 Thread Robert Collins
On 11 March 2015 at 13:59, Robert Collins wrote: > On 11 March 2015 at 10:27, Dolph Mathews wrote: >> Great to hear that this has been addressed, as this impacted a few tests in >> keystone. >> >> (but why was the fix not released as 1.7.1?) > > There will be a new release indeed later today to f

Re: [openstack-dev] [python-novaclient] Better wording for secgroup-*-default-rules? help text

2015-03-10 Thread Chris St. Pierre
On Tue, Mar 10, 2015 at 4:50 PM, melanie witt wrote: > > I don't think your suggestion for the help text is excessively verbose. > There are already longer help texts for some commands than that, and I > think it's important to accurately explain what commands do. You can use a > multiline docstri

Re: [openstack-dev] Avoiding regression in project governance

2015-03-10 Thread Joe Gordon
On Tue, Mar 10, 2015 at 3:31 PM, James E. Blair wrote: > Joe Gordon writes: > > > After watching the TC meeting, and double checking with the meeting notes > > [0], it looks like the magnum vote was deferred to next week. But what > > concerns me is the lack of action items assigned that will he

Re: [openstack-dev] [python-novaclient] Better wording for secgroup-*-default-rules? help text

2015-03-10 Thread melanie witt
On Mar 10, 2015, at 19:28, Chris St. Pierre wrote: > Ah, look at that! In some other projects, flake8 complains about a docstring > whose first line doesn't end in a period, so I didn't think it'd be possible. > If you don't think that's excessively verbose, there'll be a patch in > shortly. T

Re: [openstack-dev] [Congress]How to add tempest tests for testing murano drive

2015-03-10 Thread Aaron Rosen
The ci runs: `cp -r contrib/tempest/tempest /opt/stack/tempest` so all you need to do is add you're file and it will get copied into tempest. Aaron On Tue, Mar 10, 2015 at 10:31 AM, Wong, Hong wrote: > Hi Aaron, > > > > I just want to confirm how CI is running the congress tempest tests in it

Re: [openstack-dev] [nova] Unshelve Instance Performance Optimization Questions

2015-03-10 Thread Kekane, Abhishek
Hi Devs, As another alternative we can use start/stop API’s instead of shelve/unshelve the instance. Following is the details of start/stop and shelve/unshelve on the basis of cpu/memory/disk released and fast respawning. API’S: start/stop cpu/memory released: No Disk released: No Fast respawni

Re: [openstack-dev] [Glance] Proposal to change Glance meeting time.

2015-03-10 Thread Inessa Vasilevskaya
+1 On Mon, Mar 9, 2015 at 2:43 AM, Alexander Tivelkov wrote: > Works for me, but the previous one worked as well. So, consider my vote as > +1 unless the majority is against this :) > > -- > Regards, > Alexander Tivelkov > > On Mon, Mar 9, 2015 at 12:36 AM, Fei Long Wang > wrote: > >> Oh, it m

<    1   2