Re: [openstack-dev] [tripleo] using molecule to test ansible playbooks and roles

On Sun, Nov 11, 2018 at 11:29:43AM +, Sorin Sbarnea wrote: > I recently came across molecule a > project originated at Cisco which recently become an officially Ansible > project, at the same time as ansible-lint. Both projects were transferred > from

Re: [openstack-dev] [oslo][taskflow] Thoughts on moving taskflow out of openstack/oslo

On Mon, Oct 15, 2018 at 04:27:00PM -0500, Monty Taylor wrote: > On 10/15/2018 05:49 AM, Stephen Finucane wrote: > > On Wed, 2018-10-10 at 18:51 +, Jeremy Stanley wrote: > > > On 2018-10-10 13:35:00 -0500 (-0500), Greg Hill wrote: > > > [...] > > > > We plan to still have a CI gatekeeper,

[openstack-dev] non-candidacy for TC

Greetings, After a year on the TC, I've decided not to run for another term. I'd like to thank the other TC members for helping bring me up to speed over the last year and community for originally voting. There is always work to do, and I'd like to use this email to encourage everybody to

Re: [openstack-dev] [barbican][ara][helm][tempest] Removal of fedora-27 nodes

On Mon, Aug 13, 2018 at 09:56:44AM -0400, Paul Belanger wrote: > On Thu, Aug 02, 2018 at 08:01:46PM -0400, Paul Belanger wrote: > > Greetings, > > > > We've had fedora-28 nodes online for some time in openstack-infra, I'd like > > to > > finish the migration pr

Re: [openstack-dev] [barbican][ara][helm][tempest] Removal of fedora-27 nodes

On Thu, Aug 02, 2018 at 08:01:46PM -0400, Paul Belanger wrote: > Greetings, > > We've had fedora-28 nodes online for some time in openstack-infra, I'd like to > finish the migration process and remove fedora-27 images. > > Please take a moment to review and approve the f

Re: [openstack-dev] [openstack-ansible][kolla-ansible][tripleo] ansible roles: where they live and what do they do

On Thu, Aug 09, 2018 at 08:00:13PM -0600, Wesley Hayutin wrote: > On Thu, Aug 9, 2018 at 5:33 PM Alex Schultz wrote: > > > On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann > > wrote: > > > Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600: > > >> Ahoy folks, > > >> > > >> I think

[openstack-dev] [barbican][ara][helm][tempest] Removal of fedora-27 nodes

Greetings, We've had fedora-28 nodes online for some time in openstack-infra, I'd like to finish the migration process and remove fedora-27 images. Please take a moment to review and approve the following patches[1]. We'll be using the fedora-latest nodeset now, which make is a little easier for

Re: [openstack-dev] Disk space requirement - any way to lower it a little?

On Thu, Jul 19, 2018 at 05:30:27PM +0200, Cédric Jeanneret wrote: > Hello, > > While trying to get a new validation¹ in the undercloud preflight > checks, I hit an (not so) unexpected issue with the CI: > it doesn't provide flavors with the minimal requirements, at least > regarding the disk

Re: [openstack-dev] Fwd: [TIP] tox release 3.1.1

On Mon, Jul 09, 2018 at 01:44:00PM -0400, Doug Hellmann wrote: > Excerpts from Eric Fried's message of 2018-07-09 11:16:11 -0500: > > Doug- > > > > How long til we can start relying on the new behavior in the gate? I > > gots me some basepython to purge... > > > > -efried > > Great

Re: [openstack-dev] [openstack-ansible] dropping selinux support

On Thu, Jun 28, 2018 at 12:56:22PM -0400, Mohammed Naser wrote: > Hi everyone: > > This email is to ask if there is anyone out there opposed to removing > SELinux bits from OpenStack ansible, it's blocking some of the gates > and the maintainers for them are no longer working on the project >

Re: [openstack-dev] [tripleo] tripleo gate is blocked - please read

On Sat, Jun 16, 2018 at 12:47:10PM +, Jeremy Stanley wrote: > On 2018-06-15 23:15:01 -0700 (-0700), Emilien Macchi wrote: > [...] > > ## Dockerhub proxy issue > > Infra using wrong image layer object storage proxy for Dockerhub: > > https://review.openstack.org/#/c/575787/ > > Huge thanks to

Re: [openstack-dev] [all][python3][tc][infra] Python 3.6

On Tue, Jun 05, 2018 at 04:48:00PM -0400, Zane Bitter wrote: > On 05/06/18 16:38, Doug Hellmann wrote: > > Excerpts from Zane Bitter's message of 2018-06-05 15:55:49 -0400: > > > We've talked a bit about migrating to Python 3, but (unless I missed it) > > > not a lot about which version of Python

[openstack-dev] [all] Gerrit server replacement finished

