I think there's a lot of value to this feature. It can also be helpful for support/debugging if there's a quick way to load the config of a cloud created by a customer or coworker. I know a diagnostic snapshot can expose this information, but something like a YAML that has all the fields from the UI would be pretty useful.
-Christopher On Fri, Sep 26, 2014 at 12:31 AM, Oleg Gelbukh <[email protected]> wrote: > A clone/copy environment configuration feature could also serve for upgrade > purposes in future. Clone environment doesn't have to include nodes from > original environment, just general settings like IP ranges and enabled > services. > > -Oleg > > On Thu, Sep 25, 2014 at 7:28 PM, Gleb Galkin <[email protected]> wrote: >> >> Vladimir, >> >> Another use case for save/restore: >> What if I need to set up few similar clouds that has little difference? >> If I have save/restore feature I can clone the environment and easily >> change some or I can clone some settings from one FUEL to another. >> >> >> On Thu, Sep 25, 2014 at 11:23 AM, Gleb Galkin <[email protected]> >> wrote: >>> >>> Vladimir, >>> >>> It doesn't help if I have to reinstall FUEL. >>> It soen't help if I have to drop database >>> >>> On Thu, Sep 25, 2014 at 11:21 AM, Vladimir Sharshov >>> <[email protected]> wrote: >>>> >>>> Hi, Gleb. >>>> >>>> What about Reset Environment feature? >>>> >>>> >>>> http://docs.mirantis.com/openstack/fuel/fuel-5.1/user-guide.html#resetting-environment-after-deployment >>>> >>>> >>>> >>>> On Thu, Sep 25, 2014 at 7:09 PM, Gleb Galkin <[email protected]> >>>> wrote: >>>>> >>>>> Hello, >>>>> >>>>> As I wrote before it would be really nice if Fuel can save and restore >>>>> the all settings for environment. I think all the deployment engineers >>>>> want >>>>> this feature. >>>>> In real life we often have to delete environment and set it again. It >>>>> takes a lot of time type the same ip ranges and vlans id? assign the >>>>> network >>>>> interfaces and disks. >>>>> It's be nice if I can save it to some xml file and then restore this in >>>>> new environment. >>>>> >>>>> There is export and import now in CLI but it doesn't help because YAML >>>>> or JSON contain ID that are different for every environment. >>>>> >>>>> >>>>> -- >>>>> Best Regards, >>>>> Gleb Galkin >>>>> OpenStack Deployment Engineer >>>>> >>>>> Mirantis Inc. >>>>> www.mirantis.com >>>>> >>>>> -- >>>>> Mailing list: https://launchpad.net/~fuel-dev >>>>> Post to : [email protected] >>>>> Unsubscribe : https://launchpad.net/~fuel-dev >>>>> More help : https://help.launchpad.net/ListHelp >>>>> >>>> >>> >>> >>> >>> -- >>> Best Regards, >>> Gleb Galkin >>> OpenStack Deployment Engineer >>> >>> Mirantis Inc. >>> www.mirantis.com >> >> >> >> >> -- >> Best Regards, >> Gleb Galkin >> OpenStack Deployment Engineer >> >> Mirantis Inc. >> www.mirantis.com >> >> -- >> Mailing list: https://launchpad.net/~fuel-dev >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~fuel-dev >> More help : https://help.launchpad.net/ListHelp >> > > > -- > Mailing list: https://launchpad.net/~fuel-dev > Post to : [email protected] > Unsubscribe : https://launchpad.net/~fuel-dev > More help : https://help.launchpad.net/ListHelp > -- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
