Re: [openstack-dev] [tripleo] Proposing Jose Luis Franco for TripleO core reviewer on Upgrade bits

[Carlos Camacho Gonzalez]

Thank you Jose Luis for the work,

Let's keep the thread open until July 31st and iif there is no veto I'll
grant you the correct permissions.

Cheers,
Carlos.

On Fri, Jul 20, 2018 at 2:55 PM, Jose Luis Franco Arza 
wrote:

> Thank you very much to all for the recognition.
> I will use this power with responsibility, as Uncle Ben once said:
> https://giphy.com/gifs/MCZ39lz83o5lC/fullscreen
>
> Regards,
> Jose Luis
>
> On Fri, Jul 20, 2018 at 1:00 PM, Emilien Macchi 
> wrote:
>
>>
>>
>> On Fri, Jul 20, 2018 at 4:09 AM Carlos Camacho Gonzalez <
>> ccama...@redhat.com> wrote:
>>
>>> Hi!!!
>>>
>>> I'll like to propose Jose Luis Franco [1][2] for core reviewer in all
>>> the TripleO upgrades bits. He shows a constant and active involvement in
>>> improving and fixing our updates/upgrades workflows, he helps also trying
>>> to develop/improve/fix our upstream support for testing the
>>> updates/upgrades.
>>>
>>> Please vote -1/+1, and consider this my +1 vote :)
>>>
>>
>> Nice work indeed, +1. Keep doing a good job and thanks for all your help!
>> --
>> 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] Proposing Jose Luis Franco for TripleO core reviewer on Upgrade bits

[Carlos Camacho Gonzalez]

Hi!!!

I'll like to propose Jose Luis Franco [1][2] for core reviewer in all the
TripleO upgrades bits. He shows a constant and active involvement in
improving and fixing our updates/upgrades workflows, he helps also trying
to develop/improve/fix our upstream support for testing the
updates/upgrades.

Please vote -1/+1, and consider this my +1 vote :)

[1]: https://review.openstack.org/#/q/owner:jfrancoa%2540redhat.com
[2]: http://stackalytics.com/?release=all=commits_id=jfrancoa

Cheers,
Carlos.
__
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] [nova] Cleaning databases before running a major upgrade or for maintenance purposes.

[Carlos Camacho Gonzalez]

Hi!

I'll like to raise a question related to "How to clean Nova databases
before running upgrades"
We want to check that Nova databases (nova, nova_api, nova_cell0,
nova_placement) are in good shape before running upgrade, we know that
there is some effort to "purge the deleted instances" but no patches yet
for that.

In general, how can I know we have cleaned all Nova DBs? This can be i.e.
for maintenance purposes or for checking it before the major upgrade.

Currently the command we run is:
   nova-manage db archive_deleted_rows --max_rows 100 --until-complete
Still, the archived rows are stored in shadow tables so we still have a big
DB, and there is some specs[1] to remove them but nothing landed/usable.

[1]: https://blueprints.launchpad.net/nova/+spec/purge-deleted-instances-cmd

Thanks,
Carlos
__
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] Nominate chem and matbu for tripleo-core !

[Carlos Camacho Gonzalez]

Yeah!!! Welcome both!

On Thu, Nov 16, 2017 at 11:32 AM, Marios Andreou 
wrote:

> Thanks to everyone who voted and with only positive feedback (successfully
> spread across two threads ** ) it looks like we can now welcome Sofer and
> Mathieu to the tripleo core team.
>
> I'll ping alex when he's online later to check that chem and matbu are
> added to the right launchpad and gerrit groups.
>
> thanks,
>
> marios
>
> **
> http://lists.openstack.org/pipermail/openstack-dev/2017-
> November/124385.html
> http://lists.openstack.org/pipermail/openstack-dev/2017-
> November/124386.html
>
>
> On Thu, Nov 9, 2017 at 10:48 AM, Marios Andreou 
> wrote:
>
>> Hello fellow owls,
>> (appologies for duplicate, forgot to add the tripleo in subject so
>> worried it would be missed)
>>
>> I would like to nominate (and imo these are both long overdue already):
>>
>> Sofer Athlan Guyot (chem)  and
>>
>> Mathieu Bultel (matbu)
>>
>> to tripleo-core. They have both made many many core contributions to the
>> upgrades & updates over the last 3 cycles touching many of the tripleo
>> repos (tripleo-heat-templates, tripleo-common, python-tripleoclient,
>> tripleo-ci, tripleo-docs and others tripleo-quickstart/extras too unless am
>> mistaken).
>>
>> IMO their efforts and contributions are invaluable for the upgrades squad
>> (and beyond - see openstack overcloud config download for example) and we
>> will be very lucky to have them as fully voting cores.
>>
>> Please vote with +1 or -1 for either or both chem and matbu - I'll keep
>> it open for a week as customary,
>>
>> thank you,
>>
>> marios
>>
>
>
> __
> 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

Re: [openstack-dev] [tripleo] Proposing Bogdan Dobrelya core on TripleO / Containers

[Carlos Camacho Gonzalez]

Congrats!

On Mon, Jul 31, 2017 at 6:29 PM, Bogdan Dobrelya  wrote:
> On 31.07.2017 15:51, Emilien Macchi wrote:
>> On Fri, Jul 21, 2017 at 7:55 AM, Emilien Macchi  wrote:
>>> Hi,
>>>
>>> Bogdan (bogdando on IRC) has been very active in Containerization of
>>> TripleO and his quality of review has increased over time.
>>> I would like to give him core permissions on container work in TripleO.
>>> Any feedback is welcome as usual, we'll vote as a team.
>>
>> Votes were positive, it's done now.
>> Bogdan has now +2 and we expect him to use it on patches related to
>> container work.
>>
>> Thanks,
>>
>
> Thank you for your votes!
>
> --
> Best regards,
> Bogdan Dobrelya,
> Irc #bogdando
>
> __
> 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

Re: [openstack-dev] [tripleo] weekly meetings on #tripleo

[Carlos Camacho Gonzalez]

+1

We can try this and see how it goes.

On Thu, Jul 6, 2017 at 10:53 PM, Jason E. Rist  wrote:
> On 07/05/2017 11:40 AM, Ben Nemec wrote:
>> I don't have a particularly strong opinion one way or another (probably
>> because I tend to skip most of the meetings lately anyway...), but some
>> thoughts inline.
>>
>> On 07/05/2017 11:56 AM, Emilien Macchi wrote:
>> > After reading
>> > http://lists.openstack.org/pipermail/openstack-dev/2017-June/118899.html
>> > - we might want to collect TripleO's community feedback on doing
>> > weekly meetings on #tripleo instead of #openstack-meeting-alt.
>> >
>> > I see some direct benefits:
>> > - if you come up late in meetings, you could easily read backlog in
>> > #tripleo
>>
>> Most people idle in the meeting channels anyway, so +0 on this one.
>>
>> > - newcomers not aware about the meeting channel wouldn't have to
>> > search for it
>>
>> We generally announce meetings in #tripleo before starting, don't we?
>>
>> > - meeting would maybe get more activity and we would expose the
>> > information more broadly
>>
>> I guess this would preclude non-meeting related activity in #tripleo,
>> which in my experience is a thing that happens pretty frequently during
>> the meeting.  Whether that's a good thing or not is a matter of opinion.
>> :-)
>>
>> >
>> > Any feedback on this proposal is welcome before we make any change (or
>> > not).
>> >
>> > 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
> I echo Ben on all of these sentiments, but otherwise I'm impartial.
>
> -J
>
> __
> 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

Re: [openstack-dev] [TripleO] Undercloud backup and restore

[Carlos Camacho Gonzalez]

Hi Shinobu,