Hello from Infra. Gerrit maintenance has concluded successfully and running happily on Ubuntu Xenial. We were able to save and restore the queues from zuul, but as always be sure to check your patches as a recheck maybe be required. If you have any questions or comments, please reach out to us

[openstack-dev] [all] Gerrit server replacement scheduled for May 2nd 2018

Hello from Infra. Today is the day for scheduled maintenance of gerrit, we'll be allocating 2 hours for the outage but don't expect it to take that long. During this time you will not be able to access gerrit. If you have any questions, or would like to follow along, please join us in

Re: [openstack-dev] Thank you TryStack!!

On Mon, Apr 30, 2018 at 09:37:21AM +, Jens Harbott wrote: > 2018-03-26 22:51 GMT+00:00 Jimmy Mcarthur : > > Hi everyone, > > > > We recently made the tough decision, in conjunction with the dedicated > > volunteers that run TryStack, to end the service as of March 29, 2018.

Re: [openstack-dev] [all][tc] final stages of python 3 transition

On Thu, Apr 26, 2018 at 09:27:31AM -0500, Sean McGinnis wrote: > On Wed, Apr 25, 2018 at 04:54:46PM -0400, Doug Hellmann wrote: > > It's time to talk about the next steps in our migration from python > > 2 to python 3. > > > > [...] > > > > 2. Change (or duplicate) all functional test jobs to

[openstack-dev] [all] Gerrit server replacement scheduled for May 2nd 2018

On Thu, Apr 19, 2018 at 11:49:12AM -0400, Paul Belanger wrote: Hello from Infra. This is our weekly reminder of the upcoming gerrit replacement. We'll continue to send these announcements out up until the day of the migration. We are now 1 weeks away from replacement date. If you have any

[openstack-dev] [bifrost][bandit][magnum][ironic][kolla][pyeclib][mistral] Please merge bindep changes

Greetings, Could you please review the following bindep.txt[1] changes to your projects and approve them, it would be helpful to the openstack-infra team. We are looking to remove some legacy jenkins scripts from openstack-infra/project-config and your projects are still using them. The

Re: [openstack-dev] [all][infra] ubuntu-bionic and legacy nodesets

ython to 3.6 and likely be too late in the cycle to do it. I guess something we can hash out with infra / requirements / tc / EALLTHEPROJECTS. -Paul > > On 20 April 2018 at 00:37, Paul Belanger <pabelan...@redhat.com> wrote: > > Greetings, > > > > With ubuntu-bionic r

[openstack-dev] [all][infra] ubuntu-bionic and legacy nodesets

Greetings, With ubuntu-bionic release around the corner we'll be starting discussions about migrating jobs from ubuntu-xenial to ubuntu-bionic. On topic I'd like to raise, is round job migrations from legacy to native zuulv3. Specifically, I'd like to propose we do not add legacy-ubuntu-bionic

[openstack-dev] [infra] Removal of debian-jessie, replaced by debian-stable (stretch)

Greetings, I'd like to propose now that we have debian-stable (stretch) nodesets online for nodepool, that we start the process to remove debian-jessie. As I can see, there really is only 2 projects using debian-jessie: * ARA * ansible-hardening I've already proposed patches to update

[openstack-dev] [all] Gerrit server replacement scheduled for May 2nd 2018

Hello from Infra. This is our weekly reminder of the upcoming gerrit replacement. We'll continue to send these announcements out up until the day of the migration. We are now 2 weeks away from replacement date. If you have any questions, please contact us in #openstack-infra. --- It's that

[openstack-dev] [all] Gerrit server replacement scheduled for May 2nd 2018

Hello from Infra. This is our weekly reminder of the upcoming gerrit replacement. We'll continue to send these announcements out up until the day of the migration. If you have any questions, please contact us in #openstack-infra. --- It's that time again... on Wednesday, May 02, 2018 20:00

Re: [openstack-dev] [infra][qa][requirements] Pip 10 is on the way

On Sat, Apr 07, 2018 at 12:56:31AM -0700, Arun SAG wrote: > Hello, > > On Thu, Apr 5, 2018 at 5:39 PM, Paul Belanger <pabelan...@redhat.com> wrote: > > > Yah, I agree your approach is the better, i just wanted to toggle what was > > supported by default. However,

Re: [openstack-dev] [bifrost][helm][OSA][barbican] Switching from fedora-26 to fedora-27

On Wed, Apr 04, 2018 at 11:27:34AM -0400, Paul Belanger wrote: > On Tue, Mar 13, 2018 at 10:54:26AM -0400, Paul Belanger wrote: > > On Mon, Mar 05, 2018 at 06:45:13PM -0500, Paul Belanger wrote: > > > Greetings, > > > > > > A quick search of git shows you

Re: [openstack-dev] [infra][qa][requirements] Pip 10 is on the way

