FYI, I have refined my pictures at
https://docs.google.com/drawings/d/1Y_yyIpql5_cdC8116XrBHzn6GfP_g0NHTTG_W4o0R9U
and
https://docs.google.com/drawings/d/1TCfNwzH_NBnx3bNz-GQQ1bRVgBpJdstpu0lH_TONw6g
to hopefully make it clearer that I agree with the sentiment that holistic
infrastructure
Excerpts from Georgy Okrokvertskhov's message of 2013-09-30 11:44:26 -0700:
Hi,
I am working on the OpenStack project Murano which actually had to solve
the same problem with software level orchestration. Right now Murano has a
DSL language which allows you to define a workflow for a complex
On 1 October 2013 19:31, Clint Byrum cl...@fewbar.com wrote:
TripleO meets at 2000 UTC every Tuesday.
1900UTC.
:)
-Rob
--
Robert Collins rbtcoll...@hp.com
Distinguished Technologist
HP Converged Cloud
___
OpenStack-dev mailing list
Hi Mike and Zane,
Le 27/09/2013 15:58, Mike Spreitzer a écrit :
Zane Bitter zbit...@redhat.com wrote on 09/27/2013 08:24:49 AM:
Your diagrams clearly show scheduling happening in a separate stage to
(infrastructure) orchestration, which is to say that at the point where
resources are
Clint Byrum cl...@fewbar.com wrote on 01.10.2013 08:31:44 - Excerpt:
From: Clint Byrum cl...@fewbar.com
To: openstack-dev openstack-dev@lists.openstack.org,
Date: 01.10.2013 08:33
Subject: Re: [openstack-dev] [heat] [scheduler] Bringing things
together for Icehouse (now featuring software
Hi,
I am working on the OpenStack project Murano which actually had to solve
the same problem with software level orchestration. Right now Murano has a
DSL language which allows you to define a workflow for a complex service
deployment.
Murano uses Heat for infrastructure managements and actually
On 25/09/13 07:03, Mike Spreitzer wrote:
Zane wrote:
To take the first example, wouldn't your holistic scheduler
effectively have
to reserve a compute instance and some directly attached block
storage prior
to actually creating them? Have you considered Climate rather than
Heat as
an
Zane Bitter zbit...@redhat.com wrote on 09/27/2013 08:24:49 AM:
Your diagrams clearly show scheduling happening in a separate stage to
(infrastructure) orchestration, which is to say that at the point where
resources are scheduled, their actual creation is in the *future*.
I am not a
Sorry, I was a bit too hasty in writing the last part of my last message;
I forgot to qualify software orchestration to indicate I am speaking
only of its preparatory phase. I should have written:
Zane Bitter zbit...@redhat.com wrote on 09/27/2013 08:24:49 AM:
...
If I understood your
On Wed, Sep 25, 2013 at 11:04:54PM +0200, Thomas Spatzier wrote:
Excerpt from Clint's mail on 25.09.2013 22:23:07:
I think we already have some summit suggestions for discussing HOT,
it would be good to come prepared with some visions for the future
of HOT so that we can hash these
Excerpts from Mike Spreitzer's message of 2013-09-24 22:03:21 -0700:
Let me elaborate a little on my thoughts about software orchestration, and
respond to the recent mails from Zane and Debo. I have expanded my
picture at
Clint Byrum cl...@fewbar.com wrote on 25.09.2013 08:46:57:
From: Clint Byrum cl...@fewbar.com
To: openstack-dev openstack-dev@lists.openstack.org,
Date: 25.09.2013 08:48
Subject: Re: [openstack-dev] [heat] [scheduler] Bringing things
together for Icehouse (now featuring software orchestration
Clint wrote:
There is a third stealth-objective that CFN has caused to linger in
Heat. That is packaging cloud applications. By allowing the 100%
concrete CFN template to stand alone, users can ship the template.
IMO this marrying of software assembly, config, and orchestration is a
] Bringing things
together for Icehouse (now featuring software orchestration)
Excerpts from Mike Spreitzer's message of 2013-09-24 22:03:21 -0700:
Let me elaborate a little on my thoughts about software orchestration,
and
respond to the recent mails from Zane and Debo. I have expanded my
Excerpt from Clint's mail on 25.09.2013 22:23:07:
I think we already have some summit suggestions for discussing HOT,
it would be good to come prepared with some visions for the future
of HOT so that we can hash these things out, so I'd like to see this
discussion continue.
Absolutely! Can
Let me elaborate a little on my thoughts about software orchestration, and
respond to the recent mails from Zane and Debo. I have expanded my
picture at
https://docs.google.com/drawings/d/1Y_yyIpql5_cdC8116XrBHzn6GfP_g0NHTTG_W4o0R9U
and added a companion picture at
16 matches
Mail list logo
