Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

On Mon, 2018-10-22 at 07:50 -0700, Morgan Fainberg wrote: > Also, doesn't bitbucket have a git interface now too (optionally)? > It does :) But I think it requires a new repo, so it means that could as well move to somewhere else like github or openstack infra :p

Re: [openstack-dev] [goals][upgrade-checkers] Week R-25 Update

On Tue, 2018-10-23 at 16:40 -0500, Matt Riedemann wrote: > On 10/23/2018 1:41 PM, Sean McGinnis wrote: > > > Yeah, but part of the reason for placeholders was consistency > > > across all of > > > the services. I guess if there are never going to be upgrade > > > checks in > > > adjutant then I

Re: [Openstack-operators] [openstack-dev] [goals][upgrade-checkers] Week R-26 Update

hecker code, but I would love to see it re-using oslo-config- validator, as it would be the unique source of truth for upgrades before the upgrade happens (vs having to do multiple steps). If I am completely out of my league here, tell me. Just my 2 cents. Jean-Philippe Evrard (evrardjp) ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [openstack-dev] [goals][upgrade-checkers] Week R-26 Update

hecker code, but I would love to see it re-using oslo-config- validator, as it would be the unique source of truth for upgrades before the upgrade happens (vs having to do multiple steps). If I am completely out of my league here, tell me. Just my 2 cents. Jean-Philippe Evrard (evrardjp)

Re: [openstack-dev] [tc][all] Discussing goals (upgrades) with community @ office hours

On Sat, 2018-10-13 at 15:04 +0200, Mohammed Naser wrote: > I wanted to propose one of the upcoming office hours to perhaps > invite > some of the community members (PTL, developers, anyone!) as well as > the TC with goal champions to perhaps discuss some of these goals to > help everyone get a

Re: [openstack-dev] [tc] assigning new liaisons to projects

On Mon, 2018-10-08 at 10:27 -0400, Doug Hellmann wrote: > TC members, > > Since we are starting a new term, and have several new members, we > need > to decide how we want to rotate the liaisons attached to each our > project teams, SIGs, and working groups [1]. > > Last term we went through a

Re: [openstack-dev] [openstack-ansible] dropping xenial jobs

On Wed, 2018-10-10 at 06:50 +0200, Mohammed Naser wrote: > Hi everyone! > > So I’ve been thinking of dropping the Xenial jobs to reduce our > overall impact in terms of gate usage in master because we don’t > support it. > > However, I was a bit torn on this because i realize that it’s >

Re: [openstack-dev] [tc] bringing back formal TC meetings

On Fri, 2018-10-05 at 07:40 -0400, Doug Hellmann wrote: > Chris Dent writes: > > > On Thu, 4 Oct 2018, Doug Hellmann wrote: > > > > > TC members, please reply to this thread and indicate if you would > > > find > > > meeting at 1300 UTC on the first Thursday of every month > > > acceptable, and

Re: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the lists!

Agreed with the merge.  null__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] ?==?utf-8?q? ?==?utf-8?q? [infra] Gerrit User Summit, November 2018

n/mailman/listinfo/openstack-dev Good catch! When I read your email, I assume you won't be going? Palo Alto is indeed not very close to Europe and it's indeed a long trip for a two day effort. Maybe there is someone closer that

Re: [openstack-dev] ?==?utf-8?q? ?==?utf-8?q? [helm] multiple nova compute nodes

> > The nova-compute pods are part of a daemonset which will automatically > create a nova-compute pod on each node that has the > "openstack-compute-node=enabled" label. > Hello, Should we add this in the documentation, maybe with an architecture diagram? Rega

Re: [Openstack-operators] Best kernel options for openvswitch on network nodes on a large setup

Thank you, I will try it next week (since today is Friday) and update this thread if it has fixed my issues. We are indeed using the latest RDO Pike, so ovsdbapp 0.4.3.1 . Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 28 s

Re: [Openstack-operators] Best kernel options for openvswitch on network nodes on a large setup

r, I don’t think it’s max open file since the number of open files is nowhere close to what I’ve set it. Ideas? Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 26 sept. 2018 à 15:16, Jean-Philippe Méthot > a écrit : >

Re: [Openstack-operators] Best kernel options for openvswitch on network nodes on a large setup

constantly under load. Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 26 sept. 2018 à 11:48, Simon Leinen a écrit : > > Jean-Philippe Méthot writes: >> This particular message makes it sound as if openvswitch is getting

