[Yahoo-eng-team] [Bug 1370177] Re: Lack of EC2 image attributes for volume backed snapshot.

2015-11-20 Thread Andrey Pavlov
** Changed in: ec2-api
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1370177

Title:
  Lack of EC2 image attributes for volume backed snapshot.

Status in ec2-api:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  For EBS images AWS returns device names, volume sizes, delete on
  termination flags in block device mapping structure.

  $ euca-describe-images ami-d13845e1
  IMAGE ami-d13845e1amazon/amzn-ami-hvm-2014.03.2.x86_64-ebsamazon  
available   public  x86_64  machine ebs hvm 
xen
  BLOCKDEVICEMAPPING/dev/xvda   snap-d15cde24   8   true

  The same in xml form:
  
  
  /dev/xvda
  
  snap-d15cde24
  8
  true
  standard
  
  
  

  But Nova didn't do it now:

  $ euca-describe-images ami-000a
  IMAGE ami-000aNone (sn-in)ef3ddd7aa4b24cda974200baef02730b
available   private machine aki-0002ari-0003
instance-store
  BLOCKDEVICEMAPPINGsnap-0005

  The same in xml form:
    
  
    
  snap-0005
    
  
    

  NB. In Grizzly device names and delete on termination flags was returned. It 
was changed by 
https://github.com/openstack/nova/commit/33e3d4c6b9e0b11500fe47d861110be1c1981572
  Now these attributes are not stored in instance snapshots, so there is no way 
to output them.

  Device name is most critical attribute. Because there is another one 
compatibility issue (see https://bugs.launchpad.net/nova/+bug/1370250): Nova 
isn't able to adjust attributes of volume being created at instance launch 
stage. For example in AWS we can change volume size and delete on termination 
flag of a device by set new values in parameters of run instance command. To 
identify the device in image block device mapping we use device name. For 
example:
  euca-run-instances ... -b /dev/vda=:100
  runs an instance with vda device increased to 100 GB.
  Thus if we haven't device names in images, we haven't a chance to fix this 
compatibility problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ec2-api/+bug/1370177/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1370177] Re: Lack of EC2 image attributes for volume backed snapshot.

2015-07-28 Thread Thierry Carrez
** Changed in: nova
   Status: Fix Committed = Fix Released

** Changed in: nova
Milestone: None = liberty-2

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1370177

Title:
  Lack of EC2 image attributes for volume backed snapshot.

Status in ec2-api:
  Fix Committed
Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  For EBS images AWS returns device names, volume sizes, delete on
  termination flags in block device mapping structure.

  $ euca-describe-images ami-d13845e1
  IMAGE ami-d13845e1amazon/amzn-ami-hvm-2014.03.2.x86_64-ebsamazon  
available   public  x86_64  machine ebs hvm 
xen
  BLOCKDEVICEMAPPING/dev/xvda   snap-d15cde24   8   true

  The same in xml form:
  blockDeviceMapping
  item
  deviceName/dev/xvda/deviceName
  ebs
  snapshotIdsnap-d15cde24/snapshotId
  volumeSize8/volumeSize
  deleteOnTerminationtrue/deleteOnTermination
  volumeTypestandard/volumeType
  /ebs
  /item
  /blockDeviceMapping

  But Nova didn't do it now:

  $ euca-describe-images ami-000a
  IMAGE ami-000aNone (sn-in)ef3ddd7aa4b24cda974200baef02730b
available   private machine aki-0002ari-0003
instance-store
  BLOCKDEVICEMAPPINGsnap-0005

  The same in xml form:
    blockDeviceMapping
  item
    ebs
  snapshotIdsnap-0005/snapshotId
    /ebs
  /item
    /blockDeviceMapping

  NB. In Grizzly device names and delete on termination flags was returned. It 
was changed by 
https://github.com/openstack/nova/commit/33e3d4c6b9e0b11500fe47d861110be1c1981572
  Now these attributes are not stored in instance snapshots, so there is no way 
to output them.

  Device name is most critical attribute. Because there is another one 
compatibility issue (see https://bugs.launchpad.net/nova/+bug/1370250): Nova 
isn't able to adjust attributes of volume being created at instance launch 
stage. For example in AWS we can change volume size and delete on termination 
flag of a device by set new values in parameters of run instance command. To 
identify the device in image block device mapping we use device name. For 
example:
  euca-run-instances ... -b /dev/vda=:100
  runs an instance with vda device increased to 100 GB.
  Thus if we haven't device names in images, we haven't a chance to fix this 
compatibility problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ec2-api/+bug/1370177/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1370177] Re: Lack of EC2 image attributes for volume backed snapshot.

2015-04-17 Thread Andrey Pavlov
** Also affects: ec2-api
   Importance: Undecided
   Status: New

** Changed in: ec2-api
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1370177

Title:
  Lack of EC2 image attributes for volume backed snapshot.

Status in EC2 API:
  Confirmed
Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  For EBS images AWS returns device names, volume sizes, delete on
  termination flags in block device mapping structure.

  $ euca-describe-images ami-d13845e1
  IMAGE ami-d13845e1amazon/amzn-ami-hvm-2014.03.2.x86_64-ebsamazon  
available   public  x86_64  machine ebs hvm 
xen
  BLOCKDEVICEMAPPING/dev/xvda   snap-d15cde24   8   true

  The same in xml form:
  blockDeviceMapping
  item
  deviceName/dev/xvda/deviceName
  ebs
  snapshotIdsnap-d15cde24/snapshotId
  volumeSize8/volumeSize
  deleteOnTerminationtrue/deleteOnTermination
  volumeTypestandard/volumeType
  /ebs
  /item
  /blockDeviceMapping

  But Nova didn't do it now:

  $ euca-describe-images ami-000a
  IMAGE ami-000aNone (sn-in)ef3ddd7aa4b24cda974200baef02730b
available   private machine aki-0002ari-0003
instance-store
  BLOCKDEVICEMAPPINGsnap-0005

  The same in xml form:
    blockDeviceMapping
  item
    ebs
  snapshotIdsnap-0005/snapshotId
    /ebs
  /item
    /blockDeviceMapping

  NB. In Grizzly device names and delete on termination flags was returned. It 
was changed by 
https://github.com/openstack/nova/commit/33e3d4c6b9e0b11500fe47d861110be1c1981572
  Now these attributes are not stored in instance snapshots, so there is no way 
to output them.

  Device name is most critical attribute. Because there is another one 
compatibility issue (see https://bugs.launchpad.net/nova/+bug/1370250): Nova 
isn't able to adjust attributes of volume being created at instance launch 
stage. For example in AWS we can change volume size and delete on termination 
flag of a device by set new values in parameters of run instance command. To 
identify the device in image block device mapping we use device name. For 
example:
  euca-run-instances ... -b /dev/vda=:100
  runs an instance with vda device increased to 100 GB.
  Thus if we haven't device names in images, we haven't a chance to fix this 
compatibility problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ec2-api/+bug/1370177/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp