Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Where did the docker image ceph/demo go? #1169

Closed
DeepDiver1975 opened this issue Aug 22, 2018 · 8 comments

Comments

@DeepDiver1975
Copy link

@DeepDiver1975 DeepDiver1975 commented Aug 22, 2018

What happened:
We use the docker image ceph/demo within our ci setup.
As of yesterday it seems to be gone.

Where did it go? THX a lot

@leseb

This comment has been minimized.

Copy link
Contributor

@leseb leseb commented Aug 22, 2018

I'm sorry to read that @DeepDiver1975 -, I actually removed that image yesterday since it was not maintained anymore and did not receive any update for the last 10 months.

If you want to keep on using ceph/demo, you should switch to ceph/daemon and call it with demo, see an example run here: https://github.com/ceph/ceph-container/blob/master/.travis.yml#L23

Sorry for the inconvenience.

@DeepDiver1975

This comment has been minimized.

Copy link
Author

@DeepDiver1975 DeepDiver1975 commented Aug 22, 2018

@leseb thanks a lot for your feedback!

We are using the ceph images within a drone setup and I see the container hanging at the demo user creation:

2018-08-22 10:00:30  /entrypoint.sh: Setting up a demo user...
++demo.sh:129: bootstrap_demo_user(): '[' -n owncloud ']'
++demo.sh:129: bootstrap_demo_user(): '[' -n owncloud123456 ']'
++demo.sh:129: bootstrap_demo_user(): '[' -n secret123456 ']'
++demo.sh:130: bootstrap_demo_user(): radosgw-admin --cluster ceph user create --uid=owncloud '--display-name=Ceph demo user' --access-key=owncloud123456 --secret-key=secret123456

@DeepDiver1975

This comment has been minimized.

Copy link
Author

@DeepDiver1975 DeepDiver1975 commented Aug 22, 2018

This is the ceph container setup:

  ceph:
    image: ceph/daemon:v3.0.5-stable-3.0-jewel-ubuntu-16.04-x86_64
    pull: true
    environment:
      - NETWORK_AUTO_DETECT=4
      - CEPH_DAEMON=demo
      - RGW_NAME=ceph
      - CEPH_DEMO_UID=owncloud
      - CEPH_DEMO_ACCESS_KEY=owncloud123456
      - CEPH_DEMO_SECRET_KEY=secret123456
      - DEBUG=verbose
@DeepDiver1975

This comment has been minimized.

Copy link
Author

@DeepDiver1975 DeepDiver1975 commented Aug 22, 2018

seems to be related to v3.0.5-stable-3.0-jewel-ubuntu-16.04-x86_64 -

3.0.7 looks promising ...

@DeepDiver1975

This comment has been minimized.

Copy link
Author

@DeepDiver1975 DeepDiver1975 commented Aug 23, 2018

THX a lot! We can iterate from here!

@leseb

This comment has been minimized.

Copy link
Contributor

@leseb leseb commented Aug 23, 2018

@DeepDiver1975 Ok good to know!

@Goltergaul

This comment has been minimized.

Copy link

@Goltergaul Goltergaul commented May 28, 2019

which port do i need to expose so that i can connect to the demo cluster? only exposing 6890 seems not to work

@dsavineau

This comment has been minimized.

Copy link
Collaborator

@dsavineau dsavineau commented May 28, 2019

@Goltergaul you should have open a dedicated issue for this instead of replying on a closed one.

To answer to your question, the simpler way if you don't want to manage the port list is to use the --host=net option.
If you want to use a different network container option, then it depends on the ceph daemons and how you configure them with the demo. By default:

  • mon: 6879 (+3300 with nautilus)
  • mds,mgr,osd: 6800-6811
  • rgw: 8080
  • rest api: 8003
  • sree: 5000
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.