Re: [openstack-dev] [Heat] conditional resource exposure - second thoughts

On 14/07/15 14:34, Pavlo Shchelokovskyy wrote: Hi Heaters, currently we already expose to the user only resources for services deployed in the cloud [1], and soon we will do the same based on whether actual user roles allow creating specific resources [2]. Here I would like to get your opinion o

Re: [openstack-dev] [tc] [all] thinking additional tags

On 08/07/15 18:12, Steve Baker wrote: On 09/07/15 04:39, Zane Bitter wrote: On 08/07/15 09:03, Sean Dague wrote: Personally, I'm running out of steam on tags for this cycle, but Zane brought up a good point in the TC meeting yesterday, which was that "it would be nice to have tags fo

Re: [openstack-dev] [tc] [all] thinking additional tags

On 08/07/15 12:51, Thierry Carrez wrote: Sean Dague wrote: Personally, I'm running out of steam on tags for this cycle, but Zane brought up a good point in the TC meeting yesterday, which was that "it would be nice to have tags for criteria that we used to use for integration requirements". I st

Re: [openstack-dev] [tc] [all] thinking additional tags

On 08/07/15 09:03, Sean Dague wrote: Personally, I'm running out of steam on tags for this cycle, but Zane brought up a good point in the TC meeting yesterday, which was that "it would be nice to have tags for criteria that we used to use for integration requirements". I strongly agree with that

Re: [openstack-dev] [oslo.messaging] [mistral] Acknowledge feature of RabbitMQ in oslo.messaging

On 07/07/15 06:13, Renat Akhmerov wrote: Just to clarify: what we’re looking for is how to implement “Work queue” pattern described at [1] with oslo messaging. As Nikolay said, it requires that a message to be acknowledged after it has been processed. Yeah, so as you've discovered, oslo.messagi

Re: [openstack-dev] [heat] Question about retrieving resource_list from ResourceGroup

On 26/06/15 15:14, Hongbin Lu wrote: Hi team, I would like to start my question by using a sample template: heat_template_version: 2014-10-16 parameters: count: type: number default: 5 removal_list: type: comma_delimited_list default: [] resources: sample_g

[openstack-dev] [GBP][Heat] Group-based Policy plug-in for Heat

Every day I get an email about broken dependencies for the group-based policy Heat plugin in Fedora (openstack-heat-gbp), because the version of Heat it depends on is capped. Two points: 1) Would whoever maintains that package (Bob?) please fix it :) 2) Why was this plugin not submitted to /co

Re: [openstack-dev] [puppet] [fuel] more collaboration request

