diff --git a/bare-metal/dedibox/concepts.mdx b/bare-metal/dedibox/concepts.mdx index 8152a459f7..be498c8683 100644 --- a/bare-metal/dedibox/concepts.mdx +++ b/bare-metal/dedibox/concepts.mdx @@ -38,11 +38,11 @@ A backup is a copy of your data, stored in another location. In case of any hard ## Dedibackup -Dedibackup is a backup solution for your Dedibox server. Dedibackup is based on Scaleway's Object Storage solution and provides FTP access to a secure backup space located in the DC5 datacenter. This allows you to store copies of your data for security purposes. +Dedibackup is a backup solution for your Dedibox server. Dedibackup is based on Scaleway's Object Storage solution and provides FTP access to a secure backup space located in the DC5 data center. This allows you to store copies of your data for security purposes. ## Dedicated server -A dedicated server is a physical computer hosted in a datacenter and connected to the internet. Each dedicated server is rented to one single customer who has full access to the machine to install any software of their choice on it. +A dedicated server is a physical computer hosted in a data center and connected to the internet. Each dedicated server is rented to one single customer who has full access to the machine to install any software of their choice on it. ## Hostname diff --git a/bare-metal/dedibox/how-to/order-dedibox.mdx b/bare-metal/dedibox/how-to/order-dedibox.mdx index c3b3c2b0f9..213dc3ee41 100644 --- a/bare-metal/dedibox/how-to/order-dedibox.mdx +++ b/bare-metal/dedibox/how-to/order-dedibox.mdx @@ -22,7 +22,7 @@ dates: 1. Click **Dedibox** in the **Bare Metal** section of the side menu. The Dedibox overview page displays. 2. Click **+ Order a Dedibox server** to launch the creation wizard. -3. Choose a **Datacenter**, in which your Dedibox server will be deployed. Then select the server offer to deploy and click **Server options >**. +3. Choose a **Data center**, in which your Dedibox server will be deployed. Then select the server offer to deploy and click **Server options >**. You can group the offer list by clicking on the tab corresponding to each offer group. diff --git a/bare-metal/dedibox/quickstart.mdx b/bare-metal/dedibox/quickstart.mdx index 31adc9d770..cd36a3bf4b 100644 --- a/bare-metal/dedibox/quickstart.mdx +++ b/bare-metal/dedibox/quickstart.mdx @@ -24,7 +24,7 @@ dates: 1. Click **Dedibox** in the **Bare Metal** section of the side menu. The Dedibox overview page displays. 2. Click **+ Order a Dedibox server** to launch the creation wizard. -3. Choose a **Datacenter**, in which your Dedibox server will be deployed. Then select the server offer to deploy and click **Server options >**. +3. Choose a **Data center**, in which your Dedibox server will be deployed. Then select the server offer to deploy and click **Server options >**. You can group the offer list by clicking on the tab corresponding to each offer group. @@ -101,7 +101,7 @@ To connect to your server from Windows, you will need to use a small application To connect to your Instance from Windows, you will need to use a small application called **PuTTY**, an SSH client. -1. Download and install PuTTY [here](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) +1. [Download and install PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html). 2. Launch PuTTY on your computer. The main screen of the application displays. 3. Enter your Instance's IP address in the **Hostname** field. diff --git a/bare-metal/dedibox/reference-content/dedibox-datasheet.mdx b/bare-metal/dedibox/reference-content/dedibox-datasheet.mdx index 6a3dfae374..c5879d0a13 100644 --- a/bare-metal/dedibox/reference-content/dedibox-datasheet.mdx +++ b/bare-metal/dedibox/reference-content/dedibox-datasheet.mdx @@ -17,22 +17,22 @@ This datasheet provides a concise overview of the performance, technical feature ## Server Dedibox PRO-9-M -| Dedibox PRO-9-M | | -|-----------------------|-----------------------------------| -| **CPU** | AMD EPYC™ 7272 (12c/24t, 2.9 Ghz) | -| **RAM** | 128 GB DDR4 ECC | -| **Disk** | 2 x 1 TB NVMe | -| **Public bandwidth** | 1 Gbps | +| Dedibox PRO-9-M | | +|------------------------|-----------------------------------| +| **CPU** | AMD EPYC™ 7272 (12c/24t, 2.9 Ghz) | +| **RAM** | 128 GB DDR4 ECC | +| **Disk** | 2 x 1 TB NVMe | +| **Public bandwidth** | 1 Gbps | | **[RPN](/dedibox-network/rpn/concepts/#rpn) private bandwidth** | 1 Gbps (10 Gbps optional) | -| **Datacenter** | DC2, DC5 | +| **Data center** | DC2, DC5 | ## Server Dedibox PRO-9-L -| Dedibox PRO-9-L | | -|-----------------------|-----------------------------------| -| **CPU** | AMD EPYC™ 7272 (12c/24t, 2.9 Ghz) | -| **RAM** | 256 GB DDR4 ECC | -| **Disk** | 2 x 2 TB NVMe | -| **Public bandwidth** | 1 Gbps | +| Dedibox PRO-9-L | | +|------------------------|-----------------------------------| +| **CPU** | AMD EPYC™ 7272 (12c/24t, 2.9 Ghz) | +| **RAM** | 256 GB DDR4 ECC | +| **Disk** | 2 x 2 TB NVMe | +| **Public bandwidth** | 1 Gbps | | **[RPN](/dedibox-network/rpn/concepts/#rpn) private bandwidth** | 1 Gbps (10 Gbps optional) | -| **Datacenter** | DC2, DC5 | \ No newline at end of file +| **Data center** | DC2, DC5 | \ No newline at end of file diff --git a/bare-metal/elastic-metal/how-to/configure-flexible-ip.mdx b/bare-metal/elastic-metal/how-to/configure-flexible-ip.mdx index bb5648ef0f..3807709a90 100644 --- a/bare-metal/elastic-metal/how-to/configure-flexible-ip.mdx +++ b/bare-metal/elastic-metal/how-to/configure-flexible-ip.mdx @@ -24,7 +24,7 @@ Learn how to configure a [flexible IP address](/bare-metal/elastic-metal/concept - A [flexible IP address](/bare-metal/elastic-metal/how-to/attach-detach-flexible-ip/) attached to your Elastic Metal server - You can find information about the DNS resolver to use in each datacenter at the [network reference documentation](/console/account/reference-content/scaleway-network-information/#dns-cache-servers). + You can find information about the DNS resolver to use in each data center at the [network reference documentation](/console/account/reference-content/scaleway-network-information/#dns-cache-servers). ## How to configure a flexible IP on Ubuntu Linux @@ -137,6 +137,4 @@ Configure the networking of your VM's as follows: * The gateway of all flexible IPs is `62.210.0.1`. This allows you to move your VMs between your hypervisors without changing the network configuration of the virtual machine. * When configuring a failover IP in a virtual machine, you must specify which route will be used by the VM. Refer to our [dedicated documentation](/dedibox-network/network/how-to/configure-network-netplan/#configuring-failover-ip-for-virtual-machines) for further information. - - - + \ No newline at end of file diff --git a/bare-metal/elastic-metal/troubleshooting/enable-ssh-virtualization-distribution.mdx b/bare-metal/elastic-metal/troubleshooting/enable-ssh-virtualization-distribution.mdx index 19fa079ad0..08f59ae3d0 100644 --- a/bare-metal/elastic-metal/troubleshooting/enable-ssh-virtualization-distribution.mdx +++ b/bare-metal/elastic-metal/troubleshooting/enable-ssh-virtualization-distribution.mdx @@ -35,7 +35,7 @@ If you require SSH access to your Elastic Metal server, you can enable SSH on yo You can find the URL of the Proxmox VE interface on the overview page of your Elastic Metal server in the Scaleway console. -2. Select your server in the Datacenter view of Proxmox. +2. Select your server in the Data center view of Proxmox. 3. Click **Shell** in the server view to open a shell in the web interface. 4. Open the file `/etc/ssh/sshd_config` in a text editor. 5. Go to the line `#PermitRootLogin` and uncomment it by removing the `#`. Change the option to yes: @@ -91,5 +91,4 @@ VMware ESXi is a bare metal hypervisor that allows you to install multiple virtu 4. Disable SSH from the host dashboard. Click **Actions** > **Services** > **Disable Secure Shell (SSH)**. SSH is disabled. It is recommended to disable SSH access when not in use, to avoid potential security vulnerabilities related to the access. - - \ No newline at end of file + \ No newline at end of file diff --git a/console/account/reference-content/scaleway-network-information.mdx b/console/account/reference-content/scaleway-network-information.mdx index c3257afee9..3c79ca6647 100644 --- a/console/account/reference-content/scaleway-network-information.mdx +++ b/console/account/reference-content/scaleway-network-information.mdx @@ -14,7 +14,7 @@ categories: --- This page serves as a resourceful hub for information related to the Scaleway network infrastructure. -It provides a detailed overview of the IP ranges used by Scaleway, details about the DNS resolver IPs in each datacenter, and further information regarding various other network-associated services. +It provides a detailed overview of the IP ranges used by Scaleway, details about the DNS resolver IPs in each data center, and further information regarding various other network-associated services. ## IP ranges used by Scaleway @@ -38,7 +38,7 @@ Currently, we use the following IP ranges: ## DNS cache servers -DNS cache servers are available in every datacenter. The IPs for each DC are: +DNS cache servers are available in every data center. The IPs for each DC are: ### AMS1 IPv4: @@ -108,4 +108,4 @@ IP: `62.210.16.24` (`vpn-rpn-dc3.online.net`) ### Monitoring of Dedibox servers -Our monitoring servers are located in the IP subnet `62.210.16.0/24`. +Our monitoring servers are located in the IP subnet `62.210.16.0/24`. \ No newline at end of file diff --git a/containers/kubernetes/how-to/edit-kosmos-cluster.mdx b/containers/kubernetes/how-to/edit-kosmos-cluster.mdx index 80d3553236..66cf7a2a79 100644 --- a/containers/kubernetes/how-to/edit-kosmos-cluster.mdx +++ b/containers/kubernetes/how-to/edit-kosmos-cluster.mdx @@ -113,6 +113,4 @@ The Kubernetes version of the existing nodes in your multi-cloud pool can be upg 1. In the Pools section of your Kosmos cluster, click **Upgrade** next to the node pool. This will not cause any of your existing nodes to upgrade, but will instead ensure that any new nodes added to the pool will start up with the newer version. 2. Run the installer program as you would do for a fresh node install, with the additional option `-self-update`. If the option is not available, redownload the program from the Object Storage bucket. 3. Now the node will register itself with the Apiserver. Once it is ready, you will see the same node with two kubelet versions. The older node should end up `NotReady` after 5m, you can safely delete it with `kubectl`. -4. Detach the older node in Scaleway API. - - +4. Detach the older node in Scaleway API. \ No newline at end of file diff --git a/dedibox-network/domains/quickstart.mdx b/dedibox-network/domains/quickstart.mdx index 66e4c0a595..0245783db1 100644 --- a/dedibox-network/domains/quickstart.mdx +++ b/dedibox-network/domains/quickstart.mdx @@ -99,7 +99,7 @@ WAPS, or **W**hois **A**ccuracy **P**rogram **S**pecification, is a system intro If you are expecting a validation email (e.g. if you have modified your domain owner's contact information) but cannot find the email, try the following steps: - - Check your SPAM folder + - Check your spam folder - Check and update, if necessary, the email address of your domain name contact from the [console](https://console.online.net/). - [Open a ticket](https://console.online.net/en/assistance/ticket) or contact the support team directly. They will be able to check to which address the validation email has been sent and whether it has been validated. \ No newline at end of file diff --git a/dedibox-network/ip-failover/concepts.mdx b/dedibox-network/ip-failover/concepts.mdx index d3ffbde74f..053bbf1a68 100644 --- a/dedibox-network/ip-failover/concepts.mdx +++ b/dedibox-network/ip-failover/concepts.mdx @@ -18,7 +18,7 @@ A bridged network is a mode of networking for virtual machines, another being [N ## Failover IPs -Failover IPs are IP addresses that you can order and move from one server to another (even across datacenters), without changing your whole configuration. If your server is out of order, you can move the failover IP to your fallback server, and have your services remain available without any downtime. Failover IPs can also be used as additional IP addresses for a single server, for example, if you want to give each website in Plesk its own IP. Another functionality of Failover IPs is to create virtual machines on your Dedibox. +Failover IPs are IP addresses that you can order and move from one server to another (even across data centers), without changing your whole configuration. If your server is out of order, you can move the failover IP to your fallback server, and have your services remain available without any downtime. Failover IPs can also be used as additional IP addresses for a single server, for example, if you want to give each website in Plesk its own IP. Another functionality of Failover IPs is to create virtual machines on your Dedibox. ## IP configuration diff --git a/dedibox-network/ip-failover/how-to/configure-network-virtual-machine.mdx b/dedibox-network/ip-failover/how-to/configure-network-virtual-machine.mdx index 82237d90b1..550b08c1a5 100644 --- a/dedibox-network/ip-failover/how-to/configure-network-virtual-machine.mdx +++ b/dedibox-network/ip-failover/how-to/configure-network-virtual-machine.mdx @@ -1,10 +1,10 @@ --- meta: title: How to configure the network of a virtual machine on a Dedibox host - description: Learn how to configure network settings for virtual machines on various operating systems, including Ubuntu, Debian, CentOS, and Windows Server. + description: Learn how to configure network settings for virtual machines on various operating systems, including Ubuntu, Debian, CentOS, and Windows Server. content: h1: How to configure the network of a virtual machine on a Dedibox host - paragraph: Learn how to configure network settings for virtual machines on various operating systems, including Ubuntu, Debian, CentOS, and Windows Server. + paragraph: Learn how to configure network settings for virtual machines on various operating systems, including Ubuntu, Debian, CentOS, and Windows Server. tags: dedibox network virtual-machine virtual machine ubuntu debian centOS windows-server dates: validation: 2024-07-22 @@ -89,7 +89,7 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for nameserver 51.159.47.26 ``` - Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each datacenter](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) + Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) 6. Activate the network on your virtual machine by running: ``` @@ -141,5 +141,5 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for * DNS 2: `51.159.47.26` - Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each datacenter](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) - + Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) + \ No newline at end of file diff --git a/dedibox-network/ip-failover/index.mdx b/dedibox-network/ip-failover/index.mdx index a3c83a3447..007a5d1e41 100644 --- a/dedibox-network/ip-failover/index.mdx +++ b/dedibox-network/ip-failover/index.mdx @@ -7,7 +7,7 @@ meta: diff --git a/dedibox-network/ip-failover/quickstart.mdx b/dedibox-network/ip-failover/quickstart.mdx index b074f62fc6..acac39591e 100644 --- a/dedibox-network/ip-failover/quickstart.mdx +++ b/dedibox-network/ip-failover/quickstart.mdx @@ -10,7 +10,7 @@ categories: - dedibox-network --- -Failover IPs are IP addresses you can order and move from one server to another (even across datacenters), without changing your whole configuration. If your server is out of order, you can move the failover IP to your fallback server, and keep your services available without any downtime. Failover IPs can also be used as additional IP addresses for a single server, for example, if you want to give each website in Plesk its IP. Another functionality of Failover IPs is to create virtual machines on your Dedibox. +Failover IPs are IP addresses you can order and move from one server to another (even across data centers), without changing your whole configuration. If your server is out of order, you can move the failover IP to your fallback server, and keep your services available without any downtime. Failover IPs can also be used as additional IP addresses for a single server, for example, if you want to give each website in Plesk its IP. Another functionality of Failover IPs is to create virtual machines on your Dedibox. diff --git a/dedibox-network/network/how-to/configure-network-netplan.mdx b/dedibox-network/network/how-to/configure-network-netplan.mdx index 29ca105f74..0990ef2299 100644 --- a/dedibox-network/network/how-to/configure-network-netplan.mdx +++ b/dedibox-network/network/how-to/configure-network-netplan.mdx @@ -73,7 +73,7 @@ network: ``` - Replace the DNS cache servers in the example above (`51.159.47.28` and `51.159.47.26`) with the nameservers [available in the same datacenter](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) as your server for optimal latency. + Replace the DNS cache servers in the example above (`51.159.47.28` and `51.159.47.26`) with the nameservers [available in the same data center](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) as your server for optimal latency. Once you have edited and saved the file, you can reload the configuration with the following command: @@ -104,7 +104,5 @@ When configuring a failover IP in a virtual machine, you must specify which rout ``` - Replace the DNS cache servers in the example above (`51.159.47.28` and `51.159.47.26`) with the nameservers [available in the same datacenter](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) as your server for optimal latency. - - - + Replace the DNS cache servers in the example above (`51.159.47.28` and `51.159.47.26`) with the nameservers [available in the same data center](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) as your server for optimal latency. + \ No newline at end of file diff --git a/dedibox-network/rpn/concepts.mdx b/dedibox-network/rpn/concepts.mdx index cc9825f9d2..ffb0b56b54 100644 --- a/dedibox-network/rpn/concepts.mdx +++ b/dedibox-network/rpn/concepts.mdx @@ -25,7 +25,7 @@ This way, we keep your tags inside our tag, and use numerous possible VLANs on y ## RPN -Real Private Network (RPN) is a second physical network that uses a dedicated Ethernet adapter to enable network coverage over all of Scaleway datacenters. You can create "RPN Groups" with different servers that are able to communicate with each other. Servers of different accounts can be in the same RPN group, and each server can be in multiple groups. The RPN allows you to exchange internal data in a dedicated and secure network and without using the bandwidth of your internet connection. "Jumboframes" with an MTU of 9000 are supported in the RPN. +Real Private Network (RPN) is a second physical network that uses a dedicated Ethernet adapter to enable network coverage over all of Scaleway data centers. You can create "RPN Groups" with different servers that are able to communicate with each other. Servers of different accounts can be in the same RPN group, and each server can be in multiple groups. The RPN allows you to exchange internal data in a dedicated and secure network and without using the bandwidth of your internet connection. "Jumboframes" with an MTU of 9000 are supported in the RPN. ## RPN SAN diff --git a/dedibox-network/rpn/how-to/use-rpn-san-proxmox.mdx b/dedibox-network/rpn/how-to/use-rpn-san-proxmox.mdx index 4d35e930ae..d6da19d498 100644 --- a/dedibox-network/rpn/how-to/use-rpn-san-proxmox.mdx +++ b/dedibox-network/rpn/how-to/use-rpn-san-proxmox.mdx @@ -79,7 +79,7 @@ Proxmox requires the Open-iSCSI software to support mounting of iSCSI volumes. I ## Discover and connect to targets in Proxmox -1. In the **Server View**, click **Datacenter**, then **Storage**. +1. In the **Server View**, click **Data center**, then **Storage**. 2. Click **Add** and then **iSCSI Target**. Fill in the form: * **ID**: any identifier used to name this RPN SAN volume. * **Portal**: the server on which your space is available (ex: san-1.rpn.online.net). @@ -98,4 +98,4 @@ Proxmox requires the Open-iSCSI software to support mounting of iSCSI volumes. I * **Nodes**: the nodes that will be able to access this space. * **Enable**: check the box. -Your RPN SAN is available for use. +Your RPN SAN is available for use. \ No newline at end of file diff --git a/dedibox/dedicated-servers/concepts.mdx b/dedibox/dedicated-servers/concepts.mdx index 521c2d632a..df517efd77 100644 --- a/dedibox/dedicated-servers/concepts.mdx +++ b/dedibox/dedicated-servers/concepts.mdx @@ -34,11 +34,11 @@ A backup is a copy of your data, stored in another location. In case of any hard ## Dedibackup -A backup solution for your Dedibox. Dedibackup is based on Scaleway's Object Storage solution and provides FTP access to a secure backup space located in the DC5 datacenter. This allows you to store copies of your data for security purposes. +A backup solution for your Dedibox. Dedibackup is based on Scaleway's Object Storage solution and provides FTP access to a secure backup space located in the DC5 data center. This allows you to store copies of your data for security purposes. ## Dedicated server -A dedicated server is a physical computer hosted in a datacenter and connected to the internet. Each dedicated server is rented to one single customer who has full access to the machine to install any software of their choice on it. +A dedicated server is a physical computer hosted in a data center and connected to the internet. Each dedicated server is rented to one single customer who has full access to the machine to install any software of their choice on it. ## Hostname diff --git a/dedibox/dedicated-servers/how-to/order-a-server.mdx b/dedibox/dedicated-servers/how-to/order-a-server.mdx index 1efcf1db32..2640e977c5 100644 --- a/dedibox/dedicated-servers/how-to/order-a-server.mdx +++ b/dedibox/dedicated-servers/how-to/order-a-server.mdx @@ -23,7 +23,7 @@ categories: 1. Click **Order** on your Dedibox console homepage. 2. Click **Server**. The server offers page displays. - You can view all servers available in your preferred datacenter by clicking the **Datacenter selection** drop-down menu in the top right corner. + You can view all servers available in your preferred data center by clicking the **Data center selection** drop-down menu in the top right corner. 3. Select a server model and click the **Order** button next to your choice. The server creation wizard displays. 4. Complete the following steps in the wizard: @@ -31,9 +31,9 @@ categories: This step only displays for Dedibox servers eligible for a commitment plan. - - Select the datacenter. + - Select the data center. - Some server models are available in more than one datacenter. If you have no preference, select **"No preference"**. + Some server models are available in more than one data center. If you have no preference, select **"No preference"**. - Choose the service level. There are two plans available: - **Basic service level**: Included with any Dedibox server. Offers: @@ -58,4 +58,4 @@ categories: 5. Click **Order**. A summary of your order displays. 6. Select your payment method in the **Payment mode choice** drop-down menu in the top right corner. 7. Check the boxes confirming that you have read and agreed to the terms of service. -8. Click **Confirm my order**. A confirmation of your order displays. +8. Click **Confirm my order**. A confirmation of your order displays. \ No newline at end of file diff --git a/dedibox/dedicated-servers/quickstart.mdx b/dedibox/dedicated-servers/quickstart.mdx index 66c4a1b341..956431cbc0 100644 --- a/dedibox/dedicated-servers/quickstart.mdx +++ b/dedibox/dedicated-servers/quickstart.mdx @@ -25,7 +25,7 @@ categories: 1. Click **Order** on your Dedibox console homepage. 2. Click **Server**. The server offers page displays. - You can view all servers available in your preferred datacenter by clicking the **Datacenter selection** drop-down menu in the top right corner. + You can view all servers available in your preferred data center by clicking the **Data center selection** drop-down menu in the top right corner. 3. Select a server model and click the **Order** button next to your choice. The server creation wizard displays. 4. Complete the following steps in the wizard: @@ -33,9 +33,9 @@ categories: This step only displays for Dedibox servers eligible for a commitment plan. - - Select the datacenter. + - Select the data center. - Some server models are available in more than one datacenter. If you have no preference, select **"No preference"**. + Some server models are available in more than one data center. If you have no preference, select **"No preference"**. - Choose the service level. There are two plans available: - **Basic service level**: Included with any Dedibox server. Offers: diff --git a/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator-estimation.mdx b/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator-estimation.mdx index e7af2c65ef..bcad52ab27 100644 --- a/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator-estimation.mdx +++ b/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator-estimation.mdx @@ -29,7 +29,7 @@ When you select your Elastic Metal server's Availability Zone, you can see the q -This data is determined by the [Power Usage Effectiveness (PUE)](/environmental-footprint/environmental-footprint/concepts/#pue-power-usage-effectiveness) of the datacenter and the [energy mix](/environmental-footprint/environmental-footprint/concepts/#energy-mix) of the country in which the datacenter is located. +This data is determined by the [Power Usage Effectiveness (PUE)](/environmental-footprint/environmental-footprint/concepts/#pue-power-usage-effectiveness) of the data center and the [energy mix](/environmental-footprint/environmental-footprint/concepts/#energy-mix) of the country in which the data center is located. We use [Ember's](https://ember-climate.org/) Electricity Data Explorer to determine the impact linked to the energy mix. The energy mix can be very different from one country to another depending on the origin of the electricity used. We can see on [Electricity Maps' Environmental Impact by Zone map](https://app.electricitymaps.com/map) the significant differences that there can be between countries. @@ -63,7 +63,7 @@ For usage, we rely on an estimate of electricity consumption. This estimation is These different computing configurations allow us to simulate enough use cases to have an idea of the power consumption, but the actual consumption will depend on how the server is used in practice. -We estimate the measure the server's electricity consumption and then calculate its estimated impact based on the energy mix of the selected zone and the datacenter's PUE. +We estimate the measure the server's electricity consumption and then calculate its estimated impact based on the energy mix of the selected zone and the data center's PUE. The estimation is represented by three green leaf icons: @@ -79,6 +79,4 @@ The estimation is represented by three green leaf icons: A summary of the total environmental footprint estimation for the selected offer is shown before the order summary. We also add an indication to help you imagine what this impact is, such as `≈ 35 km by car`. - - - + \ No newline at end of file diff --git a/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator.mdx b/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator.mdx index 3c58c60f95..7389f4caca 100644 --- a/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator.mdx +++ b/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator.mdx @@ -19,45 +19,45 @@ The environmental footprint estimation tool is currently in private beta. Sign u This page details the methodology used to calculate the environmental footprint of Scaleway cloud services, and Bare Metal offers. This methodology ensures transparency and precision, as it provides reliable estimations covering a full lifecycle analysis. -## Methodology Overview +## Methodology overview Our calculation methodology was developed in collaboration with the green IT specialist consultancy firm [IJO](https://ijo.tech/index.html), ensuring a rigorous and expert-validated approach to assessing environmental impact accurately and transparently. -Our Methodology is based on the [ADEME (French Government Agency for Ecological Transition) Product Category Rules (PCR) for Datacenter and Cloud services](https://librairie.ademe.fr/produire-autrement/6105-methodological-standard-for-the-environmental-assessment-of-datacenter-it-hosting-services-and-cloud-services.html), which provide a standardized framework for calculating and reporting the environmental impact of datacenters and cloud services. These rules are designed to ensure consistency, transparency, and comparability in the assessment of environmental footprints across the industry. +Our Methodology is based on the [ADEME (French Government Agency for Ecological Transition) Product Category Rules (PCR) for Data center and Cloud services](https://librairie.ademe.fr/produire-autrement/6105-methodological-standard-for-the-environmental-assessment-of-datacenter-it-hosting-services-and-cloud-services.html), which provide a standardized framework for calculating and reporting the environmental impact of data centers and cloud services. These rules are designed to ensure consistency, transparency, and comparability in the assessment of environmental footprints across the industry. -The ADEME PCR specifies the methodology for conducting [Life Cycle Analysis (LCA)](/environmental-footprint/environmental-footprint/concepts/#life-cycle-analysis-lca) for datacenter operations, which includes the evaluation of energy consumption, greenhouse gas emissions, resource usage, and other environmental impacts associated with the lifecycle of datacenter infrastructures and cloud services. This lifecycle covers all stages from raw material extraction, manufacturing, and transportation, to the use and end-of-life disposal of datacenter equipment. +The ADEME PCR specifies the methodology for conducting [Life Cycle Analysis (LCA)](/environmental-footprint/environmental-footprint/concepts/#life-cycle-analysis-lca) for data center operations, which includes the evaluation of energy consumption, greenhouse gas emissions, resource usage, and other environmental impacts associated with the lifecycle of data center infrastructures and cloud services. This lifecycle covers all stages from raw material extraction, manufacturing, and transportation, to the use and end-of-life disposal of data center equipment. The stages of the lifecycle that are really significant in the total impact of a server are its manufacturing and its use. We will therefore focus on these two stages in the rest of this documentation. -By adhering to PCR guidelines, we provide reliable and standardized environmental impact data. This facilitates better decision-making for both providers and consumers of datacenter and cloud services, as it allows for clear comparisons and informed choices regarding sustainability. +By adhering to PCR guidelines, we provide reliable and standardized environmental impact data. This facilitates better decision-making for both providers and consumers of data center and cloud services, as it allows for clear comparisons and informed choices regarding sustainability. In addition, to provide an even more comprehensive and realistic assessment, we have extended this methodology to include several additional elements integral to our operations' overall environmental impact. These additional elements cover: -- **Cross-functional IT equipment** - Servers and storage devices dedicated to the enterprise as a whole, managing offers, or equipment held in stock. This includes:  +- **Cross-functional IT equipment** - Servers and storage devices dedicated to the enterprise as a whole, managing offers, or equipment held in stock. This includes: - **Enterprise servers and storage devices** - IT equipment dedicated to Scaleway's internal digital services - **Servers and storage devices for managing offers** - IT equipment for management and supervision of Scaleway offers - **Servers and storage equipment in stock** - IT equipment in stock and waiting to be commissioned - **Non-IT cross-functional elements** - all components necessary for the smooth operation of our company, such as office facilities, employee transportation, and other logistics. Refer to our [2024 Environmental Impact Report](https://www.scaleway.com/en/environmental-leadership/?utm_source=linkedin&utm_medium=social&utm_term=&utm_content=&utm_campaign=default) for more information about these components. -By integrating these additional factors into the PCR Datacenter and cloud methodology, we ensure that our calculations reflect a more complete and transparent view of our environmental impact. +By integrating these additional factors into the PCR Data center and cloud methodology, we ensure that our calculations reflect a more complete and transparent view of our environmental impact. -## Detailed Calculation Breakdown +## Detailed calculation breakdown -The final calculation of the environmental impact considers several critical factors to provide a thorough and accurate assessment. This includes considering the manufacturing processes for datacenters and related technical components, network machines, and servers directly used by customers. Additionally, the assessment accounts for servers dedicated to IT tools and those maintained in stock. +The final calculation of the environmental impact considers several critical factors to provide a thorough and accurate assessment. This includes considering the manufacturing processes for data centers and related technical components, network machines, and servers directly used by customers. Additionally, the assessment accounts for servers dedicated to IT tools and those maintained in stock. -The usage phase also includes every datacenter [Power Usage Effectiveness (PUE)](/environmental-footprint/environmental-footprint/concepts/#pue-power-usage-effectiveness), which is multiplied by the impact related to electricity consumption of network servers, customer-used servers, and servers used for transversal IT tools. This approach ensures that both the direct and indirect energy consumption associated with datacenter operations is accurately represented. +The usage phase also includes every data center [Power Usage Effectiveness (PUE)](/environmental-footprint/environmental-footprint/concepts/#pue-power-usage-effectiveness), which is multiplied by the impact related to electricity consumption of network servers, customer-used servers, and servers used for transversal IT tools. This approach ensures that both the direct and indirect energy consumption associated with data center operations is accurately represented. Our calculations of the impact of electricity consumption are based on a 'location-based' approach, although we have PPA (Power Purchase Agreements) type contracts for each of our data centers, we have chosen not to take them into account in accordance with ADEME guidelines. -Furthermore, the calculation will integrate the environmental impact of all elements necessary for the proper functioning of the enterprise. This includes the office premises, employee transportation, and other logistical aspects.  +Furthermore, the calculation will integrate the environmental impact of all elements necessary for the proper functioning of the enterprise. This includes the office premises, employee transportation, and other logistical aspects. -The details of the calculations for each of these elements are detailed below.  +The details of the calculations for each of these elements are detailed below. ### Definition of the variables @@ -70,27 +70,27 @@ All calculations will use the following variables: - [dU](/environmental-footprint/environmental-footprint/concepts/##du-duration-of-use): duration of use of the equipment included in the study -- [DDV](/environmental-footprint/environmental-footprint/concepts/#ddvdc-datacenter-lifespan): lifespan +- [DDV](/environmental-footprint/environmental-footprint/concepts/#ddvdc-data-center-lifespan): lifespan - [PuissEqt](/environmental-footprint/environmental-footprint/concepts/#puisseqt-rated-power): rated power of the equipment -- [PuissCommDC](/environmental-footprint/environmental-footprint/concepts/#puisscommdc): proportion of the datacenter's installed power reserved by customers +- [PuissCommDC](/environmental-footprint/environmental-footprint/concepts/#puisscommdc): proportion of the data center's installed power reserved by customers - [FE](/environmental-footprint/environmental-footprint/concepts/#emission-factor): emission factor -- [%mutualisation](/environmental-footprint/environmental-footprint/concepts/#mutualisation): mutualization factor +- [%mutualization](/environmental-footprint/environmental-footprint/concepts/#mutualization): mutualization factor Refer to the [Environmental Footprint concepts page](/environmental-footprint/concepts/) for more information about each of the concepts above. -### Datacenter and technical environment +### Data center and technical environment -To calculate the impact of the datacenter and the technical environment, it is necessary to have either a preliminary study carried out by the hardware suppliers and datacenter administrators or a quote including all the components. Without such a study, we have chosen to use [ADEME data](https://data.ademe.fr/) to evaluate the impact of the construction of the datacenter and technical environment (air conditioning and power supply system). +To calculate the impact of the data center and the technical environment, it is necessary to have either a preliminary study carried out by the hardware suppliers and data center administrators or a quote including all the components. Without such a study, we have chosen to use [ADEME data](https://data.ademe.fr/) to evaluate the impact of the construction of the data center and technical environment (air conditioning and power supply system). -To allocate the environmental impact of the manufacturing of the datacenter and the technical environment we multiply the proportion of the datacenter lifespan that corresponds to the device's usage time by the specific equipment's power usage relative to the total power reserved by customers in the datacenter by the datacenter emission factor.  +To allocate the environmental impact of the manufacturing of the data center and the technical environment we multiply the proportion of the data center lifespan that corresponds to the device's usage time by the specific equipment's power usage relative to the total power reserved by customers in the data center by the data center emission factor. #### Calculation example -For the use of an Elastic Metal server with a power of 110w for 100 hours in a 2000m2 datacenter which has a power of 3000 kw (3e+6w) and a lifespan of 25 years (219 000 hours) and considering via ADEME estimates that the impact of the manufacturing of this datacenter and its technical environment is 3.3e+6 kgCo2e, we make the following calculation: +For the use of an Elastic Metal server with a power of 110w for 100 hours in a 2000m2 data center which has a power of 3000 kw (3e+6w) and a lifespan of 25 years (219 000 hours) and considering via ADEME estimates that the impact of the manufacturing of this data center and its technical environment is 3.3e+6 kgCo2e, we make the following calculation: ```math DC&TEenv = (100 / 219 000) * (110 / 3e+6w) * 3,3e+6 = 0,055 kgCO2e @@ -130,7 +130,7 @@ ServerManufacturing = (100 / 52560) * 850 = 1,62 kgCO2e Therefore 1,62 kgCO2e is added to the total manufacturing impact for the use of this server. -### Cross-IT Equipment & stock +### Cross-IT equipment & stock @@ -138,7 +138,7 @@ Our calculation will also incorporate the environmental footprint of all transve To determine their manufacturing impact, we add the environmental footprint of each machine hosting these transversal tools over the duration of customer usage. This aggregated impact will then be divided by the total number of customers. A "customer" is defined as an active organization, that is to say an organization which consumes and which is billed. -To determine stock manufacturing impact, we will divide the sum of the impact of all hardware components in stock by the total number of servers.  +To determine stock manufacturing impact, we will divide the sum of the impact of all hardware components in stock by the total number of servers. ### Non-IT cross-functional elements @@ -159,7 +159,6 @@ This data is availlable for: * FR-PAR-3 * NL-AMS-1 - For each Scaleway product or service in these Availability Zones, we calculate the water consumption based on its energy consumption. To estimate the water consumption by multiplying the total energy consumption for each service by the [Water Usage Effectiveness (WUE)](/environmental-footprint/environmental-footprint/concepts/#water-usage-effectiveness), as such: @@ -173,11 +172,10 @@ Water Consumption (liters) = Energy Consumption (kWh) × WUE (liters/kWh) At Scaleway we currently collect power consumption metrics for Elastic Metal servers. Using an Elastic Metal server as an example, we can assume that: - A server consumes 500 kWh of energy per month. -- The WUE of the datacenter (PAR-DC5) is 0,014 liters/kWh. +- The WUE of the data center (PAR-DC5) is 0,014 liters/kWh. Therefore, the total water consumption for the server would be: ``` 500 kWh × 0.014 liters/kWh = 7 liters/month -``` - +``` \ No newline at end of file diff --git a/environmental-footprint/environmental-footprint/concepts.mdx b/environmental-footprint/environmental-footprint/concepts.mdx index e355ced251..a53926a497 100644 --- a/environmental-footprint/environmental-footprint/concepts.mdx +++ b/environmental-footprint/environmental-footprint/concepts.mdx @@ -10,9 +10,9 @@ dates: validation: 2024-09-11 --- -## DDV_DC (Datacenter Lifespan) +## DDV_DC (Data center Lifespan) -This value indicates the lifespan of a datacenter; if the value is not available, it can be estimated. For example `DDV_DC` = 25 years. +This value indicates the lifespan of a data center; if the value is not available, it can be estimated. For example `DDV_DC` = 25 years. ## dU (Duration of use) @@ -53,21 +53,21 @@ For each stage of the life cycle, the environmental impact is assessed based on In the context of Scaleway, the LCA can be used to assess the environmental impact of the entire life cycle of cloud services, including the extraction of raw materials for the manufacturing of hardware equipment, energy production to power data centers, the manufacturing and distribution of IT equipment, the use of cloud services by customers, and the end of life of equipment. Data on energy consumption, greenhouse gas emissions, water consumption, waste production, etc., must also be collected and analyzed for each stage of the life cycle. -## mutualisation +## Mutualization -This factor is equivalent to [PuissEqt](/environmental-footprint/environmental-footprint/concepts/#puisseqt-rated-power) and PuissDisponibleDC, which is the nominal power available for Scaleway at the datacenter. For shared equipment, such as management servers and network equipment of the datacenter, this factor is applied. +This factor is equivalent to [PuissEqt](/environmental-footprint/environmental-footprint/concepts/#puisseqt-rated-power) and PuissDisponibleDC, which is the nominal power available for Scaleway at the data center. For shared equipment, such as management servers and network equipment of the data center, this factor is applied. ## PuissCommDC -This value is defined by the ADEME PCR as the proportion of a datacenter's installed power reserved for users. +This value is defined by the ADEME PCR as the proportion of a data center's installed power reserved for users. ## PUE (Power Usage Effectiveness) -PUE is a key indicator used to measure the energy efficiency of data centers. It was created by [The Green Grid](https://www.thegreengrid.org/), an organization dedicated to improving the energy efficiency of datacenters. +PUE is a key indicator used to measure the energy efficiency of data centers. It was created by [The Green Grid](https://www.thegreengrid.org/), an organization dedicated to improving the energy efficiency of data centers. -The PUE represents the ratio between the total amount of energy consumed by a datacenter and the energy used directly to power IT equipment (servers, storage, networks). +The PUE represents the ratio between the total amount of energy consumed by a data center and the energy used directly to power IT equipment (servers, storage, networks). -It is a key factor in estimating the energy efficiency of data centers and, by extension, their environmental impact. The lower the PUE, the more energy-efficient the datacenter, which translates into lower greenhouse gas emissions and better sustainability performance. +It is a key factor in estimating the energy efficiency of data centers and, by extension, their environmental impact. The lower the PUE, the more energy-efficient the data center, which translates into lower greenhouse gas emissions and better sustainability performance. ## PuissEqt (Rated power) @@ -75,7 +75,7 @@ This value is defined by the ADEME PCR as how much electrical power a particular ## Water Usage Effectiveness -Water Usage Effectiveness (WUE) is a metric used to measure the water consumption efficiency of a datacenter. It is defined as the amount of water used by a datacenter in liters, per kilowatt-hour (kWh) of energy consumed. +Water Usage Effectiveness (WUE) is a metric used to measure the water consumption efficiency of a data center. It is defined as the amount of water used by a data center in liters, per kilowatt-hour (kWh) of energy consumed. The calculation is performed using the following formula: diff --git a/environmental-footprint/environmental-footprint/how-to/track-monthly-footprint.mdx b/environmental-footprint/environmental-footprint/how-to/track-monthly-footprint.mdx index 06d7bd4d11..048b982bdd 100644 --- a/environmental-footprint/environmental-footprint/how-to/track-monthly-footprint.mdx +++ b/environmental-footprint/environmental-footprint/how-to/track-monthly-footprint.mdx @@ -31,17 +31,17 @@ The environmental footprint estimation tool is currently in private beta. Sign u 2. Click the next to the month for the report you want to download. The monthly report is downloaded to your local computer in PDF format. 3. Open the PDF file. -4. Read through the document considering the following elements on the page: +4. Read through the document, considering the following elements on the page: - **1.** The start and end date of the period being tracked (month). - **2.** The name of your Organization. - - **3.** The total carbon footprint of your Organization per month, which takes into account the impact of the **manufacture** and **use** of all the components that run your active Scaleway products in relation to the each service's useful life. + - **3.** The total carbon footprint of your Organization per month, which takes into account the impact of the **manufacture** and **use** of all the components that run your active Scaleway products in relation to each service's useful life. - For a detailed description of how the carbon emission are calculated, refer to the [Environmental Footprint calculation breakdown](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page. + For a detailed description of how the carbon emissions are calculated, refer to the [Environmental Footprint calculation breakdown](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page. - - **4.** The total water consumption of your Organization per month, which is calculated on the basis of the [Water Usage Effectiveness (WUE)](/environmental-footprint/environmental-footprint/concepts/#water-usage-effectiveness) of the datacentes in which each of your services are located, as well as the services' electricity consumption. + - **4.** The total water consumption of your Organization per month, which is calculated on the basis of the [Water Usage Effectiveness (WUE)](/environmental-footprint/environmental-footprint/concepts/#water-usage-effectiveness) of the data centers in which each of your services are located, as well as the services' electricity consumption. For a detailed description of how the water consumption is calculated, refer to the [Water Consumption section](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator/#water-consumption) of the Environmental Footprint calculation breakdown documentation page. @@ -55,6 +55,4 @@ For example, if you start your Elastic Metal server on the 15th of the month and Currently, for the electricity consumption, which is part of the calculation, we rely on estimates based on internal tests in which the Elastic Metal servers were tested in different configurations. We will soon provide an electricity consumption agent to get your exact electricity consumption and provide more accurate reports. - - - + \ No newline at end of file diff --git a/faq/databases-for-postgresql-and-mysql.mdx b/faq/databases-for-postgresql-and-mysql.mdx index ce91a9f7fa..3a9e54eb34 100644 --- a/faq/databases-for-postgresql-and-mysql.mdx +++ b/faq/databases-for-postgresql-and-mysql.mdx @@ -49,7 +49,7 @@ See our documentation on [upgrading a Database for PostgreSQL](/tutorials/upgrad **PostgreSQL** -To import data into your Managed Database for PostgreSQL, export your data using the `pg_dump` command in a first step: +To import data into your Managed Database for PostgreSQL, export your data using the `pg_dump` command: ```pg_dump -h OLD_DB_IP -p OLD_DB_PORT -U OLD_DB_USERNAME -F c -b -v -f "/usr/local/backup/database.backup" DATABASE_NAME``` @@ -89,9 +89,9 @@ Automatic backups are enabled by default. It is possible to disable them at any It is also possible to launch manual backups by clicking on the **Create a backup** button in the **Backups** tab. -## Are my active and standby database nodes in a high-availability cluster hosted in the same datacenter? +## Are my active and standby database nodes in a high-availability cluster hosted in the same data center? -In a high-availability cluster, active and hot standby nodes are indeed located in the same datacenter but in two separate racks. +In a high-availability cluster, active and hot standby nodes are indeed located in the same data center but in two separate racks. The idea is to offer the best performance to our users by reducing latency between active and hot standby nodes, as we use a sync replication process between the nodes. ## What is the Private Networks feature for Database Instances? @@ -139,4 +139,4 @@ You can use the [Read Replica feature](/managed-databases/postgresql-and-mysql/h ## If my main node becomes unavailable, is my Read Replica automatically promoted to the main node? -No. To promote a Read Replica to the main node, follow the [How to promote a Read Replica](/managed-databases/postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) procedure. +No. To promote a Read Replica to the main node, follow the [How to promote a Read Replica](/managed-databases/postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) procedure. \ No newline at end of file diff --git a/faq/dedibox.mdx b/faq/dedibox.mdx index 1af0aa334d..22c103a345 100644 --- a/faq/dedibox.mdx +++ b/faq/dedibox.mdx @@ -19,7 +19,7 @@ We offer five ranges of Dedibox servers: **Start**, **Pro**, **Core**, **Store** The delivery of Dedibox dedicated servers is ultra-fast: 2 minutes on average. Next, choose your operating system in our library or install your ISO image directly. Any configuration displayed on our website is available in stock for instant delivery. ### Where are the Dedibox dedicated servers hosted? -All Dedibox servers and associated services are hosted in our Paris & Amsterdam datacenters. We also have a Warsaw datacenter. +All Dedibox servers and associated services are hosted in our Paris & Amsterdam data centers. We also have a Warsaw data center. ### Is my data secure? Scaleway does not have access to your data; however, you are responsible for your backups and the redundancy systems to be put in place to ensure continuity of service even in the event of hardware failure. @@ -83,8 +83,8 @@ They are ideal for hosting websites, web applications, development environments, ### What ranges of Dedibox VPS are available? Currently, we offer two ranges of Dedibox VPS: - * **Dedibox VPS START**: Ideal for smaller projects and development, offering 1 to 16 vCores, 1 to 32GB RAM, and SATA SSD storage ranging from 10GB to 320GB. - * **Dedibox VPS PRO**: Designed for production workloads, with 1 to 16 vCores, 1 to 16GB RAM, and NVMe storage ranging from 20GB to 640GB. + * **Dedibox VPS START**: Ideal for smaller projects and development, offering 1 to 16 vCores, 1 to 32 GB RAM, and SATA SSD storage ranging from 10 GB to 320 GB. + * **Dedibox VPS PRO**: Designed for production workloads, with 1 to 16 vCores, 1 to 16 GB RAM, and NVMe storage ranging from 20 GB to 640 GB. ### What are the available locations for Dedibox VPS? Dedibox VPS are available in 60+ different locations worldwide, allowing you to deploy a Dedibox VPS as close as geographically possible to your user base. @@ -133,4 +133,4 @@ If you exceed this limit, your connection speed will be reduced for the remainde The speed of your connection will return to normal at the start of the next billing cycle when your data allocation resets. ### How secure is a Dedibox VPS? -Each Dedibox VPS is isolated from other virtual servers on the same host, ensuring security. However, best security practices, including regular updates, strong passwords, and firewall configurations, are essential to enhance security further. +Each Dedibox VPS is isolated from other virtual servers on the same host, ensuring security. However, best security practices, including regular updates, strong passwords, and firewall configurations, are essential to enhance security further. \ No newline at end of file diff --git a/faq/loadbalancer.mdx b/faq/loadbalancer.mdx index b5f5a66fbc..652f5cb321 100644 --- a/faq/loadbalancer.mdx +++ b/faq/loadbalancer.mdx @@ -1,7 +1,7 @@ --- meta: title: Load Balancer FAQ - description: Discover Scaleway Load Balancer and find the answers to all your questions about flexible IP addresses, IPv6, multicloud offers and more. + description: Discover Scaleway Load Balancer and find the answers to all your questions about flexible IP addresses, IPv6, multi-cloud offers and more. content: h1: Load Balancer dates: @@ -15,7 +15,7 @@ productIcon: LbProductIcon Load Balancers are highly available and fully managed Instances, configured to distribute workload across a set of backend servers. They ensure the scaling of applications while securing their continuous availability. Load Balancers are therefore commonly used to improve the performance and reliability of websites, applications, databases, and other services. Scaleway Load Balancer monitors the availability of your backend servers via health checks. If it detects that a server is down, it rebalances the load between the rest of the servers, making your applications highly available for users. -A Load Balancer can be used as frontend for any Instance type, even if it is not a Scaleway resource, thanks to the [multicloud feature](/faq/loadbalancer/#what-is-the-difference-between-multicloud-and-non-multicloud-offers). +A Load Balancer can be used as frontend for any Instance type, even if it is not a Scaleway resource, thanks to the [multi-cloud feature](/faq/loadbalancer/#what-is-the-difference-between-multi-cloud-and-non-multi-cloud-offers). ## Can I use Load Balancers with other products? @@ -48,13 +48,13 @@ If you want to know more about the failover system, read [our article about stre No, this is not necessary. Your Load Balancer can reach your backend servers via their private IP addresses on a Private Network, as long as the Load Balancer and servers are all in the same region. -## What is the difference between multicloud and non multicloud offers? +## What is the difference between multi-cloud and non multi-cloud offers? -Multicloud means that you can backend servers that are neither Instances, nor Elastic Metal servers, nor Dedibox dedicated servers. These can be services from other cloud platforms such as Amazon Web Services, Digital Ocean, Google Cloud, Microsoft Azure or OVH, but also on-premises servers hosted in a third-party datacenter. +Multi-cloud means that you can backend servers that are neither Instances, nor Elastic Metal servers, nor Dedibox dedicated servers. These can be services from other cloud platforms such as Amazon Web Services, Digital Ocean, Google Cloud, Microsoft Azure or OVH, but also on-premises servers hosted in a third-party data center. Unlike the multi-cloud offers, non-multi-cloud offers allow you to add only backend servers part of the Scaleway ecosystems which include Instances, Elastic Metal servers, and Dedibox dedicated servers. -To take advantage of multicloud, you must choose a compatible Load Balancer offer type when creating your Load Balancer, or [resize](/network/load-balancer/how-to/resize-lb/) to such an offer afterwards. +To take advantage of multi-cloud, you must choose a compatible Load Balancer offer type when creating your Load Balancer, or [resize](/network/load-balancer/how-to/resize-lb/) to such an offer afterwards. ## What are the communication protocols currently supported? @@ -78,4 +78,4 @@ A health check is one of the core concepts for a well-functioning Load Balancer. ## Can I set up a caching service for my load balanced application? -Yes, this is possible with Scaleway's [Edge Services](/network/edge-services/) product, currently in Public Beta. By creating an Edge Services pipeline for your Load Balancer, you can access Edge Services caching service reduce load on your origin. \ No newline at end of file +Yes, this is possible with Scaleway's [Edge Services](/network/edge-services/) product, currently in Public Beta. By creating an Edge Services pipeline for your Load Balancer, you can access Edge Services caching service reduce load on your origin. \ No newline at end of file diff --git a/faq/objectstorage.mdx b/faq/objectstorage.mdx index 3626662d92..b035456d6f 100644 --- a/faq/objectstorage.mdx +++ b/faq/objectstorage.mdx @@ -20,7 +20,7 @@ Scaleway provides an integrated UI in the [console](https://console.scaleway.com - batch deletion is limited to 1000 objects. - empty files are not reported as empty folders. -We provide an Amazon Amazon S3-compatible API for programmatic access or usage with any compatible software. Therefore, we recommend using dedicated tools such as `s3cmd` to manage large data sets. +We provide an Amazon S3-compatible API for programmatic access or usage with any compatible software. Therefore, we recommend using dedicated tools such as `s3cmd` to manage large data sets. ## How am I billed for Object Storage? @@ -31,14 +31,14 @@ We provide an Amazon Amazon S3-compatible API for programmatic access or usage w | Requests | Included | | Ingress | Included | | Bucket websites feature | Free | -| Egress fees* | 75 GB free every month, then €0.01/GB | +| Egress fees* | 75 GB free every month, then €0.01/GB | \* Egress fees include external outgoing data transfer and inter-region data transfers (PAR\<->AMS / PAR\<->WAW / AMS \<-> WAW). Intra-regional data transfers are free of charge. Refer to our [Cold Storage FAQ](/faq/objectstorage/#cold-storage) for more information on Scaleway Glacier billing. - Chia farming on Scaleway Object Storage that occurs without prior authorization will be billed at €0.08 per GB. [Read our blogpost to learn more](https://www.scaleway.com/en/blog/scaleway-and-chia/). + Chia farming on Scaleway Object Storage that occurs without prior authorization will be billed at €0.08 per GB. [Read our blog post to learn more](https://www.scaleway.com/en/blog/scaleway-and-chia/). ## How can I benefit from the Object Storage free trial? @@ -151,7 +151,7 @@ Each Scaleway Project can use up to 250 TB of Object Storage resources. If you w Scaleway offers three storage classes: -- `Standard (Multi-AZ)`: your data is secured by distributing it across three different [Availability Zones (AZ)](/storage/object/concepts/#region-and-availability-zone). In the event of a complete datacenter failure in an AZ, we are still able to rebuild your data and make it accessible. This is the system we call Multi-AZ (one datacenter per AZ, three AZs per region). The Standard class is available in [all regions](/storage/object/concepts/#region-and-availability-zone). +- `Standard (Multi-AZ)`: your data is secured by distributing it across three different [Availability Zones (AZ)](/storage/object/concepts/#region-and-availability-zone). In the event of a complete data center failure in an AZ, we are still able to rebuild your data and make it accessible. This is the system we call Multi-AZ (one data center per AZ, three AZs per region). The Standard class is available in [all regions](/storage/object/concepts/#region-and-availability-zone). - `One Zone - Infrequent Access`: your data is stored across three different racks in a single [Availability Zone (AZ)](/storage/object/concepts/#region-and-availability-zone). This storage class is best suited for secondary backups and recreatable data. The One Zone - IA class is available in [all regions](/storage/object/concepts/#region-and-availability-zone). @@ -225,7 +225,7 @@ We recommend that you use Glacier to archive data that you may need only once or The time it takes to restore an object depends on the size of the object and if [multipart](/storage/object/concepts/#multipart-uploads) is configured. It can take anywhere from a few minutes to 24 hours for restore to start (for objects larger than 1 MB). Unfortunately, we are unable to provide estimates of how long data retrieval takes for each use case. - To facilitate the steps of restoration and ensure a fast restitution of your data, we recommend you use average-sized files (larger than 1 MB). + To facilitate restoration and ensure the fast restitution of your data, we recommend you use average-sized files (larger than 1 MB). Find out [how to restore an object from Glacier](/storage/object/how-to/restore-an-object-from-glacier/) on our dedicated page. diff --git a/network/load-balancer/reference-content/public-private-accessibility.mdx b/network/load-balancer/reference-content/public-private-accessibility.mdx index caca20ef98..fc4f588736 100644 --- a/network/load-balancer/reference-content/public-private-accessibility.mdx +++ b/network/load-balancer/reference-content/public-private-accessibility.mdx @@ -32,7 +32,7 @@ A Load Balancer is defined as public when you choose the "public" accessibility - It can optionally have an additional public IPv6 address. - The Load Balancer is accessible over the public internet via its public IP address(es), but can optionally also be attached to up to eight different Private Networks. - It can be configured or deleted using the Scaleway API, console, CLI, Terraform or other devtools. -- It provides its metrics to [Scaleway Cockpit](/observability/cockpit/concepts/#cockpit), allows the use of Let's Encrypt certificates, and (if the appropriate Load Balancer type is selected), supports multicloud IP addresses for its backend servers. +- It provides its metrics to [Scaleway Cockpit](/observability/cockpit/concepts/#cockpit), allows the use of Let's Encrypt certificates, and (if the appropriate Load Balancer type is selected), supports multi-cloud IP addresses for its backend servers. @@ -46,7 +46,7 @@ A Load Balancer is defined as private when you choose the "private" accessibilit - It can be configured or deleted using the Scaleway API, console, CLI, Terraform, or other devtools. - It provides its metrics to [Scaleway Cockpit](/observability/cockpit/concepts/#cockpit), even though there is no traffic. - It does not allow the use of a Let's Encrypt [certificate](#certificate) - only imported certificates are supported. -- It does not support multicloud IP addresses for its backend servers, since it is not directly connected to the internet. Routes to them are thus, not guaranteed. +- It does not support multi-cloud IP addresses for its backend servers, since it is not directly connected to the internet. Routes to them are thus, not guaranteed. A private Load Balancer can be used to balance requests between backends internally, where your backends' clients are in the same Private Network as the Load Balancer. The security of your infrastructure is strengthened, as the Load Balancer does not have a public IP address and is not accessible over the public internet. @@ -54,5 +54,4 @@ A private Load Balancer can be used to balance requests between backends interna When you attach a private Load Balancer to multiple Private Networks, it has an IP address in each one. The Load Balancer can then forward traffic to any resource or service attached to any of its Private Networks, thus allowing inter-Private-Networks load balancing. Scaleway's managed DNS also makes it possible to contact the Load Balancer over the Private Network without knowing its IP address (using `lb-name.pn-name`, which then resolves to its private IP address). - - + \ No newline at end of file diff --git a/tutorials/create-esxi-cluster-dedibox/index.mdx b/tutorials/create-esxi-cluster-dedibox/index.mdx index 4aa7502063..a87bb8063e 100644 --- a/tutorials/create-esxi-cluster-dedibox/index.mdx +++ b/tutorials/create-esxi-cluster-dedibox/index.mdx @@ -15,7 +15,7 @@ dates: --- - Due to VMware's acquisition by Broadcom, the free edition of VMware vSphere Hypervisor is no longer available on the VMware website. For more details, check out [the EOL of free vSphere Hypervisor](https://knowledge.broadcom.com/external/article?legacyId=2107518). Please note that the following content is provided as-is, without any guarantee of functionality. + Due to VMware's acquisition by Broadcom, the free edition of VMware vSphere Hypervisor is no longer available on the VMware website. For more details, check out [the EOL of free vSphere Hypervisor](https://knowledge.broadcom.com/external/article?legacyId=2107518). Note that the following content is provided as-is and does not guarantee functionality. We suggest considering alternative hypervisors such as Proxmox. You can learn how to [deploy virtual machines with Proxmox on Scaleway Dedibox](/tutorials/configure-failover-proxmox/). @@ -49,24 +49,18 @@ In this tutorial, we use VMware vSphere Hypervisor (ESXi) 6.7U3b. This version i 1. Access the server page of your Dedibox in the console and click **Install** to launch the installation via the KVM-over-IP device. 2. Click KVM over IP: -3. A disclaimer window pops up. Make sure you have read and agreed to the terms displayed and click **I ACCEPT**. You will be redirected to your server's status page. 2. Click KVM over IP: - -3. A disclaimer window pops up. Make sure you have read and agreed to the terms displayed and click **I ACCEPT**. You will be redirected to your server's status page. 2. Click KVM over IP: - -3. A disclaimer window pops up. Make sure you have read and agreed to the terms displayed and click **I ACCEPT**. You will be redirected to your server's status page. 2. Click KVM over IP: - -3. A disclaimer window pops up. Make sure you have read and agreed to the terms displayed and click **I ACCEPT**. You will be redirected to your server's status page. n the top of the virtual console window. A pop-up displays. -8. Click **Choose file** (1) and select the downloaded VMware ESXi ISO file. Then click **Map device** (2) to connect the virtual CD-ROM drive to the server. Once done close the pop-up. +3. A disclaimer window pops up. Make sure you have read and agreed to the terms displayed and click **I accept**. You will be redirected to your server's status page. +4. Click **Choose file** (1) and select the downloaded VMware ESXi ISO file. Then click **Map device** (2) to connect the virtual CD-ROM drive to the server. Once done close the pop-up. -9. Reboot your machine from the Dedibox console. -10. Press **F11** on your keyboard, during the boot process, to enter the boot manager: +5. Reboot your machine from the Dedibox console. +6. Press **F11** on your keyboard during the boot process to enter the boot manager: -11. Click **One-shot BIOS Menu** in the boot manager: +7. Click **One-shot BIOS Menu** in the boot manager: -12. Select the **Virtual Optical Drive** to boot the machine from the connected ISO file: +8. Select the **Virtual Optical Drive** to boot the machine from the connected ISO file: The server is booting from the ISO file. Depending on your internet connection, this may take a while. Once ready, the ESXi installer displays. -13. Follow the prompts to complete the installation of VMware ESXi on the machine: +9. Follow the prompts to complete the installation of VMware ESXi on the machine: Repeat the steps above on the second Dedibox server, once the installation of ESXi is completed on the first server. @@ -75,13 +69,12 @@ Repeat the steps above on the second Dedibox server, once the installation of ES Configure the RPN interface on both servers once the installation of both machines is completed. To do so, the first step is to activate the SSH service from the ESXi web interface. -1. Connect to the first Dedibox server by typing the server's IP address in a web browser. The ESXi login displays. Enter your credentials to log in. +1. Connect to the first Dedibox server by typing the server's IP address in a web browser. ESXi login displays. Enter your credentials to log in. 2. Click **Actions** > **Services** > **Enable Secure Shell (SSH)**: -3. SSH is enabled once the following warning displays: **SSH is enabled on this host. You should disable SSH unless it is necessary for administrative purposes.**2. Click **Actions** > **Services** > **Enable Secure Shell (SSH)**: - -3. SSH is enabled once the following warning displays: **SSH is enabled on this host. You should disable SSH unless it is necessary for administrative purposes.** -5. Create new **VMkernel NIC** by clicking on **Networking** > **VMkernel NICs** > **Add VMkernel NIC** and configure it as follows. Make sure to tick the **vMotion** checkbox as it is required in a later part of this tutorial: +3. SSH is enabled once the following warning displays: + _SSH is enabled on this host. You should disable SSH unless it is necessary for administrative purposes._ +5. Create a new **VMkernel NIC** by clicking on **Networking** > **VMkernel NICs** > **Add VMkernel NIC** and configure it as follows. Make sure to tick the **vMotion** checkbox as it is required in a later part of this tutorial: @@ -96,21 +89,21 @@ Configure the RPN interface on both servers once the installation of both machin ``` configstorecli config current get -c esx -g network -k vmknics > vmknics.json ``` -7. Open the VMkernel NIC configuration file in a text editor: +9. Open the VMkernel NIC configuration file in a text editor: ``` vi vmknics.json ``` -8. Replace the MAC address of your RPN VMkernel NIC with your [Virtual MAC](/dedibox-network/ip-failover/how-to/create-virtual-mac/). +10. Replace the MAC address of your RPN VMkernel NIC with your [Virtual MAC](/dedibox-network/ip-failover/how-to/create-virtual-mac/). -9. Import the new configuration: +11. Import the new configuration: ``` configstorecli config current set -c esx -g network -k vmknics -i vmknics.json --overwrite ``` -10. Reboot the machine to activate the new configuration. -11. Enter the ESXi web interface, click **Networking** > **Virtual Switches** > **RPN Switch** and check the IP address of the VMkernel NIC. It now has the RPN IP auto-assigned to the interface via DHCP: +12. Reboot the machine to activate the new configuration. +13. Enter the ESXi web interface, click **Networking** > **Virtual Switches** > **RPN Switch** and check the IP address of the VMkernel NIC. It now has the RPN IP auto-assigned to the interface via DHCP: -12. Reactivte the SSH service and connect to the machine via SSH. -13. Run the following command to add the RPN route: +14. Reactivate the SSH service and connect to the machine via SSH. +15. Run the following command to add the RPN route: ``` esxcfg-route -a 10.88.0.0/13 [YOUR_RPN_GATEWAY_IP] ``` @@ -118,11 +111,11 @@ Configure the RPN interface on both servers once the installation of both machin You can find the RPN gateway either on your server's overview page in the Dedibox console or by following [this guide](/dedibox-network/rpn/how-to/find-rpn-gateway/). -14. Ping the RPN-SAN to check if the RPN connection is working properly: +16. Ping the RPN-SAN to check if the RPN connection is working properly: ``` ping san-1.rpn.online.net ``` -15. Open the file `/etc/rc.local.d/local.sh` in a text editor and add the following lines to it to configure the RPN route automatically during boot: +17. Open the file `/etc/rc.local.d/local.sh` in a text editor and add the following lines to it to configure the RPN route automatically during boot: ``` esxcfg-route -a 10.88.0.0/13 [YOUR_RPN_GATEWAY_IP] exit 0 @@ -133,16 +126,16 @@ Repeat the steps above on the second Dedibox server. ### Connecting the RPN-SAN - The following steps require that you have an [RPN-SAN](https://www.scaleway.com/en/dedibox/storage/) product. + The following steps require an [RPN-SAN](https://www.scaleway.com/en/dedibox/storage/). - To be able to communicate with the RPN-SAN, you need to allow your servers to access it. + To communicate with the RPN-SAN, you must allow your servers to access it. 1. Connect to the Dedibox console and click **Storage** > **RPN-SAN**. -2. Select the SAN you want to configure and click **Manage** -3. Add the server(s) you want to permit to access your SAN services in the list. Optionally you can add RPN subnet IPs. Note that if you use RPNv2, an [additional configuration](/dedibox-network/rpn/how-to/configure-rpnv1-gateway/) is required to access the RPN-SAN. +2. Select the SAN you want to configure and click **Manage**. +3. Add the server(s) you want to permit to access your SAN services in the list. Optionally, you can add RPN subnet IPs. Note that if you use RPNv2, an [additional configuration](/dedibox-network/rpn/how-to/configure-rpnv1-gateway/) is required to access the RPN-SAN. While it is technically possible, it is not recommended to allow more than one server at a time to communicate with the SAN. The iSCSI protocol does not handle concurrency, you may lose all your data if you allow more than one server to access this storage. @@ -154,9 +147,9 @@ Repeat the steps above on the second Dedibox server. ESXi rescans for devices, and you can see the new iSCSI disk in the **Devices** tab of the storage section. -## Adding a new Datastore +## Adding a new datastore -To use the RPN-SAN with ESXi, we need to create a new datastore. To do so, follow these steps: +To use the RPN-SAN with ESXi, we need to create a new datastore. To do so, follow the steps below: 1. Connect to the ESXi web interface, then click **Storage** > **Datastores** > **New Datastore**. 2. Select **Create new VMFS datastore** and click **Next**. @@ -170,10 +163,10 @@ To use the RPN-SAN with ESXi, we need to create a new datastore. To do so, follo 6. The newly created datastore displays in the datastore list and is ready for use: -## Setting-up VMware vCenter Server +## Setting up VMware vCenter Server We now have two ESXi hosts and an RPN-SAN but no possibility to manage both hypervisors from a centralized point. Therefore, we deploy a virtual machine, running on Windows Server 2016 and install the VMware vCenter Server 6.7U3j on this machine. -vCenter is a web-based tool for graphical management of the entire fabric of datacenter, cluster, network, datastore, CPUs, and virtual machines in the form of a dynamic and seamless operating environment. +vCenter is a web-based tool for graphical management of the entire fabric of data center, clusters, networks, datastore, CPUs, and virtual machines in the form of a dynamic and seamless operating environment. To proceed with these steps, you need to configure at least one [failover IP](/dedibox-network/ip-failover/quickstart/) with an associated [virtual MAC address](/dedibox-network/ip-failover/how-to/create-virtual-mac/). If you have not yet configured it, go to your [Dedibox console](https://console.online.net) before proceeding. @@ -183,7 +176,7 @@ vCenter is a web-based tool for graphical management of the entire fabric of dat If you do not have a Windows Server 2016 ISO file, [download](https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016) it directly from Microsoft. -### Creating a Virtual Machine +### Creating a virtual machine 1. Connect to the ESXi web interface of one of the machines. 2. Click **Storage** > **Datastore browser** to browse the contents of your datastores. @@ -195,15 +188,13 @@ vCenter is a web-based tool for graphical management of the entire fabric of dat 4. Create a new virtual machine by clicking on **Virtual Machines** > **Create / Register VM** 5. Select **Create a new virtual machine** and confirm by clicking **Next**. -6. Enter a name for the new virtual machine, and select the compatibility, guest OS family, and guest OS version. Then tick the box to enable Windows Virtualization Based Security and click **Next** to proceed: - -7. Select the storage for the data of your VM and confirm by clicking **Next**.6. Enter a name for the new virtual machine, and select the compatibility, guest OS family and guest OS version. Then tick the box to enable Windows Virtualization Based Security and click **Next** to proceed: +6. Enter a name for the new virtual machine, and select the compatibility, guest OS family, and guest OS version. Then tick the box to enable Windows Virtualization-based Security and click **Next** to proceed: 7. Select the storage for the data of your VM and confirm by clicking **Next**. 9. Verify each setting in the summary of all parameters of the virtual machine, and click **Finish** to launch the VM creation. The virtual machine appears in the list. 10. Click its name: -11. Click **Power on** to switch the VM on. Then click in the preview area to see the graphical output of the server. Follow the Windows installer to complete the installation of Windows Server 2016. Choose the **Full Desktop Experience** version of Windows Server 2016, as it will be required to install the vCenter Server application: +11. Click **Power on** to switch the VM on. Then click the preview area to see the graphical output of the server. Follow the Windows installer to complete the installation of Windows Server 2016. Choose the **Full Desktop Experience** version of Windows Server 2016, as it will be required to install the vCenter Server application: ### Installing VMware vCenter Server @@ -256,9 +247,9 @@ vCenter is a web-based tool for graphical management of the entire fabric of dat 1. Open a web browser and point it to the domain name of your vCenter. Log in using the `administrator@vsphere.local` user and the password set during the installation. The vSphere dashboard displays: -2. Click **Actions** > **New Datacenter** to create a new datacenter. A datacenter is a group of machines. -3. Enter a name for the new datacenter and click **OK**. It appears in the list on the left. -4. Enter the datacenter and click **Actions** > **New Host**. Enter the IP address of your first Dedibox server in the form and click **Next**. +2. Click **Actions** > **New data center** to create a new data center. A data center is a group of machines. +3. Enter a name for the new data center and click **OK**. It appears in the list on the left. +4. Enter the data center and click **Actions** > **New Host**. Enter the IP address of your first Dedibox server in the form and click **Next**. 5. Enter the ESXi login credentials of the machine and click **Next**: @@ -266,24 +257,24 @@ vCenter is a web-based tool for graphical management of the entire fabric of dat 7. vCenter manages all ESXi licenses centrally. Assign a license to the machine and click **Next**: -8. Choose the "Lockdown mode" for ESXi, if the server is locked down it can only be managed from vCenter and the ESXi web interface becomes unavailable. +8. Choose the **Lockdown mode** for ESXi. If the server is locked down, it can only be managed from vCenter and the ESXi web interface becomes unavailable. -9. Select the location of the machine. Currently, we only have one datacenter, so click **Next** to continue: +9. Select the location of the machine. Currently, we only have one data center, so click **Next** to continue: 10. A summary of your settings displays, click **Finish** to import the machine into vCenter Server: Repeat the import for the second server to manage both of them centrally from the vCenter Server. -## Creating a Cluster +## Creating a cluster -A cluster is a group of several machines. When a host is added to a cluster, the resources of the host become part of the resources of the cluster, and all resources of the hosts within it are managed by the cluster. +A cluster is a group of several machines. When a host is added to a cluster, its resources become part of the cluster, and all hosts' resources within it are managed by the cluster. -1. From the **Datacenter** dashboard in your vSphere web interface click **Actions** > **New Cluster**: +1. From the **Data center** dashboard in your vSphere web interface click **Actions** > **New Cluster**: 2. Enter a Name for the cluster and activate the features you want to use: -3. From the cluster quickstart page click **Add** in the **Add Hosts** section. Select the hosts you want to add to the cluster and click **Next**. A summary of the hosts that will be added to the cluster displays. +3. From the cluster quickstart page, click **Add** in the **Add Hosts** section. Select the hosts you want to add to the cluster and click **Next**. A summary of the hosts that will be added to the cluster displays. 4. Click **Next** to continue: @@ -292,7 +283,7 @@ A cluster is a group of several machines. When a host is added to a cluster, the 6. Configure the cluster by clicking on **Configure** in the **Configure cluster** section on the cluster quickstart page: -## Migrating Virtual Machines +## Migrating virtual machines vCenter Server supports the [vMotion technology](https://www.vmware.com/products/vsphere/vmotion.html) for live migration of virtual machines without any downtime. This allows you to: @@ -320,7 +311,7 @@ The virtual machine retains its network identity and connections, ensuring a sea 7. A summary of your migration displays. Click **Finish** to launch the migration process: -8. Once the migration is complete, you see a notification in **Recent Tasks** bar: +8. Once the migration is complete, you will see a notification in the **Recent Tasks** bar: 9. Update the destination host of your failover IP, either from the [Dedibox console](https://console.online.net) or by using the [Dedibox API](https://console.online.net/en/api/). diff --git a/tutorials/install-cassandra/index.mdx b/tutorials/install-cassandra/index.mdx index 06e292797a..109fceccd7 100644 --- a/tutorials/install-cassandra/index.mdx +++ b/tutorials/install-cassandra/index.mdx @@ -94,7 +94,7 @@ The key points to edit are: endpoint_snitch: GossipingPropertyFileSnitch ``` - To be fault-tolerant and to minimize the risk of data loss or downtime, Cassandra distributes data across the cluster. Whenever possible it will ensure that data and backups are stored on a different rack, or datacenter to ensure that the impact of even a failing datacenter will be minimal on the production environment. + To be fault-tolerant and to minimize the risk of data loss or downtime, Cassandra distributes data across the cluster. Whenever possible it will ensure that data and backups are stored on a different rack, or data center to ensure that the impact of even a failing data center will be minimal on the production environment. 2. Edit the `/etc/cassandra/cassandra-rackdc.properties` file on each node and set the DC and rack information. You can use your own naming standard to determine the location of each node. - On Node 1: ``` diff --git a/tutorials/load-overflow-proxmox-and-elastic-metal/index.mdx b/tutorials/load-overflow-proxmox-and-elastic-metal/index.mdx index 90a4609ed4..911b783040 100644 --- a/tutorials/load-overflow-proxmox-and-elastic-metal/index.mdx +++ b/tutorials/load-overflow-proxmox-and-elastic-metal/index.mdx @@ -45,19 +45,19 @@ Finally, we can introduce and configure a Load Balancer to evenly distribute tra ## Preparing Proxmox -1. Log into the Proxmox web interface and select your server in the datacenter view. Then click **Network** in the menu. +1. Log into the Proxmox web interface and select your server in the data center view. Then click **Network** in the menu. 2. Click **Create** > **Linux Bridge**. The configuration wizard displays. Enter a private IP for your Elastic Metal server in CIDR format. The **Bridge port** is the name of your primary network interface, followed by a dot and your VLAN-ID. Tick the boxes **Autostart** and **VLAN aware**, then click **Create** to create the bridge. 3. Click **Apply configuration** to activate the new configuration. -4. Go to the **Datacenter** view and click **Create Cluster**. +4. Go to the **Data center** view and click **Create Cluster**. 5. Enter a name for the cluster and select your Private Network bridge `vmbr1` as the cluster network. Then click **Create** to launch cluster creation. 6. Select the cluster in the cluster list and click **Join Information**. The cluster join information displays. 7. Click **Copy Information** to copy the cluster join information into the clipboard. -8. Go to the Proxmox interface of your second Elastic Metal server and click **Cluster** to enter the cluster configuration from the Datacenter view of the machine. +8. Go to the Proxmox interface of your second Elastic Metal server and click **Cluster** to enter the cluster configuration from the Data center view of the machine. 9. Click **Join Cluster** and paste the cluster join information in the form. 10. Enter your first Elastic Metal server's `root` password and click **Join** to link the machine to the cluster. - The second node appears now in the cluster in the Datacenter view of Proxmox. You can manage both machines using a single interface. Communication between members of the cluster is entirely via your Private Network, ensuring the highest level of security and the lowest latency. + The second node appears now in the cluster in the Data center view of Proxmox. You can manage both machines using a single interface. Communication between members of the cluster is entirely via your Private Network, ensuring the highest level of security and the lowest latency. ## Creating virtual machines diff --git a/tutorials/setup-elastic-metal-proxmox-cluster-with-private-networks/index.mdx b/tutorials/setup-elastic-metal-proxmox-cluster-with-private-networks/index.mdx index 7270fa77ff..40ab8e5df8 100644 --- a/tutorials/setup-elastic-metal-proxmox-cluster-with-private-networks/index.mdx +++ b/tutorials/setup-elastic-metal-proxmox-cluster-with-private-networks/index.mdx @@ -61,7 +61,7 @@ Once the server has rebooted, the Proxmox web interface is available. Instead of [configuring the Private Network interface directly from your server's command line](/bare-metal/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks), we must configure it using the Proxmox interface. -1. Click the Proxmox host in the datacenter menu on the left. The server's dashboard displays. +1. Click the Proxmox host in the data center menu on the left. The server's dashboard displays. 2. Click **Network** in the **System** section of the menu. The network dashboard displays. 3. Click **Create** > **Linux VLAN**. @@ -79,7 +79,7 @@ Instead of [configuring the Private Network interface directly from your server' ## Creating a cluster -1. Click **Cluster** in the Datacenter view of the Promox interface of your first node. The cluster dashboard displays. +1. Click **Cluster** in the data center view of the Promox interface of your first node. The cluster dashboard displays. 2. Click **Create cluster**. 3. Enter a name for the cluster and select your Private Network as the cluster network. Then click **Create**. @@ -87,11 +87,11 @@ Instead of [configuring the Private Network interface directly from your server' 4. Select the cluster in the list and click **Join Information**. The cluster join information displays. 5. Click **Copy Information** to copy the cluster join information into the clipboard. -6. Go to the Proxmox interface of your second node and click **Cluster** to enter the cluster configuration from the datacenter view of the machine. +6. Go to the Proxmox interface of your second node and click **Cluster** to enter the cluster configuration from the data center view of the machine. 7. Click **Join cluster** and paste the cluster join information in the form. 8. Enter your first node's `root` password and click **Join** to link the machine to the cluster. -The second node appears now in the cluster in the Datacenter view of Proxmox. You can manage both machines using a single interface. The communication between members of the cluster is entirely in your Private Network, ensuring the highest level of security and the lowest latency. +The second node appears now in the cluster in the Data center view of Proxmox. You can manage both machines using a single interface. The communication between members of the cluster is entirely in your Private Network, ensuring the highest level of security and the lowest latency. \ No newline at end of file diff --git a/tutorials/stop-outgoing-spam/index.mdx b/tutorials/stop-outgoing-spam/index.mdx index 79e3700b07..05bbd28f2b 100644 --- a/tutorials/stop-outgoing-spam/index.mdx +++ b/tutorials/stop-outgoing-spam/index.mdx @@ -1,11 +1,11 @@ --- meta: - title: Stopping outgoing SPAM + title: Stopping outgoing spam description: This page provides information on how to identify and stop abusive usage of your Instances. content: - h1: Stopping outgoing SPAM + h1: Stopping outgoing spam paragraph: This page provides information on how to identify and stop abusive usage of your Instances. -tags: Instances SPAM +tags: Instances spam categories: - compute dates: @@ -14,13 +14,13 @@ dates: validation_frequency: 24 --- -While the most widely recognized form of SPAM is email SPAM, other SPAM types exist, such as Usenet newsgroup SPAM, SPAM in communities, SPAM in blog comments, and much more. Users concerned by SPAM can contact the abuse helpdesk of the service provider (unknowingly), hosting the machines being abused to distribute these messages. The service provider will inform his customer about the situation. If you have received an abuse complaint about SPAM, immediate action from your side is required to stop the transmission of these unsolicited messages and secure your system. +While the most widely recognized form of spam is email spam, other spam types exist, such as Usenet newsgroup spam, spam in communities, spam in blog comments, and much more. Users concerned by spam can contact the abuse helpdesk of the service provider (unknowingly), hosting the machines being abused to distribute these messages. The service provider will inform his customer about the situation. If you have received an abuse complaint about spam, immediate action from your side is required to stop the transmission of these unsolicited messages and secure your system. ### Understanding what is going on -When you receive an abuse alert for SPAM on one of your machines, an intruder likely gained access to it by either guessing your passwords or by using a security hole that may be present in one of your applications. +When you receive an abuse alert for spam on one of your machines, an intruder likely gained access to it by either guessing your passwords or by using a security hole that may be present in one of your applications. -Your immediate action is required in this case to stop the SPAMs outgoing from the machine. It is recommended to boot the machine in **rescue mode**, to interrupt the outgoing connections as a first step, before proceeding with more in-depth investigations into what is going on: +Your immediate action is required in this case to stop the spams outgoing from the machine. It is recommended to boot the machine in **rescue mode**, to interrupt the outgoing connections as a first step, before proceeding with more in-depth investigations into what is going on: - [Rescue Mode on Instances](/compute/instances/how-to/use-boot-modes/) - [Rescue Mode on Elastic Metal servers](/bare-metal/elastic-metal/how-to/reboot-server/) @@ -146,7 +146,7 @@ The application runs various checks on the file system to identify files that ha ### Checking for suspicious files -To get information on the amount of SPAM sent by the intruder and to see any suspicious logs, it is useful to check the servers' log-files for unusual entries. +To get information on the amount of spam sent by the intruder and to see any suspicious logs, it is useful to check the servers' log-files for unusual entries. The log-files are located in the `/var/log` directory. Different applications create their own log files. You can use the `ls -la` command to retrieve a list of all files and folders available in the directory. @@ -187,6 +187,6 @@ tail -n 50 /mnt/data/var/log/dpkg.log ## Conclusion -In this tutorial, you have learned how to check your server for suspicious files and potential rootkits. It is important that you clean your machine carefully before rebooting it into "normal" mode, as your server will continue to send SPAM if the machine is not thoroughly cleaned. It is recommended for security reasons to reinstall an infected server with a clean and fresh operating system and restore your application from your backups. +In this tutorial, you have learned how to check your server for suspicious files and potential rootkits. It is important that you clean your machine carefully before rebooting it into "normal" mode, as your server will continue to send spam if the machine is not thoroughly cleaned. It is recommended for security reasons to reinstall an infected server with a clean and fresh operating system and restore your application from your backups. Remember always to use strong passwords, protect your server against any intrusion, do not keep unnecessary services running on it, and configure an additional layer of security by installing and configuring a [firewall](/tutorials/installation-uncomplicated-firewall/) and tools like [fail2ban](/tutorials/protect-server-fail2ban/) on it. \ No newline at end of file