+1
On Wed, Nov 29, 2017 at 12:34 PM, John Trowbridge wrote:
> I would like to propose Ronelle be given +2 for the above repos. She has
> been a solid contributor to tripleo-quickstart and extras almost since the
> beginning. She has solid review numbers, but more importantly has always
> done qua
On Thu, Nov 30, 2017 at 2:36 PM, Wesley Hayutin wrote:
> Greetings,
>
> Just wanted to share some progress with the containerized undercloud work.
> Ian pushed some of the patches along and we now have a successful undercloud
> install with containers.
>
> The initial undercloud install works [1]
On Fri, Dec 1, 2017 at 3:54 AM, Bogdan Dobrelya wrote:
> On 11/30/17 10:36 PM, Wesley Hayutin wrote:
>>
>> Greetings,
>>
>> Just wanted to share some progress with the containerized undercloud work.
>> Ian pushed some of the patches along and we now have a successful
>> undercloud install with con
On Fri, Dec 1, 2017 at 8:05 AM, Alex Schultz wrote:
> On Thu, Nov 30, 2017 at 2:36 PM, Wesley Hayutin wrote:
>> Greetings,
>>
>> Just wanted to share some progress with the containerized undercloud work.
>> Ian pushed some of the patches along and we now have a succe
On Fri, Dec 1, 2017 at 7:54 AM, Emilien Macchi wrote:
> Bogdan and Dmitry's suggestions are imho a bit too much and would lead
> to very very (very) long names... Do we actually want that?
>
No i don't think so. I think -- is ideal for communicating at least the
basics. If we did it this way for
Hello everyone,
We have released TripleO for Queens milestone 2 yesterday. As we
discussed at the PTG, now is the time to stop working on new features
and start stabilizing the release. As mentioned in the meeting
today[0], we need to start reviewing the open patches for features
still in flight
+1
On Wed, Dec 6, 2017 at 8:45 AM, Emilien Macchi wrote:
> Team,
>
> Wes has been consistently and heavily involved in TripleO CI work.
> He has a very well understanding on how tripleo-quickstart and
> tripleo-quickstart-extras work, his number and quality of reviews are
> excellent so far. His
+1
On Thu, Dec 7, 2017 at 7:34 AM, Ana Krivokapic wrote:
> Hey TripleO devs,
>
> Gaël has consistently been contributing high quality reviews and patches to
> the tripleo-validations project. The project would highly benefit from his
> addition to the core reviewer team.
>
> Assuming that there a
Hey folks,
So I went through the list of blueprints and moved some that were
either not updated or appeared to have a bunch of patches not in a
mergable state.
Please take some time to review the list of blueprints currently
associated with Rocky[0] to see if your efforts have been moved. If
you
gs/tripleo/2017/tripleo.2017-11-14-14.01.log.html#l-170
>
> [1] - https://review.openstack.org/#/c/502313/
> [2] - https://blueprints.launchpad.net/tripleo/+spec/tripleo-ovs-hw-offload
>
>> -Original Message-
>> From: Alex Schultz [mailto:aschu...@redhat.com]
>> Sent
On Mon, Dec 11, 2017 at 1:20 PM, Brad P. Crochet wrote:
>
>
> On Fri, Dec 8, 2017 at 6:35 PM Alex Schultz wrote:
>>
>> Hey folks,
>>
>> So I went through the list of blueprints and moved some that were
>> either not updated or appeared to have a bunc
able to consume these environment files via the UI as
well.
Thanks,
-Alex
>
>> -Original Message-
>> From: Alex Schultz [mailto:aschu...@redhat.com]
>> Sent: Tuesday, December 12, 2017 12:20 AM
>> To: OpenStack Development Mailing List (not for usage questions)
>
On Tue, Dec 12, 2017 at 5:50 PM, Tony Breeds wrote:
> On Fri, Dec 08, 2017 at 04:34:09PM -0700, Alex Schultz wrote:
>> Hey folks,
>>
>> So I went through the list of blueprints and moved some that were
>> either not updated or appeared to have a bunch of patches
On Wed, Dec 13, 2017 at 11:16 AM, Sven Anderson wrote:
>
> On Sat, Dec 9, 2017 at 12:35 AM Alex Schultz wrote:
>>
>> Please take some time to review the list of blueprints currently
>> associated with Rocky[0] to see if your efforts have been moved. If
>> you believ
On Wed, Dec 13, 2017 at 3:22 PM, Mark Hamzy wrote:
>> I just need an understanding on the impact and the timeline. Replying
>> here is sufficient.
>>
>> I assume since some of this work was sort of done earlier outside of
>> tripleo and does not affect the default installation path that most
>> fo
On Wed, Dec 13, 2017 at 6:36 PM, Mark Hamzy wrote:
> Alex Schultz wrote on 12/13/2017 04:29:49 PM:
>> On Wed, Dec 13, 2017 at 3:22 PM, Mark Hamzy wrote:
>> > What I have done at a high level is to rename the images into
>> > architecture
>> >
On Thu, Dec 14, 2017 at 12:38 PM, Mark Hamzy wrote:
> Alex Schultz wrote on 12/14/2017 09:24:54 AM:
>> On Wed, Dec 13, 2017 at 6:36 PM, Mark Hamzy wrote:
>> ... As I said previously, please post the
>> patches ASAP so we can get eyes on these changes. Since this does
>
On Thu, Dec 14, 2017 at 5:01 PM, Tony Breeds wrote:
> On Wed, Dec 13, 2017 at 03:01:41PM -0700, Alex Schultz wrote:
>> I assume since some of this work was sort of done earlier outside of
>> tripleo and does not affect the default installation path that most
>> folks will con
Hey everyone,
Due to likely low attendance, we'll be canceling the next two weekly
meetings on Dec 26th and Jan 2nd. We'll resume weekly meetings back on
Jan 9th. Happy holidays and stuff.
Thanks,
-Alex
__
OpenStack Develop
On Mon, Nov 20, 2017 at 3:31 PM, David Moreau Simard wrote:
> Hi,
>
> As the migration of review.rdoproject.org to Zuul v3 draws closer, I'd like
> to open up the discussion around how we want to approach an eventual
> migration to Zuul v3 outside the gate.
> I'd like to take this opportunity to a
On Tue, Dec 19, 2017 at 9:53 AM, Ben Nemec wrote:
> The reboot is done (mostly...see below).
>
> On 12/18/2017 05:11 PM, Joe Talerico wrote:
>>
>> Ben - Can you provide some links to the ovs port exhaustion issue for
>> some background?
>
>
> I don't know if we ever had a bug opened, but there's s
Currently they are all globally failing in master (we are using pike
still[0] which is probably the problem) in the tempest run[1] due to:
AttributeError: 'module' object has no attribute 'requires_ext'
I've submit a patch[2] to switch UCA to queens. If history is any
indication, it will probably
On Thu, Dec 21, 2017 at 10:40 AM, Alex Schultz wrote:
> Currently they are all globally failing in master (we are using pike
> still[0] which is probably the problem) in the tempest run[1] due to:
> AttributeError: 'module' object has no attribute 'requires_ext'
> Just a note, the queens repo is not currently synced in the infra so
> the queens repo patch is failing on Ubuntu jobs. I've proposed adding
> queens to the infra configuration to resolve this:
> https://review.openstack.org/529670
>
As a follow up, the mirrors have landed and two of the four sc
On Tue, Jan 2, 2018 at 9:08 AM, Julie Pichon wrote:
> Hi!
>
> On 27 December 2017 at 16:48, Emilien Macchi wrote:
>> - Keystone removed _member_ role management, so we stopped using it
>> (only Member is enough): https://review.openstack.org/#/c/529849/
>
> There's been so many issues with the de
Due to a loss in my family, I will not be around for the next few
weeks. If you have any TripleO issues, please reach out to Emilien
Macchi (emil...@redhat.com) or Steven Hardy (sha...@redhat.com).
Thanks,
-Alex
__
OpenStack
Hey All,
During our meeting today we discussed getting the keystone middleware
configuration for the services properly migrated to use the
keystone::resource::authtoken resource. I've created a bug[0] to track the
effort. If you wish to assist with this effort, please update the bug with
your nam
+1
On Thu, Jul 28, 2016 at 9:16 AM, Emilien Macchi wrote:
> You might not know who Sofer is but he's actually "chem" on IRC.
> He's the guy who will find the root cause of insane bugs, in OpenStack
> in general but also in Puppet OpenStack modules.
> Sofer has been working on Puppet OpenStack mod
On Wed, Aug 24, 2016 at 9:45 AM, Andy Smith wrote:
> Hi,
>
> We have a puppet module for the qpid-dispatch-router. The
> oslo.messaging AMQP 1.0 driver support for the router
> feature is part of the newton oslo.messaging release (5.9.0).
>
> This module is presently in a user repository and we w
Ahoy Fuel Cores,
I would like to propose Denis Egorenko for fuel-library core. Denis is
always providing great reviews[0] and continues to help keep Fuel moving
forward. He's the #3 reviewer and committer of the last 90 days[1] and 180
days[2].
Please vote with a +1/-1. Voting will close on Aug
On Thu, Sep 1, 2016 at 12:51 PM, Guillaume Espanel
wrote:
> Hi!
>
> At the moment, I don't think theres a Puppet module for
> the Cloudkitty rating service. I'd like to start the development
> of this project.
>
> What are you thoughts on the matter?
>
Sounds good. We've put together some documen
+1
On Wed, Sep 7, 2016 at 5:07 PM, Maksim Malchuk wrote:
> Hello,
>
> I would like to nominate Stanislaw Bogatkin to fuel-library core due to his
> significant contribution to the project [1] and [2]. He is one of the top
> reviewers and contributors in the project.
>
> [1]
> http://stackalytics.
v3 actions and
focus on developers ability to reproduce CI outside of the upstream.
Thanks,
Alex Schultz
irc: mwhahaha
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-re
On Thu, Feb 1, 2018 at 11:55 AM, James E. Blair wrote:
> Zane Bitter writes:
>
>> Yeah, it's definitely nice to have that flexibility. e.g. here is a
>> patch that wouldn't merge for 3 months because the thing it was
>> dependent on also got proposed as a backport:
>>
>> https://review.openstack.
On Tue, Oct 10, 2017 at 2:24 PM, Emilien Macchi wrote:
> On Fri, Oct 6, 2017 at 5:09 AM, Jiří Stránský wrote:
>> On 5.10.2017 22:40, Alex Schultz wrote:
>>>
>>> Hey folks,
>>>
>>> So I wandered across the policy spec[0] for how we should be handling
On Thu, Feb 8, 2018 at 2:29 PM, Matthew Thode wrote:
> As the title states, cycle trailing projects will need to change their
> requirements update behavior until they create stable/queens branches.
>
> When requirements unfreezes we will be doing rocky work, meaning that
> requirements updates to
Hey everyone,
So we currently have 63 blueprints for currently targeted for
Rocky[0]. Please make sure that any blueprints you are interested in
delivering have an assignee set and have been approved. I would like
to have the ones we plan on delivering for Rocky to be updated by
April 3, 2018.
Hey everyone,
In today's IRC meeting, I brought up[0] that we've been having an
increase in the number of open bugs of the last few weeks. We're
currently at about 635 open bugs. It would be beneficial for everyone
to take a look at the bugs that they are currently assigned to and
ensure they are
On Mon, Mar 26, 2018 at 2:33 PM, Doug Hellmann wrote:
> Excerpts from zuul's message of 2018-03-26 18:11:49 +:
>> Build failed.
>>
>> - publish-openstack-releasenotes
>> http://logs.openstack.org/94/94bb28ae46bd263314c9d846069ca913d225e625/tag/publish-openstack-releasenotes/9440894/
>> : POS
On Tue, Mar 13, 2018 at 7:58 AM, Alex Schultz wrote:
> Hey everyone,
>
> So we currently have 63 blueprints for currently targeted for
> Rocky[0]. Please make sure that any blueprints you are interested in
> delivering have an assignee set and have been approved. I would like
>
On Thu, Mar 29, 2018 at 11:32 AM, David Moreau Simard
wrote:
> Nice!
>
> I don't have a strong opinion
> about this but what I might recommend would be to chat with the
> openshift-ansible [1] and the kolla-ansible [2] folks.
>
> I'm happy to do the introductions if necessary !
>
> Their models, r
On Thu, Apr 5, 2018 at 12:55 PM, Wesley Hayutin wrote:
> FYI...
>
> This is news to me so thanks to Emilien for pointing it out [1].
> There are official tags for tripleo launchpad bugs. Personally, I like what
> I've seen recently with some extra tags as they could be helpful in finding
> the hi
Hey everyone,
We released Rocky Milestone 1 this week[0]. I have gone through and
updated the blueprints that were still targeted to rocky-1 to move
them to rocky-2. Please take some time to review the outstanding
blueprints to make sure that we still still be able to deliver them
during the Roc
+1
On Mon, Apr 23, 2018 at 5:55 AM, James Slagle wrote:
> On Thu, Apr 19, 2018 at 1:01 PM, Emilien Macchi wrote:
>> Greetings,
>>
>> As you probably know mcornea on IRC, Marius Cornea has been contributing on
>> TripleO for a while, specially on the upgrade bits.
>> Part of the quality team, he'
+1
On Fri, Apr 27, 2018 at 11:41 AM, Emilien Macchi wrote:
> +1, thanks Tobias for your contributions!
>
> On Fri, Apr 27, 2018 at 8:21 AM, Iury Gregory wrote:
>>
>> +1
>>
>> On Fri, Apr 27, 2018, 12:15 Mohammed Naser wrote:
>>>
>>> Hi everyone,
>>>
>>> I'm proposing that we add Tobias Urdin to
On Mon, Apr 30, 2018 at 9:47 AM, Jimmy McArthur wrote:
> Project Updates are in their own track:
> https://www.openstack.org/summit/vancouver-2018/summit-schedule#track=223
>
TripleO is still missing?
Thanks,
-Alex
> As are SIG, BoF and Working Groups:
> https://www.openstack.org/summit/vancouv
On Mon, Apr 30, 2018 at 3:16 PM, Ben Nemec wrote:
> Resending from an address that is subscribed to the list. Apologies to
> those of you who get this twice.
>
> On 04/30/2018 10:06 AM, Doug Hellmann wrote:
>>
>> It would be useful to have more input from PTLs on this issue, so I'm
>> CCing all o
On Wed, May 2, 2018 at 10:23 AM, Shyam Biradar
wrote:
> Hi,
>
> I am working on TrilioVault deployment integration with TripleO.
> This integration will contain changes to TripleO heat templates repo and
> tripleO puppet module as shown in attached document.
>
> We are targeting this integration f
On Fri, Apr 27, 2018 at 9:49 AM, Ade Lee wrote:
> Hi,
>
> Recently I starting looking at how we implement password changes in an
> existing deployment, and found that there were issues. This made me
> wonder whether we needed a test job to confirm that password changes
> (and other config changes
On Thu, Apr 26, 2018 at 6:08 AM, Waleed Musa wrote:
> Hi guys,
>
>
> I'm wondering, what is the plan of having these environments/*.yaml and
> enviroments/services-baremetal/*.yaml.
>
> It seems that it's deprecated files, Please advice here.
>
The services-baremetal were to allow for an end use
On Thu, May 3, 2018 at 8:29 AM, John Fulton wrote:
> We hit a bug [1] in CI job container-to-container-upgrades because a
> workflow that was needed only for Pike and Queens was removed [2] as
> clean up for the migration to external_deploy_tasks.
>
> As we need to support an n undercloud deployin
We haven't used tripleo-incubator in some time and it is no longer
maintained. We are planning on officially retiring it ASAP[0]. We
had previously said we would do it for the pike py35 goals[1] but we
never got around to removing it. Efforts have begun to officially
retire it. Please let us kn
Welcome to the twentieth edition of a weekly update in TripleO world!
The goal is to provide a short reading (less than 5 minutes) to learn
what's new this week.
Any contributions and feedback are welcome.
Link to the previous version:
http://lists.openstack.org/pipermail/openstack-dev/2018-May/130
Hello tripleo folks,
So we've been experimenting with migrating some squads over to
storyboard[0] but this seems to be causing more issues than perhaps
it's worth. Since the upstream community would like to standardize on
Storyboard at some point, I would propose that we do a cut over of all
the
On Wed, May 9, 2018 at 2:20 PM, Wesley Hayutin wrote:
>
>
> On Wed, May 9, 2018 at 3:25 PM Alex Schultz wrote:
>>
>> Hello tripleo folks,
>>
>> So we've been experimenting with migrating some squads over to
>> storyboard[0] but this seems to be ca
On Mon, May 14, 2018 at 10:15 AM, Bogdan Dobrelya wrote:
> An update for your review please folks
>
>> Bogdan Dobrelya writes:
>>
>>> Hello.
>>> As Zuul documentation [0] explains, the names "check", "gate", and
>>> "post" may be altered for more advanced pipelines. Is it doable to
>>> introduce
some time to review this and raise any
concerns/issues now.
Thanks,
-Alex
[0] https://docs.openstack.org/infra/manual/developers.html#development-workflow
On Wed, May 9, 2018 at 1:24 PM, Alex Schultz wrote:
> Hello tripleo folks,
>
> So we've been experimenting with migrating
On Wed, May 16, 2018 at 1:04 PM, Doug Hellmann wrote:
> Excerpts from Wesley Hayutin's message of 2018-05-16 12:51:25 -0600:
>> On Wed, May 16, 2018 at 2:41 PM Doug Hellmann wrote:
>>
>> > Excerpts from Petr Kovar's message of 2018-05-16 17:39:14 +0200:
>> > > Hi all,
>> > >
>> > > In the past fe
Since the summit is coming up, there will likely be very low
attendance. We'll carry any open items until the following week.
Thanks,
-Alex
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
On Wed, May 23, 2018 at 8:30 AM, Sagi Shnaidman wrote:
> Hi, Sergii
>
> thanks for the question. It's not first time that this topic is raised and
> from first view it could seem that branching would help to that sort of
> issues.
>
> Although it's not the case. Tripleo-quickstart(-extras) is part
org/cgit/openstack/ansible-role-container-registry/
[1] http://git.openstack.org/cgit/openstack/ansible-role-redhat-subscription/
[2] http://git.openstack.org/cgit/openstack/ansible-role-tripleo-keystone/
[3] http://git.openstack.org/cgit/openstack/puppet-openstacklib/
[4] https://review.openst
On Tue, May 29, 2018 at 9:31 AM, Doug Hellmann wrote:
> Excerpts from zuul's message of 2018-05-29 14:28:57 +:
>> Build failed.
>>
>> - release-openstack-python
>> http://logs.openstack.org/26/26956a27b95550e2162243da79d62bb1b19d50d7/release/release-openstack-python/2bd7f7d/
>> : POST_FAILUR
On Wed, May 30, 2018 at 3:18 PM, Remo Mattei wrote:
> Hello all,
> I have talked to several people about this and I would love to get this
> finalized once and for all. I have checked the OpenStack puppet modules
> which are mostly developed by the Red Hat team, as of right now, TripleO is
> usin
Hey folks,
So I'm in the process of evaluating options for implementing the
capture-environment-status-and-logs[0] blueprint. At the moment my
current plan is to implement a mistral workflow to execute the
sosreport to bundle the status and logs up on the requested nodes.
I'm leveraging a similar
On Fri, Dec 2, 2016 at 7:29 AM, Oliver Walsh wrote:
> Hi Yolanda,
>
> I've the same requirements for a real-time compute role.
>
> I'm current using #4. Puppet sets the kernel cmdline in
> /etc/defaults/grub, then touches a file that triggers a reboot in an
> os-refresh-config post-configure scrip
Hey everyone,
We're going to be running a small midcycle/sprint on January 11-12,
2017 in #puppet-openstack on freenode. We will be reviewing the work
items for Ocata and doing some bug triage. Feel free to add additional
topics to the etherpad[0].
Thanks,
-Alex
[0] https://etherpad.openstack.o
Hey,
Given that the next few meetings will be right after some holidays,
we're going to go ahead and cancel the meetings on Dec 27 and Jan 3.
Our next meeting will be on Jan 10. See you then.
Thanks,
-Alex
__
OpenStack Deve
On Thu, Jan 5, 2017 at 8:58 AM, Sam Yaple wrote:
> Involving kolla-ansible and kolla-kubernetes in a decision about
> kolla-salt (or kolla-puppet, or kolla-chef) is silly since the projects are
> unrelated. That would be like involving glance when cinder has a new
> service because they both use
On Thu, Jan 5, 2017 at 10:25 AM, Michał Jastrzębski wrote:
> Ad kolla-ansible core team +2ing new deliverable,I agree with Sam,
> there is no reason in my mind for kolla-ansible/k8s core team to vote
> on accepting new deliverable. I think this should be lightweight and
> easy, we should allow exp
On Tue, Dec 6, 2016 at 12:32 PM, Alex Schultz wrote:
> Hey everyone,
>
> We're going to be running a small midcycle/sprint on January 11-12,
> 2017 in #puppet-openstack on freenode. We will be reviewing the work
> items for Ocata and doing some bug triage. Feel free to add ad
Ahoy folks,
So we've been running into issues with the addition of the cell v2
setup as part of the requirements for different parts of nova. It was
recommended that we move the conversation to the ML to get a wider
audience. Basically, cell v2 has been working it's way into a
required thing for
On Fri, Jan 13, 2017 at 1:05 PM, Matt Riedemann
wrote:
> On 1/13/2017 11:43 AM, Alex Schultz wrote:
>>
>> Ahoy folks,
>>
>> So we've been running into issues with the addition of the cell v2
>> setup as part of the requirements for different parts of nova.
On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann
wrote:
> Sylvain and I were talking about how he's going to work placement
> microversion requests into his filter scheduler patch [1]. He needs to make
> requests to the placement API with microversion 1.4 [2] or later for
> resource provider filter
On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes wrote:
> On 01/19/2017 11:25 AM, Alex Schultz wrote:
>>
>> On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann
>> wrote:
>>>
>>> Sylvain and I were talking about how he's going to work placement
>>> mic
On Thu, Jan 19, 2017 at 11:45 AM, Jay Pipes wrote:
> On 01/19/2017 01:18 PM, Alex Schultz wrote:
>>
>> On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes wrote:
>>>
>>> On 01/19/2017 11:25 AM, Alex Schultz wrote:
>>>>
>>>>
>>
Hey Puppet Cores,
I would like to nominate Mykyta Karpin as a Core reviewer for the
Puppet OpenStack modules. He has been providing quality patches and
reviews for some time now and I believe he would be a good addition to
the team. His stats for the last 90 days can be viewed here[0]
Please re
Hey Puppet Cores,
I would like to nominate Zhong Shengping as a Core reviewer for the
Puppet OpenStack modules. He is an excellent contributor to our
modules over the last several cycles. His stats for the last 90 days
can be viewed here[0].
Please response with your +1 or any objections. If the
configurations have already been removed.
I look forward to working with all of you. As always, I'm open to any
suggestions or ideas for additional places to improve our processes and modules.
Thanks,
Alex Schultz
irc: mwhahaha
https://review.openstack.org/4
Just FYI,
We switched the Ubuntu scenario jobs to non-voting this week due to
the large amount of breakage caused by the ocata-proposed update to m2
based packages. The Ubuntu beaker jobs are still voting on the
modules themselves.
Here's where we're keeping track of issues:
https://etherpad.op
On Tue, Jan 24, 2017 at 6:43 AM, Corey Bryant
wrote:
>
> On Fri, Jan 20, 2017 at 6:34 PM, Alex Schultz wrote:
>>
>> Just FYI,
>>
>> We switched the Ubuntu scenario jobs to non-voting this week due to
>> the large amount of breakage caused by the ocata-pro
On Thu, Jan 19, 2017 at 3:25 PM, Alex Schultz wrote:
> Hey Puppet Cores,
>
> I would like to nominate Mykyta Karpin as a Core reviewer for the
> Puppet OpenStack modules. He has been providing quality patches and
> reviews for some time now and I believe he would be a good additio
On Fri, Jan 20, 2017 at 10:19 AM, Alex Schultz wrote:
> Hey Puppet Cores,
>
> I would like to nominate Zhong Shengping as a Core reviewer for the
> Puppet OpenStack modules. He is an excellent contributor to our
> modules over the last several cycles. His stats for the last 9
Hi all,
Since the agenda[0] for the meeting is empty, I'm canceling the
meeting. If you wish to talk about something next week, please add it
to the agenda[1].
Thanks,
-Alex
[0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170131
[1] https://etherpad.openstack.org/p/puppet
Hey all,
The agenda etherpad[0] was empty so we're skipping today's meeting.
The next meeting will be on Feb 14th, 2017. If you have something to
discuss, please add it to the agenda etherpad[1].
Thanks,
-Alex
[0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170207
[1] htt
Just a reminder but we will be having our meeting tomorrow Feb 14th at
1500 UTC in #openstack-meeting-4 unless the agenda[0] remains empty.
So if you have something you wish to talk about it, please add it to
the agenda. As always the the previous meeting logs and agendas are
reviewable here[1].
Hey folks,
The final mascot is available for viewing here:
https://www.dropbox.com/sh/oax7i1xvca3edxc/AAAtfQSyx0rJijKBoqoZmp-va?dl=0
Thanks,
-Alex
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On Wed, Feb 15, 2017 at 9:02 AM, Samuel Cassiba wrote:
>
>> On Feb 15, 2017, at 02:07, Thierry Carrez wrote:
>>
>> Samuel Cassiba wrote:
>>> [...]
>>> *TL;DR* if you don't want to keep going -
>>> OpenStack-Chef is not in a good place and is not sustainable.
>>> [...]
>>
>> Thanks for sharing, Sa
On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe wrote:
> On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote:
>
>> When we signed off on the Big Tent changes we said competition
>> between projects was desirable, and that deployers and contributors
>> would make choices based on the work being done in th
guide/releases.html#releases-summary
On Fri, Nov 11, 2016 at 2:11 PM, Alex Schultz wrote:
> On Thu, Nov 3, 2016 at 11:31 PM, Sam Morrison wrote:
>>
>> On 4 Nov. 2016, at 1:33 pm, Emilien Macchi wrote:
>>
>> On Thu, Nov 3, 2016 at 9:10 PM, Sam Morrison wrote:
>>
>
Due to the PTG this week, we are skipping the meeting tomorrow. The
next meeting will be on Feb 28th. The agenda[0] is currently empty. If
you have something you wish to talking about, please add it to the
list.
Thanks,
-Alex
[0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20
+1
On Wed, Jun 13, 2018 at 9:50 AM, Emilien Macchi wrote:
> Alan Bishop has been highly involved in the Storage backends integration in
> TripleO and Puppet modules, always here to update with new features, fix
> (nasty and untestable third-party backends) bugs and manage all the
> backports for
with waiting until early Stein to
continue. Let's focus on the Rocky work and push this to early Stein
instead. I'll talk about this in the next IRC meeting if anyone wishes
to discuss further.
Thanks,
-Alex
> Thanks,
> Michele
>
>> Thanks,
>>
>> On Tue, May 15, 2018 at
On Mon, Jun 4, 2018 at 6:26 PM, Emilien Macchi wrote:
> TL;DR: we made nice progress and you can checkout this demo:
> https://asciinema.org/a/185533
>
> We started the discussion back in Dublin during the last PTG. The idea of
> Standalone (aka All-In-One, but can be mistaken with all-in-one over
On Mon, Jun 18, 2018 at 9:13 AM, Lars Kellogg-Stedman wrote:
> Hey folks,
>
> I'm trying to patch puppet-keystone to support multi-valued
> configuration options (like trusted_dashboard). I have a patch that
> works, mostly, but I've run into a frustrating problem (frustrating
> because it would
On Mon, Jun 18, 2018 at 4:08 PM, Tobias Urdin wrote:
> Hello CloudKitty team,
>
>
> I'm having an issue with this review not going through and being stuck after
> staring at it for a while now [1].
>
> Is there any configuration[2] issue that are causing the error[3]? Or is the
> package broken?
>
On Wed, Jun 13, 2018 at 9:50 AM, Emilien Macchi wrote:
> Alan Bishop has been highly involved in the Storage backends integration in
> TripleO and Puppet modules, always here to update with new features, fix
> (nasty and untestable third-party backends) bugs and manage all the
> backports for stab
On Tue, Jun 19, 2018 at 9:17 AM, Jiří Stránský wrote:
> On 19.6.2018 16:29, Lars Kellogg-Stedman wrote:
>>
>> On Tue, Jun 19, 2018 at 02:18:38PM +0100, Steven Hardy wrote:
>>>
>>> Is this the same issue Carlos is trying to fix via
>>> https://review.openstack.org/#/c/494517/ ?
>>
>>
>> That solves
On Tue, Jun 19, 2018 at 1:45 PM, Wesley Hayutin wrote:
> Check and gate jobs look clear.
> More details on a bit.
>
So for a recap of the last 24 hours or so...
Mistral auth problems - https://bugs.launchpad.net/tripleo/+bug/1777541
- caused by https://review.openstack.org/#/c/574878/
- fixed
On Tue, Jun 26, 2018 at 8:05 AM, Paul Bourke wrote:
> Hi all,
>
> At the weekly meeting a week or two ago, we mentioned removing some old /
> unused images from Kolla in the interest of keeping the gate run times down,
> as well as general code hygiene.
>
> The images I've determined that are eith
Hello everyone,
As milestone 3 is quickly approaching, it's time to review the open
blueprints[0] and their status. It appears that we have made good
progress on implementing significant functionality this cycle but we
still have some open items. Below is the list of blueprints that are
still op
201 - 300 of 370 matches
Mail list logo
