Thank you to the electorate, to all those who voted and to all
candidates who put their name forward for Project Team Lead (PTL) in
this election. A healthy, open process breeds trust in our decision
making capability thank you to all those who make this process
possible.
Now for the results of
Please join me in congratulating the 4 newly elected members of the
Technical Committe (TC).
Dan Smith (dansmith)
Jens Harbott (frickler)
Ghanshyam Mann (gmann)
Jay Faulkner (JayF)
Full results: https://civs1.civs.us/cgi-bin/results.pl?id=E_36ebf2eba022aded
Election process details and results
Hi everybody!
As the subject reads, the "T" release of OpenStack is officially
"Train". Unlike recent choices Train was the popular choice so
congrats!
Thanks to everybody who participated and help with the naming process.
Lets make OpenStack Train the release so awesome that people can't
Hi everybody!
As the subject reads, the "T" release of OpenStack is officially
"Train". Unlike recent choices Train was the popular choice so
congrats!
Thanks to everybody who participated and help with the naming process.
Lets make OpenStack Train the release so awesome that people can't
Hi everybody!
As the subject reads, the "T" release of OpenStack is officially
"Train". Unlike recent choices Train was the popular choice so
congrats!
Thanks to everybody who participated and help with the naming process.
Lets make OpenStack Train the release so awesome that people can't
On Wed, Nov 07, 2018 at 08:35:02PM +0100, Luka Peschke wrote:
> Here's the patch: https://review.openstack.org/#/c/616205/. If it is not
> merged by Friday (date of the first meeting), I'll send the log of the first
> meeting to this ML.
Even if the above doesn't merge you can still use
Hello all!
The results of the naming poll are in!
**PLEASE REMEMBER** that these now have to go through legal vetting. So
it is too soon to say 'OpenStack Train' is our next release, given that
previous polls have had some issues with the top choice.
In any case, the names will be sent off
Hello all!
The results of the naming poll are in!
**PLEASE REMEMBER** that these now have to go through legal vetting. So
it is too soon to say 'OpenStack Train' is our next release, given that
previous polls have had some issues with the top choice.
In any case, the names will be sent off
Hello all!
The results of the naming poll are in!
**PLEASE REMEMBER** that these now have to go through legal vetting. So
it is too soon to say 'OpenStack Train' is our next release, given that
previous polls have had some issues with the top choice.
In any case, the names will be sent off
On Tue, Nov 06, 2018 at 06:07:18AM -0800, Julia Kreger wrote:
> I don't know how the cost structure works for Bluejeans, but I've found it
> works very well for calls with many people on video. I typically have calls
> with 14+ people nearly everyone has their video enabled without a problem.
Hi all,
Time is running out for you to have your say in the T release name
poll. We have just under 3 days left. If you haven't voted please do!
On Tue, Oct 30, 2018 at 04:40:25PM +1100, Tony Breeds wrote:
> Hi folks,
>
> It is time again to cast your vote for the naming of the
Hi all,
Time is running out for you to have your say in the T release name
poll. We have just under 3 days left. If you haven't voted please do!
On Tue, Oct 30, 2018 at 04:40:25PM +1100, Tony Breeds wrote:
> Hi folks,
>
> It is time again to cast your vote for the naming of the
Hi all,
Time is running out for you to have your say in the T release name
poll. We have just under 3 days left. If you haven't voted please do!
On Tue, Oct 30, 2018 at 04:40:25PM +1100, Tony Breeds wrote:
> Hi folks,
>
> It is time again to cast your vote for the naming of the
On Tue, Oct 30, 2018 at 11:25:02AM -0700, iain macdonnell wrote:
> I must be losing it. On what planet is "Tiny Town" a single word, and
> "Troublesome" not more than 10 characters?
Sorry for the mistake. Should either of these names win the popular
vote clearly they would not be viable.
Yours
On Tue, Oct 30, 2018 at 11:25:02AM -0700, iain macdonnell wrote:
> I must be losing it. On what planet is "Tiny Town" a single word, and
> "Troublesome" not more than 10 characters?
Sorry for the mistake. Should either of these names win the popular
vote clearly they would not be viable.
Yours
On Tue, Oct 30, 2018 at 11:25:02AM -0700, iain macdonnell wrote:
> I must be losing it. On what planet is "Tiny Town" a single word, and
> "Troublesome" not more than 10 characters?
Sorry for the mistake. Should either of these names win the popular
vote clearly they would not be viable.
Yours
Hi folks,
It is time again to cast your vote for the naming of the T Release.
As with last time we'll use a public polling option over per user private URLs
for voting. This means, everybody should proceed to use the following URL to
cast their vote:
Hi folks,
It is time again to cast your vote for the naming of the T Release.
As with last time we'll use a public polling option over per user private URLs
for voting. This means, everybody should proceed to use the following URL to
cast their vote:
Hi folks,
It is time again to cast your vote for the naming of the T Release.
As with last time we'll use a public polling option over per user private URLs
for voting. This means, everybody should proceed to use the following URL to
cast their vote:
On Wed, Oct 24, 2018 at 03:23:53AM +, z...@openstack.org wrote:
> Build failed.
>
> - release-openstack-python3
> http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/release/release-openstack-python3/e84da68/
> : POST_FAILURE in 2m 18s
So this failed because pypi thinks
On Mon, Oct 22, 2018 at 04:33:49PM +0200, Thomas Goirand wrote:
> One of the reoccurring problem that I'm facing in Debian is that not
> only Python 3 version is lagging behind, but OpenStack dependencies are
> also lagging behind the distro. Often, the answer is "we don't support
> this or that
On Thu, Oct 18, 2018 at 05:35:39PM +1100, Tony Breeds wrote:
> Hello all,
> As per [1] the nomination period for names for the T release have
> now closed (actually 3 days ago sorry). The nominated names and any
> qualifying remarks can be seen at2].
>
> Proposed N
On Thu, Oct 18, 2018 at 05:35:39PM +1100, Tony Breeds wrote:
> Hello all,
> As per [1] the nomination period for names for the T release have
> now closed (actually 3 days ago sorry). The nominated names and any
> qualifying remarks can be seen at2].
>
> Proposed N
Hello all,
As per [1] the nomination period for names for the T release have
now closed (actually 3 days ago sorry). The nominated names and any
qualifying remarks can be seen at2].
Proposed Names
* Tarryall
* Teakettle
* Teller
* Telluride
* Thomas
* Thornton
* Tiger
* Tincup
*
Hello all,
As per [1] the nomination period for names for the T release have
now closed (actually 3 days ago sorry). The nominated names and any
qualifying remarks can be seen at2].
Proposed Names
* Tarryall
* Teakettle
* Teller
* Telluride
* Thomas
* Thornton
* Tiger
* Tincup
*
On Tue, Oct 16, 2018 at 06:03:54PM +0530, ʂʍɒρƞįł Ҟưȴķɒʁʉɨ wrote:
> Dear OpenStackers,
>
> For a few months now, I am not able to contribute to code or reviewing
> Kolla and Requirements actively given my current responsibilities, I
> would like to take a step back and release my core reviewer
On Wed, Oct 17, 2018 at 04:18:26PM +0300, Ivan Kolodyazhny wrote:
> Hi all,
>
> We discussed this topic at PTG both with Horizon and other teams. Sounds
> like everybody is interested to have some cross-project CI jobs to verify
> that plugins are not broken with the latest Horizon changes.
>
>
On Sat, Sep 29, 2018 at 02:50:31PM +0200, Ildiko Vancsa wrote:
> Hi Training Team,
>
> Based on the votes on the Doodle poll below we will have our ad-hoc meeting
> __next Friday (October 5) 1600 UTC__.
>
> Hangouts link for the call:
> https://hangouts.google.com/call/BKnvu7e72uB_Z-QDHDF2AAEI
Hey everybody,
Once again, it is time for us to pick a name for our "T" release.
Since the associated Summit will be in Denver, the Geographic
Location has been chosen as "Colorado" (State).
Nominations are now open. Please add suitable names to
Hey everybody,
Once again, it is time for us to pick a name for our "T" release.
Since the associated Summit will be in Denver, the Geographic
Location has been chosen as "Colorado" (State).
Nominations are now open. Please add suitable names to
Hi All,
As Stable is no longer a project, I'm no longer a PTL so I don't
really need to do this but ...
I'm going on vacation for 3'ish weeks. I do plan on checking my email
from time-to-time but really if anything comes up that needs urgent
attention you'll need to ping stable-maint-core.
On Tue, Sep 11, 2018 at 10:20:52AM +, z...@openstack.org wrote:
> Build failed.
>
> - publish-openstack-releasenotes
> http://logs.openstack.org/6c/6ce2f5edd0b3dbb2c7edebca37ccc8219675e189/tag/publish-openstack-releasenotes/85bfc1a/
> : FAILURE in 4m 45s
> -
On Mon, Sep 10, 2018 at 05:58:21AM -0600, Doug Hellmann wrote:
> The python3 version of the job worked. I think both jobs ran because the
> repo is in the middle of its zuul settings transition and the cleanup
> patch hasn't merged yet. Since one of them worked, I think the published
> output
On Wed, Sep 05, 2018 at 10:03:09AM -0500, Matthew Thode wrote:
> The requirements team has gone ahead and made a aweful hack to get gate
> unwedged. The commit message is a very good summary of our reasoning
> why it has to be this way for now. My comment explains our plan going
> forward
On Tue, Sep 11, 2018 at 07:39:39AM +1000, Ian Wienand wrote:
> > On Mon, Sep 10, 2018 at 05:13:35AM +, z...@openstack.org wrote:
> >> Build failed.
> >>
> >> - publish-openstack-releasenotes
> >>
On Mon, Sep 10, 2018 at 08:40:28AM +0200, Julien Danjou wrote:
> On Mon, Sep 10 2018, Tony Breeds wrote:
>
> > It looks like in August this was already setup
> > https://review.openstack.org/#/c/591682/
> > So releases going forward will be on pypi.
> >
> &
On Mon, Sep 10, 2018 at 05:13:35AM +, z...@openstack.org wrote:
> Build failed.
>
> - publish-openstack-releasenotes
> http://logs.openstack.org/c8/c89ca61fdcaf603a10750b289228b7f9a3597290/tag/publish-openstack-releasenotes/fbbd0fa/
> : FAILURE in 4m 03s
I'm not sure what caused this to
On Mon, Sep 10, 2018 at 11:02:06AM +1000, Ian Wienand wrote:
> On 09/10/2018 09:39 AM, Tony Breeds wrote:
> > Julien, Do you mind me arranging for at least the following versions to
> > be published to pypi?
>
> For this particular case, I think our best approach is to hav
On Sat, Sep 08, 2018 at 03:21:38PM +1000, Tony Breeds wrote:
> On Fri, Sep 07, 2018 at 11:09:15AM +0200, Julien Danjou wrote:
>
> > You can, I've already said +1 on a review a few weeks ago. :)
>
> Oh great. I'll dig that up and push forward with that side of things i
On Fri, Sep 07, 2018 at 11:09:15AM +0200, Julien Danjou wrote:
> You can, I've already said +1 on a review a few weeks ago. :)
Oh great. I'll dig that up and push forward with that side of things if
you don't mind.
Yours Tony.
signature.asc
Description: PGP signature
On Thu, Sep 06, 2018 at 03:01:01PM -0500, Lance Bragstad wrote:
> I'm noticing some odd cases with respect to the python 3 community goal
> [0]. So far my findings are specific to keystone repositories, but I can
> imagine this affecting other projects.
>
> Doug generated the python 3 reviews for
On Wed, Sep 05, 2018 at 10:54:25AM +0100, Dougal Matthews wrote:
> On 5 September 2018 at 10:52, Dougal Matthews wrote:
>
> > (Note: I added [release] to the email subject, as I think that will make
> > it visible to the right folks.)
> >
>
> Darn. It should have been [stable]. I have added
On Thu, Sep 06, 2018 at 01:33:12PM +0300, Michel Peterson wrote:
> I remember that before landing the problematic patch [1] there was some
> discussion around it. Basically the problem was not n-odl but ceilometer
> not being in pypi, but we never foresaw this problem.
>
> Now that the problem
On Thu, Sep 06, 2018 at 09:24:39AM +1000, Tony Breeds wrote:
> Hi JP,
>I don't see a review in openstack/election from you. Are you able to
> upload one befoer the deadline?
>
> Please see:
> https://governance.openstack.org/election/#how-to-submit-a-candidacy
> for
Hi folks,
A quick reminder that we are in the last hours for TC
candidate announcements. Nominations are open until Sep 06, 2018 23:45
UTC.
If you want to stand for TC, don't delay, follow the
instructions at [1] to make sure the community knows your
intentions.
Make sure your nomination has
On Wed, Sep 05, 2018 at 01:04:09PM +0200, jean-phili...@evrard.me wrote:
> Hello everyone,
>
> I am hereby announcing my candidacy for a position on the OpenStack Technical
> Committee (TC).
Hi JP,
I don't see a review in openstack/election from you. Are you able to
upload one befoer the
On Fri, Aug 31, 2018 at 07:52:09PM -0500, Matthew Thode wrote:
> The requirements project has a co-installability test for the various
> projects, networking-odl being included.
>
> Because of the way the dependancy on ceilometer is done it is blocking
> all reviews and updates to the
On Thu, Aug 30, 2018 at 09:12:57PM +, Jeremy Stanley wrote:
> On 2018-08-31 01:13:58 +0800 (+0800), Rico Lin wrote:
> [...]
> > What needs to be done for this is full topic categories support
> > under `options` page so people get to filter emails properly.
> [...]
>
> Unfortunately, topic
Nominations for the Technical Committee positions (6 positions)
are now open and will remain open until Sep 06, 2018 23:45 UTC.
All nominations must be submitted as a text file to the
openstack/election repository as explained on the election website[1].
Please note that the name of the file
On Thu, Aug 30, 2018 at 09:12:57PM +, Jeremy Stanley wrote:
> On 2018-08-31 01:13:58 +0800 (+0800), Rico Lin wrote:
> [...]
> > What needs to be done for this is full topic categories support
> > under `options` page so people get to filter emails properly.
> [...]
>
> Unfortunately, topic
On Thu, Aug 30, 2018 at 09:12:57PM +, Jeremy Stanley wrote:
> On 2018-08-31 01:13:58 +0800 (+0800), Rico Lin wrote:
> [...]
> > What needs to be done for this is full topic categories support
> > under `options` page so people get to filter emails properly.
> [...]
>
> Unfortunately, topic
Thank you to the electorate, to all those who voted and to all
candidates who put their name forward for Project Team Lead (PTL) in
this election. A healthy, open process breeds trust in our decision
making capability thank you to all those who make this process possible.
Now for the results of
On Tue, Aug 28, 2018 at 03:26:02PM -0500, Matt Riedemann wrote:
> I hereby nominate Melanie Witt for nova stable core. Mel has shown that she
> knows the stable branch policy and is also an active reviewer of nova stable
> changes.
>
> +1/-1 comes from the stable-maint-core team [1] and then
Election details: https://governance.openstack.org/election/
Please read the stipulations and timelines for candidates and
electorate contained in this governance documentation.
There will be further announcements posted to the mailing list as
action is required from the electorate or
On Mon, Aug 20, 2018 at 10:23:07AM -0700, Kendall Nelson wrote:
> Hello Everyone,
>
> To avoid meeting conflicts with the Women of OpenStack, we will actually be
> doing meetings weekly on Mondays at 20:00 UTC on odd weeks.
>
> Long story short, our kickoff meeting after this luxurious summer
On Thu, Aug 16, 2018 at 10:45:32AM -0400, Doug Hellmann wrote:
> Is there any reason we can't uncap pbr, at least within the CI jobs?
It might work for the docs builds but jumping a major version of pbr,
which if I recall caused problems ate the time (hence the lower-bound)
for all octata
On Thu, Aug 16, 2018 at 06:27:39AM +0200, Andreas Jaeger wrote:
> Ocata should be retired by now ;) Let's drop it...
*cough* extended maintenance *cough* ;P
So we don't need the Ocata docs to be rebuilt with this version?
Yours Tony.
signature.asc
Description: PGP signature
On Wed, Aug 15, 2018 at 09:10:18AM -0400, Doug Hellmann wrote:
> Excerpts from Andreas Jaeger's message of 2018-08-15 09:28:51 +0200:
> > On 08/15/2018 07:25 AM, Tony Breeds wrote:
> > > On Tue, Aug 14, 2018 at 04:22:16PM -0400, Doug Hellmann wrote:
> >
On Wed, Aug 15, 2018 at 09:28:51AM +0200, Andreas Jaeger wrote:
> openstackdocsstheme has:
> sphinx!=1.6.6,!=1.6.7,>=1.6.2
>
> So, we cannot use it on branches that constraint sphinx to an older version,
>
> Sorry, can't check this right now from where I am,
Constraints
---
On Tue, Aug 14, 2018 at 04:22:16PM -0400, Doug Hellmann wrote:
> Now that https://review.openstack.org/#/c/591671/ has landed, we need
> someone to propose the backports of the constraint updates to all of the
> existing stable branches.
Done:
On Mon, Aug 13, 2018 at 04:10:30PM -0700, Eric K wrote:
> It appears that gabbi<1.42.1 is causing on error with heat tempest
> plugin in congress stable/queens dsvm job [1][2][3]. The issue was
> addressed in heat tempest plugin [4], but the problem remains for
> stable/queens jobs because the
On Tue, Aug 14, 2018 at 12:11:53AM -0500, Matthew Thode wrote:
> Maybe it'd be better to figure out what's using that removed method and
> those would need the update?
Given we have per-project deps in rocky only those that *need* the
exclusion will need to apply it.
I think it's fair to accept
On Thu, Aug 09, 2018 at 05:20:53PM -0400, Doug Hellmann wrote:
> Excerpts from Tony Breeds's message of 2018-08-08 14:39:30 +1000:
> > Hello all,
> > With the PTL elections behind us it's time to start looking at the
> > TC election. Our charter[1] says:
> >
> > The election is held no
Hello all,
With the PTL elections behind us it's time to start looking at the
TC election. Our charter[1] says:
The election is held no later than 6 weeks prior to each OpenStack
Summit (on or before ‘S-6’ week), with elections held open for no less
than four business days.
Assuming
Thank you to the electorate, to all those who voted and to all
candidates who put their name forward for Project Team Lead (PTL) in
this election. A healthy, open process breeds trust in our decision
making capability thank you to all those who make this process possible.
Now for the results of
On Tue, Aug 07, 2018 at 02:34:45PM +1000, Tony Breeds wrote:
> On Mon, Aug 06, 2018 at 07:27:37PM +0200, Andreas Jaeger wrote:
> > Tony,
> >
> > On 2018-07-19 06:59, Tony Breeds wrote:
> > > On Wed, Jul 18, 2018 at 08:08:16PM -0400, Emilien Macchi wrote:
&g
On Mon, Aug 06, 2018 at 07:27:37PM +0200, Andreas Jaeger wrote:
> Tony,
>
> On 2018-07-19 06:59, Tony Breeds wrote:
> > On Wed, Jul 18, 2018 at 08:08:16PM -0400, Emilien Macchi wrote:
> > > Option 2, EOL everything.
> > > Thanks a lot for your help on th
Hello Senlin and Tacker contributors,
Just a quick reminder that elections are closing soon, if you haven't
already you should use your right to vote and pick your favourite
candidate!
You have until Aug 07, 2018 23:45 UTC.
Thanks for your time!
Yours Tony.
signature.asc
Description: PGP
On Tue, Jul 31, 2018 at 06:39:36PM +0100, Graham Hayes wrote:
> Hi Stable Team,
>
> I would like to nominate 2 new stable core reviewers for Designate.
>
> * Erik Olof Gunnar Andersson
> * Jens Harbott (frickler)
>
> Erik has been doing a lot of stable reviews recently, and Jens has shown
>
On Wed, Aug 01, 2018 at 09:55:13AM +1000, Tony Breeds wrote:
>
> Hello all,
> The PTL Nomination period is now over. The official candidate list
> is available on the election website[0].
>
> There are 8 projects without candidates, so according to this
> resolution
Hi folks,
Polls for PTL elections are now open and will remain open for you to
cast your vote until Aug 07, 2018 23:45 UTC.
We are having elections for Senlin and Tacker.
If you are a Foundation individual member and had a commit in
one of the program's projects[0] over the Aug 11, 2017
Hello all,
The PTL Nomination period is now over. The official candidate list
is available on the election website[0].
There are 8 projects without candidates, so according to this
resolution[1], the TC will have to decide how the following
projects will proceed: Dragonflow, Freezer, Loci,
Hello all,
A quick reminder that we are in the last hours for PTL candidate
nominations.
If you want to stand for PTL, don't delay, follow the instructions
at [1] to make sure the community knows your intentions.
Make sure your nomination has been submitted to the openstack/election
repository
On Tue, Jul 17, 2018 at 01:52:39PM -0400, Doug Hellmann wrote:
> The Adjutant team's application [1] to become an official project
> has been approved. Welcome!
>
> As I said on the review, because it is past the deadline for Rocky
> membership, Adjutant will not be considered part of the Rocky
>
On Thu, Jul 26, 2018 at 10:54:52PM -0500, Matt Riedemann wrote:
> On 7/26/2018 4:37 PM, Sean McGinnis wrote:
> > I'd be curious to hear more about why you don't think that tag is
> > maintained.
>
> Are projects actively applying for the tag?
>
> >
> > For projects that assert they follow
On Thu, Jul 26, 2018 at 11:42:01AM -0500, Matt Riedemann wrote:
> On 7/25/2018 3:07 PM, Mohammed Naser wrote:
> > 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
On Fri, Jul 20, 2018 at 01:05:26PM +1000, Tony Breeds wrote:
>
> Hello folks,
> So really the subject says it all. I fell like at the time we
> created the Stable branch project team that was the only option. Since
> then we have crated the SIG structure and in my opinion
team and Opening the Extended Maintenance SIG
Reply-To:
Hello folks,
So really the subject says it all. I fell like at the time we
created the Stable branch project team that was the only option. Since
then we have crated the SIG structure and in my opinion that's a better
fit. We've also
On Wed, Jul 18, 2018 at 08:08:16PM -0400, Emilien Macchi wrote:
> Option 2, EOL everything.
> Thanks a lot for your help on this one, Tony.
No problem.
I've created:
https://review.openstack.org/583856
to tag final releases for tripleo deliverables and then mark them as
EOL.
Once that merges
Hi All,
As of I3671f10d5a2fef0e91510a40835de962637f16e5 we have meta-data in
openstack/releases that tells us that the following repos are at
newton-eol:
- openstack/instack-undercloud
- openstack/os-net-config
- openstack/puppet-tripleo
- openstack/tripleo-common
-
On Fri, Jul 13, 2018 at 10:12:04AM +1000, Tony Breeds wrote:
> On Wed, Jul 11, 2018 at 10:39:30AM -0600, Alex Schultz wrote:
> > Currently open with pending patches (may need FFE):
> > - https://blueprints.launchpad.net/tripleo/+spec/multiarch-support
>
> I'd like an F
On Wed, Jul 11, 2018 at 10:39:30AM -0600, Alex Schultz wrote:
> Currently open with pending patches (may need FFE):
> - https://blueprints.launchpad.net/tripleo/+spec/multiarch-support
I'd like an FFE for this, the open reviews are in pretty good shape and
mostly merged. (or +W'd).
We'll need
On Thu, Jul 12, 2018 at 11:31:34AM -0500, Monty Taylor wrote:
> there is also
>
> https://review.openstack.org/#/c/580730/
>
> which adds a role to install docker and configure it to use the correct
> registry.
shiny! That'll take care of all the docker setup nice!
Can I create a job
On Thu, Jul 12, 2018 at 11:05:09AM -0500, Matthew Thode wrote:
> I'm of the opinion that we should decouple from distro supported python
> versions and rely on what versions upstream python supports (longer
> lifetimes than our releases iirc).
Using docker/pyenv does this decoupling but I'm not
On Thu, Jul 12, 2018 at 11:31:34AM -0500, Monty Taylor wrote:
> FWIW, I use pyenv for python versions on my laptop and love it. I've
> completely given up on distro-provided python for my own usage.
Hmm okay I'll look at that and how it'd play with the generate job.
It's quite possible I'm
On Thu, Jul 12, 2018 at 01:52:56PM +, Jeremy Stanley wrote:
> On 2018-07-12 06:37:52 -0700 (-0700), Clark Boylan wrote:
> [...]
> > I think most of the problems with Fedora stability are around
> > bringing up a new Fedora every 6 months or so. They tend to change
> > sufficiently within that
On Thu, Jul 12, 2018 at 06:37:52AM -0700, Clark Boylan wrote:
> On Wed, Jul 11, 2018, at 9:34 PM, Tony Breeds wrote:
> > 1. Build pythons from source and use that to construct the venv
> >[please no]
>
> Fungi mentions that 3.3 and 3.4 don't build easily on modern linu
On Thu, Jul 12, 2018 at 03:53:22PM +0900, Takashi Yamamoto wrote:
> hi,
>
> queens branch of networking-midonet has had no changes merged since
> its creation.
> the following commit would tell you how many gate blockers have been
> accumulated.
> https://review.openstack.org/#/c/572242/
>
> it
Hi all,
The requirements team is only a light user of Launchpad and we're
looking at moving to StoryBoard as it looks like for the most part it'll
be a better fit.
To date the thing that has stopped us doing this is the handling of
bugs/stories that are shared between LP and SB.
Assume that
Hi Folks,
We have a pit of a problem in openstack/requirements and I'd liek to
chat about it.
Currently when we generate constraints we create a venv for each
(system) python supplied on the command line, install all of
global-requirements into that venv and capture the pip freeze.
Where
On Mon, Jul 09, 2018 at 04:38:47PM +0900, Xinni Ge wrote:
> Hello openstack-infra team,
>
> I uploaded a patch to add a new release of xstatic-angular-material, and
> thanks for your work it was merged several days ago.
> Here is the link of the patch.
> https://review.openstack.org/#/c/577018/
>
On Tue, Jul 03, 2018 at 06:12:21AM +0200, Ignazio Cassano wrote:
> Hi Tony, I sent log file and script yesterday. I hope you received them.
Sorry I can't find them in any of my inboxes :(
Yours Tony.
signature.asc
Description: PGP signature
___
On Mon, Jul 02, 2018 at 08:13:39AM +0200, Ignazio Cassano wrote:
> Tony, do you mean the script I am using to create the image ?
Yup, it'd be good to try and reproduce this outside your environment as
that'll make fixing the underlying bug quicker.
Yours Tony.
signature.asc
Description: PGP
On Mon, Jul 02, 2018 at 07:55:13AM +0200, Ignazio Cassano wrote:
> Hi Tony,
> applying the patch reported here (https://review.openstack.org/#/c/561740/)
> the issue is solved..
> The above path was related to another issue (distutils) but is solves also
> the cleanup error.
> Anycase I could
On Sun, Jul 01, 2018 at 12:25:24PM +0200, Ignazio Cassano wrote:
> Hi All,
> I just installed disk-image builder on my centos 7.
> For creating centos7 image I am using the same command used 3 o 4 months
> ago, but wiith the last diskimage-builder installed with pip I got the
> following error:
>
On Tue, Jun 26, 2018 at 09:03:40AM -0400, Doug Hellmann wrote:
> Requirements team,
>
> At some point in the next few months we're going to want to raise
> the constraint on openstackdocstheme in all of the old branches so
> we can take advantage of a new feature for showing the supported
>
On Mon, Jun 25, 2018 at 05:42:00PM -0500, Lance Bragstad wrote:
> Keystone is hitting this, too [0]. I attempted the same solution that
> Tony posted, but no luck. I've even gone so far as removing every
> comment from the module to see if that helps narrow down the problem
> area, but sphinx
On Mon, Jun 18, 2018 at 12:03:52PM +1000, Tony Breeds wrote:
> Without strong objections I'll do that on (my) Monday 25th June.
Done.
Yours Tony.
signature.asc
Description: PGP signature
__
OpenStack Development Mail
On Wed, Jun 20, 2018 at 08:54:56PM +0900, Takashi Yamamoto wrote:
> do you have a plan to submit these changes on gerrit?
I didn't but I have now:
* https://review.openstack.org/577028
* https://review.openstack.org/577029
Feel free to edit/test as you like.
Yours Tony.
signature.asc
Hello folks,
Recently Ivan became the Horizon PTL and as with past PTLs (Hi Rob)
isn't a member of the horizon-stable-maint team. Ivan is a member of
the Cinder stable team and as such has demonstrated an understanding of
the stable policy. Since the Dublin PTG Ivan has been doing consistent
1 - 100 of 717 matches
Mail list logo
