Re: [openstack-dev] Announcing Fuel
Thanks for support, as a starting point we have chosen Ironic - we really want to see it as a replacement of Fuel's existing provisioning layer, with an intention of participation and delivery of many features which we already know from the real-world installations with Fuel. We are trying to be more test-driven, so starting our contributions as proof of concept for functional testing framework for Ironic: https://review.openstack.org/#/c/62410/2, see the description in README file: https://review.openstack.org/#/c/62410/2/irci/README.md Distributed envs testing, especially PXE booting is the area of our interest. Next, we plan to collaboratively work on torrent-based provisioning driver. Fuel UI Tuskar UI are also very interesting topic. Mark - thanks for provided links. Let us get a few cycles to research what you have so far and get back to you. On Fri, Dec 13, 2013 at 6:11 PM, Liz Blanchard lsure...@redhat.com wrote: On Dec 13, 2013, at 8:04 AM, Jaromir Coufal jcou...@redhat.com wrote: On 2013/12/12 15:31, Mike Scherbakov wrote: Folks, Most of you by now have heard of Fuel, which we’ve been working on as a related OpenStack project for a period of time -https://github.com/stackforge/fuel-mainsee https://launchpad.net/fueland https://wiki.openstack.org/wiki/Fuel. The aim of the project is to provide a distribution agnostic and plug-in agnostic engine for preparing, configuring and ultimately deploying various “flavors” of OpenStack in production. We’ve also used Fuel in most of our customer engagements to stand up an OpenStack cloud. ... We’d love to open discussion on this and hear everybody’s thoughts on this direction. Hey Mike, it sounds all great. I'll be very happy to discuss all the UX efforts going on in TripleO/Tuskar UI together with intentions and future steps of Fuel. +1. The Fuel wizard has some great UX ideas to bring to our thoughts around deployment in the Tuskar UI! Great to hear these will be brought together, Liz Cheers -- Jarda --- Jaromir Coufal (jcoufal) --- OpenStack User Experience --- IRC: #openstack-ux (at FreeNode) --- Forum: http://ask-openstackux.rhcloud.com --- Wiki: https://wiki.openstack.org/wiki/UX ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Mike Scherbakov #mihgen ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Announcing Fuel
On 17 December 2013 09:59, Mike Scherbakov mscherba...@mirantis.com wrote: Thanks for support, as a starting point we have chosen Ironic - we really want to see it as a replacement of Fuel's existing provisioning layer, with an intention of participation and delivery of many features which we already know from the real-world installations with Fuel. We are trying to be more test-driven, so starting our contributions as proof of concept for functional testing framework for Ironic: https://review.openstack.org/#/c/62410/2, see the description in README file: https://review.openstack.org/#/c/62410/2/irci/README.md Distributed envs testing, especially PXE booting is the area of our interest. Next, we plan to collaboratively work on torrent-based provisioning driver. Cool. Rather than torrents you may prefer a multicast driver, it should be about 50% network utilisation, linear IO for the target disk - much better. Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Announcing Fuel
On Dec 13, 2013, at 8:04 AM, Jaromir Coufal jcou...@redhat.com wrote: On 2013/12/12 15:31, Mike Scherbakov wrote: Folks, Most of you by now have heard of Fuel, which we’ve been working on as a related OpenStack project for a period of time -https://github.com/stackforge/fuel-mainsee https://launchpad.net/fueland https://wiki.openstack.org/wiki/Fuel. The aim of the project is to provide a distribution agnostic and plug-in agnostic engine for preparing, configuring and ultimately deploying various “flavors” of OpenStack in production. We’ve also used Fuel in most of our customer engagements to stand up an OpenStack cloud. ... We’d love to open discussion on this and hear everybody’s thoughts on this direction. Hey Mike, it sounds all great. I'll be very happy to discuss all the UX efforts going on in TripleO/Tuskar UI together with intentions and future steps of Fuel. +1. The Fuel wizard has some great UX ideas to bring to our thoughts around deployment in the Tuskar UI! Great to hear these will be brought together, Liz Cheers -- Jarda --- Jaromir Coufal (jcoufal) --- OpenStack User Experience --- IRC: #openstack-ux (at FreeNode) --- Forum: http://ask-openstackux.rhcloud.com --- Wiki: https://wiki.openstack.org/wiki/UX ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Announcing Fuel
Mike, It's great that we are continuing to align fuel with TripleO. I've been toying with the idea of using TripleO components and CEPH to enhance our CI infra for a while now, and this announcement has encouraged me to write it down. I've proposed a BP for Super fast deploy CI that would help us perform CI better by accelerate fuel CI testing by taking reasonable shortcuts integrating with several existing components like TripleO and CEPH. Blueprint: https://blueprints.launchpad.net/fuel/+spec/fuel-superfastdeploy-ci Pad Spec: https://etherpad.openstack.org/p/bp-fuel-superfastdeploy-ci -- Andrew Woodward Mirantis On Thu, Dec 12, 2013 at 6:31 AM, Mike Scherbakov mscherba...@mirantis.comwrote: Folks, Most of you by now have heard of Fuel, which we’ve been working on as a related OpenStack project for a period of time - https://github.com/stackforge/fuel-mainsee https://launchpad.net/fueland https://wiki.openstack.org/wiki/Fuel. The aim of the project is to provide a distribution agnostic and plug-in agnostic engine for preparing, configuring and ultimately deploying various “flavors” of OpenStack in production. We’ve also used Fuel in most of our customer engagements to stand up an OpenStack cloud. At the same time, we’ve been actively involved with TripleO, which we believe to be a great effort in simplifying deployment, operations, scaling (and eventually upgrading) of OpenStack. Per our discussions with core TripleO team during the Icehouse summit, we’ve uncovered that while there are certain areas of collision, most of the functionality in TripleO and Fuel is complementary. In general, Fuel helps solve many problems around “step zero” of setting up an OpenStack environment, such as auto-discovery and inventory of bare metal hardware, pre-deployment post-deployment environment checks, and wizard-driven web-based configuration of OpenStack flavors. At the same time, TripleO has made great progress in deployment, scaling and operations (with Tuskar). We’d like to propose an effort for community consideration to bring the two initiatives closer together to eventually arrive at a distribution agnostic, community supported framework covering the entire spectrum of deployment, management and upgrades; from “step zero” to a fully functional and manageable production-grade OpenStack environment. To that effect, we propose the following high-level roadmap plans for this effort: - Keep and continue to evolve bare-metal discovery and inventory module of Fuel, tightly integrating it with Ironic. - Keep and continue to evolve Fuel’s wizard-driven OpenStack flavor configurator. In the near term we’ll work with the UX team to unify the user experience across Fuel, TripleO and Tuskar. We are also thinking about leveraging diskimagebuilder. - Continue to evolve Fuel’s pre-deployment (DHCP, L2 connectivity checks) and post-deployment validation checks in collaboration with the TripleO and Tempest teams. - Eventually replace Fuel’s current orchestration engine https://github.com/stackforge/fuel-astute/ with Heat We’d love to open discussion on this and hear everybody’s thoughts on this direction. -- Mike Scherbakov Fuel Engineering Lead #mihgen ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
