Hi,
I would like to deploy a small overcloud with just one controller and one
compute for testing.
I want to use swift as the glance backend.
How do I configure the overcloud templates?
Samuel
__
OpenStack Development
?Jeffrey,
Thanks for your excellent service as Kolla PTL. You have served the Kolla
community well.
Regards,
-steve
From: Jeffrey Zhang
Sent: Tuesday, July 24, 2018 8:48 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [kolla] ptl non
Hello everyone,
I'd like to announce my candidacy for the Senlin PTL position during
the Stein cycle.
I've been contributing to Senlin since the Queens cycle and became a
core reviewer during the Rocky cycle. I work for Blizzard
Entertainment where I'm an active operator and upstream developer
Hello Sam,
Thanks for the clarifications.
On 07/25/2018 07:46 PM, Sam Doran wrote:
> I spoke with other Ansible Core devs to get some clarity on this change.
>
> This is not a change that is being made quickly, lightly, or without a
> whole of bunch of reservation. In fact, that PR created by
+1 :).
On 07/25/2018 02:03 PM, Juan Antonio Osorio wrote:
> Hello folks!
>
> I'd like to nominate myself for the TripleO PTL role for the Stein cycle.
>
> Alex has done a great job as a PTL: The project is progressing nicely
> with many
> new, exciting features and uses for TripleO coming to
I'd like to request a FFE for this blueprint[1].
Theremaining changes will be tracked as Depends-On on this oooq change[2].
Initially the aim of this blueprint was to do all container prepare
operations in a mistral action before the overcloud deploy. However the
priority for delivery
On Wed, Jul 25, 2018 at 3:50 PM, Steve Baker wrote:
> I'd like to request a FFE for this blueprint[1].
>
> The remaining changes will be tracked as Depends-On on this oooq change[2].
>
> Initially the aim of this blueprint was to do all container prepare
> operations in a mistral action before
On Wed, 25 Jul 2018 23:53:18 +0900 Surya Seetharaman
wrote
> Hi!
> On Wed, Jul 25, 2018 at 11:53 AM, Ghanshyam Mann
> wrote:
>
> 5. API Extensions merge work
> - https://blueprints.launchpad.net/nova/+spec/api-extensions-merge-rocky
> -
>
Octavia is done. Thank you for the patch!
Michael
On Tue, Jul 24, 2018 at 8:35 AM Hongbin Lu wrote:
>
> Hi folks,
>
>
>
> Neutron has landed a patch to enable strict validation on query parameters
> when listing resources [1]. I tested the Neutorn’s change in your project’s
> gate and the
2018-07-25 17:44 GMT+08:00 Ghanshyam Mann :
> Hi All,
>
> During today API office hour, we were discussing about keypair quota usage
> bug (newton) [1]. key_pair 'in_use' quota is always 0 even when request per
> user which is because it is being set as 0 always [2].
>
> From checking the history
2018-07-26 0:29 GMT+08:00 William M Edmonds :
>
> Ghanshyam Mann wrote on 07/25/2018 05:44:46 AM:
> ... snip ...
> > 1. is it ok to show the keypair used info via API ? any original
> > rational not to do so or it was just like that from starting.
>
> keypairs aren't tied to a tenant/project, so
2018-07-26 1:43 GMT+08:00 Chris Friesen :
> On 07/25/2018 10:29 AM, William M Edmonds wrote:
>
>>
>> Ghanshyam Mann wrote on 07/25/2018 05:44:46 AM:
>> ... snip ...
>> > 1. is it ok to show the keypair used info via API ? any original
>> > rational not to do so or it was just like that from
Indeed. Thanks Alex for your great leadership of TripleO.
From: Remo Mattei [mailto:r...@rm.ht]
Sent: Wednesday, July 25, 2018 4:09 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tripleo] PTL non-candidacy
I want publically want to say THANK
On Wed, 25 Jul 2018 22:22:24 +0900 Matt Riedemann
wrote
> On 7/25/2018 1:46 AM, Ghanshyam Mann wrote:
> > yeah, there are many tests taking too long time. I do not know the reason
> > this time but last time we did audit for slow tests was mainly due to ssh
> > failure.
> >
On Wed, 25 Jul 2018 05:15:53 +0900 Matt Riedemann
wrote
> While going through our uncategorized gate failures [1] I found that we
> have a lot of jobs failing (161 in 7 days) due to the tempest run timing
> out [2]. I originally thought it was just the networking scenario tests,
Hello everyone,
If you were not at the previous OpenStack-Ansible meeting*, I'd like to inform
you I will not be running for PTL of OSA.
It's been a pleasure being the PTL of OSA for the last 2 cycles.
We have improved in many ways: testing, stability, speed, features,
documentation, user
On Wednesday, July 25, 2018 08:46 CEST, Ghanshyam Mann
wrote:
> On Wed, 25 Jul 2018 05:15:53 +0900 Matt Riedemann
> wrote
> > While going through our uncategorized gate failures [1] I found that we
> > have a lot of jobs failing (161 in 7 days) due to the tempest run timing
[posted & mailed] https://review.openstack.org/#/c/585663/
This is my announcement for re-candidacy as I18n PTL in Stein Cycle.
At first a quick review what we've done in the last cycle:
1. Zanata upgrade done. As one of the first community's we're running
Zanata Release 4 in production. A big
Hi All,
During today API office hour, we were discussing about keypair quota usage bug
(newton) [1]. key_pair 'in_use' quota is always 0 even when request per user
which is because it is being set as 0 always [2].
From checking the history and review discussion on [3], it seems that it was
Hello folks,
I have filed a bug in os-vif:
https://bugs.launchpad.net/os-vif/+bug/1778724 and
working on a patch. Any feedback/comments from you guys would be extremely
helpful.
Bug details:
OVS DB server has the feature of listening over a TCP socket for
connections rather than just on the
Hi All,
Please find the Nova API highlights of this week.
Weekly Office Hour:
===
What we discussed this week:
- Discussion on priority BP and remaining reviews on those.
- Discussed keypair quota usage bug.
Planned Features :
==
Below are the API related
Thanks for your work as PTL during the Rocky cycle Jeffrey. Hope you are
able to stay part of the community.
Cheers,
Mark
On 25 July 2018 at 04:48, Jeffrey Zhang wrote:
> Hi all,
>
> I just wanna to say I am not running PTL for Stein cycle. I have been
> involved in Kolla project for almost 3
On Wed, Jul 25, 2018 at 03:22:27PM +0530, pranab boruah wrote:
> Hello folks,
>
> I have filed a bug in os-vif:
> https://bugs.launchpad.net/os-vif/+bug/1778724 and
> working on a patch. Any feedback/comments from you guys would be extremely
> helpful.
>
> Bug details:
>
> OVS DB server has the
Hi Team,
For those of you who has been around since the "Nomad" time, you know how a
terrific journey we have come along together. A pure idea, through
community discussion and development, morphed into a project who is rapidly
growing and gaining industry attentions.
It is my privilege to serve
Hello folks!
I'd like to nominate myself for the TripleO PTL role for the Stein cycle.
Alex has done a great job as a PTL: The project is progressing nicely with
many
new, exciting features and uses for TripleO coming to fruition recently.
It's a
great time for the project. But, there's more
Hello Stackers,
Would just like to give a heads-up that the puppet-openstack project as
of the Rocky release will supports
Ubuntu 18.04 Bionic and we are as of yesterday/today checking that in
infra Zuul CI.
As a step for adding this support we also introduced support for the
Ceph Mimic release
__
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
On 7/25/2018 1:46 AM, Ghanshyam Mann wrote:
yeah, there are many tests taking too long time. I do not know the reason this
time but last time we did audit for slow tests was mainly due to ssh failure.
I have created the similar ethercalc [3] to collect time taking tests and then
round figure
Hey folks,
So it's been great fun and we've accomplished much over the last two
cycles but I believe it is time for me to step back and let someone
else do the PTLing. I'm not going anywhere so I'll still be around to
focus on the simplification and improvements that TripleO needs going
forward.
On Jun 6, 2018, at 7:35 PM, Gilles Dubreuil wrote:
>
> The branch is now available under feature/graphql on the neutron core
> repository [1].
I wanted to follow up with you on this effort. I haven’t seen any activity on
StoryBoard for several weeks now, and wanted to be sure that there was
Hi!
On Wed, Jul 25, 2018 at 11:53 AM, Ghanshyam Mann
wrote:
>
> 5. API Extensions merge work
> - https://blueprints.launchpad.net/nova/+spec/api-extensions-merge-rocky
> - https://review.openstack.org/#/q/project:openstack/nova+
> branch:master+topic:bp/api-extensions-merge-rocky
> - Weekly
Hi Steve,
You were right, when I removed most of the roles it worked.
I've encountered another problem. It seems that the network-isolation.yaml
I used with OSP11 is pointing to files that do not exist anymore such as
* # Port assignments for the Controller role*
*
Hi All,
I'm trying to add Py3 packaging support for Ubuntu Rocky and while there
are a lot of issues involved with supporting Py3.7, this is one of the big
ones that I could use a hand with.
With py3.7, there's a deadlock when eventlet monkeypatch of stdlib thread
modules is combined with use of
Hi,
I'm trying to upgrade from OSP11(Ocata) to OSP13 (Queens)
In my network-isolation I refer to files that do not exist anymore on the
director such as
OS::TripleO::Compute::Ports::ExternalPort:
/usr/share/openstack-tripleo-heat-templates/network/ports/external.yaml
Hi All,
Trove currently has a really small team, and all the active team members
are from China, we had some good discussions during the Rocky online PTG
meetings[1], and the goals were arranged and priorited [2][3]. But it's sad
that none of us could focus on the project, and the number of
cc to the Trove team members and guys from Samsung R Center in Krakow,
Poland privately, so anyone of them who are not reading the ML could also
be notified.
On Thu, Jul 26, 2018 at 12:09 AM, 赵超 wrote:
> Hi All,
>
> Trove currently has a really small team, and all the active team members
> are
On 18-07-23 14:20:59, Sean McGinnis wrote:
> Just a quick reminder that this week is a big one for deadlines.
>
> This Thursday, July 26, is our scheduled deadline for feature freeze, soft
> string freeze, client library freeze, and requirements freeze.
>
> String freeze is necessary to give our
Ghanshyam Mann wrote on 07/25/2018 05:44:46 AM:
... snip ...
> 1. is it ok to show the keypair used info via API ? any original
> rational not to do so or it was just like that from starting.
keypairs aren't tied to a tenant/project, so how could nova track/report a
quota for them on a given
Jeffrey, Great work with great leadership for Rocky Cycle.
Hope to see you around always.
---spsurya
On Wed, Jul 25, 2018 at 9:19 AM Jeffrey Zhang
wrote:
> Hi all,
>
> I just wanna to say I am not running PTL for Stein cycle. I have been
> involved in Kolla project for almost 3 years. And
+1 for Juan,
> On Jul 25, 2018, at 5:03 AM, Juan Antonio Osorio wrote:
>
> Hello folks!
>
> I'd like to nominate myself for the TripleO PTL role for the Stein cycle.
>
> Alex has done a great job as a PTL: The project is progressing nicely with
> many
> new, exciting features and uses for
Have you tried the following instead of threadpoolexecutor (which
honestly should work as well, even under eventlet + eventlet patching).
https://docs.openstack.org/futurist/latest/reference/index.html#futurist.GreenThreadPoolExecutor
If you have the ability to specify which executor your code
+1
On Wed, Jul 25, 2018 at 8:04 AM Juan Antonio Osorio wrote:
>
> Hello folks!
>
> I'd like to nominate myself for the TripleO PTL role for the Stein cycle.
>
> Alex has done a great job as a PTL: The project is progressing nicely with
> many
> new, exciting features and uses for TripleO coming
On Wed, Jul 25, 2018 at 9:24 AM Alex Schultz wrote:
> Hey folks,
>
> So it's been great fun and we've accomplished much over the last two
> cycles but I believe it is time for me to step back and let someone
> else do the PTLing. I'm not going anywhere so I'll still be around to
> focus on the
Josh,
Thanks for the input. GreenThreadPoolExecutor does not have the deadlock
issue, so that is promising (at least with futurist 1.6.0).
Does ThreadPoolExecutor have better performance than
GreenThreadPoolExecutor? Curious if we could just swap out
ThreadPoolExecutor for
On 25/07/2018 15:23, Alex Schultz wrote:
> Hey folks,
> So it's been great fun and we've accomplished much over the last two
> cycles but I believe it is time for me to step back and let someone
> else do the PTLing. I'm not going anywhere so I'll still be around to
> focus on the simplification
On Wed, Jul 25, 2018 at 1:38 PM Raoul Scarazzini wrote:
>
> On 25/07/2018 15:23, Alex Schultz wrote:
> > Hey folks,
> > So it's been great fun and we've accomplished much over the last two
> > cycles but I believe it is time for me to step back and let someone
> > else do the PTLing. I'm not
On 07/25/2018 10:29 AM, William M Edmonds wrote:
Ghanshyam Mann wrote on 07/25/2018 05:44:46 AM:
... snip ...
> 1. is it ok to show the keypair used info via API ? any original
> rational not to do so or it was just like that from starting.
keypairs aren't tied to a tenant/project, so how
I spoke with other Ansible Core devs to get some clarity on this change.
This is not a change that is being made quickly, lightly, or without a whole of
bunch of reservation. In fact, that PR created by agaffney may not be merged
any time soon. He just wanted to get something started and there
I don't do enough in TripleO to chime in on the list, but I can't
think of a more helpful PTL!
Thank you for your service.
On 25/07/18 10:31 -0700, Wesley Hayutin wrote:
On Wed, Jul 25, 2018 at 9:24 AM Alex Schultz wrote:
Hey folks,
So it's been great fun and we've accomplished much over
So the only diff is that GreenThreadPoolExecutor was customized to work
for eventlet (with a similar/same api as ThreadPoolExecutor); as for
performance I would expect (under eventlet) that GreenThreadPoolExecutor
would have better performance because it can use the native eventlet
green
Ok thanks again for the input.
Corey
On Wed, Jul 25, 2018 at 2:15 PM, Joshua Harlow
wrote:
> So the only diff is that GreenThreadPoolExecutor was customized to work
> for eventlet (with a similar/same api as ThreadPoolExecutor); as for
> performance I would expect (under eventlet) that
Hi,
This came up recently on my review to add an environment to enable
Designate in a TripleO deployment. It needs to set both resource
registry entries and some user-configurable parameters, which means
users need to make a copy of it that they can edit. However, if the
file moves then
Dear Neutron Team,
Tomorrow's L3 sub team meeting will be canceled. We will resume next week,
on August 2nd, at 1500 UTC as normal
Best regards
Miguel
__
OpenStack Development Mailing List (not for usage questions)
Hi everyone:
This email is just to notify everyone on the TC and the community that
the change to remove the stable branch maintenance as a project
team[1] has been fast-tracked[2].
The change should be approved on 2018-07-28 however it is beneficial
to remove the stable branch team (which has
This is the weekly summary of work being done by the Technical
Committee members. The full list of active items is managed in the
wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
Doug (who usually sends these out!) is out so we've come up with
the idea of a vice-chair, which I'll
On Wed, Jul 25, 2018 at 11:56 AM, Samuel Monderer
wrote:
> Hi,
>
> I'm trying to upgrade from OSP11(Ocata) to OSP13 (Queens)
> In my network-isolation I refer to files that do not exist anymore on the
> director such as
>
> OS::TripleO::Compute::Ports::ExternalPort:
>
I want publically want to say THANK YOU Alex. You ROCK.
Hopefully one of those summit, I will meet.
Ciao,
Remo
> On Jul 25, 2018, at 6:23 AM, Alex Schultz wrote:
>
> Hey folks,
>
> So it's been great fun and we've accomplished much over the last two
> cycles but I believe it is time for
Hello everyone!
I would like to submit my name to continue as the release management PTL for
the Stein release.
Since I failed to recruit someone new to take over for me, I guess I'm still
it.
But being serious, I think I've now gotten a much deeper understanding of our
release tools and
I would like to announce my candidacy for PTL of the Requirements project for
the Stein cycle.
The following will be my goals for the cycle, in order of importance:
1. The primary goal is to keep a tight rein on global-requirements and
upper-constraints updates. (Keep things working well)
2.
59 matches
Mail list logo
