Re: [openstack-dev] [tripleo] The Weekly Owl - 1st Edition

[Ronelle Landy]

This is a great overview - and a valuable point of reference.
Thanks Emilien!

On Wed, Dec 6, 2017 at 1:46 AM, Marios Andreou  wrote:

>
>
> On Tue, Dec 5, 2017 at 9:48 PM, Emilien Macchi  wrote:
>
>> Note: this is the first edition of a weekly update of what happens in
>> TripleO. The goal is to provide a short reading (less than 5 minutes)
>> to learn where we are and what we're doing.
>> Any contributions or feedback are welcome.
>>
>
> ++ fwiw it is really nice to have all the status in one place like this
> thanks for taking the time to put it together
>
>
>
>>
>>
>>
>> +--+
>> | Continuous Integration |
>> +--+
>>
>> +--> New rover is Sagi and new ruck is Matt. Please let them know any
>> new CI issue.
>> +--> Team will focus on developers reproduce CI jobs on their own RDO
>> Cloud (https://trello.com/c/EWotWxGe)
>> +--> Promotions look good so far: Master promoted 12/5/2017 - Pike
>> promoted 12/2/2017 - Ocata promoted 12/4/2017
>> +--> Newton promotion job now handled by rdo-phase1
>> +--> More: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
>>
>> +-+
>> | Upgrades |
>> +-+
>>
>> +--> Some experimental jobs are WIP to test Fast Forward Upgrades (aka
>> FFU). Reviews are needed on https://review.rdoproject.org/r/#/c/10827
>> and https://review.openstack.org/#/q/topic:ffu/ci+(status:open+O
>> R+status:merged).
>> +--> Some work is being done to make upgrade jobs working from Ocata
>> to Pike in RDO CI - and in the same time some bugs are being fixed
>> regarding this upgrade path.
>> +--> tripleo-upgrade upstream repository is being updated from the old
>> repo, the team is working on it.
>> +--> More: https://etherpad.openstack.org/p/tripleo-upgrade-squad-status
>> and https://etherpad.openstack.org/p/tripleo-upgrade-squad-meeting
>>
>> +---+
>> | Containers |
>> +---+
>>
>> +--> k8s: good progress on CI when deploying with Kubespray.
>> +--> k8s: working on getting tempest working for ansible-role-k8s-* repos
>> +--> k8s: migrated ansible-role-k8s-glance from external github under
>> `openstack`
>> +--> undercloud: some progress has been made but some bugs are
>> currently under investigation (idempotency issues, Registry config,
>> etc).
>> +--> overcloud: work in progress on image prepare workflows
>> +--> overcloud: Paunch now explicitly pulls images before docker run.
>> +--> overcloud: we can now have the port in the image name and tag
>> discover will still work fine.
>> +--> More: https://etherpad.openstack.org/p/tripleo-containers-squad-
>> status
>>
>> +--+
>> | Integration |
>> +--+
>>
>> +--> The team is working on Multiple Ceph clusters blueprint and
>> Multiple Ceph pools for Cinder.
>> +--> The team is preparing the integration to deploy Ceph Luminous!
>> +--> Some backports are being done to resolve a CVE:
>> https://review.openstack.org/#/q/topic:bug/1720787+(status:o
>> pen+OR+status:merged)
>> +--> More: https://etherpad.openstack.org/p/tripleo-integration-squad-
>> status
>>
>> +-+
>> | UI/CLI |
>> +-+
>>
>> +--> Roles management ready for review on GUI side, waiting for
>> tripleo-common patches to get finished.
>> +--> Nodes registration refactoring merged.
>> +--> The team is still working on testing Pike.
>> +--> Layout changes and refactoring patchset merged
>> +--> More: https://etherpad.openstack.org/p/tripleo-ui-cli-squad-status
>>
>> +---+
>> | Validations |
>> +---+
>> +--> The team has requested more review from TripleO developers,
>> please help if you can!
>> https://etherpad.openstack.org/p/validations-reviews
>> +--> More: https://etherpad.openstack.org/p/tripleo-validations-squad-
>> status
>>
>> +---+
>> | Networking |
>> +---+
>> +--> In the last meeting, the team discussed about the future of
>> os-net-config, routed-networks and OVS containerization.
>> +--> In the next meeting, the team will discuss about how we can
>> prepare nodes for NFV features and the state of  tests for
>> containerized deployments and networking.
>> +--> Some folks are also focused on Octavia integration.
>> +--> More: https://etherpad.openstack.org/p/tripleo-networking-squad-
>> status
>>
>> +--+
>> | Workflows |
>> +--+
>>
>> +--> No update this week.
>> +--> More: https://etherpad.openstack.org/p/tripleo-workflows-squad-sta
>> tus
>>
>> ++
>> | Weekly Owl |
>> ++
>>
>> The Barn Owl (aka Tyto alba) is a medium sized owl with no ear-tufts
>> and a heart-shaped face. These pale, nearly worldwide birds are
>> closely associated with man through their traditional use of barn
>> lofts and church steeples as nesting sites. The species name "alba"
>> refers to the white color. Other names for the Barn Owl have included
>> Monkey-faced Owl, Ghost Owl, and Church Owl. (source:
>> 

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

[Ronelle Landy]

+1

On Thu, Dec 7, 2017 at 8:47 AM, Brad P. Crochet  wrote:

> +1
>
>
> On Wed, Dec 6, 2017 at 10:46 AM 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:
>> 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 <(704)%20236-9385>
>
>
> __
> 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][ci] TripleO OVB check gates to move to third party

[Ronelle Landy]

Greetings,

TripleO OVB check gates are managed by upstream Zuul and executed on nodes
provided by test cloud RH1. RDO Cloud is now available as a test cloud to
be used when running CI jobs. To utilize to RDO Cloud, we could either:

- continue to run from upstream Zuul (and spin up nodes to deploy the
overcloud from RDO Cloud)
- switch the TripleO OVB check gates to run as third party and manage
these jobs from the Zuul instance used by Software Factory

The openstack infra team advocates moving to third party.
The CI team is meeting with Frederic Lepied, Alan Pevec, and other members
of the Software Factory/RDO project infra tream to discuss how this move
could be managed.

Note: multinode jobs are not impacted - and will continue to run from
upstream Zuul on nodes provided by nodepool.

Since a move to third party could have significant impact, we are posting
this out to gather feedback and/or concerns that TripleO developers may
have.


Thanks!
__
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] OVB deployments for developers using tripleo-quickstart devmode

[Ronelle Landy]

Hello,

tripleo-quickstart devmode [1] is used by TripleO developers to test unmerged 
changes in review.openstack.org locally and reproduce the upstream TripleO CI.
Functionality has been added to tripleo-quickstart devmode to allow users to 
run TripleO deployments on an OVB host cloud.

See the documentation [2] for instructions on how to do a basic TripleO 
deployment with devmode.sh,
as well as more in-depth instructions on options like:
 - Removing old stacks and key pairs from the host cloud before deploying
 - Testing patches
 - Using alternative configurations/network isolation types

[1] - https://docs.openstack.org/developer/tripleo-quickstart/devmode.html
[2] - https://docs.openstack.org/developer/tripleo-quickstart/devmode-ovb.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