> Its been discussed at several summits. We have settled on a general solution
> using Zaqar,
> but no work has been done that I know of. I was just pointing out that
> similar blueprints/specs
> exist and you may want to look through those to get some ideas about writing
> your own and/or
> b
Its been discussed at several summits. We have settled on a general solution
using Zaqar, but no work has been done that I know of. I was just pointing out
that similar blueprints/specs exist and you may want to look through those to
get some ideas about writing your own and/or basing your propo
Rundal-san,
> There should already be blueprints in launchpad for very similar
> functionality.
> For example: https://blueprints.launchpad.net/heat/+spec/lifecycle-callbacks.
> While that specifies Heat sending notifications to the outside world,
> there has been discussion around debugging that
> On Fri, Dec 19, 2014 at 05:02:04PM +0900, Yasunori Goto wrote:
> >
> > Hello,
> >
> > This is the first mail at Openstack community,
>
> Welcome! :)
>
> > and I have a small question about how to write blueprint for Heat.
> >
> > Currently our team would like to propose 2 interfaces
> > for
There should already be blueprints in launchpad for very similar functionality.
For example: https://blueprints.launchpad.net/heat/+spec/lifecycle-callbacks.
While that specifies Heat sending notifications to the outside world, there has
been discussion around debugging that would allow the rece
On Fri, Dec 19, 2014 at 05:02:04PM +0900, Yasunori Goto wrote:
>
> Hello,
>
> This is the first mail at Openstack community,
Welcome! :)
> and I have a small question about how to write blueprint for Heat.
>
> Currently our team would like to propose 2 interfaces
> for users operation in HOT.
Hi, Pavlo-san
> Hi Yasunori,
>
> that's the point of using code review for specs - you make your the best
> bet / effort, and we then as a community decide if it should be changed ;)
>
> So feel free submitting it with e.g. K-3 target, we'll figure out the
> correct thing during review.
Ok, I
Hi Yasunori,
that's the point of using code review for specs - you make your the best
bet / effort, and we then as a community decide if it should be changed ;)
So feel free submitting it with e.g. K-3 target, we'll figure out the
correct thing during review.
Best regards,
Pavlo Shchelokovskyy
Hi, Thomas-san,
Thank you for your response.
> you can submit a blueprint spec as a gerrit review to the heat-specs
> repository [1].
> I would suggest to have a look at some existing specs that already got
> accepted to have an example for the format, important sections etc.
>
> All kilo relate
Hi Yasunori,
you can submit a blueprint spec as a gerrit review to the heat-specs
repository [1].
I would suggest to have a look at some existing specs that already got
accepted to have an example for the format, important sections etc.
All kilo related specs are in a kilo sub-directory in the re
10 matches
Mail list logo
