亚博贵宾会贴吧MongoDB的博客

文章，公告，新闻，更新和更多

亚博贵宾会贴吧MongoDB的4.4：用户驱动的工程。为你准备好了

亚博贵宾会贴吧MongoDB的4.4现在是GA并准备生产使用。了解什么是在查询语言和新的驱动程序。

2020年7月30日

新闻

如何改进我们的现代化工具包可以帮助您了解您的数据中心退出

全球的客户都准备离开他们的数据中心的后面。我们新近增强的现代化工具包可以帮助您选择适合您的云迁移正确的数据库。

二〇二〇年九月三十〇日
更新

实习生系列：从研究员MongoDBers学习 - 符合英俄嗯亚博贵宾会贴吧

亚博贵宾会贴吧MongoDBers是知识的源泉一个。把它从实习生，迎ENG，谁把从许多人在今年夏天学习的机会！#lifeatmonogdb＃m亚博贵宾会贴吧ongodbsummer20

2020年9月25日
文化

亚博贵宾会贴吧MongoDB的阿特拉斯现已在24个谷歌云区

亚博贵宾会贴吧MongoDB的Atlas是在谷歌云三个新的地区提供：盐湖城，拉斯维加斯，和雅加达。这使谷歌支持的云区的24个总数。

2020年9月23日
更新

illimity和Mo亚博贵宾会贴吧ngoDB的：革命尚未可靠

革命而可靠的！了解illimity如何选择在微软的Azure Mo亚博贵宾会贴吧ngoDB的阿特拉斯打造意大利首个云本地的，数字化的银行。

2020年9月21日
应用的

HalaPlay证明1500％的增长是没有任何幻想，感谢MongoDB的阿特拉斯和MongoDB境界亚博贵宾会贴吧

了解MongoDB的亚博贵宾会贴吧领域的应用开发服务如何帮助Halaplay - 幻想体育联盟 - 快速构建新的功能和规模达到900万个用户。

2020年9月18日
应用的

有关MongoDB阿特拉斯合并结算多群集选项亚博贵宾会贴吧

详细了解最新改进的MongoDB阿特拉斯，包括合并结算，新的低CPU集群，并降低亚博贵宾会贴吧集群定价。

2020年9月2日
更新

与Zaloni和MongoDB云优化DataOps亚博贵宾会贴吧

Zaloni有助于从内部部署环境中的MongoDB阿特拉斯公司的过渡，因为他们自己的数据架构现代化，云亚博贵宾会贴吧

2020年9月2日
开发人员

运行S3兼容的端点在Kubernetes主机操作管理员的二进制文件