On Thu, Apr 05, 2018 at 01:27:13PM -0700, Clark Boylan wrote: > On Mon, Apr 2, 2018, at 9:13 AM, Clark Boylan wrote: > > On Mon, Apr 2, 2018, at 8:06 AM, Matthew Thode wrote: > > > On 18-03-31 15:00:27, Jeremy Stanley wrote: > > > > According to a notice[1] posted to the pypa-announce and > > > >

Re: [openstack-dev] Asking for ask.openstack.org

On Wed, Apr 04, 2018 at 04:26:12PM -0500, Jimmy McArthur wrote: > Hi everyone! > > We have a very robust and vibrant community at ask.openstack.org > . There are literally dozens of posts a day. > However, many of them don't receive knowledgeable answers. I'm really

[openstack-dev] [openstack-helm][infra] Please consider using experimental pipeline for non-voting jobs

Greetings, I've recently proposed https://review.openstack.org/558870 to the openstack-helm project. This moves both centos / fedora jobs into the experimental pipeline. The reason for this, the multinode jobs in helm each use 5 nodes per distro. This this case, 10 shared between centos / fedora.

Re: [openstack-dev] [bifrost][helm][OSA][barbican] Switching from fedora-26 to fedora-27

On Tue, Mar 13, 2018 at 10:54:26AM -0400, Paul Belanger wrote: > On Mon, Mar 05, 2018 at 06:45:13PM -0500, Paul Belanger wrote: > > Greetings, > > > > A quick search of git shows your projects are using fedora-26 nodes for > > testing. > > Please take a moment t

[openstack-dev] Gerrit server replacement scheduled for May 2nd 2018

Hello from Infra. It's that time again... on Wednesday, May 02, 2018 20:00 UTC, the OpenStack Project Infrastructure team is upgrading the server which runs review.openstack.org to Ubuntu Xenial, and that means a new virtual machine instance with new IP addresses assigned by our service provider.

Re: [openstack-dev] [all][infra] Upcoming changes in ARA Zuul job reports

On Thu, Mar 29, 2018 at 06:14:06PM -0400, David Moreau Simard wrote: > Hi, > > By default, all jobs currently benefit from the generation of a static > ARA report located in the "ara" directory at the root of the log > directory. > Due to scalability concerns, these reports were only generated

[openstack-dev] All Hail our Newest Release Name - OpenStack Stein

Hi everybody! As the subject reads, the "S" release of OpenStack is officially "Stein". As been with previous elections this wasn't the first choice, that was "Solar". Solar was judged to have legal risk, so as per our name selection process, we moved to the next name on the list. Thanks to

[openstack-dev] OpenStack "S" Release Naming Preliminary Results

Hello all! We decided to run a public poll this time around, we'll likely discuss the process during a TC meeting, but we'd love the hear your feedback. The raw results are below - however ... **PLEASE REMEMBER** that these now have to go through legal vetting. So it is too soon to say

Re: [openstack-dev] Poll: S Release Naming

On Tue, Mar 13, 2018 at 07:58:59PM -0400, Paul Belanger wrote: > Greetings all, > > It is time again to cast your vote for the naming of the S Release. This time > is little different as we've decided to use a public polling option over per > user private URLs for voting. This m

Re: [openstack-dev] [horizon][neutron] tools/tox_install changes - breakage with constraints

On Wed, Mar 14, 2018 at 10:25:49PM +, Chris Dent wrote: > On Thu, 15 Mar 2018, Akihiro Motoki wrote: > > > (1) it makes difficult to run tests in local environment > > We have only released version of neutron/horizon on PyPI. It means > > PyPI version (i.e. queens) is installed when we run

Re: [openstack-dev] [bifrost][helm][OSA][barbican] Switching from fedora-26 to fedora-27

On Wed, Mar 14, 2018 at 04:44:07PM -0400, Paul Belanger wrote: > On Wed, Mar 14, 2018 at 03:20:40PM -0400, Paul Belanger wrote: > > On Wed, Mar 14, 2018 at 03:53:59AM +, na...@vn.fujitsu.com wrote: > > > Hello Paul, > > > > > > I am Nam from Barbican te

Re: [openstack-dev] [bifrost][helm][OSA][barbican] Switching from fedora-26 to fedora-27

On Wed, Mar 14, 2018 at 03:20:40PM -0400, Paul Belanger wrote: > On Wed, Mar 14, 2018 at 03:53:59AM +, na...@vn.fujitsu.com wrote: > > Hello Paul, > > > > I am Nam from Barbican team. I would like to notify a problem when using > > fedora-27. > > > >

Re: [openstack-dev] [bifrost][helm][OSA][barbican] Switching from fedora-26 to fedora-27

