# ceph Ceph is an open-source distributed storage system providing unified object, block, and file storage. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Self-Hosted Platform Build Order: Dependencies from Bare Metal to Model Serving DevFeed: [Self-Hosted Platform Build Order: Dependencies from Bare Metal to Model Serving]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-04T07:00:00Z Content type: article Language: en Sources: [Philipp Lehmann]() Topics: [Self-hosted](), [Ansible](), [Kubernetes](), [ceph](), [observability](), [model-serving](), [Compose]() Tags: [ansible](), [architecture](), [article](), [ceph](), [compose](), [infrastructure-as-code](), [kubernetes](), [model-serving](), [observability](), [self-hosted]() ### AI overview This article explains the dependency order for building a self-hosted platform. It covers consistent bare-metal inventory, Ansible configuration convergence, networking, Kubernetes, Ceph storage, identity, observability, and model serving. ### Source excerpt Self-hosted platform build order: why mesh, cluster, Ceph storage, identity and observability must precede model serving, shown with Compose depends_on. ## Recover the Ceph Monitor Store Using OSDs DevFeed: [Recover the Ceph Monitor Store Using OSDs]() Original publisher: [Read original article]() Author: Eugen Block, crossposted by Anthony D'Atri Published: 2026-07-04T00:00:00Z Content type: article Language: en Sources: [Ceph Blog]() Topics: [ceph](), [monitor](), [Script](), [Containers](), [log management]() Tags: [blog](), [blog-post](), [ceph](), [containers](), [en-article](), [en-blog-post](), [how-to](), [logging](), [logs](), [mon](), [monitor](), [recovery]() ### AI overview This blog post presents a general procedure for recovering a failed Ceph Monitor store by collecting osdmaps from existing OSDs, with additional considerations for cephadm-managed container deployments. It automates osdmap collection and basic logging while leaving the store rebuild and client authentication steps for careful manual inspection. The procedure applies only to non-encrypted OSDs, and the article emphasizes the importance of backing up dmcrypt/LUKS keys and reviewing host logs. ### Source excerpt Introduction ¶ A few weeks ago I helped a Ceph user to recover his broken cluster (see this thread). Basically, after his Monitors stopped working he re-deployed a new cluster with the same Ceph FSID and attached the existing OSDs to the re-deployed hosts. But it's not that easy to re-activate those OSDs because the new Monitors don't have the old osdmap, hence they don't know anything about the existing OSDs. So how did we fix that? This scenario can be considered a total Monitor store failure. There's a documented procedure in the upstream docs, unfortunately it's written for non-cephadm clusters and doesn't contain many details about subsequent steps. When Ceph daemons run within containers there are more things to consider. So I decided to write this blog post and add some more details to the procedure, targeting mainly clusters managed by cephadm. But the recovery procedure doesn't specifically require cephadm-specific commands, so it can be considered as a general guideline how to recover from a Monitor store loss, just with some extra details about cephadm deployments. This procedure only works for non-encrypted OSDs. If you are using dmcrypt (LUKS) OSDs, make sure you have a backup of the keys, otherwise your data is lost forever! But there is some development, a user in Slack pointed me to this PR which adds a backup mechanism for Monitors, probably available in the upcoming Umbrella release. Note that the PR also contains this statement: Monitor backups complement, but do not replace, the existing Monitor recovery procedures The procedure covered by said docs is already written in script form, so I used that as a template and extended it for cephadm usage and included some very basic logging. It collects the osdmaps from all OSDs and contains the necessary considerations regarding containers. I decided to automate only the osdmap collection, not all required steps of the store rebuild procedure (e. g. Monitor store rebuild, client auth, etc.) because the r ## Ceph Q2 2026 Newsletter DevFeed: [Ceph Q2 2026 Newsletter]() Original publisher: [Read original article]() Author: Anthony Middleton Published: 2026-06-25T00:00:00Z Content type: article Language: en Sources: [Ceph Blog]() Topics: [ceph](), [releases]() Tags: [2026](), [blog-post](), [ceph](), [ceph-events](), [collaboration](), [communication](), [community](), [contribute](), [developers](), [documentation](), [ecosystem](), [en-article](), [en-blog-post](), [event](), [governance](), [growth](), [metrics](), [newsletter](), [operational](), [operations](), [releases](), [resources](), [support]() ### AI overview The Ceph Q2 2026 Newsletter covers governance coordination, community elections, documentation initiatives, contributor resources, regional Ceph Days events, project releases, and ways to contribute. It emphasizes collaboration among users, developers, operators, and organizations across the Ceph ecosystem. ### Source excerpt During the second quarter, the Ceph Foundation focused on strengthening collaboration across the project, expanding community programs, supporting documentation efforts, and investing in regional events. This edition highlights recent governance discussions, community elections, new contributor resources, Ceph Days events, and opportunities for community members to get involved. If you have an idea for a Ceph-related event, outreach effort, or project, we encourage you to submit a funding request and work with the Foundation to help bring it to life. In This Issue ¶ Board and CSC Alignment on Community Priorities 2026 CSC Election Recap Meet the New Ceph Technical Writer Ceph Days Continue to Grow Latest Ceph Releases Community Committees and New Ways to Contribute Board and CSC Alignment on Community Priorities ¶ The Ceph Governing Board and Community Steering Committee (CSC) met this quarter to discuss the long-term health of the project, governance, documentation, community growth, and Foundation-supported initiatives. The discussion reaffirmed the distinct roles of each organization within the Ceph ecosystem. The CSC continues to provide technical governance for the project, while the Ceph Foundation focuses on community growth, events, outreach, and funding. The Linux Foundation provides operational, legal, and financial support that enables both groups to operate effectively. A significant area of focus was improving coordination between technical priorities and Foundation-supported programs. Current documentation initiatives include improvements to the documentation backport process, development of a new OSD operations guide, clarification of package and container documentation, and the removal of outdated content. The Board and CSC also discussed the future of community events and the importance of establishing clear goals and success metrics for Foundation-funded programs. Both groups reaffirmed their commitment to supporting collaboration between users, de ## Migrating from VMware to Proxmox VE at 3,000-Core Scale DevFeed: [Migrating from VMware to Proxmox VE at 3,000-Core Scale]() Original publisher: [Read original article]() Author: Shivam Anand Published: 2025-08-23T08:25:07Z Content type: article Language: en Sources: [Shivam Anand - DevOps & Cloud Engineering Blog]() Topics: [Proxmox](), [virtualization](), [migration](), [Automation](), [Command-line interface](), [ceph](), [NVMe]() Tags: [automation](), [ceph](), [cli](), [kvm](), [migration](), [nvme](), [proxmox](), [virtualization-cloud-infrastructure](), [vmware]() ### AI overview The article describes a three-month migration of 3,000 CPU cores, 8 TB of RAM, and production and archival storage from VMware to Proxmox VE. It explains the use of NFS, Ceph, and a custom CLI orchestrator to manage the resulting infrastructure. ### Source excerpt Discover how I migrated 3,000 cores, 8TB RAM from VMware to Proxmox VE, built a custom CLI orchestrator, and leveraged Ceph storage for seamless management. ## How to Upgrade Proxmox 7 to 8 DevFeed: [How to Upgrade Proxmox 7 to 8]() Original publisher: [Read original article]() Author: Techno Tim Published: 2023-06-24T15:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Proxmox](), [Debian](), [apt](), [Linux](), [Kernel](), [qemu](), [ceph](), [x86](), [Text-based user interface]() Tags: [apt](), [debian](), [how-to](), [kernel](), [linux](), [new-features](), [proxmox](), [qemu](), [upgrade](), [virtual-machines](), [x86]() ### AI overview A practical guide to upgrading a Proxmox server from version 7 to version 8. It covers backups, checking the installed version, running upgrade checks, applying current updates, and updating Debian and Proxmox apt repositories to Bookworm. ### Source excerpt Proxmox 8.0 has been released (June, 22, 2023) and includes several new features and a Debian version upgrade. Among the changes are: Debian 12 "Bookworm", but using a newer Linux kernel 6.2 QEMU 8.0.2, LXC 5.0.2, ZFS 2.1.12 Optional Text mode installer (TUI) New default CPU type x86-64-v2-AES for VMs Ceph Quincy 17.2.6 and a new, stable Ceph Enterprise repository Authentication r... ## Integrating Confluent Schema Registry with Apache Spark applications DevFeed: [Integrating Confluent Schema Registry with Apache Spark applications]() Original publisher: [Read original article]() Author: Dominik Liebler Published: 2022-01-24T08:04:19Z Content type: tutorial Language: en Sources: [YAZIO Engineering - Medium]() Topics: [Kafka](), [Apache Spark](), [Streaming](), [data lake](), [parquet](), [Kotlin](), [Kubernetes](), [ceph](), [JSON Schema]() Tags: [apache-spark](), [backpressure](), [ceph](), [confluent](), [data-engineering](), [data-lake](), [data-pipeline](), [json](), [kafka](), [kotlin](), [kubernetes](), [parquet](), [payload](), [pipelines](), [schema](), [schemaregistry](), [serialization](), [spark](), [streaming]() ### AI overview This engineering article explains YAZIO's data pipeline from mobile and web applications through Kafka and Spark Structured Streaming into a Ceph-based data lake. It discusses why schemas matter and describes replacing JSON with Apache Avro and Confluent Schema Registry to reduce message size while keeping schema information externally stored and cached. ### Source excerpt At YAZIO, we believe in making decisions backed by data to help people live healthier lives through better nutrition. For each new and existing feature we want to evaluate how well it performs and how our users interact with it. In order to do so, we need a lot of data and we need to handle backpressure in our systems. To cope with that we use a Kafka cluster managed by Strimzi operators running in Kubernetes. The data itself is being ingested from our mobile and web apps via HTTP or TCP endpoints serialized into JSON and stored in Kafka by a small application written in Kotlin/JVM. Overview of our data pipeline architecture At the other end of the pipeline, different Spark Structured Streaming applications (also written in Kotlin) dump this information into our data lake residing in a Ceph bucket. They read data from Kafka, deserialize it, transform some of the fields and write Parquet files into the data lake using a new schema. Why schemas? Schemas play an important role in data pipelines because they give meaning and context to data. In a world without schemas we would still do random interpretations about the context and meaning of data every now and then when using it. As you might have guessed already this would lead to a lot of bugs and misunderstandings. Photo by EJ Strat https://unsplash.com/photos/VjWi56AWQ9k Similar to a legal contract that binds you to certain limits, a schema binds the data to certain limits and meaning which narrow down the need of interpretation. Choice of serialization formats At the time of writing, Confluent Schema Registry supports these three serialization formats: Apache Avro Protocol Buffers (protobuf) JSON Schema From those choices, only two really provide more than just validation of the data that is ingested and transmitted through our data pipelines. Avro and Protobuf also allow us to shrink the sizes of our topics because only the payload is contained in a message, while the repeating schema will not be stored. In the cas ## Allas November 2020 incident details DevFeed: [Allas November 2020 incident details]() Original publisher: [Read original article]() Author: Kalle Happonen (noreply@blogger.com) Published: 2020-12-22T12:31:00Z Content type: article Language: en Sources: [CSC - IT Center For Science - Cloud Team]() Topics: [ceph](), [incident](), [Amazon S3](), [rocksdb](), [NVMe](), [Processes](), [Vapor]() Tags: [ceph](), [deep-dive](), [incident](), [nvme](), [processes](), [rocksdb](), [s3](), [software](), [storage](), [swift](), [technical]() ### AI overview A technical deep dive into the November 2020 Allas downtime incident. It describes Allas as a Ceph cluster and explains its storage nodes, OSD processes, S3 and SWIFT access, replicated metadata pools, RocksDB metadata, placement groups, and erasure-coded object storage. ### Source excerpt Allas downtime November 2020 - technical deep-dive We use Ceph (https://ceph.io/) to provide software defined storage in our Allas service. I'll try to speak some Ceph here. There may be a lot of unfamiliar terms for most readers here as we dive deep into a technology. I'll try to clarify where I can, but architectural knowledge of Ceph helps when reading this. Allas is a Ceph cluster with 48 storage nodes (OSD nodes). Each has one nvme, 24 spinning disks, and 192 GiB of memory. Each OSD node runs one OSD process per disk. The Allas storage is provided over SWIFT and S3 protocols through radosgw daemons. The radowsgw layer is provided by separate internet facing servers. In addition we have 5 nodes running monitor processes (they control the state of the cluster), which also run Ceph manager (handles more advanced monitoring views into the cluster state). The object store metadata pools are 3-way replicated pools (data is stored in 3 different copies) on the nvmes across the OSD nodes. This metadata contains e.g. owners of buckets and objects, permissions, versions, etc. Everything that has to do with S3/SWIFT. The nvme also hosts the rocksdb (ceph internal metadata, as opposed to object store metadata) for the OSDs. This metadata is internal Ceph clustster status. Data on placement groups, etc. I'll use the term placement group (or pg) quite a lot in the post as they are central for Ceph. Basically when you store data objects into Ceph, they are mapped into placement groups, which define where in the cluster the data is are stored. The object store data is stored on an 8+3 erasure coded (data is split into 8 chunks + 3 parity chunks) pool on the spinning disks. The total amount of placement groups for the data pool is 16 384. In the graph the amount ~18 000 is shown, as the graph contains other pools too. The beginning Side note: I love that we collect trending data for our cluster (collectd+graphite in our case). As we had the data stored from a long time, this al ## Preparing a Proxmox Server for Production Use DevFeed: [Preparing a Proxmox Server for Production Use]() Original publisher: [Read original article]() Author: Techno Tim Published: 2020-11-28T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Proxmox](), [networking](), [ceph](), [Linux]() Tags: [ceph](), [clustering](), [hardware](), [iommu](), [linux](), [networking](), [proxmox](), [ssh](), [storage](), [tutorials]() ### AI overview A tutorial covering the author's preparation steps for newly installed Proxmox servers, including updates, storage, networking and VLANs, ISO uploads, clustering, PCI passthrough, cloned Linux machine cleanup, and alerts. ### Source excerpt After setting up my Proxmox servers, there are a few things I do before I use them for their intended purpose.This ranges from updates, to storage, to networking and VLANS, to uploading ISOs, to clustering, and more.Join me as we pick up where the rest of the proxmox tutorials stop, and that's everything you need to do to make these production ready (and maybe a bonus item too). 📺 Watch Vide... ## Migrating cPouta Object Storage to the Allas Ceph Service DevFeed: [Migrating cPouta Object Storage to the Allas Ceph Service]() Original publisher: [Read original article]() Author: Kalle Happonen (noreply@blogger.com) Published: 2019-12-27T11:23:00Z Content type: article Language: en Sources: [CSC - IT Center For Science - Cloud Team]() Topics: [ceph](), [migration](), [Data Management](), [data](), [cloud-infrastructure]() Tags: [ceph](), [data-management](), [migration](), [object-storage](), [openstack](), [radosgw](), [rgw](), [storage]() ### AI overview This article describes CSC's migration from the cPouta object storage service to Allas, a standalone Ceph-based object storage service. The plan aimed to move user data without requiring user changes or breaking existing data links, using a new Ceph cluster and new data pools. ### Source excerpt We have released our new Allas object storage service. We firmly believe it will play a growing role for data management, at CSC and for the whole academic field in Finland. Alas, the road to Allas was not completely without pain. CSC also hosts the cPouta IaaS service. It provided its own object storage service. Our goal with Allas was to build on this, and transform the object storage portion to a standalone service. This would raise the profile of the service, and make it easier to scale, both human resource wise and where it comes to the platform size. So, in brief, our aim was: Replace cPouta object storage with Allas Make sure all the user data from cPouta object storage moves over. Make sure cPouta object storage users don't have to do any changes. Don't break any existing links to data in cPouta object storage. How did we intend to do this, you may ask? Migration plan What were our options? We had a large bunch of new hardware, and a high level plan. For those of you who know Ceph, you might have already thought of how you'd do this. Add more hardware to the same storage pool, slap on an additional domain name to access the data, and call it a day. Create additional data pools, make sure radosgw uses old and new pools for data, slap on an additional domain name, and call it a day. Create a new Ceph cluster with new pools, migrate the data over, add the old and new domain names, and call it a day. Number 3. is definitely the most work, but we went with that. The main reason for that was that if we want to achieve all the benefits of separating Allas into its own service, we actually need to be a bit separate. For example, the old object storage pools were in the same cluster as the block storage pools used by our OpenStack virtual machines. This not only locked us to the current version of Ceph running there, but created a lot on interdependencies between the services. To make it easier, I'll use the terms rgw-old (cPouta object storage) and rgw-new (Allas) t ## Object Storage Use Cases Part 3: Storing binary files in Object Storage instead of in your git repository DevFeed: [Object Storage Use Cases Part 3: Storing binary files in Object Storage instead of in your git repository]() Original publisher: [Read original article]() Author: Unknown (noreply@blogger.com) Published: 2019-04-29T09:06:00Z Content type: tutorial Language: en Sources: [CSC - IT Center For Science - Cloud Team]() Topics: [Git](), [ceph](), [pip](), [Haskell]() Tags: [aws](), [ceph](), [data](), [data-lake](), [git](), [install](), [object-storage](), [python](), [rados](), [radosgw](), [s3](), [storage]() ### AI overview This post explains why binary files should not be stored directly in Git repositories and explores using CSC's Pouta Cloud Object Storage instead. It documents attempts with git-annex and git-bigstore, including a patch to configure a non-default S3-compatible endpoint. ### Source excerpt 1. It's bad to store binary blobs in git. This is known [1] 2. A great place to store binary files is in object storage 3. Can we use CSC's Pouta Cloud Object Storage service for this? Why yes, yes you can! This is a post in a series about different use cases for object storage. Others include for example hosting a reveal.js presentation and NFS server backups More details about CSC's Pouta Cloud Object Storage Service, it is based on CEPH Rados Object Storage Gateway. What The general solution* to storing binaries in git is to not store them in git and instead create a link to some other place Attempt 1 Install an application that you like. In https://www.perforce.com/blog/storing-large-binary-files-in-git-repositories I searched for "S3", found git-annex which had recent commits so it looked like it wasn't dead. Installation instructions: https://git-annex.branchable.com/install/ The version in EPEL/Ubuntu Xenial does not have S3 support and is from 2014. There's a recent one in Fedora's repos though. Unfortunately, compiling it requires cabal. I don't know Haskell. https://spack.readthedocs.io/en/latest/package_list.html does not have any Haskell, cabal or git-annex available. Next. Attempt 2 Next application in the blog post was https://github.com/lionheart/git-bigstore To install it was much more comfortable for me: pip install "git-bigstore<=2.0" First issue was that looking at https://github.com/lionheart/git-bigstore/blob/master/bigstore/backends/s3.py there was no way to tell it to use another endpoint than the default of AWS S3. A small patch takes care of that, add , endpoint_url='https://object.pouta.csc.fi:443' to the client() boto3 call in the backends/s3.py file from git-bigstore. For a more detailed example see this Pull Request. After spending some time going down some rabbit holes it seems that the Profile option that is supported in git-bigstore does not support endpoints. It can only be used to specify credentials and a few other parameters. Mino ## cPouta Cloud Object Storage Service has been updated to run CEPH Luminous! DevFeed: [cPouta Cloud Object Storage Service has been updated to run CEPH Luminous!]() Original publisher: [Read original article]() Author: Unknown (noreply@blogger.com) Published: 2019-02-06T10:03:00Z Content type: release Language: en Sources: [CSC - IT Center For Science - Cloud Team]() Topics: [ceph](), [Amazon S3](), [Cloud](), [configuration](), [Command-line interface]() Tags: [amazon-s3](), [api](), [automatic](), [ceph](), [cli](), [configuration](), [cpouta](), [format](), [object-storage](), [openstack](), [radosgw](), [s3](), [storage](), [upgrade](), [xml]() ### AI overview The CSC Pouta Cloud Team describes an upgrade of its Ceph Object Storage Gateway from Jewel to Luminous. The update enables AWS4 signatures by default and adds support for several S3 features, including bucket lifecycle, website hosting, and request payment. The article also begins an example of configuring an S3 lifecycle policy with s3cmd and XML. ### Source excerpt We (the CSC Pouta Cloud Team) has finally upgraded CEPH Object Storage Gateway from Jewel to Luminous! There may come more blog posts about other improvements to other of our Openstack services (cinder and glance) which use CEPH. No need to use s3 --signature-v2 anymore! Before this upgrade, anyone using the S3 protocol needed to use the "AWS2" for most actions to work. Now that we run Luminous it is no longer necessary and the default AWS4 signature is working. Yay! In general things should be faster, shinier and also more API calls are supported. Comparing http://docs.ceph.com/docs/luminous/radosgw/s3/ and http://docs.ceph.com/docs/jewel/radosgw/s3/ these features* have gone from unsupported to supported: Bucket Lifecycle Supported Removing expired files is supported Bucket Website Supported Bucket Request Payment Supported Which got me a bit excited! Now to learn a bit about these and see if they work on our setup and if possible if we can make them work without breaking anything for existing objects & users: Bucket Lifecycle This is about expiration/automatic removal of objects at a certain time or after a certain time has passed. Let's start with S3 Some more details about the policies from Amazon S3: https://docs.aws.amazon.com/AmazonS3/latest/dev/lifecycle-configuration-examples.html https://docs.aws.amazon.com/AmazonS3/latest/dev/set-lifecycle-cli.html Telefonica open cloud has some nice documentation with s3cmd examples: https://support.telefonicaopencloud.com/en-us/ugs3cmd/obs/en-us_topic_0051518501.html I have not found anything better on docs.ceph.com -- Step 1. Create a lifecycle policy with s3cmd and in the XML format. (there is a JSON style with awscli and "aws s3api get-bucket-lifecycle-configuration --bucket mybucketname" ): Call the file expiry.xml and make the content something like this: ExampleRule expire_these_ Enabled 1 ) Original publisher: [Read original article]() Author: Unknown (noreply@blogger.com) Published: 2018-11-26T14:44:00Z Content type: release Language: en Sources: [CSC - IT Center For Science - Cloud Team]() Topics: [cloud-infrastructure](), [ceph](), [Hardware]() Tags: [capacity](), [ceph](), [cpouta](), [energy](), [hardware](), [hpc](), [standard](), [storage]() ### AI overview The communiqué announces changes to cPouta VM flavours: several older HPC flavours will no longer be available for new launches, while new hpc.4 and standard.xxlarge flavours will be added. The hpc.4 flavours use Ceph for VM root-disk backing storage, replacing older hardware without adding cPouta capacity. ### Source excerpt We are making some changes to the cPouta flavours offering tl;dr You won't be able to launch _new_ hpc-gen1.*core, hpc-gen2.2core, hpc-gen2.8core, hpc-gen2.16core flavours. We are adding hpc.4 flavours. We are adding a standard.xxlarge flavour. The new hpc.4 flavours The hpc.4 flavours are similar to the similarly named flavour in ePouta. The big difference between the hpc-genX is that hpc.4 will be using Ceph as default backing storage for VM root disks. We have wholesome experiences from Ceph in ePouta where all hpc-flavours are using Ceph as backing storage. One of the benefit is that if a hypervisor breaks, we can either migrate the customer instances away without customer noticing anything, or if the hypervisor has catastrophic failure the instance can be booted up on a new hypervisor without loss of data. Furthermore the sequential reads are much faster than on local spinning disks. This change will not bring additional capacity in cPouta, but replace old energy inefficient hardware in-kind with newer hardware. The new bigger standard flavour standard.xxlarge The standard flavours are the most popular flavours by a huge margin. An interesting thing that we have noticed is that if you combine the amount of hpc-gen2.8core and hpc-gen1.8core flavours that would be the second most popular flavour. We belivie that many will prefer to use standard.xxlarge instead of hpc flavours with similar amount of RAM. The new flavours hpc.4.5core - 5 cores 22GB RAM - replacement for hpc-gen1.1core, hpc-gen1.4core, alternative to hpc-gen2.2core, hpc.4.10core - 10 cores 44GB RAM - replacement for hpc-gen1.8core, alternative to hpc-gen2.8core hpc.4.20core - 20 cores 88GB RAM - replacement for hpc-gen1.16core, alternative to hpc-gen2.16core and hpc-gen2.24core standard.xxlarge - 8 oversubscribed cores, 32GB RAM - alternative to hpc-gen2.8core, hpc-gen1.8core, hpc4.5core and hpc.4.10core Why are the hpc-gen1 flavours disappearing? Existing instances of these flavour will continue to ## Object Storage Use Cases Part 2: Storing your reveal.js presentation in Object Storage DevFeed: [Object Storage Use Cases Part 2: Storing your reveal.js presentation in Object Storage]() Original publisher: [Read original article]() Author: Unknown (noreply@blogger.com) Published: 2018-05-09T11:00:00Z Content type: tutorial Language: en Sources: [CSC - IT Center For Science - Cloud Team]() Topics: [Command-line interface](), [ceph](), [Cloud](), [Amazon Web Services]() Tags: [aws](), [ceph](), [cli](), [demo](), [installation](), [object-storage](), [openstack](), [presentation](), [python](), [radosgw](), [s3](), [storage]() ### AI overview A technical tutorial in the CSC Pouta Cloud Team series explains how to upload a reveal.js presentation to Pouta Object Storage using the awscli tool with Ceph RadosGW's S3-like implementation. It covers URL requirements, credentials, virtual-environment setup, installation, and configuration. ### Source excerpt This is part of a technical series of blog post where the CSC Pouta Cloud Team illustrates with words and sometimes figures how to do things with our object storage. The pevious installation in this series was the magnificent NFS + ZFS + Encryption blog post Topic for this post: we will experiment with Pouta Object Storage, the aws tool and reveal.js to upload a presentation at a nice https://mypresentation20180423.object.pouta.csc.fi/index.html URL. At the time of writing we have not enabled any automatic redirection to index.html with HAProxy if there is no filename specified, so "index.html" is needed or you will see the S3 XML details about the bucket (or AccessDenied). Also https:// at the beginning is needed as we do not yet redirect from TCP 80 to TCP 443. This blog post has two tracks, either you continue with the content on this blog post or you read the content in a reveal.js format on https://mypresentation20180423.object.pouta.csc.fi/index.html Step 1: Configure aws-cli We need something to write files to object storage. We will try the "industry standard" awscli tool to illustrate that it does work even though we are using Ceph's RadosGW which has an s3-like implementation. There are many clients one can use with S3. awscli comes with an s3 client inside which is working with our version for Ceph RadosGW. For some clients we have rudimentary documentation how to use them. You will need OpenStack ec2 credentials to use S3. You get those with this command: $ openstack ec2 credentials create Setting up a python virtual environment and install awscli inside it (so we don't mess with system libraries): $ virtualenv venv_aws $ source venv_aws/bin/activate $ pip install -U setuptools # this was needed on my CentOS7 laptop $ pip install awscli # don't confuse this with "aws" in pip Configuring it: $ aws configure AWS Access Key ID [None]: Enteryouraccesskeyidhere AWS Secret Access Key [None]: Enteryoursecretaccesskeyhere Default region name [None]: # press ENTE ## Object Storage Use Cases Part 1: NFS Server Backups to cPouta S3 DevFeed: [Object Storage Use Cases Part 1: NFS Server Backups to cPouta S3]() Original publisher: [Read original article]() Author: Jukka Nousiainen (noreply@blogger.com) Published: 2018-04-24T11:20:00Z Content type: tutorial Language: en Sources: [CSC - IT Center For Science - Cloud Team]() Topics: [Amazon S3](), [Server](), [Ansible](), [configuration-management](), [ceph](), [Availability](), [Ubuntu](), [API](), [cloud-infrastructure]() Tags: [ansible](), [backups](), [ceph](), [object-storage](), [storage](), [ubuntu]() ### AI overview This tutorial presents a backup design for NFS shares hosted on a cPouta virtual machine, with backups scheduled to cPouta object storage. It discusses encrypting data before it reaches shared storage, using ZFS, Ansible, S3, and Ubuntu 16.04, and considers failure domains and storage redundancy. ### Source excerpt After releasing object storage in cPouta, we've been asked quite a lot about various use cases. Thus we're starting a blog series to showcase some of them. Premise A popular design pattern for Pouta users is to host a data storage NFS server in the default project network and back it up to a host on their campus or home organization network. In similar fashion, in this blog post we will be enabling NFS shares from a cPouta Virtual Machine and scheduling backups to cPouta object storage. Since the demand to process biomedical and other types of sensitive data in cloud computing platforms is increasing, we also try to cater for these kind of scenarios by choosing a model where data is encrypted before it lands on any kind of shared storage. The reader is expected to be somewhat familiar with the following concepts: NFS which is used for file sharing within project network ZFS which is used as encrypting file storage Ansible which is used for configuration management S3 as the chosen API for uploading objects. The operating system used in the examples is Ubuntu 16.04. Failure domains One of the most important things to take into account when designing any kind of backup scheme are the failure domains of the underlying systems and services. In cPouta, users can store data in several locations, which map to several failure domains: standard persistent volumes on highly redundant Ceph block storage standard VM root disks on highly redundant Ceph block storage Highly redundant Ceph object storage RAID1 root disks of gpu VM flavors RAID0 root disks of hpc-gen1, hpc-gen2 and io flavors RAID0 ephemeral disks of io flavors Furthermore, all of these resources are currently in the single availability zone called nova. In our scheme, active NFS server data will reside on a dedicated persistent volume. Backups will go to object storage. As for redundancy, currently all backing Ceph pools are configured to replicate three copies of each block or object. Targeted data locations are ## Admin Stories: Implement Object Storage in CSC's cPouta DevFeed: [Admin Stories: Implement Object Storage in CSC's cPouta]() Original publisher: [Read original article]() Author: Unknown (noreply@blogger.com) Published: 2018-02-12T12:58:00Z Content type: article Language: en Sources: [CSC - IT Center For Science - Cloud Team]() Topics: [ceph](), [Amazon S3](), [Cloud](), [API]() Tags: [backend](), [ceph](), [cpouta](), [infrastructure](), [object](), [object-storage](), [openstack](), [rados](), [radosgw](), [rgw](), [s3](), [server](), [servers](), [storage](), [volume]() ### AI overview This article explains the decisions behind implementing object storage in CSC's cPouta cloud. It describes using Ceph RADOS Gateway with existing Ceph clusters and clarifies the relationship between S3 buckets, Swift containers, accounts, and OpenStack project IDs. ### Source excerpt In our previous user survey we found out that you were interested in "OpenStack admin stories". This will be our first attempt in doing that. User guide: https://research.csc.fi/pouta-user-guide While implementing object storage we made a few decisions. This blog post is about highlighting the decisions and their backing thought process. Some background information: cPouta uses OpenStack as the underlying cloud middleware, and Ceph for storing volumes and images. And going forward, objects, too. Terminology RADOS Gateway/RadosGW/RGW/Ceph RGW/Ceph radosgw/radosgw. We mean the same thing. It's a piece of software which exposes an API for storing and retrieving objects. Ceph - the storage system which RadosGW daemons access as a client. Buckets in S3 and Containers in Swift are synonymous. The Ceph radosgw-admin tool also operates on buckets. The latter are mostly the same, but can contain a bit more information i.e. OpenStack project ID. If we write about buckets, the reader can presume we are referring to S3 buckets and Swift containers unless otherwise noted. Account is something that RGW binds usage data into. In some of the radosgw-admin CLI calls, accounts are referred to as users or UIDs. These users and/or accounts get a mapping to OpenStack project IDs in our configuration. So be it account/user/project, we are always talking about the same thing. - Why Ceph RadosGW The other option we briefly looked at for an Object Storage server was the OpenStack Swift server. Yes, there is an API called Swift and a piece of sofware called Swift which serves the Swift API. Not to mention the programming language Swift, the ISO standard SWIFT or the Scottish potato variant Swift. In the end we used none of these for backend because we prefer to reuse existing infrastructure. We already have Ceph clusters used for Virtual Machine image and block (volume) storage in our clouds. Installing some Ceph RadosGW servers and pointing those to an existing Ceph cluster utilizes a lot o ## Storage updates, revisited DevFeed: [Storage updates, revisited]() Original publisher: [Read original article]() Author: Jukka Nousiainen (noreply@blogger.com) Published: 2016-12-13T13:19:00Z Content type: news Language: en Sources: [CSC - IT Center For Science - Cloud Team]() Topics: [cloud-infrastructure](), [migration](), [ceph](), [systems]() Tags: [ceph](), [cpouta](), [migration](), [storage](), [systems](), [updates]() ### AI overview The article revisits cPouta storage changes, including the migration of most detached HPC storage volumes to standard Ceph-based volumes. It also announces a December 28-30, 2016 service break, during which affected virtual machines may be forcefully shut down, and explains that Ceph will become cPouta's only storage system. ### Source excerpt Run of the Mill Back in September we blogged about disabling the possibility to create older cPouta volume types. This was the first step on the path to a more streamlined cPouta storage backend. Continuing on this path, we have now migrated most detached HPC storage volumes to standard volumes, and contacted users about their migration options for HPC storage volumes still attached to VMs. Next up, there will be a service break for the whole HPC storage environment, followed by severing the link between cPouta and the HPC storage backend for good. As pictures are often better than a thousand words, we'd like to illustrate these changes for the pleasure of the astute observer. Here's a (very) simplified diagram of cPouta's connectivity to its storage systems: Figure 1. Current topology of cPouta storage backends. The HPC storage system on the left hosts cPouta volumes that are visible to the user as "hpc-storage" or as the dash sign "-". The Ceph-based storage system on the right hosts cPouta volumes that are visible to the user as "standard". Going forward this Ceph-based system will be the only storage system of cPouta. Let it down The next upcoming change potentially affecting cPouta users is the service break for HPC storage systems between December 28th-30th 2016. Components affected by this maintenance are highlighted in Figure 2. Figure 2. Scope of service break on Dec 28th-30th 2016. Maintenance work on the cPouta specific storage controller will occur on December 29th. On this date, any cPouta VMs which still have hpc-storage volumes attached will be forcefully shut down to allow hypervisors to gracefully terminate their iSCSI connections to the HPC storage backend. Apologies about this inconvenience, which is unavoidable with the current firmware/kernel versions. All things must pass Throughout 2016 there has been aggressive growth in the utilization of CSC clouds' volume storage. This has been largely possible thanks to the elasticity of the Ceph-based st