It's really helpful to get feedback from customers, please, can you give me
details about the failures you are having?. If so, sending me directly some
logs would be great.

Thanks,
Carlos.

On Mon, May 29, 2017 at 9:07 AM, Shinobu Kinjo <ski...@redhat.com> wrote:
>
> Here is feedback from the customer.
>
> Following the guide [1], undercloud restoration was not succeeded.
>
> Swift objects could haven't been downloaded after restoration even
> though they followed all procedures during backing up / restoring
> their system described in [1].
>
> Since that, I'm not 100% sure if `tar -czf` is good enough to take a
> backup of the system or not.
>
> It would be great help to do dry-run against backed up data so that we
> can make sure that backed up data is completely fine.
>
> [1]
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_openstack_platform/7/html/back_up_and_restore_red_hat_enterprise_linux_openstack_platform/back_up_and_restore_the_undercloud
>
>
> On Wed, May 24, 2017 at 4:26 PM, Carlos Camacho Gonzalez
> <ccama...@redhat.com> wrote:
> > Hey folks,
> >
> > Based on what we discussed yesterday in the TripleO weekly team meeting,
> > I'll like to propose a blueprint to create 2 features, basically to
backup
> > and restore the Undercloud.
> >
> > I'll like to follow in the first iteration the available docs for this
> > purpose [1][2].
> >
> > With the addition of backing up the config files on /etc/ specifically
to be
> > able to recover from a failed Undercloud upgrade, i.e. recover the repos
> > info removed in [3].
> >
> > I'll like to target this for P as I think I have enough time for
> > coding/testing these features.
> >
> > I already have created a blueprint to track this effort
> > https://blueprints.launchpad.net/tripleo/+spec/undercloud-backup-restore
> >
> > What do you think about it?
> >
> > Thanks,
> > Carlos.
> >
> > [1]:
> >
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_openstack_platform/7/html/back_up_and_restore_red_hat_enterprise_linux_openstack_platform/restore
> >
> > [2]:
> >
https://docs.openstack.org/developer/tripleo-docs/post_deployment/backup_restore_undercloud.html
> >
> > [3]:
> >
https://docs.openstack.org/developer/tripleo-docs/installation/updating.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 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

Re: [openstack-dev] [TripleO] Undercloud backup and restore

[Carlos Camacho Gonzalez]

On Wed, May 24, 2017 at 3:17 PM, Jiří Stránský <ji...@redhat.com> wrote:

> On 24.5.2017 15:02, Marios Andreou wrote:
>
>> On Wed, May 24, 2017 at 10:26 AM, Carlos Camacho Gonzalez <
>> ccama...@redhat.com> wrote:
>>
>> Hey folks,
>>>
>>> Based on what we discussed yesterday in the TripleO weekly team meeting,
>>> I'll like to propose a blueprint to create 2 features, basically to
>>> backup
>>> and restore the Undercloud.
>>>
>>> I'll like to follow in the first iteration the available docs for this
>>> purpose [1][2].
>>>
>>> With the addition of backing up the config files on /etc/ specifically to
>>> be able to recover from a failed Undercloud upgrade, i.e. recover the
>>> repos
>>> info removed in [3].
>>>
>>> I'll like to target this for P as I think I have enough time for
>>> coding/testing these features.
>>>
>>> I already have created a blueprint to track this effort
>>> https://blueprints.launchpad.net/tripleo/+spec/undercloud-backup-restore
>>>
>>> What do you think about it?
>>>
>>>
>> +1 from me as you know but adding my support on the list too. I think it
>> is
>> a great idea - there are cases especially around changing network config
>> during an upgrade for example where the best remedy is to restore the
>> undercloud for the network definitions (both neutron config and heat db).
>>
>
> +1 i think there's not really an easy way out of these issues other than a
> restore. We already recommend doing a backup before upgrading [1], so
> having something that can further help operators in this regard would be
> good.
>
>
Hey Jiri, Marios!!!

Sorry for the delayed reply here.

Yeahp, that's what I'll like to achieve, more than recover the UC, this is
about to restore it to a point we know it was working correctly.

Now, I'm following Ben's advise for this new iteration, taking a part the
big method which is currently meking the backup into small ones for
finishing the unit thests.

Cheers,
Carlos.

Jirka
>
> [1] http://tripleo.org/post_deployment/upgrade.html
>
>
>
>> thanks,
>>
>>
>>
>>> Thanks,
>>> Carlos.
>>>
>>> [1]: https://access.redhat.com/documentation/en-us/red_hat_
>>> enterprise_linux_openstack_platform/7/html/back_up_and_
>>> restore_red_hat_enterprise_linux_openstack_platform/restore
>>>
>>> [2]: https://docs.openstack.org/developer/tripleo-docs/post_
>>> deployment/backup_restore_undercloud.html
>>>
>>> [3]: https://docs.openstack.org/developer/tripleo-docs/
>>> installation/updating.html
>>>
>>>
>>> 
>>> __
>>> 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
>>>
>>>
>>>
>>
>>
>> 
>> __
>> 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

Re: [openstack-dev] [TripleO] Undercloud backup and restore

[Carlos Camacho Gonzalez]

Hey Yolanda!

Thanks for your feedback, that's partially the idea of these 2 features,
right now they are targeting the Undercloud (backup and restore), but yes,
we should point something similar to the OC.

Cheers,
Carlos.

On Wed, May 24, 2017 at 10:10 AM, Yolanda Robla Mota <yrobl...@redhat.com>
wrote:

> Hi Carlos
> A common request that i hear, is that customers need a way to rollback or
> downgrade a system after an upgrade. So that will be useful of course. What
> about the overcloud, are you considering that possibility? If they find
> that an upgrade on a controller node breaks something for example.
>
> On Wed, May 24, 2017 at 9:26 AM, Carlos Camacho Gonzalez <
> ccama...@redhat.com> wrote:
>
>> Hey folks,
>>
>> Based on what we discussed yesterday in the TripleO weekly team meeting,
>> I'll like to propose a blueprint to create 2 features, basically to backup
>> and restore the Undercloud.
>>
>> I'll like to follow in the first iteration the available docs for this
>> purpose [1][2].
>>
>> With the addition of backing up the config files on /etc/ specifically to
>> be able to recover from a failed Undercloud upgrade, i.e. recover the repos
>> info removed in [3].
>>
>> I'll like to target this for P as I think I have enough time for
>> coding/testing these features.
>>
>> I already have created a blueprint to track this effort
>> https://blueprints.launchpad.net/tripleo/+spec/undercloud-backup-restore
>>
>> What do you think about it?
>>
>> Thanks,
>> Carlos.
>>
>> [1]: https://access.redhat.com/documentation/en-us/red_hat_enterp
>> rise_linux_openstack_platform/7/html/back_up_and_restore_
>> red_hat_enterprise_linux_openstack_platform/restore
>>
>> [2]: https://docs.openstack.org/developer/tripleo-docs/post_deplo
>> yment/backup_restore_undercloud.html
>>
>> [3]: https://docs.openstack.org/developer/tripleo-docs/installati
>> on/updating.html
>>
>>
>> 
>> __
>> 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
>>
>>
>
>
> --
>
> Yolanda Robla Mota
>
> Principal Software Engineer, RHCE
>
> Red Hat
>
> <https://www.redhat.com>
>
> C/Avellana 213
>
> Urb Portugal
>
> yrobl...@redhat.comM: +34605641639
> <http://redhatemailsignature-marketing.itos.redhat.com/>
> <https://red.ht/sig>
>
> __
> 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] Undercloud backup and restore

[Carlos Camacho Gonzalez]

 Hey folks,

Based on what we discussed yesterday in the TripleO weekly team meeting,
I'll like to propose a blueprint to create 2 features, basically to backup
and restore the Undercloud.

