# Rockpro64-2 Published articles for Rockpro64-2. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Cluster build log: Moving to temporary cluster DevFeed: [Cluster build log: Moving to temporary cluster]() Original publisher: [Read original article]() Published: 2021-09-01T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [hosting](), [Network](), [Ethernet]() Tags: [cluster](), [community](), [downtime](), [ethernet](), [hosting](), [network](), [rockpro64-2]() ### AI overview This build log explains why PINE64 is creating a temporary hosting cluster. The existing cluster needs hardware changes that require extended downtime, so a smaller cluster will keep community services running during the work. The article introduces the power and network requirements for the temporary cluster. ### Source excerpt As promised in the last month's community update Housekeeping section, this is the first part of the cluster's build log! This mini-series in which I will cover everything about upcoming changes our hosting cluster, and it begins with building a temporary cluster. Why build a temporary cluster? One of the latest photo of cluster Let's start from beginning. When we built the current hosting cluster a year ago, it was made in quite a hurry (some of the services needed to be migrated to the cluster on a moment's notice). Also, it was the first time I (gamiee) and Matthew (fire219) were tasked with building a cluster. Because of this, some of the cluster's features are missing and various things don't work quite as well as we have hoped. For example, the cluster has power management boards (PCB on right side of every row), which are used primary for power distribution to the SBCs, but also it also has a I2C GPIO Expander for rebooting and turning off the SBCs. The I2C Expansion isn't in use yet, because the primary node wasn't able to detect it, so this is something that needs to be checked out when the cluster is turned off. And this is exactly the main reason why we are building a temporary cluster. We need to do some changes which require us to have the whole cluster turned off and on a workbench (not in housing room where isn't much space), and this means that it will be inaccessible for several days. Obviously a long downtime wouldn't be good when 100% of PINE64 community services are running on it. So we are going to build a temporary small cluster, which will have the minimal number of required nodes to have all services running, so we can make all upgrades with precision and at our own pace. What do we need to make a custom cluster? There are two things each node needs: a power supply and access to the network. Access to the network can be solved by using a classic Ethernet switch, but powering multiple RockPros, which are actually pretty power hungry, is a bit ## April Update: CE & FCC, Software Update and DIY Router? DevFeed: [April Update: CE & FCC, Software Update and DIY Router?]() Original publisher: [Read original article]() Published: 2020-04-15T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [Linux](), [Pinephone](), [IRC](), [Matrix](), [Ubuntu](), [notifications](), [USB]() Tags: [android](), [community-update](), [development](), [devices](), [fcc](), [irc](), [linux](), [matrix](), [pinebook-pro](), [pinephone](), [pinetab](), [pinetime](), [rockpro64-2](), [ubuntu](), [update](), [usb]() ### AI overview PINE64's April community update covers device shipping plans, PinePhone certifications and software progress, Pinebook Pro development, hardware projects, community infrastructure, and a possible ROCKPro64-based router. ### Source excerpt I hope and trust this update finds everyone well. Production in China is picking up pace and we expect to start shipping the Pinebook Pro with Manjaro and PinePhone UBports Community edition next month. I am happy to report that, for the time being, everything is proceeding smoothly and we're on track to ship devices in accordance with our original plans. Still, I encourage you to sign up to this blog to stay up-to-date on shipping information since anything can happen in the next 30 days. Here is the TL:DR for this month's community update: ROCKPro64 cluster is up and running; IRC and Matrix will be moved over to it soon We're shipping surgical masks to those in need in your local community PinePhone UBports edition gets CE, FCC and RED certifications UBports Ubuntu Touch shaping up nicely; major development milestones reached Other PinePhone OSes begin maturing; state of development + new phone OS CRUST suspend on the PinePhone; 15 hours battery now possible Schematics for PCBA v1.2 available after testing; v1.2 will be available in the store for BH users eventually Pinebook Pro Manjaro KDE build is very polished; development report Docking your Pinebook Pro using USB-C; using Manjaro mainline kernel We're making our own USB-C dock; better ergonomics than most OEM options RK3399 OG Pinebook upgrade kit testing and challenges; we'll likely use graphene for cooling PineTab delayed until pandemic over; ready for fabrication and report of improvements + tablet keyboard is ready The PineTime is now a smartwatch; BLE notifications support; we need a Linux + Android companion app OpenWRT on ROCKPro64; what do you think about a ROCKPro64-based router? Housekeeping The PINE64 ROCKPro64 cluster has finally made it to its location at BBXNET and the process of setting it up began. For those who don't know, in November last year we announced that we'll be moving our services over to a custom 24-node ROCKPro64 cluster. At the time of writing the cluster is already up and runnin