On Wed, 16 Mar 2016, Salvatore Orlando wrote:
- Looking at quotas it is worth distinguishing between management (eg::
resource limits per tenant and/or users), and enforcement (eg.: can the
bakery service give me 4 cookies or did I already eat too many?)
While for the reasons listed throughout
On 16 March 2016 at 15:26, Thierry Carrez wrote:
> Hi PTLs,
>
> Here is the proposed slot allocation for project teams at the Newton
> Design Summit in Austin. This is based on the requests the mitaka PTLs have
> made, space availability and project activity & collaboration needs.
>
> | fb: fishb
On 3/17/2016 1:26 PM, Tim Bell wrote:
On 17/03/16 18:29, "Sean Dague" wrote:
On 03/17/2016 11:57 AM, Markus Zoeller wrote:
Suggested action items:
1. I close the open wish list items older than 6 months (=138 reports)
and explain in the closing comment that they are outdated and the
On Thu, Mar 17, 2016 at 3:24 PM, Kairat Kushaev wrote:
>
> Also curious about this. It seems weird to separate the 'positive' and
> the 'negative' ones, assuming those patches are mostly contributed by
> the same group of developers.
>
>
> Yeah, agree. This approach leads to situation when I nee
Kanthi, sorry for chiming in, I suggest you may have a chance to take
a look at Mistral[1], which is the workflow as a service in
OpenStack(or without OpenStack).
[1]: http://docs.openstack.org/developer/mistral/
On Sun, Mar 20, 2016 at 5:35 AM, pnkk wrote:
> Filed it at https://bugs.launchpad.n
Hello,
Recently when testing neutron upgrades for openstack-ansible, I ran into an
existing bug [1] where the networksecuritybindings and portsecuritybindings
tables were not populated after an upgrade from Kilo to Liberty. Updating the
table manually resolved the issue, as mentioned in the bug
As an Op, I've seen quota's in the db get out of sync all the time I'm sure
some of my clouds right now have some stuff out of sync :/
With my dev hat on:
The code is really hard to get right.
There are also a lot of places quota's are missing. quota's per host aggregate,
quota's for floati
Matt Riedemann wrote:
I'd like to propose tonyb for stable-maint-core. Tony is pretty much my
day to day guy on stable, he's generally in every stable team meeting
(which is not attended well so I appreciate it), and he's as proactive as
ever on staying on top of gate issues when they come
On Thu, Mar 17, 2016 at 12:24 PM, Vasyl Saienko
wrote:
> Hello Community,
>
> We started using tempest/devstack plugins. They allows to do not bother
> other teams when Project specific changes need to be done. Tempest
> configuration is still performed at devstack [0].
> So I would like to rise
On 18 Mar 2016 20:11, "Matt Riedemann" wrote:
>
> I'd like to propose tonyb for stable-maint-core.
> Please respond with ack/nack.
+1, Great work Tony.
--
Kind Regards,
Dave Walker
__
OpenStack Development Mailing List (not
Hi all,
I'm writing the spec for the COE drivers, and I wanted some feedback about what
it should include. I'm trying to reconstruct some of the discussion that was
had at the mid-cycle meet-up, but since I wasn't there I need to rely on people
who were :)
>From my perspective, the spec shou
On 18 March 2016 at 00:16, Jeremy Stanley wrote:
> On 2016-03-17 09:44:59 +0530 (+0530), Armando M. wrote:
> > Unfortunately, Neutron is also going to need an RC2 due to
> > upstream CI issues triggered by infra change [1] that merged right
> > about the same time RC1 was being cut.
>
> Do you ha
Excerpts from Csaba Henk's message of 2016-03-16 15:02:40 +0100:
> Hi,
>
> I'm asking for a Feature Free Exception for the update_access code for
> Ganesha library and the two GlusterFS drivers (glusterfs, glusterfs-native).
>
> This benefits the whole project in terms of getting closer to the po
+1
From: Dave Walker mailto:em...@daviey.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Sunday, March 20, 2016 at 12:27 PM
To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [stable] Proposing Tony Breeds for
stable-maint-
On Fri, 18 Mar 2016, Anita Kuno wrote:
On 03/16/2016 10:45 AM, Paul Belanger wrote:
I would like to see it added to openstack-infra so we can properly
manage it.
I agree with Paul here.
purpler (which includes the bot) is now packaged and on pypi:
https://pypi.python.org/pypi/purpler
I
On 16/03/2016 04:47, Tony Breeds wrote:
> On Tue, Mar 15, 2016 at 09:41:41PM +, Hayes, Graham wrote:
>> I do not see the time frame for defining an electorate there.
>>
>> PTL seats are completely renewed every 6 months. A separate election is
>> run for
>> each project team. These elections ar
This morning, Craig tagged RC1 on trove[1] and a short while ago I tagged RC1
on trove-dashboard[2]. The python-troveclient for Mitaka was tagged some days
ago[3].
At this point, changes merged into master will be headed for Newton.
Any changes that are required for Mitaka RC2 will have to be b
Also curious about this. It seems weird to separate the 'positive' and
the 'negative' ones, assuming those patches are mostly contributed by
the same group of developers.
Yeah, agree. This approach leads to situation when I need to look at two
places to observe test coverage for each component.
Hi, everyone,
we'd like to announce Packaging CI for Fuel.
For now there are no extended tests, just package builds.
Package-based test will be added later in Newton development cycle.
Current workflow:
* for every request we build a package and publish it to temporary
repository, which you can
Hello everyone,
The Telemetry team's release candidate for Ceilometer for the end
of the Mitaka cycle is available! You can find the RC1 source code
tarball at:
https://tarballs.openstack.org/ceilometer/ceilometer-6.0.0.0rc1.tar.gz
Unless release-critical issues are found that warrant a release
Hello everyone,
The Telemetry team's release candidate for Aodh for the end
of the Mitaka cycle is available! You can find the RC1 source code
tarball at:
https://tarballs.openstack.org/aodh/aodh-2.0.0.0rc1.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin,
Hello everyone,
The release candidate for Manila for the end of the Mitaka cycle
is available! You can find the RC1 source code tarball at:
https://tarballs.openstack.org/manila/manila-2.0.0.0rc1.tar.gz
Unless release-critical issues are found that warrant a release
candidate respin, this RC1 w
The following proposed API guidelines are available for broader
review by interested parties.
* https://review.openstack.org/#/c/281511/
Delete multiple metadata items with a single request
* https://review.openstack.org/#/c/260292/
Add unexpected attribute guideline
* https://review.opens
Lingxian Kong wrote:
Kanthi, sorry for chiming in, I suggest you may have a chance to take
a look at Mistral[1], which is the workflow as a service in
OpenStack(or without OpenStack).
Out of curiosity, why? Seems the ML post was about 'TaskFlow
persistence' not mistral, just saying (unsure how
I won't be able to make the TC meeting this week because of travel,
so I wanted to lay out my thoughts on the three PTL-less projects
based on the outcome of the recent election (EC2-API, Winstackers,
and Stable Maintenance).
The EC2-API project doesn't appear to be very actively worked on.
There
On 03/19/2016 11:33 PM, Joshua Harlow wrote:
Howday all,
Just to start some conversation for the next cycle,
I wanted to start thinking about what folks may like to see in oslo
(or yes, even what u dislike in any of the oslo libraries).
For those who don't know, oslo[1] is a lot of libraries
Ihar Hrachyshka wrote:
>
> One thing that we discussed on the event is updating networking-guide with
> detailed description of the upgrade process for neutron. We already have
> some pieces scattered there [f.e. we have some coverage for
> neutron-db-manage tool] but it’s nothing complete or deep
On Fri, Mar 18, 2016 at 07:01:34PM +0100, Markus Zoeller wrote:
> Kashyap Chamarthy wrote on 03/18/2016 07:28:09 AM:
[...]
> > Writing a thoughtful report is hard and time-taking.
>
> Yeah, and I assume that's the reason many bug reports lack that
> information. I have the hope to dig deeper in
I'd like to propose that we add Emilien Macchi to the TripleO core
review team. Emilien has been getting more involved with TripleO during
this last release. In addition to help with various Puppet things he
also has experience in building OpenStack installation tooling,
upgrades, and would be a va
I'd like to propose that we add John Trowbridge to the TripleO core
review team. John has become one of the goto guys in helping to chase
down upstream trunk chasing issues. He has contributed a lot to helping
keep general CI issues running and been involved with several new
features over the past
Doug,
Given that the EC2 functionality is currently in use by at least 1/6th of
production clouds
(https://www.openstack.org/assets/survey/Public-User-Survey-Report.pdf page
34), this is a worrying situation.
The EC2 functionality was recently deprecated from Nova on the grounds that the
EC2
On 03/20/2016 02:22 PM, Dan Prince wrote:
I'd like to propose that we add Emilien Macchi to the TripleO core
review team. Emilien has been getting more involved with TripleO during
this last release. In addition to help with various Puppet things he
also has experience in building OpenStack insta
+1
On Sunday, March 20, 2016, Dan Prince wrote:
> I'd like to propose that we add Emilien Macchi to the TripleO core
> review team. Emilien has been getting more involved with TripleO during
> this last release. In addition to help with various Puppet things he
> also has experience in building
Unfortunately none of this discussion solves the substantive issue which is
that we cannot release an xstatic package without breaking the gate.
We currently have one solution that's a close to viable as we've been able
to get: move the version pinning for xstatic packages out of
upper-constraints
+1
On 20 Mar 2016 20:27, "Dan Prince" wrote:
> I'd like to propose that we add Emilien Macchi to the TripleO core
> review team. Emilien has been getting more involved with TripleO during
> this last release. In addition to help with various Puppet things he
> also has experience in building Open
On Sun, Mar 20, 2016 at 1:26 PM, Richard Jones wrote:
> Unfortunately none of this discussion solves the substantive issue which is
> that we cannot release an xstatic package without breaking the gate.
>
> We currently have one solution that's a close to viable as we've been able
> to get: move t
On 03/20/2016 10:00 AM, Adam Young wrote:
I started with a blog post here:
http://adam.younglogic.com/2016/03/what-can-talk-to-what-on-the-openstack-message-broker/
and did a brief spike here:
http://adam.younglogic.com/2016/03/tie-your-rabbit-down/
We made the mistake of pursuing HMAC back
Thanks for your inputs. It sounds like we have no other option besides Barbican
as long as we need to store credentials in Magnum. Then I have a new proposal:
switch to an alternative authentication mechanism that doesn't require to store
credentials in Magnum. For example, the following options
The Magnum team discussed Anchor several times (in the design summit/midcycle).
According to what I remembered, the conclusion is to leverage Anchor though
Barbican (presumably there is an Anchor backend for Barbican). Is Anchor
support in Barbican still in the roadmap?
Best regards,
Hongbin
>
Hello,
First of all, let me apologize for answering on Alex Levine's behalf, but
it's late night/early morning in Moscow, so I'm taking the liberty.
Second, Alex Levine was recently made PTL of the EC2-API project when it was
formally accepted as an official project, but failed to unders
> The EC2-API project doesn't appear to be very actively worked on.
> There is one very recent commit from an Oslo team member, another
> couple from a few days before, and then the next one is almost a
> month old. Given the lack of activity, if no team member has
> volunteered to be PTL I think w
+1
Original message
From: Dan Prince
Date: 03/20/2016 12:23 PM (GMT-07:00)
To: openstack-dev
Subject: [openstack-dev] [TripleO] propose EmilienM for core
I'd like to propose that we add Emilien Macchi to the TripleO core
review team. Emilien has been getting more i
- Original Message -
> On 03/19/2016 01:43 AM, Tony Breeds wrote:
> > On Sun, Mar 13, 2016 at 12:15:23PM +, Amrith Kumar wrote:
> >> Hi,
> >>
> >> Sorry for the blast mail, this is targeted at the stable-maint team. The
> >> following five changes are now ready to merge. Two of them are
On Sun, Mar 20, 2016 at 08:00:07PM -0400, Luigi Toscano wrote:
> No one said that there will be other backports, at this time. It would have
> made sense if the reviews would have been merged when they have been
> proposed. It would be nice thought to backports one or two other patches for
> the i
Hi,
as discussed in the last (two) Sahara meetings, I'm working on moving the
Tempest API tests from the Tempest repository to the new sahara-tests
repository, which contains only (non-tempest) scenario tests and it's
branchless as well.
The move is a natural consequence of the Tempest focus on
On Sun, Mar 20, 2016 at 12:48:43PM -0400, Doug Hellmann wrote:
> I won't be able to make the TC meeting this week because of travel,
> so I wanted to lay out my thoughts on the three PTL-less projects
> based on the outcome of the recent election (EC2-API, Winstackers,
> and Stable Maintenance).
>
On Sun, Mar 20, 2016 at 04:14:02PM -0700, Dan Smith wrote:
> > The EC2-API project doesn't appear to be very actively worked on.
> > There is one very recent commit from an Oslo team member, another
> > couple from a few days before, and then the next one is almost a
> > month old. Given the lack o
> Just clarifying:
> For Nova: Yes. Matt's the only candidate I think that's a preety save
> assumption.
Sorry, I meant for Nova.
I guess since the nomination period is over (right), I'm not sure how
it's not more than an assumption...but okay :)
--Dan
hi, guys.
I received Visa Invitation Letter a few days ago. But the letter doesn't
contain attachment. What should I do?
Thanks
Zhi Chang__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: op
We are content to announce the release of:
glance_store 0.9.2: OpenStack Image Service Store Library
This release is part of the liberty stable release series.
With source available at:
http://git.openstack.org/cgit/openstack/glance_store
With package available at:
https://pypi.python
For sure.
Regards,
Daneyon
On Mar 19, 2016, at 1:52 PM, Steven Dake (stdake)
mailto:std...@cisco.com>> wrote:
Thanks - although it wasn't me that made it happen, it was the team.
Regards,
-steve
From: "Daneyon Hansen (danehans)"
mailto:daneh...@cisco.com>>
Reply-To: "OpenStack Development
On 12:50 Mar 21, Tony Breeds wrote:
> On Sun, Mar 20, 2016 at 12:48:43PM -0400, Doug Hellmann wrote:
> > I won't be able to make the TC meeting this week because of travel,
> > so I wanted to lay out my thoughts on the three PTL-less projects
> > based on the outcome of the recent election (EC2-API
As I didn't get any volunteers [1] to run the irc meeting I'm cancelling it
for this week. We will resume the week after on Mar 29th, 2016.
Hope this will give an hour back to the community towards their time to
wrap up last minute Mitaka targets. Please keep you response times tight
for those rev
> On Mar 18, 2016, at 4:01 AM, Ihar Hrachyshka wrote:
>
> Hi all,
>
> Just giving my fellows an update from the event where we gathered our
> upgrades subteam to plan for Newton and do some coding.
>
> ==
>
> We had folks from multiple companies participating in the event (Red Hat,
> SuSE,
Hi everybody,
My name is Alex Levine and I'm the current PTL of EC2 project.
Apparently I have to apologize for everybody because being in this role
for just less than a month I didn't expect I have to go through
elections for the newborn project so I haven't even looked at this side.
When I'd
Hi,
Wrote a Tempest test to check force_delete_backup method [1].
Check the tempest test run was successful see [2]
However jenkins fails with below trace back
Captured traceback:
2016-03-18 09:14:16.884 | ~~~
2016-03-18 09:14:16.884 | Traceback (most recent call last):
2
On 20/03/16 20:22, Dan Prince wrote:
> I'd like to propose that we add Emilien Macchi to the TripleO core
> review team. Emilien has been getting more involved with TripleO during
> this last release. In addition to help with various Puppet things he
> also has experience in building OpenStack inst
On 20/03/16 20:32, Dan Prince wrote:
> I'd like to propose that we add John Trowbridge to the TripleO core
> review team. John has become one of the goto guys in helping to chase
> down upstream trunk chasing issues. He has contributed a lot to helping
> keep general CI issues running and been invo
58 matches
Mail list logo