I'll like to follow in the first iteration the available docs for this
purpose [1][2].

With the addition of backing up the config files on /etc/ specifically to
be able to recover from a failed Undercloud upgrade, i.e. recover the repos
info removed in [3].

I'll like to target this for P as I think I have enough time for
coding/testing these features.

I already have created a blueprint to track this effort
https://blueprints.launchpad.net/tripleo/+spec/undercloud-backup-restore

What do you think about it?

Thanks,
Carlos.

[1]:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_openstack_platform/7/html/back_up_and_restore_red_hat_enterprise_linux_openstack_platform/restore

[2]:
https://docs.openstack.org/developer/tripleo-docs/post_deployment/backup_restore_undercloud.html

[3]:
https://docs.openstack.org/developer/tripleo-docs/installation/updating.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

Re: [openstack-dev] [tripleo] Final project logo files

[Carlos Camacho Gonzalez]

Thank you all!

On Mon, Apr 24, 2017 at 2:04 PM, Emilien Macchi  wrote:

> On Fri, Apr 21, 2017 at 6:06 PM, Heidi Joy Tretheway
>  wrote:
> > Hello TripleO team!
> >
> > Thanks to your input on the last round (which corrected the owls eyes to
> have a yellow circle, and make the mascot not cross-eyed), we have a final
> version for your team.
> >
> > Here’s a quick look at the logo:
> > https://www.dropbox.com/s/ejfa7holov7u1g5/OpenStack_
> Project_Tripleo_vertical.jpg?dl=0
> >
> > And here’s a folder with all 10 variations:
> > https://www.dropbox.com/sh/zvmw0j1bm14dk6w/
> AAD2je5lCaB5ZUlLjCjhPlYYa?dl=0
> >
> > We’ll post these to a public repo and on openstack.org/project-mascots
> soon. Thanks again for your input!
>
> Thank you very much for this work, unless we have more feedback this
> week, you can go ahead and push it online!
>
> >
> > 
> __
> > 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
>
>
>
> --
> 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

Re: [openstack-dev] [tripleo] Consistent way of integrating services with different backends

[Carlos Camacho Gonzalez]

 I think the answer here should be if we want to define environment files
as a whole
“With all the information required to deploy something functional” or
composing them like
a LEGO (which might not work separately).

I don't have a strong opinion about it, but I'm inclined to use them as
functional blocks, i.e. if you want to deploy the pacemaker profiles you
just have to include puppet-pacemaker.yaml and that's all.

What IMHO would do is:

* -e neutron-l2gw-basic.yaml → Will install the API and the agent.
* -e neutron-l2gw-odl.yaml → Will install the API and ODL.

The API is a common factor here so we can add it into all envs using it.
Also, I think will be easier from a user POV as they won't have to master
how to compose their environment files to have it running.

What do you think about it?

Cheers,
Carlos.




On Thu, Apr 6, 2017 at 1:07 PM, Ricardo Noriega De Soto 
wrote:
>
> Hi owls!
>
> This is something that I've been discussing in the IRC channel but still
I think we should define a consistent way of integrating services which
support different backends. In this case, I'm refering to BGPVPN and L2GW
Neutron services, but it could be applied to any other type of service.
>
> These two Neutron service plugins support different backends such an
agent and a SDN controller (OpenDaylight). Usually the reference
architecture will use the agents.
>
> My main question is about how to model this into THT properly.
>
> It is clear that we have to create two different composable services: one
for the API and one for the agent. However, how many environment files we
should have and which should be the content?
>
> i.e. L2GW project
>
> Option 1:
>
> neutron-l2gw-api.yaml enabling the corresponding API composable service.
> neutron-l2gw-agent.yaml enabling the corresponding agent composable
service.
>
> openstack overcloud deploy -e neutron-l2gw-api.yaml -e
 neutron-l2gw-agent.yaml (with agent)
> openstack overcloud deploy -e neutron-l2gw-api.yaml -e
 neutron-opendaylight-l3.yaml (with ODL)
>
> Option 2:
>
> neutron-l2gw.yaml enabling the API and the agent as a reference
architecture scenario.
> neutron-l2gw-odl.yaml enabling the API with OpenDaylight as
service_provider
>
> openstack overcloud deploy -e neutron-l2gw.yaml (with agent)
> openstack overcloud deploy -e neutron-l2gw-odl.yaml -e
 neutron-opendaylight-l3.yaml (with ODL)
>
>
> I'm not really pushing for any option, but I'm just concern from the user
experience point of view. As a user, which way is more friendly? or
understandable? Where in the documentation is this reflected?
>
>
> Some pointers of the L2GW service and agent services:
>
> https://review.openstack.org/#/c/447429/
> https://review.openstack.org/#/c/451175/
>
> Cheers
>
> --
> Ricardo Noriega
>
> Senior Software Engineer - NFV Partner Engineer | Office of Technology  |
Red Hat
> irc: rnoriega @freenode
>
>
> __
> 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

Re: [openstack-dev] [openstack-docs] [tripleo] Creating official Deployment guide for TripleO

[Carlos Camacho Gonzalez]

Hey,

I'll like to collaborate, please, just let me know what can I do to help
with this task.

Might be a good idea to have in the blueprint a list of tasks?

Also, I think this can be called Deployment/Upgrade guide for TripleO.

Cheers,
Carlos.



On Mon, Mar 20, 2017 at 3:26 PM, Sanjay Upadhyay 
wrote:

>
>
> On Mon, Mar 20, 2017 at 5:31 PM, Emilien Macchi 
> wrote:
>
>> I proposed a blueprint to track the work done:
>>
>> https://blueprints.launchpad.net/tripleo/+spec/tripleo-deploy-guide
>> Target: pike-3
>>
>> Volunteers to work on it with me, please let me know.
>>
>
> Please add me (irc handle - saneax), I am interested on this.
>
> regards
> /sanjay
>
>
>> Thanks,
>>
>> On Tue, Mar 14, 2017 at 7:00 AM, Alexandra Settle 
>> wrote:
>> > Hey Emilien,
>> >
>> > You pretty much covered it all! Docs team is happy to provide guidance,
>> but in reality, it should be a fairly straight forward process.
>> >
>> > The Kolla team just completed their deploy-guide patches and were able
>> to help refine the process a bit further. Hopefully this should help the
>> TripleO team :)
>> >
>> > Reach out if you have any questions at all :)
>> >
>> > Thanks,
>> >
>> > Alex
>> >
>> > On 3/13/17, 10:32 PM, "Emilien Macchi"  wrote:
>> >
>> > Team,
>> >
>> > [adding Alexandra, OpenStack Docs PTL]
>> >
>> > It seems like there is a common interest in pushing deployment
>> guides
>> > for different OpenStack Deployment projects: OSA, Kolla.
>> > The landing page is here:
>> > https://docs.openstack.org/project-deploy-guide/newton/
>> >
>> > And one example:
>> > https://docs.openstack.org/project-deploy-guide/openstack-
>> ansible/newton/
>> >
>> > I think this is pretty awesome and it would bring more visibility
>> for
>> > TripleO project, and help our community to find TripleO
>> documentation
>> > from a consistent place.
>> >
>> > The good news, is that openstack-docs team built a pretty solid
>> > workflow to make that happen:
>> > https://docs.openstack.org/contributor-guide/project-deploy
>> -guide.html
>> > And we don't need to create new repos or do any crazy changes. It
>> > would probably be some refactoring and sphinx things.
>> >
>> > Alexandra, please add any words if I missed something obvious.
>> >
>> > Feedback from the team would be welcome here before we engage any
>> work,
>> >
>> > Thanks!
>> > --
>> > Emilien Macchi
>> >
>> >
>>
>>
>>
>> --
>> 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