Re: [Openstack-operators] Best kernel options for openvswitch on network nodes on a large setup

almost instantly though. I’ve done some research about that particular message, but it didn’t give me anything I can use to fix it. Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 25 sept. 2018 à 19:37, Erik McCormick a éc

[Openstack-operators] Best kernel options for openvswitch on network nodes on a large setup

and thus minimize the impact of such an attack, or whatever it was. Best regards, Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. ___ OpenStack-operators mailing list OpenStack-operators

Re: [openstack-dev] ?==?utf-8?q? ?==?utf-8?q? [docs] Nominating Ian Y. Choi for openstack-doc-core

> > > > Based on our PTG discussion, I'd like to nominate Ian Y. Choi for > > membership in the openstack-doc-core team. I think Ian doesn't need an > > introduction, he's been around for a while, recently being deeply involved > > in infra work to get us robust support for project team docs

[Openstack-operators] Network metadata+userdata and rate limits

receive metadata? We currently use Pike on centos 7. Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http

Re: [Openstack-operators] Open letter/request to TC candidates (and existing elected officials)

setting up the right processes. I'd be happy to discuss that with you to have a real/more complete understanding of what you mean there. Jean-Philippe Evrard (evrardjp) ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

ing that box right now :D Best regards, Jean-Philippe Evrard (evrardjp) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe h

[openstack-dev] [election][tc] Opinion about 'PTL' tooling

of OpenStack. Thanks for reading me, and do not hesitate to ask me questions on the mailing lists, or in real life during the PTG! Regards, Jean-Philippe Evrard (evrardjp) [1]: https://git.openstack.org/cgit/openstack/election/plain/candidates/stein/TC/jean-phili...@evrard.me

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

t: I would like to be there to help shaping the community together, with your help. Thank you for your consideration, Jean-Philippe Evrard (evrardjp) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] ?==?utf-8?q? [openstack-ansible] Stepping down from OpenStack-Ansible core

s, change of testing!), and always there when we needed you. I'd like to thank you for your work. I wish you all the best for your new role, and hope our paths will cross again soon! Best regards, Jean-Philippe Evrard (evrardjp) ___

Re: [Openstack-operators] ?==?utf-8?q? [openstack-ansible] configuration file override

s are named compute1, compute2, ... Maybe a cleanup of your environment and redeploy would help you? I am not sure to have enough information to answer you there. Best regards, Jean-Philippe Evrard (evrardjp) ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [openstack-dev] ?==?utf-8?q? [kolla][project?==?utf-8?q? navigator] kolla missing in project navigator

nd upgrade of the openstack cloud. Therefore, shouldn't OSA also be listed in the "Deployment / Lifecycle Tools"? Best regards, Jean-Philippe Evrard (evrardjp) __ OpenStack Development Mailing List (not for usage questions)

Re: [Openstack-operators] ?==?utf-8?q? [openstack-ansible] configuration file override

and it will apply on all your nodes. If you want to be more surgical, you'd have to give more details about your OpenStack-Ansible version and what you're trying to achieve. Regards, Jean-Philippe Evrard (evrardjp) ___ OpenStack-operators mailing

[openstack-dev] [openstack-ansible][ptg] PTG etherpad planning.

it on the etherpad, and we'll run the session remotely if we can. Note: There will be the now traditional team photos and dinner too :) Regards, Jean-Philippe Evrard (evrardjp) [1]: https://etherpad.openstack.org/p/osa-stein-ptg

Re: [openstack-dev] ?==?utf-8?q? PTG Denver Horns

On Wednesday, August 08, 2018 16:12 CEST, Jeremy Stanley wrote: > On 2018-08-08 06:51:27 -0500 (-0500), David Medberry wrote: > > So basically, we have added "sl" to osc. Duly noted. > > > > (FWIW, I frequently use "sl" as a demo of how "live" a VM is during live > > migration. The train

Re: [Openstack-operators] ?==?utf-8?q? Openstack Ansible ODL+OvS+SFC

, like a regular ansible ini inventory. Hope it helps. Jean-Philippe Evrard (evrardjp) [1]: https://docs.openstack.org/openstack-ansible/latest/reference/inventory/inventory.html On Thursday, August 02, 2018 11:23 CEST, nico...@lrasc.fr wrote: > Hi Openstack community ! > > I have a

[Openstack-operators] [openstack-ansible] Change in our IRC channel

not that hard to register! [1]). The conversations will be easier to follow though. You can still contact us on the mailing lists too. Regards, Jean-Philippe Evrard (evrardjp) [0]: https://freenode.net/news/spambot-attack [1]: https://freenode.net/kb/answer/registration

