Merge branch 'master' into hgw-husky

docker/Dockerfile

@@ -30,7 +30,7 @@ RUN apk upgrade --no-cache --no-progress \
 ################################### BUILDER ################################
 FROM base AS builder 
 
-RUN echo "Rebuild image 1"
+RUN echo "Rebuild image 2"
 # Note: we need to install git here because bundle needs git in the next step
 RUN apk --no-cache add git curl nodejs yarn shared-mime-info
 

plugins/access_profile/README.md

@@ -1,28 +1,31 @@
-# Galvani
-Short description and motivation.
+# Galvani Plugin
+
+This README serves as a central location for plugin-specific information, including setup instructions, configurations, usage examples, or any other relevant details specific to this plugin.
 
 ## Usage
+
 How to use my plugin.
 
 ## Installation
+
 Add this line to your application's Gemfile:
 
 ```ruby
 gem 'galvani'
 ```
 
 And then execute:
+
 ```bash
 $ bundle
 ```
 
 Or install it yourself as:
+
 ```bash
 $ gem install galvani
 ```
 
 ## Contributing
-Contribution directions go here.
 
-## License
-The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+Contribution directions go here.

plugins/audit/README.md

@@ -0,0 +1,3 @@
+# Audit Plugin
+
+This README serves as a central location for plugin-specific information, including setup instructions, configurations, usage examples, or any other relevant details specific to this plugin.

plugins/audit/plugin_help.md

@@ -1,9 +1,9 @@
 #### What is Audit Log?
 
-Audit Log provides an audit trail or change log for Converged Cloud services.
+The Audit Log feature offers a comprehensive audit trail and change log for Converged Cloud services.
 
-It records audit-relevant activities and stores them in a project-specific journal. In the journal, each recorded activity is represented by an audit event. The event describes the performed activity, the outcome and lastly the resources that are affected.
+It captures audit-relevant activities and stores them in a project-specific journal. Within this journal, each recorded activity is represented by an audit event. These events detail the performed action, its outcome, and the affected resources.
 
-This service is not just for auditors! Use it to conduct a root-cause analysis when you run into configuration issues (e.g. downtimes). With the information of the audit events, it is much easier to separate human error from platform malfunctions.
+This service isn't exclusively for auditors. It's a valuable tool for conducting root-cause analysis when encountering configuration issues, such as downtimes. The information provided by audit events significantly simplifies the process of distinguishing between human errors and platform malfunctions.
 
-For now only Keystone events are recorded, additional sources will be added one by one.
+Currently, the system only records Keystone events. However, additional sources will be incorporated incrementally in the future.

plugins/automation/README.md

@@ -0,0 +1,3 @@
+# Automation Plugin
+
+This README serves as a central location for plugin-specific information, including setup instructions, configurations, usage examples, or any other relevant details specific to this plugin.

plugins/automation/plugin_nodes_help.md

@@ -2,8 +2,10 @@
 
 ##### Floating IP reported by the Arc node
 
-By default Arc nodes report the fixed IP and floating IP as a fact from the instance they run on. If the floating IP is not shown check the following:
+By default, Arc nodes report both the fixed IP and floating IP as facts from the instance they are running on. If the floating IP is not displayed, consider the following possibilities:
 
-* There is no floating IP assigned to the instance. If this is the case go the **servers area** and assign a floating IP to your instance.
-* The Arc node is outdated. Check if the Arc node is still running and if it is running with the latest version. Check the documentation for more help.
-* The Arc node is not running on an Openstack instance. In this case cannot be retrieved because the metadata service is not reachable from the instance.
+1. No floating IP is assigned to the instance. In this case, navigate to the **Servers section** and allocate a floating IP to your instance.
+
+2. The Arc node is outdated. Verify that the Arc node is still operational and running the latest version. Consult the documentation for further guidance.
+
+3. The Arc node is not operating on an OpenStack instance. In this scenario, the floating IP cannot be retrieved because the metadata service is inaccessible from the instance.

plugins/block_storage/README.md

@@ -0,0 +1,3 @@
+# Block Storage Plugin
+
+This README serves as a central location for plugin-specific information, including setup instructions, configurations, usage examples, or any other relevant details specific to this plugin.

plugins/cloudops/README.md

@@ -1,28 +1,31 @@
-# Cloudops
-Short description and motivation.
+# Cloudops Plugin
+
+This README serves as a central location for plugin-specific information, including setup instructions, configurations, usage examples, or any other relevant details specific to this plugin.
 
 ## Usage
+
 How to use my plugin.
 
 ## Installation
+
 Add this line to your application's Gemfile:
 
 ```ruby
 gem 'cloudops'
 ```
 
 And then execute:
+
 ```bash
 $ bundle
 ```
 
 Or install it yourself as:
+
 ```bash
 $ gem install cloudops
 ```
 
 ## Contributing
-Contribution directions go here.
 
-## License
-The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
+Contribution directions go here.

plugins/compute/README.md

@@ -0,0 +1,3 @@
+# Compute Plugin
+
+This README serves as a central location for plugin-specific information, including setup instructions, configurations, usage examples, or any other relevant details specific to this plugin.

plugins/compute/plugin_instances_help.md

@@ -2,9 +2,12 @@
 
 ##### Creating new servers
 
-By default new servers you create are not accessible from outside the network they were deployed into. To create a VM with external access follow these steps:
+By default, newly created servers are not accessible from outside their deployment network. To create a VM with external access, follow these steps:
 
-1. Create a new VM instance: since you'll most likely eventually want to login via SSH, be sure to also **create or import an SSH public key** (if you haven't done so already) and specify the key during VM creation. You won't be able to add your key later to an already existing VM.
-2. Once the instance is created and an IP has been assigned from the private network, associate a Floating IP to the instance. Before doing this you will need to allocate one to your project from the External network pool.
-3. The instance is now accessible via the Floating IP you assigned. However, during creation (unless you specified otherwise) it was assigned to your project's Default security group. Before you can access via SSH or ping the instance you need ensure the security group has a rule allowing ingress for TCP port 22 and/or ICMP Type 8 Code 0 respectively. Corresponding egress rules are also required.
-4. You should now be able to access the instance via SSH using ssh [user]@[floating ip]. In most cases the user is `ccloud` (for CoreOS `core`). On older images before March 2017 the user is dependent on the image operating system: for Ubuntu use 'ubuntu', for Cirros use 'cirros', for RHEL use 'fedora' and for SLES use 'root'. You also need to make sure that your SSH client is using the private key corresponding to the public key you have assigned during machine creation.
+1. Create a new VM instance: As you'll likely want to log in via SSH eventually, ensure you create or import an SSH public key (if you haven't already) and specify it during VM creation. Note that you cannot add a key to an existing VM later.
+
+2. Once the instance is created and assigned an IP from the private network, associate a Floating IP with the instance. Before doing this, you'll need to allocate one to your project from the External network pool.
+
+3. The instance is now accessible via the assigned Floating IP. However, during creation (unless specified otherwise), it was assigned to your project's Default security group. Before you can access the instance via SSH or ping it, ensure the security group has rules allowing ingress for TCP port 22 and/or ICMP Type 8 Code 0, respectively. Corresponding egress rules are also required.
+
+4. You should now be able to access the instance via SSH using the command: ssh [user]@[floating ip]. In most cases, the user is 'ccloud' (for CoreOS, use 'core'). On older images (before March 2017), the user depends on the image operating system: for Ubuntu use 'ubuntu', for Cirros use 'cirros', for RHEL use 'fedora', and for SLES use 'root'. Ensure your SSH client is using the private key corresponding to the public key you assigned during machine creation.

plugins/dns_service/README.md

@@ -0,0 +1,3 @@
+# DNS Service Plugin
+
+This README serves as a central location for plugin-specific information, including setup instructions, configurations, usage examples, or any other relevant details specific to this plugin.

plugins/email_service/README.md

@@ -1,33 +1,36 @@
-# EmailService
-Short description and motivation.
+# EmailService Plugin
+
+This README serves as a central location for plugin-specific information, including setup instructions, configurations, usage examples, or any other relevant details specific to this plugin.
 
 ## Usage
+
 How to use my plugin.
 
 ## Installation
+
 Add this line to your application's Gemfile:
 
 ```ruby
 gem 'email_service'
 ```
 
 And then execute:
+
 ```bash
 $ bundle
 ```
 
 Or install it yourself as:
+
 ```bash
 $ gem install email_service
 ```
 
 ## Contributing
-Contribution directions go here.
 
-## License
-The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+Contribution directions go here.
 
 ## TODO LIST
-  * Multi-encoding support - to send plain and templated emails.
-  * Send email with verified domains.
-  
+
+- Multi-encoding support - to send plain and templated emails.
+- Send email with verified domains.

plugins/email_service/plugin_help.md

@@ -1,5 +1 @@
 #### Email Service
-
-##### What it is
-
-##### How to use

plugins/identity/README.md

@@ -0,0 +1,3 @@
+# Identity Plugin
+
+This README serves as a central location for plugin-specific information, including setup instructions, configurations, usage examples, or any other relevant details specific to this plugin.

plugins/image/README.md

@@ -0,0 +1,3 @@
+# Image Plugin
+
+This README serves as a central location for plugin-specific information, including setup instructions, configurations, usage examples, or any other relevant details specific to this plugin.