Re: [openstack-dev] [tripleo] Proposing Marius Cornea core on upgrade bits

2018-04-20 Thread Arx Cruz 
+1 Congrats man!!!

On Fri, Apr 20, 2018 at 2:29 PM, Brent Eagles  wrote:

> +1 !!!
>
> On Fri, Apr 20, 2018 at 9:42 AM, Brad P. Crochet  wrote:
>
>> +1 from me!
>>
>> On Fri, Apr 20, 2018 at 8:04 AM Yolanda Robla Mota 
>> wrote:
>>
>>> +1, Marius has been a great help
>>>
>>> On Thu, Apr 19, 2018 at 7:01 PM, Emilien Macchi 
>>> wrote:
>>>
 Greetings,

 As you probably know mcornea on IRC, Marius Cornea has been
 contributing on TripleO for a while, specially on the upgrade bits.
 Part of the quality team, he's always testing real customer scenarios
 and brings a lot of good feedback in his reviews, and quite often takes
 care of fixing complex bugs when it comes to advanced upgrades scenarios.
 He's very involved in tripleo-upgrade repository where he's already
 core, but I think it's time to let him +2 on other 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.
 --
 Emilien Macchi

 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.op
 enstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


>>>
>>>
>>> --
>>>
>>> Yolanda Robla Mota
>>>
>>> Principal Software Engineer, RHCE
>>>
>>> Red Hat
>>>
>>> 
>>>
>>> C/Avellana 213
>>>
>>> Urb Portugal
>>>
>>> yrobl...@redhat.comM: +34605641639
>>> 
>>> 
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>> --
>> Brad P. Crochet, RHCA, RHCE, RHCVA, RHCDS
>> Principal Software Engineer
>> (c) 704.236.9385
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/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/mailman/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/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] TripleO CI Sprint end

2018-03-23 Thread Arx Cruz 
*Hello,On March 21 we came the end of sprint using our new team structure,
and here’s the highlights.Sprint Review:Due the outage in our infra a few
weeks ago, we decided to work on the automation on all the servers used in
our CI, in this way, in case of a any outage, we are able to teardown all
the servers, and bring it up again without the need of manually configure
anything.One can see the results of the sprint via
https://tinyurl.com/yd8wmqxz <https://tinyurl.com/yd8wmqxz>Ruck and
RoverWhat is Ruck and RoverOne person in our team is designated Ruck and
another Rover, one is responsible to monitoring the CI, checking for
failures, opening bugs, participate on meetings, and this is your focal
point to any CI issues. The other person, is responsible to work on these
bugs, fix problems and the rest of the team are focused on the sprint. For
more information about our structure, check [1]List of bugs that Ruck and
Rover were working on: - https://bugs.launchpad.net/tripleo/+bug/1756892
<https://bugs.launchpad.net/tripleo/+bug/1756892> - dlrnapi promoter:
promotion of older link > newer link- causing ocata rdo2 incorrect
promotion- https://bugs.launchpad.net/tripleo/+bug/1754036
<https://bugs.launchpad.net/tripleo/+bug/1754036> - fs020, tempest, image
corrupted after upload to glance (checksum mismatch)- MTU values were not
being passed to UC/OC- https://bugs.launchpad.net/tripleo/+bug/1755485
<https://bugs.launchpad.net/tripleo/+bug/1755485> - Barbican tempest test
failing to ssh to cirros image- LP + merge skip list-
https://bugs.launchpad.net/tripleo/+bug/1755891
<https://bugs.launchpad.net/tripleo/+bug/1755891> - OVB based jobs are not
collecting logs from OC nodes- changes made in past weeks to move log
collection outside upstream jobs had negative side effects-
https://bugs.launchpad.net/tripleo/+bug/1755865
<https://bugs.launchpad.net/tripleo/+bug/1755865> - BMU job(s) failing on
installation of missing package (ceph-ansible)-
https://bugs.launchpad.net/tripleo/+bug/1755478
<https://bugs.launchpad.net/tripleo/+bug/1755478> - all BM jobs are not
able to be hand edited, JJB contains deprecated element-
https://bugs.launchpad.net/tripleo/+bug/1753580
<https://bugs.launchpad.net/tripleo/+bug/1753580> - newton, cache image
script is looking in the wrong place.We also have our new Ruck and Rover
for this week: - Ruck- Rafael Folco - rfolco|ruck- Rover- Arx Cruz  -
arxcruz|roverIf you have any questions and/or suggestions, please contact
us[1]
https://specs.openstack.org/openstack/tripleo-specs/specs/policy/ci-team-structure.html
<https://specs.openstack.org/openstack/tripleo-specs/specs/policy/ci-team-structure.html>*
__
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

[openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

2018-03-19 Thread Arx Cruz 
Hello

We are going to have a TripleO CI Community meeting tomorrow 03/20/2018 at
3 pm UTC time.
The meeting is going to happen on BlueJeans [1] and also on IRC on #tripleo
 channel.

After that, we will hold Office Hours starting at 4PM UTC in case someone
from community have any questions related to CI.

Hope to see you there.

1 - https://bluejeans.com/7071866728
<https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F7071866728=D=1510075851653000=AFQjCNE_gUUl_WZUBJfZO0otaEPP1j1ZoQ>


Kind regards,
Arx Cruz
__
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

Re: [openstack-dev] [tripleo] rdo cloud tenant reach 100 stacks

2018-02-23 Thread Arx Cruz 
Just an update, we cleaned up the stacks with more than 10 hours, jobs
should be working properly now.

Kind regards,
Arx Cruz

On Fri, Feb 23, 2018 at 12:49 PM, Arx Cruz <arxc...@redhat.com> wrote:

> Hello,
>
> We just notice that there are several jobs failing because the
> openstack-nodepool tenant reach 100 stacks and cannot create new ones.
>
> I notice there are several stacks created > 10 hours, and I'm manually
> deleting those ones.
> I don't think it will affect someone, but just in case, be aware of it.
>
> Kind regards,
> Arx Cruz
>
__
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

[openstack-dev] [tripleo] rdo cloud tenant reach 100 stacks

2018-02-23 Thread Arx Cruz 
Hello,

We just notice that there are several jobs failing because the
openstack-nodepool tenant reach 100 stacks and cannot create new ones.

I notice there are several stacks created > 10 hours, and I'm manually
deleting those ones.
I don't think it will affect someone, but just in case, be aware of it.

Kind regards,
Arx Cruz
__
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

[openstack-dev] [tripleo] TripleO CI end of sprint status

2018-02-16 Thread Arx Cruz 
*Hello,On February 14 we came the end of sprint using our new team
structure, and here’s the highlights.Sprint Review:On this sprint, was the
first one where the team worked in collaboration with another team to have
TripleO Upgrade jobs running on RDO cloud on tripleo-quickstart,
tripleo-quickstart-extras and tripleo-upgrade projects.One can see the
results of the sprint via https://tinyurl.com/y8h8xmo8
<https://tinyurl.com/y8h8xmo8>Ruck and RoverWhat is Ruck and RoverOne
person in our team is designated Ruck and another Rover, one is responsible
to monitoring the CI, checking for failures, opening bugs, participate on
meetings, and this is your focal point to any CI issues. The other person,
is responsible to work on these bugs, fix problems and the rest of the team
are focused on the sprint. For more information about our structure, check
[1]List of bugs that Ruck and Rover were working on: -
https://bugs.launchpad.net/tripleo/+bug/1749335
<https://bugs.launchpad.net/tripleo/+bug/1749335>-
https://bugs.launchpad.net/tripleo/+bug/1749186
<https://bugs.launchpad.net/tripleo/+bug/1749186>-
https://bugs.launchpad.net/tripleo/+bug/1749105
<https://bugs.launchpad.net/tripleo/+bug/1749105>-
https://bugs.launchpad.net/tripleo/+bug/1748971
<https://bugs.launchpad.net/tripleo/+bug/1748971>-
https://bugs.launchpad.net/tripleo/+bug/1748934
<https://bugs.launchpad.net/tripleo/+bug/1748934>-
https://bugs.launchpad.net/tripleo/+bug/1748751
<https://bugs.launchpad.net/tripleo/+bug/1748751>-
https://bugs.launchpad.net/tripleo/+bug/1748315
<https://bugs.launchpad.net/tripleo/+bug/1748315>-
https://bugs.launchpad.net/tripleo/+bug/1748262
<https://bugs.launchpad.net/tripleo/+bug/1748262>-
https://bugs.launchpad.net/tripleo/+bug/1748199
<https://bugs.launchpad.net/tripleo/+bug/1748199>-
https://bugs.launchpad.net/tripleo/+bug/1748180
<https://bugs.launchpad.net/tripleo/+bug/1748180>-
https://bugs.launchpad.net/tripleo/+bug/1747986
<https://bugs.launchpad.net/tripleo/+bug/1747986>-
https://bugs.launchpad.net/tripleo/+bug/1747690
<https://bugs.launchpad.net/tripleo/+bug/1747690>-
https://bugs.launchpad.net/tripleo/+bug/1747623
<https://bugs.launchpad.net/tripleo/+bug/1747623>-
https://bugs.launchpad.net/tripleo/+bug/1747294
<https://bugs.launchpad.net/tripleo/+bug/1747294>-
https://bugs.launchpad.net/tripleo/+bug/1747089
<https://bugs.launchpad.net/tripleo/+bug/1747089>-
https://bugs.launchpad.net/tripleo/+bug/1747055
<https://bugs.launchpad.net/tripleo/+bug/1747055>-
https://bugs.launchpad.net/tripleo/+bug/1747043
<https://bugs.launchpad.net/tripleo/+bug/1747043>-
https://bugs.launchpad.net/tripleo/+bug/1746978
<https://bugs.launchpad.net/tripleo/+bug/1746978>-
https://bugs.launchpad.net/tripleo/+bug/1746857
<https://bugs.launchpad.net/tripleo/+bug/1746857>-
https://bugs.launchpad.net/tripleo/+bug/1746812
<https://bugs.launchpad.net/tripleo/+bug/1746812>-
https://bugs.launchpad.net/tripleo/+bug/1746737
<https://bugs.launchpad.net/tripleo/+bug/1746737>-
https://bugs.launchpad.net/tripleo/+bug/1746734
<https://bugs.launchpad.net/tripleo/+bug/1746734>We also have our new Ruck
and Rover for this week: - Ruck- Arx Cruz - arxcruz|ruck- Rover- Ronele
Landy  - rlandy|roverIf you have any questions and/or suggestions, please
contact us[1]
https://github.com/openstack/tripleo-specs/blob/master/specs/policy/ci-team-structure.rst
<https://github.com/openstack/tripleo-specs/blob/master/specs/policy/ci-team-structure.rst>
*
__
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

[openstack-dev] [tripleo] TripleO CI end of sprint status

2018-02-02 Thread Arx Cruz 
Hello,

On January 31 we came the end of sprint using our new team structure, and
here’s the highlights.

Sprint Review:

On this sprint, the team worked on internal infrastructure.

One can see the results of the sprint via https://tinyurl.com/ycpw42pj


Ruck and Rover

What is Ruck and Rover

One person in our team is designated Ruck and another Rover, one is
responsible to monitoring the CI, checking for failures, opening bugs,
participate on meetings, and this is your focal point to any CI issues. The
other person, is responsible to work on these bugs, fix problems and the
rest of the team are focused on the sprint. For more information about our
structure, check [1]

List of bugs that Ruck and Rover were working on:


   -

   https://bugs.launchpad.net/tripleo/+bug/1744151 -
   
barbican_tempest_plugin.tests.scenario.test_volume_encryption.VolumeEncryptionTest
   fails on Invalid Volume
   -

   https://bugs.launchpad.net/tripleo/+bug/1745712 - master:
   etc/pki/tls/certs/undercloud-192.168.24.2.pem]: Failed to generate
   additional resources using 'eval_generate': comparison of Array with Array
   failed
   -

   https://bugs.launchpad.net/tripleo/+bug/1746023 - rdo phase 2 status to
   dlrn_api fails with file not found
   -

   https://bugs.launchpad.net/tripleo/+bug/1746026 - Tracker, CI: OVB jobs
   on RDO cloud can't get OVB env because of 504 gateway timeout
   -

   https://bugs.launchpad.net/tripleo/+bug/1746281 - tripleo jobs running
   in rax have slow package downloads, jobs timing out
   -

   https://bugs.launchpad.net/tripleo/pike/+bug/1745686 -
   [gnocchi-db-sync]: gnocchi-upgrade --config-file /etc/gnocchi/gnocchi.conf
   --skip-storage --skip-incoming returned 2
   -

   https://bugs.launchpad.net/tripleo/+bug/1746729 - tracker, rdo sf
   nodepool slaves going off line
   -

   https://bugs.launchpad.net/tripleo/+bug/1746737 - "msg": "No package
   matching 'jq' found available, installed or updated"
   -

   https://bugs.launchpad.net/tripleo/+bug/1746734 - Periodic Jobs failing
   at tempest config while creating image(with swift backend)


We also have our new Ruck and Rover for this week:


   -

   Ruck
   -

  Rafael Folco - rfolco|ruck
  -

   Rover
   -

  Sagi Shnaidman  - sshnaidm|rover


If you have any questions and/or suggestions, please contact us

[1]
https://github.com/openstack/tripleo-specs/blob/master/specs/policy/ci-team-structure.rst
__
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

[openstack-dev] [tripleo] TripleO CI Squad meeting

2018-01-23 Thread Arx Cruz 
Hello,

Here’s the highlights from TripleO CI Squad meeting from January 18


   -

   Roles
   -

  The Ruck and the Rover will be responsible for any CI problems, so if
  you have anything related to CI, please contact them. The rest
of the team
  will work on the sprint
  -

 Ruck
 -

John Trownbridge - trown|ruck
-

 Rover
 -

Wesley Hayutin - weshay|rover
-

   Team
   -

  Arx Cruz
  -

  Ronelle Landy
  -

  Attila Darazs
  -

  Gabrielle Cerami
  -

  Rafael Folco
  -

  Matt Young
  -

   For this sprint 01/18/2018 - 01/31/2018
   -

  The proposed topic is work on internal ci jobs
  -

 Promotion pipeline
 -

 OVB jobs
 -

 Upgrade jobs
 -

  The epic task with more information can be found here
  https://trello.com/c/rzHPI7kb
  -

  Tasks can be found in both the trello card above, or in the TripleO
  CI Squad trello board using the filter by label “Sprint 7” or clicking in
  this link here https://tinyurl.com/ya359l2l
  -

   Promotions
   -

  Master promoted 12 days ago
  -

 There are some issues opened and the team is working on that
 -

  Pike promoted 13 days ago
  -

  Newton promoted today


If you have any questions, suggestions please let us know. Your feedback is
very important to us!
__
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

[openstack-dev] [tripleo] TripleO CI end of sprint status

2018-01-23 Thread Arx Cruz 
Hello,

Sorry the delay...


On January 17 we came the end of sprint using our new team structure, and
here’s the highlights.

Sprint Review:

On this sprint, the team worked in the first steps to have metrics enabled
in Tripleo Jobs. With this in place will be easier to identify places where
we are seeing the code taking more time than usual, and will be easier to
developers identify more easily where to focus.

One can see the results of the sprint via https://tinyurl.com/yb4z5gd4


Ruck and Rover

What is Ruck and Rover

One person in our team is designated Ruck and another Rover, one is
responsible to monitoring the CI, checking for failures, opening bugs,
participate on meetings, and this is your focal point to any CI issues. The
other person, is responsible to work on these bugs, fix problems and the
rest of the team are focused on the sprint. For more information about our
structure, check [1]