[openstack-dev] [openstack-ansible] Change in our IRC channel

not that hard to register! [1]). The conversations will be easier to follow though. You can still contact us on the mailing lists too. Regards, Jean-Philippe Evrard (evrardjp) [0]: https://freenode.net/news/spambot-attack [1]: https://freenode.net/kb/answer/registration

[openstack-dev] [openstack-ansible] Proposing Jonathan Rosser as core reviewer

remember the storage backend conversations for lxc/systemd-nspawn!), and I'd like this positive trend to continue. On top of it Jonathan has been recently reviewing quite a series of patches, and is involved into some of our important work: bringing the Bionic support. Best regards, Jean-Philippe

[openstack-dev] [openstack-ansible] Using jmespath more

== 'source' I hope this will inspire people to refactor some tedious to read tasks into more readable ones. Thanks for your contributions! Best regards, Jean-Philippe Evrard (evrardjp) [1]: https://etherpad.openstack.org/p/osa-readability-test ___

Re: [openstack-dev] [charms] PTL non-candidacy for Stein cycle

On July 27, 2018 4:09:04 PM UTC, James Page wrote: >Hi All > >I won't be standing for PTL of OpenStack Charms for this upcoming >cycle. > >Its been my pleasure to have been PTL since the project was accepted >into >OpenStack, but its time to let someone else take the helm. I'm not >going

Re: [openstack-dev] ?==?utf-8?q? Lots of slow tests timing out jobs

> > [3] https://ethercalc.openstack.org/dorupfz6s9qt > > -gmann > We have a similar observation in openstack-ansible. It is painful. Recently something that passed gates without rechecks (but close to timeout) took 14 (timeouts) rechecks to get in. In OSA, we will be start

[openstack-dev] [openstack-ansible] PTL non-candidacy

friendliness... I am glad of the work we achieved, and I think it's time for a fresh view with a new PTL. Thanks for being an awesome community. Jean-Philippe Evrard (evrardjp) *Please join! 4PM UTC in #openstack-ansible

Re: [openstack-dev] [sig][upgrades][ansible][charms][tripleo][kolla][airship] reboot or poweroff?

Sorry about the lack of participation too. Monthly sounds good. Regards, JP On July 24, 2018 9:34:56 AM UTC, Paul Bourke wrote: >Hi James, > >Sorry to hear about the lack of participation. I for one am guilty of >not taking part, there just seems to be never enough time in the day to > >cram

Re: [openstack-dev] [docs][all] Front page template for project team documentation

Is there a lint tool that can catch incoherent markup at a global project level (vs at a page gen level)? Any tool to catch these issues would help. JP. On July 19, 2018 3:55:29 PM UTC, Petr Kovar wrote: >Hi all, > >A spin-off discussion in https://review.openstack.org/#/c/579177/ >resulted

[Openstack-operators] Cinder-volume and high availability

. In such a configuration, would I still need to have only one cinder-volume service running at a time? Also, the backend is a Dell compellent SAN, if that makes a difference. Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc

[Openstack-operators] Storage concerns when switching from a single controller to a HA setup

their block device. I know this issue doesn’t happen on Ceph, so I’ve been wondering, is this a limitation of Openstack or the SAN driver? Also, is there actually a way to reach even active-passive high availability with this current storage solution? Jean-Philippe Méthot Openstack system

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

This title seems very scary. It was to be read as "... for source installs" : ) To be honest, I feel very sad about the lack of involvement in CentOS in OSA over the years. We didn't get many contributors over time for it. This has always been a labour of love, and the honeymoon seems over for

Re: [openstack-dev] [tc] [all] TC Report 18-26

My two cents: > I think if OpenStack wants to gain back some of the steam it had before, it > needs to adjust to the new world it is living in. This means: > * Consider abolishing the project walls. They are driving bad architecture > (not intentionally but as a side affect of structure) As

Re: [openstack-dev] [tc] [ptl] PTL E-mail addresses on rendered team pages

> Not sure it'd help but one option we do is to create aliases based on > the title. Though since the PTLs don't have addresses on the openstack > domain an alias may not make as much sense, it'd have to be a full > account forward. It's useful for centralized spam filtering. I foresee this: 1)

