Re: [Openstack] Nova idear, thoughts wanted.
Sweet hotness, haha. I gotta get more involved with whats going on there :-) On 5/3/12 8:12 AM, "Sandy Walsh" wrote: Agreed. That's largely the effort of the Orchestration group. From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of Joshua Harlow [harlo...@yahoo-inc.com] Sent: Thursday, May 03, 2012 12:35 AM To: openstack Subject: [Openstack] Nova idear, thoughts wanted. Hi all, I was thinking today about how nova-compute could become more pluggable. I was wondering if there had been any thought into how say each method, say in the compute-manager could almost become a set of stages in a pipeline. For example the run instance method is really doing the following steps: run_instance: steps: - check_instance_not_already_created - check_image_size - notify_about_instance_usage - instance_update(BUILDING) - allocate_network - prep_block_device - spawn: - instance_update(BUILD) - driver_spawn - instance_update(ACTIVE) on_failure: - deallocate_network This reminds me slightly of what devstackpy (to be renamed soon) does but instead of via code, actions are partially defined via config/persona/ Now say if the above steps are plugins (similar to say a paste pipeline) then it becomes easy for company Y to add special sauce Z before or after stage W. I was just wondering what people thought about this. It sort of makes nova more of a orchestrator that loads plugins that perform various pipelines, where in nova's case those pipelines are VM related. Comments welcome. This might already have been thought of, but if so, that's ok also :-) -Josh ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Nova idear, thoughts wanted.
Agreed. That's largely the effort of the Orchestration group. From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of Joshua Harlow [harlo...@yahoo-inc.com] Sent: Thursday, May 03, 2012 12:35 AM To: openstack Subject: [Openstack] Nova idear, thoughts wanted. Hi all, I was thinking today about how nova-compute could become more pluggable. I was wondering if there had been any thought into how say each method, say in the compute-manager could almost become a set of stages in a pipeline. For example the run instance method is really doing the following steps: run_instance: steps: - check_instance_not_already_created - check_image_size - notify_about_instance_usage - instance_update(BUILDING) - allocate_network - prep_block_device - spawn: - instance_update(BUILD) - driver_spawn - instance_update(ACTIVE) on_failure: - deallocate_network This reminds me slightly of what devstackpy (to be renamed soon) does but instead of via code, actions are partially defined via config/persona/ Now say if the above steps are plugins (similar to say a paste pipeline) then it becomes easy for company Y to add special sauce Z before or after stage W. I was just wondering what people thought about this. It sort of makes nova more of a orchestrator that loads plugins that perform various pipelines, where in nova’s case those pipelines are VM related. Comments welcome. This might already have been thought of, but if so, that’s ok also :-) -Josh ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Nova idear, thoughts wanted.
Hi all, I was thinking today about how nova-compute could become more pluggable. I was wondering if there had been any thought into how say each method, say in the compute-manager could almost become a set of stages in a pipeline. For example the run instance method is really doing the following steps: run_instance: steps: - check_instance_not_already_created - check_image_size - notify_about_instance_usage - instance_update(BUILDING) - allocate_network - prep_block_device - spawn: - instance_update(BUILD) - driver_spawn - instance_update(ACTIVE) on_failure: - deallocate_network This reminds me slightly of what devstackpy (to be renamed soon) does but instead of via code, actions are partially defined via config/persona/ Now say if the above steps are plugins (similar to say a paste pipeline) then it becomes easy for company Y to add special sauce Z before or after stage W. I was just wondering what people thought about this. It sort of makes nova more of a orchestrator that loads plugins that perform various pipelines, where in nova's case those pipelines are VM related. Comments welcome. This might already have been thought of, but if so, that's ok also :-) -Josh ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
