I like proposal from comment #4 more. It is more obvious interface, imho.
Yes, command will be changed, but we in support have a script with with instructions on how to generate snapshot. So we still will be able to request snapshot using fuel snapshot for both, old and new versions. But for new versions file jsut will be stored in /var/www/nailgiun/dump
If default behaviour of of 'fuel snapshot' will be not to download, can we make output like this:
[root@fuel remote]# fuel snapshot
Generating dump...
Dump is stored at /var/www/nailgun/dump on fuel master node
I like proposal from comment #4 more. It is more obvious interface, imho. nailgiun/ dump
Yes, command will be changed, but we in support have a script with with instructions on how to generate snapshot. So we still will be able to request snapshot using fuel snapshot for both, old and new versions. But for new versions file jsut will be stored in /var/www/
Right now output is the following: 10.20.15. 2:8000/ api/dump/ fuel-snapshot- 2016-03- 24_07-37- 27.tar. xz Bytes: 99102756 ======= ======= ======= ======= ======= ======= ======= ======= ======= ======= ==]()
[root@fuel remote]# fuel snapshot
Generating dump...
Downloading: http://
[======
If default behaviour of of 'fuel snapshot' will be not to download, can we make output like this: nailgun/ dump on fuel master node
[root@fuel remote]# fuel snapshot
Generating dump...
Dump is stored at /var/www/
So it will be self-explanatory.