This thread kind of deteriorated a bit (though it looks like it's hopefully recovering), so I'd just like to add some observations. What we have here is a classic case of a long-running fork, with all that that entails. In this case the fork is a public one, but that actually makes very little

Re: [openstack-dev] [all] grenade with external plugins for the big tent - how to use

On 11/06/15 09:38, Kyle Mestery wrote: On Thu, Jun 11, 2015 at 6:11 AM, Sean Dague mailto:s...@dague.net>> wrote: Yesterday we landed the infrastructure for Grenade external plugins - https://review.openstack.org/#/c/185050/ The first user of this is the Heat project, with a patch t

[openstack-dev] Standard way to indicate a partial blueprint implementation?

Ever since we established[1] a format for including metadata about bugs in Git commit messages that included a 'Partial-Bug' tag, people have been looking for a way to do the equivalent for partial blueprint implementations. A non-exhaustive search of a small number of projects reveals at least

Re: [openstack-dev] [TripleO] [Puppet] Package updates strategy

On 28/05/15 03:35, Jan Provaznik wrote: On 05/28/2015 01:10 AM, Steve Baker wrote: On 28/05/15 10:54, Richard Raseley wrote: Zane Bitter wrote: Steve is working on a patch to allow package-based updates of overcloud nodes[1] using the distro's package manager (yum in the case of RDO

[openstack-dev] [TripleO] Package updates strategy

Steve is working on a patch to allow package-based updates of overcloud nodes[1] using the distro's package manager (yum in the case of RDO, but conceivable apt in others). Note we're talking exclusively about minor updates, not version-to-version upgrades here. Dan mentioned at the summit tha

Re: [openstack-dev] [Zaqar][all] Zaqar will stay... Lots of work ahead

On 27/05/15 12:42, Clint Byrum wrote: == Crazy idea section == One thing I never had a chance to discuss with any of the Zaqar devs that I would find interesting is an email-only backend for Zaqar. Basically make Zaqar an HTTP-to-email gateway. There are quite a few hyper-scale options for SMTP

Re: [openstack-dev] meeting with the zaqar team at summit; my notes

something multi-tenant capable and authenticated (if it's so safe why not use the same RabbitMQ as all the other services?), but it would be less of an 'immediate uninstall' case. cheers, Zane. Thanks, Kevin * * ---

Re: [openstack-dev] meeting with the zaqar team at summit; my notes

On 22/05/15 11:48, Amrith Kumar wrote: I’m posting this to the mailing list to summarize my notes from a meeting at 5pm yesterday at Summit relative to Zaqar and lightweight multi-tenant messaging and how it may be applicable to a number of projects. I’ll begin by saying these are not ‘minutes’

Re: [openstack-dev] [Murano] [Mistral] [Zaqar] [Keystone] SSH workflow action

On 15/05/15 11:57, Adam Young wrote: It's kind of unfortunate IMHO that the default policy.json files tend to give all users access to non-admin APIs, rather than requiring a specific role (like "Member"). Working on that. Come to my policy session! This one, I assume: http://libertydesignsu

Re: [openstack-dev] [Murano] [Mistral] [Zaqar] [Keystone] SSH workflow action

On 14/05/15 23:38, Adam Young wrote: So the mechanisms are there. In the short term we'd need some cross-project co-operation to define a system through which we can do this across projects (i.e. Murano or any other service can create a user and have Zaqar authorise it for listening on a particul

Re: [openstack-dev] [horizon][keystone][heat] Are "AVAILABLE_REGIONS" and multi-region service catalog mutually exclusive?

cloud. Horizon offers support for dealing with multiple regions within a single cloud. It also offers an option to switch between multiple different clouds using an option unfortunately called AVAILABLE_REGIONS, which is a total misnomer. - ZB Geoff On May 14, 2015, at 7:56 AM, Zane Bitter w

Re: [openstack-dev] [horizon][keystone][heat] Are "AVAILABLE_REGIONS" and multi-region service catalog mutually exclusive?

On 14/05/15 10:39, Geoff Arnold wrote: +1 There seems to be a significant disconnect between Heat, Horizon and Keystone on the subject of multi-region configurations, and the documentation isn’t helpful. At the very least, it would be useful if discussions at the summit could result in a decent

Re: [openstack-dev] [trove][zaqar] Trove and Zaqar integration. Summit working session

On 11/05/15 05:49, Flavio Percoco wrote: On 08/05/15 00:45 -0700, Nikhil Manchanda wrote: 3) The trove-guest-agent is in vm. it is connected by taskmanager by rabbitmq. We designed it. But is there some prectise to do this? how to make the vm be connected in vm-network and managem

Re: [openstack-dev] [Murano] [Mistral] SSH workflow action

nd found that it didn't meet their needs (at least at the time). cheers, Zane. Sincerely yours, Stan Lagun Principal Software Engineer @ Mirantis <mailto:sla...@mirantis.com> On Tue, May 12, 2015 at 10:52 AM, Renat Akhmerov mailto:rakhme...@mirantis.com>> wrote: Zan

Re: [openstack-dev] [Murano] [Mistral] SSH workflow action

is it is possible to have a token which is restricted to be authenticated to specific API URL like GET /v1/queues// Thanks Gosha On Tue, May 12, 2015 at 8:58 AM, Fox, Kevin M mailto:kevin@pnnl.gov>> wrote: +1 ____ From: Zane Bitter

Re: [openstack-dev] [Murano] [Mistral] [Zaqar] [Keystone] SSH workflow action

ne team and make sure they're getting feedback from all of the many groups who need it so that they can prioritise the work appropriately :) cheers, Zane. Thanks Gosha On Tue, May 12, 2015 at 8:58 AM, Fox, Kevin M mailto:kevin@pnnl.gov>> wrote: +1

Re: [openstack-dev] [Murano] [Mistral] SSH workflow action

Hello! This looks like a perfect soapbox from which to talk about my favourite issue ;) You're right about the ssh idea, for the reasons discussed related to networking and a few more that weren't (e.g. users shouldn't have to and generally don't want to give their private SSH keys to cloud

Re: [openstack-dev] [all] TC Communications planning

On 06/05/15 09:13, Anne Gentle wrote: Hi all, In the interest of communicating sooner rather than later, I wanted to write a new thread to say that Flavio Percoco and I are going to work on a TC communications plan as co-chairs of a TC communications working group. I think we can find a happy m

Re: [openstack-dev] [heat][ceilometer] autoscaling

On 06/05/15 08:25, ICHIBA Sara wrote: hey there, Please I wanna know if their is anyway I can have cpu, ram and network meters for each VM returned by ceilometer to heat for autoscaling tasks? In advance, thank you for your response, Sara The openstack-dev list is for discussing future develo

Re: [openstack-dev] [heat] Stack/Resource updated_at conventions

On 28/04/15 03:56, Steven Hardy wrote: On Mon, Apr 27, 2015 at 06:41:52PM -0400, Zane Bitter wrote: On 27/04/15 13:38, Steven Hardy wrote: On Mon, Apr 27, 2015 at 04:46:20PM +0100, Steven Hardy wrote: AFAICT there's two options: 1. Update the stack.Stack so we store "now" at e

Re: [openstack-dev] [heat] Stack/Resource updated_at conventions

On 27/04/15 13:38, Steven Hardy wrote: On Mon, Apr 27, 2015 at 04:46:20PM +0100, Steven Hardy wrote: AFAICT there's two options: 1. Update the stack.Stack so we store "now" at every transition (e.g in state_set) 2. Stop trying to explicitly control updated_at, and just allow the oslo Timestamp

Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)

