Thanks Sergey, Will look into this, but still have the same question, would introducing containers increase my footprint per fake compute service? I can run multiple compute service in same hosts without containers. Containers give you a nice isolation and another way to try a more realistic scenario, but my initial goal now is to be able to simulate many fake compute node scenario with as little resources as possible.
Regards, David Peraza -----Original Message----- From: Sergey Skripnick [mailto:sskripn...@mirantis.com] Sent: Monday, March 03, 2014 3:18 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova] Simulating many fake nova compute nodes for scheduler testing David Peraza <david_per...@persistentsys.com> писал(а) в своём письме Mon, 03 Mar 2014 21:27:01 +0200: > > Using compute inside LXC, I created 100 computes per physical host. Here > is what I did, it's very simple: > - Creating a LXC with logical volume > - Installing a fake nova-compute inside the LXC > - Make a booting script that modifies its nova.conf to use its IP > address & starts nova-compute > - Using the LXC above as the master, clone as many compute as you like! > > (Note that while cloning the LXC, the nova.conf is copied with the > former's IP address, that's why we need the booting script.) > Also btrfs can be used to reduce disk space usage. Scenario is looks like this: * create btrfs filesystem on /var/lib/lxc * create first container with btrfs backingstore (lxc-create -B btrfs ...) * setup devstack with fakevirt * stop container, and make N snapshotted clones (lxc-clone --snapshot ...) * start containers and run booting script (here script used by Rally [0]) If you do not want to do all this manually, there is MultihostEngine/LxcEngine coming soon in Rally [1] [0] https://review.openstack.org/#/c/56222/25/rally/deploy/engines/lxc/start.sh [1] https://wiki.openstack.org/wiki/Rally -- Regards, Sergey Skripnick _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