Re: [openstack-dev] [tc] [summary] Organizational diversity tag

I think PTLs would naturally like to have those updated, and for me a TC +w would make sense. But we need to have guidelines, so that's it's more tangible, and the subtlety stays impartial. __ OpenStack Development Mailing

[Openstack-operators] [openstack-ansible] Restarting our very own "SIG" teams

Please don't hesitate to edit this etherpad, adding your new special interest group, or simply joining an existing one if you have spare cycles! Thank you! Jean-Philippe Evrard (evrardjp) [1]: https://etherpad.openstack.org/p/osa-liaisons ___ OpenStack-op

[openstack-dev] [openstack-ansible] Restarting our very own "SIG" teams

Please don't hesitate to edit this etherpad, adding your new special interest group, or simply joining an existing one if you have spare cycles! Thank you! Jean-Philippe Evrard (evrardjp) [1]: https://etherpad.openstack.org/p/osa-liaisons __

Re: [openstack-dev] [tc] [summary] Organizational diversity tag

> - Drop tags, write a regular report instead that can account for the > subtlety of each situation (ttx). One issue here is that it's obviously a > lot more work than the current situation. That's what I'd prefer personally. We have a website with a nice project navigator now [1]. This is

Re: [openstack-dev] [all] [release] How to handle "stable" deliverables releases

Option 2 for me. And the option switch to independant is IMO just fine. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [Openstack-operators] [openstack-ansible][releases][governance] Change in OSA roles tagging