这个职位是该公司对MongoDB的Kubernetes操作运行操作管理员正在进行系列的一部分。亚博贵宾会贴吧退房的相关文章更多。在Kubernetes在亚博贵宾会贴吧Kubernetes运行MongoDB的行动经理最近引进的MongoDB操作管理员，我们宣布在Kubernetes部署行动经理的能力，并就如何在您的环境设置这一步一步的指导。现在我们回到向您展示如何使用一个令人兴奋的新功能，我们已经发布：运行一个兼容的S3服务用于部署集群MongoDB的二进制文件的能力，或者HTTP（S）端点。亚博贵宾会贴吧这允许您设置操作管理员一Kubernetes群集上没有接入互联网而无需管理在行动Manager部署中的每个豆荚的mongod / mongos二进制文件。我们会告诉你如何配置端点，上传正确的二进制文件，并重新配置行动Manager部署，从这个端点提供使用的文件。前提条件本指南假定您已经设置了和你的集群上运行操作管理员和MongoDB的企业Kubernetes操作，下面这里的指南中的步骤。亚博贵宾会贴吧这会给你一个部署的集群，我们可以修改以使用新的HTTP端点来检索部署和升级的mongod / mongos实例所需要的二进制文件。如果你有一个现有的环境，那么你将需要安装以下版本：Kubernetes API V1.16以上MongoDB的操作V1.17或以上MinIO操作MongoDB的企业Kubernetes操作1.6.0或以上的MongoDB操作管理员4.4。亚博贵宾会贴吧0或以上选择在哪里主机二进制文件从操作管理员的唯一要求是一个HTTP端点，所以你可以根据需要组织内利用现有的文件服务器配置。在本教程中，我们将使用MinIO，即对集装箱基础设施，如Kubernetes私有云部署，在许多财富500强公司采用优化的一个流行的开源对象存储平台。 With MinIO, customers can manage their binaries with individual policies through rich programmatic and UI admin services that align with best practices for file management such as bitrot protection, encryption, and identity management. Installing MinIO Installing MinIo is similar to the MongoDB Kubernetes Operator. The MinIO documentation shows you how to deploy on your Kubernetes cluster, with many configurations to suit your organization’s requirements. In this tutorial, we will show you how to use the Operator to manage the installation of your instance. First, let’s ensure the operator is installed and configured by running the following command on your cluster: kubectl apply -k github.com/minio/operator Now, let's create the MinIO instances to serve our binaries: kubectl apply -f https://raw.githubusercontent.com/minio/operator/master/examples/tenant.yaml This deployment will take a few moments. Let's verify that the instance successfully deploys: kubectl get pods NAME READY STATUS RESTARTS AGE minio-zone-0-0 1/1 Running 0 6m14s minio-zone-0-1 1/1 Running 0 6m14s minio-zone-0-2 1/1 Running 0 6m14s minio-zone-0-3 1/1 Running 0 6m14s Once this is complete, we should also get a service name, which we will use in the Ops Manager configuration later: kubectl get svc -l v1.min.io/tenant=minio NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE minio-hl ClusterIP None 9000/TCP 48m Creating Buckets With MongoDB Binaries and Database Tools Now that we have a running instance of MinIO, we can populate it with binaries for use by the operator to deploy mongoDB instances. The MongoDB Kubernetes Operator, as of v0.10 , uses Ubuntu 16.04 mongoDB binaries, which can be downloaded from https://www.mongodb.org/dl/linux/x86_64-ubuntu1604 . If Ops Manager will also be managing deployments, you may also wish to populate your buckets with versions for other architectures and platforms. A full list of the currently supported binaries can be retrieved from the version manifest of Ops Manager through the Version Manifest endpoint. For the purposes of this tutorial, we will just fetch versions 4.2.3 and 4.2.0 for use by the operator: curl -O http://downloads.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1604-4.2.3.tgz curl -O http://downloads.mongodb.org/linux/mongodb-linux-x86_64-ubuntu1604-4.2.0.tgz Also, we’ll need the mongodb-database-tools for the current version of Ops Manager. For the 4.4.0 release, this is v100.0.2. curl -O https://fastdl.mongodb.org/tools/db/mongodb-database-tools-ubuntu1604-x86_64-100.0.2.tgz Now, let's put the mongod files into a bucket named ‘linux’, and the database tools in a bucket named ‘tools/db’. Both buckets will have read-only permissions for all users. We can do this with the mc MinIO command-line client or through the graphical UI that MinIO provides. For this tutorial, we will use the UI, but the command line would allow us to script this operation if required. To access the UI, we will need to forward a connection to the MinIO service running on kubernetes. In a terminal, run the following command: kubectl port-forward svc/minio-hl-svc 9000:9000 You should now be able to access the MinIO dashboard at http://localhost:9000 The default credentials, from the public sample config we deployed earlier, are minio/minio123 . Once we log in, we can create a bucket named ‘linux’ through the + → Create bucket button in the bottom right of the interface. Once this is created, it will appear in the left menu. Select this and upload the binaries you downloaded earlier, again using the + → Upload file button in the bottom right. Once all files are uploaded, you will need to allow read-only access to the bucket from anyone who has the link. This is to allow unauthenticated GET and HEAD HTTP requests to access the resource from our Ops Manager container. To enable read-only access, click the ... button on the ‘linux’ bucket and select Edit Policy. On the modal dialog, select Read Only and click Add , which will enable access. At this point, we should be able to validate the files that can be downloaded. Running the following HEAD request should now return a successful result: curl --head http://localhost:9000/linux/mongodb-linux-x86_64-ubuntu1604-4.2.3.tgz HTTP/1.1 200 OK Accept-Ranges: bytes Content-Length: 132149028 Content-Security-Policy: block-all-mixed-content Content-Type: application/gzip ETag: "397903bcabe29abd9d1258653270e76f-1" Last-Modified: Tue, 04 Feb 2020 17:44:10 GMT Server: MinIO/RELEASE.2020-01-03T19-12-21Z Vary: Origin X-Amz-Request-Id: 15F0DF60120863EB X-Xss-Protection: 1; mode=block Date: Thu, 06 Feb 2020 17:11:12 GMT Our S3 buckets are now ready to serve binaries for the Ops Manager instance. Let’s now configure it to consume these resources. Upgrade Ops Manager to 4.4.0 or Later In the previous tutorial, we created the ops-manager.yaml configuration file, which we will now edit to include the following options: spec version: 4.4.0 # This must be 4.4.0 or later to support the new HTTP endpoint as a source for binaries. configuration automation.versions.source: remote # This sets the endpoint that will serve mongoDB binaries and was retrieved earlier when we fetched the service name for our MinIO instance. automation.versions.download.baseUrl: http://minio-hl:9000 The updated configuration file should match the following: apiVersion: mongodb.com/v1 kind: MongoDBOpsManager metadata: name: ops-manager namespace: mongodb spec: # the version of Ops Manager distro to use version: 4.4.0 # the name of the secret containing admin user credentials. adminCredentials: ops-manager-admin-secret configuration: automation.versions.source: remote automation.versions.download.baseUrl: http://minio-hl:9000 externalConnectivity: type: LoadBalancer # the Replica Set backing Ops Manager. # appDB has the SCRAM-SHA authentication mode always enabled applicationDatabase: members: 3 version: 4.2.2 We can now update the running instance: kubectl apply -f ops-manager.yaml The deployment will take a few minutes to update, as it will need to redeploy the configuration with new pods. Check the status and ensure the Ops Manager resource gets to the “Running” phase: kubectl get om -n mongodb NAME REPLICAS VERSION VERSION (DB) STATE STATE (DB) AGE ops-manager 1 4.4.0 4.2.2 Running Running 13m Now, let’s connect to our Ops Manager instance through the UI Dashboard. Get the load balancer address, as with the previous tutorial: kubectl get svc ops-manager-svc-ext -o jsonpath='{.status.loadBalancer.ingress[0].hostname}' Create a MongoDB Replica Set At this point, everything should be in place to let us deploy mongoDB binaries using our MinIO instance. Let’s verify this, creating a new project and replica set using the Kubernetes Operator. First, let’s make the replica set configuration Create the file replica-set-s3-endpoint.yaml describing the new MongoDB resource, reusing the ops-manager-connection configMap from the previous tutorial: apiVersion: mongodb.com/v1 kind: MongoDB metadata: name: replica-set-s3-endpoint namespace: mongodb spec: members: 3 version: 4.2.3 type: ReplicaSet opsManager: configMapRef: name: ops-manager-connection credentials: ops-manager-admin-secret Apply it to the Kubernetes cluster: kubectl apply -f replica-set-s3-endpoint.yaml Wait until the resource enters the Running state: kubectl get mdb -n mongodb NAME TYPE STATE VERSION AGE my-replica-set-s3-endpoint ReplicaSet Running 4.2.3 12m Now, let’s verify this has deployed correctly in Ops Manager: Also, if we click on the modify button and click the versions dropdown, we will see the listing is limited to 4.2.3 and 4.2.2; the versions we uploaded to the MinIO instance. If the user configured a version that isn’t stored on the MinIO instance, we instead will get a deployment failure. The MongoDB Agent logs will give a clear error about which file and location could not be found on the remote endpoint, allowing admins to quickly identify where the files should be uploaded. To test this, let’s change the version to 4.2.1 on the replica-set-s3-endpoint.yaml and deploy using: kubectl -f apply replica-set-s3-endpoint.yaml In Ops Manager, a red deployment bar will be displayed for the deployment. If we click on the view agent logs link, the following will now be shown : Would you like to know more? Stay tuned for upcoming blog posts in this series, where we will continue to do deep dives on all things Ops Manager. Learn about how to backup Ops Manager, configure it for high availability, set up SCRAM and get an inside look at the architecture behind the MongoDB Enterprise Kubernetes Operator.