On 24/04/15 20:00, Joe Gordon wrote: On Fri, Apr 24, 2015 at 4:35 PM, Fox, Kevin M mailto:kevin@pnnl.gov>> wrote: Notification might be a good way to integrate with nova. Individual tenants might want to do things as vm's come up/down, etc. Right now, you need a privileged pipe

Re: [openstack-dev] [Zaqar] Call for adoption (or exclusion?)

On 24/04/15 19:02, Joe Gordon wrote: On Mon, Apr 20, 2015 at 5:54 AM, Flavio Percoco mailto:fla...@redhat.com>> wrote: Greetings, I'd like my first action as Zaqar's PTL to be based on reflections and transparency with regards to what our past has been, to what our present is

Re: [openstack-dev] [all] Question for the TC candidates

On 24/04/15 09:52, Ed Leafe wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 04/24/2015 08:30 AM, Zane Bitter wrote: I'm not sure what you see as the difference between the "end users" and the "operators" of OpenStack, because in my mind they are one and t

Re: [openstack-dev] Please stop reviewing code while asking questions

On 24/04/15 07:21, Amrith Kumar wrote: Julien, We had a similar discussion within Trove several months ago and agreed to a convention that if you have a question, that should not warrant a -1 unless, as you indicate there's a strong reason to believe that the code is wrong and the question is

Re: [openstack-dev] [all] Question for the TC candidates

On 24/04/15 09:00, Ed Leafe wrote: I'm not sure what you see as the difference between the "end users" and the "operators" of OpenStack, because in my mind they are one and the same. I don't consider the people using, say, public cloud services to be OpenStack end users, because ultimately they

Re: [openstack-dev] [all] Question for the TC candidates

On 23/04/15 12:14, Chris Dent wrote: This might be a bit presumptuous, but why not give it a try... Not at all, we should *strongly* encourage people to ask questions of the candidates. In fact, I think we should encourage everyone to contribute to the discussion, not just the candidates.

[openstack-dev] TC Candidacy

Hello Stackists, I'd like to announce my candidacy for the OpenStack Technical Committee. I'm running because I don't think that the diversity of perspectives amongst TC members reflects the diversity of our community. We're fortunate to have a few people whose brilliance often transcends the

Re: [openstack-dev] [heat] is cloudwatch really deprecated?

On 17/04/15 13:54, Matt Fischer wrote: On Fri, Apr 17, 2015 at 11:03 AM, Zane Bitter mailto:zbit...@redhat.com>> wrote: On 17/04/15 12:46, Matt Fischer wrote: The wiki for Using Cloudwatch states: "This feature will be deprecated or removed during the Havana

Re: [openstack-dev] [Heat] moving sqlite migration scripts to tests

