[ONBOARDING] Mia Altieri

[MiaAltieri]

Image name

charmed-mongodb

Short description

This is a MongoDB ROCK, providing the OCI image for MongoDB a source-available cross-platform document-oriented database program. Further it bundles all of the MongoDB tools used for backups, restores, monitoring, and security.

Image repository

https://github.com/canonical/charmed-mongodb-rock

Image type

ROCK

Maintainer agreement

• I agree to follow this project's Code of Conduct

• I understand and acknowledge the CONTRIBUTING guidelines and Image Maintainer Agreement

• This image is either a ROCK or a Docker image which already exists in the 'ubuntu' namespace

• I agree to be the image's Maintainer and thus own it and be responsible for it, thus committing to maintaining it throughout its lifetime

• My image's repository (where the build recipes are hosted) is public

• I agree to have the provided contacts added to the Image Maintainers mailing list in Launchpad

• This image is meant to be published to the 'ubuntu' namespace, and thus a new registry repository should be created

• I acknowledge that this image shall be monitored by the security team and that I've made the necessary modifications
  to support that

• I commit to address image issues in a timely manner and according to their severity

• I will always provide up-to-date documentation for this image

• I understand the OCI tagging convention

• I understand the image's stability commitments

• I will test my image before proposing new build and releases

Security enablement

        - util-linux
        - libssh-4
        - libbrotli1

Primary contact

[email protected]

Backup contact

No response

[cjdcordeiro]

Thanks for the info @MiaAltieri !

I few questions:

• you've marked This image is either a ROCK or a Docker image which already exists in the 'ubuntu' namespace. Is this true? https://hub.docker.com/r/ubuntu/charmed-mongodb doesn't exist yet...
• why charmed-mongodb and not just mongodb? We try to stay away from tech-specific titles for rocks, unless the image can only be used on that context (which typically is not the case)
• You have marked I agree to have the provided contacts added to the Image Maintainers mailing list in Launchpad and then provided the primary contact [email protected]. Are you sure you want to add this contact to the mailing list? There is already [email protected] in there, so you might want to double-check that
• you marked I acknowledge that this image shall be monitored by the security team and that I've made the necessary modifications to support that, but from https://github.com/canonical/charmed-mongodb-rock/blob/5-22.04/rockcraft.yaml, I don't see the necessary changes being added into the image
• your image is based on a snap, which means the security team won't be able to issue ROCK notifications based on that snap. Having said that, are you one of the snap collaborators?
• you seem to be adding a few additional debs to this ROCK, which means there is additional deb-based content worth being monitored by the security team. Did you reach out to @metorino for having your ROCK added into their watchlist?

Thanks

[MiaAltieri]

1. Oops my apologies, you are correct.
2. There are actually several reasons for this:

• Product has decided to market all MongoDB product as charmed, ie. i.e. Charmed MongoDB Snap, Charmed MongoDB-K8s, Charmed MongoDB Operator
• The ROCK doesn't just contain MongoDB, but it contains a suite of tools for MongoDB, i.e. backups (percona backup for mongodb), mongodb monitoring tools, and other relevant tools
• The ROCK actually doesn't use MongoDB, but instead uses Percona MongoDB, the reasoning here is that MongoDB changed their licenses and it is better for our customers if we package Percona MongoDB

3. Yes! Sorry [email protected] is correct
4. Oops my apologies, you are correct. Let me reach out to the Security Team
5. Yes I am the maintainer of the snap
6. No, thank you for letting me know, I will do this

Thank you so much for the help @cjdcordeiro , above you'll see the answers for your questions! I realise I have missed some crucial steps and I will get started on those. Thank you very much for your patience and your guidance here :)

[cjdcordeiro]

Thanks for the information!

wrt 2., if that's your PM's mandate, and since there's a precedent (charmed-opensearch), I won't block progress, but please double check the licensing terms and where you are entitled to re-distribute the image under a different name.

4. and 6.: np. please feel free to put me in cc so I know once the image is being monitored and thus can finish the onboarding

;)

P.S.: I've already created the repositories for the image in Docker Hub and ECR: https://us-east-1.console.aws.amazon.com/ecr/repositories/public/099720109477/charmed-mongodb?region=us-east-1 and https://hub.docker.com/repository/docker/ubuntu/charmed-mongodb/general

[cjdcordeiro]

@MiaAltieri it seems we should not use the charmed- prefix in the ubuntu namespace.