List of bugs that Ruck and Rover were working on:


   -

   https://bugs.launchpad.net/tripleo/+bug/1741445 -
   tripleo-ci-centos-7-scenario002-multinode-oooq-container failing with
   timeout in deploy overcloud
   -

   https://bugs.launchpad.net/tripleo/+bug/1741850 - VolumeEncryptionTest
   is failing in tripleo-ci-centos-7-scenario002-multinode-oooq-container with
   request timeout
   -

   https://bugs.launchpad.net/tripleo/+bug/1742080 - Job
   tripleo-quickstart-gate-newton-delorean-quick-basic fails with missing
   ci_centos_libvirt.yml
   -

   https://bugs.launchpad.net/tripleo/+bug/1742435 -
   tripleo-quickstart-gate-master-delorean-quick-basic failing to parse
   jenkins env vars
   -

   https://bugs.launchpad.net/tripleo/+bug/1742465 -
   periodic-tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset002-ocata is failing
   with Resource could not be found on mistral
   -

   https://bugs.launchpad.net/tripleo/+bug/1742557 - quickstart reproducer
   create script is getting skipped
   -

   https://bugs.launchpad.net/tripleo/+bug/1742528 - ovb jobs in rdo-cloud
   are not logging the overcloud nodes


We also have our new Ruck and Rover for this week:


   -

   Ruck
   -

  John Trownbridge - trown|ruck
  -

   Rover
   -

  Wesley Hayutin - weshay|ruck


If you have any questions and/or suggestions, please contact us

[1] https://review.openstack.org/#/c/509280/
__
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

[openstack-dev] [tripleo] TripleO CI end of sprint status

2018-01-04 Thread Arx Cruz 
Hello,

On January 03 we came the end of sprint using our new team structure, and
here’s the highlights.

Sprint Review:

This was a tech debt sprint, and due the holidays and mostly of the team
out, we haven't set a goal for this sprint, leaving the team free to work
on the tech debt cards, as much as the time permits.

One can see the results of the sprint via https://trello.com/c/fvLpZMF6/

Tripleo CI community meeting


   - Promotion issues due mistral
   -


  
http://lists.openstack.org/pipermail/openstack-dev/2018-January/125935.html
  
<http://lists.openstack.org/pipermail/openstack-dev/2018-January/125935.html)>
  -

  The plan (from Emilien's email)
  -

 Carry Steve's patch in Mistral distgit:
 -

https://review.rdoproject.org/r/#/c/11140/ - DONE
-

 Remove featureset010 from promotion requirements - DONE
 -

 Once we have a promotion, we'll be able to land
 https://review.openstack.org/#/c/530783/ - IN PROGRESS
 -

 Once https://review.openstack.org/#/c/530783/ is landed, and the
 upstream patch is landed, revert
 https://review.rdoproject.org/r/#/c/11140/ (otherwise RDO will
 become inconsistent) and failing to build on master)
 -

 Re-add featureset010 in promotion requirements (revert
 https://review.rdoproject.org/r/#/c/11142) so we'll catch the
 issue next time.
 -

 Landed in current-tripleo because we don't have voting in
 multinode job and scenario 001, 002 and 003 were non voting
 -

   Scenario jobs not voting due timeouts
   -


  
http://lists.openstack.org/pipermail/openstack-dev/2018-January/125935.html
  -

   Which scenario / services we care about
   -

  We need an investigation to determine what we want to test in our
  scenario jobs, and what we don't, in order to release resources and focus
  our work on
  -

   Graphite report status
   -

  Working on grafana
  -

  Initially focused on OVB jobs


Ruck and Rover

What is Ruck and Rover

One person in our team is designated Ruck and another Rover, one is
responsible to monitoring the CI, checking for failures, opening bugs,
participate on meetings, and this is your focal point to any CI issues. The
other person, is responsible to work on these bugs, fix problems and the
rest of the team are focused on the sprint. For more information about our
structure, check [1]

List of bugs that Ruck and Rover were working on:


   -

   https://bugs.launchpad.net/tripleo/+bug/1736113
   CI: newton promotion fails because no stable/newton branch in aodh
   -

   https://bugs.launchpad.net/tripleo/+bug/1740940
   Tempest test on Ocata failing with Error: No valid Host was found
   -

   https://bugs.launchpad.net/tripleo/+bug/1740934 Tracker Bug: Tempest
   fails with packaging error - python-oslo-db-tests
   -

   https://bugs.launchpad.net/tripleo/+bug/1739661 Tracker Bug:
   Intermittent failures creating OVB stacks on RDO Cloud since upgrade  (**
   would like to close this bug - tenant has been cleaned up and is working)
   -

   https://bugs.launchpad.net/tripleo/+bug/1739639 ci.centos gate are
   failing with THT default change


We also have our new Ruck and Rover for this week:


   -

   Ruck
   -

      Arx Cruz - arxcruz|ruck
  -

   Rover
   -

  Gabrielle Cerami - panda|rover


If you have any questions and/or suggestions, please contact us

[1] https://review.openstack.org/#/c/509280/
__
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

[openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

2018-01-02 Thread Arx Cruz 
Hello

We are going to have a TripleO CI Community meeting tomorrow 01/03/2018 at
2 pm UTC time.
The meeting is going to happen on BlueJeans [1] and also on IRC on #tripleo
 channel.

After that, we will hold Office Hours starting at 4PM UTC in case someone
from community have any questions related to CI.

Hope to see you there.

1 - https://bluejeans.com/7071866728
<https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F7071866728=D=1510075851653000=AFQjCNE_gUUl_WZUBJfZO0otaEPP1j1ZoQ>


Kind regards,
Arx Cruz
__
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

[openstack-dev] [tripleo] TripleO CI end of sprint status

2017-12-15 Thread Arx Cruz 
Hello,

On December 13 we came the end of sprint using our new team structure, and
here’s the highlights.

Sprint Review:

The goal on this sprint was to enable into quickstart a way to reproduce
upstream jobs, in your personal RDO cloud tenant, making easy to developers
to debug and reproduce their code.

Unfortunately due the RDO cloud upgrade and upstream infra issues, we
weren’t able to finish successfully this sprint, having completed 4 cards,
5 that are waiting to be merged, and 3 blocked.

Nevertheless we have reviews [1] and documentation that can be used to
reproduce the jobs upstream manually [2], and your feedback is more than
welcome to improve it in our future automated script

One can see the results of the sprint via https://trello.com/c/EWotWxGe/

Tripleo CI community meeting


   - TLS Everywhere Job:
   - Harry is working to have a periodic job running TLS
  - OVB (most recent hash) has the ability to deploy an extra node
  alongside the undercloud
 - https://github.com/cybertron/openstack-virtual-baremetal/commit/
 c288a1ae973f3b32e9e4481f6604204386cbae9c
 

 - https://github.com/cybertron/openstack-virtual-baremetal/commit/
 2e4dd517d1736f004725ee29ac3e4764af246bab
 

  - Patch is live to deploy extra nodes in te-broker
 - https://review.openstack.org/#/c/512899/
  - OVB migration
  - Blocked due RDO cloud upgrade
   - RDO Cloud
  - Upgrade process still in progress
   - Kubernetes
  - Will we see kubernetes in CI? Yes
  - There are several scenarios for kubernetes and openshift already
  - Kubernetes jobs are in check queue
  - Openshift jobs are in experimental
  - For more questions, please ping Flavio (flaper87)
   - Upgrades related patches:
  - https://review.openstack.org/#/c/504822/ Support release change
  during playbook run
  - https://review.openstack.org/#/c/504939/ Set repo setup release in
  playbook




Ruck and Rover

What is Ruck and Rover

One person in our team is designated Ruck and another Rover, one is
responsible to monitoring the CI, checking for failures, opening bugs,
participate on meetings, and this is your focal point to any CI issues. The
other person, is responsible to work on these bugs, fix problems and the
rest of the team are focused on the sprint. For more information about our
structure, check [1]

List of bugs that Ruck and Rover were working on:


   - Undercloud fails with " [ERROR] Could not lock
   /var/run/os-refresh-config.lock
  - intermittently seen from upstream --> rdophase2.  posted patch to
  add elastic-recheck query to help id future instances
  - https://bugs.launchpad.net/tripleo/+bug/1669110
  - https://review.openstack.org/#/c/527559
   - Newton: RDO CI gate and phase1 promotion jobs fail with error
   "publicURL endpoint for workflowv2 service not found" because mistral is
   disabled
  - https://bugs.launchpad.net/tripleo/+bug/1737502
   - http_proxy makes quickstart fail
  - https://bugs.launchpad.net/tripleo/+bug/1736499
   - Need better logging for HA jobs
  - https://bugs.launchpad.net/tripleo/+bug/1695237
  - https://review.openstack.org/#/c/527554/
   - Remove mistral tempest tests jenkins-periodic-master-rdo_
   trunk-virtbasic-1ctlr_1comp_64gb
  - https://bugs.launchpad.net/tripleo/+bug/1736252
   - 1737940 CI: neutron.tests.tempest.scenario.test_qos.QoSTest.test_qos
   fails in pike promotion jobs
   - Fix Released - #1737716 TripleO CI jobs fail: can't connect to
   nodepool hosts
   - #1737688 RDO CI quickstart job logs collection of dlrn logs is broken
   in tripleo-quickstart-extras-gate-master-tripleo-ci-
   delorean-full-minimal_pacemaker
   - #1737617 master promoter script looping and failing since 12/9 (should
   put a 2 hr timeout on the promioter script  - to tech debt for the sprint
   team)
   - #1737568 CI: fs035 OVB job fails to run mysql_init_bundle container  (
   still running on RH1 - could fix it there - contact HA people)
   - Fix Released - 1737502 Newton: RDO CI gate and phase1 promotion jobs
   fail with error "publicURL endpoint for workflowv2 service not found"
   because mistral is disabled
   - #1737485 CI: featureset020 (all tempest tests) promotion job fails
   with timeout on mtu test
   - Cron jobs of promotions scripts are commented, please uncomment them
   when RDO cloud is online and stable


