Re: [openstack-dev] [telemetry][heat] Removal of Aodh combination alarms

Zane, as I understand, all related code was removed. Probably we may to remove our Hidden resource too. If we want to have hidden resource, then probably as you mentioned will be enough to raise Exceptions and execute nothing for handle_delete. On 28 February 2017 at 01:36, Zane Bitter

Re: [openstack-dev] [Heat] OpenStack Summit Barcelona: Heat Meetup (evening)

o get there together, we can gettering around > Registration table(CCIB hall) at 7:20 and go there together. > > 2016-10-25 15:27 GMT+08:00 Sergey Kraynev <skray...@mirantis.com>: > >> Rico, >> >> I realized, that this place is not so close to summit center

Re: [openstack-dev] [Heat] OpenStack Summit Barcelona: Heat Meetup (evening)

Rico, I realized, that this place is not so close to summit center :) So I think, that follow link will be helpful:

Re: [openstack-dev] [heat] [magnum] Subjects to discuss during the summit

Hi Spyros, AFAIK we already have special session slot related with your topic. So thank you for the providing all items here. Rabi, can we add link on this mail to etherpad ? (it will save our time during session :) ) On 10 October 2016 at 18:11, Spyros Trigazis wrote: > Hi

Re: [openstack-dev] [heat] Presence at PTG, Atlanta

Thierry, Thank you for the clarification :) On 7 October 2016 at 11:35, Thierry Carrez <thie...@openstack.org> wrote: > Sergey Kraynev wrote: > > Rabi, thank you for the information. > > > > I think, that we need to attend as a team. So I agree with you opinion >

Re: [openstack-dev] [heat] Presence at PTG, Atlanta

Rabi, thank you for the information. I think, that we need to attend as a team. So I agree with you opinion about option 1. Also I have a question: When do we need prepare new list of topics for design sessions for this event ? On 7 October 2016 at 08:48, Rabi Mishra wrote:

Re: [openstack-dev] [heat] resigning from heat-cores

Hi Pavlo, It's really bad to hear such news. However as you said we all stay in community and I believe, we will meet again! :) See you in Barcelona, I hope ;) On 12 September 2016 at 15:35, Pavlo Shchelokovskyy wrote: > Hi Heaters, > > with great regret I announce

Re: [openstack-dev] [tc] [heat] [murano] [app-catalog] OpenStack Apps Community, several suggestions how to improve collaboration

Hi Jeremy, Please see my answers below: On 31 May 2016 at 19:38, Jeremy Stanley <fu...@yuggoth.org> wrote: > On 2016-05-31 19:20:22 +0300 (+0300), Sergey Kraynev wrote: > [...] > > * *Second part related with changes with future repositories and* > > important

Re: [openstack-dev] [tc] [heat] [murano] [app-catalog] OpenStack Apps Community, several suggestions how to improve collaboration

Hi Infra, Murano and App Catalog teams. We discussed in some more details plan suggested below with App Catalog, Murano and (partially) Infra team regarding moving repositories with source code of Murano applications out of area of responsibility of Murano core team. * *First part related

Re: [openstack-dev] [heat] api-ref gate job is active

Hi guys, just for clarification: do I correctly understand, that now we store all API related docs in local (Heat) repository and we have not copy of this staff somewhere else? so we can easily update it ourself and don't push the same commit to another repository ? And also library mentioned in

Re: [openstack-dev] [heat]informal meetup during summit

I will be there after 15 min 28 апр. 2016 г. 7:14 PM пользователь "Rico Lin" написал: > *Tomorrow 10:00 am at alta's cafe* > > See you guys have there:) > > http://altascafe.com/ > > map >

Re: [openstack-dev] [heat] Issue with validation and preview due to get_attr==None

Zane, I like you idea. As example we may discuss some steps for it during summit session (if it need). Also I have another question, which probably came in your heads a lot of times: Can we somekind improve our existing approach for validation? we do validation twice - before create and during

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

] http://docs.openstack.org/developer/heat/template_guide/hot_spec.html#get-attr On 24 March 2016 at 08:39, Rabi Mishra <ramis...@redhat.com> wrote: >> On Wed, Mar 23, 2016 at 05:25:57PM +0300, Sergey Kraynev wrote: >> >Hello, >> >It looks similar on issu

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

