Docs should clearly say that fuel-menu is not meant to be used after installation

Registered by Victor Denisov

Users constantly try to use fuel-menu after installation. It breaks a lot of things and they even forget to mention they used it.

Consider even disabling this script after installation or presenting a big warning.

Dev response: Fuelmenu can be used to update config and redeploy, but not all items can be changed after initial deployment without resetting the entire Fuel environment. Initially, there was meant to be a limited post-deploy mode where you could change some network settings, DNS, and NTP config, but it was never implemented. Updating docs is a good short term solution for 5.1.

Blueprint information

Status:
Complete
Approver:
Dmitry Pyzhov
Priority:
Low
Drafter:
Victor Denisov
Direction:
Needs approval
Assignee:
Matthew Mosesohn
Definition:
Obsolete
Series goal:
Accepted for 5.1.x
Implementation:
Unknown
Milestone target:
None
Completed by
Matthew Mosesohn

Related branches

Sprints

Whiteboard

These warnings were already completed by Miroslav Anashkin. There are clear warnings now in the user guide about not running Fuel Setup after deployment and that it will break configuration.

[Dmitry Borodaenko 2015-01-12]
Documented in Fuel User Guide:
http://docs.mirantis.com/openstack/fuel/fuel-6.0/user-guide.html#changing-pxe-network-parameters-during-installation

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.