Re: [openstack-dev] [all] grenade with external plugins for the big tent - how to use
On Sun, Jun 28, 2015 at 2:02 PM, Chris Dent chd...@redhat.com wrote: I started extracting ceilometer from devstack into its own plugin. This is working in local tests. It revealed that it would likely be problematic without there also being a grenade plugin. So I started that too. I should be able to look at the patches below this afternoon, but a couple of thoughts real quick... You might need to do this in the other order, ie build the celio plugin for Grenade first because it will need to make sure the right bits are included for the target phase, which doesn't use stack.sh and the DevStack plugin support. The Grenade plugin can handle both, looking to see if the target DevStack config has Celiometer set for an external plugin, and if so include the right bits otherwise handle the existing in-repo stuff. The DevStack plugin shouldn't change too much re function names, so once the right includes are in place it should go smoothly. Most of the trouble we've seen is getting the right things included in the target GRenade phase. I'll loop back on this later today (hopefully) and see how close I really am here... ;) dt -- Dean Troyer dtro...@gmail.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
Re: [openstack-dev] [all] grenade with external plugins for the big tent - how to use
On Thu, 11 Jun 2015, Sean Dague wrote: And... you should be good to go. Additional questions on moving forward, or clarifications in the documentation, can be handled on this thread or in the #openstack-qa channel. I finally got started on this today but am having some issues, likely because I am trying to do too many things at once. I started extracting ceilometer from devstack into its own plugin. This is working in local tests. It revealed that it would likely be problematic without there also being a grenade plugin. So I started that too. Questions: * Is it necessary for the plugins to merge to master before testing can completely or is there a clean way to reference the plugins before they have merged? * How do branches come into play in any of this, if at all? * Are there particular issues that come up with projects like Ceilometer where the goal is to move an existing project out of both devstack and grenade? Links to the various related reviews below. I'm sure I've gotten parts wrong and missed bits, but I figured I'd get starting points in place and iterate. There is quite a stack of interdependent patches making this go, they can all be found by starting at the devstack change which removes ceilometer https://review.openstack.org/#/c/196383/ The other patches are: * The actual devstack plugin for ceilo: https://review.openstack.org/#/c/196384/ * Setting the plugins in project config: https://review.openstack.org/#/c/196446/ * The start of the grenade plugin: https://review.openstack.org/#/c/196441/ * Removing ceilometer from grenade: https://review.openstack.org/#/c/196448/ Thanks! -- Chris Dent tw:@anticdent freenode:cdent https://tank.peermore.com/tanks/cdent __ 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] [all] grenade with external plugins for the big tent - how to use
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 that's nearly ready to land (still sorting out an issue because heat's cli commands aren't console entry points) - https://review.openstack.org/#/c/188148/. Much appreciation to the Heat team for patience in getting here, and for helping sort out all the infrastructure. For additional projects to work the basic pattern is as follows: * create a custom grenade job for your project * write a grenade plugin following the instructions here - https://github.com/openstack-dev/grenade/blob/master/PLUGINS.rst - put it in your project tree. * export the following in your project-config definition export GRENADE_PLUGINRC enable_grenade_plugin PROJECTNAME git://git.openstack.org/openstack/PROJECTNAME And... you should be good to go. Additional questions on moving forward, or clarifications in the documentation, can be handled on this thread or in the #openstack-qa channel. -Sean -- Sean Dague http://dague.net __ 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] [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 s...@dague.net 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 that's nearly ready to land (still sorting out an issue because heat's cli commands aren't console entry points) - https://review.openstack.org/#/c/188148/. Much appreciation to the Heat team for patience in getting here, and for helping sort out all the infrastructure. For additional projects to work the basic pattern is as follows: * create a custom grenade job for your project * write a grenade plugin following the instructions here - https://github.com/openstack-dev/grenade/blob/master/PLUGINS.rst - put it in your project tree. * export the following in your project-config definition export GRENADE_PLUGINRC enable_grenade_plugin PROJECTNAME git://git.openstack.org/openstack/ http://git.openstack.org/openstack/PROJECTNAME And... you should be good to go. Additional questions on moving forward, or clarifications in the documentation, can be handled on this thread or in the #openstack-qa channel. This is really pretty awesome! Very excited that this will allow projects to host their own grenade plugins in their own repositories. Similar to the devstack plugins, I think this is a huge win! Great work! +1, I know this big tent transition is creating a lot of work for the cross-project teams in the short term, but I think this will pay huge dividends in the future in increasing the capacity of our community to innovate across the board. Many thanks to Sean and everyone else involved in making this a reality :) cheers, Zane. __ 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] [all] grenade with external plugins for the big tent - how to use
On Thu, Jun 11, 2015 at 6:11 AM, Sean Dague 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 that's nearly ready to land (still sorting out an issue because heat's cli commands aren't console entry points) - https://review.openstack.org/#/c/188148/. Much appreciation to the Heat team for patience in getting here, and for helping sort out all the infrastructure. For additional projects to work the basic pattern is as follows: * create a custom grenade job for your project * write a grenade plugin following the instructions here - https://github.com/openstack-dev/grenade/blob/master/PLUGINS.rst - put it in your project tree. * export the following in your project-config definition export GRENADE_PLUGINRC enable_grenade_plugin PROJECTNAME git://git.openstack.org/openstack/PROJECTNAME And... you should be good to go. Additional questions on moving forward, or clarifications in the documentation, can be handled on this thread or in the #openstack-qa channel. This is really pretty awesome! Very excited that this will allow projects to host their own grenade plugins in their own repositories. Similar to the devstack plugins, I think this is a huge win! Great work! Kyle -Sean -- Sean Dague http://dague.net __ 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
