; Matt
> --
> Matthew Booth
> Red Hat OpenStack Engineer, Compute DFG
>
> Phone: +442070094448 (UK)
>
> ___
> OpenStack-operators mailing list
> openstack-operat...@lists.openstack.org
> http:
tp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Mohammed Naser — vexxhost
-
D. 514-316-8872
D. 800-910-1726 ext. 200
E. mna...@vexxhost.com
W. http://vexxhost.com
i-bin/mailman/listinfo/openstack-dev
>>
>
>
> --
> Emilien Macchi
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu
Hi everyone,
Due to most of us being at the OpenStack Summit, we're cancelling the
meeting tomorrow.
Thanks everyone and see you in Berlin.
Regards,
Mohammed
--
Mohammed Naser — vexxhost
-
D. 514-316-8872
D. 800-910-1726 ext. 200
E
On Wed, Nov 7, 2018 at 2:07 PM Dr. Jens Harbott (frickler)
wrote:
>
> 2018-11-07 12:47 GMT+00:00 Mohammed Naser :
> > On Wed, Nov 7, 2018 at 1:37 PM Doug Hellmann wrote:
> >>
> >> Corey Bryant writes:
> >>
> >> > On Wed, Oct 10, 2018 at 8:45 AM
__
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cg
On Mon, Nov 5, 2018 at 4:17 PM Matt Riedemann wrote:
>
> On 11/4/2018 4:22 AM, Mohammed Naser wrote:
> > Just for information sake, a clean state cloud which had no reported issues
> > over maybe a period of 2-3 months already has 4 allocations which are
> > incorrect and
Sent from my iPhone
> On Nov 5, 2018, at 10:19 AM, Thierry Carrez wrote:
>
> Monty Taylor wrote:
>> [...]
>> What if we added support for serving vendor data files from the root of a
>> primary URL as-per RFC 5785. Specifically, support deployers adding a json
>> file to .well-known/openstac
URL
magically disappears but shifting the responsibilities on the provider rather
than maintainers of this project is a much cleaner alternative, IMHO.
> Monty
>
> __
> OpenStack Development Mailing List (not for u
ring if this is a thing that's possible at the moment or if we
perhaps need to look into it.
Thanks,
Mohammed
--
Mohammed Naser — vexxhost
-
D. 514-316-8872
D. 800-910-1726 ext. 200
E. mna...@
ags changing in runtime?)
> * Regardless of what we do, I think we should probably *at least* make
> that refresh associations config allow 0 to disable it so CERN (and
> others) can avoid the need to continually forward-porting code to
> disable it.
+1
> [1]
> https://specs.op
up since it's related to the "why do we
> need provider aggregates in the compute?" question.
>
> * Regardless of what we do, I think we should probably *at least* make
> that refresh associations config allow 0 to disable it so CERN (and
> others) can avoid the need to c
I believe this project is a client for Storyboard, an OpenStack project and not
the commercial product you’re mentioning
Sent from my iPhone
> On Oct 31, 2018, at 11:39 PM, Krishna Jain wrote:
>
> Hi,
> I’m an animator with some coding experience picking up Python. I came across
> your python
For what it’s worth: I ran into the same issue. I think the problem lies a bit
deeper because it’s a problem with kombu as when debugging I saw that Oslo
messaging tried to connect and hung after.
Sent from my iPhone
> On Oct 31, 2018, at 2:29 PM, Thomas Goirand wrote:
>
> Hi,
>
> It took
___
> 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
--
Mohammed Naser — vexxhost
-
In echoing the words of everyone, it takes a tremendous amount of effort and
patience to lead this effort.
THANK YOU!
Sent from my iPhone
> On Oct 30, 2018, at 6:14 PM, Doug Hellmann wrote:
>
> "Ian Y. Choi" writes:
>
>> Hello,
>>
>> I got involved organizing & mentoring Korean people for
iew.openstack.org/#/c/604454/
> [3] https://review.openstack.org/#/c/600162/
>
> --
>
> Thanks,
>
> Matt
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstac
t; 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
--
Mohammed Naser — vexxhost
-
D
FYI: Thanks to Jesse, he has picked up this work and it's up here:
https://review.openstack.org/#/c/609329/6
On Wed, Oct 10, 2018 at 9:56 AM Jesse Pretorius
wrote:
>
> On 10/10/18, 5:54 AM, "Mohammed Naser" wrote:
>
> >So I’ve been thinking of dropping the Xen
Hi everyone:
I was going over our governance documents, more specifically this section:
"All project meetings are held in public IRC channels and recorded."
Does this mean that all official projects are *required* to hold their
project meetings over IRC? Is this a hard requirement or is this
so
Hi everyone!
It looks like we're not going to be able to have a TC meeting every 2
weeks as I had hoped for, the majority of the TC seems to want to meet
once every month. However, I wanted to ask if the community would be
interested in taking one of the upcoming office hours to discuss the
curre
s the community, I'd invite TC members to vote on the change
that they prefer! :)
- Weekly: https://review.openstack.org/#/c/609562/
- Monthly: https://review.openstack.org/#/c/608751/
Thank you!
Mohammed
--
Mohammed Naser — vexxhost
-
D.
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 possible for us
to write things and backport them only to find out that they’d
Hi everyone:
Our gates have unfortunately been blocked because of OpenSUSE failures
and Bionic timeouts, I have submitted a patch to set both to non
voting
Bionic: It seems to take a really long time for APT installs, I'm
investigating and thanks to fungi I hope to have an instance to get it
up a
On Oct 4 2018, at 1:40 pm, Doug Hellmann wrote:
>
> During the TC office hours today [1] we discussed the question of
> resuming having formal meetings of the TC to ensure we are in compliance
> with the section of the bylaws that says "The Technical Committee shall
> meet at least quarterly." [
-
> Chris Dent ٩◔̯◔۶ https://anticdent.org/
> freenode: cdent tw:
> @anticdent__
> OpenStack Development Mailing List (not for usage q
t (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Mohammed Naser — vexxhost
--
> 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
--
Mohammed Naser — vexxhost
s, however, far
> easier to bikeshed over which platform of choice.
>
> At present, it seems a collective presence is forming ad hoc,
> regardless of any such resolution. With some additional coordination
> and planning, I think that there could be something that could scale
> be
Sign me up too :)
Sent from my iPhone
> On Sep 16, 2018, at 6:06 PM, Zhipeng Huang wrote:
>
> Great to see the momentum going ! :)
>
> Another problem is that many people doesn't follow upstream so they are
> oblivious about the new features and cool things had been done in every
> cycle, a
I think something we should take into consideration is *what* you consider
health because the way we’ve gone about it over health checks is not something
that can become a toolkit because it was more of question asking, etc
Sent from my iPhone
> On Sep 10, 2018, at 6:29 AM, Rico Lin wrote:
>
e let me know if you have any difficulty accessing that link.
Also, it seems like a very loaded schedule however we're likely going
to have extra time here and there so it's very tentative :)
Thanks and look forward to seeing everyone!
Regards,
Mohammed
--
Mohammed N
Hi team:
We won't be conducting a meeting this week because of the PTG,
however, we'll be making an effort to try and allow/bring remote
access to those not at the PTG over this week.
Thanks everyone.
Regards,
Mohammed
__
O
anging the current
> agreed-to plan regarding the split.
>
> Is everyone okay with the above summary of the outcome?
I've dropped my -1 from this given the discussion
https://review.openstack.org/#/c/600157/
> --Dan
>
> _
P or port change). Am I
> remembering correctly that the catalog can get cached in various places
> such that much of nova would need a restart to notice?
We already have placement in the catalog and it's behind a load balancer
so changing the backends resolves things
On Wed, Sep 5, 2018 at 10:57 AM Matt Riedemann wrote:
>
> On 9/5/2018 8:47 AM, Mohammed Naser wrote:
> > Could placement not do what happened for a while when the nova_api
> > database was created?
>
> Can you be more specific? I'm having a brain fart here and n
man/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/
o the new one (not
> including the sqlalchemy-migrate versions table).
>
> --Dan
>
> ______
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj
Émilien:
I think you’re one of the role models of our community. Your leadership has
helped make it easier for me to become more involved from leading a project to
joining the TC.
Thank you again!
Regards,
Mohammed
Sent from my iPhone
> On Sep 4, 2018, at 10:11 PM, Emilien Macchi wrote:
Forgive me for barging into this, but just with my deployer and PTL of
a deployment project hat on..
As part of the split, wouldn't we *not* need to make a devstack change
if this is done correctly because placement will become a nova
dependency, which is pulled out of Git and when using Zuul, wil
__
> 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
--
Moham
Hi Chris,
This is an awesome effort. We can provide nested virt resources which are
leveraged by Kata at the moment.
Thanks!
Mohammed
Sent from my iPhone
> On Aug 21, 2018, at 6:38 PM, Chris Hoge wrote:
>
> As discussed at the Vancouver SIG-K8s and Copenhagen SIG-OpenStack sessions,
> we're
ns)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Mohammed Naser — vexxhost
-
D. 514-316-8872
D
est
> [2] http://git.openstack.org/cgit/openstack/openstack-ansible-os_tempest/
> [3]
> http://git.openstack.org/cgit/openstack/kolla-ansible/tree/ansible/roles/tempest
> [4] http://git.openstack.org/cgit/openstack/ansible-role-tripleo-tempest
>
> __
Hi Victoria,
Thank you so much for all your wonderful work especially around Outreachy! :)
Sincerely,
Mohammed
On Tue, Aug 7, 2018 at 7:47 PM, Victoria Martínez de la Cruz
wrote:
> Hi all,
>
> I'm reaching you out to let you know that I'll be stepping down as
> coordinator for OpenStack next ro
_
> 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
--
Mohammed Naser — vexxhost
--
Hi everyone,
Unfortunately, I've gotten busy with a few other projects over time
and I won't be able to run PTL for the upcoming Stein cycle.
I'd like to personally thank all of the current Puppet team due to
their help in on-boarding and helping me take on one of my first
leadership experiences
he project easier is extremely useful.
I hope to work with the team for the upcoming cycle.
Regards,
Mohammed
--
Mohammed Naser — vexxhost
-
D. 514-316-8872
D. 800-910-1726 ext. 200
E. mna...@vexxhost.com
W.
nstack.org/#/c/583947/
- designate Mohammed Naser as vice chair
https://review.openstack.org/#/c/583948/
Other approved changes:
- ansible-role-tripleo-zaqar had a typo which was fixed up
https://review.openstack.org/#/c/583636/
- added validation for repo names (because of the abo
Hi everyone:
This email is just to notify everyone on the TC and the community that
the change to remove the stable branch maintenance as a project
team[1] has been fast-tracked[2].
The change should be approved on 2018-07-28 however it is beneficial
to remove the stable branch team (which has be
Hi Paul:
On Thu, Jun 28, 2018 at 5:03 PM, Paul Belanger wrote:
> 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&#
Also, this is the change that drops it, so feel free to vote with your
opinion there too:
https://review.openstack.org/578887 Drop SELinux support from os_swift
On Thu, Jun 28, 2018 at 12:56 PM, Mohammed Naser wrote:
> Hi everyone:
>
> This email is to ask if there is anyone out ther
to deal with them
3) With the work currently in place to let OpenStack Ansible install
distro packages, we can rely on upstream `openstack-selinux` package
to deliver deployments that run with SELinux on.
Is there anyone opposed to removing it? If so, please let us know. :-)
Thanks!
Mohammed
Hi everyone:
While working with the OpenStack infrastructure team, we noticed that
we were having some intermittent issues where we wanted to identify a
theory if all VMs with this issue were landing on the same hypervisor.
However, there seems to be no way of directly accessing `hostId` from
ins
|
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstac
23 PM, Mohammed Naser wrote:
> Hi everyone:
>
> Over the past week in the summit, there was a lot of discussion
> regarding StarlingX
> and members of the technical commitee had a few productive discussions
> regarding
> the best approach to deal with a proposed new pilot proje
Hi everyone:
Over the past week in the summit, there was a lot of discussion
regarding StarlingX
and members of the technical commitee had a few productive discussions regarding
the best approach to deal with a proposed new pilot project for
incubation in the OSF's Edge
Computing strategic focus a
On Tue, May 29, 2018 at 10:43 AM, Artom Lifshitz wrote:
> I dunno, there's a fine line to be drawn between getting a finished
> product that looks unprofessional (because of typos, English mistakes,
> etc), and nitpicking to the point of smothering and being
> counter-productive. One idea would be
On Tue, May 29, 2018 at 7:59 AM, Thierry Carrez wrote:
> Mohammed Naser wrote:
>>
>> During the TC retrospective at the OpenStack summit last week, the
>> topic of the organizational diversity tag is becoming irrelevant was
>> brought up by Thierry (ttx)[1]. It seems
Hi everyone!
During the TC retrospective at the OpenStack summit last week, the
topic of the organizational diversity tag is becoming irrelevant was
brought up by Thierry (ttx)[1]. It seems that for projects that are
not very active, they can easily lose this tag with a few changes by
perhaps the
pient, you should not disseminate, distribute or copy this
> e-mail. Please notify the sender immediately and destroy all copies of this
> message and any attachments. WARNING: Computer viruses can be transmitted via
> email. The recipient should check this email and any attachments for
On Mon, May 7, 2018 at 9:52 AM, Doug Hellmann wrote:
> There is a patch to update the Python 3.5 goal for Kolla [1]. While
> I'm glad to see the work happening, the change adds a new deliverable
> to an old goal, and it isn’t clear whether we want to use that
> approach for tracking goal work inde
Tobias for your contributions!
>>
>> On Fri, Apr 27, 2018 at 8:21 AM, Iury Gregory wrote:
>>>
>>> +1
>>>
>>> On Fri, Apr 27, 2018, 12:15 Mohammed Naser wrote:
>>>>
>>>> Hi everyone,
>>>>
>>>> I'm proposing
On Wed, May 2, 2018 at 11:14 AM, Jean-Philippe Evrard
wrote:
> Hello everyone,
>
> Now that we are all part-time, I'd like to toy with a new idea,
> proposed in the past by Jesse, to rotate the duties with people who
> are involved in OSA, or want to get involved more (it's not restricted
> to cor
On Wed, May 2, 2018 at 9:16 AM, Boden Russell wrote:
> Back in 2016 we tagged neutron-lib as a "tc-approved-release" and as a
> result neutron-lib commits/reviews showed up on stackalytics under
> TC-approved Project Types.
>
> However as of recent that's seemed to have changed and neutron-lib
> c
Hi everyone,
I'm proposing that we add Tobias Urdin to the core Puppet OpenStack
team as they've been putting great reviews over the past few months
and they have directly contributed in resolving all the Ubuntu
deployment issues and helped us bring Ubuntu support back and make the
jobs voting aga
On Mon, Apr 23, 2018 at 10:06 AM, Doug Hellmann wrote:
> [This is meant to be one of (I hope) several conversation-provoking
> questions directed at prospective TC members to help the community
> understand their positions before considering how to vote in the
> ongoing election.]
>
> Over the las
tory to Puppet OpenStack[1][2][3]. I'm
> going to work on this module. Please review.
>
> [1]https://review.openstack.org/#/c/559537/
> [2]https://review.openstack.org/#/c/559539/
> [3]https://review.openstack.org/#/c/559563/
>
&g
On Fri, Mar 16, 2018 at 5:34 PM, Jeremy Stanley wrote:
> On 2018-03-16 21:22:51 + (+), Jim Rollenhagen wrote:
> [...]
>> It seems mod_wsgi doesn't want python applications catching SIGHUP,
>> as Apache expects to be able to catch that. By default, it even ensures
>> signal handlers do not
Major,
I've only recently had the chance to work with you more recently on
several projects but it's always been great to see the type of work
that you do. From seeing the work that you do inside OpenStack, to
your extremely informative blog and the talks you've given. You'll be
greatly missed i
On Thu, Mar 8, 2018 at 12:49 PM, Flint WALRUS wrote:
> Pretty easy, put the PTG online with a livestream on
> YouTube/Hangout/whatever platform that will then be saved and could even be
> watched later on!
+1
I think that we can work out a solution so that every room at the PTG
has a live stream
> On Jan 22, 2018, at 6:46 PM, Jay S Bryant wrote:
>
>
>
>> On 1/22/2018 5:09 PM, Matt Riedemann wrote:
>>> On 1/15/2018 11:04 AM, Kendall Nelson wrote:
>>> Election details: https://governance.openstack.org/election/
>>>
>>> Please read the stipulations and timelines for candidates and elect
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not f
Hi everyone,
I'll get right into the point.
At the moment, the Puppet OpenStack modules don't have much
contributors which can help maintain the Ubuntu support. We deploy on
CentOS (so we try to get all the fixes in that we can) and there is a
lot of activity from the TripleO team as well which
Hi Gary,
It looks like Gerrit is having some issues indeed and they are getting
worked on at the moment.
Thanks,
Mohammed
On Wed, Dec 20, 2017 at 8:00 AM, Gary Kotton wrote:
> Hi,
>
> Anyone else experience problems accessing gerrit?
>
> Thanks
>
> Gary
>
>
> ___
Jens,
That's quite an interesting catch. I'm reaching out to the author of
this change to get some more information.
Thanks,
Mohammed
On Tue, Nov 14, 2017 at 2:02 PM, Jens Harbott wrote:
> 2017-11-14 16:29 GMT+00:00 Mohammed Naser :
>> Hi everyone,
>>
>> Thank y
Hi everyone,
Thank you so much for the work on this, I'm sure we can progress with
this together. I have noticed that this only occurs in master and
never in the stable branches. Also, it only occurs under Ubuntu (so
maybe something related to mod_wsgi version?)
Given that we don't have any "ma
)
I would be really sad if we had to drop Ubuntu/Debian support because
we cannot test it. I think there are a lot of users out there using
it! I'd be more than happy to provide any assistance/information in
troubleshooting this.
Thank you,
Mohammed
On Thu, Nov 2, 2017 at 1:10 PM, Mohamm
Hi everyone,
With a few languages getting PTI jobs which are defined in
project-config, I think Puppet should be a candidate as the build and
release process of Puppet modules is the same across all modules.
Given that Puppet OpenStack has a large number of modules, in addition
to Infra's puppet
Sorry for the top post, looks like it was puppet-magnum that might be missing
adding “puppet” to its bindep file.
I’ll look into this shortly
Sent from my iPhone
> On Nov 13, 2017, at 9:57 AM, Doug Hellmann wrote:
>
> Excerpts from zuul's message of 2017-11-13 09:25:04 +:
>> Build failed
)
>
> I don't think that l3-agent trace is it, as the failure is coming from
> the API. It's actually a trace that's happening due to the async nature
> of how the agent runs arping, fix is
> https://review.openstack.org/#/c/507914/ but it only removes the log noise.
. The
other reason to eliminate config issues is the fact that this happens
intermittently (though, often enough that we had to switch it to
non-voting). If it was a config issue, it would constantly and always
fail.
Thank you Brian & Matthew for your help so far.
> -Brian
>
&g
Hi everyone,
I'm looking for some help regarding an issue that we're having with
the Puppet OpenStack modules, we've had very inconsistent failures in
the Xenial with the following error:
http://logs.openstack.org/47/514347/1/check/puppet-openstack-integration-4-scenario001-tempest-ubuntu-xe
On Fri, Oct 27, 2017 at 12:48 PM, Jeremy Stanley wrote:
> On 2017-10-26 22:26:59 -0400 (-0400), Mohammed Naser wrote:
> [...]
> > The use-case for us is that it helps us easily identify or find VMs which
> > we get any abuse reports for (or anything we see malicious traffic
On Thu, Oct 26, 2017 at 10:23 PM, Matt Riedemann
wrote:
> Nova has had this long-standing known performance issue if you're
> filtering a large number of instances by IP. The instance IPs are stored in
> a JSON blob in the database so we don't do filtering in SQL. We pull the
> instances out of t
rs,
> Arnaud.
>
> On 1 October 2017 at 17:27, Mohammed Naser wrote:
>
>> Hi everyone,
>>
>> As the Puppet modules CI is still in the process of getting plumbed
>> properly with Zuul v3, you'll notice many of your checks failing. If
>> you notice a jo
On Fri, Oct 13, 2017 at 1:21 PM, Emilien Macchi wrote:
> Alfredo has been doing an incredible work on maintaining Puppet
> OpenStack CI; by always testing OpenStack from trunk and taking care
> of issues. He has been involved in fixing the actual CI problems in
> OpenStack projects but also maint
On Thu, Oct 12, 2017 at 10:10 PM, Ed Leafe wrote:
> On Oct 12, 2017, at 8:10 PM, Mohammed Naser wrote:
>
>> I think that the OpenStack infrastructure team is doing a wonderful
>> job at keeping such a huge CI system working to the best of their
>> effort, however, I thin
On Thu, Oct 12, 2017 at 2:38 PM, 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?
This is great and the timing of this question is
k 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
--
Mohammed Naser — vexxhost
-
D. 514-31
On Thu, Oct 12, 2017 at 8:15 PM, Zane Bitter wrote:
> On 12/10/17 15:07, Mohammed Naser wrote:
>>
>> Hi Zane,
>>
>> Thank you for your question. I think you're raising a critical
>> question which we must all come to (fairly relative) agreement to so
>
Hi Zane,
Thank you for your question. I think you're raising a critical
question which we must all come to (fairly relative) agreement to so
that we can all build OpenStack in the same direction.
On Thu, Oct 12, 2017 at 12:51 PM, Zane Bitter wrote:
> (Reminder: we are in the TC election campaig
st of
luck to all other candidates.
Regards,
Mohammed Naser
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.o
t;> be considered.
>>
>> --
>>
>> Thanks,
>>
>> Matt
>>
>> ______
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...
Hi everyone,
As the Puppet modules CI is still in the process of getting plumbed
properly with Zuul v3, you'll notice many of your checks failing. If
you notice a job that has a legacy- prefix, it is probably not
migrated yet and will likely fail, therefore, I'd avoid a recheck to
avoid taking up
Hi Vega,
Please check the document. Some jobs were migrated with incorrect nodesets and
have to be switched to multinode in the job definition in openstack-zuul-jobs
Good luck
Mohammed
Sent from my iPhone
> On Sep 30, 2017, at 7:35 AM, Vega Cai wrote:
>
> Hi,
>
> In Tricircle we use the "mu
On Mon, Sep 18, 2017 at 3:04 PM, Alex Schultz wrote:
> Hey ops & devs,
>
> We talked about containers extensively at the PTG and one of the items
> that needs to be addressed is that currently we still deploy the
> services as bare metal services via puppet. For Queens we would like
> to switch th
Hi everyone,
Just a quick heads up that at the moment, there is an issue in the
TripleO CI which is in the process of being fixed at the moment:
https://bugs.launchpad.net/tripleo/+bug/1717545
As certain Puppet modules gate for TripleO, please don't recheck
changes that have failing jobs which s
Thank you for the kind words everyone! :)
On Tue, Sep 5, 2017 at 12:06 PM, Dmitry Tantsur wrote:
> I think it's not unreasonable to give core rights to the PTL :)
>
>
> On 09/05/2017 05:42 PM, Alex Schultz wrote:
>>
>> Hey folks,
>>
>> I'm writing to ask that we add mnaser to the cores list for t
On Tue, Sep 5, 2017 at 4:15 AM, Emil Enemærke wrote:
> Hi,
>
> I have stated using the puppet-ceph module for deploying ceph, and have
> noticed a heavy use of exec in fx define 'ceph::osd'
> (https://github.com/openstack/puppet-ceph/blob/master/manifests/osd.pp). Is
> there a reason for not writi
1 - 100 of 115 matches
Mail list logo
