works and I'd like
suggest him as core reviewer of TripleO in CI related code.
Please vote!
My +1 is here :)
Thanks
--
Best regards
Sagi Shnaidman
__
OpenStack Development Mailing List (not for usage questions)
U
E
> <https://calendar.google.com/calendar/b/1/embed?src=whayu...@redhat.com&ctz=America/New_York>
>
--
Best regards
Sagi Shnaidman
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: o
___
> 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
>
>
--
Best regards
Sagi Shnaidman
__
ttp://git.openstack.org/cgit/openstack/ansible-role-
> container-registry/
> [1] http://git.openstack.org/cgit/openstack/ansible-role-redhat-
> subscription/
> [2] http://git.openstack.org/cgit/openstack/ansible-role-tripleo-keystone/
> [3] http://git.openstack.org/cgit/openstack/puppet-
rent work in CI.
Thanks
On Wed, May 23, 2018 at 7:04 PM, Alex Schultz wrote:
> On Wed, May 23, 2018 at 8:30 AM, Sagi Shnaidman
> wrote:
> > Hi, Sergii
> >
> > thanks for the question. It's not first time that this topic is raised
> and
> > from firs
bscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Best regards
Sagi Shnaidman
__
OpenStack Development Mailing List (not
ice of somewhat extended time of
>> the main zuul pipeline. I think it makes sense and that extended CI time
>> will not overhead the RDO CI execution times so much to become a problem.
>> WDYT?
>>
>> [0] https://review.openstack.org/#/c/568275/
>> [1] https://rev
t; WDYT?
>
> [0] https://review.openstack.org/#/c/568275/
> [1] https://review.openstack.org/#/c/568278/
> [2] https://review.openstack.org/#/c/568326/
> [3] https://docs.openstack.org/tripleo-quickstart/latest/feature
> -configuration.html
> [4] http://tripleo.org/cistatus.html
>
> * i
12225/
--
Best regards
Sagi Shnaidman
__
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/open
hey're rather High or Medium.
>
> If any doubt, please ask on #tripleo.
>
> Thanks,
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-re
e to bring any feedback.
> Thanks everyone,
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.
st (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Best regards
Sagi Shnaidman
__
Open
itor ovb jobs and run rh1 ovb jobs as
experimental to check if we have the same results (or better :) )
10) OVB jobs on rh1 cloud stay in experimental pipeline in tripleo for a
next month or two.
--
Best regards
Sagi Shnaidman
___
TripleO CI has heat-convergence job running on heat patches in experimental
pipeline [1] It runs there during last year at least.
No any high memory usage was detected in last few months when I watched it.
[1]
https://github.com/openstack-infra/project-config/b
> >> Please let us know if this method sounds like a step forward.
> >
> >
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: op
s will be that it will be easy to reproduce a gate
>> job on a local virthost by typing something like:
>>
>> ./quickstart.sh --release tripleo-ci/master \
>> --nodes config/nodes/3ctlr_1comp.yml \
>> --config config/general_config/featureset001.yml \
>>
>>
>>
Hi,
FYI that gates now are blocked because of [1] and containers jobs now are
part of gate jobs. Please try to resolve it asap.
Thanks
[1] CI: containers jobs fail in pingtest because volume error:
https://bugs.launchpad.net/tripleo/+bug/1700333
--
Best regards
Sagi Shnaidman
ugs.launchpad.net/tripleo/+bugs?field.tag=deployment-time Please
use it for bugs that affect deployment time or CI job run time. It will be
easier to handle them in the sprint.
Please provide your comments and suggestions.
Thanks
On Tue, May 23, 2017 at 1:47 PM, Sagi Shnaidman wrote:
> Hi, al
Hi
I think a "deep dive" about containers in TripleO and some helpful
documentation would help a lot for valuable reviews of these container
patches. The knowledge gap that's accumulated here is pretty big.
Thanks
On Jun 5, 2017 03:39, "Dan Prince" wrote:
> Hi,
>
> Any help reviewing the follow
tatistics collection, profiling and detection of places to
optimize. After this tasks are created, patches are tested and submitted.
The prizes will be presented to teams which saved most of time :)
What do you think?
Tha
pment 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
--
Best regards
Sagi Shnaidman
__
OpenStack Develo
otent install (+another specific
features?)
3) ovb updates job
thoughts?
--
Best regards
Sagi Shnaidman
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
hanks,
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstac
[2] https://review.openstack.org/450023
--
Best regards
Sagi Shnaidman
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
2017 at 12:03 PM, Emilien Macchi
> wrote:
> >
> > > On Mon, Mar 20, 2017 at 3:29 PM, Paul Belanger
> > > wrote:
> > > > On Sun, Mar 19, 2017 at 06:54:27PM +0200, Sagi Shnaidman wrote:
> > > >> Hi, Paul
> > > >> I would say that r
;t think it's appropriate
behavior, although not sure it's the reason for failing jobs. Any ideas why
it could happen?
Thanks
--
Best regards
Sagi Shnaidman
__
OpenStack Development Mailing List (not for usage questio
ay like it happens now or with "low" priority.
Thanks
On Wed, Mar 15, 2017 at 11:16 PM, Paul Belanger
wrote:
> On Wed, Mar 15, 2017 at 03:42:32PM -0500, Ben Nemec wrote:
> >
> >
> > On 03/13/2017 02:29 PM, Sagi Shnaidman wrote:
> > > Hi, all
> > >
&
s to this list.
>
> - trown
>
> __
> 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/op
ck.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> ______
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>
e and you prefer to run all experimental jobs we have at
once, please provide a feedback and I'll take it back.
Patch about the topic: https://review.openstack.org/#/c/425184/
Thanks
--
Best regards
Sagi Shnaidman
___
Hi, all
FYI, the periodic TripleO nonha jobs fail because of introspection failure,
there is opened bug in mistral:
Ironic introspection fails because unexpected keyword "insecure"
https://bugs.launchpad.net/tripleo/+bug/1656692
and marked as promotion blocker.
Thanks
--
Best re
that does everything
for you (as all scripts should do usually).
In case you need to test your patch, just send me your *public* keys
*offline*, I'll add them to tenant defaults and you'll be able to run it.
Thanks
[1] https://github.com/openstack/tripleo-quickstart
--
Best re
hem and it
should be updated on next promotion job run.
Thanks
--
Best regards
Sagi Shnaidman
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
service on
overcloud controllers.
On Fri, Aug 19, 2016 at 12:41 PM, Derek Higgins wrote:
> On 19 August 2016 at 00:07, Sagi Shnaidman wrote:
> > Hi,
> >
> > we have a problem again with not enough memory in HA jobs, all of them
> > constantly fails in CI: http://status-t
e able to watch this if
it works and no problems appear.
TripleO CI cloud admins, please increase the memory for baremetal flavor on
rh1 tomorrow (to 6144?).
Thanks
[1] https://review.openstack.org/#/c/357532/
--
Best regards
://bugs.launchpad.net/cinder/+bug/1610073
[5]
https://github.com/openstack-infra/tripleo-ci/blob/master/scripts/tripleo.sh#L100
--
Best regards
Sagi Shnaidman
__
OpenStack Development Mailing List (not for usage questions
patch: https://review.openstack.org/#/c/349261
Thanks
--
Best regards
Sagi Shnaidman
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
On Thu, Jul 21, 2016 at 3:11 AM, Alan Pevec wrote:
> On Wed, Jul 20, 2016 at 7:49 PM, Sagi Shnaidman
> wrote:
> > How then it worked before? Can you show me the patch that broke this
> > functionality in delorean? It should be about 15 Jul when jobs started to
> > f
> > as a quickfix in tripleo.sh you could patch dlrn and set local=True in
>
> correction, patch local=False there while running dlrn command with
> --local to keep source checkout as-is
>
--
Best regards
Sagi Shnaidman
> specified in projects.ini
>
> Alan,
I don't want to reset local checkouts and reset branches - I need to build
with these checkout, it's all CI is for.
> Alan
>
--
Best regards
Sagi Shnaidman
__
syncport=22
[gitrepo_driver]
--
Best regards
Sagi Shnaidman
__
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
ing me if you have any unclear points or would like to discuss
it in separate meeting, I'll give the all required info.
Thanks
--
Best regards
Sagi Shnaidman
__
OpenStack Development Mailing List (not for u
Sorry, missed the mentioned patches:
[1] Refresh log files for tripleo project:
https://review.openstack.org/#/c/312985/
[2] Add bug for TripleO timeouts: https://review.openstack.org/#/c/313038/
On Mon, May 9, 2016 at 8:22 PM, Sagi Shnaidman wrote:
> Hi, all
>
> I'd like to
quot;crm_resource for openstack "
and various puppet errors.
However almost all of these messages could have different root causes,
except of network failures. Easy to fix bug doesn't make to submit there,
because they will be fixed yet before recheck patch will be merge
For making clear all advantages and disadvantages, I've created a doc:
https://docs.google.com/document/d/1HmY-I8OzoJt0SzLzs79hCa1smKGltb-byrJOkKKGXII/edit?usp=sharing
Please comment.
On Sun, Apr 17, 2016 at 12:14 PM, Sagi Shnaidman
wrote:
>
> Hi,
>
> John raised up the issue
aintain according to very
dynamical configuration.
So, do we need to use pure upstream tempest from current source and to
maintain configuration scripts or we can use packaged from delorean and not
duplicate effort of test teams?
Thanks
--
Best re
pproach and we definitely should take it into account,
but now it looks pretty raw and not stable enough to use it in gate jobs.
Anyway, thank you for your pointing out to this great tool.
Thanks
On Fri, Apr 8, 2016 at 2:33 PM, Andrey Kurilin
wrote:
> Hi Sagi,
>
>
> On Thu, Apr 7, 201
ator_role':
value => 'SwiftOperator',
path => "${tempest_clone_path}/etc/tempest.conf",
}
}
After this run puppet on controller node:
sudo puppet apply --verbose --debug --detailed-exitcodes -e "include
::testt" | tee ~/puppet
48 matches
Mail list logo
