Two silly questions regarding the images created by cloud-init:

1) Is the following an expected behavior?
   Step1: Taking a snapshot of a working instance
   Step2: Launching a new instance from the snapshot
Step3: The new instance is booting but the network fails since it already has eth0 and a new eth1 is allocated to the new instance.

What do I have to do in order for this to work without any trouble?


2) Do you know where I can find some info regarding the way to make the / partition dynamic based on the flavor?? I have built an instance on which the / partition is 20GB . Is there a way to make it change according to the flavor? Obviously this should apply to bigger / partitions. What I am trying to do is to have an image which I can boot with either 20GB or bigger / partition.

Best,


G.



On Sun, 02 Mar 2014 11:42:33 +0200, Georgios Dimitrakakis wrote:
Dear Antonio,

thank you very much for the useful info!

I will give it a shot!!!

Best,

G.

On Sat, 1 Mar 2014 12:17:14 +0100, Antonio Messina wrote:
On Fri, Feb 28, 2014 at 8:36 PM, Georgios Dimitrakakis
<gior...@acmac.uoc.gr> wrote:
Thx for your suggestion!

I am trying since yesterday to achieve this but unfortunately the installer always start in a text-based mode and cannot change the partition scheme
from there :-(

Hi Georgios,

I don't know if this can be helpful for you or other people here, but I usually create my centos/ubuntu images with virt-inst from kickstart
or preseed using a script.

Script and related kickstart is available at
https://github.com/gc3-uzh-ch/openstack-tools
they are mainly for internal use, so you may need to modify the
kickstart (we always provides images with the 'gc3-user' user so we
need to modify the configuration of cloud-init.

We partition our disks with one single partition. The script doesn't
yet take into account the extra swap partition though, we don't have
swap in our flavors.

.a.


_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Reply via email to