with the CI infrastructure).
--
IRC: radix
Christopher Armstrong
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
all the problems, while enabling
it for the unit tests so bugs won't be reintroduced in the future.
Interestingly it also didn't fail any of the tempest tests, I'm not sure
why.
--
IRC: radix
Christopher Armstrong
___
OpenStack-dev mailing list
OpenStack
of problems.
We will make sure to work with Liang Chen to avoid this happening
again.https://review.openstack.org/#/dashboard/7135
fwiw Thomas Hervé has posted a patch to revert the introduction of lazy
translation:
https://review.openstack.org/#/c/74454/
--
IRC: radix
Christopher Armstrong
it's being e.g. resized.
--
IRC: radix
http://twitter.com/radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
feature.
--
Christopher Armstrong
http://twitter.com/radix/
http://github.com/radix/
http://radix.twistedmatrix.com/
http://planet-if.com/
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
of different resource relationships).
--
IRC: radix
http://twitter.com/radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.
And this is a very useful feature for projects that want to have a single
codebase that runs on both python 2 and python 3, so it's worth taking
advantage of.
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
sense, for example).
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
naming the group for
each parameter.
Thanks very much for writing up these use cases!
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
On Tue, Nov 26, 2013 at 4:35 PM, Tim Schnell tim.schn...@rackspace.comwrote:
From: Christopher Armstrong chris.armstr...@rackspace.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: Tuesday, November 26, 2013 4:02 PM
On Thu, Nov 21, 2013 at 5:18 AM, Zane Bitter zbit...@redhat.com wrote:
On 20/11/13 23:49, Christopher Armstrong wrote:
On Wed, Nov 20, 2013 at 2:07 PM, Zane Bitter zbit...@redhat.com
mailto:zbit...@redhat.com wrote:
On 20/11/13 16:07, Christopher Armstrong wrote:
On Tue, Nov
On Thu, Nov 21, 2013 at 12:31 PM, Zane Bitter zbit...@redhat.com wrote:
On 21/11/13 18:44, Christopher Armstrong wrote:
2) It relies on a plugin being present for any type of thing you
might want to notify.
I don't understand this point. What do you mean by a plugin? I
On Tue, Nov 19, 2013 at 4:27 PM, Zane Bitter zbit...@redhat.com wrote:
On 19/11/13 19:14, Christopher Armstrong wrote:
[snip]
It'd be interesting to see some examples, I think. I'll provide some
examples of my proposals, with the following caveats:
Excellent idea, thanks :)
- I'm
On Wed, Nov 20, 2013 at 2:07 PM, Zane Bitter zbit...@redhat.com wrote:
On 20/11/13 16:07, Christopher Armstrong wrote:
On Tue, Nov 19, 2013 at 4:27 PM, Zane Bitter zbit...@redhat.com
mailto:zbit...@redhat.com wrote:
On 19/11/13 19:14, Christopher Armstrong wrote:
[snip
On Mon, Nov 18, 2013 at 5:57 AM, Zane Bitter zbit...@redhat.com wrote:
On 16/11/13 11:15, Angus Salkeld wrote:
On 15/11/13 08:46 -0600, Christopher Armstrong wrote:
On Fri, Nov 15, 2013 at 3:57 AM, Zane Bitter zbit...@redhat.com wrote:
On 15/11/13 02:48, Christopher Armstrong wrote
remember what that was.
It's almost always possible to go without metaclasses without losing much
relevant brevity, and improving clarity. I strongly recommend against their
use.
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
On Sun, Nov 17, 2013 at 2:57 PM, Steve Baker sba...@redhat.com wrote:
On 11/15/2013 05:19 AM, Christopher Armstrong wrote:
http://docs.heatautoscale.apiary.io/
I've thrown together a rough sketch of the proposed API for
autoscaling. It's written in API-Blueprint format (which is a simple
On Fri, Nov 15, 2013 at 4:16 AM, Zane Bitter zbit...@redhat.com wrote:
On 14/11/13 19:58, Christopher Armstrong wrote:
On Thu, Nov 14, 2013 at 10:44 AM, Zane Bitter zbit...@redhat.com
mailto:zbit...@redhat.com wrote:
On 14/11/13 18:51, Randall Burt wrote:
Perhaps, but I also
this webhook on this
schedule would be nice, too, but I wouldn't raise a fuss if they didn't
exist and I had to actually define a trivial workflow.
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev
:)
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
, Randall Burt randall.b...@rackspace.com
wrote:
On Nov 14, 2013, at 10:19 AM, Christopher Armstrong
chris.armstr...@rackspace.com
wrote:
http://docs.heatautoscale.apiary.io/
I've thrown together a rough sketch of the proposed API for autoscaling.
It's written in API-Blueprint format
Thanks for the comments, Zane.
On Thu, Nov 14, 2013 at 9:56 AM, Zane Bitter zbit...@redhat.com wrote:
On 14/11/13 17:19, Christopher Armstrong wrote:
http://docs.heatautoscale.apiary.io/
I've thrown together a rough sketch of the proposed API for autoscaling.
It's written in API-Blueprint
) -- see the Schema
sections under each. In case you didn't notice, you can click on each
action to expand details under it.
Thanks
Georgy
On Thu, Nov 14, 2013 at 9:56 AM, Zane Bitter zbit...@redhat.com wrote:
On 14/11/13 17:19, Christopher Armstrong wrote:
http
On Thu, Nov 14, 2013 at 10:44 AM, Zane Bitter zbit...@redhat.com wrote:
On 14/11/13 18:51, Randall Burt wrote:
On Nov 14, 2013, at 11:30 AM, Christopher Armstrong
chris.armstr...@rackspace.com mailto:chris.armstr...@rackspace.com
wrote:
On Thu, Nov 14, 2013 at 11:16 AM, Randall Burt
the initial deployment
-- especially with recent discussion around healing / convergence.
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
On Thu, Nov 14, 2013 at 11:00 AM, Randall Burt
randall.b...@rackspace.comwrote:
On Nov 14, 2013, at 12:44 PM, Zane Bitter zbit...@redhat.com
wrote:
On 14/11/13 18:51, Randall Burt wrote:
On Nov 14, 2013, at 11:30 AM, Christopher Armstrong
chris.armstr...@rackspace.com
On Thu, Nov 14, 2013 at 12:52 PM, Randall Burt
randall.b...@rackspace.comwrote:
On Nov 14, 2013, at 1:05 PM, Christopher Armstrong
chris.armstr...@rackspace.com wrote:
On Thu, Nov 14, 2013 at 11:00 AM, Randall Burt
randall.b...@rackspace.com wrote:
On Nov 14, 2013, at 12:44 PM, Zane
On Thu, Nov 14, 2013 at 5:40 PM, Angus Salkeld asalk...@redhat.com wrote:
On 14/11/13 10:19 -0600, Christopher Armstrong wrote:
http://docs.heatautoscale.apiary.io/
I've thrown together a rough sketch of the proposed API for autoscaling.
It's written in API-Blueprint format (which
have responded. My recent patch (now already
merged) won't delete the resource_id.
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
trivially be accepted
by the submitter of the patch into his own patch -- with a click of a
button).
--
Christopher Armstrong
http://radix.twistedmatrix.com/
http://planet-if.com/
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
) in
a check_delete_complete method?
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
!
Congrats! I'm glad you guys finally released the code :)
Does Cisco (or anyone else) plan to continue to put development resources
into these projects, or should we basically view them as reference code for
solving particular problems?
Thanks,
--
IRC: radix
Christopher Armstrong
Rackspace
the only effect that a
dependency has is to wait until it is met before performing create, update,
or delete operations on other resources. So I think it would be nice to
understand your use case a little bit more before continuing discussion.
--
IRC: radix
Christopher Armstrong
Rackspace
/mailman/listinfo/openstack-dev
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
this right?
Pretty much! Thanks for the summary :-)
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
in this thread. I
doesn't appear that the design of Heat autoscaling (informed by Zane,
Clint, Angus and others) fails to meet the criteria you've brought up.
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev
On Fri, Aug 16, 2013 at 1:35 PM, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Zane Bitter's message of 2013-08-16 09:36:23 -0700:
On 16/08/13 00:50, Christopher Armstrong wrote:
*Introduction and Requirements*
So there's kind of a perfect storm happening around autoscaling
On Thu, Aug 15, 2013 at 6:39 PM, Randall Burt randall.b...@rackspace.comwrote:
On Aug 15, 2013, at 6:20 PM, Angus Salkeld asalk...@redhat.com wrote:
On 15/08/13 17:50 -0500, Christopher Armstrong wrote:
2. There should be a new custom-built API for doing exactly what the
autoscaling
.
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
functionality?
I can imagine that being a useful thing, if it's very easy to do, and
won't increase my test execution time too much.
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
work well.
--
IRC: radix
Christopher Armstrong
Rackspace
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
if applied properly.
It seems we could trivialize the task of keeping your template up to date
by providing an API for fetching a template that reflects the current
stack. Does that sound sensible given the current direction of the design
of Heat?
--
IRC: radix
Christopher Armstrong
Rackspace
44 matches
Mail list logo