> Right, you can set the stable-branch-type field to 'tagless' (see > http://git.openstack.org/cgit/openstack/releases/tree/README.rst#n462) and > then set the branch location field to the SHA you want to use. Exactly what I thought. > If you would be ready to branch all of the roles at one

Re: [openstack-dev] [Openstack-operators] [openstack-ansible][releases][governance] Change in OSA roles tagging

> Right, you can set the stable-branch-type field to 'tagless' (see > http://git.openstack.org/cgit/openstack/releases/tree/README.rst#n462) and > then set the branch location field to the SHA you want to use. Exactly what I thought. > If you would be ready to branch all of the roles at one

Re: [Openstack-operators] Switching from Fuel to OpenStack-Ansible

flows. Don't hesitate to join us on our IRC channel for more detailed questions, on freenode #openstack-ansible. If you want to continue by email, don't hesitate to put [openstack-ansible] in the email title :) Best regards, Jean-Philippe Evrard (evrardjp

[Openstack-operators] [openstack-ansible][releases][governance] Change in OSA roles tagging

lease file, similar to it. What I would like to have, from this email, is: 1. Raise awareness to all the involved parties; 2. Confirmation we can go ahead, from a governance standpoint; 3. Confirmation we can still benefit from this automatic branch tooling. Thank you in advance. Jean-Phili

[openstack-dev] [openstack-ansible][releases][governance] Change in OSA roles tagging

lease file, similar to it. What I would like to have, from this email, is: 1. Raise awareness to all the involved parties; 2. Confirmation we can go ahead, from a governance standpoint; 3. Confirmation we can still benefit from this automatic branch tooling. Thank you in advance. Jean-Phili

Re: [openstack-dev] [tc] Organizational diversity tag

This would be, IMO, good enough to promote/declare diversity after the facts (and is an answer to the "what happened during the cycle"). Jean-Philippe Evrard (evrardjp) __ OpenStack Development Mailing List (not

Re: [openstack-dev] [docs][openstack-ansible]

Can't. use. words. Much sadness! But happiness for you and your future, at the same time :) It was a pleasure to work on your side. https://media.giphy.com/media/IcGkqdUmYLFGE/giphy.gif __ OpenStack Development Mailing List

Re: [Openstack-operators] New project creation fails because of a Nova check in a multi-region cloud

> Le 11 mai 2018 à 08:36, Matt Riedemann <mriede...@gmail.com> a écrit : > > On 5/10/2018 6:30 PM, Jean-Philippe Méthot wrote: >> 1.I was talking about the region-name parameter underneath >> keystone_authtoken. That is in the pike doc you linked, but I am unawa

Re: [Openstack-operators] New project creation fails because of a Nova check in a multi-region cloud

>> >>> I currently operate a multi-region cloud split between 2 geographic >>> locations. I have updated it to Pike not too long ago, but I've been >>> running into a peculiar issue. Ever since the Pike release, Nova now >>> asks Keystone if a new project exists in Keystone before configuring

[Openstack-operators] New project creation fails because of a Nova check in a multi-region cloud

the code for the Nova check) Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman

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

stone" towards both python2 and python3. I am not sure this answers your question, as this is more gray than a black or white answer. But I am hoping we'll stabilize python3 this cycle, for ubuntu 18.04 at least, and other distros as a stretch goal. Best regards, Jean-Phili

Re: [openstack-dev] [openstack-ansible] Implement rotations for meetings handling

, but one step at a time :) Best regards, Jean-Philippe Evrard (evrardjp) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

[openstack-dev] [openstack-ansible] Implement rotations for meetings handling

for your understanding. Jean-Philippe Evrard (evrardjp) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin

Re: [openstack-dev] [OpenStackAnsible] Tag repos as newton-eol

Hello, > I'd like to phase out openstack/openstack-ansible-tests and > openstack/openstack-ansible later. Now that we had the time to bump the roles in openstack-ansible, and adapt the tests, we can now EOL the rest of newton, i.e.: openstack/openstack-ansible and

Re: [Openstack-operators] Strange behaviour change in cinder with a Dell compellent backend

that was in-use previously. That was my main concern and now it does make the process of fixing this simpler. Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 25 avr. 2018 à 00:22, Sean McGinnis <sean.mcgin...@gmx.com> a écrit :

[openstack-dev] [openstack-ansible] Proposing Mohammed Naser as core reviewer

to safeguard the existing and future work about CentOS and help grow the maintenance community for it. [1] http://stackalytics.com/?module=openstackansible-group_id=mnaser=rocky=person-day Best regards, Jean-Philippe Evrard IRC: evrardjp

[Openstack-operators] Strange behaviour change in cinder with a Dell compellent backend

in the SAN has changed? Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman

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

That's very cool. Any idea of the repartition of nodes xenial vs bionic? Is that a very restricted amount of nodes? On 20 April 2018 at 00:37, Paul Belanger wrote: > Greetings, > > With ubuntu-bionic release around the corner we'll be starting discussions > about >

Re: [openstack-dev] [openstack-ansible] Problems with Openstack services while migrating VMs

Maybe worth posting on operators, but it looks like the scheduling of the action fails, which let me think that nova is not running fine somewhere. Why is the restart in a random order? That can cause issues, and that's the whole reason why we are orchestrating the deploys/upgrade with ansible.

[Openstack-operators] Fwd: [openstack-ansible] We need to change!

to merge. It makes the reduction of technical debt easier. Really thank you for your understanding. Best regards, Jean-Philippe (evrardjp) [1]: http://zuul.openstack.org/builds.html?pipeline=periodic=openstack%2Fopenstack-ansible ___ OpenStack

[openstack-dev] [openstack-ansible] We need to change!

for your understanding. Best regards, Jean-Philippe (evrardjp) [1]: http://zuul.openstack.org/builds.html?pipeline=periodic=openstack%2Fopenstack-ansible __ OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [openstack-ansible] Stepping down from OpenStack-Ansible core

Hello, Ahah, gate job breakages? You were the first to break them, but also willing to step in to fix them as soon as you knew. And that's the part I will remember the most. You will be missed, Major. Your next team is lucky to have you! It was a pleasure working with you. And the gifs, omagad!

Re: [openstack-dev] [stable][release] Remove complex ACL changes around releases

LGTM __ 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

[openstack-dev] [OpenStack-Ansible] Vancouver forum etherpad

. [1]: https://etherpad.openstack.org/p/YVR-openstack-ansible-brainstorming Best regards, Jean-Philippe. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

Re: [openstack-dev] [charms] [tripleo] [puppet] [fuel] [kolla] [openstack-ansible] [cloudcafe] [magnum] [mogan] [sahara] [shovel] [watcher] [helm] [rally] Heads up: ironic classic drivers deprecation

Hello, Thanks for the notice! JP On 16 March 2018 at 12:09, Dmitry Tantsur wrote: > Hi all, > > If you see your project name in the subject that is because a global search > revived usage of "pxe_ipmitool", "agent_ipmitool" or "pxe_ssh" drivers in > the non-unit-test

Re: [openstack-dev] [ALL][PTLs] Community Goals for Rocky: Toggle the debug option at runtime

Thanks! On 16 March 2018 at 16:56, Doug Hellmann <d...@doughellmann.com> wrote: > Excerpts from Jeremy Stanley's message of 2018-03-16 13:43:00 +: >> On 2018-03-16 08:34:28 -0500 (-0500), Sean McGinnis wrote: >> > On Mar 16, 2018, at 04:02, Jean-Philippe Evrard

Re: [openstack-dev] [ALL][PTLs] Community Goals for Rocky: Toggle the debug option at runtime

Hello, For OpenStack-Ansible, we don't need to do anything for that community goal. I am not sure how we can remove our name from the storyboard, so I just inform you here. Jean-Philippe Evrard (evrardjp) On 28 February 2018 at 05:27, ChangBo Guo <glongw...@gmail.com> wrote: > Hi AL

Re: [openstack-dev] [infra][all] Anyone using our ubuntu-mariadb mirror?

Hello, We were using it until a couple of weeks ago, when 10.1.31 got out. 10.1.31 got issues with clustering and we moved to use a mirror of 10.1. (here 10.1.30), instead of 10.1. We haven't decided if we'll move back to 10.1 when 10.1.32 will be out. You can remove it for now, I think we can

Re: [openstack-dev] OpenStack Ansible Disk requirements [docs] [osa]

, ephemeral storage... Will commit a patch today. Best regards, Jean-Philippe Evrard On 15 March 2018 at 18:31, Gordon, Kent S <kent.gor...@verizonwireless.com> wrote: > Compute host disk requirements for Openstack Ansible seem high in the > documentation. > > I think I have us

Re: [openstack-dev] [OpenStackAnsible] Tag repos as newton-eol

Looks good to me. On 15 March 2018 at 01:11, Tony Breeds <t...@bakeyournoodle.com> wrote: > On Wed, Mar 14, 2018 at 09:40:33PM +0000, Jean-Philippe Evrard wrote: >> Hello folks, >> >> The list is almost perfect: you can do all of those except >> openstack/ope

Re: [openstack-dev] [OpenStackAnsible] Tag repos as newton-eol

Hello folks, The list is almost perfect: you can do all of those except openstack/openstack-ansible-tests. I'd like to phase out openstack/openstack-ansible-tests and openstack/openstack-ansible later. JP On 14 March 2018 at 21:20, Tony Breeds wrote: > Hi all, > JP

Re: [openstack-dev] [openstack-ansible] Meetings change (PTG discussion follow-up)

> think that's a good alternative but the conversations still need to take > place and as many people involved as possible. What about having office > hours? > > Amy (spotz) > > On Tue, Mar 6, 2018 at 9:51 AM, Jean-Philippe Evrard > <jean-phili...@evrard.me> wrote: >&

[openstack-dev] [openstack-ansible] Meetings change (PTG discussion follow-up)

Hello, During the PTG, we've discussed about changing our meetings. I'd like to have a written evidence in our mailing lists, showing what we discussed, and what we proposed to change. I propose we validate those changes if they get no opposition in the next 7 days (deadline: 13 March). What we

[openstack-dev] [openstack-ansible] Roles not passing functional tests

to unmaintained, and will eventually be removed from release. Thank you for your understanding, Jean-Philippe Evrard (evrardjp) [1]: https://docs.openstack.org/openstack-ansible/latest/contributor/additional-roles.html#maturity-downgrade-procedure [2]: https://bugs.launchpad.net/openstack-ansible

[openstack-dev] [openstack-ansible][ptl] PTL candidacy for Rocky

g the time to read this and I hope to see you in Dublin, Jean-Philippe Evrard (evrardjp) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs

Re: [openstack-dev] [openstack-ansible] Limiting pip wheel builds for OpenStack clients

I added my comment/opinion on the bug. Thanks for reporting this, Major! __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [Openstack-operators] Inverted drive letters on block devices that use virtio-scsi

or migration. Probably better to wait before I start converting my multi-disk instances to virtio-scsi. If I am not mistaken, this should also be an issue in Pike and master, right? Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 26 janv. 2

Re: [Openstack-operators] Inverted drive letters on block devices that use virtio-scsi

it be as easy as changing the drive order in the database? Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. > Le 26 janv. 2018 à 13:06, Logan V. <lo...@protiumit.com> a écrit : > > https://bugs.launchpad.net/nova/+bug/17

[Openstack-operators] Inverted drive letters on block devices that use virtio-scsi

Hi, Lately, we’ve been converting our VMs block devices (cinder block devices) to use the virtio-scsi driver instead of virtio-blk by modifying the database. This works great, however, we’ve run into an issue with an instance that has more than one drive. Essentially, the root device has

[Openstack-operators] Converting existing instances from virtio-blk to virtio-scsi

this in the openstack database? What parameters would I need to change? Is there an easier, less likely to break everything way? Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc. ___ OpenStack-operators mailing

Re: [openstack-dev] [all] Switching to longer development cycles

On 13 December 2017 at 16:52, Matt Riedemann wrote: > On 12/13/2017 10:17 AM, Thierry Carrez wrote: >> >> Hi everyone, >> >> Over the past year, it has become pretty obvious to me that our >> self-imposed rhythm no longer matches our natural pace. It feels like we >> are

Re: [openstack-dev] [all] Switching to longer development cycles

On 13 December 2017 at 16:49, Jeremy Stanley wrote: > On 2017-12-13 16:45:14 + (+), Chris Jones wrote: > [...] >> For me the first thing that comes to mind with this proposal, is >> how would the milestones/FF/etc be arranged within that year? > [...] > > Excellent

Re: [Openstack-operators] How to deal with MTU issue on routers servicing vxlan tenant networks? (openstack-ansible with LXC containers)

> Hey Jean-Philippe, > > No, after I disasterously split-brained/partitioned my rabbitmq and galera > clusters by allowing LXC to start the containers up without the dnsmasq > process to address their eth0 interfaces (due to what _may_ be a > template/Xenial bug), I've spent the l

Re: [Openstack-operators] How to deal with MTU issue on routers servicing vxlan tenant networks? (openstack-ansible with LXC containers)

Hello David, Did you solve your issue? Did you check that it depends on the default container interface's mtu itself? Best regards, JP On 6 December 2017 at 18:45, David Young <dav...@funkypenguin.co.nz> wrote: > So.. > > On 07/12/2017 03:12, Jean-Philippe Evrard wrote:

Re: [openstack-dev] [E] [openstack-ansible] Cannot connect to proxy server from infra1-repo-container

your bridges on the host too? And your openstack_user_config.yml? When the repo-server gets installed, it installs a reverse proxy. All the nodes are then configured to use the repo server(s). So all the nodes need to r

Re: [Openstack-operators] How to deal with MTU issue on routers servicing vxlan tenant networks? (openstack-ansible with LXC containers)

ld work out of > the box. > > Agreed, that seems to be the case currently with 1500, I’d expect it to be > true with the updated value > > 6) If your instance is reaching its router with no mtu issue, you may > still have issues for the Northbound trafic. Check how you configure

