MongoDB 3.2.0-rc3 is out and is ready for testing. This is the culmination of the 3.1.x development series.
Fixed in this release candidate:
- SERVER-20164: Finish unit tests for CatalogManagerReplicaSet::addShard
- SERVER-21287: $lookup should use $eq queries
- SERVER-21298: rollback_index.js fails to wait for replication before continuing
- SERVER-21292: replsets/remove1.js failed in replset_legacy suite
- SERVER-20937: Add mode to FSM framework that drives greater amount of load on the system
- SERVER-21099: Improve logging in SecureRandom and PseudoRandom classes
- SERVER-20402: Add Election Failover JS tests
- SERVER-21308: fsm-suite doesn’t wait long enough for the distributed lock when dropping a collection
- SERVER-20867: Integrate mongobridge into ShardingTest
- SERVER-21355: Coverity analysis defect 76731: Unchecked return value
- SERVER-21305: Lock ‘timeAcquiringMicros’ value is much higher than the actual time spent
- SERVER-21371: find_and_modify_concurrent_update.js join() is called after read
- TOOLS-983: mongorestore panic when restoring a compressed archive without using –gzip
Want to test the release? Get involved in the MongoDB Bug Hunt and enter for a chance to win some prizes for your contributions.
As always, please let us know of any issues.
– The MongoDB Team
MongoDB Authentication and Automation
MongoDB supports role-based authentication, so you can restrict access to your deployment for safety and security. Cloud Manager Automation makes enabling and managing your users easy. An important note before we begin: Authentication Settings made here apply to your entire Cloud Manager group. If you are using Automation, and it’s vital that different deployments in your group have different credentials, you will have to create a new Cloud Manager group for these deployment items and import them . Enabling Authentication If you already have authentication enabled, follow the normal importation into Automation methodolgy , especially noting the creation of a new automation-agent user, then you can skip this section and go on to the role and user management sections below. If you have an unauthenticated deployment: Click the “…” menu on your Deployment Page and choose “Authentication & SSL Settings” Click “Next” to get to the “Select Authentication Mechanisms” screen Select “Username/Password” and click “Next”. Click “Next” again to skip the SSL settings (a topic for this other post ). Now you will see the new users that will be automatically created for you. Click “Save” to create a new automation draft with your new users. Now you just have to “Review & Deploy” and “Confirm & Deploy” as normal. Beware: Clients without authentication will fail to connect after this point. Make sure your application is ready for this change. Check your drivers’ documentation on how to enable MongoDB authentication in your application. Role Management Let’s start with adding a new role: Head over to your “Authorization & Roles” tab When you click the “Add Role” button in the upper-right, you will be presented with a dialog to fill out: You can even add collection-level and other privileges if you want In my case, I’ve let my reader role also be able to do certain diagnostic actions Once the role is added, you just have to do the usual “Review & Deploy”/”Confirm & Deploy” to push this role out to your group. Once the role has been created, you can edit or remove it via the gear icon, as shown below. You can only edit custom roles, not built-in roles . Users Once you have the roles you need (if you need custom roles at all), you can start creating users. Head to your “Authentication & Users” tab Create a new user via the “Add User” button in the upper-right You can choose any custom or built-in roles you wish and enter the user’s password Once the user is added, you just have to do the usual “Review & Deploy”/”Confirm & Deploy” to push this user out to your group. Once the user has been created, you can edit or delete it via the gear. You cannot edit the built-in users for the agents. Removing Authentication Maybe you have moved your deployment into a private network and have decided to remove your authentication settings. Here’s how: Click the “…” menu on your Deployment page and select “Authentication & SSL Settings” Click “Next” to get to the “Authentication Mechanisms” screen and un-check “Username/Password” Click “Next” to skip the SSL settings, and then click “Save” When you next do a “Review & Deploy”/”Confirm & Deploy”, the Automation Agents will disable authentication. All your custom roles and users will remain cached in Cloud Manager in case you wish to re-enable authentication. You can edit them even when authentication is not enabled.
How Thoughtful Illustration Is Setting MongoDB Apart: Meet Champa Lo
I sat down with Champa Lo, Technical Illustrator based in our New York headquarters, to learn more about her role as the first full-time illustrator at MongoDB. We talked about her passion for illustration, what she does, and how she’s shaping the future of design within the company. Ashley Perez: Welcome to the team! Can you tell me about your role? Champa Lo: Sure. I joined MongoDB right before COVID-19 hit. I came into the headquarters twice for an interview but ended up being one of the first new hires who had to start at home, on top of being the first person in a brand-new role. Technical Illustration is a first for MongoDB. The company has never had an illustrator on hand. Although we have talented designers who can illustrate within a design, that’s not their main focus: the overall design is. The difference with my role is that I work specifically on illustration. I also work to define the illustration style and help create a style guide. The most important aspect of my job is building good relationships with people throughout the company. I need to understand their goals and what they’re looking for so I can tell a purely visual story. AP: How did you get into illustration? CL: I guess you can say I fell into it (at least the illustration part). I always knew I wanted to be a graphic designer early on. I was a mentee for a graphic designer in high school and absolutely fell in love with the profession. I even have a cute clipping from my senior year high school paper where I talk about my dreams of being a designer. Interview excerpt from Champa's senior-year high school newspaper After high school, I studied graphic design at the University of Colorado Denver. When I was in the design program, I always found ways to incorporate fun illustrations in my projects. A year after I graduated, I moved to New York City because there were more jobs in design there and landed a job that allowed me to put my illustrating skills to good use. My first job was working with an incredible Creative Director at a small startup who built an amazing brand using illustrations to convey the company’s goals and messages. This was a part-time job: for four hours a day, I would concentrate on illustrating bespoke email banners for marketing prompts the team created that morning. With her guidance, I saw my illustration skills grow. It showed me the possibility of being a full-time illustrator. Here’s an example of a design I did while I was there: Email banner Champa created for ThinkEco during her first job as illustrator I love to illustrate (especially this type of illustration) because I’m a designer by trade, and the core of designing is to problem-solve. Illustration is no different. As a Technical Illustrator, I simplify and visualize complicated theories and concepts. Also, it’s fun! If I’m not having fun while illustrating, I’m very unmotivated. My creativity relies on avoiding boredom. I’m always working to improve my artistic skills. I’m a lover of learning, so I subscribe to tutorial sites such as Skillshare; follow artists on YouTube who share tutorials; and subscribe to a monthly art box that sends paints, brushes, pens, and so forth so I can try new mediums. Champa's illustration for a Google Local Guides social media post AP: How do you make your illustrations purposeful, engaging, and memorable? CL: Having thoughtful conversations about the subject matter is how you get good designs and illustration. If you don’t understand the subject to the best of your ability, how can you be successful at visualizing it? In school, I was taught to always research your subject matter and not design blindly. Putting in the extra work makes a huge difference. That’s also why 1:1 meetings are so important. It’s a time for me to learn, and it’s also a creative process for the stakeholders, because they find creative ways to help me understand. GIF Champa created for a MongoDB University Page We want to understand the goal. For example, should the illustration be futuristic or nostalgic? Recently, we had a conversation about cars and how we wanted to present them for a project. We decided to design the cars as compact or electric to show MongoDB as forward thinking and environmentally conscious, because those are the kinds of people we want to hire and work with. Or take COVID-19, for instance. The pandemic has changed the way people illustrate office environments. No longer do you have teams sitting in conference rooms. Instead, you have people working at home. So, I had to think of things to illustrate such as a sofa, home desk, and desk lamp. Maybe even a dog or a child. We thought about how we could incorporate this into the Zoom interface. Before, we didn’t have to think about it. Now, Zoom can be a way to add some personality to everyone’s digital space as we work remotely. That’s what I’m here for. To have those conversations and get deeper behind the meaning of everything we create. AP: Let’s talk a little more about your role at MongoDB. What projects do you work on? CL: I’m part of the Visual Design Team, which supports the whole company. It’s fun to meet and talk to many different people at MongoDB. It gives us a lot of diversity in the projects we work on. Along with illustrations, I also work on diagrams and small animations. Projects include campaigns, web illustrations, and events. Because I’ve joined the team, we’re able to have fuller discussions about illustration. Our designers work in a fast-paced world, but my process is slower because I make more bespoke illustrations and have to talk to people to understand the technicalities so we can go beyond generic illustrations. I have to be more thoughtful of what we’re presenting to the audience. Even though by having these conversations I slow down how quickly the designers move, I'm striving to build stronger relationships on the team through this practice. Top left: Champa’s illustration for MongoDB's new multi-cloud feature. Bottom right: An illustration for MongoDB's vendors page. I have found that by showing and explaining my illustration process and inviting them into it, people seem to trust me more. For example, I always share my sketches with stakeholders before digitizing the work. My sketches aren’t perfect, but by showing them not-so-perfect work, we can build the relationship and align on ideas. My hope is that the sketches allow people to see I’m open for collaboration and conversation. Example of a project working with MongoDB's Web Design team from initial sketch through final illustration AP: How does having these conversations help your design? CL: Great question! Working with such a diversity of people and projects helps me gain an immense amount of knowledge and insight. Past conversations and concerns help inform my design decisions. I’m almost like a liaison for all these different departments, and it's nice to transfer the information so we’re all aligned. For example, I’ve been working closely with Product Marketing on diagrams, and soon I’ll be working on diagrams with a member from the Docs team, too. Each team has taken its own paths for diagrams, but I would love to eventually create a holistic style that works for all teams beyond just these two. I believe having a good process to follow leads to meaningful and engaging illustrations. However, it’s important to find balance. You can’t overengineer it, because that can easily turn unproductive and formulaic. I always want an open dialogue and strive to show there’s room to collaborate. The process we have created has been successful so far, but it’s not set in stone. Further along we can add another step, or we may find certain things aren’t needed. AP: What’s your creative vision for MongoDB? CL: My goal for illustration is that we are inclusive, diverse, and thoughtful. What I’ve seen here is a global company full of people who are very passionate and kind. As designers, we have the power to show who and what MongoDB is. For me, that’s showing off who we are. One of our company’s values is “Own What You Do.” I think it’s such an important one for designers, because we should always add our personal experiences and perspectives to our work and translate the rest of the company’s perspectives and experiences, too. For the team, my goal is to continue streamlining a process so we’re transparent and support a collaborative spirit when it comes to working with us. Champa’s illustration for the MongoDB Atlas onboarding experience My goal is to create a unified vision between our two audiences: developer and enterprise customers. My hope is the illustrations bring joy and delight, and that our audiences see MongoDB has a personality. A really effective illustration system is memorable, and our research is starting to show that our audiences are beginning to remember our visuals. This is a huge brand lift, creating a personal experience versus the cold one people may experience with other tech brands. Interested in pursuing a career at MongoDB? We have several open roles on our teams across the globe , and would love for you to build your career with us!