Odd ec2 behavior - volumes attached to bootstrap node.

John Meinel john at arbash-meinel.com
Fri Mar 21 04:21:11 UTC 2014


Notice that volume which is attached is a *new* volume. The reason is
because we are booting the images that use elastic block storage,
rather than only local temp files.
So yes, when you create new instances, you will see new volumes that
are mounted automatically. When those instances are destroyed, it will
delete those volumes.

On Fri, Mar 21, 2014 at 1:44 AM, David Britton
<david.britton at canonical.com> wrote:
> Is this expected?  Notice one of my volumes is attached after the bootstrap
> node comes up.  The ec2-tools and aws dashboard show the same thing.
>
> I've never seen this behavior before (I haven't looked that much), but I'm
> having trouble finding anything other than the -b option to ec2-run-instances
> that would expose anything like this.
>
>
> dpb at helo:~$ euca-describe-volumes
> VOLUME  vol-d59280d7    1               us-west-2a      available       2014-03-11T19:22:23.660Z        standard
> TAG     volume  vol-d59280d7    volume_name     nfs/0 volume
> VOLUME  vol-0a373504    9               us-west-2b      available       2014-03-20T17:02:22.356Z        standard
> TAG     volume  vol-0a373504    volume_name     postgresql/0 volume
>
> dpb at helo:~$ juju bootstrap; juju status -v
> verbose is deprecated with the current meaning, use show-log
> 2014-03-20 21:06:32 INFO juju.provider.ec2 ec2.go:193 opening environment "dpb-aws-us-west-2"
> 2014-03-20 21:06:54 INFO juju.state open.go:68 opening state; mongo addresses: ["ec2-54-245-152-4.us-west-2.compute.amazonaws.com:37017"]; entity ""
> 2014-03-20 21:10:04 INFO juju.state open.go:106 connection established
> 2014-03-20 21:10:04 INFO juju conn.go:66 juju: authorization error while connecting to state server; retrying
> 2014-03-20 21:10:04 INFO juju.state open.go:68 opening state; mongo addresses: ["ec2-54-245-152-4.us-west-2.compute.amazonaws.com:37017"]; entity ""
> 2014-03-20 21:10:05 INFO juju.state open.go:106 connection established
> environment: dpb-aws-us-west-2
> machines:
>   "0":
>     agent-state: pending
>     dns-name: ec2-54-245-152-4.us-west-2.compute.amazonaws.com
>     instance-id: i-7bae4d73
>     instance-state: running
>     series: precise
>     hardware: arch=amd64 cpu-cores=1 cpu-power=100 mem=1740M root-disk=8192M
> services: {}
> 2014-03-20 21:10:07 INFO juju supercommand.go:286 command finished
>
> dpb at helo:~$ euca-describe-volumes
> VOLUME  vol-d59280d7    1               us-west-2a      available       2014-03-11T19:22:23.660Z        standard
> TAG     volume  vol-d59280d7    volume_name     nfs/0 volume
> VOLUME  vol-2a1cf92f    8       snap-00d68df1   us-west-2a      in-use  2014-03-20T21:06:35.358Z        standard
> ATTACHMENT      vol-2a1cf92f    i-7bae4d73      /dev/sda1       attached        2014-03-20T21:06:35.000Z
> VOLUME  vol-0a373504    9               us-west-2b      available       2014-03-20T17:02:22.356Z        standard
> TAG     volume  vol-0a373504    volume_name     postgresql/0 volume
>
> --
> David Britton <david.britton at canonical.com>
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju



More information about the Juju mailing list