owse/MDEV-13508 > Looking at https://apps.fedoraproject.org/packages/mariadb seems 10.2.13 has already been updated. Let me recheck the patch and see if it will use the newer version. > Thanks, > Nam > > > -Original Message- > > From: Paul Belanger [mailto:pabelan...@redhat.com]

[openstack-dev] Poll: S Release Naming

Greetings all, It is time again to cast your vote for the naming of the S Release. This time is little different as we've decided to 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:

Re: [openstack-dev] [bifrost][helm][OSA][barbican] Switching from fedora-26 to fedora-27

On Mon, Mar 05, 2018 at 06:45:13PM -0500, Paul Belanger wrote: > Greetings, > > A quick search of git shows your projects are using fedora-26 nodes for > testing. > Please take a moment to look at gerrit[1] and help land patches. We'd like to > remove fedora-26 node

[openstack-dev] [bifrost][helm][OSA][barbican] Switching from fedora-26 to fedora-27

Greetings, A quick search of git shows your projects are using fedora-26 nodes for testing. Please take a moment to look at gerrit[1] and help land patches. We'd like to remove fedora-26 nodes in the next week and to avoid broken jobs you'll need to approve these patches. If you jobs are

Re: [openstack-dev] Release Naming for S - time to suggest a name!

On Tue, Feb 20, 2018 at 08:19:59PM -0500, Paul Belanger wrote: > Hey everybody, > > Once again, it is time for us to pick a name for our "S" release. > > Since the associated Summit will be in Berlin, the Geographic > Location has been chosen as "Berlin"

[openstack-dev] [infra][3rd party ci] Removal of jenkins user from DIB images

Greetings, As we move forward with using zuulv3 more and more and less and less of jenkins, we are continuing the clean up of our images. Specifically, if your 3rd party CI is still using jenkins please take note of the following changes[1]. By default our openstack-infra images will no longer

Re: [openstack-dev] [tripleo] rdo cloud tenant reach 100 stacks

On Fri, Feb 23, 2018 at 02:20:34PM +0100, Arx Cruz wrote: > Just an update, we cleaned up the stacks with more than 10 hours, jobs > should be working properly now. > > Kind regards, > Arx Cruz > > On Fri, Feb 23, 2018 at 12:49 PM, Arx Cruz wrote: > > > Hello, > > > > We

[openstack-dev] Release Naming for S - time to suggest a name!

Hey everybody, Once again, it is time for us to pick a name for our "S" release. Since the associated Summit will be in Berlin, the Geographic Location has been chosen as "Berlin" (State). Nominations are now open. Please add suitable names to

Re: [openstack-dev] [infra] [all] project pipeline definition should stay in project-config or project side ?

On Tue, Feb 13, 2018 at 11:05:34PM +0900, gmann wrote: > Hi Infra Team, > > I have 1 quick question on zuulv3 jobs and their migration part. From > zuulv3 doc [1], it is clear about migrating the job definition and use > those among cross repo pipeline etc. > > But I did not find clear

Re: [openstack-dev] [tripleo] CI'ing ceph-ansible against TripleO scenarios

On Thu, Jan 25, 2018 at 04:22:56PM -0800, Emilien Macchi wrote: > Is there any plans to run TripleO CI jobs in ceph-ansible? > I know the project is on github but thanks to zuulv3 we can now easily > configure ceph-ansible to run Ci jobs in OpenStack Infra. > > It would be really great to

Re: [openstack-dev] [devstack] Broken repo on devstack-plugin-container for Fedora

On Wed, Jan 24, 2018 at 02:14:40PM +0100, Daniel Mellado wrote: > Hi everyone, > > Since today, when I try to install devstack-plugin-container plugin over > fedora. It complains in here [1] about not being able to sync the cache > for the repo with the following error [2]. > > This is affecting

Re: [openstack-dev] Many timeouts in zuul gates for TripleO

On Fri, Jan 19, 2018 at 11:23:45AM -0600, Ben Nemec wrote: > > > On 01/18/2018 09:45 AM, Emilien Macchi wrote: > > On Thu, Jan 18, 2018 at 6:34 AM, Or Idgar wrote: > > > Hi, > > > we're encountering many timeouts for zuul gates in TripleO. > > > For example, see > > >

Re: [openstack-dev] [qa][neutron][octavia][horizon][networking-l2gw] Renaming tox_venvlist in Zuul v3 run-tempest

On Fri, Jan 12, 2018 at 05:13:28PM +0100, Andreas Jaeger wrote: > The Zuul v3 tox jobs use "tox_envlist" to name the tox environment to > use, the tempest run-tempest role used "tox_venvlist" with an extra "v" > in it. This lead to some confusion and a wrong fix, so let's be > consistent across

Re: [openstack-dev] [tc][ptl][goals][storyboard] tracking the rocky goals with storyboard

