Add commands to operate snapshot template
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Triaged
|
Medium
|
Fuel Sustaining | ||
Mitaka |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
Newton |
Triaged
|
Medium
|
Fuel Sustaining |
Bug Description
Analogously to https:/
We need to be able to operate snapshot template(that is predefined in DUMP in nailgun/
1) Export default template
2) Import custom template
Having this will allow us to have the following workflow:
1. Customer files a ticket
2. We read the description and send him snapshot template.
We probably may customize the template for every ticket, since we want to get additional info depending on what is broken.
3. Client generate a customized snapshot and send it to us.
It is important that snapshot template doesn't contain any environment-
This data is populated by DumpTaks in nailgun/
So we these templates will be universal and suitable for every environemnt.
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
milestone: | none → 6.1 |
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
Changed in fuel: | |
milestone: | 6.1 → 7.0 |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
status: | Won't Fix → Triaged |
no longer affects: | fuel/8.0.x |
tags: | added: area-python |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
But this is what exactly was achieved with https:/ /bugs.launchpad .net/fuel/ +bug/1431240 - you create a snapshot config (as it is in DUMP section of settings.yaml) and user can then create a snapshot:
$ fuel snapshot < custom_ snapshot_ config. yaml