On Fri, 15 Jun 2018 06:17:34 +0900 Doug Hellmann
wrote
> Excerpts from Doug Hellmann's message of 2018-06-14 13:02:31 -0400:
> > Excerpts from Ghanshyam's message of 2018-06-14 16:54:33 +0900:
>
> > > > > > Could it be as simple as adding tempest-full-py3 with the
> > > >
Excerpts from Sean McGinnis's message of 2018-06-14 16:28:14 -0500:
> >
> > After giving everyone a week to volunteer as liaisons for project teams,
> > I have filled out the roster so that every team has 2 TC members
> > assigned. I used random.shuffle() and then went down the list and tried
> >
>
> After giving everyone a week to volunteer as liaisons for project teams,
> I have filled out the roster so that every team has 2 TC members
> assigned. I used random.shuffle() and then went down the list and tried
> to avoid assigning the same person twice while ensuring that everyone
> had
Excerpts from Doug Hellmann's message of 2018-06-14 13:02:31 -0400:
> Excerpts from Ghanshyam's message of 2018-06-14 16:54:33 +0900:
> > > > > Could it be as simple as adding tempest-full-py3 with the
> > > > > required-projects list updated to include the current repository? So
> > > > >
+1
The new time slot would definitely make it much easier for me to attend
than the current one.
- Douglas Mendizábal
On Thu, 2018-06-14 at 16:30 -0400, Ade Lee wrote:
> The new time slot has been pretty difficult for folks to attend.
> I'd like to propose a new time slot, which will hopefully
The new time slot has been pretty difficult for folks to attend.
I'd like to propose a new time slot, which will hopefully be more
amenable to everyone.
Tuesday 12:00 UTC
https://www.timeanddate.com/worldclock/fixedtime.html?hour=12=00
c=0
This works out to 8 am EST, around 1pm in Europe, and 8
Sphinx is being updated from 1.6.7 to 1.7.5. You may need to update
your docs/templates to work with it.
--
Matthew Thode (prometheanfire)
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not
Excerpts from Doug Hellmann's message of 2018-06-07 14:28:02 -0400:
> As we discussed in today's office hours, I have set up some space in the
> wiki for us to track which TC members are volunteering to act as liaison
> to the teams and other groups within the community to ensure they have
> the
Excerpts from Ghanshyam's message of 2018-06-14 16:54:33 +0900:
>
>
>
> On Thu, 14 Jun 2018 05:55:55 +0900 Doug Hellmann
> wrote
> > Excerpts from Doug Hellmann's message of 2018-06-13 12:19:18 -0400:
> > > Excerpts from Doug Hellmann's message of 2018-06-13 10:31:00 -0400:
> >
On Thu, Jun 14, 2018 at 08:10:56AM -0300, Erlon Cruz wrote:
> Hi Thomas,
>
> The reserved_percentage *is* taken in account for non thin provisoning
> backends. So you can use it to spare the space you need for backups. It is
> a per backend configuration.
>
> If you have already tried to used it
Greetings OpenStack community,
A small, intimate meeting today, as only cdent and edleafe were present. We
discussed the work being done [7] to migrate our bug/issue tracking from
Launchpad to StoryBoard [8]. The change to the infra docs will trigger the
setup of StoryBoard when it merges.
On Thu, Jun 14, 2018 at 11:13:22AM +0200, Thomas Goirand wrote:
> Hi,
>
> When using cinder-backup, it first makes a snapshot, then sends the
> backup wherever it's configured. The issue is, to perform a backup, one
> needs to make a snapshot of a volume, meaning that one needs the size of
> the
> While I have tried to review a few of the runway-slotted efforts, I
> have gotten burned out on a number of them. Other runway-slotted
> efforts, I simply don't care enough about or once I've seen some of
> the code, simply can't bring myself to review it (sorry, just being
> honest).
I have
On Wed, 13 Jun 2018 15:47:33 -0700, Melanie Witt wrote:
Hi everybody,
Just a heads up that we have an intermittent gate failure of the
nova-cells-v1 job happening right now [1] and a revert of the tempest
change related to it has been approved [2] and will be making its way
through the gate.
Welcome to the weekly countdown email.
Development Focus
-
Teams should be focused on implementing planned work for the cycle.
It is also a good time to review those plans and reprioritize anything if
needed based on the what progress has been made and what looks realistic to
It sounds like we merged a bunch last night thanks to the revert, so I went
ahead and restored/rechecked everything that was out of the gate. I've
checked and nothing was left over, but let me know in case I missed
something.
I'll keep updating this thread with the progress made to improve the
On 06/13/2018 05:33 PM, Matt Riedemann wrote:
On 6/13/2018 3:33 PM, melanie witt wrote:
We've been experimenting with a new process this cycle, Review Runways
[1] and we're about at the middle of the cycle now as we had the r-2
milestone last week June 7.
I wanted to start a thread and
On 06/13/2018 07:50 PM, Emilien Macchi wrote:
TL;DR: gate queue was 25h+, we put all patches from gate on standby, do
not restore/recheck until further announcement.
We recently enabled the containerized undercloud for multinode jobs and
we believe this was a bit premature as the container
I am trying to delete the Storage, StorageMgmt, Tenant, and Management
networks and trying to deploy using TripleO.
The following patch
https://hamzy.fedorapeople.org/0001-RedisVipPort-error-internal_api.patch
applied on top of /usr/share/openstack-tripleo-heat-templates from
Hi Thomas,
The reserved_percentage *is* taken in account for non thin provisoning
backends. So you can use it to spare the space you need for backups. It is
a per backend configuration.
If you have already tried to used it and that is not working, please let us
know what release you are using,
On 6/14/18 3:50 AM, Emilien Macchi wrote:
TL;DR: gate queue was 25h+, we put all patches from gate on standby, do
not restore/recheck until further announcement.
We recently enabled the containerized undercloud for multinode jobs and
we believe this was a bit premature as the container
+1
On 13.6.2018 17:50, 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 stable releases:
+1. Well deserved.
On Thu, Jun 14, 2018 at 11:08 AM, Bogdan Dobrelya wrote:
> On 6/13/18 6:50 PM, 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
Hi,
When using cinder-backup, it first makes a snapshot, then sends the
backup wherever it's configured. The issue is, to perform a backup, one
needs to make a snapshot of a volume, meaning that one needs the size of
the volume as empty space to be able to make the snapshot.
So, let's say I have
On 6/13/18 6:50 PM, 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 stable releases:
On Thu, 14 Jun 2018 05:55:55 +0900 Doug Hellmann
wrote
> Excerpts from Doug Hellmann's message of 2018-06-13 12:19:18 -0400:
> > Excerpts from Doug Hellmann's message of 2018-06-13 10:31:00 -0400:
> > > Excerpts from Ghanshyam's message of 2018-06-13 16:52:33 +0900:
> > > >
On Wed, Jun 13, 2018 at 5:50 PM, 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
27 matches
Mail list logo
