fuel-dev team mailing list archive

[Gleb Galkin <ggalkin@xxxxxxxxxxxx>]

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 <ggalkin@xxxxxxxxxxxx> 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 <
> vsharshov@xxxxxxxxxxxx> 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 <ggalkin@xxxxxxxxxxxx>
>> 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     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> 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