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
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
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)
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
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
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
>
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
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
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
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
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
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
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
> 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)
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
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
__
> - 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
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
> 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
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
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
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
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
, 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
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
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
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
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
>
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.
Dear community,
Starting at the end of this month, I won't be able to work full time
on OpenStack-Ansible anymore.
I want to highlight the following:
Our current way of working is not sustainable in the long run, as a lot
of work (and therefore pressure) is concentrated on a few individuals.
I
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!
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
Dear OpenStack-Ansiblers,
We've got an etherpad here [1], to track all the things we want to
discuss at the forum.
if you're an OpenStack-Ansible user, don't hesitate to add your
session ideas, list what you liked or disliked in the last release,
and share your experience!
Thank you in advance.
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
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
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
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
, 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
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
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
> 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:
>&
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
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
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
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
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
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
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
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
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
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
>> --
>>>> Emilien Macchi
>>>>
>>>>
>>>> __________
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe:
>>>> openstack-dev-re
hanks to the infra team for enabling this to happen today.
>
> Tony.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
sage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Hello,
Thanks Kendall and the elections team.
It looks the reminders have paid off :)
Best regards,
Jean-Philippe Evrar
peating this Pike trend. It looks
like Queens is better in terms of turnout (see the amazing positive
delta!). However, I can't help but noticing that the trend for
turnouts is slowly reducing (excluding some outliers) since the
beginning of these stats.
Any idea on how to improve that?
On top
To be as cool as nova, we'll find nicknames until then.
We can probably start with Kevin "Destroy of Clouds" Carter.
On 17 October 2017 at 15:28, Jean-Philippe Evrard
<jean-phili...@evrard.me> wrote:
> Hello,
>
> I'd be happy to have a room for OpenStack-Ansible.
>
&
Hello,
I'd be happy to have a room for OpenStack-Ansible.
I'll be there, and probably more ppl, like Kevin Carter(cloudnull) and
Amy Marrich(spotz).
Thanks!
On 17 October 2017 at 03:39, Jeffrey Zhang wrote:
> I am the speaker. Michal couldn't be Sydney this summit.
>
On 16 October 2017 at 12:27, Thierry Carrez wrote:
> Emilien Macchi wrote:
>> [...]
>> ## Proposal
>>
>> Proposal 1: create a new policy that fits for projects like installers.
>> I kicked-off something here: https://review.openstack.org/#/c/511968/
>> (open for feedback).
answer on this email or talk
to us on our irc channel #openstack-ansible.
If no contributor step forward for those roles, we'll have no choice
than to downgrade their maturity status during the next community
meeting.
Thank you for your understanding.
Best regards,
Jean-Philippe Evrard (evrardjp
, it's greatly rewarding (be ahead of bugs).
If you are interested, please contact me on IRC or answer this email.
Thank you.
Best regards,
Jean-Philippe Evrard (evrardjp)
__
OpenStack Development Mailing List (not for usage
in mind that daylight saving might apply to you this month,
for example in mainline Europe will be in "winter time" (that's how we
call it in french, please translate to whatever word applies to you!),
starting from the last weekend of October.
See you next week,
Best regards,
Jean-Phili
dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
Congratulations on the new job.
You'll be missed, for sure! Thanks for the work done.
Best regards,
Jean-Philippe Evrard (evrardjp)
ropose a follow-up patch.
In any case, I don't think it's a good idea to wait for things to
happen, and expect that uniformity will happen naturally. This is a
step in the right direction.
On top of that we are still early in
On Tue, Oct 3, 2017 at 7:52 PM, Sean McGinnis wrote:
> I'm hoping this will get a little more attention.
>
> We recently started discussing removing governance tags that did not have any
> projects asserting them. I think this makes a lot of sense. Some tags were
> defined
o
it's maybe worth waiting after
that for the next full rollout/roll-forward (whatever the term is!) to
avoid the overlap of critical events in the same timeframe.
Best regards,
Jean-Philippe Evrard (evrardjp)
__
OpenStack
On Tue, Oct 3, 2017 at 2:07 PM, Luigi Toscano wrote:
> On Tuesday, 3 October 2017 14:31:05 CEST Thomas Goirand wrote:
>> On 10/02/2017 02:04 PM, Luigi Toscano wrote:
>> > Why not? Even if it does not fix the issue for proper installations,
>> > - it does not provent people
in which you can regularily attend
OpenStack-Ansible meetings
Please give your irc nick too, that would help.
Thank you in advance.
Best regards,
Jean-Philippe Evrard (evrardjp)
[1] https://etherpad.openstack.org/p/osa-meetings-planification
Well, there are ppl already running OpenVSwitch on openstack-ansible,
so I guess it's just a question of a few bug fixes and adding a
scenario to make sure this is working forever :p
On Fri, Sep 29, 2017 at 8:22 AM, Gyorgy Szombathelyi
wrote:
>
>>
>> Hello
On Fri, Sep 29, 2017 at 11:16 PM, Mike Perez wrote:
> On 14:33 Sep 26, Anne Bertucio wrote:
>> Release marketing is a critical part of sharing what’s new in each release,
>> and we want to rework how the marketing community and projects work together
>> to make the release
Hello Michael,
On top of that, we intend to have a "role maturity" that will include
when the role was proposed and it's current maturity phase, for more
clarity, not unlike openstack project navigator.
Our os_trove role has not received many commits recently, and the
"maintenance mode" of Trove
Hello,
We currently don't have a full scenario for openvswitch for an easy
"one line" install.
It still deserves more love. You could come on our channel in
#openstack-ansible to discuss about it if you want. But the general
idea should be close to the same explained in the blog post.
Best
Hello guys,
I propose we have a team dinner at casey's this Thursday, at the PTG.
Could you please vote on the following poll, this way I can book?
https://framadate.org/zQPEvPGPOH1u2EU8
Thank you in advance.
Best regards,
JP
Hello,
The OpenStack-Ansible team will have a session to share feedbacks
about ansible 2.4 or ansible+python3.
Anyone welcomed to share their experience and give insights.
It will be on Wednesday 3:30 to 5pm.
See you there!
Best regards,
Jean-Philippe Evrard (evrardjp
Hello Emilien,
The Discussion room is a good idea. I like it.
Most of the OpenStack-Ansible crew will be available the whole week, so we
can even think of doing a conversation outside the Wed-Friday timeframe.
If you/we all have enough time, maybe we could organise two sessions,
probably with
Hello,
The variables documented in each of the roles defaults/ are generally what
you can consider a user level interface (i.e.: what you can modify), while
the variables from vars/ are generally what's best to avoid overriding.
We've been slowly phasing out variables insides templates, to
I'd be happy to join.
I don't think we have constraints on the schedule yet, and we can indeed
book slot(s).
Best regards,
JP.
On Thu, Aug 17, 2017 at 3:30 PM, Emilien Macchi wrote:
> Hey folks,
>
> As usual, we'll meet in Denver and I hope we can spend some time
>
experience in the larger community.
* Upgrade to Ansible 2.4.
I look forward to working with you all, and it would be my honor
to serve as PTL for the next cycle.
Best regards,
Jean-Philippe Evrard (evrardjp)
__
OpenStack Developme
Hello,
A few additions for/against firewalld, linked to ansible's firewalld
module: http://docs.ansible.com/ansible/latest/firewalld_module.html
+:
The module is built-in, so no need to ship it. It provides idempotency, and
is easy to use.
-:
The module is: "Not tested on any Debian based
Hello team,
We've talked about a few times in our channels about a bug smash.
I think it's time to do it:
- We have 9 bugs triaged as highly important
- We have 21 bugs of medium importance
- We have 30 bugs classified as low.
That's 60 bugs we've agreed to fix, ranging from "when convenient"
+1 Thanks for all the work!
On Tue, Jul 18, 2017 at 10:33 AM, Nicolas Bock <
nicolasbock.openst...@gmail.com> wrote:
> On Tue, Jul 18, 2017 at 10:23:46AM +0100, Andy McCrae wrote:
>
>> Following on from last week's meeting I'd like to propose Markos
>> (hwoarang)
>> for OSA core.
>>
>
> +1 !!
>
-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/mailman/listinfo/openstack
ther alternative.
Regards,
Fabrice
> Le 25 mai 2017 à 14:01, Jean-Philippe Evrard
<jean-philippe.evr...@rackspace.co.uk> a écrit :
>
> I doubt many people have tried this, because 1) cinder/nova/glance
probably do the job well in a multi-tenant fashion 2) you’
I doubt many people have tried this, because 1) cinder/nova/glance probably do
the job well in a multi-tenant fashion 2) you’re poking holes into your ceph
cluster security.
Anyway, if you still want it, you would need (I guess) have to create a
provider network that will be allowed to access
Hello everyone,
We’ll not have an openstack-ansible bug triage this week, as many of our
contributors are on the summit!
See you next week!
Best regards,
Jean-Philippe Evrard
(@)evrardjp
Rackspace Limited is a company registered in England & Wales (com
Hey,
My two cents.
JP
On 04/04/2017, 13:39, "Monty Taylor" wrote:
Hey all!
I woke up early this morning and found myself thinking "I clearly don't
have enough work on my plate, why don't I add some more?"
I'd love to make a gate job that:
- Deploys
Hello,
Great!
+1
Best regards,
JP
From: Jesse Pretorius
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, 3 February 2017 at 13:33
To: "OpenStack Development Mailing List (not for usage
Hello,
Ofc it’s a +1!
Thanks Amy for all the work :)
Best regards,
JP
From: Alexandra Settle
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, 27 January 2017 at 14:29
To: "OpenStack Development
be happy to
understand how we’ll adapt http://governance.openstack.org/goals/index.html
into real life work usable for everyone.
Thanks for your clarifications.
Best regards,
Jean-Philippe Evrard
On 12/12/2016, 12:19, "Emilien Macchi" <emil...@redhat.com> wrote:
On Tue, N
s/COBOL/go/g and it makes your comment even funnier.
Best regards,
JP
On 13/12/2016, 00:00, "Jay Pipes" wrote:
On 12/12/2016 06:40 PM, Nick Chase wrote:
> OK, so if you were putting together New Year's Resolutions for OpenStack
> development for 2017, what would
Hello,
Is this a greenfield newton?
Could you wget your
http://172.16.1.2:8181/os-releases/14.0.1/requirements_constraints.txt file
reliably?
Are you using haproxy? Are all the backends OK there?
Don’t hesitate to come by our irc channel, it’s probably easier to have a
conversation there.
to see in haproxy.
I have an etherpad set up, and I’d be happy if you could fill your comments
there:
https://etherpad.openstack.org/p/openstack-ansible-haproxy-improvements
Thank you in advance.
Best regards,
Jean-Philippe Evrard (evrardjp)
Rackspace Limited
spamming here.
Thank for your help!
Best regards,
Jean-Philippe Evrard
[1] https://etherpad.openstack.org/p/openstack-ansible-inventory-ideas
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
92 matches
Mail list logo