Charmed MongoDB
- By Canonical Data Platform
- Databases
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 6/stable | 164 | 26 Mar 2024 | |
| 6/candidate | 164 | 26 Mar 2024 | |
| 6/beta | 164 | 26 Mar 2024 | |
| 6/edge | 172 | 14 May 2024 | |
| 5/stable | 117 | 20 Apr 2023 | |
| 5/candidate | 117 | 20 Apr 2023 | |
| 5/edge | 139 | 21 Nov 2023 | |
| 3.6/stable | 100 | 28 Apr 2023 | |
| 3.6/candidate | 100 | 13 Apr 2023 | |
| 3.6/edge | 100 | 03 Feb 2023 |
juju deploy mongodb --channel 6/stable
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
Charm Testing reference
Hint: Use Juju 3. (Charmed MongoDB dropped support for juju 2.9)
There are a lot of test types available and most of them are well applicable for Charmed MongoDB. Here is a list prepared by Canonical:
- Unit tests
- Integration tests
- Performance tests
Unit tests:
Please check the “Contributing” guide and follow tox run -e unit examples there.
Integration tests:
The integration tests coverage is rather rich in the MongoDB charm.
Please check the “Contributing” guide and follow tox run -e integration examples there.
For tests related to complex features, and HA (High Availability) - each test serves as an integration as well as a smoke test with continuous writes routines being perpetually ran in parallel of whatever operation the test is involved in. These continuous writes ensure the availability of the service under different conditions.
Those tests make use of the following fixture:
continuous_writes: creates a replicated collection and continuously stores data into it.
After each test completes, the collection gets deleted.
Performance test
Refer to the charmed MongoDB VM benchmark guide for charmed Charmed MongoDB.