Hi Andrew, Actually there we devices with /dev/xvdX .... Do you mean they are the new devices created?
On Mon, Jan 6, 2014 at 6:44 PM, Andrew Bayer <[email protected]> wrote: > EC2 is weird about its device names - check for /dev/xvdX. > > A. > > > On Mon, Jan 6, 2014 at 4:44 AM, Andrew Phillips <[email protected]>wrote: > >> Quoting Udara Liyanage <[email protected]>: >> >> Hi, >>> >>> I am in the process of adding a EBS volume to the instances. I fallowed >>> [1]. >>> >>> Template template = templateBuilder.build(); >>> template.getOptions().as(EC2TemplateOptions.class) >>> .mapEphemeralDeviceToDeviceName("/dev/sdm", "ephemeral0")// >>> .mapNewVolumeToDeviceName("/dev/sdn", 3, true)// >>> .mapEBSSnapshotToDeviceName("/dev/sdo", "snap-40fc8675", 2, >>> true); >>> >>> Above code executed with no errors and an instance is spawned. But I >>> could >>> not find any */dev/sd *device in the instance. >>> >> >> What is the content of >> >> node.getHardware().getVolumes() >> >> for the NodeMetadata [1] that is returned by the above call? >> >> Also, if you enable wire and header logging [2], can you see which EC2 >> calls are actually being made? >> >> ap >> >> [1] http://javadocs.jclouds.cloudbees.net/ >> [2] http://jclouds.apache.org/documentation/reference/jclouds-logging/ >> > > -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware http://udaraliyanage.wordpress.com/ phone: +94 71 443 6897
