ff. In this specific case, I don't personally see this proposal
helping us with Edge use cases in a meaningful way given the scope of
the changes. That's not to say there aren't other use cases that could
justify it
I won't be around to run the Edge squad meeting this week and next
week. If someone else wants to pick it up, that would be great.
Otherwise, consider it cancelled :). Thanks!
https://etherpad.openstack.org/p/tripleo-edge-squad-status
--
-- James S
ing of the task output per role after
each task finishes. This is mostly cosmetic, but using free does
create a lot more noisier output IMO.
--
-- James Slagle
--
__
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
uality and I think he would
> be a addition to the core team.
>
> What do you folks think?
+1
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-d
e
stacks and hopefully reduce the amount of time it takes to
create/update the ServiceChain stacks.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.
I won't be able to chair the edge squad meeting this week. Can anyone
take it over? If not, we'll pick it back up next week.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
U
something, please bring them up.
See everyone for the meeting. Thanks!
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
perators who are already accustomed to devops type
workflows. I think we could make these changes without it impact the
API too much or, hopefully, at all.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for
On Mon, Aug 20, 2018 at 4:47 PM James Slagle wrote:
> https://etherpad.openstack.org/p/tripleo-edge-squad-status
Several folks have signed up for the squad, so I've added a poll in
the etherpad to pick a meeting time.
> --
> -- James Slagle
> --
--
add something to the etherpad. Thanks.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack
ng Tuesday with the group.
https://etherpad.openstack.org/p/EdgeComputingGroupPTG4
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openst
hrough in person at the
upcoming Denver PTG.
I'm happy to help facilitate the squad. If you have any feedback on these ideas
or would like to join the squad, reply to the thread or sign up in the
etherpad:
https://etherpad.openstack.org/p/tripleo-edge-squad-status
I'm just refer
On Thu, Jul 26, 2018 at 4:58 AM, Samuel Monderer
wrote:
> Hi James,
>
> I understand the network-environment.yaml will also be generated.
> What do you mean by rendered path? Will it be
> "usr/share/openstack-tripleo-heat-templates/network/ports/"?
Yes, the rendered path is the path that the jinj
ment. See:
https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/custom_networks.html
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: o
till need to make changes (see points about distributed above).
Using the standalone deployment can help us quickly answer these
questions and develop a "Steel Thread"[1] to build upon.
Ultimately, this is the sort of high level designs and architectures
we are beginnin
shardy) that I've been testing with
split-controlplane:
https://review.openstack.org/#/c/521928/
https://review.openstack.org/#/c/521929/
https://review.openstack.org/#/c/581080/
I'll pull some docs together if I have some initial success.
--
-- James Slagle
--
__
h would be a new template that just consumes the default? Or
perhaps a symlink, although it was pointed out symlinks don't work in
swift containers. Still, that could possibly be addressed in our plan
upload workflows. Then the resource-re
ecial migrations, or could support the
existing method forever for upgrades, and only deprecate it for new
deployments.
I'd like to help with this work. I'll start by taking a look at what
you've got so far. Feel free to reach out if you'd like some
additional dev assistance or
s.openstack.org/openstack/tripleo-specs/specs/rocky/split-controlplane.html
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj
On Tue, Jun 12, 2018 at 11:03 AM, Jiří Stránský wrote:
> On 12.6.2018 15:06, James Slagle wrote:
>>
>> On Mon, Jun 11, 2018 at 3:34 PM, Wesley Hayutin
>> wrote:
>>>
>>> Greetings,
>>>
>>> I wanted to let everyone know that we have a
ure on several patches:
http://logs.openstack.org/59/571459/1/check/tripleo-ci-centos-7-scenario000-multinode-oooq-container-upgrades/8bbd827/logs/undercloud/home/zuul/overcloud_upgrade_run_Controller.log.txt.gz
Is this a known issue?
--
-- James Slagle
--
_
people will care to
> follow it though.
Yes, this sounds pretty reasonable to me.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openst
On Thu, Apr 26, 2018 at 10:24 AM, Dmitry Tantsur wrote:
> Answering to both James and Ben inline.
>
>
> On 04/25/2018 05:47 PM, Ben Nemec wrote:
>>
>>
>>
>> On 04/25/2018 10:28 AM, James Slagle wrote:
>>>
>>> On Wed, Apr 25, 2018 at 10:55 AM,
On Wed, Apr 25, 2018 at 10:55 AM, Dmitry Tantsur wrote:
> On 04/25/2018 04:26 PM, James Slagle wrote:
>>
>> On Wed, Apr 25, 2018 at 9:14 AM, Dmitry Tantsur
>> wrote:
>>>
>>> Hi all,
>>>
>>> I'd like to restart conversation on enab
t actions. And even that was not enabled
by default.
IMO, we need to keep "safe" defaults. Even if it means manually
documenting that you should clean to prevent the issues you point out
above. The alternative is to have no way to recover deleted nodes by
default.
--
-- James Slagle
ther tripleo repos for the patches
> related to upgrades (we trust people's judgement for reviews).
>
> As usual, we'll vote!
>
> Thanks everyone for your feedback and thanks Marius for your hard work and
> involvement in the project.
+1
--
-- James Slagle
--
_
On Thu, Apr 5, 2018 at 10:38 AM, James Slagle wrote:
> I've pushed up for review a set of patches to switch us over to using
> config-download by default:
>
> https://review.openstack.org/#/q/topic:bp/config-download-default
>
> I believe I've come up with the prop
On Thu, Apr 5, 2018 at 10:38 AM, James Slagle wrote:
> I've pushed up for review a set of patches to switch us over to using
> config-download by default:
>
> https://review.openstack.org/#/q/topic:bp/config-download-default
>
> I believe I've come up with the prop
couple of weeks.
--
-- James Slagle
--
__
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
wnload playbooks for
any given TripleO stack (openstack tripleo depoy?). This would be
possible when using deployed-server, noop'ing Neutron networks, and
using fixed IP's as those are the only OpenStack resources actually
created by Heat when using a full undercloud.
This would allow one t
default by the Rocky-1
milestone (April 16 - April 20), and I feel we're still on track to do
that.
If you'd like to help with this effort we're coordinating our work
with this etherpad:
https://etherpad.openstack.org/p/tripleo-config-download-squad-status
--
https://bluejeans.com/7754237859/
Optional pre-reading:
https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/ansible_config_download.html
The session will be recorded and later uploaded to Youtube at:
https://www.youtube.com/channel/UCNGDxZGwUELpgaBoLvABsTA
--
-- James S
want to add an item for the routed ctlplane work that landed
at the end of Queens. Afaik, that will need to be supported with the
containerized undercloud.
--
-- James Slagle
--
__
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
level status.
I'll set this up this week. If you plan to participate with this work,
please let me know.
[1]
https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/ansible_config_download.html
--
-- Ja
on) in
> overcloud-deploy role[3] depending on other features (like docker, ipv6,
> etc).
> The other is to set them in featureset[4] files for each job.
> The question is also which network templates we want to gate in CI and
> should it be the same we have by default in tripleo-quickstar
t; (tripleo-ci, t-q and t-q-e repos for now).
> Anyway, thanks a lot Wes for your hard work on CI, I think it's time
> to move on and get you +2 ;-)
>
> As usual, it's open for voting, feel free to bring any feedback.
> Thanks everyone,
+1
--
-- James Slagle
--
done quality reviews. She also has been working in the very intense rover
> role on the CI squad in the past CI sprint, and has done very well in that
> role.
+1
--
-- James Slagle
--
__
OpenStack Development Mai
ming. You may find that is an easier way of consuming the
standalone Ansible roles you've already done as opposed to trying to
make those fit into the composable services framework that uses t-h-t
in tree Ansible tasks.
--
-- James Slagle
--
On Fri, Nov 17, 2017 at 4:43 AM, Steven Hardy wrote:
> On Thu, Nov 16, 2017 at 4:56 PM, James Slagle wrote:
>> On Thu, Nov 16, 2017 at 8:44 AM, Flavio Percoco wrote:
>> What I'm trying to propose is a path towards deprecating the Heat
>> parameter/environment d
no Heat[1].
[0] https://slagle.fedorapeople.org/tripleo-ansible-arch.png
[1] Except for perhaps deployment of baremetal resources, but even
then I'm personally of the opinion that would be better serviced by
Mistral->Ansible->Ironic directly.
--
-- James Slagle
--
On Wed, Nov 8, 2017 at 7:16 AM, James Slagle wrote:
> On Wed, Nov 8, 2017 at 12:09 AM, Steven Hardy wrote:
>> Hi all,
>>
>> Today I had a productive hallway discussion with jtomasek and
>> stevebaker re $subject, so I wanted to elaborate here for the benefit
&g
as part of
the deployment. Right now, we have no such requirement, and are able
to drive a deployment with only an ephemeral Heat and
ansible-playbook, which is the basis of how undercloud deploy works.
--
-- James Slagle
--
__
O
installer. I also want to keep
> running Tempest.
> And of course, like we said, keep one multinode job to test overcloud
> workflow, and OVB with some adjustments.
>
> Is it good?
+1
--
-- James Slagle
--
_
of coverage around mistral and all of our workflows. Perhaps down the
road we could find ways to optimize that by using an ephemeral Mistral
(similar to the ephemeral Heat container), and then use a single node,
but we're not there yet.
On the other hand, if the goal is just to test le
we're happy with where we get to in queens with
config-download, we could consider making it the default.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-
unchpad.net/tripleo/+spec/ansible-config-download
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://list
On Thu, Sep 21, 2017 at 11:53 AM, Jiří Stránský wrote:
> On 21.9.2017 18:04, Marios Andreou wrote:
>>
>> On Thu, Sep 21, 2017 at 3:53 PM, Jiří Stránský wrote:
>>
>>> On 21.9.2017 12:31, Giulio Fidente wrote:
>>>
>>>> On 09/20/2017 07:36 PM, Jam
On Tue, Sep 19, 2017 at 8:37 AM, Giulio Fidente wrote:
> On 09/18/2017 05:37 PM, James Slagle wrote:
>> - The entire sequence and flow is driven via Mistral on the Undercloud
>> by default. This preserves the API layer and provides a clean reusable
>> interface for the CLI
OvercloudComputeNfvFlavor: baremetal
>
> ComputeNfvCount: 3
>
> HugePageSize: 2048
>
> HugePageCount: 4
>
>
>
Since you're setting use_hiera:True in the config, there should be a
hieradata file created for the config under /etc/puppet/hieradata o
ventual solutions that can interface with playbooks
(Mistral, AWX, cli, etc).
I don't imagine we'd do anything prohibitive that would prevent
someone from loading those playbooks into AWX if desired, or using
them directly from the cli. You just wouldn't be g
provide feedback
about this plan as it should still be considered open for discussion.
[1] http://lists.openstack.org/pipermail/openstack-dev/2017-July/119405.html
[2] https://slagle.fedorapeople.org/tripleo-ansible-arch.png
--
-- James Slagle
--
_
On Mon, Jul 24, 2017 at 3:12 AM, Marios Andreou wrote:
>
>
> On Fri, Jul 21, 2017 at 1:21 AM, James Slagle
> wrote:
>>
>> Following up on the previous thread:
>> http://lists.openstack.org/pipermail/openstack-dev/2017-July/119405.html
>>
>> I wanted to
On Thu, Jul 20, 2017 at 9:52 PM, James Slagle wrote:
> On Thu, Jul 20, 2017 at 9:04 PM, Paul Belanger wrote:
>> On Thu, Jul 20, 2017 at 06:21:22PM -0400, James Slagle wrote:
>>> Following up on the previous thread:
>>> http://lists.openstack.org/pipermail/openstac
On Thu, Jul 20, 2017 at 9:04 PM, Paul Belanger wrote:
> 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
ut much (any?) change
in tripleo-heat-templates. Although I'm not trying to say it'd be a
small amount of work to even do that, as this is a very rough
prototype.
--
-- James Slagle
--
__
OpenStack Develop
pleO that are a result of having to use OpenStack (OVB,
split-stack).
That's exactly why we are starting a discussion around using Ansible,
and is one of the fundamental changes that operators have been
requesting in TripleO.
--
-- James Slagle
--
___
On Fri, Jul 14, 2017 at 3:38 PM, Steven Dake wrote:
>
>
> On Fri, Jul 14, 2017 at 10:26 AM, James Slagle
> wrote:
>>
> James,
>
>>
>> Just to frame the conversation with a bit more context, I'm sure there
>> are many individual features/bugs/spe
erfectly valid
given that we are creating deployment tools. Part of the individual
value in each deployment project is the underlying tooling itself.
I think what TripleO is trying to do here is not immediately jump to a
solution that uses Helm and explore what alternatives exist. Even if
the projec
On Tue, Jul 11, 2017 at 5:53 PM, Steve Baker wrote:
>
>
> On Tue, Jul 11, 2017 at 3:37 AM, Lars Kellogg-Stedman
> wrote:
>>
>> On Fri, Jul 7, 2017 at 1:50 PM, James Slagle
>> wrote:
>>>
>>> There are also some ideas forming around pulling the A
On Tue, Jul 11, 2017 at 6:53 PM, Steve Baker wrote:
>
>
> On Tue, Jul 11, 2017 at 6:51 AM, James Slagle
> wrote:
>>
>> On Mon, Jul 10, 2017 at 11:37 AM, Lars Kellogg-Stedman
>> wrote:
>> > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle
>> > wrot
On Mon, Jul 10, 2017 at 2:54 PM, Giulio Fidente wrote:
> On 07/10/2017 07:06 PM, James Slagle wrote:
>> On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente wrote:
>>> splitstack though requires changes in how the *existing* openstack
>>> services are deployed and we didn
On Mon, Jul 10, 2017 at 11:37 AM, Lars Kellogg-Stedman wrote:
> On Fri, Jul 7, 2017 at 1:50 PM, James Slagle wrote:
>>
>> There are also some ideas forming around pulling the Ansible playbooks
>>
>> and vars out of Heat so that they can be rerun (or run initially)
>
On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente wrote:
> On 07/10/2017 03:19 PM, Steven Hardy wrote:
>> On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote:
>
> [...]
>
>> Yeah, I think the first step is to focus on a clean "split stack"
>> model where t
On Mon, Jul 10, 2017 at 9:19 AM, Steven Hardy wrote:
> On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote:
> Yeah so my idea with (4), and subsequent patches such as[1] is to
> gradually move the deploy steps performed to configure services (on
> baremetal and in containers) to a si
s an open proposal, any feedback is welcome.
+1
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.ope
On Fri, Jul 7, 2017 at 5:31 PM, David Moreau Simard wrote:
> On Fri, Jul 7, 2017 at 1:50 PM, James Slagle wrote:
>> (0) tripleo-quickstart which follows the common and well accepted
>> approach to bundling a set of Ansible playbooks/roles.
>
> I don't want to de-rail th
t offer some form of
migration tooling.
Thanks for your feedback.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubsc
a shot at
working on the prototype I mentioned in (5) if anyone would like to
collaborate around that.
I think if we can form some broad agreement before the PTG, we have a
chance at making some meaningful progress during Queens.
--
-- James Slagle
--
_
obs that is still not transitioned running on a few
> repos. We need to figure out if those jobs are still needed and if yes,
> what's holding them back from transition.
Hi, is there a plan or potential dates for tran
On Wed, May 3, 2017 at 8:34 AM, James Slagle wrote:
> I saw there was no deep dive scheduled for tomorrow, so I decided I'd
> go ahead and plan one.
>
> It will be recorded if you can't make it on the short notice.
>
> I plan to cover the "deployed-server" fe
choices instead of making
comments such as what you've done here.
While minor (with some thinly veiled praise sprinkled in), I'm a bit
shocked no one else has called attention to your response. It is not
friendly, considerate, and above all else
his feature more fully for an
end to end "split-stack".
Thursday May 4th at 1400 UTC at https://bluejeans.com/176756457/
You don't want to miss it! (or maybe you do). Go Owls!
--
-- James Slagle
--
__
Open
t operators who
know what they're doing, actually be able to do it". There are risks
with exposing more knobs to enable/disable functionality. However, if
you know what you're doing, and it's documented sufficiently, then
there a
ink it's
all due to development environments.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscr
On Wed, Mar 8, 2017 at 4:08 AM, Steven Hardy wrote:
> On Tue, Mar 07, 2017 at 02:34:50PM -0500, James Slagle wrote:
>> I've been working on this spec for TripleO:
>> https://review.openstack.org/#/c/431745/
>>
>> which allows users to selectively disable Heat dep
On Tue, Mar 7, 2017 at 7:24 PM, Zane Bitter wrote:
> On 07/03/17 14:34, James Slagle wrote:
>>
>> I've been working on this spec for TripleO:
>> https://review.openstack.org/#/c/431745/
>>
>> which allows users to selectively disable Heat deployment resourc
cted_actions approach is taken, is Heat
interested in this functionality natively? I think it would make for a
much cleaner implementation than something TripleO specific. I can
work on a Heat spec if there's interest, though I'd like to get some
early
e started addressing in this
branch: https://review.openstack.org/#/q/topic:traas
Any feedback is welcome.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
__
> 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
+1. Dmitry is also one of the top reviewers and committers to
tripl
on tripleo-common and tripleo-heat-templates
> docker bits.
> - Add Steve Backer on os-collect-config and also docker bits in
> tripleo-common and tripleo-heat-templates.
+1
--
-- James Slagle
--
__
OpenStack Developme
; I think he'll make a great addition to the team and will help move CI
> issues forward quicker.
+1
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscr
ever.
The reason I -1'd Paul's TripleO spec and suggested it be proposed to
diskimage-builder was due to:
http://lists.openstack.org/pipermail/openstack-dev/2016-June/098560.html and
https://review.openstack.org/#/c/336109/
I just want to make sure the right set of reviewers who are dri
ially around release time.
I'm wondering if there are still plans to move to 3rd party and how
those plans might line up with this proposed schedule.
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-October/105248.html
--
-- James Slagle
--
_
volvement and hard work in the project, this is
> very appreciated!
>
> As usual, I'll let the team to vote about this proposal.
+1
--
-- James Slagle
--
__
OpenStack Development Mailing List (not
ion (backports, bug triaging/reporting and improving
> our processes[2]).
>
> I think she will be a valuable addition to the review team
+1
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for u
bility to branch out and dive into any aspect of
TripleO.
--
-- James Slagle
--
__
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
sap.
[1] https://review.openstack.org/#/c/391799/
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/
en we reviewed all the blueprints at the summit, and discussed all
the features we plan to implement for Ocata, I think it would be
reasonable to go with the above. However, 'm interested in any
feedback or if anyone feels t
oud, are an
unnatural fit for infra's nodepool. Conversely, OVB jobs are a natural
fit for 3rd party CI.
So, I feel like more naturally aligning our CI efforts with the reset
of the infra community is the most reasonable path to ma
ck-infra/tripleo-ci/blob/master/test-environments/worker-config.yaml.
If we can get that down to 1, looks like that might save around 270MB.
It also looks like there are 2 nova-api workers despite having
NovaWorkers: 1. Is that normal? Getting
On Mon, Aug 8, 2016 at 1:47 PM, James Slagle wrote:
> On Mon, Aug 8, 2016 at 1:06 PM, Jeremy Stanley wrote:
>> On 2016-08-08 11:47:56 -0400 (-0400), James Slagle wrote:
>> [...]
>>> I suppose it's also possible that we might be pushing too strongly
>>> d
d he may have more bandwidth to help with
> reviews around networking in future.
>
> Please can I get feedback from exisitng core reviewers - you're free to +1
> these nominations (or abstain), but any -1 will veto the process. I'll
> wait one week, and if we have co
https://review.openstack.org/#/q/topic:mistral-validations
If I missed anything, please point it out.
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ.
On Thu, Aug 25, 2016 at 9:49 AM, James Slagle wrote:
> On Thu, Aug 25, 2016 at 5:40 AM, Derek Higgins wrote:
>> On 25 August 2016 at 02:56, Paul Belanger wrote:
>>> On Wed, Aug 24, 2016 at 02:11:32PM -0400, James Slagle wrote:
>>>> The latest recurring problem that
if that can be accommodated.
>
> What do folks think, if I can get some acks on this plan I will go ahead
> and provide the feedback to Thierry.
+1, sounds good to me.
--
-- James Slagle
--
__
OpenStack Developmen
On Wed, Aug 24, 2016 at 9:56 PM, Paul Belanger wrote:
> I actually believe these problem highlights how large tripleo-ci has grown,
> and
> in need of a refactor. While we won't solve this problem today, I do think
> tripleo-ci is to monolithic today. I believe there is some discussion on
> break
On Thu, Aug 25, 2016 at 5:40 AM, Derek Higgins wrote:
> On 25 August 2016 at 02:56, Paul Belanger wrote:
>> On Wed, Aug 24, 2016 at 02:11:32PM -0400, James Slagle wrote:
>>> The latest recurring problem that is failing a lot of the nonha ssl
>>> jobs in t
is
just not going to be the case given other constraints. It often comes
down to what one is able to reproduce locally, and how to mitigate the
issues as best we can (see email I just sent for an example).
Let me know or add the specifics to the etherpad and
if there is any disagreement on making these changes. If
there isn't, I'll apply them in the next day or so. If there are any
other ideas on how to address this particular bug for some immediate
short term relief, pl
eep-dive-topics
Thanks!
--
-- James Slagle
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/m
1 - 100 of 277 matches
Mail list logo
