On Fri, Dec 15, 2017 at 11:39:16AM -0700, Alex Schultz wrote:
> Perhaps we can start reviewing the items and those with little to no
> impact we can merge for the remainder of the cycle. I know
> realistically everything has an impact so it'll be >0, but lets try
> and keep it as close to 0 as pos
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 consume, it shouldn't be
I have
https://blueprints.launchpad.net/mistral/+spec/mistral-workflow-executions-yaql-function
almost all implemented and I would like submit an FFE for it
Cheers,
Adriano
On Fri, Dec 15, 2017 at 12:01 AM, Tony Breeds
wrote:
> On Wed, Dec 13, 2017 at 03:01:41PM -0700, Alex Schultz 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 consume, it shouldn't be impacting to general testing or
> increase regressions. My
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
>> have an impact on the ex
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
> have an impact on the existing functionality this should have been
> merged earlier
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
>> > specific
>> > images. For example,
>> >
>> > (underc
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
> > specific
> > images. For example,
> >
> > (undercloud) [stack@oscloud5 ~]$ openstack image list
> > +
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
> 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
> folks will consume, it shouldn't be impacting to general te
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 believe you're close to implementing
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 not in a
>> mergable state.
>>
>> P
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 believe you're close to implementing the feature in the next week
> or two, let me know and we can mov
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 not in a
> mergable state.
>
> Please take some time to review the list of blueprints curren
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 Mon, Dec 11, 2017 at 5:20 PM Alex Schultz wrote:
> 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 o
is and fix the sample-env-generator late?
> -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)
>
> Subject: Re: [openstack-dev] [tripleo] B
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 bunch of patches not in a
>> mergable state.
>>
>>
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 bunch of patches not in a
> mergable state.
>
> Please take some time to review the list of blueprints currently
> assoc
> -Original Message-
> From: Alex Schultz [mailto:aschu...@redhat.com]
> Sent: Monday, December 11, 2017 8:31 PM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky
>
> On
: Saturday, December 9, 2017 1:34 AM
>> To: OpenStack Development Mailing List (not for usage questions)
>>
>> Subject: [openstack-dev] [tripleo] Blueprints moved out to Rocky
>>
>> Hey folks,
>>
>> So I went through the list of blueprints and moved some th
lex Schultz [mailto:aschu...@redhat.com]
> Sent: Saturday, December 9, 2017 1:34 AM
> To: OpenStack Development Mailing List (not for usage questions)
>
> Subject: [openstack-dev] [tripleo] Blueprints moved out to Rocky
>
> Hey folks,
>
> So I went through the list of
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
23 matches
Mail list logo
