[openstack-dev] [heat] Network name as a Server properties
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? I expected it to be like image under OS::Nova::Server: The property name should be network, and it should accept both id and name Thanks Stotland Limor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Global Requirements] Adding apscheduler to global requirements
From: Renat Akhmerov rakhme...@mirantis.com Subject: Re: [openstack-dev] [Global Requirements] Adding apscheduler to global requirements Date: 3 Jun 2015 16:48:08 GMT+6 To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Thanks Doug, got it. Limor, can you please explain why exactly do you need this library? This is the only live library I found that enable creating scheduled job in seconds granularity. I am planning on using : BackgroundScheduler (apscheduler.schedulers.background). Doug, Does Oslo have this ability? Renat Akhmerov @ Mirantis Inc. On 02 Jun 2015, at 18:45, Doug Hellmann d...@doughellmann.com wrote: Excerpts from Renat Akhmerov's message of 2015-06-02 18:26:40 +0600: Any comments from TC on that? What is the typical procedure of accepting new libs into global requirements? There is a requirements management team, and usually we would want a patch to the list in openstack/requirements, with some description of the need for the package, especially which projects are going to use it and why no existing package with similar functionality is suitable. There are more details about the evaluation criteria in http://git.openstack.org/cgit/openstack/requirements/tree/README.rst Doug Thanks Renat Akhmerov @ Mirantis Inc. On 02 Jun 2015, at 18:11, BORTMAN, Limor (Limor) limor.bort...@alcatel-lucent.com wrote: Hi all, As part as a BP in mistral (Add seconds granularity in cron-trigger execute[1]) I would like to add apscheduler (Advanced Python Scheduler[2]) to the openstack Global Requirements. Any objections? [1] https://blueprints.launchpad.net/mistral/+spec/cron-trigger-seconds-granularity [2] https://apscheduler.readthedocs.org/en/latest/ Thanks Stotland Limor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [mistral] Proposing Lingxian Kong as a core reviewer
+1 From: W Chan [mailto:m4d.co...@gmail.com] Sent: Tuesday, June 23, 2015 12:07 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [mistral] Proposing Lingxian Kong as a core reviewer +1 Lingxian, keep up with the good work. :D __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Mistral] Proposal for the Resume Feature
+1, I just have one question. Do we want to able resume for WF in error state? I mean isn't real resume it should be more of a rerun, don't you think? So in an error state we will create new executor and just re run it Thanks Limor -Original Message- From: Lingxian Kong [mailto:anlin.k...@gmail.com] Sent: Tuesday, June 16, 2015 5:47 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Mistral] Proposal for the Resume Feature Thanks Winson for the write-up, very detailed infomation. (the format was good) I'm totally in favor of your idea, actually, I really think you proposal is complementary to my proposal in https://etherpad.openstack.org/p/vancouver-2015-design-summit-mistral, please see 'Workflow rollback/recovery' section. What I wanna do is configure some 'checkpoints' throughout the workflow, and if some task failed, we could rollback the execution to some checkpoint, and resume the whole workflow after we have fixed some problem, seems like the execution has never been failed before. It's just a initial idea, I'm waiting for our discussion to see if it really makes sense to users, to get feedback, then we can talk about the implementation and cooperation. On Tue, Jun 16, 2015 at 7:51 AM, W Chan m4d.co...@gmail.com wrote: Resending to see if this fixes the formatting for outlines below. I want to continue the discussion on the workflow resume feature. Resuming from our last conversation @ http://lists.openstack.org/pipermail/openstack-dev/2015-March/060265.h tml. I don't think we should limit how users resume. There may be different possible scenarios. User can fix the environment or condition that led to the failure of the current task and the user wants to just re-run the failed task. Or user can actually fix the environment/condition which include fixing what the task was doing, then just want to continue the next set of task(s). The following is a list of proposed changes. 1. A new CLI operation to resume WF (i.e. mistral workflow-resume). A. If no additional info is provided, assume this WF is manually paused and there are no task/action execution errors. The WF state is updated to RUNNING. Update using the put method @ ExecutionsController. The put method checks that there's no task/action execution errors. B. If WF is in an error state i. To resume from failed task, the workflow-resume command requires the WF execution ID, task name, and/or task input. ii. To resume from failed with-items task a. Re-run the entire task (re-run all items) requires WF execution ID, task name and/or task input. b. Re-run a single item requires WF execution ID, task name, with-items index, and/or task input for the item. c. Re-run selected items requires WF execution ID, task name, with-items indices, and/or task input for each items. - To resume from the next task(s), the workflow-resume command requires the WF execution ID, failed task name, output for the failed task, and a flag to skip the failed task. 2. Make ERROR - RUNNING as valid state transition @ is_valid_transition function. 3. Add a comments field to Execution model. Add a note that indicates the execution is launched by workflow-resume. Auto-populated in this case. 4. Resume from failed task. A. Re-run task with the same task inputs POST new action execution for the task execution @ ActionExecutionsController B. Re-run task with different task inputs POST new action execution for the task execution, allowed for different input @ ActionExecutionsController 5. Resume from next task(s). A. Inject a noop task execution or noop action execution (undecided yet) for the failed task with appropriate output. The spec is an adhoc spec that copies conditions from the failed task. This provides some audit functionality and should trigger the next set of task executions (in case of branching and such). __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Regards! --- Lingxian Kong __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Global Requirements] Adding apscheduler to global requirements
Hi all can anybody please take a look on my PR[1]? [1] https://review.openstack.org/#/c/189564/ Thanks Limor -Original Message- From: BORTMAN, Limor (Limor) [mailto:limor.bort...@alcatel-lucent.com] Sent: Wednesday, June 03, 2015 2:28 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Global Requirements] Adding apscheduler to global requirements From: Renat Akhmerov rakhme...@mirantis.com Subject: Re: [openstack-dev] [Global Requirements] Adding apscheduler to global requirements Date: 3 Jun 2015 16:48:08 GMT+6 To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Thanks Doug, got it. Limor, can you please explain why exactly do you need this library? This is the only live library I found that enable creating scheduled job in seconds granularity. I am planning on using : BackgroundScheduler (apscheduler.schedulers.background). Doug, Does Oslo have this ability? Renat Akhmerov @ Mirantis Inc. On 02 Jun 2015, at 18:45, Doug Hellmann d...@doughellmann.com wrote: Excerpts from Renat Akhmerov's message of 2015-06-02 18:26:40 +0600: Any comments from TC on that? What is the typical procedure of accepting new libs into global requirements? There is a requirements management team, and usually we would want a patch to the list in openstack/requirements, with some description of the need for the package, especially which projects are going to use it and why no existing package with similar functionality is suitable. There are more details about the evaluation criteria in http://git.openstack.org/cgit/openstack/requirements/tree/README.rst Doug Thanks Renat Akhmerov @ Mirantis Inc. On 02 Jun 2015, at 18:11, BORTMAN, Limor (Limor) limor.bort...@alcatel-lucent.com wrote: Hi all, As part as a BP in mistral (Add seconds granularity in cron-trigger execute[1]) I would like to add apscheduler (Advanced Python Scheduler[2]) to the openstack Global Requirements. Any objections? [1] https://blueprints.launchpad.net/mistral/+spec/cron-trigger-seconds-granularity [2] https://apscheduler.readthedocs.org/en/latest/ Thanks Stotland Limor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Global Requirements] Adding apscheduler to global requirements
Hi all, As part as a BP in mistral (Add seconds granularity in cron-trigger execute[1]) I would like to add apscheduler (Advanced Python Scheduler[2]) to the openstack Global Requirements. Any objections? [1] https://blueprints.launchpad.net/mistral/+spec/cron-trigger-seconds-granularity [2] https://apscheduler.readthedocs.org/en/latest/ Thanks Stotland Limor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] puppet-mistral
Hi all, I am trying to push mistral puppet but so far no one from the puppet team take a look. can anyone please take a look ? Thanks Limor Stotland ALCATEL-LUCENT SENIOR SOFTWARE ENGINEER CLOUDBAND BUSINESS UNIT 16 Atir Yeda St. Kfar-Saba 44643, ISRAEL T: +972 (0) 9 793 3166 M: +972 (0) 54 585 3736 limor.bort...@alcatel-lucent.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [puppet]puppet-mistral
Hi all, I am trying to push mistral puppet but so far no one from the puppet team take a look. can anyone please take a look ? Thanks Limor Stotland ALCATEL-LUCENT SENIOR SOFTWARE ENGINEER CLOUDBAND BUSINESS UNIT 16 Atir Yeda St. Kfar-Saba 44643, ISRAEL T: +972 (0) 9 793 3166 M: +972 (0) 54 585 3736 limor.bort...@alcatel-lucent.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [puppet]puppet-mistral
Hi all, I have some changes at the end of last week and so far i got no comment on it. can anyone please take a look? https://review.openstack.org/#/c/208457/10 Thanks Thanks Limor Stotland ALCATEL-LUCENT SENIOR SOFTWARE ENGINEER CLOUDBAND BUSINESS UNIT 16 Atir Yeda St. Kfar-Saba 44643, ISRAEL T: +972 (0) 9 793 3166 M: +972 (0) 54 585 3736 limor.bort...@alcatel-lucent.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [opesntack-puppet] mistral puppet
Hi all, I have puppet for mistral and i would like to contribute it. Any objection/comments? Thanks Limor Stotland ALCATEL-LUCENT SENIOR SOFTWARE ENGINEER CLOUDBAND BUSINESS UNIT 16 Atir Yeda St. Kfar-Saba 44643, ISRAEL T: +972 (0) 9 793 3166 M: +972 (0) 54 585 3736 limor.bort...@alcatel-lucent.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [openstack-puppet] mistral puppet
Hi all, I have puppet for mistral and i would like to contribute it. Any objection/comments? Thanks Limor Stotland ALCATEL-LUCENT SENIOR SOFTWARE ENGINEER CLOUDBAND BUSINESS UNIT 16 Atir Yeda St. Kfar-Saba 44643, ISRAEL T: +972 (0) 9 793 3166 M: +972 (0) 54 585 3736 limor.bort...@alcatel-lucent.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
