api: '1.0'
astute_sha: c3e7c7a18528cf9acca48021488a93dff74f5c97
auth_required: true
build_id: 2014-10-16_19-59-04
build_number: '72'
feature_groups:
- mirantis
fuellib_sha: 677c2809bd602ed6f793b03df49ef8b0f8dcb7e7
fuelmain_sha: 5cf06aac43ccb4a6031fbfa87ff9f9a729314daa
nailgun_sha: b83eaf18cbcc36393f8ac1e7732a6395546a7ca8
ostf_sha: de177931b53fbe9655502b73d03910b8118e25f1
production: docker
release: '6.0'
On the big env Fuel snapshot time creation and size are huge
In my case - 100 nodes after 13 hours uptime
size
fuel-snapshot-2014-10-17_11-08-01.tgz - 479M
time
[root@fuel nailgun]# time fuel snapshot
Generating dump...
Downloading: http://10.20.0.2:8000/dump/fuel-snapshot-2014-10-17_11-34-03.tgz Bytes: 517229965
[==============================================================================]()
real 23m53.762s
user 0m13.284s
sys 0m4.506s
This file hard to store and share
I guess Fuel must have feature like 'dockerctl shell nailgun /usr/bin/manage.py dropdb, syncdb, loaddefault' for all files including in snapshot.
This may be checkbox for UI and option of command 'fuel snapshot' about cleaning snapshoted files.
I belive we have feature rotate logs, so we need to see if this wowrks properly