On 18.05.17 15:02, Mehdi Abaakouk wrote:
On Thu, May 18, 2017 at 11:26:41AM +0200, Lance Haig wrote:
This is not only an Aodh/Ceilometer alarm issue. I can confirm that
whatever the resource prefix, this works well.
But an alarm description also contains a query an external API to
retrieve
On Thu, May 18, 2017 at 11:26:41AM +0200, Lance Haig wrote:
This is not only an Aodh/Ceilometer alarm issue. I can confirm that
whatever the resource prefix, this works well.
But an alarm description also contains a query an external API to
retrieve statistics. Aodh alarms are currently able t
On 18.05.17 08:00, Mehdi Abaakouk wrote:
Hi,
On Mon, May 15, 2017 at 01:01:57PM -0400, Zane Bitter wrote:
On 15/05/17 12:10, Steven Hardy wrote:
On Mon, May 15, 2017 at 04:46:28PM +0200, Lance Haig wrote:
Hi Steve,
I am happy to assist in any way to be honest.
It was great to meet you in
On 17.05.17 22:18, Zane Bitter wrote:
On 16/05/17 10:32, Lance Haig wrote:
What if instead of a directory per release, we just had a 'deprecated'
directory where we move stuff that is going away (e.g. anything
relying on OS::Glance::Image), and then deleted them when it
disappeared from any su
Hi,
On Mon, May 15, 2017 at 01:01:57PM -0400, Zane Bitter wrote:
On 15/05/17 12:10, Steven Hardy wrote:
On Mon, May 15, 2017 at 04:46:28PM +0200, Lance Haig wrote:
Hi Steve,
I am happy to assist in any way to be honest.
It was great to meet you in Boston, and thanks very much for
volunteer
On 16/05/17 10:32, Lance Haig wrote:
What if instead of a directory per release, we just had a 'deprecated'
directory where we move stuff that is going away (e.g. anything
relying on OS::Glance::Image), and then deleted them when it
disappeared from any supported release (e.g. LBaaSv1 must be clo
On 15.05.17 19:01, Zane Bitter wrote:
On 15/05/17 12:10, Steven Hardy wrote:
On Mon, May 15, 2017 at 04:46:28PM +0200, Lance Haig wrote:
Hi Steve,
I am happy to assist in any way to be honest.
It was great to meet you in Boston, and thanks very much for
volunteering to help out.
BTW one i
On 15.05.17 18:10, Steven Hardy wrote:
On Mon, May 15, 2017 at 04:46:28PM +0200, Lance Haig wrote:
Hi Steve,
I am happy to assist in any way to be honest.
The backwards compatibility is not always correct as I have seen when
developing our library of templates on Liberty and then trying to dep
On 15/05/17 12:10, Steven Hardy wrote:
On Mon, May 15, 2017 at 04:46:28PM +0200, Lance Haig wrote:
Hi Steve,
I am happy to assist in any way to be honest.
It was great to meet you in Boston, and thanks very much for
volunteering to help out.
BTW one issue I'm aware of is that the autoscali
Hi Lico and team,
Let me show up in this thread again, because I think now is really good
timing to introduce myself.
My name is Kazunori Shinohara (Kaz) working for NTT Communications as
software engineer.
I'm taking Heat as public cloud's orchestration services by adding own
resource plugins an
On Mon, May 15, 2017 at 04:46:28PM +0200, Lance Haig wrote:
> Hi Steve,
>
> I am happy to assist in any way to be honest.
>
> The backwards compatibility is not always correct as I have seen when
> developing our library of templates on Liberty and then trying to deploy it
> on Mitaka for example
Hi Steve,
I am happy to assist in any way to be honest.
The backwards compatibility is not always correct as I have seen when
developing our library of templates on Liberty and then trying to deploy
it on Mitaka for example.
As you guys mentioned in our discussions the Networking example I q
Hi Rico,
Great to meet you at the summit.
The version related templates I think would work as follows.
In each named directory we would have the same set of templates
e.g.
Single instance
Clustered instance
resource group
etc..
And so if you are on Pike you would go to the pike directory and
On Mon, May 15, 2017 at 03:21:30AM -0400, Lance Haig wrote:
>Good to know that there is interest.
Thanks for starting this effort - I agree it would be great to see the
example templates we provide improved and over time become better
references for heat features (as well as being more well te
Hi Lance and all others who shows interest
IMO, after some feedback from the summit. I think it will be greate to have
efforts on
- *bug/blueprint: We needs more people doing fix/review/spec. Since we
still on the way to make heat more handy as Orchestration tools*
- *template example*:
Good to know that there is interest.
I was thinking that we should perhaps create a directory for each openstack
version.
so we start say with a mitaka directory and then move the files there and
test them all so that they work with Liberty.
Then we can copy it over to Mitaka and do the same but
Hi Lance,
I like it too.
We should keep them updated according to the latest spec and actual use
cases.
Regards,
Kaz Shinohara
2017-05-13 13:00 GMT+09:00 Foss Geek :
> Hi Lance, I am also interested to assisting you on this.
>
> Thanks
> Mohan
> On 11-May-2017 2:25 am, "Lance Haig" wrote:
>
>
Hi Lance, I am also interested to assisting you on this.
Thanks
Mohan
On 11-May-2017 2:25 am, "Lance Haig" wrote:
> Hi,
>
> I would like to introduce myself to the heat team.
>
> My name is Lance Haig I currently work for Mirantis doing workload
> onboarding to openstack.
>
> Part of my job is a
I like it.
the heat template is very old ,need to update.
On Thu, May 11, 2017 at 4:54 AM, Lance Haig wrote:
> Hi,
>
> I would like to introduce myself to the heat team.
>
> My name is Lance Haig I currently work for Mirantis doing workload
> onboarding to openstack.
>
> Part of my job is assis
Hi,
I would like to introduce myself to the heat team.
My name is Lance Haig I currently work for Mirantis doing workload
onboarding to openstack.
Part of my job is assisting customers with using the new Openstack cloud
they have been given.
I recently gave a talk with a colleague Florin Stinga
20 matches
Mail list logo