Re: [openstack-dev] [all] Dublin PTG format

On 29 November 2017 at 03:20, Masayuki Igawa wrote: > On 11/28, Ghanshyam Mann wrote: >> Mon-Tue/Wed-Fri works as most suitable format. There are always >> conflict for many of us but that can be adjusted by working with team >> planning. >> >> Another thing can help is

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

On 29 November 2017 at 11:30, Thierry Carrez wrote: > Jimmy McArthur wrote: >> Thierry Carrez wrote: >>> Historically blog.o.o used to be our only blog outlet, so almost >>> anything would go in: >>> >>> "OpenStack Events Sponsorship Webinar" >>> "New Foundation Gold

Re: [Openstack-operators] Openstack release compatibility

Hello, OpenStack-Ansible Mitaka deploys Linux Bridge by default. This would still happen, but as said, it's not too big of a deal too. Best regards, Jean-Philippe (evrardjp) On 6 November 2017 at 08:10, Kevin Benton <ke...@benton.pub> wrote: > The Neutron OVS agent should not cause i

Re: [Openstack-operators] Openstack release compatibility

critical security updates for things like kernel? Just my 2 cents, it's probably good to have other opinions out there. Best regards, Jean-Philippe Evrard (evrardjp) On 3 November 2017 at 13:19, haad <haa...@gmail.com> wrote: > Hi, > > I have one additional question. What is

Re: [Openstack-operators] Openstack release compatibility

has been some > discussion around "skip-level" upgrades. > > Chris > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac

[Openstack-operators] [openstack-ansible] Sydney summit -- We'll be there!

oject Update" session. I am looking forward meeting all of you! Best regards, Jean-Philippe Evrard (evrardjp) PS: We have an etherpad listing all these activities and more details about the ops session here: https://etherpad.openstack.org/p/osa-sydney-summi

  1   2   >