Cloudstack Marvin[1] can do the import if you give the cfg file. Maybe export functionality could be added to it.
More details about marvin are in the wiki[2] This is what I usually do to deploy: cloudstack/tools/marvin(master)$ sudo python setup.py install # to install marvin cloudstack/tools/marvin(master)$ python marvin/deployDataCenter.py -i ../../setup/dev/advanced.cfg # to deploy datacenter in the configuration file [1] https://pypi.python.org/pypi/cloudstack-marvin/4.4.0 [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Marvin+-+Testing+with+Python On Wed, Aug 13, 2014 at 2:42 AM, ilya musayev <ilya.mailing.li...@gmail.com> wrote: > One other thought, > > CloudMonkey can print output with JSON format via "set display json". > > If that same output can be fed into CloudStack via CloudMonkey, it would > achieve the same result. > > > On 8/12/14, 12:11 PM, Andrei Mikhailovsky wrote: > >> Hello guys, >> >> I thought to share some ideas on migrating the cloud environment from one >> build to another. Let's say you have a cloudstack build with a bunch of >> domains, users, guest vms and networks and you would like to replicate or >> move it across to a different setup (It may be a different physical >> location with different network setup, etc.). >> >> At the moment, there is no way of doing this. There is not even a >> function to reliably export a vm with all of it's volumes and networking >> settings. Would it not be a great feature to have in ACS - a backup/restore >> or export/import like functionality which is built in to almost every >> single commercial software nowadays. The use cases for this are limitless >> (from a simple recovery of the broken ACS install/database to replication >> of dev/test/qa/production environments). It would be even more useful if >> one could choose which hierarchy within ACS to migrate/export/backup. Like >> account/domain/project/root level backup and restore. The function should >> go over the existing setup and accumulate all settings required in >> producing the identical setup elsewhere. This would include not only the >> guest vms and the attached volumes, but also, the networking setup, access >> rights, qos settings, snapshots, etc. >> >> The end result should be something like a folder with exported data that >> one could simply point his/her newly created ACS setup and say - Import >> this cloud setup please. >> >> Should ACS has this functionality or is it too complicated and too much >> to ask? >> >> Thanks for your thoughts >> >> >> Andrei >> >> >> >> > > -- ~Rajani