Re: [openstack-dev] [tripleo] propose Alex Schultz core on tripleo-heat-templates

[Carlos Camacho Gonzalez]

+1

On Mon, Mar 13, 2017 at 4:12 PM, Jiří Stránský  wrote:

> On 13.3.2017 15:30, Emilien Macchi wrote:
>
>> Hi,
>>
>> Alex is already core on instack-undercloud and puppet-tripleo.
>> His involvement and knowledge in TripleO Heat Templates has been very
>> appreciated over the last months and I think we can give him +2 on
>> this project.
>>
>> As usual, feel free to vote -1/+1 on this proposal.
>>
>
> +1
>
>
>> 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 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] Fwd: TripleO mascot - how can I help your team?

[Carlos Camacho Gonzalez]

Hey!

Yeahp I think most owls have yellow/orange eyes, this can be a good thing
to try.

Cheers,
Carlos

On Fri, Mar 10, 2017 at 8:53 PM, Dan Sneddon  wrote:

> On 03/10/2017 08:26 AM, Heidi Joy Tretheway wrote:
> > Hi TripleO team,
> >
> > Here’s an update on your project logo. Our illustrator tried to be as
> > true as possible to your original, while ensuring it matched the line
> > weight, color palette and style of the rest. We also worked to make sure
> > that three Os in the logo are preserved. Thanks for your patience as we
> > worked on this! Feel free to direct feedback to me.
> >
> >
> > 
> __
> > 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
> >
>
> This is a huge improvement! Some of the previous drafts looked more like
> a generic bird and less like an owl.
>
> I have a suggestion on how this might be more owl-like. If you look at
> real owl faces [1], you will see that their eyes are typically yellow,
> and they often have a white circle around the eyes (black pupil, yellow
> eye, black/white circle of feathers). I think that we could add a yellow
> ring around the black pupil, and possibly accentuate the ears (since
> owls often have white tufts on their ears).
>
> I whipped up a quick example of what I'm talking about, it's attached
> (hopefully it will survive the mailing list).
>
> [1] - https://www.google.com/search?q=owl+face=isch=u=univ
>
> --
> Dan Sneddon |  Senior Principal OpenStack Engineer
> dsned...@redhat.com |  redhat.com/openstack
> dsneddon:irc|  @dxs:twitter
>
> __
> 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

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

[Carlos Camacho Gonzalez]

Hey

This version looks awesome, it really feels like what we currently have,
but upgraded xD

I don't see how we can keep the head feathers, so forth,

+1

Thanks Heidi for your effort!

Cheers,
Carlos.

On Fri, Mar 10, 2017 at 5:36 PM, Jason Rist  wrote:

> On 03/10/2017 09:26 AM, Heidi Joy Tretheway wrote:
> > Hi TripleO team,
> >
> > Here’s an update on your project logo. Our illustrator tried to be as
> true as
> > possible to your original, while ensuring it matched the line weight,
> color
> > palette and style of the rest. We also worked to make sure that three Os
> in the
> > logo are preserved. Thanks for your patience as we worked on this! Feel
> free to
> > direct feedback to me.
> >
> >
> >
> > 
> __
> > 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
> >
> This is a good interpretation of the original, possibly even making it
> better.  I like it.  Thanks Heidi!
>
> -J
>
> --
> Jason E. Rist
> Senior Software Engineer
> OpenStack User Interfaces
> Red Hat, Inc.
> Freenode: jrist
> github/twitter: knowncitizen
>
> __
> 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

Re: [openstack-dev] [tripleo] Atlanta PTG

[Carlos Camacho Gonzalez]

Thanks Emilien!

I think will be enough just by sharing a mic and the Etherpad notes.

Cheers,
Carlos.

On Wed, Feb 22, 2017 at 5:16 AM, Emilien Macchi  wrote:

> On Tue, Feb 21, 2017 at 11:46 AM, Sai Sindhur Malleni
>  wrote:
> > Is there a plan to have a google hangouts session or similar to attend
> > remotely?
>
> to be honest, mixing face 2 face & remote meetings is very challenging.
> But because people want it, we'll give a try on Friday morning during
> the CI sessions.
>
> If anyone at PTG volunteers to do the same for the other sessions on
> Wednesday or Thursday, feel free to do so.
>
> > On Mon, Jan 23, 2017 at 8:45 AM, John Trowbridge 
> wrote:
> >>
> >>
> >>
> >> On 01/21/2017 05:37 AM, Michele Baldessari wrote:
> >> > Hi Emilien,
> >> >
> >> > while not a design session per se, I would love to propose a short
> slot
> >> > for TripleO CI Q, if we have some time left. In short, I'd like to
> be
> >> > more useful around CI failures, but I lack the understanding of a few
> >> > aspects of our current CI (promotion, when do images get built, etc.),
> >> > that would benefit quite a bit from a short session where we have a
> few
> >> > CI folks in the room that could answer questions or give some tips.
> >> > I know of quite few other people that are in the same boat and maybe
> >> > this will help a bit our current issue where only a few folks always
> >> > chase CI issues.
> >> >
> >> > If there is consensus (and some CI folks willing to attend ;) and time
> >> > for this, I'll be happy to organize this and prepare a bunch of
> >> > questions ideas beforehand.
> >> >
> >>
> >> Great idea. We have a room for three days, so it is not like summit
> >> where there is really limited time.
> >>
> >> > Thoughts?
> >> > Michele
> >> >
> >> > On Wed, Jan 04, 2017 at 07:26:52AM -0500, Emilien Macchi wrote:
> >> >> I would like to bring this topic up on your inbox, so we can continue
> >> >> to make progress on the agenda. Feel free to follow existing examples
> >> >> in the etherpad and propose a design dession.
> >> >>
> >> >> Thanks,
> >> >>
> >> >> On Wed, Dec 21, 2016 at 9:06 AM, Emilien Macchi 
> >> >> wrote:
> >> >>> General infos about PTG: https://www.openstack.org/ptg/
> >> >>>
> >> >>> Some useful informations about PTG/TripleO:
> >> >>>
> >> >>> * When? We have a room between Wednesday and Friday included.
> >> >>> Important sessions will happen on Wednesday and Thursday. We'll
> >> >>> probably have sessions on Friday, but it might be more hands-on and
> >> >>> hackfest, where people can enjoy the day to work together.
> >> >>>
> >> >>> * Let's start to brainstorm our topics:
> >> >>> https://etherpad.openstack.org/p/tripleo-ptg-pike
> >> >>>   Feel free to add any topic, as soon as you can. We need to know
> asap
> >> >>> which sessions will be share with other projects (eg:
> tripleo/mistral,
> >> >>> tripleo/ironic, tripleo/heat, etc).
> >> >>>
> >> >>>
> >> >>> Please let us know any question or feedback,
> >> >>> Looking forward to seeing you there!
> >> >>> --
> >> >>> Emilien Macchi
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> 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
> >
> >
> >
> >
> > --
> > Sai Sindhur Malleni
> >
> > Red Hat Inc.
> > 100 East Davie Street
> > Raleigh, NC, USA
> > Work: (919) 754-4557 | Cell: (919) 985-1055
> >
> > 
> __
> > 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
> >
>
>
>
> --
> 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

Re: [openstack-dev] [tripleo] Atlanta PTG

[Carlos Camacho Gonzalez]

+1 Sai

On Tue, Feb 21, 2017 at 5:46 PM, Sai Sindhur Malleni 
wrote:

> Is there a plan to have a google hangouts session or similar to attend
> remotely?
>
> On Mon, Jan 23, 2017 at 8:45 AM, John Trowbridge  wrote:
>
>>
>>
>> On 01/21/2017 05:37 AM, Michele Baldessari wrote:
>> > Hi Emilien,
>> >
>> > while not a design session per se, I would love to propose a short slot
>> > for TripleO CI Q, if we have some time left. In short, I'd like to be
>> > more useful around CI failures, but I lack the understanding of a few
>> > aspects of our current CI (promotion, when do images get built, etc.),
>> > that would benefit quite a bit from a short session where we have a few
>> > CI folks in the room that could answer questions or give some tips.
>> > I know of quite few other people that are in the same boat and maybe
>> > this will help a bit our current issue where only a few folks always
>> > chase CI issues.
>> >
>> > If there is consensus (and some CI folks willing to attend ;) and time
>> > for this, I'll be happy to organize this and prepare a bunch of
>> > questions ideas beforehand.
>> >
>>
>> Great idea. We have a room for three days, so it is not like summit
>> where there is really limited time.
>>
>> > Thoughts?
>> > Michele
>> >
>> > On Wed, Jan 04, 2017 at 07:26:52AM -0500, Emilien Macchi wrote:
>> >> I would like to bring this topic up on your inbox, so we can continue
>> >> to make progress on the agenda. Feel free to follow existing examples
>> >> in the etherpad and propose a design dession.
>> >>
>> >> Thanks,
>> >>
>> >> On Wed, Dec 21, 2016 at 9:06 AM, Emilien Macchi 
>> wrote:
>> >>> General infos about PTG: https://www.openstack.org/ptg/
>> >>>
>> >>> Some useful informations about PTG/TripleO:
>> >>>
>> >>> * When? We have a room between Wednesday and Friday included.
>> >>> Important sessions will happen on Wednesday and Thursday. We'll
>> >>> probably have sessions on Friday, but it might be more hands-on and
>> >>> hackfest, where people can enjoy the day to work together.
>> >>>
>> >>> * Let's start to brainstorm our topics:
>> >>> https://etherpad.openstack.org/p/tripleo-ptg-pike
>> >>>   Feel free to add any topic, as soon as you can. We need to know asap
>> >>> which sessions will be share with other projects (eg: tripleo/mistral,
>> >>> tripleo/ironic, tripleo/heat, etc).
>> >>>
>> >>>
>> >>> Please let us know any question or feedback,
>> >>> Looking forward to seeing you there!
>> >>> --
>> >>> Emilien Macchi
>> >>
>> >>
>> >>
>> >> --
>> >> 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
>> >
>>
>> 
>> __
>> 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
>>
>
>
>
> --
> Sai Sindhur Malleni
>
> Red Hat Inc.
> 100 East Davie Street
> Raleigh, NC, USA
> Work: (919) 754-4557 | Cell: (919) 985-1055
>
> __
> 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

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

[Carlos Camacho Gonzalez]

Hi,

Yeah, I tried drafting something based on our current logo and following my
perception about the new foundation styles,
again here are the files (WIP version, is just a PoC)

https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_
tripleo_logo_h.pdf
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_
tripleo_logo_h.png
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_
tripleo_logo_h.svg
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_
tripleo_logo_v.pdf
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_
tripleo_logo_v.png
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_
tripleo_logo_v.svg

Again, don't hesitate on pinging me if you think I can help you solve this
:)

Cheers,
Carlos.



On Thu, Feb 16, 2017 at 2:49 PM, Giulio Fidente  wrote:

> On 02/14/2017 03:38 AM, Emilien Macchi wrote:
> > Team, I've got this email from Heidi.
> >
> > I see 3 options :
> >
> > 1. Keep existing logo: http://tripleo.org/_static/tripleo_owl.svg .
> >
> > 2. Re-design a new logo that "meets" OpenStack "requirements".
> >
> > 3. Pick-up the one proposed (see below).
>
> while not the most skilled around, I can tell I have seen tripleo
> changing a lot over time, the project, not the logo, so I wouldn't ever
> think of tripleo people as hostile to changes
>
> I'd vote for option (1) as well but if someone could iterate over the
> *existing* logo to make it meet the requirements, instead of proposing a
> new one completely different, that would be received better I think; is
> this still an option? I think Carlos (in CC) suggested something like
> that too?
>
> also, to propose a change I think it would be useful to share the (new?)
> requirements as well, so that people can eventually understand those
> better too
> --
> Giulio Fidente
> GPG KEY: 08D733BA
>
__
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] Fwd: TripleO mascot - how can I help your team?

[Carlos Camacho Gonzalez]

Hello Heidi,

I think most of us already agreed on the fact that our current logo was
created by developers and we like it.
The idea should be to iterate over our current logo to make it fit the
foundation guidelines.

I don't think is hard to do it, I can give you some examples (***The owl
colors were randomly chosen).

https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_h.pdf
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_h.png
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_h.svg
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_v.pdf
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_v.png
https://cdn.rawgit.com/ccamacho/tripleo-graphics/5ed624b8/logos/openstack_tripleo_logo_v.svg

Please just let me know if you need any further information/feedback/help.

Cheers,
Carlos.



On Tue, Feb 14, 2017 at 3:44 PM, Emilien Macchi <emil...@redhat.com> wrote:
>
> Heidi,
>
> TripleO team discussed about the logo this morning during our weekly
meeting.
> We understood that we had to change our existing logo because it
> doesn't meet OpenStack themes requirements, and that's fine.
>
> Though we would like you to re-iterate on a new logo that would be a
> variation on the current logo that moves closer to the foundation.
>
> Our existing logo is: http://tripleo.org/_static/tripleo_owl.svg
>
> Please let us know if you can prepare a new logo close to this one,
> and I think we would find a middle ground here.
>
> Thanks a lot,
>
> On Tue, Feb 14, 2017 at 7:30 AM, Carlos Camacho Gonzalez
> <ccama...@redhat.com> wrote:
> > I'll vote also for option 1 if we can keep it.
> >
> > One thing, you can see how designers have iterated over ironic's logo
> >
http://lists.openstack.org/pipermail/openstack-dev/attachments/20170201/a016f685/attachment.png
> > to fit the OpenStack illustration style.
> >
> > Is it possible for designers to iterate over
> > http://tripleo.org/_static/tripleo_owl.svg to make it fit the
guidelines?
> >
> > Cheers,
> > Carlos.
> >
> > On Tue, Feb 14, 2017 at 12:34 PM, Lucas Alvares Gomes
> > <lucasago...@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> Just a FYI, we have had similar discussions about the proposed logo for
> >> Ironic, there's still many unanswered questions but, if you guys are
> >> interested this is the link to the ML thread:
> >>
http://lists.openstack.org/pipermail/openstack-dev/2017-February/111401.html
> >>
> >> Cheers,
> >> Lucas
> >>
> >> On Tue, Feb 14, 2017 at 2:38 AM, Emilien Macchi <emil...@redhat.com>
> >> wrote:
> >>>
> >>> Team, I've got this email from Heidi.
> >>>
> >>> I see 3 options :
> >>>
> >>> 1. Keep existing logo: http://tripleo.org/_static/tripleo_owl.svg .
> >>>
> >>> 2. Re-design a new logo that "meets" OpenStack "requirements".
> >>>
> >>> 3. Pick-up the one proposed (see below).
> >>>
> >>>
> >>> Personally, I would vote for keeping our existing logo (1.) unless
> >>> someone has time to create another one or if the team likes the
proposed
> >>> one.
> >>>
> >>> The reason why I want to keep our logo is because our current logo was
> >>> created by TripleO devs, we like it and we already have tee-shirts
and other
> >>> goodies with it. I don't see any good reason to change it.
> >>>
> >>> Discussion is open and we'll vote as a team.
> >>>
> >>> Thanks,
> >>>
> >>> Emilien.
> >>>
> >>> -- Forwarded message --
> >>> From: Heidi Joy Tretheway <heidi...@openstack.org>
> >>> Date: Mon, Feb 13, 2017 at 8:27 PM
> >>> Subject: TripleO mascot - how can I help your team?
> >>> To: Emilien Macchi <emil...@redhat.com>
> >>>
> >>>
> >>> Hi Emilien,
> >>>
> >>> I’m following up on the much-debated TripleO logo. I’d like to help
your
> >>> team reach a solution that makes them happy but still fits within the
family
> >>> of logos we’re using at the PTG and going forward. Here’s what our
> >>> illustrators came up with, which hides an “O” shape in the owl (face
and
> >>> wing arcs).
> >>>
> >>>
https://www.dropbox.com/sh/qz45miiiam3caiy/AAAzPGYEZRMGH6Otid3bLfHFa?dl=0
>

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