. there is corresponding bug was created https://bugs.launchpad.net/heat/+bug/1561157 On 23 March 2016 at 20:35, Steven Hardy <sha...@redhat.com> wrote: > On Wed, Mar 23, 2016 at 05:25:57PM +0300, Sergey Kraynev wrote: >>Hello, >>It looks similar on issue, which was discussed her

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

Hello, It looks similar on issue, which was discussed here [1] I suppose, that the root cause is incorrect using get_attr for your case. Probably you got "list" instead of "string". F.e. if I do something similar: outputs: rg_1: value: {get_attr: [rg_a, rg_a_public_ip]} rg_2:

Re: [openstack-dev] 答复: [Heat] Nomination Oleksii Chuprykov to Heat core reviewer

Looks like it was unanimously decision :) Oleksii, my congratulations ! Good work. I will add you to necessary groups ;) On 17 March 2016 at 04:34, Huangtianhua <huangtian...@huawei.com> wrote: > +1 ：） > > -邮件原件- > 发件人: Sergey Kraynev [mailto:skray...@mirantis.com] >

Re: [openstack-dev] [Heat][Neutron] Mitaka RC1 available

On 16 March 2016 at 20:15, Thierry Carrez wrote: > Hello everyone, > > Heat and Neutron just produced a release candidate for the end of the Mitaka > cycle! You can find their RC1 source code tarballs at: Heat team also plan to cut RC2 on the week. > >

[openstack-dev] [Heat] Nomination Oleksii Chuprykov to Heat core reviewer

Hi Heaters, The Mitaka release is close to finish, so it's good time for reviewing results of work. One of this results is analyze contribution results for the last release cycle. According to the data [1] we have one good candidate for nomination to core-review team: Oleksii Chuprykov. During

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

ation, only after Heat receives the signal of "SUCCESS", > then it try to begin launch "rg_b"(my another server in another resource > group). > > I am wondering whether there is a chance that, the "IP" information is > available but Heat doesn't try

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

Hi, Doug Heat team is agree to use python-heatclient == 1.0.0 for creating stable branch On 9 March 2016 at 20:26, Doug Hellmann wrote: > It's time to start opening the stable branches for libraries. I've > prepared a list of repositories and the proposed versions from

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

Hi Gary, First of all you don't need to use "depends_on", because using "get_attr" already create implicit dependency from rg_a. About getting Null instead of real Ip address: It sounds like a bug, but IMO, it's expected behavior, because I suppose it happens due to: - you create in rg_a some

Re: [openstack-dev] [all][release] Release countdown for week R-4, Mar 7 - 11

Hi Doug. I have one question related with last item: "Release actions". Who will prepare patches for Reno and for updating .gitreview? Should it be done by related project team or it will be done by someone else? On 5 March 2016 at 02:01, Doug Hellmann wrote: > The Mitaka

[openstack-dev] [Heat] Release of M3 milestone and FFE for rc-1

Hi all. I want to inform all, that mitaka-3 milestone was recently released: https://review.openstack.org/#/c/284198/ So now we are going to prepare mitaka-rc1. This milestone has one Feature Freeze Exception: https://blueprints.launchpad.net/heat/+spec/lbaasv2-suport For this BP we still has

[openstack-dev] [heat] Heat Convergence in Mitaka/Newton status and plans

Hi all, I want to share results of the last Heat meeting, where we discussed "convergence" status. "Convergence" feature still has some issues, which prevent enabling "convergence" engine by default. Some of them were found on TripleO during manual deploying. Also there are valuable numbers of

[openstack-dev] [heat] re-ask about Global OpenStack Bug Smash Mitaka

Hi Heaters. I want to attract your attention on mail [1] about Bug Smash Day and ask question related with it: Does anybody plan to visit Moscow during this event? If yes, we can meet there and work together :) It will be really cool to create group of people in different locations and discuss

Re: [openstack-dev] Any chances to backport port_security_enabled support into Heat for Kilo 2015.1.3?