2020年8月28日
快速开始

释放你的天才MongoDB的阿特拉斯自由层亚博贵宾会贴吧

什么是免费的，永久使用，并可以帮助您探索所有的应用程序的想法？你猜对了 - 一个MongoDB的阿特亚博贵宾会贴吧拉斯自由层集群。显然有足够的理由使用更强大的集群，但在此之前，让我们探索阿特拉斯自由层的能力。它是免费的 - 你永远听到这里首先，乡亲们。你从来没有付出为您免费梯队集群，你可以保持它上，只要你想，在我们身上。这意味着有不需使用信用卡。我们投资在你的奇迹，和所有的好点子。为什么不测试他们全力以赴？新阿特拉斯？亚博贵宾会贴吧MongoDB的Atlas是我们的全面管理全球云数据库，提供最好的一流的基础设施，自动化和成熟的做法保证可用性，可扩展性和安全标准的合规性。 Atlas is available on more than 70 regions across AWS, GCP and Azure on our M0 free tier or our paid tiers (starting at M2). The most popular features of Atlas are available on paid and free clusters . Features like MongoDB Atlas Search help you design and deliver top-notch built-in search capabilities. The Collections view lets you inspect and interact with your data. It also provides the Aggregation Pipeline Builder , which allows you to learn, test and visualize MongoDB’s aggregation framework. You can also use your free tier cluster to test out MongoDB solutions that come integrated with Atlas, such as MongoDB Realm and MongoDB Charts , which both have their own free tier versions. Free tier clusters are a great opportunity to start innovating at no cost. If you decide you want something more powerful, upgrading to a larger tier has never been easier. To get yourself an account, sign up for Atlas today. Atlas Veteran? If you already know your way around a cloud database, why would you use a free tier cluster? No matter where you are in your Atlas journey, free tier clusters can be useful for development environments, proof of concepts, checking out new Atlas features, and demos. No matter how many projects you have, you can always spin up one free tier cluster per project. It’s Advantageous Free tier clusters are deployed on the latest battle-tested version of MongoDB, meaning you’re getting all the perks (on-demand materialized views, client side FLE, wildcard indexes), with none of the cost. For more information on what you’d get with a free tier cluster today, read through this blog post, which discusses free tier features on MongoDB 4.2 . Free tier clusters come with 512MB of storage. If you’re curious about what you can do with that, we have a few ideas to get you started: Build a search engine in less than 10 minutes with MongoDB Atlas Search, test out MongoDB with new programming languages , or kickstart your Atlas learning process with our sample data sets . It’s Distributed Atlas free tier clusters are available on the cloud provider of your choice in the most popular regions, including AWS North Virginia, Google Cloud São Paulo, and Azure in the Netherlands. We’ll be expanding to more regions in the future, so if you don’t have access to your preferred region now, it won’t be long until you do. To see all the free tier options available, simply create a new cluster in the Atlas UI. The best way to check out all the features available on free tier is to play around with one yourself… What are you waiting for?

2020年8月14日
家

准备好开始使用MongoDB的阿特拉斯？亚博贵宾会贴吧

入门