[Carlos Camacho Gonzalez]

I'll vote also for option 1 if we can keep it.

One thing, you can see how designers have iterated over ironic's logo
http://lists.openstack.org/pipermail/openstack-dev/
attachments/20170201/a016f685/attachment.png to fit the OpenStack
illustration style.

Is it possible for designers to iterate over http://tripleo.org/_static/
tripleo_owl.svg to make it fit the guidelines?

Cheers,
Carlos.

On Tue, Feb 14, 2017 at 12:34 PM, Lucas Alvares Gomes 
wrote:
>
> Hi,
>
> Just a FYI, we have had similar discussions about the proposed logo for
Ironic, there's still many unanswered questions but, if you guys are
interested this is the link to the ML thread: http://lists.openstack.org/
pipermail/openstack-dev/2017-February/111401.html
>
> Cheers,
> Lucas
>
> On Tue, Feb 14, 2017 at 2:38 AM, Emilien Macchi 
wrote:
>>
>> Team, I've got this email from Heidi.
>>
>> I see 3 options :
>>
>> 1. Keep existing logo: http://tripleo.org/_static/tripleo_owl.svg .
>>
>> 2. Re-design a new logo that "meets" OpenStack "requirements".
>>
>> 3. Pick-up the one proposed (see below).
>>
>>
>> Personally, I would vote for keeping our existing logo (1.) unless
someone has time to create another one or if the team likes the proposed
one.
>>
>> The reason why I want to keep our logo is because our current logo was
created by TripleO devs, we like it and we already have tee-shirts and
other goodies with it. I don't see any good reason to change it.
>>
>> Discussion is open and we'll vote as a team.
>>
>> Thanks,
>>
>> Emilien.
>>
>> -- Forwarded message --
>> From: Heidi Joy Tretheway 
>> Date: Mon, Feb 13, 2017 at 8:27 PM
>> Subject: TripleO mascot - how can I help your team?
>> To: Emilien Macchi 
>>
>>
>> Hi Emilien,
>>
>> I’m following up on the much-debated TripleO logo. I’d like to help your
team reach a solution that makes them happy but still fits within the
family of logos we’re using at the PTG and going forward. Here’s what our
illustrators came up with, which hides an “O” shape in the owl (face and
wing arcs).
>>
>> https://www.dropbox.com/sh/qz45miiiam3caiy/AAAzPGYEZRMGH6Otid3bLfHFa?dl=0
>> At this point, I don’t have quorum from your team (I got a lot of
conflicting feedback, most of which was “don’t like” but not actionable for
the illustrators to make a revision). At the PTG, we’ll have mascot
stickers and signage for all teams except for Ironic and TripleO, since
we’re still waiting on your teams to make a final decision.
>>
>> May I recommend that your team choose one person (or a small group of no
more than three) to finalize this? I was able to work through all of
Swift’s issues with just a quick 15-minute chat with John Dickinson and I’d
like to believe we can solve this for TripleO as well.
>>
>> We know some of your team has expressed concern over retiring the
existing mascot. It’s not our intention to make anyone “get rid of” a
beloved icon. Your team can certainly print it on vintage items like shirts
and stickers. But for official channels like the website, we need a logo to
represent TripleO that’s cohesive with the rest of the set.
>>
>> Perhaps when you’re face to face with your team at the PTG, you can
discuss and hopefully render a final decision to either accept this as a
logo, or determine a few people willing to make any final changes with me?
>>
>> Thanks in advance for your help!
>>
>>
>> Heidi Joy Tretheway
>> Senior Marketing Manager, OpenStack Foundation
>> 503 816 9769 <(503)%20816-9769> | Skype: heidi.tretheway
>>
>>
>>
>>
>>
>>
>>
>> --
>> 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 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 Dmitry Tantsur and Alex Schultz as instack-undercloud cores

[Carlos Camacho Gonzalez]

+1!

On Wed, Feb 1, 2017 at 9:57 AM, Julie Pichon  wrote:

> On 31 January 2017 at 16:02, Ben Nemec  wrote:
> > In the spirit of all the core team changes, here are a couple more I'd
> like
> > to propose.
> >
> > Dmitry has been very helpful reviewing in instack-undercloud for a long
> time
> > so this is way overdue.  I'm also going to propose that he be able to +2
> > anything Ironic-related in TripleO since that is his primary area of
> > expertise.
> >
> > Alex has ramped up quickly on TripleO and has also been helping out with
> > instack-undercloud quite a bit.  He's already core for the puppet
> modules,
> > and a lot of the changes to instack-undercloud these days are primarily
> in
> > the puppet manifest so it's not a huge stretch to add him.
> >
> > As usual, TripleO cores please vote and/or provide comments.  Thanks.
>
> +1!
>
> __
> 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

Re: [openstack-dev] [tripleo] Update TripleO core members

[Carlos Camacho Gonzalez]

+1 Awesome!

On Wed, Jan 25, 2017 at 9:35 AM, Michele Baldessari 
wrote:

> On Mon, Jan 23, 2017 at 02:03:28PM -0500, Emilien Macchi wrote:
> > Greeting folks,
> >
> > I would like to propose some changes in our core members:
> >
> > - Remove Jay Dobies who has not been active in TripleO for a while
> > (thanks Jay for your hard work!).
> > - Add Flavio Percoco core on tripleo-common and tripleo-heat-templates
> > docker bits.
> > - Add Steve Backer on os-collect-config and also docker bits in
> > tripleo-common and tripleo-heat-templates.
> >
> > Indeed, both Flavio and Steve have been involved in deploying TripleO
> > in containers, their contributions are very valuable. I would like to
> > encourage them to keep doing more reviews in and out container bits.
>
> +1!!
> --
> Michele Baldessari
> C2A5 9DA3 9961 4FFB E01B  D0BC DDD4 DCCB 7515 5C6D
>
> __
> 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] Cheatsheets for FOSDEM and devconf

[Carlos Camacho Gonzalez]

Hi TripleOers!

We are working preparing some cheatsheets for people jumping into TripleO.

So there is an early WIP version for a few cheatsheets that we want to share:

-TripleO manual installation  (Just a copy/paste step-wise process to
install TripleO)
- Deployments debugging tips (Relevant commands to know what's
happening with the deployment)
- CI (URL's and resource to check our CI status)
- OOOQ (Also a step-wise recipe to install OOOQ, does not exist yet)

We already have some drafts available in
https://github.com/ccamacho/tripleo-cheatsheet

So, we will like to have some feedback from the community and make a
stable version for the cheatsheets in the next week.

Feedback for adding/removing content and general reviews about all of
them is welcomed.

Thanks!,
Carlos

__
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 Alex Schultz core on puppet-tripleo

[Carlos Camacho Gonzalez]

+1

On Thu, Dec 1, 2016 at 11:37 PM, Dan Trainor  wrote:
> +1
>
> On Dec 1, 2016 5:36 PM, "James Slagle"  wrote:
>>
>> On Thu, Dec 1, 2016 at 5:26 PM, Emilien Macchi  wrote:
>> > Team,
>> >
>> > Alex Schultz (mwhahaha on IRC) has been active on TripleO since a few
>> > months now.  While he's very active in different areas of TripleO, his
>> > reviews and contributions on puppet-tripleo have been very useful.
>> > Alex is a Puppet guy and also the current PTL of Puppet OpenStack. I
>> > think he perfectly understands how puppet-tripleo works. His
>> > involvement in the project and contributions on puppet-tripleo deserve
>> > that we allow him to +2 puppet-tripleo.
>> >
>> > Thanks Alex for your involvement and hard work in the project, this is
>> > very appreciated!
>> >
>> > As usual, I'll let the team to vote about this proposal.
>>
>> +1
>>
>>
>> --
>> -- James Slagle
>> --
>>
>> __
>> OpenStack Development Mailing List (not 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

Re: [openstack-dev] [tripleo] CI scenarios design - how to add more services

[Carlos Camacho Gonzalez]

I think would be cool to go with option, +1 to 1.A

IMHO,
- Easier to read.
- Easier to maintain.
- We don't make backports, instead we guarantee backwards compatibility.
- We'll re-use experience from Puppet OpenStack CI.

On Wed, Nov 23, 2016 at 10:13 PM, Giulio Fidente  wrote:
> hi Emilien,
>
> thanks for putting some thought into this. We have a similar problem to test
> RGW which was only added in Newton.
>
>
> On 11/23/2016 03:02 AM, Emilien Macchi wrote:
>>
>> == Context
>>
>> In Newton we added new multinode jobs called "scenarios".
>> The challenged we tried to solve was "how to test the maximum of
>> services without overloading the nodes that run tests".
>>
>> Each scenarios deploys a set of services, which allows us to
>> horizontally scale the number of scenarios to increase the service
>> testing coverage.
>> See the result here:
>> https://github.com/openstack-infra/tripleo-ci#service-testing-matrix
>>
>> To implement this model, we took example of Puppet OpenStack CI:
>> https://github.com/openstack/puppet-openstack-integration#description
>> We even tried to keep consistent the services/scenarios relations, so
>> it's consistent and easier to maintain.
>>
>> Everything was fine until we had to add new services during Ocata cycles.
>> Because tripleo-ci repository is not branched, adding Barbican service
>> in the TripleO environment for scenario002 would break Newton CI jobs.
>> During my vacations, the team created a new scenario, scenario004,
>> that deploys Barbican and that is only run for Ocata jobs.
>> I don't think we should proceed this way, and let me explain why.
>>
>> == Problem
>>
>> How to scale the number of services that we test without increasing
>> the number of scenarios and therefore the complexity of maintaining
>> them on long-term.
>>
>>
>> == Solutions
>>
>> The list is not exhaustive, feel free to add more.
>>
>> 1) Re-use experience from Puppet OpenStack CI and have environments
>> that are in a branched repository.
>> environments.
>> In Puppet OpenStack CI, the repository that deploys environments
>> (puppet-openstack-integration) is branched. So if puppet-barbican is
>> ready to be tested in Ocata, we'll patch
>> puppet-openstack-integration/master to start testing it and it won't
>> break stable jobs.
>> Like this, we were successfully able to maintain a fair number of
>> scenarios and keep our coverage increasing over each cycle.
>>
>> I see 2 sub-options here:
>>
>> a) Move CI environments and pingtest into
>> tripleo-heat-templates/environments/ci/(scenarios|pingtest). This repo
>> is branched and we could add a README to explain these files are used
>> in CI and we don't guarantee they would work outside TripleO CI tools.
>> b) Branch tripleo-ci repository. Personally I don't like this solution
>> because a lot of patches in this repo are not related to OpenStack
>> versions, which means we would need to backport most of the things
>> from master.
>
>
> I'd +1 this idea. It sounds like we could make the scenarios generic enough
> to be usable also outside CI? Maybe they can serve as samples?
> --
> Giulio Fidente
> GPG KEY: 08D733BA
>
>
> __
> 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

Re: [openstack-dev] [TripleO] Proposing Julie Pichon for tripleo core

[Carlos Camacho Gonzalez]

+1

On Tue, Nov 22, 2016 at 10:05 PM, Marios Andreou  wrote:
> +1
>
> __ sent from my mobile device kindly excuse spacing & spelling __
>
>
> -Original Message-
> From: Dougal Matthews [dou...@redhat.com]
> Received: Tuesday, 22 Nov 2016, 19:06
> To: OpenStack Development Mailing List (not for usage questions)
> [openstack-dev@lists.openstack.org]
> Subject: [openstack-dev] [TripleO] Proposing Julie Pichon for tripleo core
>
>
> Hi all,
>
> I would like to propose we add Julie (jpich) to the TripleO core team for
> python-tripleoclient and tripleo-common. This nomination is based partially
> on review stats[1] and also my experience with her reviews and
> contributions.
>
> Julie has consistently provided thoughtful and detailed reviews since the
> start of the Newton cycle. She has made a number of contributions which
> improve the CLI and has been extremely helpful with other tasks that don't
> often get enough attention (backports, bug triaging/reporting and improving
> our processes[2]).
>
> I think she will be a valuable addition to the review team
>
> Dougal
>
>
> [1]: http://stackalytics.com/report/contribution/tripleo-group/90
> [2]: https://review.openstack.org/#/c/352852/
>
> __
> 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

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

[Carlos Camacho Gonzalez]

+1 Awesome!!!

On Fri, Nov 4, 2016 at 7:49 PM, Brent Eagles  wrote:
>
>
> On Fri, Nov 4, 2016 at 3:10 PM, Emilien Macchi  wrote:
>>
>> MIchele Baldessari (bandini on IRC) has consistently demonstrated high
>> levels of contributions in TripleO projects, specifically in High
>> Availability area where's he's for us a guru (I still don't understand
>> how pacemaker works, but hopefully he does).
>>
>> He has done incredible work on composable services and also on
>> improving our HA configuration by following reference architectures.
>> Always here during meetings, and on #tripleo to give support to our
>> team, he's a great team player and we are lucky to have him onboard.
>> I believe he would be a great core reviewer on HA-related work and we
>> expect his review stats to continue improving as his scope broadens
>> over time.
>>
>> As usual, feedback is welcome and please vote for this proposal!
>>
>> Thanks,
>> --
>> Emilien Macchi
>>
>
> +1 indeed
>
>
> __
> 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

Re: [openstack-dev] [all] indoor climbing break at summit?

[Carlos Camacho Gonzalez]

Hey! I think is an awesome idea!

- We should be able to do some Top roping as the ropes should be already there.
- No need to take all you equipment (rental package: harness + shoes +
chalk bag 5€) I can take my grigri so no one will die.
- I'll give them a call to check availability.

Cheers,
Carlos.

On Tue, Oct 18, 2016 at 11:18 AM, Chris Dent  wrote:
> On Mon, 17 Oct 2016, Joshua Harlow wrote:
>
>> Anyone want to bring a (gym size recommended, unless the walls there are
>> *hugg*) rope for leading? I don't want to bring mine all the way
>> from CA (unless I have to).
>
>
> I've got a shorty I can probably bring if someone closer cannot. I
> was initially planning to only bring shoes and boulder, but if
> people want to lead that could be fun.
>
> I'm not sure what their restrictions will be on who is allowed to
> lead on their first day. Given it is Catalonia I wouldn't be surprised
> if it is quite laid back.
>
> Anyway, I've made an etherpad where we can accumulate some plans,
> and also linked a doodle poll in there to figure out some good ideas
> for when. If I should put more day time slots into the poll, let me
> know.
>
> https://etherpad.openstack.org/p/ocata-climb
>
>
> --
> 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

Re: [openstack-dev] [TripleO] TripleO Core nominations

[Carlos Camacho Gonzalez]

Hi guys!!!,

This is awesome, I really appreciate all the support/guidance and help
from you! The list is quite long, so forth, a big thanks for all of
you.

Cheers,
Carlos


On Mon, Sep 26, 2016 at 6:04 PM, Steven Hardy  wrote:
> On Thu, Sep 15, 2016 at 10:20:07AM +0100, Steven Hardy wrote:
>> Hi all,
>>
>> As we work to finish the last remaining tasks for Newton, it's a good time
>> to look back over the cycle, and recognize the excellent work done by
>> several new contributors.
>>
>> We've seen a different contributor pattern develop recently, where many
>> folks are subsystem experts and mostly focus on a particular project or
>> area of functionality.  I think this is a good thing, and it's hopefully
>> going to allow our community to scale more effectively over time (and it
>> fits pretty nicely with our new composable/modular architecture).
>>
>> We do still need folks who can review with the entire TripleO architecture
>> in mind, but I'm very confident folks will start out as subsystem experts
>> and over time broaden their area of experience to encompass more of
>> the TripleO projects (we're already starting to see this IMO).
>>
>> We've had some discussion in the past[1] about strictly defining subteams,
>> vs just adding folks to tripleo-core and expecting good judgement to be
>> used (e.g only approve/+2 stuff you're familiar with - and note that it's
>> totally fine for a core reviewer to continue to +1 things if the patch
>> looks OK but is outside their area of experience).
>>
>> So, I'm in favor of continuing that pattern and just welcoming some of our
>> subsystem expert friends to tripleo-core, let me know if folks feel
>> strongly otherwise :)
>>
>> The nominations, are based partly on the stats[2] and partly on my own
>> experience looking at reviews, patches and IRC discussion with these folks
>> - I've included details of the subsystems I expect these folks to focus
>> their +2A power on (at least initially):
>>
>> 1. Brent Eagles
>>
>> Brent has been doing some excellent work mostly related to Neutron this
>> cycle - his reviews have been increasingly detailed, and show a solid
>> understanding of our composable services architecture.  He's also provided
>> a lot of valuable feedback on specs such as dpdk and sr-iov.  I propose
>> Brent continues this exellent Neutron focussed work, while also expanding
>> his review focus such as the good feedback he's been providing on new
>> Mistral actions in tripleo-common for custom-roles.
>>
>> 2. Pradeep Kilambi
>>
>> Pradeep has done a large amount of pretty complex work around Ceilomenter
>> and Aodh over the last two cycles - he's dealt with some pretty tough
>> challenges around upgrades and has consistently provided good review
>> feedback and solid analysis via discussion on IRC.  I propose Prad
>> continues this excellent Ceilomenter/Aodh focussed work, while also
>> expanding review focus aiming to cover more of t-h-t and other repos over
>> time.
>>
>> 3. Carlos Camacho
>>
>> Carlos has been mostly focussed on composability, and has done a great job
>> of working through the initial architecture implementation, including
>> writing some very detailed initial docs[3] to help folks make the transition
>> to the new architecture.  I'd suggest that Carlos looks to maintain this
>> focus on composable services, while also building depth of reviews in other
>> repos.
>>
>> 4. Ryan Brady
>>
>> Ryan has been one of the main contributors implementing the new Mistral
>> based API in tripleo-common.  His reviews, patches and IRC discussion have
>> consistently demonstrated that he's an expert on the mistral
>> actions/workflows and I think it makes sense for him to help with review
>> velocity in this area, and also look to help with those subsystems
>> interacting with the API such as tripleoclient.
>>
>> 5. Dan Sneddon
>>
>> For many cycles, Dan has been driving direction around our network
>> architecture, and he's been consistently doing a relatively small number of
>> very high-quality and insightful reviews on both os-net-config and the
>> network templates for tripleo-heat-templates.  I'd suggest Dan continues
>> this focus, and he's indicated he may have more bandwidth to help with
>> reviews around networking in future.
>>
>> Please can I get feedback from exisitng core reviewers - you're free to +1
>> these nominations (or abstain), but any -1 will veto the process.  I'll
>> wait one week, and if we have consensus add the above folks to
>> tripleo-core.
>
> Ok, so we got quite a few +1s and no objections, so I will go ahead and add
> the folks listed above to tripleo-core, congratulations (and thanks!) guys,
> keep up the great work! :)
>
> Steve
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 

Re: [openstack-dev] [TripleO] TripleO Deep dive sessions for CI topics.

[Carlos Camacho Gonzalez]

Yeahp I think in case of debugging upstream submissions (on CI)
it's the same process of debugging locally those errors,
in which case, the only missing part there I think can be
just to point where to see when reading CI logs.

What I think will be a bigger challenge it's about to
teach other people to understand and master how
TripleO CI works, including how to define new jobs,
where to see when we have a package conflict
breaking the build, or how to detect infra issues
among other topics. (This won't be for debugging
submissions, instead to debug when we have CI
failures)

Not sure if it's needed a deep historical understanding about
how CI was built and about how it's actually working
but I think this will make people love a little bit more
our CI.

I'll add more items to the Etherpad, let's see how many people
are interested.

Cheers,
Carlos.


On Wed, Aug 24, 2016 at 8:24 PM, James Slagle <james.sla...@gmail.com>
wrote:

> On Wed, Aug 24, 2016 at 12:17 PM, Carlos Camacho Gonzalez
> <ccama...@redhat.com> wrote:
> > Hello guys!
> >
> > I will like to ask you a question related to future TripleO deep dive
> > sessions.
> >
> > What about having a specific series for CI? I read some people kind of
> > “complaining” on IRC when CI does not work properly and assuming that
> taking
> > care of CI is part of everyone's work let's try go have more eyes on CI
> > (including me).
> >
> > I believe if more people its actually able to debug “real” CI issues we
> will
> > be able to decrease the amount of work that these tasks take from the
> team.
> >
> > I added to https://etherpad.openstack.org/p/tripleo-deep-dive-topics a
> > section with some topics, feel free to add/edit items and let's discuss
> it
> > on the weekly meeting to see if in a mid-term we can have some
> introduction
> > to CI.
>
> I think this is a great idea. What I'd like to know before planning
> something like this is what specific things do people need help on
> when it comes to debugging failed jobs. How have folks tried to debug
> jobs that have failed and gotten stuck?
>
> Most of the time it is looking at logs and trying to reproduce
> locally. I'd be happy to show that, but I feel like we've already
> covered that to a large degree. So, I'd like to dig a little more into
> specific ways people get stuck with failures and then we can directly
> address those.
>
> Ideally, a root cause of a failure could always be found, but that is
> just not going to be the case given other constraints. It often comes
> down to what one is able to reproduce locally, and how to mitigate the
> issues as best we can (see email I just sent for an example).
>
> Let me know or add the specifics to the etherpad and I'll pull
> something together if there are no other volunteers :).
>
> --
> -- James Slagle
> --
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
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 Deep dive sessions for CI topics.

[Carlos Camacho Gonzalez]

Hello guys!

I will like to ask you a question related to future TripleO deep dive
sessions.

What about having a specific series for CI? I read some people kind of
“complaining” on IRC when CI does not work properly and assuming that
taking care of CI is part of everyone's work let's try go have more eyes on
CI (including me).

I believe if more people its actually able to debug “real” CI issues we
will be able to decrease the amount of work that these tasks take from the
team.

I added to https://etherpad.openstack.org/p/tripleo-deep-dive-topics a
section with some topics, feel free to add/edit items and let's discuss it
on the weekly meeting to see if in a mid-term we can have some introduction
to CI.

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