Sean, thank you for the spotting. Martinx, According to the information mentioned by Sean, we unfortunately can not do it :( On 29 January 2016 at 10:45, Sean M. Collins wrote: > Kilo is in the "security supported" stage of the lifecycle. So no, > that's not going to get

Re: [openstack-dev] Any chances to backport port_security_enabled support into Heat for Kilo 2015.1.3?

I see ,that it has a assigned bug. So we can process it as normal backport (although it looks as a small enhancement). So Please just propose patch and we will review it. On 28 January 2016 at 23:45, Martinx - ジェームズ wrote: > Guys, > > This is important and Kilo is

Re: [openstack-dev] [heat] spec-lite for simple feature requests

+1 from my side. I agree with this idea. There is only one question from my side, which IMO we should describe in documentation: Do we need to upload release-notes for such small features? My guess is - Yes. I'd like to know what other guys think about it. On 20 January 2016 at 18:21, Rabi

Re: [openstack-dev] [heat] spec-lite for simple feature requests

On 21 January 2016 at 05:57, Rico Lin wrote: > +1 > > And how everyone think about if we deprecate to use Blueprint in Launchpad > and use bug system instead? > Rico, I am not sure, that it will be really useful. It's obvious, that we may track progress by reno +

Re: [openstack-dev] [heat] Convergence status

Anant, thank you for the summary. I planned to announce it (enabling convergence by default) on the next week (after m-2). I think, that we need to land two first mentioned patches before it ^. On 19 January 2016 at 09:44, Anant Patil wrote: > > Hi, > > This is to discuss

[openstack-dev] [heat] cancel IRC meeting for 30 Dec

Hi, Heaters. I'd suggest to cancel tomorrow meeting (30 Dec 2015). The experience of previous meeting showed, that the most part of Heat team is on holidays/vacations. more over I don't think, that we have some useful updates after Christmas :) If somebody have a really important reason do not

Re: [openstack-dev] [heat][telemetry] gate-ceilometer-dsvm-integration broken

Hi, Julien. I suppose, that your guess is right. Mentioned patch was merged recently and it broke our Ceilometer related functional test. There is a patch, which skip it. [1] and related bug [2] We already have a revert for this staff [3] and patch for check based on this revert [4]. [1]

[openstack-dev] [Heat] Status of the Support Conditionals in Heat templates

Hi Heaters, On the last IRC meeting we had a question about Support Conditionals spec [1]. Previous attempt for this staff is here [2]. The example of first POC in Heat can be reviewed here [3] As I understand we have not had any complete decision about this work. So I'd like to clarify feelings

Re: [openstack-dev] [heat] Rico Lin for heat-core

So looks like most part have agreement :) My congratulations, Rico!!! Good luck in this important work. I will add you to gerrit group. On 8 December 2015 at 06:30, Rabi Mishra wrote: > - Original Message - > > Hi all. > > > > I'd like to nominate Rico Lin for

[openstack-dev] [heat] Rico Lin for heat-core

Hi all. I'd like to nominate Rico Lin for heat-core. He did awesome job with providing useful and valuable reviews. Also his contribution is really high [1] . [1] http://stackalytics.com/report/contribution/heat-group/60 Heat core-team, please vote with: +1 - if you agree -1 - if you

Re: [openstack-dev] [tripleo][ironic][heat] Adding back the tripleo check job

On 30 November 2015 at 18:19, Derek Higgins wrote: > Hi All, > > A few months tripleo switch from its devtest based CI to one that was > based on instack. Before doing this we anticipated disruption in the ci > jobs and removed them from non tripleo projects. > > We'd

[openstack-dev] [Heat] Heat specs re-organization

Hi all. This mail is announcement of changes in heat-specs repository, which were *partially* discussed on the last Heat weekly meeting. There are following list of planned changes: - Create one main directory for all specs with name, e.g. scope - Move all not implemented specs from previous

Re: [openstack-dev] [Heat] how to start heat through devstack

Hi, P. Ramanjaneya Reddy. Please read Heat documentation page: http://docs.openstack.org/developer/heat/getting_started/on_devstack.html#configure-devstack-to-enable-heat In your case it looks like you use localrc for new version of devstack, so you need use local.conf file instead. If it will

Re: [openstack-dev] [neutron][heat] LBaaS of Neutron

On 16 November 2015 at 09:46, Qiao,Liyong wrote: > hi, I have some questions about neutorn LBaas. > > seen from the wiki, the load balancer only support: > > *Table 4.6. Load Balancing Algorithms* > *Name* LEAST_CONNECTIONS ROUND_ROBIN >

Re: [openstack-dev] [heat] Questions about BP for enable/disable heat-engine

