[Hawkular-dev] https://hub.docker.com/r/hawkular/*

[Thomas Heute]

Agreed, we need to clean this up...

"hawkular" can probably be deleted
hawkular Metrics image needs to be created automatically (last build is 2
years old)




On Thu, May 25, 2017 at 4:34 PM, Josejulio Martinez Magana <
jmartine at redhat.com> wrote:

> +1
>
> I agree.
> We should:
>   Delete the old and unused images, those are confusing.
>   Move images used in examples to hawkular-labs, and
>   Put more effort into adding some descriptions to the maintained images,
> e.g. a general description of what it does/have.
>
> On Thu, May 25, 2017 at 9:21 AM, Jiri Kremser <jkremser at redhat.com> wrote:
>
>> Hi,
>>   the Dockerhub is the image registry that is enabled by default for
>> dockerd. IMO, we can't support only our internal RH registries and ignore
>> the dockerhub. This is what we deliver to the community. Less and less
>> people are downloading zip files and installing stuff these days (or even
>> using package managers). If I want to try tool/product/project X (where X
>> can be prometheus, ) First thing that comes to my mind is to google for the
>> docker image and some short code (like `docker run -e foo=bar org/image`)
>> that I can copy&paste to the terminal and have everything set up correctly.
>> We have nothing like that today and that was 1 of the reasons, why I
>> started the hawkinit cli/tui tool.
>>
>> Currently we have dozens of images there that are obsolete or that were
>> used for 1 particular use-case/demo. For instance the hawkular-metrics
>> https://hub.docker.com/r/hawkular/hawkular-metrics/tags/ has the latest
>> change before 2 years and contains bunch of images that have snapshot in
>> the tag. If I am a newcomer trying to play with hawkular-metrics, I would
>> run away quickly.
>>
>> The very first image is the https://hub.docker.com/r/hawkular/hawkular/
>> which should be the "Hawkular", right? Last change is 1 year old and again,
>> for the newcomers it's hard to explain the fact that it's the old version
>> containing the old components, but it has the rich UI, while the new ones
>> have no UI, but new components.
>>
>> Could you guys look and reply to this email if you want to preserve
>> certain image?
>> Currently these are 'maintained' and quite ok (I didn't go through all of
>> them):
>> * hawkular-services
>> * hawkular-openshift-agent
>> * wildfly-hawkular-javaagent
>> * wildfly-hawkular-agent-domain
>> * wildfly-hawkular-agent
>> * hawkular-website
>> * hawkular-grafana-datasource
>> * hawkular-openshift-agent-example-jolokia-wildfly (despite the name,
>> (name != description))
>> ... the rest seems to be abbandoned or was created for some demo and it's
>> a question if those images should be under the hawkular org, or if we
>> shouldn't move them to something like hawkular-labs or hawkular-examples,
>> or similar. I don't know.
>>
>> One note to the naming: we have quite a lot of different agents without
>> any description or metadata in the image itself, what should I use and
>> when? I know that, mazz knows that and probably couple of other guys know
>> that, but people out there would have no idea.
>>
>> Perhaps it would be good to have also some thoughts from people that are
>> relatively new in the team or work a lot with the d. images. Like Caina,
>> Paul, Josejulio.
>>
>> wdyt, guys?
>>
>> jk
>>
>
>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20170529/edf3c232/attachment.html