date:20150209

Re: [openstack-dev] [Mistral] Roll back capabilities execution data context variables in YAML

2015-02-09 Thread Renat Akhmerov

1) Roll back support : I came across few blueprints that talk about the
roll-back support but not sure if they are delivered yet, I wanted to check
if something is there out of the box that I should be aware of. Ofcourse,
roll-back being very specific, I'd expect a user defined action being called
for rolling back, just wondering if there is any construct after (on-error :
) to be used in YAML

Yes, it’s really specific. We ourselves discussed several options on what
facilities we could provide regarding rollbacks. None of the BPs that you’ve
probably seen is implemented yet though and more importantly there haven’t been
any decisions made on that. I think we should start a wider discussion on that.

As far as the idea itself, the whole point is that it may not be required to
implement any specific in addition to existing functionality because from what
we learned we can make a conclusion that most often rollback is a different
workflow. Meaning that rolling back all the tasks in the same but reverse order
(assuming they have a roll back action) doesn’t make too much sense. It’s 100%
true if workflow tasks change some state in a non-revertable manner, for
example. If so then Mistral already has ‘on-error’ clause which could be used
to jump to a task associated with calling a workflow (rollback workflow).

I really wonder what your input on this would be?

2) Execution context predefined ids - Here is what I found that talks about
task and execution ids that I can access (execution context
https://wiki.openstack.org/wiki/Mistral/DSLv2#Predefinted_Values_in_execution_data_context),
it would be great if you could point me to the list of all possible
variables like $.execution_id that are accessible inside the YAML.

Not too many things at this point:
* $.__execution consisting of fields ‘id’, ‘wf_spec’ (workflow specification as
a dictionary), ‘input’ and ‘start_params’ (which can contain some additional
start parameters like ‘task_name’ for reverse workflows and ‘env’ containing
the environment variables or a name of the previously saved environment, but
environments are not officially announced yet).
* $.openstack which contains whatever is listed in the doc (project_id etc.)

This part is slightly changing now and there isn’t still a final doc on that.
It will be created by the end of kilo-3.

Thanks

Renat Akhmerov
@ Mirantis Inc.

__
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] [ceilometer] nova api.fault notification isn't collected by ceilometer

2015-02-09 Thread yuntong


Hi all,
In nova api, a nova api.fault notification will be send out when the 
when there is en error.

http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/__init__.py#n119
but i couldn't find where they are  processed  in ceilometer,
an error notification can be very desired to be collected, do we have 
plan to add this, shall i need a bp to do that ?


-Yuntong


__
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] [nova] FFE request for passing capabilities in the flavor to ironic

2015-02-09 Thread Lucas Alvares Gomes

+1 for FFE. This should be very low risk to Nova since it affects only
the Ironic driver.

On Sun, Feb 8, 2015 at 11:38 AM, Nisha Agarwal
agarwalnisha1...@gmail.com wrote:
Hi wanyen and Nova team,

I support wanyen for this FFE. The code changes are very small and harmless
to Nova. They just provide a way to ironic to comsume inputs given at
flavor.

Regards
Nisha

On Sat, Feb 7, 2015 at 12:33 AM, Hsu, Wan-Yen wan-yen@hp.com wrote:

Hi,

I would like to ask for a feature freeze exception for passing
capabilities in the flavor to Ironic:

https://blueprints.launchpad.net/nova/+spec/pass-flavor-capabilities-to-ironic-virt-driver

Addressed by: https://review.openstack.org/136104
Pass on the capabilities in the flavor to the ironic

Addressed by: https://review.openstack.org/141012
Pass on the capabilities to instance_info

several Ironic Kilo features including secure boot, trusted boot, and
local boot support with partition image are depending on this feature. It
also has impact on Ironic vendor driver’s hardware property introspection
feature.

Code changes to support this spec in Nova ironic virt driver is very
small-

only 31 lines of code (including comments) in
nova/virt/ironic/patcher.py, and 22 lines of code in test_patcher.py.

Please consider approving this FFE. Thanks!

Regards,

wanyen

--
The Secret Of Success is learning how to use pain and pleasure, instead
of having pain and pleasure use you. If You do that you are in control
of your life. If you don't life controls you.

1 2 >

1 - 100 of 108 matches

Mail list logo