Ethan, I can see, that it was assigned on Kanagaraj, but he is now in vacation (afaik). Also corresponding patch with specification was abandoned by his request, so I suggest wait answer here or may be ping him in IRC directly on the next week. On 8 November 2015 at 17:26, Ethan Lynn

Re: [openstack-dev] [heat] Convergence plans

Anant, thank you for notification. I will be happy to hear Kanagaraj. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [Heat][Rant] About blank rechecks

On 22 October 2015 at 10:58, Thomas Herve wrote: > Hi all, > > You've seen me complain about people doing blank rechecks in Gerrit on IRC, > and it seems it had little to no effect. So here I am trying to spread the > word here. I'll try to stay calm. > > I'm seeing way too

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

Rabi, Peter, my congradulations. You were elected by a unanimous vote :) I will add you to heat-core group. Enjoy and stay on this course ! :) On 21 October 2015 at 09:45, Qiming Teng <teng...@linux.vnet.ibm.com> wrote: > +1 to both. > > Qiming > > On Tue, Oct 20, 2015 at 04:

Re: [openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

On 20 October 2015 at 16:04, Monty Taylor wrote: > On 10/20/2015 06:43 AM, Andreas Jaeger wrote: >> >> On 2015-10-20 12:17, Qiming Teng wrote: >>> >>> Hi, >>> >>> Just encountered this again in code review [1]. The question is about >>> the repository to point to when

[openstack-dev] [Heat] core team nomination

I'd like to propose new candidates for heat core-team: Rabi Mishra Peter Razumovsky According statistic both candidate made a big effort in Heat as reviewers and as contributors [1][2]. They were involved in Heat community work during last several releases and showed good understanding of Heat

[openstack-dev] [Heat] Mitaka design summit schedule

Hi folks, I glad to inform you about final version of Heat schedule for design summit. Online version is available here: - http://mitakadesignsummit.sched.org/type/Heat#.Vh_V7NSlyko It will be useful for understanding rooms and time. If you want to look on description and etherpad for each

Re: [openstack-dev] [Heat] mox to mock migration

Jay, I think, that only one person who partially do the same job is Qiming. Please ask him about it. Also I think, that will be good to create BP for it, which you may mention in commit messages. In this Bp you may specify list of directories for parallel work. There is nothing else from my side.

Re: [openstack-dev] [heat] perfomance benchmark metrics of heat-api

On 6 October 2015 at 10:18, Christian Berendt wrote: > On 10/06/2015 05:20 AM, ESWAR RAO wrote: >> >> Has anyone done any performance tests on heat-api servers on any >> standard setup so as to know how many stack requests it can handle >> before it can stumble so that we

Re: [openstack-dev] [heat] Traditional question about Heat IRC meeting time.

from my iPhone > >> On Oct 1, 2015, at 10:36 PM, Zane Bitter <zbit...@redhat.com> wrote: >> >>> On 29/09/15 05:56, Sergey Kraynev wrote: >>> Hi Heaters! >>> >>> Previously we had constant "tradition" to change meeting time for >>> inv

Re: [openstack-dev] [Heat] Assumptions regarding extensions to OpenStack api's

Guys. Thank you for the pointing to the this gap. It probably was wrong missed before assumption about nova extension. I was personally sure, that it this extension always is installed. Currently we have couple resources OS::Nova::Server and AWS::EC2::Instance, which uses this extension with

[openstack-dev] [heat] Traditional question about Heat IRC meeting time.

Hi Heaters! Previously we had constant "tradition" to change meeting time for involving more people from different time zones. However last release cycle show, that two different meetings with 07:00 and 20:00 UTC are comfortable for most of our contributors. Both time values are acceptable for me

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

e latter, IMO. > > What was the result of your meeting discussion? (*goes to grub around in > eavesdrop logs after typing this.*) > > Thanks, > doug > > > > On Sep 23, 2015, at 12:09 PM, Sergey Kraynev <skray...@mirantis.com> > wrote: > > Guys. I happy, that

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

rg >> > Subject: Re: [openstack-dev] [neutron][lbaas] - Heat >> > support for LbaasV2 >> > >> > Well I'd hate to have the V2 postfix on it because V1 >> > will be deprecated >>

Re: [openstack-dev] [neutron][lbaas] - Heat support for LbaasV2

Brandon. As I understand we v1 and v2 have differences also in list of objects and also in relationships between them. So I don't think that it will be easy to upgrade old resources (unfortunately). I'd agree with second Kevin's suggestion about implementation new resources in this case. I see,

Re: [openstack-dev] [Heat] Integration Test Questions

sorry, false pressing ;) Regards, Sergey. On 13 September 2015 at 16:10, Sergey Kraynev <skray...@mirantis.com> wrote: > Hi Sabeen, > > I think, that Pavlo described whole picture really nice. > So I'd like just to add couple my thoughts below: > > > Regards, > Se

Re: [openstack-dev] [Heat] Integration Test Questions

Hi Sabeen, I think, that Pavlo described whole picture really nice. So I'd like just to add couple my thoughts below: Regards, Sergey. On 12 September 2015 at 15:08, Pavlo Shchelokovskyy < pshchelokovs...@mirantis.com> wrote: > Hi Sabeen, > > thank you for the effort :) More tests is always

[openstack-dev] [Tripleo][Heat][Nova][Ironic] Rich-network stuff and ironic hypervisor

Hi folks, Currently during implementation rich-network bp [1] (spec - [2]) we met with issue on Tripleo [3]. As temporary solution patch [4] was reverted. According traceback mentioned in bug description current issue related with mac addresses which should be used for specific hypervisor [5]

Re: [openstack-dev] [heat] [gate] gate-heat-dsvm-functional-orig-mysql fails 100%

Sean, thank you for the raising it. We know about this issue. It was related with glanceclient: There is a fix, which fixes this issue - https://review.openstack.org/#/c/219533/ If it's possible may you abandon changes in queue before this patch? Regards, Sergey. On 2 September 2015 at 16:07,

Re: [openstack-dev] [Heat] convergence rally test results (so far)

Angus! it's Awesome! Thank you for the investigation. I had a talk with guys from Sahara team and we decided to start testing convergence with Sahara after L release. I suppose, that Murano can also join to this process. Also AFAIK Sahara team plan to create functional tests with Heat-engine.

Re: [openstack-dev] [magnum] devstack/heat problem with master_wait_condition

Hi Stanislaw, Your host with Fedora should have special config file, which will send signal to WaitCondition. For good example please take a look this template https://github.com/openstack/heat-templates/blob/819a9a3fc9d6f449129c8cefa5e087569340109b/hot/native_waitcondition.yaml

Re: [openstack-dev] Proposing Kanagaraj Manickam and Ethan Lynn for heat-core

+1 from me for both. Regards, Sergey. On 31 July 2015 at 07:35, Steve Baker sba...@redhat.com wrote: I believe the heat project would benefit from Kanagaraj Manickam and Ethan Lynn having the ability to approve heat changes. Their reviews are valuable[1][2] and numerous[3], and both have

Re: [openstack-dev] [all][heat][oslo] Public show and validation clients methods

Doug, Terry. Thank you for the feedback. I will create a BP with list of desired public methods and will add all projects to it. Regards, Sergey. On 9 July 2015 at 21:20, Doug Hellmann d...@doughellmann.com wrote: Excerpts from Sergey Kraynev's message of 2015-07-09 18:26:09 +0300: Hi

Re: [openstack-dev] [Heat] Show attribute is a collection of other attributes or not?

Thank everyone for the good feedback. If summarize all suggestions: - I will continue add show as raw output (similar on clients show command output) - Also we decided to implement additional functional for get_attr function, when it get only resource name and returns map with all attributes

[openstack-dev] [Heat] Show attribute is a collection of other attributes or not?

Hi Heaters. I don't think that my question is very huge for openstack-dev, but it affects a lot of Heat resources and need collect more opinions before apply some of follow approaches. I recently uploaded initial approach for implementation common 'show' attribute [1]

Re: [openstack-dev] [Heat][Oslo] Versioned objects compatibility mode

Davanum, Can we also use SIGHUP signal tool instead of for these restarts? Regards, Sergey. On 22 June 2015 at 13:12, Davanum Srinivas dava...@gmail.com wrote: Michał, we are adding that reread config to oslo.service, there's a test version on pypi 0.1.0 (API not yet stable) that you can

Re: [openstack-dev] [heat][python-heatclient] Does python-heatclient works with keystone sessions?

Hi Jay. AFAIK, it works, but we can have some minor issues. There several atches on review to improve it: https://review.openstack.org/#/q/status:open+project:openstack/python-heatclient+branch:master+topic:improve-sessionclient,n,z Also as I remember we really had bug mentioned by you, but fix

Re: [openstack-dev] [QA][Glance][Heat][Cinder] Removing the CLI tests from Tempest

Hi guys. Probably we have missed this activity, so I start working on it. These are first commits: https://review.openstack.org/#/c/180215/ Regards, Sergey. On 30 April 2015 at 19:55, Matthew Treinish mtrein...@kortar.org wrote: On Thu, Apr 30, 2015 at 05:44:40PM +0100, Louis Taylor wrote:

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

, So IIUC approach #2 may still help to autoscale docker on openstack. I will try that out and post questions on heat irc thanks. Regards Ashish -- *From:* Sergey Kraynev skray...@mirantis.com *Sent:* Friday, April 17, 2015 7:01 PM *To:* OpenStack

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

Hi, Ashish. Honestly I am not familiar with most part of these ways, but can add more information from Heat side (item 2). I am surprised, that you have missed Heat autoscaling mechanism (You should look it :) ). It's one of the important part of Heat project. It allows to scale vms/stacks by

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

hypervisor something similar to this ( https://github.com/openstack/ceilometer/tree/master/ceilometer/compute/virt ). Regards Ashish -- *From:* Sergey Kraynev skray...@mirantis.com *Sent:* Friday, April 17, 2015 8:12 PM *To:* OpenStack Development Mailing List

[openstack-dev] [Heat][Horizon] What we can do for Heat in Horizon else?

Hi community. I want to ask feedback from our Heat team and also involve Horizon team in this discussion. AFAIK during Kilo was implemented bp: https://blueprints.launchpad.net/horizon/+spec/heat-ui-improvement This bp add more base Heat functionality to Horizon. I asked some ideas from Heat

Re: [openstack-dev] [Heat] [Ceilometer] [rc1] bug is unresolved due to requirements freeze

Hi Guys. A couple of concerns: #1 - would have been really nice if the commit message for the review included the above block of text. The current commit message is not clear that Heat *can not* work. I will update commit message regarding info mentioned in this thread. #2 - why

Re: [openstack-dev] [Heat] Stepping down from core

Thank you for the great contribution. Good luck in your new endeavors :) Regards, Sergey. On 27 February 2015 at 23:23, Jeff Peeler jpee...@redhat.com wrote: As discussed during the previous Heat meeting, I'm going to be stepping down from core on the Heat project. My day to day focus is

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

I really like some benefits of this approach: - easy use in functional tests (did not require additional job) - every user can try from this moment - we can use both code ways in the same time without service restarting So I really close to give my +1, if someone give answers on questions from

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

+1 Regards, Sergey. On 28 January 2015 at 10:52, Pavlo Shchelokovskyy pshchelokovs...@mirantis.com wrote: +1 Pavlo Shchelokovskyy Software Engineer Mirantis Inc www.mirantis.com On Wed, Jan 28, 2015 at 8:26 AM, Thomas Herve thomas.he...@enovance.com wrote: Hi all After having

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

On 24 January 2015 at 00:00, Zane Bitter zbit...@redhat.com wrote: 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

Re: [openstack-dev] [heat] Remove deprecation properties

that) = subnet_id } 4. Add migration mechanism: When user use old template, property automatically translated to the new name. Regards, Sergey. On 19 January 2015 at 14:51, Sergey Kraynev skray...@mirantis.com wrote: On 19 January 2015 at 05:13, Angus Salkeld asalk...@mirantis.com wrote: On Fri, Jan 16

Re: [openstack-dev] [heat] Remove deprecation properties

On 19 January 2015 at 05:13, Angus Salkeld asalk...@mirantis.com wrote: On Fri, Jan 16, 2015 at 11:10 PM, Sergey Kraynev skray...@mirantis.com wrote: Steve, Thanks for the feedback. On 16 January 2015 at 15:09, Steven Hardy sha...@redhat.com wrote: On Thu, Dec 25, 2014 at 01:52:43PM +0400

Re: [openstack-dev] [heat] Remove deprecation properties

Steve, Thanks for the feedback. On 16 January 2015 at 15:09, Steven Hardy sha...@redhat.com wrote: On Thu, Dec 25, 2014 at 01:52:43PM +0400, Sergey Kraynev wrote: Hi all. In the last time we got on review several patches, which removes old deprecation properties [1

[openstack-dev] [heat] Remove deprecation properties

Hi all. In the last time we got on review several patches, which removes old deprecation properties [1], and one mine [2]. The aim is to delete deprecated code and redundant tests. It looks simple, but the main problem, which we met, is backward compatibility. F.e. user has created resource

Re: [openstack-dev] [Heat] Nominating Pavlo Shchelokovskyy for heat-core

+1 Regards, Sergey. On 7 October 2014 00:41, Zane Bitter zbit...@redhat.com wrote: I'd like to propose that we add Pavlo Shchelokovskyy to the heat-core team. Pavlo has been a consistently active member of the Heat community - he's a regular participant in IRC and at meetings, has been

Re: [openstack-dev] [heat] heat.conf.sample is not up to date

Mike, I had same problem some time ago. The problem was that I had a vm with installed devstack and file /etc/hosts contained string: 127.0.0.1 localhost ubuntu and changing it to: 127.0.0.1 localhost helped me. So we should have not any symbols (names) after localhost. I am not

Re: [openstack-dev] [Heat] Live update of openstack

Added tag Heat Regards, Sergey. On 1 August 2014 09:52, Manickam, Kanagaraj kanagaraj.manic...@hp.com wrote: Hi, This mail is generic to all openstack service and explained the problem with respect to heat here. I have come across the situation where, updates are involved in the

[openstack-dev] [heat] Uniform style of README file for contrib resources

Hello guys. In the last time I meet again change related with changing content of README for Docker resource. https://review.openstack.org/#/c/110541/ https://review.openstack.org/#/c/101144/ Both changes try to improve current description. I looked on other README files in contrib directories

Re: [openstack-dev] [heat] Uniform style of README file for contrib resources

On 30 July 2014 16:21, Angus Salkeld angus.salk...@rackspace.com wrote: On Wed, 2014-07-30 at 13:41 +0400, Sergey Kraynev wrote: Hello guys. In the last time I meet again change related with changing content of README for Docker resource. https://review.openstack.org/#/c/110541

Re: [openstack-dev] [Heat] Upwards-compatibility for HOT

On 8 July 2014 01:25, Zane Bitter zbit...@redhat.com wrote: With the Icehouse release we announced that there would be no further backwards-incompatible changes to HOT without a revision bump. However, I notice that we've already made an upward-incompatible change in Juno:

Re: [openstack-dev] [heat] Sergey Kraynev for heat-core

Thanks you everyone for the chance to join to this awesome team! It's honor for me and I hope, that my 5 cents will help to make Heat even better :) Regards, Sergey. On 27 June 2014 02:08, Steve Baker sba...@redhat.com wrote: I'd like to nominate Sergey Kraynev for heat-core. His reviews

[openstack-dev] Uniform name for logger in projects

Hello, community. I hope, that most of your know, that a bug with name Log debugs should not have translations (f.e. [1], [2], [3]) was recently raised in several projects. The reason for this work is related with the following concerns [4]. There is a special check that is used (or will be used

Re: [openstack-dev] [Heat][Nova][Neutron]Detach interface will delete the port

Hello Huang. You are right, that this problem is presented in networks update for OS::Nova::Server. I have known about it, and I wanted to discuss it with Steve Baker, but possibly forgot to do it. Thank you, that you raise this thread. About issue. The cause why it happens is simple: when nova

Re: [openstack-dev] [Heat][Nova][Neutron]Detach interface will delete the port

wrote: *发件人:* Sergey Kraynev [mailto:skray...@mirantis.com] *发送时间:* 2014年4月17日 15:35 *收件人:* OpenStack Development Mailing List (not for usage questions) *主题:* Re: [openstack-dev] [Heat][Nova][Neutron]Detach interface will delete the port Hello Huang. You are right, that this problem

[openstack-dev] [Heat][Neutron] Refactoring heat LBaaS architecture according Neutron API

Hello community. I'd like to discuss feature of Neutron LBaaS in Heat. Currently Heat resources are not identical to Neutron's. There are four resources here: 'OS::Neutron::HealthMonitor' 'OS::Neutron::Pool' 'OS::Neutron::PoolMember' 'OS::Neutron::LoadBalancer'