Fuel for OpenStack

How To Patch Fuel 11

Asked by John T Johnson

There are a lot of bugs and bug fixes that are shown to be completed for Openstack-Fuel. However, there's no mention in any documentation or forums that I can find that gives a way to install these fixes.

I am having a tremendous amount of problems installing Fuel - I've tried Fuel 9.x to 12.x on a Dell FX2 with over 100 fuel installation attempts (no exaggeration). I've received more than 30 different errors during deployment of an environment with only a Controller and 1 Compute node in addition to the Fuel-Master (FYI... Every networking check has passed). I'm currently focusing on Fuel 11 expecting that it's been out long enough for most of the bugs have been worked out. I think I'm wrong. However, the bugs that I see fixed in LaunchPad, I see no way to apply them.

These fixes needs to be moved to the Openstack-Fuel site with version numbers incremented. How else are we to determine what level of patches we're on. Additionally, the Openstack-Fuel Docs site - probably the Admin or User guide, needs detailed, step-by-step documentation showing the patching process, execution and expected results.

It it my understanding that Fuel is no longer a viable tool for OpenStack deployments and now that Mirantis will no longer offer any support or open their forums to the public, I feel this is a rapidly dying product.

Can someone help change my opinion and help me out on this?

Thanks,
John

Question information

Language:
English Edit question
Status:
Answered
For:
Fuel for OpenStack Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said : 		#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
John T Johnson (jt.johnson) said : 		#2

Anyone? For this to be a viable product, there needs to be an active support arm so could someone please help me with this question?

Revision history for this message
Fabrizio Soppelsa (fsoppelsa) said : 		#3

Right: Fuel is not supported by Mirantis anymore.

Revision history for this message
Hey Chang (changhey) said : 		#4

John,

There are few links which can explain the current situation:
According to the mailing list most of the engineers who developed Fuel were from Russia and Ukraine.
https://www.mirantis.com/blog/a-hard-road-from-dev-to-ops/

https://review.openstack.org/#/c/475721/
http://stackalytics.com/?module=fuel-group&release=queens

There are still few folks on mailing list who can help you with your issue, but they respond with a long delay.
From my exp Fuel 9.x is the most stable release, I would suggest to stick with that, or switch to OpenStack Ansible, which is not an alternative, but at least it's supported.

Revision history for this message
Collin M. (ziggit) said : 		#5

I definitely have to agree with the 9.x suggestion. Specifically the 9.2 release. Our 9.x releases have been my favorite to work with of the official Mirantis Fuel releases, and the 9.2 release really just knocks it out of the park. Things like the live visual representation of the task graph is really handy for quickly identifying the step a deploy is failing on.

Have you tried running the provisioning step separate from the deploy step, and manually attempted to sync ntp before running the deploy process? You can also tell Fuel to skip certain tasks if you start the deploy from the CLI. Running specific tasks is a pretty powerful way to kick Fuel around a bit, and the --help options in the Fuel CLI are really well documented, and include examples.

Revision history for this message
John T Johnson (jt.johnson) said : 		#6

Thank you for the suggestions. I will certainly take them under consideration. I feel that the OpenStack-Ansible effort has the most promise at this point. Too bad too. We were really looking for Fuel to help with things like upgrades and deployments.

Can you help with this problem?

Provide an answer of your own, or ask John T Johnson for more information if necessary.

To post a message you must log in.