on and get you +2 ;-)
As usual, it's open for voting, feel free to bring any feedback.
Thanks everyone,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
steeples as nesting sites. The species name "alba"
refers to the white color. Other names for the Barn Owl have included
Monkey-faced Owl, Ghost Owl, and Church Owl. (source:
https://www.owlpages.com/owls/species.php?s=10)
Stay tuned!
--
Your fellow reporter, Emilien Macchi
, introspection, pacemaker on 3
controllers, containerized overcloud, TLS and it runs Tempest (shiny
eh?).
Thanks a lot to Sagi, Juan and reviewers who helped to make that effort.
On Thu, Nov 23, 2017 at 2:44 PM, Emilien Macchi <emil...@redhat.com> wrote:
> On Thu, Nov 23, 2017 at 1:54 PM
@redhat.com> wrote:
>>
>> On 11/30/17 8:11 PM, Emilien Macchi wrote:
>>>
>>> A few months ago, we renamed ovb-updates to be
>>> tripleo-ci-centos-7-ovb-1ctlr_1comp_1ceph-featureset024.
>>> The name is much longer but it describes better what it's doing.
&g
they became quite familiar now, and it would
confuse people to rename the jobs.
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
importantly has always
> done quality reviews. She also has been working in the very intense rover
> role on the CI squad in the past CI sprint, and has done very well in that
> role.
solid +1 :-)
Thanks for your work Ron
/governance like Kendall did.
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
On Mon, Nov 27, 2017 at 5:44 AM, Alfredo Moralejo Alonso
<amora...@redhat.com> wrote:
>
>
> On Thu, Nov 23, 2017 at 7:59 PM, Emilien Macchi <emil...@redhat.com> wrote:
>>
>> Queens's main theme is stabilization.
>> That's what we're currently working
On Thu, Nov 23, 2017 at 1:54 PM, Emilien Macchi <emil...@redhat.com> wrote:
> On Thu, Nov 23, 2017 at 1:49 PM, Emilien Macchi <emil...@redhat.com> wrote:
>> So far in my testing I found 2 issues:
>>
>> - IPv6 + TLS doesn't work in tripleo-ci, certificates aren't
On Thu, Nov 23, 2017 at 1:49 PM, Emilien Macchi <emil...@redhat.com> wrote:
> So far in my testing I found 2 issues:
>
> - IPv6 + TLS doesn't work in tripleo-ci, certificates aren't good
> (expected). We might need to generate new ones, I'll take a look
> myself
-23_21_03_57
Any help on that one is welcome
Thanks,
On Thu, Nov 23, 2017 at 11:37 AM, Emilien Macchi <emil...@redhat.com> wrote:
> I forgot to add an ongoing effort to reduce number of services
> deployed on ovb jobs at a strict minimum:
> https://review.openstack.org/522310
> So we h
.
On Thu, Nov 23, 2017 at 10:59 AM, Emilien Macchi <emil...@redhat.com> wrote:
> Queens's main theme is stabilization.
> That's what we're currently working on in our CI, see which areas we
> can consolidate and stabilize so we can continue to scale TripleO
> development.
>
&g
than welcome,
--
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/opens
ase job.
But I'll let the tripleo-ui maintainers to answer that question.
>
>
> On Wed, Nov 22, 2017 at 9:43 AM, Emilien Macchi <emil...@redhat.com> wrote:
>>
>> Yeah, I confirm we were able to build an RPM and release a new version
>> of TripleO UI, which was our
balls listing, and the file is in fact present. Our
> project doesn't produce any other release artifacts upstream.
>
> Please direct any future failures to me (in addition to the mailing list
> of course)
>
> Thanks
>
> Honza Pokorny
>
> On 2017-11-21 21:34, Emilien M
I'm trying to backport zuulv3 layout in ec2api but it seems like the
gate is broken:
https://review.openstack.org/#/c/521592/
Bringing it here for visibility, hopefully someone from the project
can have a look.
Thanks,
--
Emilien Macchi
f230bd29516dc202eb406270604f27e27f9/release/release-openstack-javascript/95af4ef/job-output.txt.gz#_2017-11-22_03_01_48_750499
>
> ___
> Release-job-failures mailing list
> release-job-failu...@lists.openstack.org
ork.
> Thanks !
>
> [1]: http://git.openstack.org/cgit/openstack-infra/tripleo-ci/tree/zuul.d
>
> David Moreau Simard
> Senior Software Engineer | OpenStack RDO
>
> dmsimard = [irc, github, twitter]
--
Emilien Macchi
16, 2017 at 11:20 AM, Emilien Macchi <emil...@redhat.com> wrote:
>> TL;DR: don't approve or recheck any tripleo patch from now, until
>> further notice on this thread.
>>
>> Some good progress has been made on migrating legacy tripleo CI jobs
>> to be
/514778 is merged, people are free
to do recheck or approve any patches. We hope it should happen over
the weekend.
- I'll continue to migrate all other tripleo projects to have in-tree
layout. On the list: t-p-e, t-i-e, paunch, os-*-config,
tripleo-validations.
Thanks for your help,
--
Emilien
ores.
If you can't self triage a bug in Launchpad, please let us know and
we'll fix it, even if you're not core.
The URL to do it is: https://launchpad.net/~tripleo-drivers/+addmember
For Gerrit, I took care of it.
--
Em
"ansiblelize" the tasks and optimize things.
But before that, we need to migrate and do this first step now.
Thanks,
On Tue, Nov 14, 2017 at 4:18 PM, Emilien Macchi <emil...@redhat.com> wrote:
> Hi,
>
> I'm working on migrating all TripleO CI jobs to be in-tree, I'm also
On Tue, Nov 14, 2017 at 11:44 PM, Andreas Jaeger <a...@suse.com> wrote:
> On 2017-11-15 01:18, Emilien Macchi wrote:
>> Hi,
>>
>> I'm working on migrating all TripleO CI jobs to be in-tree, I'm also
>> refactoring the layout and do some cleanup.
>
>
in
project-config & zuul layout, so we can update my work in tripleo-ci
patch, otherwise it will be lost when we land the patches.
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage quest
nstack 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,
Thanks Marios for proposing them :-)
Of course +1, thanks for your hard work! Stay awesome.
---
Emilien Macchi
On Nov 9, 2017 4:58 PM, "Marios Andreou" <mandr...@redhat.com> wrote:
>
>
> On Thu, Nov 9, 2017 at 12:24 AM, Giulio Fidente <gfide...@redhat.com>
> wrote:
>
>> Hi,
>>
>&
y check jobs.
> We talked about allowing rdo sf to -2 reviews upstream as well which would
> be handy.
LGTM. Thanks for the clarification.
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
arity from
what we had upstream) in RDO CI.
We'll need to make the job experimental in RDO CI, so we can only run
them at demand until they actually work. Can we do that as well?
Thanks,
--
Emilien Macchi
__
OpenStack Developm
On Wed, Nov 8, 2017 at 3:30 AM, James Slagle <james.sla...@gmail.com> wrote:
> On Sun, Nov 5, 2017 at 7:01 PM, Emilien Macchi <emil...@redhat.com> wrote:
>> On Mon, Oct 2, 2017 at 5:02 AM, Dan Prince <dpri...@redhat.com> wrote:
>> [...]
>>
>>> -CI r
in master. That would be
the next iteration I guess.
Any feedback is welcome,
On Mon, Nov 6, 2017 at 6:22 PM, Emilien Macchi <emil...@redhat.com> wrote:
> On Mon, Nov 6, 2017 at 12:57 PM, Wesley Hayutin <whayu...@redhat.com> wrote:
>>
>>
>> On Mon, Nov 6, 2017 a
On Mon, Nov 6, 2017 at 12:57 PM, Wesley Hayutin <whayu...@redhat.com> wrote:
>
>
> On Mon, Nov 6, 2017 at 7:35 AM, Bogdan Dobrelya <bdobr...@redhat.com> wrote:
>>
>> On 11/6/17 1:01 AM, Emilien Macchi wrote:
>>>
>>> On Mon, Oct 2, 201
edhat.com>
>>> wrote:
>>>
>>>> On Sat, Nov 4, 2017 at 2:27 AM, Emilien Macchi <emil...@redhat.com>
>>>> wrote:
>>>>>
>>>>> Since we've got promotion, we can now properly test upgrades from ocata
>>&g
ws, and great patches.
>
> With Ana's help as a core, we can get more done, and innovate faster.
>
> If there are no objections within a week, we'll proceed with adding Ana
> to the team.
+1, good work Ana!
Thanks Honza f
On Mon, Nov 6, 2017 at 4:35 AM, Bogdan Dobrelya <bdobr...@redhat.com> wrote:
> On 11/6/17 1:01 AM, Emilien Macchi wrote:
>>
>> On Mon, Oct 2, 2017 at 5:02 AM, Dan Prince <dpri...@redhat.com> wrote:
>> [...]
>>
>>> -CI resources: better use of C
on overcloud.
I really want to get consensus on these points, please raise your
voice now before we engage some work on that front.
[...]
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscr
point, now the framework is in place and we had promotion.
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
/tripleo-project-update
--
Emilien Macchi on behalf of the TripleO team
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
On Wed, Oct 25, 2017 at 1:59 PM, Emilien Macchi <emil...@redhat.com> wrote:
> Quick update before being afk for some hours:
>
> - Still trying to land https://review.openstack.org/#/c/513701 (thanks
> Paul for promoting it in gate).
Landed.
> - Disabling voting on scenar
branches (syntax jobs not
running properly) - jeblair is looking at it now
Once again, we'll need to retrospect and see why we reached that
terrible state but let's focus on bringing our CI in a good shape
again.
Thanks a ton to everyone who is involved,
On Wed, Oct 25, 2017 at 7:25 AM, Emilien Macchi
/515070
- I cleared the patches in check and queue to make sure the 2 blockers
are tested and can be merged in priority. I'll keep an eye on it
today.
Any help is very welcome.
On Wed, Oct 25, 2017 at 5:58 AM, Emilien Macchi <emil...@redhat.com> wrote:
> We have been working very hard to get
please do not recheck, rebase or approve any patch until further notice.
Thank you,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
re often asked for that because our communities are
> largely operators and we're arguably closest projects to operators).
>
> I, for one, think we should keep current stable policy, not make
> exception for deployment tools, and address this issue across the
> board. What Emilien is descr
ionality. If we're happy with where we get to in queens with
> config-download, we could consider making it the default.
We'll give feedback in the review.
Thanks James for this update,
--
Emilien Macchi
___
ll it change in the future?
(so I can update my calendar)
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ck.org/#/c/513943/
Thanks Wes & David for helping out,
--
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
one displayed in Gerrit. Please
scroll-down to the comments to see first pipeline results as well, so
we make sure we're not merging patches that didn't pass some
non-voting jobs (specially the ones in check-tripleo).
Thank you,
--
Emilien Macchi
On Mon, Oct 16, 2017 at 4:27 AM, Thierry Carrez <thie...@openstack.org> wrote:
> Emilien Macchi wrote:
>> [...]
>> ## Proposal
>>
>> Proposal 1: create a new policy that fits for projects like installers.
>> I kicked-off something here: https://re
Stack 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
___
>
> On Fri, Oct 13, 2017 at 11:49 AM, Mohammed Naser <mna...@vexxhost.com>
> wrote:
>>
>>
>> On Fri, Oct 13, 2017 at 1:21 PM, Emilien Macchi <emil...@redhat.com>
>> wrote:
>>>
>>> Alfredo has been doing an incredible work on maintaining P
ce and motivation, make our community growing in
healthy and diverse ways.
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
htt
ty etiquette (not my best option in my opinion).
Anyway, feedback is welcome, I'm now listening. If you work on Kolla,
TripleO, OpenStack-Ansible, PuppetOpenStack (or any project who has
this need), please get involved in the review process.
Thanks
and solid manner.
Also, he has an excellent understanding how things work in this
project and I would like to propose him part of p-o-i maintainers
(among the rest of the whole core team and also dmsimard).
As usual, feel free to vote and give feedback.
Thanks,
--
Emilien Macchi
eams). (ex: doc team had a PTG
session about visioning as well).
I hope I answered the question, please let me know if that's not the
case if you want more details.
--
Emilien Macchi
__
OpenStack Development Mailing List (not fo
ot;perennity" for our end-users.
Having talked with some users, some folks say "OpenStack becomes
boring and we like it". Pursuing the discussion, they like to have
long life API support and stability in how they operate. I think at a
TC level we need to make sure we can both inno
TC
might ensure that healthy metrics and discussion happen, so projects
can scale.
I'm happy to answer questions on that topic.
Thanks Ed for this first question :-)
--
Emilien Macchi
__
OpenStack Development Mailing List
ll your extreme hard work at the TC, which is a great
example for our community.
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj
>>>
>>>>
>>>> Agreed, I think this is the longer term plan in regards to using
>>>> APB's, where everything consumed is an external playbook/role.
>>>>
>>>> We definitely want to consider this plan in parallel with the POC work
>>>> t
ake that, you'll help to solve the bugs more
quickly and everyone is happy.
Any question or feedback is welcome.
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscrib
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-d
able I guess.
Ping me anytime for further discussion,
Thanks!
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://li
ng OpenStack with Ansible
apbs.
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
fic to TripleO that we want it in the name?
--
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
d emails anyone that will be speaking with you.
TripleO - Emilien Macchi - emil...@redhat.com
Thanks!
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj
g
places, and continue to make OpenStack the best Open-Source project
to contribute
to.
Of course you don't need to be TC member to contribute on these topics; though
changes made in Governance are voted by TC members; so I would like to be
candidate one more time.
Thank you for your consideration,
-
Emilien, would you suggest we
> define these as separate line items as well?
[...]
No, I think it's good as it is now, good work!
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscr
by end of Queens (put some number in metrics is
probably a good start) - it's already mentioned in your draft vision
but it might be revisited once you define the 2 previous items.
Good work!
--
Emilien Macchi
__
O
east a good
step forward.
Also, we could ship this feature as "experimental" in Queens and
"stable" in Rocky (even if it has been developed since more than one
cycle by dprince & co), I think it's a r
r work is related to *Upgrades*
and not minor updates but still super cool.
Note: FTR we discussed on IRC that we would probably do the same kind
of thing for minor updates testing.
Thanks Wes,
--
Emilien Macchi
__
Ope
rade front, but I really think having more
investment in CI will help on the long term. If upgrade folks need
help on CI, bring it to the TripleO CI squad so they can maybe help,
etc...
Thanks,
--
Emilien Macchi
__
OpenStack Dev
give up the tag and
which repos we do it.
2) Someone to propose an amendment to the existing stable policy or
propose a new policy.
3) Figure out if we can postpone TripleO Newton EOL and make sure
we're doing it right (e.g. having CI jobs working, not burning
anything etc).
4) On the long term,
tested.
That's IMHO how we should write our software.
If there is any feedback on this, please let us know here, otherwise
I'll keep my -2 until we've got this coverage in place. Also please
someone (maybe matbu?) raise your hand if you want to pair up and do
this quickly.
Thanks,
--
Emilien
iew.openstack.org/507924 in the meantime.
I'm not entirely sure about the THT-extras and the fact it would add
another layer of complexity, but I'm happy to discuss about it.
Tony, Alex, Steve, (others of course) - if you can look at the
governance change and give feedback on it, that would help.
Th
d on real environments (not
in devstack from master). If we can't have this code in-tree, we'll
probably carry this patch downstream (which is IMHO bad because of
maintenance and lack of CI). In that case, I'll vote to give up
stable:follows-policy so we can do what we need.
--
Emili
.
If you need any help to get backport merged, please raise it here or
ask on IRC as usual.
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
for the help,
--
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
team
is awesome so I have no doubt we'll continue to succeed.
Thanks, and enjoy the PTG for the lucky attendees!
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
s collaboration meeting and
Wednesday is whatever TripleO / Kolla collab related things.
Does it make sense?
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
will confuse people
otherwise.
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
%40group.calendar.google.com=America/Denver
Which contains an updated agenda for TripleO related topics.
We'll track everything in this etherpad:
https://etherpad.openstack.org/p/tripleo-ptg-queens
I'm looking forward to seeing you folks!
Have safe trips,
--
Emilien Macchi
o and John to make that happen, thanks again for
your hard work :-)
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subjec
On Wed, Apr 5, 2017 at 1:49 PM, Emilien Macchi <emil...@redhat.com> wrote:
[...]
> == Solutions
>
> 1) Switch pingtest to Tempest run on some specific tests, with feature
> parity of what we had with pingtest.
> For example, we could imagine to run the scenarios that deplo
We don't run the weekly meeting during the PTG, so next meeting is
scheduled for September 19th.
Safe travels,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
On Tue, Sep 5, 2017 at 10:16 AM, Ben Nemec <openst...@nemebean.com> wrote:
>
>
> On 09/04/2017 11:50 PM, Emilien Macchi wrote:
>>
>> On Fri, Sep 1, 2017 at 2:37 PM, Tong Liu <lex...@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> In
an/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/mail
at's good).
For the backports, we'll have to evaluate case by case and see if it's possible.
Thanks for your work and we hope our collaboration can happen earlier
the next time.
> Thanks,
> Tong
> [1] Blueprint:
> https://blueprin
On Sun, Sep 3, 2017 at 7:40 PM, Emilien Macchi <emil...@redhat.com> wrote:
> Here are the priorities and blockers so we can release final Pike.
> If you have any question, or think I missed something, or have any
> comment, please reply to this thread.
> Also, your help is cr
bugs when you do backports though.
We're almost there! Thanks all for the help,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
probably missed something (it's WIP?) but I found useful to clarify
now, since we're about to release final Pike.
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
ppens.
Thank you, that would be very helpful.
--
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
he etherpad to some LP blueprints
>
> thanks Emilien for setting everything up :D
I appreciate your help in doing the agenda :-)
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: op
On Thu, Aug 31, 2017 at 10:27 AM, Emilien Macchi <emil...@redhat.com> wrote:
[...]
> I'm preparing a Google Calendar today, so everyone can easily
> understand the schedule.
I prepared this public agenda:
https://calendar.google.com/calendar/ical/c1g5npdrsd3p37
easily
understand the schedule.
Any feedback / comment is welcome, thanks.
On Tue, Aug 29, 2017 at 8:36 AM, Emilien Macchi <emil...@redhat.com> wrote:
> On Mon, Aug 28, 2017 at 3:17 PM, Emilien Macchi <emil...@redhat.com> wrote:
> [...]
>> Also, it's still time to propose
On Tue, Aug 29, 2017 at 4:17 PM, Emilien Macchi <emil...@redhat.com> wrote:
> We are currently dealing with 4 issues and until they are fix, please
> do not approve any patch. We want to keep the gate clear to merge the
> fixes for the 4 problems first.
>
> 1) devstack-gate br
/1708832
Until further notice from Alex or myself, please do not approve any patch.
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
On Mon, Aug 28, 2017 at 3:17 PM, Emilien Macchi <emil...@redhat.com> wrote:
[...]
> Also, it's still time to propose topics, please go ahead and
> contribute to the etherpad. We'll review the schedule before the PTG
> (probably during our weekly meetings tomorrow and next week).
oduction environment and hopefully spot issues
we wouldn't see with multinode jobs
Pike, Ocata, Newton:
no change on OVB job
(note it's a proposal, not a statement)
[...]
> [3] https://review.openstack.org/498474
a
On Fri, Aug 25, 2017 at 5:00 PM, Emilien Macchi <emil...@redhat.com> wrote:
> I created an etherpad: https://etherpad.openstack.org/p/deployment-queens
>
> Please bring topics (and names) - we'll try to be prepared before the
> PTG with an agenda and some scheduling.
I th
to the etherpad. We'll review the schedule before the PTG
(probably during our weekly meetings tomorrow and next week).
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
cheduling before the PTG but it would likely
happen between Wednesday and Friday morning.
Thanks,
--
Emilien Macchi
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.open
LB + web server + uwsgi
>> - Possibility of sharing infrastructure (mariadb/rabbitmq/...)
>> experience/code between projects.
>>
>> Thank you in advance.
>>
>> Best regards,
>> JP
>>
>> On Fri, Aug 25, 2017 at 8:16 PM, Emilien Macchi <emil.
201 - 300 of 1350 matches
Mail list logo