On 16/04/15 04:05, Anant Patil wrote: Hi, Sometime back we had a discussion on IRC regarding sqlite migration scripts. Since sqlite is mostly used for testing, we were thinking about moving the sqlite migration related code to tests folder and keep the migrate_repo sane (with only production cod

Re: [openstack-dev] [nova-docker][ceilometer][heat] Autoscaling docker in openstack

On 17/04/15 10:11, VACHNIS, AVI (AVI) wrote: Hi, @Ashish, if the limitation you've mentioned for #1 still exists, I join your question how heat auto-scale-group may work w/o ceilometer being able to collect docker metrics? Yeah, you're correct. Approach #2 has exactly the same problem as appr

Re: [openstack-dev] [heat] is cloudwatch really deprecated?

On 17/04/15 12:46, Matt Fischer wrote: The wiki for Using Cloudwatch states: "This feature will be deprecated or removed during the Havana cycle as we move to using Ceilometer as a metric/alarm service instead." [1] However it seems that cloudwatch is still being developed. It doesn't seem th

Re: [openstack-dev] [all] how to send messages (and events) to our users

On 06/04/15 22:55, Angus Salkeld wrote: Hi all For quite some time we (Heat team) have wanted to be able to send messages to our users (by user I do not mean the Operator, but the User that is interacting with the client). What do I mean by "user messages", and how do they differ from our curre

Re: [openstack-dev] [heat] autoscaling and load balancers

On 08/04/15 21:51, Miguel Grinberg wrote: Hi Angus, Regarding this: > As Zane suggested, you should think of autoscaling as been in a different service. It's not that I can't see your point of view. I can imagine an autoscaling service. I agree with you guys that if we had that, then none of

Re: [openstack-dev] [heat] autoscaling and load balancers

On 08/04/15 18:03, Miguel Grinberg wrote: Here is where we disagree. In my opinion this is broken functionality. It's not broken functionality, it's functionality that never existed. Spontaneous stack updates are just not part of the CloudFormation model, and they've never been a part of Heat

Re: [openstack-dev] [heat] autoscaling and load balancers

On 07/04/15 22:02, Miguel Grinberg wrote: Hi, The OS::Heat::AutoScalingGroup resource is somewhat limited at this time, because when a scaling even occurs it does not notify dependent resources, such as a load balancer, that the pool of instances has changed. As Thomas mentioned, the 'approved

Re: [openstack-dev] [TripleO][Heat] Overcloud software updates and ResourceGroups

On 07/04/15 05:13, Steven Hardy wrote: On Thu, Apr 02, 2015 at 06:31:39PM -0400, Zane Bitter wrote: A few of us have been looking for a way to perform software updates to servers in a TripleO Heat/Puppet-based overcloud that avoids an impedance mismatch with Heat concepts and how Heat runs its

Re: [openstack-dev] [TripleO][Heat] Overcloud software updates and ResourceGroups

On 03/04/15 01:29, Giulio Fidente wrote: hi there, thanks for sharing this, I have a On 04/03/2015 12:31 AM, Zane Bitter wrote: A few of us have been looking for a way to perform software updates to servers in a TripleO Heat/Puppet-based overcloud [...] Here's a trivial example of

Re: [openstack-dev] [TripleO][Heat] Overcloud software updates and ResourceGroups

On 02/04/15 20:31, Fox, Kevin M wrote: I'm not sure how to feel about this... Its clever... That's... unfortunate ;) Ideally this would sound like something that is a natural fit for Heat's data model. The reason it's not is that config management tools like Puppet are less sophisticated tha

[openstack-dev] [TripleO][Heat] Overcloud software updates and ResourceGroups

A few of us have been looking for a way to perform software updates to servers in a TripleO Heat/Puppet-based overcloud that avoids an impedance mismatch with Heat concepts and how Heat runs its workflow. As many talented TripleO-ers who have gone before can probably testify, that's surprisingl

Re: [openstack-dev] [heat] Network name as a Server properties

On 30/03/15 03:51, BORTMAN, Limor (Limor) wrote: Hi, I noticed the we can't use network name under OS::Neutron::Port (only "network_id") as a valid neutron property, and I was wondering why? IIRC it was something weird about how python-neutronclient worked at the time. I expected it to be

Re: [openstack-dev] [heat] heat delete woes in Juno

On 26/03/15 15:30, Georgy Okrokvertskhov wrote: I attached an example of the template which is hanging right now in my Juno environment. I believe it hangs because of floating ip stuff and the way how it is attached to a VM. It is autogenerated, so please don't be disturbed by strange resource na

