pet-enterprise-lifecycle
>>
>> ___
>> OpenStack-operators mailing list
>> openstack-operat...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
&
-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
__
OpenStack Development Mailing
tps://github.com/redhat-openstack/ansible-role-tripleo-overcloud-prep-containers/issues
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u
Our current certificate handling code is dealing only with IPv4
> addresses, so if we need to test both, we'll have to add that part too.
Definitely yes, I think most of people who go in production with IPv6
has SSL, so it should be the standard imho.
--
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
>
--
Emilien Macchi
__
leo-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
va/conf/netconf.py#L25-L40
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailma
:openstack/tripleo-specs+status:open
We decided to freeze Ocata specs for Ocata-2 (we will probably change
this limit in the next cycle to be pike-1?).
Please let us know any question or feedback.
Thanks,
--
Emilien Macchi
__
is now open and my
hope is that we find a consensus soon, so we can make progress in our
testing coverage.
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openst
is required? Even with rpm,
> can't we just rpm --prefix=/some/other/location?
>
> Thanks,
> -Alex
>
>
>>
>>>
>>> Thanks,
>>> -Alex
>>>
>>>> 1: https://review.openstack.org/#/c/395813
>>>> 2:
>>>>
gt; 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
;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 thou
On Fri, Nov 25, 2016 at 7:22 AM, Gabriele Cerami wrote:
> On 22 Nov, Emilien Macchi wrote:
>> 1) Re-use experience from Puppet OpenStack CI and have environments
>> that are in a branched repository.
>> a) Move CI environments and pingtest into
>> tripleo-heat-templates
we support Ubuntu and CentOS and we
commit to test these distros in project gates, like it's already the
case for a lot of projects.
https://review.openstack.org/#/c/402940/
Feel free to give any feedback,
Thanks!
--
to find a liaison. The liaison will act as a
squad lead and PTL will collaborate with liaison first when dealing
with some work related to the squad. If you volunteer, please put your
name.
This new squad thing is really new for us, please keep giving feedback
and propose new ideas,
Thanks!
--
Emil
sn't have a team yet).
For now, openstack/governance is the repository for Goals, please
propose them here.
Please give feedback, we're doing iterations here, and hopefully we'll
improve our Community Goals over the next cycles.
Thank
about this proposal.
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/mailma
wn service, or propose
scenario improvements, it's highly welcome!
Thanks,
On Mon, Nov 28, 2016 at 3:35 PM, John Trowbridge wrote:
>
>
> On 11/22/2016 09:02 PM, Emilien Macchi wrote:
>> == Context
>>
>> In Newton we added new multinode jobs called "scenarios&qu
10 positive replies, I think it's a yes :-)
Thanks again Alex for your hard work, it's very appreciated.
On Fri, Dec 2, 2016 at 4:16 PM, Giulio Fidente wrote:
> On 12/01/2016 11:26 PM, Emilien Macchi wrote:
>>
>> Team,
>>
>> Alex Schultz (mwhahaha on IRC) h
On Tue, Nov 29, 2016 at 7:39 PM, Emilien Macchi wrote:
> A few months ago, our community started to find and work on
> OpenStack-wide goals to "achieve visible common changes, push for
> basic levels of consistency and user experience, and efficiently
> improve certain areas whe
e deployed with Pacemaker on a dedicated
node:
https://review.openstack.org/#/c/362389
I'm not sure if we can deploy it with systemd only, in a HA manner but
Michele could eventually confirm.
Regarding the timeline to do it in Ocata, I'm really not sure that's
doable, it depen
ttps://blueprints.launchpad.net/tripleo/+spec/remote-execution
>
> __________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> htt
s, not adding even more
> example templates.
>
> If we can do some of that during the Ocata timefram, I expect fully
> composable/custom networks may be possible during Pike?
Thanks Steve for your inputs, it sounds like we have a plan.
Tim, would you mind to draft a tripleo-specs
pics
>
> --
> Regards,
> Ana Krivokapic
> Senior Software Engineer
> OpenStack team
> Red Hat Inc.
>
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
gt;
> [1]
> http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-12-13-14.00.log.html
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.opensta
y
have more than 100 bugs open, just for ocata-2) and keep CI stable
until final release. The last thing we want is to push for last
features and stress people because it breaks all the things.
Please provide any feedback, it's highly we
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
__
Op
On Tue, Dec 13, 2016 at 5:02 PM, Emilien Macchi wrote:
> I thought it would be useful to share our roadmap for TripleO releases.
> As a reminder, this is the official source of trust for OpenStack
> releases schedule:
> https://releases.openstack.org/ocata/schedule.html
>
> O
ck
> | stack_owner | None
> | stack_status | CREATE_FAILED
> | stack_status_reason | Resource CREATE failed: ResourceInError:
> | | resources.server1: Went to status ERROR due to
> | | "Message: No valid host was found. There are not
> enough
>
06 1.78
> 7 235 1181.5
> 8 193 130 1.67
> 9 147 123 1.84
> 10 233 159 1.68
> 11 13786 1.63
> 12 20 5 1.25
> total 1532 1079 1.7
&
)
> 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
le-liberty_eol_data-txt-L181
>
> __________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mail
details on the bugs, and give any
feedback.
Again, I would like to thank all people involved in debugging,
patching and reviewing fixes to unblock CI this week, it was not easy
but we made it as a team!
Enjoy the wee
On Sat, Dec 17, 2016 at 4:30 PM, Emilien Macchi wrote:
> This week was outstanding for CI and I found useful to share what
> happened in TripleO and Puppet CIs, and where we are now.
> TL;DR:
> - Puppet OpenStack: full green on ocata/newton/mitaka
> - TripleO CI: full green e
I'm proposing a new Newton release for TripleO, as we scheduled it a
few weeks ago:
https://review.openstack.org/#/c/412643/
Please let me know any blocker or any backport you want to see in this release.
Thanks,
--
Emilien M
On Sat, Dec 17, 2016 at 4:30 PM, Emilien Macchi wrote:
> This week was outstanding for CI and I found useful to share what
> happened in TripleO and Puppet CIs, and where we are now.
> TL;DR:
> - Puppet OpenStack: full green on ocata/newton/mitaka
> - TripleO CI: full green e
We won't hold our weekly meeting on December 27th.
Next meeting is schedule on January 3rd.
Happy holidays everyone,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: open
l,
tripleo/ironic, tripleo/heat, etc).
Please let us know any question or feedback,
Looking forward to seeing you there!
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
abandoned some of the patches. Let's see if we can come to an
> agreement about how to improve the experience for people finding our
> projects and wanting to collaborate with us.
>
> [1]:
> https://review.openstack.org/#/q/owner:zhouyunfeng%40inspur.com+topic:addCONTRIBUTING.rst
> --
> <http://twitter.com/heiditretheway>
<http://www.openstack.org/>
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.o
patches is definitely not
how our project work, we develop in the open, we have policies, let's
respect them.
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
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: ht
t; 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 que
ep the meeting open
to anyone and take notes afterward, well communicated to the
community.
> Thank you for your thoughts,
> Attila
>
>
>> https://wiki.openstack.org/wiki/Meetings/TripleO
>>
>> Thanks!
>>
>> Steve
>>
>> _______
On Wed, Jan 4, 2017 at 8:57 AM, John Trowbridge wrote:
>
>
> On 01/03/2017 07:30 PM, Emilien Macchi wrote:
>> I've noticed some TripleO core reviewers self approving patch without
>> respecting our review policy, specially in tripleo-quickstart.
>>
>
> Th
deployment. and run pure v2 everywhere in my cloud.
Thanks for your help,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
t like the idea, and I'll just wait for Heat to
support Glance v2 API.
[1] https://review.openstack.org/#/c/240450/
[2] http://lists.openstack.org/pipermail/openstack-dev/2017-January/109722.html
--
Emilien Macchi
__
oned here. We
don't want to inject more regressions.
Also, please do not try CI promotions until we have solved all blockers.
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscrib
On Fri, Jan 6, 2017 at 6:57 AM, Emilien Macchi wrote:
> I found useful to share a status on what's going on in CI now.
>
> 1) We fixed ovb-updates job: https://review.openstack.org/#/c/416706/
> It should be stable again now. Please don't ignore it anymore (it was
>
ld be
>> great if we could set up a non-voting job on t-h-t with convergence enabled
>> and start tracking memory use over time there too. As a first step, maybe we
>> could at least add an experimental job on Heat to give us a baseline?
>
> +1. We haven't made any huge changes i
On Fri, Jan 6, 2017 at 5:41 PM, Zane Bitter wrote:
> On 06/01/17 16:58, Emilien Macchi wrote:
>>
>> On Fri, Jan 6, 2017 at 4:35 PM, Thomas Herve wrote:
>>>
>>> On Fri, Jan 6, 2017 at 6:12 PM, Zane Bitter wrote:
>>>>
>>>> It's wo
On Tue, Jan 3, 2017 at 9:08 AM, Emilien Macchi wrote:
> (Happy new year folks!)
>
> Forwarding Heidi's email to TripleO folks, so anyone can contribute to it.
>
> Feel free to propose questions on:
> https://etherpad.openstack.org/p/tripleo-user-survey-2017
>
> The
97/6/extraconfig/pre_network/host_config_and_reboot.role.j2.yaml
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
le on Friday, who would be travelling).
Thanks for your collaboration!
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
and avoid conflicts.
>
> Andy
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cg
-1 patches which don't have a release note. I think 3 or 4
months is fair to learn how to use reno (it takes less than 5 min to
create a good release note).
Any feedback is highly welcome, let's make TripleO releases better!
Thanks,
[1] http://docs.opensta
On Wed, Jan 11, 2017 at 9:21 AM, Emilien Macchi wrote:
> Greetings,
>
> OpenStack has been using reno [1] to manage release notes for a while
> now and it has been proven to be super useful.
> Puppet OpenStack project adopted it in Mitaka and since then we loved it.
> The pat
mmend to move forward and stop ignoring the new API version.
> We could document how to hide the resource in Heat if you don't deploy
> Glance v1.
>
> --
> Thomas
>
> __
> OpenStack Development
> 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 M
eleases.openstack.org/schedule.ics
This is really awesome.
I found useful to document it in the PTL guide:
https://review.openstack.org/419600
Any feedback is welcome.
> Doug
>
> __________
> OpenStack Development Mailing Lis
ack.org/openstack/tripleo-specs/specs/ocata/containerize-tripleo-overcloud.html
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
://etherpad.openstack.org/p/community-goals
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org
On Fri, Nov 25, 2016 at 12:51 PM, Emilien Macchi wrote:
> I'm happy to announce we officially accepted TripleO Squads in our project:
> http://specs.openstack.org/openstack/tripleo-specs/specs/policy/squads.html
>
> We hope it will help us to scale our team and improve our way to
estions)
> 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 fo
Thanks Doug for your excellent technical leadership and being always
helpful. Your impact on release management has been very appreciated.
---
Emilien Macchi
On Jan 13, 2017 9:16 PM, "Anita Kuno" wrote:
> On 2017-01-13 03:19 PM, Steve Martinelli wrote:
>
>> +++ Thanks for
1, 2017 8:49 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [tripleo] Release notes in TripleO
>
>
>
> On 01/11/2017 08:24 AM, Emilien Macchi wrote:
>> On Wed, Jan 11, 2017 at 9:21 AM, Emilien Macchi wrote:
>>
it to stable/ocata.
We'll release the client by Thursday 19th end of day.
Please let us know any blocker,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
penstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailma
One day I'll read calendars correctly :-)
Client releases are next week, so we'll release tripleoclient by January 26th.
Sorry for confusion.
On Sun, Jan 15, 2017 at 6:41 PM, Emilien Macchi wrote:
> https://releases.openstack.org/ocata/schedule.html
>
> It's time to rele
1301 - 1369 of 1369 matches
Mail list logo