We also have our new Ruck and Rover for this week:


   - Ruck
  - John Trownbridge - trown|ruck
   - Rover
  - Ronelle Landy - rlandy|rover


If you have any questions and/or suggestions, please contact us

[1] https://review.openstack.org/#/c/509280/

[2] https://review.openstack.org/#/c/525743/

[3]

[openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

2017-12-12 Thread Arx Cruz 
Hello

We are going to have a TripleO CI Community meeting tomorrow 12/13/2017 at
1 pm UTC time.
The meeting is going to happen on BlueJeans [1] and also on IRC on #tripleo
 channel.

After that, we will hold Office Hours starting at 4PM UTC in case someone
from community have any questions related to CI.

Hope to see you there.

1 - https://bluejeans.com/7071866728
<https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F7071866728=D=1510075851653000=AFQjCNE_gUUl_WZUBJfZO0otaEPP1j1ZoQ>


Kind regards,
Arx Cruz
__
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

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

2017-12-07 Thread Arx Cruz 
+1 !!!

On Thu, Dec 7, 2017 at 7:47 AM, Marios Andreou  wrote:

> +1 !
>
>
> On Wed, Dec 6, 2017 at 5:45 PM, Emilien Macchi  wrote:
>
>> Team,
>>
>> Wes has been consistently and heavily involved in TripleO CI work.
>> He has a very well understanding on how tripleo-quickstart and
>> tripleo-quickstart-extras work, his number and quality of reviews are
>> excellent so far. His experience with testing TripleO is more than
>> valuable.
>> Also, he's always here to help on TripleO CI issues or just
>> improvements (he's the guy filling bugs on a Saturday evening).
>> I think he would be a good addition to the TripleO CI core team
>> (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,
>> --
>> Emilien Macchi
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/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/mailman/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/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] TripleO CI Squad meeting

2017-12-05 Thread Arx Cruz 
Hello,

Here’s the highlights from TripleO CI Squad meeting from November 30



   - Roles
  - The Ruck and the Rover will be responsible for any CI problems, so
  if you have anything related to CI, please contact them. The rest of the
  team will work on the sprint
 - Ruck
- Matt Young, irc: myoung|ruck
 - Rover
- Sagi Shnaidman, irc: sshnaidm



   - Team
  - Arx Cruz
  - Ronelle Landy
  - Attila Darazs
  - Gabrielle Cerami
  - John Trowbridge



   - For this sprint 11/30/2017 - 12/13/2017
  - The proposed topic is make easy to developers reproduce CI jobs on
  their own RDO Cloud
 - Break up the upstream workflow for both ovb and multinode
 nodepool jobs into logical steps such that both CI and
developers can walk
 through a deployment step by step.
 - Update / Create a reproduce.sh script for TripleO-CI where a
 developer can download the script and reproduce the test
environment in
 RDO-Cloud.
  - The epic task with more information can be found here
  https://trello.com/c/EWotWxGe
  - Tasks can be found in both the trello card above, or in the TripleO
  CI Squad trello board using the filter by label “Sprint 4 (11/30/2017 -
  12/13/2017)” or clicking in this link here
  https://tinyurl.com/ycs4qelu



   - Promotions
  - Master promoted 12/5/2017
  - Pike promoted 12/2/2017
  - Ocata promoted 12/4/2017



   - Gate Jobs
  -
  
http://status.openstack.org/openstack-health/#/?searchProject=tripleo=build_name
 - The list of containers that are uploaded is currently a static
 list requiring updates.  This is less than ideal when devel adds new
 containers as it will cause gate failures.
- https://bugs.launchpad.net/tripleo/+bug/1736411
 - Scenario003 is failing periodically in the gate
- https://bugs.launchpad.net/tripleo/+bug/1736284




If you have any questions, suggestions please let us know. Your feedback is
very important to us!

Kind regards,
Arx Cruz
__
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

[openstack-dev] [tripleo] Newton promotion job now handled by rdo-phase1

2017-12-04 Thread Arx Cruz 
Hello,

Just a reminder that tripleo upstream newton promotion job is now handled
by rdo-phase1 until the EOL. We are also uploading uploading the overcloud
images manually to the upstream mirror server.

Kind regards,
Arx Cruz
__
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

[openstack-dev] [tripleo] TripleO CI end of sprint status

2017-12-01 Thread Arx Cruz 
ps://bugs.launchpad.net/tripleo/+bug/1734778
  - CI: Container multinode upgrades job does not upgrade overcloud
  from pike to queens/master
   - https://bugs.launchpad.net/tripleo/+bug/1735139
  - Error when deploying ceph in overcloud with containers using
  ceph-ansible
   - https://bugs.launchpad.net/tripleo/+bug/1735211
  - Master promotion fs002 and fs020 jobs are failing overcloud
  deployment on  ControllerDeployment_Step3




We also have our new Ruck and Rover for this week:


   - Ruck
  - Matt Young - myoung|ruck
   - Rover
  - Sagi Shnaidman - sshnaidm|rover


If you have any questions and/or suggestions, please contact us

Kind regards,
Arx Cruz

[1] https://review.openstack.org/#/c/509280/
__
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

Re: [openstack-dev] [TripleO] Proposing Ronelle Landy for Tripleo-Quickstart/Extras/CI core

2017-11-30 Thread Arx Cruz 
+1 well deserved!!!

On Thu, Nov 30, 2017 at 11:37 AM, Jiří Stránský  wrote:

> +1
>
>
> On 29.11.2017 20:34, 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 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.
>>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/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/mailman/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/mailman/listinfo/openstack-dev

[openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

2017-11-28 Thread Arx Cruz 
Hello

We are going to have a TripleO CI Community meeting tomorrow 11/29/2017 at
1 pm UTC time.
The meeting is going to happen on BlueJeans [1] and also on IRC on #tripleo
 channel.

After that, we will hold Office Hours starting at 4PM UTC in case someone
from community have any questions related to CI.

Hope to see you there.

1 - https://bluejeans.com/7071866728
<https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F7071866728=D=1510075851653000=AFQjCNE_gUUl_WZUBJfZO0otaEPP1j1ZoQ>


Kind regards,
Arx Cruz
__
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

[openstack-dev] [tripleo] TripleO CI end of sprint status

2017-11-15 Thread Arx Cruz 
Hello,

On November 13 we came the end of sprint using our new team structure [1],
and here’s the highlights:

Sprint Review:

The sprint epic was Reproduce of upstream CI jobs against RDO cloud
personal tenant [2] in order to help our Ruck and Rover to reproduce CI
issues.

It was we set several cards each with one specific task to achieve our
objective, and I am glad to report that we were able to complete it and now
the Ruck and Rover have a easy tool to reproduce CI issues upstream.

There are some reviews pending to be merged, but we are considering the
work done. You can try it by following the documentation [3]! I'm also
happy to say that in this sprint, we have only one card in tech debt!

One can see the results of the sprint via https://tinyurl.com/ybfds8p3

List of what was done by the Ruck and Rover:

   -

   https://bugs.launchpad.net/tripleo/+bug/1729586
   -

   https://bugs.launchpad.net/tripleo/+bug/1729328
   -

   https://bugs.launchpad.net/tripleo/+bug/1728135
   -

   https://bugs.launchpad.net/tripleo/+bug/1728070


We also have our new Ruck and Rover for this wee:

   - Ruck
  - Attila Darazs - adaras|ruck
   - Rover
  - Ronelle Landy - rlandy|rover


If you have any questions and/or sugestions, please contact us

Kind regards,
Arx Cruz

[1] https://review.openstack.org/#/c/509280/

[2] https://trello.com/c/aPuHTfo4

[3] https://etherpad.openstack.org/p/ruck-rover-reproduce-jobs
__
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

[openstack-dev] [tripleo] TripleO CI Community meeting November 8

2017-11-09 Thread Arx Cruz 
Hello,

Here's the highlights from TripleO CI Community meeting from November 8.

   - Promotion is now stabilized and started to happen often
  - The same for Pike and Ocata
   - We are having a problem with the zuul gate queue - 24 hours
   approximately
  - For more info check http://lists.openstack.org/
  pipermail/openstack-dev/2017-November/124294.html
  
<http://lists.openstack.org/pipermail/openstack-dev/2017-November/124294.html>
  - Today 8 hours +-
  - CI team are continue to work in order to identify the root cause
  - Hold all the changes on gate until we hear from Alex that we have
  green light.
   - Removal of upgrade jobs from upstream and move it to rdo cloud
  - We had a discussion with the upgrade team, and they will work with
  us to have it migrated to rdo cloud
 - The idea is use tripleo-upgrade role in quickstart
  - Right now, there are some experimental jobs that can be triggered
  in the experimental queue on rdo cloud
   - Moving the community meeting for 2pm UTC
  - Due the daylight saving time
   - Devmode is broken by latest patch
  - The reason is because some patches are not merged yet (depends on
  zuul gate queue)
  - Attila Darazs is working on this
   - OVB Migration
  - Jobs are running pretty well
  - rdo cloud wasn't updated yet
  - Still in progress
  - https://bugs.launchpad.net/tripleo/+bug/1724328

Kind regards,
Arx Cruz
__
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

Re: [openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

2017-11-07 Thread Arx Cruz 
Correction, tomorrow 11/08/2017

On Tue, Nov 7, 2017 at 4:31 PM, Arx Cruz <arxc...@redhat.com> wrote:

> Hello
>
> We are going to have a TripleO CI Community meeting tomorrow 11/07/2017
> at 1 pm UTC time.
> The meeting is going to happen on BlueJeans [1] and also on IRC on
> #tripleo channel.
>
> After that, we will hold Office Hours starting at 4PM UTC in case someone
> from community have any questions related to CI.
>
> Hope to see you there.
>
> 1 - https://bluejeans.com/7071866728
> <https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F7071866728=D=1510075851653000=AFQjCNE_gUUl_WZUBJfZO0otaEPP1j1ZoQ>
>
>
> Kind regards,
> Arx Cruz
>
__
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

[openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

2017-11-07 Thread Arx Cruz 
Hello

We are going to have a TripleO CI Community meeting tomorrow 11/07/2017 at
1 pm UTC time.
The meeting is going to happen on BlueJeans [1] and also on IRC on #tripleo
channel.

After that, we will hold Office Hours starting at 4PM UTC in case someone
from community have any questions related to CI.

Hope to see you there.

1 - https://bluejeans.com/7071866728
<https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F7071866728=D=1510075851653000=AFQjCNE_gUUl_WZUBJfZO0otaEPP1j1ZoQ>


Kind regards,
Arx Cruz
__
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

[openstack-dev] [tripleo] TripleO Ci Squad meeting

2017-11-06 Thread Arx Cruz 
Hello,

A little bit late but here’s the highlights from TripleO CI Squad meeting
from October 26

   - Roles
  - The Ruck and the Rover will be responsible for any CI problems, so
  if you have anything related to CI, please contact them. The rest of the
  team will work on the sprint
  - Ruck
 - Gabrielle Cerami, irc: panda|ruck
  - Rover
 - Attila Darazs, irc: adarazs|rover
  - Backup
  - Ronelly Landy, irc rlandy
 - Matt Young, irc myoung
  - Team
   - Arx Cruz
  - Ronelle Landy
  - Sagi Shnaidman
  - John Trowbridge
  - For this sprint 10/26/2017 - 11/8/2017
   - After review the proposed topics from the UA, the team voted to work
  on Reproduce of upstream CI jobs against RDO cloud personal tenant
  - The epic task with more information can be found here
  
https://trello.com/c/aPuHTfo4/404-reproduce-of-upstream-ci-jobs-against-rdo-cloud-personal-tenant
  - Tasks can be found in both the trello card above, or in the TripleO
  CI Squad trello board using the filter by label “Sprint 3  ( Oct 26 - Nov
  8)” or clicking in this link here https://tinyurl.com/ybfds8p3


If you have any questions, suggestions please let us know. Your feedback is
very important to us!

Kind regards,
Arx Cruz
__
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

Re: [openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

2017-11-01 Thread Arx Cruz 
The idea is to have the community meeting at the end of our sprint. So far,
we are having 2 weeks sprint, but we are thinking about flexible sprints,
depending of the scope of our work. For now, yes, it’s regular, but once we
adopt flexible sprint, it will change.

Kind regards,
Arx Cruz

On Tue, 24 Oct 2017 at 17:56 Emilien Macchi <emil...@redhat.com> wrote:

> On Tue, Oct 24, 2017 at 8:50 AM, Arx Cruz <arxc...@redhat.com> wrote:
> > Hello
> >
> > We are going to have a TripleO CI Community meeting tomorrow 10/25/2017
> at 1
> > pm UTC time.
> > The meeting is going to happen on BlueJeans [1] and also on IRC on
> #tripleo
> > channel.
> >
> > After that, we will hold Office Hours starting at 4PM UTC in case someone
> > from community have any questions related to CI.
> >
> > Hope to see you there.
> >
> > 1 - https://bluejeans.com/7071866728
> >
> >
> > Kind regards,
> > Arx Cruz
>
> quick question, is it a regular time or will it change in the future?
>
> (so I can update my calendar)
>
> Thanks,
> --
> Emilien Macchi
>
> __
> 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
>
__
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

[openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

2017-10-24 Thread Arx Cruz 
Hello

We are going to have a TripleO CI Community meeting tomorrow 10/25/2017 at
1 pm UTC time.
The meeting is going to happen on BlueJeans [1] and also on IRC on #tripleo
 channel.

After that, we will hold Office Hours starting at 4PM UTC in case someone
from community have any questions related to CI.

Hope to see you there.

1 - https://bluejeans.com/7071866728
<https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F7071866728=D=1508867299727000=AFQjCNHcZW8-fJjAew24KFECzrgWmJexeg>


Kind regards,
Arx Cruz
__
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

[openstack-dev] [tripleo] TripleO CI Squad meeting - Oct 11

2017-10-12 Thread Arx Cruz 
Hello,

Here’s the highlights from TripleO CI Squad meeting from October 11


   -

   Roles
   -

  The Ruck and the Rover will be responsible for any CI problems, so if
  you have anything related to CI, please contact them. The rest
of the team
  will work on the sprint
  -

 Ruck
 -

Wes Hayutin, irc: weshay|ruck
-

 Rover
 -

Gabrielle Cerami, irc: panda|rover
-

   Team
   -

  Arx Cruz
  -

  Ronelle Landy
  -

  Attila Darazs
  -

  Sagi Shnaidman
  -

  John Trowbridge



   -

   For this sprint 10/11/2017 - 10/25/2017
   -

  After review the proposed topics from the UA, the team voted to work
  on OVB migration to RDO cloud and related work.
  -

  The epic task with more information can be found here
  
https://trello.com/c/wyUOPIhP/377-ovb-migration-to-rdo-cloud-and-related-work



   -

   Tasks can be found in both the trello card above, or in the TripleO CI
   Squad trello board using the filter by label “Sprint 2 ( 10/11/2017 -
   10/25/2017 )” or clicking in this link here https://tinyurl.com/yb2mkpwv


If you have any questions, suggestions please let us know. Your feedback is
very important to us!


Kind regards,

Arx Cruz
__
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

[openstack-dev] [tripleo] TripleO CI end of sprint status

2017-10-11 Thread Arx Cruz 
Sorry, I forgot to add [tripleo] tag.


Hello,

On October 10 we came to our first end of sprint using our new team
structure [1], and here’s the highlights:

TripleO CI Infra meeting notes:


   -

   Zuul v3 related patch:
   -

  The new Zuul v3 doesn’t have the cirros image cached, so we have a
  patch to change the tempest image to default value, that is download the
  image from cirros website.
  -

 https://review.openstack.org/510839
 -

   Zuul migration
   -

  There will have an outage in order to fix some issues found during
  the Zuul migration to v3
  -

 http://lists.openstack.org/pipermail/openstack-dev/2017-
 October/123337.html
 -

   Job for migration
   -

  We are planning to start moving some jobs rom rh1 cloud to rdo cloud.
  -

   RDO Software Factory outage
   -

  There were an outage on RDO cloud on October 9, some jobs were
  stalled for a long time, now everything is working.


Sprint Review:

The sprint epic was utilizing the DLRN api across TripleO and RDO [2] to
report job status and promotions, and we set several tasks in 20 cards, and
I am glad to report that we were able to complete 19 cards! Some of these
cards generate some tech debts, and after a review, we got 11 card in the
tech debt list, plus 3 new bugs opened and XYZ bugs closed by the Ruck and
Rover.

One can see the results of the sprint via https://tinyurl.com/yblqs5z2

Below the list of new bugs related to the work completed in the sprint:


   -

   https://bugs.launchpad.net/tripleo/+bug/1722552
   -

   https://bugs.launchpad.net/tripleo/+bug/1722554
   -

   https://bugs.launchpad.net/tripleo/+bug/1722558


And here the list of what was done by the Ruck and Rover:

   -

   https://bugs.launchpad.net/tripleo/+bug/1722640
   -

   https://bugs.launchpad.net/tripleo/+bug/1722621
   -

   https://bugs.launchpad.net/tripleo/+bug/1722596
   -

   https://bugs.launchpad.net/tripleo/+bug/1721790
   -

   https://bugs.launchpad.net/tripleo/+bug/1721366
   -

   https://bugs.launchpad.net/tripleo/+bug/1721134
   -

   https://bugs.launchpad.net/tripleo/+bug/1720556
   -

   https://bugs.launchpad.net/tripleo/+bug/1719902
   -

   https://bugs.launchpad.net/tripleo/+bug/1719421



[1] https://review.openstack.org/#/c/509280/

[2] https://trello.com/c/5FnfGByl
__
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

[openstack-dev] TripleO CI end of sprint status

2017-10-11 Thread Arx Cruz 
Hello,

On October 10 we came to our first end of sprint using our new team
structure [1], and here’s the highlights:

TripleO CI Infra meeting notes:


   -

   Zuul v3 related patch:
   -

  The new Zuul v3 doesn’t have the cirros image cached, so we have a
  patch to change the tempest image to default value, that is download the
  image from cirros website.
  -

 https://review.openstack.org/510839
 -

   Zuul migration
   -

  There will have an outage in order to fix some issues found during
  the Zuul migration to v3
  -


 
http://lists.openstack.org/pipermail/openstack-dev/2017-October/123337.html
 -

   Job for migration
   -

  We are planning to start moving some jobs rom rh1 cloud to rdo cloud.
  -

   RDO Software Factory outage
   -

  There were an outage on RDO cloud on October 9, some jobs were
  stalled for a long time, now everything is working.


Sprint Review:

The sprint epic was utilizing the DLRN api across TripleO and RDO [2] to
report job status and promotions, and we set several tasks in 20 cards, and
I am glad to report that we were able to complete 19 cards! Some of these
cards generate some tech debts, and after a review, we got 11 card in the
tech debt list, plus 3 new bugs opened and XYZ bugs closed by the Ruck and
Rover.

One can see the results of the sprint via https://tinyurl.com/yblqs5z2

Below the list of new bugs related to the work completed in the sprint:


   -

   https://bugs.launchpad.net/tripleo/+bug/1722552
   -

   https://bugs.launchpad.net/tripleo/+bug/1722554
   -

   https://bugs.launchpad.net/tripleo/+bug/1722558


And here the list of what was done by the Ruck and Rover:

   -

   https://bugs.launchpad.net/tripleo/+bug/1722640
   -

   https://bugs.launchpad.net/tripleo/+bug/1722621
   -

   https://bugs.launchpad.net/tripleo/+bug/1722596
   -

   https://bugs.launchpad.net/tripleo/+bug/1721790
   -

   https://bugs.launchpad.net/tripleo/+bug/1721366
   -

   https://bugs.launchpad.net/tripleo/+bug/1721134
   -

   https://bugs.launchpad.net/tripleo/+bug/1720556
   -

   https://bugs.launchpad.net/tripleo/+bug/1719902
   -

   https://bugs.launchpad.net/tripleo/+bug/1719421



[1] https://review.openstack.org/#/c/509280/

[2] https://trello.com/c/5FnfGByl
__
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

Re: [openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

2017-10-10 Thread Arx Cruz 
Hello,

Sorry for the mistake, the bluejeans meeting is in
https://bluejeans.com/u/whayutin/

Kind regards,
Arx Cruz

On Mon, Oct 9, 2017 at 6:29 PM, Arx Cruz <arxc...@redhat.com> wrote:

> Hello
>
> We are going to have a TripleO CI Community meeting tomorrow 10/10/2017 at
> 1 pm UTC time.
> The meeting is going to happen on BlueJeans [1] and also on IRC on
> #tripleo channel.
>
> After that, we will hold Office Hours starting at 4PM UTC in case someone
> from community have any questions related to CI.
>
> Hope to see you there.
>
> 1 - https://bluejeans.com/287352206?src=calendarLink
> <https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F287352206%3Fsrc%3DcalendarLink=D=1507571288925000=AFQjCNHq96rkvy2zVXpCuawqvpJW8CxwiQ>
>
>
> Kind regards,
> Arx Cruz
>
__
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

[openstack-dev] [tripleo] Tripleo CI Community meeting tomorrow

2017-10-09 Thread Arx Cruz 
Hello

We are going to have a TripleO CI Community meeting tomorrow 10/10/2017 at
1 pm UTC time.
The meeting is going to happen on BlueJeans [1] and also on IRC on #tripleo
channel.

After that, we will hold Office Hours starting at 4PM UTC in case someone
from community have any questions related to CI.

Hope to see you there.

1 - https://bluejeans.com/287352206?src=calendarLink
<https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F287352206%3Fsrc%3DcalendarLink=D=1507571288925000=AFQjCNHq96rkvy2zVXpCuawqvpJW8CxwiQ>


Kind regards,
Arx Cruz
__
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

[openstack-dev] [tripleo] Tripleo tempest results in openstack-health

2017-05-10 Thread Arx Cruz 
Hello,

Since last week, we have two periodic tripleo jobs running full tempest run
upstream with tripleo-quickstart:

The first job runs tempest against ocata release [1]
The second job runs tempest against master release [2]

Good news is on ocata, we are having full tempest run with 100% pass mostly
of the time, with one or two tests failing, probably because some
concurrency or network issues.
In master, we are having around 17 failures which I'm working to debug and
fix.

These jobs are now showing up in openstack-health, which gave us more
visibility, and several data like, how often these jobs are failing, etc,
and developers can also subscribe to the rss feed.

And also, we are generating the stackviz report, which makes easy to see
the failures, passes, logs from the failures, network, cpu and io status,
etc. An example you can see here [3]

For the future, we want to collect these data, and according with which
test had failed send an email to key developers to debug the failure.

That's the news for now!

[1] - http://status.openstack.org/openstack-health/#/job/
periodic-tripleo-ci-centos-7-ovb-nonha-tempest-oooq-ocata
[2] - http://status.openstack.org/openstack-health/#/job/
periodic-tripleo-ci-centos-7-ovb-nonha-tempest-oooq-master
[3] - http://logs.openstack.org/periodic/periodic-tripleo-ci-
centos-7-ovb-nonha-tempest-oooq-master/799e5e3/logs/oooq/stackviz/#/stdin

Kind regards,
Arx Cruz
__
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

Re: [openstack-dev] [tripleo] pingtest vs tempest

2017-05-04 Thread Arx Cruz 
On Wed, May 3, 2017 at 11:53 PM, Emilien Macchi <emil...@redhat.com> wrote:

> (cross-posting)
>
> I've seen a bunch of interesting thoughts here.
> The most relevant feedback I've seen so far:
>
> - TripleO folks want to keep testing fast and efficient.
> - Tempest folks understand this problematic and is willing to collaborate.
>
> I propose that we move forward and experiment the usage of Tempest in
> TripleO CI for one job that could be experimental or non-voting to
> start.
> Instead of running the Pingtest, we would execute a Tempest Scenario
> that boot an instance from volume (like Pingstest is already doing)
> and see how it goes (in term of coverage and runtime).
> I volunteer to kick-off the work with someone more expert than I am
> with quickstart (Arx maybe?).
>
>
Sure, let's work on that :)


> Another iteration could be to start building an easy interface to
> select which Tempest tests we want a TripleO CI job to run and plug it
> to our CI tooling (tripleo-quickstart I presume).
> I also hear some feedback about keeping the pingtest alive for some
> uses cases, and I agree we could keep some CI jobs to run the pingtest
> when it makes more sense (when we want to test Heat for example, or
> just maintain it for developers who used it).
>
> How does it sounds? Please bring feedback.
>
>
> On Tue, Apr 18, 2017 at 7:41 AM, Attila Fazekas <afaze...@redhat.com>
> wrote:
> >
> >
> > On Tue, Apr 18, 2017 at 11:04 AM, Arx Cruz <arxc...@redhat.com> wrote:
> >>
> >>
> >>
> >> On Tue, Apr 18, 2017 at 10:42 AM, Steven Hardy <sha...@redhat.com>
> wrote:
> >>>
> >>> On Mon, Apr 17, 2017 at 12:48:32PM -0400, Justin Kilpatrick wrote:
> >>> > On Mon, Apr 17, 2017 at 12:28 PM, Ben Nemec <openst...@nemebean.com>
> >>> > wrote:
> >>> > > Tempest isn't really either of those things.  According to another
> >>> > > message
> >>> > > in this thread it takes around 15 minutes to run just the smoke
> >>> > > tests.
> >>> > > That's unacceptable for a lot of our CI jobs.
> >>> >
> >>
> >>
> >> I rather spend 15 minutes running tempest than add a regression or a new
> >> bug, which already happen in the past.
> >>
> > The smoke tests might not be the best test selection anyway, you should
> pick
> > some scenario which does
> > for example snapshot of images and volumes. yes, these are the slow ones,
> > but they can run in parallel.
> >
> > Very likely you do not really want to run all tempest test, but 10~20
> minute
> > time,
> > sounds reasonable for a sanity test.
> >
> > The tempest config utility also should be extended by some parallel
> > capability,
> > and should be able to use already downloaded (part of the image)
> resources.
> >
> > Tempest/testr/subunit worker balance is not always the best,
> > technically would be possible to do dynamic balancing, but it would
> require
> > a lot of work.
> > Let me know when it becomes the main concern, I can check what
> can/cannot be
> > done.
> >
> >
> >>
> >>>
> >>> > Ben, is the issue merely the time it takes? Is it the affect that
> time
> >>> > taken has on hardware availability?
> >>>
> >>> It's both, but the main constraint is the infra job timeout, which is
> >>> about
> >>> 2.5hrs - if you look at our current jobs many regularly get close to
> (and
> >>> sometimes exceed this), so we just don't have the time budget available
> >>> to
> >>> run exhasutive tests every commit.
> >>
> >>
> >> We have green light from infra to increase the job timeout to 5 hours,
> we
> >> do that in our periodic full tempest job.
> >
> >
> > Sounds good, but I am afraid it could hurt more than helping, it could
> delay
> > other things get fixed by lot
> > especially if we got some extra flakiness, because of foobar.
> >
> > You cannot have all possible tripleo configs on the gate anyway,
> > so something will pass which will require a quick fix.
> >
> > IMHO the only real solution, is making the before test-run steps faster
> or
> > shorter.
> >
> > Do you have any option to start the tempest running jobs in a more
> developed
> > state ?
> > I mean, having more things already done at the start time
> (images/snapshot)
> > and just do a fast upgrade at the beginning of the job.

Re: [openstack-dev] [tripleo] pingtest vs tempest

2017-04-18 Thread Arx Cruz 
On Tue, Apr 18, 2017 at 10:42 AM, Steven Hardy  wrote:

> On Mon, Apr 17, 2017 at 12:48:32PM -0400, Justin Kilpatrick wrote:
> > On Mon, Apr 17, 2017 at 12:28 PM, Ben Nemec 
> wrote:
> > > Tempest isn't really either of those things.  According to another
> message
> > > in this thread it takes around 15 minutes to run just the smoke tests.
> > > That's unacceptable for a lot of our CI jobs.
> >
>

I rather spend 15 minutes running tempest than add a regression or a new
bug, which already happen in the past.


> > Ben, is the issue merely the time it takes? Is it the affect that time
> > taken has on hardware availability?
>
> It's both, but the main constraint is the infra job timeout, which is about
> 2.5hrs - if you look at our current jobs many regularly get close to (and
> sometimes exceed this), so we just don't have the time budget available to
> run exhasutive tests every commit.
>

We have green light from infra to increase the job timeout to 5 hours, we
do that in our periodic full tempest job.


>
> > Should we focus on how much testing we can get into N time period?
> > Then how do we decide an optimal N
> > for our constraints?
>
> Well yeah, but that's pretty much how/why we ended up with pingtest, it's
> simple, fast, and provides an efficient way to do smoke tests, e.g creating
> just one heat resource is enough to prove multiple OpenStack services are
> running, as well as the DB/RPC etc etc.
>
> > I've been working on a full up functional test for OpenStack CI builds
> > for a long time now, it works but takes
> > more than 10 hours. IF you're interested in results kick through to
> > Kibana here [0]. Let me know off list if you
> > have any issues, the presentation of this data is all experimental still.
>
> This kind of thing is great, and I'd support more exhaustive testing via
> periodic jobs etc, but the reality is we need to focus on "bang for buck"
> e.g the deepest possible coverage in the most minimal amount of time for
> our per-commit tests - we rely on the project gates to provide a full API
> surface test, and we need to focus on more basic things like "did the
> service
> start", and "is the API accessible".  Simple crud operations on a subset of
> the API's is totally fine for this IMO, whether via pingtest or some other
> means.
>
>
Right now we do have a periodic job running full tempest, with a few skips,
and because of the lack of tempest tests in the patches, it's being pretty
hard to keep it stable enough to have a 100% pass, and of course, also the
installation very often fails (like in the last five days).
For example, [1] is the latest run we have in periodic job that we get
results from tempest, and we have 114 failures that was caused by some new
code/change, and I have no idea which one was, just looking at the
failures, I can notice that smoke tests plus minimum basic scenario tests
would catch these failures and the developer could fix it and make me happy
:)
Now I have to spend several hours installing and debugging each one of
those tests to identify where/why it fails.
Before this run, we got 100% pass, but unfortunately I don't have the
results anymore, it was removed already from logs.openstack.org



> Steve
>
> __
> 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]
http://logs.openstack.org/periodic/periodic-tripleo-ci-centos-7-ovb-nonha-tempest-oooq/0072651/logs/oooq/stackviz/#/stdin
__
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

Re: [openstack-dev] [tripleo] pingtest vs tempest

2017-04-06 Thread Arx Cruz 
I would say smoke tests, and at least the minimum scenario tests.
Smoke tests takes 14 minutes (113 tests) to run, and I can check how long
it takes the minimum scenario tests later. So it won't take a long time
running.

Kind regards,
Arx Cruz

On Thu, Apr 6, 2017 at 2:44 PM, Andrea Frittoli <andrea.fritt...@gmail.com>
wrote:

> I don't really have much context in what the decision is going to be based
> on here,
> so I'll just add some random comments here and there.
>
> On Thu, Apr 6, 2017 at 12:48 PM Arx Cruz <arxc...@redhat.com> wrote:
>
>> Having tempest running will allow these jobs to appear in
>> openstack-health system as well.
>>
>
> I agree that's a plus. It's also rather easy to produce subunit from
> whatever you
> are using to run tests, and that's all you need in fact to get data into
> open stack-health
> without touching the existing infrastructure. So in case you decide not to
> use Tempest,
> open stack-health can still be on the list.
>
>
>>
>> On Thu, Apr 6, 2017 at 1:29 PM, Justin Kilpatrick <jkilp...@redhat.com>
>> wrote:
>>
>> Maybe I'm getting a little off topic with this question, but why was
>> Tempest removed last time?
>>
>> I'm not well versed in the history of this discussion, but from what I
>> understand Tempest in the gate has
>> been an off and on again thing for a while but I've never heard the
>> story of why it got removed.
>>
>> On Thu, Apr 6, 2017 at 7:00 AM, Chris Dent <cdent...@anticdent.org>
>> wrote:
>> > On Thu, 6 Apr 2017, Sagi Shnaidman wrote:
>> >
>> >> It may be useful to run a "limited edition" of API tests that maximize
>> >> coverage and don't duplicate, for example just to check service working
>> >> basically, without covering all its functionality. It will take very
>> >> little
>> >> time (i.e. 5 tests for each service) and will give a general picture of
>> >> deployment success. It will cover fields that are not covered by
>> pingtest
>> >> as well.
>>
>> >
>>
>>
> We have a smoke attribute here an there, but it's not well curated at all,
> so you're
> probably better off maintaining your own list.
> Since presumably you're more interested in verifying that a deployed cloud
> is
> functional - as opposed to verify specific APIs are working properly - you
> may want
> to look at scenario tests, where with a couple of test you can cover
> already a lot of
> basic stuff, e.g. if you can boot a server from a volume with an image
> from glance,
> and ssh into it, you have proven a lot already about the general health of
> your cloud.
>
>
>> >
>> > It's sound like using some parts of tempest is perhaps the desired
>> > thing here but in case a "limited edition" test against the APIs to
>> > do what amounts to a smoke test is desired, it might be worthwhile
>> > to investigate using gabbi[1] and its command line gabbi-run[2] tool for
>> > some fairly simple and readable tests that can describe a sequence
>> > of API interactions. There are lots of tools that can do the same
>> > thing, so gabbi may not be the right choice but it's there as an
>> > option.
>> >
>> > The telemetry group had (an may still have) some integration tests
>> > that use gabbi files to integrate ceilometer, heat (starting some
>> > vms), aodh and gnocchi and confirm that the expected flow happened.
>> > Since the earlier raw scripts I think there's been some integration
>> > with tempest, but gabbi files are still used[3].
>> >
>> > If this might be useful and I can help out, please ask.
>> >
>> > [1] http://gabbi.readthedocs.io/
>> > [2] http://gabbi.readthedocs.io/en/latest/runner.html
>> > [3]
>> > https://github.com/openstack/ceilometer/tree/master/
>> ceilometer/tests/integration
>> >
>> > --
>> > Chris Dent ¯\_(ツ)_/¯   https://anticdent.org/
>> > freenode: cdent tw: @anticdent
>> > 
>> __
>> > 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
>> >
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usag

Re: [openstack-dev] [tripleo] pingtest vs tempest

2017-04-06 Thread Arx Cruz 
Having tempest running will allow these jobs to appear in openstack-health
system as well.

On Thu, Apr 6, 2017 at 1:29 PM, Justin Kilpatrick 
wrote:

> Maybe I'm getting a little off topic with this question, but why was
> Tempest removed last time?
>
> I'm not well versed in the history of this discussion, but from what I
> understand Tempest in the gate has
> been an off and on again thing for a while but I've never heard the
> story of why it got removed.
>
> On Thu, Apr 6, 2017 at 7:00 AM, Chris Dent  wrote:
> > On Thu, 6 Apr 2017, Sagi Shnaidman wrote:
> >
> >> It may be useful to run a "limited edition" of API tests that maximize
> >> coverage and don't duplicate, for example just to check service working
> >> basically, without covering all its functionality. It will take very
> >> little
> >> time (i.e. 5 tests for each service) and will give a general picture of
> >> deployment success. It will cover fields that are not covered by
> pingtest
> >> as well.
> >
> >
> > It's sound like using some parts of tempest is perhaps the desired
> > thing here but in case a "limited edition" test against the APIs to
> > do what amounts to a smoke test is desired, it might be worthwhile
> > to investigate using gabbi[1] and its command line gabbi-run[2] tool for
> > some fairly simple and readable tests that can describe a sequence
> > of API interactions. There are lots of tools that can do the same
> > thing, so gabbi may not be the right choice but it's there as an
> > option.
> >
> > The telemetry group had (an may still have) some integration tests
> > that use gabbi files to integrate ceilometer, heat (starting some
> > vms), aodh and gnocchi and confirm that the expected flow happened.
> > Since the earlier raw scripts I think there's been some integration
> > with tempest, but gabbi files are still used[3].
> >
> > If this might be useful and I can help out, please ask.
> >
> > [1] http://gabbi.readthedocs.io/
> > [2] http://gabbi.readthedocs.io/en/latest/runner.html
> > [3]
> > https://github.com/openstack/ceilometer/tree/master/
> ceilometer/tests/integration
> >
> > --
> > Chris Dent ¯\_(ツ)_/¯   https://anticdent.org/
> > freenode: cdent tw: @anticdent
> > 
> __
> > 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
> >
>
> __
> 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
>
__
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