On 15 Nov, Sagi Shnaidman wrote:
> Hi,
> I'd like to propose Quique (@quiquell) as a core reviewer for TripleO.
> Quique is actively involved in improvements and development of TripleO and
> TripleO CI. He also helps in other projects including but not limited to
> Infrastructure.
It'll be grand.
Hi,
as part of the process to migrate all the jobs to use a workflow that
takes advantage of zuulv3, we need to migrate the jobs that form the
promotion pipeline in rdo sf.
There are a total of 95 jobs that need migration in rdo sf. Of these, 55
are in the various promotion pipeline for all the
On 16 Feb, Gabriele Cerami wrote:
> Hi,
>
> I started circling around technical debts a few months ago, and recently
> started to propose changes in my team (CI) process on how to manage
> them.
> https://review.openstack.org/545392
Hi,
I'd like to draw again some attention o
Hi,
we recently changed our set of scripts to uniform the users workflow
with the CI workflow.
One of the results of this change was the reproducer script, that is now
the official way to spawn a live environment to debug a set of changes.
One of the negative results of this changes was the
Hi,
I started circling around technical debts a few months ago, and recently
started to propose changes in my team (CI) process on how to manage
them.
I didn't realize there was already a policy discussed and merged, and I
underestimated the audience for my proposal, which cannot be only my team
On 09 Feb, Thierry Carrez wrote:
> Doug Hellmann wrote:
> > What makes reno a good fit for this task? It seems like updating a
> > regular documentation page in the source tree would work just as well,
> > since presumably these technical debt descriptions don't need to be
> > backported to stable
On 08 Feb, Ben Nemec wrote:
> So TripleO has a tech debt policy:
> https://specs.openstack.org/openstack/tripleo-specs/specs/policy/tech-debt-tracking.html
> (and I'm tagging tripleo on this thread for visibility).
I didn't know about this policy. I've been circling around tech debts
for more
Hi,
sometimes it happens, while reviewing a patch, to find an issue that
is not quite a bug, because it doesn't limit functionality, but
may represent a problem in some corner case, or with some possible
future modification in some component involved in the patch; it may
best be described as a
On 29 Nov, John Trowbridge wrote:
> I would like to propose Ronelle be given +2 for the above repos. She has
> been a solid contributor to tripleo-quickstart and extras almost since the
> beginning. She has solid review numbers, but more importantly has always
> done quality reviews. She also has
Hi,
since the failures in Tuesday's tests were caused by infra problems, we
believed a specific hash involved in the failures to remain the best
candidate for a promotion.
So we pinned it in our promotion pipeline and insisted on it for some
hours. It has passed all the tests twice, so we dacided
Hi,
for a little more than an hour, 21:35 - 22:40 UTC we had a new hash
promoted as master, but it was broken, wasn't fully tested and was
missing containers images.
We reverted it to the last known good hash from September again and we
managed to stop it from being propagated down the production
On 19 Oct, Sam Yaple wrote:
> So it seems tripleo is building *all* images and then pushing them.
> Reworking your number leads me to believe you will be consuming 10-15GB in
> total on Dockerhub. Kolla images are only the size that you posted when
> built as seperate services. Just keep building
On 19 Oct, Sam Yaple wrote:
> docker_image wouldn't be the best place for that. Buf if you are looking
> for a quicker solution, kolla_docker was written specifically to be license
> compatible for openstack. its structure should make it easily adapted to
> delete an image. And you can copy it and
Hi,
our CI scripts are now automatically building, testing and pushing
approved openstack/RDO services images to public repositories in
dockerhub using ansible docker_image module.
Promotions have had some hiccups, but we're starting to regularly upload
new images every 4 hours.
When we'll get
Hi,
as discussed during the previous meeting, we are adding a lot of new
jobs that need new featurset files recently. It's difficult to scan all
the review to find an unused featureset file index, so there have been a
lot of conflicts.
To avoid this I created an etherpad at
A video from the recording of the deep-dive is now available at
https://youtu.be/qaTwGBuLoRc
Thanks to everyone for the participation, we hope it helped.
__
OpenStack Development Mailing List (not for usage questions)
On 24 Apr, Emilien Macchi wrote:
> >
> > What time?
>
> If it's like usual, it's 1400 UTC.
>
Yes, I meant to use the same usual slot
thanks.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hi,
with the end of the first phase of the transition of CI to quickstart,
it was suggested it could be beneficial to everyone doing a deep dive of
quickstart, how to use it, how to contribute to it.
I'm proposing next thursday, 27th of april as the date for such a deep
dive.
The location:
Hi,
despite CI freeze for substantial change is in order, I recognize
there's always the need to add or modify slightly the jobs for
important fixes or to improve debugging.
Unfortunately in these days we are wrapping up the gap in feature
coverage between tripleo-ci and quickstart, and any of
On 30 Jan, Paul Belanger wrote:
> Before you go out an implement some sort of in-repo configuration for
> testing, I
> strongly encourage you to read up on our Zuulv3 spec[3], as we are providing
> this functionality. What is comes down to, you'll be able to focus on writing
> tests, where zuul
Hi,
as part of an effort to bring success rate of tempest test closer to
100% in tripleo-ci, we propose to replace the current periocic ha
tempest job with a one that is using quickstart, but tests in nonha.
We pushed a change in infra: https://review.openstack.org/420647
that will replace the
Hi,
following a suggestion from Alal Pevec I'm proposing to stop using
"current" repo from dlrn and start using "consistent" instead.
The main difference should only be that "consistent" is not affected by
packages in ftbfs, so we're testing with a bit more stability.
This is the proposal
On 22 Nov, Emilien Macchi wrote:
> 1) Re-use experience from Puppet OpenStack CI and have environments
> that are in a branched repository.
> a) Move CI environments and pingtest into
> tripleo-heat-templates/environments/ci/(scenarios|pingtest). This repo
> is branched and we could add a README
On 22 Nov, Yolanda Robla Mota wrote:
> Hi all
> I wanted to start a thread about the current privileges model for TripleO
> quickstart.
> Currently there is the assumption that quickstart does not need root
> privileges after the environment and provision roles. However, this
> assumption
On 18 Oct, Gabriele Cerami wrote:
> Hello,
>
> after adding coverage in CI for HA IPv6 scenario here
> https://review.openstack.org/363674 we wanted to add IPv6 testing on the
> gates.
> To not use any more resources the first suggestion to add IPv6 to the
> gates was to
On 08 Nov, Wesley Hayutin wrote:
> [3], please if you have time review the etherpad and respond with any
> questions, suggestions or concerns.
Hi,
I added a step on the PRE phase (line 192) in [3] regarding logs.
Coming from TripleO CI developers may feel lost when they try to debug a
failure.
Hello,
after adding coverage in CI for HA IPv6 scenario here
https://review.openstack.org/363674 we wanted to add IPv6 testing on the
gates.
To not use any more resources the first suggestion to add IPv6 to the
gates was to make all HA jobs IPv6, move network isolation testing for
IPv4 on non-ha
Hi,
As reported on this bug
https://bugs.launchpad.net/tripleo/+bug/1626483
HA gate and periodic jobs for master and sometimes newton started to
fail for errors related to memory shortage. Memory on undercloud
instance was increased to 8G less than a month ago, so the problem
needs a different
On Fri, 2016-04-08 at 16:18 +0100, Steven Hardy wrote:
> Note we're not using devtest at all anymore, the developer script
> many
> folks use is tripleo.sh:
So, I followed the flow of the gate jobs starting from jenkins builder
script, and it seems like it's using devtest (or maybe something I
Hi,
I'm trying to find an entry point to join the effort in TripleO CI.
I studied the infrastructure and the scripts, but there's still something I'm
missing.
The last step of studying the complex landscape of TripleO CI and the first to
start contributing
is being able to reproduce failures in
Hi,
why are current beaker-rspec tests installing puppet from puppetlabs
instead of using a package from a distribution repo, like what is done
for git ?
More generally, spec_helper_acceptance.rb is setting up what it seems to
be a distribution independent environment that is using a lot of
Hi,
for people who, like me, would like to contribute to the effort of
adding tests to the upcoming beaker-rspec framework, could be really
helpful discussing about the scope, requirements and goals for the
framework and for a test to make sense in this environment.
I'd like to see, if possible,
32 matches
Mail list logo
