Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-17 Thread Tony Breeds
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-15 Thread Alex Schultz
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-15 Thread Adriano Petrich
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-14 Thread Tony Breeds
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.

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-14 Thread Alex Schultz
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-14 Thread Mark Hamzy
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-14 Thread Alex Schultz
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-13 Thread Mark Hamzy
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-13 Thread Alex Schultz
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-13 Thread Mark Hamzy
> 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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-13 Thread Alex Schultz
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 >>

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-13 Thread Alex Schultz
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-13 Thread Sven Anderson
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-12 Thread Tony Breeds
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-12 Thread Alex Schultz
questions) >> <openstack-dev@lists.openstack.org> >> Subject: Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky >> >> On Mon, Dec 11, 2017 at 1:20 PM, Brad P. Crochet <b...@redhat.com> >> wrote: >> > >> > >> > On

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-12 Thread Brad P. Crochet
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-12 Thread Moshe Levi
ject: Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky > > On Mon, Dec 11, 2017 at 1:20 PM, Brad P. Crochet <b...@redhat.com> > wrote: > > > > > > On Fri, Dec 8, 2017 at 6:35 PM Alex Schultz <aschu...@redhat.com> wrote: > >> > >

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-11 Thread Alex Schultz
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-11 Thread Brad P. Crochet
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

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-11 Thread Moshe Levi
> -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) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [tripleo] Bluep

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-11 Thread Alex Schultz
turday, December 9, 2017 1:34 AM >> To: OpenStack Development Mailing List (not for usage questions) >> <openstack-dev@lists.openstack.org> >> Subject: [openstack-dev] [tripleo] Blueprints moved out to Rocky >> >> Hey folks, >> >> So I went

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-08 Thread Moshe Levi
chultz [mailto:aschu...@redhat.com] > Sent: Saturday, December 9, 2017 1:34 AM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [tripleo] Blueprints moved out to Rocky > > Hey folks, &

[openstack-dev] [tripleo] Blueprints moved out to Rocky

2017-12-08 Thread Alex Schultz
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