Wesley,
For Ubuntu I suggest to enable 'proposed' repo to catch the problem
before package will be moved to 'updates'.
On Mon, May 14, 2018 at 11:42 PM, Wesley Hayutin wrote:
>
>
> On Sun, May 13, 2018 at 11:50 PM Tristan Cacqueray
> wrote:
>>
>> On May 14, 2018 2:44 am, Wesley Hayutin wrote:
>
Doug Hellmann wrote:
There is a patch to update the Python 3.5 goal for Kolla [1]. While
I'm glad to see the work happening, the change adds a new deliverable
to an old goal, and it isn’t clear whether we want to use that
approach for tracking goal work indefinitely. I see a few options.
1. We c
Doug Hellmann wrote:
We will also hold a retrospective for the TC as a team on Monday
at the Forum. Please be prepared to discuss things you think are
going well, things you think we need to change, items from our
backlog that you would like to work on, etc. [10]
[10]
https://www.openstack.org
On 5/14/18 9:15 PM, Sagi Shnaidman wrote:
Hi, Bogdan
I like the idea with undercloud job. Actually if undercloud fails, I'd
stop all other jobs, because it doens't make sense to run them. Seeing
the same failure in 10 jobs doesn't add too much. So maybe adding
undercloud job as dependency for
On 5/14/18 10:06 PM, Alex Schultz wrote:
On Mon, May 14, 2018 at 10:15 AM, Bogdan Dobrelya wrote:
An update for your review please folks
Bogdan Dobrelya writes:
Hello.
As Zuul documentation [0] explains, the names "check", "gate", and
"post" may be altered for more advanced pipelines. Is
On 05/14/2018 03:30 PM, Akihiro Motoki wrote:
> Is Python 3 ever used for mod_wsgi? Does the WSGI setup code honor
> the variable that tells devstack to use Python 3?
>
>
> Ubuntu 16.04 provides py2 and py3 versions of mod_wsgi (libapache2-mod-wsgi
> and libapache2-mod-wsgi-py3) and as a
Added a few more patches [0], [1] by the discussion results. PTAL folks.
Wrt remaining in the topic, I'd propose to give it a try and revert it,
if it proved to be worse than better.
Thank you for feedback!
The next step could be reusing artifacts, like DLRN repos and containers
built for patc
I imagine most people have been seeing warnings like the one below
raised by various openstack packages recently:
.tox/py27/lib/python2.7/site-packages/psycopg2/__init__.py:144: UserWarning:
The psycopg2
wheel package will be renamed from release 2.8; in order to keep installing
from binary
Hi,
I created etherpads for Vitrage forum sessions:
- Advanced RCA use cases - taking Vitrage to the next level:
https://etherpad.openstack.org/p/YVR-vitrage-advanced-use-cases
- Vitrage RCA over K8s. Pets and Cattle - Monitor each cow? :
https://etherpad.openstack.org/p/YVR-vitrage-rca-over-
Excerpts from Stephen Finucane's message of 2018-05-15 11:44:11 +0100:
> I imagine most people have been seeing warnings like the one below
> raised by various openstack packages recently:
>
> .tox/py27/lib/python2.7/site-packages/psycopg2/__init__.py:144:
> UserWarning: The psycopg2
> wheel
Let me clarify the problem I want to solve with pipelines.
It is getting *hard* to develop things and move patches to the Happy End
(merged):
- Patches wait too long for CI jobs to start. It should be minutes and
not hours of waiting.
- If a patch fails a job w/o a good reason, the consequent r
Hi,
A few minor bugs opened and one critical one -
https://bugs.launchpad.net/neutron/+bug/1771293
Thanks
Gary
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected].
On 2018-05-15 14:07:56 +0200 (+0200), Bogdan Dobrelya wrote:
[...]
> How pipelines may help solve it?
> Pipelines only alleviate, not solve the problem of waiting. We only want to
> build pipelines for the main zuul check process, omitting gating and RDO CI
> (for now).
>
> Where are two cases to
On 5/15/18 2:30 PM, Jeremy Stanley wrote:
On 2018-05-15 14:07:56 +0200 (+0200), Bogdan Dobrelya wrote:
[...]
How pipelines may help solve it?
Pipelines only alleviate, not solve the problem of waiting. We only want to
build pipelines for the main zuul check process, omitting gating and RDO CI
(f
On Tue, 2018-05-15 at 07:24 -0400, Doug Hellmann wrote:
> Excerpts from Stephen Finucane's message of 2018-05-15 11:44:11 +0100:
> > I imagine most people have been seeing warnings like the one below
> > raised by various openstack packages recently:
> >
> > .tox/py27/lib/python2.7/site-packages
On 2018-05-15 15:22:14 +0200 (+0200), Bogdan Dobrelya wrote:
[...]
> I mean pipelines as jobs executed in batches, ordered via defined
> dependencies, like gitlab pipelines [0]. And those batches can
> also be thought of steps, or whatever we call that.
[...]
Got it. So Zuul refers to that relatio
Bogdan Dobrelya writes:
> Added a few more patches [0], [1] by the discussion results. PTAL folks.
> Wrt remaining in the topic, I'd propose to give it a try and revert
> it, if it proved to be worse than better.
> Thank you for feedback!
>
> The next step could be reusing artifacts, like DLRN re
Excerpts from Thierry Carrez's message of 2018-05-15 10:38:36 +0200:
> Doug Hellmann wrote:
> > We will also hold a retrospective for the TC as a team on Monday
> > at the Forum. Please be prepared to discuss things you think are
> > going well, things you think we need to change, items from our
>
Excerpts from Lance Bragstad's message of 2018-05-14 18:45:49 -0500:
>
> On 05/14/2018 05:46 PM, Doug Hellmann wrote:
> > Excerpts from Lance Bragstad's message of 2018-05-14 15:20:42 -0500:
> >> On 05/14/2018 02:24 PM, Doug Hellmann wrote:
> >>> Excerpts from Lance Bragstad's message of 2018-05-1
Dan and I are organizing a deep-dive session focused on the containerized
undercloud.
https://etherpad.openstack.org/p/tripleo-deep-dive-containerized-undercloud
We proposed a date + list of topics but feel free to comment and ask for
topics/questions.
Thanks,
--
Emilien & Dan
__
Bumping this up so folks can review this. It was mentioned in this
week's meeting that it would be a good idea for folks to take a look
at Storyboard to get familiar with it. The upstream docs have been
updated[0] to point to the differences when dealing with proposed
patches. Please take some t
Bogdan,
I think before final decisions we need to know exactly - what a price we
need to pay? Without exact numbers it will be difficult to discuss about.
I we need to wait 80 mins of undercloud-containers job to finish for
starting all other jobs, it will be about 4.5 hours to wait for result (+
Dear all,
Here is a gentle reminder regarding the FEMDC meeting that was postponed
from last week to tomorrow: May, the 16th at 15:00 UTC.
As a consequence, the meeting will be held on #edge-computing-irc
This meeting will focus on the preparation of the Vancouver summit
(presentations, F2F
On 5/15/18 4:30 PM, James E. Blair wrote:
Bogdan Dobrelya writes:
Added a few more patches [0], [1] by the discussion results. PTAL folks.
Wrt remaining in the topic, I'd propose to give it a try and revert
it, if it proved to be worse than better.
Thank you for feedback!
The next step could
HTML: https://anticdent.org/tc-report-18-20.html
Trying to write a TC report after a gap of 3 weeks is hard enough,
but when that gap involves some time off, the TC elections, and the
run up to summit (next week in
[Vancouver](https://www.openstack.org/summit/vancouver-2018/)) then
it gets bewil
On 2018-05-15 17:31:07 +0200 (+0200), Bogdan Dobrelya wrote:
[...]
> * upload into a swift container, with an automatic expiration set, the
> de-duplicated and compressed tarball created with something like:
> # docker save $(docker images -q) | gzip -1 > all.tar.xz
> (I expect it will be somethi
On 5/15/18 5:08 PM, Sagi Shnaidman wrote:
Bogdan,
I think before final decisions we need to know exactly - what a price we
need to pay? Without exact numbers it will be difficult to discuss about.
I we need to wait 80 mins of undercloud-containers job to finish for
starting all other jobs, it
On 15/05/18 16:31, Chris Dent wrote:
>
> HTML: https://anticdent.org/tc-report-18-20.html
>
> Trying to write a TC report after a gap of 3 weeks is hard enough,
> but when that gap involves some time off, the TC elections, and the
> run up to summit (next week in
> [Vancouver](https://www.opensta
On 13/05/18 13:22, Matthew Thode wrote:
This is a reminder to the projects called out that they are using old,
unmaintained and probably insecure libraries (it's been dead since
2014). Please migrate off to use the cryptography library. We'd like
to drop pycrypto from requirements for rocky.
S
From my memory, the LCOO was started in 2015 or 2016. The UC was started at the
end of 2012, start of 2013 (https://www.openstack.org/blog/?p=3777) with Ryan,
JC and I.
Tim
-Original Message-
From: Graham Hayes
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Bogdan Dobrelya writes:
> * check out testing depends-on things,
(Zuul should have done this for you, but yes.)
> * build repos and all tripleo docker images from these repos,
> * upload into a swift container, with an automatic expiration set, the
> de-duplicated and compressed tarball created
On 15/05/18 17:33, Tim Bell wrote:
> From my memory, the LCOO was started in 2015 or 2016. The UC was started at
> the end of 2012, start of 2013 (https://www.openstack.org/blog/?p=3777) with
> Ryan, JC and I.
>
> Tim
Yeap - I miss read what mrhillsman said [0].
The point still stands - I thin
fyi Jay tried to once -
http://lists.openstack.org/pipermail/openstack-dev/2017-February/thread.html#111511
On Tue, May 15, 2018 at 12:40 PM, Graham Hayes wrote:
> On 15/05/18 17:33, Tim Bell wrote:
>> From my memory, the LCOO was started in 2015 or 2016. The UC was started at
>> the end of 2012
fyi Jay tried to once -
http://lists.openstack.org/pipermail/openstack-dev/2017-February/thread.html#111511
On Tue, May 15, 2018 at 12:40 PM, Graham Hayes wrote:
> On 15/05/18 17:33, Tim Bell wrote:
>> From my memory, the LCOO was started in 2015 or 2016. The UC was started at
>> the end of 2012
Please unblock webob-1.8.1, you are the only library holding it back at
this point. I don't see a way to submit code to the project so I cc'd
the project in launchpad.
https://bugs.launchpad.net/openstack-requirements/+bug/1765748
--
Matthew Thode (prometheanfire)
signature.asc
Description: P
On 2018-05-15 09:40:28 -0700 (-0700), James E. Blair wrote:
[...]
> We're also talking about making a new kind of job which can continue to
> run after it's "finished" so that you could use it to do something like
> host a container registry that's used by other jobs running on the
> change. We do
On 18-05-15 12:25:04, Zane Bitter wrote:
> On 13/05/18 13:22, Matthew Thode wrote:
> > This is a reminder to the projects called out that they are using old,
> > unmaintained and probably insecure libraries (it's been dead since
> > 2014). Please migrate off to use the cryptography library. We'd
Jeremy Stanley writes:
> On 2018-05-15 09:40:28 -0700 (-0700), James E. Blair wrote:
> [...]
>> We're also talking about making a new kind of job which can continue to
>> run after it's "finished" so that you could use it to do something like
>> host a container registry that's used by other jobs
Welcome to the twenty first edition of a weekly update in TripleO world!
The goal is to provide a short reading (less than 5 minutes) to learn
what's new this week.
Any contributions and feedback are welcome.
Link to the previous version:
http://lists.openstack.org/pipermail/openstack-dev/2018-May/
Hello!
As part of the work from the Security Squad, we added the ability for the
containerized undercloud to encrypt the overcloud plans. This is done by
enabling Swift's encrypted volumes, which require barbican. Right now it's
turned off, but I would like to enable it by default [1]. What do you
On Tue, 15 May 2018 14:27:12 +0800, Chen Ch Ji wrote:
Thanks for the sharing, The z/VM driver spec review marked as END DATE:
2018-05-15
Thanks a couple folks helped a lot on the review and still need more
review activity on the patch sets, can I apply for extend the end date
for the run way?
On Tue, May 15, 2018 at 1:29 PM James E. Blair wrote:
> Jeremy Stanley writes:
>
> > On 2018-05-15 09:40:28 -0700 (-0700), James E. Blair wrote:
> > [...]
> >> We're also talking about making a new kind of job which can continue to
> >> run after it's "finished" so that you could use it to do so
On Mon, May 14, 2018 at 3:16 PM Sagi Shnaidman wrote:
> Hi, Bogdan
>
> I like the idea with undercloud job. Actually if undercloud fails, I'd
> stop all other jobs, because it doens't make sense to run them. Seeing the
> same failure in 10 jobs doesn't add too much. So maybe adding undercloud
> j
On Tue, May 15, 2018 at 11:42 AM Jeremy Stanley wrote:
> On 2018-05-15 17:31:07 +0200 (+0200), Bogdan Dobrelya wrote:
> [...]
> > * upload into a swift container, with an automatic expiration set, the
> > de-duplicated and compressed tarball created with something like:
> > # docker save $(dock
On 2018-05-15 14:52:26 -0600 (-0600), Wesley Hayutin wrote:
[...]
> The content would then sync to a swift file server on a central
> point for ALL the openstack providers or it would be sync'd to
> each cloud?
[...]
We haven't previously requested that all the Infra provider donors
support Swift,
Hi,
Maybe I missed the original discussion, I found the 'mutable' configuration
implementation relies on oslo.service, but is there any guide for the
projects using cotyledon instead?
Cheers,
Lingxian Kong
On Wed, May 16, 2018 at 2:46 AM Doug Hellmann wrote:
> Excerpts from Lance Bragstad's m
Bump the last time
Hi all,
As we keep adding more info to the migration guideline [1], you might like
to take a look again.
And do hope it will make things easier for you. If not, please find me in
irc or mail.
[1] https://etherpad.openstack.org/p/Heat-StoryBoard-Migration-Info
2018-05-10 18:42
Thanks for the reminder
we updated the code to 1.1.1 , and current info can be found
https://pypi.org/project/zVMCloudConnector/#description
detailed code can be found here , you can see no block for webob anymore
https://github.com/mfcloud/python-zvm-sdk/blob/master/requirements.txt#L7
please s
48 matches
Mail list logo