Re: [openstack-dev] [heat] heat delete woes in Juno

On 26/03/15 15:56, Matt Fischer wrote: We don't have heat stack-abandon enabled. It's marked as a "preview feature", have you had any issues? It's fairly safe for this use case. If it's important for you that you don't lose track of your resources and you want to adopt them again later, it's

Re: [openstack-dev] [Heat] Decoupling Heat integration tests from Heat tree

On 26/03/15 10:38, Pavlo Shchelokovskyy wrote: Hi all, following IRC discussion here is a summary of what I propose can be done in this regard, in the order of increased decoupling: 1) make a separate requirements.txt for integration tests and modify the tox job to use it. The code of these tes

Re: [openstack-dev] [Heat] vnic_type in OS::Neutron::Port

On 20/03/15 14:33, Rob Pothier (rpothier) wrote: Hi All, It was brought to my attention that the recent changes with the vnic_type possibly should not include the colon in the property value. In the earlier versions of the review the colon was not in the property, and was appended later. https

Re: [openstack-dev] [heat][congress] Stack lifecycle plugpoint as an enabler for cloud provider's services

On 19/03/15 06:17, VACHNIS, AVI (AVI) wrote: Hi, I'm looking at this interesting blueprint https://blueprints.launchpad.net/heat/+spec/stack-lifecycle-plugpoint and I hope you can easily clarify some things to me. I see the following statements related to this BP: * [in "problem description" s

Re: [openstack-dev] [TripleO][Tuskar] Common library for shared code

On 16/03/15 16:38, Ben Nemec wrote: On 03/13/2015 05:53 AM, Jan Provaznik wrote: On 03/10/2015 05:53 PM, James Slagle wrote: On Mon, Mar 9, 2015 at 4:35 PM, Jan Provazník wrote: Hi, it would make sense to have a library for the code shared by Tuskar UI and CLI (I mean TripleO CLI - whatever i

Re: [openstack-dev] Avoiding regression in project governance

On 10/03/15 12:29, Russell Bryant wrote: I feel that we're at a very vulnerable part of this transition. We've abolished the incubation process and integrated release. We've established a fairly low bar for new projects [2]. However, we have not yet approved*any* tags other than the one that

Re: [openstack-dev] [heat] Unknown resource OS::Heat::ScaledResource

On 10/03/15 12:26, Manickam, Kanagaraj wrote: Hi, I observed in one of the patch mentioned below, OS::Heat::ScaledResource is reported as unknown, could anyone help here to resolve the issue. Thanks. http://logs.openstack.org/76/157376/8/check/check-heat-dsvm-functional-mysql/c9a1be3/logs/scree

Re: [openstack-dev] [Magnum][Heat] Expression of Bay Status

On 09/03/15 23:47, Angus Salkeld wrote: On Tue, Mar 10, 2015 at 8:53 AM, Adrian Otto mailto:adrian.o...@rackspace.com>> wrote: Magnum Team, In the following review, we have the start of a discussion about how to tackle bay status: https://review.openstack.org/159546 I thin

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

On 25/02/15 19:15, Dolph Mathews wrote: On Wed, Feb 25, 2015 at 5:42 PM, Zane Bitter mailto:zbit...@redhat.com>> wrote: On 25/02/15 15:37, Joe Gordon wrote: On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell mailto:tim.b...@cern.ch> <mailto:tim.b...@cern.ch &

Re: [openstack-dev] [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

On 25/02/15 15:37, Joe Gordon wrote: On Sat, Feb 21, 2015 at 5:03 AM, Tim Bell mailto:tim.b...@cern.ch>> wrote: A few inline comments and a general point How do we handle scenarios like volumes when we have a per-component janitor rather than a single co-ordinator ? To be cl

Re: [openstack-dev] [stable][all] Revisiting the 6 month release cycle

On 23/02/15 19:14, Joe Gordon wrote: Was: http://lists.openstack.org/pipermail/openstack-dev/2015-February/057578.html There has been frustration with our current 6 month development cadence. This is an attempt to explain those frustrations and propose a very rough outline of a possible alternat

Re: [openstack-dev] [Mistral] Changing "expression" delimiters in Mistral DSL

On 16/02/15 16:06, Dmitri Zimine wrote: 2) Use functions, like Heat HOT or TOSCA: HOT templates and TOSCA doesn’t seem to have a concept of typed variables to borrow from (please correct me if I missed it). But they have functions: function: { function_name: {foo: [parameter1, parameter 2], bar:

Re: [openstack-dev] [heat] operators vs users for choosing convergence engine

On 03/02/15 14:12, Clint Byrum wrote: The visible change in making things parallel was minimal. In talking about convergence, it's become clear that users can and should expect something radically different when they issue stack updates. I'd love to say that it can be done to just bind convergenc

Re: [openstack-dev] [Heat] Add extraroutes support to neutron routers

On 05/02/15 12:23, James Denton wrote: Hello all, Regarding https://blueprints.launchpad.net/heat/+spec/router-properties-object Does anyone know if there are plans to implement this functionality in an upcoming release? Unlikely - unfortunately the Neutron API for extra routes makes it impo

Re: [openstack-dev] [heat] operators vs users for choosing convergence engine

On 02/02/15 19:52, Steve Baker wrote: A spec has been raised to add a config option to allow operators to choose whether to use the new convergence engine for stack operations. For some context you should read the spec first [1] Rather than doing this, I would like to propose the following: I

Re: [openstack-dev] [Heat] Convergence Phase 1 implementation plan

On 26/01/15 19:04, Angus Salkeld wrote: On Sat, Jan 24, 2015 at 7:00 AM, Zane Bitter mailto:zbit...@redhat.com>> wrote: I'm also prepared to propose specs for all of these _if_ people think that would be helpful. I see three options here: - Propose 18 fairly minimal spec

Re: [openstack-dev] [Heat][Keystone] Native keystone resources in Heat

On 30/01/15 02:19, Thomas Spatzier wrote: From: Zane Bitter To: openstack Development Mailing List Date: 29/01/2015 17:47 Subject: [openstack-dev] [Heat][Keystone] Native keystone resources in Heat I got a question today about creating keystone users/roles/tenants in Heat templates. We

Re: [openstack-dev] [Heat][Keystone] Native keystone resources in Heat

On 30/01/15 05:20, Steven Hardy wrote: On Thu, Jan 29, 2015 at 12:31:17PM -0500, Zane Bitter wrote: On 29/01/15 12:03, Steven Hardy wrote: On Thu, Jan 29, 2015 at 11:41:36AM -0500, Zane Bitter wrote: IIUC keystone now allows you to add users to a domain that is otherwise backed by a read-only

Re: [openstack-dev] [Heat][Keystone] Native keystone resources in Heat

On 29/01/15 12:03, Steven Hardy wrote: On Thu, Jan 29, 2015 at 11:41:36AM -0500, Zane Bitter wrote: >IIUC keystone now allows you to add users to a domain that is otherwise >backed by a read-only backend (i.e. LDAP). If this means that it's now >possible to configure a cloud so

[openstack-dev] [Heat][Keystone] Native keystone resources in Heat

I got a question today about creating keystone users/roles/tenants in Heat templates. We currently support creating users via the AWS::IAM::User resource, but we don't have a native equivalent. IIUC keystone now allows you to add users to a domain that is otherwise backed by a read-only backen

Re: [openstack-dev] [heat] multicloud support for ec2

On 25/01/15 00:03, Hongbin Lu wrote: Hi Heat team, I am looking for a solution to bridge between OpenStack and EC2. According to documents, it seems that Heat has multicloud support but the remote cloud(s) must be OpenStack. It actually doesn't, although it is planned. (We have multi-region s

Re: [openstack-dev] [Heat] core team changes

On 27/01/15 20:36, Angus Salkeld wrote: Hi all After having a look at the stats: http://stackalytics.com/report/contribution/heat-group/90 http://stackalytics.com/?module=heat-group&metric=person-day I'd like to propose the following changes to the Heat core team: Add: Qiming Teng Huang Tianhu

Re: [openstack-dev] [heat][hot]

On 25/01/15 10:41, Dmitry wrote: Hello, I need to receive instance id as part of the instance installation script. Something like: params: $current_id: {get_param: $this.id } I have no idea what this is supposed to mean, sorry. Is it possible? The get_resource fun

[openstack-dev] [Heat] Convergence Phase 1 implementation plan

I've mentioned this in passing a few times, but I want to lay it out here in a bit more detail for comment. Basically we're implementing convergence at a time when we still have a lot of 'unit' tests that are really integration tests, and we don't want to have to rewrite them to anticipate this

[openstack-dev] [Heat] Final steps toward a Convergence design

Hi folks, I'd like to come to agreement on the last major questions of the convergence design. I well aware that I am the current bottleneck as I have been struggling to find enough time to make progress on it, but I think we are now actually very close. I believe the last remaining issue to

Re: [openstack-dev] [tc][python-clients] More freedom for all python clients

On 13/01/15 10:01, Jeremy Stanley wrote: On 2015-01-13 07:46:38 -0500 (-0500), Sean Dague wrote: Why doesn't rally just remove itself from projects.txt, then there would be no restrictions on what it adds. I second this recommendation. If Rally wants to depend on things which are not part of O

Re: [openstack-dev] [Heat] Where to keep data about stack breakpoints?

On 13/01/15 11:58, Tomas Sedovic wrote: I also had a chat with Steve Hardy and he suggested adding a STOPPED state to the stack (this isn't in the spec). While not strictly necessary to implement the spec, this would help people figure out that the stack has reached a breakpoint instead of just w

Re: [openstack-dev] [Heat] Where to keep data about stack breakpoints?

On 12/01/15 13:05, Steven Hardy wrote: >I also had a chat with Steve Hardy and he suggested adding a STOPPED state >to the stack (this isn't in the spec). While not strictly necessary to >implement the spec, this would help people figure out that the stack has >reached a breakpoint instead of jus

Re: [openstack-dev] [Heat] Where to keep data about stack breakpoints?

On 12/01/15 10:49, Ryan Brown wrote: On 01/12/2015 10:29 AM, Tomas Sedovic wrote: Hey folks, I did a quick proof of concept for a part of the Stack Breakpoint spec[1] and I put the "does this resource have a breakpoint" flag into the metadata of the resource: https://review.openstack.org/#/c/1

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

On 08/01/15 05:39, Anant Patil wrote: 1. The stack was failing when there were single disjoint resources or just one resource in template. The graph did not include this resource due to a minor bug in dependency_names(). I have added a test case and fix here: https://github.com/anantpatil/heat-co

Re: [openstack-dev] [Heat] Precursor to Phase 1 Convergence

On 09/01/15 01:07, Angus Salkeld wrote: I am not in favor of the --continue as an API. I'd suggest responding to resource timeouts and if there is no response from the task, then re-start (continue) the task. Yeah, I am not in favour of a new API either. In fact, I believe we already have this

Re: [openstack-dev] [heat] Application level HA via Heat

On 24/12/14 05:17, Steven Hardy wrote: On Mon, Dec 22, 2014 at 03:42:37PM -0500, Zane Bitter wrote: On 22/12/14 13:21, Steven Hardy wrote: Hi all, So, lately I've been having various discussions around $subject, and I know it's something several folks in our community are intereste

Re: [openstack-dev] [heat] Application level HA via Heat

On 22/12/14 13:21, Steven Hardy wrote: Hi all, So, lately I've been having various discussions around $subject, and I know it's something several folks in our community are interested in, so I wanted to get some ideas I've been pondering out there for discussion. I'll start with a proposal of h

Re: [openstack-dev] Fw: [Heat] Multiple_Routers_Topoloy

The -dev mailing list is not for usage questions. Please post your question to ask.openstack.org and include the text of the error message you when trying to add a RouterInterface. cheers, Zane. On 22/12/14 04:18, Rao Shweta wrote: Hi All I am working on openstack Heat and i wanted to make

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

On 15/12/14 07:47, Murugan, Visnusaran wrote: We have similar questions regarding other areas in your implementation, which we believe if we understand the outline of your implementation. It is difficult to get a hold on your approach just by looking at code. Docs strings / Etherpad will help.

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

On 17/12/14 13:05, Gurjar, Unmesh wrote: I'm storing a tuple of its name and database ID. The data structure is resource.GraphKey. I was originally using the name for something, but I suspect I could probably drop it now and just store the database ID, but I haven't tried it yet. (Having the name

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

On 15/12/14 10:15, Anant Patil wrote: On 13-Dec-14 05:42, Zane Bitter wrote: On 12/12/14 05:29, Murugan, Visnusaran wrote: -Original Message- From: Zane Bitter [mailto:zbit...@redhat.com] Sent: Friday, December 12, 2014 6:37 AM To: openstack-dev@lists.openstack.org Subject: Re

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

post operation if Rollback==True) 3. DELETE will be just another update with an empty to_be_realized_graph. Yes, that goes without saying. In my implementation Stack._create_or_update() handles all three operations. It would be great if we can freeze a stable approach by mid-week as Christmas

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

On 15/12/14 09:32, Anant Patil wrote: On 12-Dec-14 06:29, Zane Bitter wrote: On 11/12/14 01:14, Anant Patil wrote: On 04-Dec-14 10:49, Zane Bitter wrote: On 01/12/14 02:02, Anant Patil wrote: On GitHub:https://github.com/anantpatil/heat-convergence-poc I'm trying to review this code a

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

On 12/12/14 05:29, Murugan, Visnusaran wrote: -Original Message- From: Zane Bitter [mailto:zbit...@redhat.com] Sent: Friday, December 12, 2014 6:37 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown On 11/12/14 08:26

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

On 11/12/14 08:26, Murugan, Visnusaran wrote: [Murugan, Visnusaran] In case of rollback where we have to cleanup earlier version of resources, we could get the order from old template. We'd prefer not to have a graph table. In theory you could get it by keeping old templates around. But that me

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

On 11/12/14 01:14, Anant Patil wrote: On 04-Dec-14 10:49, Zane Bitter wrote: On 01/12/14 02:02, Anant Patil wrote: On GitHub:https://github.com/anantpatil/heat-convergence-poc I'm trying to review this code at the moment, and finding some stuff I don't understand: https://

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

You really need to get a real email client with quoting support ;) On 10/12/14 06:42, Murugan, Visnusaran wrote: Well, we still have to persist the dependencies of each version of a resource _somehow_, because otherwise we can't know how to clean them up in the correct order. But what I think

Re: [openstack-dev] [Mistral] Query on creating multiple resources

On 09/12/14 03:48, Renat Akhmerov wrote: Hey, I think it’s a question of what the final goal is. For just creating security groups as a resource I think Georgy and Zane are right, just use Heat. If the goal is to try Mistral or have this simple workflow as part of more complex then it’s total

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

On 08/12/14 07:00, Murugan, Visnusaran wrote: Hi Zane & Michael, Please have a look @ https://etherpad.openstack.org/p/execution-stream-and-aggregator-based-convergence Updated with a combined approach which does not require persisting graph and backup stack removal. Well, we still have to

Re: [openstack-dev] [Mistral] Query on creating multiple resources

On 08/12/14 09:41, Sushma Korati wrote: Can we create multiple resources using a single task, like multiple keypairs or security-groups or networks etc? Define them in a Heat template and create the Heat stack as a single task. - ZB ___ OpenStack-de

Re: [openstack-dev] [Heat] Convergence proof-of-concept showdown

On 01/12/14 02:02, Anant Patil wrote: On GitHub:https://github.com/anantpatil/heat-convergence-poc I'm trying to review this code at the moment, and finding some stuff I don't understand: https://github.com/anantpatil/heat-convergence-poc/blob/master/heat/engine/stack.py#L911-L916 This appe

Re: [openstack-dev] [Heat] Rework auto-scaling support in Heat

On 01/12/14 18:34, Angus Salkeld wrote: I'd suggest a combination between A and B. We may not be as far apart as I thought. 1) Separate some of the autoscaling logic into libraries in Heat 2) Get the separated REST service in place and working (using the above heat library) 3) Add an environm

Re: [openstack-dev] [Heat] Rework auto-scaling support in Heat

On 28/11/14 02:33, Qiming Teng wrote: Dear all, Auto-Scaling is an important feature supported by Heat and needed by many users we talked to. There are two flavors of AutoScalingGroup resources in Heat today: the AWS-based one and the Heat native one. As more requests coming in, the team has p

Re: [openstack-dev] [Heat] Using Job Queues for timeout ops

On 13/11/14 13:59, Clint Byrum wrote: I'm not sure we have the same understanding of AMQP, so hopefully we can clarify here. This stackoverflow answer echoes my understanding: http://stackoverflow.com/questions/17841843/rabbitmq-does-one-consumer-block-the-other-consumers-of-the-same-queue Not

[openstack-dev] [Heat] Convergence proof-of-concept showdown

A bunch of us have spent the last few weeks working independently on proof of concept designs for the convergence architecture. I think those efforts have now reached a sufficient level of maturity that we should start working together on synthesising them into a plan that everyone can forge ah

<    1   2   3   4   5   6   7   8   9   >