Skip to content

Conversation

@smarterclayton
Copy link
Contributor

  • Allow ImageRepositoryMapping to accept an ImageRepository Name/Namespace pair along with DockerImageRegistry, make validation detect passing both.
  • Make Image/ImageRepository/ImageRepositoryMapping much more strict.
  • Use strict versioning of incoming Docker image metadata structs by integrating them into the conversion framework - stop using go-dockerclient directly (can't break our API accidentally)
  • Introduce a new GET /imageRepositoryTags/<name>:<tag> endpoint which returns the image that is tagged or a 404.

Sets the stage for allowing build output to point to an IR by name

[test]

@smarterclayton smarterclayton changed the title ImageRepository lookup should check the OpenShift for <namespace>/<name> ImageRepository lookup should check named repos (not just DockerImageRepository) Jan 12, 2015
@openshift-bot
Copy link
Contributor

@smarterclayton
Copy link
Contributor Author

@ncdc review. Going to have some changes after this to allow api consumers to get at the DockerImageReference for a tagged image in a single call, want to get this nailed down.

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_openshift3/736/)

smarterclayton added a commit to smarterclayton/docker-registry-extensions that referenced this pull request Jan 12, 2015
…itory

Do not merge until equivalent lookup is supported in OpenShift under
openshift/origin#635
smarterclayton added a commit to smarterclayton/docker-registry-extensions that referenced this pull request Jan 12, 2015
…itory

Do not merge until equivalent lookup is supported in OpenShift under
openshift/origin#635
smarterclayton added a commit to smarterclayton/docker-registry-extensions that referenced this pull request Jan 13, 2015
…itory

Do not merge until equivalent lookup is supported in OpenShift under
openshift/origin#635
@smarterclayton
Copy link
Contributor Author

Upstream item was merged, this is now backwards compatible with old and new registries.

@smarterclayton
Copy link
Contributor Author

[test]

@smarterclayton
Copy link
Contributor Author

@ncdc this is ready for final review, I'll do the rest of the changes later.

@smarterclayton
Copy link
Contributor Author

[test]

hack/test-go.sh Outdated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this supposed to be commented out?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, see the comment on the commit

On Jan 19, 2015, at 9:49 AM, Andy Goldstein [email protected] wrote:

In hack/test-go.sh:

fi
KUBE_TIMEOUT=${KUBE_TIMEOUT:--timeout 45s}

if [ -z ${KUBE_RACE+x} ]; then

  • KUBE_RACE="-race"
  • KUBE_RACE="" #"-race"
    Is this supposed to be commented out?


Reply to this email directly or view it on GitHub.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't worry about this one, Jordan is reviewing it

On Jan 19, 2015, at 9:49 AM, Andy Goldstein [email protected] wrote:

In hack/test-go.sh:

fi
KUBE_TIMEOUT=${KUBE_TIMEOUT:--timeout 45s}

if [ -z ${KUBE_RACE+x} ]; then

  • KUBE_RACE="-race"
  • KUBE_RACE="" #"-race"
    Is this supposed to be commented out?


Reply to this email directly or view it on GitHub.

@ncdc
Copy link
Contributor

ncdc commented Jan 19, 2015

A few comments, otherwise LGTM

Allow ImageRepositoryMapping to accept an ImageRepository Name/Namespace
pair along with DockerImageRegistry, make validation detect passing both.
Make Image/ImageRepository/ImageRepositoryMapping much more strict.
@smarterclayton smarterclayton force-pushed the image_stream_status branch 4 times, most recently from 338478b to 2187e78 Compare January 19, 2015 19:27
Create a new internal object image/api.DockerImage which has two
versions, "1.0" and "pre012" to match the docker client and docker
registry API versioning.  Allow the version of that API to be
passed when submitting an image - if not passed, assume that the
object is "1.0" (which is our legacy behavior).  Clients should
set "apiVersion" inside the "DockerImageMetadata" field for maximum
forward compatibility to "1.0".

TODO: Upstream should allow the ability to decode and default a
kind and apiVersion for maximum flexibility.
This endpoint will be used by clients to fetch the latest image for
a given resource.  Sets the stage for BuildOutput to be an image
reference.
@smarterclayton
Copy link
Contributor Author

[merge]

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_openshift3/627/) (Image: devenv-fedora_552)

@openshift-bot
Copy link
Contributor

Evaluated for origin up to 361cdea

openshift-bot pushed a commit that referenced this pull request Jan 19, 2015
@openshift-bot openshift-bot merged commit 7c12a9c into openshift:master Jan 19, 2015
@smarterclayton smarterclayton deleted the image_stream_status branch May 18, 2015 02:16
@coveralls
Copy link

coveralls commented Aug 2, 2016

Coverage Status

Changes Unknown when pulling 361cdea on smarterclayton:image_stream_status into * on openshift:master*.

sjenning pushed a commit to sjenning/origin that referenced this pull request Jan 5, 2018
Do not exclude the excluder for atomic-openshift
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants