← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1312690] [NEW] nova-docker snapshot does not return proper image ID

 

Public bug reported:

With the current impl of the nova-docker virt driver and the docker-
registry (https://github.com/dotcloud/docker-registry) snapshotting a
docker container does not return the image ID of the final image created
from the snapshot operation.

For example consumer code should be able to do something like this:

        image_uuid = self.clients("nova").servers.create_image(server,
                                                               server.name)
        image = self.clients("nova").images.get(image_uuid)
        image = bench_utils.wait_for(
            image,
            is_ready=bench_utils.resource_is("ACTIVE"),
            update_resource=bench_utils.get_from_manager(),
            timeout=CONF.benchmark.nova_server_image_create_timeout,
            check_interval=
                CONF.benchmark.nova_server_image_create_poll_interval
        )

That is, the image returned from the create_image should reflect the
image UUID of the "final" image created during capture. However with
docker driver the process actually creates a final image call
<image_name>:latest.

Example:
- Install devstack + nova-docker driver
- Pull, tag and push a docker image into glance using docker-registry with glance store
- Create a nova server for docker -- results in a docker container
- Use the nova python api to snapshot the server (see code snippet above).
- The image_uuid returned in the above snippet might point to an image named 'myzirdsivgoftfqp'. However the actual final image created by the snapshot is named 'myzirdsivgoftfqp:latest' and is not the same image referred to in the return response from the create_image call

Such behavior impacts consumers and is not consistent with the nova
snapshot behavior.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1312690

Title:
  nova-docker snapshot does not return proper image ID

Status in OpenStack Compute (Nova):
  New

Bug description:
  With the current impl of the nova-docker virt driver and the docker-
  registry (https://github.com/dotcloud/docker-registry) snapshotting a
  docker container does not return the image ID of the final image
  created from the snapshot operation.

  For example consumer code should be able to do something like this:

          image_uuid = self.clients("nova").servers.create_image(server,
                                                                 server.name)
          image = self.clients("nova").images.get(image_uuid)
          image = bench_utils.wait_for(
              image,
              is_ready=bench_utils.resource_is("ACTIVE"),
              update_resource=bench_utils.get_from_manager(),
              timeout=CONF.benchmark.nova_server_image_create_timeout,
              check_interval=
                  CONF.benchmark.nova_server_image_create_poll_interval
          )

  That is, the image returned from the create_image should reflect the
  image UUID of the "final" image created during capture. However with
  docker driver the process actually creates a final image call
  <image_name>:latest.

  Example:
  - Install devstack + nova-docker driver
  - Pull, tag and push a docker image into glance using docker-registry with glance store
  - Create a nova server for docker -- results in a docker container
  - Use the nova python api to snapshot the server (see code snippet above).
  - The image_uuid returned in the above snippet might point to an image named 'myzirdsivgoftfqp'. However the actual final image created by the snapshot is named 'myzirdsivgoftfqp:latest' and is not the same image referred to in the return response from the create_image call

  Such behavior impacts consumers and is not consistent with the nova
  snapshot behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1312690/+subscriptions


Follow ups

References