Fuel for OpenStack

I think we need to reformulate inscription for successfully stopped deployment

  1. Series newton
  2. Bug #1483329
Bug #1483329 reported by Anastasia Palkina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Triaged
Medium
Fuel Sustaining
Fuel for OpenStack 10.0
Mitaka
Won't Fix
Medium
Fuel Python (Deprecated)
Fuel for OpenStack 9.0
Newton
Triaged
Medium
Fuel Sustaining
Fuel for OpenStack 10.0

Bug Description

Now inscription is:
"Deployment of environment 'test' was successfully stopped. Please reset the environment if you want to redeploy it."

But I think that it is out of date.

After successful stopping of deployment user can just click "Deploy Changes" button. User does not need to reset environment in this case because all settings are available to edit.

So I think that we need to reformulate this inscription.

Revision history for this message
Anastasia Palkina (apalkina) wrote :
Changed in fuel:
importance: Medium → Wishlist
Roman Prykhodchenko (romcheg)
Changed in fuel:
status: New → Confirmed
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

It was done by purpose in order to deal with corner cases, AFAIK. See #1464326

Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

https://bugs.launchpad.net/fuel/+bug/1464326

Igor Shishkin (teran)
Changed in fuel:
milestone: 7.0 → 8.0
Dmitriy Novakovskiy (dnovakovskiy)
tags: added: feature
Revision history for this message
Dmitriy Novakovskiy (dnovakovskiy) wrote :

Here's the current UX:
1. User presses "Stop deployment"
2. Nodes that are not yet in "ready" state go into reboot (for further re-provisioning)
3. Nodes that are in "ready" state are potentially inconsistent - changes made by plugins (that run in post-deployment) might be not yet applied, and never will be (since node is "ready" :))
4. User has no way to troubleshoot nodes, since they went into reboot
5. User is prompted to hit "Reset environment", and then

Here's the target UX that we need to implement:
1. User presses "Stop deployment"
2. Fuel stops execution of all deployment tasks on nodes
3. The nodes that haven't yet executed post-deployment/plugins are not claimed "ready" (some other status has to be established)
4. User is able to press "Deploy changes" after fixing parameters
5. If user presses "Deploy changes" - full puppet rerun is done on all nodes (w/o OS provisioning) to make sure that settings are consistent everywhere
6. If during "Stop deployment" execution there were cases that could lead to inconsistency (e.g. killing puppet w/ -9) - user is provided with hint to Reset env, not to resume via Deploy changes

Alexey Shtokolov (ashtokolov)
Changed in fuel:
importance: Wishlist → Medium
status: Confirmed → Triaged
Dmitry Pyzhov (dpyzhov)
tags: added: area-python
Alexey Shtokolov (ashtokolov)
Changed in fuel:
assignee: Mike Scherbakov (mihgen) → Fuel Python Team (fuel-python)
Revision history for this message
Alexander Kislitsky (akislitsky) wrote :

We passed SCF in 8.0. Moving the bug to 9.0.

Changed in fuel:
milestone: 8.0 → 9.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.