The office is a productivity suite, developed and maintained by one of the biggest companies, market leaders in technology, Microsoft Office. You must already have gotten your answer, Microsoft is not just another company that poses to be developing great software with just a team of 100 members but Microsoft is a big company that needs to keep its reputation and work always on par with the revenue they are getting. This means they need to hire the best people to get the job done and that’s how it works in Microsoft. There is no issue with Microsoft, but the only issue is that Microsoft has been the target for hackers for quite a while now, It is one of the easiest targets anyone can find when it comes to the customer base and data theft. The data Microsoft has stored on their cloud servers is enormous and is really important for most of the people.
I'm seeing some of our internal Red Hat builders going OOM and killing
ceph builds. This is happening across architectures.
Upstream our braggi builders have 48 vCPUs and 256GB of RAM. That's not small.
What is the minimum memory and CPU requirement for building pacific?
Internally, to use one ppc64le example, we're running with 14Gb RAM
and 16 CPUs, and the RPM spec file chooses -j5, hitting OOM. We tuned
mem_per_process from 2500 to 2700 a while back to alleviate this, but
we're still hitting OOM consistently with the pacific branch now.
due to a meeting conflict, we've moved the Moving Orchestrator Weekly to
The event in the Ceph Community Calendar is already updated. See
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
(HRB 36809, AG Nürnberg). Geschäftsführer: Felix Imendörffer
At this point PRs should be targeted to master, and if you have a bug
fix for pacific you should create a PR cherry-picking it from master.
No tracker ticket is needed at point for pacific-only bug fixes.
If fix should be applied to nautilus or octopus as well, please add a
tracker ticket for it as usual.
Hey folks, ceph is a large system, and like any large system testing it
can be quite complex.
To help new and existing developers I'd like to organize some training
sessions on different aspects of testing, and record these for
We can start out with basics, like how to run tests, and then cover more
complicated topics like how to develop new teuthology tasks, or cephadm
integration. This can also be a useful source of content for updating
the developer docs, like Deepika Upadhyay is doing here:
Here's an etherpad to capture topics to cover - please take a look and