On Fri, Jan 12, 2018 at 01:11:40PM -0800, Emilien Macchi wrote: > On Fri, Jan 12, 2018 at 12:37 PM, Doug Hellmann wrote: > > Since we are discussing goals for the Rocky cycle, I would like to > > propose a change to the way we track progress on the goals. > > > > We've

Re: [openstack-dev] Keystone Team Update - Week of 4 December 2017

On Fri, Dec 08, 2017 at 05:58:05PM +, Jeremy Stanley wrote: > On 2017-12-08 18:48:56 +0100 (+0100), Colleen Murphy wrote: > [...] > > The major hindrance to keystone using Storyboard is its lack of > > support for private bugs, which is a requirement given that > > keystone is a VMT-managed

Re: [openstack-dev] [tc] [all] TC Report 49

On Thu, Dec 07, 2017 at 05:28:53PM +, Jeremy Stanley wrote: > On 2017-12-07 17:08:55 + (+), Graham Hayes wrote: > [...] > > It is worth remembering that this is a completely separate project to > > OpenStack, with its own governance. They are free not to use our tooling > > (and

Re: [openstack-dev] [infra][all] Removal of packages from bindep-fallback

On Thu, Nov 23, 2017 at 07:55:07PM +0100, Andreas Jaeger wrote: > On 2017-11-16 06:59, Ian Wienand wrote: > > Hello, > > > > Some time ago we started the process of moving towards projects being > > more explicit about thier binary dependencies using bindep [1] > > > > To facilitate the

Re: [openstack-dev] Removing internet access from unit test gates

On Tue, Nov 21, 2017 at 04:41:13PM +, Mooney, Sean K wrote: > > > > -Original Message- > > From: Jeremy Stanley [mailto:fu...@yuggoth.org] > > Sent: Tuesday, November 21, 2017 3:05 PM > > To: OpenStack Development Mailing List (not for usage questions) > >

Re: [openstack-dev] [doc][infra][stable] we are ready to restore stable/mitaka for openstack-manuals

On Mon, Nov 20, 2017 at 05:40:26PM +0100, Andreas Jaeger wrote: > On 2017-11-20 17:32, Doug Hellmann wrote: > > As we agreed in the new documentation retention policy spec [1], I need > > to restore the stable/mitaka branch for the openstack/openstack-manuals > > repository and then trigger a

Re: [openstack-dev] [infra][all] Removal of packages from bindep-fallback

On Thu, Nov 16, 2017 at 04:59:01PM +1100, Ian Wienand wrote: > Hello, > > Some time ago we started the process of moving towards projects being > more explicit about thier binary dependencies using bindep [1] > > To facilitate the transition, we created a "fallback" set of > dependencies [2]

Re: [openstack-dev] Upstream LTS Releases

On Tue, Nov 14, 2017 at 11:25:03AM -0500, Doug Hellmann wrote: > Excerpts from Bogdan Dobrelya's message of 2017-11-14 17:08:31 +0100: > > >> The concept, in general, is to create a new set of cores from these > > >> groups, and use 3rd party CI to validate patches. There are lots of > > >>

Re: [openstack-dev] [tc][election] Question for all candidates in TC election: What will you do if you don't win?

On Sun, Oct 15, 2017 at 08:15:51AM -0400, Amrith Kumar wrote: > Full disclosure, I'm running for election as well. I intend to also > provide an answer to the question I pose here, one that I've posed > before on #openstack-tc in an office hours session. > > Question 1: > > "There are M open

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

On Fri, Oct 13, 2017 at 02:45:28PM +0200, Flavio Percoco wrote: > Greetings, > > Some of you, TC candidates, expressed concerns about diversity and > inclusiveness > (or inclusivity, depending on your taste) in your candidacy. I believe this > is a > broad, and some times ill-used, topic so,

Re: [openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?

On Thu, Oct 12, 2017 at 12:51:10PM -0400, Zane Bitter wrote: > (Reminder: we are in the TC election campaigning period, and we all have the > opportunity to question the candidates. The campaigning period ends on > Saturday, so make with the questions.) > > > In my head, I have a mental picture

Re: [openstack-dev] [tc][election] Question for the candidates

On Thu, Oct 12, 2017 at 12:42:46PM -0700, Clay Gerrard wrote: > I like a representative democracy. It mostly means I get a say in which > other people I have to trust to think deeply about issues which effect me > and make decisions which I agree (more or less) are of benefit to the > social

Re: [openstack-dev] [tc][election] Question for the candidates

On Thu, Oct 12, 2017 at 01:38:03PM -0500, Ed Leafe wrote: > In the past year or so, has there been anything that made you think “I wish > the TC would do something about that!” ? If so, what was it, and what would > you have wanted the TC to do about it? > > -- Ed Leafe > No, I've been happy

[openstack-dev] [tc][election] TC candidacy

project allows for the ability to see what is great about OpenStack and what could use improvements. I believe you get out of something what you put into it, so here I am adding my name of the list. Good luck to all, Paul Belanger

Re: [openstack-dev] Update on Zuul v3 Migration - and what to do about issues

On Wed, Oct 04, 2017 at 02:39:17PM +0900, Rikimaru Honjo wrote: > Hello, > > I'm trying to run jobs with Zuul v3 in my local environment.[1] > I prepared a sample job that runs sleep command on zuul's host. > This job doesn't use Nodepool. [2] > > As a result, Zuul v3 submitted "SUCCESS" to

Re: [openstack-dev] [infra] pypi publishing

On Sun, Oct 01, 2017 at 05:02:00AM -0700, Clark Boylan wrote: > On Sat, Sep 30, 2017, at 10:28 PM, Gary Kotton wrote: > > Hi, > > Any idea why latest packages are not being published to pypi. > > Examples are: > > vmware-nsxlib 10.0.2 (latest stable/ocata) > > vmware-nsxlib 11.0.1 (latest

Re: [openstack-dev] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL

On Wed, Sep 20, 2017 at 11:26:46AM -0400, Tony Breeds wrote: > On Wed, Sep 20, 2017 at 12:56:07PM +0200, Andreas Jaeger wrote: > > > So, for fuel we have stable/7.0 etc - what are the plans for these? Can > > we retire them as well? > > > > Those are even older AFAIK, > > As discussed on IRC,

Re: [openstack-dev] [devstack] Why do we apt-get install NEW files/debs/general at job time ?

On Fri, Sep 22, 2017 at 02:31:20PM +, Jeremy Stanley wrote: > On 2017-09-22 15:04:43 +0200 (+0200), Attila Fazekas wrote: > > "if DevStack gets custom images prepped to make its jobs > > run faster, won't Triple-O, Kolla, et cetera want the same and where > > do we draw that line?). " > > > >

Re: [openstack-dev] Garbage patches for simple typo fixes

On Fri, Sep 22, 2017 at 10:26:09AM +0800, Zhipeng Huang wrote: > Let's not forget the epic fail earlier on the "contribution.rst fix" that > almost melt down the community CI system. > > For any companies that are doing what Matt mentioned, please be aware that > the dev community of the country

Re: [openstack-dev] [tripleo] Pike final release - blockers & priorities

On Sun, Sep 03, 2017 at 10:23:15PM -0700, Emilien Macchi wrote: > On Sun, Sep 3, 2017 at 7:40 PM, Emilien Macchi wrote: > > Here are the priorities and blockers so we can release final Pike. > > If you have any question, or think I missed something, or have any > > comment,

Re: [openstack-dev] [tripleo] Gate is broken - Do not approve any patch until further notice

gt; 4) We should use pip instead of git for delorean > >> https://bugs.launchpad.net/tripleo/+bug/1708832 > >> > >> > >> Until further notice from Alex or myself, please do not approve any patch. > > > > The 4 problems have been mitigated. > >

Re: [openstack-dev] [TripleO] CI design session at the PTG

On Mon, Aug 28, 2017 at 09:42:45AM -0400, David Moreau Simard wrote: > Hi, > > (cc whom I would at least like to attend) > > The PTG would be a great opportunity to talk about CI design/layout > and how we see things moving forward in TripleO with Zuul v3, upstream > and in

Re: [openstack-dev] [tripleo] critical situation with CI / upgrade jobs

On Mon, Aug 21, 2017 at 10:43:07AM +1200, Steve Baker wrote: > On Thu, Aug 17, 2017 at 4:13 PM, Steve Baker wrote: > > > > > > > On Thu, Aug 17, 2017 at 10:47 AM, Emilien Macchi > > wrote: > > > >> > >> > Problem #3: from Ocata to Pike: all container

Re: [openstack-dev] [tripleo] critical situation with CI / upgrade jobs

On Tue, Aug 15, 2017 at 11:06:20PM -0400, Wesley Hayutin wrote: > On Tue, Aug 15, 2017 at 9:33 PM, Emilien Macchi wrote: > > > So far, we're having 3 critical issues, that we all need to address as > > soon as we can. > > > > Problem #1: Upgrade jobs timeout from Newton to

Re: [openstack-dev] [tripleo][puppet] Hold off on approving patches until further notice

On Thu, Aug 10, 2017 at 10:32:25PM -0600, Alex Schultz wrote: > On Thu, Aug 10, 2017 at 11:12 AM, Paul Belanger <pabelan...@redhat.com> wrote: > > On Thu, Aug 10, 2017 at 07:03:32AM -0600, Alex Schultz wrote: > >> FYI, > >> > >> The gates are hosed for a

Re: [openstack-dev] [tripleo][puppet] Hold off on approving patches until further notice

On Thu, Aug 10, 2017 at 07:03:32AM -0600, Alex Schultz wrote: > FYI, > > The gates are hosed for a variety of reasons[0][1] and we can't get > critical patches merged. Please hold off on rechecking or approving > anything new until further notice. We're hoping to get some of the > fixes for

Re: [openstack-dev] [heat][infra] Help needed! high gate failure rate

On Thu, Aug 10, 2017 at 07:22:42PM +0530, Rabi Mishra wrote: > On Thu, Aug 10, 2017 at 4:34 PM, Rabi Mishra wrote: > > > On Thu, Aug 10, 2017 at 2:51 PM, Ian Wienand wrote: > > > >> On 08/10/2017 06:18 PM, Rico Lin wrote: > >> > We're facing a high

Re: [openstack-dev] [tripleo][qa] Enabling elastic-recheck for tripleo job

On Mon, Aug 07, 2017 at 03:28:13PM -0400, Paul Belanger wrote: > On Mon, Aug 07, 2017 at 10:34:59AM -0700, Emilien Macchi wrote: > > On Mon, Aug 7, 2017 at 9:18 AM, Paul Belanger <pabelan...@redhat.com> wrote: > > > I've just pushed up a change to puppet-elas

Re: [openstack-dev] [tripleo][qa] Enabling elastic-recheck for tripleo job

On Mon, Aug 07, 2017 at 10:34:59AM -0700, Emilien Macchi wrote: > On Mon, Aug 7, 2017 at 9:18 AM, Paul Belanger <pabelan...@redhat.com> wrote: > > I've just pushed up a change to puppet-elastic_recheck[1] to update the jobs > > regex for elastic-recheck to start tracking trip

[openstack-dev] [tripleo][qa] Enabling elastic-recheck for tripleo job

Greetings, I've just pushed up a change to puppet-elastic_recheck[1] to update the jobs regex for elastic-recheck to start tracking tripleo. What this means, is now the elasticRecheck bot will start leaving comments on reviews once it matches a failure in knows about. The goal here is to better

Re: [openstack-dev] [tc][packaging][deb] retiring Packaging Deb project

On Thu, Aug 03, 2017 at 10:09:59AM -0400, Allison Randal wrote: > Hi all, > > The Debian OpenStack packagers are gathered at the annual Debian > developer event, and discussing the future of OpenStack packaging for > Debian. There's general agreement that we'd like to go ahead and package > Pike,

Re: [openstack-dev] [TripleO] An experiment with Ansible

On Thu, Jul 20, 2017 at 10:06:00PM -0400, James Slagle wrote: > On Thu, Jul 20, 2017 at 9:52 PM, James Slagle <james.sla...@gmail.com> wrote: > > On Thu, Jul 20, 2017 at 9:04 PM, Paul Belanger <pabelan...@redhat.com> > > wrote: > >> On Thu, Jul 20, 2017 at

Re: [openstack-dev] [TripleO] An experiment with Ansible

On Thu, Jul 20, 2017 at 06:21:22PM -0400, James Slagle wrote: > Following up on the previous thread: > http://lists.openstack.org/pipermail/openstack-dev/2017-July/119405.html > > I wanted to share some work I did around the prototype I mentioned > there. I spent a couple days exploring this

Re: [openstack-dev] [infra][devstack] DIB builds after mysql.qcow2 removal

On Mon, Jul 17, 2017 at 07:22:34PM +1000, Ian Wienand wrote: > Hi, > > The removal of the mysql.qcow2 image [1] had a flow-on effect noticed > first by Paul in [2] that the tools/image_list.sh "sanity" check was > not updated, leading to DIB builds failing in a most unhelpful way as > it tries to

Re: [openstack-dev] diskimage builder works for trusty but not for xenial

On Wed, Jun 21, 2017 at 08:44:45AM +0200, Ignazio Cassano wrote: > Hi all, > today I am creating openstack images with disk-image-create. > It works fine for centos and ubuntu trusty. > With xenial I got the following error: > > * Connection #0 to host cloud-images.ubuntu.com left intact >

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

On Thu, Jun 15, 2017 at 03:56:30PM +, Jeremy Stanley wrote: > On 2017-06-15 11:48:42 -0400 (-0400), Davanum Srinivas wrote: > > We took that tradeoff before and have suffered as a result. I'd say > > it's the cost of getting a project under governance. > > Well, sort of. We took the slightly

Re: [openstack-dev] [tripleo][ci] TripleO OVB check gates to move to third party

On Tue, Jun 13, 2017 at 02:11:53PM -0500, Ben Nemec wrote: > > > On 06/13/2017 12:28 PM, Paul Belanger wrote: > > On Tue, Jun 13, 2017 at 11:12:08AM -0500, Ben Nemec wrote: > > > > > > > > > On 06/12/2017 06:19 PM, Ronelle Landy wrote: > > &

Re: [openstack-dev] [tripleo][ci] TripleO OVB check gates to move to third party

On Tue, Jun 13, 2017 at 11:12:08AM -0500, Ben Nemec wrote: > > > On 06/12/2017 06:19 PM, Ronelle Landy wrote: > > Greetings, > > > > TripleO OVB check gates are managed by upstream Zuul and executed on > > nodes provided by test cloud RH1. RDO Cloud is now available as a test > > cloud to be

[openstack-dev] [infra][deb-packaging] Stop using track-upstream for deb projects

Greetings, I'd like to propose we stop using track-upstream for project-config on deb-packaging projects. It seems there is no active development on these projects currently and by using track-upstream we currently wasting both CI resources and HDD space keeping their projects in sync with there

Re: [openstack-dev] [tripleo][ci] tripleo periodic jobs moving to RDO's software factory and RDO Cloud

obs will move. The move > will depend on tenant resource allocation and how easily the periodic jobs > can be modified. This email is to inform the group that changes are being > planned to the tripleo periodic workflow and allow time for comment and > preparation. > > Completed

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On Fri, Jun 09, 2017 at 04:52:25PM +, Flavio Percoco wrote: > On Fri, Jun 9, 2017 at 11:30 AM Britt Houser (bhouser) > wrote: > > > How does confd run inside the container? Does this mean we’d need some > > kind of systemd in every container which would spawn both confd

Re: [openstack-dev] how to set default security group rules?

On Fri, Jun 09, 2017 at 05:20:03AM -0700, Kevin Benton wrote: > This was an intentional decision. One of the goals of OpenStack is to > provide consistency across different clouds and configurable defaults for > new tenants default rules hurts consistency. > > If I write a script to boot up a

Re: [openstack-dev] [forum] Future of Stackalytics

On Thu, Jun 08, 2017 at 02:11:18PM +, Jeremy Stanley wrote: > On 2017-06-08 09:22:48 -0400 (-0400), Paul Belanger wrote: > [...] > > We also have another issue where we loose access to gerrit and our apache > > process pins CPU to 100%, these might also be low hangin

Re: [openstack-dev] [forum] Future of Stackalytics

On Wed, May 17, 2017 at 06:55:57PM +, Jeremy Stanley wrote: > On 2017-05-17 16:16:30 +0200 (+0200), Thierry Carrez wrote: > [...] > > we need help with completing the migration to infra. If interested > > you can reach out to fungi (Infra team PTL) nor mrmartin (who > > currently helps with

[openstack-dev] [all][infra] Missing OpenSSL headers (fatal error: openssl/opensslv.h: No such file or directory)

Greetings, If your project is seeing the following errors, this likely means you do not have libssl development headers included in your bindep.txt file. To fix this you can add the following to your local bindep.txt file: libssl-dev [platform:dpkg] openssl-devel [platform:rpm] This will

[openstack-dev] [infra] Removal of git-review from DIB images

Greetings, Does your project use git-review on our zuul worker nodes? If so, this post is for you. For a long time we have installed git-review on to our worker nodes that are used by jobs. This also installs additional python dependencies: Successfully installed argparse-1.4.0

Re: [openstack-dev] Update re: debian packages?

On Thu, May 25, 2017 at 08:30:46AM -0500, Andrew Bogott wrote: > I've just noticed that, as predicted, Mirantis has switched off their > Openstack package repos (e.g. http://liberty-jessie.pkgs.mirantis.com/). > Are there any updates about a replacement repo, or a newly-reconstituted >

Re: [openstack-dev] [release][infra][puppet][stable] Re: [Release-job-failures] Release of openstack/puppet-nova failed

On Mon, May 22, 2017 at 10:53:32AM -0400, Doug Hellmann wrote: > Excerpts from jenkins's message of 2017-05-22 10:49:09 +: > > Build failed. > > > > - puppet-nova-tarball > > http://logs.openstack.org/89/89c58e7958b448364cb0290c1879116f49749a68/release/puppet-nova-tarball/fe9daf7/ > > :

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

On Thu, May 18, 2017 at 09:34:44AM -0700, Michał Jastrzębski wrote: > >> Issue with that is > >> > >> 1. Apache served is harder to use because we want to follow docker API > >> and we'd have to reimplement it > > > > No, the idea is apache is transparent, for now we have been using proxypass > >

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

On Tue, May 16, 2017 at 02:11:18PM +, Sam Yaple wrote: > I would like to bring up a subject that hasn't really been discussed in > this thread yet, forgive me if I missed an email mentioning this. > > What I personally would like to see is a publishing infrastructure to allow > pushing built

  1   2   3   >